Electronic Registration Identification (ERI)

Size: px

Start display at page:

Download "Electronic Registration Identification (ERI)"

Claribel Daniels
10 years ago
Views:

1 Electronic Registration Identification (ERI) Concept, architecture and current status Murcia, 18th June 2009

2 Overview The ERI standard User requirements Architecture Current status 2 Electronic Registration Identification (ERI) 18 juni 2009

3 The ERI standard: Scope ISO/TS Electronic Registration Identification (ERI) A standard for identifying vehicles by electronic means Suitable for: Identification of local and foreign vehicles by authorities Vehicle manufacturing, vehicle life cycle management Safety related purposes Crime reduction Commercial services Adhering to privacy/data protection regulations 3 Electronic Registration Identification (ERI) 18 juni 2009

authorities Vehicle manufacturing, vehicle life cycle management Safety related purposes Crime reduction

4 The ERI standard: History A CEN and ISO standard (part 5 is ISO only) A basic variant: Basis ERI Work started in spring 2003 Participants from: US, Mexico, Japan, several EU countries 2004: Expert opinions security & feasibility Currently a Technical Specification (TS) In transition to an International Standard (IS) unanimous positive vote in June 4 Electronic Registration Identification (ERI) 18 juni 2009

opinions security & feasibility Currently a Technical Specification (TS) In transition to an

5 The ERI standard: 5 parts and Basic ERI : Architecture : Operational Requirements 24535: Basic ERI : Vehicle data : Secure communications Using asymmetrical techniques Basic ERI : allows for proprietary security implementations Part 4: Security may vary from very modest to highly secure Part 5: Used in Japan : Secure communications Using symmetrical techniques Focus on application layer communication, lower layers are only referenced 5 Electronic Registration Identification (ERI) 18 juni 2009

4: Security may vary from very modest to highly secure Part 5: Used in Japan 24534-5: Secure communications Using symmetrical

6 User requirements: Identification Two types of identification: Specific vehicle identification Vehicle vicinity identification Safe, no hindrance to the driver Mandatory: no due diligence assumed Under all traffic and whether conditions Irrespective of the vehicle s speed Readable with roadside, mobile & handheld equipment 6 Electronic Registration Identification (ERI) 18 juni 2009

assumed Under all traffic and whether conditions Irrespective of the vehicle s speed Readable

7 User requirements: Security Adaptable to user needs from very modest to highly secure Identification usable as legal evidence Authenticity (as needed) Is the ERT attached to the right vehicle Is it a genuine (not a fake) ERT ERT inoperable when removed Confidentiality (to the roadside) (as needed) privacy and protection against attack Read authorisation of authorities / third parties Support of international vehicle sales ERT key management / diversification 7 Electronic Registration Identification (ERI) 18 juni 2009

Confidentiality (to the roadside) (as needed) privacy and protection against attack Read authorisation of authorities / third

8 User requirements: ERI data Vehicle Id Vehicle Identification Number VIN (ISO 3779) Or, registration authority specific (WMI + e.g. a chassis number) Additional ERI data (optional) More then 60 different items E.g. vehicle registration certificate data Registration authority specific data 8 Electronic Registration Identification (ERI) 18 juni 2009

g. vehicle registration certificate data Registration authority specific data 8

9 ERI: Architecture Overview: Basics Overall system concept The ERI system Two board variants In-vehicle architecture 9 Electronic Registration Identification (ERI) 18 juni 2009

10 Architecture: Basics For an acquirer: Architecture = Procurement policy! Only distinguish components if more than one party will be involved, i.e.: Different suppliers / maintenance companies Different owners / users do not specify internal details /interfaces Focus on behaviour / interfaces: Vehicle road-side (the main interface) In-vehicle (to support other onboard applications & architectures) ERI part 4 defines complete interfaces 10 Electronic Registration Identification (ERI) 18 juni 2009

11 Architecture: Overall system concept Vehicle Reader (writer) (Registration) authority Road Road-side (garage) Back office 11 Electronic Registration Identification (ERI) 18 juni 2009

12 Architecture: The ERI system ERI system ERT ERI reader/ writer Sensor system Onboard Non-ERI equipment ERI back office system E.g. a (registration) authority Vehicle 12 Electronic Registration Identification (ERI) 18 juni 2009

13 Architecture: Two onboard variants One single onboard component: ERT + DSRC tag Multiple onboard components: ERT ERR Other DSRC application module Onboard communication DSRC beacon ERI readers or readers/writers (ERRs) DSRC beacon Vehicle Road side 13 Electronic Registration Identification (ERI) 18 juni 2009

Onboard communication DSRC beacon ERI readers or readers/writers (ERRs) DSRC

14 Architecture: In-vehicle architecture ERI standard interface ERI standard interface ERI Device Inductive coupling Internal reader /writer Other In vehicle device In vehicle communication Comm. device Air Interface e.g. ISO e.g. ISO / CEN Electronic Registration Identification (ERI) 18 juni 2009

vehicle device In vehicle communication Comm. device Air Interface e.g.

15 Architecture: The ERT life cycle Customisation to a vehicle Writing vehicle data into the ERT Commissioning by a registration authority (RA) who may: assigns himself as the vehicle s RA enable / disable signing / encryption capabilities allow others to access ERT data Deployment, i.e. customised and commissioned Withdrawn (customised with revoked commissioning) 15 Electronic Registration Identification (ERI) 18 juni 2009

16 Current status ERI standard: Last steps in transition from TS to IS In the Netherlands: a TNO RDW project (see e.g. For 2 use cases: The inspector Rush hour avoidance Proprietary environment (=> secret keys) Multiple tags per vehicle to prevent identity fraud 16 Electronic Registration Identification (ERI) 18 juni 2009

nl) For 2 use cases: The inspector Rush hour avoidance Proprietary environment (=>

17 In summary The ERI standard TS with part 4: Defines a complete interface with the OBE Allows a variety of onboard architectures Security is adaptable to user needs 17 Electronic Registration Identification (ERI) 18 juni 2009

onboard architectures Security is adaptable to user needs

18 Thank you for your attention For further information: Jan Vis Electronic Registration Identification (ERI) 18 juni 2009

Security risk analysis approach for on-board vehicle networks

1 Security risk analysis approach for on-board vehicle networks Alastair Ruddle Consultant, MIRA Limited Motivation 2 o o Future vehicles will become mobile nodes in a dynamic transport network vehicle