Newer
Older
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
**Categories:** Infrastructure information
**Revision:** _V1.3.1_
```asn1
LayerID ::= INTEGER (0..100)
```
### <a name="LayerType"></a>LayerType
This DE is used to uniquely identify the type of information to be found in a layer of a geographic map fragment such as an intersection.
@field `mixedContent`: two or more of the below types
**Categories:** Infrastructure information
**Revision:** _V1.3.1_
```asn1
LayerType ::= ENUMERATED {
none,
mixedContent,
generalMapData,
intersectionData,
curveData,
roadwaySectionData,
parkingAreaData,
sharedLaneData,
...
}
```
### <a name="LaneWidth"></a>LaneWidth
This DE conveys the width of a lane in LSB units of 1 cm. Maximum value for a lane is 327.67 meters in width
@units: cm
**Categories:** Infrastructure information
**Revision:** _V1.3.1_
```asn1
LaneWidth ::= INTEGER (0..32767)
```
### <a name="LineNumber"></a>LineNumber
This DE is used to provide the R09 line information.
**Categories:** Infrastructure information
**Revision:** _V2.2.1_
```asn1
LineNumber ::= INTEGER (0..4294967295)
```
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
### <a name="MergeDivergeNodeAngle"></a>MergeDivergeNodeAngle
The angle at which another lane path meets the current lanes at the node point. Typically found in the node
attributes and used to describe the angle of the departing or merging lane. Note that oblique and obtuse angles are allowed.
The value `-180` shall be used to represent data is not available or unknown
**Unit:** _1.5 degrees from north_
**Categories:** Infrastructure information
**Revision:** _V1.3.1_
```asn1
MergeDivergeNodeAngle ::= INTEGER (-180..180)
```
### <a name="MinuteOfTheYear"></a>MinuteOfTheYear
This DE expresses the number of elapsed minutes of the current year in the time system being used (typically UTC time).
It is typically used to provide a longer range time stamp indicating when a message was created.
Taken together with the DSecond data element, it provides a range of one full year with a resolution of 1 millisecond.
The value 527040 shall be used for invalid.
**Categories:** Infrastructure information
**Revision:** _V1.3.1_
>>>
NOTE: It should be noted that at the yearly roll-over point there is no "zero" minute, in the same way that there was
never a "year zero" at the very start of the common era (BC -> AD). By using the number of elapsed whole minutes here
this issue is avoided and the first valid value of every new year is zero, followed by one, etc. Leap years are
accommodated, as are leap seconds in the DSecond data concept.
>>>
```asn1
MinuteOfTheYear ::= INTEGER (0..527040)
```
### <a name="MovementPhaseState"></a>MovementPhaseState
This DE provides the overall current state of the movement (in many cases a signal state), including its core phase state
and an indication of whether this state is permissive or protected.
It is expected that the allowed transitions from one state to another will be defined by regional deployments. Not all
regions will use all states; however, no new states are to be defined. In most regions a regulatory body provides precise
legal definitions of these state changes. For example, in the US the MUTCD is used, as is indicated in the US regional
variant of the above image. In various regions and modes of transportation, the visual expression of these states varies
(the precise meaning of various color combinations, shapes, and/or flashing etc.). The below definition is designed to to
be independent of these regional conventions.
Values:
- `unavailable` - 0: This state is used for unknown or error
- `dark` - 1: The signal head is dark (unlit)
- `stop-Then-Proceed` - 2: Often called 'flashing red'
Driver Action:
- Stop vehicle at stop line.
- Do not proceed unless it is safe.
Note that the right to proceed either right or left when it is safe may be contained in the lane description to
handle what is called a 'right on red'
- `stop-And-Remain` - 3: e.g. called 'red light'
Driver Action:
- Stop vehicle at stop line.
- Do not proceed.
Note that the right to proceed either right or left when it is safe may be contained in the lane description to
handle what is called a 'right on red'
- `pre-Movement` - 4: Not used in the US, red+yellow partly in EU
Driver Action:
- Stop vehicle.
- Prepare to proceed (pending green)
- (Prepare for transition to green/go)
- `permissive-Movement-Allowed` - 5: Often called 'permissive green'
Driver Action:
- Proceed with caution,
- must yield to all conflicting traffic
Conflicting traffic may be present in the intersection conflict area
- `protected-Movement-Allowed` - 6: Often called 'protected green'
Driver Action:
- Proceed, tossing caution to the wind, in indicated (allowed) direction.
- `permissive-clearance` - 7: Often called 'permissive yellow'.
The vehicle is not allowed to cross the stop bar if it is possible
to stop without danger.
Driver Action:
- Prepare to stop.
- Proceed if unable to stop,
- Clear Intersection.
Conflicting traffic may be present in the intersection conflict area
- `protected-clearance` - 8: Often called 'protected yellow'
Driver Action:
- Prepare to stop.
- Proceed if unable to stop, in indicated direction (to connected lane)
- Clear Intersection.
- `caution-Conflicting-Traffic` - 9: Often called 'flashing yellow'
Often used for extended periods of time
Driver Action:
- Proceed with caution,
Conflicting traffic may be present in the intersection conflict area
Values:
* **unavailable** (0)<br>
* **dark** (1)<br>
* **stop-Then-Proceed** (2)<br>
* **stop-And-Remain** (3)<br>
* **pre-Movement** (4)<br>
* **permissive-Movement-Allowed** (5)<br>
* **protected-Movement-Allowed** (6)<br>
* **permissive-clearance** (7)<br>
* **protected-clearance** (8)<br>
* **caution-Conflicting-Traffic** (9)<br>
**Categories:** Infrastructure information
**Revision:** _V1.3.1_
```asn1
MovementPhaseState ::= ENUMERATED {
unavailable (0),
dark (1),
stop-Then-Proceed (2),
stop-And-Remain (3),
pre-Movement (4),
permissive-Movement-Allowed (5),
protected-Movement-Allowed (6),
permissive-clearance (7),
protected-clearance (8),
caution-Conflicting-Traffic (9)
}
```
### <a name="MsgCount"></a>MsgCount
This DE is used to provide a sequence number within a stream of messages with the same DSRCmsgID and from the same sender.
A sender may initialize this element to any value in the range 0-127 when sending the first message with a given DSRCmsgID,
or if the sender has changed identity (e.g. by changing its TemporaryID) since sending the most recent message with that DSRCmsgID.
Depending on the application the sequence number may change with every message or may remain fixed during a stream of messages when the content within each
message has not changed from the prior message sent. For this element, the value after 127 is zero.
The receipt of a non-sequential MsgCount value (from the same sending device and message type) implies that one or
more messages from that sending device may have been lost, unless MsgCount has been re-initialized due to an identity
change.
In usage, some devices change their Temporary ID frequently, to prevent identity tracking, while others do not. A change
in Temporary ID data element value (which also changes the message contents in which it appears) implies that the
MsgCount may also change value.
If a sender is composing a message with new content with a given DSRCmsgID, and the TemporaryID has not changed
since it sent the previous message, the sender shall increment the previous value.
If a sender is composing a message with new content with a given DSRCmsgID, and the TemporaryID has changed since
it sent the previous message, the sender may set the MsgCount element to any valid value in the range (including
incrementing the previous value).
If a sender is composing a message with the same content as the most recent message with the same DSRCmsgID, and
less than 10 seconds have elapsed since it sent the previous message with that DSRCmsgID, the sender will use the
same MsgCount as sent in the previous message.
If a sender is composing a message with the same content as the most recent message with the same DSRCmsgID, and
at least 10 seconds have elapsed since it sent the previous message with that DSRCmsgID, the sender may set the
MsgCount element to any valid value in the range; this includes the re-use of the previous value.
If a sending device sends more than one stream of messages from message types that utilize the MsgCount element, it
shall maintain a separate MsgCount state for each message type so that the MsgCount value in a given message
identifies its place in the stream of that message type. The MsgCount element is a function only of the message type in a
given sending device, not of the one or more applications in that device which may be sending the same type of message.
**Categories:** Infrastructure information
**Revision:** _V1.3.1_
>>>
NOTE: In the absence of additional requirements defined in a standard using this data element, the follow guidelines shall be used.
>>>
```asn1
MsgCount ::= INTEGER (0..127)
```
### <a name="Offset-B09"></a>Offset-B09
A 9-bit delta offset in X, Y or Z direction from some known point. For non-vehicle centric coordinate frames of
reference, offset is positive to the East (X) and to the North (Y) directions. The most negative value shall be used to
indicate an unknown value.
a range of +- 2.55 meters
**Categories:** Infrastructure information
**Revision:** _V1.3.1_
```asn1
Offset-B09 ::= INTEGER (-256..255)
```
### <a name="Offset-B10"></a>Offset-B10
A 10-bit delta offset in X, Y or Z direction from some known point. For non-vehicle centric coordinate frames of
reference, offset is positive to the East (X) and to the North (Y) directions. The most negative value shall be used to
indicate an unknown value.
a range of +- 5.11 meters
**Categories:** Infrastructure information
**Revision:** _V1.3.1_
```asn1
Offset-B10 ::= INTEGER (-512..511)
```
### <a name="Offset-B11"></a>Offset-B11
An 11-bit delta offset in X or Y direction from some known point. For non-vehicle centric coordinate frames of
reference, offset is positive to the East (X) and to the North (Y) directions. The most negative value shall be used to
indicate an unknown value.
a range of +- 10.23 meters
**Categories:** Infrastructure information
**Revision:** _V1.3.1_
```asn1
Offset-B11 ::= INTEGER (-1024..1023)
```
### <a name="Offset-B12"></a>Offset-B12
A 12-bit delta offset in X, Y or Z direction from some known point. For non-vehicle centric coordinate frames of
reference, non-vehicle centric coordinate frames of reference, offset is positive to the East (X) and to the North (Y)
directions. The most negative value shall be used to indicate an unknown value.
a range of +- 20.47 meters
**Categories:** Infrastructure information
**Revision:** _V1.3.1_
```asn1
Offset-B12 ::= INTEGER (-2048..2047)
```
### <a name="Offset-B13"></a>Offset-B13
A 13-bit delta offset in X or Y direction from some known point. For non-vehicle centric coordinate frames of
reference, offset is positive to the East (X) and to the North (Y) directions. The most negative value shall be used to
indicate an unknown value.
a range of +- 40.95 meters
**Categories:** Infrastructure information
**Revision:** _V1.3.1_
```asn1
Offset-B13 ::= INTEGER (-4096..4095)
```
### <a name="Offset-B14"></a>Offset-B14
A 14-bit delta offset in X or Y direction from some known point. For non-vehicle centric coordinate frames of
reference, offset is positive to the East (X) and to the North (Y) directions.
a range of +- 81.91 meters
**Categories:** Infrastructure information
**Revision:** _V1.3.1_
```asn1
Offset-B14 ::= INTEGER (-8192..8191)
```
### <a name="Offset-B16"></a>Offset-B16
A 16-bit delta offset in X, Y or Z direction from some known point. For non-vehicle centric coordinate frames of
reference, offset is positive to the East (X) and to the North (Y) directions. The most negative value shall be used to
indicate an unknown value.
a range of +- 327.68 meters
**Categories:** Infrastructure information
**Revision:** _V1.3.1_
```asn1
Offset-B16 ::= INTEGER (-32768..32767)
```
### <a name="PedestrianBicycleDetect"></a>PedestrianBicycleDetect
This DE is used to provide an indication of whether Pedestrians and/or Bicyclists have been detected in the crossing lane.
true if ANY Pedestrians or Bicyclists are detected crossing the target lane or lanes
**Categories:** Infrastructure information
**Revision:** _V1.3.1_
```asn1
PedestrianBicycleDetect ::= BOOLEAN
```
### <a name="PositionConfidence"></a>PositionConfidence
This DE entry is used to provide the 95% confidence level for the currently reported value of
entries such as the DE_Position entries, taking into account the current calibration and precision of the sensor(s) used to
measure and/or calculate the value. It is used in the horizontal plane. This data element is only to provide the listener with
information on the limitations of the sensing system; not to support any type of automatic error correction or to imply a
guaranteed maximum error. This data element should not be used for fault detection or diagnosis, but if a vehicle is able
to detect a fault, the confidence interval should be increased accordingly. The frame of reference and axis of rotation used
shall be accordance with that defined in Section 11 of this standard.
- `unavailable` - 0: B'0000 Not Equipped or unavailable
- `a500m` - 1: B'0001 500m or about 5 * 10 ^ -3 decimal degrees
- `a200m` - 2: B'0010 200m or about 2 * 10 ^ -3 decimal degrees
- `a100m` - 3: B'0011 100m or about 1 * 10 ^ -3 decimal degrees
- `a50m` - 4: B'0100 50m or about 5 * 10 ^ -4 decimal degrees
- `a20m` - 5: B'0101 20m or about 2 * 10 ^ -4 decimal degrees
- `a10m` - 6: B'0110 10m or about 1 * 10 ^ -4 decimal degrees
- `a5m` - 7: B'0111 5m or about 5 * 10 ^ -5 decimal degrees
- `a2m` - 8: B'1000 2m or about 2 * 10 ^ -5 decimal degrees
- `a1m` - 9: B'1001 1m or about 1 * 10 ^ -5 decimal degrees
- `a50cm` - 10: B'1010 0.50m or about 5 * 10 ^ -6 decimal degrees
- `a20cm` - 11: B'1011 0.20m or about 2 * 10 ^ -6 decimal degrees
- `a10cm` - 12: B'1100 0.10m or about 1 * 10 ^ -6 decimal degrees
- `a5cm` - 13: B'1101 0.05m or about 5 * 10 ^ -7 decimal degrees
- `a2cm` - 14: B'1110 0.02m or about 2 * 10 ^ -7 decimal degrees
- `a1cm` - 15) B'1111 0.01m or about 1 * 10 ^ -7 decimal degrees
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
- Encoded as a 4 bit value
Values:
* **unavailable** (0)<br>
* **a500m** (1)<br>
* **a200m** (2)<br>
* **a100m** (3)<br>
* **a50m** (4)<br>
* **a20m** (5)<br>
* **a10m** (6)<br>
* **a5m** (7)<br>
* **a2m** (8)<br>
* **a1m** (9)<br>
* **a50cm** (10)<br>
* **a20cm** (11)<br>
* **a10cm** (12)<br>
* **a5cm** (13)<br>
* **a2cm** (14)<br>
* **a1cm** (15)<br>
**Categories:** Infrastructure information
**Revision:** _V1.3.1_
```asn1
PositionConfidence ::= ENUMERATED {
unavailable (0),
a500m (1),
a200m (2),
a100m (3),
a50m (4),
a20m (5),
a10m (6),
a5m (7),
a2m (8),
a1m (9),
a50cm (10),
a20cm (11),
a10cm (12),
a5cm (13),
a2cm (14),
a1cm (15)
}
```
### <a name="PrioritizationResponseStatus"></a>PrioritizationResponseStatus
This DE is used in the [**PrioritizationResponse**](#PrioritizationResponse) data frame to indicate the
general status of a prior prioritization request.
- `unknown` - 0: Unknown state
- `requested` - 1: This prioritization request was detected by the traffic controller
- `processing` - 2: Checking request (request is in queue, other requests are prior)
- `watchOtherTraffic` - 3: Cannot give full permission, therefore watch for other traffic. Note that other requests may be present
- `granted` - 4: Intervention was successful and now prioritization is active
- `rejected` - 5: The prioritization or preemption request was rejected by the traffic controller
- `maxPresence` - 6: The Request has exceeded maxPresence time. Used when the controller has determined that the requester should then back off and request an alternative.
- `reserviceLocked` - 7: Prior conditions have resulted in a reservice
locked event: the controller requires the passage of time before another similar request will be accepted
Values:
* **unknown** (0)<br>
* **requested** (1)<br>
* **processing** (2)<br>
* **watchOtherTraffic** (3)<br>
* **granted** (4)<br>
* **rejected** (5)<br>
* **maxPresence** (6)<br>
* **reserviceLocked** (7)<br>
**Categories:** Infrastructure information
**Revision:** _V1.3.1_
```asn1
PrioritizationResponseStatus ::= ENUMERATED {
unknown (0),
requested (1),
processing (2),
watchOtherTraffic (3),
granted (4),
rejected (5),
maxPresence (6),
reserviceLocked (7),
...
}
```
### <a name="PriorityLevel"></a>PriorityLevel
This DE is used to provide the R09 priority.
**Categories:** Infrastructure information
**Revision:** _V2.2.1_
```asn1
PriorityLevel ::= INTEGER (0..255)
```
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
### <a name="PriorityRequestType"></a>PriorityRequestType
This DE provides a means to indicate if a request (found in the Signal RequestMessage) represents
a new service request, a request update, or a request cancellation for either preemption or priority services.
Values:
* **priorityRequestTypeReserved** (0)<br>
* **priorityRequest** (1)<br>
* **priorityRequestUpdate** (2)<br>
* **priorityCancellation** (3)<br>
**Categories:** Infrastructure information
**Revision:** _V1.3.1_
```asn1
PriorityRequestType ::= ENUMERATED {
priorityRequestTypeReserved (0),
priorityRequest (1),
priorityRequestUpdate (2),
priorityCancellation (3),
...
}
```
### <a name="RegionId"></a>RegionId
This DE is used to define regions where unique additional content may be added and
used in the message set. The index values defined below represent various regions known at the time of publication. This
list is expected to grow over time. The index values assigned here can be augmented by local (uncoordinated)
assignments in the allowed range. It should be noted that such a local value is specified in the "REGION" ASN module, so
there is no need to edit the DSRC ASN specification of the standard. This process is further described in Section 11.1.
- `noRegion` - 0: Use default supplied stubs
- `addGrpA` - 1: USA
- `addGrpB` - 2: Japan
- `addGrpC` - 3: EU
**Categories:** Infrastructure information
**Revision:** _V1.3.1_
>>>
NOTE: new registered regional IDs will be added here
The values 128 and above are for local region use
>>>
```asn1
RegionId ::= INTEGER (0..255)
noRegion RegionId ::= 0
addGrpA RegionId ::= 1
addGrpB RegionId ::= 2
addGrpC RegionId ::= 3
```
### <a name="ReportingPoint"></a>ReportingPoint
This DE is used to provide the R09 reporting point.
**Categories:** Infrastructure information
**Revision:** _V2.2.1_
```asn1
ReportingPoint ::= INTEGER (0..65535)
```
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
4602
4603
4604
4605
4606
4607
4608
4609
4610
4611
4612
4613
4614
4615
4616
4617
4618
4619
4620
4621
4622
4623
4624
4625
4626
4627
4628
4629
4630
4631
4632
4633
4634
4635
4636
4637
4638
4639
4640
4641
4642
4643
4644
4645
4646
4647
4648
4649
4650
4651
4652
4653
4654
4655
4656
4657
4658
4659
4660
4661
4662
4663
4664
4665
4666
4667
4668
4669
4670
4671
4672
4673
4674
4675
4676
4677
4678
4679
4680
4681
4682
4683
4684
4685
4686
4687
4688
4689
4690
4691
4692
4693
4694
4695
4696
4697
4698
4699
4700
4701
4702
4703
4704
4705
4706
4707
4708
4709
4710
4711
4712
4713
4714
4715
4716
4717
4718
4719
4720
4721
4722
4723
4724
4725
4726
4727
4728
4729
4730
4731
4732
4733
4734
4735
4736
4737
4738
4739
4740
4741
4742
4743
4744
4745
4746
4747
4748
4749
4750
4751
4752
### <a name="RequestID"></a>RequestID
This DE is used to provide a unique ID between two parties for various dialog exchanges.
Combined with the sender's VehicleID (consisting of a TempID or a Station ID), this provides a unique string for some
mutually defined period of time. A typical example of use would be a signal preemption or priority request dialog
containing multiple requests from one sender (denoted by the unique RequestID with each). When such a request is
processed and reflected in the signal status messages, the original sender and the specific request can both be determined.
**Categories:** Infrastructure information
**Revision:** _V1.3.1_
>>>
NOTE: In typical use, this value is simply incremented in a modulo fashion to ensure a unique stream of values for the
device creating it. Any needs for uniqueness across multiple dialogs to one or more parties shall be the responsibility of
the device to manage. There are often normative restrictions on the device changing its TempID during various dialogs
when this data element is used. Further details of these operational concepts can be found in the relevant standards.
>>>
```asn1
RequestID ::= INTEGER (0..255)
```
### <a name="RequestImportanceLevel"></a>RequestImportanceLevel
This DE is used to state what type of signal request is being made to a signal
controller by a DSRC device in a defined role (such as a police vehicle). The levels of the request typically convey a
sense of urgency or importance with respect to other demands to allow the controller to use predefined business rules to
determine how to respond. These rules will vary in terms of how details of overall importance and urgency are to be
ranked, so they are to be implemented locally. As a result of this regional process, the list below should be assigned well-
defined meanings by the local deployment. These meaning will typically result in assigning a set of values to list for each
vehicle role type that is to be supported.
- `requestImportanceLevel1` 1: The least important request
- `requestImportanceLevel14` 14: The most important request
- `requestImportanceReserved` 15: Reserved for future use
Values:
* **requestImportanceLevelUnKnown** (0)<br>
* **requestImportanceLevel1** (1)<br>
* **requestImportanceLevel2** (2)<br>
* **requestImportanceLevel3** (3)<br>
* **requestImportanceLevel4** (4)<br>
* **requestImportanceLevel5** (5)<br>
* **requestImportanceLevel6** (6)<br>
* **requestImportanceLevel7** (7)<br>
* **requestImportanceLevel8** (8)<br>
* **requestImportanceLevel9** (9)<br>
* **requestImportanceLevel10** (10)<br>
* **requestImportanceLevel11** (11)<br>
* **requestImportanceLevel12** (12)<br>
* **requestImportanceLevel13** (13)<br>
* **requestImportanceLevel14** (14)<br>
* **requestImportanceReserved** (15)<br>
**Categories:** Infrastructure information
**Revision:** _V1.3.1_
```asn1
RequestImportanceLevel ::= ENUMERATED {
requestImportanceLevelUnKnown (0),
requestImportanceLevel1 (1),
requestImportanceLevel2 (2),
requestImportanceLevel3 (3),
requestImportanceLevel4 (4),
requestImportanceLevel5 (5),
requestImportanceLevel6 (6),
requestImportanceLevel7 (7),
requestImportanceLevel8 (8),
requestImportanceLevel9 (9),
requestImportanceLevel10 (10),
requestImportanceLevel11 (11),
requestImportanceLevel12 (12),
requestImportanceLevel13 (13),
requestImportanceLevel14 (14),
requestImportanceReserved (15)
}
```
### <a name="RequestSubRole"></a>RequestSubRole
This DE is used to further define the details of the role which any DSRC device might
play when making a request to a signal controller. This value is not always needed. For example, perhaps in a
deployment all police vehicles are to be treated equally. The taxonomy of what details are selected to be entered into the
list is a regional choice but should be devised to allow the controller to use predefined business rules to respond using the
data. As another example, perhaps in a regional deployment a cross-city express type of transit vehicle is given a different
service response for the same request than another type of transit vehicle making an otherwise similar request. As a
result of this regional process, the list below should be assigned well-defined meanings by the local deployment. These
meanings will typically result in assigning a set of values to list for each vehicle role type that is to be supported.
- `requestSubRole1` - 1: The first type of sub role
- `requestSubRole14` - 14: The last type of sub role
- `requestSubRoleReserved` - 15: Reserved for future use
Values:
* **requestSubRoleUnKnown** (0)<br>
* **requestSubRole1** (1)<br>
* **requestSubRole2** (2)<br>
* **requestSubRole3** (3)<br>
* **requestSubRole4** (4)<br>
* **requestSubRole5** (5)<br>
* **requestSubRole6** (6)<br>
* **requestSubRole7** (7)<br>
* **requestSubRole8** (8)<br>
* **requestSubRole9** (9)<br>
* **requestSubRole10** (10)<br>
* **requestSubRole11** (11)<br>
* **requestSubRole12** (12)<br>
* **requestSubRole13** (13)<br>
* **requestSubRole14** (14)<br>
* **requestSubRoleReserved** (15)<br>
**Categories:** Infrastructure information
**Revision:** _V1.3.1_
```asn1
RequestSubRole ::= ENUMERATED {
requestSubRoleUnKnown (0),
requestSubRole1 (1),
requestSubRole2 (2),
requestSubRole3 (3),
requestSubRole4 (4),
requestSubRole5 (5),
requestSubRole6 (6),
requestSubRole7 (7),
requestSubRole8 (8),
requestSubRole9 (9),
requestSubRole10 (10),
requestSubRole11 (11),
requestSubRole12 (12),
requestSubRole13 (13),
requestSubRole14 (14),
requestSubRoleReserved (15)
}
```
### <a name="RestrictionAppliesTo"></a>RestrictionAppliesTo
The RestrictionAppliesTo data element provides a short list of common vehicle types which may have one or more
special movements at an intersection. In general, these movements are not visible to other traffic with signal heads, but
the SPAT data reflects the state of the movement. Various restricted movements at an intersection can be expressed
using this element to indicate where the movement applies.
- `none` : applies to nothing
- `equippedTransit`: buses etc.
- `equippedTaxis`:
- `equippedOther`: other vehicle types with necessary signal phase state reception equipment
- `emissionCompliant`: regional variants with more definitive items also exist
- `equippedBicycle`:
- `weightCompliant`:
- `heightCompliant`: Items dealing with traveler needs serviced by the infrastructure. These end users (which are not vehicles) are presumed to be suitably equipped
- `pedestrians`:
- `slowMovingPersons`:
- `wheelchairUsers`:
- `visualDisabilities`:
- `audioDisabilities`: hearing
**Categories:** Infrastructure information
**Revision:** _V1.3.1_
```asn1
RestrictionAppliesTo ::= ENUMERATED {
none,
equippedTransit,
equippedTaxis,
equippedOther,
emissionCompliant,
equippedBicycle,
weightCompliant,
heightCompliant,
pedestrians,
slowMovingPersons,
wheelchairUsers,
visualDisabilities,
audioDisabilities,
otherUnknownDisabilities,
...
}
```
### <a name="RestrictionClassID"></a>RestrictionClassID
This DE defines an intersection-unique value to convey data about classes of users.
The mapping used varies with each intersection and is defined in the MAP message if needed. The defined mappings
found there are used to determine when a given class is meant. The typical use of this element is to map additional
movement restrictions or rights (in both the MAP and SPAT messages) to special classes of users (trucks, high sided
vehicles, special vehicles etc.). There is the general presumption that in the absence of this data, any allowed movement
extends to all users.
An index value to identify data about classes of users the value used varies with each intersection's
needs and is defined in the map to the assigned classes of supported users.
**Categories:** Infrastructure information
**Revision:** _V1.3.1_
```asn1
RestrictionClassID ::= INTEGER (0..255)
```
### <a name="RoadRegulatorID"></a>RoadRegulatorID
This DE is a 16-bit globally unique identifier assigned to an entity responsible for assigning
Intersection IDs in the region over which it has such authority. The value zero shall be used for testing, and should only be
used in the absence of a suitable assignment. A single entity which assigns intersection IDs may be assigned several
RoadRegulatorIDs. These assignments are presumed to be permanent.
The value zero shall be used for testing only
**Categories:** Infrastructure information
**Revision:** _V1.3.1_
```asn1
RoadRegulatorID ::= INTEGER (0..65535)
```
### <a name="RoadSegmentID"></a>RoadSegmentID
This DE is used to uniquely define a section of roadway within a country or region in a 16-bit field.
Assignment rules for this value are established elsewhere and may use regional assignment schemas that vary. Within
the region the policies used to ensure an assigned valueâs uniqueness before that value is reused is the responsibility of
that region. Such reuse is expected to occur, but over somewhat lengthy epoch (months).
The values zero to 255 shall be used for testing only
Note that the value assigned to an RoadSegment will be
unique within a given regional ID only during its use
**Categories:** Infrastructure information
**Revision:** _V1.3.1_
```asn1
RoadSegmentID ::= INTEGER (0..65535)
```
### <a name="RoadwayCrownAngle"></a>RoadwayCrownAngle
The RoadwayCrownAngle data element relates the gross tangential angle of the roadway surface with respect to
the local horizontal axis and is measured at the indicated part of the lane. This measurement is typically made at the
crown (centerline) or at an edge of the lane path. Its typical use is to relate data used in speed warning and traction
calculations for the lane segment or roadway segment in which the measurement is taken.
- The value -128 shall be used for unknown
- The value zero shall be used for angles which are between -0.15 and +0.15
**Unit:** _0.3 degrees of angle over a range of -38.1 to + 38.1 degrees_
**Categories:** Infrastructure information
**Revision:** _V1.3.1_
```asn1
RoadwayCrownAngle ::= INTEGER (-128..127)
```
### <a name="RouteNumber"></a>RouteNumber
This DE is used to provide the R09 route information.
**Categories:** Infrastructure information
**Revision:** _V2.2.1_
```asn1
RouteNumber ::= INTEGER (0..4294967295)
```
4763
4764
4765
4766
4767
4768
4769
4770
4771
4772
4773
4774
4775
4776
4777
4778
4779
4780
4781
4782
4783
4784
4785
4786
4787
4788
4789
4790
4791
4792
4793
4794
4795
4796
4797
4798
4799
4800
4801
4802
4803
4804
4805
4806
### <a name="RTCMmessage"></a>RTCMmessage
This DE contains the stream of octets of the actual RTCM message that is being sent.
The messageâs contents are defined in RTCM Standard 10403.1 and in RTCM Standard 10402.1 and its successors.
Note that most RTCM messages are considerably smaller than the size limit defined here, but that some messages may
need to be broken into smaller messages (as per the rules defined in the RTCM work) in order to be transmitted over DSRC.
**Categories:** Infrastructure information
**Revision:** _V1.3.1_
```asn1
RTCMmessage ::= OCTET STRING (SIZE(1..1023))
```
### <a name="RTCM-Revision"></a>RTCM-Revision
This DE provides the specific revision of the RTCM standard which is being used. This is
helpful to know precisely the mapping of the message types to their definitions, as well as some minor transport layer
ordering details when received in the mobile unit. All RTCM SC-104 messages follow a common message numbering
method (wherein all defined messages are given unique values) which can be decoded from the initial octets of the
message. This operation is typically performed by the GNSS rover that consumes the messages, so it is transparent at
the DSRC message set level.
Values:
- `rtcmRev2`: Std 10402.x et al
- `rtcmRev3`: Std 10403.x et al
Values:
* **unknown** (0)<br>
* **rtcmRev2** (1)<br>
* **rtcmRev3** (2)<br>
* **reserved** (3)<br>
**Categories:** Infrastructure information
**Revision:** _V1.3.1_
>>>
NOTE: In order to fully support the use of networked transport of RTCM corrections (so-called Ntrip systems), the
enumerated list of protocol types provides for all the common types outlined in RTCM Standard 10410.0, Appendix B. It is
anticipated that revisions 3.x and 2.3 will predominate in practice as they do today. It should also be noted that RTCM
standards use the term `byte` for an 8-bit value, while in this standard the term `octet` is used.
>>>
```asn1
RTCM-Revision ::= ENUMERATED {
unknown (0),
rtcmRev2 (1),
rtcmRev3 (2),
4810
4811
4812
4813
4814
4815
4816
4817
4818
4819
4820
4821
4822
4823
4824
4825
4826
4827
4828
4829
4830
4831
4832
4833
4834
4835
4836
4837
4838
4839
4840
4841
4842
4843
4844
4845
4846
4847
4848
4849
4850
4851
4852
4853
4854
4855
4856
4857
4858
4859
4860
4861
4862
4863
4864
4865
4866
4867
4868
4869
4870
4871
4872
4873
4874
4875
4876
4877
4878
4879
4880
4881
4882
4883
4884
4885
4886
4887
4888
4889
4890
4891
4892
4893
4894
4895
4896
4897
4898
4899
4900
4901
4902
4903
4904
4905
4906
4907
4908
4909
4910
4911
4912
4913
4914
4915
4916
4917
4918
4919
4920
4921
4922
4923
4924
4925
4926
4927
4928
4929
4930
4931
4932
4933
4934
4935
4936
4937
4938
4939
4940
4941
4942
4943
4944
4945
4946
4947
4948
4949
4950
4951
4952
4953
4954
4955
4956
4957
4958
4959
4960
4961
4962
4963
4964
4965
4966
4967
4968
4969
4970
4971
4972
4973
4974
4975
4976
4977
4978
4979
4980
4981
4982
4983
4984
4985
4986
4987
4988
4989
4990
4991
4992
4993
4994
4995
4996
4997
4998
4999
5000
reserved (3),
...
}
```
### <a name="Scale-B12"></a>Scale-B12
A 12-bit signed scaling factor supporting scales from zero (which is not used) to >200%. In this data element, the
value zero is taken to represent a value of one (scale 1:1). Values above and below this add or remove exactly 0.05%
from the initial value of 100%. Hence, a value of 2047 adds 102.35% to 100%, resulting in a scale of 202.35% exactly (the
largest valid scale value). Negative values which would result in an effective final value below zero are not supported. The
smallest valid value allowed is -1999 and the remaining negative values are reserved for future definition.
**Unit:** _in steps of 0.05 percent_
**Categories:** Infrastructure information
**Revision:** _V1.3.1_
```asn1
Scale-B12 ::= INTEGER (-2048..2047)
```
### <a name="SignalGroupID"></a>SignalGroupID
This DE is an index used to map between the internal state machine of one or more signal controllers (or
other types of traffic flow devices) and a common numbering system that can represent all possible combinations of active
states (movements and phases in US traffic terminology). All possible movement variations are assigned a unique value
within the intersection. Conceptually, the ID represents a means to provide a list of lanes in a set which would otherwise
need to be enumerated in the message. The values zero and 255 are reserved, so there may up to 254 different signal
group IDs within one single intersection. The value 255 represents a protected-Movement-Allowed or permissive-
Movement-Allowed condition that exists at all times. This value is applied to lanes, with or without traffic control devices,
that operate as free-flow lanes. Typically referred to as Channelized Right/Left Turn Lanes (in right/left-hand drive
countries).
Values:
- the value `0` shall be used when the ID is not available or not known
- the value `255` is reserved to indicate a permanent green movement state
- therefore a simple 8 phase signal controller device might use 1..9 as its groupIDs
**Categories:** Infrastructure information
**Revision:** _V1.3.1_
```asn1
SignalGroupID ::= INTEGER (0..255)
```
### <a name="SegmentAttributeXY"></a>SegmentAttributeXY
This DE is an enumerated list of attributes about the current lane segment which
may be enabled or disabled to indicate the presence or absence of the selected attribute on the segment. A segment is
one or more of the straight lines formed between each set of node points. It is common for a segment attribute to persist
for more than one set of node points if there is any curvature in the lane itself. The described attributes are all binary flags
in that they do not need to convey any additional data. Other attributes allow sending short data values to reflect a setting
which is set and persists in a similar fashion.
Various values which can be Enabled and Disabled for a lane segment
- reserved:
- doNotBlock: segment where a vehicle may not come to a stop
- whiteLine: segment where lane crossing not allowed such as the final few meters of a lane
- mergingLaneLeft: indicates porous lanes
- mergingLaneRight: indicates porous lanes
- curbOnLeft: indicates presence of curbs
- curbOnRight: indicates presence of curbs
- loadingzoneOnLeft: loading or drop off zones
- loadingzoneOnRight: loading or drop off zones
- turnOutPointOnLeft: opening to adjacent street/alley/road
- turnOutPointOnRight: opening to adjacent street/alley/road
- adjacentParkingOnLeft: side of road parking
- adjacentParkingOnRight: side of road parking
- adjacentBikeLaneOnLeft: presence of marked bike lanes
- adjacentBikeLaneOnRight: presence of marked bike lanes
- sharedBikeLane: right of way is shared with bikes who may occupy entire lane width
- bikeBoxInFront:
- transitStopOnLeft: any form of bus/transit loading, with pull in-out access to lane on left
- transitStopOnRight: any form of bus/transit loading, with pull in-out access to lane on right
- transitStopInLane: any form of bus/transit loading, in mid path of the lane
- sharedWithTrackedVehicle: lane is shared with train or trolley, not used for crossing tracks
- safeIsland: begin/end a safety island in path
- lowCurbsPresent: for ADA support
- rumbleStripPresent: for ADA support
- audibleSignalingPresent: for ADA support
- adaptiveTimingPresent: for ADA support
- rfSignalRequestPresent: Supports RF push to walk technologies
- partialCurbIntrusion: path is blocked by a median or curb but at least 1 meter remains open for use
and at-grade passage Lane geometry details
- taperToLeft: Used to control final path shape (see standard for defined shapes)
- taperToRight: Used to control final path shape (see standard for defined shapes)
- taperToCenterLine: Used to control final path shape (see standard for defined shapes)
- parallelParking: Parking at an angle with the street
- headInParking: Parking at an angle with the street
- freeParking: No restriction on use of parking
- timeRestrictionsOnParking: Parking is not permitted at all times
typically used when the 'parking' lane becomes a driving lane at times
- costToPark: Used where parking has a cost
- midBlockCurbPresent: a protruding curb near lane edge
- unEvenPavementPresent: a disjoint height at lane edge
Values:
* **reserved** <br>
* **doNotBlock** <br>
* **whiteLine** <br>
* **mergingLaneLeft** <br>
* **mergingLaneRight** <br>
* **curbOnLeft** <br>
* **curbOnRight** <br>
* **loadingzoneOnLeft** <br>
* **loadingzoneOnRight** <br>
* **turnOutPointOnLeft** <br>
* **turnOutPointOnRight** <br>
* **adjacentParkingOnLeft** <br>
* **adjacentParkingOnRight** <br>
* **adjacentBikeLaneOnLeft** <br>
* **adjacentBikeLaneOnRight** <br>
* **sharedBikeLane** <br>
* **bikeBoxInFront** <br>
* **transitStopOnLeft** <br>
* **transitStopOnRight** <br>
* **transitStopInLane** <br>
* **sharedWithTrackedVehicle** <br>
* **safeIsland** <br>
* **lowCurbsPresent** <br>
* **rumbleStripPresent** <br>
* **audibleSignalingPresent** <br>
* **adaptiveTimingPresent** <br>
* **rfSignalRequestPresent** <br>
* **partialCurbIntrusion** <br>
* **taperToLeft** <br>
* **taperToRight** <br>
* **taperToCenterLine** <br>
* **parallelParking** <br>
* **headInParking** <br>
* **freeParking** <br>
* **timeRestrictionsOnParking** <br>
* **costToPark** <br>
* **midBlockCurbPresent** <br>
* **unEvenPavementPresent** <br>
**Categories:** Infrastructure information
**Revision:** _V1.3.1_
```asn1
SegmentAttributeXY ::= ENUMERATED {
reserved ,
doNotBlock ,
whiteLine ,
mergingLaneLeft ,
mergingLaneRight ,
curbOnLeft ,
curbOnRight ,
loadingzoneOnLeft ,
loadingzoneOnRight ,
turnOutPointOnLeft ,
turnOutPointOnRight ,
adjacentParkingOnLeft ,
adjacentParkingOnRight ,
adjacentBikeLaneOnLeft ,
adjacentBikeLaneOnRight ,
sharedBikeLane ,
bikeBoxInFront ,
transitStopOnLeft ,
transitStopOnRight ,
transitStopInLane ,
sharedWithTrackedVehicle ,
safeIsland ,
lowCurbsPresent ,
rumbleStripPresent ,
audibleSignalingPresent ,
adaptiveTimingPresent ,
rfSignalRequestPresent ,
partialCurbIntrusion ,
taperToLeft ,
taperToRight ,
taperToCenterLine ,
parallelParking ,
headInParking ,
freeParking ,
timeRestrictionsOnParking ,
costToPark ,
midBlockCurbPresent ,
unEvenPavementPresent ,
...
}
```
### <a name="SemiMajorAxisAccuracy"></a>SemiMajorAxisAccuracy
This DE is used to express the radius (length) of the semi-major axis of an
ellipsoid representing the accuracy which can be expected from a GNSS system in 5cm steps,
typically at a one sigma level of confidence.
Value is semi-major axis accuracy at one standard dev.
- Range 0-12.7 meter, LSB = .05m
- 254 = any value equal or greater than 12.70 meter
- 255 = unavailable semi-major axis value