Navigation bar
  Print document Start Previous page
 34 of 210 
Next page End  

SAE J2735-Draft-Rev18 [issued: 06-26-07] 
-
34 -
This is an SAE Motor Vehicle Council draft document of the DSRC committee, subject to change.
               <xs:sequence minOccurs="1" maxOccurs="32">
                  <xs:element name="dataElement" type="TEMP_XML_TYPE_VALUE" />
                  <xs:element name="stdTagList" type="VehicleStatusDeviceTypeTag" />
                  <!-- Vehicle Sensor that the
                  following threshold applies
                  to  (from J2735) -->
                  <xs:element name="threshold" type="VehicleStatusDeviceType" />
                  <!-- new threshold -->
               </xs:sequence>
            </xs:complexType>
         </xs:element>
      </xs:sequence>
</xs:complexType>
Remarks: Provided by VII POC-A team.
5.9 Message: MSG_ProbeVehicleData
Use: The probe vehicle message frame is defined below.  The probe vehicle message is used to exchange
status about a vehicle with other (typically RSU) DSRC readers to allow the collection of information
about typically vehicle traveling behaviors along a segment of road.  The exchanges of this message as well
as the event which caused the collection of various elements defined in the messages are defined in Annex
B of this standard.   In typical use the reporting vehicle has collected one or more snapshots which it will
send to a receiving RSU along with information (the vector) about the point in time and space when the
snapshot event occurred.  Because any sequence of snapshots are related within a limit range of time and
space, some data compression may be used in the message to reduce redundant information.
ASN.1 Representation:
ProbeVehicleData ::= SEQUENCE {
   msgID           DSRCmsgID,            -- App ID value, 1 byte
   startVector     FullPositionVector,   -- the space and time of 
                                         -- transmission to the RSU
   vehicleType     VehicleType,          -- type of vehicle, 1 byte
   cntSnapshoots   INTEGER (1..32),      -- a count of how many snaphots 
                                         -- type entires will follow
   snapshots       SEQUENCE (SIZE(1..32)) OF Snapshot,               
                                         -- a seq of name-value pairs 
                                         -- along with the space and time 
                                         -- of the first measurement set
   ... -- # LOCAL_CONTENT 
   } -- Est size about 64 bytes plus snapshot sizes (about 12 per)
XML Representation:
<xs:element name="probeVehicleData" type="ProbeVehicleData"/>
<xs:complexType name="ProbeVehicleData" >
      <xs:annotation>
         <xs:documentation>       
            Est size about 64 bytes plus snapshot sizes  (about 12 per)
         </xs:documentation>
      </xs:annotation>
      <xs:sequence>
         <xs:element name="msgID" type="DSRCmsgID" />
         <!-- App ID value,  1 byte -->
         <xs:element name="startVector" type="FullPositionVector" />
         <!-- the space and time of
         transmission to the RSU -->
         <xs:element name="vehicleType" type="VehicleType" />
         <!-- type of vehicle,  1 byte -->
         <xs:element name="cntSnapshoots" >
            <xs:simpleType>
               <xs:restriction base="xs:unsignedByte">
                  <xs:minInclusive value="1"/>
                  <xs:maxInclusive value="32"/>
               </xs:restriction>
            </xs:simpleType>
         </xs:element>