 |
 |
 |
 |
|
 |
 |
SAE J2735-Draft-Rev29 [issued: 12-11-08]
-
60 -
This is an SAE Motor Vehicle Council draft document of the DSRC committee, subject to change.
combined with certain map information, can determine the state of the signal lights.
ASN.1 Representation:
MovementState ::= SEQUENCE {
-- The MovementNumber is contained in the enclosing DF.
movementName DescriptiveName OPTIONAL,
-- uniquely defines movement by nzame
laneCnt INTEGER (1..255) OPTIONAL,
-- the number of lanes to follow
laneSet LaneSet,
-- 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:
currState SignalLightState OPTIONAL,
-- the state of a Motorised lane
pedState PedestrianSignalState OPTIONAL,
-- the state of a Pedestrian type lane
specialState SpecialSignalState OPTIONAL,
-- the state of a special type lane
-- such as a deadicatd train lane
timeToChange 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.
-- Yellow phase time intervals
-- (used for motorised vehicle lanes and pedestrian lanes)
-- For the yellow Signal State, you may CHOICE one of the below:
yellState SignalLightState OPTIONAL,
-- the next state of a
-- Motorised lane
yellPedState PedestrianSignalState OPTIONAL,
-- the next state of a
-- Pedestrian type lane
yellTimeToChange TimeToChange OPTIONAL,
yellStateConfidence StateConfidence OPTIONAL,
-- below items are all optinal based on use and context
-- some are used only for ped lans
vehicleCount INTEGER (0..60000) OPTIONAL,
pedDetect PedestrianDetect OPTIONAL,
-- true if ANY ped are detected crossing
-- the above lanes
pedCount INTEGER (0..60000) OPTIONAL,
-- est count of peds
... -- # LOCAL_CONTENT
}
XML Representation:
<xs:complexType name="MovementState" >
<xs:sequence>
<!-- The MovementNumber is contained in the enclosing DF. -->
<xs:element name="movementName" type="DescriptiveName" minOccurs="0"/>
<!-- uniquely defines movement by nzame -->
<xs:element name="laneCnt" minOccurs="0">
<xs:simpleType>
<xs:restriction base="xs:unsignedByte">
<xs:minInclusive value="1"/>
</xs:restriction>
</xs:simpleType>
</xs:element>
<!-- the number of lanes to follow -->
<xs:element name="laneSet" type="LaneSet" />