• 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: 'RSE 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 'Roadside Equipment' to 'Center'.

Roadside Equipment (Source Physical Object): 'Roadside Equipment' (RSE) represents the Connected Vehicle roadside devices that are used to send messages to, and receive messages from, nearby vehicles using Dedicated Short Range Communications (DSRC) or other alternative wireless communications technologies. Communications with adjacent field equipment and back office centers that monitor and control the RSE are also supported. This device operates from a fixed position and may be permanently deployed or a portable device that is located temporarily in the vicinity of a traffic incident, road construction, or a special event. It includes a processor, data storage, and communications capabilities that support secure communications with passing vehicles, other field equipment, and centers.

RSE Communications Support (Source Application Object): "RSE 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.