 |
 |
 |
 |
|
 |
 |
SAE J2735-Draft-Rev18 [issued: 06-26-07]
-
40 -
This is an SAE Motor Vehicle Council draft document of the DSRC committee, subject to change.
6.4 Data Frame: DF_Approach
Use: The Approach data structure is used to bundle reference lanes and and computed lanes together with a
The Approach data structure is used to bundle reference lanes and and computed lanes together with a
Approach data structure is used to bundle reference lanes and and computed lanes together with a
roach data structure is used to bundle reference lanes and and computed lanes together with a
ch data structure is used to bundle reference lanes and and computed lanes together with a
data structure is used to bundle reference lanes and and computed lanes together with a
structure is used to bundle reference lanes and and computed lanes together with a
ructure is used to bundle reference lanes and and computed lanes together with a
cture is used to bundle reference lanes and and computed lanes together with a
re is used to bundle reference lanes and and computed lanes together with a
is used to bundle reference lanes and and computed lanes together with a
used to bundle reference lanes and and computed lanes together with a
to bundle reference lanes and and computed lanes together with a
bundle reference lanes and and computed lanes together with a
reference lanes and and computed lanes together with a
reference lanes and and computed lanes together with a
rence lanes and and computed lanes together with a
ce lanes and and computed lanes together with a
lanes and and computed lanes together with a
and and computed lanes together with a
and computed lanes together with a
computed lanes together with a
computed lanes together with a
lanes together with a
together with a
r with a
with a
a
unique ID within the intersections for an Approach or Egress description which is part of an intersection.
unique ID within the intersections for an Approach or Egress description which is part of an intersection.
ID within the intersections for an Approach or Egress description which is part of an intersection.
within the intersections for an Approach or Egress description which is part of an intersection.
the intersections for an Approach or Egress description which is part of an intersection.
intersections for an Approach or Egress description which is part of an intersection.
rsections for an Approach or Egress description which is part of an intersection.
ctions for an Approach or Egress description which is part of an intersection.
for an Approach or Egress description which is part of an intersection.
r an Approach or Egress description which is part of an intersection.
an Approach or Egress description which is part of an intersection.
Approach or Egress description which is part of an intersection.
roach or Egress description which is part of an intersection.
ch or Egress description which is part of an intersection.
or Egress description which is part of an intersection.
r Egress description which is part of an intersection.
Egress description which is part of an intersection.
ress description which is part of an intersection.
description which is part of an intersection.
cription which is part of an intersection.
ription which is part of an intersection.
which is part of an intersection.
ch is part of an intersection.
is part of an intersection.
part of an intersection.
rt of an intersection.
of an intersection.
an intersection.
intersection.
rsection.
ction.
ASN.1 Representation:
Approach ::= SEQUENCE {
name DescriptiveName OPTIONAL,
id ApproachNumber, -- could this be OPTIONAL,
-- could it be infered from the
-- order it is sent in?
-- is it large enough?
refLane SEQUENCE (SIZE(1..32)) OF
computedLane SEQUENCE (SIZE(0..32)) OF
ComputedLane OPTIONAL,
...
}
XML Representation:
<xs:complexType name="Approach" >
<xs:sequence>
<xs:element name="name" type="DescriptiveName" minOccurs="0"/>
<xs:element name="id" type="ApproachNumber" />
<!-- could this be OPTIONAL ,
could it be infered from the
order it is sent in?
is it large enough? -->
<xs:element name="refLane" >
<xs:complexType>
<xs:sequence minOccurs="1" maxOccurs="32">
<xs:element name="refLane-item" type="ReferenceLane" />
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="computedLane" minOccurs="0">
<xs:complexType>
<xs:sequence minOccurs="0" maxOccurs="32">
<xs:element name="computedLane-item" type="ComputedLane" />
</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_LinkObject <ASN> <XML>. In addition, this item may be used by data structures in other ITS
standards.
6.5 Data Frame: DF_BrakeSystemStatus
Use: A single byte long data frame combining multiple related bit fields into one byte.
ASN.1 Representation:
BrakeSystemStatus ::= SEQUENCE {
wheelBrakes BrakeAppliedStatus,
-- 4 bits
traction TractionControlState,
-- 2 bits
-- 2 bits
}
XML Representation:
<xs:complexType name="BrakeSystemStatus" >
<xs:sequence>
<xs:element name="wheelBrakes" type="BrakeAppliedStatus" />