Skip to content
GitLab
Find file Normal viewHistoryPermalink
TS103301_V104_clean.xhtml 171 KB
Newer Older
filatov's avatar
Initial version of TS103301 requirements
filatov committed
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 275 276 277 278 279 280 281 282 283 284 285 286 287 288 289 290 291 292 293 294 295 296 297 298 299 300 301 302 303 304 305 306 307 308 309 310 311 312 313 314 315 316 317 318 319 320 321 322 323 324 325 326 327 328 329 330 331 332 333 334 335 336 337 338 339 340 341 342 343 344 345 346 347 348 349 350 351 352 353 354 355 356 357 358 359 360 361 362 363 364 365 366 367 368 369 370 371 372 373 374 375 376 377 378 379 380 381 382 383 384 385 386 387 388 389 390 391 392 393 394 395 396 397 398 399 400 401 402 403 404 405 406 407 408 409 410 411 412 413 414 415 416 417 418 419 420 421 422 423 424 425 426 427 428 429 430 431 432 433 434 435 436 437 438 439 440 441 442 443 444 445 446 447 448 449 450 451 452 453 454 455 456 457 458 459 460 461 462 463 464 465 466 467 468 469 470 471 472 473 474 475 476 477 478 479 480 481 482 483 484 485 486 487 488 489 490 491 492 493 494 495 496 497 498 499 500 501 502 503 504 505 506 507 508 509 510 511 512 513 514 515 516 517 518 519 520 521 522 523 524 525 526 527 528 529 530 531 532 533 534 535 536 537 538 539 540 541 542 543 544 545 546 547 548 549 550 551 552 553 554 555 556 557 558 559 560 561 562 563 564 565 566 567 568 569 570 571 572 573 574 575 576 577 578 579 580 581 582 583 584 585 586 587 588 589 590 591 592 593 594 595 596 597 598 599 600 601 602 603 604 605 606 607 608 609 610 611 612 613 614 615 616 617 618 619 620 621 622 623 624 625 626 627 628 629 630 631 632 633 634 635 636 637 638 639 640 641 642 643 644 645 646 647 648 649 650 651 652 653 654 655 656 657 658 659 660 661 662 663 664 665 666 667 668 669 670 671 672 673 674 675 676 677 678 679 680 681 682 683 684 685 686 687 688 689 690 691 692 693 694 695 696 697 698 699 700 701 702 703 704 705 706 707 708 709 710 711 712 713 714 715 716 717 718 719 720 721 722 723 724 725 726 727 728 729 730 731 732 733 734 735 736 737 738 739 740 741 742 743 744 745 746 747 748 749 750 751 752 753 754 755 756 757 758 759 760 761 762 763 764 765 766 767 768 769 770 771 772 773 774 775 776 777 778 779 780 781 782 783 784 785 786 787 788 789 790 791 792 793 794 795 796 797 798 799 800 801 802 803 804 805 806 807 808 809 810 811 812 813 814 815 816 817 818 819 820 821 822 823 824 825 826 827 828 829 830 831 832 833 834 835 836 837 838 839 840 841 842 843 844 845 846 847 848 849 850 851 852 853 854 855 856 857 858 859 860 861 862 863 864 865 866 867 868 869 870 871 872 873 874 875 876 877 878 879 880 881 882 883 884 885 886 887 888 889 890 891 892 893 894 895 896 897 898 899 900 901 902 903 904 905 906 907 908 909 910 911 912 913 914 915 916 917 918 919 920 921 922 923 924 925 926 927 928 929 930 931 932 933 934 935 936 937 938 939 940 941 942 943 944 945 946 947 948 949 950 951 952 953 954 955 956 957 958 959 960 961 962 963 964 965 966 967 968 969 970 971 972 973 974 975 976 977 978 979 980 981 982 983 984 985 986 987 988 989 990 991 992 993 994 995 996 997 998 999 1000 
<?xml version="1.0" encoding="UTF-8"?>
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<style>${[cssclasses]}</style>
<meta name="Content-Type" content="application/vnd.openxmlformats-officedocument.wordprocessingml.document" />
<title></title>
</head>
<body>
<p class="header">Draft ETSI TS 103 301 V1.0.4 (2016-04)</p>
<p class="header">4</p>
<p class="header"></p>
<p class="header"></p>
<p class="zA">
<a name="_GoBack"></a>Draft ETSI TS 103 301 V1.0.4 (2016-04)</p>
<p class="zT">Intelligent Transport Systems (ITS);</p>
<p class="zT">Vehicular Communications;</p>
<p class="zT">Basic Set of Applications;</p>
<p class="zT">Facilities layer protocols and communication requirements</p>
<p class="zT">for infrastructure services</p>
<p class="zG"></p>
<p class="zD"></p>
<p class="zB"></p>
<p></p>
<p></p>
<p></p>
<p></p>
<p></p>
<p class="zB"></p>
<p class="fP"></p>
<p class="zB">
<b>Technical Specification</b>
</p>
<p class="header">
<img src="embedded/image1.jpeg" alt="ETSI_BG_final_new" />
</p>
<p></p>
<p class="footer"></p>
<p class="footer"></p>
<p class="fP">Reference</p>
<p class="fP">DTS/ITS-00166</p>
<p class="fP">Keywords</p>
<p class="fP">application, data, ITS, protocol, requirements</p>
<p></p>
<p class="fP">
<b>
<i>ETSI</i>
</b>
</p>
<p class="fP">650 Route des Lucioles</p>
<p class="fP">F-06921 Sophia Antipolis Cedex - FRANCE</p>
<p class="fP"></p>
<p class="fP">Tel.: +33 4 92 94 42 00   Fax: +33 4 93 65 47 16</p>
<p class="fP"></p>
<p class="fP">Siret N° 348 623 562 00017 - NAF 742 C</p>
<p class="fP">Association à but non lucratif enregistrée à la</p>
<p class="fP">Sous-Préfecture de Grasse (06) N° 7803/88</p>
<p class="fP"></p>
<p></p>
<p></p>
<p class="fP">
<b>
<i>Important notice</i>
</b>
</p>
<p class="fP">The present document can be downloaded from:<br />
<a href="http://www.etsi.org/standards-search">http://www.etsi.org/standards-search</a>
</p>
<p class="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>
<p class="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 <a href="https://portal.etsi.org/TB/ETSIDeliverableStatus.aspx">https://portal.etsi.org/TB/ETSIDeliverableStatus.aspx</a>
</p>
<p class="fP">If you find errors in the present document, please send your comment to one of the following services:<br />
<a href="https://portal.etsi.org/People/CommiteeSupportStaff.aspx">https://portal.etsi.org/People/CommiteeSupportStaff.aspx</a>
</p>
<p class="fP">
<b>
<i>Copyright Notification</i>
</b>
</p>
<p class="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>
<p class="fP"></p>
<p class="fP">© European Telecommunications Standards Institute 2016.</p>
<p class="fP">All rights reserved.<br />
</p>
<p>
<b>DECT</b>TM, <b>PLUGTESTS</b>TM, <b>UMTS</b>TM and the ETSI logo are Trade Marks of ETSI registered for the benefit of its Members.<br />
<b>3GPP</b>TM and <b>LTE</b>™ are Trade Marks of ETSI registered for the benefit of its Members and<br />of the 3GPP Organizational Partners.<br />
<b>GSM</b>® and the GSM logo are Trade Marks registered and owned by the GSM Association.</p>
<p>
<br />
</p>
<p class="tT">Contents</p>
<p class="toc_1">Intellectual Property Rights	5</p>
<p class="toc_1">Foreword	5</p>
<p class="toc_1">Modal verbs terminology	5</p>
<p class="toc_1">Introduction	5</p>
<p class="toc_1">1	Scope	6</p>
<p class="toc_1">2	References	6</p>
<p class="toc_2">2.1	Normative references	6</p>
<p class="toc_2">2.2	Informative references	7</p>
<p class="toc_1">3	Definitions and abbreviations	7</p>
<p class="toc_2">3.1	Definitions	7</p>
<p class="toc_2">3.2	Abbreviations	8</p>
<p class="toc_1">4	Infrastructure services introduction and general requirements	9</p>
<p class="toc_2">4.1	Naming convention	9</p>
<p class="toc_2">4.2	Infrastructure services in the ITS communications architecture	9</p>
<p class="toc_2">4.3	Infrastructure services in the ITS organizational architecture	10</p>
<p class="toc_2">4.4	Interfaces of the infrastructure services	11</p>
<p class="toc_3">4.4.1	Interface between Application layer and Facilities layer	11</p>
<p class="toc_3">4.4.2	Interface between Facilities layer and Management entity	11</p>
<p class="toc_3">4.4.3	Interface between Facilities layer and Security entity	12</p>
<p class="toc_3">4.4.4	Interface between Facilities layer and the N&amp;T layer	12</p>
<p class="toc_2">4.5	Common protocol requirements for infrastructure services	12</p>
<p class="toc_3">4.5.1	Security for messages used by infrastructure	12</p>
<p class="toc_3">4.5.2	Message payload encapsulation	12</p>
<p class="toc_3">4.5.3	Message encoding scheme	13</p>
<p class="toc_2">4.6	Protocol version	13</p>
<p class="toc_3">4.6.1	Protocol version definition	13</p>
<p class="toc_3">4.6.2	Protocol version handling	13</p>
<p class="toc_1">5	Traffic Light Maneuver (TLM) service	14</p>
<p class="toc_2">5.1	TLM service overview	14</p>
<p class="toc_2">5.2	TLM service	14</p>
<p class="toc_2">5.3	TLM service message and version	14</p>
<p class="toc_2">5.4	TLM service dissemination	14</p>
<p class="toc_3">5.4.1	TLM service identification	15</p>
<p class="toc_3">5.4.2	TLM service trigger, update, repetition and termination	15</p>
<p class="toc_3">5.4.3	TLM service communication requirements	15</p>
<p class="toc_4">5.4.3.1	TLM service communication overview	15</p>
<p class="toc_4">5.4.3.2	TLM service communication requirements for short range access technologies	15</p>
<p class="toc_4">5.4.3.3	TLM service communication requirements for long range communication	17</p>
<p class="toc_1">6	Road and Lane Topology (RLT) service	17</p>
<p class="toc_2">6.1	RLT service overview	17</p>
<p class="toc_2">6.2	RLT service	18</p>
<p class="toc_2">6.3	RLT service message and version	18</p>
<p class="toc_2">6.4	RLT service dissemination	19</p>
<p class="toc_3">6.4.1	RLT service identification	19</p>
<p class="toc_3">6.4.2	RLT service trigger, update, repetition and termination	19</p>
<p class="toc_3">6.4.3	RLT service communication requirements	19</p>
<p class="toc_4">6.4.3.1	RLT service communication overview	19</p>
<p class="toc_4">6.4.3.2	RLT service communication requirements for short range access technologies	19</p>
<p class="toc_4">6.4.3.3	RLT service dissemination parameters for long range communication	21</p>
<p class="toc_1">7	Infrastructure to Vehicle Information (IVI) service	21</p>
<p class="toc_2">7.1	IVI service overview	21</p>
<p class="toc_2">7.2	IVI service	21</p>
<p class="toc_2">7.3	IVI service message and version	22</p>
<p class="toc_2">7.4	IVI service dissemination	22</p>
<p class="toc_3">7.4.1	IVI service identification	22</p>
<p class="toc_3">7.4.2	IVI service trigger, update, repetition and termination	22</p>
<p class="toc_3">7.4.3	IVI service communication requirements	23</p>
<p class="toc_4">7.4.3.1	IVI service communication parameters for short-range communication	23</p>
<p class="toc_4">7.4.3.2	IVI service dissemination parameters for long-range communication	25</p>
<p class="toc_1">8	Traffic Light Control (TLC) service	26</p>
<p class="toc_2">8.1	TLC service overview	26</p>
<p class="toc_2">8.2	TLC service	27</p>
<p class="toc_2">8.3	TLC service message and version	27</p>
<p class="toc_2">8.4	TLC service dissemination	28</p>
<p class="toc_3">8.4.1	TLC service identification	28</p>
<p class="toc_3">8.4.2	TLC service trigger, update, repetition and termination	28</p>
<p class="toc_3">8.4.3	TLC service communication parameters	28</p>
<p class="toc_4">8.4.3.1	TLC service service communication overview	28</p>
<p class="toc_4">8.4.3.2	TLC service communication parameters for short range access technologies	29</p>
<p class="toc_4">8.4.3.3	TLC service communication parameters for long range communication	31</p>
<p class="toc_1">9	Basic services running on ITS infrastructure devices	32</p>
<p class="toc_2">9.1	Basic service overview	32</p>
<p class="toc_2">9.2	DEN service on ITS infrastructure devices	32</p>
<p class="toc_2">9.3	CA service on ITS infrastructure devices	32</p>
<p class="toc_1">10	Communication Parameter Settings	33</p>
<p class="toc_2">10.1	Overview	33</p>
<p class="toc_2">10.2	CPS_001	33</p>
<p class="toc_2">10.3	CPS_002	34</p>
<p class="toc_2">10.4	CPS_003	34</p>
<p class="toc_2">10.5	CPS_004	35</p>
<p class="toc_2">10.6	CPS_005	35</p>
<p class="toc_1">11	Security Profile	35</p>
<p class="toc_8">Annex A (normative): ASN.1 specification of SPATEM	36</p>
<p class="toc_8">Annex B (normative): ASN.1 specification of MAPEM	37</p>
<p class="toc_8">Annex C (normative): ASN.1 specification of IVIM	38</p>
<p class="toc_8">Annex D (normative): ASN.1 specification of SREM	39</p>
<p class="toc_8">Annex E (normative): ASN.1 specification of SSEM	40</p>
<p class="toc_8">Annex F (informative): Bibliography	41</p>
<p class="toc_1">History	42</p>
<p></p>
<p>
<br />
</p>
<h1>
<a name="_Toc442882188"></a>
<a name="_Toc442882417"></a>
<a name="_Toc442965230"></a>
<a name="_Toc455389572"></a>Intellectual Property Rights</h1>
<p>
<a name="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 (<a href="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>
<a name="_Toc442882189"></a>
<a name="_Toc442882418"></a>
<a name="_Toc442965231"></a>
<a name="_Toc455389573"></a>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>
<h1>
<a name="_Toc441580672"></a>
<a name="_Toc442882190"></a>
<a name="_Toc442882419"></a>
<a name="_Toc442965232"></a>
<a name="_Toc455389574"></a>Modal verbs terminology</h1>
<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 <a href="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>
<a name="_Toc442882191"></a>
<a name="_Toc442882420"></a>
<a name="_Toc442965233"></a>
<a name="_Toc455389575"></a>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 />
</p>
<h1>
<a name="_Toc442882192"></a>
<a name="_Toc442882421"></a>
<a name="_Toc442965234"></a>
<a name="_Toc455389576"></a>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>
<h1>
<a name="_Toc442882193"></a>
<a name="_Toc442882422"></a>
<a name="_Toc442965235"></a>
<a name="_Toc455389577"></a>2	References</h1>
<h2>
<a name="_Toc442882194"></a>
<a name="_Toc442882423"></a>
<a name="_Toc442965236"></a>
<a name="_Toc455389578"></a>2.1	Normative references</h2>
<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 <a href="https://docbox.etsi.org/Reference/">https://docbox.etsi.org/Reference/</a>.</p>
<p class="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>
<p class="eX">
<a name="REF_EN302665"></a>[1]	ETSI EN 302 665 (V1.1.1): "Intelligent Transport Systems (ITS); Communications Architecture".</p>
<p class="eX">
<a name="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>
<p class="eX">
<a name="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>
<p class="eX">
<a name="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>
<p class="eX">
<a name="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>
<p class="eX">
<a name="REF_TS103097"></a>[6]	ETSI TS 103 097 (V1.2.1): "Intelligent Transport Systems (ITS); Security; Security header and certificate formats".</p>
<p class="eX">
<a name="REF_CENISOTS19321_2015"></a>[7]	CEN ISO/TS 19321-2015: "Intelligent transport systems – Cooperative ITS – Dictionary of in-vehicle information (IVI) data structures".</p>
<p class="eX">
<a name="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>
<p class="eX">
<a name="REF_EN302931"></a>[9]	ETSI EN 302 931 (V1.1.1): "Intelligent Transport Systems (ITS); Vehicular Communications; Geographical Area Definition".</p>
<p class="eX">
<a name="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>
<p class="eX">
<a name="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>
<p class="eX">
<a name="REF_ITU_TX691"></a>[12]	Recommendation ITU-T X.691/ISO/IEC 8825-2 (1997-12): "Information technology - ASN.1 encoding rules: Specification of Packed Encoding Rules (PER)".</p>
<p class="eX">
<a name="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>
<p class="eX">
<a name="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>
<p class="eX">
<a name="REF_ISO17419"></a>[15]	ISO TS17419 V2016-02-09: "ITS-AID_AssignedNumbers" (<a href="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>
<p class="eX">
<a name="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>
<p class="eX"></p>
<h2>
<a name="_Toc442882195"></a>
<a name="_Toc442882424"></a>
<a name="_Toc442965237"></a>
<a name="_Toc455389579"></a>2.2	Informative references</h2>
<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 class="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>
<p class="eX">
<a name="REF_TR102965"></a>[i.1]	ETSI TS 102 965 (V1.2.1): "Intelligent Transport Systems (ITS); Application object identifier (ITS-AID); Registration list".</p>
<p class="eX">
<a name="REF_ISOTS17423"></a> [i.2]	ISO/TS 17423:2014: "Intelligent Transport Systems – Cooperative Systems – Application requirements for selection of communication profiles".</p>
<p class="eX">
<a name="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>
<p class="eX">
<a name="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>
<p class="eX">
<a name="REF_ISO14832"></a>[i.5]	ISO  EN 14823: " Intelligent transport systems – Graphic data dictionary".</p>
<p class="eX">
<a name="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>
<p class="eX">[i.7]	IETF Internet-Draft “Transport Layer Security (TLS) Authentication using ITS ETSI and IEEE certificates”, draft-lonc-tls-certieee1609-01.txt</p>
<p class="eX"></p>
<h1>
<a name="_Toc442882196"></a>
<a name="_Toc442882425"></a>
<a name="_Toc442965238"></a>
<a name="_Toc455389580"></a>3	Definitions and abbreviations</h1>
<h2>
<a name="_Toc455389581"></a>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>
<p class="nO">NOTE: The definition is compliant to ETSI EN 302 637-3 [14].</p>
<p>
<b>Driver awareness zone:</b> area in which the driver will be informed about upcoming situations</p>
<p class="nO">NOTE: The definition is compliant to ISO/TS 19321 [7].</p>
<p>
<b>Minimum dissemination area:</b> minimum area where an information is disseminated by an ITS-S based on application requirements</p>
<p>NOTE: The definition is compliant to ISO/TS 19321 [7].</p>
<p>
<b>Relevance zone:</b> area where the information is applicable</p>
<p>NOTE: The definition is compliant to ISO/TS 19321 [7].</p>
<p>
<b>Long range:</b> Communication with coverage of more than 500 meters (e.g. cellular systems)</p>
<p>
<b>MAPEM:</b> Road/lane topology and traffic maneuver message</p>
<p class="nO">NOTE:	As defined in Annex B including the corresponding extensions defined in ISO/TS 19091 [8].</p>
<p>
<b>Short range:</b> Communication with coverage of approximately 500 meters (e.g. WiFi)</p>
<p>
<b>ITS-G5: </b>access technology to be used in frequency bands dedicated for European intelligent transport System (ITS)</p>
<h2>
<a name="_Toc455389582"></a>3.2	Abbreviations</h2>
<p>For the purposes of the present document, the following abbreviations apply:</p>
<p class="eW">ADU	Application Data Unit</p>
<p class="eW">AID	Action Identifier</p>
<p class="eW">APU	Application Protocol Unit</p>
<p class="eW">ASN	Anstract Syntax Notation</p>
<p class="eW">BTP	Basic Transport Protocol</p>
<p class="eW">CA	Certifiaction Authority</p>
<p class="eW">C-ITS	Cooperative ITS</p>
<p class="eX">C-ITS-S	Cooperative ITS-S</p>
<p class="nO">NOTE:	Server managing R-ITS-S roadside station.</p>
<p class="eW">DAZ	Driver Awareness Zone</p>
<p class="eW">DE	Data Element</p>
<p class="eW">DEN	Decentralized Environmental Notification</p>
<p class="eW">DENM	DEN Message</p>
<p class="eW">GBC	GeoBroadCast</p>
<p class="eW">GN	GeoNetworking</p>
<p class="eW">GPCH	General Purpose CHannel</p>
<p class="eW">ITS-AID	ITSApplication Identifier</p>
<p class="eW">ITIS	International Traveler Information Systems</p>
<p class="eW">ITS	Intelligent Transport System</p>
<p class="eW">ITS-S	ITS Station</p>
<p class="eW">ITS-SCP	ITS-S Communication Profile</p>
<p class="eW">ITU-T	International Telecommunication Union – Telecommunication</p>
<p class="eX">IVI	Infrastructure to Vehicle Information</p>
<p class="nO">NOTE:	As defined in clause 7.</p>
<p class="eX">IVIM	Infrastructure to Vehicle Information Message</p>
<p class="nO">NOTE:	As defined in Annex C.</p>
<p class="eX">MDA	Minimum Dissemination Area</p>
<p class="eW">MF-SAP	Management Facilities layer SAP</p>
<p class="eW">MSB	Most Significant Bit</p>
<p class="eX">MTU	Maximum Transmit Unit</p>
<p class="nO">NOTE:	E.g. 1 500 bytes on Ethernet.</p>
<p class="eW">PDU	Protocol Data Unit</p>
<p class="eW">PER	Packet Encoding Rule</p>
<p class="eW">R-ITS-S	Roadside ITS Station</p>
<p class="eX">RLT	Road and Lane Topology</p>
<p class="nO">NOTE:	As defined in clause 6.</p>
<p class="eX">RZ	Relevance Zone</p>
<p class="eW">SAP	Service Access Primitive</p>
<p class="eW">SCH	Service Channel	</p>
<p class="eW">SHB	Single Hop Broadcast</p>
<p class="eX">SPATEM	Signal Phase And Timing Message</p>
<p class="nO">NOTE:	As defined in Annex A including the corresponding extensions defined in ISO/TS 19091 [8].</p>
<p class="eX">SREM	Signal Request Message</p>
<p class="nO">NOTE:	As defined in Annex B including the corresponding extensions defined in ISO/TS 19091 [8].</p>
<p class="eX">SSEM	Signal Request Status Message</p>
<p class="nO">NOTE	As defined in Annex B including the corresponding extensions defined in ISO/TS 19091 [8].</p>
<p class="eW">SSP	Service Specific Permissions</p>
<p class="eW">TCC	Traffic Control Center</p>
<p class="eX">TLC	Traffic Light Control</p>
<p class="nO">NOTE:	As defined in clause 8.</p>
<p class="eW">TLM	Traffic Light Maneuver</p>
<p class="eW">TSB	Topological Scope Broadcast</p>
<p class="eW">UDP	User Datagram Protocol</p>
<p class="eX">V-ITS-S	Vehicular and personal ITS Station</p>
<p class="nO">NOTE:	In this present document the abbreviation V-ITS-S represents all ITS based equipment used by the end user.</p>
<p class="eX">WLAN	Wireless Local Area Network</p>
<h1>
<a name="_Toc442882197"></a>
<a name="_Toc442882426"></a>
<a name="_Toc442965239"></a>
<a name="_Toc455389583"></a>4	Infrastructure services introduction and general requirements</h1>
<h2>
<a name="_Toc442882198"></a>
<a name="_Toc442882427"></a>
<a name="_Toc442965240"></a>
<a name="_Toc455389584"></a>4.1	Naming convention</h2>
<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 &amp; Transport layer with a set of communication parameters.</p>
<p class="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>
<a name="clause_Infrastr_services_in_the_ITS"></a>
<a name="_Toc442882199"></a>
<a name="_Toc442882428"></a>
<a name="_Toc442965241"></a>
<a name="_Toc455389585"></a>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>
<p class="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>
<p class="b1+">MAPEM as defined in Annex B. The corresponding service entity is referred as "Road and Lane Topology" - RLT service in the present document. RLT service is specified in clause 6 of the present document.</p>
<p class="b1+">IVIM as defined in Annex C. The corresponding service entity is referred as "Infrastructure to Vehicle Information" - IVI service in the present document. IVI service is specified in clause 7 of the present document.</p>
<p class="b1+">SREM as specified in Annex D. The corresponding service entity is referred as "Traffic Light Control" - TLC service in the present document. TLC service is specified in clause 8 of the present document.</p>
<p class="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>
<p class="nO">NOTE:	Other messages may be supported by infrastructure services in the future.</p>
<p class="fL">
<div id="rId18" class="embedded"></div>
</p>
<p class="tF">
<a name="_Ref326015634"></a>Figure 1: Infrastructure services within the ITS-S architecture</p>
<p>The infrastructure service shall provide at least the following functions.</p>
<p>For the transmission service:</p>
<p class="b1+">Message encoding;</p>
<p class="b1+">Transmission management.</p>
<p>For the reception service:</p>
<p class="b1+">Message decoding;</p>
<p class="b1+">Reception management.</p>
<h2>
<a name="_Toc442882200"></a>
<a name="_Toc442882429"></a>
<a name="_Toc442965242"></a>
<a name="_Toc455389586"></a>4.3	Infrastructure services in the ITS organizational architecture</h2>
<p>Within the role "System Operation" as defined in ISO/TS 17427 [10], the following sub roles are relevant for the infrastructure services:</p>
<p class="b1+">"Content Provision" is responsible for generating the information that is conveyed in the message. This task is included in any application providing information to the application which generates the payload.</p>
<p class="b1+">"Service Provision" is responsible for the generation of the payload and the transmission of the message using an ITS-S. This task is managed by the application making use of the infrastructure services.</p>
<p class="b1+">"Service Presentation" is responsible for the reception of the messages and its processing and presentation. This task is managed by the infrastructure services and the application.</p>
<p class="fL">
<img src="embedded/image3.emf" alt="" />
</p>
<p class="tF">Figure 2: Identification of sub-roles of the role system (lifecycle)<br />operation in the ITS organizational architecture</p>
<h2>
<a name="_Toc442882201"></a>
<a name="_Toc442882430"></a>
<a name="_Toc442965243"></a>
<a name="_Toc455389587"></a>4.4	Interfaces of the infrastructure services</h2>
<h3>
<a name="_Toc442882202"></a>
<a name="_Toc442882431"></a>
<a name="_Toc442965244"></a>
<a name="_Toc455389588"></a>4.4.1	Interface between Application layer and Facilities layer</h3>
<p>The infrastructure services within the Facilities layer provide APIs to applications for the processing of the payload at the transmitting  ITS-S and the receiving ITS-S. An application may execute requests to the infrastructure services in the Facilities layer to trigger, update or terminate transmission of a message. In addition, a set of Facilities control information is passed as specified in table 1.</p>
<p>Table 1 presents the Facilities control Information (SAP primitives) contained in an application request.</p>
<p class="tH">
<a name="_Ref414288410"></a>Table 1: Facilities control information (SAP primitives)</p>
<table>
<tbody>
<tr>	<td>
<p class="tAH">Category</p>
</td>	<td>
<p class="tAH">Data</p>
</td>	<td>
<p class="tAH">Definition</p>
</td>
</tr>
<tr>	<td>
<p class="tAL">Data passed from application to infrastructure services</p>
</td>	<td>
<p class="tAL">Infrastructure message identification</p>
</td>	<td>
<p class="tAL">Identification of the message</p>
</td>
</tr>
<tr>	<td>
<p class="tAL"></p>
</td>	<td>
<p class="tAL">Request type</p>
</td>	<td>
<p class="tAL">Trigger, update or ending of transmission</p>
</td>
</tr>
<tr>	<td>
<p class="tAL"></p>
</td>	<td>
<p class="tAL">Dissemination parameter</p>
</td>	<td>
<p class="tAL">For more details see the dissemination profile for each service in the clauses 5 to 8</p>
</td>
</tr>
<tr>	<td>
<p class="tAL"></p>
</td>	<td>
<p class="tAL">Traffic class</p>
</td>	<td>
<p class="tAL">GN traffic class as defined in ETSI EN 302 636-4-1 [3], if GeoNetworking/BTP is used</p>
</td>
</tr>
<tr>	<td>
<p class="tAL"></p>
</td>	<td>
<p class="tAL">Payload</p>
</td>	<td>
<p class="tAL">Information contained in payload</p>
</td>
</tr>
<tr>	<td>
<p class="tAL">Data returned from I2V service to the requesting application</p>
</td>	<td>
<p class="tAL">actionID or<br />other applicable identifier</p>
</td>	<td>
<p class="tAL">The infrastructure service returns the message identification or other applicable identifier created by the infrastructure service to the requesting application</p>
</td>
</tr>
<tr>	<td>
<p class="tAL"></p>
</td>	<td>
<p class="tAL">Failure notification</p>
</td>	<td>
<p class="tAL">The infrastructure service returns a failure notification to the requesting application</p>
</td>
</tr>
</tbody>
</table>
<p></p>
<h3>
<a name="_Toc442882203"></a>
<a name="_Toc442882432"></a>
<a name="_Toc442965245"></a>
<a name="_Toc455389589"></a>4.4.2	Interface between Facilities layer and Management entity</h3>
<p>The infrastructure services may exchange information with the Management entity. This includes the default service communication parameters specified in clauses 5 to 8. The interface MF-SAP may be realized as the MF-SAP ETSI TS 102 723-5 [11].</p>
<h3>
<a name="_Toc442882204"></a>
<a name="_Toc442882433"></a>
<a name="_Toc442965246"></a>
<a name="_Toc455389590"></a>4.4.3	Interface between Facilities layer and Security entity</h3>
<p>The infrastructure service may exchange information with the Security entity. The interface SF-SAP may be realized as the SF-SAP ETSI TS 102 723-9 [i.6].</p>
<h3>
<a name="_Toc442882205"></a>
<a name="_Toc442882434"></a>
<a name="_Toc442965247"></a>
<a name="_Toc455389591"></a>4.4.4	Interface between Facilities layer and the N&amp;T layer</h3>
<p>The infrastructure services deliver the message as payload to the Networking &amp; Transport Layer for dissemination via the NF-SAP.</p>
<p>The Networking &amp; Transport Layer indicates the reception of an ITS message to the infrastructure services.</p>
<h2>
<a name="_Toc442882206"></a>
<a name="_Toc442882435"></a>
<a name="_Toc442965248"></a>
<a name="_Toc455389592"></a>4.5	Common protocol requirements for infrastructure services</h2>
<h3>
<a name="_Toc442882207"></a>
<a name="_Toc442882436"></a>
<a name="_Toc442965249"></a>
<a name="_Toc455389593"></a>4.5.1	Security for messages used by infrastructure</h3>
<p>The security mechanisms for messages used by the infrastructure service as specified in the present document shall use the message authentication with signatures to be verified at the receiving ITS-S with public keys contained in certificates. A certificate indicates its holder's permissions, i.e. what statements the holder is allowed to make or privileges it is allowed to assert in a message signed by that certificate. The format for the certificates shall be as specified in ETSI TS103 097 [6].</p>
<p>Service permissions are indicated by a pair of identifiers within a certificate, the ITS-AID and the SSP. The ITSApplication Identifier (ITS-AID) as given in ETSI TS 102 965 [i.1] indicates the overall type of permissions being granted.</p>
<p>The Service Specific Permissions (SSP) is a field that indicates specific sets of permissions within the overall permissions indicated by the ITS-AID. The originating ITS-S shall provide SSP information in its certificate for all generated, signed messages. The SSP permissions are defined for each message in the corresponding clause. The common approach that is used for all messages is that  the SSP information is constructed out of N octets with a maximum length as specified in ETSI TS 103 097 [6]. For each octet, the most significant bit (MSB) shall be the leftmost bit.  The transmission order shall always be the MSB first. <span class="requality_text id_c8ae979e-6c54-4b01-8ce1-0ce4e8b853ac"><a name="c8ae979e-6c54-4b01-8ce1-0ce4e8b853ac" id="id_c8ae979e-6c54-4b01-8ce1-0ce4e8b853ac" class="requality_id"></a>The first octet shall control the SSP version and be interpreted in the following way:</span></p><span class="requality_text id_c8ae979e-6c54-4b01-8ce1-0ce4e8b853ac">
</span><p class="eX"><span class="requality_text id_c8ae979e-6c54-4b01-8ce1-0ce4e8b853ac">0: 	No version, length 1 octet; the value shall only be used for testing purposes.</span></p><span class="requality_text id_c8ae979e-6c54-4b01-8ce1-0ce4e8b853ac">
</span><p class="eX"><span class="requality_text id_c8ae979e-6c54-4b01-8ce1-0ce4e8b853ac">1: 	First version, SSP contains information as defined in the present document.</span></p><span class="requality_text id_c8ae979e-6c54-4b01-8ce1-0ce4e8b853ac">
</span><p class="eX"><span class="requality_text id_c8ae979e-6c54-4b01-8ce1-0ce4e8b853ac">2 to 255:	Reserved for future usage.</span></p>
<p><span class="requality_text id_02e92920-4241-4fd0-bb41-5e09fb7402ca"><a name="02e92920-4241-4fd0-bb41-5e09fb7402ca" id="id_02e92920-4241-4fd0-bb41-5e09fb7402ca" class="requality_id"></a>At reception of a message, the ITS-S shall check whether the message content is consistent with the SSP contained in the certificate in its signature. If the consistency check fails, the message shall be discarded.</span></p>
<h3>
<a name="_Toc442882208"></a>
<a name="_Toc442882437"></a>
<a name="_Toc442965250"></a>
<a name="_Toc455389594"></a>4.5.2	Message payload encapsulation</h3>
<p>The <i>ItsPduHeader</i> header as defined in ETSI TS102 894-2 [2] shall be used to encapsulate the payload in order to construct messages. The ITS PDU header includes the following elements:</p>
<p class="b1+">
<i>protocolVersion</i>: Version of the ITS payload contained in the message as defined for the specific infrastructure service.</p>
<p class="b1+">
<i>messageID</i>: Type of the ITS payload contained in the message as defined for the specific infrastructure service.</p>
<p class="b1+">
<i>stationID</i>: Identifier of the ITS-S that generated the message.</p>
<p>The <i>messageID</i> data element allows the receiver to identify the ITS message and to make it available to the corresponding Facilities layer service.</p>
<p>The <i>protocolVersion</i> data element allows the receiver to correctly deal with different versions of the protocol specification for the message.</p>
<p>More detailed information is covered in the Annexes A to E.</p>
<h3>
<a name="_Toc442882209"></a>
<a name="_Toc442882438"></a>
<a name="_Toc442965251"></a>
<a name="_Toc455389595"></a>4.5.3	Message encoding scheme </h3>
<p>Unless specified otherwise, the Unaligned PER encoding scheme as specified in Recommendation ITU-T X.691 [12] shall be used for the encoding of the messages specified in the present document.</p>
<h2>
<a name="_Toc442882210"></a>
<a name="_Toc442882439"></a>
<a name="_Toc442965252"></a>
<a name="_Toc455389596"></a>4.6	Protocol version</h2>
<h3>
<a name="_Toc442882211"></a>
<a name="_Toc442882440"></a>
<a name="_Toc442965253"></a>
<a name="_Toc455389597"></a>4.6.1	Protocol version definition</h3>
<p>The value of the protocol version for the messages SPATEM, MAPEM, IVIM, SREM, SSEM is individual and independent of each other. It is defined in the <i>ItsPduHeader</i> for each message and identified by the <i>protocolVersion</i> data element (see clauses 5 to 8).</p>
<h3>
<a name="_Toc442882212"></a>
<a name="_Toc442882441"></a>
<a name="_Toc442965254"></a>
<a name="_Toc455389598"></a>4.6.2	Protocol version handling</h3>
<p>If the ASN.1 definition of the protocol is extended without compromising the backwards compatibility, the data element <i>protocolVersion</i> will not be increased. This allows the receiving ITS-S to process the message correctly (except the extnsions) without the need for immediate update. An update for protocol interoperability is not needed, unless the receiving ITS-Station is intended to correctly interpret also the added extensions.</p>
<p>The <i>protocolVersion</i> data element is increased only in case of non-backwards compatible changes in the protocol specification to allow the receiving ITS-S to handle the message appropriately.</p>
<p>An example of how a receiving ITS-Station deals with messages according to the <i>protocolVersion</i> data element is shown in Table 2.</p>
<p>In the example the Version "V1" is the published version (<i>protocolVersion</i> = 1). Private extensions indicate extensions that are either not standardized or only recognized in a specific application context, e.g. applications implementing extensions for usage within local geographical regions. Version "V2" indicates a published, nonbackwards compatible extension (<i>protocolVersion</i> = 2).</p>
<p>It is recommended that all changes to the protocol specification are additions using the ASN.1 extensions mechanism. These can be:</p>
<p class="b1+">Private (non-standardized) extensions: the support for this is limited and its use is discouraged.</p>
<p class="b1+">Standardized extensions as part as new version of published standards.</p>
<p class="tH">
<a name="_Ref440282843"></a>Table 2: Example for handlingof messages with different protocol versions</p>
<table>
<tbody>
<tr>	<td>
<p class="tAH">Sending ITS-S</p>
<p class="tAH">Implemented version of the protocol</p>
</td>	<td>
<p class="tAH">Receiving ITS-S</p>
<p class="tAH">Implemented version of the protocol</p>
</td>	<td>
<p class="tAH">Receiving ITS-S</p>
<p class="tAH">Decoding result</p>
</td>
</tr>
<tr>	<td>
<p class="tAL">V1</p>
</td>	<td>
<p class="tAL">V1</p>
</td>	<td>
<p class="tAL">Support of V1</p>
</td>
</tr>
<tr>	<td>
<p class="tAL">V1 with private extensions</p>
</td>	<td>
<p class="tAL">V1</p>
</td>	<td>
<p class="tAL">Support of V1 and<br />no support of private extensions</p>
</td>
</tr>
<tr>	<td>
<p class="tAL">V1 with private extensions</p>
</td>	<td>
<p class="tAL">V1 with same private extensions as the sending ITS-S</p>
</td>	<td>
<p class="tAL">Support of V1 and<br />and support of private extensions from the sending ITS-S</p>
</td>
</tr>
<tr>	<td>
<p class="tAL">V1 with private extensions</p>
</td>	<td>
<p class="tAL">V1 with other private extensions as the sending ITS-S</p>
</td>	<td>
<p class="tAL">Support of V1 and<br />no support of private extensions from the sending ITS-S</p>
</td>
</tr>
<tr>	<td>
<p class="tAL">V1 with private extensions</p>
</td>	<td>
<p class="tAL">V2</p>
</td>	<td>
<p class="tAL">No support of V1 and<br />no support of private V1 extensions</p>
</td>
</tr>
<tr>	<td>
<p class="tAL">V2 (V1 with published extensions, included after the extension mark)</p>
</td>	<td>
<p class="tAL">V1</p>
</td>	<td>
<p class="tAL">Support of V1</p>
</td>
</tr>
<tr>	<td>
<p class="tAL">V2 (V1 with published extensions, included after extension mark)</p>
</td>	<td>
<p class="tAL">V2 with published extensions</p>
</td>	<td>
<p class="tAL">Support of V2</p>
</td>
</tr>
<tr>	<td>
<p class="tAL">V2 (changes in the data elements, included before the extension mark)</p>
</td>	<td>
<p class="tAL">V2</p>
</td>	<td>
<p class="tAL">No support of V2</p>
</td>
</tr>
</tbody>
</table>
<p></p>
<h1>
<a name="clause_TLM_service"></a>
<a name="_Toc442882213"></a>
<a name="_Toc442882442"></a>
<a name="_Toc442965255"></a>
<a name="_Toc455389599"></a><span class="requality_text id_8724cfcb-6374-41c4-993d-1b5c319eb8cf"><a name="8724cfcb-6374-41c4-993d-1b5c319eb8cf" id="id_8724cfcb-6374-41c4-993d-1b5c319eb8cf" class="requality_id"></a>5	Traffic Light Maneuver (TLM) service</span></h1>
<h2>
<a name="_Toc442882214"></a>
<a name="_Toc442882443"></a>
<a name="_Toc442965256"></a>
<a name="_Toc455389600"></a>5.1	TLM service overview</h2>
<p>The TLM service is one instantiation of the infrastructure services to manage the generation, transmission and reception of SPATEM messages. The TLM service includes safety-related information for supporting traffic participants (vehicles, pedestrians, etc.) to execute safe maneuvers in an intersection area. The goal is to enter and exit an intersection "conflict area" in a controlled way. The TLM service informs in real-time about the operational states of the traffic light controller, the current signal state, the residual time of the state before changing to the next state, the allowed maneuvers and provides assistance for crossing. Additionally the TLM service foresees the inclusion of detailed green way advisory information and the status for public transport prioritization.</p>
<p class="fL">
<div id="rId21" class="embedded"></div>
</p>
<p class="tF">
<a name="_Ref415031170"></a>Figure 3: Signaling status of the maneuvers in an intersection</p>
<p>Figure 3 gives an example of the TLM service describing the driving permissions given to the traffic streams. The connection lanes (see clause 6), which describe the allowed maneuver, are highlighted based on the signaling status of the traffic light controller. The status information (e.g. "stop", "go") transmitted by the traffic controller is depicted in Figure 3 with red and green connection lines, respectively.</p>
<h2>
<a name="_Toc442882215"></a>
<a name="_Toc442882444"></a>
<a name="_Toc442965257"></a>
<a name="_Toc455389601"></a>5.2	TLM service</h2>
<p>The TLM service instantiated in an ITS-Station shall provide the communication services defined in clause 4.2.</p>
<h2>
<a name="_Toc442882216"></a>
<a name="_Toc442882445"></a>
<a name="_Toc442965258"></a>
<a name="_Toc455389602"></a>5.3	TLM service message and version</h2>
<p>The TLM service shall use the message SPATEM as defined in Annex A. The header of SPATEM shall be as specified in the data dictionary ETSI TS 102 894-2 [2]. The data elements of SPATEM payload shall be as specified in ISO/TS 19091 [8].</p>
<p><span class="requality_text id_d5639917-0102-42fe-9b78-eb662d5f982d"><a name="d5639917-0102-42fe-9b78-eb662d5f982d" id="id_d5639917-0102-42fe-9b78-eb662d5f982d" class="requality_id"></a>The </span><i><span class="requality_text id_d5639917-0102-42fe-9b78-eb662d5f982d">protocolVersion</span></i><span class="requality_text id_d5639917-0102-42fe-9b78-eb662d5f982d"> (defined in the header) of SPATEM message based on the present document is set to value "1".</span></p>
<h2>
<a name="_Toc442882217"></a>
<a name="_Toc442882446"></a>
<a name="_Toc442965259"></a>
<a name="_Toc455389603"></a>5.4	TLM service dissemination</h2>
<h3>
<a name="_Toc442882218"></a>
<a name="_Toc442882447"></a>
<a name="_Toc442965260"></a>
<a name="_Toc455389604"></a>5.4.1	TLM service identification</h3>
<p>The TLM service provides real-time information of the traffic light signal phase and timing of an intersection or parts of an intersection identified by the intersection reference identifier. The timestamp indicates the order of messages within the given time system as defined in ISO/TS 19091 [8]. There is no additional identifier needed to distinguish a SPATEM from a previous one.</p>
<h3>
<a name="_Toc442882219"></a>
<a name="_Toc442882448"></a>
<a name="_Toc442965261"></a>
<a name="_Toc455389605"></a>5.4.2	TLM service trigger, update, repetition and termination </h3>
<p>The application triggers the TLM service for the transmission of SPATEM. The application provides all data content included in a SPATEM payload. The TLM service constructs a SPATEM and delivers it to the Networking &amp; Transport Layer for dissemination. The SPATEM is not repeated.</p>
<p><span class="requality_text id_2bdd05fa-8e32-4a3e-bf3c-4f2ff5550109"><a name="2bdd05fa-8e32-4a3e-bf3c-4f2ff5550109" id="id_2bdd05fa-8e32-4a3e-bf3c-4f2ff5550109" class="requality_id"></a>The TLM service shall be terminated, if the ITS-S application requests the termination.</span></p>
<h3>
<a name="_Toc442882220"></a>
<a name="_Toc442882449"></a>
<a name="_Toc442965262"></a>
<a name="_Toc455389606"></a>5.4.3	TLM service communication requirements</h3>
<h4>
<a name="_Toc455389607"></a>5.4.3.1	TLM service communication overview</h4>
<p>The TLM service uses SPATEM to disseminate the status of the traffic light controller, traffic lights and intersection traffic information. It transmits continuously in real-time the information relevant for all maneuvers in the of an intersection. The goal is to address all traffic participants using the intersection for travel or cross walking. Due to different equipment of end users, the SPATEM may be disseminated using different access technologies for short range or for long range communication.</p>
<h4>
<a name="_Toc442882221"></a>
<a name="_Toc442882450"></a>
<a name="_Toc442965263"></a>
<a name="_Toc455389608"></a>5.4.3.2	TLM service communication requirements for short range access technologies</h4>
<p>For short range broadcast communication different access technologies are applicable for dissemination of SPATEM as follows:</p>
<p class="b1+">Short range communication data transmission using ITS-G5 broadcast transmission,</p>
<p class="b1+">WiFi communication.</p>
<p><span class="requality_text id_3dc31e63-315a-421b-b74a-0c41cf4ae097"><a name="3dc31e63-315a-421b-b74a-0c41cf4ae097" id="id_3dc31e63-315a-421b-b74a-0c41cf4ae097" class="requality_id"></a>In case the GN protocol and the GBC is used, the TLM service shall provide the destination area in the format compliant to ETSI EN 302 931 [9] and to the ITS networking &amp; transport layer.</span></p>
<p>Table 3 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">
<a name="_Ref423692151"></a>Table 3: TLM 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="tAC">Operational parameters</p>
</td>
</tr>
<tr>	<td>
<p class="tAC">CSP_LogicalChannelType</p>
</td>	<td>
<p class="tAC">SfCH</p>
</td>	<td>
<p class="tAC">Safety channel</p>
</td>
</tr>
<tr>	<td>
<p class="tAC">CSP_SessionCont</p>
</td>	<td>
<p class="tAC">n.a.</p>
</td>	<td>
<p class="tAC">No continuous connectivity</p>
</td>
</tr>
<tr>	<td>
<p class="tAC">CSP_AvgADUrate</p>
</td>	<td>
<p class="tAC">255, 1 seconds (default)</p>
</td>	<td>
<p class="tAC"></p>
</td>
</tr>
<tr>	<td>
<p class="tAC">CSP_FlowType</p>
</td>	<td>
<p class="tAC">n.a.</p>
</td>	<td>
<p class="tAC"></p>
</td>
</tr>
<tr>	<td>
<p class="tAC">CSP_MaxPrio</p>
</td>	<td>
<p class="tAC">253</p>
</td>	<td>
<p class="tAC"></p>
</td>
</tr>
<tr>	<td>
<p class="tAC">CSP_PortNo</p>
</td>	<td>
<p class="tAC"><span class="requality_text id_ec4af833-ea05-49fb-b5b2-6a3ee65b1dcb"><a name="ec4af833-ea05-49fb-b5b2-6a3ee65b1dcb" id="id_ec4af833-ea05-49fb-b5b2-6a3ee65b1dcb" class="requality_id"></a>2004</span></p>
</td>	<td>
<p class="tAC">Port Number of the transport protocol (see ETSI TS 103 248 [16])</p>
</td>
</tr>
<tr>	<td>
<p class="tAC">CSP_ExpFlowLifetime</p>
</td>	<td>
<p class="tAC">n.a.</p>
</td>	<td>
<p class="tAC"></p>
</td>
</tr>
<tr>	<td>
<p class="tAC">Destination related parameters</p>
</td>
</tr>
<tr>	<td>
<p class="tAC">CSP_DestinationType</p>
</td>	<td>
<p class="tAC">geo-location-based<br /><span class="requality_text id_f85e8afe-948d-4164-9a06-70c8dc7b5ba9"><a name="f85e8afe-948d-4164-9a06-70c8dc7b5ba9" id="id_f85e8afe-948d-4164-9a06-70c8dc7b5ba9" class="requality_id"></a>GeoBroadcast</span></p>
</td>	<td>
<p class="tAC"></p>
</td>
</tr>
<tr>	<td>
<p class="tAC">CSP_DestinationDomain</p>
</td>	<td>
<p class="tAC">site-local</p>
</td>	<td>
<p class="tAC"></p>
</td>
</tr>
<tr>	<td>
<p class="tAC">CSP_CommDistance</p>
</td>	<td>
<p class="tAC">400 m radius  (default value)</p>
</td>	<td>
<p class="tAC"></p>
</td>
</tr>
<tr>	<td>
<p class="tAC">CSP_Directivity</p>
</td>	<td>
<p class="tAC">n.a.</p>
</td>	<td>
<p class="tAC"></p>
</td>
</tr>
<tr>	<td>
<p class="tAC">Performance communication service parameters</p>
</td>
</tr>
<tr>	<td>
<p class="tAC">CSP_Resilience</p>
</td>	<td>
<p class="tAC">High</p>
</td>	<td>
<p class="tAC">Repeated transmission of the same message</p>
</td>
</tr>
<tr>	<td>
<p class="tAC">CSP_MinThP</p>
</td>	<td>
<p class="tAC">n.a.</p>
</td>	<td>
<p class="tAC"></p>
</td>
</tr>
<tr>	<td>
<p class="tAC">CSP_MaxLat</p>
</td>	<td>
<p class="tAC">ms100 (8)</p>
</td>	<td>
<p class="tAC">-- response within less than 100 ms</p>
</td>
</tr>
<tr>	<td>
<p class="tAC">CSP_MaxADU</p>
</td>	<td>
<p class="tAC">Max message size allowed by access technology </p>
</td>	<td>
<p class="tAC"></p>
</td>
</tr>
<tr>	<td>
<p class="tAC">Security related parameters</p>
</td>
</tr>
<tr>	<td>
<p class="tAC">CSP_DataConfidentiality</p>
</td>	<td>
<p class="tAC">n.a.</p>
</td>	<td>
<p class="tAC"></p>
</td>
</tr>
<tr>	<td>
<p class="tAC">CSP_DataIntegrity</p>
</td>	<td>
<p class="tAC">required</p>
</td>	<td>
<p class="tAC"></p>
</td>
</tr>
<tr>	<td>
<p class="tAC">CSP_NonRepudiation</p>
</td>	<td>
<p class="tAC">required</p>
</td>	<td>
<p class="tAC"></p>
</td>
</tr>
<tr>	<td>
<p class="tAC">CSP_SourceAuthentication</p>
</td>	<td>
<p class="tAC">required</p>
</td>	<td>
<p class="tAC"></p>
</td>
</tr>
<tr>	<td>
<p class="tAC">Protocol related parameter</p>
</td>
</tr>
<tr>	<td>
<p class="tAC">Protocol-Req</p>
</td>	<td>
<p class="tAC">n.a.</p>
</td>	<td>
<p class="tAC"></p>
</td>
</tr>
</tbody>
</table>
<p></p>
<p>
<b>TLM Application Identifier (AID)</b>
</p>
<p><span class="requality_text id_2ce3cc2b-aa51-421e-a422-6a9e6cce2082"><a name="2ce3cc2b-aa51-421e-a422-6a9e6cce2082" id="id_2ce3cc2b-aa51-421e-a422-6a9e6cce2082" class="requality_id"></a>The ITS AID of the TLM service is allocated in [15]</span></p>
<p></p>
<p>
<b><span class="requality_text id_515ef264-826f-4dc4-b5d2-5a2ad8b288ba"><a name="515ef264-826f-4dc4-b5d2-5a2ad8b288ba" id="id_515ef264-826f-4dc4-b5d2-5a2ad8b288ba" class="requality_id"></a>TLM service security parameters</span></b>
</p>
<p>For security against misuse of keys also for stationary installations it is necessary to change the pseudonym identity regularly. The default time for is given in Table 4. 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="_Ref414943591"></a>Table 4: TLM service security parameters</p>
<table>
<tbody>
<tr>	<td>
<p class="tAH">TLM 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>
<p>
<b>TLM service specific permissions (SSP):</b>
</p>
<p>The interpretation of the SSP octet scheme is defined as depicted in Figure 4.</p>
<table>
<tbody>
<tr>	<td>
<p class="tAC">0</p>
</td>	<td>
<p class="tAC"></p>
</td>	<td>
<p class="tAC"></p>
</td>	<td>
<p class="tAC"></p>
</td>	<td>
<p class="tAC"></p>
</td>	<td>
<p class="tAC"></p>
</td>	<td>
<p class="tAC"></p>
</td>	<td>
<p class="tAC"></p>
</td>	<td>
<p class="tAC">1</p>
</td>	<td>
<p class="tAC"></p>
</td>	<td>
<p class="tAC"></p>
</td>	<td>
<p class="tAC"></p>
Show full blame