 |
 |
 |
 |
|
 |
 |
SAE J2735-Draft-Rev26 [issued: 09-18-08]
-
88 -
This is an SAE Motor Vehicle Council draft document of the DSRC committee, subject to change.
}
XML Representation:
<xs:complexType name="VehicleReferenceLane" >
<xs:sequence>
<xs:element name="laneNumber" type="LaneNumber" />
<xs:element name="laneWidth" type="LaneWidth" minOccurs="0"/>
<xs:element name="laneAttributes" type="VehicleLaneAttributes" />
<xs:element name="nodeList" type="NodeList" />
<!-- path details of the lane and width -->
<xs:element name="keepOutList" type="NodeList" minOccurs="0"/>
<!-- no stop points along the path -->
</xs:sequence>
</xs:complexType>
Used By: This entry is used directly by one other data structure in this standard, a DF called
DF_Approach <ASN> <XML>. In addition, this item may be used by data structures in other ITS
standards.
6.54 Data Frame: DF_VehicleSize
Use: The VehicleSize is a data frame representing the vehicle length and vehicle width in a three byte
value.
ASN.1 Representation:
VehicleSize ::= SEQUENCE {
width VehicleWidth,
length VehicleLength
} -- 3 bytes in length
XML Representation:
<xs:complexType name="VehicleSize" >
<xs:annotation>
<xs:documentation>
3 bytes in length
</xs:documentation>
</xs:annotation>
<xs:sequence>
<xs:element name="width" type="VehicleWidth" />
<xs:element name="length" type="VehicleLength" />
</xs:sequence>
</xs:complexType>
Used By: This entry is used directly by one other data structure in this standard, a MSG called
MSG_BasicSafetyMessage_Verbose <ASN> <XML>. In addition, this item may be used by data
structures in other ITS standards.
Remarks: Note that besides the width and length which are always present in the BSM Part I, other values
data can also be sent in Part II including mass and bumper heights.
6.55 Data Frame: DF_VehicleStatus
Use: A data frame that is used to relate specific items of the vehicles status. This structure relates all the
different types of information that can be related about the vehicle inside a probe message of in a BSM part
II section. Typically these are used in data event snapshots which are gathered and periodically reported to
an RSU or as part of the BSM Part II content.
Observe that this data structure makes use of other defined data elements and data frames, enclosing them
in a sequence structure so that a number of such items can be sent within the VehicleStatus instance but that
this data follows the definition of each defined elsewhere.
ASN.1 Representation:
VehicleStatus ::= SEQUENCE {
-- data which follows must still fit within any message size limits
 |