 |
 |
 |
 |
|
 |
 |
SAE J2735-Draft-Rev18 [issued: 06-26-07]
-
25 -
This is an SAE Motor Vehicle Council draft document of the DSRC committee, subject to change.
The combining of various data elements based on the demands of different active safety applications in the
vehicle is the job of the message dispatcher, who manages the selection of what is to be sent. The specific
encoding of those elements into the final transmitted message is defined by this structure. The message
dispatcher is an abstract architectural concept from the perspective of the message set standard. It should
be pointed out that the message dispatcher is expected to provide translation services from the received
messages into various ordering and forms required by the application which it supports. This is outside the
scope of this standard. Additional information on the use of message dispatcher in applications can be
found in Annex D.
Additional information on the use of this message in applications can be found in Annex A.
ASN.1 Representation:
BasicSafetyMessage ::= SEQUENCE {
-- Part I, sent at all times without any tagging
msgID DSRCmsgID, -- App ID value, 1 byte
secMark DSecond, -- 2 bytes
id TemporaryID, -- 6 bytes
-- pos PositionLocal3D,
lat Latitude, -- 4 bytes (1/8th micro degrees)
long Longitude, -- 4 bytes
elev Elevation, -- 3 bytes
-- motion Motion,
speed Speed, -- 2 bytes
heading Heading, -- 2 byte
accelSet AccelerationSet4Way, -- accel set (four way)
-- control Control,
brakes BrakeSystemStatus, -- 1 byte
steering SteeringWheelAngle, -- 2 bytes
throttle ThrottlePosition, -- 1 byte
lightSet ExteriorLights, -- 1 byte
-- basic VehicleBasic,
size VehicleSize, -- 3 bytes
-- Part II, send as required with short tags
valueCnt1 INTEGER (0..32), -- 1 byte
items1 SEQUENCE (SIZE(0..32)) OF SEQUENCE {
tag StdTagList, -- 1 byte
},
-- Part III, send as required with 2-byte tags
valueCnt2 INTEGER (0..32),
items2 SEQUENCE (SIZE(0..32)) OF SEQUENCE {
tag TwoByteTagList,
data CHOICE {
payload Payload,
value ValueList
}
},
... -- # LOCAL_CONTENT
XML Representation:
<xs:element name="basicSafetyMessage" type="BasicSafetyMessage"/>
<xs:complexType name="BasicSafetyMessage" >
<xs:sequence>
<!-- Part I, sent at all times without any tagging -->
<xs:element name="msgID" type="DSRCmsgID" />
<!-- App ID value, 1 byte -->
<xs:element name="secMark" type="DSecond" />
<!-- 2 bytes -->
<xs:element name="id" type="TemporaryID" />
<!-- 6 bytes