 |
 |
 |
 |
|
 |
 |
SAE J2735-Draft-Rev26 [issued: 09-18-08]
-
35 -
This is an SAE Motor Vehicle Council draft document of the DSRC committee, subject to change.
<!-- Applicable headings/directions -->
<xs:element name="term" >
<xs:complexType>
<xs:choice>
<xs:element name="termtime" type="TermTime" />
<!-- Terminate management process
based on Time-to-Live -->
<xs:element name="termDistance" type="TermDistance" />
<!-- Terminate management process
based on Distance-to-Live -->
</xs:choice>
</xs:complexType>
</xs:element>
<xs:element name="snapshot" >
<xs:complexType>
<xs:choice>
<xs:element name="snapshotTime" type="SnapshotTime" />
<!-- Collect snapshots based on time -->
<xs:element name="snapshotDistance" type="SnapshotDistance" />
<!-- Collect snapshots based on Distance -->
</xs:choice>
</xs:complexType>
</xs:element>
<xs:element name="txInterval" type="TxTime" />
<!-- Time Interval at which to send snapshots -->
<xs:element name="cntTthreshold" >
<xs:simpleType>
<xs:restriction base="xs:unsignedByte">
<xs:minInclusive value="1"/>
<xs:maxInclusive value="32"/>
</xs:restriction>
</xs:simpleType>
</xs:element>
<!-- number of thresholds that will be changed -->
<xs:element name="dataElements" >
<xs:complexType>
<xs:sequence minOccurs="1" maxOccurs="32">
<!-- rework above item to fit new needs new threshold (the object type
is now handled by the tagging) -->
</xs:sequence>
</xs:complexType>
</xs:element>
</xs:sequence>
</xs:complexType>
In addition, this item may be used by data structures in other ITS standards.
Remarks: Provided by VII POC-A team.
5.10 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
 |