 |
 |
 |
 |
|
 |
 |
SAE J2735-Draft-Rev26 [issued: 09-18-08]
-
33 -
This is an SAE Motor Vehicle Council draft document of the DSRC committee, subject to change.
<xs:element name="msgID" type="DSRCmsgID" />
<xs:element name="msgCnt" type="MsgCount" />
<!-- updated when message content changes -->
<xs:element name="name" type="DescriptiveName" minOccurs="0"/>
<xs:element name="layerType" type="LayerType" minOccurs="0"/>
<xs:element name="layerID" type="LayerID" minOccurs="0"/>
<xs:element name="intersections" minOccurs="0">
<xs:complexType>
<xs:sequence minOccurs="1" maxOccurs="32">
<xs:element name="intersection" type="Intersection" />
</xs:sequence>
</xs:complexType>
</xs:element>
<!-- other objects may be added at this layer, tbd,
this might become a nested CHOICE statement
roadSegments SEQUENCE (SIZE (1..32) ) OF
RoadSegments OPTIONAL ,
curveSegments SEQUENCE (SIZE (1..32) ) OF
curveSegments OPTIONAL ,
wanted: some type of data frame describing how
the data was determined/processed to go here -->
<xs:element name="dataParameters" type="DataParameters" minOccurs="0"/>
<xs:element name="localMapData" type="local:MapData" minOccurs="0"/>
</xs:sequence>
</xs:complexType>
In addition, this item may be used by data structures in other ITS standards.
Remarks: Issues: Not clear how multiple intersections would really be used in this concept. It may be
that complex intersections must be broken down this way. It may be that sending sets of locally nearby
intersections (although each is independent may be the answer).
5.8 Message: MSG_NMEA_Corrections (Remove?)
Use: The NMEA_Corrections message is used to encapsulate NMEA 183 style differential corrections for
GPS radio navigation signals as defined by the NMEA (National Marine Electronics Association)
committee in its Protocol 0183 standard. 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 NMEA standard and used directly by GPS positioning systems to increase the absolute and relative
accuracy estimates produced.
ASN.1 Representation:
NMEA-Corrections ::= SEQUENCE {
-- the specific edition of the standard
-- that is being sent, normally 2.0
-- the message and sub-message type, as
-- defined in the 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="nMEA-Corrections" type="NMEA-Corrections"/>
<xs:complexType name="NMEA-Corrections" >
<xs:sequence>
<!-- the specific edition of the standard
that is being sent, normally 2.0 -->
<!-- the message and sub-message type, as
 |