![]() SAE J2735-Draft-Rev26 [issued: 09-18-08]   
-  
36 -  
This is an SAE Motor Vehicle Council draft document of the DSRC committee, subject to change.  
                                         -- not used when ident is used  
   probeID         VehicleIdent OPTIONAL,   
                                         -- ident data for selected   
                                         -- types of vehicles      
                   -- Roy: above two items could be in a CHIOCE statement?   
   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  
                                         -- 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="segNum" type="ProbeSegmentNumber"  minOccurs="0"/>  
         <!-- a short term Ident value  
         not used when ident is used -->  
         <xs:element name="probeID" type="VehicleIdent"  minOccurs="0"/>  
         <!-- ident data for selected  
         types of vehicles  
         Roy: above two items could be in a CHIOCE statement? -->  
         <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>  
         <!-- a count of how many snaphots  
         type entires will follow -->  
         <xs:element name="snapshots" >  
            <xs:complexType>  
               <xs:sequence minOccurs="1" maxOccurs="32">  
                  <xs:element name="snapshot" type="Snapshot" />  
                  <!-- a seq of name-value pairs along with the space and time of the  
first measurement set -->  
               </xs:sequence>  
            </xs:complexType>  
         </xs:element>  
         <xs:element name="localProbeVehicleData" type="local:ProbeVehicleData"  
minOccurs="0"/>  
      </xs:sequence>  
</xs:complexType>  
 In addition, this item may be used by data structures in other ITS standards.  
Remarks:  At the time of writing additional probe vehicle messages are being developed that will allow control over  
what information is gathered and reported in a probe vehicle message.  Builders are urged to consider these messages in  
their development of products using this message.  
 |