• About
  • Connected Vehicle
  • Architecture
  • Approach
  • Viewpoints
  • Security
• Applications
• Views
  • Enterprise
  • Functional
  • Physical
  • Communications
• Standards
  • CV Standards
  • CV Standards Plan
• Resources
  • Databases
  • Diagrams
  • Documents
  • Presentations
  • Tools
  • Training
• Glossary
  • Acronyms
• Contact Us

device identification Quintuple

Bidirectional?: False

device identification (A-Interconnect): This CVRIA application interconnect encapsulates all of the Layer 2 information flows between two application objects: 'Vehicle Communications Support', and 'Center Permission Management'. In this case, there is only a single Layer 2 flow associated with this interconnect, so the Layer 1 application interconnect name and the Layer 2 information flow name are both 'device identification'. This application interconnect is uni-directional since the underlying layer 2 information flows go from 'Vehicle OBE' to 'Center'.

Vehicle OBE (Source Physical Object): The Vehicle On-Board Equipment (OBE) provides the vehicle-based processing, storage, and communications functions necessary to support connected vehicle operations. The radio(s) supporting V2V and V2I communications are a key component of the Vehicle OBE. This communication platform is augmented with processing and data storage capability that supports the connected vehicle applications.

In CVRIA, the Vehicle OBE includes the functions and interfaces that support connected vehicle applications for passenger cars, trucks, and motorcycles. Many of these applications (e.g., V2V Safety applications) apply to all vehicle types including personal vehicles, commercial vehicles, emergency vehicles, transit vehicles, and maintenance vehicles. From this perspective, the Vehicle OBE includes the common interfaces and functions that apply to all motorized vehicles.

Vehicle Communications Support (Source Application Object): "Vehicle Communications Support" supports secure, reliable communications with other connected devices. It provides the communications functions that add a timestamp, the message origin, and a digital signature in outbound messages and processes, verifies, and authenticates the same fields in inbound messages. It also encrypts (outbound) and decrypts (inbound) sensitive data.

Center (Destination Physical Object): This general physical object is used to model core capabilities that are common to any center.

Center Permission Management (Destination Application Object): "Center Permission Management" enables Connected Vehicle system users to request permission to access connected vehicle services. A center may request permission for the center or the infrastructure devices and vehicles associated with the center.