ISO 24102-2:2018

INTERNATIONAL ISO
STANDARD 24102-2
Second edition
2018-11
Intelligent transport systems — ITS
station management —
Part 2:
Remote management of ITS-SCUs
Systèmes intelligents de transport — Gestion de la station ITS —
Partie 2: Gestion à distance des SCUs-ITS
Reference number
©
ISO 2018
© ISO 2018
All rights reserved. Unless otherwise specified, or required in the context of its implementation, 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
CP 401 • Ch. de Blandonnet 8
CH-1214 Vernier, Geneva
Phone: +41 22 749 01 11
Fax: +41 22 749 09 47
Email: copyright@iso.org
Website: www.iso.org
Published in Switzerland
ii © ISO 2018 – All rights reserved

Contents Page
Foreword .v
Introduction .vi
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 . 7
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.10
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 RMCH-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 .12
9.2.1 Active closure .12
9.2.2 Timeout .12
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 SRM .15
11 Dynamic data .15
12 Conformance .16
13 Test methods .16
Annex A (normative) Contexts of the RMPE ITS application class .17
Annex B (normative) ASN.1 modules .18
Annex C (informative) Communication service parameters .26
Annex D (normative) Implementation conformance statement (ICS) proforma .28
Bibliography .37
iv © ISO 2018 – All rights reserved

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 of the voluntary nature of standards, the meaning of ISO specific terms and
expressions related to conformity assessment, as well as information about ISO's adherence to the
World Trade Organization (WTO) principles in the Technical Barriers to Trade (TBT), see www .iso
.org/iso/foreword .html.
This document was prepared by Technical Committee ISO/TC 204, Intelligent transport systems.
This second edition cancels and replaces the first edition (ISO 24102-2:2015) which has been technically
revised.
A list of all parts in the ISO 24102 series can be found on the ISO website.
Any feedback or questions on this document should be directed to the user’s national standards body. A
complete listing of these bodies can be found at www .iso .org/members .html.
NOTE The former ISO 24102-5 has been converted into a separate standard ISO 22418, as it is not a station
management standard.
Introduction
This document is part of a series of International Standards for communications in intelligent transport
systems (ITS) based on the ITS station and communications architecture specified in ISO 21217 and
illustrated in Figure 1.
Figure 1 — ITS station reference architecture
This document is Part 2 of a multi-part document which determines remote management of an ITS
station unit (ITS-SU) operated as a bounded secured managed entity (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, communication
[5]
protocol layer parameters ,
— installation, update and uninstallation of persistent information in an ITS-SCU, e.g. ITS-S application
processes specified in ISO 21217, ITS-S communication protocols,
— notification and retrieval of management information, e.g. log files of events, alarms generated by
the ITS-SCU(s) of an ITS-SU.
[1]
By this it covers the five management areas identified in ISO/IEC 7498-4 .
vi © ISO 2018 – All rights reserved

INTERNATIONAL STANDARD ISO 24102-2:2018(E)
Intelligent transport systems — ITS station management —
Part 2:
Remote management of ITS-SCUs
1 Scope
This document provides specifications for intelligent transport systems (ITS) station management to
conform with the ITS station reference architecture.
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 communication unit. Distinction is made between managed entities (management clients) and
managing entities (management servers).
2 Normative references
The following documents are referred to in the text in such a way that some or all of their content
constitutes requirements of this document. For dated references, only the edition cited applies. For
undated references, the latest edition of the referenced document (including any amendments) applies.
ISO/IEC 8825-2, Information technology — ASN.1 encoding rules: Specification of Packed Encoding
Rules (PER)
ISO TS 16460, Intelligent transport systems — Communications access for land mobiles (CALM) —
Communication protocol messages for global usage
ISO 17419, Intelligent transport systems — Cooperative systems — Globally unique identification
ISO 17423, Intelligent transport systems — Cooperative systems — Application requirements and objectives
ISO 21217, Intelligent transport systems — Communications access for land mobiles (CALM) — Architecture
ISO 24102-1, Intelligent transport systems — ITS station management — Part 1: Local management
ISO 24102-3, Intelligent transport systems — ITS station management — Part 3: Service access points
3 Terms and definitions
For the purposes of this document, the terms and definitions given in ISO 21217, ISO 24102-1,
[1]
ISO 24102-3, ISO TS 16460, and ISO/IEC 7498-4 and the following apply.
ISO and IEC maintain terminological databases for use in standardization at the following addresses:
— ISO Online browsing platform: available at https: //www .iso .org/obp
— IEC Electropedia: available at http: //www .electropedia .org/
3.1
remote management client
ITS station communication unit in which remote ITS station management is performed by a remote
management server
3.2
remote management server
entity performing remote ITS station management in an ITS station communication unit
4 Symbols and abbreviated terms
For the purposes of this document, the abbreviated terms given in ISO 21217, ISO 24102-1, ISO 24102-3,
[1]
ISO TS 16460, and ISO/IEC 7498-4 and the following apply.
BSME Bounded Secured Managed Entity (from ISO 21217)
[3]
FSAP Fast Service Advertisement Protocol (from ISO 22418 )
ITS Intelligent Transport Systems
ITS-SCU ITS Station Communication Unit (from ISO 21217)
ITS-SCU-CMC ITS-SCU Configuration Management Centre (from ISO 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 provides the functionality specified in the various parts of this
multi-part document:
— The functionality of local ITS station management specified in ISO 24102-1.
— The functionality of remote ITS station management specified in this document (Part 2).
— The functionality of management service access points specified in ISO 24102-3.
— The functionality of ITS station-internal management communications specified in [2] (ISO 24102-4).
— The functionality of 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 document.
Detailed mandatory requirements are specified in the following clauses of this document:
— 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).
2 © ISO 2018 – All rights reserved

— Clause 11 identifies dynamic data.
— Clause 12 informs about conformance declaration.
— Clause 13 informs about conformance testing.
— The normative Annex A specifies contexts of the RMPE ITS application class.
— The normative Annex B specifies the ASN.1 module for remote management.
— The informative Annex C proposes settings of communication service parameters used for automatic
selection of communication profiles specified in ISO 17423.
— The normative Annex D presents the implementation conformance statement (ICS) proforma.
6 Remote management architecture
6.1 Functionality
The "Remote ITS Station Management Protocol" (RSMP) specified in this document 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 (ISO 17419), security related information, accounting information,
[5]
access layer parameters , etc.
— installation, update and uninstallation of persistent information in an ITS-SCU, e.g. ITS-S application
processes, ITS-S communication protocols,
— notification and retrieval of management information, e.g. log files of events, alarms generated by
the ITS-SCU of an ITS-SU.
[1]
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 an ITS station unit (ITS-
SU) acting as remote management server (RMS) manages an ITS station communication unit (ITS-SCU)
of an ITS-SU acting as remote management client (RMC).
An RMS is associated with an ITS-SCU configuration management centre identified in ISO 17419. An
RMS may be implemented e.g. in a roadside ITS sub-system, or in a central ITS sub-system. Several
RMSs may be associated with the same ITS-SCU configuration management centre. A single RMSs
may be associated with several ITS-SCU configuration management centre. A single ITS-SCU always is
associated only with a single ITS-SCU configuration management centre.
[1]
Remote ITS station management is applied to managed objects 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
[3]
(FSAP) 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 document enable future specifications of remote management
features in separate standards or by means of registries.
Figure 2 — Server initiated session (example with FSAP)
SAM and SRM specified in [3] with details specified in this document 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 2018 – All rights reserved

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.
Figure 4 — Client initiated session
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 Application Identifier" (ITS-AID) and "the ITS-S application process identifier" (ITS-SAPID)
of values
— 1 for the RSM client and
— 2 for the RSM server;
— the ITS-S facility "Remote Management Communication Handler" (RMCH) using a well-known
[4]
registered ITS port number PORT_RSMP and dynamically assigned ITS port numbers for localized
communications .The value of PORT_RSMP 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 ISO 17419.
Figure 5 — Functional blocks of RSMP
The RMCH communication protocol is located in the ITS-S facilities layer.
The RMPE ITS-S application process is located in the ITS-S management entity.
RMCH and RMPE are connected via the MF-SAP services MF-COMMAND and MF-REQUEST specified in
ISO 24102-3 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.
6 © ISO 2018 – All rights reserved

Details depend on the ITS-S networking & transport layer protocol used and are outside the scope of
this document.
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
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 see ISO 21217.
Management activities include:
— 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 management 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 6 from peer ITS-SUs,
— exchanges RSMP-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.
[4]
The well-known ITS port PORT_RSMP for localized communications is used by
a) an RMS for transmission of a message
— as a source port number;
— 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 "Request a
secure session" message shown in Figure 4.
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 B.
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.
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 a RMS.
The PDU-Counter distinguishes PDUs uniquely in a session. The value presented in a RSMP-Request is
used in the corresponding RSMP-Response.
The PDU-ID distinguishes RSMP-Request and RSMP-Response messages.
8 © ISO 2018 – All rights reserved

Figure 8 — Request and response data elements RequestData and ResponseData
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.
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
The 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
document specifies functions for these generic service primitives applicable for RSMP.
8.2 MF-SAP service primitive functions
8.2.1 Transmission request of RSMP-Request and RSMP-Response
The service primitive MF-COMMAND.request is used. ASN.1 types and values for the applicable function
shall be as specified in Table 1, with ASN.1 details specified in Annex B.
Table 1 — Transmission request of RSMP-Request and RSMP-Response
MF-Command-request
&mxref &MXParam Description
c-rsmpMessageTX RSMPmessageTX
Request to transmit RSMP-Request and RSMP-
Response to a specific peer station
MF-Command-confirm
&mxref &MXParam Description
c-rsmpMessageTX RSMPmessageTXconf
The MF-Command-request RSMPmessageTX shall
be confirmed with RSMPmessageTXconf and
with ErrStatus specified in ISO 24102-3.
8.2.2 Notification of reception of RSMP-Request and RSMP-Response
The service primitive MF-REQUEST.request is used. ASN.1 types and values for the applicable functions
shall be as specified in Table 2, with ASN.1 details specified in Annex B.
Table 2 — Notification of reception of RSMP-Request and RSMP-Response
MF-Request-request
&mxref &MXParam Description
c-rsmpMessageRX RSMPmessageRX
Notification of reception of RSMP-Request and
RSMP-Response from specific peer station
MF-Request-confirm
&mxref &MXParam Description
c-rsmpMessageRX RSMPmessageRXconf
The request RSMPmessageRX shall be confirmed
with RSMPmessageRXconf and with ErrStatus
specified in ISO 24102-3.
8.3 SF-SAP service primitive functions
8.3.1 Security procedure applied to RSMP-Request and RSMP-Response
The service primitive SF-REQUEST.request is used. ASN.1 types and values for the applicable functions
shall be as specified in Table 3, with ASN.1 details specified in Annex B.
Table 3 — Security procedure applied to RSMP-Request and RSMP-Response
SF-Request-request
&mxref &MXParam Description
c-secRSMPmessageTX SecRSMPmessageTX
Request to secure RSMP-Request/RSMP-
Response prior to transmission to a specific
peer station
SF-Request-confirm
&mxref &MXParam Description
c-secRSMPmessageTX RMCHmessage The SF-Request-request SecRSMPmessageTX
shall be confirmed with the secured copy of
RSMP-Request/RSMP-Response, i.e. the RMCH-
Request/RMCH-Response and with ErrStatus
specified in ISO 24102-3.
8.3.2 Security procedure applied to RMCH-Request and RMCH-Response
The service primitive SF-Request.request is used. ASN.1 types and values for the applicable functions
shall be as specified in Table 4, with ASN.1 details specified in Annex B.
10 © ISO 2018 – All rights reserved

Table 4 — Security procedure applied to RMCH-Request and RMCH response
SF-Request-request
&mxref &MXParam Description
c-secRMCHrX SecRMCHrX
Request to process security of a received
RMCH-Request/RMCH-Response from a specif-
ic peer station prior to forwarding to the RMPE
SF-Request-confirm
&mxref &MXParam Description
c-secRMCHrX RSMPmessage
The SF-Request-request SecRMCHrX shall be
confirmed with the unsecured copy of RMCH-
Request/RMCH-Response, i.e. the RSMP-
Request/RSMP-Response and with ErrStatus
specified in ISO 24102-3.
9 Remote management procedures
9.1 Remote management session initiation
9.1.1 Initiation by server
An RMS may initiate a remote management session upon purpose. In order to start a remote management
session, the RMS shall send the RSMP-Request(RMSinitSession) to the RMC in the desired ITS-SCU.
Upon reception of a valid RSMP-Request(RMSinitSession), the RMC shall acknowledge the request
with the RSMP-Response(RMSinitSessionRs).
9.1.2 Initiation by client
An RMC may initiate a remote management session upon purpose. In order to request initiation
of a remote management session, the RMC shall send the RSMP-Request(RMCreqSession) to
the desired management center. This request may be repeated until the RMC receives an RSMP-
Request(RMSinitSession) from the selected RMS starting the requested session.
NOTE An ITS-SCU knows how to reach its associated ITS-SCU management centre and the necessary
communication protocols and addresses. Details are out of scope of this document. Typically a cellular network
and Internet can be used.
Upon reception of the RSMP-Request(RMSinitSession), the RMC shall acknowledge the request with
the RSMP-Response(RMSinitSessionRs).
9.1.3 RSMP session identifier
Every remote management session is identified by an RSMP session identifer "SessionID" of ASN.1
type RsmpSessionID assigned by the RMC. The values of SessionID shall be unique for a given RMC.
The value zero shall be used by a RMC in the RSMP-Request message requesting initiation of a secure
session by a RMS as specified in Clause 7.
9.1.4 RSMP session security
Details of security schemes to be applied for a remote management session may be negotiated between
RMS and RMC. This negotiation is performed using the RSMP-Request and RSMP-Response PDUs
specified in Clause 7. Details of these PDUs will be specified in a future version of this document.
9.2 Remote management session closure
9.2.1 Active closure
As soon as no further remote management actions are needed in a remote management session, the
RMS shall close the session. Closure of a remote management session shall be indicated by the RMS by
sending the RSMP-Request(RMScloseSession) to the RMC.
Upon reception of the RSMP-Request(RMScloseSession), the RMC shall acknowledge the request with
the RSMP-Response(RMScloseSessionRs), and shall treat the remote management session as closed.
9.2.2 Timeout
In case an RMC does not receive RSMP-Requests from a RMS during an open remote management
session for a time period larger than the time indicated in the management parameter RSMPtimeout of
ASN.1 type RSMPtimeout, the RMC shall close the remote management session on its own.
In order to keep a session alive, an RMS may periodically send the Ping-command RSMP-
Request(RSMPping) with arbitrary data which shall be acknowledged by the RMC with the Ping-
command RSMP-Response(RSMPping) returning the received arbitrary data.
NOTE This document does not specify a value for RSMPtimeout.
9.2.3 No active session
As long as an RMC is not in an active remote management session with an RMS, it shall ignore all RSMP-
Request messages except the one to start a remote management session and an optionally repeated
RSMP-Request(RMScloseSession).
9.3 Firmware update
A partial or complete update of the firmware of an ITS-SCU may be requested by the RMS by sending the
RSMP-Request(firmwareUpdate) message. Upon reception of the RSMP-Request(firmwareUpdate)
message the RMC shall first acknowledge reception of the RSMP-Request(firmwareUpdate) message
by sending the RSMP-Response(firmwareUpdateRs) message, and shall then perform the requested
firmware update in line with requirements on secure operation of the platform in which the ITS-SCU is
installed. Upon automatic restart of the ITS-SCU after the firmware update, the ITS-SCU shall request a
remote management session at the RMS to confirm success of the operation, and to close correctly the
session.
As long as a firmware update session is active, other management sessions are prohibited.
9.4 Maintenance of ITS-S protocols
ITS-S protocols are protocols different to ITS-S application processes which reside in the ITS-S access
layer, the ITS-S networking & transport layer, the ITS-S facilities layer, the ITS-S management entity and
the ITS-S security entity.
Maintenance of an ITS-S protocols may be performed with RSMP-Request(ProtMaintenance)
distinguishing three types of maintenance operation:
a) Installation of a new ITS-S protocol requested with ASN.1 type ProtMgmtInstallRq.
b) Update of an existing ITS-S protocol requested with ASN.1 type ProtMgmtUpdateRq. The
existing ITS-S protocol is identified with ASN.1 type ProtocolID provided by the RSC in the
acknowledgement of an initial installation.
12 © ISO 2018 – All rights reserved

c) Deletion of an existing ITS-S protocol requested with ASN.1 type ProtMgmtDeleteRq. The
existing ITS-S protocoll is identified with ASN.1 type ProtocolID provided by the RSC in the
acknowledgement of an initial installation.
A maintenance request shall be acknowledged by an RMC with RSMP-Response (protMaintenanceRs)
distinguishing three types of maintenance operation:
a) Acknowledgement of an installation of a new (instantiation of an) ITS-S application process with
ASN.1 type ProtMgmtInstallRs providing the unique application Identifier of ASN.1 type
ProtocolID of this instantiation of an ITS-S application process. In case of failure ProtocolID.
instance shall contain the value zero, otherwise the value contained in ProtMgmtInstallRq.
b) Acknowledgement of an update of an existing ITS-S protocoll with ASN.1 type ProtMgmtUpdateRs.
In case of failure ProtocolID.instance contained in ProtMgmtUpdateRs shall contain the
value zero, otherwise the value contained in ProtMgmtUpdateRq.
c) Acknowledgement of deletion of an existing ITS-S protocoll with ASN.1 type ProtMgmtDeleteRs.
In case of success ProtocolID.instance contained in ProtMgmtDeleteRs shall contain the
value zero, otherwise the value contained in ProtMgmtDeleteRq.
The return status of ASN.1 type RSMPErrStatus contained in the acknowledgement shall present a
value as specified in Table 5.
Table 5 — Protocol maintenance result status
Status value in Installation Update Deletion
RSMPErrStatus
rsmpErrSuccess
Successful installation Successful update Successful deletion
rsmpErrRejected
Request rejected by RSC for unknown reasons
rsmpErrProtUnknown
n.a. Request rejected as referenced ITS-S protocol given
in ASN.1 type ProtocolID is not known at the RSC.
rsmpErrUnspecFailure
Request failed for unknown reasons
9.5 Maintenance of ITS-S application processes
Maintenance of an ITS-S application process may be performed with RSMP-Request(appMaintenance)
distinguishing three types of maintenance operation:
a) Installation of a new (instantiation of an) ITS-S application process requested with ASN.1 type
AppMgmtInstallRq.
b) Update of an existing ITS-S application process requested with ASN.1 type AppMgmtUpdateRq.
The existing ITS-S application process is identified with ASN.1 type ITSsapiid provided by the
RSC in the acknowledgement of an initial installation.
c) Deletion of an existing ITS-S application process requested with ASN.1 type AppMgmtDeleteRq.
The existing ITS-S application process is identified with ASN.1 type ITSsapiid provided by the
RSC in the acknowledgement of an initial installation.
A maintenance request shall be acknowledged by an RMC with RSMP-Response(appMaintenanceRs)
distinguishing three types of maintenance operation:
a) Acknowledgement of an installation of a new (instantiation of an) ITS-S application process with
ASN.1 type AppMgmtInstallRs providing the unique application Identifier of ASN.1 type
ITSsapiid of this instantiation of an ITS-S application process. In case of failure ITSsapiid.
AppInstance shall contain the value zero, otherwise the value contained in AppMgmtInstallRq.
b) Acknowledgement of an update of an existing ITS-S application process with ASN.1
type AppMgmtUpdateRs. In case of failure ITSsapiid.AppInstance contained
in AppMgmtUpdateRs shall contain the value zero, otherwise the value contained in
AppMgmtUpdateRq.
c) Acknowledgement of deletion of an existing ITS-S application process with ASN.1 type
AppMgmtDeleteRs. In case of success ITSsapiid.AppInstance contained in
AppMgmtDeleteRs shall contain the value zero, otherwise the value contained in
AppMgmtDeleteRq.
The return status of ASN.1 type RSMPErrStatus contained in the acknowledgement shall present a
value as specified in Table 6.
Table 6 — Application maintenance result status
Status value in Installation Update Deletion
RSMPErrStatus
rsmpErrSuccess
Successful installation Successful update Successful deletion
rsmpErrRejected
Request rejected by RSC for unknown reasons
rsmpErrAppUnknown
n.a. Request rejected as referenced instantiation of an ITS-S
application process given in ASN.1 type ITSsapiid
is not known at the RSC.
rsmpErrUnspecFailure
Request failed for unknown reasons
9.6 Maintenance of configuration information
In order to read the value of one or several management parameters (M-Params specified in
ISO 24102-1), an RMS shall send the RSMP-Request(getMparams) message. Upon reception of the
RSMP-Request(getMparams) message, the RMC shall return the requested information in the RSMP-
Response(getMparamsRs) message. In case a parameter value cannot be provided, it shall be omitted
in RSMP-Response(getMparamsRs).
In order to write the value of one or several management parameters (M-Params specified in
ISO 24102-1), an RMS shall send the RSMP-Request(setMparams) message. Upon reception of the
RSMP-Request(setMparams), the RMC shall perform the requested parameter settings in case no
access violation occurred, and shall report success or failure in the RSMP-Response(setMparamsRs).
In case all requested parameter settings could be performed, the global result status shall be set to
"rsmpErrSuccess". Otherwise the global result status shall be set to "rsmpErrSetErrorGeneral"
and detailed result status shall be returned for every failure that occurred.
10 Usage of FSAP
10.1 General
The "Fast Service Advertisement Protocol" FSAP is specified in [3]. This document specifies usage of
FSAP for RSMP; for the general parts of FSAP see [3].
10.2 SAM
The "ITS-AID" field contained in the element for "RMPE advertisement" of the "Service Info Segment"
of the "Service Advertisement Message" (SAM) shall contain the registered value of RMPE. RMPE is
registered as an ITS Application Class; see ISO 17419. The various contexts of this application class
are distinguished by the globally unique identifier ITS-SCU-CMCID of the ITS-SCU configuration
management centre (ITS-SCU-CMC) of the ITS-SCU to be managed.
NOTE 1 The registered value of ITS-AID for RMPE is 134.
14 © ISO 2018 – All rights reserved

NOTE 2 ITS-SCU-CMCID is of ASN.1 type ItsScuCmcID::=OBJECT IDENTIFIER.
Contexts of the RMPE ITS application class are presented in Annex A.
The "Reply Port Number" field, if present in the element for "RMPE advertisement" of the "Service Info
Segment" of a SAM, shall show the registered well-known number PORT_RSMP specified in ISO 17419.
NOTE 3 Presence of the "Reply Port Number" field is not required, as the value contained in it is the registered
well-known port number PORT_RSMP.
NOTE 4 The registered value of the well-known port number PORT_RSMP is 32763.
The optional "SAMapplicationData" field of the "Service Info Extensions" field contained in the element
for "RMPE advertisement" of the "Service Info Segment" of a "Service Advertisement Message" (SAM)
may contain the unique identifier of ASN.1 type ItsScuCmcID of the ITS-SCU-CMC specified in
ISO 17419 that offers remote station management. In case different ITS-SCU-CMCs are available, this
optional
...