Multi-Modal Navigation With Ride Service APIs Without App Switching

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing mapping applications require users to switch between different ride service applications for selecting and ordering transportation services, lacking integrated inter-application communication for seamless ride service integration.

Innovation Solution

A mapping application communicates directly with ride service APIs to provide multi-modal travel directions, allowing users to select and order transportation services without leaving the mapping app, incorporating ride service data such as types, prices, and wait times, and offering interactive map visualizations.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If users switch between mapping application and separate ride service applications to order transportation services, then ride service functionality is available, but user convenience deteriorates due to multiple app switches

Engineering Contradiction:
Improveuser convenienceVSAvoidnumber of applications
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

The patent combines ride service functionality with the mapping application by establishing direct communication between the mapping application and ride service provider APIs. This allows users to access ride service features (booking, tracking, pricing) within the mapping application interface, eliminating the need to switch to separate ride service applications and thereby improving user convenience while reducing the effective number of applications needed.

Inventive Principle:
Principle #5Merging (Combining)

2Adaptability or versatility

If mapping application integrates ride service functionality through direct API communication, then user experience improves through seamless integration, but system complexity increases

Engineering Contradiction:
Improveintegration capabilityVSAvoidsystem architecture
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent employs an intermediary communication layer (API interface) that bridges the mapping application and ride service provider systems. This intermediary mechanism handles the complexity of inter-application communication, data exchange, and integration logic, allowing the mapping application to gain enhanced adaptability and versatility for providing multi-modal directions while the intermediary manages the system architecture complexity.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Adaptability or versatility

If multiple ride service providers are integrated into the mapping application, then service selection capability improves, but information processing complexity increases

Engineering Contradiction:
Improveservice selection capabilityVSAvoiddata processing
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent segments the integration approach by establishing individual, independent communication channels with each ride service provider through separate API interfaces. This segmentation allows the mapping application to selectively access and compare services from multiple providers without creating a monolithic complex system, thereby improving service selection capability while managing information processing complexity through modular, provider-specific integration segments.

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS12417416B2Multi-modal directions with a ride service segment in a navigation application
Publication Date: 2025.09.16 GOOGLE LLC
  • US12417416B2 patent drawing
  • US12417416B2 patent drawing
  • US12417416B2 patent drawing

AI summary

To provide ride services within a mapping application in a client computing device without directing the user to a separate ride service application, the mapping application invokes one or several ride service APIs to access ride service data from various ride service providers. For example, the mapping application receives a request for travel directions to a destination and generates multi-modal travel directions which include a route segment where the mode of transportation is a ride service. The mapping application invokes one or several ride service APIs to retrieve a price estimate, estimated wait time, or any other suitable information regarding the ride service route segment. Accordingly, the mapping application provides the multi-modal travel directions to a user including information regarding the ride service route segment.