Skip to content
GitLab
Find file Normal viewHistoryPermalink
TS103301_V104_clean.xhtml 174 KB
Newer Older
garciay's avatar
Modify SPATEM/MAPEM TPs to support RSU and OBU roles  
garciay committed
2001 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014 2015 2016 2017 2018 2019 2020 2021 2022 2023 2024 2025 2026 2027 2028 2029 2030 2031 2032 2033 2034 2035 2036 2037 2038 2039 2040 2041 2042 2043 2044 2045 2046 2047 2048 2049 2050 2051 2052 2053 2054 2055 2056 2057 2058 2059 2060 2061 2062 2063 2064 2065 2066 2067 2068 2069 2070 2071 2072 2073 2074 2075 2076 2077 2078 2079 2080 2081 2082 2083 2084 2085 2086 2087 2088 2089 2090 2091 2092 2093 2094 2095 2096 2097 2098 2099 2100 2101 2102 2103 2104 2105 2106 2107 2108 2109 2110 2111 2112 2113 2114 2115 2116 2117 2118 2119 2120 2121 2122 2123 2124 2125 2126 2127 2128 2129 2130 2131 2132 2133 2134 2135 2136 2137 2138 2139 2140 2141 2142 2143 2144 2145 2146 2147 2148 2149 2150 2151 2152 2153 2154 2155 2156 2157 2158 2159 2160 2161 2162 2163 2164 2165 2166 2167 2168 2169 2170 2171 2172 2173 2174 2175 2176 2177 2178 2179 2180 2181 2182 2183 2184 2185 2186 2187 2188 2189 2190 2191 2192 2193 2194 2195 2196 2197 2198 2199 2200 2201 2202 2203 2204 2205 2206 2207 2208 2209 2210 2211 2212 2213 2214 2215 2216 2217 2218 2219 2220 2221 2222 2223 2224 2225 2226 2227 2228 2229 2230 2231 2232 2233 2234 2235 2236 2237 2238 2239 2240 2241 2242 2243 2244 2245 2246 2247 2248 2249 2250 2251 2252 2253 2254 2255 2256 2257 2258 2259 2260 2261 2262 2263 2264 2265 2266 2267 2268 2269 2270 2271 2272 2273 2274 2275 2276 2277 2278 2279 2280 2281 2282 2283 2284 2285 2286 2287 2288 2289 2290 2291 2292 2293 2294 2295 2296 2297 2298 2299 2300 2301 2302 2303 2304 2305 2306 2307 2308 2309 2310 2311 2312 2313 2314 2315 2316 2317 2318 2319 2320 2321 2322 2323 2324 2325 2326 2327 2328 2329 2330 2331 2332 2333 2334 2335 2336 2337 2338 2339 2340 2341 2342 2343 2344 2345 2346 2347 2348 2349 2350 2351 2352 2353 2354 2355 2356 2357 2358 2359 2360 2361 2362 2363 2364 2365 2366 2367 2368 2369 2370 2371 2372 2373 2374 2375 2376 2377 2378 2379 2380 2381 2382 2383 2384 2385 2386 2387 2388 2389 2390 2391 2392 2393 2394 2395 2396 2397 2398 2399 2400 2401 2402 2403 2404 2405 2406 2407 2408 2409 2410 2411 2412 2413 2414 2415 2416 2417 2418 2419 2420 2421 2422 2423 2424 2425 2426 2427 2428 2429 2430 2431 2432 2433 2434 2435 2436 2437 2438 2439 2440 2441 2442 2443 2444 2445 2446 2447 2448 2449 2450 2451 2452 2453 2454 2455 2456 2457 2458 2459 2460 2461 2462 2463 2464 2465 2466 2467 2468 2469 2470 2471 2472 2473 2474 2475 2476 2477 2478 2479 2480 2481 2482 2483 2484 2485 2486 2487 2488 2489 2490 2491 2492 2493 2494 2495 2496 2497 2498 2499 2500 2501 2502 2503 2504 2505 2506 2507 2508 2509 2510 2511 2512 2513 2514 2515 2516 2517 2518 2519 2520 2521 2522 2523 2524 2525 2526 2527 2528 2529 2530 2531 2532 2533 2534 2535 2536 2537 2538 2539 2540 2541 2542 2543 2544 2545 2546 2547 2548 2549 2550 2551 2552 2553 2554 2555 2556 2557 2558 2559 2560 2561 2562 2563 2564 2565 2566 2567 2568 2569 2570 2571 2572 2573 2574 2575 2576 2577 2578 2579 2580 2581 2582 2583 2584 2585 2586 2587 2588 2589 2590 2591 2592 2593 2594 2595 2596 2597 2598 2599 2600 2601 2602 2603 2604 2605 2606 2607 2608 2609 2610 2611 2612 2613 2614 2615 2616 2617 2618 2619 2620 2621 2622 2623 2624 2625 2626 2627 2628 2629 2630 2631 2632 2633 2634 2635 2636 2637 2638 2639 2640 2641 2642 2643 2644 2645 2646 2647 2648 2649 2650 2651 2652 2653 2654 2655 2656 2657 2658 2659 2660 2661 2662 2663 2664 2665 2666 2667 2668 2669 2670 2671 2672 2673 2674 2675 2676 2677 2678 2679 2680 2681 2682 2683 2684 2685 2686 2687 2688 2689 2690 2691 2692 2693 2694 2695 2696 2697 2698 2699 2700 2701 2702 2703 2704 2705 2706 2707 2708 2709 2710 2711 2712 2713 2714 2715 2716 2717 2718 2719 2720 2721 2722 2723 2724 2725 2726 2727 2728 2729 2730 2731 2732 2733 2734 2735 2736 2737 2738 2739 2740 2741 2742 2743 2744 2745 2746 2747 2748 2749 2750 2751 2752 2753 2754 2755 2756 2757 2758 2759 2760 2761 2762 2763 2764 2765 2766 2767 2768 2769 2770 2771 2772 2773 2774 2775 2776 2777 2778 2779 2780 2781 2782 2783 2784 2785 2786 2787 2788 2789 2790 2791 2792 2793 2794 2795 2796 2797 2798 2799 2800 2801 2802 2803 2804 2805 2806 2807 2808 2809 2810 2811 2812 2813 2814 2815 2816 2817 2818 2819 2820 2821 2822 2823 2824 2825 2826 2827 2828 2829 2830 2831 2832 2833 2834 2835 2836 2837 2838 2839 2840 2841 2842 2843 2844 2845 2846 2847 2848 2849 2850 2851 2852 2853 2854 2855 2856 2857 2858 2859 2860 2861 2862 2863 2864 2865 2866 2867 2868 2869 2870 2871 2872 2873 2874 2875 2876 2877 2878 2879 2880 2881 2882 2883 2884 2885 2886 2887 2888 2889 2890 2891 2892 2893 2894 2895 2896 2897 2898 2899 2900 2901 2902 2903 2904 2905 2906 2907 2908 2909 2910 2911 2912 2913 2914 2915 2916 2917 2918 2919 2920 2921 2922 2923 2924 2925 2926 2927 2928 2929 2930 2931 2932 2933 2934 2935 2936 2937 2938 2939 2940 2941 2942 2943 2944 2945 2946 2947 2948 2949 2950 2951 2952 2953 2954 2955 2956 2957 2958 2959 2960 2961 2962 2963 2964 2965 2966 2967 2968 2969 2970 2971 2972 2973 2974 2975 2976 2977 2978 2979 2980 2981 2982 2983 2984 2985 2986 2987 2988 2989 2990 2991 2992 2993 2994 2995 2996 2997 2998 2999 3000 
<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_IVI_Service"/>
<a name="_Toc442882234"/>
<a name="_Toc442882463"/>
<a name="_Toc442965276"/>
<a name="_Toc455389621"/><span class="requality_text id_fb47bcfb-85ca-4f88-985f-0053fa08c228"><a class="requality_id" id="id_fb47bcfb-85ca-4f88-985f-0053fa08c228" name="fb47bcfb-85ca-4f88-985f-0053fa08c228"/>7	Infrastructure to Vehicle Information (IVI) service</span></h1>
<h2>
<a name="_Toc442882235"/>
<a name="_Toc442882464"/>
<a name="_Toc442965277"/>
<a name="_Toc455389622"/>7.1	IVI service overview</h2>
<p>IVI service is one instantiation of the infrastructure services to manage the generation, transmission and reception of the IVIM messages. An IVIM supports mandatory and advisory road signage such as contextual speeds and road works warnings. IVIM either provides information of physical road signs such as static or variable road signs, virtual signs or road works.</p>
<h2>
<a name="_Toc442882236"/>
<a name="_Toc442882465"/>
<a name="_Toc442965278"/>
<a name="_Toc455389623"/>7.2	IVI service</h2>
<p>The IVI service instantiated in an ITS-Station shall provide either the transmission or the reception service defined in clause 4.2.</p>
<h2>
<a name="_Toc442882237"/>
<a name="_Toc442882466"/>
<a name="_Toc442965279"/>
<a name="_Toc455389624"/>7.3	IVI service message and version</h2>
<p>The IVI service shall use the IVIM as defined in Annex C. The header of the IVIM is defined in the data dictionary ETSI TS 102 894-2 [2]. The data elements of the IVIM message payload are defined in ISO/TS 19321 [7].</p>
<p><span class="requality_text id_108bba89-25e3-47e4-878e-0c5de7a5092f"><a class="requality_id" id="id_108bba89-25e3-47e4-878e-0c5de7a5092f" name="108bba89-25e3-47e4-878e-0c5de7a5092f"/>The </span><i><span class="requality_text id_108bba89-25e3-47e4-878e-0c5de7a5092f">protocolVersion</span></i><span class="requality_text id_108bba89-25e3-47e4-878e-0c5de7a5092f"> (defined in the header) of IVIM message based on the present document is set to value "1".</span></p>
<h2>
<a name="_Toc442882238"/>
<a name="_Toc442882467"/>
<a name="_Toc442965280"/>
<a name="_Toc455389625"/>7.4	IVI service dissemination</h2>
<h3>
<a name="_Toc442882239"/>
<a name="_Toc442882468"/>
<a name="_Toc442965281"/>
<a name="_Toc455389626"/>7.4.1	IVI service identification</h3>
<p>The IVIM identification is enabled by the parameter <i>{IVIM.ivi.mandatory.iviIdentificationNumber}</i>. <span class="requality_text id_6a936fb2-7785-4307-bcda-982306487e1c"><a class="requality_id" id="id_6a936fb2-7785-4307-bcda-982306487e1c" name="6a936fb2-7785-4307-bcda-982306487e1c"/>Each time a new IVIM is generated upon an application request, a new </span><i><span class="requality_text id_6a936fb2-7785-4307-bcda-982306487e1c">iviIdentificationNumber</span></i><span class="requality_text id_6a936fb2-7785-4307-bcda-982306487e1c"> (ISO/TS 19321 [7]) value shall be assigned by the IVI service.</span></p>
<p><span class="requality_text id_68d18e5e-3607-49fa-8771-d2641c58fe54"><a class="requality_id" id="id_68d18e5e-3607-49fa-8771-d2641c58fe54" name="68d18e5e-3607-49fa-8771-d2641c58fe54"/>When a iviIdentificationNumber is set, it shall be set to an recently unused value.</span> In one possible implementation, the iviIdentificationNumber is randomly set to a recently unused value within the range as specified in  ISO/TS 19321 [7].</p>
<p>An <i>iviIdentificationNumber</i> is linked to the organization providing the IVI service (e.g. the Service Provider, as defined in ISO/TS 17427 [10]). It enables the receiving ITS-S to differentiate IVIM messages transmitted from different service providers. </p>
<h3>
<a name="_Toc442882240"/>
<a name="_Toc442882469"/>
<a name="_Toc442965282"/>
<a name="_Toc455389627"/>7.4.2	IVI service trigger, update, repetition and termination</h3>
<p><span class="requality_text id_46061c36-999b-4ac9-ba0e-d5af670d8901"><a class="requality_id" id="id_46061c36-999b-4ac9-ba0e-d5af670d8901" name="46061c36-999b-4ac9-ba0e-d5af670d8901"/>IVI service trigger refers to the process of the generation and transmission of an IVIM when the IVI service of the sending ITS-S receives an application request. The IVI service shall then generate a new message with status </span><i><span class="requality_text id_46061c36-999b-4ac9-ba0e-d5af670d8901">{IVIM.ivi.mandatory.iviStatus} </span></i><span class="requality_text id_46061c36-999b-4ac9-ba0e-d5af670d8901">set to "</span><i><span class="requality_text id_46061c36-999b-4ac9-ba0e-d5af670d8901">new</span></i><span class="requality_text id_46061c36-999b-4ac9-ba0e-d5af670d8901">".</span></p>
<p><span class="requality_text id_fa90ddce-f302-4f09-ba88-09f938feb3fc"><a class="requality_id" id="id_fa90ddce-f302-4f09-ba88-09f938feb3fc" name="fa90ddce-f302-4f09-ba88-09f938feb3fc"/>An IVIM content is updated e.g. by the service provider. The ITS-S application provides the update information to the IVI service at the sending ITS-S. The IVI service shall then generate an update IVIM with the </span><i><span class="requality_text id_fa90ddce-f302-4f09-ba88-09f938feb3fc">iviStatus</span></i><span class="requality_text id_fa90ddce-f302-4f09-ba88-09f938feb3fc"> set to </span><i><span class="requality_text id_fa90ddce-f302-4f09-ba88-09f938feb3fc">update</span></i><span class="requality_text id_fa90ddce-f302-4f09-ba88-09f938feb3fc">.</span></p>
<p><span class="requality_text id_8a5e77e8-1e74-4263-b66a-6c2960fff2fb"><a class="requality_id" id="id_8a5e77e8-1e74-4263-b66a-6c2960fff2fb" name="8a5e77e8-1e74-4263-b66a-6c2960fff2fb"/>An "</span><i><span class="requality_text id_8a5e77e8-1e74-4263-b66a-6c2960fff2fb">update"</span></i><span class="requality_text id_8a5e77e8-1e74-4263-b66a-6c2960fff2fb"> is also used to change or add the end time to the IVIM.</span> In some applications this corresponds to ending the service (logical end message).The parameter "<i>timestamp" {IVIM.ivi.mandatory.timeStamp} </i>is the identifier for i<i>viStatus</i> (<i>update</i>) in relation to a specific <i>iviIdentificationNumber</i>. <span class="requality_text id_e6a00a64-ce4e-417e-a7bf-a46c07290fcd"><a class="requality_id" id="id_e6a00a64-ce4e-417e-a7bf-a46c07290fcd" name="e6a00a64-ce4e-417e-a7bf-a46c07290fcd"/>The </span><i><span class="requality_text id_e6a00a64-ce4e-417e-a7bf-a46c07290fcd">timeStamp </span></i><span class="requality_text id_e6a00a64-ce4e-417e-a7bf-a46c07290fcd">represents the time stamp of the generation (if </span><i><span class="requality_text id_e6a00a64-ce4e-417e-a7bf-a46c07290fcd">IviStatus set to</span></i><span class="requality_text id_e6a00a64-ce4e-417e-a7bf-a46c07290fcd"> </span><i><span class="requality_text id_e6a00a64-ce4e-417e-a7bf-a46c07290fcd">new</span></i><span class="requality_text id_e6a00a64-ce4e-417e-a7bf-a46c07290fcd">) or last change of information content (if </span><i><span class="requality_text id_e6a00a64-ce4e-417e-a7bf-a46c07290fcd">iviStatus set to update</span></i><span class="requality_text id_e6a00a64-ce4e-417e-a7bf-a46c07290fcd">) by the Service Provider.</span></p>
<p><span class="requality_text id_8a9b0b92-c278-4367-b849-f4313a3df6a9"><a class="requality_id" id="id_8a9b0b92-c278-4367-b849-f4313a3df6a9" name="8a9b0b92-c278-4367-b849-f4313a3df6a9"/>The </span><i><span class="requality_text id_8a9b0b92-c278-4367-b849-f4313a3df6a9">iviIdentificationNumber</span></i><span class="requality_text id_8a9b0b92-c278-4367-b849-f4313a3df6a9"> shall remain unchanged for </span><i><span class="requality_text id_8a9b0b92-c278-4367-b849-f4313a3df6a9">iviSStatus</span></i><span class="requality_text id_8a9b0b92-c278-4367-b849-f4313a3df6a9"> set to update.</span></p>
<p><span class="requality_text id_1f766cd6-cb72-4d44-a02b-d648ea2b4e43"><a class="requality_id" id="id_1f766cd6-cb72-4d44-a02b-d648ea2b4e43" name="1f766cd6-cb72-4d44-a02b-d648ea2b4e43"/>In between two consequent </span><i><span class="requality_text id_1f766cd6-cb72-4d44-a02b-d648ea2b4e43">iviStatus</span></i><span class="requality_text id_1f766cd6-cb72-4d44-a02b-d648ea2b4e43"> updates, an IVIM shall be repeated by the IVI service of the sending ITSS at a pre-defined repetition interval, in order that new ITS-S entering the MDA during the event validity duration may also receive the IVIM. </span>This process is referred to as IVI service repetition. <span class="requality_text id_8bbcc8c7-67ce-440e-b7d1-ed1d8a329a11"><a class="requality_id" id="id_8bbcc8c7-67ce-440e-b7d1-ed1d8a329a11" name="8bbcc8c7-67ce-440e-b7d1-ed1d8a329a11"/>The IVI service repetition shall be activated under the request from the ITS-S application.</span></p>
<p>The IVI service termination indicates the end of the validity of the IVI service. An IVI service termination is either the ending of transmission, an application cancelation or an application negation: a Cancellation of the IVI service can only be provided by the organization that originally provided the IVI service; a Negation of the IVI service can be provided by other organizations. Termination of IVI service is achieved in the following ways:</p>
<p class="b1+">Ending of transmission by the ITS-S originally sending the IVIM:<br/><span class="requality_text id_77979574-9fcd-4f47-82e4-25b79b781873"><a class="requality_id" id="id_77979574-9fcd-4f47-82e4-25b79b781873" name="77979574-9fcd-4f47-82e4-25b79b781873"/>The IVI service shall stop the IVIM transmission repetition automatically at the end of the repetition interval.</span></p>
<p class="b1+">IVI service cancellation by the Service Provider originating the IVIM:<br/><span class="requality_text id_e4cba9e5-2a65-4b7a-8caa-200865aad31e"><a class="requality_id" id="id_e4cba9e5-2a65-4b7a-8caa-200865aad31e" name="e4cba9e5-2a65-4b7a-8caa-200865aad31e"/>In this case, the IVI service shall generate a cancellation IVIM with the </span><i><span class="requality_text id_e4cba9e5-2a65-4b7a-8caa-200865aad31e">iviStatus</span></i><span class="requality_text id_e4cba9e5-2a65-4b7a-8caa-200865aad31e"> set to </span><i><span class="requality_text id_e4cba9e5-2a65-4b7a-8caa-200865aad31e">cancellation</span></i><span class="requality_text id_e4cba9e5-2a65-4b7a-8caa-200865aad31e">. For the generation of a cancellation IVIM, the </span><i><span class="requality_text id_e4cba9e5-2a65-4b7a-8caa-200865aad31e">iviIdentificationNumber</span></i><span class="requality_text id_e4cba9e5-2a65-4b7a-8caa-200865aad31e"> shall be set to the </span><i><span class="requality_text id_e4cba9e5-2a65-4b7a-8caa-200865aad31e">iviIdentificationNumber</span></i><span class="requality_text id_e4cba9e5-2a65-4b7a-8caa-200865aad31e"> of the message for which the IVI service negation refers to; the service provider identification </span><i><span class="requality_text id_e4cba9e5-2a65-4b7a-8caa-200865aad31e">{IVIM.ivi.mandatory.serviceProviderId}</span></i><span class="requality_text id_e4cba9e5-2a65-4b7a-8caa-200865aad31e"> shall be set to the value of the originating Service Provider. The time stamp </span><i><span class="requality_text id_e4cba9e5-2a65-4b7a-8caa-200865aad31e">{IVIM.ivi.mandatory.TimeStamp} </span></i><span class="requality_text id_e4cba9e5-2a65-4b7a-8caa-200865aad31e">shall be set to the value of the latest received IVI of the same "iviIdentificationNumber".</span></p>
<p class="b1+">IVIM negation by another organization:<br/><span class="requality_text id_48b08012-a369-49d3-b0f6-eee95a02e76a"><a class="requality_id" id="id_48b08012-a369-49d3-b0f6-eee95a02e76a" name="48b08012-a369-49d3-b0f6-eee95a02e76a"/>In this case, the IVI service of the sending ITS-S shall generate a negation IVIM, i.e. an IVIM with i</span><i><span class="requality_text id_48b08012-a369-49d3-b0f6-eee95a02e76a">viStatus</span></i><span class="requality_text id_48b08012-a369-49d3-b0f6-eee95a02e76a"> set to </span><i><span class="requality_text id_48b08012-a369-49d3-b0f6-eee95a02e76a">negation</span></i><span class="requality_text id_48b08012-a369-49d3-b0f6-eee95a02e76a">. For the generation of a negation IVIM, the </span><i><span class="requality_text id_48b08012-a369-49d3-b0f6-eee95a02e76a">iviIdentificationNumber</span></i><span class="requality_text id_48b08012-a369-49d3-b0f6-eee95a02e76a"> shall be set to the </span><i><span class="requality_text id_48b08012-a369-49d3-b0f6-eee95a02e76a">iviIdentificationNumber</span></i><span class="requality_text id_48b08012-a369-49d3-b0f6-eee95a02e76a"> of the event for which the IVIM negation</span><i><span class="requality_text id_48b08012-a369-49d3-b0f6-eee95a02e76a"> </span></i><span class="requality_text id_48b08012-a369-49d3-b0f6-eee95a02e76a">refers to; the </span><i><span class="requality_text id_48b08012-a369-49d3-b0f6-eee95a02e76a">serviceProviderId</span></i><span class="requality_text id_48b08012-a369-49d3-b0f6-eee95a02e76a"> shall be set to the value of the originating Service Provider. The </span><i><span class="requality_text id_48b08012-a369-49d3-b0f6-eee95a02e76a">timeStamp </span></i><span class="requality_text id_48b08012-a369-49d3-b0f6-eee95a02e76a">shall be set to the value of the latest received IVIM of the same </span><i><span class="requality_text id_48b08012-a369-49d3-b0f6-eee95a02e76a">iviIdentificationNumber</span></i> </p>
<p>Once a cancellation IVIM or a negation IVIM is verified to be trustworthy by the receiving ITS-S, all information related to the previously received IVIM concerning the same <i>iviIdentificationNumber</i> may be considered as not valid any more, the IVI service may notify ITS-S applications of the event termination.</p>
<p><span class="requality_text id_bb3d3790-fa2a-4cdc-8569-3f252de9f24f"><a class="requality_id" id="id_bb3d3790-fa2a-4cdc-8569-3f252de9f24f" name="bb3d3790-fa2a-4cdc-8569-3f252de9f24f"/>A cancellation IVIM or negation IVIM shall be transmitted at least once by the originating ITS-S per application request. It may be repeated by the IVI service of the originating ITS-S.</span></p>
<h3>
<a name="_Toc442882241"/>
<a name="_Toc442882470"/>
<a name="_Toc442965283"/>
<a name="_Toc455389628"/>7.4.3	IVI service communication requirements</h3>
<h4>
<a name="_Toc442882242"/>
<a name="_Toc442882471"/>
<a name="_Toc442965284"/>
<a name="_Toc455389629"/>7.4.3.1	IVI service communication parameters for short-range communication</h4>
<p>An IVIM shall be transmitted if applicable, e.g. when it is applicable in time (e.g. a speed limitation only valid between 8:00 and 20:00) and due to the context as determined by the sending ITS-S (e.g. a speed limitation applicable in case of fog).</p>
<p>An IVIM shall be disseminated to reach as many ITS-S as possible, located in the MDA. The MDA is provided by the ITS Application to the IVI service and is typically defined in a way that every receiving ITS-S has received at least once the IVIM before entering the DAZ (or if null the RZ) of the IVI.</p>
<p>The IVI service shall provide the MDA as destination area in the format compliant to the one as specified in ETSI EN 302 931 [9] to the ITS networking &amp; transport layer.</p>
<p>Table 13 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 profiles that fulfill these requirements are specified in clause 10.</p>
<p class="tH">
<a name="_Ref418590174"/>Table 13: IVI 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">253</p>
</td>	<td>
<p class="tAL"/>
</td>
</tr>
<tr>	<td>
<p class="tAL">CSP_PortNo</p>
</td>	<td>
<p class="tAL">2006</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">1: broadcast transmission</p>
<p class="tAL">16: geocast transmission to an area given by geocoordinates.</p>
</td>	<td>
<p class="tAL">If the MDA is within direct communication range of the sending ITS-S, destination type 1 shall be used. If the MDA exceeds the direct communication range or is not within the direct communication range, destination type 16 shall be used</p>
</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>IVI Application Identifier (AID)</b>
</p>
<p><span class="requality_text id_c3ba0b26-17cf-4dd8-90f3-941a01c66f96"><a class="requality_id" id="id_c3ba0b26-17cf-4dd8-90f3-941a01c66f96" name="c3ba0b26-17cf-4dd8-90f3-941a01c66f96"/>The ITS AID of the IVI service is allocated in [15].</span></p>
<p/>
<p>
<b><span class="requality_text id_09b4e90f-647e-40b8-bbfe-3b757cf53081"><a class="requality_id" id="id_09b4e90f-647e-40b8-bbfe-3b757cf53081" name="09b4e90f-647e-40b8-bbfe-3b757cf53081"/>IVI service specific permissions (SSP)</span></b>
</p>
<p>The IVIM contains the identification of the organization originating the IVIM, e.g. the Service Provider that originated it. An R-ITS-S is only allowed to send out IVIM for a defined Service Provider.</p>
<p>The SSP for the IVIM is defined by a variable number of octets and shall correspond to the octet scheme of Table 14. For each octet, the most significant bit (MSB) shall be the leftmost bit. The transmission order shall always be the MSB first. The interpretation of the SSP octet scheme is defined as depicted in Figure 7.</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="_Ref440402682"/>Figure 7: Format for the Octets</p>
<p class="tH">
<a name="_Ref414609194"/>Table 14. Octet Scheme for IVI SSPs</p>
<table>
<tbody>
<tr>	<td>
<p class="tAH">Octet #</p>
</td>	<td>
<p class="tAH">Component</p>
</td>	<td>
<p class="tAH">Semantics</p>
</td>
</tr>
<tr>	<td>
<p class="tAL">0</p>
</td>	<td>
<p class="tAL">version</p>
</td>	<td>
<p class="tAL">SSP version control:</p>
<p class="tAL">0: No version, length 1 octet; the value shall only be used for testing purposes.</p>
<p class="tAL"><span class="requality_text id_37041512-f1ea-427f-a8e6-e8f8c3f1a9f4"><a class="requality_id" id="id_37041512-f1ea-427f-a8e6-e8f8c3f1a9f4" name="37041512-f1ea-427f-a8e6-e8f8c3f1a9f4"/>1: First version, variable length, SSP contains information as defined in the present document.</span></p>
<p class="tAL">2 to 255:	Reserved for Future Usage.</p>
</td>
</tr>
<tr>	<td>
<p class="tAL">1 to 3</p>
</td>	<td>
<p class="tAL">serviceProviderId</p>
</td>	<td>
<p class="tAL"><span class="requality_text id_c6de9a60-98e3-4e25-aa6b-25757a753703"><a class="requality_id" id="id_c6de9a60-98e3-4e25-aa6b-25757a753703" name="c6de9a60-98e3-4e25-aa6b-25757a753703"/>Identification of the Service Provider for which the R-ITS-S is allowed to send out IVIM and to which the Service-specific parameter apply, using the DE Provider from ISO/TS19321 [7].</span></p>
</td>
</tr>
<tr>	<td>
<p class="tAL">4 to 5</p>
</td>	<td>
<p class="tAL">parameter</p>
</td>	<td>
<p class="tAL">Service-specific parameter, see Table 15.</p>
</td>
</tr>
</tbody>
</table>
<p/>
<p><span class="requality_text id_9099b2b8-ed7b-4943-9a69-bb697d241c23"><a class="requality_id" id="id_9099b2b8-ed7b-4943-9a69-bb697d241c23" name="9099b2b8-ed7b-4943-9a69-bb697d241c23"/>The Service-specific parameter shall be as defined in Table 15.</span></p>
<p class="tH">
<a name="_Ref411589978"/>Table 15: IVI service SSPs</p>
<table>
<tbody>
<tr>	<td>
<p class="tAH">Octet Position</p>
</td>	<td>
<p class="tAH">Bit Position</p>
</td>	<td>
<p class="tAH">IVIM 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) (MSBit)</p>
</td>	<td>
<p class="tAL">Vienna Convention Code for road sign</p>
<p class="tAL">{IVIM.ivi.optional.gic.GicPart.<br/>roadSignCodes.RSCode.code.<br/>viennaConvention}</p>
</td>	<td>
<p class="tAL">1: The sending ITS-S is authorized to sign "General IVI container" using the Vienna convention road signs</p>
<p class="tAL">0: The sending ITS-S is not authorized.</p>
</td>
</tr>
<tr>	<td>
<p class="tAL">1</p>
</td>	<td>
<p class="tAL">1 (40h)</p>
</td>	<td>
<p class="tAL">ISO/TS 14823 [i.3] traffic sign pictogram (danger warning)</p>
<p class="tAL">{IVIM.ivi.optional.gic.GicPart.<br/>roadSignCodes.RSCode.code.<br/>iso14823.pictogramCode.<br/>serviceCategoryCode.<br/>trafficSignPictogram.dangerWarning}</p>
</td>	<td>
<p class="tAL">1: The sending ITS-S is authorized to sign the "General IVI container" using the ISO/TS 14823 [i.3] road signs with traffic sign pictogram set to dangerWarning</p>
<p class="tAL">0: The sending ITS-S is not authorized.</p>
</td>
</tr>
<tr>	<td>
<p class="tAL">1</p>
</td>	<td>
<p class="tAL">2 (20h)</p>
</td>	<td>
<p class="tAL">ISO/TS 14823 [i.3] traffic sign pictogram  (regulatory) </p>
<p class="tAL">{IVIM.ivi.optional.gic.GicPart.<br/>roadSignCodes.RSCode.code.<br/>iso14823.pictogramCode.<br/>serviceCategoryCode.<br/>trafficSignPictogram.regulatory}</p>
</td>	<td>
<p class="tAL">1: The sending ITS-S is authorized to sign the "General IVI container" using the ISO/TS 14823 [i.3] road signs with traffic sign pictogram set to regulatory</p>
<p class="tAL">0: The sending ITS-S is not authorized.</p>
</td>
</tr>
<tr>	<td>
<p class="tAL">1</p>
</td>	<td>
<p class="tAL">3 (10h)</p>
</td>	<td>
<p class="tAL">ISO/TS 14823 [i.3] traffic sign pictogram  (informative) </p>
<p class="tAL">{IVIM.ivi.optional.gic.GicPart.<br/>roadSignCodes.RSCode.code.<br/>iso14823.pictogramCode.<br/>serviceCategoryCode.<br/>trafficSignPictogram.informative}</p>
</td>	<td>
<p class="tAL">1: The sending ITS-S is authorized to sign the "General IVI container" using the ISO/TS 14823 [i.3] road signs with traffic sign pictogram set to informative</p>
<p class="tAL">0: The sending ITS-S is not authorized.</p>
</td>
</tr>
<tr>	<td>
<p class="tAL">1</p>
</td>	<td>
<p class="tAL">4 (08h)</p>
</td>	<td>
<p class="tAL">ISO/TS 14823 [i.3] public facilities pictogram </p>
<p class="tAL">{IVIM.ivi.optional.gic.GicPart.<br/>roadSignCodes.RSCode.code.<br/>iso14823.pictogramCode.<br/>serviceCategoryCode.<br/>publicFacilitiesPictogram}</p>
</td>	<td>
<p class="tAL">1: The sending ITS-S is authorized to sign the "General IVI container" using the ISO/TS 14823 [i.3] road signs with public facilities pictogram</p>
<p class="tAL">0: The sending ITS-S is not authorized.</p>
</td>
</tr>
<tr>	<td>
<p class="tAL">1</p>
</td>	<td>
<p class="tAL">5 (04h)</p>
</td>	<td>
<p class="tAL">ISO/TS 14823 [i.3] ambient or road conditions pictogram (ambient condition)</p>
<p class="tAL">{IVIM.ivi.optional.gic.GicPart.<br/>roadSignCodes.RSCode.code.<br/>iso14823.pictogramCode.<br/>serviceCategoryCode.<br/>ambientOrRoadContitionPictogram.ambientCondition}</p>
</td>	<td>
<p class="tAL">1: The sending ITS-S is authorized to sign the "General IVI container" using the ISO/TS 14823 [i.3] road signs with ambient and road conditions set to ambientCondition</p>
<p class="tAL">0: The sending ITS-S is not authorized.</p>
</td>
</tr>
<tr>	<td>
<p class="tAL">1</p>
</td>	<td>
<p class="tAL">6 (02h)</p>
</td>	<td>
<p class="tAL">ISO/TS 14823 [i.3] ambient or road conditions pictogram (road condition)</p>
<p class="tAL">{IVIM.ivi.optional.gic.GicPart.<br/>roadSignCodes.RSCode.code.<br/>iso14823.pictogramCode.<br/>serviceCategoryCode.<br/>ambientOrRoadContitionPictogram.<br/>roadCondition}</p>
</td>	<td>
<p class="tAL">1: The sending ITS-S is authorized to sign the "General IVI container" using the ISO/TS 14823 [i.3] road signs with ambient and road conditions set to roadCondition</p>
<p class="tAL">0: The sending ITS-S is not authorized.</p>
</td>
</tr>
<tr>	<td>
<p class="tAL">1</p>
</td>	<td>
<p class="tAL">7 (01h)<br/>(LSBit)</p>
</td>	<td>
<p class="tAL">ITIS codes</p>
<p class="tAL">{IVIM.ivi.optional.gic.GicPart.<br/>roadSignCodes.RSCode.code.<br/>itisCodes}</p>
</td>	<td>
<p class="tAL">1: The sending ITS-S is authorized to sign the "General IVI container" using the ITIS codes</p>
<p class="tAL">0: The sending ITS-S is not authorized.</p>
</td>
</tr>
<tr>	<td>
<p class="tAL">2</p>
</td>	<td>
<p class="tAL">0 (80h)<br/>(MSBit)</p>
</td>	<td>
<p class="tAL">Lane status</p>
<p class="tAL"/>
<p class="tAL">{IVIM.ivi.optional.gic.GicPart.<br/>laneStatus}</p>
</td>	<td>
<p class="tAL">1: The sending ITS-S is authorized to sign the "General IVI container" using the laneStatus</p>
<p class="tAL">0: The sending ITS-S is not authorized.</p>
</td>
</tr>
<tr>	<td>
<p class="tAL">2</p>
</td>	<td>
<p class="tAL">1 (40h)</p>
</td>	<td>
<p class="tAL">Road configuration container </p>
<p class="tAL"/>
<p class="tAL">{IVIM.ivi.optional.rcc}</p>
</td>	<td>
<p class="tAL">1: The sending ITS-S is authorized to sign the "Road Configuration Container"</p>
<p class="tAL">0: The sending ITS-S is not authorized.</p>
</td>
</tr>
<tr>	<td>
<p class="tAL">2</p>
</td>	<td>
<p class="tAL">2 (20h)</p>
</td>	<td>
<p class="tAL">Text container</p>
<p class="tAL"/>
<p class="tAL">{IVIM.ivi.optional.tc}</p>
</td>	<td>
<p class="tAL">1: The sending ITS-S is authorized to sign the "Text Container"</p>
<p class="tAL">0: The sending ITS-S is not authorized.</p>
</td>
</tr>
<tr>	<td>
<p class="tAL">2</p>
</td>	<td>
<p class="tAL">3 (10h)</p>
</td>	<td>
<p class="tAL">Layout Container</p>
<p class="tAL"/>
<p class="tAL">{IVIM.ivi.optional.lac}</p>
</td>	<td>
<p class="tAL">1: The sending ITS-S is authorized to sign the "Layout Container"</p>
<p class="tAL">0: The sending ITS-S is not authorized.</p>
</td>
</tr>
<tr>	<td>
<p class="tAL">2</p>
</td>	<td>
<p class="tAL">4 (08h)</p>
</td>	<td>
<p class="tAL">IVI Status (negation)</p>
<p class="tAL"/>
<p class="tAL">{IVIM.ivi.mandatory.iviStatus}</p>
</td>	<td>
<p class="tAL">1: The sending ITS-S is authorized to sign use the iviStatus set to negation</p>
<p class="tAL">0: The sending ITS-S is not authorized.</p>
</td>
</tr>
<tr>	<td>
<p class="tAL"><span class="requality_text id_e3359386-7c08-4b84-9241-a47ef0d3ae95"><a class="requality_id" id="id_e3359386-7c08-4b84-9241-a47ef0d3ae95" name="e3359386-7c08-4b84-9241-a47ef0d3ae95"/>All other bits of the SSP are not used and set to 0.</span></p>
</td>
</tr>
</tbody>
</table>
<p/>
<h4>
<a name="_Toc442882243"/>
<a name="_Toc442882472"/>
<a name="_Toc442965285"/>
<a name="_Toc455389630"/>7.4.3.2	IVI 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 16: IVI 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 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">No continuous connectivity</p>
</td>
</tr>
<tr>	<td>
<p class="tAL">CSP_AvgADUrate</p>
</td>	<td>
<p class="tAL">n.a</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"/>
</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_c5034f72-3698-4bcd-9169-243698e123ef"><a class="requality_id" id="id_c5034f72-3698-4bcd-9169-243698e123ef" name="c5034f72-3698-4bcd-9169-243698e123ef"/>2006</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"><span class="requality_text id_4aafd874-da69-4aa9-8142-ee95841e1434"><a class="requality_id" id="id_4aafd874-da69-4aa9-8142-ee95841e1434" name="4aafd874-da69-4aa9-8142-ee95841e1434"/>Unicast</span></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">n.a.</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">sec (16) </p>
</td>	<td>
<p class="tAL">-- response within less than 10 seconds</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">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_TLC_Service"/>
<a name="_Toc442882244"/>
<a name="_Toc442882473"/>
<a name="_Toc442965286"/>
<a name="_Toc455389631"/><span class="requality_text id_e43b478a-ba35-4122-859f-18ad5768a7ca"><a class="requality_id" id="id_e43b478a-ba35-4122-859f-18ad5768a7ca" name="e43b478a-ba35-4122-859f-18ad5768a7ca"/>8	Traffic Light Control (TLC) service</span></h1>
<h2>
<a name="_Toc442882245"/>
<a name="_Toc442882474"/>
<a name="_Toc442965287"/>
<a name="_Toc455389632"/>8.1	TLC service overview</h2>
<p>The Traffic Light Control service is one instantiation of the infrastructure services to manage the generation, transmission of SREM messages and SSEM messages. The TLC service supports prioritization of public transport and public safety vehicles (ambulance, fire brigade, etc.) to traverse a signalized road infrastructure (e.g. intersection) as fast as possible or using a higher priority than ordinary traffic participants. The corresponding SREM is sent by an ITSS (e.g. vehicle) to the traffic infrastructure environment (e.g. R-ITS-S, TCC). In a signalized environment (e.g. intersection) the SREM is sent for requesting traffic light signal priority (public transport) signal preemption (public safety). The service may not only be requested for the approaching signalized environment but also for a sequence of e.g. intersections along a defined traffic route. In response to the request the infrastructure (e.g. R-ITS-S/TLC or TCC) will acknowledge with a SSEM notifying if the request has been granted, canceled or changed in priority due to a more relevant signal request (e.g. ambulance).</p>
<p class="fL">
<div class="embedded" id="rId25"/>
</p>
<p class="tF">
<a name="_Ref418597707"/>Figure 8: Traffic Light Control service example</p>
<p>Figure 8 gives an example of a Bus requesting traffic light signal priority (using SREM) for the defined bus route to the Traffic Control Centre (TCC). The request is sent via the ITS-S Station connected to the Traffic Controller or by other communication facilities. Multiple requests, related to different intersections, are possible to transmit using one SREM only. Depending on prioritization needs, a single request to the approaching Traffic Controller is also possible. The Traffic light controller analyzes the request and returns a SSEM as feedback. Alternatively if the SREM request has been forwarded by the traffic controller to the TCC the SSEM reply will be generated by the TCC and distributed via the R-ITS-S of the corresponding TLC.</p>
<h2>
<a name="_Toc442882246"/>
<a name="_Toc442882475"/>
<a name="_Toc442965288"/>
<a name="_Toc455389633"/>8.2	TLC service</h2>
<p>The TLC service shall provide the communication service defined in clause 4.2 and support additionally the following functionality:</p>
<p class="b1+">Generation of SREM with a single request or sequence of signal requests (e.g. related to several signalized intersections).</p>
<p class="b1+">Generation of SSEM with a signal status response.</p>
<p class="b1+">Single or continuous transmission of SREM and SSEM.</p>
<p class="b1+">Reception of SREM and SSEM.</p>
<h2>
<a name="_Toc442882247"/>
<a name="_Toc442882476"/>
<a name="_Toc442965289"/>
<a name="_Toc455389634"/>8.3	TLC service message and version</h2>
<p>The Signal Control service shall use the SREM as defined in Annex D and the SSEM as defined in Annex E. The header of the SREM and the SSEM are defined in the data dictionary ETSI TS 102 894-2 [2]. The data elements of the SREM and the SSEM payload are defined in ISO/TS 19091 [8].</p>
<p><span class="requality_text id_89b8cf8c-fbae-474e-81d7-1d550dd36762"><a class="requality_id" id="id_89b8cf8c-fbae-474e-81d7-1d550dd36762" name="89b8cf8c-fbae-474e-81d7-1d550dd36762"/>The </span><i><span class="requality_text id_89b8cf8c-fbae-474e-81d7-1d550dd36762">protocolVersion</span></i><span class="requality_text id_89b8cf8c-fbae-474e-81d7-1d550dd36762"> (defined in the header) of SREM based on the present document is set to value "1".</span></p>
<p><span class="requality_text id_66399e8a-0632-497a-9f97-f2d870a4b31f"><a class="requality_id" id="id_66399e8a-0632-497a-9f97-f2d870a4b31f" name="66399e8a-0632-497a-9f97-f2d870a4b31f"/>The </span><i><span class="requality_text id_66399e8a-0632-497a-9f97-f2d870a4b31f">protocolVersion</span></i><span class="requality_text id_66399e8a-0632-497a-9f97-f2d870a4b31f"> (defined in the header) of SSEM based on the present document is set to value "1".</span></p>
<h2>
<a name="_Toc442882248"/>
<a name="_Toc442882477"/>
<a name="_Toc442965290"/>
<a name="_Toc455389635"/>8.4	TLC service dissemination</h2>
<h3>
<a name="_Toc442882249"/>
<a name="_Toc442882478"/>
<a name="_Toc442965291"/>
<a name="_Toc455389636"/>8.4.1	TLC service identification</h3>
<p><span class="requality_text id_9209867a-6a0f-4c16-aedc-d5f64435f14e"><a class="requality_id" id="id_9209867a-6a0f-4c16-aedc-d5f64435f14e" name="9209867a-6a0f-4c16-aedc-d5f64435f14e"/>The SREM is identified by a request identification which is unique.</span> Additionally a sequence number identifies a sequence of requests.<span class="requality_text id_b3f84797-487a-4c3e-a81e-258938163a1c"><a class="requality_id" id="id_b3f84797-487a-4c3e-a81e-258938163a1c" name="b3f84797-487a-4c3e-a81e-258938163a1c"/> If the request or one of the requests with the same request identification has changed, the sequence number will be incremented.</span> <span class="requality_text id_65f67d00-63ae-4d5e-9272-cecfef3beace"><a class="requality_id" id="id_65f67d00-63ae-4d5e-9272-cecfef3beace" name="65f67d00-63ae-4d5e-9272-cecfef3beace"/>For having a clear relation between an SREM request and the SSEM status response, the request identification is used in both messages.</span></p>
<p><span class="requality_text id_d51284f2-a002-4664-b81f-c761eb425ec0"><a class="requality_id" id="id_d51284f2-a002-4664-b81f-c761eb425ec0" name="d51284f2-a002-4664-b81f-c761eb425ec0"/>The SSEM is a reply to a SREM. It uses the request identification of the SREM for identification.</span></p>
<h3>
<a name="_Toc442882250"/>
<a name="_Toc442882479"/>
<a name="_Toc442965292"/>
<a name="_Toc455389637"/>8.4.2	TLC service trigger, update, repetition and termination</h3>
<p>
Show full blame