 |
 |
 |
 |
|
 |
 |
SAE J2735-Draft-Rev29 [issued: 12-11-08]
-
61 -
This is an SAE Motor Vehicle Council draft document of the DSRC committee, subject to change.
<!-- each encoded as a: LaneNumber,
the collection of lanes, by num,
to which this state data applies
For the current movement State, you may CHOICE one of the below: -->
<xs:element name="currState" type="SignalLightState" minOccurs="0"/>
<!-- the state of a Motorised lane -->
<xs:element name="pedState" type="PedestrianSignalState" minOccurs="0"/>
<!-- the state of a Pedestrian type lane -->
<xs:element name="specialState" type="SpecialSignalState" minOccurs="0"/>
<!-- the state of a special type lane
such as a deadicatd train lane -->
<xs:element name="timeToChange" type="TimeToChange" />
<!-- Roy suggests abs. time here to avoid latency issues
and not using a time-to-live value,
we could put out one UTC time, then offset from it?
Damlr still wants count-down timers, so kept as is
untill this is settled for good. -->
<xs:element name="stateConfidence" type="StateConfidence" minOccurs="0"/>
<!-- Yellow phase time intervals
(used for motorised vehicle lanes and pedestrian lanes)
For the yellow Signal State, you may CHOICE one of the below: -->
<xs:element name="yellState" type="SignalLightState" minOccurs="0"/>
<!-- the next state of a
Motorised lane -->
<xs:element name="yellPedState" type="PedestrianSignalState" minOccurs="0"/>
<!-- the next state of a
Pedestrian type lane -->
<xs:element name="yellTimeToChange" type="TimeToChange" minOccurs="0"/>
<xs:element name="yellStateConfidence" type="StateConfidence" minOccurs="0"/>
<!-- below items are all optinal based on use and context
some are used only for ped lans -->
<xs:element name="vehicleCount" minOccurs="0">
<xs:simpleType>
<xs:restriction base="xs:unsignedShort">
<xs:maxInclusive value="60000"/>
</xs:restriction>
</xs:simpleType>
</xs:element>
<xs:element name="pedDetect" type="PedestrianDetect" minOccurs="0"/>
<!-- true if ANY ped are detected crossing
the above lanes -->
<xs:element name="pedCount" minOccurs="0">
<xs:simpleType>
<xs:restriction base="xs:unsignedShort">
<xs:maxInclusive value="60000"/>
</xs:restriction>
</xs:simpleType>
</xs:element>
<!-- est count of peds -->
<xs:element name="localMovementState" type="local:MovementState" minOccurs="0"/>
</xs:sequence>
</xs:complexType>
In addition, this item may be used by data structures in other ITS standards.
Remarks: Note that the value given for the time to change will vary in many actuated signalized
intersection based on the sensor data received during the phase. The data transmitted always reflects the
then most current time value. Therefore, as an example, in a phase which may vary from 15 to 25 seconds
of duration based on observed traffic flows, a time to change value of 15 seconds might be transmitted for
many seconds on end (as many as 10 seconds) followed by decreasing values as the time runs out. During
this entire period of time, the yellow time would also be sent. The time to change element can be regarded
as a guaranteed minimum value of the time that will be elapse unless a preemption event occurs.
6.28 Data Frame: DF_NodeList
Use: The NodeList data structure provides the sequence of signed offset values for determining the Xs