 |
 |
 |
 |
|
 |
 |
SAE J2735-Draft-Rev15 [issued: 01-30-07]
-
30 -
This is an SAE Motor Vehicle Council draft document of the DSRC committee, subject to change.
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="localProbeVehicleData" type="local:ProbeVehicleData"
minOccurs="0"/>
</xs:sequence>
</xs:complexType>
Remarks: At the time of writing additional probe vehicle messages are being developed that will allow control over what
information is gathered and reported in a probe vehicle message. Builders are urged to consider these messages in
their development of products using this message.
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 {
-- the specific edition of the standard
-- that is being sent
-- the message and sub-message type, as
-- defined in the RTCM revision being used
-- NOTE as the message type is also in the payload,
-- we may want to remove it from here, not sure right now. DCK
wdCount INTEGER (0..1023),
-- a count of bytes to follow
...
XML Representation:
<xs:complexType name="RTCM-Corrections" >
<xs:sequence>
<!-- the specific edition of the standard
that is being sent -->
<xs:element name="msg" type="RTCM-MsgType" />
<!-- the message and sub-message type, as
defined in the RTCM revision being used
NOTE as the message type is also in the payload,
we may want to remove it from here, not sure right now. DCK -->
<xs:element name="wdCount" >
<xs:simpleType>
<xs:restriction base="xs:unsignedShort">
<xs:maxInclusive value="1023"/>
</xs:restriction>
</xs:simpleType>
</xs:element>
<!-- a count of bytes to follow -->
<xs:element name="payload" type="RTCM-Payload" />
</xs:sequence>
</xs:complexType>
Remarks: Observe that the transport layer details (preamble, CRC, etc.) as outlined in RTCM standard 10403.1
version 3.0 clause four are not sent in this message. In a similar fashion, the same framing information found in
clause 4.2 of the RTCM standard 10402.3 (version 2.3) is not sent. These would be reconstituted after reception