Ride Request Device with Predefined Destination Routing

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional methods for requesting a ride in an autonomous vehicle are time-consuming and lack options for trip restrictions, requiring users to download applications and manually input destinations and pick-up locations.

Innovation Solution

A device with a location sensor and transmitter that communicates with a dispatch server to set predefined destinations and dynamic pick-up locations, allowing users to hail vehicles with simplified input, such as a single button press, and enabling autonomous vehicles to navigate to these locations while adhering to user-defined restrictions.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If conventional ride request methods are used requiring manual input of destinations and pick-up locations, then users can request rides, but the process becomes time-consuming and complex

Engineering Contradiction:
Improveride request processVSAvoidtime to request ride
Core Design Contradiction:
Ease of operationVSLoss of time

Solution Approach 1:

The system pre-loads destination options and pick-up location data into the autonomous vehicle application, allowing users to select from predefined choices rather than manually inputting information. This preliminary preparation of data options significantly reduces the time and effort required for ride requests.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The application automatically accesses and processes location data, vehicle availability information, and trip details without requiring manual intervention for each parameter. The system self-manages the complex data processing and matching between users and available autonomous vehicles.

Inventive Principle:
Principle #25Self-service

2Adaptability or versatility

If conventional ride request methods are used, then users can request rides, but options for trip restrictions and customization are limited

Engineering Contradiction:
Improvetrip customization optionsVSAvoidride request process
Core Design Contradiction:
Adaptability or versatilityVSEase of operation

Solution Approach 1:

The ride request system is divided into distinct selectable components including destination options, pick-up location choices, and trip restriction parameters. Each segment can be independently configured and selected, allowing users to customize their ride requests according to specific needs while maintaining operational simplicity through structured presentation.

Inventive Principle:
Principle #1Segmentation

3Ease of operation

If simplified input methods are used for hailing vehicles, then user convenience is enhanced, but the risk of unintentional vehicle hails increases

Engineering Contradiction:
Improvevehicle hailing processVSAvoidaccidental hail prevention
Core Design Contradiction:
Ease of operationVSReliability

Solution Approach 1:

The system requires users to pre-configure destination preferences and trip parameters before enabling simplified hailing. This preliminary setup creates a buffer that prevents accidental hails, as the system will only dispatch vehicles to pre-approved destinations rather than responding to any casual input.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The application provides confirmation prompts and visual feedback when processing hail requests, allowing users to verify their intent before vehicle dispatch is initiated. This feedback mechanism ensures that simplified input methods do not lead to unintentional hails by maintaining user awareness and confirmation in the process.

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS11830100B2Efficient ride request
Publication Date: 2023.11.28 GM GLOBAL TECHNOLOGY OPERATIONS LLC
  • US11830100B2 patent drawing
  • US11830100B2 patent drawing
  • US11830100B2 patent drawing

AI summary

A device for hailing a vehicle includes a location sensor outputting location information indicative of a location of the device. The device further includes a device interface configured to receive an input from a user of the device. Responsive to the input, a transmitter of the device transmits the location information, input information, and identification information for the device to a dispatch server system. The transmitter is further configured to route the location information, the input information, and the identification information for the device to only the dispatch server system. The identification information is used by the dispatch server system to set a predefined location associated with the identification information as a destination for a trip for the user in the vehicle. The predefined location is defined in an account corresponding to the identification information of the device maintained by the dispatch server system prior to receipt of the input.