 |
 |
 |
 |
|
 |
 |
SAE J2735-Draft-Rev26 [issued: 09-18-08]
-
38 -
This is an SAE Motor Vehicle Council draft document of the DSRC committee, subject to change.
status VehicleRequestStatus,
-- current status data about the vehicle
timeOfService DSignalSeconds,
-- the time in the near future when service is
-- requested to start
endOfService DSignalSeconds,
-- the time in the near future when service is
-- requested to end
...
}
XML Representation:
<xs:complexType name="SignalPriorityRequest" >
<xs:sequence>
<xs:element name="request" type="SignalRequest" />
<!-- the specific request to the intersection -->
<xs:element name="vehicleVIN" type="VINstring" />
<!-- a unique string to identify the requesting vehicle -->
<xs:element name="vehicleData" type="BSMblob" />
<!-- current position data about the vehicle -->
<xs:element name="status" type="VehicleRequestStatus" />
<!-- current status data about the vehicle -->
<xs:element name="timeOfService" type="DSignalSeconds" />
<!-- the time in the near future when service is
requested to start -->
<xs:element name="endOfService" type="DSignalSeconds" />
<!-- the time in the near future when service is
requested to end -->
</xs:sequence>
</xs:complexType>
In addition, this item may be used by data structures in other ITS standards.
5.13 Message: MSG_RTCM_Corrections (Revise this as per VSC)
Use: The RTCM_Corrections message is used to encapsulate RCTM differential corrections for GPS and
other radio navigation signals as defined by the RTCM (Radio Technical Commission For Maritime
Services) special committee number 104 in its various standards. Here, in the work of DSRC, these
messages are "wrapped" for transport on the DSRC media, and then can be re-constructed back into the
final expected formats defined by the RCTM standard and used directly by various positioning systems to
increase the absolute and relative accuracy estimates produced.
ASN.1 Representation:
RTCM-Corrections ::= SEQUENCE {
-- the specific edition of the standard
-- that is being sent
-- the message and sub-message type, as
-- defined in the RTCM revision being used
-- NOTE as the message type is also in the payload,
-- we may want to remove it from here, not sure right now. DCK
wdCount INTEGER (0..1023),
-- a count of bytes to follow
...
}
XML Representation:
<xs:element name="rTCM-Corrections" type="RTCM-Corrections"/>
<xs:complexType name="RTCM-Corrections" >
<xs:sequence>
<!-- the specific edition of the standard
that is being sent -->
 |