Vehicle --> 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.

Vehicle (Source Physical Object): This 'Vehicle' physical object is used to model core capabilities that are common to more than one type of Vehicle. It provides the vehicle-based general sensory, processing, storage, and communications functions that support efficient, safe, and convenient travel. Many of these capabilities (e.g., see the Vehicle Safety service packages) apply to all vehicle types including personal vehicles (including motorcycles), commercial vehicles, emergency vehicles, transit vehicles, and maintenance vehicles. From this perspective, the Vehicle includes the common interfaces and functions that apply to all motorized vehicles. The radio(s) supporting V2V and V2I communications are a key component of the Vehicle. Both one-way and two-way communications options support a spectrum of information services from basic broadcast to advanced personalized information services. Advanced sensors, processors, enhanced driver interfaces, and actuators complement the driver information services so that, in addition to making informed mode and route selections, the driver travels these routes in a safer and more consistent manner. This physical object supports all six levels of driving automation as defined in SAE J3016. Initial collision avoidance functions provide 'vigilant co-pilot' driver warning capabilities. More advanced functions assume limited control of the vehicle to maintain lane position and safe headways. In the most advanced implementations, this Physical Object supports full automation of all aspects of the driving task, aided by communications with other vehicles in the vicinity and in coordination with supporting infrastructure subsystems.

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

Included In

This Triple is in the following Service Packages:

• MC07: Work Zone Safety Monitoring
• PS07: Incident Scene Safety Monitoring
• TM14: Advanced Railroad Grade Crossing
• TM22: Dynamic Lane Management and Shoulder Use
• VS12: Vulnerable Road User Safety
• VS13: Intersection Safety Warning and Collision Avoidance
• VS16: Vehicle Cooperative Maneuvers

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 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:

Communication Solutions

Characteristics

Security