![]() ![]() ![]() ![]() SAE J2735-Draft-Rev29 [issued: 12-11-08]
-
35 -
This is an SAE Motor Vehicle Council draft document of the DSRC committee, subject to change.
<!-- the urgency of this message, a relative
degree of merit compared with other
similar messages for this type (not other
message being sent by the device) , nor a
priority of display urgency
one byte in length -->
<xs:element name="heading" type="HeadingSlice" minOccurs="0"/>
<!-- Applicable headings/direction -->
<xs:element name="extent" type="Extent" minOccurs="0"/>
<!-- the spatial distance over which this
message applies and should be presented
to the driver
one byte in length -->
<xs:element name="positon" type="FullPositionVector" minOccurs="0"/>
<!-- a compact summary of the position,
heading, rate of speed, etc of the
event in question. Including stationary
and wide area events. -->
<xs:element name="furtherInfoID" type="FurtherInfoID" minOccurs="0"/>
<!-- a link to any other incident
information data that may be available
in the normal ATIS incident description
or other messages
1~2 bytes in length -->
<xs:element name="crc" type="MsgCRC" />
</xs:sequence>
</xs:complexType>
Used By: This entry is used directly by one other data structure in this standard, a MSG called
MSG_EmergencyVehicleAlert <ASN> <XML>. In addition, this item may be used by data structures
in other ITS standards.
Remarks: This message is also used a building blocm for other DSRC messages. When used in other
public safety messages, additional elements may be appended to form new message types.
5.9 Message: MSG_RTCM_Corrections
Use: The RTCM_Corrections message is used to encapsulate RCTM differential corrections for GPS and
other radio navigation signals as defined by the RTCM (Radio Technical Commission For Maritime
Services) special committee number 104 in its various standards. Here, in the work of DSRC, these
messages are "wrapped" for transport on the DSRC media, and then can be re-constructed back into the
final expected formats defined by the RCTM standard and used directly by various positioning systems to
increase the absolute and relative accuracy estimates produced.
ASN.1 Representation:
RTCM-Corrections ::= SEQUENCE {
msgID DSRCmsgID,
msgCnt MsgCount,
-- the specific edition of the standard
-- that is being sent
-- the message and sub-message type, as
-- defined in the RTCM revision being used
status GPSstatus,
...
}
XML Representation:
<xs:element name="rTCM-Corrections" type="RTCM-Corrections"/>
<xs:sequence>
<xs:element name="msgID" type="DSRCmsgID" />
<xs:element name="msgCnt" type="MsgCount" />
|