120 likes | 274 Views
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
E N D
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 • (e.g. can be implemented with simple state machine) • Low cost Multi-application One or more applications may talk to low-capability equipment
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.
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
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
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
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
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
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
Conclusion • 1609.1 is relevant • especially for low capability devices and situational awareness • Work required to update standard • Security : need to define and incorporate