The USA s 5.9 GHz DSRC Prototype Development Program. Dick Schnacke, VP, TransCore ITS World Congress Nagoya Session TP74 10/22/04

Size: px

Start display at page:

Download "The USA s 5.9 GHz DSRC Prototype Development Program. Dick Schnacke, VP, TransCore ITS World Congress Nagoya Session TP74 10/22/04"

Frederick Mills
5 years ago
Views:

1 The USA s 5.9 GHz DSRC Prototype Development Program Dick Schnacke, VP, TransCore ITS World Congress Nagoya Session TP74 10/22/04

2 Topics Prototypes WHAT? Status of activities The schedule Potential rollout scenario

3 5.9 GHz DSRC Prototypes What?

4 5.9 GHz DSRC What Is It? The Next Generation of Short-Range Communications Transmission Range increases 2 orders of magnitude From 10 meters to 1000 meters Transmission Rate increases 2 orders of magnitude From 0.25 Mbps to 25 Mbps Tailored to the hi-speed mobile environment Near-instant access

5 VII Tier 1 Architecture GPS Other Other communications communications: PCS, Cellular PCS, Cellular, etc. GPS Other Other communications communications: PCS, Cellular PCS, Cellular, etc. Vehicle #1 OBU Driver Vehicle #2 OBU Driver Public infrastructure roadside Roadside Unit (RSU) Infrastructure applications Public infrastructure control centers Jurisdictions Message management Data cache Private services WiFi access point ISP Legend Private Public Vehicle

6 U.S. DOT wanted. Fast-paced prototype development program for 5.9 GHz DSRC Industry driven Shared-cost, but heavily funded up front by DOT Goals: Prove the standards Provide standard-compliant operational hardware for the vehicle OEMs Perform testing to confirm vitality of the hardware, reasonableness of certain safety applications, and system acceptance by vehicle users Provide a launching pad for DSRC industry

7 We Have Spectrum Channel 172 Channel 174 Channel 176 Channel 178 Channel 180 Channel 182 Channel GHz GHz Channel 178 used as Control Channel All other channels used as Service Channels Each channel is 10 MHz

8 OSI-Based Architecture Overview Data Plane Management Plane IVN Application Notification Handler WME MIB TSAP Transport Layer (TCP/UDP) Notification Generator IVN API Ethernet NSAP Network Layer (IP) NCM IVN Manager WME WME-MLME SAP MLME MIB Data Link Layer Channelization Channel Switching MLME Channel Switch Decision MLME-PLME SAP PHY Layer PLME MIB PLME

9 Contract for Prototype Development Substantial funding committed Contracted to DSRC Industry Consortium (thru ARINC) Participating members: TransCore Mark IV Raytheon Sirit Four competitors working together???

10 Prototype Project Organization ARINC Raytheon Mark IV TransCore Prototype Steering Group Overall PM Prototype PMs Roger O Connor Highway Electronics Mark IV - - Roger Tong Raytheon - - Doug Kavner Sirit - - Randy Roebuck TransCore - - Filip Weytjens DIC Sirit

12 5.9 GHz DSRC Prototypes Status Standards Design Hardware Development Software Development Test Planning

13 Status Standards

14 The initial standards task Content Support standardization activity Oversee communication security Test the resulting standards Specifically does not say Develop the Standards

15 A small problem - Development of standards had been in work for 4+ years Moving forward slowly Program to develop standard-compliant prototypes soon caught up and passed the standards process The solution: US DOT issued a contract amendment to fund DSRC Industry Consortium to expedite completion of standards

16 IEEE Sub-Working Groups IEEE 1609/1556 Steering Group Members: Tom Kurihara Tom Schaffnit Broady Cash Dick Schnacke Upper Layers Std Sub-Working Group Leader: Ken Cook Sub-Working Group Coordinator Roger O Connor Middle Layers Std Sub-Working Group Leader: Doug Kavner Sub-Working Group Leaders Security Std Sub-Working Group 1556 Leader: Doug Kavner

17 Current status All standards except Security will be delivered to IEEE Working Group by 17 December 2004 Security standard will be delivered in January 2005 Meanwhile, the Radio standard is nearing completion and has been designated by IEEE as p (yes, we re going to be a mobile wireless LAN)

18 Status Design

19 The system design task Content Selection of applications Requirements (Functional, Performance, Testing) Architecture and network topology Prototype development plan

20 Development of scenarios & functionality In-vehicle signing: Icy bridge ahead Prototype Implementation Scenario Trafic center IPv6 Network Configure Message IPv6 Network IPv6 Network layer Ethernet UDP RSU RSU WAVE Radio Icy bridge ahead! SNMP Agent Icy bridge ahead! WME Icy bridge ahead! Broadcast Message WME OBU OBU IPv6 Network layer WAVE Radio UDP Ethernet Be carefull. You are approaching an icy bridge! Inform Driver

21 Functional Dissection of Each Application RSU/OBU Service Channel Transaction RSU OBU Application WME MLME MLME WME Application WME-SET.request (Register ST/WRA) WME MIB WME MIB WME-SET.request (Register ST) WME-SET.confirm MLME-START.request (Register WSIE) CCH Monitoring WME-SET.confirm MLME-START.confirm Transmit Beacon MLME-WAVE.indication (WSIE) Switch to response channel Switch to response channel MLME-JOIN.request MLME-JOIN.confirm MLME-WAVE.request Match AID Link Up Send UST MLME-WAVE.confirm IPv6 Address Config WME-NOTIFY.indication SCH/CCH Switch SCH/CCH Switch Run Application MLME-RESET.request WME-NOTIFY.response MLME-RESET.confirm CCH Monitoring

22 What Makes the Solution Complex? Unlike conventional , communication points are moving about at high speeds Must operate as master/slave when communicating to roadside but as peer-to-peer when vehicles talk directly Must acquire in milliseconds Must change channels in microseconds Must control power dynamically to decrease interferences Must always get the most important message through first Must have bulletproof communications security

23 Architecture and Design Architecture is network based to support: Many applications Comm for other vehicle computers Latest version of TCP/IP: IPv6 Existing IPv4 devices can be supported via gateways Internet can also be a private network App Application MIB MIB SET GET SNMP Engine Ethernet MAC PHY In-Vehicle Network VACM USM OBU UDP IPv6 NMS IVN Mgr NCM Notification Handler Application TRAP Notification Generator Channelization Channelization CCH MAC SCH SCH MAC CCH PHY Data Path Air Interface PST(WRA) UST NCM TRAP Notification Handler Notification Generator PHY RSU Data Path VACM USM UDP IPv6 Internet MIB MIB SNMP Engine SET GET PHY Application Application Ethernet MAC Mgmt/Data Interface Internet The design task is completed NMS Application Application

24 Hardware Platform Division of Task Common hardware for OBU and RSU Flash SDRAM Timers RF Switch RF Filter RF Frontend PA Receiver Frequency Synthesizer RF/IF Transmitter Control Baseband and RF/IF loop Filter I/Q AD I/Q AD External Interface Base Band MAC (PHY) BASE BAND/Mac Configuration Control and Low Memory MAC HOST Interface HOST Interface Bus controller HOST Host uprocessor Crystal Parallel Interface Visual (LEDs) Interface Audio Interface The Radio (Developed by TransCore) Power Supply Power Control Network Interface Serial Interface Development Port The Controller (Developed by Mark IV)

25 Software Platform Division of Task Green: To be delivered by MarkIV Orange: To be delivered by TransCore Grey: Third-party software to be used later

26 Status Hardware Development

27 Realistic Design Considerations NEMA 4 Enclosure RSU Power Supply Omni Directional Ant In Vehicle Computer OBU IBM Compatible Power Supply Power unit Prototype / test article status affects the design

28 Key Requirements are Defined Environmental Temperature, humidity, vibration, shock, etc. Electrical characteristics Installation Mounting provisions & limitations Cabling, connectors, etc. Antennas Memory allocations Bus width, transfer speed, memory size Interfaces Internal & external

29 Major system Elements are Selected Radio chipset Microprocessor Operating System These decisions enable the selection of myriad secondary components and allow start of circuit board layouts. Numerous tasks underway now.

30 Prototype Packaging Concept

31 Status Software Development

32 Software It s always the biggest & hardest job Requirements pretty well defined Software architecture taking shape Certain software decisions dependent on un-made hardware decisions

33 Software functionality being defined Basic Use Cases RSU/OBU OBU Broadcast service RSU OBU Transaction service (2-way message exchange) Support for prioritized applications Network services IPv6 network access for the RSU and the OBU Simple network management protocol WAVE Management Entity PST/UST exchange and processing Channelizer management (Control/service channel switching) Device and application configuration management MAC Layer Random MAC address generation IEEE e Priority control IEEE h Channel switching

34 Status Test Planning

35 Testing Methodology Initial Test Process Development of DRSC Technology: Identify Test Equipment and Test Software Develop Test Procedures (not Certification) Verification Testing of the Prototypes per the Requirements: IEEE a/p IEEE 1609 ASTM E2213 DSRC Prototype Specifications Test UUT for Functionality and Minimum Durability (environmental screening) Demonstrate key application use cases and scenarios * Selection Criteria: Test, Analysis, Modelling, Simulation & Inspection

36 Test Phases Alpha Testing of Radio modules and Development units: Test basic functionality and operation of modules and units. Lab Testing and Evaluation of DSRC Prototypes: Test transmitter and receiver (air interface) for compliance to required standards. Test functionality of prototype for message transmission protocol compliance. Field Testing of DSRC Prototypes: Range (driving) tests for distance, speed, and throughput requirements. Testing of key use cases for end-to-end message and data transmission compliance. Environmental Testing of Final Prototypes: Temperature testing over required range. FCC Pre-screening, but not full certification for prototypes. Customer Witness Testing of Final Prototypes per Test Plan

37 5.9 GHz DSRC Prototypes Schedule

38 Prototype Program Schedule 38 February, 2004 March, 2004 April, 2004 May, 2004 June, 2004 July, 2004 August, 2004 September, 2004 October, 2004 November, 2004 December, 2004 January, 2005 February, 2005 March, 2005 April, 2005 May, 2005 June, 2005 July, 2005 August, 2005 September, 2005 October, 2005 November, 2005 December, 2005 Phase I Kick off Prototype System Design Phase II Kick off Draft Standards Development Development of prototype equipment Hardware Software Integration Evaluation testing Review PDR CDR FDR FPR

39 5.9 GHz DSRC Prototypes Potential Rollout Scenario

40 Realism Present Activities Mid-2004 through mid-2006 Finish standards, test them, re-work as needed Finish the prototype program Test prototypes to exhaustion Design realistic antennas Develop certification procedures

41 Realism Next Activities Mid-2006 through mid-2008 Larger scale tests MDIs (3?) Thousands of OBUs, hundreds of RSUs Stressing the system Design re-works based on above Productizing hardware and software

42 Leading to.. Deployment Decision in mid-2008 (Both Infrastructure & Vehicles) *Announced position of both DOT and Vehicle OEMs

43 A Realistic Scenario DOT Infrastructure Assumption: Mid-2008 deployment decision First safety priority: Intersections Current plan: Equip 400,000 intersections with DSRC beacons over 6 years Those years likely to be: 2009 through 2014

44 A Realistic Scenario Vehicle Implementation Assumption: Mid-2008 deployment decision Normal OEM design/implement cycle: 3 years Some indications this could happen in 2 years Therefore, first vehicles could appear in 2010 Normal model deployment cycle: Start in high-end vehicles & push down Some indications this pushdown could occur more rapidly than usual

45 *Schnacke - educated guesstimate Vehicle Implementation Scenario Using the most optimistic assumptions, a possible scenario is (in millions): Year Vehicles Cumulative out of a U.S. vehicle population of million

46 Summary The 5.9 GHz DSRC Prototype Program is alive and well Prototypes will have capabilities well beyond any presentday systems. Prototypes will become available in late 2005 and will feed into numerous application evaluation projects For more information: Dick Schnacke TransCore

The WAVE Communications Stack: IEEE p, and, September, 2007

The WAVE Communications Stack: IEEE 802.11p, 1609.4 and, 1609.3 September, 2007 WAVE System Components External Systems ROAD SIDE UNIT Covered by WAVE Standards ON-BOARD UNITS External Systems Host Host