"value":"The <i xmlns=\"http://www.w3.org/1999/xhtml\">protocolVersion<\/i> (defined in the header) of IVIM message based on the present document is set to value \"1\"."
"value":"The <i xmlns=\"http://www.w3.org/1999/xhtml\">protocolVersion<\/i> (defined in the header) of SSEM based on the present document is set to value \"1\"."
"value":"The <i xmlns=\"http://www.w3.org/1999/xhtml\">protocolVersion<\/i> (defined in the header) of SREM based on the present document is set to value \"1\"."
<pclass="fP">The present document may be made available in electronic versions and/or in print. The content of any electronic and/or print versions of the present document shall not be modified without the prior written authorization of ETSI. In case of any existing or perceived difference in contents between such versions and/or in print, the only prevailing document is the print of the Portable Document Format (PDF) version kept on a specific network drive within ETSI Secretariat.</p>
<pclass="fP">Users of the present document should be aware that the document may be subject to revision or change of status. Information on the current status of this and other ETSI documents is available at <ahref="https://portal.etsi.org/TB/ETSIDeliverableStatus.aspx">https://portal.etsi.org/TB/ETSIDeliverableStatus.aspx</a>
</p>
<pclass="fP">If you find errors in the present document, please send your comment to one of the following services:<br/>
<pclass="fP">If you find errors in the present document, please send your comment to one of the following services:<br/>
<pclass="fP">Reproduction is only permitted for the purpose of standardization work undertaken within ETSI.<br/>The copyright and the foregoing restrictions extend to reproduction in all media.</p>
<pclass="fP"></p>
<pclass="fP">Reproduction is only permitted for the purpose of standardization work undertaken within ETSI.<br/>The copyright and the foregoing restrictions extend to reproduction in all media.</p>
<aname="For_tbname"></a>IPRs essential or potentially essential to the present document may have been declared to ETSI. The information pertaining to these essential IPRs, if any, is publicly available for <b>ETSI members and non-members</b>, and can be found in ETSI SR 000 314: <i>"Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in respect of ETSI standards"</i>, which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web server (<ahref="https://ipr.etsi.org/">https://ipr.etsi.org/</a>).</p>
<aname="For_tbname"/>IPRs essential or potentially essential to the present document may have been declared to ETSI. The information pertaining to these essential IPRs, if any, is publicly available for <b>ETSI members and non-members</b>, and can be found in ETSI SR 000 314: <i>"Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in respect of ETSI standards"</i>, which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web server (<ahref="https://ipr.etsi.org/">https://ipr.etsi.org/</a>).</p>
<p>Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No guarantee can be given as to the existence of other IPRs not referenced in ETSI SR 000 314 (or the updates on the ETSI Web server) which are, or may be, or may become, essential to the present document.</p>
<h1>
<aname="_Toc442882189"></a>
<aname="_Toc442882418"></a>
<aname="_Toc442965231"></a>
<aname="_Toc455389573"></a>Foreword</h1>
<aname="_Toc442882189"/>
<aname="_Toc442882418"/>
<aname="_Toc442965231"/>
<aname="_Toc455389573"/>Foreword</h1>
<p>This Technical Specification (TS) has been produced by ETSI Technical Committee Intelligent Transport Systems (ITS).</p>
<p>The present document includes the integration of infrastructure based application protocols within the ITS message environment.</p>
<p>In the present document "<b>shall</b>", "<b>shall not</b>", "<b>should</b>", "<b>should not</b>", "<b>may</b>", "<b>need not</b>", "<b>will</b>", "<b>will not</b>", "<b>can</b>" and "<b>cannot</b>" are to be interpreted as described in clause 3.2 of the <ahref="https://portal.etsi.org/Services/editHelp%21/Howtostart/ETSIDraftingRules.aspx">ETSI Drafting Rules</a> (Verbal forms for the expression of provisions).</p>
<p>"<b>must</b>" and "<b>must not</b>" are <b>NOT</b> allowed in ETSI deliverables except when used in direct citation.</p>
<h1>
<aname="_Toc442882191"></a>
<aname="_Toc442882420"></a>
<aname="_Toc442965233"></a>
<aname="_Toc455389575"></a>Introduction</h1>
<aname="_Toc442882191"/>
<aname="_Toc442882420"/>
<aname="_Toc442965233"/>
<aname="_Toc455389575"/>Introduction</h1>
<p>The infrastructure services are application support facilities provided by the Facilities layer that construct, manage and process messages distributed from infrastructure to end-users or vice-versa based on payload received from the application. The infrastructure services specified in the present document support infrastructure-based applications in order to achieve communication interoperability, and may be implemented in parallel to other services in an ITS-S.</p>
<p>
<br/>
<br/>
</p>
<h1>
<aname="_Toc442882192"></a>
<aname="_Toc442882421"></a>
<aname="_Toc442965234"></a>
<aname="_Toc455389576"></a>1 Scope</h1>
<aname="_Toc442882192"/>
<aname="_Toc442882421"/>
<aname="_Toc442965234"/>
<aname="_Toc455389576"/>1 Scope</h1>
<p>The present document provides specifications of infrastructure related ITS services to support communication between infrastructure ITS equipment and traffic participants using ITS equipment (e.g. vehicles, pedestrians). It defines services in the Facilities layer for communication between the infrastructure and traffic participants. The specifications covers the protocol handling for infrastructure-related messages as well as requirements to lower layer protocols and to the security entity.</p>
<p>References are either specific (identified by date of publication and/or edition number or version number) or nonspecific. For specific references, only the cited version applies. For non-specific references, the latest version of the reference document (including any amendments) applies.</p>
<p>Referenced documents which are not found to be publicly available in the expected location might be found at <ahref="https://docbox.etsi.org/Reference/">https://docbox.etsi.org/Reference/</a>.</p>
<pclass="nO">NOTE: While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee their long term validity.</p>
<p>The following referenced documents are necessary for the application of the present document.</p>
<pclass="eX">
<aname="REF_EN302665"></a>[1] ETSI EN 302 665 (V1.1.1): "Intelligent Transport Systems (ITS); Communications Architecture".</p>
<aname="REF_EN302665"/>[1] ETSI EN 302 665 (V1.1.1): "Intelligent Transport Systems (ITS); Communications Architecture".</p>
<pclass="eX">
<aname="REF_TS102894_2"></a>[2] ETSI TS 102 894-2 (V1.2.1): "Intelligent Transport Systems (ITS); Users and applications requirements; Part 2: Applications and facilities layer common data dictionary".</p>
<aname="REF_TS102894_2"/>[2] ETSI TS 102 894-2 (V1.2.1): "Intelligent Transport Systems (ITS); Users and applications requirements; Part 2: Applications and facilities layer common data dictionary".</p>
<pclass="eX">
<aname="REF_EN302636_4_1"></a>[3] ETSI EN 302 636-4-1 (V1.2.1): "Intelligent Transport Systems (ITS); Vehicular Communications; GeoNetworking; Part 4: Geographical addressing and forwarding for point-to-point and pointtomultipoint communications; Sub-part 1: Media-Independent Functionality".</p>
<aname="REF_EN302636_4_1"/>[3] ETSI EN 302 636-4-1 (V1.2.1): "Intelligent Transport Systems (ITS); Vehicular Communications; GeoNetworking; Part 4: Geographical addressing and forwarding for point-to-point and pointtomultipoint communications; Sub-part 1: Media-Independent Functionality".</p>
<pclass="eX">
<aname="REF_EN302636_5_1"></a>[4] ETSI EN 302 636-5-1 (V1.2.1): "Intelligent Transport Systems (ITS); Vehicular Communications; GeoNetworking; Part 5: Transport Protocols; Sub-part 1: Basic Transport Protocol".</p>
<aname="REF_EN302636_5_1"/>[4] ETSI EN 302 636-5-1 (V1.2.1): "Intelligent Transport Systems (ITS); Vehicular Communications; GeoNetworking; Part 5: Transport Protocols; Sub-part 1: Basic Transport Protocol".</p>
<pclass="eX">
<aname="REF_EN302636_6_1"></a>[5] ETSI EN 302 636-6-1 (V1.2.1): "Intelligent Transport Systems (ITS); Vehicular Communications; GeoNetworking; Part 6: Internet Integration; Sub-part 1: Transmission of IPv6 Packets over GeoNetworking Protocols ".</p>
<aname="REF_EN302636_6_1"/>[5] ETSI EN 302 636-6-1 (V1.2.1): "Intelligent Transport Systems (ITS); Vehicular Communications; GeoNetworking; Part 6: Internet Integration; Sub-part 1: Transmission of IPv6 Packets over GeoNetworking Protocols ".</p>
<pclass="eX">
<aname="REF_TS103097"></a>[6] ETSI TS 103 097 (V1.2.1): "Intelligent Transport Systems (ITS); Security; Security header and certificate formats".</p>
<aname="REF_TS103097"/>[6] ETSI TS 103 097 (V1.2.1): "Intelligent Transport Systems (ITS); Security; Security header and certificate formats".</p>
<pclass="eX">
<aname="REF_CENISOTS19321_2015"></a>[7] CEN ISO/TS 19321-2015: "Intelligent transport systems – Cooperative ITS – Dictionary of in-vehicle information (IVI) data structures".</p>
<aname="REF_CENISOTS19321_2015"/>[7] CEN ISO/TS 19321-2015: "Intelligent transport systems – Cooperative ITS – Dictionary of in-vehicle information (IVI) data structures".</p>
<pclass="eX">
<aname="REF_CENISOTS19091"></a>[8] CEN ISO/TS 19091: "Intelligent transport systems - Cooperative ITS - Using V2I and I2V communications for applications related to signalized intersections".</p>
<aname="REF_CENISOTS19091"/>[8] CEN ISO/TS 19091: "Intelligent transport systems - Cooperative ITS - Using V2I and I2V communications for applications related to signalized intersections".</p>
<pclass="eX">
<aname="REF_EN302931"></a>[9] ETSI EN 302 931 (V1.1.1): "Intelligent Transport Systems (ITS); Vehicular Communications; Geographical Area Definition".</p>
<aname="REF_EN302931"/>[9] ETSI EN 302 931 (V1.1.1): "Intelligent Transport Systems (ITS); Vehicular Communications; Geographical Area Definition".</p>
<pclass="eX">
<aname="REF_ISOTS17427"></a>[10] ISO/TS 17427:2014: "Intelligent transport systems - Cooperative systems - Roles and responsibilities in the context of cooperative ITS based on architecture(s) for cooperative systems".</p>
<aname="REF_ISOTS17427"/>[10] ISO/TS 17427:2014: "Intelligent transport systems - Cooperative systems - Roles and responsibilities in the context of cooperative ITS based on architecture(s) for cooperative systems".</p>
<pclass="eX">
<aname="REF_TS102723_5"></a>[11] ETSI TS 102 723-5 (V1.1.1): "Intelligent Transport Systems (ITS); OSI cross-layer topics; Part 5: Interface between management entity and facilities layer".</p>
<aname="REF_TS102723_5"/>[11] ETSI TS 102 723-5 (V1.1.1): "Intelligent Transport Systems (ITS); OSI cross-layer topics; Part 5: Interface between management entity and facilities layer".</p>
<aname="REF_EN302637_2"></a>[13] ETSI EN 302 637-2 (V1.3.2): "Intelligent Transport Systems (ITS); Vehicular Communications; Basic Set of Applications; Part 2: Specification of Cooperative Awareness Basic Service".</p>
<aname="REF_EN302637_2"/>[13] ETSI EN 302 637-2 (V1.3.2): "Intelligent Transport Systems (ITS); Vehicular Communications; Basic Set of Applications; Part 2: Specification of Cooperative Awareness Basic Service".</p>
<pclass="eX">
<aname="REF_EN302637_3"></a>[14] ETSI EN 302 637-3 (V1.2.2): "Intelligent Transport Systems (ITS); Vehicular Communications; Basic Set of Applications; Part 3: Specifications of Decentralized Environmental Notification Basic Service".</p>
<aname="REF_EN302637_3"/>[14] ETSI EN 302 637-3 (V1.2.2): "Intelligent Transport Systems (ITS); Vehicular Communications; Basic Set of Applications; Part 3: Specifications of Decentralized Environmental Notification Basic Service".</p>
<pclass="eX">
<aname="REF_ISO17419"></a>[15] ISO TS17419 V2016-02-09: "ITS-AID_AssignedNumbers" (<ahref="http://standards.iso.org/iso/ts/17419/TS17419%20Assigned%20Numbers/TS17419_ITS-AID_AssignedNumbers.pdf">http://standards.iso.org/iso/ts/17419/TS17419%20Assigned%20Numbers/TS17419_ITS-AID_AssignedNumbers.pdf</a>)</p>
<aname="REF_ISO17419"/>[15] ISO TS17419 V2016-02-09: "ITS-AID_AssignedNumbers" (<ahref="http://standards.iso.org/iso/ts/17419/TS17419%20Assigned%20Numbers/TS17419_ITS-AID_AssignedNumbers.pdf">http://standards.iso.org/iso/ts/17419/TS17419%20Assigned%20Numbers/TS17419_ITS-AID_AssignedNumbers.pdf</a>)</p>
<pclass="eX">
<aname="REF_TS103248"></a>[16] ETSI TS 103 248 (V1.0.0): "Intelligent Transport Systems (ITS); GeoNetworking; Port Numbers for the Basic Transport Protocol (BTP)".</p>
<pclass="eX"></p>
<aname="REF_TS103248"/>[16] ETSI TS 103 248 (V1.0.0): "Intelligent Transport Systems (ITS); GeoNetworking; Port Numbers for the Basic Transport Protocol (BTP)".</p>
<p>References are either specific (identified by date of publication and/or edition number or version number) or nonspecific. For specific references, only the cited version applies. For non-specific references, the latest version of the reference document (including any amendments) applies.</p>
<pclass="nO">NOTE: While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee their long term validity.</p>
<p>The following referenced documents are not necessary for the application of the present document but they assist the user with regard to a particular subject area.</p>
<pclass="eX">
<aname="REF_TR102965"></a>[i.1] ETSI TS 102 965 (V1.2.1): "Intelligent Transport Systems (ITS); Application object identifier (ITS-AID); Registration list".</p>
<aname="REF_TR102965"/>[i.1] ETSI TS 102 965 (V1.2.1): "Intelligent Transport Systems (ITS); Application object identifier (ITS-AID); Registration list".</p>
<pclass="eX">
<aname="REF_ISOTS17423"></a> [i.2] ISO/TS 17423:2014: "Intelligent Transport Systems – Cooperative Systems – Application requirements for selection of communication profiles".</p>
<aname="REF_ISOTS17423"/> [i.2] ISO/TS 17423:2014: "Intelligent Transport Systems – Cooperative Systems – Application requirements for selection of communication profiles".</p>
<pclass="eX">
<aname="REF_ISO14823"></a>[i.3] ISO/TS 14823: "Traffic and travel information – Messages via media independent stationary dissemination systems – Graphic data dictionary for pre-trip and in-trip information dissemination systems".</p>
<aname="REF_ISO14823"/>[i.3] ISO/TS 14823: "Traffic and travel information – Messages via media independent stationary dissemination systems – Graphic data dictionary for pre-trip and in-trip information dissemination systems".</p>
<pclass="eX">
<aname="REF_IEEE80211ABGN"></a>[i.4] IEEE 802.11-2012: "IEEE Standard for Information technology - Telecommunications and information exchange between systems - Local and metropolitan area networks-Specific requirements - Part 11: Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY) Specifications".</p>
<aname="REF_IEEE80211ABGN"/>[i.4] IEEE 802.11-2012: "IEEE Standard for Information technology - Telecommunications and information exchange between systems - Local and metropolitan area networks-Specific requirements - Part 11: Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY) Specifications".</p>
<pclass="eX">
<aname="REF_ISO14832"></a>[i.5] ISO EN 14823: " Intelligent transport systems – Graphic data dictionary".</p>
<aname="REF_ISO14832"/>[i.5] ISO EN 14823: " Intelligent transport systems – Graphic data dictionary".</p>
<pclass="eX">
<aname="REF_TS102723_9"></a>[i.6] ETSI TS 102 723-9: "Intelligent Transport Systems; OSI cross-layer topics; Part 9: Interface between security entity and facilities layer".</p>
<aname="REF_TS102723_9"/>[i.6] ETSI TS 102 723-9: "Intelligent Transport Systems; OSI cross-layer topics; Part 9: Interface between security entity and facilities layer".</p>
<pclass="eX">[i.7] IETF Internet-Draft “Transport Layer Security (TLS) Authentication using ITS ETSI and IEEE certificates”, draft-lonc-tls-certieee1609-01.txt</p>
<pclass="eX"></p>
<pclass="eX"/>
<h1>
<aname="_Toc442882196"></a>
<aname="_Toc442882425"></a>
<aname="_Toc442965238"></a>
<aname="_Toc455389580"></a>3 Definitions and abbreviations</h1>
<aname="_Toc442882196"/>
<aname="_Toc442882425"/>
<aname="_Toc442965238"/>
<aname="_Toc455389580"/>3 Definitions and abbreviations</h1>
<h2>
<aname="_Toc455389581"></a>3.1 Definitions</h2>
<aname="_Toc455389581"/>3.1 Definitions</h2>
<p>For the purposes of the present document, the following terms and definitions apply:</p>
<p>
<b>Destination area:</b> geographic area in which a message is disseminated</p>
...
...
@@ -319,7 +318,7 @@
<p>
<b>ITS-G5: </b>access technology to be used in frequency bands dedicated for European intelligent transport System (ITS)</p>
<h2>
<aname="_Toc455389582"></a>3.2 Abbreviations</h2>
<aname="_Toc455389582"/>3.2 Abbreviations</h2>
<p>For the purposes of the present document, the following abbreviations apply:</p>
<pclass="eW">ADU Application Data Unit</p>
<pclass="eW">AID Action Identifier</p>
...
...
@@ -378,23 +377,23 @@
<pclass="nO">NOTE: In this present document the abbreviation V-ITS-S represents all ITS based equipment used by the end user.</p>
<pclass="eX">WLAN Wireless Local Area Network</p>
<h1>
<aname="_Toc442882197"></a>
<aname="_Toc442882426"></a>
<aname="_Toc442965239"></a>
<aname="_Toc455389583"></a>4 Infrastructure services introduction and general requirements</h1>
<aname="_Toc442882197"/>
<aname="_Toc442882426"/>
<aname="_Toc442965239"/>
<aname="_Toc455389583"/>4 Infrastructure services introduction and general requirements</h1>
<p>Within the scope of the present document, the term message refers to the Facilities layer PDU; the term payload refers to the applications layer ADU. The payload is generated by the application and provided to the corresponding service of the Facilities layer. The Facilities service merges the <i>ItsPduHeader</i> (ETSI TS102 894-2 [2]) with the payload, in order to construct a message. The message is then delivered to the Networking & Transport layer with a set of communication parameters.</p>
<pclass="nO">NOTE: In other standards referred by the present document, the term message, payload, data structure may have different meanings e.g. in ISO/TS 19091 [8] and in ISO/TS 19321 [7]. Therefore, the current convention is defined for clarification purpose.</p>
<h2>
<aname="clause_Infrastr_services_in_the_ITS"></a>
<aname="_Toc442882199"></a>
<aname="_Toc442882428"></a>
<aname="_Toc442965241"></a>
<aname="_Toc455389585"></a>4.2 Infrastructure services in the ITS communications architecture</h2>
<aname="clause_Infrastr_services_in_the_ITS"/>
<aname="_Toc442882199"/>
<aname="_Toc442882428"/>
<aname="_Toc442965241"/>
<aname="_Toc455389585"/>4.2 Infrastructure services in the ITS communications architecture</h2>
<p>The infrastructure services refer to Facilities layer entities that manage the generation, transmission and reception of infrastructure-related messages from the infrastructure (C-ITS-S or R-ITS-S) to V-ITS-S or vice-versa. Figure 1 illustrates a high level functional architecture of the infrastructure services within the ITS communication architecture, as specified in ETSI EN 302 665 [1]. The messages are Facilities layer PDUs that are exchanged among ITS-Ss. The payload is generated by ITS applications in the transmitting ITS-S or other connected ITS-S (e.g. a C-ITS-S). At the transmitting ITS-S, the transmission of a message is triggered by applications or by forwarding mechanisms. For this purpose, the applications may connect to other entities of the Facilities layer or to external entities, in order to collect relevant information for the generation of the payload. Once the message is generated, the services may repeat the transmission, until the applications requests the termination of the transmission, or trigger another request to generate updated messages. At the receiving ITS-S, the messages are processed by the services and the content of the message is delivered to applications or to other Facilities layer entity. In one typical application, the message is transmitted by an RITS-S and disseminated to V-ITS-S within a target destination area, in which the information included in the message is considered as relevant to traffic participants.</p>
<p>In the scope of the present document, the infrastructure services supports the management of the following message types. As result, the infrastructure services include a set of service entities as listed below:</p>
<pclass="b1+">SPATEM as defined in Annex A. The corresponding service entity is referred as "Traffic Light Maneuver" - TLM service in the present document. TLM service is specified in clause 5 of the present document.</p>
...
...
@@ -404,10 +403,10 @@
<pclass="b1+">SSEM as specified in Annex E. The corresponding service is referred as " Traffic Light Control" - TLC service in the present document. TLC service is specified in clause 8 of the present document.</p>
<pclass="nO">NOTE: Other messages may be supported by infrastructure services in the future.</p>
