Border Inspection System --> Commercial Vehicle OBE:
clearance notification
Definitions
clearance notification (Information Flow): Notification that cargo has been cleared through customs.
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:
| None |
Communication Solutions
-
(None-Data) - Local Unicast Wireless (1609.2) (35)
-
(None-Data) - Local Unicast Wireless (EU) (38)
Selected Solution
(None-Data) - Local Unicast Wireless (1609.2)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 | True |
| 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 | Moderate | Moderate | Moderate | |
| Basis | This notification is sensitive. If someone is able to know in advance that a truck was not cleared through customs, they may attempt to flee. If this contains information about the contents of a container, this could be raised to a HIGH. | Some minimal guarantee of data integrity is necessary for all C-ITS flows. This information is useful for logistic specialists to know, however, they will also be receiving similar information from other sources. A false message here may cause confusions, but there will be other sources of data, such as the vehicles GPS that would help clear this up. DISC: Original V2I analysis classified this as LOW. | This information is not acted upon in the Border Management System. It provides a useful service to the users, but the lack of a message would not cause the Border Management System to be harmed in any way. It is necessary for the sender to know if the message was received. | |
| Security Characteristics | Value |
|---|---|
| Authenticable | True |
| Encrypt | True |