1. IEEE SCC32DSRC Standards Update Clay Collier

2. Review of Steps • Review of existing documentation (completed) • Review current implementations (CVISN, etc.) (completed) • Resolve open issues on data typing and missing elements • Review P1488 methodology and Working Group efforts • Review Data Dictionary element conflicts • Review P1489, Data Dictionary specification • Create technical content for DSRC Data Dictionary in P1489 format • Produce technical content for Message Sets for CVO and ETC

3. Resolve Open Issues: Missing (or “Format-Limited”) Data Elements • World-wide country codes • Codes for credentialing • Weigh Station open/close codes • Physical Lane vehicle is travelling in • Vehicle and Driver Out-Of-Service flags • Multiple VIN fields for double/triple bottoms

4. Missing (or “Format-Limited”) Data Elements • Lock summary information for Border Clearance • Separate codes for oversize/overweight permits • FIPS codes being replaced by ANSI • Driver Signalling values are ambiguous • Shipment Type may need more values • Julian day in roadside date is too limiting

5. Resolve Open Issues: Data Typing • Message Set Template (MST) Group will specify: • Physical quantities and associated units of measure • Currencies • Geographical location - including country/state codes • Telephone numbers • Date and time of day

6. Example 1: Date/Time • Seconds since 1/1/1970 • 60 seconds x 60 minutes x 24 hours x 365 days = ~31 million seconds • Based on 4 bytes, can provide more than 100 years of time measurement • Aging messages: • Year (0..9) decade only -- rolls over every ten years • Day (0..366)

7. Example 2: Location Referencing Second Street Green Street 1 2 3 Maple Street 4 5 Main Street Second Street Ramp Charles Freeway W Charles Freeway E

8. Location Referencing Methods • Link ID • Linear Referencing (mile markers) • Street Address (state, city, street, number) • Coordinates (lat/long) • Street Matching (state, city, street, street) • Combinations • Plaza ID/Lane ID (for ETTM)

9. Link Statistics In the U.S. there are 300,000 road names and 40 million links Chicago: 12,000 road names and 235,000 links Washington, D.C.: 20,000 road names and 161,000 links Los Angeles: 33,000 road names and 700,000 links

10. Next Steps • Review P1488 Message Set methodology and Message Set Working Group results • Create model for P1488 type Message Set representation

11. Review of U.S. - JapanCEN Harmonization Workshop • Consensus that CEN Layers 3 to 7 is appropriate • Existing ministack • Accepted in Europe, likely to be used in Japan • Extensible to other applications • Navigation • Traffic information • Parking

12. International Comparison Japan • 1 million nav systems sold @ ~$2,000 • 150,000 VICS receivers sold @ $200-$500 • Toll roads very expensive Europe • 250,000 nav systems sold @ ~$2,000 • CEN DSRC standard in place U.S. • Huge emerging market • Standards not yet in place

13. New Project Plan Outline • Foreword and Introduction • Scope • References • Definitions and Abbreviations • Architecture • Explanation of the capabilities and interfaces between the DSRC components governed by this standard and other standards • Transponder Resources • Definition and explication of the set of resources that may be present on the transponder, as well as the transponder memory map and the pre-defined fields in read-only memory

14. New Project Plan (continued) • Transponder Commands and Memory Access • Definition and explication of the commands used to access transponder resources • Resource Manager • Definition and explication of the capabilities and interfaces of the Resource Manager in the roadside equipment • ITS Application Messages • ASN.1 Definitions • Binary (PER) • Common Types

15. New Project Plan (continued) • Application Layer • Specification of the Layer 7 services used to connect the Resource Manager to the Layer 2 elements • CEN Tailoring