ISO 24102-4:2013/Amd 1:2017

INTERNATIONAL ISO
STANDARD 24102-4
First edition
2013-07-01
AMENDMENT 1
2017-04
Intelligent transport systems —
Communications access for land
mobiles (CALM) — ITS station
management —
Part 4:
Station-internal management
communications
AMENDMENT 1
Systèmes intelligents de transport — Accès aux communicat ions des
services mobiles terrestres (CALM) — Gestion des stations ITS —
Partie 4: Communications de gestion interne à la station
AMENDEMENT 1
Reference number
ISO 24102-4:2013/Amd.1:2017(E)
©
ISO 2017

---------------------- Page: 1 ----------------------
ISO 24102-4:2013/Amd.1:2017(E)

COPYRIGHT PROTECTED DOCUMENT
© ISO 2017, 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. +41 22 749 01 11
Fax +41 22 749 09 47
copyright@iso.org
www.iso.org
ii © ISO 2017 – All rights reserved

---------------------- Page: 2 ----------------------
ISO 24102-4:2013/Amd.1:2017(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 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 the following
URL: w w w . i s o .org/ iso/ foreword .html.
Amendment 1 to ISO 24102-4:2013 was prepared by Technical Committee ISO/TC 204, Intelligent
transport systems.
A list of all parts in the ISO 24102 series can be found on the ISO website.
© ISO 2017 – All rights reserved iii

---------------------- Page: 3 ----------------------
ISO 24102-4:2013/Amd.1:2017(E)
Intelligent transport systems — Communications access
for land mobiles (CALM) — ITS station management —
Part 4:
Station-internal management communications
AMENDMENT 1
Page 4, Figure 3
Replace Figure 3 by the following.
Figure 3 — IIC PDU structure
© ISO 2017 – All rights reserved 1

---------------------- Page: 4 ----------------------
ISO 24102-4:2013/Amd.1:2017(E)

Page 4, Table 1
Replace Table 1 by the following.
PDU element IIC-Request IIC-Response
SourceITS-SCU-ID ITS-SCU-ID of source ITS-SCU, which ITS-SCU-ID of ITS-SCU, which produces
produces the request. See parameter the response.
“ITS-scuId” specified in ISO 24102-1.
DestinationITS-SCU-ID ITS-SCU-ID of destination ITS-SCU, Same as SourceITS-SCU-ID of related
which shall evaluate the request. request if not requested otherwise in
this document.
PDU-Counter Even number generated from a cyclic PDU-Counter of related request in-
counter at the ITS-SCU, which produces cremented by one.
the request.
PDU-ID One octet INTEGER value 0. One octet INTEGER value 1.
Data Data type identifier RqDataID followed Data type identifier RsDataID followed
by length of RqData in Integer multiples by length of RsData in Integer multiples
of an octet and RqData. of an octet and RsData.
ErrorStatus Not existent. Existent.
0: No error happened > 0: Number
indicating type of error.
Seq Security type identifier SecRqID fol- Security type identifier SecRsID fol-
lowed by the length of SecRequest lowed by the length of SecResponse
in Integer multiples of an octet and in Integer multiples of an octet and
SecRequest. SecResponse.
Page 5, Table 2
Replace Table 2 by the following.
SourceITS-SCU-ID Destination- Description
ITS-SCU-ID
0 Reserved. Used to indicate “own/local ITS-SCU”. Must not be used in
communications with other ITS-SCUs.
n.a. 1 ITS-SCU-ID identifying ITS-SCUs with ITS-S host role.
n.a. 2 ITS-SCU-ID identifying ITS-SCUs with ITS-S router role.
3 3 ITS test system (using IICP for upper tester access).
4 - 7 ITS-SCU-ID identifying ITS-SCUs with an implementation specific role.
8 . 65534 ITS-SCU-ID identifying uniquely a specific ITS-SCU in an ITS station.
n.a. 65535 ITS-SCU-ID identifying all ITS-SCUs.
2 © ISO 2017 – All rights reserved

---------------------- Page: 5 ----------------------
ISO 24102-4:2013/Amd.1:2017(E)

Page 10, Annex A
Replace Annex A with the following:
Annex A
(normative)

ASN.1 module
A.1 Overview
The following ASN.1 module is specified in this annex:
— CALMiitsscu { ISO (1) standard (0) calm-management (24102) iitsscu (4) asnm-1 (1)}
A.2 Module CALMiitsscu
This module specifies ASN.1 type definitions together with useful ASN.1 value definitions.
Unaligned packed encoding rules (PER) as specified in ISO/IEC 8825-2 shall be applied for this
ASN.1 module.
In order to achieve octet alignment enabling cheap implementations, “fill” bits were defined. All fill bits
shall be set to the value ‘0’b.
CALMiitsscu { iso (1) standard (0) calm-management (24102) iitsscu (4) asnm-1 (1)}
DEFINITIONS AUTOMATIC TAGS::=BEGIN

IMPORTS
CIaClass, CIclass, CIstatus, Directivity, Link-ID, LLserviceAddr, MACaddress, MedType FROM
CALMllsap {iso(1) standard(0) calm-ll-sap(21218) asnm-1 (1)}

ITS-scuId, Param24102No, Param24102 FROM CALMmanagement { iso (1) standard (0)
calm-management (24102) local (1) asnm-1 (1)}

SimFUTcmd, SimFUTreq, SimFLTcmd, SimNUTcmd, SimNLTcmd, SimIUTcmd, SimFLTreq, SimNUTreq,
SimNLTreq, SimIUTreq, ErrStatus, MF-Command-request, MF-Request-request, MN-Command-
request, MN-Request-request, MI-Command-request, MI-Request-request, MA-Command-request,
MA-Request-request, MS-Command-request, MS-Request-request, MI-Get-request, MI-Set-
request, MF-Command-confirm, MF-Request-confirm, MN-Command-confirm, MN-Request-confirm,
MI-Command-confirm, MI-Request-confirm, MA-Command-confirm, MA-Request-confirm, MS-Command-
confirm, MS-Request-confirm, MI-Get-confirm, MI-Set-confirm FROM CALMmsap {iso (1) standard
(0) calm-management (24102) msap (3) asnm-1 (1)}

-- Details on SecRq and SecRs to be provided by a standard on security
;
-- End of IMPORTS

-- Types

-- PDUs --
-- IIC-Request PDU
IIC-Request::=SEQUENCE{
sourceITS-scuId ITS-scuId,
destinationITS-scuId ITS-scuId,
pduCounter  PduCounter,
requestID  RequestID, -- value zero
pduRequest  PduRequest,
secRq  SecRq
}

RequestID::=INTEGER{
request (0)
} (0.255)


SECIICP::=CLASS{
&ref  INTEGER(0.255), -- security type identifier
© ISO 2017 – All rights reserved 3

---------------------- Page: 6 ----------------------
ISO 24102-4:2013/Amd.1:2017(E)

&SecIICP
}

SecIICPs SECIICP::={noSecurity | octString, .}


noSecurity  SECIICP::={&ref 0, &SecIICP NULL}
octString  SECIICP::={&ref 1, &SecIICP OCTET STRING (SIZE(0.65535))}

SecRq::=SEQUENCE{
secRqRef SECIICP.&ref({SecIICPs}),
secRq  SECIICP.&SecIICP({SecIICPs}{@secRqRef})
}

IICPREQ::=CLASS{
&ref  INTEGER(0.255), -- data type identifier
&IICPrequest
}

IICPrequests IICPREQ::={aliveRq | mfRcmdRq | mfRreqRq | mnRcmdRq | mnRreqRq | miRcmdRq |
miRreqRq | miRgetRq | miRsetRq | mCmdRq | maRcmdRq | maRreqRq | msRcmdRq | msRreqRq |
simFutCmdRq | simFutReqRq | simNutCmdRq | simNutReqRq | simIutCmdRq | simIutReqRq |
simFltCmdRq | simFltReqRq | simNltCmdRq | simNltReqRq, .}

PduRequest::=SEQUENCE{
reqRef  IICPREQ.&ref({IICPrequests}), -- data type identifier
iicpReq IICPREQ.&IICPrequest({IICPrequests}{@reqRef})
}

aliveRq IICPREQ::={&ref 0, &IICPrequest ITS-SCUalive}
mfRcmdRq IICPREQ::={&ref 1, &IICPrequest MF-Command-request}
mfRreqRq IICPREQ::={&ref 2, &IICPrequest MF-Request-request}
mnRcmdRq IICPREQ::={&ref 3, &IICPrequest MN-Command-request}
mnRreqRq IICPREQ::={&ref 4, &IICPrequest MN-Request-request}
miRcmdRq IICPREQ::={&ref 5, &IICPrequest MI-Command-request}
miRreqRq IICPREQ::={&ref 6, &IICPrequest MI-Request-request}
miRgetRq IICPREQ::={&ref 7, &IICPrequest MI-Get-request}
miRsetRq IICPREQ::={&ref 8, &IICPrequest MI-Set-request}
mCmdRq  IICPREQ::={&ref 9, &IICPrequest McmdRq}
maRcmdRq IICPREQ::={&ref 10, &IICPrequest MA-Command-request}
maRreqRq IICPREQ::={&ref 11, &IICPrequest MA-Request-request}
msRcmdRq IICPREQ::={&ref 12, &IICPrequest MS-Command-request}
msRreqRq IICPREQ::={&ref 13, &IICPrequest MS-Request-request}
-- simAutCmdRq IICPREQ::={&ref 242, &IICPrequest SimAUTcmd}
-- simAutReqRq IICPREQ::={&ref 243, &IICPrequest SimAUTreq}
simFutCmdRq  IICPREQ::={&ref 244, &IICPrequest SimFUTcmd}
simFutReqRq  IICPREQ::={&ref 245, &IICPrequest SimFUTreq}
simNutCmdRq  IICPREQ::={&ref 246, &IICPrequest SimNUTcmd}
simNutReqRq  IICPREQ::={&ref 247, &IICPrequest SimNUTreq}
simIutCmdRq  IICPREQ::={&ref 248, &IICPrequest SimIUTcmd}
simIutReqRq  IICPREQ::={&ref 249, &IICPrequest SimIUTreq}
-- simAltCmdRq IICPREQ::={&ref 250, &IICPrequest SimALTcmd}
-- simAltReqRq IICPREQ::={&ref 251, &IICPrequest SimALTreq}
simFltCmdRq  IICPREQ::={&ref 252, &IICPrequest SimFLTcmd}
simFltReqRq  IICPREQ::={&ref 253, &IICPrequest SimFLTreq}
simNltCmdRq  IICPREQ::={&ref 254, &IICPrequest SimNLTcmd}
simNltReqRq  IICPREQ::={&ref 255, &IICPrequest SimNLTreq}

ITS-SCUalive::=SEQUENCE{
message AliveMessage,
its-scuType ITS-SCUtype
}

AliveMessage::= INTEGER{
alive (0),
delete (1),
new (255)
} (0.255)

ITS-SCUtype::= INTEGER{
unknown (0),
4 © ISO 2017 – All rights reserved

---------------------- Page: 7 ----------------------
ISO 24102-4:2013/Amd.1:2017(E)

host (1),
router (2),
itsTestSystem (3),
any (255)
} (0.255)

-- General OBJECT CLASS for management commands

MCMD::=CLASS{
&refMcmd INTEGER(0.255), -- allows for 256 commands
&Mcmd
}


MCMDREQ::=MCMD

McmdRq::=SEQUENCE{
mCmdRef MCMDREQ.&refMcmd({McmdReqs}),
mcmd MCMDREQ.&Mcmd ({McmdReqs}{@mCmdRef})
}

McmdReqs MCMDREQ::={pingRq | vCIinfoRq | vCIupdateRq | getParam24102Rq | setParam24102Rq |
testIicpRq | testConfigRq, .}

pingRq  MCMDREQ::={&refMcmd 0, &Mcmd PingIICP}
vCIinfoRq MCMDREQ::={&refMcmd 1, &Mcmd VCI-info-req}
vCIupdateRq MCMDREQ::={&refMcmd 2, &Mcmd VCI-update-req}
getParam24102Rq MCMDREQ::={&refMcmd 3, &Mcmd Param24102No}
setParam24102Rq MCMDREQ::={&refMcmd 4, &Mcmd Param24102}
testIicpRq MCMDREQ::={&refMcmd 254, &Mcmd TestIicp}
testConfigRq MCMDREQ::={&refMcmd 255, &Mcmd TestConfigIICP}

PingIICP::=OCTET STRING (SIZE(0.255))

VCI-info-req::=SEQUENCE{
medType MedType,
ciaClass CIaClass,
ciClass CIclass
}

VCI-update-req::=SEQUENCE (SIZE(0.255)) OF VCI-Info

VCI-Info::=SEQUENCE{
linkId Link-ID,
medType MedType,
ciaClass CIaClass,
ciClass CIclass,
status CIstatus
}

TestIicp::=SEQUENCE{
fill BIT STRING (SIZE(6)), -- all bits set to '0'
action CHOICE{
-- simulation of a trigger event in the ITS-S management entity of the SUT
-- to perform remote COMMAND access to an MX-SAP in the ITS test system
-- request to send MF-Command-request to ITS test system
mfRcmd  MFrcmd,
-- request to send MN-Command-request to ITS test system
mnRcmd  MNrcmd,
-- request to send MI-Command-request to ITS test system
miRcmd  MIrcmd
-- request to send MS-Command-request to ITS test system
-- msRcmd  MSrcmd,
-- request to send MA-Command-request to ITS test system
maRcmd  MArcmd
 }
}

-- Upper Tester TX: remote COMMAND accesses to an MX-SAP

-- MSrcmd::=SEQUENCE{
© ISO 2017 – All rights reserved 5

---------------------- Page: 8 ----------------------
ISO 24102-4:2013/Amd.1:2017(E)

-- destination ITS-scuId,
-- cmd MS-Command-request
-- }
MArcmd::=SEQUENCE{
destination ITS-scuId,
cmd MA-Command-request
}
MFrcmd::=SEQUENCE{
destination ITS-scuId,
cmd MF-Command-request
}
MNrcmd::=SEQUENCE{
destination ITS-scuId,
cmd MN-Command-request
}
MIrcmd::=SEQUENCE{
destination ITS-scuId,
cmd MF-Command-request
}

TestConfigIICP::=SEQUENCE{
location BIT STRING (SIZE(6)),
lowerLayers BIT STRING (SIZE(1)),
testMode BIT STRING (SIZE(1))
}

-- IIC-Response PDU

IIC-Response::=SEQUENCE{
sourceITS-scuId ITS-scuId,
destinationITS-scuId ITS-scuId,
pduCounter  PduCounter,
responseID  ResponseID, -- value 1
pduResponse  PduResponse,
errorStatus  PduErrStatus,
secRs  SecRs
}

ResponseID::=INTEGER{
response (1)
} (0.255)

SecRs::=SEQUENCE{
secRsRef SECIICP.&ref({SecIICPs}),
secRs  SECIICP.&SecIICP({SecIICPs}{@secRsRef})
}


IICPRES::=CLASS{
&ref  INTEGER(0.255),
&IICPresponse
}

IICPresponses IICPRES::={aliveRs | mfRcmdRs | mfRreqRs | mnRcmdRs | mnRreqRs | miRcmdRs |
miRreqRs | miRgetRs | miRgetRs | miRsetRs | mCmdRs | maRcmdRs | maRreqRs | msRcmdRs |
msRreqRs | simAutCmdRs | simAutReqRs | simFutCmdRs | simFutReqRs | simNutCmdRs |
simNutReqRs | simIutCmdRs | simIutReqRs |
...