 |
 |
 |
 |
|
 |
 |
SAE J2735-Draft-Rev28 [issued: 11-10-08]
-
73 -
This is an SAE Motor Vehicle Council draft document of the DSRC committee, subject to change.
Remarks: In use, all subsequent offset value are added to this point in order to determine the absolute
position to be described. In some data structures more than once ReferencePoint may be present. Data
values are interpreted in a stream fashion. That is, until a new ReferencePoint is read, the value for the last
one is used as the basis for all offset values found the same structure.
6.34 Data Frame: DF_RoadSignID
Use: The RoadSignID data frame is used ro provide a precise location of one or more roadside signs.
ASN.1 Representation:
RoadSignID ::= SEQUENCE {
position Position3D,
-- Location of sign
viewAngle HeadingSlice,
-- Vehicle directinof travel while
-- facing active side of sign
mutcdCodee MUTCDCode,
-- Tag for MUTCD code or "generic sign"
crc INTEGER (0..65535) OPTIONAL
-- Used to provide a check sum
}
XML Representation:
<xs:complexType name="RoadSignID" >
<xs:sequence>
<xs:element name="position" type="Position3D" />
<!-- Location of sign -->
<xs:element name="viewAngle" type="HeadingSlice" />
<!-- Vehicle directinof travel while
facing active side of sign -->
<xs:element name="mutcdCodee" type="MUTCDCode" />
<!-- Tag for MUTCD code or "generic sign" -->
<xs:element name="crc" minOccurs="0">
<xs:simpleType>
<xs:restriction base="xs:unsignedShort"/>
</xs:simpleType>
</xs:element>
<!-- Used to provide a check sum -->
</xs:sequence>
</xs:complexType>
Used By: This entry is used directly by one other data structure in this standard, a DF called
MSG_TravelerInformation <ASN> <XML>. In addition, this item may be used by data structures in
other ITS standards.
6.35 Data Frame: DF_Sample
Use: Allows the Probe Management message to apply its settings to a random sample of vehicles (all
vehicles within the stated range). This uses the last single digit of the current probe segment number (PSN)
to determine if probe management is to be used. [Ed note: or do we use the temp-mac value because some
commercial fleet vehicles do not use the PSN at all] If the current PSN falls between these two (2) values,
then the Probe Data Management policy should be applied. The numbers are inclusive e.g. using 0x10 and
0x20 would provide a 1/16th sample and the values 0x00 and 0x80 would provide a 50% sample.
ASN.1 Representation:
Sample ::= SEQUENCE {
sampleStart INTEGER(0..255), -- Sample Starting Point
sampleEnd INTEGER(0..255) -- Sample Ending Point
}
XML Representation:
<xs:complexType name="Sample" >
<xs:sequence>
<xs:element name="sampleStart" >