METHOD AND DEVICE FOR DETERMINING EMERGENCY TRAJECTORIES AND FOR OPERATING AUTOMATED VEHICLES

Abstract

A method and a device for determining emergency trajectories. A method and a device for operating an automated vehicle are also described.

Claims

1-9. (canceled)

10. A method for determining emergency trajectories, comprising the following steps: receiving route data values, which represent route information of automated vehicles; determining emergency trajectories for each of the automated vehicles, as a function of the route information of the automated vehicles, the emergency trajectories each maintaining a temporal and/or local predefined minimum distance with respect to one another; and transferring the emergency trajectories to the automated vehicles, for operating the automated vehicles.

11. The method as recited in claim 10, wherein the steps of the method are cyclically repeated with a predefined cycle duration, until route data values are no longer received.

12. The method as recited in claim 10, wherein further comprising: receiving surroundings data values, the surroundings data values representing surroundings of the automated vehicles, wherein the determination of the emergency trajectories additionally taking place as a function of the surroundings of the automated vehicles.

13. A device, comprising: a server configured to determine emergency trajectories, the server configured to: receive route data values, which represent route information of automated vehicles; determine emergency trajectories for each of the automated vehicles, as a function of the route information of the automated vehicles, the emergency trajectories each maintaining a temporal and/or local predefined minimum distance with respect to one another; and transfer the emergency trajectories to the automated vehicles, for operating the automated vehicles.

14. A non-transitory machine-readable memory medium on which is stored a computer program for determining emergency trajectories, the computer program, when executed by a computer, causing the computer to perform the following steps: receiving route data values, which represent route information of automated vehicles; determining emergency trajectories for each of the automated vehicles, as a function of the route information of the automated vehicles, the emergency trajectories each maintaining a temporal and/or local predefined minimum distance with respect to one another; and transferring the emergency trajectories to the automated vehicles, for operating the automated vehicles.

15. A method for operating an automated vehicle, comprising the following steps: transferring route data values to an external server, the route data values representing route information, as a function of a normal trajectory of the automated vehicle; receiving an emergency trajectory from the external server, the emergency trajectory being determined by the external service by performing: receiving the route data values, and further route data values from other automated vehicles which represent route information of the other automated vehicles, determining emergency trajectories for each of the automated vehicles, as a function of the route information of the automated vehicles, the emergency trajectories each maintaining a temporal and/or local predefined minimum distance with respect to one another, and transferring the emergency trajectories to the automated vehicles, for operating the automated vehicles; checking a functionality of a communication link of the automated vehicle, the communication link being at least configured to receive the emergency trajectory; and operating the automated vehicle using a normal trajectory or using the emergency trajectory, as a function of the functionality of the communication link.

16. The method as recited in claim 15, wherein the steps of the method are cyclically repeated, and the operation of the automated vehicle takes place using a normal trajectory or using a most recently received emergency trajectory.

17. A device, comprising: a control unit configured to operate an automated vehicle, the control unit configured to: transfer route data values to an external server, the route data values representing route information, as a function of a normal trajectory of the automated vehicle; receive an emergency trajectory from the external server, the external service configured to: receive the route data values, and further route data values from other automated vehicles which represent route information of the other automated vehicles, determine emergency trajectories for each of the automated vehicles, as a function of the route information of the automated vehicles, the emergency trajectories each maintaining a temporal and/or local predefined minimum distance with respect to one another, and transfer the emergency trajectories to the automated vehicles, for operating the automated vehicles; check a functionality of a communication link of the automated vehicle, the communication link being at least configured to receive the emergency trajectory; and operate the automated vehicle using a normal trajectory or using the emergency trajectory, as a function of the functionality of the communication link.

Description

BRIEF DESCRIPTION OF THE DRAWINGS

[0028] Exemplary embodiments of the present invention are shown in the figures and are described in greater detail in the following descriptions.

[0029] FIG. 1 shows one exemplary embodiment of the method according to the present invention for determining emergency trajectories in the form of a flowchart.

[0030] FIG. 2 shows one exemplary embodiment of the method according to the present invention for operating an automated vehicle in the form of a flowchart.

[0031] FIG. 3 shows an exemplary embodiment of the cooperation of the two methods in the form of a flowchart.

DETAILED DESCRIPTION OF EXAMPLE EMBODIMENTS

[0032] FIG. 1 shows one exemplary embodiment of a method 300 for determining 320 emergency trajectories.

[0033] In step 301, method 300 starts.

[0034] In step 310, route data values, which represent route information of automated vehicles, are received.

[0035] In one specific embodiment, step 320 follows. In an alternative specific embodiment, step 315 follows.

[0036] In step 315, surroundings data values are received, the surroundings data values representing surroundings of the automated vehicles.

[0037] In further alternative specific embodiments, first step 315 follows, and thereafter step 310, or steps 310 and 315 are at least partially carried out simultaneously.

[0038] In step 320, emergency trajectories are determined for each of the automated vehicles, as a function of the route information of the automated vehicles, in such a way that the emergency trajectories each maintain a temporal and/or local predefined minimum distance with respect to one another. In one further specific embodiment, the emergency trajectories are additionally determined as a function of the surroundings of the automated vehicles.

[0039] In step 330, the emergency trajectories are transferred to the automated vehicles, for operating the automated vehicles. In one specific embodiment, step 340 follows. In one alternative specific embodiment, steps 310, 320, 330 of method 300 are cyclically repeated, in particular with a predefined cycle duration, until route data values are no longer received.

[0040] In step 340, method 300 ends.

[0041] FIG. 2 shows one exemplary embodiment of a method 400 for operating 440 an automated vehicle.

[0042] In step 401, method 400 starts.

[0043] In step 410, route data values are transferred to an external server, the route data values representing route information, as a function of a normal trajectory of the automated vehicle.

[0044] In step 420, an emergency trajectory is received from the external server, the emergency trajectory being determined with the aid of one specific embodiment of method 300.

[0045] In step 430, a functionality of a communication link of the automated vehicle is checked, the communication link being at least designed to receive the emergency trajectory.

[0046] In step 440, the automated vehicle is operated with the aid of the normal trajectory or with the aid of the emergency trajectory, as a function of the functionality of the communication link. In one alternative specific embodiment, steps 410, 420, 430 of method 400 are cyclically repeated, the automated vehicle being operated with the aid of the normal trajectory or with the aid of the most recently received emergency trajectory.

[0047] In step 450, method 400 ends.

[0048] FIG. 3 shows one exemplary embodiment of the cooperation of method 300 for determining 320 emergency trajectories and of method 400 for operating 440 an (identified) automated vehicle.

[0049] In step 410, route data values are transferred from the (identified) automated vehicle to an external server, the route data values representing route information, as a function of a normal trajectory of the (identified) automated vehicle.

[0050] In step 310, the route data values from the (identified) automated vehicle as well as further route data values, which represent route information from (further) automated vehicles, are received.

[0051] In step 320, emergency trajectories (i.e., also an identified emergency trajectory for the identified automated vehicle, which in step 410 transferred its route data values) are determined for each of the automated vehicles, as a function of the route information of the automated vehicles, in such a way that the emergency trajectories in each case maintain a temporal and/or local predefined minimum distance with respect to one another.

[0052] In step 330, the emergency trajectories are transferred to the automated vehicles (i.e., the identified emergency trajectory is also transferred to the identified automated vehicle, which in step 410 transferred its route data values), for operating the automated vehicles.

[0053] In step 420, the emergency trajectory is received from the external server.

[0054] In step 430, a functionality of a communication link of the (identified) automated vehicle is checked, the communication link being at least designed to receive the emergency trajectory.

[0055] In step 440, the (identified) automated vehicle is operated with the aid of the normal trajectory or with the aid of the (identified) emergency trajectory, as a function of the functionality of the communication link.