prEN ISO 17573

SLOVENSKI STANDARD
01-april-2009
Elektronsko pobiranje pristojbin - Sistemska arhitektura za cestninjenje vozil
(ISO/DIS 17573:2009)
Electronic fee collection - Systems architecture for vehicle related tolling (ISO/DIS
17573:2009)
Straßenverkehrstelematik - Elektronische Gebührenerhebung - Systemarchitektur für
fahrzeugbezogene Transportdienstleistungen (ISO/DIS 17573:2009)
Perception du télépéage - Architecture des systèmes pour le péage lié au véhicule
(ISO/DIS 17573:2009)
Ta slovenski standard je istoveten z: prEN ISO 17573
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
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

EUROPEAN STANDARD
DRAFT
NORME EUROPÉENNE
EUROPÄISCHE NORM
January 2009
ICS Will supersede CEN ISO/TS 17573:2003
English Version
Electronic fee collection - Systems architecture for vehicle
related tolling (ISO/DIS 17573:2009)
Perception du télépéage - Architecture des systèmes pour Straßenverkehrstelematik - Elektronische
le péage lié au véhicule (ISO/DIS 17573:2009) Gebührenerhebung - Systemarchitektur für
fahrzeugbezogene Transportdienstleistungen (ISO/DIS
17573:2009)
This draft European Standard is submitted to CEN members for parallel enquiry. It has been drawn up by the Technical Committee
CEN/TC 278.
If this draft becomes a European Standard, CEN members are bound to comply with the CEN/CENELEC Internal Regulations which
stipulate the conditions for giving this European Standard the status of a national standard without any alteration.
This draft European Standard was established by CEN in three official versions (English, French, German). A version in any other language
made by translation under the responsibility of a CEN member into its own language and notified to the CEN Management Centre has the
same status as the official versions.
CEN members are the national standards bodies of Austria, Belgium, Bulgaria, Cyprus, Czech Republic, Denmark, Estonia, Finland,
France, Germany, Greece, Hungary, Iceland, Ireland, Italy, Latvia, Lithuania, Luxembourg, Malta, Netherlands, Norway, Poland, Portugal,
Romania, Slovakia, Slovenia, Spain, Sweden, Switzerland and United Kingdom.
Recipients of this draft are invited to submit, with their comments, notification of any relevant patent rights of which they are aware and to
provide supporting documentation.
Warning : This document is not a European Standard. It is distributed for review and comments. It is subject to change without notice and
shall not be referred to as a European Standard.
EUROPEAN COMMITTEE FOR STANDARDIZATION
COMITÉ EUROPÉEN DE NORMALISATION
EUROPÄISCHES KOMITEE FÜR NORMUNG
Management Centre: Avenue Marnix 17, B-1000 Brussels
© 2009 CEN All rights of exploitation in any form and by any means reserved Ref. No. prEN ISO 17573:2009: E
worldwide for CEN national Members.

Contents Page
Foreword .3

Foreword
This document (prEN ISO 17573:2009) 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".
This document is currently submitted to the parallel Enquiry.
This document will supersede CEN ISO/TS 17573:2003.
DRAFT INTERNATIONAL STANDARD ISO/DIS 17573
ISO/TC 204 Secretariat: ANSI
Voting begins on: Voting terminates on:
2009-01-15 2009-06-15
INTERNATIONAL ORGANIZATION FOR STANDARDIZATION • МЕЖДУНАРОДНАЯ ОРГАНИЗАЦИЯ ПО СТАНДАРТИЗАЦИИ • ORGANISATION INTERNATIONALE DE NORMALISATION
Electronic fee collection — Systems architecture for vehicle
related tolling
Perception du télépéage — Architecture des systèmes pour le péage lié au véhicule
(Revision of ISO/TS 17573:2003)
ICS 03.220.20; 35.240.60
ISO/CEN PARALLEL PROCESSING
This draft has been developed within the European Committee for Standardization (CEN), and processed
under the CEN-lead mode of collaboration as defined in the Vienna Agreement.
This draft is hereby submitted to the ISO member bodies and to the CEN member bodies for a parallel
five-month enquiry.
Should this draft be accepted, a final draft, established on the basis of comments received, will be
submitted to a parallel two-month approval vote in ISO and formal vote in CEN.
In accordance with the provisions of Council Resolution 15/1993 this document is circulated in
the English language only.
Conformément aux dispositions de la Résolution du Conseil 15/1993, ce document est distribué
en version anglaise seulement.
To expedite distribution, this document is circulated as received from the committee secretariat.
ISO Central Secretariat work of editing and text composition will be undertaken at publication
stage.
Pour accélérer la distribution, le présent document est distribué tel qu'il est parvenu du
secrétariat du comité. Le travail de rédaction et de composition de texte sera effectué au
Secrétariat central de l'ISO au stade de publication.
THIS DOCUMENT IS A DRAFT CIRCULATED FOR COMMENT AND APPROVAL. IT IS THEREFORE SUBJECT TO CHANGE AND MAY NOT BE
REFERRED TO AS AN INTERNATIONAL STANDARD UNTIL PUBLISHED AS SUCH.
IN ADDITION TO THEIR EVALUATION AS BEING ACCEPTABLE FOR INDUSTRIAL, TECHNOLOGICAL, COMMERCIAL AND USER PURPOSES, DRAFT
INTERNATIONAL STANDARDS MAY ON OCCASION HAVE TO BE CONSIDERED IN THE LIGHT OF THEIR POTENTIAL TO BECOME STANDARDS TO
WHICH REFERENCE MAY BE MADE IN NATIONAL REGULATIONS.
RECIPIENTS OF THIS DRAFT ARE INVITED TO SUBMIT, WITH THEIR COMMENTS, NOTIFICATION OF ANY RELEVANT PATENT RIGHTS OF WHICH
THEY ARE AWARE AND TO PROVIDE SUPPORTING DOCUMENTATION.
©
International Organization for Standardization, 2009

ISO/DIS 17573
PDF disclaimer
This PDF file may contain embedded typefaces. In accordance with Adobe's licensing policy, this file may be printed or viewed but shall
not be edited unless the typefaces which are embedded are licensed to and installed on the computer performing the editing. In
downloading this file, parties accept therein the responsibility of not infringing Adobe's licensing policy. The ISO Central Secretariat
accepts no liability in this area.
Adobe is a trademark of Adobe Systems Incorporated.
Details of the software products used to create this PDF file can be found in the General Info relative to the file; the PDF-creation
parameters were optimized for printing. Every care has been taken to ensure that the file is suitable for use by ISO member bodies. In the
unlikely event that a problem relating to it is found, please inform the Central Secretariat at the address given below.
Copyright notice
This ISO document is a Draft International Standard and is copyright-protected by ISO. Except as permitted
under the applicable laws of the user's country, neither this ISO draft nor any extract from it may be
reproduced, stored in a retrieval system or transmitted in any form or by any means, electronic, photocopying,
recording or otherwise, without prior written permission being secured.
Requests for permission to reproduce should be addressed to either ISO at the address below or ISO's
member body in the country of the requester.
ISO copyright office
Case postale 56  CH-1211 Geneva 20
Tel. + 41 22 749 01 11
Fax + 41 22 749 09 47
E-mail copyright@iso.org
Web www.iso.org
Reproduction may be subject to royalty payments or a licensing agreement.
Violators may be prosecuted.
©
ii ISO 2009 – All rights reserved

Contents Page
1 Scope.7
2 Normative references.7
3 Terms and definitions .8
4 Abbreviations and symbols .11
4.1 Abbreviations.11
4.2 Symbols.11
5 The EFC community: roles and objectives.11
5.1 Introduction.11
5.2 Toll charging environment .12
5.3 External objects.13
5.3.1 Financial systems, e.g. banks, credit cards companies and clearing houses .13
5.3.2 Telecom systems.13
5.3.3 Positioning systems.13
5.3.4 Vehicle sensors and data stores .13
5.3.5 Environmental sensors and other ITS systems .13
5.3.6 EFC equipment suppliers .14
5.3.7 Certification bodies.14
5.3.8 Standardisation bodies.14
5.3.9 Authorities.14
6 Roles and responsibilities in the toll charging environment.15
6.1 Introduction.15
6.2 Role related to the provision of the toll service .16
6.3 Role related to the use of the toll service .16
6.4 Role related to the charging of the toll.17
6.5 Role related to the management of the toll charging environment .18
6.6 Decomposition of the toll charging environment .18
6.6.1 Introduction.18
6.6.2 The toll service provider domain.19
6.6.3 The user domain.20
6.6.4 The toll charger domain.21
6.6.5 The toll charging environment management domain.23
7 EFC system behaviour.24
7.1 Introduction.24
7.2 Roles, responsibilities and actors.24
7.3 Interaction matrix and action diagrams .27
7.3.1 Adding (or excluding) a new toll charger.28
7.3.2 Adding (or excluding) a new service provider .28
7.3.3 Adding, modifying or closing an EFC regime .29
7.3.4 Defining rules and monitoring operations.30
7.3.5 Providing EFC contract – subscribing (or unsubscribing) of a new user.32
7.3.6 Collecting fee information – user billing.33
7.3.7 Collecting transit information .34
7.3.8 Collecting charging information (GNSS/CN) .35
7.3.9 Claiming fees .36
7.3.10 Providing customer care .37
7.3.11 Exceptions detection – user and OBE compliance checking.38
7.4 Resulting interaction between actors .39
8 Information schemata and basic information types.41
8.1 Static schema .41
DRAFT 2009
8.2 Basic information objects .42
8.2.1 The EFC rules .42
8.2.2 Transit information.44
8.2.3 Operational information.44
8.2.4 Payment information.45
8.3 Dynamic schema .45
9 Interfaces and computational objects.46
9.1 Generalities .46
9.2 Management object interfaces.47
9.2.1 Security requirements.48
9.3 Charging object interfaces .48
9.3.1 General .48
9.3.2 Charging-Management interface .48
9.3.3 Charging-Basic Provision interface .49
9.3.4 Charging-Providing EFC Context Data interface .49
9.3.5 Charging-Operating Pre-billing interface.49
9.3.6 Charging-Use interface.49
9.3.7 Security requirements.50
9.4 Basic Provision object interfaces.51
9.4.1 General .51
9.4.2 Basic Provision-Management interface .51
9.4.3 Basic Provision-Charging interface .51
9.4.4 Basic Provision-Personalizing the OBE interface .51
9.4.5 Basic Provision-Acting as a Contract Agent interface.51
9.4.6 Basic Provision-Operating Pre-billing interface .52
9.4.7 Basic Provision-Use interface.52
9.4.8 Security requirements.52
9.5 Maintaining the OBE object interfaces.53
9.5.1 General .53
9.5.2 Maintaining the OBE-Personalizing the OBE interface .54
9.5.3 Maintaining the OBE-Use interface .54
9.5.4 Security requirements.54
9.6 Personalizing the OBE object interfaces .54
9.6.1 General .54
9.6.2 Personalizing the OBE-Basic provision interface.54
9.6.3 Personalizing the OBE-Maintaining the OBE interface .55
9.6.4 Personalizing the OBE-Acting as a Contract Agent interface .55
9.6.5 Personalizing the OBE-Use interface.55
9.6.6 Security requirements.55
9.7 Acting as a Contract Agent object interfaces .55
9.7.1 General .55
9.7.2 Acting as a Contract Agent-Basic Provision interface.56
9.7.3 Acting as a Contract Agent-Maintaining the OBE interface.56
9.7.4 Acting as a Contract Agent-Personalizing the OBE interface .56
9.7.5 Acting as a Contract Agent-Charging interface .56
9.7.6 Acting as a Contract Agent-Use interface .56
9.7.7 Security requirements.56
9.8 Providing Context Data object interfaces.57
9.8.1 General .57
9.8.2 Providing Context Data-Charging interface.57
9.8.3 Providing Context Data-Use interface.57
9.8.4 Security requirements.57
9.9 Operating Pre-billing object interfaces .58
9.9.1 General .58
9.9.2 Operating Pre-billing-Basic Provision interface .58
9.9.3 Operating Pre-billing-Charging interface.58
9.9.4 Operating Pre-billing-Use interface.58
9.9.5 Security requirements.58
9.10 Use object interfaces .59
DRAFT 2009
9.10.1 General.59
9.10.2 Use-Basic Provision interface.59
9.10.3 Use-Maintaining the OBE interface .59
9.10.4 Use-Personalizing the OBE interface.59
9.10.5 Use-Acting as a Contract Agent interface .60
9.10.6 Use-Providing Context Data interface.60
9.10.7 Use-Operating Pre-billing interface.60
9.10.8 Use-Charging interface.60
9.10.9 Security requirements.60
10 Points of observation and viewpoint correspondences .61
10.1 Points of observation.61
10.2 Correspondence between enterprise and information viewpoints.61
10.3 Correspondence between enterprise and computational viewpoints .62
Annex A (informative) Short ODP description .63
Annex B (informative) Comparison with previous versions.66
B.1 Previous model for EFC used for vehicle related transport services.66
B.2 The relationships between the new and the previous conceptual model.67
Annex C (informative) Relations between this Standard and IFMSA .69
C.1 Introduction: the IFM environment.69
C.2 The relationships between the EFC model in this Standard and the IFMSA model.70
Annex D (informative) Relation with the European Electronic Toll System .73
D.1 Terms.73
D.2 EETS roles model.73
Annex E (informative) Example of the Japanese electronic toll system.75
E.1 Updated previous class diagram for EFC system. .75
E.2 The relation with the new model.76

DRAFT 2009
Foreword
This document prEN ISO 17573:2008 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 “Intelligent transport systems”.
This document is currently submitted to the parallel Enquiry.
This document will supersede CEN ISO/TS 17573:2002.
DRAFT 2009
Introduction
The widespread use of tolling also requires provisions for users of vehicles that are roaming through
many different toll domains. Users should be offered a single contract for driving a vehicle through
various toll domains and those vehicles require onboard equipment (OBE) that is interoperable with
the toll system in the various toll domains. In Europe, for example, this need has been officially
recognised and legislation on interoperability already has been adopted. See Directive 2004/52. There
is a commercial and economic justification both in respect of the OBE and the toll systems for
standards enabling interoperability.
In addition to other standards there is also a further a need for a system architecture that:
⎯ provides an architectural “umbrella” for other EFC standards in terms of a common definition of
terms and concepts, basic system functionalities, and structure
⎯ provides a common terminology which enables its users
⎯ to improve the quality of specifications to be used in an international market,
⎯ to reduce the risk for different interpretations of specifications (purchaser) and descriptions
(supplier),
⎯ to simplify the communication between experts from different continents, and
⎯ to enhance the potential use of other EFC standards;
⎯ defines a common framework, that enables both:
⎯ identification of potential activities subject to standardization, and
⎯ maintaining a common and consistent view of the whole area;
⎯ defines the boundaries between the EFC and the external world;
⎯ identifies all architectural objects that lay inside the EFC boundaries;
⎯ provides a basic understanding of EFC, EFC interoperability, and the EFC services being offered.
The previous edition of this Standard was based on a conceptual model defined in ENV ISO 14904.
Since then ideas on conceptual models have evolved in several regional projects and implementations,
e.g. in Japan and Europe. Those new models have been detailed to a further extent compared to CEN
ISO/TS 17573 and are more close to real life implementations. This Standard is based on these new
conceptual models and uses the associated terms and definitions. A comparison between the old
edition of this standard and the current one is shown in Annex B.
Although there are many differences, collecting toll for vehicles can be to some extent compared with
collecting fare for public transport. Architectural harmonisation of the collection of fee and fare may be
desirable from a policy and from a user point of view. In the past EN ISO24014-1 Interoperable Fare
Management System - Part 1: Architecture (IFMSA) prepared by CEN TC 278 WG 3 Public Transport
used CEN ISO/TS 17573:2002 as a starting point for their work. This Standard has benefited from that
and has also taken ISO/FDIS 24014-1 into account.
DRAFT 2009
In this Standard the Open Distributed Processing (ODP) standard is used for the description of the
architecture.
The ODP standard gives a vocabulary and modelling tools to see the architecture of a system from
different perspectives (the viewpoints), in order to cover, e.g., hardware components as well as
network protocols or interfaces or roles and general policies of the system itself. This is accomplished
using different sets of concepts and terminologies, each one of those expressed as a viewpoint
language. A complete description of a real system can only be achieved when all viewpoint models
are designed. This allows for a clear separation of concerns and an easier way to define a system. A
brief description of the ODP concepts can be found in Annex A.
This Standard gives a description of the architecture of the toll systems environment from the
enterprise viewpoint. In addition, this Standard defines the foundations of the information viewpoint by
defining information interactions and general information objects, and gives the basis for the
computational view, by identifying needed computational objects and their interfaces.
1 Scope
This Standard defines the architecture of a toll system environment in which a customer with one
contract may use a vehicle in a variety of toll domains and with a different toll charger for each domain.
Toll systems covered by this Standard may be used for various purposes including road (network)
tolling, area tolling, collecting toll for bridges, tunnels, ferries, for access, for parking. From a technical
point of view the considered toll systems use electronic equipments on board of a vehicle.
From a process point of view the architectural description focuses on fee determination, fee charging,
and the associated enforcement measures. The actual collection of the fee, i.e. collecting payments, is
not included.
The architecture in this Standard is defined with no more details than those required for an overall
overview, a common language, an identification of the need for other standards, and the drafting of
these standards.
This Standard provides:
⎯ The enterprise view on the architecture, which is concerned with the purpose, scope and policies
governing the activities of the specified system within the organization of which it is a part.
⎯ Terms and definitions for common use in a toll environment
⎯ A decomposition of the toll systems environment into its main objects
⎯ The responsibilities of the main actors
⎯ An identification of the main interfaces between the main objects
⎯ An identification of the main flows of information between the main objects
⎯ Action diagrams reflecting the co-operation between the main actors.
2 Normative references
This European Standard 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 European Standard only when incorporated in it by amendment or
DRAFT 2009
revision. For undated references the latest edition of the publication referred to applies (including
amendments).
EN ISO 24014-1, Public Transport – Interoperable fare management system – Part 1 Architecture.
ISO/IEC 7498-1:1994, Information Technology - Open systems interconnection reference model -
Basic reference model - Part 1: The basic model (ITU-T Recommendation X.200, 1994).
ISO/IEC 10746-1: Information technology – Open distributed processing – Reference Model: Overview
(ITU-T Recommendation X.901).
ISO/IEC 10746-2: Information technology – Open distributed processing – Reference Model:
Foundations (ITU-T Recommendation X.902).
ISO/IEC 10746-3: Information technology – Open distributed processing – Reference Model:
Architecture (ITU-T Recommendation X.903).
ISO/IEC 10746-4: Information technology – Open distributed processing – Reference Model:
Architectural semantics (ITU-T Recommendation X.904).
ISO/IEC 15414: Information technology – Open distributed processing – Reference Model: Enterprise
language (ITU-T Recommendation X.911).
3 Terms and definitions
For the purposes of this document, the terms and definitions given in ISO/IEC 7498-1:1994,
ISO/IEC 10746-2, ISO/IEC 10746-3, ISO/IEC 15414 and the following apply.
3.1 Customer (of a toll service provider)
A person or legal entity that uses the service of a toll service provider.
NOTE Depending on the local situation the customer may be the owner, lessor, lessee, keeper, (fleet)
operator, holder of the vehicle's registration certificate, driver of the vehicle, or any other third person.
3.2 Driver
A person who drives a vehicle.
NOTE The driver is assumed to operate (use / serve) the OBE (e.g. the setting of the number of axles).
3.3 Electronic fee collection (EFC)
Toll charging by electronic means via a wireless interface.
NOTE The actual payment (collection of the fee) may take place outside the toll system.
3.4 Enforcement
The process of compelling observance of a law, regulation, etc.
NOTE In this context: the process of compelling observance of a toll regime.
3.5 Equipment interoperability
The ability of two or more pieces of equipment to operate in conjunction
3.6 Interoperability
The ability of systems to provide services to and accept services from other systems and to use the
services so exchanged to enable them to operate effectively together.
EXAMPLE For tolling interoperability aims at enabling a vehicle to drive through various toll domains while
having only one OBE operating under one contract with a toll service provider.
DRAFT 2009
3.7 Onboard equipment (OBE)
Equipment fitted within or on the outside of a vehicle and used for toll purposes.
NOTE The OBE does not need to include payment means.
3.8 one(s) liable for toll
Person(s) or legal entities liable to pay toll under the operation of a toll regime.
NOTE A toll regime may designate more than one person to be (jointly and severally) liable for the paying
the toll.
3.9 Point of observation
Interfaces, or in general identifiable accesses to a system, where conformance can be stated and
verified.
3.10 Roadside equipment
Equipment located along the road transport network, for the purpose of communication and data
exchanges with on-board equipments.
3.11 Tariff Scheme
A set of rules to determine the fee due for a vehicle in a toll domain for a tolled object at a certain day
and time.
EXAMPLE A table that shows the fee for various classes of vehicles.
3.12 Toll
A charge, a tax, a fee, or a duty in connection with using a vehicle within a toll domain
NOTE The definition is generalization of the classic definition of a toll as 'a charge, a tax, or a duty for
permission to pass a barrier or to proceed along a road, over a bridge, etc.'. The definition above also includes
fees regarded as an (administrative) obligation, e.g. a tax or a duty.
3.13 Toll charger
A legal entity charging toll for vehicles in a toll domain
NOTE In other documents the terms operator or toll operator may be used.
3.14 Toll declaration (from OBE)
A statement (from the OBE of a vehicle) to a toll charger, not necessarily transmitted via a direct
communication channel, that confirms the presence of a vehicle in a toll domain in a format agreed
between the toll service provider and the toll charger
NOTE A valid toll declaration has to fulfil formal requirements, including security requirements, agreed
between the toll service provider and the toll charger.
3.15 Toll domain
An area or part of a road network where a toll regime is applied
3.16 Toll point
A location within a toll domain where the OBE has to issue a toll declaration.
EXAMPLE A part of a toll plaza for electronic fee collection.
3.17 Toll regime
The set of rules, including enforcement rules, governing the collection of toll in a toll domain.
3.18 Toll schema
A generic term used for toll regime and/or toll domain and/or toll system depending on the context.
DRAFT 2009
3.19 Toll service
A service enabling users having only one contract and one set of OBE to use a vehicle in one or more
toll domains.
3.20 Toll service provider
A legal entity providing to his customers toll services on one or more toll domains for one or more
classes of vehicles.
NOTE 1 In other documents the terms issuer or contract issuer may be used.
NOTE 2 The toll service provider may provide the OBE or may provide only a magnetic card or a smart card to
be used with OBE provided by a third party (like a mobile telephone and a SIM card can be obtained from
different parties).
NOTE 3 The toll service provider is responsible for the operation (functioning) of the OBE.
3.21 Toll system
The off board equipment and possible other provisions used by a toll charger for the collection of toll
for vehicles.
NOTE 1 The OBE is excluded from the definition. If not, OBE should be part of any toll system for which it may
be used.
NOTE 2 The actual payment (collection of the fee) may be take place outside the toll system.
3.22 Toll systems environment management
The controlling enterprise object for the toll systems environment.
NOTE The toll systems environment management may encompass several distinct entities, e.g. a
political/legislative one, a regulatory one, private associations, standardization authorities, and so on.
3.23 Tolled object
A distinguished part of a toll domain for which one or more tariff schema applies.
EXAMPLE A tolled object may be e.g. an area, all public roads within an area, a bridge, a zone, or a stretch
of a road (network).
3.24 user
A generic term used for the customer of a toll service provider, one liable for toll, the owner of the
vehicle, a fleet operator, a driver etc. depending on the context.
DRAFT 2009
4 Abbreviations and symbols
4.1 Abbreviations
For the purpose of this document, the following abbreviations apply throughout the document unless
otherwise specified.
CE  Central Equipment
CRM  Customer Relationship Management
DSRC  Dedicated Short-Range Communication
EETS  European Electronic Toll System
EFC  Electronic Fee Collection
GNSS  Global Navigation Satellite Systems
ID  Identity
IFMSA  Interoperable Fare Management System Architecture
OBU  On-board Unit
ODP  Open Distributed Processing
RSE  Roadside Equipment
SLA  Service Level Agreements
TC  Toll Charger
TMS  Traffic Management System
TTP  Trusted Third Party
UML  Unified Modelling Language

4.2 Symbols
In action diagrams, the following graphical conventions apply:
Rounded corner boxes indicate responsibilities and related activities within roles

Horizontal arrows indicate information exchanges between roles as activities

performed within responsibilities
Vertical arrows represent execution steps within activities

Solid circles represent start of activities

Partially coloured circles represent end of activities

Solid horizontal bars represent decision gates

5 The EFC community: roles and objectives
5.1 Introduction
This clause specifies the EFC community in terms of its relationships and interactions with the external
objects with which the EFC community interacts.
By EFC community is meant:
DRAFT 2009
a) The collection of all entities that have been set up for carrying through the different roles and
responsibilities
b) the EFC specific equipment needed for the fulfilling the roles and responsibilities
c) the vehicle related transport services subject to tolling
By external entities is meant objects that are involved in the toll charging but that are not set up for the
only purpose of toll charging, e.g. satellite positioning systems and standardisation bodies.
The EFC community is represented as a toll charging environment and the objects that the toll
charging environment interacts with, which together act as a configuration of objects formed to meet
an objective which in this case is electronically collecting tolls for vehicle related transport services.
The toll charging environment itself is represented as an enterprise object in the community and the
objectives and scope of the toll charging environment are defined in terms of the roles it fulfils within
the community of which it is part and the policy statements about these roles. Also, the roles of the
enterprise objects external to the toll charging environment are defined here in terms of their
implication for the tolling.
Figure 1 shows the external enterprise objects that define the environment of this Standard. Objects
shown in Figure 1 are the major objects, although there may be other
...