# US 11,999,365 B2 · Method for carrying out a start-up process for an at least semi-automated vehicle > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 11,999,365 B2 - Document ID: US11999365B2 - Status: Granted - Kind: B2 - Application number: 17/835,580 - Filed: 2022-06-08 - Published: 2022-12-15 - Granted: 2024-06-04 - Earliest claimed: 2021-06-14 - Assignees: Robert Bosch GmbH - Applicants: Robert Bosch GmbH - Inventors: Andreas Schultz; Lukas Oppolzer; Selina Meier; Tobias Hofmann; Nils Pletschen; Thomas Brettschneider - Web page: https://patentgrep.com/patent/US11999365B2 ## CPC - B60W 30/18027: {Drive off, accelerating from standstill} - B60W 50/035: Bringing the control units into a predefined state, e.g. giving priority to particular actuators - B60W 50/0205: {Diagnosing or detecting failures; Failure detection models} - B60W 60/001: {Planning or execution of driving tasks} - B60W 2520/10: Longitudinal speed - B60W 2554/60: Traversable objects, e.g. speed bumps or curbs - B60W 2720/10: Longitudinal speed - B60W 2720/24: Direction of travel - B60W 2754/30: Longitudinal distance - B60W: CONJOINT CONTROL OF VEHICLE SUB-UNITS OF DIFFERENT TYPE OR DIFFERENT FUNCTION; CONTROL SYSTEMS SPECIALLY ADAPTED FOR HYBRID VEHICLES; ROAD VEHICLE DRIVE CONTROL SYSTEMS FOR PURPOSES NOT RELATED TO THE CONTROL OF A PARTICULAR SUB-UNIT ## Abstract A method for carrying out a start-up process of an at least semi-automated vehicle. The method includes: recognizing at least one unsuccessful start-up process using a first set of drive parameters; reporting the unsuccessful start-up process to a control system; receiving changed driving-related boundary conditions from the control system; ascertaining at least one changed drive parameter from the changed driving-related boundary conditions; and repeating the start-up process at least once, using the at least one changed drive parameter. ## Claims ### Claim 1 A method for carrying out a start-up process of an at least semi-automated vehicle, comprising the following steps: recognizing at least one unsuccessful start-up process using a first set of drive parameters; reporting the unsuccessful start-up process to a control system; receiving changed driving-related boundary conditions from the control system; ascertaining at least one changed drive parameter from the changed driving-related boundary conditions; and repeating the start-up process at least once, using the at least one changed drive parameter. ### Claim 2 (depends on 1) The method as recited in claim 1, wherein the driving-related boundary conditions are as follows: available residual distance of the at least semi-automated vehicle in the longitudinal direction, permissible maximum speed of the at least semi-automated vehicle in the longitudinal direction, and driving direction of the at least semi-automated vehicle. ### Claim 3 (depends on 2) The method as recited in claim 2, wherein the at least one-time repetition of the start-up process is carried out with a changed driving direction. ### Claim 4 (depends on 2) The method as recited in claim 2, wherein a changed permissible drive power is calculated with a changed residual distance and/or a changed permissible maximum speed, and a new start-up process is carried out when the changed drive power is greater than in the unsuccessful start-up process. ### Claim 5 (depends on 4) The method as recited in claim 4, wherein the drive power is incrementally increased in a defined manner until a maximum value is reached. ### Claim 6 (depends on 1) The method as recited in claim 1, wherein a new start-up process is started when a predefined driving direction has changed, and the predefined driving direction previously was a reason for the unsuccessful start-up process. ### Claim 7 (depends on 1) The method as recited in claim 1, wherein a new start-up process is started when a changed residual distance takes on a larger value, and the residual distance was a reason for the unsuccessful start-up process. ### Claim 8 (depends on 1) The method as recited in claim 1, wherein a new start-up process is started when the predefined maximum speed takes on a larger value, and the maximum speed was a reason for the unsuccessful start-up process. ### Claim 9 (depends on 1) The method as recited in claim 1, wherein, in the case of the unsuccessful start-up process, it is reported to the higher-level control system due to which driving-related boundary condition the start-up process was unsuccessful. ### Claim 10 (depends on 9) The method as recited in claim 9, wherein a safeguarding of the semi-automated vehicle is initiated by the higher-level control system. ### Claim 11 A device configured to carry out a start-up process of an at least semi-automated vehicle, the device configured to: recognize at least one unsuccessful start-up process using a first set of drive parameters; report the unsuccessful start-up process to a control system; receive changed driving-related boundary conditions from the control system; ascertain at least one changed drive parameter from the changed driving-related boundary conditions; and repeat the start-up process at least once, using the at least one changed drive parameter. ### Claim 12 A non-transitory computer-readable data medium on which is stored a computer program including program code for carrying out a start-up process of an at least semi-automated vehicle, the program code, when executed by a computer, causing the computer to perform the following steps: recognizing at least one unsuccessful start-up process using a first set of drive parameters; reporting the unsuccessful start-up process to a control system; receiving changed driving-related boundary conditions from the control system; ascertaining at least one changed drive parameter from the changed driving-related boundary conditions; and repeating the start-up process at least once, using the at least one changed drive parameter.