Multi-Access Edge Computing --> Maint and Constr Vehicle OBE:
work zone warning notification
This triple is bi-directional. See also
Maint and Constr Vehicle OBE --> Multi-Access Edge Computing: work zone warning notification This flow may also be implemented by Connected Vehicle Roadside Equipment --> Maint and Constr Vehicle OBE: work zone warning notification
Definitions
work zone warning notification (Information Flow): Notification of a work zone emergency or safety issue. This flow identifies that a work zone emergency or safety issue has occurred so that warnings may be generated by more than one system in the work zone.
Multi-Access Edge Computing (Source 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
Maint and Constr Vehicle OBE (Destination Physical Object): The 'Maint and Constr Vehicle OBE' resides in a maintenance, construction, or other specialized service vehicle or equipment and provides the processing, storage, and communications functions necessary to support highway maintenance and construction. All types of maintenance and construction vehicles are covered, including heavy equipment, supervisory vehicles, unmanned remote controlled field maintenance robots, and sensory platforms that may be wheeled or low altitude aerial vehicles (e.g. drones, balloons). The MCV OBE provides two-way communications between drivers/operators and dispatchers and maintains and communicates current location and status information. A wide range of operational status is monitored, measured, and made available, depending on the specific type of vehicle or equipment. A snow plow for example, would monitor whether the plow is up or down and material usage information. The Maint and Constr Vehicle OBE may also contain capabilities to monitor vehicle systems to support maintenance of the vehicle itself. A separate 'Vehicle OBE' physical object supports the general vehicle safety and driver information capabilities that apply to all vehicles, including maintenance and construction vehicles. The Maint and Constr Vehicle OBE supplements these general capabilities with capabilities that are specific to maintenance and construction 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:
- None
This Triple has the following triple relationships:
| None |
Communication Solutions
-
EU: ETSI data dictionary - Secure Wireless Internet (EU) (19)
-
(None-Data) - Secure Wireless Internet (ITS) (43)
-
(None-Data) - Secure Wireless Internet (EU) (43)
Selected Solution
(None-Data) - Secure Wireless Internet (EU)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 | Adjacent |
| Acknowledgement | False |
| Cardinality | Unicast |
| Initiator | Source |
| Authenticable | True |
| Encrypt | False |
| 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 | Not Applicable | Moderate | Moderate | |
| Basis | This data is intentionally transmitted to everyone via a broadcast. It can also be determined via other visual indicators. | This information should be accurate, but an incorrect information should not have a direct impact causing the loss of life or limb. | The system should be able to operate properly if it misses a few messages. If a message is not received, the RSE should know. | |
| Security Characteristics | Value |
|---|---|
| Authenticable | True |
| Encrypt | False |


