VIEWS: 15 PAGES: 32 POSTED ON: 2/7/2012
April 2010 ISO TC 204 Plenary Justin McNew 5.9 GHz DSRC Workshop Standards Update 1 Introduction This presentation provides an overview of the status of 1609 and 802.11p standards as of April 2010 • Focus on 1609.3 and 1609.4 Agenda: • Status of standards • Overview of changes in Permanent Use drafts from Trial Use • Review of significant new features • Service request processing • Management data delivery • Timing Advertisements • WSMP extensions • Business perspectives • Message formats (backup charts) | 2 Background Trial Use WAVE standards published • 1609.1-2006 Resource Manager • 1609.2-2006 Security Services for Applications and Management Messages • 1609.3-2007 Networking Services • 1609.4-2006 Multi-channel Operation Full Use standards in development • 1609.0 Architecture • 1609.1 Resource Manager • 1609.2 Security Services for Applications and Management Messages • 1609.3 Networking Services • 1609.4 Multi-channel Operation • 1609.5 Communications Manager (deferred indefinitely) • 1609.11 Over-the-Air Data Exchange Protocol for Intelligent Transportation Systems (ITS) - Electronic Payment Service 802.11p sponsor ballot is complete; forwarding to RevCom for publication | 3 Status 1609.0 Architecture (J Moring) • Informative document; draft posted; expected date late 2010 1609.1 Resource Manager (A Malarky) • Complete replacement of Trial Use functions; now includes logical identities, remote management functions, and timing info security; expected date mid to late 2010 1609.2 Security Services for Applications and Management Messages (W Whyte) • Major update with some features deferred; expected date mid to late 2010 1609.3 Networking Services (J Moring) • Major update; expected date mid 2010 - Sponsor Ballot Closed ~ 92 % approval rate 1609.4 Multi-channel Operation (J Moring) 443 comments (158 on 1609.3, 285 on 1609.4) • Major update; expected date mid 2010 – Sponsor Ballot Closed 1609.11 Over-the-Air Data Exchange Protocol for Intelligent Transportation Systems (ITS) - Electronic Payment Service (D Sumida/J McNew) • New standard; expected date mid to late 2010 – Sponsor Ballot Open 802.11p Wireless Access in Vehicular Environments (WAVE) • Sponsor ballot complete – 131 affirmative votes, 1 negative vote (no comments left to resolve) | 4 1609 standards layer standards Future higher 1609.2 UDP / TCP WSMP 1609.3 IPv6 Management Security LLC 1609.4 WAVE MAC (including channel coordination) 802.11 PHY | 5 1609.3/1609.4 milestones D2.0 published 2009/12/05 Balloting signup January 2010 (IEEE ballot group now closed) Working Group comment period ended 2010/1/14 • Proposed comment resolutions posted D3.0 released 2010/1/31 Working Group sponsor ballot decision 2010/2/4 D3.x to IEEE for editorial review 2010/2/15 D4.0 Sponsor ballot 2010/3/1 – 2010/4/30 • Allows time for one short recirculation Documents published 2010/7/5 • Includes IEEE REVCOM, SASB | 6 1609.3 Scope and Purpose • Scope The scope of this standard is to define services, operating at the network and transport layers, in support of wireless connectivity among vehicle- based devices, and between fixed roadside devices and vehicle-based devices using the 5.9 GHz DSRC/WAVE mode. • Purpose WAVE Networking Services represent layers 3 and 4 of the OSI communications stack. The purpose of this standard is to provide addressing and data delivery services within a WAVE system, providing multiple higher layer entities access to WAVE communication services. Upper layer support includes in-vehicle applications offering safety and convenience to their users. | 7 1609.4 Scope and Purpose • Scope This standard describes multi-channel wireless radio operations outside the context of a basis service set, medium access control (MAC), including the operation of control channel (CCH) and service channel (SCH) interval timing, parameters for priority access, channel switching and routing, management services, and primitives designed for multi-channel operation. • Purpose To enable effective mechanisms that control the operation of upper layer data transfers across multiple channels, without requiring knowledge of PHY parameters, and describe the multi-channel operation channel routing and switching for different scenarios. | 8 Agenda Status of standards Overview of changes in Permanent Use from Trial Use Review of significant new features • Service request processing • Management data delivery • Timing Advertisements • WSMP extensions Business Perspectives • Backup Charts (Message formats) | 9 What hasn’t changed from Trial Use General Control Channel (CCH) and Service Channel (SCH) functions and timing Use of service advertisements (WSAs) to indicate SCH availability Use of WSMP, IPv6, and LLC Use of service and packet prioritization | 10 Major changes from Trial to Full Use 1609.3/1609.4 Aligned with 802.11p Sponsor Ballot version • Including different Timing Advertisement frame, no unique WSA frame Rework of the service request, scheduling and access processes for more flexibility • More flexible options for channel switching (and not switching), e.g., immediate and extended access • Changes in terms: no “WBSS,” “persistence,” “joining,” or “registration” Clearer specification of minimal compliant implementation WSA carried in Vendor Specific Action (VSA) frame • Unsigned WSA option Added optional extension fields in WSA and WSM header for flexibility, capability, and growth Include support of other regulatory domains, e.g., Country info element Little or no specification of requirements by RSU/OBU device type • Removed specification of RSU backside distribution system Support generic management data transfer via VSAs Support for Timing Advertisement (TA) frame and functions Added WSMP Safety extension protocol (1609.3 Annex G), and support for other extensions Added primitives for address change to support anonymity/pseudonymity More explicit security call (for advertisement signing & verification) via new 1609.2 SAPs | 11 Rationale for changes CHANGE RATIONALE Aligned with 802.11p Consistency Rework of the service requests Allow more flexible implementations Specification of minimal compliance Preparation for certification WSA carried in VSA frame Loss of WSA frame in 802.11p; most suitable vehicle for WSA. TA may be used in the future. Optional extension fields in WSM and WSA Flexibility and future-proofing Other regulatory domains Allows operation outside USA No spec of requirements by RSU/OBU type Remove unnecessary constraints; allow other device types Support generic management data transfer Request from A Malarky/MarkIV/1609.1 for remote device configuration Support for Timing Advertisement 802.11p feature felt needed by 1609 group for synchronization; may expand in the future Added WSMP Safety extension protocol Request from J Kenney/Toyota; also supports addressing features in 1609.1 Added primitives for address change Feature felt needed by 1609 group for minimal anonymity capability; may expand in the future Security SAPs Clarifies security processing | 12 Agenda Status of standards Overview of changes in Permanent Use drafts from Trial Use Review of significant new features • Service request processing • Management data delivery • Timing Advertisements • WSMP extensions Business Perspectives • Message formats (backup charts) | 13 Service requests in 1609.3 We previously had the concept of applications registering for service (provider/user), with the service subsequently becoming active based on strict rules Now WME accepts service requests of several types from higher layer entities, and runs an unspecified scheduling algorithm to assign channel access • Requests still stored in MIB • Requests are more flexible, e.g., many possible parameters to match in User Service Request | 14 Service request types Service Request Primary Purpose Channel/interval assignment Message Generation Type Provider Service advertisement/ SCH CCH in CCH interval and SCH VSA frame containing participation in SCH interval; or continuous WSA on CCH SCH access User Service availability notification/ SCH in SCH interval, plus none SCH participation optionally SCH in CCH interval WSM Received message delivery none none CCH Control channel participation CCH in CCH or SCH interval none or both Management data Management data distribution CCH or SCH; CCH or SCH VSA frame with interval or both external data Timing Time distribution CCH or SCH; CCH or SCH TA frame advertisement interval or both | 15 Service flow Provider User Higher Higher WME SECURITY MLME MLME SECURITY WME layer layer Service request processing WaveSecurityServices- Service request SignedWsa.req processing Decide to WaveSecurityServices- assign channel SignedWsa.cfm access MLMEX-WSA.req MLMEX-WSA.cfm WSA MLMEX-SCHSTART.req MLMEX-SCHSTART.cfm MLMEX-WSA.ind MLMEX- WaveSecurityServices- REGISTERTXPROFILE.req SignedWsaValidation.req MLMEX- WaveSecurityServices- REGISTERTXPROFILE.cfm SignedWsaValidation.cfm Decide to assign channel MLMEX-WSA.rsp access Sent if service uses IP MLMEX-SCHSTART.req MLMEX-SCHSTART.cfm MLMEX- REGISTERTXPROFILE.req MLMEX- REGISTERTXPROFILE.cfm Data exchange | 16 Agenda Status of standards Overview of changes in Permanent Use drafts from Trial Use Review of significant new features • Service request processing • Management data delivery • Timing Advertisements • WSMP extensions Business Perspectives • Message formats (backup charts) | 17 Sending general management data Management data is accepted from external management entities Delivered in VSA frames Delivered to peer recipient by Management ID 1609.4 1609.4 1609.3 802.11p 802.11p 1609.3 MLME MLME WME MLME/PLME MLME/PLME WME Extension Extension WME-VSA.req WME-VSA.cfm MLMEX-VSA.req MLMEX-VSA.cfm WME-Notification.ind MLME-VSPECIFIC.req Vendor Specific Action MLME-VSPECIFIC.cfm MLME-VSPECIFIC.ind MLMEX-VSA.ind Repeated WME-VSA.ind periodically | 18 Sending Time Advertisements for clock alignment Timing sender Timing requestor 1609.3 1609.4 802.11p 802.11p 1609.4 1609.3 WME- TimingAdvertisement Service.req WME- TimingAdvertisement Service.cfm MLMEX-TA.req MLME-Timing Advertisement.req Time Advertisement MLME-Timing MLME-Timing Advertisement.ind MLMEX-TA.ind MLMEX-TA.cfm Advertisement.cfm WME-Notification.ind May be repeated MLMEX-TimeSet.req MLMEX-TimeSet.cfm Optional Timing distribution triggered by external entity Timing info may be used by 1609.4 or external entity | 19 Support for WSMP Extensions WSMP-S WSMP WSMP WSMP-S WME WME- WSMS- WsmRequest.req WaveShortMessage. req WSM- WME- WaveShortMessage. WsmRequest.cfm req WSM WSM- WaveShortMessage. ind WSMS-WaveShortMessage.ind External entity delivers short message data to new processing entity • Here WSMP-S specified in 1609.3 Annex G After any processing, transferred via normal WSMP Data is delivered on receipt to peer processing entity (based on Management ID) and finally to the recipient higher layer (based on PSID) | 20 Agenda Status of standards Overview of changes in Permanent Use drafts from Trial Use Review of significant new features • Service request processing • Management data delivery • Timing Advertisements • WSMP extensions Business Perspectives • Backup Charts (Message formats) | 21 One producer’s perspective on the business of 5.9 GHz DSRC Aftermarket devices will drive device penetration levels initially • Infrastructure based applications will drive demand among users/consumers • Supports traveler information services, traffic signal timing (green speed), basic safety messages, commercial vehicle screening and electronic payment applications • Leads to active safety applications Cost of deployment is actually quite reasonable • In the US 133,000 sites nationwide will cost under $1.5 B to deploy and $100 M to $150 M per month to operate • Addresses 80% of intersection accidents • Divide this down to the state/local governments and the cost becomes well within budgetary capabilities • High ROI in terms of congestion relief and accident reduction Interoperability is critical | 22 Agenda Status of standards Overview of changes in Permanent Use drafts from Trial Use Review of significant new features • Service request processing • Management data delivery • Timing Advertisements • WSMP extensions Business Perspectives • Backup Charts (Message formats) | 23 Thank You!!! Justin McNew CTO, Kapsch TrafficCom Inc. email@example.com 24 Protocols Management Plane Data Plane Management UDP / TCP WSMP WAVE Entity IPv6 Security LLC Management WAVE MAC Lower Layer (including channel coordination) PHY Data Frames Management Frames (WSMP, IP) (VSA, TA, other) | 25 WSMP format Red lines indicate WAVE extensions Dotted lines indicate local control info Shading indicates optional Higher layer Peer Transmit MAC User Channel Data Power Expiry PSID Length WSM WME-Wave priority number rate Time data ShortMessage.req address Level WSMP Header WSMP 1 4 Var. 1 2 Var. WAVE DL- Dest_ Channel Data TxPwr_ Expiry WSMP Ext. WSM WSM Priority PSID element UNITDATAX.req address number rate Level Time version fields length data ID LLC 1 1 1 3 2 DSAP SSAP Protocol MA- Dest Channel Data TxPwr_ Expiry Control Ether WSMP WSM Priority = = ID= address number rate Level Time = 0x03 Type Header data UNITDATAX.req 0xAA 0xAA 0x000000 MAC LLC header SNAP header Data field | 26 LLC/SNAP Ethernet Type 0x88DC WSMP Ethernet Type 0x86DD IPv6 LLC not used for management frames Data passed to the MAC: Control fields Data fields Dest Priority ... Channel Data Tx Pwr ... DSAP= SSAP= Control= Protocol EtherType WSMP Header WSM data address number rate Level 0xAA 0xAA 0x03 ID=0 =0x88DC WSMP transmit control LLC header SNAP header Control fields Data fields Dest Priority ... DSAP= SSAP= Control= Protocol EtherType IP Header IP data address 0xAA 0xAA 0x03 ID=0 =0x86DD LLC header SNAP header | 27 New support for WSMP sublayers, e.g., WSMP-S Annex G WSMs are generally delivered by PSID on receipt Networking Services Networking Services WME Higher Higher WSMP LLC MAC/PHY MAC/PHY LLC WSMP layer layer WSM- WaveShortMessage. req WME-WsmRequest.req DL-UNITDATAX.req WME-WsmRequest.cfm MA-UNITDATAX.req MA-UNITDATAX.cfm WSM MA-UNITDATA.ind DL-UNITDATA.ind WSM- WaveShortMessage. Ind Now allow interim delivery by Element ID to sublayer (step e) Sender WSMP-S WSMP WSMP WSMP-S WME Recipient WME- WSMS- WsmRequest.req WaveShortMessage. a req WSM- WME- WaveShortMessage. WsmRequest.cfm req b WSM c WSM- WaveShortMessage. d ind WSMS-WaveShortMessage.ind e f | 28 WSA resides in the 802.11p Vendor Specific Action management frame Higher layer Service WME- info ProviderService.req WME WSA WSS-SignedWSA.req PST WRA Header Security Services Security Security WSS-SignedWSA.cfm WaveService Advertisement Header Trailer WME WSA MLMEX-VSA.req MLME extension Cont- MLME- OID ent WSA VSPECIFIC.req descr. MLME Cate OID Vendor Specific Content gory MAC MAC MAC Vendor Specific Action frame Header Trailer PHY PHY Header Air interface | 29 VSA frame per 802.11/802.11p/1609.4/1609.0 Organization Identifier Vendor-specific content 8 36 4 variable IAB Manage Category =0x00 50 ment ID = 127 C2 4A 4 =3 Vendor specific action frame | 30 WSA format, per 1609.3/1609.2 Vendor Specific Content WSA Content Descriptor 1609Dot2Message =1 SignedMessage per 1609.2 Protocol Type= Protocol Type= WaveService Security WaveService Security version unsecured OR version signed Advertisement Header Advertisement Trailer =2 =0 =2 =1 Unsecured WSA Secured WSA | 31 WAVE Service Advertisement, per 1609.3 1 1 Var. WAVE version/ Extension fields Provider Service Table WAVE Routing Advertisement change count Header 1 2 16 1 16 16 Var. WAVE Router Prefix Default Primary Extension Service Info Channel Info Element IpPrefix lifetime length gateway DNS fields ID=3 KEY Optional Field Lengths in octets 1 4 1 1 Var. 1 1 1 1 1 1 Var. WAVE WAVE Regulat Transmit Service Channel Extension Channel Adapt- Data Extension Element PSID Element ory Power Priority Index fields Number able Rate fields ID=1 ID=2 Class Level May be May be repeated repeated | 32
"1609 Full Use"