Commercial Vehicle OBE --> Multi-Access Edge Computing:
vehicle location and motion
This flow may also be implemented by
Commercial Vehicle OBE --> Connected Vehicle Roadside Equipment: vehicle location and motion Definitions
vehicle location and motion (Information Flow): Data describing the vehicle's location in three dimensions, heading, speed, acceleration, braking status, and size.
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.
Multi-Access Edge Computing (Destination Physical Object): 'Multi-Access Edge Computing' ((MEC) previously known as mobile edge computing) represents computing devices that operate and are managed like a cloud server, but are deployed at the edge of a network (typically a cellular network, but it could be any network). While not in strict proximity to the transportation network, these systems do benefit from vastly decreased distances to the roadway compared to central systems, and so can provide lower latency than strictly backoffice systems
This Triple is an instantiation of the more general triple:
Included In
This Triple is in the following Service Packages:
This triple is associated with the following Functional Objects:
- MEC Incident Scene Safety
- MEC Intersection Management
- MEC Intersection Safety
- MEC Rail Crossing Warning
- MEC Restricted Lanes Application
- MEC Traveler Information Communications
- MEC Work Zone Safety
- Vehicle Basic Safety Communication
- Vehicle Gap Assist
- Vehicle Rail Crossing Warning
- Vehicle Restricted Lanes Application
This Triple is described by the following Functional View Data Flows:
- vehicle_roadside_current_status_data
- vehicle_roadside_light_setting
- vehicle_roadside_location_data
- vehicle_roadside_size_data
- vehicle_roadside_speed_data
- vehicle_status_for_intersection
This Triple has the following triple relationships:
| None |
This Triple is an instantiation of the more general triple:
Communication Solutions
This Triple is an instantiation of the more general triple:
Characteristics
| Characteristic | Value |
|---|---|
| Time Context | Now |
| Spatial Context | Adjacent |
| Acknowledgement | False |
| Cardinality | Unicast |
| 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). |
This Triple is an instantiation of the more general triple:
Security
| Information Flow Security | ||||
|---|---|---|---|---|
| Confidentiality | Integrity | Availability | ||
| Rating | Not Applicable | High | Moderate | |
| Basis | This data is intentionally transmitted to everyone via a broadcast. Much of its information content can also be determined via other visual indicators | Incorrect information could lead to the system not operating properly. If the system does not properly know where the vehicle is, it cannot make an accurate decision about whether there is going to be a pedestrian in the crosswalk that the vehicle is approaching. This can have a safety impact. | This data is required for the system to operate properly. If this data is not available, the system cannot give accurate warning information. | |
| Security Characteristics | Value |
|---|---|
| Authenticable | True |
| Encrypt | False |