Electronic Registration
Identification (ERI)
Concept, architecture and current status
Overview
• The ERI standard • User requirements • Architecture
The ERI standard: Scope
• ISO/TS 24524 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
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
The ERI standard: 5 parts and Basic ERI
24534-1: Architecture 24534-2: Operational Requirements 24534-3: Vehicle data 24535: Basic ERI 24534-4: Secure communications Using asymmetrical techniques 24534-5: Secure communications Using symmetrical techniques Basic ERI : allows for proprietary security implementationsPart 4: Security may vary from very modest to highly secure Part 5: Used in Japan
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
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
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
ERI: Architecture
Overview:
• Basics
• Overall system concept • The ERI system
• Two board variants • In-vehicle architecture
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
Architecture: Overall system concept
(Registration)
authority
Vehicle
Back office
Road-side
(garage)
Reader
(writer)
Road
Architecture: The ERI system
ERI system
ERI back office system E.g. a (registration) authority
ERI reader/ writer Sensor system Onboard Non-ERI equipment ERT
Architecture: Two onboard variants
One single onboard component:
DSRC
beacon
ERT
+
DSRC tag
DSRC
beacon
ERR
DSRC
module
Onboard communication
ERT
ERI readers or
readers/writers
(ERRs)
Multiple onboard components:
Other
application
Architecture: In-vehicle architecture
ERI
Device
Internal
reader
/writer
Other
In vehicle
device
Comm.
device
Inductive coupling
In vehicle communication
Air
Interface
ERI
standard
interface
e.g.
ERI
standard
interface
e.g.
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
Current status
• ERI standard: Last steps in transition from TS to IS • In the Netherlands: a TNO – RDW project
(see e.g. www.tno.nl) – For 2 use cases:
• The inspector
• Rush hour avoidance
– Proprietary environment (=> secret keys)
In summary
The ERI standard TS 24534 with part 4:
• Defines a complete interface with the OBE • Allows a variety of onboard architectures • Security is adaptable to user needs
Thank you for your attention
For further information:
Jan Vis