 |
 |
 |
 |
|
 |
 |
SAE J2735-Draft-Rev28 [issued: 11-10-08]
-
42 -
This is an SAE Motor Vehicle Council draft document of the DSRC committee, subject to change.
-- User Data
vehicleVIN VehicleIdent OPTIONAL,
-- a set of unique strings to identify the requesting vehicle
vehicleData BSMblob,
-- current position data about the vehicle
status VehicleRequestStatus OPTIONAL,
-- current status data about the vehicle
...
}
XML Representation:
<xs:complexType name="SignalRequestMsg" >
<xs:sequence>
<xs:element name="msgID" type="DSRCmsgID" />
<xs:element name="msgCnt" type="MsgCount" />
<!-- Request Data -->
<xs:element name="request" type="SignalRequest" />
<!-- the specific request to the intersection
contains IntersectionID, cancel flags,
requested action, OPTIONAL lanes data -->
<xs:element name="timeOfService" type="DSignalSeconds" minOccurs="0"/>
<!-- the time in the near future when service is
requested to start -->
<xs:element name="endOfService" type="DSignalSeconds" minOccurs="0"/>
<!-- the time in the near future when service is
requested to end -->
<xs:element name="transitStatus" type="TransitStatus" minOccurs="0"/>
<!-- additional information pertaining
to transit events
User Data -->
<xs:element name="vehicleVIN" type="VehicleIdent" minOccurs="0"/>
<!-- a set of unique strings to identify the requesting vehicle -->
<xs:element name="vehicleData" type="BSMblob" />
<!-- current position data about the vehicle -->
<xs:element name="status" type="VehicleRequestStatus" minOccurs="0"/>
<!-- current status data about the vehicle -->
</xs:sequence>
</xs:complexType>
In addition, this item may be used by data structures in other ITS standards.
5.15 Data Frame: MSG_SignalStatusMessage
Use: The Signal Status Message is a message sent by a an RSU in a signalized intersection. It is used to
relate the current status of the signal and any collection of pending or active preemption or priority events
acknowledged by the controller. The data contained in this message allow other users to determine their
"ranking" for any request they have made as well as see the currently active events. When there have been
no recently received requests for service messages, this message may not be sent. The outcome of the all
pending requests to a signal can be found in the Signal Status Message, and the current event may also be
reflected in the SPAT message contents if successful.
ASN.1 Representation:
SignalStatusMessage ::= SEQUENCE {
msgID DSRCmsgID,
msgCnt MsgCount,
-- updated when message content changes
id IntersectionID,
-- this provides a unique mapping to the
-- intersection map in question
-- which provides complete location
-- and approach/move/lane data
-- as well as zones for priority/preemption