Light Vehicle OBE --> Border Inspection System:
traveler credentials
Definitions
traveler credentials (Information Flow): Traveler identification, including trusted traveler program information, if applicable.
Light Vehicle OBE (Source Physical Object): The 'Light Vehicle OBE' includes traveler-oriented capabilities that apply to passenger cars, trucks, and motorcycles that are used for personal travel. The rules vary by jurisdiction, but generally light vehicles are restricted in their weight and the maximum number of passengers they can carry. In ARC-IT, the Light Vehicle OBE represents vehicles that are operated as personal vehicles that are not part of a vehicle fleet and are not used commercially; thus, the choice between the various vehicle subsystems should be based more on how the vehicle is used than how much the vehicle weighs. See also the 'Vehicle' subsystem that includes the general safety and information services that apply to all types of vehicles, including light vehicles.
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.
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:
None |
Communication Solutions
- (None-Data) - Local Unicast Wireless (1609.2) (51)
- (None-Data) - Local Unicast Wireless (EU) (54)
Selected Solution
Solution Description
ITS Application Entity
Development needed |
Click gap icons for more info.
|
||
Mgmt
Addressed Elsewhere |
Facilities
Development needed |
Security
|
|
TransNet
IEEE 1609.3 |
|||
Access
|
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 | Unicast |
Initiator | Source |
Authenticable | True |
Encrypt | True |
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 | High | Moderate | Moderate | |
Basis | This contains sensitive information on multiple individuals that could potentially be used to impersonate them or steal their identity. If anyone other than the intended parties can view this information it could lead to a large financial cost for many individuals. | The identity reported by this transmission might not actually be the individual in the vehicle. If a border officer can add information that gets sent to the BIS, then the integrity requirement could potentially be raised to HIGH as this flow might be used to make law enforcement decisions involving the use of force. We assume that if this information is added it is added at the BIS rather than the RSE, so this integrity requirement on this flow is MEDIUM. | Assuming it is still possible to validate travelers in the way that is currently possible this is acceptable as a MEDIUM. If when this system is down, the border cannot process any individuals then this would need to be a HIGH because completely shutting down the border could cause significant financial problems. |
Security Characteristics | Value |
---|---|
Authenticable | True |
Encrypt | True |