WP2.4

WP2.4

Analysis of related specific issues (standardisation, policies, interoperability etc.)

Date: 5th November 2009

Place: Dublin

GNSS for INnovative Road Applications

Company LOGO

GNSS for Innovative road Applications

Company’s

logo02/07/2009 Page 2

1. Standardisation – ICC

2. Policies (including integration with eCall) – ERF

3. Interoperability – ICC

4. EGNOS/EDAS – GMV

5. Authentication – Skysoft

Coordination of 4 and 5, commenting on and providing additional input for drafts from all sub-workpackages – NW

WP2.4 Topics and responsibilities

WP2.4 Analysis of related specific issues


Company’s

logo21/04/23 Page 3

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 Timetable



Company’s

logo02/07/2009 Page 4

1. 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

2. 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)

3. CEN Project teams

4. The GMAR initiative

5. Value added services

WP2.4 1. Standardisation



Company’s

logo02/07/2009 Page 5

1. Introduction2. Key decision makers

A. European institutions

B. European GNSS Supervisory Authority

C. Public administrations of the 27 Member States

D. Local/regional governments: example of the Netherlands

3. State-of-the-art EU legislative frameworkA. 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

B. Pricing applications

C. Traffic information generation, processing and provision

D. eCall

E. Human-Machine Interface

F. Data privacy

4. Case studies: Netherlands, Germany, Slovenia, Slovakia

WP2.4 2. Policies (including integration with eCall)



Company’s

logo02/07/2009 Page 6

1. The Interoperability Directive 2004/52/EC– Background– The role of GNSS– Revised timescales

2. 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

3. 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

4. Impact of the EETS definition on GINA

WP2.4 3. Interoperability



Company’s

logo02/07/2009 Page 7

1. Overview– Description– Technical information

2. Added value of EDAS– Generic advantages– Applications

3. EDAS in GINA– Contribution of EDAS to RUC and VAS– EDAS limitations

WP2.4 4. EGNOS/EDAS



Company’s

logo02/07/2009 Page 8

1. 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

WP2.4 4. EGNOS/EDAS


Architecture


Company’s

logo02/07/2009 Page 9

WP2.4 4. EGNOS/EDAS


Products and services

Data Format


Company’s

logo02/07/2009 Page 10

1. 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

WP2.4 4. EGNOS/EDAS


2. EDAS in GINA-How does this apply to GINA demonstrator?

-Technical and business implications of the use of EDAS in operational GINA


Company’s

logo02/07/2009 Page 11

WP2.4 4. EGNOS/EDAS


2. 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.


Company’s

logo02/07/2009 Page 12

3. 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 4. EGNOS/EDAS



Company’s

logo02/07/2009 Page 13

1. Introduction– What is authentication; benefits; GNSS authentication; position

integrity

2. Road applications– Types of application requiring authentication;

end user needs; benefits– Safety-critical applications– Liability-critical applications

3. Security risks– Description of different types of risk– Real risks for road applications

4. Authentication feasibility– Technical feasibility

5. Analysis of authentication in GINA

WP2.4 5. Authentication



Company’s

logo

WP2.4 5. AuthenticationRoad Applications:

– Safety Critical Applications– Automobile Safety Systems

– Liability Critical Applications– Road Tolling Applications– PAYD Insurance– Contractual Obligations Enforcement

21/04/23 Page 14PRESENTATION TITLE VERDANA (9)


Company’s

logo

WP2.4 5. AuthenticationSecurity 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



Company’s

logo

WP2.4 5. AuthenticationAuthentication Feasibility:

– Authentication Navigation Messages– Spread Spectrum Security Codes– Spreading Code Encryption

Threats:

– Signal jamming,– OBU tampering.



Company’s

logo

WP2.4 5. AuthenticationAuthentication 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


Thank you

Date post:	27-Jan-2016
Category:	Documents
Upload:	boyce
View:	51 times
Download:	1 times

WP2.4

Documents