Navigation bar
  Print document Start Previous page
 36 of 303 
Next page End  

SAE J2735-Draft-Rev29 [issued: 12-11-08] 
-
36 -
This is an SAE Motor Vehicle Council draft document of the DSRC committee, subject to change.
         <!-- the specific edition of the standard
         that is being sent -->
         <xs:element name="rtcmID" type="RTCM-ID" />
         <!-- the message and sub-message type,  as
         defined in the RTCM revision being used -->
         <xs:element name="status" type="GPSstatus" />
         <xs:element name="payload" type="RTCM-Payload" />
      </xs:sequence>
</xs:complexType>
In addition, this item may be used by data structures in other ITS standards.
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.10 Message: MSG_TravelerInformation
Use: The Traveler Information message is used to send various types of messages (advisory and road sign
types) over the WSM stack to vehicles.  It makes heavy use of the ITIS encoding system to send well
known phrases, but allows limited text for local place names. The supported message types specify several
sub-dialects of ITIS phrase patterns to further reduce the number of bytes to be sent.  The expressed
messages are active at a precise start and duration period, which can be specified to a resolution of a
minute.  The affected local area can be expressed using either a radius system or a system of short defined
regions which is similar to the way roadway geometry is defined in the map fragment messages.   
ASN.1 Representation:
TravelerInformation ::= SEQUENCE {
   msgID           DSRCmsgID
   packetID        UniqueMSGID    OPTIONAL,    
   urlB            URL-Base       OPTIONAL,  
   dataFrameCount  INTEGER(1..32) OPTIONAL, 
   
   dataFrames SEQUENCE (SIZE(1..8)) OF SEQUENCE {
   
      -- Part I, Frame header
      frameType   TravelerInfoType,  -- (enum, advisory or road sign)
      msgId       CHOICE  {
                     furtherInfoID   FurtherInfoID,
                                     -- links to ATIS msg
                     roadSignID      RoadSignID  
                                     -- to be defined as a DF
                     },
      startYear   DYear OPTIONAL, 
                  -- Current year used if missing
      startTime   MinuteOfTheYear,
      duratonTime MinutesDuration,
      priority    SignPrority,
  
      -- Part II, Applicable Regions of Use
      regions  SEQUENCE (SIZE(1..8)) OF ValidRegion,
   
      -- Part III, Content
      content  CHOICE  {
                 
advisory       ITIS.ITIScodesAndText,           
                                 -- typical ITIS warnings
                  workZone       WorkZone,       
                                 -- work zone signs and directions
                  genericSign    GenericSignage
                                 -- MUTCD signs and directions
                  speedLimit     SpeedLimit,