Newer
Older
* _hpmsType_ of type [**VehicleType**](#VehicleType) OPTIONAL<br>
* _regional_ of type [**RegionalExtension**](#RegionalExtension) {{Reg-RequestorType}} OPTIONAL<br>
**Categories:** Infrastructure information
**Revision:** _V1.3.1_
```asn1
RequestorType ::= SEQUENCE {
role BasicVehicleRole,
subrole RequestSubRole OPTIONAL,
request RequestImportanceLevel OPTIONAL,
iso3883 Iso3833VehicleType OPTIONAL,
hpmsType VehicleType OPTIONAL,
regional RegionalExtension {{Reg-RequestorType}} OPTIONAL,
...
}
```
### <a name="RestrictionClassAssignment"></a>RestrictionClassAssignment
This DF is used to assign (or bind) a single RestrictionClassID data
element to a list of all user classes to which it applies. A collection of these bindings is conveyed in the
RestrictionClassList data frame in the MAP message to travelers. The established index is then used in the lane object of
the MAP message, in the ConnectTo data frame, to qualify to whom a signal group ID applies when it is sent by the SPAT
message about a movement.
* _id_ of type [**RestrictionClassID**](#RestrictionClassID) <br>
the unique value (within an intersection or local region) that is assigned to this group of users.
* _users_ of type [**RestrictionUserTypeList**](#RestrictionUserTypeList) <br>
The list of user types/classes to which this restriction ID applies.
**Categories:** Infrastructure information
**Revision:** _V1.3.1_
```asn1
RestrictionClassAssignment ::= SEQUENCE {
id RestrictionClassID,
users RestrictionUserTypeList
}
```
### <a name="RestrictionClassList"></a>RestrictionClassList
This DF is used to enumerate a list of user classes which belong to a given
assigned index. The resulting collection is treated as a group by the signal controller when it issues movement data
(signal phase information) with the GroupID for this group. This data frame is typically static for long periods of time
(months) and conveyed to the user by means of the MAP message.
**Categories:** Infrastructure information
**Revision:** _V1.3.1_
>>>
NOTE: The overall restriction class assignment process allows dynamic support within the framework of the common
message set for the various special cases that some signalized intersections must support. While the assigned value
needs to be unique only within the scope of the intersection that uses it, the resulting assignment lists will tend to be static
and stable for regional deployment areas such as a metropolitan area based on their operational practices and needs.
>>>
```asn1
RestrictionClassList ::= SEQUENCE (SIZE(1..254)) OF RestrictionClassAssignment
```
### <a name="RestrictionUserType"></a>RestrictionUserType
This DF is used to provide a means to select one, and only one, user type or class
from a number of well-known lists. The selected entry is then used in the overall Restriction Class assignment process to
indicate that a given GroupID (a way of expressing a movement in the SPAT/MAP system) applies to (is restricted to) this
class of user.
Values:
* _basicType_ of type [**RestrictionAppliesTo**](#RestrictionAppliesTo) <br>
* _regional_ of type **SEQUENCE** (SIZE(1..4)) OF<br>
* **RegionalExtension** {{Reg-RestrictionUserType}}<br>
**Categories:** Infrastructure information
**Revision:** _V1.3.1_
```asn1
RestrictionUserType ::= CHOICE {
basicType RestrictionAppliesTo,
regional SEQUENCE (SIZE(1..4)) OF
RegionalExtension {{Reg-RestrictionUserType}},
...
}
```
### <a name="RestrictionUserTypeList"></a>RestrictionUserTypeList
This DF consists of a list of [**RestrictionUserType**](#RestrictionUserType) entries.
**Categories:** Infrastructure information
**Revision:** _V1.3.1_
```asn1
RestrictionUserTypeList ::= SEQUENCE (SIZE(1..16)) OF RestrictionUserType
```
### <a name="RoadLaneSetList"></a>RoadLaneSetList
This DF consists of a list of GenericLane entries used to describe a segment of roadway.
**Categories:** Infrastructure information
**Revision:** _V1.3.1_
```asn1
RoadLaneSetList ::= SEQUENCE (SIZE(1..255)) OF GenericLane
```
### <a name="RoadSegmentReferenceID"></a>RoadSegmentReferenceID
This DF is used to convey theRoadSegmentID which is unique to a given road segment of interest,
and also the RoadRegulatorID assigned to the region in which it is operating (when required).
* _region_ of type [**RoadRegulatorID**](#RoadRegulatorID) OPTIONAL<br>
a globally unique regional assignment value typically assigned to a regional DOT authority the value zero shall be used for testing needs.
* _id_ of type [**RoadSegmentID**](#RoadSegmentID) <br>
a unique mapping to the road segment in question within the above region of use during its period of assignment and use
note that unlike intersectionID values, this value can be reused by the region.
**Categories:** Infrastructure information
**Revision:** _V1.3.1_
```asn1
RoadSegmentReferenceID ::= SEQUENCE {
region RoadRegulatorID OPTIONAL,
id RoadSegmentID
}
```
### <a name="RoadSegment"></a>RoadSegment
This DF is a complete description of a RoadSegment including its geometry and its
allowed navigational paths (independent of any additional regulatory restrictions that may apply over time or from user
classification) and any current disruptions such as a work zone or incident event.
Values:
* _name_ of type [**DescriptiveName**](#DescriptiveName) OPTIONAL<br>
* _id_ of type [**RoadSegmentReferenceID**](#RoadSegmentReferenceID) <br>
* _revision_ of type [**MsgCount**](#MsgCount) <br>
* _refPoint_ of type [**Position3D**](#Position3D) <br>
the reference from which subsequent data points are offset until a new point is used.
* _laneWidth_ of type [**LaneWidth**](#LaneWidth) OPTIONAL<br>
Reference width used by all subsequent lanes unless a new width is given.
* _speedLimits_ of type [**SpeedLimitList**](#SpeedLimitList) OPTIONAL<br>
Reference regulatory speed limits used by all subsequent lanes unless a new speed is given.
* _roadLaneSet_ of type [**RoadLaneSetList**](#RoadLaneSetList) <br>
Data describing disruptions in the RoadSegment such as work zones etc will be added here.
* _regional_ of type **SEQUENCE** (SIZE(1..4)) OF<br>
* **RegionalExtension** {{Reg-RoadSegment}} OPTIONAL<br>
**Categories:** Infrastructure information
**Revision:** _V1.3.1_
```asn1
RoadSegment ::= SEQUENCE {
name DescriptiveName OPTIONAL,
id RoadSegmentReferenceID,
revision MsgCount,
refPoint Position3D,
laneWidth LaneWidth OPTIONAL,
speedLimits SpeedLimitList OPTIONAL,
roadLaneSet RoadLaneSetList,
regional SEQUENCE (SIZE(1..4)) OF
RegionalExtension {{Reg-RoadSegment}} OPTIONAL,
...
}
```
### <a name="RoadSegmentList"></a>RoadSegmentList
This DF consists of a list of [**RoadSegment**](#RoadSegment) entries.
**Categories:** Infrastructure information
**Revision:** _V1.3.1_
```asn1
RoadSegmentList ::= SEQUENCE (SIZE(1..32)) OF RoadSegment
```
### <a name="RTCMheader"></a>RTCMheader
This DF is a collection of data values used to convey RTCM information between users. It
is not required or used when sending RTCM data from a corrections source to end users (from a base station to devices
deployed in the field which are called rovers).
* _status_ of type [**GNSSstatus**](#GNSSstatus) <br>
* _offsetSet_ of type [**AntennaOffsetSet**](#AntennaOffsetSet) <br>
**Categories:** Infrastructure information
**Revision:** _V1.3.1_
```asn1
RTCMheader ::= SEQUENCE {
status GNSSstatus,
offsetSet AntennaOffsetSet
```
### <a name="RTCMmessageList"></a>RTCMmessageList
This DF consists of a list of [**RTCMmessage**](#RTCMmessage) entries.
**Categories:** Infrastructure information
**Revision:** _V1.3.1_
```asn1
RTCMmessageList ::= SEQUENCE (SIZE(1..5)) OF RTCMmessage
```
### <a name="SegmentAttributeXYList"></a>SegmentAttributeXYList
This DF consists of a list of [**SegmentAttributeXY**](#SegmentAttributeXY) entries.
**Categories:** Infrastructure information
**Revision:** _V1.3.1_
```asn1
SegmentAttributeXYList ::= SEQUENCE (SIZE(1..8)) OF SegmentAttributeXY
```
### <a name="SignalControlZone"></a>SignalControlZone
This DF is a dummy placeholder to contain a regional SignalControlZone DF.
It is not used, yet here for backwards compatibility.
* _zone_ of type [**RegionalExtension**](#RegionalExtension) {{Reg-SignalControlZone}}<br>
**Categories:** Infrastructure information
**Revision:** _V1.3.1_
```asn1
SignalControlZone ::= SEQUENCE {
zone RegionalExtension {{Reg-SignalControlZone}},
...
}
```
### <a name="SignalRequesterInfo"></a>SignalRequesterInfo
This DF is used to contain information regarding the entity that requested a given
signal behavior. In addition to the VehicleID, the data frame also contains a request reference number used to uniquely
refer to the request and some basic type information about the request maker which may be used by other parties.
* _id_ of type [**VehicleID**](#VehicleID) <br>
to uniquely identify the requester and the specific request to all parties.
* _request_ of type [**RequestID**](#RequestID) <br>
to uniquely identify the requester and the specific request to all parties.
* _sequenceNumber_ of type [**MsgCount**](#MsgCount) <br>
to uniquely identify the requester and the specific request to all parties.
* _role_ of type [**BasicVehicleRole**](#BasicVehicleRole) OPTIONAL<br>
* _typeData_ of type [**RequestorType**](#RequestorType) OPTIONAL<br>
Used when addition data besides the role is needed, at which point the role entry above is not sent.
**Categories:** Infrastructure information
**Revision:** _V1.3.1_
```asn1
SignalRequesterInfo ::= SEQUENCE {
id VehicleID,
request RequestID,
sequenceNumber MsgCount,
role BasicVehicleRole OPTIONAL,
typeData RequestorType OPTIONAL,
...
}
```
### <a name="SignalRequest"></a>SignalRequest
This DF is used (as part of a request message) to request either a priority or a preemption service
from a signalized intersection. It relates the intersection ID as well as the specific request information. Additional
information includes the approach and egress values or lanes to be used.
Values:
* _id_ of type [**IntersectionReferenceID**](#IntersectionReferenceID) <br>
* _requestID_ of type [**RequestID**](#RequestID) <br>
* _requestType_ of type [**PriorityRequestType**](#PriorityRequestType) <br>
The type of request or cancel for priority or preempt use when a prior request is canceled, only the requestID is needed.
* _inBoundLane_ of type [**IntersectionAccessPoint**](#IntersectionAccessPoint) <br>
* _outBoundLane_ of type [**IntersectionAccessPoint**](#IntersectionAccessPoint) OPTIONAL<br>
desired exit approach or lane. the value zero is used to indicate intent to stop within the intersection.
* _regional_ of type **SEQUENCE** (SIZE(1..4)) OF<br>
* **RegionalExtension** {{Reg-SignalRequest}} OPTIONAL<br>
**Categories:** Infrastructure information
**Revision:** _V1.3.1_
>>>
NOTE: In typical use either an approach or a lane number would be given, this indicates the requested
path through the intersection to the degree it is known.
>>>
```asn1
SignalRequest ::= SEQUENCE {
id IntersectionReferenceID,
requestID RequestID,
requestType PriorityRequestType,
inBoundLane IntersectionAccessPoint,
outBoundLane IntersectionAccessPoint OPTIONAL,
regional SEQUENCE (SIZE(1..4)) OF
RegionalExtension {{Reg-SignalRequest}} OPTIONAL,
...
}
```
### <a name="SignalRequestList"></a>SignalRequestList
This DF consists of a list of [**SignalRequest**](#SignalRequest) entries.
**Categories:** Infrastructure information
**Revision:** _V1.3.1_
```asn1
SignalRequestList ::= SEQUENCE (SIZE(1..32)) OF SignalRequestPackage
```
### <a name="SignalRequestPackage"></a>SignalRequestPackage
This DF contains both the service request itself (the preemption and priority
details and the inbound-outbound path details for an intersection) and the time period (start and end time) over which this
service is sought from one single intersection. One or more of these packages are contained in a list in the Signal
Request Message (SREM).
Values:
* _request_ of type [**SignalRequest**](#SignalRequest) <br>
The specific request to the intersection contains IntersectionID, request type, requested action (approach/lane request).
* _minute_ of type [**MinuteOfTheYear**](#MinuteOfTheYear) OPTIONAL<br>
* _second_ of type [**DSecond**](#DSecond) OPTIONAL<br>
* _duration_ of type [**DSecond**](#DSecond) OPTIONAL<br>
The duration value is used to provide a short interval that extends the ETA so that the requesting vehicle can arrive at
the point of service with uncertainty or with some desired duration of service. This concept can be used to avoid needing
to frequently update the request. The requester must update the ETA and duration values if the
period of services extends beyond the duration time. It should be assumed that if the vehicle does not clear the
intersection when the duration is reached, the request will be cancelled and the intersection will revert to normal operation.
* _regional_ of type **SEQUENCE** (SIZE(1..4)) OF<br>
* **RegionalExtension** {{Reg-SignalRequestPackage}} OPTIONAL<br>
**Categories:** Infrastructure information
**Revision:** _V1.3.1_
```asn1
SignalRequestPackage ::= SEQUENCE {
request SignalRequest,
minute MinuteOfTheYear OPTIONAL,
second DSecond OPTIONAL,
duration DSecond OPTIONAL,
regional SEQUENCE (SIZE(1..4)) OF
RegionalExtension {{Reg-SignalRequestPackage}} OPTIONAL,
...
}
```
### <a name="SignalStatus"></a>SignalStatus
This DF is used to provide the status of a single intersection to others, including any active
preemption or priority state in effect.
Values:
* _sequenceNumber_ of type [**MsgCount**](#MsgCount) <br>
* _id_ of type [**IntersectionReferenceID**](#IntersectionReferenceID) <br>
this provides a unique mapping to the intersection map in question which provides complete location
and approach/movement/lane data as well as zones for priority/preemption.
* _sigStatus_ of type [**SignalStatusPackageList**](#SignalStatusPackageList) <br>
a list of detailed status containing all priority or preemption state data, both active and pending,
and who requested it requests which are denied are also listed here for a short period of time.
* _regional_ of type **SEQUENCE** (SIZE(1..4)) OF<br>
* **RegionalExtension** {{Reg-SignalStatus}} OPTIONAL<br>
**Categories:** Infrastructure information
**Revision:** _V1.3.1_
```asn1
SignalStatus ::= SEQUENCE {
sequenceNumber MsgCount,
id IntersectionReferenceID,
sigStatus SignalStatusPackageList,
regional SEQUENCE (SIZE(1..4)) OF
RegionalExtension {{Reg-SignalStatus}} OPTIONAL,
...
}
```
### <a name="SignalStatusList"></a>SignalStatusList
This DF consists of a list of [**SignalStatus**](#SignalStatus) entries.
**Categories:** Infrastructure information
**Revision:** _V1.3.1_
```asn1
SignalStatusList ::= SEQUENCE (SIZE(1..32)) OF SignalStatus
```
### <a name="SignalStatusPackageList"></a>SignalStatusPackageList
This DF consists of a list of [**SignalStatusPackage**](#SignalStatusPackage) entries.
**Categories:** Infrastructure information
**Revision:** _V1.3.1_
```asn1
SignalStatusPackageList ::= SEQUENCE (SIZE(1..32)) OF SignalStatusPackage
```
### <a name="SignalStatusPackage"></a>SignalStatusPackage
This DF contains all the data needed to describe the preemption or priority state
of the signal controller with respect to a given request and to uniquely identify the party who requested that state to occur.
It should be noted that this data frame describes both active and anticipated states of the controller. A requested service
may not be active when the message is created and issued. A requested service may be rejected. This structure allows
the description of pending requests that have been granted (accepted rather than rejected) but are not yet active and
being serviced. It also provides for the description of rejected requests so that the initial message is acknowledged
(completing a dialog using the broadcast messages).
Values:
* _requester_ of type [**SignalRequesterInfo**](#SignalRequesterInfo) OPTIONAL<br>
* _inboundOn_ of type [**IntersectionAccessPoint**](#IntersectionAccessPoint) <br>
* _outboundOn_ of type [**IntersectionAccessPoint**](#IntersectionAccessPoint) OPTIONAL<br>
* _minute_ of type [**MinuteOfTheYear**](#MinuteOfTheYear) OPTIONAL<br>
The Estimated Time of Arrival (ETA) when the service is requested. This data echos the data of the request.
* _second_ of type [**DSecond**](#DSecond) OPTIONAL<br>
* _duration_ of type [**DSecond**](#DSecond) OPTIONAL<br>
* _status_ of type [**PrioritizationResponseStatus**](ETSI-ITS-DSRC.md#PrioritizationResponseStatus) <br>
* _regional_ of type **SEQUENCE** (SIZE(1..4)) OF<br>
* **RegionalExtension** {{Reg-SignalStatusPackage}} OPTIONAL<br>
**Categories:** Infrastructure information
**Revision:** _V1.3.1_
```asn1
SignalStatusPackage ::= SEQUENCE {
requester SignalRequesterInfo OPTIONAL,
inboundOn IntersectionAccessPoint,
outboundOn IntersectionAccessPoint OPTIONAL,
minute MinuteOfTheYear OPTIONAL,
second DSecond OPTIONAL,
duration DSecond OPTIONAL,
status PrioritizationResponseStatus,
regional SEQUENCE (SIZE(1..4)) OF
RegionalExtension {{Reg-SignalStatusPackage}} OPTIONAL,
...
}
### <a name="SpeedandHeadingandThrottleConfidence"></a>SpeedandHeadingandThrottleConfidence
This DF is a single data frame combining multiple related bit fields into one concept.
* _heading_ of type [**HeadingConfidenceDSRC**](#HeadingConfidenceDSRC) <br>
* _speed_ of type [**SpeedConfidenceDSRC**](#SpeedConfidenceDSRC) <br>
* _throttle_ of type [**ThrottleConfidence**](#ThrottleConfidence) <br>
**Categories:** Infrastructure information
**Revision:** _V1.3.1_
```asn1
SpeedandHeadingandThrottleConfidence ::= SEQUENCE {
heading HeadingConfidenceDSRC,
speed SpeedConfidenceDSRC,
throttle ThrottleConfidence
```
### <a name="SpeedLimitList"></a>SpeedLimitList
This DF consists of a list of SpeedLimit entries.
**Categories:** Infrastructure information
**Revision:** _V1.3.1_
```asn1
SpeedLimitList ::= SEQUENCE (SIZE(1..9)) OF RegulatorySpeedLimit
```
### <a name="SpeedLimitType"></a>SpeedLimitType
This DE relates the type of speed limit to which a given speed refers.
- unknown: Speed limit type not available
- maxSpeedInSchoolZone: Only sent when the limit is active
- maxSpeedInSchoolZoneWhenChildrenArePresent: Sent at any time
- maxSpeedInConstructionZone: Used for work zones, incident zones, etc. where a reduced speed is present
- vehicleMinSpeed: Regulatory speed limit for general traffic
- vehicleMaxSpeed: Regulatory speed limit for general traffic
**Categories:** Infrastructure information
**Revision:** _V1.3.1_
```asn1
SpeedLimitType ::= ENUMERATED {
unknown,
maxSpeedInSchoolZone,
maxSpeedInSchoolZoneWhenChildrenArePresent,
maxSpeedInConstructionZone,
vehicleMinSpeed,
vehicleMaxSpeed,
vehicleNightMaxSpeed,
truckMinSpeed,
truckMaxSpeed,
truckNightMaxSpeed,
vehiclesWithTrailersMinSpeed,
vehiclesWithTrailersMaxSpeed,
vehiclesWithTrailersNightMaxSpeed,
...
}
```
### <a name="TimeChangeDetails"></a>TimeChangeDetails
This DF conveys details about the timing of a phase within a movement. The core
data concept expressed is the time stamp (time mark) at which the related phase will change to the next state. This is
often found in the MinEndTime element, but the other elements may be needed to convey the full concept when adaptive
timing is employed.
* _startTime_ of type [**TimeMark**](#TimeMark) OPTIONAL<br>
is used to relate when the phase itself started or is expected to start. This in turn allows the
indication that a set of time change details refers to a future phase, rather than a currently active phase.
By this method, timing information about "pre" phase events (which are the short transitional phase used to alert OBUs to
an impending green/go or yellow/caution phase) and the longer yellow-caution phase data is supported in the same form
as various green/go phases. In theory, the time change details could be sent for a large sequence of phases if the signal
timing was not adaptive and the operator wished to do so. In practice, it is expected only the "next" future phase will
commonly be sent. It should be noted that this also supports the sending of time periods regarding various red phases;
however, this is not expected to be done commonly.
* _minEndTime_ of type [**TimeMark**](#TimeMark) <br>
is used to convey the earliest time possible at which the phase could change, except when
unpredictable events relating to a preemption or priority call disrupt a currently active timing plan. In a phase where the
time is fixed (as in a fixed yellow or clearance time), this element shall be used alone. This value can be viewed as the
earliest possible time at which the phase could change, except when unpredictable events relating to a preemption or
priority call come into play and disrupt a currently active timing plan.
* _maxEndTime_ of type [**TimeMark**](#TimeMark) OPTIONAL<br>
is used to convey the latest time possible which the phase could change,
except when unpredictable events relating to a preemption or priority
call come into play and disrupt a currently active timing plan. In a phase where the time is fixed (as in a fixed yellow or
clearance time), this element shall be used alone.
* _likelyTime_ of type [**TimeMark**](#TimeMark) OPTIONAL<br>
is used to convey the most likely time the phase changes. This occurs between MinEndTime and
MaxEndTime and is only relevant for traffic-actuated control programs. This time might be calculated out of logged
historical values, detected events (e.g., from inductive loops), or from other sources.
* _confidence_ of type [**TimeIntervalConfidence**](#TimeIntervalConfidence) OPTIONAL<br>
is used to convey basic confidence data about the likelyTime.
* _nextTime_ of type [**TimeMark**](#TimeMark) OPTIONAL<br>
is used to express a general (and presumably less precise) value regarding when this phase will
next occur. This is intended to be used to alert the OBU when the next green/go may occur so that various ECO driving
applications can better manage the vehicle during the intervening stopped time.
**Categories:** Infrastructure information
**Revision:** _V1.3.1_
>>>
NOTE: Remarks: It should be noted that all times are expressed as absolute values and not as countdown timer values. When
the stated time mark is reached, the state changes to the next state. Several technical reasons led to this choice; among
these was that with a countdown embodiment, there is an inherent need to update the remaining time every time a SPAT
message is issued. This would require re-formulating the message content as as well as cryptographically signing the
message each time. With the use of absolute values (time marks) chosen here, the current count down time when the
message is created is added to the then-current time to create an absolute value and can be used thereafter without
change. The message content need only change when the signal controller makes a timing decision to be published. This
allows a clean separation of the logical functions of message creation from the logical functions of message scheduling
and sending, and fulfills the need to minimize further real time processing when possible. This Standard sets no limits on
where each of these functions is performed in the overall roadside system.
>>>
maxEndTime TimeMark OPTIONAL,
likelyTime TimeMark OPTIONAL,
}
```
### <a name="TimeMark"></a>TimeMark
This DE is used to relate a moment in UTC (Coordinated Universal Time)-based time when a
signal phase is predicted to change, with a precision of 1/10 of a second. A range of 60 full minutes is supported and it
can be presumed that the receiver shares a common sense of time with the sender which is kept aligned to within a
fraction of a second or better.
If there is a need to send a value greater than the range allowed by the data element (over one hour in the future), the
value 36000 shall be sent and shall be interpreted to indicate an indefinite future time value. When the value to be used is
undefined or unknown a value of 36001 shall be sent. Note that leap seconds are also supported.
The value is tenths of a second in the current or next hour in units of 1/10th second from UTC time
- The values 35991..35999 are used when a leap second occurs
- The value 36000 is used to indicate time >3600 seconds
- 36001 is to be used when value undefined or unknown
**Categories:** Infrastructure information
**Revision:** _V1.3.1_
>>>
NOTE: Note that this is NOT expressed in GPS time or in local time
>>>
```asn1
TimeMark ::= INTEGER (0..36001)
```
### <a name="TransmissionAndSpeed"></a>TransmissionAndSpeed
This DF expresses the speed of the vehicle and the state of the transmission.
The transmission state of 'reverse' can be used as a sign value for the speed element when needed.
* _transmisson_ of type [**TransmissionState**](#TransmissionState) <br>
* _speed_ of type [**Velocity**](#Velocity) <br>
**Categories:** Infrastructure information
**Revision:** _V1.3.1_
```asn1
TransmissionAndSpeed ::= SEQUENCE {
transmisson TransmissionState,
speed Velocity
}
```
### <a name="VehicleID"></a>VehicleID
This DF is used to contain either a (US) TemporaryID or an (EU) StationID in a simple frame.
These two different value domains are used to uniquely identify a vehicle or other object in these two regional DSRC
value is unavailable but needed by another type of user (such as the roadside infrastructure sending data about an
environments. In normal use cases, this value changes over time to prevent tracking of the subject vehicle. When this
unequipped vehicle), the value zero shall be used. A typical restriction on the use of this value during a dialog or other
exchange is that the value remains constant for the duration of that exchange. Refer to the performance requirements for
a given application for details.
* _entityID_ of type [**TemporaryID**](#TemporaryID) <br>
* _stationID_ of type [**StationID**](ETSI-ITS-CDD.md#StationID) <br>
**Categories:** Infrastructure information
**Revision:** _V1.3.1_
```asn1
VehicleID ::= CHOICE {
entityID TemporaryID,
stationID StationID
}
```
### <a name="AdvisorySpeedType"></a>AdvisorySpeedType
This DE relates the type of travel to which a given speed refers. This element is
typically used as part of an [**AdvisorySpeed**](#AdvisorySpeed) data frame for signal phase and timing data.
Values:
* **none** (0)<br>
* **greenwave** (1)<br>
* **ecoDrive** (2)<br>
* **transit** (3)<br>
**Categories:** Infrastructure information
**Revision:** _V1.3.1_
```asn1
AdvisorySpeedType ::= ENUMERATED {
none (0),
greenwave (1),
ecoDrive (2),
transit (3),
...
}
```
### <a name="AllowedManeuvers"></a>AllowedManeuvers
This DE relates the allowed (possible) maneuvers from a lane, typically a
motorized vehicle lane. It should be noted that in practice these values may be further restricted by vehicle class, local
regulatory environment and other changing conditions.
Values:
* **maneuverStraightAllowed** (0)<br>
* **maneuverLeftAllowed** (1)<br>
* **maneuverRightAllowed** (2)<br>
* **maneuverUTurnAllowed** (3)<br>
* **maneuverLeftTurnOnRedAllowed** (4)<br>
* **maneuverRightTurnOnRedAllowed** (5)<br>
* **maneuverLaneChangeAllowed** (6)<br>
* **maneuverNoStoppingAllowed** (7)<br>
* **yieldAllwaysRequired** (8)<br>
* **goWithHalt** (9)<br>
* **caution** (10)<br>
* **reserved1** (11)<br>
**Categories:** Infrastructure information
**Revision:** _V1.3.1_
>>>
NOTE: When used by data frames, the AllowedManeuvers data concept is used in two places: optionally in the
generic lane structure to list all possible maneuvers (as in what that lane can do at its stop line point); and within each
ConnectsTo structure. Each ConnectsTo structure contains a list used to provide a single valid maneuver in the context of
one lane connecting to another in the context of a signal phase that applies to that maneuver. It should be noted that, in
some intersections, multiple outbound lanes can be reached by the same maneuver (for example two independent left
turns might be found in a 5-legged intersection) but that to reach any given lane from the stop line of another lane is
always a single maneuver item (hence the use of a list). Not all intersection descriptions may contain an exhaustive set of
ConnectsTo information (unsignalized intersections for example) and in such cases the AllowedManeuvers in the generic
lane structure can be used. If present in both places, the data expressed in the generic lane shall not conflict with the data
found in the collection of ConnectsTo entries.
>>>
```asn1
AllowedManeuvers ::= BIT STRING {
maneuverStraightAllowed (0),
maneuverLeftAllowed (1),
maneuverRightAllowed (2),
maneuverUTurnAllowed (3),
maneuverLeftTurnOnRedAllowed (4),
maneuverRightTurnOnRedAllowed (5),
maneuverLaneChangeAllowed (6),
maneuverNoStoppingAllowed (7),
yieldAllwaysRequired (8),
goWithHalt (9),
caution (10),
reserved1 (11)
} (SIZE(12))
```
### <a name="Angle"></a>Angle
This DE is used to describe an angular measurement in units of degrees. This data
element is often used as a heading direction when in motion. In this use, the current heading of the sending device is
expressed in unsigned units of 0.0125 degrees from North, such that 28799 such degrees represent 359.9875 degrees.
North shall be defined as the axis defined by the WGS-84 coordinate system and its reference ellipsoid. Any angle "to the
east" is defined as the positive direction. A value of 28800 shall be used when Angle is unavailable.
**Unit:** _0.0125 degrees_
**Categories:** Infrastructure information
**Revision:** _V1.3.1_
>>>
NOTE: Note that other heading and angle data elements of various sizes and precisions are found in other parts of this standard and in ITS.
>>>
```asn1
Angle ::= INTEGER (0..28800)
```
### <a name="ApproachID"></a>ApproachID
This DE is used to relate the index of an approach, either ingress or egress within the
subject lane. In general, an approach index in the context of a timing movement is not of value in the MAP and SPAT
process because the lane ID and signal group ID concepts handle this with more precision. This value can also be useful
as an aid as it can be used to indicate the gross position of a moving object (vehicle) when its lane level accuracy is
unknown. This value can also be used when a deployment represents sets of lanes as groups without further details (as is
done in Japan).
**Categories:** Infrastructure information
**Revision:** _V1.3.1_
>>>
NOTE: zero to be used when valid value is unknown
>>>
```asn1
ApproachID ::= INTEGER (0..15)
```
### <a name="BasicVehicleRole"></a>BasicVehicleRole
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
This DE provides a means to indicate the current role that a DSRC device is playing
This is most commonly employed when a vehicle needs to take on another role in order to send certain DSRC message
types. As an example, when a public safety vehicle such as a police car wishes to send a signal request message (SRM)
to an intersection to request a preemption service, the vehicle takes on the role "police" from the below list in both the
SRM message itself and also in the type of security CERT which is sent (the SSP in the CERT it used to identify the
requester as being of type "police" and that they are allowed to send this message in this way). The BasicVehicleRole
entry is often used and combined with other information about the requester as well, such as details of why the request is
being made.
- 0 - `basicVehicle` - Light duty passenger vehicle type
- 1 - `publicTransport` - Used in EU for Transit us
- 2 - `specialTransport` - Used in EU (e.g. heavy load)
- 3 - `dangerousGoods` - Used in EU for any HAZMAT
- 4 - `roadWork` - Used in EU for State and Local DOT uses
- 5 - `roadRescue` - Used in EU and in the US to include tow trucks.
- 6 - `emergency` - Used in EU for Police, Fire and Ambulance units
- 7 - `safetyCar` - Used in EU for Escort vehicles
- 8 - `none-unknown` - added to follow current SAE style guidelines
- 9 - `truck` - Heavy trucks with additional BSM rights and obligations
- 10 - `motorcycle` - Motorcycle
- 11 - `roadSideSource` - For infrastructure generated calls such as fire house, rail infrastructure, roadwork site, etc.
- 12 - `police` - Police vehicle
- 13 - `fire` - Firebrigade
- 14 - `ambulance` - (does not include private para-transit etc.)
- 15 - `dot` - all roadwork vehicles
- 16 - `transit` - all transit vehicles
- 17 - `slowMoving` - to also include oversize etc.
- 18 - `stopNgo` - to include trash trucks, school buses and others
- 19 - `cyclist` - bicycles
- 20 - `pedestrian` - also includes those with mobility limitations
- 21 - `nonMotorized` - other, horse drawn, etc.
- 22 - `military` - military vehicles
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
Values:
* **basicVehicle** (0)<br>
* **publicTransport** (1)<br>
* **specialTransport** (2)<br>
* **dangerousGoods** (3)<br>
* **roadWork** (4)<br>
* **roadRescue** (5)<br>
* **emergency** (6)<br>
* **safetyCar** (7)<br>
* **none-unknown** (8)<br>
* **truck** (9)<br>
* **motorcycle** (10)<br>
* **roadSideSource** (11)<br>
* **police** (12)<br>
* **fire** (13)<br>
* **ambulance** (14)<br>
* **dot** (15)<br>
* **transit** (16)<br>
* **slowMoving** (17)<br>
* **stopNgo** (18)<br>
* **cyclist** (19)<br>
* **pedestrian** (20)<br>
* **nonMotorized** (21)<br>
* **military** (22)<br>
**Categories:** Infrastructure information
**Revision:** _V1.3.1_
>>>
NOTE: It should be observed that devices can at times change their roles (i.e. a fire operated by a volunteer
fireman can assume a fire role for a period of time when in service, or a pedestrian may assume a cyclist role when using
a bicycle). It should be observed that not all devices (or vehicles) can assume all roles, nor that a given
device in a given role will be provided with a security certificate (CERT) that has suitable SSP credentials to provide the
ability to send a particular message or message content. The ultimate responsibility to determine what role is to be used,
and what CERTs would be provided for that role (which in turn controls the messages and message content that can be
sent within SAE-defined PSIDs) rests with the regional deployment.
>>>
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
```asn1
BasicVehicleRole ::= ENUMERATED {
basicVehicle (0),
publicTransport (1),
specialTransport (2),
dangerousGoods (3),
roadWork (4),
roadRescue (5),
emergency (6),
safetyCar (7),
none-unknown (8),
truck (9),
motorcycle (10),
roadSideSource (11),
police (12),
fire (13),
ambulance (14),
dot (15),
transit (16),
slowMoving (17),
stopNgo (18),
cyclist (19),
pedestrian (20),
nonMotorized (21),
military (22),
}
```
### <a name="DDay"></a>DDay
The DSRC style day is a simple value consisting of integer values from zero to 31. The value of zero shall represent an unknown value.
**Unit:** _days_
**Categories:** Infrastructure information
**Revision:** _V1.3.1_
```asn1
DDay ::= INTEGER (0..31)
```
### <a name="DeltaAngle"></a>DeltaAngle
This DE provides the final angle used in the last point of the lane path. Used to "cant" the stop line of the lane.
With an angle range from negative 150 to positive 150 in one degree steps where zero is directly
along the axis or the lane center line as defined by the two closest points.
**Unit:** _degree_
**Categories:** Infrastructure information
**Revision:** _V1.3.1_
```asn1
DeltaAngle ::= INTEGER (-150..150)
```
### <a name="DeltaTime"></a>DeltaTime
This DE provides a time definition for an object's schedule adherence (typically a transit
vehicle) within a limited range of time. When the reporting object is ahead of schedule, a positive value is used; when
behind, a negative value is used. A value of zero indicates schedule adherence. This value is typically sent from a vehicle
to the traffic signal controller's RSU to indicate the urgency of a signal request in the context of being within schedule or
not. In another use case, the traffic signal controller may advise the transit vehicle to speed up (DeltaTime > 0) or to slow
down (DeltaTime < 0) to optimize the transit vehicle distribution driving along a specific route (e.g. a Bus route).
Supporting a range of +/- 20 minute in steps of 10 seconds:
- the value of `-121` shall be used when more than -20 minutes
- the value of `+120` shall be used when more than +20 minutes
- the value `-122` shall be used when the value is unavailable
**Categories:** Infrastructure information
**Revision:** _V1.3.1_
```asn1
DeltaTime ::= INTEGER (-122 .. 121)
```
### <a name="DescriptiveName"></a>DescriptiveName
This DE is used in maps and intersections to provide a human readable and
recognizable name for the feature that follows. It is typically used when debugging a data flow and not in production use.
One key exception to this general rule is to provide a human-readable string for disabled travelers in the case of
crosswalks and sidewalk lane objects.
**Categories:** Infrastructure information
**Revision:** _V1.3.1_
```asn1
DescriptiveName ::= IA5String (SIZE(1..63))
```
### <a name="DHour"></a>DHour
The DSRC hour consists of integer values from zero to 23 representing the hours within a day. The value of 31 shall
represent an unknown value. The range 24 to 30 is used in some transit applications to represent schedule adherence.
**Unit:** _hours_
**Categories:** Infrastructure information