Interface: Private Vehicles - Micro Mobility Services

Private Vehicles to Micro Mobility Services Interface Diagram

Information Flow Definitions

automated vehicle control parameters  (Planned)  

Information, instructions, and control parameters for automated vehicle operations including current system conditions and advisories, control parameters (e.g., speed, required vehicle performance profiles, gaps or headways) and check in/checkout instructions.

interactive traveler information  (Existing)  

Traveler information provided in response to a traveler request. The provided information includes traffic and road conditions, advisories, incidents, restrictions, payment information, transit services, parking information, weather information, and other travel–related data updates and confirmations.

intersection status  (Planned)  

Current signal phase and timing information for all lanes at a signalized intersection. This flow identifies active lanes and lanes that are being stopped and specifies the length of time that the current state will persist for each lane. It also identifies signal priority and preemption status and pedestrian crossing status information where applicable.

traveler alerts  (Existing)  

Traveler information alerts reporting congestion, incidents, adverse road or weather conditions, parking availability, transit service delays or interruptions, and other information that may impact the traveler. Relevant alerts are provided based on traveler–supplied profile information including trip characteristics and preferences.

traveler request  (Existing)  

A request for traveler information including traffic, transit, toll, parking, road weather conditions, event, and passenger rail information. The request identifies the type of information, the area of interest, parameters that are used to prioritize or filter the returned information, and sorting preferences.

trip confirmation  (Planned)  

Acknowledgement by the driver/traveler of acceptance of a trip plan with associated personal and payment information required to confirm reservations. Conversely, this flow may also reject the proposed trip plan. Confirmations include the selected route and subsequent trip confirmation messages will be issued for route changes.

trip feedback  (Planned)  

Information provided at the conclusion of a trip that supports performance monitoring and system optimization. Information provided may include a record of the trip including HOV/HOT lane usage and user provided feedback at the conclusion of the trip.

trip plan  (Planned)  

A travel itinerary identifying a route and associated traveler information and instructions identifying recommended modes and transfer information, ride sharing options, and transit and parking reservation information. This flow also includes intermediate information that is provided as the trip plan is interactively created, including identification of alternatives, requests for additional information.

trip request  (Planned)  

Request for trip planning services that identifies the trip origin, destination(s), timing, preferences, and constraints. The request may also include the requestor's location or a request for transit and parking reservations and ridesharing options associated with the trip. The trip request also covers requests to revise a previously planned trip and interim updates that are provided as the trip is interactively planned.

user account setup  (Existing)  

Billing information, vehicle information (or registration information), and requests for reports. Also includes subsequent account changes.

user profile  (Planned)  

Information provided to register for a travel service and create a user account. The provided information includes personal identification, traveler preferences (e.g., maximum transfer wait time, maximum walking distance, mode preferences, special needs), device information, a user ID and password, and information to support payment transactions, if applicable.