 |
 |
 |
 |
|
 |
 |
SAE J2735-Draft-Rev18 [issued: 06-26-07]
-
49 -
This is an SAE Motor Vehicle Council draft document of the DSRC committee, subject to change.
XML Representation:
<xs:complexType name="LinkObject" >
<xs:sequence>
<xs:element name="refPoint" type="ReferencePoint" minOccurs="0"/>
<!-- OPTIONAL reference from which subsequent
data points in this link are offset
Keep? id IntersectionID,
a gloablly unique value, -->
<xs:element name="config" type="NodeConfig" minOccurs="0"/>
<!-- data about the treamentof values
which follow in the Approach -->
<xs:element name="approaches" minOccurs="0">
<xs:complexType>
<xs:sequence minOccurs="0" maxOccurs="32">
<xs:element name="approache" type="Approach" />
<!-- list of Approaches and thier lanes -->
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="egresses" minOccurs="0">
<xs:complexType>
<xs:sequence minOccurs="0" maxOccurs="32">
<xs:element name="egresse" type="Approach" />
<!-- list of Egresses and thier lanes add other attrubute items here?
item1 MyType3 OPTIONAL , item2 MyType3 OPTIONAL , item3 MyType3 OPTIONAL ,
-->
</xs:sequence>
</xs:complexType>
</xs:element>
</xs:sequence>
</xs:complexType>
Used by: This entry is used directly by one other data structure in this standard, a DF called
DF_Intersection <ASN> <XML>. In addition, this item may be used by data structures in other ITS
standards.
Remarks: Note that the offset data found in the underlying data structures will use the values found in the
last ReferencePoint and the last NodeConfig as the basis to which the offset are added values. Normally
this will be found in the enclosing object (typically an intersection type) but it may be reestablished here if
needed (this is intended for use in the case of huge intersections which may exceed the offset ranges). If
present, it applies to the scope of this link object, and not to any subsequent link objects which may be
found in the same message. Similar logic is applied to the Node Configuration element, if present.
6.18 Data Frame: DF_MovementState
Use: The MovementState data frame is used to convey all information about the current and next state of a
single lane or common set of lanes in an approach in a signalized intersection. It is used in the SPAT
message to convey every movement in the approaches in a given intersections so that vehicles, when
combined with certain map information, can determine the state of the signal lights.
ASN.1 Representation:
MovementState ::= SEQUENCE {
id MovementNumber,
id ApproachNumber, -- may not be needed?
laneNumber LaneNumber,
name DescriptiveName OPTIONAL,
-- uniquely defines approach/lane
approachType ApproachType, -- need to define
signalState SignalState,
timeToChange INTEGER (0..60000), -- refine type
vehicleCount INTEGER (0..60000), -- take from TMDD
pedState PedestrianSignalState OPTIONAL,
pedCountDown INTEGER (0..60000) OPTIONAL, -- refine type
pedDetect PedestrianDetect OPTIONAL,
pedDetectSec INTEGER (0..60000) OPTIONAL, -- take from T