Simplified Transportation Request Device Backend Driver Matching

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current transportation request systems require complex user interactions and significant bandwidth, leading to increased latency and power consumption, making them inefficient for quick and simple ride requests.

Innovation Solution

A simplified transportation request device with limited user input, such as a single button, that initiates ride requests by communicating directly with a backend server, reducing the need for complex app usage and minimizing data transfer, while a backend system selects the most suitable driver based on predefined passenger preferences.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If a simplified transportation request device with limited user input is used, then the ease of operation is improved, but the device complexity increases due to backend system requirements

Engineering Contradiction:
Improveease of operationVSAvoiddevice complexity
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

A backend server acts as an intermediary between the simplified request device and the driver selection system. The device sends minimal requests (e.g., single button press) to the backend, which handles complex processing including driver matching, route calculation, and coordination, thereby keeping the device simple while maintaining operational ease.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

Complex functionality is extracted from the request device and relocated to the backend system. The device retains only essential input mechanisms (one or two buttons), while the backend assumes responsibility for sophisticated algorithms, data management, and decision-making processes.

Inventive Principle:
Principle #2Taking out (Extraction)

2Loss of energy

If direct communication between the simplified device and backend server is implemented, then the communication bandwidth is reduced, but the reliability may worsen due to limited error handling capabilities

Engineering Contradiction:
Improvepower consumptionVSAvoidreliability
Core Design Contradiction:
Loss of energyVSReliability

Solution Approach 1:

The backend server performs preliminary actions by pre-processing transportation requests and pre-identifying suitable drivers before the user completes their input. This allows the system to have requests ready for immediate fulfillment, reducing latency and power consumption while maintaining reliability through advance preparation.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system implements self-service mechanisms where the backend automatically handles driver selection, route optimization, and request fulfillment without requiring extensive user input or intervention. This automation reduces communication overhead and power consumption while maintaining system reliability through programmed error handling.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS10921140B2Navigating drivers to service transportation requests from a simplified transportation request device
Publication Date: 2021.02.16 LYFT INC
  • US10921140B2 patent drawing
  • US10921140B2 patent drawing
  • US10921140B2 patent drawing

AI summary

Systems and methods for navigating drivers to service transportation requests from a simplified transportation request device are described. In one implementation, a method includes establishing, by a processing device of a server device, a communication connection with a transportation request device dedicated solely to functions associated with a transportation service, communicating, via the communication connection, configuration information with the transportation request device, receiving, via the communication connection, one or more passenger preferences associated with the transportation service and a user of the transportation request device, receiving one or more transportation requests from the transportation request device, and causing, by the processing device, the received one or more transportation requests to be serviced based on the configuration information and the one or more passenger preferences.