Navigation API Waypoint Routing for Multi-Platform Integration

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current navigation applications on computing devices lack a standardized and customizable API for integrating navigation services, limiting their ability to provide tailored navigation experiences across various platforms and use cases.

Innovation Solution

A non-transitory computer-readable medium storing instructions for an application programming interface (API) that enables navigation services by specifying parameters for controlling navigation implementations and interactions with navigation engines, including a waypoint function for setting multiple waypoints and event listener interfaces for updating navigation information in real-time.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If a standardized API for navigation services is implemented, then adaptability and ease of integration are improved, but device complexity and implementation requirements increase

Engineering Contradiction:
ImproveadaptabilityVSAvoidcomplexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The API is divided into distinct functional components including waypoint management functions, route calculation functions, and navigation instruction functions. Each function handles a specific aspect of navigation, allowing developers to integrate only the needed components while maintaining overall system adaptability across different platforms and use cases.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The navigation API is designed as a universal interface that can be applied across multiple platforms (mobile devices, vehicles, wearables) and various use cases (ride-sharing, delivery, social applications). The standardized parameter structures and function interfaces enable the same API to serve diverse navigation needs without requiring platform-specific implementations.

Inventive Principle:
Principle #6Universality (Multi-functionality)

2Adaptability or versatility

If multiple waypoints and custom parameters are supported, then navigation customization and versatility are improved, but processing requirements and computational load increase

Engineering Contradiction:
ImprovecustomizationVSAvoidprocessing power
Core Design Contradiction:
Adaptability or versatilityVSPower

Solution Approach 1:

Waypoints and navigation parameters are defined and validated in advance through standardized data structures before route calculation begins. The API pre-processes waypoint inputs, validates coordinate formats, and prepares parameter sets, reducing the computational burden during actual route calculation and enabling support for multiple waypoints without excessive processing requirements.

Inventive Principle:
Principle #10Preliminary action

3Measurement precision

If real-time navigation updates and event listener interfaces are implemented, then navigation accuracy and responsiveness are improved, but data transmission and processing requirements increase

Engineering Contradiction:
ImproveprecisionVSAvoiddata volume
Core Design Contradiction:
Measurement precisionVSQuantity of substance

Solution Approach 1:

The API implements event listener interfaces that provide real-time feedback on navigation progress, route deviations, and waypoint arrivals. The system continuously monitors navigation state and transmits only relevant update events (such as reaching a waypoint or route recalculation) rather than continuous data streams, maintaining precision while reducing overall data transmission volume.

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS10061625B2Navigation application programming interface to accommodate multiple waypoint routing
Publication Date: 2018.08.28 GOOGLE LLC
  • US10061625B2 patent drawing
  • US10061625B2 patent drawing
  • US10061625B2 patent drawing

AI summary

Navigation application programming interfaces that can be used to embed navigation services in software applications are provided. In one embodiment, the application programming interface includes a first set of instructions specifying one or more first parameters to control the implementation of a navigation service by the software application. The navigation service can provide navigation information to a user of the software application. The application programming interface can include a second set of instructions specifying one or more second parameters to control interaction with a navigation engine provided by the navigation data provider via the application programming interface. The application programming interface can further include a waypoint function specified as part of the first instructions operable to set a plurality of waypoints for a navigation route. The application programming interface can be operable to receive a multi-waypoint navigation route determined based on the plurality of waypoints.