TS103301_V104_clean.xhtml

<p class="tAC"/>
</td>	<td>
<p class="tAC"/>
</td>	<td>
<p class="tAC"/>
</td>	<td>
<p class="tAC"/>
</td>	<td>
<p class="tAC">2</p>
</td>	<td>
<p class="tAC"/>
</td>	<td>
<p class="tAC"/>
</td>	<td>
<p class="tAC"/>
</td>	<td>
<p class="tAC"/>
</td>	<td>
<p class="tAC"/>
</td>	<td>
<p class="tAC"/>
</td>	<td>
<p class="tAC"/>
</td>
</tr>
<tr>	<td>
<p class="tAC">0</p>
</td>	<td>
<p class="tAC">1</p>
</td>	<td>
<p class="tAC">2</p>
</td>	<td>
<p class="tAC">3</p>
</td>	<td>
<p class="tAC">4</p>
</td>	<td>
<p class="tAC">5</p>
</td>	<td>
<p class="tAC">6</p>
</td>	<td>
<p class="tAC">7</p>
</td>	<td>
<p class="tAC">0</p>
</td>	<td>
<p class="tAC">1</p>
</td>	<td>
<p class="tAC">2</p>
</td>	<td>
<p class="tAC">3</p>
</td>	<td>
<p class="tAC">4</p>
</td>	<td>
<p class="tAC">5</p>
</td>	<td>
<p class="tAC">6</p>
</td>	<td>
<p class="tAC">7</p>
</td>	<td>
<p class="tAC">0</p>
</td>	<td>
<p class="tAC">1</p>
</td>	<td>
<p class="tAC">2</p>
</td>	<td>
<p class="tAC">3</p>
</td>	<td>
<p class="tAC">4</p>
</td>	<td>
<p class="tAC">5</p>
</td>	<td>
<p class="tAC">6</p>
</td>	<td>
<p class="tAC">7</p>
</td>
</tr>
<tr>	<td>
<p class="tAC">Octet 0</p>
</td>	<td>
<p class="tAC">Octet 1</p>
</td>	<td>
<p class="tAC">Octet 2</p>
</td>
</tr>
</tbody>
</table>
<p class="nF"/>
<p class="tF">
<a name="_Ref414524055"/>Figure 4: Format for the Octets</p>
<p>The SSP for the TLM service shall correspond to the octet scheme of Table 5.</p>
<p class="tH">
<a name="_Ref419805087"/>Table 5: Octet Scheme for TLM service SSPs</p>
<table>
<tbody>
<tr>	<td>
<p class="tAH">Octet #</p>
</td>	<td>
<p class="tAH">Description</p>
</td>
</tr>
<tr>	<td>
<p class="tAL">0</p>
</td>	<td>
<p class="tAL">SSP version control</p>
</td>
</tr>
<tr>	<td>
<p class="tAL">1</p>
</td>	<td>
<p class="tAL">Service-specific parameter</p>
</td>
</tr>
<tr>	<td>
<p class="tAL">2 to 30</p>
</td>	<td>
<p class="tAL">Reserved for Future Usage</p>
</td>
</tr>
</tbody>
</table>
<p/>
<p><span class="requality_text id_ffb90c26-8785-43c8-a067-454300b1482e"><a class="requality_id" id="id_ffb90c26-8785-43c8-a067-454300b1482e" name="ffb90c26-8785-43c8-a067-454300b1482e"/>The Service specific parameter shall be as defined in Table 6.</span></p>
<p class="tH">
<a name="_Ref386548905"/>Table 6: TLM service specific permissions</p>
<table>
<tbody>
<tr>	<td>
<p class="tAH">Octet position</p>
</td>	<td>
<p class="tAH">Bit position</p>
</td>	<td>
<p class="tAH">SPATEM data Item</p>
</td>	<td>
<p class="tAH">Bit Value</p>
</td>
</tr>
<tr>	<td>
<p class="tAL">1</p>
</td>	<td>
<p class="tAL">0 (80h)</p>
</td>	<td>
<p class="tAL">Information about Intersection state without advisory speed (see bit position 1) and Maneuver assisting information (see Bit position 4)</p>
<p class="tAL">{SPATEM.spat.intersections.<br/>IntersectionState }</p>
</td>	<td>
<p class="tAL">0: certificate not allowed to sign </p>
<p class="tAL">1: certificate allowed to sign</p>
</td>
</tr>
<tr>	<td>
<p class="tAL">1</p>
</td>	<td>
<p class="tAL">1 (40h)</p>
</td>	<td>
<p class="tAL">General status of the traffic controller</p>
<p class="tAL">{SPATEM.spat.intersections.<br/>IntersectionState.status}</p>
</td>	<td>
<p class="tAL">0: certificate not allowed to sign </p>
<p class="tAL">1: certificate allowed to sign</p>
</td>
</tr>
<tr>	<td>
<p class="tAL">1</p>
</td>	<td>
<p class="tAL">2 (20h)</p>
</td>	<td>
<p class="tAL">Advisory speed</p>
<p class="tAL">{SPATEM.spat.intersections.<br/>IntersectionState.states.MovementState.state-time-speed.MovementEvent.speeds. AdvisorySpeed}</p>
</td>	<td>
<p class="tAL">0: certificate not allowed to sign </p>
<p class="tAL">1: certificate allowed to sign </p>
</td>
</tr>
<tr>	<td>
<p class="tAL">1</p>
</td>	<td>
<p class="tAL">3 (10h)</p>
</td>	<td>
<p class="tAL">Public transport prioritization </p>
<p class="tAL">{SPATEM.spat.intersections.<br/>IntersectionState.regional.SEQUENCE.<br/>regExtValue.<br/>IntersectionState-aggGrpC.activePrioritizations}</p>
</td>	<td>
<p class="tAL">0: certificate not allowed to sign </p>
<p class="tAL">1: certificate allowed to sign </p>
</td>
</tr>
<tr>	<td>
<p class="tAL">1</p>
</td>	<td>
<p class="tAL">4 (08h)</p>
</td>	<td>
<p class="tAL">Maneuver assisting information </p>
<p class="tAL">{SPATEM.spat.intersections.<br/>IntersectionState.maneuverAssistList}</p>
<p class="tAL">and</p>
<p class="tAL">{SPATEM.spat.intersections.<br/>IntersectionState.states.MovementState.<br/>maneuverAssistList}</p>
</td>	<td>
<p class="tAL">0: certificate not allowed to sign </p>
<p class="tAL">1: certificate allowed to sign</p>
</td>
</tr>
<tr>	<td>
<p class="tAL"><span class="requality_text id_4bda289f-d3a6-42f9-9eea-f94b9a276478"><a class="requality_id" id="id_4bda289f-d3a6-42f9-9eea-f94b9a276478" name="4bda289f-d3a6-42f9-9eea-f94b9a276478"/>All other bits of the SSP are not used and set to 0.</span></p>
</td>
</tr>
</tbody>
</table>
<p/>
<h4>
<a name="_Toc442882222"/>
<a name="_Toc442882451"/>
<a name="_Toc442965264"/>
<a name="_Toc455389609"/>5.4.3.3	TLM service communication requirements for long range communication</h4>
<p>This clause provides the requirements for the long range unicast communication (e.g. usage of cellular network) in accordance with ISO/TS 17423 [i.2].</p>
<p class="tH">Table 7: TLM service communication requirements for long range</p>
<table>
<tbody>
<tr>	<td>
<p class="tAH">Requirement</p>
</td>	<td>
<p class="tAH">Value</p>
</td>	<td>
<p class="tAH">Comment</p>
</td>
</tr>
<tr>	<td>
<p class="tAL">Operational communication service parameters</p>
</td>
</tr>
<tr>	<td>
<p class="tAL">CSP_LogicalChannelType</p>
</td>	<td>
<p class="tAL">GpCH</p>
</td>	<td>
<p class="tAL">General Purpose Channel</p>
</td>
</tr>
<tr>	<td>
<p class="tAL">CSP_SessionCont</p>
</td>	<td>
<p class="tAL">n.a.</p>
</td>	<td>
<p class="tAL"/>
</td>
</tr>
<tr>	<td>
<p class="tAL">CSP_AvgADUrate</p>
</td>	<td>
<p class="tAL">n.a</p>
</td>	<td>
<p class="tAL">No repetition</p>
</td>
</tr>
<tr>	<td>
<p class="tAL">CSP_FlowType</p>
</td>	<td>
<p class="tAL">n.a.</p>
</td>	<td>
<p class="tAL"/>
</td>
</tr>
<tr>	<td>
<p class="tAL">CSP_MaxPrio</p>
</td>	<td>
<p class="tAL"/>
</td>	<td>
<p class="tAL"/>
</td>
</tr>
<tr>	<td>
<p class="tAL">CSP_PortNo</p>
</td>	<td>
<p class="tAL">2 004</p>
</td>	<td>
<p class="tAL">Port Number of the transport protocol  (see ETSI TS 103 248 [16])</p>
</td>
</tr>
<tr>	<td>
<p class="tAL">CSP_ExpFlowLifetime</p>
</td>	<td>
<p class="tAL">n.a.</p>
</td>	<td>
<p class="tAL"/>
</td>
</tr>
<tr>	<td>
<p class="tAL">Destination communication service parameters</p>
</td>
</tr>
<tr>	<td>
<p class="tAL">CSP_DestinationType</p>
</td>	<td>
<p class="tAL">unicast</p>
</td>	<td>
<p class="tAL"/>
</td>
</tr>
<tr>	<td>
<p class="tAL">CSP_DestinationDomain</p>
</td>	<td>
<p class="tAL">global</p>
</td>	<td>
<p class="tAL"/>
</td>
</tr>
<tr>	<td>
<p class="tAL">CSP_CommDistance</p>
</td>	<td>
<p class="tAL">n.a.</p>
</td>	<td>
<p class="tAL"/>
</td>
</tr>
<tr>	<td>
<p class="tAL">CSP_Directivity</p>
</td>	<td>
<p class="tAL">n.a.</p>
</td>	<td>
<p class="tAL"/>
</td>
</tr>
<tr>	<td>
<p class="tAL">Performance communication service parameters</p>
</td>
</tr>
<tr>	<td>
<p class="tAL">CSP_Resilience</p>
</td>	<td>
<p class="tAL">required</p>
</td>	<td>
<p class="tAL"/>
</td>
</tr>
<tr>	<td>
<p class="tAL">CSP_MinThP</p>
</td>	<td>
<p class="tAL">n.a.</p>
</td>	<td>
<p class="tAL"/>
</td>
</tr>
<tr>	<td>
<p class="tAL">CSP_MaxLat</p>
</td>	<td>
<p class="tAL">n.a.</p>
</td>	<td>
<p class="tAL"/>
</td>
</tr>
<tr>	<td>
<p class="tAL">CSP_MaxADU</p>
</td>	<td>
<p class="tAL">Max message size allowed by access technology</p>
</td>	<td>
<p class="tAL"/>
</td>
</tr>
<tr>	<td>
<p class="tAL">Security communication service parameters</p>
</td>
</tr>
<tr>	<td>
<p class="tAL">CSP_DataConfidentiality</p>
</td>	<td>
<p class="tAL">required</p>
</td>	<td>
<p class="tAL"/>
</td>
</tr>
<tr>	<td>
<p class="tAL">CSP_DataIntegrity</p>
</td>	<td>
<p class="tAL">n.a.</p>
</td>	<td>
<p class="tAL"/>
</td>
</tr>
<tr>	<td>
<p class="tAL">CSP_NonRepudiation</p>
</td>	<td>
<p class="tAL">required</p>
</td>	<td>
<p class="tAL"/>
</td>
</tr>
<tr>	<td>
<p class="tAL">CSP_SourceAuthentication</p>
</td>	<td>
<p class="tAL">required</p>
</td>	<td>
<p class="tAL"/>
</td>
</tr>
<tr>	<td>
<p class="tAL">Protocol communication service parameter</p>
</td>
</tr>
<tr>	<td>
<p class="tAL">Protocol-Req</p>
</td>	<td>
<p class="tAL">n.a.</p>
</td>	<td>
<p class="tAL"/>
</td>
</tr>
</tbody>
</table>
<p/>
<h1>
<a name="Clause_RLT_Service"/>
<a name="_Toc442882223"/>
<a name="_Toc442882452"/>
<a name="_Toc442965265"/>
<a name="_Toc455389610"/><span class="requality_text id_b735fdb9-6d23-48f4-b1b0-aab01f6bb2dd"><a class="requality_id" id="id_b735fdb9-6d23-48f4-b1b0-aab01f6bb2dd" name="b735fdb9-6d23-48f4-b1b0-aab01f6bb2dd"/>6	Road and Lane Topology (RLT) service</span></h1>
<h2>
<a name="_Toc442882224"/>
<a name="_Toc442882453"/>
<a name="_Toc442965266"/>
<a name="_Toc455389611"/>6.1	RLT service overview</h2>
<p>The RLT service is one instantiation of the infrastructure services to manage the generation, transmission and reception of a digital topological map, which defines the topology of an infrastructure area. It includes the lane topology for e.g. vehicles, bicycles, parking, public transportation and the paths for pedestrian crossings and the allowed maneuvers within an intersection area or a road segment. In future enhancements the digital map will include additional topologydescriptions like traffic roundabouts.</p>
<p>The area of an intersection described by the topology covers about 200 m of the approaches, starting from the position of the stop line. If a neighbor intersection is closer than 400 meters, the description may be done up to an extent of approximately the half distance between the intersections.</p>
<p class="fL">
<div class="embedded" id="rId23"/>
</p>
<p class="tF">
<a name="_Ref413857845"/>Figure 5: Lane topology and corresponding connection</p>
<p>Figure 5 gives an example of the topology of an intersection. The topology is organized in several approaches (three approaches in the given example) and a "conflict area" in the junction of the approaches. Each approach holds "ingressing" (driving direction towards the conflict area) and "egressing" lanes (driving direction away from the "conflict area"). Each lane (e.g. vehicle, pedestrian, etc.) consists of two or more waypoint (positioned in the middle of the lane). Basically each ingress lane is connected with one or more egress lanes which define the allowed maneuvers in the intersection. This "connection" includes the signal group identifier, which is the link for signalization between the topology and the corresponding signaling.</p>
<h2>
<a name="_Toc442882225"/>
<a name="_Toc442882454"/>
<a name="_Toc442965267"/>
<a name="_Toc455389612"/>6.2	RLT service</h2>
<p>The Road and Lane Topology service instantiated in an ITS-Station shall provide either the transmission or the reception service defined in clause 4.2. Additionally the Road and lane Topology service supports the following functionality:</p>
<p class="b1+">Continuous transmission for infinity of the MAPEM. As the MAPEM message is not changed very often in time, a stable release is stored within the ITS-S for continuous broadcast.</p>
<p class="b1+">Assembly and disassembly fragmented MAPEM fragments on an Application level as defined by the data element <i>{MAPEM.map.layerID}</i> ISO/TS 19091 [8].</p>
<h2>
<a name="_Toc442882226"/>
<a name="_Toc442882455"/>
<a name="_Toc442965268"/>
<a name="_Toc455389613"/>6.3	RLT service message and version</h2>
<p>The RLT service shall use the message MAPEM as defined in Annex B . The header of MAPEM is defined in the data dictionary ETSI TS 102 894-2 [2]. The data elements of MAPEM payload are defined in CEN ISO/TS 19091, Annex G.</p>
<p>T<span class="requality_text id_c3059bb9-d9ca-4509-8d32-e216420f69a2"><a class="requality_id" id="id_c3059bb9-d9ca-4509-8d32-e216420f69a2" name="c3059bb9-d9ca-4509-8d32-e216420f69a2"/>he </span><i><span class="requality_text id_c3059bb9-d9ca-4509-8d32-e216420f69a2">protocolVersion</span></i><span class="requality_text id_c3059bb9-d9ca-4509-8d32-e216420f69a2"> (defined in </span><i><span class="requality_text id_c3059bb9-d9ca-4509-8d32-e216420f69a2">header</span></i><span class="requality_text id_c3059bb9-d9ca-4509-8d32-e216420f69a2">) of MAPEM message based on the present document is set to value "1".</span></p>
<h2>
<a name="_Toc442882227"/>
<a name="_Toc442882456"/>
<a name="_Toc442965269"/>
<a name="_Toc455389614"/>6.4	RLT service dissemination</h2>
<h3>
<a name="_Toc442882228"/>
<a name="_Toc442882457"/>
<a name="_Toc442965270"/>
<a name="_Toc455389615"/>6.4.1	RLT service identification</h3>
<p>The RLT service uses MAPEM which represents the topology/geometry of a set of lanes. E.g. considering an intersection MAPEM defines the topology of the lanes or parts of the topology of the lanes identified by the intersection reference identifier. The MAPEM does not change very often in time. The same MAPEM is retransmitted with the same content, unless the Application indicates to transmit a new MAPEM.</p>
<p class="b1+"><span class="requality_text id_c3436086-7d4a-4452-aab8-d48d11161c76"><a class="requality_id" id="id_c3436086-7d4a-4452-aab8-d48d11161c76" name="c3436086-7d4a-4452-aab8-d48d11161c76"/>If the size of the MAPEM exceeds the allowed message length (e.g. MTU), the RLT service fragments the message which will be transmitted in different messages. Each fragment is identified by the "layerID " as defined in ISO/TS 19091 [8], Annex G.</span></p>
<h3>
<a name="_Toc442882229"/>
<a name="_Toc442882458"/>
<a name="_Toc442965271"/>
<a name="_Toc455389616"/>6.4.2	RLT service trigger, update, repetition and termination</h3>
<p>The application triggers the Road and lane Topology service for the transmission of the MAPEM. The application provides all data content included in the MAPEM payload. The RLT service constructs a MAPEM and delivers it to the Networking &amp; Transport Layer for dissemination.</p>
<p>As the MAPEM content is only changed, e.g. if the road and lane topology is changed, the MAPEM remains stable in time. The MAPEM is re-broadcasted continuously.</p>
<p>The MAPEM transmission may be terminated if the ITS-S application requests the termination.</p>
<h3>
<a name="_Toc442882230"/>
<a name="_Toc442882459"/>
<a name="_Toc442965272"/>
<a name="_Toc455389617"/>6.4.3	RLT service communication requirements</h3>
<h4>
<a name="_Toc442882231"/>
<a name="_Toc442882460"/>
<a name="_Toc442965273"/>
<a name="_Toc455389618"/>6.4.3.1	RLT service communication overview</h4>
<p>The RLT service uses MAPEM to define all the road topological details. It uses the lane "connection" (between ingress and egress lanes) which includes the signal-group identifier which is the link to SPATEM signaling information. <span class="requality_text id_87b10e4b-b1dc-449c-b9ac-23380151b75e"><a class="requality_id" id="id_87b10e4b-b1dc-449c-b9ac-23380151b75e" name="87b10e4b-b1dc-449c-b9ac-23380151b75e"/>MAPEM shall be transmitted continuously together with the SPATEM to inform the traffic participant (driver, pedestrian, etc.) about the status of allowed maneuvers within the intersection conflict area</span>. Due to potential different communication paths to the end users, the MAPEM may be disseminated using different access technologies for short range and long range communication.</p>
<h4>
<a name="_Toc442882232"/>
<a name="_Toc442882461"/>
<a name="_Toc442965274"/>
<a name="_Toc455389619"/>6.4.3.2	RLT service communication requirements for short range access technologies</h4>
<p>For short range broadcast communication different access technologies are applicable for dissemination of the MAPEM as follows:</p>
<p class="b1+">Short range communication data transmission using ITS-G5 broadcast transmission,</p>
<p class="b1+">WiFi communication.</p>
<p>In case the GN protocol and the GBC is used, the RLT service shall provide the destination area in the format compliant to ETSI EN 302 931 [9] and to the ITS networking &amp; transport layer.</p>
<p>Table 8 provides the requirements for the broadcast communication in accordance with ISO/TS 17423 [i.2].</p>
<p>The ITS station management uses the communication requirements to select suitable ITS-S communication protocol stacks. Some examples of communication parameter settings that fulfill these requirements are specified in clause 10.</p>
<p class="tH">Table 8: RLT service communication requirements for short range access technologies</p>
<table>
<tbody>
<tr>	<td>
<p class="tAH">Requirement</p>
</td>	<td>
<p class="tAH">Value</p>
</td>	<td>
<p class="tAH">Comment</p>
</td>
</tr>
<tr>	<td>
<p class="tAL">Operational parameters</p>
</td>
</tr>
<tr>	<td>
<p class="tAL">CSP_LogicalChannelType</p>
</td>	<td>
<p class="tAL">SfCH</p>
</td>	<td>
<p class="tAL">Safety channel</p>
</td>
</tr>
<tr>	<td>
<p class="tAL">CSP_SessionCont</p>
</td>	<td>
<p class="tAL">n.a.</p>
</td>	<td>
<p class="tAL">No continuous connectivity</p>
</td>
</tr>
<tr>	<td>
<p class="tAL">CSP_AvgADUrate</p>
</td>	<td>
<p class="tAL">255, 1 seconds (default)</p>
</td>	<td>
<p class="tAL"/>
</td>
</tr>
<tr>	<td>
<p class="tAL">CSP_FlowType</p>
</td>	<td>
<p class="tAL">n.a.</p>
</td>	<td>
<p class="tAL"/>
</td>
</tr>
<tr>	<td>
<p class="tAL">CSP_MaxPrio</p>
</td>	<td>
<p class="tAL">252</p>
</td>	<td>
<p class="tAL"/>
</td>
</tr>
<tr>	<td>
<p class="tAL">CSP_PortNo</p>
</td>	<td>
<p class="tAL"><span class="requality_text id_5aab70c2-219e-460f-9223-64c99800e70a"><a class="requality_id" id="id_5aab70c2-219e-460f-9223-64c99800e70a" name="5aab70c2-219e-460f-9223-64c99800e70a"/>2003</span></p>
</td>	<td>
<p class="tAL">Port Number of the transport protocol (see ETSI TS 103 248 [16])</p>
</td>
</tr>
<tr>	<td>
<p class="tAL">CSP_ExpFlowLifetime</p>
</td>	<td>
<p class="tAL">n.a.</p>
</td>	<td>
<p class="tAL"/>
</td>
</tr>
<tr>	<td>
<p class="tAL">Destination communication service parameters</p>
</td>
</tr>
<tr>	<td>
<p class="tAL">CSP_DestinationType</p>
</td>	<td>
<p class="tAL">geo-location-based</p>
<p class="tAL"><span class="requality_text id_77a4a214-685d-4d91-b306-36ebef6c3db8"><a class="requality_id" id="id_77a4a214-685d-4d91-b306-36ebef6c3db8" name="77a4a214-685d-4d91-b306-36ebef6c3db8"/>GeoBroadcast</span></p>
</td>	<td>
<p class="tAL"/>
</td>
</tr>
<tr>	<td>
<p class="tAL">CSP_DestinationDomain</p>
</td>	<td>
<p class="tAL">site-local</p>
</td>	<td>
<p class="tAL"/>
</td>
</tr>
<tr>	<td>
<p class="tAL">CSP_CommDistance</p>
</td>	<td>
<p class="tAL">400 m radius  (default value)</p>
</td>	<td>
<p class="tAL"/>
</td>
</tr>
<tr>	<td>
<p class="tAL">CSP_Directivity</p>
</td>	<td>
<p class="tAL">n.a.</p>
</td>	<td>
<p class="tAL"/>
</td>
</tr>
<tr>	<td>
<p class="tAL">Performance communication service parameters</p>
</td>
</tr>
<tr>	<td>
<p class="tAL">CSP_Resilience</p>
</td>	<td>
<p class="tAL">High</p>
</td>	<td>
<p class="tAL">Repeated transmission of the same message</p>
</td>
</tr>
<tr>	<td>
<p class="tAL">CSP_MinThP</p>
</td>	<td>
<p class="tAL">n.a.</p>
</td>	<td>
<p class="tAL"/>
</td>
</tr>
<tr>	<td>
<p class="tAL">CSP_MaxLat</p>
</td>	<td>
<p class="tAL">ms100 (8)</p>
</td>	<td>
<p class="tAL">-- response within less than 100 ms</p>
</td>
</tr>
<tr>	<td>
<p class="tAL">CSP_MaxADU</p>
</td>	<td>
<p class="tAL">Max message size allowed by access technology</p>
</td>	<td>
<p class="tAL"/>
</td>
</tr>
<tr>	<td>
<p class="tAL">Security communication service parameters</p>
</td>
</tr>
<tr>	<td>
<p class="tAL">CSP_DataConfidentiality</p>
</td>	<td>
<p class="tAL">n.a.</p>
</td>	<td>
<p class="tAL"/>
</td>
</tr>
<tr>	<td>
<p class="tAL">CSP_DataIntegrity</p>
</td>	<td>
<p class="tAL">required</p>
</td>	<td>
<p class="tAL"/>
</td>
</tr>
<tr>	<td>
<p class="tAL">CSP_NonRepudiation</p>
</td>	<td>
<p class="tAL">required</p>
</td>	<td>
<p class="tAL"/>
</td>
</tr>
<tr>	<td>
<p class="tAL">CSP_SourceAuthentication</p>
</td>	<td>
<p class="tAL">required</p>
</td>	<td>
<p class="tAL"/>
</td>
</tr>
<tr>	<td>
<p class="tAL">Protocol communication service parameter</p>
</td>
</tr>
<tr>	<td>
<p class="tAL">Protocol-Req</p>
</td>	<td>
<p class="tAL">n.a.</p>
</td>	<td>
<p class="tAL"/>
</td>
</tr>
</tbody>
</table>
<p/>
<p>
<b>RLT Application Identifier (AID)</b>
</p>
<p><span class="requality_text id_f73eb6c1-2513-4e4a-a8d7-de4c80675bb4"><a class="requality_id" id="id_f73eb6c1-2513-4e4a-a8d7-de4c80675bb4" name="f73eb6c1-2513-4e4a-a8d7-de4c80675bb4"/>The ITS AID of the RLT service is allocated in [15]</span></p>
<p>
<b><span class="requality_text id_ec702020-740d-4430-ba57-7b45b5d93273"><a class="requality_id" id="id_ec702020-740d-4430-ba57-7b45b5d93273" name="ec702020-740d-4430-ba57-7b45b5d93273"/>RLT service security parameters</span></b>
</p>
<p>For security against misuse of keys it is necessary to change the pseudonym identity regularly. The default time for is given in Table 9. For special cases like offline working traffic light controllers where manually driven provision of pseudonym identity keys is necessary, longer periods of e.g. half a year are allowed and shall be agreed with the operator.</p>
<p class="tH">
<a name="_Ref415033177"/>Table 9: RLT services security parameters</p>
<table>
<tbody>
<tr>	<td>
<p class="tAH">RLT service security parameters</p>
</td>
</tr>
<tr>	<td>
<p class="tAL">Message certificate validity</p>
</td>	<td>
<p class="tAL">2 months (default value)</p>
</td>
</tr>
<tr>	<td>
<p class="tAL">Station-ID change of pseudonym identity</p>
</td>	<td>
<p class="tAL">1 month (default value)</p>
</td>
</tr>
</tbody>
</table>
<p/>
<p>
<b>RLT service specific permissions (SSP)</b>
</p>
<p>The interpretation of the SSP octet scheme is defined as depicted in Figure 6.</p>
<table>
<tbody>
<tr>	<td>
<p class="tAC">0</p>
</td>	<td>
<p class="tAC"/>
</td>	<td>
<p class="tAC"/>
</td>	<td>
<p class="tAC"/>
</td>	<td>
<p class="tAC"/>
</td>	<td>
<p class="tAC"/>
</td>	<td>
<p class="tAC"/>
</td>	<td>
<p class="tAC"/>
</td>	<td>
<p class="tAC">1</p>
</td>	<td>
<p class="tAC"/>
</td>	<td>
<p class="tAC"/>
</td>	<td>
<p class="tAC"/>
</td>	<td>
<p class="tAC"/>
</td>	<td>
<p class="tAC"/>
</td>	<td>
<p class="tAC"/>
</td>	<td>
<p class="tAC"/>
</td>	<td>
<p class="tAC">2</p>
</td>	<td>
<p class="tAC"/>
</td>	<td>
<p class="tAC"/>
</td>	<td>
<p class="tAC"/>
</td>	<td>
<p class="tAC"/>
</td>	<td>
<p class="tAC"/>
</td>	<td>
<p class="tAC"/>
</td>	<td>
<p class="tAC"/>
</td>
</tr>
<tr>	<td>
<p class="tAC">0</p>
</td>	<td>
<p class="tAC">1</p>
</td>	<td>
<p class="tAC">2</p>
</td>	<td>
<p class="tAC">3</p>
</td>	<td>
<p class="tAC">4</p>
</td>	<td>
<p class="tAC">5</p>
</td>	<td>
<p class="tAC">6</p>
</td>	<td>
<p class="tAC">7</p>
</td>	<td>
<p class="tAC">0</p>
</td>	<td>
<p class="tAC">1</p>
</td>	<td>
<p class="tAC">2</p>
</td>	<td>
<p class="tAC">3</p>
</td>	<td>
<p class="tAC">4</p>
</td>	<td>
<p class="tAC">5</p>
</td>	<td>
<p class="tAC">6</p>
</td>	<td>
<p class="tAC">7</p>
</td>	<td>
<p class="tAC">0</p>
</td>	<td>
<p class="tAC">1</p>
</td>	<td>
<p class="tAC">2</p>
</td>	<td>
<p class="tAC">3</p>
</td>	<td>
<p class="tAC">4</p>
</td>	<td>
<p class="tAC">5</p>
</td>	<td>
<p class="tAC">6</p>
</td>	<td>
<p class="tAC">7</p>
</td>
</tr>
<tr>	<td>
<p class="tAC">Octet 0</p>
</td>	<td>
<p class="tAC">Octet 1</p>
</td>	<td>
<p class="tAC">Octet 2</p>
</td>
</tr>
</tbody>
</table>
<p class="nF"/>
<p class="tF">
<a name="_Ref415033252"/>Figure 6: Format for the Octets</p>
<p><span class="requality_text id_299468b6-80e7-4a89-9e17-fcfec17120a3"><a class="requality_id" id="id_299468b6-80e7-4a89-9e17-fcfec17120a3" name="299468b6-80e7-4a89-9e17-fcfec17120a3"/>The SSP for the RLT service shall correspond to the octet scheme of Table 10.</span></p>
<p class="tH">
<a name="_Ref419808009"/>Table 10: Octet Scheme for RLT service SSPs</p>
<table>
<tbody>
<tr>	<td>
<p class="tAH">Octet #</p>
</td>	<td>
<p class="tAH">Description</p>
</td>
</tr>
<tr>	<td>
<p class="tAL">0</p>
</td>	<td>
<p class="tAL">SSP version control</p>
</td>
</tr>
<tr>	<td>
<p class="tAL">1</p>
</td>	<td>
<p class="tAL">Service-specific parameter</p>
</td>
</tr>
<tr>	<td>
<p class="tAL">2 to 30</p>
</td>	<td>
<p class="tAL">Reserved for Future Usage</p>
</td>
</tr>
</tbody>
</table>
<p/>
<p><span class="requality_text id_28cb2500-bdc6-433d-9a15-2c14136109ab"><a class="requality_id" id="id_28cb2500-bdc6-433d-9a15-2c14136109ab" name="28cb2500-bdc6-433d-9a15-2c14136109ab"/>The Service-specific parameter shall be as defined in Table 11.</span></p>
<p class="tH">
<a name="_Ref415033296"/>Table 11: RLT service communication profile</p>
<table>
<tbody>
<tr>	<td>
<p class="tAH">Octet Position</p>
</td>	<td>
<p class="tAH">Bit Position</p>
</td>	<td>
<p class="tAH">RLT service SSP data Item</p>
</td>	<td>
<p class="tAH">Bit Value</p>
</td>
</tr>
<tr>	<td>
<p class="tAL">1</p>
</td>	<td>
<p class="tAL">0 (80h)</p>
</td>	<td>
<p class="tAL">Road and lane topology controlled by a traffic light controller without speed limits (see Bit position 2)</p>
<p class="tAL"> {MAPEM}</p>
</td>	<td>
<p class="tAL">0: certificate not allowed to sign </p>
</td>
</tr>
<tr>	<td>
<p class="tAL"/>
</td>	<td>
<p class="tAL"/>
</td>	<td>
<p class="tAL"/>
</td>	<td>
<p class="tAL">1: certificate allowed to sign </p>
</td>
</tr>
<tr>	<td>
<p class="tAL">1</p>
</td>	<td>
<p class="tAL">1 (40h)</p>
</td>	<td>
<p class="tAL">Road and lane topology not using traffic light controller (see Bit position 2)</p>
<p class="tAL"> {MAPEM}</p>
</td>	<td>
<p class="tAL">0: certificate not allowed to sign </p>
</td>
</tr>
<tr>	<td>
<p class="tAL">1</p>
</td>	<td>
<p class="tAL">2 (20h)</p>
</td>	<td>
<p class="tAL">Speed limits included in the road and lane topology</p>
<p class="tAL">{MAPEM.map.intersections.<br/>IntersectionGeometry.speedLimits}</p>
</td>	<td>
<p class="tAL">0: certificate not allowed to sign </p>
</td>
</tr>
<tr>	<td>
<p class="tAL"/>
</td>	<td>
<p class="tAL"/>
</td>	<td>
<p class="tAL"/>
</td>	<td>
<p class="tAL">1: certificate allowed to sign </p>
</td>
</tr>
<tr>	<td>
<p class="tAL"><span class="requality_text id_4486101d-d3b2-4156-bbd5-8bcef139d100"><a class="requality_id" id="id_4486101d-d3b2-4156-bbd5-8bcef139d100" name="4486101d-d3b2-4156-bbd5-8bcef139d100"/>All other bits of the SSP are not used and set to 0.</span></p>
</td>
</tr>
</tbody>
</table>
<h4>
<a name="_Toc442882233"/>
<a name="_Toc442882462"/>
<a name="_Toc442965275"/>
<a name="_Toc455389620"/>6.4.3.3	RLT service dissemination parameters for long range communication</h4>
<p>This clause provides the requirements for the long range unicast communication (e.g. usage of cellular network) in accordance with ISO/TS 17423 [i.2].</p>
<p class="tH">Table 12: RLT service communication requirements for long range</p>
<table>
<tbody>
<tr>	<td>
<p class="tAH">Requirement</p>
</td>	<td>
<p class="tAH">Value</p>
</td>	<td>
<p class="tAH">Comment</p>
</td>
</tr>
<tr>	<td>
<p class="tAL">Operational communication service parameters</p>
</td>
</tr>
<tr>	<td>
<p class="tAL">CSP_LogicalChannelType</p>
</td>	<td>
<p class="tAL">GPCH</p>
</td>	<td>
<p class="tAL">General Purpose Channel</p>
</td>
</tr>
<tr>	<td>
<p class="tAL">CSP_SessionCont</p>
</td>	<td>
<p class="tAL">n.a.</p>
</td>	<td>
<p class="tAL"/>
</td>
</tr>
<tr>	<td>
<p class="tAL">CSP_AvgADUrate</p>
</td>	<td>
<p class="tAL">n.a.</p>
</td>	<td>
<p class="tAL">No repetition</p>
</td>
</tr>
<tr>	<td>
<p class="tAL">CSP_FlowType</p>
</td>	<td>
<p class="tAL">n.a.</p>
</td>	<td>
<p class="tAL"/>
</td>
</tr>
<tr>	<td>
<p class="tAL">CSP_MaxPrio</p>
</td>	<td>
<p class="tAL"/>
</td>	<td>
<p class="tAL"/>
</td>
</tr>
<tr>	<td>
<p class="tAL">CSP_PortNo</p>
</td>	<td>
<p class="tAL">2003</p>
</td>	<td>
<p class="tAL">Port Number of the transport protocol (see ETSI TS 103 248 [16])</p>
</td>
</tr>