TECHNICAL SPECIFICATION ISO/TS 742 First edition 2017-03 Intelligent transport systems — Cooperative ITS — ITS station facilities for the transfer of information between ITS stations Systèmes intelligents de transport — ITS coopératifs — Fonctionnalités des stations ITS pour le transfert d’information entre stations ITS Reference number ISO/TS 17429:2017(E) © ISO 2017 ISO/TS 742 9: 01 7(E) COPYRIGHT PROTECTED DOCUMENT © ISO 2017, Published in Switzerland All rights reserved Unless otherwise specified, no part o f 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 o f the requester ISO copyright o ffice Ch de Blandonnet • 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 ISO/TS 742 9: 01 7(E) Contents Page v Introduction vi Scope Normative references Terms and definitions Abbreviated terms Conformance Overview 6.1 Motivations 6.1.1 Communication services 6.1.2 General purpose ITS station facilities layer services 6.1.3 Information sharing services 6.2 Technical specification overview 6.2.1 Architecture elements 6.2.2 ITS-S application processes 6.2.3 Communication Profile Handler (CPH) 10 6.2.4 Facilities Services Handler (FSH) 11 6.2.5 Content Subscription Handler (CSH) 12 6.2.6 Service access points (SAP) 12 6.2.7 Application data unit and protocol data unit 12 General requirements Requirements for the “ITS-S application Processes” 8.1 ITS-S-AP: Requirements for data transmission 13 8.2 ITS-S-AP: Requirements for publishing and subscribing to data objects 13 8.3 ITS-S-AP: Flow type registration 14 8.4 ITS-S-AP: Transmitting data 14 8.5 ITS-S-AP: Receiving data 14 8.6 ITS-S-AP: Publishing data objects 14 8.7 ITS-S-AP: Subscribing to the reception of data objects 15 8.8 ITS-S-AP: Stopping the reception of data objects 15 8.9 ITS-S-AP: Receiving data objects 15 Requirements for the Communication Profile Handler 9.1 CPH: Initialization 15 9.2 CPH: Management o f communication profiles 16 9.2.1 CPH: Communication flow profile parameters 16 9.2.2 CPH: Updating communication flow profile parameters 17 9.2.3 CPH: Reporting communication flow statistics 18 9.3 CPH: Processing data sent by ITS-S application processes 18 9.3.1 CPH: Processing TransmitFlowData instructions 18 9.3.2 CPH: Checking for a corresponding communication flow profile 19 9.3.3 CPH: Checking for an available path 19 9.3.4 CPH: Performing address resolution 19 9.3.5 CPH: Checking for ITS-S facilities services 20 9.3.6 CPH: Transmission to the NF-SAP 20 10 Requirements for the Facilities Services Handler 10.1 FSH: Initialization 20 10.2 FSH: ITS-S facilities layer protocol data unit format (ITS-FPDU) 21 10.3 FSH: Execution of facilities services 21 10.4 FSH: Transmission to the NF-SAP 22 10.5 FSH: Reception of messages 22 Foreword © ISO 2017 – All rights reserved iii ISO/TS 742 9: 01 7(E) 11 Requirements for the Content Subscription Handler 11.1 11.2 11.3 11.4 11.5 11.6 2 CSH: Initialization 22 CSH: processing content publication from ITS-S-AP 23 CSH: processing content subscription from ITS-S-AP 24 CSH: processing content subscription cancellation from ITS-S-AP 24 CSH: transmitting content to ITS-S-AP 24 ITS-S generic data container format 24 12.1 Overview 25 12.2 Error codes 25 12.3 TransmitFlowData 26 12.4 ReceiveFlowData 26 12.5 PublishContent 27 12.6 SubscribeContent 28 12.7 CancelContent 28 12.8 ReceiveContent 29 13 NF-SAP service primitive functions 13.1 ReceiveNTSDU 29 13.2 TransmitNTSDU 30 Annex A (normative) ASN.1 modules Annex B (informative) Bibliography 42 12 FA-SAP service primitive functions iv P r o f i l e s © ISO 2017 – All rights reserved ISO/TS 742 9: 01 7(E) Foreword ISO (the International Organization for Standardization) is a worldwide federation of national standards bodies (ISO member bodies) The work o f 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 o f electrotechnical standardization The procedures used to develop this document and those intended for its further maintenance are described in the ISO/IEC Directives, Part In particular the different approval criteria needed for the di fferent types o f ISO documents should be noted This document was dra fted in accordance with the editorial rules of the ISO/IEC Directives, Part (see www.iso org/directives) Attention is drawn to the possibility that some o f the elements o f this document may be the subject o f patent rights ISO shall not be held responsible for identi fying any or all such patent rights Details o f any patent rights identified during the development o f 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 in formation given for the convenience o f users and does not constitute an endorsement For an explanation on the meaning o f ISO specific terms and expressions related to formity 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: www.iso org/iso/foreword.html The committee responsible for this document is ISO/TC 204, Intelligent transport systems © ISO 2017 – All rights reserved v ISO/TS 742 9: 01 7(E) Introduction ITS station units compliant with the ITS station re ference architecture specified in ISO 21217 may engage in Cooperative ITS (C-ITS) activities involving data exchanges between ITS stations in a variety of roles Such data exchanges include, but are not limited to: — data collected by the roadside in frastructure and transmitted to tra ffic control centers, possibly after aggregation, — roadside equipment configured from the control centers to process a given set o f data or issue messages to vehicles, — roadside events reported to control centers, and — broadcast transmission o f vehicle status and event messages (e.g CAM) to nearby ITS stations An example o f an ITS station unit engaged in a C-ITS activity is a roadside ITS station unit collecting tra ffic-related in formation generated by road sensors and/or by vehicle ITS station units The collected data can o ften serve other purposes than the originally intended one For example, the cooperative awareness message (CAM) from the ETSI C-ITS message set generated for tra ffic-sa fety applications can be collected by roadside ITS station units for exploitation by tra ffic e fficiency applications in tra ffic control centers (e.g central ITS stations) The same in formation is thus used to improve road sa fety, as well as tra ffic e fficiency and also to reduce greenhouse gas emissions The exploitation o f such exchanges for purposes not initially intended is made possible once this exchange o f in formation is per formed in a standardized way through an ITS station facilities layer that is able to recognize messages from specific message sets (e.g DATEX II, TPEG, C-ITS message sets) with data according to data object specifications from data dictionaries (e.g the common ETSI data dictionary) and to forward them to applications which have an interest therein and have subscribed to the delivery o f such message(s) and data A Communication Profile Handler (CPH), a Facilities Services Handler (FSH) and a Content Subscription Handler (CSH) are defined in this Technical Specification to serve this purpose Outside o f this Technical Specification, the commonly used term “message set” is used to indicate a collection o f “messages” used in the exchange o f in formation between peer ITS station units (see ISO/TS 17419) These messages are composed o f structures sometime re ferred to as “data frames” and/or “data objects” which are in turn composed o f objects called “data elements” (see SAE J2735) Herein, a slightly di fferent lexicon is adopted The term “data dictionary” is used to indicate a collection o f “messages”, including “data object” from which the messages are composed Thus, herein, “data objects” are synonymous with “data frames” and “data elements” However, in this Technical Specification, the terms are used with the precise meaning to distinguish messages and data objects from which messages are constructed The functionalities specified in this Technical Specification include a Communication Profile Handler (CPH), a Facilities Services Handler (FSH), and a Content Subscription Handler (CSH) These unctionalities are intended to enable, and be invoked by, technology-agnostic ITS applications and to acilitate the deployment o f C-ITS applications that share in formation In particular, these functionalities f f allow an application to — speci fy a set o f facilities layer services to be applied to its data units (ADUs), — allow ITS station management to select the optimum communication profile (as a function o f time) for any or all o f its data flows, and — publish in formation to and subscribe to in formation from a central repository (the CSH) in a standardized way that enables sharing o f in formation between applications (the definition o f C-ITS) These functionalities provide a toolkit facilitating the specification o f standards and the development of ITS applications [e.g In-Vehicle Signage (ISO/TS 17425), Contextual Speed (ISO/TS 17426), Point of vi © ISO 2017 – All rights reserved ISO/TS 742 9: 01 7(E) I ntere s t, P rob e D ata, I VI , LD M s ynch ron i z ation, remo te I T S s tation figu ration, and I T S appl ic ation s for freight, lo gi s tics , publ ic tran s p or tation, e tc ] complyi ng with the s e t o f C o op erative I T S s tand ard s © ISO 2017 – All rights reserved vii TECHNICAL SPECIFICATION ISO/TS 742 9: 01 7(E) Intelligent transport systems — Cooperative ITS — ITS station facilities for the transfer of information between ITS stations Scope This Technical Specification specifies generic mechanisms enabling the exchange o f in formation between ITS stations for applications related to Intelligent Transport Systems It complies with the ITS station re ference architecture (ISO 21217) and defines the following ITS station facilities layer functionalities: — Communication Profile Handler (CPH); — Content Subscription Handler (CSH); — Facilities Services Handler (FSH) These functionalities are used by ITS-S application processes (ITS-S-AP) to communicate with other ITS-S application processes and share information These functionalities describe — how lower-layer communication services assigned to a given data flow are applied to the service data units at the various layers in the communication protocol stack (CPH, see 6.2.3), — how content from data dictionaries can be published and subscribed to by ITS-S application processes (CSH, see 6.2.5), — how well-known ITS station facilities layer and management services can be applied to application process data units (FSH, see 6.2.4), relieving (ITS-S) application processes from having to implement these services on their own, — how service access points (SAP) primitives specified in ISO 24102-3 are used, — service primitives for the exchange of information between ITS-S application processes and the ITS station facilities layer (FA-SAP), and — a set o f communication requirements and objectives (profiles) using the methods defined in ISO/TS 17423 to select the level o f per formance (best e ffort or real-time, etc.), confidence and security (authentication, encryption, etc.) for in formation exchange between ITS stations, such as data provision, event notification, roadside configuration, map update Normative references The following documents are re ferred to in the text in such a way that some or all o f their content constitutes requirements o f this document For dated re ferences, only the edition cited applies For undated re ferences, the latest edition o f the re ferenced document (including any amendments) applies ISO/TS 17419, Intelligent tran sport system s — Cooperative system s — Classification and management of ITS applications in a global context ISO/TS 17423, Intelligent transport systems — Cooperative systems — ITS application requirements and objectives for selection o f communication profiles ISO 21217, Intelligent transport systems — Communications access for land mobiles (CALM) — Architecture ISO 24102-3, Intelligent transport systems — Communications access for land mobiles (CALM) — ITS station management — Part 3: Service access points © ISO 2017 – All rights reserved ISO/TS 742 9: 01 7(E) ISO 24102-6, Intelligent transport systems — Communications access for land mobiles (CALM) — ITS station management Part 6: Path and flow management Terms and definitions For the pu rp o s e s o f th i s c ument, the fol lowi ng term s and defi nition s apply ITS-S application I TS -S appl ic ation pro ce s s re s id i ng i n the I T S - S appl ic ation entity [SOURCE: ISO 21217:2014, 3.18] 3.2 ITS-S application process ITS-S-AP element in an ITS station that performs information processing for a particular application, and uses ITS-S services to transmit and receive information N o te to entr y: E xa mp le s o f I T S -S app l ic atio n p ro ce s s e s a re co nte x tu a l s p e e d ( I S O/ T S 1742 ) a nd I n-Veh icle Signage (ISO/TS 17425) [SOURCE: ISO 21217:2014, 3.19] 3.3 ITS-S capability ITS-S capabilities un iquely add re s s able pro to col fu nc tiona l ity N o te to entr y: E xa mp le s o f I T S - S c ap abi l itie s a re C o ntent S ub s c r ip tion H a nd ler (C S H ) , Facilities Service Handler (F S H ) , C om mu n ic atio n P ro fi le H a nd ler (C PH ) [SOURCE: ISO 24102-6:2015, 3.6] ITS-S facilities layer protocol data unit ITS-FPDU pro to col data u n it as s emble d b y the Fac i l itie s S er vice s H a nd ler i n the I T S - S ne s te d pro to col data un its exchange d b e twe en p e er fac i l itie s faci l itie s layer s i s ti ng o f layer s er vice s i n I T S - S 3.5 ITS-S communication profile parameterized ITS-S communication protocol stack [SOURCE: ISO/TS 17423:2014, 3.7] ITS-S data container s e quence o f typ e -leng th-va lue ( T LV ) enco de d data obj e c ts ITS-S data header he ader o f the “I T S - S generic data conta i ner format” u niquely identi fyi ng the d ata contai ne d i n the I T S - S data contai ners b y me an s o f data d ic tionar y identi fiers u n ique i n the I T S doma i n and the nu mb er o f data obj e c ts from the data d ic tiona r y i n the conta i ner © ISO 2017 – All rights reserved ISO/TS 742 9: 01 7(E) TransmitNTSDU The service primitive function TransmitNTSDU is used by the ITS-S facilities layer to transmit data (ITS-NTSDU, see Figure 6) to the ITS-S networking and transport layer (i.e for the purpose of transmission to another node) ASN.1 types and for the parameters o f the TransmitNTSDU function shall be as specified in Table 20 with ASN.1 details specified in Annex A NOTE The NF-SAP service primitive functions depend on the protocols (FNTP, IP, GN/BTP) Table — NF-DOWN.request(TransmitN TSDU) I TS -N TSDU Parameters ASN.1 Type FlowI D socket srcI nfo FlowI D Socket socket destI nfo Socket fpdu priority options 30 Description Identifier o f the ITS-S flow the packet belongs to Port number and network address of the source where this packet came from in case a reply must be sent This includes notification o f the transport protocol and network protocol to be used Port number and network address of the destination where this packet must be received This includes notification o f the transport protocol and network protocol to be used FlProtDataUnit Data object transmitted by the ITS-S-AP and possibly modified UserPriority SFoptions by the ITS-S facilities layer Priority o f the transmission request Various per-packet options (TBD) including per packet priority © ISO 2017 – All rights reserved ISO/TS 742 9: 01 7(E) Annex A (normative) ASN.1 modules A.1 Overview The ASN.1 basic notation is specified in ISO/IEC 8824-1:2008 The following ASN.1 modules are specified in this Annex: — ITSitss f { iso (1) standard (0) itss f (17429) asnm-1 (1) version1(1)} In case the ASN.1 specifications given in this Annex are not compliant with illustrations or specifications provided elsewhere in this Technical Specification, the specifications given in this Annex shall prevail Dynamic updates o f this annex will be published on http://standards iso org/iso/ts/17419/ and become an integral part o f this Technical Specification A.2 Module ITSitssf This module specifies ASN.1 type definitions together with use ful ASN.1 value definitions It imports ASN.1 definitions from modules specified in ISO 17419, ISO 21218, ISO 24102-3, SO 24102-6, ISO 17423 NOTE ASN.1 definitions and definitions contained in these standards are currently being aligned in order to ensure consistency Please re fer to the latest revisions (2017) Unaligned packed coding rules (PER) as specified in ISO/IEC 8825-2 shall be applied for this ASN.1 module I TSitssf { iso ( ) standard ( ) itssf ( 9) asnm-1 ( ) version1 ( ) } DEFI NI TI ONS AUTOMATI C TAGS: : =BEGI N I MPORTS EUI 64 , UserPriority, MACaddress FROM CALMllsap { iso( ) standard( ) calm-ll-sap( 2 ) asnm-1 ( ) version1 ( ) } ApplicationI D FROM CALMmanagement { iso ( ) standard ( ) calm-management ( ) local ( ) asnm-1 ( ) version1 ( ) } FlowI D, FlowStatisticsList, DestinationI D, CapaI nfos FROM I TSpfm { iso ( ) standard ( ) calm-management ( ) pfm ( 6) asnm-1 ( ) version1 ( ) } PortNumber FROM CALMfntp { iso ( ) standard ( ) calm-nonip( 92 ) fntp( ) asnm-1 ( ) version1 ( ) } DestinationType FROM CI TSapplReq { iso( ) standard( ) cits-applReq ( 3) asnm-1 ( ) version1 ( ) } I TSaid FROM CI TSapplMgmtApplReg { iso( ) standard( ) cits-applMgmt ( 9) applRegistry ( ) version1 ( ) } ; –- End of IMPORTS –- Types © ISO 2017 – All rights reserved 31 ISO/TS 742 9: 01 7(E) –- TransmitFlowData TransmitFlowData : : = SEQUENCE{ fowID appI D adu options } FlowID, ApplicationI D, AppProtDataUnit, SFoptions AppProtDataUnit : : = OCTET STRI NG SFoptions : : = SEQUENCE SI ZE( 56) OF SFoption TransmitFlowDataConf : : = SEQUENCE{ error SFerror, options SFoptions } SFerror : : = I NTEGER{ sfErrOK sfErr OKPATHCONGESTED sfErrFLOWNOTREGISTERED sfErrPATHUNAVAILABLE sfErrNOTAUTHORIZED sfErrNOSECU sfErrINVALID-PORT sfErrINVALID-DEST sfErrINVALID-SERV sfErrUNAVAILABLE-SERV sfErrINVALID } (0 255) –- ReceiveFlowData ReceiveFlowData : : = appI D adu srcPort destPort servFac servSec options } (0) , (1) , (2) , ( 3) , (4) , ( 5) , ( 6) , (7) , (8) , ( 9) , (10) SEQUENCE{ ApplicationI D, AppProtDataUnit, PortNumber, PortNumber, CapaI nfos, CapaI nfos, SFoptions –- PublishContent PublishContent : : = SEQUENCE{ fowID appI D data options credentials } FlowID, ApplicationI D, DataFromDDs, SFoptions, PubContCredentials PubContCredentials : : = OCTET STRI NG PublishContentConf : : = SEQUENCE{ error SFerror } –- SubscribeContent SubscribeContent : : = SEQUENCE{ appI D ApplicationI D, ddI D DataDictI D, doI D I NTEGER, credentials PubContCredentials } SubscribeContentConf : : = SEQUENCE{ error SFerror } 32 © ISO 2017 – All rights reserved ISO/TS 742 9: 01 7(E) –- CancelContent CancelContent : : = SEQUENCE{ appI D ApplicationI D, ddI D DataDictI D, doI D I NTEGER } CancelContentConf : : = SEQUENCE{ error SFerror } –- ReceiveContent ReceiveContent : : = SEQUENCE { appI D ApplicationI D, data DataFromDDs, options SFoptions } –- ReceiveNTSDU ReceiveNTSDU : : = SEQUENCE{ adu AppProtDataUnit, socket I tsSocket } I tsSocket : : = SEQUENCE{ srcI nfo Socket, -– source port number and network address destI nfo Socket -– destination port number and network address } Socket : : = SEQUENCE{ tProtAddress TprotAddress, nProtAddress NprotAddress } –- TransmitNTSDU TransmitNTSDU : : = SEQUENCE{ fowID socket fpdu priority options } FlowID, I tsSocket, FlProtDataUnit, UserPriority, SFoptions FlProtDataUnit : : = OCTET STRI NG –- ITS facilities layer protocol data unit Fpdu : : = SEQUENCE{ version serviceNos services srcFacAddr dstFacAddr data } I NTEGER( ) , I NTEGER( 31 ) , ServiceFacs, FacAddr, FacAddr, FpduData FacAddr : : = ApplicationI D FpduData : : = OCTET STRI NG –- Other types CfpPathAvailability: : = I NTEGER{ cphPAnoPathSelected (0) , cphAPpathsCongested (1) , cphAPathLeastOne ( 55) © ISO 2017 – All rights reserved 33 ISO/TS 742 9: 01 7(E) } ( 55) CfpMaxFpdu : : = I NTEGER( 65535) –- Dynamic Updates –- Instantiations of CLASS obj ects –- SF-OPTION CLASS SFoptionI D : : = I NTEGER{ sFoptNone (0) } SF-OPTI ON : : = CLASS{ &id SFoptionI D UNI QUE, &Type } WI TH SYNTAX { &Type SELECTED BY &id} SFoption : : = SEQUENCE{ sfOptI D SF-OPTI ON &id( { SFoptionTypes} ) , option SF-OPTI ON &Type( { SFoptionTypes} { @ sfOptI D} ) } –- Dynamic elements of SF-OPTI ON SFoptionTypes SF-OPTI ON : : = { { SFoptionNone SELECTED BY sFoptNone} , } SFoptionNone : : = NULL –- SERV-FAC CLASS ServFacI D : : = I NTEGER{ servFacNone (0) , servFacCSH (1) } ( 55) SERV-FAC : : = CLASS{ &id ServFacI D UNI QUE, &Type } WI TH SYNTAX { &Type SELECTED BY &id} ServiceFacs : : = SEQUENCE SI ZE( 63) OF ServFac ServFac : : = SEQUENCE{ serfFacI D SERV-FAC &id( { ServFacTypes} ) , serfFac SERV-FAC &Type( { ServFacTypes} { @ serfFacI D} ) } –- Dynamic elements of SERV-FAC ServFacTypes SERV-FAC: : = { { ServFacNone SELECTED BY servFacNone} | { ServFacCSH SELECTED BY servFacCSH} , } ServFacNone : : = NULL –- this is the empty service header ServFacCSH : : = DataFromDDs –- DATA-DICT CLASS DataDictI D : : = I NTEGER{ dataDictLdm1 50 (0) } –- is siz e constraint needed? 34 © ISO 2017 – All rights reserved ISO/TS 742 9: 01 7(E) DATA-DI CT : : = CLASS{ &id DataDictI D UNI QUE, &Type } WI TH SYNTAX { &Type SELECTED BY &id} DataFromDDs : : = SEQUENCE SI ZE( 56) OF DataFromDD DataFromDD : : = SEQUENCE{ dataDictI D DATA-DI CT &id( { DataDictionaryTypes} ) , dataFromDict DATA-DI CT &Type( { DataDictionaryTypes} { @ dataDictI D} ) } DataDictionaryTypes DATA-DI CT: : = { { DataObj ectsLDM1 50 SELECTED BY dataDictLdm1 50 } , } /* DOidentifer : : = INTEGER */ DOldm1 50 I D : : = I NTEGER { doLdm1 50 NullType ( ) –- this is a dummy value not to be used! } –- data obj ect I D for all data dictionaries must be of type I NTEGER DO-LDM1 50 : : = CLASS{ &id DOldm1 50 I D UNI QUE, &Type } WI TH SYNTAX { &Type SELECTED BY &id} DataObj ectsLDM1 50 : : = SEQUENCE SI ZE( 56) OF DataObj ectLDM1 50 DataObj ectLDM1 50 : : = SEQUENCE{ dataObj I D DO-LDM1 50 &id( { DOldm1 50 Types} ) , dataFromDict DO-LDM1 50 &Type( { DOldm1 50 Types} { @ dataObj I D} ) } DOldm1 50 Types DO-LDM1 50 : : = { { NullTypeDO SELECTED BY doLdm1 50 NullType} , } NullTypeDO : : = NULL –- TPROT CLASS TprotI D : : = I NTEGER{ tProtFntpPort tProtFntpI tsaid tProtTcp tProtUdp } ( 55) (0) , (1) , (2) , ( 3) TPROT : : = CLASS{ &id TprotI D UNI QUE, &Type } WI TH SYNTAX { &Type SELECTED BY &id} TprotAddress : : = SEQUENCE{ protI D TPROT &id( { TprotTypes} ) , protAddress TPROT &Type( { TprotTypes} { @ protI D} ) } –- Dynamic elements of TPROT TprotTypes TPROT : : = { { FntpPort SELECTED BY tProtFntpPort} | © ISO 2017 – All rights reserved 35 ISO/TS 742 9: 01 7(E) { FntpI tsaid { TcpPort { UdpPort } SELECTED BY tProtFntpI tsaid} | SELECTED BY tProtTcp} | SELECTED BY tProtUdp} , FntpPort : : = PortNumber FntpI tsaid : : = I TSaid TcpPort : : = I NTEGER ( 65535) UdpPort : : = I NTEGER ( 65535) –- NPROT CLASS NprotI D : : = I NTEGER{ nProtFntpMac (0) , nProtI Pv6 (2) } ( 55) NPROT : : = CLASS{ &id NprotI D UNI QUE, &Type } WI TH SYNTAX { &Type SELECTED BY &id} NprotAddress : : = SEQUENCE{ protI D NPROT &id( { NprotTypes} ) , protAddress NPROT &Type( { NprotTypes} { @ protI D} ) } – Dynamic elements of NPROT NprotTypes NPROT : : = { { NProtFntpMac SELECTED BY nProtFntpMac} | { NProtI Pv6 SELECTED BY nProtI Pv6} , } NProtFntpMac : : = MACaddress NProtI Pv6 : : = EUI 64 END 36 © ISO 2017 – All rights reserved ISO/TS 742 9: 01 7(E) Annex B (informative) P r o f i l e s This Annex illustrates the communication requirements parameters presented by di fferent types o f ITS-S application processes and provided to the ITS station management entity at time o f flow type registration as defined in ISO 24102-6 The set o f parameters is as defined in ISO/TS 17423:2014 NOTE The published version of ISO/TS 17423:2014 is under revision in order to be aligned with ISO 24102-6 and this Technical Specification so there are discrepancies between the content o f Tables B.1 to B.3 and the content o f the tables in ISO/TS 17423:2014; once the revision o f ISO/TS 17423:2014 is achieved, the parameters presented in Tables B.1 to B.3 will be slightly modified and new fields will probably be added B.1 Transmission of broadcast safety message from the CSH or an application Table B.1 presents the parameters used for the ITS-S flow corresponding to broadcast messages sent either from the Content Subscription Handler or an ITS-S application process installed on a roadside ITS station to nearby vehicle ITS stations The intended usage in this example is the 5,9 GHz access technology using the communication channel reserved for sa fety messages Examples include messages defined for In-Vehicle Signage (ISO/TS 17425), Contextual Speed (ISO/TS 17426), Signal Phase and Timing (SPAT) (ISO/TS 19091) The data content is formatted as defined in 11.6 The content of the payload field o f the ITS-S data container is defined in relevant standards, as for instance the ones indicated above The ITS-FPDU is formatted as indicated in 10.2 Table B — Communication parameters for a safety broadcast message C o m m u n i c a t i o n f l o w requirements Value Comment (ASN.1 type) ApplicationI D Identifiers for the ITS-S flow type registration Identifier o f the ITS-S application process realizing the ITS-S flow type registration ID of CSH or ID of the application request FlowTypeI D N/A LogicalChannelType ContConnect case for the time being) Operational communication service parameters SfCH Sa fety channel N/A No continuous connectivity needed for a broadcast 255, 0,5 s A transmission is expected once every hal f sec- NxRepeat StoreAndForward Priority PortNo N/A Maximum Rx: Tx: PORT_FSH PORT_FSH © ISO 2017 – All rights reserved Not presented unless ITS-S flow type parame ters are registered in a global registry (not the ond (0,5) until the ITS-S flow is cancelled (255) No store and forward capability needed Maximum since sa fety-related message PORT_FSH is used because ITS-S facilities services are requested by the ITS-S application process The message is thus formatted using the ITS-S data header and the ITS-S data container 37 ISO/TS 742 9: 01 7(E) Table B C o m m u n i c a t i o n f l requirements (ASN.1 type) DestType DestDomain CommDistance Multihop o (continued) w Value Comment Destination communication service parameters (GeoLocationBasedType ) Broadcast to geographical area (geoBroadcast)/ (siteLocal ) Messages are transmitted to a limited geographic area limited by the coverage range of the source 500 m Minimum distance at which vehicles are supposed to receive the message N/A Not needed since recipients are not expected to relay the message Resilience Omnidirectional Performance communication service parameters N/A Requesting increase of likelihood of proper MinThP MaxLat MaxADU × NxRepeat (ms100) Directivity delivery is not needed for a broadcast message sent over o f sa fety channel Meaningless for repeated broadcast services Maximum acceptable latency o f 100 ms, parameter not necessarily needed as the message is a broadcast and is known as high MaxADU (multiples o f 100 byte) priority anyway 100 is an example Value depends on the exact content of the message but should be short for a sa fety message ITS-S facilities services to be applied by the Facilities Services Handler (FSH) CapaI nfos DataIntegrity/NonRepudiation Security services provided by the ITS-S (security services) /SourceAuthentication security layer are called by the FSH CapaI nfos TimeStamping (this is just an Generic security services provided by ITS-S (facilities services) example o f service; CapaIn fos capabilities in the ITS-S facilities layer are allows to provide a list) called by the FSH Protocol Protocol communication service parameters N/A The choice of the protocol stack (transport, network, access technology) is le ft to the ITS-S management entity so that this Technical Specification is generically applicable to road- side ITS-S implemented with distinct protocol stacks according to regional decisions B.2 Transmission of data from a proprietary application to a server Table B.2 below presents the communication requirements corresponding to a large point-to-point data exchange between a proprietary client application installed on a vehicle and the corresponding proprietary server application reachable through the Internet (for instance, a so ftware update, map update, etc.) Among other requirements, this data exchange requires session continuity and confidentiality As a result o f providing such communication requirements, the ITS-S management entity will determine the appropriate communication profile and in form the ITS-S facilities layer (CPH) The ITS-S management entity will ensure session continuity is maintained between the vehicle and the server while the vehicle is moving using any available access technology (urban WiFi, vehicular WiFi, cellular, etc.), possibly combined so that the loss o f connectivity using one access technology is recovered by the use o f another access technology, without breaking up the ongoing data trans fer Session continuity will 38 © ISO 2017 – All rights reserved ISO/TS 742 9: 01 7(E) e ffectively be maintained by the ITS-S network and transport layer (IPv6, as specified in ISO 21210) following the instructions o f the ITS-S management entity as specified in ISO 24120-6 The data content format is proprietary to the application, and none o f the ITS-S facilities services are requested, even for security which is implemented directly in the application (thereo f, the security services are marked as “not requested”) The FSH is thus not used, and the ADU is not modified in the ITS-S facilities layer (no need to create an ITS-FPDU as indicated in 10.2 Packets are thus not transferred via the port PORT_FSH Table B — Communication parameters for a proprietary data transfer C o m m u n i c a t i o n f l o w requirements Value Comment (ASN.1 type) Identifiers for the flow type registration Identifier o f the ITS-S application process realizing the flow type registration request Not presented unless flow parameters are registered in a global registry (not the case for ApplicationI D ID of the application FlowTypeI D N/A LogicalChannelType ContConnect NxRepeat StoreAndForward Priority PortNo DestType DestDomain CommDistance Multihop Directivity Resilience MinThP MaxLat MaxADU the time being) Operational communication service parameters GPCH General purpose channel 10 (just an example of Continuous connectivity needed/an maximum estimated duration) estimated duration of the transmission is given as an indication for better selection of the communication profile by the ITS station management No repetition o f data for file trans fer N/A No store and forward capability needed N/A Best e ffort is su fficient Rx: any Tx: any Port requested by the application Destination communication service parameters (AddressBasedType)/ Unicast address in the Internet (unicast) (global) Server reachable in the Internet N/A N/A as server reachable in the Internet N/A Not needed since recipients are not expected to relay the message Omnidirectional Performance communication service parameters N/A Requesting increase of likelihood of proper (any) 65535 (multiples o f 100 byte) delivery is not necessary No speci fy transmission rate is needed Any latency is acceptable Maximum size of the data exchanged (maximum file size, etc.) ITS-S facilities services to applied by the Facilities Services Handler (FSH) CapaI nfos (security None The application uses directly the security services) services o ffered by the ITS-S security entity © ISO 2017 – All rights reserved 39 ISO/TS 742 9: 01 7(E) Table B C o m m u n i c a t i o n f l o w requirements Value (ASN.1 type) CapaI nfos services) (continued) (facilities None Comment The application does not use any ITS-S facilities service Protocol communication service parameters N/A Choice of the protocol stack (transport, Protocol network, access technology) is le ft to the ITS-S management entity so that the International Standard is generically applicable to roadside ITS-S implemented with distinct protocol stacks according to regional decisions In a regional deployment, the ITS station management entity can be statically configured to select a given communication profile (e.g FNTP/M5, GeoNet/G5, WSMP/11p) B.3 Transmission of probe data from a proprietary application to a server Table B.3 presents the communication requirements corresponding to a continuous point-to-point small data exchange between a proprietary client application installed in ITS station (roadside or vehicle ITS station) and the corresponding proprietary server application reachable through the Internet (for instance, probe data, etc.) Among other requirements, this data exchange requires confidentiality, time stamping, geo-stamping Session continuity is not necessary, but connectivity is expected to be relatively continuous As a result o f providing such communication requirements, the ITS-S management entity will determine the appropriate communication profile and in form the ITS-S facilities layer (CPH) The ITS-S management entity will ensure the data are trans ferred to the server using any available access technology (urban WiFi, vehicular WiFi, cellular, etc.), possibly combined so that the loss o f connectivity using one access technology is recovered by the use o f another access technology Connectivity will e ffectively be managed by the ITS-S network and transport layer (IPv6, as specified in ISO 21210) following the instructions o f the ITS-S management entity as specified in ISO 24120-6 The data content format is proprietary to the application, but the application requests the use o f ITS-S acilities services simpli fying the design o f the application In this example, the application relies on the ITS-S facilities layer to apply security services and for time stamping and geo-stamping each probe f data The ITS-FPDU is formatted as indicated in 10.2 Table B — Communication parameters for a proprietary probe data C o m m u n i c a t i o n f l o w requirements Value Comment (ASN.1 type) Identifiers for the flow type registration Identifier o f the ITS-S application process realizing the flow type registration request Not presented unless flow parameters are registered in a global registry (not the case for ApplicationI D ID of the application FlowTypeI D N/A LogicalChannelType the time being) Operational communication service parameters GPCH General purpose channel 40 © ISO 2017 – All rights reserved ISO/TS 742 9: 01 7(E) Table B C o m m u n i c a t i o n f l o (continued) w requirements (ASN.1 type) ContConnect NxRepea t StoreAndForward Priority PortNo DestType DestDomain CommDistance Multihop Directivity Resilience Value Comment 10 (just an example of Continuous connectivity not needed/an maximum estimated duration) estimated duration of the transmission is given as an indication for better selection of the communication profile by the ITS station management No repetition of data for probe data N/A No store and forward capability needed N/A Best e ffort is su fficient Rx: any Tx: any Port requested by the application Destination communication service parameters (AddressBasedType )/ Unicast address in the Internet (unicast ) (global ) Server reachable in the Internet N/A N/A as server reachable in the Internet N/A Not needed since recipients are not expected to relay the message Omnidirectional Performance communication service parameters N/A Requesting increase of likelihood of proper delivery is not necessary No speci fy transmission rate is needed Any latency is acceptable MinThP MaxLat MaxADU (any) 10 (multiples o f 100 byte) Protocol provide a list) Protocol communication service parameters N/A Choice of the protocol stack (transport, Maximum size of the data exchanged (maximum file size, etc) ITS-S facilities services to applied by the Facilities Services Handler (FSH) CapaI nfos DataIntegrity/NonRepudiation Security services provided by the ITS-S (security services) /SourceAuthentication security layer are called by the FSH CapaI nfos TimeStamping/GeoStamping Generic security services provided by ITS-S (facilities services) (this is just an example of capabilities in the ITS-S facilities layer are service; CapaIn fos allows to called by the FSH network, access technology) is le ft to the ITS-S management entity so that the International Standard is generically applicable to roadside ITS-S implemented with distinct protocol stacks according to regional decisions © ISO 2017 – All rights reserved 41 ISO/TS 742 9: 01 7(E) Bibliography [1] ISO/TS 17425, Intelligent tran sport system s — Cooperative system s — Data exchange specification [2] [3] [4] [5] ISO/TS 17426, Intelligent transport systems — Cooperative systems — Contextual speeds ISO/TR 17465-1, Intelligent tran sport system s — Cooperative ITS — Part : Term s and definition s ISO 18750, Intelligent transport systems — Cooperative ITS — Local dynamic maps ISO/TS 19091, Intelligent transport systems — Cooperative ITS — Using V2I and I2V communications [6] ISO 19321, Intelligent transport systems — Cooperative ITS — Dictionary of in-vehicle information (IVI) data structures [7] [8] [9] for in-vehicle presentation o f external road and tra ffic related data for applications related to signalized intersections ISO 20594-1, Intelligent tran sport system s — Cooperative system s — Test specification s TS 17429 — Part 1: Protocol implementation conformance statement (PICS) proforma for ISO 20594-2, Intelligent tran sport system s — Cooperative system s — Test specification s for TS 17429 — Part 2: Test suite structure and test purposes (TSS&TP) ISO 20594-3, Intelligent tran sport system s — Cooperative system s — Test specification s for TS 17429 — Part 3: Abstract test suite (ATS) and partial PIXIT proforma [10] ISO 21213, Intelligent transport systems — Communications access for land mobiles (CALM) — 3G cellular systems [11] ISO 21215, Intelligent transport systems — Communications access for land mobiles (CALM) — M5 [12] ISO 24102-2, Intelligent transport systems — Communications access for land mobiles (CALM) — ITS station management — Part 2: Remote management of ITS-SCUs [13] ISO 24102-4, Intelligent transport systems — Communications access for land mobiles (CALM) — ITS station management — Part 4: Station-internal management communications [14] ISO 24102-5, Intelligent transport systems — Communications access for land mobiles (CALM) — ITS station management — Part 5: Fast service advertisement protocol (FSAP) [15] ETSI/TS 102 637-2, Intelligent Transport Systems (ITS) — Vehicular Communications — Basic Set o f Application s — Part 2: Specification s o f Cooperative Awareness Basic Service [16] ETSI/TS 102 637-3, Intelligent Transport Systems (ITS) — Vehicular Communications — Basic Set o f Application s — Part 3: Specification s o f Decentralized Environmental Notification Basic Service [17] ETSI/TS 102 723-9, Intelligent Transport Systems (ITS); OSI cross-layer topics; Part 9: Interface between security entity and facilities layer [18] SAE J2735, Dedicated Short Range Communications (DSRC) Message Set Dictionary version published in November 2009 [19] ISO 21218, Intelligent transport systems — Communications access for land mobiles (CALM) — Access technology support [20] ISO/IEC 8825-2, In formation technology — ASN.1 encoding rules: Specification of Packed Encoding Rules (PER) — Part [21] ISO/IEC 8824-1:2008, In formation technology Specification o f basic notation — Part 42 — Abstract Syntax Notation One (ASN.1): © ISO 2017 – All rights reserved ISO/TS 742 9: 01 7(E) ICS 03.220.01; 35.240.60 Price based on 42 pages © ISO 2017 – All rights reserved