ISO/TS 17419:2014

TECHNICAL ISO/TS
SPECIFICATION 17419
First edition
2014-04-15
Intelligent transport systems —
Cooperative systems — Classification
and management of ITS applications
in a global context
Systèmes intelligents de transport — Classification et gestion des
applications de systèmes intelligents de transport dans un contexte
global
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 copyright@iso.org
Web www.iso.org
Published in Switzerland
ii © ISO 2014 – All rights reserved

Contents Page
Foreword .iv
Introduction .v
1 Scope . 1
2 Normative references . 1
3 Terms and definitions . 1
4 Abbreviated terms . 4
5 Application management . 5
5.1 Introduction . 5
5.2 ITS communications architecture . 6
5.3 PKI architecture . 7
5.4 Regulations and policies . 7
5.5 ITS station . 7
5.6 Applications and messages . 9
5.7 Communications .10
5.8 Identifiers and addresses summary .11
6 GCMA organizational framework .12
6.1 Overview .12
6.2 Registration of globally unique identifiers .13
6.3 Certification of ITS-S equipment .14
6.4 Certification of ITS-S application processes .15
6.5 Issuance of ITS-SCU certificates .16
6.6 Issuance of certificates for real-time operation .17
6.7 ITS application repository . .17
6.8 Secure installation and maintenance of facilities and communication protocols.18
6.9 Registries .18
6.10 Wrong behaviour reporting .23
7 GCMA technical framework .23
7.1 Addresses and identifiers .23
7.2 Online management .27
Annex A (normative) ASN.1 modules .29
Bibliography .39
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. 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. 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
ISO/TS 17419 was prepared by the European Committee for Standardization (CEN) Technical Committee
CEN/TC 278, Intelligent transport systems, in collaboration with ISO Technical Committee ISO/TC 204,
Intelligent transport systems, in accordance with the Agreement on technical cooperation between ISO
and CEN (Vienna Agreement).
iv © ISO 2014 – All rights reserved

Introduction
Classification and management of ITS applications in a global context covers more than just the ITS
applications themselves. It also covers elements of the environment in which ITS applications are
instantiated.
Intelligent Transport Systems (ITS) provide ITS services to users by execution of ITS applications which
typically requires communications between ITS station application processes residing in ITS station
units (ITS-SU). Communications includes exchange of messages dedicated to ITS applications, and
exchange of messages from ITS message sets.
ITS applications and ITS application classes are referred to as ITS application objects. ITS application
objects are uniquely identified by the registered “ITS Application Identifier” (ITS-AID) specified in this
Technical Specification.
NOTE An ITS application class groups ITS applications together that provide the same type of service,
e.g. “Electronic Fee Collection” (EFC), but operate in different contexts. The definition of ITS application
classes is based on the concept of the DSRC Application entity as introduced in Reference [4], which is
identified by a DSRCApplicationEntityID.
In Reference [17] ITS message sets were referred to as ITS application objects. This definition is not
adopted in this Technical Specification due to the fundamentally different nature of ITS message sets
and ITS application objects. ITS message sets are uniquely identified by the registered “ITS Message Set
Identifier” (ITS-MsgSetID) specified in this Technical Specification.
This Technical Specification is an extension towards more general and global applicability of Reference
[17]. This Technical Specification introduces the term “ITS-S object” as a general reference to ITS
application objects, ITS message sets and other objects that may require globally unique identification
and registration.
NOTE Examples of other ITS-S objects are ITS-S communication protocols and ITS-S security protocols.
[6][7][8][9]
Management of ITS-S objects is specified in the ISO 24102 series of International Standards
[10][11]
and in the Technical specification ISO/TS 17423. This Technical Specification focuses on some
management aspects related to authorized and controlled operation of ITS-S objects which requires
considerations of ITS-S object identifiers, i.e. ITS-AID, ITS-MsgSetID, ITS-SUID, ITS-SCUID, addresses
and protocol identifiers used in the communication protocol stack of an ITS-S, and others.
TECHNICAL SPECIFICATION ISO/TS 17419:2014(E)
Intelligent transport systems — Cooperative systems —
Classification and management of ITS applications in a
global context
1 Scope
This Technical Specification illustrates and specifies “Global Classification and Management of ITS
Applications” (GCMA). It
— is based on the ITS station and communication architecture described in ISO 21217,
— describes and specifies globally unique addresses and identifiers (ITS-S object identifiers) which
are both internal and external to ITS stations and are used for ITS station management,
— describes how ITS-S object identifiers and related technical parameters are used for classification,
registration and management of ITS applications and ITS application classes,
— describes how ITS-S object identifiers are used in the ITS communication protocol stack,
— introduces an organizational framework for registration and management of ITS-S objects, and
— defines and specifies management procedures at a high functional level.
2 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/TS 17423, Intelligent transport systems — Cooperative systems — ITS application requirements and
objectives for selection of communication profiles
ISO 21217, Intelligent transport systems — Communications access for land mobiles (CALM) — Architecture
ISO/IEC 8825-2:2008, Information technology — ASN.1 encoding rules: Specification of Packed Encoding
Rules (PER) — Part 2
3 Terms and definitions
For the purposes of this document, the terms and definitions given in ISO 21217 and the following apply.
3.1
authorization
prescription that a particular behaviour shall not be prevented
Note 1 to entry: Unlike permission (3.22), an authorization is an empowerment.
3.2
ITS application
instantiation of an ITS service that involves an association of two or more complementary ITS-S
application processes
3.3
ITS application class
group of ITS applications (3.2) that provide the same type of service, e.g. Electronic Fee Collection (EFC),
where each application operates in a different context
3.4
ITS application identifier
ITS-AID
globally unique, registered number identifying an ITS application object (3.5)
3.5
ITS application object
ITS application (3.2) or ITS application class (3.3) identified by a globally unique ITS application identifier
(3.4)
3.6
ITS message
message designed for an ITS-related purpose
3.7
ITS message set
set of uniquely identified ITS messages
3.8
ITS message set identifier
globally unique, registered number identifying an ITS message set (3.7)
3.9
ITS registration authority
entity authorized to register ITS-S object (3.17) identifiers
3.10
ITS service
functionality provided to users of intelligent transport systems designed, e.g. to increase safety,
sustainability, efficiency, and comfort
3.11
ITS trusted authority
entity authorized to issue ITS-S object (3.17) security credentials
3.12
ITS-S application process
element in an ITS station that performs information processing for a particular application and uses
ITS-S services to transmit and receive information
3.13
ITS-S application process provisioner
functionality in an ITS-SU offering ITS-S application processes (3.12) for download and installation to
other ITS-SUs
3.14
ITS-S communication protocol
protocol used in a communication protocol stack of an ITS-S
3.15
ITS-S communication protocol stack
set of ITS-S communication protocols, which may be identified by a registered globally unique reference
number, enabling communications between an ITS-SCU and other nodes
2 © ISO 2014 – All rights reserved

3.16
ITS-SCU configuration management centre
entity that retains information about capabilities of ITS-SCUs, status of objects in ITS-SCUs, and supports
management and update of this information
3.17
ITS-S object
entity used in ITS that may require a globally unique identifier
EXAMPLE ITS-SU, ITS-SCU, ITS application object, ITS message set, ITS-S communication protocol, ITS flow
type.
3.18
ITS-S object identifier
identifier of an ITS-S object (3.17)
3.19
ITS-S object owner
entity responsible for the specification (design), maintenance and registration of an ITS-S object (3.17)
3.20
ITS-S service
communication functionality of an ITS-S that provides the capability to connect to other nodes
3.21
ITS-S unit
implementation of an ITS station
3.22
permission
rule that a particular behaviour is allowed to occur
3.23
policy
set of rules related to a particular purpose, expressed as an obligation, an authorization (3.1), permission
(3.22) or a prohibition (3.24)
3.24
prohibition
prescription that a particular behaviour shall not occur
3.25
registration
assignment of an unambiguous name to an object in a way which makes the assignment available to
interested parties
3.26
registration authority
entity such as an organization or an automated facility that performs registration (3.25) of one or more
types of objects
3.27
regulation
written instrument containing rules having the force of law
3.28
regulation
process of the promulgation, monitoring, and enforcement of rules defined in regulation
(3.27), established by primary and/or delegated legislation
3.29
regulator
agency responsible for exercising autonomous authority over some area of human activity
3.30
violation
behaviour contrary to a rule
4 Abbreviated terms
ARCP Application Requirements for selection of Communication Profiles
BSMD Bounded Secured Managed Domain
CEN Commission Européenne de Normalisation
C-ITS Cooperative Intelligent Transport Systems
ETSI European Telecommunications Standards Institute
GCMA Global Classification and Management of ITS Applications
IANA Internet Assigned Numbers Authority
IEEE Institute of Electrical and Electronics Engineers
IETF Internet Engineering Task Force
ISO International Standards Organisation
ITS Intelligent Transport Systems
ITS-AID ITS Application Identifier
ITS-AOOID Application Object Owner (designer) Identifier
ITS-FlowTypeID ITS Flow Type Identifier
ITS-LCH ITS Logical Channel
ITS-LCHID ITS Logical Channel Identifier
ITS-MsgSetID ITS Message Set Identifier
ITS-MSOID Message Set Owner Identifier
ITS-NTSDU ITS Station Networking & Transport layer Service Data Unit
ITS-PN ITS Port Number
ITS-PR ITS policy region
ITS-PRID ITS-PR Identifier
ITS-RR ITS Regulatory Region
ITS-RRID ITS Regulatory Region Identifier
ITS-S ITS Station
ITS-S-APDID ITS-S Application Process Developer Identifier
4 © ISO 2014 – All rights reserved

ITS-S-APP ITS-S Application Process Provisioner
ITS-S-APPID ITS-S Application Process Provider Identifier
ITS-S-CPID ITS-S communication profile Identifier
ITS-SCU ITS Station Communication Unit
ITS-SCU-CMC ITS-SCU Configuration Management Centre
ITS-SCU-CMCID ITS-SCU-CMD Identifier
ITS-SCUID ITS-SCU Identifier
ITS-SecAlgID ITS Security Algorithm Identifier
ITS-SEMID ITS Station Equipment Manufacturer Identifier
ITS-S-FSID ITS-S Facilities layer Service Identifier
ITS-SU ITS Station Unit
ITS-SUID ITS-SU Identifier
ITS-SU-UID ITS-SU User Identifier
LDM Local dynamic map
5 Application management
This is an informative clause.
5.1 Introduction
In this Technical Specification, application management refers to objects and procedures, both internal
and external to the platforms on which the applications are installed, that are used to ensure the efficacy
and authenticity of these applications and these platforms. Platforms in this context are ITS station
1)
communication units (ITS-SCUs) and applications are ITS-S application processes as specified in
ISO 21217. Distinction is made between authorized applications and permitted applications. Application
management procedures involve protocols for exchanging information between the various entities
involved in application management, and these procedures are described at a functional level in this
Technical Specification. These procedures are to be used for authorizing and authenticating the use of
ITS-S application entities over communication networks. The architecture of this network described in
ISO 21217 and in 5.2.
Entities related to ITS application management in the global context and their roles identified and / or
specified in this Technical Specification are listed in Table 1.
Table 1 — Entities and their roles
Entity Role
ITS-S object Entity used in ITS related to ITS-S management that may be identified by a glob-
ally unique identifier.
EXAMPLE ITS application objects, ITS message sets, ITS-S communication
protocols, ITS-S units, ITS-S communication units.
1) An ITS-SU may consist of several physical units called ITS-SCUs as specified in ISO 21217.
Table 1 (continued)
Entity Role
ITS-S object owner Entity which is responsible for the specification (design), maintenance and regis-
tration of ITS-S objects
EXAMPLE Standards development organizations, industry special interest
groups such as the “Society of Automotive Engineers” (SAE).
ITS application object Entity that provides an ITS service to the user as specified in ISO 21217.
EXAMPLE ITS applications and ITS application classes.
ITS message set Set of ITS messages designed for an ITS-related purpose as specified in
ISO 21217.
ITS-S communication pro- Protocol used in a communication protocol stack of an ITS-S
tocol
ITS-S unit (ITS-SU) Physical instantiation of an ITS station specified in ISO 21217. An ITS-SU may
consist of one single ITS-SCU, or several ITS-SCUs interconnected via an ITS sta-
tion internal network. An ITS-SU is also referred to as “Bounded Secured Man-
aged Entity” as specified in ISO 21217.
ITS-S communication unit Physical unit in an ITS-SU containing a part or all of the functionality of an ITS-S
(ITS-SCU) as specified in ISO 21217.
ITS-S equipment manufac- Manufacturer of ITS-SUs or ITS-SCUs.
turer
ITS-S application process Developer (manufacturer) of ITS-S application processes for usage in ITS-SUs.
developer
ITS-S application process Entity that offers ITS-S application processes for download to an ITS-SCU.
provisioner
ITS-SCU configuration man- Entity that retains information about the capabilities of ITS-SUs, status of objects
agement centre in ITS-SUs, and supports management and update of this information.
Certification authority (Cer- Entity in charge of checking ITS-SCUs, implementations of ITS-S communication
tification laboratory) protocols, and ITS-S application processes for compliance to standards or speci-
fications defined in an ITS release.
ITS registration authority Entity in charge of registering ITS-S objects referenced by globally unique identi-
fiers.
ITS trusted authority Entity in charge of providing ITS-S object security credentials such as keys and
certificates for hardware and software.
5.2 ITS communications architecture
As illustrated in Figure 1, regardless of the complexity of the networks employed, communication between
“ITS station units” (ITS-SUs), and between ITS-SUs and other types of ITS communication nodes, is on a
peer-to-peer basis. The distinguishing feature of ITS-SUs is that of trust and authentication as discussed
in 5.5.1. The need for trust and authentication arises from the deployment of critical safety-of-life and
property applications. This leads to the definition of an ITS station as a “Bounded Secured Managed
Domain” (BSMD) as specified in ISO 21217, and the requirement for a “Public Key Infrastructure” (PKI)
for trust assertion and certificate management.
6 © ISO 2014 – All rights reserved

Figure 1 — Simplified ITS peer-to-peer communication architecture
5.3 PKI architecture
A public-key infrastructure (PKI) is a system for the creation, storage, distribution and revocation of
digital certificates which are used to verify that a particular public key and associated rights belong to
a certain entity. A PKI creates digital certificates which map public keys to entities and their rights. It
securely stores these certificates in a central repository and revokes them if needed.
5.4 Regulations and policies
Application management procedures must comply with applicable regulation and use applicable policies.
A policy is a set of rules related to a particular purpose. Such a rule can be expressed as an obligation, an
authorization, a permission, or a prohibition. A regulation is an enforceable policy. Regulations apply to
a specific regulatory domain and are produced and maintained by regulators. Policies apply to a specific
policy domain.
The need and applicability for regulations and policies in ITS is identified in this Technical Specification
for the following purposes:
— radio frequency allocation and usage;
— privacy issues;
— road traffic circulation;
— communication networks.
A regulatory region is uniquely identified by an ITS Regulatory Region Identifier ITS-RRID.
A policy region is uniquely identified by an ITS Policy Region Identifier ITS-PRID.
5.5 ITS station
5.5.1 ITS station architecture
The architecture of the ITS station (ITS-S) specified in ISO 21217 is illustrated in Figure 2.
Figure 2 — ITS station architecture (from ISO 21217)
The term ITS-S refers to functionalities rather than a physical unit. Six functional blocks of an ITS-S are
distinguished in Figure 2:
Applications
— ITS-S applications
Communications
— Data plane
— “Access”: ITS-S access layer, i.e. OSI layers one and two.
— “Networking & Transport”: ITS-S networking & transport layer, i.e. OSI layers three and four.
— “Facilities”: ITS-S facilities layer, i.e. OSI layers five, six and seven.
— Management entity
— “Management”: ITS-S management entity
8 © ISO 2014 – All rights reserved

— “Security”: ITS-S security entity
These entities are assumed to interact with each other within a “Bounded Secured Managed Domain”
(BSMD). Implementation and maintenance of these entities in a standard compliant manner creates ITS-S
objects, ITS-SUs and ITS-SCUs that can be trusted to operate according to the policies and procedures
assigned to them by trusted authorities. It is precisely the attribute of trust within the ITS domain
that distinguishes ITS-SUs (Bounded Secured Managed Entities, BSMEs) from all other communication
nodes. As a managed domain, elements of the ITS-S need to be aware of and interact with the ITS-S
management entity. As a secured domain, installation (e.g. “plug-and-play”) of an element of an ITS-S
such as an ITS-S application, communication interface, or a communication protocol must be performed
in a controlled and secure manner, applying the procedures for registration of identifiers of ITS-S objects
and the authentication of registered elements at time of installation.
ITS-S applications interact with the “Communications” block via an “Application Programming Interface”
(API). This interaction may address either protocols in the ITS-S facilities layer of the data plane, or
protocols in the ITS-S management entity or ITS-S security entity.
ITS-S access and ITS-S networking & transport layers are used by ITS-S facilities layer services and
ITS-S applications to transmit and receive ITS-NTSDUs as described in ISO 21217.
A specific combination of an ITS-S networking & transport layer protocol (residing in an instantiation of
the ITS-S networking & transport layer), a “Communication Interface” (CI) (residing in an instantiation
of the ITS-S access layer), an ITS-S facilities layer protocols (optional) and related necessary management
and security protocols (optional) is referred to as an ITS-S communication protocol stack specified in
ISO/TS 17423. An ITS-S communication profile, which is a parameterized ITS-S communication protocol
[11]
stack specified in ISO/TS 17423 is associated with a communication path. An ITS-S application
process may use more than one ITS-S communication profile, e.g. one ITS-S communication profile for
each of its distinct communication sources (flows). Further details on the automatic selection of ITS-S
communication profiles are found in ISO/TS 17423.
5.5.2 Instantiations of an ITS station
The functionality of an ITS-S may be implemented in one or more “ITS-S Communication Units”
(ITS-SCU) as explained in ISO 21217. For example, an ITS-S can be implemented by connecting units
containing ITS-S router functionality and ITS-S host functionality using a local network (called an ITS
station-internal network). An implementation of an ITS station is referred to as an “ITS-S unit” (ITS-SU).
An ITS-SU is uniquely identified by an ITS-SUID. An ITS-SCU is uniquely identified by an ITS-SCUID. An
ITS-SU comprised of more than one ITS-SCU has a master ITS-SCU. The ITS-SUID is derived from the
ITS-SCUID of the master ITS-SCU as specified in 7.1.7.
An ITS-SCU is assigned to one “ITS-SCU Configuration Management Centre” (ITS-SCU-CMC). The purpose
of the ITS-SCU-CMC is to manage the configuration of ITS-SCUs. Related ITS-S remote management
procedures are specified in Reference [7].
5.5.3 Owners and users of an ITS station
For lawful intercept, it may be necessary to uniquely identify the owner (user) of an ITS-SU. The identifier
assigned to an owner is stored in the ITS-SU-UID data object. Procedures for unique assignment and
usage of ITS-SU-UIDs are outside the scope of this Technical Specification.
5.6 Applications and messages
5.6.1 ITS application
An ITS application is an instantiation of an ITS service that involves an association of two or more
complementary ITS-S application processes as defined in ISO 21217. ITS-S application processes may
perform information dissemination by implementing groupcast (broadcast or multicast) services, or by
exchange of packets with peer ITS-S application processes as part of a communication session.
An ITS application is identified by a globally unique “ITS Application Identifier” (ITS-AID) as specified in
this Technical Specification. ITS-AIDs are assigned by a Registration Authority.
An essential feature of the ITS-S reference architecture is that ITS-S application processes need not
necessarily concern themselves with the underlying communication protocols. They only need to be
able to inform the ITS-S management of their functional requirements for communications as described
in ISO/TS 17423.
5.6.2 ITS application class
The concept of an ITS application class (cf. DSRCApplicationEntity) as introduced in Reference [4] is
based on identifying a set of different protocols that serve the same functional purpose, e.g. Electronic
Fee Collection (EFC).
An ITS application class is identified by an ITS-AID, see 5.6.1. The various protocols inside an ITS
application class are distinguished by a context which can be identified by a context identifier. Usage of
ITS application classes in service advertisements is specified in Reference [10].
NOTE The term ITS application class is introduced in this Technical Specification primarily for compatibility
[4]
with legacy systems .
5.6.3 ITS message sets
An ITS message set is a collection of ITS messages associated with an entity that is responsible for
maintenance of the set.
NOTE The term “ITS message set” is herein synonymous with the term “ITS data dictionary”.
Transmission and reception of messages from an ITS-S message set may be performed by ITS-S
application processes, e.g. ITS-S applications, ITS-S facility applications.
Messages from ITS message sets may be processed in the ITS-S facilities layer for the purpose of
dissemination as specified in References [2] and [3].
An ITS message set is identified by a globally unique “ITS Message Set Identifier” (ITS-MsgSetID)
specified in this Technical Specification. ITS-MsgSetIDs are assigned by a registration authority.
5.7 Communications
5.7.1 Addressing in the communication protocol stack
Packets (network layer data units) exchanged between ITS-SUs need to carry information on the source
and the destination (end points) of these packets above the ITS-S networking & transport layer, i.e. in
the ITS-S facilities layer. This address information applies at the NF-SAP in Figure 2. The well-known
concept of port numbers is used for this purpose.
NOTE Typically port numbers are dedicated to a specific transport protocol, i.e. the same number may have
different meanings in different transport protocols. Port numbers for ITS transport protocols such as FNTP are
referred to as “ITS Port Numbers” (ITS-PN).
Source and destination end points may be either globally unique, well-known ITS-PNs as specified in
this Technical Specification, or dynamically assigned ITS-PNs.
While globally unique transport protocol identifiers, network protocol identifiers, network addresses,
data link layer protocol identifiers are essential ITS communications, they are outside the scope of this
Technical Specification. Examples of such identifiers are given in Table 2.
10 © ISO 2014 – All rights reserved

Table 2 — Addresses and identifiers in communication protocols
Identifier or address Purpose
Facility layer service Registered identifiers for ITS-S facility layer services as specified in Reference [2].
identifier
IPv6 prefix ITS-SUs contain routers that may get a global IPv6 prefix that uniquely identifies the
router (and the station-internal network behind such a router) in the Internet.
IPv6 addresses ITS-SCUs (hosts and routers) may get globally unique IPv6 addresses that uniquely
identify them in the Internet.
[15]
DSAP/SSAP addresses DSAP / SSAP addresses are specified in IEEE 802.2. These are used to select upper
layer protocols.
Ethertype identifiers Ethertype identifiers are specified for usage in the length/type field specified in
[16]
IEEE 802.3. They are used to select upper layer (networking) protocols.
[14]
MAC addresses MAC addresses are specified in IEEE 802 and are comprised of a global and local
sub-space. The global sub-space uniquely identifies a communication interface.
5.7.2 ITS-S management
Although the ITS-S management entity is located inside the block “Communications” in Figure 2, it also
[8]
manages ITS-S applications residing in the block “Applications” via MX-SAP service primitives.
The set of ITS-S application functional communication requirements and procedures for expressing
them to the ITS-S management are described in ISO/TS 17423.
5.7.3 ITS-S Security
The ITS-S security entity provides “atomic” security services to the ITS-S. Although functions of the SX-
[8]
SAP service primitives are generally specified in various standards, detailed mechanisms necessary
to achieve security and trust are implementation dependent.
5.8 Identifiers and addresses summary
Table 3 illustrates globally unique addresses and identifiers relevant for ITS for which a registry is
required. Details of these identifiers and addresses are specified in 7.1.
Table 3 — Addresses, identifiers and registries
Address / identifier Purpose
ITS-AID An ITS application identifier is used to uniquely identify an ITS application or an
ITS application class. It is used to advertise services (cf. the service advertisement
specified in Reference [10]), and for secure installation and real-time operation of
ITS-S applications in an ITS-SU. ITS-S applications have an ITS-AID assigned to them
prior to installation in an ITS-SU.
ITS-AOOID An ITS application object owner identifier is used to uniquely identify an owner of
specifications of ITS application objects.
ITS-FlowTypeID An ITS-FlowTypeID is used to uniquely identify an ITS flow type.
An ITS flow type is a set of communication requirements and objectives specified
[11]
in ISO/TS 17423 and used by the ITS-S management to select an optimum ITS-S
communication profile.
ITS-LCHID An ITS logical channel identifier is used to uniquely identify an ITS logical channel
in the ITS-S communication profile selection process specified in ISO/TS 17423.
Table 3 (continued)
Address / identifier Purpose
ITS-MsgSetID An ITS message set identifier is used to uniquely identify an ITS message set.
ITS-S applications may construct PDUs using messages from any registered ITS
message set, and may also consume such messages through publish/subscribe
[ ]
mechanisms in ITS-SUs 2 .
ITS-MSOID An ITS message set owner identifier is used to uniquely identify an owner of specifi-
cations of ITS message sets.
ITS-PN An ITS port number is used in an ITS-SCU to uniquely identify for a given transport
[12]
protocol such as FNTP, an entity or protocol in the ITS-S facilities layer.
ITS-PRID An ITS policy region identifier is used to uniquely identify an ITS policy region (ITS-
PR) in the ITS-S communication profile selection process specified in ISO/TS 17423.
Different types of policy regions may be distinguished.
ITS-RRID An ITS regulatory region identifier is used to uniquely identify an ITS regulatory
region (ITS-RR) in the ITS-S communication profile selection process specified in
ISO/TS 17423. The following types of regulatory regions are identified:
— radio regulation
— security regulation
— privacy regulation
— traffic regulation
ITS-S-APDID An ITS-S application process developer identifier is used to uniquely identify a
developer of ITS-S application processes.
ITS-S-APPID An ITS-S application process provisioner identifier is used to uniquely identify an
ITS-S-APP.
ITS-S-CPID An ITS-S communication profile identifier is used to uniquely identify a defined
ITS-S communication protocol stack. It is used in the ITS-S communication profile
selection process specified in ISO/TS 17423
ITS-SCUID An ITS station communication unit identifier is used to uniquely identify an ITS-
SCU.
ITS-SecAlgID A security algorithm identifier is used to uniquely identify a security algorithm in
communications.
ITS-SEMID An ITS-S equipment manufacturer identifier is used to uniquely identify a manufac-
turer of ITS equipment.
ITS-SUID An ITS station unit identifier is used to uniquely identify an ITS-SU.
ITS-SU-UID A globally unique identifier of a user of an ITS-SU. Usage of this identifier is outside
the scope of this Technical Specification.
ITS-SCU-CMCID A globally unique identifier of a user of an ITS-SCU-CMC. Usage of this identifier is
specified in Reference [7].
6 GCMA organizational framework
6.1 Overview
The organizational framework of “Global Classification and Management of ITS Applications” (GCMA)
involves a number of entities listed in Table 1and the relationships between these entities. The purpose
of this framework is to allow for certification and validation of entities uniquely identified by identifiers
and addresses, and to enable operation of ITS-S application processes in an ITS-SCU based on the
principles of a “Bounded Secured Managed Domain” (BSMD) as specified in ISO 21217. This framework
provides the means to instantiate the following services:
a) Registration of globally unique identifiers presented in Table 3 as illustrated in 6.2.
12 © ISO 2014 – All rights reserved

b) Certification of ITS-S equipment, i.e. ITS-SUs and ITS-SCUs, and issuance of certificates as illustrated
in 6.3.
2)
c) Certification of ITS-S application processes as illustrated in 6.4.
d) Issuance of certificates for real-time operation of ITS-S applications as illustrated in 6.5.
e) Installation of ITS-S application processes in an ITS-SCU as illustrated in 6.7.
6.2 Registration of globally unique identifiers
Figure 3 shows entities and functional relationships involved in the registration of ITS application
objects and their identifiers (ITS-AIDs and optionally port numbers (ITS-PNs)).
NOTE The numbers (x) in Figure 3 indicate the logical sequence of actions.
Figure 3 — Registration of ITS-AID — Functional illustration
Owners (designers) of ITS applications (and ITS application classes) are uniquely identified by an ITS-
AOOID, and all ITS application objects (ITS applications or ITS application classes) are uniquely identified
by an ITS-AID. All ITS applications shall be evaluated by an “Application evaluation authority” prior
to the issuance of an ITS-AID. Upon acceptance, the application evaluation authority shall notify the
registration authority which shall register an ITS-AID with the ITS application owner as the responsible
entity.
Figure 4 shows entities and functional relationships involved in the registration of ITS message sets and
their identifiers (ITS-MsgSetIDs).
NOTE The numbers (x) in Figure 4 indicate the logical sequence of actions.
2) While necessary to ensure proper ITS-SU operation,certification of ITS communication protocols is outside the
scope of this Technical Specification.
Figure 4 — Registration of ITS-MsgSet-ID — Functional illustration
Owners of ITS message sets are uniquely identified by an ITS-MSOID, and ITS message sets themselves
are uniquely identified by an ITS-MsgSetID. Owners of ITS message sets are strongly encouraged to
submit their message sets to an appropriate ITS message set harmonization body, e.g. a standards
development organisation, to prevent unnecessary duplication and possible conflict in the definition
of ITS messages and data objects related thereto. While appropriate incorporation of the suggestions
returned by the harmonization body is also strongly encouraged, all valid requests for an ITS-MsgSetID
made to an appropriate registration authority shall be granted and an ITS-MsgSetID assigned. The ITS
message set owner shall be registered initially as the party responsible for maintenance of the message
set. The registration authority shall be notified of any changes in the responsible party.
6.3 Certification of ITS-S equipment
Figure 5 shows entities and functional relationships involved in the certification and registration of ITS-
SCUs sets and their identifiers (ITS-SCUIDs).
NOTE The numbers (x) in Figure 5 indicate the logical sequence of actions.
14 © ISO 2014 – All rights reserved

Figure 5 — Certification of ITS-SCUs — Functional illustration
ITS-SCUIDs shall be created by the manufacturer of the device as a concatenation of the globally unique
ITS equipment manufacturer ID (ITS-SEMID) and a unique serial number assigned by that manufacturer
as specified in this Technical Specification. The registration authority is notified of such assignments
by the equipment manufacturer. Once the devices passes all conformance tests as prescribed by the
certification laboratory, a trusted authority, which may be the certification laboratory itself, issues
the requested security credentials (certificates and/or key pairs) and shall notify the appropriate
registration authority of the issuance thereof.
An ITS-SU may be composed of one or several ITS-SCUs. ITS-SCUs may become part of an ITS-SU either
at time of integration of an ITS-SU, or dynamically as a plug-and-play device. One of the several (or the
only one) ITS-SCU of an ITS-SU is referred to as the “Master ITS-SCU”. While ITS-SCUs have a globally
unique identifier (ITS-SCUID) assigned under the control of the manufacturer of the ITS-SCU, a globally
unique identifier (ITS-SUID) of an ITS-SU needs to be assigned by a registration authority. The ITS-SUID
is the concatenation of a registered unique serial number with the ITS-SCUID of the “Master ITS-SCU”.
6.4 Certi
...