 |
 |
 |
 |
|
 |
 |
SAE J2735-Draft-Rev26 [issued: 09-18-08]
-
84 -
This is an SAE Motor Vehicle Council draft document of the DSRC committee, subject to change.
allow the vehicle owner to obtain parameters
from the vehicle [Need more info to fill this out]
do we really want "private data" in the probe msg? -->
<xs:element name="vehicleType" type="VehicleType" minOccurs="0"/>
<xs:element name="vehicleClass" minOccurs="0">
<xs:complexType>
<xs:choice>
<xs:element name="vGroup" type="itis:VehicleGroupAffected" />
<xs:element name="rGroup" type="itis:ResponderGroupAffected" />
<xs:element name="rEquip" type="itis:IncidentResponseEquipment" />
</xs:choice>
</xs:complexType>
</xs:element>
<xs:element name="localVehicleIdent" type="local:VehicleIdent" minOccurs="0"/>
</xs:sequence>
</xs:complexType>
Used By: This entry is directly used by the following 2 other data structures in this standard (record type,
descriptive name, ASN.1, and XML name (if present) of each):
DF
MSG
In addition, this item may be used by data structures in other ITS standards.
Remarks: Issue: Should we make the signal request message use this frame to identify the requester
(today it uses the VIN only) ?
6.52 Data Frame: DF_VehicleMotionTrail
Use: The VehicleMotionTrail data frame defines an adaptable set of bread crumbs reflecting recent vehicle
movement over some period of time. This data frame allows creating a sequence of positions (typically a
vehicle motion track) over a limited period of time. The current vehicle position is subtracted from each
breadcrumb to create the previous position in the set. This position is then used to created the next bread
crumb. In other words, the breadcrumbs proceed backwards to create previous positions in a track the
vehicle has traveled. When the data frame is sent in the Part II section of the Basic Safety Message, the
vehicle's current position is used (and the optional position elements shown in the below need not be sent).
The breadcrumb data itself allow many options variants of data to be encoded Each possible set of
breadcrumb data elements is supported in a an octet blob style, and the sets of data in that type are sent in a
single final octet blob (in other words each octet is made up of N or more sets of inner data, using the same
encoding).
The lat-long offset units used in the breadcrumb stream support units of 1/8th micro degrees of lat and long.
The vertical offset units are in 20cm units. The time is expressed in units of 0.1 milliseconds. The
GPSstatus uses 4 bytes the relate the GDOP of the system. The heading and speed follow similar units to
their data element counterparts. All of these items are defined further in the relevant data entry.
ASN.1 Representation:
VehicleMotionTrail ::= SEQUENCE {
initialPosition FullPositionVector OPTIONAL,
currGPSstatus GPSstatus OPTIONAL,
posAccuracy PositionalAccuracy OPTIONAL,
-- below CHOICE could be removed (save 2 byes)
crumbData CHOICE {
-- select one of the possible data sets to be used
verboseDataSet SEQUENCE (SIZE(1..32)) OF
-- a set of all data elements, it is
-- non-uniform in size, each item tagged in BER
 |