1 / 12

IEEE 1609.1 Review

IEEE 1609.1 Review. Alastair Malarky MARK IV IVHS amalarky@ivhs.com http://www.ivhs.com 905-624-3020 x 1203. History : CVO to 1609.1 (today). Common interoperable messaging: Direct access to functions as memory partitions Does not require significant computational resources

blaze-phelps
Download Presentation

IEEE 1609.1 Review

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 Review Alastair Malarky MARK IV IVHS amalarky@ivhs.com http://www.ivhs.com 905-624-3020 x 1203

  2. History : CVO to 1609.1 (today) • Common interoperable messaging: • Direct access to functions as memory partitions • Does not require significant computational resources • (e.g. can be implemented with simple state machine) • Low cost Multi-application One or more applications may talk to low-capability equipment

  3. IEEE 1609.1 (today)

  4. Where 1609.1 fits today 1609.1 IS 15628 : application layer core which provides communication tools for applications based on DSRC. These tools consist of kernels that can be used by application processes via service primitives.

  5. 1609.1 Review Observations • 5.9 GHz has particular relevance to local functions. Less suited for wide-area. • We see a need for low capability devices (outside vehicle) for situational awareness: • Sensors (ice/wet bridge) • Deployable “alerts” (flashing cones) • Non motorized vehicles (bicycle) • Likely limited source power • May be low RF output • Low cost

  6. 1609 Low End Devices • Minimum • Must have 802.11 CSMA • Omni coverage likely • Rx WSA - only if don’t know service channel to use or want PSC • Rx WSMP - likely • Tx WSMP - likely • UDP – probably not • Single PSID device

  7. 1609 Low End Devices • Minimum security • Need to issue authentication (sign) • Can be permanent certs but may need to be dynamic nature to signature • May not need to verify authentication • No encryption • May not need or even have user interface

  8. DSRC Low End Devices • May not be continuously active • Don’t need (or may not support) accurate local time source • Can use repeats of message with timing offsets to ensure some align to receiver • Can obtain timing from incoming messages • Can obtain time of day from more capable device while communicating

  9. DSRC Low End Devices • Knowledge of location may not be possible or needed • Cost/power • Can be loaded into static units • Coarse knowledge can be obtained from more capable device while communicating

  10. Other Aspects • Need common message sets • for interoperability and across range of classes • need abstraction at higher capability device • Need locating capability from higher end device • low granularity angle and crude range or trajectory capability is sufficient for identification of location of remote device from vehicle • maybe RSSI still has value • Possibly also passive systems for mutual location/relative position determination • May need multiple classes of device capability

  11. 1609.1

  12. Conclusion • 1609.1 is relevant • especially for low capability devices and situational awareness • Work required to update standard • Security : need to define and incorporate

More Related