Navigation bar
  Print document Start Previous page
 83 of 240 
Next page End  

SAE J2735-Draft-Rev26 [issued: 09-18-08] 
-
83 -
This is an SAE Motor Vehicle Council draft document of the DSRC committee, subject to change.
Remarks: A Vehicle Computed Lane has its own lane number, width and attributes (see also the
Reference Lane). The Reference Lane Number indicates which lane it parallels. The Driven Line Offset
gives the distance between the computed lane with respect to. its reference lane.  Lane Width indicates the
width of the driven portion of the lane in decimeters. If the width is absence or set to zero, it is inherited
from the Reference Lane. 
6.51 Data Frame: DF_VehicleIdent
Use: The VehicleIdent data frame is used to provide identity information about a selected vehicle. This
data frame is typical used with fleet type vehicles who can safety release such information for use with
probe measurements.  
ASN.1 Representation:
VehicleIdent ::= SEQUENCE {
   name           DescriptiveName OPTIONAL,
                  -- a human readable name for debuging use
   vin            VINstring OPTIONAL,
                  -- vehicle VIN value
   ownerCode      IA5String(SIZE(1..32)) OPTIONAL,
                  -- vehicle owner code (as per Roy request)
   fleetNum       IA5String(SIZE(1..32)) OPTIONAL,
                  -- vehicle fleet string value (DCK thought)
   
   -- Requirement number 5 stated that:
   -- A user data field would be added that will
   -- allow the vehicle owner to obtain parameters
   -- from the vehicle   [Need more info to fill this out]
   -- do we really want "private data" in the probe msg?
   
   vehicleType    VehicleType  OPTIONAL, 
   vehicleClass   CHOICE 
                  {
                  vGroup ITIS.VehicleGroupAffected,
                  rGroup ITIS.ResponderGroupAffected,
                  rEquip ITIS.IncidentResponseEquipment  
                  } OPTIONAL, 
   ... -- # LOCAL_CONTENT
   }
XML Representation:
<xs:complexType name="VehicleIdent" >
      <xs:sequence>
         <xs:element name="name" type="DescriptiveName"  minOccurs="0"/>
         <!-- a human readable name for debuging use -->
         <xs:element name="vin" type="VINstring"  minOccurs="0"/>
         <!-- vehicle VIN value -->
         <xs:element name="ownerCode"  minOccurs="0">
            <xs:simpleType>
               <xs:restriction base="xs:string">
                  <xs:minLength value="1"/>
                  <xs:maxLength value="32"/>
               </xs:restriction>
            </xs:simpleType>
         </xs:element>
         <!-- vehicle owner code  (as per Roy request) -->
         <xs:element name="fleetNum"  minOccurs="0">
            <xs:simpleType>
               <xs:restriction base="xs:string">
                  <xs:minLength value="1"/>
                  <xs:maxLength value="32"/>
               </xs:restriction>
            </xs:simpleType>
         </xs:element>
         <!-- vehicle fleet string value  (DCK thought)
         Requirement number 5 stated that:
         A user data field would be added that will
Click to Convert - Powerful PDF Converter and HTML Converter.