WP2.4

1. GNSS for INnovative Road Applications WP2.4 Analysis of related specific issues (standardisation, policies, interoperability etc.) Date: 5th November 2009 Place: Dublin Company LOGO

2. WP2.4 Topics and responsibilities • Standardisation – ICC • Policies (including integration with eCall) – ERF • Interoperability – ICC • EGNOS/EDAS – GMV • Authentication – Skysoft • Coordination of 4 and 5, commenting on and providing additional input for drafts from all sub-workpackages – NW WP2.4 Analysis of related specific issues

3. WP2.4 Timetable • 19th June detailed (bullet point) contents of each section • 26th June all provided comments on the contents to ICC • 3rd July ICC distributed revised bullet point contents lists • 31st July drafts of all five sections provided to ICC/NW • ICC distributed to all for comment • 21st August comments on the drafts provided to ICC • ICC/NW coordinated email discussion of contents • 28th August ICC distributed consolidated comments to authors • 20th Oct. final drafts of each section provided to ICC • 26th Oct. ICC distributed final draft of complete D2.4 • 30th Oct. final comments provided on the final draft • 2nd Nov. final version for submission WP2.4 Analysis of related specific issues

4. WP2.4 1. Standardisation • Current status of ISO TS 17575 parts 1-4 (GNSS-based EFC) • Overview • Part 1 – Charging • Part 2 – Communication • Part 3 – Context data • Part 4 - Roaming • Current status of other relevant draft standards: • ISO TS 17573 (EFC architecture) • ISO TS 17574 (security profiles) • ISO TS 12813 and ISO TS 13143 (Compliance check communication) • ISO TS 12855 (Information exchange) • ISO TS 13141 and ISO TS 13140 (Location augmentation) • CEN Project teams • The GMAR initiative • Value added services WP2.4 Analysis of related specific issues

5. WP2.4 2. Policies (including integration with eCall) • Introduction • Key decision makers • European institutions • European GNSS Supervisory Authority • Public administrations of the 27 Member States • Local/regional governments: example of the Netherlands • State-of-the-art EU legislative framework • RUC: a) Eurovignette directive; b) ITS Action Plan; c) Action plan for the applications of EGNOS and Galileo; d) Action plan for urban mobility; e) Interoperability directive • Pricing applications • Traffic information generation, processing and provision • eCall • Human-Machine Interface • Data privacy • Case studies: Netherlands, Germany, Slovenia, Slovakia WP2.4 Analysis of related specific issues

6. WP2.4 3. Interoperability • The Interoperability Directive 2004/52/EC • Background • The role of GNSS • Revised timescales • Overview of the EETS • The Commitée Télépéage and the Member States expert group • The role of GNSS • Expert Group reports • Supporting projects: CESARE I-IV, RCI • The Commission Decision on the EETS • The CESARE Architecture for the EETS: EETS Providers and Toll Chargers • The RCI technical interoperability architecture • Operational provisions in the Decision • Impact of the EETS definition on GINA WP2.4 Analysis of related specific issues

7. WP2.4 4. EGNOS/EDAS • Overview • Description • Technical information • Added value of EDAS • Generic advantages • Applications • EDAS in GINA • Contribution of EDAS to RUC and VAS • EDAS limitations WP2.4 Analysis of related specific issues

8. WP2.4 4. EGNOS/EDAS • Overview • EGNOS CDDS (3rd EGNOS service in addition to OS and SoL) accessible through EGNOS / EDAS • EDAS: EGNOS Data Access Server: commercial EGNOS service for access to information generated by EGNOS system • Opportunity for SPs to deliver EGNOS data to users not always seeing the EGNOS satellites Architecture WP2.4 Analysis of related specific issues

9. WP2.4 4. EGNOS/EDAS Products and services Data Format WP2.4 Analysis of related specific issues

10. WP2.4 4. EGNOS/EDAS • Added value of EDAS • Access to EGNOS data in any situation • Applications: • Re-distribution of EGNOS augmentation messages • GNSS for location-based services • Professional GNSS services • Others • EDAS in GINA • -How does this apply to GINA demonstrator? • -Technical and business implications of the use of EDAS in operational GINA WP2.4 Analysis of related specific issues

11. WP2.4 4. EGNOS/EDAS • EDAS in GINA • -How does this apply to GINA demonstrator? • -Technical and business implications of the use of EDAS in operational GINA • EDAS not envisaged for demonstration purposes in GINA (not contemplated during proposal and impact on OBU developments (SISNeT-enabled)) • System close to commercialization: SP s interested in offering services exploiting EDAS? Or role of EDAS SP played by a different actor in value chain? • Many applications using EDAS are mass-market oriented but many others addressed at professional markets, so necessary to understand mass-market needs first. • VAS SP offer based on CS-NAV. WP2.4 Analysis of related specific issues

12. WP2.4 4. EGNOS/EDAS • EDAS Limitations • Contributions but still open points: -Loss of service in dedicated line (SP to EDAS server) -Reliable communications between OBU and SP (GPRS/UMTS/other channels) -Availability of suitable terminals (technical and cost issue) -Exploitation of EGNOS Commercial Service: impact on business model envisaged in GINA WP2.4 Analysis of related specific issues

13. WP2.4 5. Authentication • Introduction • What is authentication; benefits; GNSS authentication; position integrity • Road applications • Types of application requiring authentication;end user needs; benefits • Safety-critical applications • Liability-critical applications • Security risks • Description of different types of risk • Real risks for road applications • Authentication feasibility • Technical feasibility • Analysis of authentication in GINA WP2.4 Analysis of related specific issues

14. WP2.4 5. Authentication • Road Applications: • Safety Critical Applications • Automobile Safety Systems • Liability Critical Applications • Road Tolling Applications • PAYD Insurance • Contractual Obligations Enforcement PRESENTATION TITLE VERDANA (9)

15. WP2.4 5. Authentication • Security Risks: • Lack of Signal and OBU authentication leads to possibility of signal simulation • Enables malicious users to: • Avoid payment of road tolls, • Report false kilometers travelled to insurance companies, • … • Signal Authentication required to ensure that sources of satellite signaling are genuine (not spoofed) • Key for liability-critical and safety-critical applications • OBU Authentication Required to ensure the correct Operation (ie not tampered) • Key for liability-critical applications PRESENTATION TITLE VERDANA (9)

16. WP2.4 5. Authentication • Authentication Feasibility: • Authentication Navigation Messages • Spread Spectrum Security Codes • Spreading Code Encryption • Threats: • Signal jamming, • OBU tampering. PRESENTATION TITLE VERDANA (9)

17. WP2.4 5. Authentication • Authentication in GINA: • Liability Critical Applications • RUC; PAYD; Etc… • Users will always attempt to subvert the system • Signal Jamming • OBU tampering • Signal Spoofing • Galileo will provide authentication • OBU’s will need to have physical measures implemented to harden them against tampering PRESENTATION TITLE VERDANA (9)

18. Thank you