US 12,227,173 B2
Secondary fallback software stack for autonomous vehicle
Juan Fasola, San Francisco, CA (US); Eugene Lo, Redwood City, CA (US); Xiaoyu Zhou, San Francisco, CA (US); and Shreyans Kushwaha, Burlingame, CA (US)
Assigned to GM Cruise Holdings LLC, San Francisco, CA (US)
Filed by GM Cruise Holdings LLC, San Francisco, CA (US)
Filed on Jun. 15, 2022, as Appl. No. 17/841,494.
Prior Publication US 2023/0406293 A1, Dec. 21, 2023
Int. Cl. B60W 30/09 (2012.01); B60W 50/02 (2012.01); B60W 50/035 (2012.01); B60W 50/038 (2012.01)
CPC B60W 30/09 (2013.01) [B60W 50/0205 (2013.01); B60W 50/035 (2013.01); B60W 50/038 (2013.01)] 8 Claims
OG exemplary drawing
 
1. A method comprising:
determining, by a primary planner of an autonomous vehicle, a first action for the autonomous vehicle using a first process;
determining, by a fallback planner of the autonomous vehicle independent of the primary planner, an alternative action for the autonomous vehicle using a second process nonoverlapping with the first process, wherein the alternative action includes at least stopping the autonomous vehicle;
sending, by a multiplexer of a common control system of the autonomous vehicle, an indication of the alternative action for actuators to use to cause the autonomous vehicle to navigate in response to a faulty condition associated with the primary planner, wherein the faulty condition is the primary planner failing to predict a trajectory for other traffic participants in an environment of the autonomous vehicle; and
computing, by the fallback planner, a collision-free path for the autonomous vehicle responsive to a determination of an area at which the autonomous vehicle stopped after performing the alternative action fails to satisfy one or more area criteria.