1、 ISO 2017 Intelligent transport systems Communications access for land mobiles (CALM) ITS station management Part 3: Service access points AMENDMENT 1 Systmes intelligents de transport Accs aux communications des services mobiles terrestres (CALM) Gestion des stations ITS Partie 3: Points daccs au s
2、ervice AMENDEMENT 1 INTERNATIONAL STANDARD ISO 24102-3 First edition 2013-07-01 Reference number ISO 24102-3:2013/Amd.1:2017(E) AMENDMENT 1 2017-04 ISO 24102-3:2013/Amd.1:2017(E)ii ISO 2017 All rights reserved COPYRIGHT PROTECTED DOCUMENT ISO 2017, Published in Switzerland All rights reserved. Unles
3、s 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 ad
4、dress below or ISOs 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 copyrightiso.org www.iso.org ISO 24102-3:2013/Amd.1:2017(E) Foreword ISO (the International Organization fo
5、r 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
6、 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 proce
7、dures 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 editori
8、al 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 rig
9、hts 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
10、 explanation on the meaning of ISO specific terms and expressions related to conformit y assessment, as well as information about ISOs adherence to the World Trade Organization (WTO) principles in the Technical Barriers to Trade (TBT) see the following URL: www . i s o .org/ iso/ foreword .html. Ame
11、ndment 1 to ISO 24102-3: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 Intelligent transport systems Communications access for land mobiles (CALM) ITS st
12、ation management Part 3: Service access points AMENDMENT 1 Page 1, Scope Add the following new list item with two sub-items after the last list item: the interfaces between the ITS-S application entity and the ITS-S management entity (MA-SAP), and the ITS-S security entity (SA-SAP).Page 2, Abbreviat
13、ed terms Add the following abbreviated terms before MF-COMMAND: MA-COMMAND command issued by the ITS-S management entity and sent to the ITS-S application entity via the MA-SAP MA-REQUEST command issued by the ITS-S management entity and sent to the ITS-S security enti- ty via the MA-SAP Add the fol
14、lowing abbreviated terms before SF-COMMAND: SA-COMMAND command issued by the ITS-S security entity and sent to the ITS-S application entity via the SA-SAP SA-REQUEST command issued by the ITS-S application entity and sent to the ITS-S security entity via the SA-SAPPage 3, Requirements In the second
15、paragraph, add the following as the first item on the list: MA-SAP, SA-SAP, At the end of the paragraph, before NOTE 1, add the following sentence: The presentation of the specified services, service primitives and functions in ASN.1 shall be as specified in Annex A. Replace NOTE 2 by the following:
16、 NOTE 2 All interfaces towards the ITS-S applications are considered to be implemented in an API. ISO 24102-3:2013/Amd.1:2017(E) ISO 2017 All rights reserved 1 ISO 24102-3:2013/Amd.1:2017(E) In the third paragraph, replace the first sentence with the following: Means to secure the access to manageme
17、nt functionality need to be specified within the global context of the BSMD security. In the last paragraph, insert the following before the last item on the list: Clause 13 specifies the MA-SAP and SA-SAP. Page 23 Insert as a new Clause 13 the following clause and subclauses: 13 Interfaces MA and S
18、A towards the ITS-S application entity 13.1 SAPs and API The API illustrated in Figure 1 contains the functionality of the interfaces MA, FA, and SA specified in ISO 21217. The MA-SAP and the SA-SAP are specified in this document. Basically, there shall be different types of services that facilitate
19、 a) sending a command from the ITS-S management entity or the ITS-S security entity to the ITS applications entity, and b) receiving a request (command) from the ITS-S application entity by the ITS-S management entity or the ITS-S security entity. Issuing of commands by the ITS-S management entity t
20、o the ITS applications entity shall be built on the service MA-COMMAND. Receiving of requests from the ITS-S application entity by the ITS-S management entity shall be built on the service MA-REQUEST. Issuing of commands by the ITS-S security entity to the ITS applications entity shall be built on t
21、he service SA-COMMAND. Receiving of requests from the ITS-S application entity by the ITS-S security entity shall be built on the service SA-REQUEST. Details of the service primitives shall be as specified in Annex A. 13.2 MA-COMMAND 13.2.1 MA-COMMANDs Annex Q provides an overview and coding details
22、 on MA-COMMANDs that may be sent to the ITS-S application entity. MA-COMMANDs shall be enabled by means of the service primitives MA-COMMAND.request and MA- COMMAND.confirm. 13.2.2 MA-COMMAND.request The management service primitive MA-COMMAND.request allows the ITS-S management entity to trigger an
23、 action at the ITS-S application entity. The parameters of the management service primitive MA-COMMAND.request are as follows: MA-COMMAND.request ( CommandRef, MA-Command )2 ISO 2017 All rights reserved ISO 24102-3:2013/Amd.1:2017(E) Table 33 MA-COMMAND.request Parameter description Name Description
24、 CommandRef Unique cyclic reference number of command. A-Command.No See Annex Q. A-Command.Value See Annex Q. An MA-COMMAND.request shall be generated by the ITS-S management entity when the ITS-S application entity shall perform an action. On receipt of MA-COMMAND.request the requested action shall
25、 be performed. 13 . 2 . 3 M A - C OM M A N D . c on f i r m The service primitive MA-COMMAND.confirm reports the result of a previous MA-COMMAND.request. The parameters of MA-COMMAND.confirm are as follows: MA-COMMAND.confirm ( CommandRef, MA-CmdConfirm, ErrStatus ) T a b l e 3 4 M A - CO M M A N D
26、. c o n f i r m P a r a m e t e r d e s c r i p t i o n Name Description CommandRef Unique cyclic reference number of command. Same value as in related MA-COMMAND. request. MA-CmdConfirm.No Reference number of command. Same value as A-Command.No in related MA-COM- MAND.request. MA-CmdConfirm.Value C
27、arries optional confirm data. ErrStatus Error/return code, see Table P.1 An MA-COMMAND.confirm shall be generated by the ITS-S application entity upon performance of a previous MA-COMMAND.request in case ErrStatus indicates error or MA-CmdConfirm is present. It may be generated in case ErrStatus ind
28、icates success or A-CmdConfirm is not present. On receipt of MA-COMMAND.confirm, ErrStatus and MA-CmdConfirm shall be evaluated and a possible action shall be performed properly. 13.3 MA-REQUEST 13.3.1 MA-REQUESTs Annex R provides an overview and coding details on MA-REQUESTs. MA-REQUESTs shall be e
29、nabled by means of the service primitives MA-REQUEST.request and MA- REQUEST.confirm. 13.3.2 MA-REQUEST.request The management service primitive MA-REQUEST.request allows the ITS-S application entity to trigger an action at the ITS-S management entity. ISO 2017 All rights reserved 3 ISO 24102-3:2013
30、/Amd.1:2017(E) The parameters of MA-REQUEST.request are as follows: MA-REQUEST.request ( CommandRef, MA-Request ) Table 35 MA-REQUEST.request Parameter description Name Description CommandRef Unique cyclic reference number of command. MA-Request.No See Annex R. MA-Request.Value See Annex R. An MA-RE
31、QUEST.request shall be generated by the ITS-S application entity when the ITS-S management entity shall perform an action. On receipt of MA-REQUEST.request the required action shall be performed. 13 . 3 . 3 M A -R E QU E S T . c on f i r m The service primitive MA-REQUEST.confirm reports the result
32、of a previous MA-REQUEST.request. The parameters of MA-REQUEST.confirm are as follows: MA-REQUEST.confirm ( CommandRef, MA-ReqConfirm, ErrStatus ) T a b l e 3 6 M A - R E Q U E S T . c o n f i r m P a r a m e t e r d e s c r i p t i o n Name Description CommandRef Unique cyclic reference number of c
33、ommand. Same value as in related MA-REQUEST. request. MA-ReqConfirm.No Reference number of command. Same value as MA-Request.No in related MA-REQUEST. request. MA-ReqConfirm.Value Carries optional confirm data. ErrStatus Error/return code, see Table P.1. An MA-REQUEST.confirm shall be generated by t
34、he ITS-S management entity upon performance of a previous MA-REQUEST.request in case ErrStatus indicates error or MA-ReqConfirm is present. It may be generated in case ErrStatus indicates success or MA-ReqConfirm is not present. On receipt of MA-REQUEST.confirm, ErrStatus and MA-ReqConfirm shall be
35、evaluated and a possible action shall be performed properly. Details are outside the scope of this document. 13.4 SA-COMMAND 13.4.1 SA-COMMANDs Annex S provides an overview and coding details on SA-COMMANDs that may be sent to the ITS-S application entity. SA-COMMANDs shall be enabled by means of th
36、e service primitives SA-COMMAND.request and SA- COMMAND.confirm.4 ISO 2017 All rights reserved ISO 24102-3:2013/Amd.1:2017(E) 13.4.2 SA-COMMAND.request The management service primitive SA-COMMAND.request allows the ITS-S management entity to trigger an action at the ITS-S application entity. The par
37、ameters of the management service primitive SA-COMMAND.request are as follows: SA-COMMAND.request ( CommandRef, SA-Command ) Table 37 SA-COMMAND.request Parameter description Name Description CommandRef Unique cyclic reference number of command. A-Command.No See Annex S. A-Command.Value See Annex S.
38、 An SA-COMMAND.request shall be generated by the ITS-S management entity when the ITS-S application entity shall perform an action. On receipt of SA-COMMAND.request the requested action shall be performed. 13 . 4 . 3 S A - C OM M A N D . c on f i r m The service primitive SA-COMMAND.confirm reports
39、the result of a previous SA-COMMAND.request. The parameters of SA-COMMAND.confirm are as follows: SA-COMMAND.confirm ( CommandRef, SA-CmdConfirm, ErrStatus ) T a b l e 3 8 S A - CO M M A N D . c o n f i r m P a r a m e t e r d e s c r i p t i o n Name Description CommandRef Unique cyclic reference n
40、umber of command. Same value as in related SA-COMMAND. request. SA-CmdConfirm.No Reference number of command. Same value as A-Command.No in related SA-COMMAND. request. SA-CmdConfirm.Value Carries optional confirm data. ErrStatus Error/return code, see Table P.1. An SA-COMMAND.confirm shall be gener
41、ated by the ITS-S application entity upon performance of a previous SA-COMMAND.request in case ErrStatus indicates error or SA-CmdConfirm is present. It may be generated in case ErrStatus indicates success or A-CmdConfirm is not present. On receipt of SA-COMMAND.confirm, ErrStatus and SA-CmdConfirm
42、shall be evaluated and a possible action shall be performed properly. 13.5 SA-REQUEST 13.5.1 SA-REQUESTs Annex T provides an overview and coding details on SA-REQUESTs. ISO 2017 All rights reserved 5 ISO 24102-3:2013/Amd.1:2017(E) SA-REQUESTs shall be enabled by means of the service primitives SA-RE
43、QUEST.request and SA- REQUEST.confirm. 13.5.2 SA-REQUEST.request The management service primitive SA-REQUEST.request allows the ITS-S application entity to trigger an action at the ITS-S management entity. The parameters of SA-REQUEST.request are as follows: SA-REQUEST.request ( CommandRef, SA-Reque
44、st ) Table 39 SA-REQUEST.request Parameter description Name Description CommandRef Unique cyclic reference number of command. SA-Request.No See Annex T. SA-Request.Value See Annex T. An SA-REQUEST.request shall be generated by the ITS-S application entity when the ITS-S management entity shall perfo
45、rm an action. On receipt of SA-REQUEST.request the required action shall be performed. 13 . 5 . 3 S A -R E QU E S T . c on f i r m The service primitive SA-REQUEST.confirm reports the result of a previous SA-REQUEST.request. The parameters of SA-REQUEST.confirm are as follows: SA-REQUEST.confirm ( C
46、ommandRef, SA-ReqConfirm, ErrStatus ) T a b l e 4 0 S A - R E Q U E S T . c o n f i r m P a r a m e t e r d e s c r i p t i o n Name Description CommandRef Unique cyclic reference number of command. Same value as in related SA-REQUEST. request. SA-ReqConfirm.No Reference number of command. Same valu
47、e as SA-Request.No in related SA-REQUEST. request. SA-ReqConfirm.Value Carries optional confirm data. ErrStatus Error/return code, see Table P.1. An SA-REQUEST.confirm shall be generated by the ITS-S management entity upon performance of a previous SA-REQUEST.request in case ErrStatus indicates erro
48、r or SA-ReqConfirm is present. It may be generated in case ErrStatus indicates success or SA-ReqConfirm is not present. On receipt of SA-REQUEST.confirm, ErrStatus and SA-ReqConfirm shall be evaluated and a possible action shall be performed properly. Details are outside the scope of this document.6
49、 ISO 2017 All rights reserved ISO 24102-3:2013/Amd.1:2017(E) Page 23, Conformance Renumber existing Clause 13 to Clause 14. Replace NOTE with the following: NOTE Service access points may become observable and thus testable in PDUs for ITS station-internal management communications specified in ISO 24102-4.Page 24, Annex A Replace the whole Annex A with the following: Annex A (normative) ASN.1 modules A.1 Overview The following ASN.1 module is specified in this annex: CALMmsap ISO (1) standard (0) calm-man
