Event-Based Driver Dispatch System for Ride-Hailing

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current taxi services face inefficiencies in identifying events and preemptively directing drivers to transport passengers, leading to suboptimal service and increased wait times for passengers.

Innovation Solution

A system that detects multiple transportation requests to a common destination location within a time window, identifies events, estimates the event's end time, and proactively navigates drivers to the location to be ready for passenger pickup upon the event's completion, utilizing mobile devices and a backend system to manage driver and passenger requests.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If drivers are dispatched reactively based on passenger requests, then the system operates with simple dispatch logic, but passenger wait times increase and service efficiency decreases

Engineering Contradiction:
Improveservice efficiencyVSAvoiddispatch system complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The system performs preliminary actions by detecting events and proactively directing drivers to event locations before passengers need transportation. The backend system monitors transportation requests, identifies patterns indicating events, and positions drivers in advance, transforming the dispatch model from reactive to proactive and reducing passenger wait times

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The dispatch system is segmented into distinct functional modules: event detection module that analyzes transportation request patterns, event identification module that determines when an event is occurring, and driver direction module that proactively routes drivers to event locations. This segmentation allows complex event-based dispatch while maintaining manageable system architecture

Inventive Principle:
Principle #1Segmentation

2Loss of time

If drivers are directed to event locations in advance, then passenger wait times are reduced, but driver idle time and fuel consumption increase

Engineering Contradiction:
Improvepassenger wait timeVSAvoiddriver fuel consumption
Core Design Contradiction:
Loss of timeVSLoss of energy

Solution Approach 1:

The system dynamically adjusts dispatch parameters based on event characteristics. It considers event type, expected duration, historical attendance patterns, and current driver availability to optimize the timing and location of driver deployment. This parameter-based approach ensures drivers are positioned efficiently without excessive idle time or fuel consumption

Inventive Principle:
Principle #35Parameter changes

Solution Approach 2:

The system incorporates feedback mechanisms where driver availability, current location, and past performance data are continuously monitored. This feedback allows the backend system to optimize driver routing and minimize unnecessary travel, balancing the need for proactive deployment with energy efficiency considerations

Inventive Principle:
Principle #23Feedback

3Measurement precision

If the system monitors all transportation requests to detect events, then event identification accuracy improves, but system computational load increases

Engineering Contradiction:
Improveevent detection accuracyVSAvoidsystem computational energy
Core Design Contradiction:
Measurement precisionVSUse of energy by moving object

Solution Approach 1:

The system applies partial monitoring by focusing computational resources on patterns that indicate events rather than analyzing every individual request in detail. It uses threshold-based detection and pattern recognition to identify event conditions, achieving sufficient accuracy while reducing unnecessary computational overhead from monitoring all requests equally

Inventive Principle:
Principle #16Partial or excessive action

Data Source

PatentUS10467561B2System for identifying events and preemptively navigating drivers to transport passengers from the events
Publication Date: 2019.11.05 LYFT INC
  • US10467561B2 patent drawing
  • US10467561B2 patent drawing
  • US10467561B2 patent drawing

AI summary

In one embodiment a plurality of transportation requests sent within a particular time window to a taxi service that specify the same destination location are detected. It is determined that an event is occurring at the destination location. An end time of the event is estimated. Prior to the end time of the event, a plurality of drivers associated with the taxi service are directed to drive to the destination location to transport passengers from the event.