Autonomous Vehicle Fallback Architecture with Partial Redundancy
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Autonomous vehicles face challenges in maintaining driving capabilities due to sensor or component failures, which can be exacerbated by size, cost, and redundancy constraints, necessitating efficient fallback configurations for partial redundancy in sensor, compute, and power systems.
Innovation Solution
The implementation of a vehicle architecture with partially redundant sensor, compute, and power systems, featuring distinct operating domains with fallback modes, where each domain has a set of sensors and computing subsystems that can independently process data and power critical vehicle loads, allowing the vehicle to continue operating safely even with component failures.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If complete redundancy of every component and subsystem is implemented, then reliability is improved, but device complexity and cost increase
Solution Approach 1:
The system divides sensors and computing subsystems into distinct operating domains (first operating domain with first set of sensors and first computing subsystem, second operating domain with second set of sensors and second computing subsystem). This segmentation allows partial redundancy where each domain can independently operate, providing reliability without requiring complete redundancy of all components.
Solution Approach 2:
The patent implements partial redundancy rather than complete redundancy. Each computing subsystem is configured to process sensor data from its associated sensors independently, and only one computing subsystem is needed to control the driving system in fallback mode. This partial action approach provides sufficient reliability for safe operation without the excessive complexity of full redundancy.
2Reliability
If complete redundancy of every component and subsystem is implemented, then reliability is improved, but cost increases
Solution Approach 1:
By segmenting the system into distinct operating domains with associated sensors and computing subsystems, the patent enables partial redundancy that maintains reliability while reducing the number of redundant components needed, thereby lowering manufacturing costs.
Solution Approach 2:
The patent applies partial redundancy where each computing subsystem can independently process sensor data from its associated sensors. This approach provides sufficient reliability for safe fallback operation without duplicating all components, thus reducing manufacturing costs compared to complete redundancy.
3Reliability
If sensor suites are expanded to provide complete redundancy, then reliability is improved, but vehicle size increases
Solution Approach 1:
The system segments sensors into different operating domains with associated computing subsystems. Each domain can independently operate with its own sensor suite, providing reliability without requiring duplicate sensor suites throughout the vehicle, thus avoiding excessive vehicle size increase.
Solution Approach 2:
The patent implements partial redundancy where each computing subsystem processes sensor data from its associated sensors independently. This approach provides sufficient sensor coverage and reliability for safe fallback operation without expanding the vehicle to accommodate complete redundancy of all sensor suites.
Data Source
AI summary
The technology relates to partially redundant equipment architectures for vehicles able to operate in an autonomous driving mode. Aspects of the technology employ fallback configurations, such as two or more fallback sensor configurations that provide some minimum amount of field of view (FOV) around the vehicle. For instance, different sensor arrangements are logically associated with different operating domains of the vehicle. Fallback configurations for computing resources and/or power resources are also provided. Each fallback configuration may have different reasons for being triggered, and may result in different types of fallback modes of operation. Triggering conditions may relate, e.g., to a type of failure, fault or other reduction in component capability, the current driving mode, environmental conditions in the vicinity of vehicle or along a planned route, or other factors. Fallback modes may involve altering a previously planned trajectory, altering vehicle speed, and/or altering a destination of the vehicle.