Thread Links Date Links
Thread Prev Thread Next Thread Index Date Prev Date Next Date Index

Re: [STDS-802-24] Call for Comments and Teleconference Announcement: ATIS IoT Characteristics Matrix

Hi Tim, Ben, and .24 colleagues.

Here are my comments.

General, I know this is not about radio technology per se, but I see UWB as potentially playing a major role in many of the IOT application areas / and use cases. Primarily this is because of UWB's utility in accurate location and accurate proximity detection, where many IOT use cases are dependent on, or certainly enhanced by, knowing the location of the devices, especially those that are mobile.  A secondary reason is that UWB is generally quite efficient in terms of energy per bit and so can be a good choice for moderate volumes of data transfer. While it may be shorter range than some other types of devices, its pulse based modulation is generally immune to multipath effects, since the receiver often employs a channel matched filter trained on the preamble which then actually uses the multipath reflections to improve performance.  Additionally UWB's higher data rates means messages can be quite short saving power and/or allowing higher density use.

Anyway, I think the IOT Characteristics Matrix could be reviewed and updated with location based services (LBS) in mind.  Nearly every sensor could have a location capability to know where the sensor readings are coming from.  Some examples are given below, just covering the first dozen rows, but I think many of the other rows have potential to add an LBS element.  

LBS is a growth area for wireless IOT, and if we don't include it we are potentially missing a major component of the future.

On "Applications & Devices" sheet:

Cell [D4] Smart city, Smart parking. 
--- add "RF based real time location (TDOA or TWR based)"  One approach (and Decawave has customers implementing this) is to have UWB tagged cars, with sensors on poles (or smart street lamps) acting as the infrastructure anchors to locate the vehicles.

Cell [D6]  Smart Cities, Smart Waste container. 
--- add "RF based real time location / proximity sensor" - It says fixed position, but these are typically mobile on wheels, so it would be of benefit to include some accurate location capability to find them. To know the bin is still in place using infrastructure. To empty the correct one, perhaps only relative location from refuse truck

 Cell [D7]  Smart Cities, Smart Street lighting, and  
 Cell [D10] Smart Buildings. Indoor Smart lighting
--- add "RF based location sensor as installation/maintenance aid, also to be infrastructure for other location services" -- Smart bulbs in network might range to each other to enable a positioning algorithm so that the installers don't have to keep a record of what is installed where. (This could apply to any IOT device installation, not just bulbs).  When a bulb fails because the location is known the network knows where to send the repair team.  Such LBS enabled smart lighting can be the infrastructure for smart parking, finding the smart waste containers, etc or indoors for location services like knowing where people or assets are in the building in real time. 

Cell [D11]  Smart Cities, Smart Buildings,  Smart access control.... 
-- add, "RF based two-way ranging and AOA based presence/proximity detection".  This is a no-brainer (Decawave has a number of different customers employing UWB for access control products).


I would be happy to continue in the same vein if needed, and/or maybe Ben could/would help in this also since he is active in 802.15.4z and au fait with UWB and its LBS capabilities.?


On Fri, 18 Jan 2019 at 14:44, Tim Godfrey <tim.godfrey@xxxxxxxx> wrote:

The ATIS TOPS Council IoT Categorization Focus Group has requested our review and comments on their IoT Characteristics Matrix.
The 802.24 TAG started the review process at the IEEE 802 Wireless Interim in January.  The Matrix with embedded comments and notes from the January Interim is in document  IEEE 802.24-19-0004r1   Background on the matrix and the ATIS Focus Group is available in document IEEE 802.24-19-0006r0

The TOPS council needs our response by the end of February 2019. To allow members of the 802.24.2 TG and others that were not able to attend the January TAG session to contribute to the process, we are issuing a Call for Comments on the matrix.   Please provide comments either in email, or as a document submission to Mentor, referring to the spreadsheet cell(s). Please do not edit the matrix and create new revisions which will be difficult to merge. Please submit comments by February 19th to allow time for consolidating before the teleconference.

There will be a teleconference on Thursday February 21, 09:00 PST, 12:00 EST.  The agenda of this teleconference is to review comment submissions on the matrix, and approve the matrix with all comments to be returned to ATIS TOPS Council.

Teleconference WebEx details below:
Join WebEx meeting  
Meeting number: 647 468 074 
Meeting password: bRWAbY3i 

Join from a video conferencing system or application
Dial 647468074@xxxxxxxxxxxxxx 
You can also dial and enter your meeting number.  

Join by phone 
+1-855-797-9485 US Toll free 
+1-415-655-0002 US Toll 
Access code: 647 468 074 
Global call-in numbers  |  Toll-free calling restrictions    
Can't join the meeting?  

Tim Godfrey

To unsubscribe from the STDS-802-24 list, click the following link:

To unsubscribe from the STDS-802-24 list, click the following link: