Border Inspection System --> Commercial Vehicle OBE:
request tag data
Definitions
request tag data (Information Flow): Request for tag information including tag id and associated data.
Border Inspection System (Source 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.
Commercial Vehicle OBE (Destination Physical Object): The Commercial Vehicle On-Board Equipment (OBE) resides in a commercial vehicle and provides the sensory, processing, storage, and communications functions necessary to support safe and efficient commercial vehicle operations. It provides two-way communications between the commercial vehicle drivers, their fleet managers, attached freight equipment, and roadside officials. A separate 'Vehicle OBE' physical object supports vehicle safety and driver information capabilities that apply to all vehicles, including commercial vehicles. The Commercial Vehicle OBE supplements these general ITS capabilities with capabilities that are specific to commercial vehicles.
Included In
This Triple is in the following Service Packages:
This triple is associated with the following Functional Objects:
This Triple is described by the following Functional View Data Flows:
This Triple has the following triple relationships:
Relationship | Source | Destination | Flow |
---|---|---|---|
Request-Response | Commercial Vehicle OBE | Border Inspection System | tag data |
Communication Solutions
- Proprietary Data - Proprietary Comm (16)
- (None-Data) - BTP/GeoNetworking/G5 (42)
- (None-Data) - LTE-V2X WSMP (44)
- (None-Data) - WAVE WSMP (46)
Selected Solution
Solution Description
ITS Application Entity
Proprietary |
Click gap icons for more info.
|
||
Mgmt
Proprietary |
Facilities
Proprietary |
Security
Proprietary |
|
TransNet
Proprietary |
|||
Access
Proprietary |
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.
Characteristics
Characteristic | Value |
---|---|
Time Context | Recent |
Spatial Context | Adjacent |
Acknowledgement | False |
Cardinality | Broadcast |
Initiator | Source |
Authenticable | True |
Encrypt | False |
Interoperability | Description |
---|---|
National | This triple should be implemented consistently within the geopolitical region through which movement is essentially free (e.g., the United States, the European Union). |
Security
Information Flow Security | ||||
---|---|---|---|---|
Confidentiality | Integrity | Availability | ||
Rating | Not Applicable | Moderate | Low | |
Basis | 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. |
Security Characteristics | Value |
---|---|
Authenticable | True |
Encrypt | False |