Autonomous Vehicle Planner Interface for Seamless Control Handoffs

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Autonomous vehicles face challenges in managing and seamlessly transitioning between different planners, leading to inconsistent data streams and operational issues in vehicle controls, particularly during transitions and in degraded states.

Innovation Solution

A unified interface is introduced between the planning and control stacks to manage communications, ensuring a single data stream to the control stack, handle inconsistencies, and facilitate smooth transitions between planners, including primary and fallback managers.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If multiple planners are used in the autonomous vehicle system, then the system's adaptability and functionality are improved, but the complexity of managing transitions between planners increases

Engineering Contradiction:
Improveplanner functionalityVSAvoidtransition management
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

A unified interface is introduced as an intermediary component between multiple planners and the control stack. This interface receives plans from different planners (e.g., primary planner, fallback planner), standardizes their data formats, and manages transitions seamlessly. The interface acts as a mediator that handles the complexity of coordinating multiple planners, allowing each planner to focus on its specific function while the interface ensures consistent data stream delivery to the control stack.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If seamless transitions between planners are implemented, then the reliability of vehicle operation is improved, but the complexity of the control system increases

Engineering Contradiction:
Improveoperational consistencyVSAvoidcontrol system structure
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent merges the transition management functionality into a unified interface that consolidates multiple planner outputs into a single standardized data stream. Instead of having separate transition management mechanisms for each planner pair, the system combines all planner communications through one interface that handles switching, validation, and data formatting. This merging approach improves reliability by ensuring consistent transition protocols while managing complexity through centralization.

Inventive Principle:
Principle #5Merging (Combining)

3Stability of the object's composition

If a unified interface is introduced to manage multiple planners, then the consistency of data streams to the control stack is improved, but the complexity of the interface management increases

Engineering Contradiction:
Improvedata stream consistencyVSAvoidinterface structure
Core Design Contradiction:
Stability of the object's compositionVSDevice complexity

Solution Approach 1:

The unified interface enforces homogeneity by standardizing all planner output data streams into a common format and protocol. Regardless of which planner generates the plan (primary, fallback, or other specialized planners), the interface ensures that all data received by the control stack follows the same structure, validation rules, and communication protocols. This homogenization approach guarantees data stream consistency while the interface internally manages the complexity of adapting different planner formats to the standard.

Inventive Principle:
Principle #33Homogeneity

Data Source

PatentUS12474703B2Unified interface between a control system and planners of an autonomous vehicle
Publication Date: 2025.11.18 GM CRUISE HOLDINGS LLC
  • US12474703B2 patent drawing
  • US12474703B2 patent drawing
  • US12474703B2 patent drawing

AI summary

Autonomous vehicles may have different specialized primary planners in the vehicle planning stack that each can generate a plan for the vehicle control stack. For instance, one primary planner may be used for the vehicle to drive forward, and another primary planner may be used for the vehicle to drive in reverse. Additionally, a fallback planner may be implemented to allow the autonomous vehicle to drive in a degraded state. A unified interface is provided between the planning stack and the control stack to manage communications between the different planners in the planning stack and the control stack.