ISO 24102-2:2015

Intelligent transport systems — Communications access for land mobiles (CALM) — ITS station management — Part 2: Remote management of ITS-SCUs

ISO 24102-2:2015 provides specifications for Intelligent Transport Systems (ITS) station management to be compliant with the ITS station reference architecture and the set of related standards from ISO/TC 204. Remote ITS station management is specified by means of protocol data units (PDUs) and procedures of the "Remote ITS Station Management Protocol" (RSMP) related to managed objects in an ITS station unit. Distinction is made between managed ITS station units (management clients) and managing remote ITS station units (management servers).

Systèmes intelligents de transport — Accès aux communications des services mobiles terrestres (CALM) — Gestion de la station ITS — Partie 2: Gestion à distance des SCUs-ITS

General Information

• Status: Withdrawn
• Publication Date: 18-Nov-2015
• Withdrawal Date: 18-Nov-2015
• ICS: 03.220.01 - Transport in general
• ICS: 35.240.60 - IT applications in transport
• Technical Committee: ISO/TC 204 - Intelligent transport systems
• Drafting Committee: ISO/TC 204/WG 16 - Communications
• Current Stage: 9599 - Withdrawal of International Standard
• Completion Date: 31-Oct-2018

Relations

• Revised: ISO 24102-2:2018 - Intelligent transport systems — ITS station management — Part 2: Remote management of ITS-SCUs
• Effective Date: 04-Feb-2017
• Revises: ISO 24102:2010 - Intelligent transport systems — Communications access for land mobiles (CALM) — Management
• Effective Date: 23-Feb-2012

Standards Content (Sample)

INTERNATIONAL ISO
STANDARD 24102-2
First edition
2015-12-01
Intelligent transport systems —
Communications access for land
mobiles (CALM) — ITS station
management —
Part 2:
Remote management of ITS-SCUs
Systèmes intelligents de transport — Accès aux communications des
services mobiles terrestres (CALM) — Gestion de la station ITS —
Partie 2: Gestion à distance des SCUs-ITS
Reference number
ISO 24102-2:2015(E)
©
ISO 2015

---------------------- Page: 1 ----------------------
ISO 24102-2:2015(E)

COPYRIGHT PROTECTED DOCUMENT
© ISO 2015, Published in Switzerland
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
Ch. de Blandonnet 8 • CP 401
CH-1214 Vernier, Geneva, Switzerland
Tel. [phone]
Fax [phone]
[e-mail]
www.iso.org
ii © ISO 2015 – All rights reserved

---------------------- Page: 2 ----------------------
ISO 24102-2:2015(E)

Contents Page
Foreword .iv
Introduction .v
1 Scope . 1
2 Normative references . 1
3 Terms and definitions . 1
4 Symbols and abbreviated terms . 2
5 Requirements . 2
6 Remote management architecture . 3
6.1 Functionality . 3
6.2 ITS station architecture . 6
6.3 Distributed implementation of an ITS-S . 6
6.4 RMPE . 6
6.5 RMCH . 7
7 Remote management protocol data units . 8
8 Service primitive functions . 9
8.1 Generic service primitives . 9
8.2 MF-SAP service primitive functions . 9
8.2.1 Transmission request of RSMP-Request and RSMP-Response . 9
8.2.2 Notification of reception of RSMP-Request and RSMP-Response. 9
8.3 SF-SAP service primitive functions .10
8.3.1 Security procedure applied to RSMP-Request and RSMP-Response .10
8.3.2 Security procedure applied to RMCH-Request and RSMP-Response .10
9 Remote management procedures.11
9.1 Remote management session initiation .11
9.1.1 Initiation by server.11
9.1.2 Initiation by client . .11
9.1.3 RSMP session identifier .11
9.1.4 RSMP session security .11
9.2 Remote management session closure .11
9.2.1 Active closure .11
9.2.2 Timeout .11
9.2.3 No active session .12
9.3 Firmware update .12
9.4 Maintenance of ITS-S protocols .12
9.5 Maintenance of ITS-S application processes .13
9.6 Maintenance of configuration information .14
10 Usage of FSAP .14
10.1 General .14
10.2 SAM .14
10.3 CTX .14
Annex A (normative) ASN.1 modules .15
Annex B (informative) Communication service parameters .23
Bibliography .24
© ISO 2015 – All rights reserved iii

---------------------- Page: 3 ----------------------
ISO 24102-2:2015(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.
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, together with ISO 24102-1, ISO 24102-3, ISO 24102-4, ISO 24102-5 and ISO 24102-6,
cancels and replaces ISO 24102:2010, which has been technically revised.
ISO 24102 consists of the following parts, under the general title Intelligent transport systems —
Communications access for land mobiles (CALM) — ITS station management:
— Part 1: Local management
— Part 2: Remote management of ITS-SCUs
— Part 3: Service access points
— Part 4: Station-internal management communications
— Part 5: Fast service advertisement protocol (FSAP)
— Part 6: Path and flow management
iv © ISO 2015 – All rights reserved

---------------------- Page: 4 ----------------------
ISO 24102-2:2015(E)

Introduction
This part of ISO 24102 is part of a family of International Standards for communications access for land
mobiles (CALM). An introduction to the whole set of International Standards for Intelligent Transport
Systems (ITS) is provided in ISO 21217.
This part of ISO 24102 is the second part of a multipart International Standard which determines
remote management of an ITS station unit (ITS-SU) with the ITS station and communication
architecture specified in ISO 21217 and illustrated in Figure 1, and operated as a bounded secured
managed domain (BSME).
Remote ITS station management has the purpose of
— setting, updating, and deletion of configuration and operation information in an ITS station
communication units (ITS-SCU) of an ITS station unit (ITS-SU) specified in ISO 21217, e.g. information
on policies and regulations, security related information, accounting information, access layer
parameters (see Reference [1]),
— installation, update, and deinstallation of persistent information in an ITS-SCU, e.g. ITS-S application
processes specified in ISO 21217, ITS-S communication protocols, and
— notification and retrieval of management information, e.g. log files of events, alarms generated by
the ITS-SCU(s) of an ITS-SU.
By this, it covers the five management areas identified in ISO/IEC 7498-4.
Applications
API
Facilities
NF
Networking &
Transport
IN
Access
MS
Communications
Figure 1 — ITS station reference architecture
© ISO 2015 – All rights reserved v
Management
MI MN MF
SI SN SF
Security

---------------------- Page: 5 ----------------------
INTERNATIONAL STANDARD ISO 24102-2:2015(E)
Intelligent transport systems — Communications access
for land mobiles (CALM) — ITS station management —
Part 2:
Remote management of ITS-SCUs
1 Scope
This part of ISO 24102 provides specifications for Intelligent Transport Systems (ITS) station
management to be compliant with the ITS station reference architecture and the set of related
standards from ISO/TC 204.
Remote ITS station management is specified by means of protocol data units (PDUs) and procedures
of the “Remote ITS Station Management Protocol” (RSMP) related to managed objects in an ITS station
unit. Distinction is made between managed ITS station units (management clients) and managing
remote ITS station units (management servers).
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 21217, Intelligent transport systems — Communications access for land mobiles (CALM) — Architecture
ISO 24102-1, Intelligent transport systems — Communications access for land mobiles (CALM) — ITS
station management — Part 1: Local management
ISO 24102-3, Intelligent transport systems — Communications access for land mobiles (CALM) — ITS
station management — Part 3: Service access points
ISO 24102-4, Intelligent transport systems — Communications access for land mobiles (CALM) — ITS
station management — Part 4: Station-internal management communications
ISO/IEC 7498-4, Information processing systems — Open Systems Interconnection — Basic Reference
Model — Part 4: Management framework
ISO/IEC 8825-2, Information technology — ASN.1 encoding rules: Specification of Packed Encoding Rules
(PER)
3 Terms and definitions
For the purposes of this document, the terms and definitions given in ISO 21217, ISO 24102-1,
ISO 24102-3, ISO 24102-4, ISO/IEC 7498-4, and the following apply.
3.1
remote management client
ITS station communication unit in which remote ITS station management is performed by a remote
management server (3.2)
3.2
remote management server
entity performing remote ITS station management in an ITS station communication unit
© ISO 2015 – All rights reserved 1

---------------------- Page: 6 ----------------------
ISO 24102-2:2015(E)

4 Symbols and abbreviated terms
For the purposes of this document, the abbreviated terms given in ISO 21217, ISO 24102-1, ISO 24102-3,
ISO/IEC 7498-4, and the following apply.
BSME Bounded Secured Managed Entity (from ISO 21217)
IICP ITS station-Internal management Communications Protocol (from ISO 24102-4)
FSAP Fast Service Advertisement Protocol (from ISO 24102-5)
ITS Intelligent Transport Systems
ITS-SCU ITS Station Communication Unit (from ISO 21217)
ITS-SCU-CMC ITS-SCU Configuration Management Centre (from CEN/ISO/TS 17419)
ITS-SU ITS Station Unit (from ISO 21217)
RMC Remote Management Client
RMCH Remote Management Communication Handler
RMPE Remote Management Protocol Execution
RMS Remote Management Server
RSMP Remote ITS station Management Protocol
5 Requirements
The ITS station management entity shall provide the functionality specified in the various parts of this
multipart International Standard.
1) The functionality of local ITS station management specified in ISO 24102-1.
2) The functionality of remote ITS station management specified in this part of ISO 24102.
3) The functionality of management service access points specified in ISO 24102-3.
4) The functionality of ITS station-internal management communications specified in ISO 24102-4.
5) The functionality of the “Fast Service Advertisement Protocol” (FSAP) specified in ISO 24102-5.
6) The functionality of the path and flow management specified in ISO 24102-6.
Means to secure the access to management functionality need to be specified within the global context
of ITS security. Details are outside the scope of this part of ISO 24102.
Detailed mandatory requirements are specified in the following clauses of this part of ISO 24102.
— Clause 6 presents the remote management architecture.
— Clause 7 specifies remote management protocol data units.
— Clause 8 specifies service primitive functions.
— Clause 9 specifies remote management procedures.
— Clause 10 specifies details needed for the Fast Service Advertisement Protocol (FSAP).
— Annex A specifies the ASN.1 module for remote management.
2 © ISO 2015 – All rights reserved

---------------------- Page: 7 ----------------------
ISO 24102-2:2015(E)

— Annex B proposes settings of communication service parameters used for automatic selection of
communication profiles specified in CEN/ISO/TS 17423.
6 Remote management architecture
6.1 Functionality
The “Remote ITS Station Management Protocol” (RSMP) specified in this part of ISO 24102 has the
purpose of
— setting, updating, and deletion of configuration and operation information in an ITS station
communication unit (ITS-SCU) of an ITS station unit (ITS-SU) specified in ISO 21217, e.g. information
on policies and regulations (CEN/ISO/TS 17419), security related information, accounting
information, access layer parameters (see Reference [1]), etc.,
— installation, update, and deinstallation of persistent information in an ITS-SCU, e.g. ITS-S application
processes, ITS-S communication protocols, and
— notification and retrieval of management information, e.g. log files of events, alarms generated by
the ITS-SCU of an ITS-SU.
By this, it covers the five management areas identified in ISO/IEC 7498-4.
Remote ITS station management covers a set of management processes where ITS station units (ITS-
SU) acting as remote management servers (RMS) manage ITS station communication units (ITS-SCU)
of managed ITS-SUs acting as remote management clients (RMC).
An RMS is associated with an ITS-SCU configuration management centre identified in CEN/ISO/
TS 17419. An RMS may be implemented, e.g. in a roadside ITS sub-system or in a central ITS sub-system.
Remote ITS station management is applied to managed objects (according to ISO/IEC 7498-4) in remote
management sessions. Such sessions may be initiated
— by the RMS (server initiated session), e.g. by means of the Fast Service Advertisement Protocol
(FSAP) (see Reference [2]) or by direct IPv6 based access, or
— by the RMC (client initiated session), typically using IPv6 communications, as illustrated in Figure 2
(server initiated session using FSAP), in Figure 3 (direct server initiated session), and in Figure 4
(client initiated session).
The mechanisms specified in this part of ISO 24102 enable future specifications of remote management
features in separate standards or by means of registries.
© ISO 2015 – All rights reserved 3

---------------------- Page: 8 ----------------------
ISO 24102-2:2015(E)

RMS RMC
SAM(RSMP)
CTX(ITS-SCUinfo)
REQW (initiatesecuresession)
RES(confirmsecuresession)
REQW (managmentcommand)
RES(command confirmation,result)
.
.
.
REQW (close session)
RES(confirmend of session
Figure 2 — Server initiated session (example with FSAP)
SAM and CTX specified in Reference [2] with details specified in this part of ISO 24102 are used in
the example of Figure 2 to prepare for the secured management session. During the FSAP service
operation phase, first, a secure session is requested from the RMS which is acknowledged by the RMC.
After successful establishment of a session with mutual authentication of RMS and RMC with optional
agreement on encryption of the management data to be exchanged in the session, the RMS may send
out a sequence of management commands, each of which is acknowledged by the RMC providing also
optional result data. Finally, the RMS closes the session, which also is acknowledged by the RMC.
Subsequent to this, no more management data can be exchanged.
4 © ISO 2015 – All rights reserved
FSAP service FSAP service
operation initialization
phase phase
RSMP RSMP RSMP
closing operation initialization
phase phase phase

---------------------- Page: 9 ----------------------
ISO 24102-2:2015(E)

RMS RMC
REQW (initiatesecuresession)
RES(confirmsecuresession)
REQW (managmentcommand)
RES(command confirmation,result)
.
.
.
REQW (close session)
RES(confirmend of session
Figure 3 — Direct server initiated session
In the example of Figure 3, an RMS directly initiates a secure session with an RMC. After confirmation
of the secure session by the RMC, the RMS runs and closes the secure session as illustrated above for
the direct server initiated session.
RMS RMC
REQW (Requestasecuresession)
REQW (initiatesecuresession)
RES(confirmsecuresession)
REQW (managmentcommand)
RES(command confirmation,result)
.
.
.
REQW (close session)
RES(confirmend of session
Figure 4 — Client initiated session
© ISO 2015 – All rights reserved 5
RSMP RSMP RSMP
RSMP RSMP RSMP
closing operation initialization closing operation initialization
phase phase phase
phase phase phase

---------------------- Page: 10 ----------------------
ISO 24102-2:2015(E)

In the example of Figure 4, upon an event internal to an RMC, an RMC notifies the need for a secure
session to the RMS. Then the RMS initiates, runs, and closes the secure session.
6.2 ITS station architecture
The “Remote ITS-station Management Protocol” (RSMP) consists of two functional blocks, i.e.
— the ITS-S application process “Remote Management Protocol Execution” (RMPE) with a
registered ITS-AID, and
— the ITS-S facility “Remote Management Communication Handler” (RMCH) using a well-known
registered ITS port number PORT_RSM and dynamically assigned ITS port numbers (see
Reference [3]). The value of PORT_RSM is 32763.
The allocation of these functional blocks in the ITS station architecture specified in ISO 21217 is
presented in Figure 5. Globally, unique identifiers are specified in CEN/ISO/TS 17419.
Communications
ITS-SManagementEntity ITS-SFacilitiesLayer ITS-SSecurityEntity
Remote Management
CommunicationHandler
(RMCH)
NF-SAP
ITS-SNetworking&TransportLayer
ITS-SAccess Layer
CI Selection
Manager
Figure 5 — Functional blocks of RSMP
The RMCH is located in the ITS-S facilities layer.
The RMPE is located in the ITS-S management entity.
RMCH and RMPE are connected via the MF-SAP services MF-COMMAND and MF-REQUEST with service
primitive functions specified in Clause 8.
6.3 Distributed implementation of an ITS-S
The “Remote ITS-station Management Protocol” (RSMP) supports distributed implementations of ITS-S
roles identified in ISO 21217, i.e. several ITS-SCUs per ITS-SU. The RMCH thus may communicate via the
ITS station-internal network with an ITS-SCU providing the link to the peer ITS station unit. Details
depend on the ITS-S networking and transport layer protocol used and are outside the scope of this
part of ISO 24102.
6.4 RMPE
“Remote Management Protocol Execution” (RMPE) is an ITS-S application process located in the ITS-S
management entity. There are two distinct instantiations of the RMPE, i.e. the server instantiation and
6 © ISO 2015 – All rights reserved
Remote Management
Protocol Execution(RMPE)
MF-SAP
MI-SAP MN-SAP
SF-SAP
Security Support

---------------------- Page: 11 ----------------------
ISO 24102-2:2015(E)

the client instantiation. There is exactly one instantiation of RMPE in each ITS-SCU of an ITS-SU. The
RMPE cannot manage ITS-SCUs in which it is not instantiated.
NOTE For more information on ITS-S application processes, read ISO 21217.
Management activities include the following:
— updating firmware in the ITS-SCU;
— maintenance of ITS-S application processes;
— new installations;
— updates of existing installations;
— deletion of existing installations;
— maintenance of communication, management, and security protocols;
— new installations;
— updates of existing installations;
— deletion of existing installations;
— maintenance of configuration parameters;
— setting of parameter values and other information;
— retrieval of parameter values and other information, e.g. logfiles;
— maintenance of security related managed objects;
6.5 RMCH
The “Remote Management Communication Handler” (RMCH) is a communication facility located in the
ITS-S facilities layer. The RMCH
— receives service data units which contain “RMCH Protocol Data Units” (RMCH-PDUs) illustrated in
Figure 7 from peer ITS-SUs,
— exchanges RMPE-PDUs illustrated in Figure 7 with the RMPE via the MF-SAP,
— transmits RMCH-PDUs to peer ITS-SUs, and
— uses services from the ITS-S security entity via SF-SAP service primitives to authenticate peer ITS
station units, and to optionally encrypt and decrypt RMPE-PDUs.
The well-known ITS port PORT_RSM (see Reference [3]) is used by the following:
a) an RMS for transmission of a message
— as a source port number, and
— as a destination port number in case of direct session initiation, and only in the REQW (initiate
secure session) message shown in Figure 3. With the REQW (initiate secure session), an
RMS requests an RMC to use a specific dynamically-assigned port number for subsequent
communications.
b) an RMC for transmission of a message
— as a destination port number in case of direct session initiation, and only in the “notify need for
secure session” message shown in Figure 4.
© ISO 2015 – All rights reserved 7

---------------------- Page: 12 ----------------------
ISO 24102-2:2015(E)

Client instantiations use dynamically-assigned port numbers as source port number.
7 Remote management protocol data units
Remote station management uses the protocol data units, data elements, and security elements illustrated
in Figure 6, Figure 7, Figure 8, and Figure 9. The ASN.1 presentation of these PDUs is specified in Annex A.
RMCH -Request/Response:
OCTET STRING containing
SecHeader RSMP-Request or RSMP-Response SecTrailer
optionally encrypted
Figure 6 — RMCH protocol data units
RMCH-Request and RMCH-Response messages encapsulate RSMP-Request and RSMP-Response
messages, respectively, between a security header and a security trailer. RSMP-Request and RSMP-
Response messages may be encrypted as indicated in the SecHeader fields.
RSMP-Request:
PDU- Length of Request
SessionID PDU-ID (0)
Counter remainder Data
RSMP-Response:
PDU- Length of Response
SessionID PDU-ID (1)
Counter remainder Data
Figure 7 — RSMP protocol data units RSMP-Request and RSMP-Response
RSMP-Request messages of ASN.1 type RSMPmessage are sent by RMSs and by RMCs to request
a remote management session as illustrated in Figure 4. RSMP-Response messages of ASN.1 type
RSMPmessage are sent only by RMCs.
The SessionID identifies uniquely a session for a specific ITS-SCU and a specific management centre.
The value zero is used by a RMC in the RSMP-Request message requesting initiation of a secure
session by an RMS.
The PDU-Counter distinguishes PDUs uniquely in a session. The value presented in an RSMP-Request is
used in the corresponding RSMP-Response.
The PDU-ID distinguishes RSMP-Request and RSMP-Response messages.
RequestData:
Length of
RqDataID RqData
RqData
Response Data:
Length of Error
RsDataID RsData
RsData Status
Figure 8 — Request and response data elements RequestData and ResponseData
8 © ISO 2015 – All rights reserved

---------------------- Page: 13 ----------------------
ISO 24102-2:2015(E)

RqDataIDs are given in the ASN.1 type RefRSMPREQ and RsDataIDs are given in the ASN.1 type
RefRSMPRES. These IDs uniquely identify RqData and RsData, respectively.
The ErrorStatus is given by the ASN.1 type RSMPErrStatus.
SecHeader:
Length of
SecHeadID SecHead
SecHead
SecTrailer:
Length of
SecTrailID SecTrail
SecTrail
Figure 9 — Security header and trailer SecHeader and SecTrailer
SecHeadIDs and SecTrailIDs are given in the ASN.1 type RefSECRSMP. Not applying any security is given
by the ASN.1 value c-noSecurity; the corresponding SecHead and SecTrail are of ASN.1 type NullType.
8 Service primitive functions
8.1 Generic service primitives
Service primitives MF-COMMAND.request, MF-COMMAND.confirm, MF-REQUEST.request, MF-
REQUEST.confirm, SF-REQUEST.request, and SF-REQUEST.confirm are specified in ISO 24102-3. This
part of ISO 24102 specifies functions for these generic service primitives applicable for RSMP.
8.2 MF-SAP service primitive functions
8.2.1 Trans
...