 |
 |
 |
 |
|
 |
 |
SAE J2735-Draft-Rev29 [issued: 12-11-08]
-
32 -
This is an SAE Motor Vehicle Council draft document of the DSRC committee, subject to change.
<!-- a count of bytes to follow -->
</xs:sequence>
</xs:complexType>
5.7 Message: MSG_ProbeVehicleData
Use: The probe vehicle message frame is defined below. The probe vehicle message is used to exchange
status about a vehicle with other (typically RSU) DSRC readers to allow the collection of information
about typically vehicle traveling behaviors along a segment of road. The exchanges of this message as well
as the event which caused the collection of various elements defined in the messages are defined in Annex
B of this standard. In typical use the reporting vehicle has collected one or more snapshots which it will
send to a receiving RSU along with information (the vector) about the point in time and space when the
snapshot event occurred. Because any sequence of snapshots are related within a limit range of time and
space, some data compression may be used in the message to reduce redundant information.
ASN.1 Representation:
ProbeVehicleData ::= SEQUENCE {
msgID DSRCmsgID, -- App ID value, 1 byte
segNum ProbeSegmentNumber OPTIONAL,
-- a short term Ident value
-- not used when ident is used
probeID VehicleIdent OPTIONAL,
-- ident data for selected
-- types of vehicles
-- Roy: above two items could be in a CHIOCE statement?
startVector FullPositionVector, -- the space and time of
-- transmission to the RSU
vehicleType VehicleType, -- type of vehicle, 1 byte
cntSnapshoots INTEGER (1..32) OPTIONAL,
-- a count of how many snaphots
-- type entires will follow
snapshots SEQUENCE (SIZE(1..32)) OF Snapshot,
-- a seq of name-value pairs
-- along with the space and time
-- of the first measurement set
... -- # LOCAL_CONTENT
} -- Est size about 64 bytes plus snapshot sizes (about 12 per)
XML Representation:
<xs:element name="probeVehicleData" type="ProbeVehicleData"/>
<xs:complexType name="ProbeVehicleData" >
<xs:annotation>
<xs:documentation>
Est size about 64 bytes plus snapshot sizes (about 12 per)
</xs:documentation>
</xs:annotation>
<xs:sequence>
<xs:element name="msgID" type="DSRCmsgID" />
<!-- App ID value, 1 byte -->
<xs:element name="segNum" type="ProbeSegmentNumber" minOccurs="0"/>
<!-- a short term Ident value
not used when ident is used -->
<xs:element name="probeID" type="VehicleIdent" minOccurs="0"/>
<!-- ident data for selected
types of vehicles
Roy: above two items could be in a CHIOCE statement? -->
<xs:element name="startVector" type="FullPositionVector" />
<!-- the space and time of
transmission to the RSU -->
<xs:element name="vehicleType" type="VehicleType" />
<!-- type of vehicle, 1 byte -->
<xs:element name="cntSnapshoots" minOccurs="0">
<xs:simpleType>
<xs:restriction base="xs:unsignedByte">
<xs:minInclusive value="1"/>