Newer
Older
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
<?xml version="1.0" encoding="UTF-8" standalone="no"?><html xmlns="http://www.w3.org/1999/xhtml">
<head>
<style>${[cssclasses]}</style>
<meta content="application/vnd.openxmlformats-officedocument.wordprocessingml.document" name="Content-Type"/>
<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 class="header"/>
<p class="zA">
<a name="_GoBack"/>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 class="zD"/>
<p class="zB"/>
<p/>
<p/>
<p/>
<p/>
<p/>
<p class="zB"/>
<p class="fP"/>
<p class="zB">
<b>Technical Specification</b>
</p>
<p class="header">
<img alt="ETSI_BG_final_new" src="embedded/image1.jpeg"/>
</p>
<p/>
<p class="footer"/>
<p class="footer"/>
<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 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 class="fP">Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16</p>
<p class="fP"/>
<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 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 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&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>
<br/>
</p>
<h1>
<a name="_Toc442882188"/>
<a name="_Toc442882417"/>
<a name="_Toc442965230"/>
<a name="_Toc455389572"/>Intellectual Property Rights</h1>
<p>
<a name="For_tbname"/>IPRs essential or potentially essential to the present document may have been declared to ETSI. The information pertaining to these essential IPRs, if any, is publicly available for <b>ETSI members and non-members</b>, and can be found in ETSI SR 000 314: <i>"Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in respect of ETSI standards"</i>, which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web server (<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 name="_Toc442882418"/>
<a name="_Toc442965231"/>
<a name="_Toc455389573"/>Foreword</h1>
<p>This Technical Specification (TS) has been produced by ETSI Technical Committee Intelligent Transport Systems (ITS).</p>
<p>The present document includes the integration of infrastructure based application protocols within the ITS message environment.</p>
<h1>
<a name="_Toc441580672"/>
<a name="_Toc442882190"/>
<a name="_Toc442882419"/>
<a name="_Toc442965232"/>
<a name="_Toc455389574"/>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 name="_Toc442882420"/>
<a name="_Toc442965233"/>
<a name="_Toc455389575"/>Introduction</h1>
<p>The infrastructure services are application support facilities provided by the Facilities layer that construct, manage and process messages distributed from infrastructure to end-users or vice-versa based on payload received from the application. The infrastructure services specified in the present document support infrastructure-based applications in order to achieve communication interoperability, and may be implemented in parallel to other services in an ITS-S.</p>
<p>
<br/>
</p>
<h1>
<a name="_Toc442882192"/>
<a name="_Toc442882421"/>
<a name="_Toc442965234"/>
<a name="_Toc455389576"/>1 Scope</h1>
<p>The present document provides specifications of infrastructure related ITS services to support communication between infrastructure ITS equipment and traffic participants using ITS equipment (e.g. vehicles, pedestrians). It defines services in the Facilities layer for communication between the infrastructure and traffic participants. The specifications covers the protocol handling for infrastructure-related messages as well as requirements to lower layer protocols and to the security entity.</p>
<h1>
<a name="_Toc442882193"/>
<a name="_Toc442882422"/>
<a name="_Toc442965235"/>
<a name="_Toc455389577"/>2 References</h1>
<h2>
<a name="_Toc442882194"/>
<a name="_Toc442882423"/>
<a name="_Toc442965236"/>
<a name="_Toc455389578"/>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"/>[1] ETSI EN 302 665 (V1.1.1): "Intelligent Transport Systems (ITS); Communications Architecture".</p>
<p class="eX">
<a name="REF_TS102894_2"/>[2] ETSI TS 102 894-2 (V1.2.1): "Intelligent Transport Systems (ITS); Users and applications requirements; Part 2: Applications and facilities layer common data dictionary".</p>
<p class="eX">
<a name="REF_EN302636_4_1"/>[3] ETSI EN 302 636-4-1 (V1.2.1): "Intelligent Transport Systems (ITS); Vehicular Communications; GeoNetworking; Part 4: Geographical addressing and forwarding for point-to-point and pointtomultipoint communications; Sub-part 1: Media-Independent Functionality".</p>
<p class="eX">
<a name="REF_EN302636_5_1"/>[4] ETSI EN 302 636-5-1 (V1.2.1): "Intelligent Transport Systems (ITS); Vehicular Communications; GeoNetworking; Part 5: Transport Protocols; Sub-part 1: Basic Transport Protocol".</p>
<p class="eX">
<a name="REF_EN302636_6_1"/>[5] ETSI EN 302 636-6-1 (V1.2.1): "Intelligent Transport Systems (ITS); Vehicular Communications; GeoNetworking; Part 6: Internet Integration; Sub-part 1: Transmission of IPv6 Packets over GeoNetworking Protocols ".</p>
<p class="eX">
<a name="REF_TS103097"/>[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"/>[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"/>[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"/>[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"/>[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"/>[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"/>[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"/>[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"/>[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"/>[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"/>[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"/>
<h2>
<a name="_Toc442882195"/>
<a name="_Toc442882424"/>
<a name="_Toc442965237"/>
<a name="_Toc455389579"/>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"/>[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"/> [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"/>[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"/>[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"/>[i.5] ISO EN 14823: " Intelligent transport systems – Graphic data dictionary".</p>
<p class="eX">
<a name="REF_TS102723_9"/>[i.6] ETSI TS 102 723-9: "Intelligent Transport Systems; OSI cross-layer topics; Part 9: Interface between security entity and facilities layer".</p>
<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"/>
<h1>
<a name="_Toc442882196"/>
<a name="_Toc442882425"/>
<a name="_Toc442965238"/>
<a name="_Toc455389580"/>3 Definitions and abbreviations</h1>
<h2>
<a name="_Toc455389581"/>3.1 Definitions</h2>
<p>For the purposes of the present document, the following terms and definitions apply:</p>
<p>
<b>Destination area:</b> geographic area in which a message is disseminated</p>
<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"/>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 name="_Toc442882426"/>
<a name="_Toc442965239"/>
<a name="_Toc455389583"/>4 Infrastructure services introduction and general requirements</h1>
<h2>
<a name="_Toc442882198"/>
<a name="_Toc442882427"/>
<a name="_Toc442965240"/>
<a name="_Toc455389584"/>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 & 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 name="_Toc442882199"/>
<a name="_Toc442882428"/>
<a name="_Toc442965241"/>
<a name="_Toc455389585"/>4.2 Infrastructure services in the ITS communications architecture</h2>
<p>The infrastructure services refer to Facilities layer entities that manage the generation, transmission and reception of infrastructure-related messages from the infrastructure (C-ITS-S or R-ITS-S) to V-ITS-S or vice-versa. Figure 1 illustrates a high level functional architecture of the infrastructure services within the ITS communication architecture, as specified in ETSI EN 302 665 [1]. The messages are Facilities layer PDUs that are exchanged among ITS-Ss. The payload is generated by ITS applications in the transmitting ITS-S or other connected ITS-S (e.g. a C-ITS-S). At the transmitting ITS-S, the transmission of a message is triggered by applications or by forwarding mechanisms. For this purpose, the applications may connect to other entities of the Facilities layer or to external entities, in order to collect relevant information for the generation of the payload. Once the message is generated, the services may repeat the transmission, until the applications requests the termination of the transmission, or trigger another request to generate updated messages. At the receiving ITS-S, the messages are processed by the services and the content of the message is delivered to applications or to other Facilities layer entity. In one typical application, the message is transmitted by an RITS-S and disseminated to V-ITS-S within a target destination area, in which the information included in the message is considered as relevant to traffic participants.</p>
<p>In the scope of the present document, the infrastructure services supports the management of the following message types. As result, the infrastructure services include a set of service entities as listed below:</p>
<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 class="embedded" id="rId18"/>
</p>
<p class="tF">
<a name="_Ref326015634"/>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 name="_Toc442882429"/>
<a name="_Toc442965242"/>
<a name="_Toc455389586"/>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 alt="" src="embedded/image3.emf"/>
</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 name="_Toc442882430"/>
<a name="_Toc442965243"/>
<a name="_Toc455389587"/>4.4 Interfaces of the infrastructure services</h2>
<h3>
<a name="_Toc442882202"/>
<a name="_Toc442882431"/>
<a name="_Toc442965244"/>
<a name="_Toc455389588"/>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"/>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"/>
</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"/>
</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"/>
</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"/>
</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"/>
</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/>
<h3>
<a name="_Toc442882203"/>
<a name="_Toc442882432"/>
<a name="_Toc442965245"/>
<a name="_Toc455389589"/>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 name="_Toc442882433"/>
<a name="_Toc442965246"/>
<a name="_Toc455389590"/>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 name="_Toc442882434"/>
<a name="_Toc442965247"/>
<a name="_Toc455389591"/>4.4.4 Interface between Facilities layer and the N&T layer</h3>
<p>The infrastructure services deliver the message as payload to the Networking & Transport Layer for dissemination via the NF-SAP.</p>
<p>The Networking & Transport Layer indicates the reception of an ITS message to the infrastructure services.</p>
<h2>
<a name="_Toc442882206"/>
<a name="_Toc442882435"/>
<a name="_Toc442965248"/>
<a name="_Toc455389592"/>4.5 Common protocol requirements for infrastructure services</h2>
<h3>
<a name="_Toc442882207"/>
<a name="_Toc442882436"/>
<a name="_Toc442965249"/>
<a name="_Toc455389593"/>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 class="requality_id" id="id_c8ae979e-6c54-4b01-8ce1-0ce4e8b853ac" name="c8ae979e-6c54-4b01-8ce1-0ce4e8b853ac"/>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 class="requality_id" id="id_02e92920-4241-4fd0-bb41-5e09fb7402ca" name="02e92920-4241-4fd0-bb41-5e09fb7402ca"/>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 name="_Toc442882437"/>
<a name="_Toc442965250"/>
<a name="_Toc455389594"/>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 name="_Toc442882438"/>
<a name="_Toc442965251"/>
<a name="_Toc455389595"/>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 name="_Toc442882439"/>
<a name="_Toc442965252"/>
<a name="_Toc455389596"/>4.6 Protocol version</h2>
<h3>
<a name="_Toc442882211"/>
<a name="_Toc442882440"/>
<a name="_Toc442965253"/>
<a name="_Toc455389597"/>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 name="_Toc442882441"/>
<a name="_Toc442965254"/>
<a name="_Toc455389598"/>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"/>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/>
<h1>
<a name="clause_TLM_service"/>
<a name="_Toc442882213"/>
<a name="_Toc442882442"/>
<a name="_Toc442965255"/>
<a name="_Toc455389599"/><span class="requality_text id_8724cfcb-6374-41c4-993d-1b5c319eb8cf"><a class="requality_id" id="id_8724cfcb-6374-41c4-993d-1b5c319eb8cf" name="8724cfcb-6374-41c4-993d-1b5c319eb8cf"/>5 Traffic Light Maneuver (TLM) service</span></h1>
<h2>
<a name="_Toc442882214"/>
<a name="_Toc442882443"/>
<a name="_Toc442965256"/>
<a name="_Toc455389600"/>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 class="embedded" id="rId21"/>
</p>
<p class="tF">
<a name="_Ref415031170"/>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 name="_Toc442882444"/>
<a name="_Toc442965257"/>
<a name="_Toc455389601"/>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 name="_Toc442882445"/>
<a name="_Toc442965258"/>
<a name="_Toc455389602"/>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 class="requality_id" id="id_d5639917-0102-42fe-9b78-eb662d5f982d" name="d5639917-0102-42fe-9b78-eb662d5f982d"/>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 name="_Toc442882446"/>
<a name="_Toc442965259"/>
<a name="_Toc455389603"/>5.4 TLM service dissemination</h2>
<h3>
<a name="_Toc442882218"/>
<a name="_Toc442882447"/>
<a name="_Toc442965260"/>
<a name="_Toc455389604"/>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 name="_Toc442882448"/>
<a name="_Toc442965261"/>
<a name="_Toc455389605"/>5.4.2 TLM service trigger, update, repetition and termination </h3>
<p><span class="requality_text id_7af8529d-8e73-40ed-b3d9-9e77dd380972"><a class="requality_id" id="id_7af8529d-8e73-40ed-b3d9-9e77dd380972" name="7af8529d-8e73-40ed-b3d9-9e77dd380972"/>The application triggers the TLM service for the transmission of SPATEM.</span> The application provides all data content included in a SPATEM payload. The TLM service constructs a SPATEM and delivers it to the Networking & Transport Layer for dissemination. The SPATEM is not repeated.</p>
<p><span class="requality_text id_485c89bc-9da3-4c8e-be0b-63b01c34b306"><a class="requality_id" id="id_485c89bc-9da3-4c8e-be0b-63b01c34b306" name="485c89bc-9da3-4c8e-be0b-63b01c34b306"/>The TLM service shall be terminated, if the ITS-S application requests the termination.</span></p>
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
1001
1002
1003
1004
1005
1006
1007
1008
1009
1010
1011
1012
1013
1014
1015
1016
1017
1018
1019
1020
1021
1022
1023
1024
1025
1026
1027
1028
1029
1030
1031
1032
1033
1034
1035
1036
1037
1038
1039
1040
1041
1042
1043
1044
1045
1046
1047
1048
1049
1050
1051
1052
1053
1054
1055
1056
1057
1058
1059
1060
1061
1062
1063
1064
1065
1066
1067
1068
1069
1070
1071
1072
1073
1074
1075
1076
1077
1078
1079
1080
1081
1082
1083
1084
1085
1086
1087
1088
1089
1090
1091
1092
1093
1094
1095
1096
1097
1098
1099
1100
1101
1102
1103
1104
1105
1106
1107
1108
1109
1110
1111
1112
1113
1114
1115
1116
1117
1118
1119
1120
1121
1122
1123
1124
1125
1126
1127
1128
1129
1130
1131
1132
1133
1134
1135
1136
1137
1138
1139
1140
<h3>
<a name="_Toc442882220"/>
<a name="_Toc442882449"/>
<a name="_Toc442965262"/>
<a name="_Toc455389606"/>5.4.3 TLM service communication requirements</h3>
<h4>
<a name="_Toc455389607"/>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 name="_Toc442882450"/>
<a name="_Toc442965263"/>
<a name="_Toc455389608"/>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 class="requality_id" id="id_3dc31e63-315a-421b-b74a-0c41cf4ae097" name="3dc31e63-315a-421b-b74a-0c41cf4ae097"/>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 & 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"/>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"/>
</td>
</tr>
<tr> <td>
<p class="tAC">CSP_FlowType</p>
</td> <td>
<p class="tAC">n.a.</p>
</td> <td>
<p class="tAC"/>
</td>
</tr>
<tr> <td>
<p class="tAC">CSP_MaxPrio</p>
</td> <td>
<p class="tAC">253</p>
</td> <td>
<p class="tAC"/>
</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 class="requality_id" id="id_ec4af833-ea05-49fb-b5b2-6a3ee65b1dcb" name="ec4af833-ea05-49fb-b5b2-6a3ee65b1dcb"/>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"/>
</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 class="requality_id" id="id_f85e8afe-948d-4164-9a06-70c8dc7b5ba9" name="f85e8afe-948d-4164-9a06-70c8dc7b5ba9"/>GeoBroadcast</span></p>
</td> <td>
<p class="tAC"/>
</td>
</tr>
<tr> <td>
<p class="tAC">CSP_DestinationDomain</p>
</td> <td>
<p class="tAC">site-local</p>
</td> <td>
<p class="tAC"/>
</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"/>
</td>
</tr>
<tr> <td>
<p class="tAC">CSP_Directivity</p>
</td> <td>
<p class="tAC">n.a.</p>
</td> <td>
<p class="tAC"/>
</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"/>
</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"/>
</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"/>
</td>
</tr>
<tr> <td>
<p class="tAC">CSP_DataIntegrity</p>
</td> <td>
<p class="tAC">required</p>
</td> <td>
<p class="tAC"/>
</td>
</tr>
<tr> <td>
<p class="tAC">CSP_NonRepudiation</p>
</td> <td>
<p class="tAC">required</p>
</td> <td>
<p class="tAC"/>
</td>
</tr>
<tr> <td>
<p class="tAC">CSP_SourceAuthentication</p>
</td> <td>
<p class="tAC">required</p>
</td> <td>
<p class="tAC"/>
</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"/>
</td>
</tr>
</tbody>
</table>
<p/>
<p>
<b>TLM Application Identifier (AID)</b>
</p>
<p><span class="requality_text id_2ce3cc2b-aa51-421e-a422-6a9e6cce2082"><a class="requality_id" id="id_2ce3cc2b-aa51-421e-a422-6a9e6cce2082" name="2ce3cc2b-aa51-421e-a422-6a9e6cce2082"/>The ITS AID of the TLM service is allocated in [15]</span></p>
<p/>
<p>
<b><span class="requality_text id_515ef264-826f-4dc4-b5d2-5a2ad8b288ba"><a class="requality_id" id="id_515ef264-826f-4dc4-b5d2-5a2ad8b288ba" name="515ef264-826f-4dc4-b5d2-5a2ad8b288ba"/>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"/>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>
<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"/>
</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="_Ref414524055"/>Figure 4: Format for the Octets</p>
<p>The SSP for the TLM service shall correspond to the octet scheme of Table 5.</p>
<p class="tH">
<a name="_Ref419805087"/>Table 5: Octet Scheme for TLM service SSPs</p>
<table>
<tbody>
<tr> <td>
<p class="tAH">Octet #</p>
</td> <td>
<p class="tAH">Description</p>
</td>
</tr>
<tr> <td>
<p class="tAL">0</p>
</td> <td>
<p class="tAL">SSP version control</p>
</td>
</tr>
<tr> <td>
<p class="tAL">1</p>
</td> <td>
<p class="tAL">Service-specific parameter</p>
</td>
</tr>
<tr> <td>
<p class="tAL">2 to 30</p>
</td> <td>
<p class="tAL">Reserved for Future Usage</p>
</td>
</tr>
</tbody>
</table>
<p/>
<p><span class="requality_text id_ffb90c26-8785-43c8-a067-454300b1482e"><a class="requality_id" id="id_ffb90c26-8785-43c8-a067-454300b1482e" name="ffb90c26-8785-43c8-a067-454300b1482e"/>The Service specific parameter shall be as defined in Table 6.</span></p>
<p class="tH">
<a name="_Ref386548905"/>Table 6: TLM service specific permissions</p>
<table>
<tbody>
<tr> <td>
<p class="tAH">Octet position</p>
</td> <td>
<p class="tAH">Bit position</p>
</td> <td>
<p class="tAH">SPATEM data Item</p>
</td> <td>
<p class="tAH">Bit Value</p>
</td>
</tr>
<tr> <td>
<p class="tAL">1</p>
</td> <td>
<p class="tAL">0 (80h)</p>
</td> <td>
<p class="tAL"><span class="requality_text id_49c99cf1-7c9a-4caf-9eac-1f9d01d11037"><a class="requality_id" id="id_49c99cf1-7c9a-4caf-9eac-1f9d01d11037" name="49c99cf1-7c9a-4caf-9eac-1f9d01d11037"/>Information about Intersection state without advisory speed (see bit position 1) and Maneuver assisting information (see Bit position 4)</span></p>
<p class="tAL">{SPATEM.spat.intersections.<br/>IntersectionState }</p>
</td> <td>
<p class="tAL">0: certificate not allowed to sign </p>
<p class="tAL">1: certificate allowed to sign</p>
</td>
</tr>
<tr> <td>
<p class="tAL">1</p>
</td> <td>
<p class="tAL">1 (40h)</p>
</td> <td>
<p class="tAL"><span class="requality_text id_b7ffa69a-f51a-4120-81d8-99e5bebd6a08"><a class="requality_id" id="id_b7ffa69a-f51a-4120-81d8-99e5bebd6a08" name="b7ffa69a-f51a-4120-81d8-99e5bebd6a08"/>General status of the traffic controller</span></p>
<p class="tAL">{SPATEM.spat.intersections.<br/>IntersectionState.status}</p>
</td> <td>
<p class="tAL">0: certificate not allowed to sign </p>
<p class="tAL">1: certificate allowed to sign</p>
</td>
</tr>
<tr> <td>
<p class="tAL">1</p>
</td> <td>
<p class="tAL">2 (20h)</p>
</td> <td>
<p class="tAL"><span class="requality_text id_a7ca0c8e-6558-424b-8486-031930010b01"><a class="requality_id" id="id_a7ca0c8e-6558-424b-8486-031930010b01" name="a7ca0c8e-6558-424b-8486-031930010b01"/>Advisory speed</span></p>
<p class="tAL">{SPATEM.spat.intersections.<br/>IntersectionState.states.MovementState.state-time-speed.MovementEvent.speeds. AdvisorySpeed}</p>
</td> <td>
<p class="tAL">0: certificate not allowed to sign </p>
<p class="tAL">1: certificate allowed to sign </p>
</td>
</tr>
<tr> <td>
<p class="tAL">1</p>
</td> <td>
<p class="tAL">3 (10h)</p>
</td> <td>
<p class="tAL"><span class="requality_text id_b9a1bb83-fea0-4b9c-be96-7177c58933b5"><a class="requality_id" id="id_b9a1bb83-fea0-4b9c-be96-7177c58933b5" name="b9a1bb83-fea0-4b9c-be96-7177c58933b5"/>Public transport prioritization</span> </p>
<p class="tAL">{SPATEM.spat.intersections.<br/>IntersectionState.regional.SEQUENCE.<br/>regExtValue.<br/>IntersectionState-aggGrpC.activePrioritizations}</p>
</td> <td>
<p class="tAL">0: certificate not allowed to sign </p>
<p class="tAL">1: certificate allowed to sign </p>
</td>
</tr>
<tr> <td>
<p class="tAL">1</p>
</td> <td>
<p class="tAL">4 (08h)</p>
</td> <td>
<p class="tAL"><span class="requality_text id_28724eed-9f77-4704-b683-9364ed74de37"><a class="requality_id" id="id_28724eed-9f77-4704-b683-9364ed74de37" name="28724eed-9f77-4704-b683-9364ed74de37"/>Maneuver assisting information</span> </p>
1190
1191
1192
1193
1194
1195
1196
1197
1198
1199
1200
1201
1202
1203
1204
1205
1206
1207
1208
1209
1210
1211
1212
1213
1214
1215
1216
1217
1218
1219
1220
1221
1222
1223
1224
1225
1226
1227
1228
1229
1230
1231
1232
1233
1234
1235
1236
1237
1238
1239
1240
1241
1242
1243
1244
1245
1246
1247
1248
1249
1250
1251
1252
1253
1254
1255
1256
1257
1258
1259
1260
1261
1262
1263
1264
1265
1266
1267
1268
1269
1270
1271
1272
1273
1274
1275
1276
1277
1278
1279
1280
1281
1282
1283
1284
1285
1286
1287
1288
1289
1290
1291
1292
1293
1294
1295
1296
1297
1298
1299
1300
1301
1302
1303
1304
1305
1306
1307
1308
1309
1310
1311
1312
1313
1314
1315
1316
1317
1318
1319
1320
1321
1322
1323
1324
1325
1326
1327
1328
1329
1330
1331
1332
1333
1334
1335
1336
1337
1338
1339
1340
1341
1342
1343
1344
1345
1346
1347
1348
1349
1350
1351
1352
1353
1354
1355
1356
1357
1358
1359
1360
1361
1362
1363
1364
1365
1366
1367
1368
1369
1370
1371
1372
1373
1374
1375
1376
1377
1378
1379
1380
1381
1382
1383
1384
1385
1386
1387
1388
1389
1390
1391
1392
1393
1394
1395
1396
1397
1398
1399
1400
1401
1402
1403
1404
1405
1406
1407
1408
1409
1410
1411
1412
1413
1414
1415
1416
1417
1418
1419
1420
1421
1422
1423
1424
1425
1426
1427
1428
1429
1430
1431
1432
1433
1434
1435
1436
1437
1438
1439
1440
1441
1442
1443
1444
1445
1446
1447
1448
1449
1450
1451
1452
1453
1454
1455
1456
1457
1458
1459
1460
1461
1462
1463
1464
1465
1466
1467
1468
1469
1470
1471
1472
1473
1474
1475
1476
1477
1478
1479
1480
1481
1482
1483
1484
1485
1486
1487
1488
1489
1490
1491
1492
1493
1494
1495
1496
1497
1498
1499
1500
1501
1502
1503
1504
1505
1506
1507
1508
1509
1510
1511
1512
1513
1514
1515
1516
1517
1518
1519
1520
1521
1522
1523
1524
1525
1526
1527
1528
1529
1530
1531
1532
1533
1534
1535
1536
1537
1538
1539
1540
1541
1542
1543
1544
1545
1546
1547
1548
1549
1550
1551
1552
1553
1554
1555
1556
1557
1558
1559
1560
1561
1562
1563
1564
1565
1566
1567
1568
1569
1570
1571
1572
1573
1574
1575
1576
1577
1578
1579
1580
1581
1582
1583
1584
1585
1586
1587
1588
1589
1590
1591
1592
1593
1594
1595
1596
1597
1598
1599
1600
1601
1602
1603
1604
1605
1606
1607
1608
1609
1610
1611
1612
1613
1614
1615
1616
1617
1618
1619
1620
1621
1622
1623
1624
1625
1626
1627
1628
1629
1630
1631
1632
1633
1634
1635
1636
1637
1638
1639
1640
1641
1642
1643
1644
1645
1646
1647
1648
1649
1650
1651
1652
1653
1654
1655
1656
1657
1658
1659
1660
1661
1662
1663
1664
1665
1666
1667
1668
1669
1670
1671
1672
1673
1674
1675
1676
1677
1678
1679
1680
1681
1682
1683
1684
1685
1686
1687
1688
1689
1690
1691
1692
1693
1694
1695
1696
1697
1698
1699
1700
1701
1702
1703
1704
1705
1706
1707
1708
1709
1710
1711
1712
1713
1714
1715
1716
1717
1718
1719
1720
1721
1722
1723
1724
1725
1726
1727
1728
1729
1730
1731
1732
1733
1734
1735
1736
1737
1738
1739
1740
1741
1742
1743
1744
1745
1746
1747
1748
1749
1750
1751
1752
1753
1754
1755
1756
1757
1758
1759
1760
1761
1762
1763
1764
1765
1766
1767
1768
1769
1770
1771
1772
1773
1774
1775
1776
1777
1778
1779
1780
1781
1782
1783
1784
1785
1786
1787
1788
1789
1790
1791
1792
1793
1794
1795
1796
1797
1798
1799
1800
1801
1802
1803
1804
1805
1806
1807
1808
1809
1810
1811
1812
1813
1814
1815
1816
1817
1818
1819
1820
1821
1822
1823
1824
1825
1826
1827
1828
1829
1830
1831
1832
1833
1834
1835
1836
1837
1838
1839
1840
1841
1842
1843
1844
1845
1846
1847
1848
1849
1850
1851
1852
1853
1854
1855
1856
1857
1858
1859
1860
1861
1862
1863
1864
1865
1866
1867
1868
1869
1870
1871
1872
1873
1874
1875
1876
1877
1878
1879
1880
1881
1882
1883
1884
1885
1886
1887
1888
1889
1890
1891
1892
1893
1894
1895
1896
1897
1898
1899
1900
1901
1902
1903
1904
1905
1906
1907
1908
1909
1910
1911
1912
1913
1914
1915
1916
1917
1918
1919
1920
1921
1922
1923
1924
1925
1926
1927
1928
1929
1930
1931
1932
1933
1934
1935
1936
1937
1938
1939
1940
1941
1942
1943
1944
1945
1946
1947
1948
1949
1950
1951
1952
1953
1954
1955
1956
1957
1958
1959
1960
1961
1962
1963
1964
1965
1966
1967
1968
1969
1970
1971
1972
1973
1974
1975
1976
1977
1978
1979
1980
1981
1982
1983
1984
1985
1986
1987
1988
1989
1990
1991
1992
1993
1994
1995
1996
1997
1998
1999
2000
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
3001
3002
3003
3004
3005
3006
3007
3008
3009
3010
3011
<p class="tAL">{SPATEM.spat.intersections.<br/>IntersectionState.maneuverAssistList}</p>
<p class="tAL">and</p>
<p class="tAL">{SPATEM.spat.intersections.<br/>IntersectionState.states.MovementState.<br/>maneuverAssistList}</p>
</td> <td>
<p class="tAL">0: certificate not allowed to sign </p>
<p class="tAL">1: certificate allowed to sign</p>
</td>
</tr>
<tr> <td>
<p class="tAL"><span class="requality_text id_4bda289f-d3a6-42f9-9eea-f94b9a276478"><a class="requality_id" id="id_4bda289f-d3a6-42f9-9eea-f94b9a276478" name="4bda289f-d3a6-42f9-9eea-f94b9a276478"/>All other bits of the SSP are not used and set to 0.</span></p>
</td>
</tr>
</tbody>
</table>
<p/>
<h4>
<a name="_Toc442882222"/>
<a name="_Toc442882451"/>
<a name="_Toc442965264"/>
<a name="_Toc455389609"/>5.4.3.3 TLM service communication requirements for long range communication</h4>
<p>This clause provides the requirements for the long range unicast communication (e.g. usage of cellular network) in accordance with ISO/TS 17423 [i.2].</p>
<p class="tH">Table 7: TLM service communication requirements for long range</p>
<table>
<tbody>
<tr> <td>
<p class="tAH">Requirement</p>
</td> <td>
<p class="tAH">Value</p>
</td> <td>
<p class="tAH">Comment</p>
</td>
</tr>
<tr> <td>
<p class="tAL">Operational communication service parameters</p>
</td>
</tr>
<tr> <td>
<p class="tAL">CSP_LogicalChannelType</p>
</td> <td>
<p class="tAL">GpCH</p>
</td> <td>
<p class="tAL">General Purpose Channel</p>
</td>
</tr>
<tr> <td>
<p class="tAL">CSP_SessionCont</p>
</td> <td>
<p class="tAL">n.a.</p>
</td> <td>
<p class="tAL"/>
</td>
</tr>
<tr> <td>
<p class="tAL">CSP_AvgADUrate</p>
</td> <td>
<p class="tAL">n.a</p>
</td> <td>
<p class="tAL">No repetition</p>
</td>
</tr>
<tr> <td>
<p class="tAL">CSP_FlowType</p>
</td> <td>
<p class="tAL">n.a.</p>
</td> <td>
<p class="tAL"/>
</td>
</tr>
<tr> <td>
<p class="tAL">CSP_MaxPrio</p>
</td> <td>
<p class="tAL"/>
</td> <td>
<p class="tAL"/>
</td>
</tr>
<tr> <td>
<p class="tAL">CSP_PortNo</p>
</td> <td>
<p class="tAL">2 004</p>
</td> <td>
<p class="tAL">Port Number of the transport protocol (see ETSI TS 103 248 [16])</p>
</td>
</tr>
<tr> <td>
<p class="tAL">CSP_ExpFlowLifetime</p>
</td> <td>
<p class="tAL">n.a.</p>
</td> <td>
<p class="tAL"/>
</td>
</tr>
<tr> <td>
<p class="tAL">Destination communication service parameters</p>
</td>
</tr>
<tr> <td>
<p class="tAL">CSP_DestinationType</p>
</td> <td>
<p class="tAL">unicast</p>
</td> <td>
<p class="tAL"/>
</td>
</tr>
<tr> <td>
<p class="tAL">CSP_DestinationDomain</p>
</td> <td>
<p class="tAL">global</p>
</td> <td>
<p class="tAL"/>
</td>
</tr>
<tr> <td>
<p class="tAL">CSP_CommDistance</p>
</td> <td>
<p class="tAL">n.a.</p>
</td> <td>
<p class="tAL"/>
</td>
</tr>
<tr> <td>
<p class="tAL">CSP_Directivity</p>
</td> <td>
<p class="tAL">n.a.</p>
</td> <td>
<p class="tAL"/>
</td>
</tr>
<tr> <td>
<p class="tAL">Performance communication service parameters</p>
</td>
</tr>
<tr> <td>
<p class="tAL">CSP_Resilience</p>
</td> <td>
<p class="tAL">required</p>
</td> <td>
<p class="tAL"/>
</td>
</tr>
<tr> <td>
<p class="tAL">CSP_MinThP</p>
</td> <td>
<p class="tAL">n.a.</p>
</td> <td>
<p class="tAL"/>
</td>
</tr>
<tr> <td>
<p class="tAL">CSP_MaxLat</p>
</td> <td>
<p class="tAL">n.a.</p>
</td> <td>
<p class="tAL"/>
</td>
</tr>
<tr> <td>
<p class="tAL">CSP_MaxADU</p>
</td> <td>
<p class="tAL">Max message size allowed by access technology</p>
</td> <td>
<p class="tAL"/>
</td>
</tr>
<tr> <td>
<p class="tAL">Security communication service parameters</p>
</td>
</tr>
<tr> <td>
<p class="tAL">CSP_DataConfidentiality</p>
</td> <td>
<p class="tAL">required</p>
</td> <td>
<p class="tAL"/>
</td>
</tr>
<tr> <td>
<p class="tAL">CSP_DataIntegrity</p>
</td> <td>
<p class="tAL">n.a.</p>
</td> <td>
<p class="tAL"/>
</td>
</tr>
<tr> <td>
<p class="tAL">CSP_NonRepudiation</p>
</td> <td>
<p class="tAL">required</p>
</td> <td>
<p class="tAL"/>
</td>
</tr>
<tr> <td>
<p class="tAL">CSP_SourceAuthentication</p>
</td> <td>
<p class="tAL">required</p>
</td> <td>
<p class="tAL"/>
</td>
</tr>
<tr> <td>
<p class="tAL">Protocol communication service parameter</p>
</td>
</tr>
<tr> <td>
<p class="tAL">Protocol-Req</p>
</td> <td>
<p class="tAL">n.a.</p>
</td> <td>
<p class="tAL"/>
</td>
</tr>
</tbody>
</table>
<p/>
<h1>
<a name="Clause_RLT_Service"/>
<a name="_Toc442882223"/>
<a name="_Toc442882452"/>
<a name="_Toc442965265"/>
<a name="_Toc455389610"/><span class="requality_text id_b735fdb9-6d23-48f4-b1b0-aab01f6bb2dd"><a class="requality_id" id="id_b735fdb9-6d23-48f4-b1b0-aab01f6bb2dd" name="b735fdb9-6d23-48f4-b1b0-aab01f6bb2dd"/>6 Road and Lane Topology (RLT) service</span></h1>
<h2>
<a name="_Toc442882224"/>
<a name="_Toc442882453"/>
<a name="_Toc442965266"/>
<a name="_Toc455389611"/>6.1 RLT service overview</h2>
<p>The RLT service is one instantiation of the infrastructure services to manage the generation, transmission and reception of a digital topological map, which defines the topology of an infrastructure area. It includes the lane topology for e.g. vehicles, bicycles, parking, public transportation and the paths for pedestrian crossings and the allowed maneuvers within an intersection area or a road segment. In future enhancements the digital map will include additional topologydescriptions like traffic roundabouts.</p>
<p>The area of an intersection described by the topology covers about 200 m of the approaches, starting from the position of the stop line. If a neighbor intersection is closer than 400 meters, the description may be done up to an extent of approximately the half distance between the intersections.</p>
<p class="fL">
<div class="embedded" id="rId23"/>
</p>
<p class="tF">
<a name="_Ref413857845"/>Figure 5: Lane topology and corresponding connection</p>
<p>Figure 5 gives an example of the topology of an intersection. The topology is organized in several approaches (three approaches in the given example) and a "conflict area" in the junction of the approaches. Each approach holds "ingressing" (driving direction towards the conflict area) and "egressing" lanes (driving direction away from the "conflict area"). Each lane (e.g. vehicle, pedestrian, etc.) consists of two or more waypoint (positioned in the middle of the lane). Basically each ingress lane is connected with one or more egress lanes which define the allowed maneuvers in the intersection. This "connection" includes the signal group identifier, which is the link for signalization between the topology and the corresponding signaling.</p>
<h2>
<a name="_Toc442882225"/>
<a name="_Toc442882454"/>
<a name="_Toc442965267"/>
<a name="_Toc455389612"/>6.2 RLT service</h2>
<p>The Road and Lane Topology service instantiated in an ITS-Station shall provide either the transmission or the reception service defined in clause 4.2. Additionally the Road and lane Topology service supports the following functionality:</p>
<p class="b1+">Continuous transmission for infinity of the MAPEM. As the MAPEM message is not changed very often in time, a stable release is stored within the ITS-S for continuous broadcast.</p>
<p class="b1+">Assembly and disassembly fragmented MAPEM fragments on an Application level as defined by the data element <i>{MAPEM.map.layerID}</i> ISO/TS 19091 [8].</p>
<h2>
<a name="_Toc442882226"/>
<a name="_Toc442882455"/>
<a name="_Toc442965268"/>
<a name="_Toc455389613"/>6.3 RLT service message and version</h2>
<p>The RLT service shall use the message MAPEM as defined in Annex B . The header of MAPEM is defined in the data dictionary ETSI TS 102 894-2 [2]. The data elements of MAPEM payload are defined in CEN ISO/TS 19091, Annex G.</p>
<p>T<span class="requality_text id_c3059bb9-d9ca-4509-8d32-e216420f69a2"><a class="requality_id" id="id_c3059bb9-d9ca-4509-8d32-e216420f69a2" name="c3059bb9-d9ca-4509-8d32-e216420f69a2"/>he </span><i><span class="requality_text id_c3059bb9-d9ca-4509-8d32-e216420f69a2">protocolVersion</span></i><span class="requality_text id_c3059bb9-d9ca-4509-8d32-e216420f69a2"> (defined in </span><i><span class="requality_text id_c3059bb9-d9ca-4509-8d32-e216420f69a2">header</span></i><span class="requality_text id_c3059bb9-d9ca-4509-8d32-e216420f69a2">) of MAPEM message based on the present document is set to value "1".</span></p>
<h2>
<a name="_Toc442882227"/>
<a name="_Toc442882456"/>
<a name="_Toc442965269"/>
<a name="_Toc455389614"/>6.4 RLT service dissemination</h2>
<h3>
<a name="_Toc442882228"/>
<a name="_Toc442882457"/>
<a name="_Toc442965270"/>
<a name="_Toc455389615"/>6.4.1 RLT service identification</h3>
<p>The RLT service uses MAPEM which represents the topology/geometry of a set of lanes. E.g. considering an intersection MAPEM defines the topology of the lanes or parts of the topology of the lanes identified by the intersection reference identifier. The MAPEM does not change very often in time. The same MAPEM is retransmitted with the same content, unless the Application indicates to transmit a new MAPEM.</p>
<p class="b1+"><span class="requality_text id_c3436086-7d4a-4452-aab8-d48d11161c76"><a class="requality_id" id="id_c3436086-7d4a-4452-aab8-d48d11161c76" name="c3436086-7d4a-4452-aab8-d48d11161c76"/>If the size of the MAPEM exceeds the allowed message length (e.g. MTU), the RLT service fragments the message which will be transmitted in different messages. Each fragment is identified by the "layerID " as defined in ISO/TS 19091 [8], Annex G.</span></p>
<h3>
<a name="_Toc442882229"/>
<a name="_Toc442882458"/>
<a name="_Toc442965271"/>
<a name="_Toc455389616"/>6.4.2 RLT service trigger, update, repetition and termination</h3>
<p>The application triggers the Road and lane Topology service for the transmission of the MAPEM. The application provides all data content included in the MAPEM payload. The RLT service constructs a MAPEM and delivers it to the Networking & Transport Layer for dissemination.</p>
<p>As the MAPEM content is only changed, e.g. if the road and lane topology is changed, the MAPEM remains stable in time. The MAPEM is re-broadcasted continuously.</p>
<p>The MAPEM transmission may be terminated if the ITS-S application requests the termination.</p>
<h3>
<a name="_Toc442882230"/>
<a name="_Toc442882459"/>
<a name="_Toc442965272"/>
<a name="_Toc455389617"/>6.4.3 RLT service communication requirements</h3>
<h4>
<a name="_Toc442882231"/>
<a name="_Toc442882460"/>
<a name="_Toc442965273"/>
<a name="_Toc455389618"/>6.4.3.1 RLT service communication overview</h4>
<p>The RLT service uses MAPEM to define all the road topological details. It uses the lane "connection" (between ingress and egress lanes) which includes the signal-group identifier which is the link to SPATEM signaling information. <span class="requality_text id_87b10e4b-b1dc-449c-b9ac-23380151b75e"><a class="requality_id" id="id_87b10e4b-b1dc-449c-b9ac-23380151b75e" name="87b10e4b-b1dc-449c-b9ac-23380151b75e"/>MAPEM shall be transmitted continuously together with the SPATEM to inform the traffic participant (driver, pedestrian, etc.) about the status of allowed maneuvers within the intersection conflict area</span>. Due to potential different communication paths to the end users, the MAPEM may be disseminated using different access technologies for short range and long range communication.</p>
<h4>
<a name="_Toc442882232"/>
<a name="_Toc442882461"/>
<a name="_Toc442965274"/>
<a name="_Toc455389619"/>6.4.3.2 RLT service communication requirements for short range access technologies</h4>
<p>For short range broadcast communication different access technologies are applicable for dissemination of the MAPEM as follows:</p>
<p class="b1+">Short range communication data transmission using ITS-G5 broadcast transmission,</p>
<p class="b1+">WiFi communication.</p>
<p>In case the GN protocol and the GBC is used, the RLT service shall provide the destination area in the format compliant to ETSI EN 302 931 [9] and to the ITS networking & transport layer.</p>
<p>Table 8 provides the requirements for the broadcast communication in accordance with ISO/TS 17423 [i.2].</p>
<p>The ITS station management uses the communication requirements to select suitable ITS-S communication protocol stacks. Some examples of communication parameter settings that fulfill these requirements are specified in clause 10.</p>
<p class="tH">Table 8: RLT service communication requirements for short range access technologies</p>
<table>
<tbody>
<tr> <td>
<p class="tAH">Requirement</p>
</td> <td>
<p class="tAH">Value</p>
</td> <td>
<p class="tAH">Comment</p>
</td>
</tr>
<tr> <td>
<p class="tAL">Operational parameters</p>
</td>
</tr>
<tr> <td>
<p class="tAL">CSP_LogicalChannelType</p>
</td> <td>
<p class="tAL">SfCH</p>
</td> <td>
<p class="tAL">Safety channel</p>
</td>
</tr>
<tr> <td>
<p class="tAL">CSP_SessionCont</p>
</td> <td>
<p class="tAL">n.a.</p>
</td> <td>
<p class="tAL">No continuous connectivity</p>
</td>
</tr>
<tr> <td>
<p class="tAL">CSP_AvgADUrate</p>
</td> <td>
<p class="tAL">255, 1 seconds (default)</p>
</td> <td>
<p class="tAL"/>
</td>
</tr>
<tr> <td>
<p class="tAL">CSP_FlowType</p>
</td> <td>
<p class="tAL">n.a.</p>
</td> <td>
<p class="tAL"/>
</td>
</tr>
<tr> <td>
<p class="tAL">CSP_MaxPrio</p>
</td> <td>
<p class="tAL">252</p>
</td> <td>
<p class="tAL"/>
</td>
</tr>
<tr> <td>
<p class="tAL">CSP_PortNo</p>
</td> <td>
<p class="tAL"><span class="requality_text id_5aab70c2-219e-460f-9223-64c99800e70a"><a class="requality_id" id="id_5aab70c2-219e-460f-9223-64c99800e70a" name="5aab70c2-219e-460f-9223-64c99800e70a"/>2003</span></p>
</td> <td>
<p class="tAL">Port Number of the transport protocol (see ETSI TS 103 248 [16])</p>
</td>
</tr>
<tr> <td>
<p class="tAL">CSP_ExpFlowLifetime</p>
</td> <td>
<p class="tAL">n.a.</p>
</td> <td>
<p class="tAL"/>
</td>
</tr>
<tr> <td>
<p class="tAL">Destination communication service parameters</p>
</td>
</tr>
<tr> <td>
<p class="tAL">CSP_DestinationType</p>
</td> <td>
<p class="tAL">geo-location-based</p>
<p class="tAL"><span class="requality_text id_77a4a214-685d-4d91-b306-36ebef6c3db8"><a class="requality_id" id="id_77a4a214-685d-4d91-b306-36ebef6c3db8" name="77a4a214-685d-4d91-b306-36ebef6c3db8"/>GeoBroadcast</span></p>
</td> <td>
<p class="tAL"/>
</td>
</tr>
<tr> <td>
<p class="tAL">CSP_DestinationDomain</p>
</td> <td>
<p class="tAL">site-local</p>
</td> <td>
<p class="tAL"/>
</td>
</tr>
<tr> <td>
<p class="tAL">CSP_CommDistance</p>
</td> <td>
<p class="tAL">400 m radius (default value)</p>
</td> <td>
<p class="tAL"/>
</td>
</tr>
<tr> <td>
<p class="tAL">CSP_Directivity</p>
</td> <td>
<p class="tAL">n.a.</p>
</td> <td>
<p class="tAL"/>
</td>
</tr>
<tr> <td>
<p class="tAL">Performance communication service parameters</p>
</td>
</tr>
<tr> <td>
<p class="tAL">CSP_Resilience</p>
</td> <td>
<p class="tAL">High</p>
</td> <td>
<p class="tAL">Repeated transmission of the same message</p>
</td>
</tr>
<tr> <td>
<p class="tAL">CSP_MinThP</p>
</td> <td>
<p class="tAL">n.a.</p>
</td> <td>
<p class="tAL"/>
</td>
</tr>
<tr> <td>
<p class="tAL">CSP_MaxLat</p>
</td> <td>
<p class="tAL">ms100 (8)</p>
</td> <td>
<p class="tAL">-- response within less than 100 ms</p>
</td>
</tr>
<tr> <td>
<p class="tAL">CSP_MaxADU</p>
</td> <td>
<p class="tAL">Max message size allowed by access technology</p>
</td> <td>
<p class="tAL"/>
</td>
</tr>
<tr> <td>
<p class="tAL">Security communication service parameters</p>
</td>
</tr>
<tr> <td>
<p class="tAL">CSP_DataConfidentiality</p>
</td> <td>
<p class="tAL">n.a.</p>
</td> <td>
<p class="tAL"/>
</td>
</tr>
<tr> <td>
<p class="tAL">CSP_DataIntegrity</p>
</td> <td>
<p class="tAL">required</p>
</td> <td>
<p class="tAL"/>
</td>
</tr>
<tr> <td>
<p class="tAL">CSP_NonRepudiation</p>
</td> <td>
<p class="tAL">required</p>
</td> <td>
<p class="tAL"/>
</td>
</tr>
<tr> <td>
<p class="tAL">CSP_SourceAuthentication</p>
</td> <td>
<p class="tAL">required</p>
</td> <td>
<p class="tAL"/>
</td>
</tr>
<tr> <td>
<p class="tAL">Protocol communication service parameter</p>
</td>
</tr>
<tr> <td>
<p class="tAL">Protocol-Req</p>
</td> <td>
<p class="tAL">n.a.</p>
</td> <td>
<p class="tAL"/>
</td>
</tr>
</tbody>
</table>
<p/>
<p>
<b>RLT Application Identifier (AID)</b>
</p>
<p><span class="requality_text id_f73eb6c1-2513-4e4a-a8d7-de4c80675bb4"><a class="requality_id" id="id_f73eb6c1-2513-4e4a-a8d7-de4c80675bb4" name="f73eb6c1-2513-4e4a-a8d7-de4c80675bb4"/>The ITS AID of the RLT service is allocated in [15]</span></p>
<p>
<b><span class="requality_text id_ec702020-740d-4430-ba57-7b45b5d93273"><a class="requality_id" id="id_ec702020-740d-4430-ba57-7b45b5d93273" name="ec702020-740d-4430-ba57-7b45b5d93273"/>RLT service security parameters</span></b>
</p>
<p>For security against misuse of keys it is necessary to change the pseudonym identity regularly. The default time for is given in Table 9. For special cases like offline working traffic light controllers where manually driven provision of pseudonym identity keys is necessary, longer periods of e.g. half a year are allowed and shall be agreed with the operator.</p>
<p class="tH">
<a name="_Ref415033177"/>Table 9: RLT services security parameters</p>
<table>
<tbody>
<tr> <td>
<p class="tAH">RLT service security parameters</p>
</td>
</tr>
<tr> <td>
<p class="tAL">Message certificate validity</p>
</td> <td>
<p class="tAL">2 months (default value)</p>
</td>
</tr>
<tr> <td>
<p class="tAL">Station-ID change of pseudonym identity</p>
</td> <td>
<p class="tAL">1 month (default value)</p>
</td>
</tr>
</tbody>
</table>
<p/>
<p>
<b>RLT service specific permissions (SSP)</b>
</p>
<p>The interpretation of the SSP octet scheme is defined as depicted in Figure 6.</p>
<table>
<tbody>
<tr> <td>
<p class="tAC">0</p>
</td> <td>
<p class="tAC"/>
</td> <td>
<p class="tAC"/>
</td> <td>
<p class="tAC"/>
</td> <td>
<p class="tAC"/>
</td> <td>
<p class="tAC"/>
</td> <td>
<p class="tAC"/>
</td> <td>
<p class="tAC"/>
</td> <td>
<p class="tAC">1</p>
</td> <td>
<p class="tAC"/>
</td> <td>
<p class="tAC"/>
</td> <td>
<p class="tAC"/>
</td> <td>
<p class="tAC"/>
</td> <td>
<p class="tAC"/>
</td> <td>
<p class="tAC"/>
</td> <td>
<p class="tAC"/>
</td> <td>
<p class="tAC">2</p>
</td> <td>
<p class="tAC"/>
</td> <td>
<p class="tAC"/>
</td> <td>
<p class="tAC"/>
</td> <td>
<p class="tAC"/>
</td> <td>
<p class="tAC"/>
</td> <td>
<p class="tAC"/>
</td> <td>
<p class="tAC"/>
</td>
</tr>
<tr> <td>
<p class="tAC">0</p>
</td> <td>
<p class="tAC">1</p>
</td> <td>
<p class="tAC">2</p>
</td> <td>
<p class="tAC">3</p>
</td> <td>
<p class="tAC">4</p>
</td> <td>
<p class="tAC">5</p>
</td> <td>
<p class="tAC">6</p>
</td> <td>
<p class="tAC">7</p>
</td> <td>
<p class="tAC">0</p>
</td> <td>
<p class="tAC">1</p>
</td> <td>
<p class="tAC">2</p>
</td> <td>
<p class="tAC">3</p>
</td> <td>
<p class="tAC">4</p>
</td> <td>
<p class="tAC">5</p>
</td> <td>
<p class="tAC">6</p>
</td> <td>
<p class="tAC">7</p>
</td> <td>
<p class="tAC">0</p>
</td> <td>
<p class="tAC">1</p>
</td> <td>
<p class="tAC">2</p>
</td> <td>
<p class="tAC">3</p>
</td> <td>
<p class="tAC">4</p>
</td> <td>
<p class="tAC">5</p>
</td> <td>
<p class="tAC">6</p>
</td> <td>
<p class="tAC">7</p>
</td>
</tr>
<tr> <td>
<p class="tAC">Octet 0</p>
</td> <td>
<p class="tAC">Octet 1</p>
</td> <td>
<p class="tAC">Octet 2</p>
</td>
</tr>
</tbody>
</table>
<p class="nF"/>
<p class="tF">
<a name="_Ref415033252"/>Figure 6: Format for the Octets</p>
<p><span class="requality_text id_299468b6-80e7-4a89-9e17-fcfec17120a3"><a class="requality_id" id="id_299468b6-80e7-4a89-9e17-fcfec17120a3" name="299468b6-80e7-4a89-9e17-fcfec17120a3"/>The SSP for the RLT service shall correspond to the octet scheme of Table 10.</span></p>
<p class="tH">
<a name="_Ref419808009"/>Table 10: Octet Scheme for RLT service SSPs</p>
<table>
<tbody>
<tr> <td>
<p class="tAH">Octet #</p>
</td> <td>
<p class="tAH">Description</p>
</td>
</tr>
<tr> <td>
<p class="tAL">0</p>
</td> <td>
<p class="tAL">SSP version control</p>
</td>
</tr>
<tr> <td>
<p class="tAL">1</p>
</td> <td>
<p class="tAL">Service-specific parameter</p>
</td>
</tr>
<tr> <td>
<p class="tAL">2 to 30</p>
</td> <td>
<p class="tAL">Reserved for Future Usage</p>
</td>
</tr>
</tbody>
</table>
<p/>
<p><span class="requality_text id_28cb2500-bdc6-433d-9a15-2c14136109ab"><a class="requality_id" id="id_28cb2500-bdc6-433d-9a15-2c14136109ab" name="28cb2500-bdc6-433d-9a15-2c14136109ab"/>The Service-specific parameter shall be as defined in Table 11.</span></p>
<p class="tH">
<a name="_Ref415033296"/>Table 11: RLT service communication profile</p>
<table>
<tbody>
<tr> <td>
<p class="tAH">Octet Position</p>
</td> <td>
<p class="tAH">Bit Position</p>
</td> <td>
<p class="tAH">RLT service SSP data Item</p>
</td> <td>
<p class="tAH">Bit Value</p>
</td>
</tr>
<tr> <td>
<p class="tAL">1</p>
</td> <td>
<p class="tAL">0 (80h)</p>
</td> <td>
<p class="tAL">Road and lane topology controlled by a traffic light controller without speed limits (see Bit position 2)</p>
<p class="tAL"> {MAPEM}</p>
</td> <td>
<p class="tAL">0: certificate not allowed to sign </p>
</td>
</tr>
<tr> <td>
<p class="tAL"/>
</td> <td>
<p class="tAL"/>
</td> <td>
<p class="tAL"/>
</td> <td>
<p class="tAL">1: certificate allowed to sign </p>
</td>
</tr>
<tr> <td>
<p class="tAL">1</p>
</td> <td>
<p class="tAL">1 (40h)</p>
</td> <td>
<p class="tAL">Road and lane topology not using traffic light controller (see Bit position 2)</p>
<p class="tAL"> {MAPEM}</p>
</td> <td>
<p class="tAL">0: certificate not allowed to sign </p>
</td>
</tr>
<tr> <td>
<p class="tAL">1</p>
</td> <td>
<p class="tAL">2 (20h)</p>
</td> <td>
<p class="tAL">Speed limits included in the road and lane topology</p>
<p class="tAL">{MAPEM.map.intersections.<br/>IntersectionGeometry.speedLimits}</p>
</td> <td>
<p class="tAL">0: certificate not allowed to sign </p>
</td>
</tr>
<tr> <td>
<p class="tAL"/>
</td> <td>
<p class="tAL"/>
</td> <td>
<p class="tAL"/>
</td> <td>
<p class="tAL">1: certificate allowed to sign </p>
</td>
</tr>
<tr> <td>
<p class="tAL"><span class="requality_text id_4486101d-d3b2-4156-bbd5-8bcef139d100"><a class="requality_id" id="id_4486101d-d3b2-4156-bbd5-8bcef139d100" name="4486101d-d3b2-4156-bbd5-8bcef139d100"/>All other bits of the SSP are not used and set to 0.</span></p>
</td>
</tr>
</tbody>
</table>
<h4>
<a name="_Toc442882233"/>
<a name="_Toc442882462"/>
<a name="_Toc442965275"/>
<a name="_Toc455389620"/>6.4.3.3 RLT service dissemination parameters for long range communication</h4>
<p>This clause provides the requirements for the long range unicast communication (e.g. usage of cellular network) in accordance with ISO/TS 17423 [i.2].</p>
<p class="tH">Table 12: RLT service communication requirements for long range</p>
<table>
<tbody>
<tr> <td>
<p class="tAH">Requirement</p>
</td> <td>
<p class="tAH">Value</p>
</td> <td>
<p class="tAH">Comment</p>
</td>
</tr>
<tr> <td>
<p class="tAL">Operational communication service parameters</p>
</td>
</tr>
<tr> <td>
<p class="tAL">CSP_LogicalChannelType</p>
</td> <td>
<p class="tAL">GPCH</p>
</td> <td>
<p class="tAL">General Purpose Channel</p>
</td>
</tr>
<tr> <td>
<p class="tAL">CSP_SessionCont</p>
</td> <td>
<p class="tAL">n.a.</p>
</td> <td>
<p class="tAL"/>
</td>
</tr>
<tr> <td>
<p class="tAL">CSP_AvgADUrate</p>
</td> <td>
<p class="tAL">n.a.</p>
</td> <td>
<p class="tAL">No repetition</p>
</td>
</tr>
<tr> <td>
<p class="tAL">CSP_FlowType</p>
</td> <td>
<p class="tAL">n.a.</p>
</td> <td>
<p class="tAL"/>
</td>
</tr>
<tr> <td>
<p class="tAL">CSP_MaxPrio</p>
</td> <td>
<p class="tAL"/>
</td> <td>
<p class="tAL"/>
</td>
</tr>
<tr> <td>
<p class="tAL">CSP_PortNo</p>
</td> <td>
<p class="tAL">2003</p>
</td> <td>
<p class="tAL">Port Number of the transport protocol (see ETSI TS 103 248 [16])</p>
</td>
</tr>
<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 & 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>
<b>SREM</b>
</p>
<p>The SREM is transmitted based on the needs of the vehicle operator and triggered by applications. The application provides all data included in SREM. The traffic light control service shall construct a SREM payload and deliver it to the N&T (Networking and Transport) layer for dissemination.</p>
<p>The SREM may be repeated (depending on data content and on implementation).</p>
<p>The SREM transmission may be terminated, if one of the following conditions is reached:</p>
<p class="b1+">Application requests the termination of SREM transmission.</p>
<p class="b1+">Application does not provide update for SREM at the expiry of the current SREM content.</p>
<p>
<b>SSEM</b>
</p>
<p>An ITS-S forwards the request to the local traffic controller (TLC) or to the traffic control center (TCC) for further operation. Based on the decision of the TLC or the TCC the ITS-S application generates a SSEM to inform the requestor and adjacent traffic participants (e.g. vehicles, pedestrians) about the status of the request.</p>
<p><span class="requality_text id_178ac26b-def1-4261-8bbf-5df1fdaa5636"><a class="requality_id" id="id_178ac26b-def1-4261-8bbf-5df1fdaa5636" name="178ac26b-def1-4261-8bbf-5df1fdaa5636"/>The SSEM is transmitted by the infrastructure equipment (ITS-S road side unit) as response to a SREM. Based on changes or incoming SREM with higher priority requests (e.g. public safety "overrules" a Bus request) a revised SSEM will be transmitted to reflect the new status.</span></p>
3013
3014
3015
3016
3017
3018
3019
3020
3021
3022
3023
3024
3025
3026
3027
3028
3029
3030
3031
3032
3033
3034
3035
3036
3037
3038
3039
3040
3041
3042
3043
3044
3045
3046
3047
3048
3049
3050
3051
3052
3053
3054
3055
3056
3057
3058
3059
3060
3061
3062
3063
3064
3065
3066
3067
3068
3069
3070
3071
3072
3073
3074
3075
3076
3077
3078
3079
3080
3081
3082
3083
3084
3085
3086
3087
3088
3089
3090
3091
3092
3093
3094
3095
3096
3097
3098
3099
3100
3101
3102
3103
3104
3105
3106
3107
3108
3109
3110
3111
3112
3113
3114
3115
3116
3117
3118
3119
3120
3121
3122
3123
3124
3125
3126
3127
3128
3129
3130
3131
3132
3133
3134
3135
3136
3137
3138
3139
3140
3141
3142
3143
3144
3145
3146
3147
3148
3149
3150
3151
3152
3153
3154
3155
3156
3157
3158
3159
3160
3161
3162
3163
3164
3165
3166
3167
3168
3169
3170
3171
3172
3173
3174
3175
3176
3177
3178
3179
3180
3181
3182
3183
3184
3185
3186
3187
3188
3189
3190
3191
3192
3193
3194
3195
3196
3197
3198
3199
3200
3201
3202
3203
3204
3205
3206
3207
3208
3209
3210
3211
3212
3213
3214
3215
3216
3217
3218
3219
3220
3221
3222
3223
3224
3225
3226
3227
3228
3229
3230
3231
3232
3233
3234
3235
3236
3237
3238
3239
3240
3241
3242
3243
3244
3245
3246
3247
3248
3249
3250
3251
3252
3253
3254
3255
3256
3257
3258
3259
3260
3261
3262
3263
3264
3265
3266
3267
3268
3269
3270
3271
3272
3273
3274
3275
3276
3277
3278
3279
3280
3281
3282
3283
3284
3285
3286
3287
3288
3289
3290
3291
3292
3293
3294
3295
3296
3297
3298
3299
3300
3301
3302
3303
3304
3305
3306
3307
3308
3309
3310
3311
3312
3313
3314
3315
3316
3317
3318
3319
3320
3321
3322
3323
3324
3325
3326
3327
3328
3329
3330
3331
3332
3333
3334
3335
3336
3337
3338
3339
3340
3341
3342
3343
3344
3345
3346
3347
3348
3349
3350
3351
3352
3353
3354
3355
3356
3357
3358
3359
3360
3361
3362
3363
3364
3365
3366
3367
3368
3369
3370
3371
3372
3373
3374
3375
3376
3377
3378
3379
3380
3381
3382
3383
3384
3385
3386
3387
3388
3389
3390
3391
3392
3393
3394
3395
3396
3397
3398
3399
3400
3401
3402
3403
3404
3405
3406
3407
3408
3409
3410
3411
3412
3413
3414
3415
3416
3417
3418
3419
3420
3421
3422
3423
3424
3425
3426
3427
3428
3429
3430
3431
3432
3433
3434
3435
3436
3437
3438
3439
3440
3441
3442
3443
3444
3445
3446
3447
3448
3449
3450
3451
3452
3453
3454
3455
3456
3457
3458
3459
3460
3461
3462
3463
3464
3465
3466
3467
3468
3469
3470
3471
3472
3473
3474
3475
3476
3477
3478
3479
3480
3481
3482
3483
3484
3485
3486
3487
3488
3489
3490
3491
3492
3493
3494
3495
3496
3497
3498
3499
3500
3501
3502
3503
3504
3505
3506
3507
3508
3509
3510
3511
3512
3513
3514
3515
3516
3517
3518
3519
3520
3521
3522
3523
3524
3525
3526
3527
3528
3529
3530
3531
3532
3533
3534
3535
3536
3537
3538
3539
3540
3541
3542
3543
3544
3545
3546
3547
3548
3549
3550
3551
3552
3553
3554
3555
3556
3557
3558
3559
3560
3561
3562
3563
3564
3565
3566
3567
3568
3569
3570
3571
3572
3573
3574
3575
3576
3577
3578
3579
3580
3581
3582
3583
3584
3585
3586
3587
3588
3589
3590
3591
3592
3593
3594
3595
3596
3597
3598
3599
3600
3601
3602
3603
3604
3605
3606
3607
3608
3609
3610
3611
3612
3613
3614
3615
3616
3617
3618
3619
3620
3621
3622
3623
3624
3625
3626
3627
3628
3629
3630
3631
3632
3633
3634
3635
3636
3637
3638
3639
3640
3641
3642
3643
3644
3645
3646
3647
3648
3649
3650
3651
3652
3653
3654
3655
3656
3657
3658
3659
3660
3661
3662
3663
3664
3665
3666
3667
3668
3669
3670
3671
3672
3673
3674
3675
3676
3677
3678
3679
3680
3681
3682
3683
3684
3685
3686
3687
3688
3689
3690
3691
3692
3693
3694
3695
3696
3697
3698
3699
3700
3701
3702
3703
3704
3705
3706
3707
3708
3709
3710
3711
3712
3713
3714
3715
3716
3717
3718
3719
3720
3721
3722
3723
3724
3725
3726
3727
3728
3729
3730
3731
3732
3733
3734
3735
3736
3737
3738
3739
3740
3741
3742
3743
3744
3745
3746
3747
3748
3749
3750
3751
3752
3753
3754
3755
3756
3757
3758
3759
3760
3761
3762
3763
3764
3765
3766
3767
3768
3769
3770
3771
3772
3773
3774
3775
3776
3777
3778
3779
3780
3781
3782
3783
3784
3785
3786
3787
3788
3789
3790
3791
3792
3793
3794
3795
3796
3797
3798
3799
3800
3801
3802
3803
3804
3805
3806
3807
3808
3809
3810
3811
3812
3813
3814
3815
3816
3817
3818
3819
3820
3821
3822
3823
3824
3825
3826
3827
3828
3829
3830
3831
3832
3833
3834
3835
3836
3837
3838
3839
3840
3841
3842
3843
3844
3845
3846
3847
3848
3849
3850
3851
3852
3853
3854
3855
3856
3857
3858
3859
3860
3861
3862
3863
3864
3865
3866
3867
3868
3869
3870
3871
3872
3873
3874
3875
3876
3877
3878
3879
3880
3881
3882
3883
3884
3885
3886
3887
3888
3889
3890
3891
3892
3893
3894
3895
3896
3897
3898
3899
3900
3901
3902
3903
3904
3905
3906
3907
3908
3909
3910
3911
3912
3913
3914
3915
3916
3917
3918
3919
3920
3921
3922
3923
3924
3925
3926
3927
3928
3929
3930
3931
3932
3933
3934
3935
3936
3937
3938
3939
3940
3941
3942
3943
3944
3945
3946
3947
3948
3949
3950
3951
3952
3953
3954
3955
3956
3957
3958
3959
3960
3961
3962
3963
3964
3965
3966
3967
3968
3969
3970
3971
3972
3973
3974
3975
3976
3977
3978
3979
3980
3981
3982
3983
3984
3985
3986
3987
3988
3989
3990
3991
3992
3993
3994
3995
3996
3997
3998
3999
4000
4001
4002
4003
4004
4005
4006
4007
4008
4009
4010
4011
4012
4013
4014
4015
4016
4017
4018
4019
4020
4021
4022
4023
4024
4025
4026
4027
4028
4029
4030
4031
4032
4033
4034
4035
4036
4037
4038
4039
4040
4041
4042
4043
4044
4045
4046
4047
4048
4049
4050
4051
4052
4053
4054
4055
4056
4057
4058
4059
4060
4061
4062
4063
4064
4065
4066
4067
4068
4069
4070
4071
4072
4073
4074
4075
4076
4077
4078
4079
4080
4081
4082
4083
4084
4085
4086
4087
4088
4089
4090
4091
4092
4093
4094
4095
4096
4097
4098
4099
4100
4101
4102
4103
4104
4105
4106
4107
4108
4109
4110
4111
4112
4113
4114
4115
4116
4117
4118
4119
4120
4121
4122
4123
4124
4125
4126
4127
4128
4129
4130
4131
4132
4133
4134
4135
4136
4137
4138
4139
4140
4141
4142
4143
4144
4145
4146
4147
4148
4149
4150
4151
4152
4153
4154
4155
4156
4157
4158
4159
4160
4161
4162
4163
4164
4165
4166
4167
4168
4169
4170
4171
4172
4173
4174
4175
4176
4177
4178
4179
4180
4181
4182
4183
4184
4185
4186
4187
4188
4189
4190
4191
4192
4193
4194
4195
4196
4197
4198
4199
4200
4201
4202
4203
4204
4205
4206
4207
4208
4209
4210
4211
4212
4213
4214
4215
4216
4217
4218
4219
4220
4221
4222
4223
4224
4225
4226
4227
4228
4229
4230
4231
4232
4233
4234
4235
4236
4237
4238
4239
4240
4241
4242
4243
4244
4245
4246
4247
4248
4249
4250
4251
4252
4253
4254
4255
4256
4257
4258
4259
4260
4261
4262
4263
4264
4265
4266
4267
4268
4269
4270
4271
4272
4273
4274
4275
4276
4277
4278
4279
4280
4281
4282
4283
4284
4285
4286
4287
4288
4289
4290
4291
4292
4293
4294
4295
4296
4297
4298
4299
4300
4301
4302
4303
4304
4305
4306
4307
4308
4309
4310
4311
4312
4313
4314
4315
4316
4317
4318
4319
4320
4321
4322
4323
4324
4325
4326
4327
4328
4329
4330
4331
4332
4333
4334
4335
4336
4337
4338
4339
4340
4341
4342
4343
4344
4345
4346
4347
4348
4349
4350
4351
4352
4353
4354
4355
4356
4357
4358
4359
4360
4361
4362
4363
4364
4365
4366
4367
4368
4369
4370
4371
4372
4373
4374
4375
4376
4377
4378
4379
4380
4381
4382
4383
4384
4385
4386
4387
4388
4389
4390
4391
4392
4393
4394
4395
4396
4397
4398
4399
4400
4401
4402
4403
4404
4405
4406
4407
4408
4409
4410
4411
4412
4413
4414
4415
4416
4417
4418
4419
4420
4421
4422
4423
4424
4425
4426
4427
4428
4429
4430
4431
4432
4433
4434
4435
4436
4437
4438
4439
4440
4441
4442
4443
4444
4445
4446
4447
4448
4449
4450
4451
4452
4453
4454
4455
4456
4457
4458
4459
4460
4461
4462
4463
4464
4465
4466
4467
4468
4469
4470
4471
4472
4473
4474
4475
4476
4477
4478
4479
4480
4481
4482
4483
4484
4485
4486
4487
4488
4489
4490
4491
4492
4493
4494
4495
4496
4497
4498
4499
4500
4501
4502
4503
4504
4505
4506
4507
4508
4509
4510
4511
4512
4513
4514
4515
4516
4517
4518
4519
4520
4521
4522
4523
4524
4525
4526
4527
4528
4529
4530
4531
4532
4533
4534
4535
4536
4537
4538
4539
4540
4541
4542
4543
4544
4545
4546
4547
4548
4549
4550
4551
4552
4553
4554
4555
4556
4557
4558
4559
4560
4561
4562
4563
4564
4565
4566
4567
4568
4569
4570
4571
4572
4573
4574
4575
4576
4577
4578
4579
4580
4581
4582
4583
4584
4585
4586
4587
4588
4589
4590
4591
4592
4593
4594
4595
4596
4597
4598
4599
4600
4601
<p>The application provides all data included in SSEM payload. The Traffic Light Control service shall construct a SSEM payload and deliver it to the Networking and Transport Layer for dissemination.</p>
<p>The SSEM may be repeated (depending on data content and on implementation).</p>
<p>The SSEM transmission may be terminated, if one of the following conditions is reached:</p>
<p class="b1+">Application requests the termination of SSEM transmission.</p>
<p class="b1+">Application does not provide update for SSEM at the expiry of the current SSEM content.</p>
<h3>
<a name="_Toc442882251"/>
<a name="_Toc442882480"/>
<a name="_Toc442965293"/>
<a name="_Toc455389638"/>8.4.3 TLC service communication parameters</h3>
<h4>
<a name="_Toc442882252"/>
<a name="_Toc442882481"/>
<a name="_Toc442965294"/>
<a name="_Toc455389639"/>8.4.3.1 TLC service service communication overview</h4>
<p>The SREM is transmitted on demand (e.g. Bus driver) or automatically by an application (e.g. in the bus) based on external conditions (e.g. position, reception of a specific SPATEM, etc.) It is transmitted once or continuously depending on the needs of the implementation. The SSEM is sent as response to a SREM. Both messages may use short range or wide area communication.</p>
<h4>
<a name="_Toc442882253"/>
<a name="_Toc442882482"/>
<a name="_Toc442965295"/>
<a name="_Toc455389640"/>8.4.3.2 TLC service communication parameters for short range access technologies</h4>
<p>For short range broadcast communication different access technologies are applicable for dissemination of the SREM or SSEM as follows:</p>
<p class="b1+">Short range communication data transmission using ITS-G5 broadcast transmission,</p>
<p class="b1+">WiFi communication.</p>
<p>In case the GN protocol and the GBC is used, the TLC service shall provide the destination area in the format compliant to ETSI EN 302 931 [9] and to the ITS networking & transport layer.</p>
<p>Table 17 provides the requirements for the broadcast communication in accordance with ISO/TS 17423 [i.2].</p>
<p>The ITS station management uses the communication requirements to select suitable ITS-S communication protocol stacks. Some examples of communication parameter settings that fulfill these requirements are specified in clause 10.</p>
<p class="tH">Table 17: TLC service communication profile 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">SCH, SfCH</p>
</td> <td>
<p class="tAL">Service channel, 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">0</p>
</td> <td>
<p class="tAL">No average transmission</p>
</td>
</tr>
<tr> <td>
<p class="tAL">CSP_FlowType</p>
</td> <td>
<p class="tAL">n.a.</p>
</td> <td>
<p class="tAL"/>
</td>
</tr>
<tr> <td>
<p class="tAL">CSP_MaxPrio</p>
</td> <td>
<p class="tAL">251</p>
</td> <td>
<p class="tAL"/>
</td>
</tr>
<tr> <td>
<p class="tAL">CSP_PortNo</p>
</td> <td>
<p class="tAL">2007</p>
</td> <td>
<p class="tAL">SREM port number of the transport protocol (see ETSI TS 103 248 [16])</p>
</td>
</tr>
<tr> <td>
<p class="tAL"/>
</td> <td>
<p class="tAL">2008</p>
</td> <td>
<p class="tAL">SSEM port number of the transport protocol (see ETSI TS 103 248 [16])</p>
</td>
</tr>
<tr> <td>
<p class="tAL">CSP_ExpFlowLifetime</p>
</td> <td>
<p class="tAL">n.a.</p>
</td> <td>
<p class="tAL"/>
</td>
</tr>
<tr> <td>
<p class="tAL">Destination communication service parameters</p>
</td>
</tr>
<tr> <td>
<p class="tAL">CSP_DestinationType</p>
</td> <td>
<p class="tAL">geo-location-based</p>
<p class="tAL">GeoBroadcast</p>
</td> <td>
<p class="tAL"/>
</td>
</tr>
<tr> <td>
<p class="tAL">CSP_DestinationDomain</p>
</td> <td>
<p class="tAL">site-local</p>
</td> <td>
<p class="tAL"/>
</td>
</tr>
<tr> <td>
<p class="tAL">CSP_CommDistance</p>
</td> <td>
<p class="tAL">400 m radius (default value)</p>
</td> <td>
<p class="tAL">Short range communication is used.</p>
</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>TLC Application Identifier (AID)</b>
</p>
<p><span class="requality_text id_845b1b76-e7cf-41aa-8bc9-2fb7f5d079cd"><a class="requality_id" id="id_845b1b76-e7cf-41aa-8bc9-2fb7f5d079cd" name="845b1b76-e7cf-41aa-8bc9-2fb7f5d079cd"/>The ITS AID of the TLC service is allocated in [15]</span></p>
<p>.</p>
<p>
<b><span class="requality_text id_fe74fe56-0d8e-476a-972b-aae7246a2b3a"><a class="requality_id" id="id_fe74fe56-0d8e-476a-972b-aae7246a2b3a" name="fe74fe56-0d8e-476a-972b-aae7246a2b3a"/>TLC service security parameters</span></b>
</p>
<p>For security against misuse of keys also for fix 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 should be agreed with the operator.</p>
<p class="tH">Table 18: TLC service security parameters</p>
<table>
<tbody>
<tr> <td>
<p class="tAH">TLC service security parameters</p>
</td>
</tr>
<tr> <td>
<p class="tAL">Message certificate validity</p>
</td> <td>
<p class="tAL">2 months (default value)</p>
</td>
</tr>
<tr> <td>
<p class="tAL">Station-ID change of pseudonym identity</p>
</td> <td>
<p class="tAL">1 month (default value)</p>
</td>
</tr>
</tbody>
</table>
<p/>
<p>
<b>TLC service specific permissions (SSP)</b>
</p>
<p>The interpretation of SSP octet scheme is defined as depicted in Figure 9.</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="_Ref440402801"/>Figure 9: Format for the Octets</p>
<p>The SSP for the SREM and SSEM shall correspond to the octet scheme of Table 19.</p>
<p class="tH">
<a name="_Ref419815887"/>Table 19: Octet scheme for TLC service SSPs</p>
<table>
<tbody>
<tr> <td>
<p class="tAH">Octet #</p>
</td> <td>
<p class="tAH">Description</p>
</td>
</tr>
<tr> <td>
<p class="tAL">0</p>
</td> <td>
<p class="tAL">SSP version control</p>
</td>
</tr>
<tr> <td>
<p class="tAL">3</p>
</td> <td>
<p class="tAL">Service-specific parameter</p>
</td>
</tr>
<tr> <td>
<p class="tAL">4 to 15</p>
</td> <td>
<p class="tAL">Reserved for future usage</p>
</td>
</tr>
</tbody>
</table>
<p/>
<p><span class="requality_text id_5bccff70-8411-49a4-86e8-6a2730ec8fa0"><a class="requality_id" id="id_5bccff70-8411-49a4-86e8-6a2730ec8fa0" name="5bccff70-8411-49a4-86e8-6a2730ec8fa0"/>The service-specific parameter for SSEM shall be as defined in Table 20.</span></p>
<p class="tH">
<a name="_Ref419815902"/>Table 20: Signal Control service specific permissions for SREM</p>
<table>
<tbody>
<tr> <td>
<p class="tAH">Octet Position</p>
</td> <td>
<p class="tAH">Bit Position</p>
</td> <td>
<p class="tAH">SREM data Item</p>
</td> <td>
<p class="tAH">Bit Value</p>
</td>
</tr>
<tr> <td>
<p class="tAL">1</p>
</td> <td>
<p class="tAL">0 (80h)</p>
</td> <td>
<p class="tAL">Signal request</p>
<p class="tAL">{SREM.srm.requests}</p>
</td> <td>
<p class="tAL">1: The sending ITS-S is authorized to sign a signal request</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">Requestor role (public transport)</p>
<p class="tAL">{SREM.srm.requestor.type.role.<br/>publicTransport}</p>
</td> <td>
<p class="tAL">1: The sending ITS-S is authorized to sign a signal request if he is part of the official public transport fleet.</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">Requestor role (special transport)</p>
<p class="tAL">{SREM.srm.requestor.type.role.<br/>specialTransport}</p>
</td> <td>
<p class="tAL">1: The sending ITS-S is authorized to sign a signal request if he is officially allowed to execute a special transport.</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">Requestor role (dangerousGoods)</p>
<p class="tAL">{SREM.srm.requestor.type.role.<br/>dangerousGoods}</p>
</td> <td>
<p class="tAL">1: The sending ITS-S is authorized to sign a signal request if he is allowed to transport officially dangerous goods</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">Requestor role (roadWork)</p>
<p class="tAL">{SREM.srm.requestor.type.role.<br/>roadWork}</p>
</td> <td>
<p class="tAL">1: The sending ITS-S is authorized to sign a signal request if he is part of the official roadwork fleet.</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">Requestor role (roadRescue)</p>
<p class="tAL">{SREM.srm.requestor.type.role.<br/>roadRescue}</p>
</td> <td>
<p class="tAL">1: The sending ITS-S is authorized to sign a signal request if he is part of the official road rescue fleet.</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">Requestor role (emergency)</p>
<p class="tAL">{SREM.srm.requestor.type.role.<br/>emergency}</p>
</td> <td>
<p class="tAL">1: The sending ITS-S is authorized to sign a signal request if he is part of the official emergency fleet</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)</p>
</td> <td>
<p class="tAL">Requestor role (safetyCar)</p>
<p class="tAL">{SREM.srm.requestor.type.role.<br/>safetyCar}</p>
</td> <td>
<p class="tAL">1: The sending ITS-S is authorized to sign a signal request if he is part of the official safety vehicle fleet</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)</p>
</td> <td>
<p class="tAL">Requestor role (truck)</p>
<p class="tAL">{SREM.srm.requestor.type.role.<br/>truck}</p>
</td> <td>
<p class="tAL">1: The sending ITS-S is authorized to sign a signal request if he is a truck allowed officially to make signal requests</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">Requestor role (motorcycle)</p>
<p class="tAL">{SREM.srm.requestor.type.role.<br/>motorcycle}</p>
</td> <td>
<p class="tAL">1: The sending ITS-S is authorized to sign a signal request if he is a motor cycle allowed officially to make signal requests</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">Requestor role (police)</p>
<p class="tAL">{SREM.srm.requestor.type.role.<br/>police}</p>
</td> <td>
<p class="tAL">1: The sending ITS-S is authorized to sign a signal request if he is part of the official police vehicle fleet</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">Requestor role (fire)</p>
<p class="tAL">{SREM.srm.requestor.type.role.<br/>fire}</p>
</td> <td>
<p class="tAL">1: The sending ITS-S is authorized to sign a signal request if he is part of the official fire brigade vehicle fleet</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">Requestor role (ambulance)</p>
<p class="tAL">{SREM.srm.requestor.type.role.<br/>ambulance}</p>
</td> <td>
<p class="tAL">1: The sending ITS-S is authorized to sign a signal request if he is part of the official ambulance vehicle fleet</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">5 (04h)</p>
</td> <td>
<p class="tAL">Requestor role (dot)</p>
<p class="tAL">{SREM.srm.requestor.type.role.<br/>dot}</p>
</td> <td>
<p class="tAL">1: The sending ITS-S is authorized to sign a signal request if he is part of the official department of transportation vehicle fleet</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">6 (02h)</p>
</td> <td>
<p class="tAL">Requestor role (transit)</p>
<p class="tAL">{SREM.srm.requestor.type.role.<br/>transit}</p>
</td> <td>
<p class="tAL">1: The sending ITS-S is authorized to sign a signal request if he is part of the official transit vehicle fleet</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">7 (01h)</p>
</td> <td>
<p class="tAL">Requestor role (slowMoving)</p>
<p class="tAL">{SREM.srm.requestor.type.role.<br/>slowMoving}</p>
</td> <td>
<p class="tAL">1: The sending ITS-S is authorized to sign a signal request if he is a slow vehicle allowed officially to make signal requests</p>
<p class="tAL">0: The sending ITS-S is not authorized.</p>
</td>
</tr>
<tr> <td>
<p class="tAL">3</p>
</td> <td>
<p class="tAL">0 (80h)</p>
</td> <td>
<p class="tAL">Requestor role (cyclist)</p>
<p class="tAL">{SREM.srm.requestor.type.role.<br/>cyclist}</p>
</td> <td>
<p class="tAL">1: The sending ITS-S is authorized to sign a signal request if he is a cyclist allowed officially to make signal requests</p>
<p class="tAL">0: The sending ITS-S is not authorized.</p>
</td>
</tr>
<tr> <td>
<p class="tAL">3</p>
</td> <td>
<p class="tAL">1 (40h)</p>
</td> <td>
<p class="tAL">Requestor role (pedestrian)</p>
<p class="tAL">{SREM.srm.requestor.type.role.<br/>pedestrian}</p>
</td> <td>
<p class="tAL">1: The sending ITS-S is authorized to sign a signal request if he is a pedestrian allowed officially to make signal requests</p>
<p class="tAL">0: The sending ITS-S is not authorized.</p>
</td>
</tr>
<tr> <td>
<p class="tAL">3</p>
</td> <td>
<p class="tAL">2 (40h)</p>
</td> <td>
<p class="tAL">Requestor role (military)</p>
<p class="tAL">{SREM.srm.requestor.type.role.<br/>military}</p>
</td> <td>
<p class="tAL">1: The sending ITS-S is authorized to sign a signal request if he is part of the official military vehicle fleet</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_5f0d0ede-e1b1-49ca-9612-6df4b53860fb"><a class="requality_id" id="id_5f0d0ede-e1b1-49ca-9612-6df4b53860fb" name="5f0d0ede-e1b1-49ca-9612-6df4b53860fb"/>All other bits of the SSP are not used and set to 0.</span></p>
</td>
</tr>
</tbody>
</table>
<p/>
<p>The service-specific parameter for SREM shall be as defined in Table 21.</p>
<p class="tH">
<a name="_Ref441236817"/>Table 21: Signal Control service specific permissions for SSEM</p>
<table>
<tbody>
<tr> <td>
<p class="tAH">Octet Position</p>
</td> <td>
<p class="tAH">Bit Position</p>
</td> <td>
<p class="tAH">SREM data Item</p>
</td> <td>
<p class="tAH">Bit Value</p>
</td>
</tr>
<tr> <td>
<p class="tAL">1</p>
</td> <td>
<p class="tAL">0 (80h)</p>
</td> <td>
<p class="tAL">Signal request status</p>
<p class="tAL">{SSEM}</p>
</td> <td>
<p class="tAL">1: The sending ITS-S is authorized to give a sign a signal request status </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_dced6c4e-4e4b-402a-9452-492fe14438d3"><a class="requality_id" id="id_dced6c4e-4e4b-402a-9452-492fe14438d3" name="dced6c4e-4e4b-402a-9452-492fe14438d3"/>All other bits of the SSP are not used and set to 0.</span></p>
</td>
</tr>
</tbody>
</table>
<p/>
<h4>
<a name="_Toc442882254"/>
<a name="_Toc442882483"/>
<a name="_Toc442965296"/>
<a name="_Toc455389641"/>8.4.3.3 TLC service communication parameters for long range communication</h4>
<p>This clause provides the communication 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 22: TLC service communication profile 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">SCH</p>
</td> <td>
<p class="tAL">Service channel</p>
</td>
</tr>
<tr> <td>
<p class="tAL">CSP_SessionCont</p>
</td> <td>
<p class="tAL">n.a.</p>
</td> <td>
<p class="tAL"/>
</td>
</tr>
<tr> <td>
<p class="tAL">CSP_AvgADUrate</p>
</td> <td>
<p class="tAL">n.a</p>
</td> <td>
<p class="tAL">No repetition</p>
</td>
</tr>
<tr> <td>
<p class="tAL">CSP_FlowType</p>
</td> <td>
<p class="tAL">n.a.</p>
</td> <td>
<p class="tAL"/>
</td>
</tr>
<tr> <td>
<p class="tAL">CSP_MaxPrio</p>
</td> <td>
<p class="tAL"/>
</td> <td>
<p class="tAL"/>
</td>
</tr>
<tr> <td>
<p class="tAL">CSP_PortNo</p>
</td> <td>
<p class="tAL"><span class="requality_text id_3d7c60ed-c139-4fe2-9427-9d71ab81be08"><a class="requality_id" id="id_3d7c60ed-c139-4fe2-9427-9d71ab81be08" name="3d7c60ed-c139-4fe2-9427-9d71ab81be08"/>2007</span></p><span class="requality_text id_3d7c60ed-c139-4fe2-9427-9d71ab81be08">
</span></td> <td><span class="requality_text id_3d7c60ed-c139-4fe2-9427-9d71ab81be08">
</span><p class="tAL"><span class="requality_text id_3d7c60ed-c139-4fe2-9427-9d71ab81be08">SREM port number of the transport protocol (see ETSI TS 103 248 [16])</span></p>
</td>
</tr>
<tr> <td>
<p class="tAL"/>
</td> <td>
<p class="tAL"><span class="requality_text id_e3e378dc-8bd3-4a4e-8612-e12b901716f8"><a class="requality_id" id="id_e3e378dc-8bd3-4a4e-8612-e12b901716f8" name="e3e378dc-8bd3-4a4e-8612-e12b901716f8"/>2008</span></p><span class="requality_text id_e3e378dc-8bd3-4a4e-8612-e12b901716f8">
</span></td> <td><span class="requality_text id_e3e378dc-8bd3-4a4e-8612-e12b901716f8">
</span><p class="tAL"><span class="requality_text id_e3e378dc-8bd3-4a4e-8612-e12b901716f8">SSEM port number of the transport protocol (see ETSI TS 103 248 [16])</span></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_56f108ee-54e4-4f1a-94d4-a95839fadc3c"><a class="requality_id" id="id_56f108ee-54e4-4f1a-94d4-a95839fadc3c" name="56f108ee-54e4-4f1a-94d4-a95839fadc3c"/>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">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="_Toc442882255"/>
<a name="_Toc442882484"/>
<a name="_Toc442965297"/>
<a name="_Toc455389642"/>9 Basic services running on ITS infrastructure devices</h1>
<h2>
<a name="_Toc455389643"/>9.1 Basic service overview</h2>
<p>Infrastructure ITS devices (e.g. road side unit) will communicate to vehicles/pedestrians and are on the other side connected to traffic controllers, traffic control centers (urban, interurban) or work in a standalone operation mode. From the application point of view, they use the same services like all other ITS stations (e.g. DEN, CA) and implement, depending on their role, additional infrastructure related applications.</p>
<h2>
<a name="_Toc442882256"/>
<a name="_Toc442882485"/>
<a name="_Toc442965298"/>
<a name="_Toc455389644"/>9.2 DEN service on ITS infrastructure devices</h2>
<p>Infrastructure ITS devices shall be able to transmit and to receive DENMs and provide the DEN (Decentralized Environmental Notification) service as defined in ETSI EN 302 637-3 [14]. Due to the role of the infrastructure device additional applications may run using the DEN basic service:</p>
<p class="b1+">Generation and transmission of DENM based on information of the directly attached devices (e.g. traffic light controller, traffic warning trailer).</p>
<p class="b1+">Generation and transmission of DENM based on traffic data received from the backbone traffic control infrastructure (e.g. traffic control center).</p>
<p class="b1+">Forwarding of DENM generated by the backbone ITS infrastructure (e.g. TCC) to other ITS stations (e.g. via ITS-G5, WLAN, cellular systems).</p>
<p class="b1+">Forwarding of DENM received from other ITS stations to the backbone ITS infrastructure (e.g. TCC).</p>
<h2>
<a name="_Toc442882257"/>
<a name="_Toc442882486"/>
<a name="_Toc442965299"/>
<a name="_Toc455389645"/>9.3 CA service on ITS infrastructure devices</h2>
<p>Infrastructure ITS devices shall be able to transmit CAM's and provide the CA (Common Awareness) service as defined in ETSI EN 302 637-2 [13]. Due to the role of the infrastructure device additional applications may run using the CA basic service:</p>
<p class="b1+">Generation of CAM's for notification of protected communication zones (e.g. Tolling stations).</p>
<p class="b1+">Forwarding of CAM's received from other ITS stations to the backbone ITS infrastructure (this requires sufficient backbone channel capacity).</p>
<p class="b1+">Aggregation of CAM's (e.g. for purpose of acquisition of probe vehicle data) for minimizing backbone channel.</p>
<h1>
<a name="Clause_Communication_Parameter_Settings"/>
<a name="_Toc442882258"/>
<a name="_Toc442882487"/>
<a name="_Toc442965300"/>
<a name="_Toc455389646"/>10 Communication Parameter Settings</h1>
<h2>
<a name="_Toc442882259"/>
<a name="_Toc442882488"/>
<a name="_Toc442965301"/>
<a name="_Toc455389647"/>10.1 Overview </h2>
<p>The infrastructure services as specified in the present document shall use one of the following communication profiles:</p>
<p class="b1+">CPS_001 Transmit of ADU using GeoNetworking/BTP over ITS-G5</p>
<p class="b1+">CPS_002 Transmit of ADU using GeoNetworking/BTP over WLAN infrastructure mode</p>
<p class="b1+">CPS_003 Transmit of ADU using GeoNetworking/BTP, IP/UDP over WLAN infrastructure mode</p>
<p class="b1+">CPS_004 Transmit of ADU using IPv6, GeoNetworking/BTP over GeoNetworking</p>
<p class="b1+">CPS_005 Transmit of secured ADU using TLS/DTLS over TCP/UDP over IPv4/6 over WLAN infra. mode</p>
<p class="b1+"/>
<h2>
<a name="COM_PARAM_SETTINGS_002_clause"/>
<a name="_Toc455389648"/>
<a name="COM_PRO_001"/>
<a name="COM_PARAM_SETTINGS_001"/>10.2 CPS_001</h2>
<p>CPS_001 defines the communication parameter settings for dissemination of an ADU using GeoNetworking/BTP over ITS G5. The involved networking and transport protocols are:</p>
<p class="list_Paragraph">Basic Transport Protocol (ETSI EN 302 636-5-1 [4])</p>
<p class="list_Paragraph">GeoNetworking protocol (ETSI EN 302 636-4-1 [3]).</p>
<p>Table 23 lists the communication parameter settings.</p>
<p class="tH">
<a name="_Ref448244534"/>Table 23: CPS_001 Communication parameter settings</p>
<table>
<tbody>
<tr> <td>
<p class="tAH">Parameter</p>
</td> <td>
<p class="tAH">TSB Single_Hop (SHB)</p>
</td> <td>
<p class="tAH">TSB Multi_Hop</p>
</td> <td>
<p class="tAH">GBC</p>
</td>
</tr>
<tr> <td>
<p class="tAL">BTP Type</p>
</td> <td>
<p class="tAL"><span class="requality_text id_287563c5-e856-4f03-9ac9-c698a9abc297"><a class="requality_id" id="id_287563c5-e856-4f03-9ac9-c698a9abc297" name="287563c5-e856-4f03-9ac9-c698a9abc297"/>2 (BTP header type B)</span></p>
</td>
</tr>
<tr> <td>
<p class="tAL">BTP Source port</p>
</td> <td>
<p class="tAL">N/A</p>
</td>
</tr>
<tr> <td>
<p class="tAL">BTP Destination port</p>
</td> <td>
<p class="tAL">As specified in ETSI TS 103 248 [16]</p>
</td>
</tr>
<tr> <td>
<p class="tAL">BTP Destination port info</p>
</td> <td>
<p class="tAL">N/A</p>
</td>
</tr>
<tr> <td>
<p class="tAL">GN Packet transport type</p>
</td> <td>
<p class="tAL">SHB</p>
<p class="tAL">(Header Type: 5, <br/>Header Sub-type: 0)</p>
</td> <td>
<p class="tAL">TSB</p>
<p class="tAL">(Header Type: 5, <br/>Header Sub-type: 1)</p>
</td> <td>
<p class="tAL">GBC</p>
<p class="tAL">(Header Type:4, <br/>Header Sub-type: 0,1, or 2)</p>
<p class="tAL">The choice of sub-type is implementation-dependent based on the destination area</p>
</td>
</tr>
<tr> <td>
<p class="tAL">GN Destination address</p>
</td> <td>
<p class="tAL">N/A</p>
</td> <td>
<p class="tAL">N/A</p>
</td> <td>
<p class="tAL">Destination area</p>
</td>
</tr>
<tr> <td>
<p class="tAL">GN Communication profile</p>
</td> <td>
<p class="tAL">1 (ITS-G5A)</p>
</td>
</tr>
<tr> <td>
<p class="tAL">GN Security profile</p>
</td> <td>
<p class="tAL">As specified in clause 11</p>
</td>
</tr>
<tr> <td>
<p class="tAL">GN Maximum packet lifetime</p>
</td> <td>
<p class="tAL">As specified in clauses 5 to 8 <br/>for the corresponding infrastructure service.</p>
</td>
</tr>
<tr> <td>
<p class="tAL">GN Repetition interval</p>
</td> <td>
<p class="tAL">If applicable as specified inclauses 5 to 8.</p>
</td>
</tr>
<tr> <td>
<p class="tAL">GN Maximum repetition time</p>
</td> <td>
<p class="tAL"/>
</td>
</tr>
<tr> <td>
<p class="tAL">GN Maximum hop limit</p>
</td> <td>
<p class="tAL">N/A</p>
</td> <td>
<p class="tAL">Implementation dependent, based on the destination area.</p>
</td>
</tr>
<tr> <td>
<p class="tAL">GN Traffic class</p>
</td> <td>
<p class="tAL">The traffic class is defined for each message in Table 1</p>
</td>
</tr>
<tr> <td>
<p class="tAL">Length</p>
</td> <td>
<p class="tAL">Length of Facilities layer data</p>
</td>
</tr>
<tr> <td>
<p class="tAL">Data</p>
</td> <td>
<p class="tAL">Facilities layer data</p>
</td>
</tr>
</tbody>
</table>
<p/>
<h2>
<a name="COM_PARAM_SETTINGS_003_clause"/>
<a name="_Toc442882260"/>
<a name="_Toc442882489"/>
<a name="_Toc442965302"/>
<a name="_Toc455389649"/>
<a name="COM_PARAM_SETTINGS_002"/>
<a name="COM_PRO_101"/>10.3 CPS_002</h2>
<p>CPS_002 defines the communication settings for dissemination of an ADU using GeoNetworking/BTP over WLAN (e.g. IEEE 802.11abgn [i.4]) in infrastructure mode. The involved networking and transport protocols are:</p>
<p class="list_Paragraph">Basic Transport Protocol (ETSI EN 302 636-5-1 [4])</p>
<p class="list_Paragraph">GeoNetworking protocol (ETSI EN 302 636-4-1 [3])</p>
<p>Table 24 lists the communication parameter settings.</p>
<p class="nO">NOTE: For interoperability with ITS-G5 the same settings as for the communication profile CPS_001 as defined in clause 10.2 are used.</p>
<p class="tH">
<a name="_Ref448244811"/>Table 24: CPS_002 Communication parameter settings</p>
<table>
<tbody>
<tr> <td>
<p class="tAH">Parameter</p>
</td> <td>
<p class="tAH">Value</p>
</td>
</tr>
<tr> <td>
<p class="tAL">BTP type</p>
</td> <td>
<p class="tAL">2 (BTP header type B)</p>
</td>
</tr>
<tr> <td>
<p class="tAL">BTP source port</p>
</td> <td>
<p class="tAL">N/A</p>
</td>
</tr>
<tr> <td>
<p class="tAL">BTP Destination port</p>
</td> <td>
<p class="tAL">As specified in ETSI TS 103 248 [16]</p>
</td>
</tr>
<tr> <td>
<p class="tAL">BTP Destination port info</p>
</td> <td>
<p class="tAL">N/A</p>
</td>
</tr>
<tr> <td>
<p class="tAL">GN Packet transport type</p>
</td> <td>
<p class="tAL">SHB (Header Type: 5, Header Sub-type: 0)</p>
</td>
</tr>
<tr> <td>
<p class="tAL">GN Destination address</p>
</td> <td>
<p class="tAL">N/A</p>
</td>
</tr>
<tr> <td>
<p class="tAL">GN Communication profile</p>
</td> <td>
<p class="tAL">N/A</p>
</td>
</tr>
<tr> <td>
<p class="tAL">GN Security profile</p>
</td> <td>
<p class="tAL">As specified in clause 11</p>
</td>
</tr>
<tr> <td>
<p class="tAL">GN Maximum packet lifetime</p>
</td> <td>
<p class="tAL">As specified in clauses 5 to 8</p>
</td>
</tr>
<tr> <td>
<p class="tAL">GN Repetition interval</p>
</td> <td>
<p class="tAL">If applicable as specified in clauses 5 to 8 for the corresponding infrastructure service..</p>
</td>
</tr>
<tr> <td>
<p class="tAL">GN Maximum repetition time</p>
</td> <td>
<p class="tAL"/>
</td>
</tr>
<tr> <td>
<p class="tAL">GN Maximum hop limit</p>
</td> <td>
<p class="tAL">N/A</p>
</td>
</tr>
<tr> <td>
<p class="tAL">GN Traffic class</p>
</td> <td>
<p class="tAL">N/A</p>
</td>
</tr>
<tr> <td>
<p class="tAL">Length</p>
</td> <td>
<p class="tAL">Length of Facilities layer data</p>
</td>
</tr>
<tr> <td>
<p class="tAL">Data</p>
</td> <td>
<p class="tAL">Facilities layer data</p>
</td>
</tr>
</tbody>
</table>
<p/>
<h2>
<a name="_Toc455389650"/>
<a name="COM_PARAM_SETTINGS_003"/>10.4 CPS_003</h2>
<p>CPS_003 defines the communication settings for dissemination of an ADU using GeoNetworking/BTP and IP/UDP over WLAN (e.g. IEEE 802.11abgn [i.4]) in infrastructure mode. It applies tunnelling of GeoNetworking packets over UDP and IP version 4/version 6. The involved networking and transport protocols are:</p>
<p class="list_Paragraph">Basic Transport Protocol (ETSI EN 302 636-5-1 [4])</p>
<p class="list_Paragraph">GeoNetworking protocol (ETSI EN 302 636-4-1 [3])</p>
<p class="list_Paragraph">User Datagram Protocol (UDP)</p>
<p class="list_Paragraph">IP version 4 / version 6</p>
<p class="nO">NOTE: For interoperability with ITS-G5 the same settings as for the communication profile CPS_001 as defined in clause 10.2 are used.</p>
<p class="tH">Table 25: CPS_003 Communication parameter settings</p>
<table>
<tbody>
<tr> <td>
<p class="tAH">Parameter</p>
</td> <td>
<p class="tAH">IP version 4</p>
</td> <td>
<p class="tAH">IP version 6</p>
</td>
</tr>
<tr> <td>
<p class="tAL">Transport protocol type</p>
</td> <td>
<p class="tAC">UDP</p>
</td>
</tr>
<tr> <td>
<p class="tAL">Source port</p>
</td> <td>
<p class="tAC">Implementation dependent</p>
</td>
</tr>
<tr> <td>
<p class="tAL">Destination port</p>
</td> <td>
<p class="tAC">47101</p>
</td>
</tr>
<tr> <td>
<p class="tAL">Destination address </p>
</td> <td>
<p class="tAC">IPv4 broadcast address dependent on network deployment</p>
</td> <td>
<p class="tAC">IPv6 link-local multicast address</p>
</td>
</tr>
</tbody>
</table>
<p class="fL"/>
<p class="nO">NOTE1: Port number values were chosen based on the “IANA Service Name and Transport Protocol Port Number Registry” (<a href="https://www.iana.org/assignments/service-names-port-numbers/service-names-port-numbers.txt">https://www.iana.org/assignments/service-names-port-numbers/service-names-port-numbers.txt</a> Last Updated 2016-04-07). According to this document, the port number <br/>values 47101 – 47556 are unassigned.</p>
<p class="nO">NOTE2: The setting of other communication parameters related to IPv4 or IPv6 are implementation-dependent.</p>
<p/>
<h2>
<a name="_Toc455389651"/>
<a name="COM_PARAM_SETTINGS_005"/>10.5 CPS_004</h2>
<p>CPS_004 defines the communication settings for dissemination of an ADU using IPv6,GeoNetworking/BTP over WLAN (e.g. IEEE 802.11abgn [i.4]) in infrastructure mode. The involved networking and transport protocols are:</p>
<p class="list_Paragraph">IP version 6</p>
<p class="list_Paragraph">Basic Transport Protocol (ETSI EN 302 636-5-1 [4])</p>
<p class="list_Paragraph">GeoNetworking protocol (ETSI EN 302 636-4-1 [3]) with the extensions for transmission of IPv6 packets over GeoNetworking (ETSI EN 302 636-6-1 [5])</p>
<p/>
<h2>
<a name="_Toc455389652"/>10.6 CPS_005</h2>
<p>"CPS_005" defines the communication settings for dissemination of an ADU over WLAN (e.g. IEEE 802.11abgn [i.4]) in infrastructure mode in a secured way. The involved networking and transport protocols are TCP/UDP and IP version 4 / version 6. The TLS/DTLS protocol extended to support ETSI ITS certificates for authentication is used to secure the communication [i.7]. Table 26 lists communication parameter settings.</p>
<p class="tH">Table26 : CPS_005 Communication parameter settings</p>
<table>
<tbody>
<tr> <td>
<p class="tAH">Parameter</p>
</td> <td>
<p class="tAH">Value</p>
</td>
</tr>
<tr> <td>
<p class="tAL">Security protocol</p>
</td> <td>
<p class="tAC">TLS/DTLS extended</p>
</td>
</tr>
<tr> <td>
<p class="tAL">Transport protocol type</p>
</td> <td>
<p class="tAC">TCP/UDP</p>
</td>
</tr>
<tr> <td>
<p class="tAL">Source port</p>
</td> <td>
<p class="tAC">Implementation dependent</p>
</td>
</tr>
<tr> <td>
<p class="tAL">Destination port</p>
</td> <td>
<p class="tAC">TLM: 47101, RLT: 47102, IVI: 47103, TLC: 47104</p>
</td>
</tr>
<tr> <td>
<p class="tAL">Destination address </p>
</td> <td>
<p class="tAC">IPv4/v6 unicast address</p>
</td>
</tr>
</tbody>
</table>
<p/>
<p>NOTE: this communication profile can also be applied over a cellular interface connected to the infrastructure instead of WLAN.</p>
<p/>
<p/>
<p/>
<h1>
<a name="Clause_Security_Profile"/>
<a name="_Toc442882261"/>
<a name="_Toc442882490"/>
<a name="_Toc442965303"/>
<a name="_Toc455389653"/>11 Security Profile</h1>
<p>The Generic security profile as defined in ETSI TS 103 097 [6] shall be applied to messages used by the TLM, RLT, IVI, TLC services. Additional HeaderField types are not allowed.</p>
<p>
<br/>
</p>
<h6>
<a name="Annex_SPAT"/>
<a name="_Toc442882262"/>
<a name="_Toc442882491"/>
<a name="_Toc442965304"/>
<a name="_Toc455389654"/>Annex A (normative):<br/>ASN.1 specification of SPATEM</h6>
<p>This annex provides the ASN.1 specification of the data types of the SPATEM.</p>
<p class="pL"/>
<p class="pL">SPATEM-PDU-Descriptions {</p>
<p class="pL"> itu-t (0) identified-organization (4) etsi (0) itsDomain (5) wg1 (1) en (103301) spatem (0) version1 (1)</p>
<p class="pL">}</p>
<p class="pL"/>
<p class="pL">DEFINITIONS AUTOMATIC TAGS ::= </p>
<p class="pL"/>
<p class="pL">BEGIN</p>
<p class="pL"/>
<p class="pL">IMPORTS</p>
<p class="pL">SPAT FROM DSRC { iso (1) standard (0) signalizedIntersection (19091) profilec(2) dsrc (2) version (1) } </p>
<p class="pL">ItsPduHeader FROM ITS-Container { itu-t (0) identified-organization (4) etsi (0) itsDomain (5) wg1 (1) ts (102894) cdd (2) version (1) };</p>
<p class="pL"/>
<p class="pL"/>
<p class="pL">SPATEM ::= SEQUENCE {</p>
<p class="pL"> header ItsPduHeader,</p>
<p class="pL"> spat SPAT</p>
<p class="pL">}</p>
<p class="pL"/>
<p class="pL">END</p>
<p class="pL"/>
<p/>
<p>
<br/>
</p>
<h6>
<a name="Annex_MAP"/>
<a name="_Toc442882263"/>
<a name="_Toc442882492"/>
<a name="_Toc442965305"/>
<a name="_Toc455389655"/>Annex B (normative):<br/>ASN.1 specification of MAPEM</h6>
<p>This annex provides the ASN.1 specification of the data types of the MAPEM.</p>
<p class="pL"/>
<p class="pL">MAPEM-PDU-Descriptions {</p>
<p class="pL"> itu-t (0) identified-organization (4) etsi (0) itsDomain (5) wg1 (1) en (103301) mapem (1) version1 (1) </p>
<p class="pL">}</p>
<p class="pL"/>
<p class="pL">DEFINITIONS AUTOMATIC TAGS ::= </p>
<p class="pL"/>
<p class="pL">BEGIN</p>
<p class="pL"/>
<p class="pL">IMPORTS</p>
<p class="pL">MapData FROM DSRC { iso (1) standard (0) signalizedIntersection (19091) profilec(2) dsrc (2) version (1) } </p>
<p class="pL">ItsPduHeader FROM ITS-Container { itu-t (0) identified-organization (4) etsi (0) itsDomain (5) wg1 (1) ts (102894) cdd (2) version (1)};</p>
<p class="pL"/>
<p class="pL"/>
<p class="pL">MAPEM ::= SEQUENCE {</p>
<p class="pL"> header ItsPduHeader,</p>
<p class="pL"> map MapData</p>
<p class="pL">}</p>
<p class="pL"/>
<p class="pL">END</p>
<p class="pL"/>
<p/>
<p>
<br/>
</p>
<h6>
<a name="Annex_IVI"/>
<a name="_Toc442882264"/>
<a name="_Toc442882493"/>
<a name="_Toc442965306"/>
<a name="_Toc455389656"/>Annex C (normative):<br/>ASN.1 specification of IVIM</h6>
<p>This annex provides the ASN.1 specification of the data types of the IVIM.</p>
<p class="pL"/>
<p class="pL">IVIM-PDU-Descriptions {</p>
<p class="pL"> itu-t (0) identified-organization (4) etsi (0) itsDomain (5) wg1 (1) en (103301) ivim (2) version1 (1)</p>
<p class="pL">}</p>
<p class="pL"/>
<p class="pL">DEFINITIONS AUTOMATIC TAGS ::= </p>
<p class="pL"/>
<p class="pL">BEGIN</p>
<p class="pL"/>
<p class="pL">IMPORTS</p>
<p class="pL">IviStructure FROM IVI {iso (1) standard (0) ivi (19321) version1 (1)}</p>
<p class="pL">ItsPduHeader FROM ITS-Container { itu-t (0) identified-organization (4) etsi (0) itsDomain (5) wg1 (1) ts (102894) cdd (2) version (1)};</p>
<p class="pL"/>
<p class="pL"/>
<p class="pL">IVIM ::= SEQUENCE {</p>
<p class="pL"> header ItsPduHeader,</p>
<p class="pL"> ivi IviStructure</p>
<p class="pL">}</p>
<p class="pL"/>
<p class="pL">END</p>
<p class="pL"/>
<p/>
<p>
<br/>
</p>
<h6>
<a name="Annex_SRM"/>
<a name="_Toc442882265"/>
<a name="_Toc442882494"/>
<a name="_Toc442965307"/>
<a name="_Toc455389657"/>Annex D (normative):<br/>ASN.1 specification of SREM</h6>
<p>This annex provides the ASN.1 specification of the data types of the SREM.</p>
<p class="pL"/>
<p class="pL">SREM-PDU-Descriptions {</p>
<p class="pL"> itu-t (0) identified-organization (4) etsi (0) itsDomain (5) wg1 (1) en (103301) srem (3) version1 (1)</p>
<p class="pL">}</p>
<p class="pL"/>
<p class="pL">DEFINITIONS AUTOMATIC TAGS ::= </p>
<p class="pL"/>
<p class="pL">BEGIN</p>
<p class="pL"/>
<p class="pL">IMPORTS</p>
<p class="pL">SignalRequestMessage FROM DSRC { iso (1) standard (0) signalizedIntersection (19091) profilec(2) dsrc (2) version (1) } </p>
<p class="pL">ItsPduHeader FROM ITS-Container { itu-t (0) identified-organization (4) etsi (0) itsDomain (5) wg1 (1) ts (102894) cdd (2) version (1)};</p>
<p class="pL"/>
<p class="pL">SREM ::= SEQUENCE {</p>
<p class="pL"> header ItsPduHeader,</p>
<p class="pL"> srm SignalRequestMessage</p>
<p class="pL">}</p>
<p class="pL"/>
<p class="pL">END</p>
<p class="pL"/>
<p/>
<p>
<br/>
</p>
<h6>
<a name="Annex_SSM"/>
<a name="_Toc442882266"/>
<a name="_Toc442882495"/>
<a name="_Toc442965308"/>
<a name="_Toc455389658"/>Annex E (normative):<br/>ASN.1 specification of SSEM</h6>
<p>This annex provides the ASN.1 specification of the data types of the SSEM.</p>
<p class="pL"/>
<p class="pL">SSEM-PDU-Descriptions {</p>
<p class="pL"> itu-t (0) identified-organization (4) etsi (0) itsDomain (5) wg1 (1) en (103301) ssem (4) version1 (1)</p>
<p class="pL">}</p>
<p class="pL"/>
<p class="pL">DEFINITIONS AUTOMATIC TAGS ::= </p>
<p class="pL"/>
<p class="pL">BEGIN</p>
<p class="pL"/>
<p class="pL">IMPORTS</p>
<p class="pL">SignalStatusMessage FROM DSRC { iso (1) standard (0) signalizedIntersection (19091) profilec(2) dsrc (2) version (1) } </p>
<p class="pL">ItsPduHeader FROM ITS-Container { itu-t (0) identified-organization (4) etsi (0) itsDomain (5) wg1 (1) ts (102894) cdd (2) version (1)};</p>
<p class="pL"/>
<p class="pL"/>
<p class="pL">SSEM ::= SEQUENCE {</p>
<p class="pL"> header ItsPduHeader,</p>
<p class="pL"> ssm SignalStatusMessage</p>
<p class="pL">}</p>
<p class="pL"/>
<p class="pL">END</p>
<p class="pL"/>
<p/>
<p>
<br/>
</p>
<h6>
<a name="_Toc442882267"/>
<a name="_Toc442882496"/>
<a name="_Toc442965309"/>
<a name="_Toc455389659"/>Annex F (informative):<br/>Bibliography</h6>
<p/>
<p>ASN.1 data as defined by CEN ISO/TS 19091[8].</p>
<p class="nO"/>
<p>
<br/>
</p>
<h1>
<a name="_Toc442882268"/>
<a name="_Toc442882497"/>
<a name="_Toc442965310"/>
<a name="_Toc455389660"/>History</h1>
<table>
<tbody>
<tr> <td>
<p>
<a name="historytable"/>
<b>Document history</b>
</p>
</td>
</tr>
<tr> <td>
<p class="fP">V0.0.1</p>
</td> <td>
<p class="fP">December 2014</p>
</td> <td>
<p class="fP">Document creation</p>
</td>
</tr>
<tr> <td>
<p class="fP">V0.0.2</p>
</td> <td>
<p class="fP">January 2015</p>
</td> <td>
<p class="fP">Editorial changes</p>
</td>
</tr>
<tr> <td>
<p class="fP">V0.0.3</p>
</td> <td>
<p class="fP">January 2015</p>
</td> <td>
<p class="fP">IVI included</p>
</td>
</tr>
<tr> <td>
<p class="fP">V0.0.7</p>
</td> <td>
<p class="fP">March 2015</p>
</td> <td>
<p class="fP">Stable draft</p>
</td>
</tr>
<tr> <td>
<p class="fP">V0.0.8</p>
</td> <td>
<p class="fP">June 2015</p>
</td> <td>
<p class="fP">Signal Control service added</p>
</td>
</tr>
<tr> <td>
<p class="fP">V0.0.12</p>
</td> <td>
<p class="fP">January 2016</p>
</td> <td>
<p class="fP">Adaptations due to ISO/TS 19091 changes, review by ETSI members</p>
</td>
</tr>
<tr> <td>
<p class="fP">V1.0.0</p>
</td> <td>
<p class="fP">March 2016</p>
</td> <td>
<p class="fP">Pre-processing done before TB approval<br/>e-mail: <a href="mailto:edithelp@etsi.org">mailto:edithelp@etsi.org</a>
</p>
</td>
</tr>
</tbody>
</table>
<p/>
<p class="footer">ETSI</p>
<p>Infrastructure services<br/>
</p>
<p>NF-SAP<br/>
</p>
<p>Access<br/>
</p>
<p>Application<br/>
</p>
<p>Network & Transport<br/>
</p>
<p>MF-SAP<br/>
</p>
<p>Facilities<br/>
</p>
<p>FA-SAP<br/>
</p>
<p>applications<br/>
</p>
<p>SF-SAP<br/>
</p>
<p>Management<br/>
</p>
<p>Security<br/>
</p>
<p>Text�</p>
<p>conflict area<br/>
</p>
<p>�</p>
<p>ITS Station /<br/>Traffic Controller</p>
</body>