Newer
Older
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
4051
4052
4053
4054
4055
4056
4057
4058
4059
4060
4061
4062
4063
4064
4065
4066
4067
4068
4069
4070
4071
4072
4073
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
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="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="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_
4268
4269
4270
4271
4272
4273
4274
4275
4276
4277
4278
4279
4280
4281
4282
4283
4284
4285
4286
4287
4288
4289
```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_
4324
4325
4326
4327
4328
4329
4330
4331
4332
4333
4334
4335
4336
4337
4338
4339
4340
4341
4342
4343
4344
4345
```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_
4368
4369
4370
4371
4372
4373
4374
4375
4376
4377
4378
4379
4380
4381
4382
4383
4384
4385
4386
4387
4388
```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="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.
>>>
unknown (0),
rtcmRev2 (1),
rtcmRev3 (2),
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
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
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_
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
```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
**Unit:** _0.05m_
**Categories:** Infrastructure information
**Revision:** _V1.3.1_
```asn1
SemiMajorAxisAccuracy ::= INTEGER (0..255)
```
### <a name="SemiMajorAxisOrientation"></a>SemiMajorAxisOrientation
This DE is used to orientate the angle of the semi-major axis of an
ellipsoid representing the accuracy which can be expected from a GNSS system with respect to the coordinate system.
Value is orientation of semi-major axis
- relative to true north (0-359.9945078786 degrees)
- LSB units of 360/65535 deg = 0.0054932479
- a value of 0 shall be 0 degrees
- a value of 1 shall be 0.0054932479 degrees
- a value of 65534 shall be 359.9945078786 deg
- a value of 65535 shall be used for orientation unavailable
**Unit:** _360/65535 degree_
**Categories:** Infrastructure information
**Revision:** _V1.3.1_
```asn1
SemiMajorAxisOrientation ::= INTEGER (0..65535)
```
### <a name="SemiMinorAxisAccuracy"></a>SemiMinorAxisAccuracy
This DE is used to express the radius of the semi-minor 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-minor 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-minor axis value
**Unit:** _0.05m_
**Categories:** Infrastructure information
**Revision:** _V1.3.1_
```asn1
SemiMinorAxisAccuracy ::= INTEGER (0..255)
```
### <a name="SpeedAdvice"></a>SpeedAdvice
This data element represents the recommended velocity of an object, typically a vehicle speed along a roadway,
expressed in unsigned units of 0.1 meters per second.
- LSB units are 0.1 m/s
- the value 499 shall be used for values at or greater than 49.9 m/s
- the value 500 shall be used to indicate that speed is unavailable
**Unit:** _0.1 m/s_
**Categories:** Infrastructure information
**Revision:** _V1.3.1_
```asn1
SpeedAdvice ::= INTEGER (0..500)
```
### <a name="SpeedConfidenceDSRC"></a>SpeedConfidenceDSRC
This DE is used to provide the 95% confidence level for the currently reported
value of [**Speed**](#Speed), taking into account the current calibration and precision of the sensor(s) used to measure and/or
calculate the value. 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
- 0 - `unavailable` : Not Equipped or unavailable
- 1 - `prec100ms` : 100 meters / sec
- 2 - `prec10ms` : 10 meters / sec
- 3 - `prec5ms` : 5 meters / sec
- 4 - `prec1ms` : 1 meters / sec
- 5 - `prec0-1ms` : 0.1 meters / sec
- 6 - `prec0-05ms` : 0.05 meters / sec
- 7 - `prec0-01ms` : 0.01 meters / sec
Values:
* **unavailable** (0)<br>
* **prec100ms** (1)<br>
* **prec10ms** (2)<br>
* **prec5ms** (3)<br>
* **prec1ms** (4)<br>
* **prec0-1ms** (5)<br>
* **prec0-05ms** (6)<br>
**Categories:** Infrastructure information
**Revision:** _V1.3.1_
```asn1
SpeedConfidenceDSRC ::= ENUMERATED {
unavailable (0),
prec100ms (1),
prec10ms (2),
prec5ms (3),
prec1ms (4),
prec0-1ms (5),
prec0-05ms (6),
prec0-01ms (7)
```
### <a name="TemporaryID"></a>TemporaryID
This is the 4 octet random device identifier, called the TemporaryID. When used for a mobile OBU device, this value
will change periodically to ensure the overall anonymity of the vehicle, unlike a typical wireless or wired 802 device ID.
Because this value is used as a means to identify the local vehicles that are interacting during an encounter, it is used in
the message set. Other devices, such as infrastructure (RSUs), may have a fixed value for the temporary ID value. See
also [**StationId**](#StationId) which is used in other deployment regions.
**Categories:** Infrastructure information
**Revision:** _V1.3.1_
>>>
NOTE: The circumstances and times at which various DSRC devices (notably OBUs) create and change their current
Temporary ID is a complex application level topic. It should be noted that the Temporary ID is not the same as a device
MAC value, although when used as a means to uniquely identify a device, both have many common properties. It should
further be noted that the MAC value for a mobile OBU device (unlike a typical wireless or wired 802 device) will
periodically change to a new random value to ensure the overall anonymity of the vehicle.
>>>
```asn1
TemporaryID ::= OCTET STRING (SIZE(4))
```
### <a name="ThrottleConfidence"></a>ThrottleConfidence
This DE is used to provide the 95% confidence level for the currently reported
value of DE [**Throttle**](#Throttle), taking into account the current calibration and precision of the sensor(s) used to measure and/or
calculate the value. This data element is only to provide 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. If a fault that triggers the MIL is of a nature to render throttle performance unreliable, then ThrottleConfidence
should be represented as "notEquipped."
- 0 - `unavailable`: B'00 Not Equipped or unavailable
- 1 - `prec10percent`: B'01 10 percent Confidence level
- 2 - `prec1percent`: B'10 1 percent Confidence level
- 3 - `prec0-5percent`: B'11 0.5 percent Confidence level
Values:
* **unavailable** (0)<br>
* **prec10percent** (1)<br>
* **prec1percent** (2)<br>
* **prec0-5percent** (3)<br>
**Categories:** Infrastructure information
**Revision:** _V1.3.1_
```asn1
ThrottleConfidence ::= ENUMERATED {
unavailable (0),
prec10percent (1),
prec1percent (2),
prec0-5percent (3)
```
### <a name="TimeConfidence"></a>TimeConfidence
This DE is used to provide the 95% confidence level for the currently reported value
of time, taking into account the current calibration and precision of the sensor(s) used to measure and/or calculate the
value. This data element is only to provide 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.
- 0 - `unavailable` : Not Equipped or unavailable
- 1 - `time-100-000` : Better than 100 Seconds
- 2 - `time-050-000` : Better than 50 Seconds
- 3 - `time-020-000` : Better than 20 Seconds
- 4 - `time-010-000` : Better than 10 Seconds
- 5 - `time-002-000` : Better than 2 Seconds
- 6 - `time-001-000` : Better than 1 Second
- 7 - `time-000-500` : Better than 0.5 Seconds
- 8 - `time-000-200` : Better than 0.2 Seconds
- 9 - `time-000-100` : Better than 0.1 Seconds
- 10 - `time-000-050` : Better than 0.05 Seconds
- 11 - `time-000-020` : Better than 0.02 Seconds
- 12 - `time-000-010` : Better than 0.01 Seconds
- 13 - `time-000-005` : Better than 0.005 Seconds
- 14 - `time-000-002` : Better than 0.001 Seconds
- 15 - `time-000-001` : Better than 0.001 Seconds
- 16 - `time-000-000-5` : Better than 0.000,5 Seconds
- 17 - `time-000-000-2` : Better than 0.000,2 Seconds
- 18 - `time-000-000-1` : Better than 0.000,1 Seconds
- 19 - `time-000-000-05` : Better than 0.000,05 Seconds
- 20 - `time-000-000-02` : Better than 0.000,02 Seconds
- 21 - `time-000-000-01` : Better than 0.000,01 Seconds
- 22 - `time-000-000-005` : Better than 0.000,005 Seconds
- 23 - `time-000-000-002` : Better than 0.000,002 Seconds
- 24 - `time-000-000-001` : Better than 0.000,001 Seconds
- 25 - `time-000-000-000-5` : Better than 0.000,000,5 Seconds
- 26 - `time-000-000-000-2` : Better than 0.000,000,2 Seconds
- 27 - `time-000-000-000-1` : Better than 0.000,000,1 Seconds
- 28 - `time-000-000-000-05` : Better than 0.000,000,05 Seconds
- 29 - `time-000-000-000-02` : Better than 0.000,000,02 Seconds
- 30 - `time-000-000-000-01` : Better than 0.000,000,01 Seconds
- 31 - `time-000-000-000-005` : Better than 0.000,000,005 Seconds
- 32 - `time-000-000-000-002` : Better than 0.000,000,002 Seconds
- 33 - `time-000-000-000-001` : Better than 0.000,000,001 Seconds
- 34 - `time-000-000-000-000-5` : Better than 0.000,000,000,5 Seconds
- 35 - `time-000-000-000-000-2` : Better than 0.000,000,000,2 Seconds
- 36 - `time-000-000-000-000-1` : Better than 0.000,000,000,1 Seconds
- 37 - `time-000-000-000-000-05` : Better than 0.000,000,000,05 Seconds
- 38 - `time-000-000-000-000-02` : Better than 0.000,000,000,02 Seconds
- 39 - `time-000-000-000-000-01` : Better than 0.000,000,000,01 Seconds
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
Values:
* **unavailable** (0)<br>
* **time-100-000** (1)<br>
* **time-050-000** (2)<br>
* **time-020-000** (3)<br>
* **time-010-000** (4)<br>
* **time-002-000** (5)<br>
* **time-001-000** (6)<br>
* **time-000-500** (7)<br>
* **time-000-200** (8)<br>
* **time-000-100** (9)<br>
* **time-000-050** (10)<br>
* **time-000-020** (11)<br>
* **time-000-010** (12)<br>
* **time-000-005** (13)<br>
* **time-000-002** (14)<br>
* **time-000-001** (15)<br>
* **time-000-000-5** (16)<br>
* **time-000-000-2** (17)<br>
* **time-000-000-1** (18)<br>
* **time-000-000-05** (19)<br>
* **time-000-000-02** (20)<br>
* **time-000-000-01** (21)<br>
* **time-000-000-005** (22)<br>
* **time-000-000-002** (23)<br>
* **time-000-000-001** (24)<br>
* **time-000-000-000-5** (25)<br>
* **time-000-000-000-2** (26)<br>
* **time-000-000-000-1** (27)<br>
* **time-000-000-000-05** (28)<br>
* **time-000-000-000-02** (29)<br>
* **time-000-000-000-01** (30)<br>
* **time-000-000-000-005** (31)<br>
* **time-000-000-000-002** (32)<br>
* **time-000-000-000-001** (33)<br>
* **time-000-000-000-000-5** (34)<br>
* **time-000-000-000-000-2** (35)<br>
* **time-000-000-000-000-1** (36)<br>
* **time-000-000-000-000-05** (37)<br>
* **time-000-000-000-000-02** (38)<br>
* **time-000-000-000-000-01** (39)<br>
**Categories:** Infrastructure information
**Revision:** _V1.3.1_
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
```asn1
TimeConfidence ::= ENUMERATED {
unavailable (0),
time-100-000 (1),
time-050-000 (2),
time-020-000 (3),
time-010-000 (4),
time-002-000 (5),
time-001-000 (6),
time-000-500 (7),
time-000-200 (8),
time-000-100 (9),
time-000-050 (10),
time-000-020 (11),
time-000-010 (12),
time-000-005 (13),
time-000-002 (14),
time-000-001 (15),
time-000-000-5 (16),
time-000-000-2 (17),
time-000-000-1 (18),
time-000-000-05 (19),
time-000-000-02 (20),
time-000-000-01 (21),
time-000-000-005 (22),
time-000-000-002 (23),
time-000-000-001 (24),
time-000-000-000-5 (25),
time-000-000-000-2 (26),
time-000-000-000-1 (27),
time-000-000-000-05 (28),
time-000-000-000-02 (29),
time-000-000-000-01 (30),
time-000-000-000-005 (31),
time-000-000-000-002 (32),
time-000-000-000-001 (33),
time-000-000-000-000-5 (34),
time-000-000-000-000-2 (35),
time-000-000-000-000-1 (36),
time-000-000-000-000-05 (37),
time-000-000-000-000-02 (38),
time-000-000-000-000-01 (39)
}
```
### <a name="TimeIntervalConfidence"></a>TimeIntervalConfidence
This is the statistical confidence for the predicted time of signal group state change. For evaluation, the formula
10<sup>(x/a)</sup>-b with a=82.5 and b=1.3 was used. The values are encoded as probability classes with proposed values listed in
the below table in the ASN.1 specification.