1 / 14

IEEE 1609.1 Status June 2009

IEEE 1609.1 Status June 2009. Alastair Malarky MARK IV IVHS amalarky@ivhs.com http://www.ivhs.com 905-624-3020 x 1203. 1609.1 Plan. Sub-group develops ConOps. – Done Mar 09 Sub-group develops functionality it thinks is needed. – Now Done

gagan
Download Presentation

IEEE 1609.1 Status June 2009

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. IEEE 1609.1 StatusJune 2009 Alastair Malarky MARK IV IVHS amalarky@ivhs.com http://www.ivhs.com 905-624-3020 x 1203

  2. 1609.1 Plan • Sub-group develops ConOps. – Done Mar 09 • Sub-group develops functionality it thinks is needed. – Now Done • WG review and comment to functionality. - Next Step • Whole WG should decide on where the functionality should reside. - Next Step • In 1609.2-4 ? • In 1609.1 as a separate standard ? • In profile specs ?

  3. Sub-Group Actions Since Last Meeting • Survey on Naming Convention • Done – but very few replies • Decided to wait until decisions made on functionality location • Retained existing naming for now. • Develop dot1 standard text • Functionality complete but missing primitive and some other details • Draft being posted now to secure site for whole WG feedback on functionality

  4. Sub-Group Actions Since Last Meeting • Updated to reflect 1609.3 and 1609.4 changes • Reflects 9 June versions • Uses Vendor Specific Action frame for WME-WME messaging • Clarified management capabilities • Fully separated data and management messaging • Added locating capability • Security approach, primitives and dot2 changes • Still just starting • Should decide on overall security first

  5. 1609.1 – What is it • Developed to support concept of low cost (low capability) devices • Example : Work Zone • Radar sensors reporting to RSE • Work crew personal alerts from RSE • Message signs dynamically loaded from RSE • Traffic cones with beacons to alert oncoming vehicles

  6. 1609.1 – Functionality • Majority of content is management functionality, e.g. • Over air configuring • Identity – logical, physical, other (TBC) • Sleep • Triggering • Locating • Higher layer interface abstracted relative to 1609.3 • WSM creation inside layer

  7. 1609.1 Functionality • Over Air Command & Request Services • Obtain logical identity (includes anonymity) • Set low end device configuration • temporary (session) & permanent (default) • group configure • Request device configuration/status • Useful to locate all devices also • Send device to sleep

  8. 1609.1 Protocol Stacks Low End device Management device Quite different from Trial Use 1609.1

  9. 1609.1 Identity • Currently have defined Physical & Logical • Physical = Electronic unique identity • Assigned by vendor • Logical identity • Assigned by Management device (session identity) • Used for higher layer access on Management device • Only used over air if required • Added Group identity • Can use for group command operations from Resource Manager(s) • Assigned by deployer/commissioner of device

  10. Sleep & Triggers • Configure sleep with timeout & triggers • Wake on message(s) capability • Control message • App message • Etc. • Wake on external trigger capability • Physical port on device • e.g. sensor (temp), loop detector

  11. Locating Capability • Report to higher layer on probable location: • Location data provided if provided by device • Estimated direction and range if not

  12. 1609.1 Data Messages • Format – extends WSM format • Contains device identity

  13. 1609.1 Over Air Mgmt • Command, Status & Response Messages • Use 802.11 Vendor Specific Action frame

  14. 1609.1 Planning Timeline • 1st Draft (0.6) : June 2009 • Functionality defined • Primitive and some other detail meeting • Ready for functionality review • Aug 2009 • Working Group decides on location of functionality • Sponsor draft – est. Mar 2009

More Related