Emergency Vehicle OBE --> Freight Equipment:
container seal interrogation
Definitions
container seal interrogation (Information Flow): Customs inspection of the electronic seal on a container to verify the container has not been opened or tampered with; requires proper authentication.
Emergency Vehicle OBE (Source Physical Object): The 'Emergency Vehicle On-Board Equipment' (OBE) resides in an emergency vehicle and provides the processing, storage, and communications functions that support public safety-related connected vehicle applications. It represents a range of vehicles including those operated by police, fire, and emergency medical services. In addition, it represents other incident response vehicles including towing and recovery vehicles and freeway service patrols. It includes two-way communications to support coordinated response to emergencies. A separate 'Vehicle OBE' physical object supports the general vehicle safety and driver information capabilities that apply to all vehicles, including emergency vehicles. The Emergency Vehicle OBE supplements these general capabilities with capabilities that are specific to emergency vehicles.
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.
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) - LTE-V2X WSMP (44)
- (None-Data) - WAVE WSMP (46)
Selected Solution
Solution Description
ITS Application Entity
Development needed |
Click gap icons for more info.
|
||
Mgmt
SAE J3161 3GPP 24.301 3GPP 36.331 |
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 | 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 | Low | Moderate | Moderate | |
Basis | Probably no need to obfuscate the request, though if any unique or proprietary information is requested this could change to MODERATE. | The container seal status returned after this interrogation will not have a HIGH integrity, as such is interrogation does not require a HIGH integrity. If the integrity of the container seal status is somehow possible to raise to a HIGH, then this could also have a HIGH integrity. | Would be nice to make this HIGH considering the safety implications in case of HAZMAT containers, but considering the context of an incident, HIGH is likely impractical for this wireless signal in a vehicular environment. |
Security Characteristics | Value |
---|---|
Authenticable | True |
Encrypt | False |