 |
 |
 |
 |
|
 |
 |
SAE J2735-Draft-Rev18 [issued: 06-26-07]
-
100 -
This is an SAE Motor Vehicle Council draft document of the DSRC committee, subject to change.
DF
<XML>, and
DF
<XML>, and
MSG
<XML>, and
DF
In addition, this item may be used by data structures in other ITS standards.
7.54 Data Element: DE_MovementNumber
Use: The MovementNumber data concept coveys a unique index value for an movement (one or one or
more lanes with a common signal state) within an approach or an egress in an intersection. See also
Approach
ASN.1 Representation:
MovementNumber ::= INTEGER (0..255)
XML Representation:
<xs:simpleType name="MovementNumber" >
<xs:restriction base="xs:unsignedByte"/>
</xs:simpleType>
Used by: This entry is used directly by one other data structure in this standard, a DF called
DF_MovementState <ASN> <XML>. In addition, this item may be used by data structures in other
ITS standards.
7.55 Data Element: DE_MultiVehicleReponse
Use: A data element which is set if the vehicle transmitting believes that more than one vehicle (regardless
of the dispatch or command and control organization of those vehicles or their agency) are currently in-
route or involved in the response to the event. When received in a message by another vehicle OBU, this
data element indicates to other vehicles that addition response vehicles may be converging to the same
location and that addition caution is warranted.
Used to indicate that more that one vehicle is responding and traveling in a closely aligned fashion (one
after the other in a loose platoon formation). This DE is intended to be used with the DSRC public safety
vehicle operating in the area use case.
ASN.1 Representation:
MultiVehicleReponse ::= ENUMERATED {
notEquipped (0),
singleVehicle (1),
multiVehicle (2),
reserved (3) -- for future use
}
XML Representation:
<xs:simpleType name="MultiVehicleReponse" >
<xs:annotation>
<xs:appinfo>
notEquipped (0)
singleVehicle (1)
multiVehicle (2)
reserved (3) -- for future use
</xs:appinfo>
</xs:annotation>
<xs:union>
<xs:simpleType>
<xs:restriction base="xs:unsignedInt">
<xs:minInclusive value="0"/>
<xs:maxInclusive value="3"/>
</xs:restriction>