 |
 |
 |
 |
|
 |
 |
SAE J2735-Draft-Rev29 [issued: 12-11-08]
-
170 -
This is an SAE Motor Vehicle Council draft document of the DSRC committee, subject to change.
-- request for a cabinet flash prempt,
-- while the value of 0 is reserved.
-- lower nibble: Strategy #:
-- Range is 0..15 and is used to specify a desired
-- strategy (if available).
-- Currently no strategies are defined and this
-- should be zero.
XML Representation:
<xs:complexType name="SignalReqScheme" >
<xs:simpleContent>
<xs:annotation>
<xs:documentation>
Encoded as follows:
upper nibble: Preempt #:
Bit 7 (MSB) 1 = Preempt and 0 = Priority
Remaining 3 bits:
Range of 0..7. The values of 1..6 represent
the respective controller preempt or Priority
to be activated. The value of 7 represents a
request for a cabinet flash prempt,
while the value of 0 is reserved.
lower nibble: Strategy #:
Range is 0..15 and is used to specify a desired
strategy (if available) .
Currently no strategies are defined and this
should be zero.
</xs:documentation>
</xs:annotation>
<xs:extension base="SignalReqScheme-string" >
<xs:attribute name="EncodingType" use="required">
<xs:simpleType>
<xs:restriction base="xs:NMTOKEN">
<xs:enumeration value="base64Binary"/>
</xs:restriction>
</xs:simpleType>
</xs:attribute>
</xs:extension>
</xs:simpleContent>
</xs:complexType>
<xs:simpleType name="SignalReqScheme-string">
<xs:restriction base="xs:base64Binary">
<xs:length value="2"/>
</xs:restriction>
</xs:simpleType >
Used By: This entry is directly used by the following 2 other data structures in this standard (record type,
descriptive name, ASN.1, and XML name (if present) of each):
DF
<XML>, and
DF
In addition, this item may be used by data structures in other ITS standards.
Remarks: In use, the the vehicle must determine which preempt number or priority number to request by
analyzing its location relative to the map layer information.
Note: if we get rid of having two complete request messages in favor of only one; we could use the MSB
bit here to differentiate between priority and preemption use cases.
7.112 Data Element: DE_SignalState
Use: The SignalState data element is used to reflect the current general state of the signal system in
question. This is how preemption and priority states are acknowledged, and in this case a single signal
system (and intersection) may have multiple states to relate. This data element is typically used as part of