Road Transport and Traffic Telematics - Electronic Fee Collection (EFC) - System architecture for vehicle related transport services (ISO/TS 17573:2003)

This Technical Specification specifies a system architecture for electronic fee collection (EFC) systems concerning vehicle related transport services such as the use of toll roads, zone access, parking and route guidance.
This Technical Specification does not cover person related transport services such as public transport. However, some of the clauses in this standard may also be applicable for fare collection.
NOTE   Fare collection architecture in public transport is covered by other Working Groups in CEN/TC278 and ISO/TC204, e.g. WG3 Public Transport in CEN/TC278.
This Technical Specification provides the overview of, and inter-relationship among, the set of standards for design, development, testing and operation of applications in the field of EFC.
This Technical Specification is also applicable to the TICS Fundamental Service called Electronic Financial Transactions which is the use of electronic, or 'cashless' payment systems for transportation. Hence, this standard covers toll collection systems, parking fee collection systems, systems for road and congestion pricing and integrated payment systems for transport services.

Straßentransport- und Verkehrstelematik - Elektronische Gebührenerhebung (EFC) - Systemarchitektur für fahrzeugbezogene Transportdienste (ISO/TS 17573:2003)

Télématique de la circulation et du transport routier (RTTT) - Perception du télépéage - Architecture des systemes pour les services embarqués sur véhicules (ISO/TS 17573:2003)

Cestna transportna in prometna telematika – Elektronsko pobiranje pristojbin – Sistemska arhitektura za transportne storitve v zvezi z vozili (ISO/TS 17573:2003)

General Information

Status
Withdrawn
Publication Date
30-Sep-2003
Withdrawal Date
22-Mar-2015
Technical Committee
Current Stage
9900 - Withdrawal (Adopted Project)
Start Date
16-Mar-2015
Due Date
08-Apr-2015
Completion Date
23-Mar-2015

RELATIONS

Buy Standard

Technical specification
SIST-TS CEN ISO/TS 17573:2003
English language
34 pages
sale 10% off
Preview
sale 10% off
Preview

e-Library read for
1 day

Standards Content (sample)

SLOVENSKI STANDARD
SIST-TS CEN ISO/TS 17573:2003
01-oktober-2003
Cestna transportna in prometna telematika – Elektronsko pobiranje pristojbin –

Sistemska arhitektura za transportne storitve v zvezi z vozili (ISO/TS 17573:2003)

Road Transport and Traffic Telematics - Electronic Fee Collection (EFC) - System
architecture for vehicle related transport services (ISO/TS 17573:2003)
Straßentransport- und Verkehrstelematik - Elektronische Gebührenerhebung (EFC) -
Systemarchitektur für fahrzeugbezogene Transportdienste (ISO/TS 17573:2003)

Télématique de la circulation et du transport routier (RTTT) - Perception du télépéage -

Architecture des systemes pour les services embarqués sur véhicules (ISO/TS
17573:2003)
Ta slovenski standard je istoveten z: CEN ISO/TS 17573:2003
ICS:
03.220.20 Cestni transport Road transport
35.240.60 Uporabniške rešitve IT v IT applications in transport
transportu in trgovini and trade
SIST-TS CEN ISO/TS 17573:2003 en

2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

---------------------- Page: 1 ----------------------
SIST-TS CEN ISO/TS 17573:2003
---------------------- Page: 2 ----------------------
SIST-TS CEN ISO/TS 17573:2003
TECHNICAL SPECIFICATION
CEN ISO/TS 17573
SPÉCIFICATION TECHNIQUE
TECHNISCHE SPEZIFIKATION
June 2003
ICS 35.240.60
English version
Road Transport and Traffic Telematics – Electronic Fee
Collection (EFC) – System architecture for vehicle related
transport services (ISO/TS 17573:2003)
Télématique de la circulation et du transport routier (RTTT)
– Perception du télépéage – Architecture des systèmes
pour les services embarqués sur véhicules (ISO/TS
17573:2003)

This Technical Specification (CEN/TS) was approved by CEN on 25 November 2002 for provisional application.

The period of validity of this CEN/TS is limited initially to three years. After two years the members of CEN will be requested to submit their

comments, particularly on the question whether the CEN/TS can be converted into a European Standard.

CEN members are required to announce the existence of this CEN/TS in the same way as for an EN and to make the CEN/TS available. It

is permissible to keep conflicting national standards in force (in parallel to the CEN/TS) until the final decision about the possible

conversion of the CEN/TS into an EN is reached.

CEN members are the national standards bodies of Austria, Belgium, Czech Republic, Denmark, Finland, France, Germany, Greece,

Hungary, Iceland, Ireland, Italy, Luxembourg, Malta, Netherlands, Norway, Portugal, Slovakia, Spain, Sweden, Switzerland and United

Kingdom.
EUROPEAN COMMITTEE FOR STANDARDIZATION
COMITÉ EUROPÉEN DE NORMALISATION
EUROPÄISCHES KOMITEE FÜR NORMUNG
Management Centre: rue de Stassart, 36 B-1050 Brussels

© 2003 CEN All rights of exploitation in any form and by any means reserved Ref. No. CEN ISO/TS 17573:2003 E

worldwide for CEN national Members.
---------------------- Page: 3 ----------------------
SIST-TS CEN ISO/TS 17573:2003
CEN ISO/TS 17573:2003 (E)
Contents

Foreword......................................................................................................................................................................3

Introduction .................................................................................................................................................................3

1 Scope .....................................................................................................................................................................5

2 Normative references...........................................................................................................................................5

3 Terms and definitions ..........................................................................................................................................5

4 Abbreviations......................................................................................................................................................10

5 Conceptual architecture.....................................................................................................................................11

5.1 General ..............................................................................................................................................................11

5.2 Payment means and Payment method .............................................................................................................11

5.3 Payment system ................................................................................................................................................12

5.4 Model for EFC used for vehicle related transport services................................................................................13

6 Logical architecture............................................................................................................................................15

6.1 Definitions ..........................................................................................................................................................15

6.2 The Use case diagram for EFC systems...........................................................................................................15

7 Interfaces.............................................................................................................................................................19

7.1 The User – Transport Service Provider interface ..............................................................................................19

7.2 The User - Collection Agent interface................................................................................................................20

7.3 Other interfaces .................................................................................................................................................21

8 Security in EFC systems....................................................................................................................................22

8.1 Security and Privacy..........................................................................................................................................22

8.2 Data Protection Framework...............................................................................................................................22

8.3 Data Protection measures .................................................................................................................................23

8.4 Data Protection and EFC System architecture..................................................................................................23

8.5 Keys and keys management .............................................................................................................................25

8.5.1 Keys................................................................................................................................................................25

8.5.2 Key management............................................................................................................................................26

8.5.3 Key distribution ...............................................................................................................................................26

Annex A (informative) Functional architecture .....................................................................................................28

Annex B (informative) Class diagram.....................................................................................................................31

Annex C (informative) Bibliography .......................................................................................................................33

---------------------- Page: 4 ----------------------
SIST-TS CEN ISO/TS 17573:2003
CEN ISO/TS 17573:2003 (E)
Foreword

This document (CEN ISO/TS 17573:2003) has been prepared by Technical Committee CEN/TC 278, "Road

Transport and Traffic Telematics" the secretariat of which is held by NEN in collaboration with Technical Committee

ISO/TC 204, “Transport information and control systems”.

According to the CEN/CENELEC Internal Regulations, the national standards organizations of the following

countries are bound to announce this Technical Specification: Austria, Belgium, Czech Republic, Denmark,

Finland, France, Germany, Greece, Hungary, Iceland, Ireland, Italy, Luxembourg, Malta, Netherlands, Norway,

Portugal, Slovak Republic, Spain, Sweden, Switzerland and the United Kingdom.
---------------------- Page: 5 ----------------------
SIST-TS CEN ISO/TS 17573:2003
CEN ISO/TS 17573:2003 (E)
Introduction

There are several standards covering the sector of Electronic Fee Collection (EFC) within Road Transport and

Traffic Telematics (RTTT). Most of the standards are related to the different interfaces that are found in EFC

systems, but with few or no references to other EFC standards. Due to this a need has arisen for an ‘umbrella’ or

Architecture standard for EFC.

The objective of this standard is to define a reference system architecture for EFC used for vehicle related transport

services. The standard provides a framework of conditions for EFC that should be considered during the

specification and implementation. The given information is technology independent as far as possible to enable

various forms of EFC systems. Specific details with regard to e.g. payment means, communication medium and

design of equipment are intentionally kept out of the scope.
The standard provides details with regard to following aspects:
— Terminology, definitions;
— List of relevant standards, regulations and other relevant documents;

— Architecture model for EFC with regard to all relevant parties and facilities (entities);

— Identification of interfaces, including references to relevant (Pre-)standards / Technical Specifications;

EFC encompasses all systems designed to collect fees from users in a non-manual way for vehicle related

transport services. Generally EFC is characterised by the use of electronic means of payment, by absence of any

action from the user at the moment that payment or transaction is made and that payment or transaction for the

transport service may be collected whether or not the vehicle is moving or stationary. EFC does not exclude

manual payment, conventional money transaction, nor does it include payment by means of sticker, vignettes,

tickets, or magnetic stripe cards etc.

The applications to which EFC is related are Toll Collection, Road Pricing, Parking and Individual Traveller and

Traffic Information. EFC systems for public passenger transport or comparable applications that do not require

vehicle related EFC equipment are excluded.
Vision

To provide enabling standards for the collection of fees from road users by automatic means, primarily by use of an

air interface.
Mission

It is the mission of this standard to describe the overall system architecture for Electronic Fee Collection with the

Road Transport and Traffic Telematics.
---------------------- Page: 6 ----------------------
SIST-TS CEN ISO/TS 17573:2003
CEN ISO/TS 17573:2003 (E)
1 Scope

This Technical Specification specifies a system architecture for electronic fee collection (EFC) systems concerning

vehicle related transport services such as the use of toll roads, zone access, parking and route guidance.

This Technical Specification does not cover person related transport services such as public transport. However,

some of the clauses in this standard may also be applicable for fare collection.

NOTE Fare collection architecture in public transport is covered by other Working Groups in CEN/TC278 and ISO/TC204, e.g.

WG3 Public Transport in CEN/TC278.

This Technical Specification provides the overview of, and inter-relationship among, the set of standards for design,

development, testing and operation of applications in the field of EFC.

This Technical Specification is also applicable to the ITS Fundamental Service called Electronic Financial

Transactions which is the use of electronic, or ‘cashless’ payment systems for transportation. Hence, this standard

covers toll collection systems, parking fee collection systems, systems for road and congestion pricing and

integrated payment systems for transport services.
2 Normative references

This Technical Specification incorporates, by dated or undated reference, provisions from other publications. These

normative references are cited at the appropriate places in the text and the publications are listed hereafter. For

dated references, subsequent amendments to or revisions of any of these publications apply to this Technical

Specification only when incorporated in it by amendment or revision. For undated references the latest edition of

the publication referred to applies (including amendments).

prCEN ISO/TS 17574 Road Transport and Traffic Telematics (RTTT) - Electronic Fee Collection (EFC) System -

– Security service Framework – Guidelines for EFC security protection profiles.

ENV ISO 14904 Road Transport and Traffic Telematics – Automatic fee collection (AFC) - - Interface

specification for clearing between operators.

ISO/IEC 11770-1 Information technology - Security techniques - Key management - Part 1: Framework.

3 Terms and definitions

For the purposes of this Technical Specification, the following terms and definitions apply.

3.1
actor
class external to the EFC system, e.g. the User and the Vehicle
3.2
availability (1)

definition related to Security: Data and information are available to authorised parties

3.3
availability (2)

definition related to operation of EFC systems: Dependability with respect to the readiness for usage. Measure of

correct service delivery with respect to the alternation of correct and incorrect service

3.4
central account

account which is containing service rights and which is kept and administrated by the issuer of the payment means

or by an entity acting on behalf of the issuer
---------------------- Page: 7 ----------------------
SIST-TS CEN ISO/TS 17573:2003
CEN ISO/TS 17573:2003 (E)
3.5
Central Communication Unit

part of the Central Equipment serving as mobile communication interface to the OBU

3.6
Central Equipment
system components at fixed centralised locations

NOTE Central equipment is not the same as Central system. Central equipment is used in GNSS/CN based EFC systems.

3.7
charging point

physical point or zone where the use of the transport service is registered. In case of a DSRC based system the

communication between the OBE/OBU and RSU takes place to exchange the information needed to charge the

user by EFC. Charging point also covers the physical point or zone where a fee is collected manually

3.8
charging Point Equipment

equipment installed at a charging point, e.g. a toll station, enabling the operator to collect the fee by the different

payment methods offered to the users
3.9
class

descriptor for a set of objects with similar structure, behaviour and relationships

3.10
class diagram

diagram that shows the classes of the system and their internal relationships (a static structure of a system)

3.11
classification

process of dividing vehicles into various classes according to certain classification parameters (e.g. weight, length,

purpose of use, engine type, number of axles, actual number of passengers)
3.12
clearing Operator

entity that collects and possibly aggregates transactions from one or more Transport Service Providers for delivery

to the Issuer(s). The Clearing Operator can also handle the Apportionment between the Transport Service

Providers. In the financial world this operator is equivalent to an Acquirer
3.13
collection agent

entity responsible for selling, reloading or delivering the Payment Means to the User and collecting the payment

from the User on behalf of the Issuer. The Collection Agent can also collect user related application specific data

from the User. The Collection Agent is also referred to as Retailer
3.14
Conceptual Architecture

overall description of an EFC system incorporating operational concepts and user requirements, together with its

known inter-relationships with other systems
3.15
confidentiality

sensitive data and information are available only to authorised parties (confidentiality of contents)

3.16
contract

expression of an agreement between two or more parties in a payment system or between payment systems. An

example of a contract is the specific relationship between a User and an Issuer in a payment system where the

contract may be explicit or implicit
---------------------- Page: 8 ----------------------
SIST-TS CEN ISO/TS 17573:2003
CEN ISO/TS 17573:2003 (E)
3.17
contractual interoperability
intention of operators to co-operate recorded in a contractual agreement
3.18
Declared Vehicle Characteristics

data set stored in the OBE/OBU containing vehicle characteristics of the vehicle the OBU is related to

3.19
Electronic Fee Collection

collection of a fee for a transport service where the fee is collected via the exchange of data, e.g. via an air-link

communication, enabling the user to pay for the transport service with electronic values, e.g. an electronic purse or

via a central account
3.20
Electronic Purse

application on an IC-card (integrated circuit card) or a similar device that can store, credit, debit and protect

electronic values having their equivalent in money
3.21
enforcement

measures or actions performed by enforcement authorities or other organisations to achieve compliance with laws,

rules and regulations
3.22
enforcement Operator
entity handling the enforcement of users
3.23
exception handling

process of dealing with system errors or passages that might possibly not be paid for. The outcome of the

Exception handling might lead to that the user is enforced or that the fee can be collected, e.g. by correlating a

pictured licence plate number with the contract register
3.24
Functional Architecture

description of the system in terms of functions and information flows between the functions

3.25
Integrity

sensitive data, information and message sequencing are guarded in such a way that any alteration or destruction

by unauthorised parties is detected (integrity of contents, integrity of message sequence)

3.26
Interoperability

ability of systems to provide services to and accept services from other systems and to use these services to

enable the systems to operate effectively together (see contractual, procedural and technical interoperability)

3.27
Issuer

entity responsible for the payment system and responsible for issuing the Payment Means to the User

3.28
Logical Architecture

determines the nature of the system as being based on Information, Control, or Functions, and describes the inter-

relationships of these aspects. A logical architecture is independent of any hardware or software approach and can

be described either from an Object oriented or Process oriented perspective
---------------------- Page: 9 ----------------------
SIST-TS CEN ISO/TS 17573:2003
CEN ISO/TS 17573:2003 (E)
3.29
non-repudiation

protection against the denial, by one of the parties involved in the communication through the interface, of having

participated in all or part of the communications
3.30
On-Board Account

account, which is containing service rights and which is being held under the responsibility of the user, e.g. data

stored on an IC-card
3.31
On-Board Equipment

equipment located within the vehicle and supporting the information exchange with the Road Side Unit or the

Central Communication Unit. It is composed of the On-Board Unit and other sub-units whose presence has to be

considered optional for the execution of a Transaction
3.32
On-Board Unit (OBU)

minimum component of an On-Board Equipment, whose functionality always includes at least the support of the

DSRC interface or/and the Central Communication Unit and the protection of the data stored in the OBU

3.33
Operator

generic term for the entities Issuer, Clearing Operator, Collection Agent, Transport Service Provider, Enforcement

Operator or Trusted Third Party
3.34
payment means

expression of a Contract between the User and the Issuer (or via a Collection Agent) that allows the User to access

the transport services available in the Payment System, e.g. an account in a credit card system or an Electronic

Purse
See also 5.2.
3.35
payment medium
carrier of payment means (such as ticket, card or on-board unit)
3.36
payment method
combination of a Payment Means, a Payment Mode and a Payment Scope
3.37
payment mode

parameter defining the time dimension in payment by the User, i.e. Pre-payment, Immediate payment or Post-

payment
3.38
payment scope

application extent of the Payment Method, e.g. national transport or inter-sector

3.39
payment system

financial system that includes the complete process of issuing and use of payment means, clearing and settlement

of transactions
See also 5.3.
---------------------- Page: 10 ----------------------
SIST-TS CEN ISO/TS 17573:2003
CEN ISO/TS 17573:2003 (E)
3.40
Privacy

right of individuals to control or influence what information related to them may be collected and stored and by

whom and to whom that information may be disclosed
3.41
procedural interoperability

existence of common data element definitions, the same working procedures and data delivery and common format

of presentation in different sets of equipment required to communicate
3.42
Roadside Equipment

equivalent to Transport service Provider Equipment in those charging point where DSRC is used for

communication between the On-Board Equipment and Transport service Provider Equipment, e.g. in a traditional

toll station
3.43
Roadside Unit

DSRC part of the Roadside Equipment whose functionality is to communicate and exchange data with vehicles

passing the charging point
3.44
Transport service

road Transport facility provided by a Transport Service provider. Normally a type of infrastructure, e.g. a toll road or

a road network inside a toll ring
3.45
Transport service Provider

person, company, authority or abstract entity offering a transport service to the User for which the user has to pay a

fee (the fee will in some cases be zero, e.g. emergency vehicles)
3.46
Transport service Provider Equipment

all equipment installed at the Charging point being used for EFC, e.g. communication equipment, classification

systems, vehicle detection systems and signs and signals to the User
3.47
System Architecture

an overall description of an Electronic Fee collection system incorporating the main elements, the main interfaces

and the main functions of the system
3.48
Technical interoperability

capability of different sets of equipment to work together through interconnection, co-ordinated execution or sharing

of resources
3.49
Toll Collection System

equipment and functions enabling the collection of a fee for the use of road infrastructure

3.50
Toll Plaza
See Charging point
3.51
Toll Station
See Charging point
---------------------- Page: 11 ----------------------
SIST-TS CEN ISO/TS 17573:2003
CEN ISO/TS 17573:2003 (E)
3.52
Transport service

road transport related facility provided by a Transport service Provider. Normally a type of infrastructure, e.g. a toll

toad or a road network inside a toll ring, the use of which is offered to the User for which the User is requested to

pay
3.53
Trusted Third Party

entity who might be responsible for operation monitoring, system and security assessment (including security key

management) as well as granting licences
3.54
User Equipment

any equipment held by the User enabling him to communicate with the collection agent updating his service rights,

e.g. with a PC and a modem
3.55
User
(client, customer, consumer)

entity that uses a transport service provided by the Transport service Provider according to the terms of an

agreement. The User may also be described as the subscriber of an EFC contract, the vehicle owner and the driver

in those cases where these are not the same person or company
3.56
Use Case

abstraction of similar and closely connected scenarios where a scenario is a typical interaction between one or

more actors and the EFC system
EXAMPLE Fee collection at the Charging point.
3.57
Use Case Diagram
graphical model that shows the relationships among the actors and the use cases
4 Abbreviated terms

For the purposes of this Technical Specification the following abbreviated terms apply.

4.1
Cellular Networks
4.2
CPE
Charging Point Equipment
4.3
DES
Data Encryption Standard
4.4
DSRC
Dedicated Short Range Communication
4.5
EFC
Electronic Fee Collection
4.6
GNSS
Global Navigation Satellite Systems
---------------------- Page: 12 ----------------------
SIST-TS CEN ISO/TS 17573:2003
CEN ISO/TS 17573:2003 (E)
4.7
ICC
IC-card
4.8
Identification
4.9
ITS
Intelligen Transport Systems
4.10
MMI
Man-Machine Interface
4.11
OBE
On-Board Equipment
4.12
OBU
On-Board Unit
4.13
RSE
Roadside Equipment
4.14
RSU
Roadside Unit
4.15
RTTT
Road Transport and Traffic Telematics
4.16
SAM
Secure Application Module
5 Conceptual architecture
5.1 General
This clause defines three essential issues related to Electronic Fee Collection:
a) Payment means and payment method;
b) Payment system;
c) Model for EFC used for vehicle related transport services.
5.2 Payment means and Payment method

By payment means is meant the expression of a Contract between the User and the Issuer that allows the User to

access the transport services available in the Payment System.

EXAMPLE 1 An example of a payment means is an account issued by VISA or MasterCard. The expression of the Contract

will be the information stored on the card and in the written contract between the User and the Issuer. For the User and the

---------------------- Page: 13 ----------------------
SIST-TS CEN ISO/TS 17573:2003
CEN ISO/TS 17573:2003 (E)

Transport service provider the card will be the crucial information carrier and for this reason the card itself becomes the symbol

of the contract and is often referred to as the payment means. An On-Board Unit may also be related to an account. In this case

the On-Board Unit becomes the symbol of the contract and is referred to as the payment means even though the real payment

means is the contract and the account behind the On-Board Unit. This perception of the On-Board Unit as the payment means

is strengthened in those cases where the payment means is an electronic purse on an IC-card inserted in the On-Board Unit.

The User will see the combination of the On-Board Unit and the IC-card as the payment means even though the payment

means is the information (electronic values) stored on the IC-card. In reality the OBU is just a physical device enabling

communication between the electronic purse (the payment means) and the charging point equipment at the roadside.

EXAMPLE 2 Another example of a payment means is illustrated by the situation where a User makes a call to the operator

to purchase his User rights via the phone. The User will give some information to the operator, e.g. a bank account number or

credit card number or even his vehicle licence plate number. The information (the ‘contract’) is stored somewhere in the EFC

system enabling the User to benefit from the transport service and the operator to charge the User for the transport service

provided, e.g. by debiting a bank account or sending an invoice based on information from the national vehicle register.

Payment means also cash, cheques etc. used for any manual fee collection at the charging point.

Payment mode means the concept defining the time dimension in payment (pre-payment, immediate payment or

post-payment).

Payment scope means the field of application in which the payment means is accepted, e.g. national transport

services.

By Payment method is meant the combination of Payment means, payment mode and payment scope. An example

will be a post-paid central account that can be used in all EFC systems within one country.

5.3 Payment system
5.3.1 General

By payment system is meant a financial system that includes the complete process of issuing and use of payment

means, clearing and settlement of transactions.

The payment means to give the holder of the payment access to the transport services related to the payment system.

Any transport related payment system can be described by means of the abstract definition given in Figure 1.

Figure 1 — The basic entities in a Payment system for EFC
5.3.2 The User

The User, i.e. the user of the Transport service, will receive a transport service from a Transport Service Provider

and the User shall pay for the transport service. The transport service can be the use of a tolled motorway or

parking in a parking house. The User can use values like electronic values on an IC-card for payment or he can

use payment information, e.g. a credit card number or a reference to a central account held by the Issuer. The

reference can be the unique identity of an electronic tag installed in the vehicle used by the User.

---------------------- Page: 14 ----------------------
SIST-TS CEN ISO/TS 17573:2003
CEN ISO/TS 17573:2003 (E)
5.3.3 The Transport Service Provider

The Transport Service Provider will receive the payment from the user for the transport service he has provided. If

the payment is in an electronic form or in form of payment data, the Transport Service provider has to convert the

values or information into real money. If the values are electronic values on an IC-card he will send a claim to the

issuer of the electronic values to exchange the values into money. If the payment is payment information the

Transport Service provider has to send a claim to the issuer of the payment means, e.g. a c

...

Questions, Comments and Discussion

Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.