Maint and Constr Vehicle OBE --> Multi-Access Edge Computing:
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.

Maint and Constr Vehicle OBE (Source 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.

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:

• Vehicle => Multi-Access Edge Computing: vehicle location and motion

Included In

This Triple is in the following Service Packages:

• MC11: Maintenance and Construction Signal Priority

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:

This Triple is an instantiation of the more general triple:

• Vehicle => Multi-Access Edge Computing: vehicle location and motion

Communication Solutions

This Triple is an instantiation of the more general triple:

• Vehicle => Multi-Access Edge Computing: vehicle location and motion

Characteristics

This Triple is an instantiation of the more general triple:

• Vehicle => Multi-Access Edge Computing: vehicle location and motion

Security