request tag data (Information Flow): Request for tag information including tag id and associated data.
Commercial Vehicle Check Equipment (Source Physical Object): 'Commercial Vehicle Check Equipment' supports automated vehicle identification at mainline speeds for credential checking, roadside safety inspections, and weigh-in-motion using two-way data exchange. These capabilities include providing warnings to the commercial vehicle drivers, their fleet managers, and proper authorities of any safety problems that have been identified, accessing and examining historical safety data, and automatically deciding whether to allow the vehicle to pass or require it to stop with operator manual override. Commercial Vehicle Check Equipment also provides supplemental inspection services such as expedited brake inspections, the use of operator hand-held devices, mobile screening sites, on-board safety database access, and the enrollment of vehicles and carriers in the electronic clearance program.
Freight Equipment (Destination Physical Object): 'Freight Equipment' represents a freight container, intermodal chassis, or trailer and provides sensory, processing, storage, and communications functions necessary to support safe, secure and efficient freight operations. It provides equipment safety data and status and can alert the appropriate systems of an incident, breach, or tamper event. It also provides accurate position information to support in-transit visibility of freight equipment.
This Triple is in the following Service Packages:
This Triple is described by the following Functional View Functional Objects:
- CVCE Electronic Screening
- CVCE International Border Crossing
- CVCE Safety and Security Inspection
- CVCE Weigh-In-Motion
- Freight Equipment Monitoring
This Triple is described by the following Functional View Data Flows:
This Triple has the following triple relationships:
|Commercial Vehicle Check Equipment
- Proprietary Data - Proprietary Comm (16)
- (None-Data) - BTP/GeoNetworking/G5 (42)
- (None-Data) - LTE-V2X WSMP (44)
- (None-Data) - WAVE WSMP (46)
ITS Application Entity
Click gap icons for more info.
Note that some layers might have alternatives, in which case all of the gap icons associated with every alternative may be shown on the diagram, but the solution severity calculations (and resulting ordering of solutions) includes only the issues associated with the default (i.e., best, least severe) alternative.
|This triple should be implemented consistently within the geopolitical region through which movement is essentially free (e.g., the United States, the European Union).
|Information Flow Security
|This request is sent to all vehicles entering the border, and does not contain any sensitive information.
|This needs to verify that it is coming from a valid sender.
|If this request is not received, the system will not broadcast its tag data. However, there are multiple chances for this data to be transmitted and received. Additionally, if the vehicle is not pre-approved it will be handled by border security.