Navigation bar
  Print document Start Previous page
 25 of 177 
Next page End  

SAE J2735-Draft-Rev15 [issued: 01-30-07]
-
25 -
This is an SAE Motor Vehicle Council draft document of the DSRC committee, subject to change.
common ITIS phrase list to both describe the event and provide advice and recommendation for travelers.  The
Emergency Vehicle Alert message appends to the message some additional data elements regarding the overall
type of vehicle involved and other useful data.  Note that this message can be used by both private and public
response vehicles, and that the relative priority of each (as well as security certificates) is determined in the
application layer.
ASN.1 Representation:
EmergencyVehicleAlert ::= SEQUENCE {
   msgID           DSRCmsgID,  -- App ID value, 1 byte
   atisMsg         ATIS.RoadSideAlert
   responseType    ResponseType,              -- zero if NA
   sirenUse        SirenInUse,
   lightsUse       LightbarInUse,
   multi           MultiVehicleReponse,
                   -- combine above three into one byte!
   mass            VehicleMass,
   basicType       VehicleType,  -- gross size and axle cnt
   
   -- type of vehicle and agency when known
   vehicleType     ITIS.VehicleGroupAffected,      -- zero if NA
   responseEquip   ITIS.IncidentResponseEquipment, -- zero if NA
   responderType   ITIS.ResponderGroupAffected,    -- zero if NA
   ... -- # LOCAL_CONTENT
XML Representation:
<xs:element name="emergencyVehicleAlert" type="EmergencyVehicleAlert"/>
<xs:complexType name="EmergencyVehicleAlert" >
      <xs:sequence>
         <xs:element name="msgID" type="DSRCmsgID" />
         <!-- App ID value,  1 byte -->
         <xs:element name="atisMsg" type="atis:RoadSideAlert" />
         <xs:element name="responseType" type="ResponseType" />
         <!-- zero if NA -->
         <xs:element name="sirenUse" type="SirenInUse" />
         <xs:element name="lightsUse" type="LightbarInUse" />
         <xs:element name="multi" type="MultiVehicleReponse" />
         <!-- combine above three into one byte! -->
         <xs:element name="mass" type="VehicleMass" />
         <xs:element name="basicType" type="VehicleType" />
         <!-- gross size and axle cnt
         type of vehicle and agency when known -->
         <xs:element name="vehicleType" type="itis:VehicleGroupAffected" />
         <!-- zero if NA -->
         <xs:element name="responseEquip" type="itis:IncidentResponseEquipment" />
         <!-- zero if NA -->
         <xs:element name="responderType" type="itis:ResponderGroupAffected" />
         <!-- zero if NA -->
         <xs:element name="localEmergencyVehicleAlert" type="local:EmergencyVehicleAlert"
minOccurs="0"/>
      </xs:sequence>
</xs:complexType>
5.5 Message: MSG_GenericTransferMsg
Use: The GenericTransferMsg provides a basic means to exchange one or more blocks of data across the
interface.  Each application using this message frame SHALL have a unique value assigned to the applicationID
value and is allowed to have up to 255 simultaneous transfer sessions in operation at one time.  If an application
requires only a single session, it SHALL set the sessionID to be the value of zero.  Within each unique
applicationID / sessionID value pair there MAY be up to 65535 unique blocks of data sent, each with its own word
count up to 65535 bytes in length.  This is followed by the payLoad value, a sequence of octets up to 65535 bytes
in length.  Proper interpretation and any re-assembly of these blocks of data (if needed) SHALL be the