ISO 15638-14:2014

Intelligent transport systems - Framework for cooperative telematics applications for regulated vehicles (TARV) - Part 14: Vehicle access control

ISO 15638-14:2014 addresses the provision of "vehicle access control" and specifies the form and content of such data required to support such systems, and access methods to that data. ISO 15638-14:2014 provides specifications for common communications and data exchange aspects of the application service vehicle access control that a regulator may elect to require or support as an option, including a) high-level definition of the service that a service provider has to provide, [The service definition describes common service elements; but does not define the detail of how such an application service is instantiated, not the acceptable value ranges of the data concepts defined.], b) means to realize the service, and c) application data, naming content and quality that an IVS has to deliver.

Systèmes intelligents de transport — Cadre pour applications télématiques collaboratives pour véhicules réglementés (TARV) — Partie 14: Contrôle de l'accès des véhicules

General Information

• Status: Published
• Publication Date: 06-Jul-2014
• ICS: 03.220.20 - Road transport
• ICS: 35.240.60 - IT applications in transport
• Technical Committee: ISO/TC 204 - Intelligent transport systems
• Drafting Committee: ISO/TC 204/WG 7 - General fleet management and commercial/freight
• Current Stage: 9060 - Close of review
• Completion Date: 04-Jun-2030

Relations

• Revises: ISO/TS 15638-14:2013 - Intelligent transport systems - Framework for collaborative Telematics Applications for Regulated commercial freight Vehicles (TARV) - Part 14: Vehicle access control (VAC)
• Effective Date: 28-Sep-2013

Overview

ISO 15638-14:2014 - part of the TARV family - defines the framework for vehicle access control within intelligent transport systems (ITS) for regulated vehicles. The standard specifies the form and content of data required to support vehicle access control services, the access methods to that data, and the common communications and data-exchange aspects that a regulator may require or support. It describes high‑level service definitions, means to realize those services, and the naming, content and quality expectations that an in-vehicle system (IVS) must deliver.

Key technical topics and requirements

• Service definition (high level): Common service elements for vehicle access control (does not prescribe implementation detail or acceptable value ranges).
• Data form and content: Standardized application data concepts, naming conventions and quality attributes required from IVSs.
• Access methods: Specified means to access and exchange vehicle access control data between IVS, service providers and jurisdictional systems.
• Quality of service & testing: Requirements for QoS and test criteria; Annex B documents independent protocol testing results.
• Conformance model: Conformance responsibility is determined by the jurisdiction where services are instantiated; approval and audit provisions for IVSs and service providers.
• Information security & access control policy: Requirements and guidance on information security, data access control and related operational processes.
• Operational rules & sequences: Concept of operations and typical sequences for regulated vehicle access control services.
• Support for approval and auditing: Provisions for approval authorities, marking/labeling, software quality systems and monitoring stations.

Practical applications and who uses it

ISO 15638-14 is practical for organizations implementing regulated telematics services that control vehicle access, including:

• Regulators and jurisdictional authorities defining access rules, conformance and enforcement procedures.
• Service providers and telematics operators delivering vehicle access control services to fleets and governments.
• IVS manufacturers and system integrators implementing standardized data naming, interfaces and security features.
• Testing laboratories and certification bodies using Annex B test results and conformance guidance.
• Fleet operators and logistics companies deploying compliant telematics to meet regulatory access requirements.

Benefits include interoperability across jurisdictions, reduced deployment cost through common data models, and a clear framework for approvals, testing and auditing.

Related standards

ISO 15638-14 is one part of the TARV suite; related parts include:

• ISO 15638-1 (Framework and architecture)
• ISO 15638-2 (Common platform parameters using CALM)
• ISO 15638-3 (Operating requirements and approval procedures)
• ISO 15638-5 (Generic vehicle information)
  Others in the series address security, monitoring and specific regulated applications.

Keywords: ISO 15638-14, vehicle access control, TARV, intelligent transport systems, telematics, regulated vehicles, IVS, data naming, quality of service, conformance.

Standards Content (Sample)

INTERNATIONAL ISO
STANDARD 15638-14
First edition
2014-07-15
Intelligent transport systems —
Framework for cooperative telematics
applications for regulated vehicles
(TARV) —
Part 14:
Vehicle access control
Systèmes intelligents de transport — Cadre pour applications
télématiques collaboratives pour véhicules réglementés (TARV) —
Partie 14: Contrôle de l’accès des véhicules
Reference number
©
ISO 2014
© ISO 2014
All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized otherwise in any form
or by any means, electronic or mechanical, including photocopying, or posting on the internet or an intranet, without prior
written permission. Permission can be requested 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 [e-mail]
Web www.iso.org
Published in Switzerland
ii © ISO 2014 – All rights reserved

Contents Page
Foreword .iv
Introduction .vi
1 Scope . 1
2 Conformance . 1
3 Normative references . 1
4 Terms and definitions . 2
5 Symbols and abbreviated terms . 7
6 General overview and framework requirements . 9
7 Requirements for services using generic vehicle data . 9
8 Application services that require data in addition to basic vehicle data .9
8.1 General . 9
8.2 Quality of service requirements . 9
8.3 Test requirements . 9
8.4 Marking, labelling and packaging .10
9 Common features of regulated TARV application services .10
9.1 General .10
9.2 Common role of the jurisdiction, approval authority, service provider, and user .11
9.3 Common characteristics for instantiations of regulated application services .11
9.4 Common sequence of operations for regulated application services .11
9.5 Quality of service .11
9.6 Information security .12
9.7 Data naming content and quality .12
9.8 Software engineering quality systems .12
9.9 Quality monitoring station .12
9.10 Audits .12
9.11 Data access control policy .12
9.12 Approval of IVSs and service providers .12
10 Vehicle access control (VAC) .12
10.1 TARV VAC service description and scope — VAC use cases .12
10.2 Concept of operations for vehicle access control .13
10.3 Sequence of operations for TARV VAC .26
10.4 Generic TARV VAC data naming content and quality .28
10.5 Specific TARV VAC data naming content and quality .28
10.6 TARV VAC application service specific provisions for quality of service .28
10.7 TARV VAC application service specific provisions for test requirements .29
10.8 TARV VAC application specific rules for the approval of IVSs and ‘service providers’ .29
11 Declaration of patents and intellectual property .29
Annex A (informative) ASN.1 modules for ISO 15638-14 data concepts .30
Annex B (informative) Independent testing of the protocols defined in this part of ISO 15638 .32
Bibliography .48
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.
The procedures used to develop this document and those intended for its further maintenance are
described in the ISO/IEC Directives, Part 1. In particular the different approval criteria needed for the
different types of ISO documents should be noted. This document was drafted in accordance with the
editorial rules of the ISO/IEC Directives, Part 2 (see www.iso.org/directives).
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. Details of
any patent rights identified during the development of the document will be in the Introduction and/or
on the ISO list of patent declarations received (see www.iso.org/patents).
Any trade name used in this document is information given for the convenience of users and does not
constitute an endorsement.
For an explanation on the meaning of ISO specific terms and expressions related to conformity
assessment, as well as information about ISO’s adherence to the WTO principles in the Technical Barriers
to Trade (TBT) see the following URL: Foreword - Supplementary information
The committee responsible for this document is ISO/TC 204, Intelligent transport systems.
This first edition cancels and replaces ISO/TS 15638-14:2013.
ISO 15638 consists of the following parts, under the general title Intelligent transport systems —
Framework for cooperative telematics applications for regulated vehicles (TARV):
— Part 1: Framework and architecture
— Part 2: Common platform parameters using CALM
— Part 3: Operating requirements, ‘Approval Authority’ procedures, and enforcement provisions for the
providers of regulated services
— Part 5: Generic vehicle information
— Part 6: Regulated applications
— Part 7: Other applications
— Part 8: Vehicle access management and monitoring
— Part 9: Remote electronic tachograph monitoring (RTM)
— Part 10: Emergency messaging system/eCall (EMS)
— Part 11: Driver work records
— Part 12: Vehicle mass monitoring
— Part 14: Vehicle access control
— Part 15: Vehicle location monitoring
— Part 16: Vehicle speed monitoring
iv © ISO 2014 – All rights reserved

— Part 17: Consignment and location monitoring
— Part 18: ADR (Dangerous Goods) transport monitoring (ADR)
— Part 19: Vehicle parking facilities (VPF)
The following parts are under preparation:
— Part 4: System security requirements
— Part 13: ‘Mass’ information for jurisdictional control and enforcement
Introduction
Many ITS technologies have been embraced by commercial transport operators (4.36) and freight
owners, in the areas of fleet management, safety and security. Telematics (4.48) applications have also
been developed for governmental use. Such regulatory services in use or being considered vary from
jurisdiction (4.32) to jurisdiction, but include electronic on-board recorders, digital tachograph (4.47),
on-board mass (4.34) monitoring, ‘mass’ penalties and levies, vehicle access (4.1) methods, hazardous
goods (4.22) tracking, and e-call. Additional applications with a regulatory impact being developed
include, fatigue management, speed monitoring, and heavy vehicle penalties imposed based on location,
distance, and time.
In such an emerging environment of regulatory and commercial applications (4.17), it is timely to
consider an overall architecture (4.12) (business and functional) that could support these functions from
a single platform within a commercial freight vehicle that operate within such regulations. International
Standards will allow for a speedy development and specification (4.46) of new applications that build
upon the functionality of a generic specification platform. A suite of standards deliverables is required
to describe and define the framework (4.28) and requirements so that the on board equipment and
back office systems can be commercially designed in an open market to meet common requirements of
jurisdictions (4.32).
This International Standard addresses and defines the framework (4.28) for a range of cooperative
telematics (4.48) applications for regulated commercial freight vehicles (4.40) [such as access methods
(4.3), driver fatigue management, speed monitoring, on-board mass (4.34) monitoring, penalties and
levies]. The overall scope includes the concept of operation, legal and regulatory issues, and the generic
cooperative provision of services to regulated vehicles, using an on-board ITS platform. The framework
is based on a (multiple) service provider (4.44) oriented approach with provisions for the approval (4.9)
and auditing (4.13) of service providers.
This International Standard will
— provides the basis for future development of cooperative telematics (4.48) applications for regulated
vehicles (4.40). Many elements to accomplish this are already available. Existing relevant standards
will be referenced, and the specifications (4.46) will use existing standards (such as CALM) wherever
practicable,
— allows for a powerful platform for highly cost-effective delivery of a range of telematics applications
for regulated vehicles,
— provide a business architecture (4.12) based on a (multiple) service provider (4.44) oriented approach,
and
— addresses legal and regulatory aspects for the approval (4.9) and auditing (4.13) of service providers.
This International Standard is timely as many governments (Europe, North America, Asia, and
Australia/New Zealand) are considering the use of telematics (4.48) for a range of regulatory purposes.
Ensuring that a single in-vehicle platform can deliver a range of services to both government and
industry through open standards and competitive markets is a strategic objective.
This part of ISO 15638 provides specifications (4.46) for vehicle access control.
NOTE 1 The definition of what comprises a “regulated commercial freight vehicle” is regarded as an issue
for national decision, and may vary from jurisdiction (4.32) to jurisdiction. This International Standard does not
impose any requirements on nations in respect of how they define a regulated vehicle (4.40).
NOTE 2 The definition of what comprises a “regulated” service is regarded as an issue for national decision, and
may vary from jurisdiction (4.32) to jurisdiction. This International Standard does not impose any requirements on
nations in respect of which services for regulated vehicles (4.40) jurisdictions will require, or support as an option,
but will provide standardized sets of requirements descriptions for identified services to enable consistent and
cost efficient implementations where implemented.
vi © ISO 2014 – All rights reserved

INTERNATIONAL STANDARD ISO 15638-14:2014(E)
Intelligent transport systems — Framework for
cooperative telematics applications for regulated vehicles
(TARV) —
Part 14:
Vehicle access control
1 Scope
This part of ISO 15638 addresses the provision of “vehicle access control” and specifies the form and
content of such data required to support such systems, and access methods (4.3) to that data.
The scope of this part of ISO 15638 is to provide specifications (4.46) for common communications and
data exchange aspects of the application service (4.6) vehicle access control that a regulator may elect to
require or support as an option, including
a) high-level definition of the service that a service provider (4.44) has to provide, [The service definition
describes common service elements; but does not define the detail of how such an application service
(4.6) is instantiated, not the acceptable value ranges of the data concepts defined.],
b) means to realize the service, and
c) application data, naming content and quality that an IVS (4.29) has to deliver.
The definition of what comprises a “regulated” service is regarded as an issue for National decision,
and may vary from jurisdiction (4.32) to jurisdiction. This International Standard does not impose any
requirements on nations in respect of which services for regulated commercial freight vehicles (4.40)
jurisdictions will require, or support as an option, but provides standardized sets of requirements
descriptions for identified services to enable consistent and cost efficient implementations where
instantiated.
This International Standard has been developed for use in the context of regulated commercial freight
vehicles (4.40). There is nothing however to prevent a jurisdiction extending or adapting the scope to
include other types of regulated vehicles, as it deems appropriate.
2 Conformance
Requirements to demonstrate conformance to any of the general provisions or specific application
services (4.6) described in this part of ISO 15638 shall be within the regulations imposed by the
jurisdiction (4.32) where they are instantiated. Conformance requirements to meet the provisions of
this International Standard are therefore deemed to be under the control of, and to the specification of,
the jurisdiction where the application service(s) is/are instantiated.
The protocols defined in this part of ISO 15638 have been independently tested. Annex B provides
results of these tests. In any conformance assurance process undertaken by candidate systems, where
appropriate, the results may be used as part of its process of conformance compliance.
3 Normative references
The following documents, in whole or in part, are normatively referenced in this document and are
indispensable for its application. For dated references, only the edition cited applies. For undated
references, the latest edition of the referenced document (including any amendments) applies.
ISO 15638-1, Intelligent transport systems — Framework for collaborative telematics applications for
regulated commercial freight vehicles (TARV) — Part 1: Framework and architecture
ISO 15638-2, Intelligent transport systems — Framework for collaborative telematics applications for
regulated commercial freight vehicles (TARV) — Part 2: Common platform parameters using CALM
ISO 15638-3, Intelligent transport systems — Framework for collaborative telematics applications for
regulated commercial freight vehicles (TARV) — Part 3: Operating requirements, ‘Approval Authority’
procedures, and enforcement provisions for the providers of regulated services
1)
ISO 15638-4:— , Intelligent transport systems — Framework for cooperative telematics applications for
regulated vehicles (TARV) — System security requirements
ISO 15638-5, Intelligent transport systems — Framework for collaborative telematics applications for
regulated commercial freight vehicles (TARV) — Part 5: Generic vehicle information
ISO 15638-6, Intelligent transport systems — Framework for collaborative telematics applications for
regulated commercial freight vehicles (TARV) — Part 6: Regulated applications
ISO 15638-8, Intelligent transport systems — Framework for cooperative telematics applications for
regulated vehicles (TARV) — Part 8: Vehicle access management
4 Terms and definitions
For the purposes of this document, the following terms and definitions given in ISO 15638-1 and the
following apply.
4.1
access
admittance, entry, permit to use the road network and/or associated infrastructure (bridges, tunnels
etc.)
4.2
access control
procedures and measures to control admittance, entry, permit to use the road network and/or associated
infrastructure (bridges, tunnels etc.)
4.3
access methods
procedures and protocols to provision and retrieve data
4.4
access monitoring
observation and recording of vehicle related data when using the road network and/or associated
infrastructure (bridges, tunnels etc.)
4.5
app
2)
small (usually) Java™ applets, organized as software bundles, that support application services (4.6) by
keeping the data pantry (4.23) of the IVS (4.29) provisioned with up-to-date data
4.6
application service
service provided by a service provider (4.44) enabled by accessing data from the IVS (4.29) of a regulated
vehicle (4.40) via a wireless communications network
1) To be published.
2) This information is given for the convenience of users of this document and does not constitute an endorsement
by ISO.
2 © ISO 2014 – All rights reserved

4.7
application service provider
ASP
party that provides an application service (4.6)
4.8
app library
separately secure area of memory in IVS (4.29) where apps are stored (with different access controls to
data pantry (4.23))
4.9
approval
formal affirmation that an applicant has satisfied all the requirements for appointment as an application
service provider (4.7) or that an application service (4.6) delivers the required service levels
4.10
approval agreement
written agreement made between an approval authority (regulatory) (4.11) and a service provider (4.44)
Note 1 to entry: Approval authority (regulatory) (4.11) approval agreement recognizes the fact that a service
provider (4.44), having satisfied the approval authority’s requirements for appointment as a service provider, is
appointed in that capacity, and sets out the legal obligations of the parties, with respect to the on-going role of the
service provider.
4.11
approval authority (regulatory)
organization (usually independent) which conducts approval (4.9) and ongoing audit (4.13) for service
providers (4.44) on behalf of a jurisdiction (4.32)
4.12
architecture
formalized description of the design of the structure of TARV and its framework (4.28)
4.13
audit
auditing
review of a party’s capacity to meet, or continue to meet, the initial and on-going approval agreements
(4.10) as a service provider (4.44)
4.14
basic vehicle data
data that shall be maintained/provided by all IVS (4.29) regardless of jurisdiction (4.32)
4.15
BigBubble
zones, such as metropolitan area, which include within them several sensitive/restricted zones (4.42)
4.16
communications access for land mobiles
CALM
layered solution that enables continuous or quasi continuous communications between vehicles and the
infrastructure, or between vehicles, using such (multiple) wireless telecommunications media that are
available in any particular location, and which have the ability to migrate to a different available media
where required and where media selection is at the discretion of user (4.49) determined parameters,
by using a suite of International Standards based on ISO 21217 (CALM architecture) and ISO 21210
(CALM networking), that provide a common platform for a number of standardized media using ITS-
stations (4.31) to provide wireless support for applications, such that the application is independent of
any particular wireless medium
4.17
commercial application(s)
ITS applications in regulated vehicles (4.40) for commercial (non-regulated) purposes
EXAMPLE Asset tracking, vehicle and engine monitoring, cargo security, driver management, etc.
4.18
consignment and load monitoring
monitoring of shipment of goods/cargo throughout or at specific points of a journey to a destination
4.19
controlled zone
controlled access zone
defined physical area which the jurisdiction (4.32) or controlled zone manager determines require access
control (4.2) for regulated vehicles (4.40)
4.20
cooperative ITS
C-ITS
ITS applications for both regulatory and commercial purposes that require the exchange of data between
uncontracted parties using multiple ITS-stations (4.31) communicating with each other and sharing data
with other parties with whom they have no direct contractual relationship to provide one or more ITS
services (4.29)
4.21
core data
basic vehicle data (4.14) plus any additional data required to provide an implemented regulated application
service (4.39)
4.22
dangerous goods
hazardous goods
HAZMAT
substances or articles which are potentially hazardous (for example, poisonous to humans, harmful to
the environment, explosive, flammable, or radioactive) that require regulatory control when transported
4.23
data pantry
secure area of memory in IVS (4.29) where data values are stored with different access controls to app
library (4.8)
4.24
driver
person driving the regulated vehicle (4.40) at any specific point in time
4.25
driver work records
DWR
collection, collation, and transfer of driver (4.24) work and rest hours data from an in-vehicle system
(4.29) to an application service provider (4.7)
4.26
emergency message system
EMS
collection, collation, and transfer of emergency message data from an in-vehicle system (4.29) to an
application service provider (4.7)
4.27
facilities
layer that sits on top of the communication stack and helps to provide data interoperability and reuse,
and to manage applications and enable dynamic real time loading of new applications
4 © ISO 2014 – All rights reserved

4.28
framework
particular set of beliefs, ideas referred to in order to describe a scenario or solve a problem
4.29
in-vehicle system
IVS
ITS-station (4.31) and connected equipment on board a vehicle
4.30
ITS service
communication functionality offered by an ITS-station (4.31) to an ITS-station application
4.31
ITS-station
ITS-s
entity in a communication network, comprised of application, facilities (4.27), networking, and access
layer components specified in ISO 21217 that operate within a bounded secure management domain
4.32
jurisdiction
government, road, or traffic authority which owns the regulatory applications (4.38)
EXAMPLE Country, state, city council, road authority, government department (customs, treasury, transport),
etc.
4.33
local data tree
LDT
frequently updated data concept stored in the on-board data pantry (4.23) containing a collection of
data values deemed essential for either a) TARV regulated application service (4.39), or b) cooperative
intelligent transport systems (4.20)
4.34
mass
mass of a given heavy vehicle as measured by equipment affixed to the regulated vehicle (4.40)
4.35
‘mass’ information for jurisdictional control and enforcement
MICE
MRC
collection, collation, and transfer of vehicle mass (4.34) data from an in-vehicle system (4.29) to an
application service provider (4.7) to enable data provision to jurisdictions (4.32) for the control and
management of equipped vehicles based on the mass of the regulated vehicle (4.40), or use of such data to
enable compliance with the provisions of regulations
4.36
operator
fleet manager of a regulated vehicle (4.40)
4.37
prime service provider
service provider (4.44) who is the first contractor to provide regulated application services (4.39) to the
regulated vehicle (4.40), or a nominated successor on termination of that initial contract; the prime service
provider is also responsible to maintain the installed IVS (4.29); if the IVS was not installed during the
manufacture of the vehicle the prime service provider is also responsible to install and commission the
IVS
4.38
regulated application
regulatory application
application arrangement using TARV utilized by jurisdictions (4.32) for granting certain categories
of commercial vehicles rights to operate in regulated circumstances subject to certain conditions, or
indeed to permit a vehicle to operate within the jurisdiction; may be mandatory or voluntary at the
discretion of the jurisdiction
4.39
regulated application service
TARV application service (4.6) to meet the requirements of a regulated application that is mandated by a
regulation imposed by a jurisdiction (4.32), or is an option supported by a jurisdiction
4.40
regulated commercial freight vehicle
regulated vehicle
vehicle that is subject to regulations determined by the jurisdiction (4.32) as to its use on the road system
of the jurisdiction in regulated circumstances, subject to certain conditions, and in compliance with
specific regulations for that class of regulated vehicle; at the option of jurisdictions; this may require the
provision of information via TARV or provide the option to do so
4.41
remote tachograph monitoring
RTM
collection, collation, and transfer of data from an on-board electronic tachograph (4.47) system to an
application service provider (4.7)
4.42
sensitive/restricted zone
defined physical area which the jurisdiction (4.32) or sensitive/restricted zone manager determines
require special monitoring (e.g. urban pedestrian areas, school and hospital surroundings, …), freight
villages, ports, road sensitivity infrastructure (bridges, tunnels, …)., weight restricted areas, width
restricted areas, areas where there has been an accident or incident, etc.
4.43
sensitive/restricted zone management
monitoring and management of regulated vehicles (4.40) in additional to normal traffic management, as
specified by the jurisdiction (4.32) or its agents to apply to regulated vehicles
4.44
service provider
party which is approved by an approval authority (regulatory) (4.11) as suitable to provide regulated or
commercial ITS application services (4.6)
4.45
session
wireless communication exchange between the ITS-station (4.31) of an IVS (4.29) and the ITS-station of
its application service provider (4.7) to achieve data update, data provision, upload apps, or otherwise
manage the provision of the application service (4.6), or a wireless communication provision of data to
the ITS-station of an IVS (4.29) from any other ITS-station
4.46
specification
explicit and detailed description of the nature and functional requirements and minimum performance
of equipment, service, or a combination of both
6 © ISO 2014 – All rights reserved

4.47
tachograph
sender unit mounted to a vehicle gearbox, a tachograph head, and a digital driver card, which records
the regulated vehicle (4.40) speed and the times at which it was driven and aspects of the driver’s (4.24)
activity selected from a choice of modes
4.48
telematics
use of wireless media to obtain and transmit (data) from a distant source
4.49
user
individual or party that enrols in and operates within a regulated or commercial application (4.17) service
EXAMPLE Driver (4.24), transport operator (4.36), freight owner, etc.
4.50
vehicle access control
VAC
control of regulated commercial freight vehicles (4.40) ingress to and egress from controlled areas and
associated penalties and levies
4.51
vehicle access management
VAM
monitoring and management of regulated vehicles (4.40) approaching or within sensitive and controlled
areas
4.52
vehicle location monitoring
VLM
collection, collation, and transfer of vehicle location data from an in-vehicle system (4.29) to an application
service provider (4.7)
4.53
vehicle mass monitoring
VMM
collection, collation, and transfer of vehicle mass (4.34) data from an in-vehicle system (4.29) to an
application service provider (4.7)
4.54
vehicle parking facility
VPF
system for booking and access (4.1) to and egress from a vehicle parking facility (VPF)
4.55
vehicle speed monitoring
VSM
collection, collation, and transfer of vehicle speed data from an in-vehicle system (4.29) to an application
service provider (4.7)
5 Symbols and abbreviated terms
AA approval authority (regulatory) (4.11)
ADR Accord Européen relatif au transport international des marchandises Dangereuses par Route [dangerous
goods (4.22)]
TMa
app applet (Java application or similar) (4.5)
AS application service
ASP application service provider (4.7)
CALM communications access for land mobiles (4.16)
C-ITS cooperative intelligent transport systems (4.20)
CZM controlled access zone (4.19) management/manager
Dr driver (4.24)
DWR driver work records (4.25)
EMS emergency message system (4.26)
ID identity
IP internet protocol
ITS-S ITS station (4.31)
IVS in-vehicle system (4.29)
J jurisdiction (4.32)
a
Java™ object-oriented open-source operating language developed by SUN systems
LDT local data tree (4.33)
MICE/ ‘Mass’ information for jurisdictional control and enforcement (4.35)/‘Mass’ regulation and control
MRC
Op operator (4.36)
PSP prime service provider (4.36)
RTM remote tachograph monitoring (4.40)
SE service element
SPF secure parking facility
SZM sensitive/restricted zone management (4.43)/manager
TARV telematics (4.48) applications for regulated vehicles (4.40)
VAC vehicle access control (4.50)
VAM vehicle access management (4.51)
VLM vehicle location monitoring (4.52)
VMM vehicle mass monitoring (4.53)
VPF vehicle parking facilities (4.54)
VSM vehicle speed monitoring (4.55)
a
This information is given for the convenience of users of this document and does not constitute an endorse-
ment by ISO.
8 © ISO 2014 – All rights reserved

6 General overview and framework requirements
ISO 15638-1 provides a framework (4.28) and architecture (4.12) for TARV. It provides a general description
of the roles of the actors in TARV and their relationships.
To understand clearly the TARV framework, architecture (4.12), and detail and specification (4.46) of the
roles of the actors involved, the reader is referred to ISO 15638-1.
ISO 15638-6 provides the core requirements for all regulated applications. To understand clearly the
general context in to which the provision of this application service, the reader is referred to ISO 15638-6.
In order to be compliant with this part of ISO 15638, the overall architecture employed shall comply
with ISO 15638-1.
In order to be compliant with this part of ISO 15638, the communications employed shall comply with
ISO 15638-2.
In order to be compliant with this part of ISO 15638, the operating requirements employed shall comply
with ISO 15638-3.
In order to be compliant with this part of ISO 15638, the security employed shall comply with ISO 15638-4.
In order to be compliant with this part of ISO 15638, the basic vehicle data shall comply with ISO 15638-5.
In order to be compliant with this part of ISO 15638, the generic conditions for this application service
shall comply with ISO 15638-6.
This International Standard has been developed for use in the context of regulated commercial freight
vehicles [hereinafter referred to as ‘regulated vehicles’ (4.40)]. There is nothing, however, to prevent a
jurisdiction extending or adapting the scope to include other types of regulated vehicles, as it deems
appropriate.
7 Requirements for services using generic vehicle data
The means by which the access commands for generic vehicle information specified in ISO 15638-5 can
be used to provide all or part of the data required in order to support a regulated application service
(4.39) shall be as defined in ISO 15638-6.
8 Application services that require data in addition to basic vehicle data
8.1 General
Application services that require data in addition to basic vehicle data shall be conducted as defined in
ISO 15638-6.
8.2 Quality of service requirements
This part of ISO 15638 contains no general requirements concerning quality of service. Such aspects
shall be determined by a jurisdiction (4.32) as part of its specification (4.46) for any particular regulated
application service (4.39). However, where a specified regulated application service (4.39) has specific
quality of service requirements essential to maintain interoperability, these aspects shall be as specified
in Clause 10.
8.3 Test requirements
This part of ISO 15638 contains no general requirements concerning test requirements. Such aspects
shall be determined by a jurisdiction (4.32) as part of its specification (4.46) for any particular regulated
application service (4.39), and issued as a formal test requirements specification (4.46) document.
However, where a specified regulated application service (4.39) has specific test requirements essential
to maintain interoperability, these aspects shall be as specified in Clause 10 relating to this regulated
application service, or in a separate standards deliverable referenced within that clause. Where multiple
jurisdictions recognize a benefit to common test procedures for a specific regulated application service,
this shall be the subject of a separate standards deliverable.
8.4 Marking, labelling and packaging
This part of ISO 15638 has no specific requirements for marking labelling or packaging.
However, where the privacy of an individual can be potentially or actually compromised by any
instantiation based on this International Standard, the contracting parties shall make such risk explicitly
known to the implementing jurisdiction (4.32) and shall abide by the privacy laws and regulations
of the implementing jurisdiction and shall mark up or label any contracts specifically and explicitly
drawing attention to any loss of privacy and precautions taken to protect privacy. Attention is drawn to
ISO/TR 12859 in this respect.
9 Common features of regulated TARV application services
9.1 General
The details of the instantiation of regulated application service (4.39) are as designed by the application
service system to meet the requirements of a particular jurisdiction (4.32) and are not defined herein.
ISO 15638-6 specifies the generic roles and responsibilities of actors in the systems, and instantiations
that claim compliance with this part of ISO 15638 shall also be compliant with the requirements of
ISO 15638-6.
The means by which data are provisioned into the data pantry (4.23), and the means to obtain the TARV
LDT (4.33) and core data (4.21) are described in ISO 15638-6, Clause 8 (esp. 8.3).
In order to minimize demand on the IVS (4.29) [which it is assumed will be performing multiple application
services (4.6) simultaneously, as well as supporting general safety related cooperative vehicle systems],
and because national requirements and system offerings will differ, a ‘cloud’ approach has been taken in
defining TARV regulated application services (4.39).
The TARV approach is for the on-board app (4.5) supporting the application service to collect and collate
the relevant data, and at intervals determined by the app, or on demand from the application service
provider (ASP) (4.7), pass that data to the ASP. All of the actual application service processing shall occur
in the mainframe system of the ASP (in the ‘cloud’).
For further information see ISO 15638-6, Clause 9.
At a conceptual level, The TARV system is therefore essentially simple, as shown in Figure 1. The process
is similar to that for CoreData, but data are supplied to a different on-board file in the data pantry
(4.23).
10 © ISO 2014 – All rights reserved

Run on-board 'app'
Collect and ile data in
on-board data pantry
Transfer the data to
Application service
ASP system
Provider
wireless link
Delete ile content and
return to repopulate
data into ile
Figure 1 — TARV regulated application service on-board procedure
At a common generic functional level for this application service, the process may be seen as shown in
Figure 2 below, however, the connected equipment may/may not be required in all cases.
9.2 Common role of the jurisdiction, approval authority, service provider, and user
The common role of the jurisdiction, approval authority, application service provider, and user shall be
as defined in ISO 15638-6, 10.2.4 and 10.2.5.
9.3 Common characteristics for instantiations of regulated application services
The common characteristics for instantiations of regulated application services shall be as defined in
ISO 15638-6.
9.4 Common sequence of operations for regulated application services
The common sequence of operations for regulated application services shall be as defined in ISO 15638-6.
9.5 Quality of service
Generic quality of service provisions for application services (4.6) shall be as defined in ISO 15638-6.
9.6 Information security
Information security shall be as defined in ISO 15638-6.
9.7 Data naming content and quality
Data naming and quality shall be as defined in ISO 15638-6.
Variations specific to the vehicle access control application service (4.6) shall be as defined below.
9.8 Software engineering quality systems
Software engineering quality systems shall be as defined in ISO 15638-6.
9.9 Quality monitoring station
The availability of quality monitoring stations shall be as defined in ISO 15638-6.
9.10 Audits
Audits shall be as defined in ISO 15638-6.
9.11 Data access control policy
To protect the data and information held by the application service provider (4.7), each provider shall
adopt a risk based data access control policy for employees of the provider.
9.12 Approval of IVSs and service providers
Generic provisions for the approval (4.9) of IVSs and service providers (4.44) shall be as specified in
ISO 15638-3. Detailed provisions for specific regulated applications (4.38) shall be as specified by the
regime of the jurisdiction (4.32).
10 Vehicle access control (VAC)
10.1 TARV VAC service description and scope — VAC use cases
10.1.1 Jurisdiction — Safety enhancement
Jurisdictions (4.32) define controlled zones (4.19) by issuing specific access (4.1) policies in order to
enhance the level of road safety in special situations by preserving the traffic efficiency and respecting
the environment. Controlled zones might be special inner city areas (e.g. urban pedestrian areas,
school, and hospital surroundings, …), freight villages, ports, road sensitivity infrastructure (bridges,
tunnels, …)., weight restricted areas, width restricted areas, areas where there has been an accident
or incident, or zones and roadways where regulated vehicles (4.40) have to pay levies for access, etc.
or temporary zones created to protect VIP movement (movement of president, senior ministers, a
public gathering/procession etc.). Public authorities are normally required to publish the access rules
and the restriction policy. ‘Vehicle access control’ (VAC) (4.50) is a specialized use case of ‘vehicle access
management’ (VAM) (4.51), where the ‘Controlled Zone Manager’ (CZM) has the right/ability to permit or
refuse entry of a regulated vehicle to a defined controlled zone.
10.1.2 Controlled zone managers — Access control monitoring and management
In the VAC (4.50) use case, controlled zone (4.19) managers (CZM) [who may be an organ of a jurisdiction
(4.32), local authority or licensed/contracted operator (4.36)] have the ability to grant or prevent access
(4.1) of regulated vehicles (4.40) according to some stipulated criteria (such as type, size, weight, status,
12 © ISO 2014 – All rights reserved

condition, payment of fees, etc.). They may also solicit and obtain data from the regulated vehicle (4.40)
when approaching, when within or when leaving the controlled zone.
10.1.3 Vehicle operators — Access control monitoring and management
Vehicle operators (4.36) may be required
...