Commercial Vehicle OBE --> Fleet and Freight Management Center:
driver alert response
Definitions
driver alert response (Information Flow): Commercial Vehicle Driver response to a breach alert for a Freight Equipment breach or tamper event, or other alerts provided to the driver.
Commercial Vehicle OBE (Source 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.
Fleet and Freight Management Center (Destination Physical Object): The 'Fleet and Freight Management Center' provides the capability for commercial drivers and fleet-freight managers to receive real-time routing information and access databases containing vehicle and/or freight equipment locations as well as carrier, vehicle, freight equipment and driver information. The 'Fleet and Freight Management Center' also provides the capability for fleet managers to monitor the safety and security of their commercial vehicle drivers and fleet.
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) - Secure Wireless Internet (EU) (32)
- (None-Data) - Secure Wireless Internet (ITS) (32)
- (None-Data) - Apache Kafka over Wireless (36)
- (None-Data) - OMG DDS over Wireless (36)
- (None-Data) - OASIS MQTT over Wireless (42)
- (None-Data) - OASIS AMQP over Wireless (45)
Selected Solution
Solution Description
ITS Application Entity
Development needed |
Click gap icons for more info.
|
||
Mgmt
|
Facilities
Development needed |
Security
|
|
TransNet
|
|||
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 | Regional |
Acknowledgement | True |
Cardinality | Unicast |
Initiator | Source |
Authenticable | True |
Encrypt | True |
Interoperability | Description |
---|---|
Local | In cases where an interface is normally encapsulated by a single stakeholder, interoperability is still desirable, but the motive is vendor independence and the efficiencies and choices that an open standards-based interface provides. |
Security
Information Flow Security | ||||
---|---|---|---|---|
Confidentiality | Integrity | Availability | ||
Rating | Moderate | Moderate | Moderate | |
Basis | May affect vehicle and/or personal security, which if viewed by a hostile third party could be used in the performance of a criminal act against the operator/vehicle. | Must be correct and timely so the appropriate response is provided. Failure to receive an accurate message could result in nothing being done, exposing the driver/vehicle to a safety/security issue, or inefficiently assigning response resources. | Must be correct and timely so the appropriate response is provided. Failure to receive an accurate message could result in nothing being done, exposing the driver/vehicle to a safety/security issue, or inefficiently assigning response resources. |
Security Characteristics | Value |
---|---|
Authenticable | True |
Encrypt | True |