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

Transit Vehicle OBE (Source Physical Object): The 'Transit Vehicle On-Board Equipment' (OBE) resides in a transit vehicle and provides the sensory, processing, storage, and communications functions necessary to support safe and efficient movement of passengers. The types of transit vehicles containing this physical object include buses, paratransit vehicles, light rail vehicles, other vehicles designed to carry passengers, and supervisory vehicles. It collects ridership levels and supports electronic fare collection. It supports a traffic signal prioritization function that communicates with the roadside physical object to improve on-schedule performance. Automated vehicle location enhances the information available to the transit operator enabling more efficient operations. On-board sensors support transit vehicle maintenance. The physical object supports on-board security and safety monitoring. This monitoring includes transit user or vehicle operator activated alarms (silent or audible), as well as surveillance and sensor equipment. The surveillance equipment includes video (e.g. CCTV cameras), audio systems and/or event recorder systems. It also furnishes travelers with real-time travel information, continuously updated schedules, transfer options, routes, and fares. A separate 'Vehicle OBE' physical object supports the general vehicle safety and driver information capabilities that apply to all vehicles, including transit vehicles. The Transit Vehicle OBE supplements these general capabilities with capabilities that are specific to transit 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:

• PT09: Transit Signal Priority
• PT12: Transit Vehicle at Station/Stop Warnings

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