SIST-TS CEN ISO/TS 17575-4:2011
(Main)Electronic fee collection - Application interface definition for autonomous systems - Part 4: Roaming (ISO/TS 17575-4:2011)
Electronic fee collection - Application interface definition for autonomous systems - Part 4: Roaming (ISO/TS 17575-4:2011)
Roaming in the context of this part of ISO/TS 17575 is understood as the ability of a Front End to operate in more than one EFC context either consecutively or at the same time. Data elements required defining operational properties of a single EFC context are defined in ISO/TS 17575-3. The additional data elements required providing interoperability in overlapping and/or interdependent EFC contexts are defined in this part of ISO/TS 17575.
Elektronische Gebührenerfassung - Anwendungsschnittstelle für autonome Systeme - Teil 4: Roaming (ISO/TS 17575-4:2011)
Perception du télépéage - Définition de l'interface d'application pour les systèmes autonomes - Partie 4: Itinérance (ISO/TS 17575-4:2011)
Elektronsko pobiranje pristojbin - Definicija aplikacijskega vmesnika za avtonomne sisteme - 4. del: Gostovanje (ISO/TS 17575-4:2011)
Gostovanje v okviru tega dela ISO/TS 17575 pomeni zmožnost čelnega dela, da deluje v več kot enem okviru EFC bodisi zaporedno bodisi istočasno. Podatkovni elementi, ki določajo lastnosti delovanja enega okvira EFC, so določeni v ISO/TS 17575-3. Dodatni podatkovni elementi, potrebni za zagotavljanje interoperabilnosti v prekrivajočih se in/ali neodvisnih okvirih EFC, so določeni v tem delu ISO/TS 17575.
General Information
Relations
Standards Content (Sample)
SLOVENSKI STANDARD
SIST-TS CEN ISO/TS 17575-4:2011
01-julij-2011
Elektronsko pobiranje pristojbin - Definicija aplikacijskega vmesnika za
avtonomne sisteme - 4. del: Gostovanje (ISO/TS 17575-4:2011)
Electronic fee collection - Application interface definition for autonomous systems - Part
4: Roaming (ISO/TS 17575-4:2011)
Elektronische Gebührenerfassung - Anwendungsschnittstelle für autonome Systeme -
Teil 4: Roaming (ISO/TS 17575-4:2011)
Perception du télépéage - Définition de l'interface d'application pour les systèmes
autonomes - Partie 4: Itinérance (ISO/TS 17575-4:2011)
Ta slovenski standard je istoveten z: CEN ISO/TS 17575-4:2011
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 17575-4:2011 en
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.
---------------------- Page: 1 ----------------------
SIST-TS CEN ISO/TS 17575-4:2011
---------------------- Page: 2 ----------------------
SIST-TS CEN ISO/TS 17575-4:2011
TECHNICAL SPECIFICATION
CEN ISO/TS 17575-4
SPÉCIFICATION TECHNIQUE
TECHNISCHE SPEZIFIKATION
April 2011
ICS 03.220.20; 35.240.60
English Version
Electronic fee collection - Application interface definition for
autonomous systems - Part 4: Roaming (ISO/TS 17575-4:2011)
Perception du télépéage - Définition de l'interface Elektronische Gebührenerfassung -
d'application pour les systèmes autonomes - Partie 4: Anwendungsschnittstelle für autonome Systeme - Teil 4:
Itinérance (ISO/TS 17575-4:2011) Roaming (ISO/TS 17575-4:2011)
This Technical Specification (CEN/TS) was approved by CEN on 18 October 2010 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
promptly at national level in an appropriate form. 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, Bulgaria, Croatia, 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.
EUROPEAN COMMITTEE FOR STANDARDIZATION
COMITÉ EUROPÉEN DE NORMALISATION
EUROPÄISCHES KOMITEE FÜR NORMUNG
Management Centre: Avenue Marnix 17, B-1000 Brussels
© 2011 CEN All rights of exploitation in any form and by any means reserved Ref. No. CEN ISO/TS 17575-4:2011: E
worldwide for CEN national Members.
---------------------- Page: 3 ----------------------
SIST-TS CEN ISO/TS 17575-4:2011
CEN ISO/TS 17575-4:2011 (E)
Contents Page
Foreword .3
2
---------------------- Page: 4 ----------------------
SIST-TS CEN ISO/TS 17575-4:2011
CEN ISO/TS 17575-4:2011 (E)
Foreword
This document (CEN ISO/TS 17575-4:2011) 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".
Attention is drawn to the possibility that some of the elements of this document may be the subject of patent
rights. CEN [and/or CENELEC] shall not be held responsible for identifying any or all such patent rights.
According to the CEN/CENELEC Internal Regulations, the national standards organizations of the following
countries are bound to announce this Technical Specification: Austria, Belgium, Bulgaria, Croatia, 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 the United Kingdom.
3
---------------------- Page: 5 ----------------------
SIST-TS CEN ISO/TS 17575-4:2011
---------------------- Page: 6 ----------------------
SIST-TS CEN ISO/TS 17575-4:2011
TECHNICAL ISO/TS
SPECIFICATION 17575-4
First edition
2011-04-15
Electronic fee collection — Application
interface definition for autonomous
systems —
Part 4:
Roaming
Perception du télépéage — Définition de l'interface d'application pour
les systèmes autonomes —
Partie 4: Itinérance
Reference number
ISO/TS 17575-4:2011(E)
©
ISO 2011
---------------------- Page: 7 ----------------------
SIST-TS CEN ISO/TS 17575-4:2011
ISO/TS 17575-4:2011(E)
COPYRIGHT PROTECTED DOCUMENT
© ISO 2011
All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized in any form or by any means,
electronic or mechanical, including photocopying and microfilm, without permission in writing from 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
Published in Switzerland
ii © ISO 2011 – All rights reserved
---------------------- Page: 8 ----------------------
SIST-TS CEN ISO/TS 17575-4:2011
ISO/TS 17575-4:2011(E)
Contents Page
Foreword .iv
Introduction.v
1 Scope.1
2 Normative References.1
3 Terms and definitions .1
4 Abbreviated terms.4
5 Basic concept .4
5.1 General .4
5.2 Overview.5
6 Data elements .6
6.1 General .6
6.2 Elements of the roaming rules attribute .7
6.2.1 The roaming rule identifier .7
6.2.2 The list of relevant EFC contexts.7
6.2.3 The list of EFC contexts which are grouped using a single charge report.9
6.2.4 House keeping data elements.9
7 Communicating the roaming rules attribute.10
7.1 Requesting an update of the roaming rules attribute.10
7.2 Responding to a roaming rules download request .10
7.3 ASN1 coding rules.10
Annex A (normative) EFC data type specifications .11
Annex B (normative) PICS proforma .13
Annex C (informative) How to assemble and use roaming data.22
Bibliography.24
© ISO 2011 – All rights reserved iii
---------------------- Page: 9 ----------------------
SIST-TS CEN ISO/TS 17575-4:2011
ISO/TS 17575-4:2011(E)
Foreword
ISO (the International Organization for Standardization) is a worldwide federation of national standards bodies
(ISO member bodies). The work of preparing International Standards is normally carried out through ISO
technical committees. Each member body interested in a subject for which a technical committee has been
established has the right to be represented on that committee. International organizations, governmental and
non-governmental, in liaison with ISO, also take part in the work. ISO collaborates closely with the
International Electrotechnical Commission (IEC) on all matters of electrotechnical standardization.
International Standards are drafted in accordance with the rules given in the ISO/IEC Directives, Part 2.
The main task of technical committees is to prepare International Standards. Draft International Standards
adopted by the technical committees are circulated to the member bodies for voting. Publication as an
International Standard requires approval by at least 75 % of the member bodies casting a vote.
In other circumstances, particularly when there is an urgent market requirement for such documents, a
technical committee may decide to publish other types of document:
⎯ an ISO Publicly Available Specification (ISO/PAS) represents an agreement between technical experts in
an ISO working group and is accepted for publication if it is approved by more than 50 % of the members
of the parent committee casting a vote;
⎯ an ISO Technical Specification (ISO/TS) represents an agreement between the members of a technical
committee and is accepted for publication if it is approved by 2/3 of the members of the committee casting
a vote.
An ISO/PAS or ISO/TS is reviewed after three years in order to decide whether it will be confirmed for a
further three years, revised to become an International Standard, or withdrawn. If the ISO/PAS or ISO/TS is
confirmed, it is reviewed again after a further three years, at which time it must either be transformed into an
International Standard or be withdrawn.
Attention is drawn to the possibility that some of the elements of this document may be the subject of patent
rights. ISO shall not be held responsible for identifying any or all such patent rights.
ISO/TS 17575-4 was prepared by the European Committee for Standardization (CEN) Technical Committee
CEN/TC 278, Road transport and traffic telematics, in collaboration with Technical Committee ISO/TC 204,
Intelligent transport systems, in accordance with the Agreement on technical cooperation between ISO and
CEN (Vienna Agreement).
ISO/TS 17575 consists of the following parts, under the general title Electronic fee collection — Application
interface definition for autonomous systems:
⎯ Part 1: Charging
⎯ Part 2: Communication and connection to the lower layers
⎯ Part 3: Context data
⎯ Part 4: Roaming
iv © ISO 2011 – All rights reserved
---------------------- Page: 10 ----------------------
SIST-TS CEN ISO/TS 17575-4:2011
ISO/TS 17575-4:2011(E)
Introduction
Autonomous systems
This part of ISO/TS 17575 is part of a series of four specifications defining the information exchange between
the Front End and the Back End in Electronic Fee Collection (EFC) based on autonomous on-board
equipment (OBE). EFC systems automatically collect charging data for the use of road infrastructure including
motorway tolls, zone-based fees in urban areas, tolls for special infrastructure like bridges and tunnels,
distance-based charging, and parking fees.
Autonomous OBE operates without relying on dedicated road-side infrastructure by employing wide-area
technologies such as Global Navigation Satellite Systems (GNSS) and Cellular Communications Networks
(CN). These EFC systems are referred to by a variety of names. Besides the terms autonomous systems and
GNSS/CN systems, also the terms GPS/GSM systems, and wide-area charging systems are in use.
Autonomous systems use satellite positioning, often combined with additional sensor technologies such as
gyroscopes, odometers and accelerometers, to localize the vehicle and to find its position on a map containing
the charged geographic objects, such as charged roads or charged areas. From the charged objects, the
vehicle characteristics, the time of day and other data that are relevant for describing road use, the tariff and
ultimately the road usage fee are determined.
Some of the strengths of the autonomous approach to electronic fee collection are its flexibility, allowing the
implementation of almost all conceivable charging principles, and its independence from local infrastructure,
thereby predisposing this technology towards interoperability across charging systems and countries.
Interoperability can only be achieved with clearly defined interfaces, which is the aim and justification of
ISO/TS 17575.
Business architecture
This part of ISO/TS 17575 complies with the business architecture defined in ISO 17573. According to this
architecture, the Toll Charger is the provider of the road infrastructure and, hence, the recipient of the road
usage charges. The Toll Charger is the actor associated with the Toll Charging role. See Figure 1.
Interoperability
Management
Service
Provision
Toll
Charging
Service Usage
Figure 1 — The rolebased model underlying this Technical Specification
© ISO 2011 – All rights reserved v
---------------------- Page: 11 ----------------------
SIST-TS CEN ISO/TS 17575-4:2011
ISO/TS 17575-4:2011(E)
Service Providers issue OBE to the users of the road infrastructure. Service Providers are responsible for
operating the OBE that will record the amount of road usage in all toll charging systems the vehicle passes
through and for delivering the charging data to the individual Toll Chargers. In general, each Service Provider
delivers charging data to several Toll Chargers, as well as each Toll Charger in general receives charging
data from more than one Service Provider. Interoperability Management in Figure 1 comprises all
specifications and activities that in common define and maintain a set of rules that govern the overall toll
charging environment.
Technical architecture
The technical architecture of Figure 2 is independent of any particular practical realization. It reflects the fact
that some processing functionalities can either be allocated to the OBE or to an associated off-board
component (Proxy). An example of processing functionality that can be realized either on- or off-board is
map-matching, where the vehicle locations in terms of measured coordinates from GNSS are associated to
geographic objects on a map that either resides on- or off-board. Also tariffication can be done with OBE tariff
tables and processing, or with an off-board component.
Scope of
ISO 17575
Proxy
Processing Equipment
OBE
Front End Back End
Road Usage Data
Context Data
Figure 2 — Assumed technical architecture and interfaces
The combined functionality of OBE and Proxy is denoted as Front End. A Front End implementation where
processing is predominately on OBE-side is known as a smart client (or intelligent client, fat client) or
edge-heavy. A Front End where processing is mostly done off-board is denoted as thin-client or edge-light
architecture. Many implementations between the “thin” and “thick” extremes are possible, as depicted by the
gradual transition in the wedges in Figure 2. Both extremes of architectural choices have their merits and are
one means where manufacturers compete with individual allocations of functionality between on-board and
central resources.
Especially for thin client OBE, manufacturers might devise a wide variety of optimizations of the transfer of
localization data between OBE and off board components, where proprietary algorithms are used for data
reduction and data compression. Standardization of this transfer is neither fully possible nor beneficial.
Location of the specification interface
In order to abstract from, and become independent of, these architectural implementation choices, the primary
scope of ISO/TS 17575 is the data exchange between Front End and Back End (see the corresponding dotted
line in Figure 2). For every toll regime, the Back End will send context data, i.e. a description of the toll regime
in terms of charged objects, charging rules and, if required, the tariff scheme to the Front End, and will receive
usage data from the Front End.
vi © ISO 2011 – All rights reserved
---------------------- Page: 12 ----------------------
SIST-TS CEN ISO/TS 17575-4:2011
ISO/TS 17575-4:2011(E)
It has to be noted also that the distribution of tasks and responsibilities between Service Provider and Toll
Charger will vary individually. Depending on local legal situation, Toll Chargers will require “thinner” or
“thicker” data, and might or might not leave certain data processing tasks to Service Providers. Hence, the
data definitions in ISO/TS 17575 may be useful on several interfaces.
ISO/TS 17575 also provides for basic media-independent communication services that may be used for
communication between Front End and Back End, which might be line-based or an air-link, and can also be
used for the air-link between OBE and central communication server.
The parts of ISO/TS 17575
Part 1: Charging, defines the attributes for the transfer of usage data from the Front End to the Back End. The
required attributes will differ from one Toll Charger to another, hence, attributes for all requirements are
offered, ranging from attributes for raw localization data, for map-matched geographic objects and for
completely priced toll transactions.
Part 2: Communication and connection to lower layers, defines basic communication services for data transfer
over the OBE air-link or between Front End and Back End.
Part 3: Context Data, defines the data to be used for a description of individual charging systems in terms of
charged geographical objects and charging and reporting rules. For every Toll Charger's system, attributes as
defined in Part 3 are used to transfer data to the Front End in order to instruct it which data to collect and
report.
Part 4: Roaming, defines the functional details and data elements required to operate more than one EFC
regime in parallel. The domains of these EFC regimes may or may not overlap. The charge rules of different
overlapping EFC regimes can be linked, i.e. they may include rules that an area pricing scheme will not be
charged if an overlapping toll road is used and already paid for.
Relations between single EFC schemes can be
⎯ EFC domains that can adjoin each other so that when moving from one EFC domain in the domain of the
adjacent EFC regime there may be a zone where the OBE starts to operate according to the rules of the
new regime before stopping the operation according to the old regime rules. Within this zone the
OBE/Front-End needs to operate according to the rules for both of these schemes at the same time.
⎯ Overlapping EFC contexts that can have dependencies in the charge object definition like overlapping
areas where the outer/bigger area will not be charged when in the inner area. Or an area will not be
charged when using a sectioned toll-road in the same area.
⎯ Required to combine several usage statements for different EFC schemes in the same charge report.
The data elements (ADUs) required to specify these related properties are defined in this part of
ISO/TS 17575.
© ISO 2011 – All rights reserved vii
---------------------- Page: 13 ----------------------
SIST-TS CEN ISO/TS 17575-4:2011
ISO/TS 17575-4:2011(E)
Back End Front End
Back End Front End
Application Application
BE calls Front End calls
Scope of
ADU
communication communication
this suite of
Functions for EFC Functions for EFC
standards
communication communication
service primitives
service primitives
data communication service
Figure 3 — Scope of ISO/TS 17575
To communicate these ADUs between the Front End and the Back End, the same methodology as for
ISO/TS 17575-1 and ISO/TS 17575-3 is applied as illustrated in Figure 3. The use of the communication stack
is defined in ISO/TS 17575-2.
Applicatory needs covered by ISO/TS 17575
⎯ The parts of ISO/TS 17575 are compliant with the architecture defined in ISO 17573.
⎯ The parts of ISO/TS 17575 support charges for use of road sections (including bridges, tunnels, passes,
etc.), passage of cordons (entry/exit), and use of infrastructure within an area (distance, time).
⎯ The parts of ISO/TS 17575 support fee collection based on units of distance or duration, and based on
occurrence of events.
⎯ The parts of ISO/TS 17575 support modulation of fees by vehicle category, road category, time of usage,
and contract type (e.g. exempt vehicles, special tariff vehicles, etc.)
⎯ The parts of ISO/TS 17575 support limiting of fees by a defined maximum per period of usage.
⎯ The parts of ISO/TS 17575 support fees with different legal status (e.g. public tax, private toll).
⎯ The parts of ISO/TS 17575 support differing requirements of different Toll Chargers, especially in terms of
⎯ geographic domain and context descriptions,
viii © ISO 2011 – All rights reserved
---------------------- Page: 14 ----------------------
SIST-TS CEN ISO/TS 17575-4:2011
ISO/TS 17575-4:2011(E)
⎯ contents and frequency of charge reports,
⎯ feedback to the driver (e.g. green or red light), and
⎯ provision of additional detailed data on request, e.g. for settling of disputes.
⎯ The parts of ISO/TS 17575 support overlapping geographic toll domains.
⎯ The parts of ISO/TS 17575 support adaptations to changes in
⎯ tolled infrastructure,
⎯ tariffs, and
⎯ participating regimes.
⎯ The parts of ISO/TS 17575 support the provision of trust guarantees by the Service Provider to the Toll
Charger for the data originated from the Front End.
© ISO 2011 – All rights reserved ix
---------------------- Page: 15 ----------------------
SIST-TS CEN ISO/TS 17575-4:2011
---------------------- Page: 16 ----------------------
SIST-TS CEN ISO/TS 17575-4:2011
TECHNICAL SPECIFICATION ISO/TS 17575-4:2011(E)
Electronic fee collection — Application interface definition for
autonomous systems —
Part 4:
Roaming
1 Scope
Roaming in the context of this part of ISO/TS 17575 is understood as the ability of a Front End to operate in
more than one EFC context either consecutively or at the same time. Data elements required defining
operational properties of a single EFC context are defined in ISO/TS 17575-3. The additional data elements
required providing interoperability in overlapping and/or interdependent EFC contexts are defined in this part
of ISO/TS 17575.
2 Normative References
The following referenced documents are indispensable for the application of this document. For dated
references, only the edition cited applies. For undated references, the latest edition of the referenced
document (including any amendments) applies.
ISO/IEC 8824-1, Information technology — Abstract Syntax Notation One (ASN.1): Specification of basic
notation
ISO/IEC 8825-2, Information technology — ASN.1 encoding rules: Specification of Packed Encoding Rules (PER)
ISO 14906, Road transport and traffic telematics — Electronic fee collection — Application interface definition
for dedicated short-range communication
ISO/TS 17575-2, Electronic fee collection — Application interface definition for autonomous systems — Part
2: Communication and connection to the lower layers
ISO/TS 17575-3:2011, Electronic fee collection — Application interface definition for autonomous systems —
Part 3: Context data
EN 15509:2007, Road transport and traffic telematics — Electronic fee collection — Interoperability
application profile for DSRC
3 Terms and definitions
For the purposes of this document, the following terms and definitions apply.
3.1
associated EFC context
EFC context for which an individual user has the contractual consent that his or her Front End is interoperable
3.2
attribute
application information formed by one or by a sequence of data elements, used for implementation of a
transaction
NOTE Adapted from ISO 14906:2011.
© ISO 2011 – All rights reserved 1
---------------------- Page: 17 ----------------------
SIST-TS CEN ISO/TS 17575-4:2011
ISO/TS 17575-4:2011(E)
3.3
authenticator
data appended to, or a cryptographic transformation of, a data unit that allows a recipient of the data unit to
prove the source and/or the integrity of the data unit and protect against forgery
[ISO 14906:2011, definition 3.4]
3.4
Back End
generic name for the computing and communication facilities of the Service Provider and/or the Toll Charger
3.5
contract
expression of an agreement between two or more parties concerning the use of the road infrastructure
[ISO 14906:2011, definition 3.7]
3.6
Front End
part(s) of the toll system where road usage data for an individual road user are collected, processed and
delivered to the Back End
NOTE The Front End comprises the on-board equipment and an optional proxy.
3.7
interoperability
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
3.8
on-board 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.
[ISO 14906:2011, definition 3.13]
3.9
proxy
optional component of the Front End that communicates with on-board equipment and processes road usage
data into a format compliant with this part of ISO/TS 17575 and delivers the data to the Back End
3.10
roadside equipment
equipment located along the road transport network, for the purpose of communication and data exchanges
with on-board equipment
[ISO 14906:2011, definition 3.16]
3.11
service primitive (communication)
elementary communication service provided by the application layer protocol to the application processes
[ISO 14906:2011, definition 3.18]
NOTE The invocation of a service primitive by an application process implicitly calls upon and uses services offered
by the lower protocol layers.
2 © ISO 2011 – All rights reserved
---------------------- Page: 18 ----------------------
SIST-TS CEN ISO/TS 17575-4:2011
ISO/TS 17575-4:2011(E)
3.12
service provider (toll)
legal entity providing its customers with toll services in one or more toll domains for one or more classes of
vehicle
3.13
system
something of interest as a whole or as comprised of parts
NOTE A system can be referred to as an entity. A component of a system can itself be a system, in which case it can
be called a subsystem.
3.14
toll
charge, tax, fee or duty in connection with using a vehicle within a toll domain
NOTE The definition is the 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.15
toll charger
legal entity charging toll for vehicles in a toll domain
[ISO/TS 17574:2009, definition 3.27]
3.16
toll cluster
group of toll schemes operating under a common agreement providing interoperability for vehicles equipped
with an appropriate OBE and being contracted under a toll service provider being part of the cluster
3.17
toll context
logical view of a toll scheme as defined by attributes and functions
NOTE Adapted from ISO/TS 12813:2009.
3.18
toll domain
area or part of a road network where a toll regime is applied
[ISO 14906:2011, definition 3.21]
3.19
toll regime
set of rules, including enforcement rules, governing the collection of toll in a toll domain
3.20
toll scheme
organizational view of a toll regime, including the group of actors of one toll domain and their relationships
3.21
toll service
service enabling users having only one contract and one set of OBE to use a vehicle in one or more toll
domains
NOTE Adapted from ISO/TS 12813:2009.
© ISO 2011 – All rights reserved 3
---------------------- Page: 19 ----------------------
SIST-TS CEN ISO/TS 17575-4:2011
ISO/TS 17575-4:2011(E)
3.22
toll system
overall view of a to
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.