 |
 |
 |
 |
|
 |
 |
SAE J2735-Draft-Rev18 [issued: 06-26-07]
-
36 -
This is an SAE Motor Vehicle Council draft document of the DSRC committee, subject to change.
</xs:sequence>
</xs:complexType>
Remarks: Observe that the transport layer details (preamble, CRC, etc.) as outlined in RTCM standard
10403.1 version 3.0 clause four are not sent in this message. In a similar fashion, the same framing
information found in clause 4.2 of the RTCM standard 10402.3 (version 2.3) is not sent. These would be
reconstituted after reception by a mobile device and before sending the resultant message to any positioning
device expecting messages in such a format, as outlined in the RTCM recommendations found in clause
four of each document. Also observe that the specific bit ordering of the transport message level used in the
final message varies between RTCM version 3.x and that of version 2.3.
5.11 Message: MSG_SPAT (SIGNAL PHASE AND TIMING MESSAGE)
Use: The Signal Phase and Timing (SPAT) message is used to convey the current status of a signalized
intersection. Along with the _working term_ MSG_MapFragment data frame (which conveys a full
geometric layout of the intersection) the receiver of this message can determine the state of the signal
phasing and the expected next phase to occur.
ASN.1 Representation:
SPAT ::= SEQUENCE {
msgID DSRCmsgID,
name DescriptiveName OPTIONAL,
-- some type of std header to go here, TBD
-- add seq here to allow sets of Intersections?
id IntersectionID,
-- this provided a uniq mapping to the
-- intersection map in question
-- which provides complete location
-- and appoach/lane data
-- a control ID may be needed to map back to sig control
-- a 'map node' is pob no needed
appchCnt INTEGER(1..255), -- the number of approaches
-- there will be at least this
-- many "lane states" that follow
lanesCnt INTEGER(1..255), -- hate this name !
states SEQUENCE (SIZE(1..255))OF
-- each Movement/lane is given in turn
-- and contains its state, and seconds
-- to the next event etc.
premept PreemptionState,
-- all posible pre-emption states and
-- other intersecton wide data is found
-- here
... -- # LOCAL_CONTENT
XML Representation:
<xs:element name="sPAT" type="SPAT"/>
<xs:complexType name="SPAT" >
<xs:sequence>
<xs:element name="msgID" type="DSRCmsgID" />
<xs:element name="name" type="DescriptiveName" minOccurs="0"/>
<!-- some type of std header to go here, TBD
add seq here to allow sets of Intersections? -->
<xs:element name="id" type="IntersectionID" />
<!-- this provided a uniq mapping to the
intersection map in question
which provides complete location
and appoach/lane data
a control ID may be needed to map back to sig control