• 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

border card data Quintuple

Bidirectional?: False

border card data (A-Interconnect): This CVRIA application interconnect encapsulates all of the Layer 2 information flows between the 'Border Inspection' application object and the 'Traveler Card' physical object. 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 'border card data'. This application interconnect is uni-directional since the underlying layer 2 information flows go from 'Traveler Card' to 'Border Inspection System'.

Traveler Card (Source Physical Object): The 'Traveler Card' stores traveler identification information, including biometric information, that can be used in trusted traveler programs to expedite clearance through security checkpoints at borders or security-critical areas.

Border Inspection System (Destination Physical Object): 'Border Inspection System' represents data systems used at the border for the inspection of people or goods. It supports immigration, customs (trade), agricultural, and FDA inspections as applicable. It includes sensors and surveillance systems to identify and classify drivers and their cargo as they approach a border crossing, the systems used to interface with the back-office administration systems and provide information on status of the crossing or events.

Border Inspection (Destination Application Object): "Border Inspection" manages and supports primary and secondary inspections at the border crossing.