 |
 |
 |
 |
|
 |
 |
SAE J2735-Draft-Rev18 [issued: 06-26-07]
-
35 -
This is an SAE Motor Vehicle Council draft document of the DSRC committee, subject to change.
<!-- a count of how many snaphots
type entires will follow -->
<xs:element name="snapshots" >
<xs:complexType>
<xs:sequence minOccurs="1" maxOccurs="32">
<xs:element name="snapshot" type="Snapshot" />
<!-- a seq of name-value pairs along with the space and time of the
first measurement set -->
</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.10 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:element name="rTCM-Corrections" type="RTCM-Corrections"/>
<xs:complexType name="RTCM-Corrections" >
<xs: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 -->
<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 -->