 |
 |
 |
 |
|
 |
 |
SAE J2735-Draft-Rev18 [issued: 06-26-07]
-
48 -
This is an SAE Motor Vehicle Council draft document of the DSRC committee, subject to change.
<xs:element name="location" type="TireLocation" />
<xs:element name="pressure" type="TirePressure" />
<xs:element name="temp" type="TireTemp" />
<xs:element name="wheelSensorStatus" type="WheelSensorStatus" />
<xs:element name="wheelEndElectFault" type="WheelEndElectFault" />
<xs:element name="leakageRate" type="TireLeakageRate" />
<xs:element name="detection" type="TirePressureThresholdDetection" />
<xs:element name="axle" >
<xs:complexType>
<xs:sequence minOccurs="0" maxOccurs="16">
<xs:element name="axle-item" type="TEMP_XML_TYPE_VALUE" />
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="location" type="AxleLocation" />
<xs:element name="weight" type="AxleWeight" />
<xs:element name="cargoWeight" type="CargoWeight" />
<xs:element name="steeringAxleTemperature" type="SteeringAxleTemperature" />
<xs:element name="driveAxleLocation" type="DriveAxleLocation" />
<xs:element name="driveAxleLiftAirPressure" type="DriveAxleLiftAirPressure" />
<xs:element name="driveAxleTemperature" type="DriveAxleTemperature" />
<xs:element name="driveAxleLubePressure" type="DriveAxleLubePressure" />
<xs:element name="steeringAxleLubePressure" type="SteeringAxleLubePressure" />
</xs:sequence>
</xs:complexType>
In addition, this item may be used by data structures in other ITS standards.
6.17 Data Frame: DF_LinkObject
Use: The LinkObject data structure associates a set of approaches and egresses with each other in the
intersection. Observe that the data structure of each is the same. These approaches then define lanes with
properties, each with a unique index value within this link object. An approach number and a lane number,
taken as a set, represent a unique path of travel thought the link (which may be traversed by specific types
of travelers, vehicles, pedestrians etc. as a function of the signal timing and regulatory environment then
in place).
It (may) also contains additional information about the approach such as the road type classification and
any barriers which are present. (TBD issue right now). We might want to allow an optional name field
here as well ("southbound traffic" etc.).
ASN.1 Representation:
LinkObject ::= SEQUENCE {
refPoint ReferencePoint OPTIONAL,
-- optional reference from which subsequent
-- data points in this link are offset
-- Keep? id IntersectionID,
-- a gloablly unique value,
config NodeConfig OPTIONAL,
-- data about the treamentof values
-- which follow in the Approach
approaches SEQUENCE (SIZE(0..32)) OF
Approach OPTIONAL,
-- list of Approaches and thier lanes
egresses SEQUENCE (SIZE(0..32)) OF
Approach OPTIONAL,
-- list of Egresses and thier lanes
-- add other attrubute items here?
-- item1 MyType3 OPTIONAL,
-- item2 MyType3 OPTIONAL,
-- item3 MyType3 OPTIONAL,
...