The present invention relates to a method for teleoperating a vehicle. The present invention moreover relates to a corresponding device, to a corresponding computer program, as well as to a corresponding storage medium.
(Semi-)autonomous vehicles according to the related art at present still include a vehicle driving interface (“driver work station”) and at present still require a person who is fit to drive and authorized to drive the vehicle as a vehicle occupant, who is able to take over driving the vehicle if necessary. Depending on the degree of automation and technological progress, it is planned in the future to dispense with the need for a driver who is fit to drive to take over within the vehicle in critical situations in sections or for the entire driving route. To nonetheless be able to circumvent system imponderables or shortcomings, numerous research projects are working on the so-called teleoperated driving (ToD) against this background. During ToD, the driving task and/or the vehicle may be intermittently supported and/or entirely taken over by an external user in a control center, the so-called operator, by way of remote control for the management of technical shortcomings of the (semi-)autonomous driving system or challenging scenarios, such as detours via alternative or unconventional roadways or routes, or the like. The vehicle and the control center or its operators are connected to one another for this purpose by a mobile communication network having a low latency and a high data rate.
U.S. Pat. No. 9,494,935 B2 describes computer devices, systems and methods for remotely operating an autonomous passenger vehicle. When an autonomous vehicle encounters unexpected surroundings, such as a road construction site or an obstacle, not suitable for autonomous operation, the vehicle sensors may collect data about the vehicle and the unexpected surroundings, including images, radar and LIDAR data, etc. The collected data may be transmitted to a remote operator. The remote operator may remotely operate the vehicle manually or issue instructions to the autonomous vehicle, which are to be carried out by different vehicle systems. The collected data transmitted to the remote operator may be optimized to save bandwidth, for example by transmitting a limited subset of the collected data.
A vehicle is described in U.S. Pat. No. 9,767,369 B2 which may receive one or multiple image(s) of surroundings of the vehicle. The vehicle may also receive a surroundings map. The vehicle may also compare at least one feature in the images to one or multiple feature(s) in the map. The vehicle may also identify a certain area in the one or the multiple image(s), which corresponds to a portion of the map situated at a threshold distance from the one or the multiple feature(s). The vehicle may also compress the one or the multiple image(s) or sensor signal(s) to record a smaller number of details in the recording areas than in the given area. The vehicle may also provide the compressed images to a remote system and, in response thereto, receive operating instructions from the remote system.
Systems and methods described in U.S. Pat. No. 9,465,388 B1 enable an autonomous vehicle to request assistance from a remote operator when the confidence of the vehicle in the operation is low, or a technical problem or a technical shortcoming or an external situation makes it necessary. An exemplary method encompasses the operation of an autonomous vehicle in a first autonomous mode. The method may also encompass the identification of a situation in which a confidence level of an autonomous operation in the first autonomous mode is below a threshold level. The method may furthermore encompass the transmission of a request for assistance to a remote assistant, the request including sensor data representative of a portion of surroundings of the autonomous vehicle. The method may additionally encompass the reception of a response from the remote assistant, the response indicating a second autonomous operating mode. The method may also cause the autonomous vehicle to operate in the second autonomous operating mode according to the response from the remote assistant.
U.S. Pat. No. 9,720,410 B2 describes a further method for remotely assisting autonomous vehicles in predetermined situations.
The present invention provides a method for teleoperating a vehicle, a corresponding device, a corresponding computer program, as well as a corresponding machine-readable storage medium.
One advantage of example embodiments of the present invention lies in the option it opens up of an (optimized) assignment of operators for the teleoperated driving to automated vehicles which request or are already using this service, and the dynamic change of these operators. For this purpose, existing communication resources and ToD service providers are gathered and evaluated to be able to ensure an efficient use of these resources. By using redundant transmission paths and mediation between the ToD service providers, low latencies may be ensured, which enables a seamless change of the ToD service providers. In this way, it is possible to carry out teleoperated driving even under difficult boundary conditions or to operate preferably many vehicles simultaneously by a corresponding distribution among available ToD service providers. A dispatcher is used for the initial mediation, taking the available resources necessary for the driving operation into consideration, between the vehicle and the operator, and for the handover of vehicles already being controlled between the different service providers.
Certain measures described herein allow advantageous refinements of and improvements present invention. It may be provided, for example, that the service companies each operate one or multiple (locally distributed or competence- and task-oriented) control center(s), whose operators are assigned by a (automated or human or a combination of both) control center dispatcher. The dispatcher manages all resources and capabilities within his or her control center(s) and reports these, together with their availability, to the dispatcher service or services. Depending on the size of the company (number of the control centers), company-internal dispatcher functions may also be implemented, specifically when fleet operators operate their own control center network. In this way, a scalable ToD approach is created, which is able to process simultaneous ToD requests for a plurality of vehicles in a time-efficient manner as needed by utilizing dispatcher services (using a centralized or also in combination with a distributed or hierarchical dispatcher architecture). In the process, ToD requests and ToD operators are brought together by analyzing, managing and cooperatively using different transmission paths, existing ToD service provider resources and ToD operators, the necessary ToD assistance, and the ToD qualification.
According to one further aspect of the present invention, it may be provided that the second operator requests the control function from the first operator for the handover of the control function from a first operator to a second operator, the handover only being carried out after the second operator has completely taken over the control function. One advantage of this specific embodiment is the implementation of a seamless change of the operator even while a driving maneuver is ongoing, to be able to use the matching operator having an appropriate release level (suitability) as a function of the required ToD driving situation, hazard level, and knowledge of the location.
Exemplary embodiments of the present invention are shown in the figures and are described in greater detail below.
For this purpose, a ranking of dispatchers 20 is transmitted to vehicle 11 at the latest at the start of the automated driving function. For safety reasons, basic principles of redundancy are employed in the process, for example by using multiple lists and dispatcher service centers. It is also possible for multiple such lists to exist, which are used as a function of the error criticality to deliberately establish a direct link in emergencies. These lists are regularly updated, e.g., also in accordance with the vehicle position and the availability of the dispatchers.
If vehicle 11, during the driving operation, enters a non-specified state or if a technical shortcoming or the need for remote assistance by the vehicle is established, it transmits the request to transfer the driving function to an operator 12 belonging to a ToD service provider to the first dispatcher 20 from this list. This request typically includes the following pieces of information:
During the classification of the transmission channels (typing) and the associated establishment of their suitability for a method according to the present invention, pieces of information about the latency, bandwidth, effective data throughput (dependent on the bit error rate) and network coverage of the transmission medium in the entire area of use are desirable. The quality of service of the transmission channel ascertained in the vehicle may also be used accordingly.
Dispatcher 20 relays the handover of ToD inquiries from vehicles 11 to ToD service providers 18 and their suitable operators 12. During an ongoing driving maneuver, dispatcher 20 may additionally enable a handover both between ToD service providers 18 and between operators 12 to enable their seamless change, and to minimize the latency itself during the teleoperation of a mobile vehicle 11. For safety reasons, all operations preferably take place using redundant transmission paths. In addition, dispatcher 20 controls the cooperative use of transmission channels by coordination among all instantaneous participants. To evaluate the transmission capacities, a classification of the transmission channels is desirable. Furthermore, the resources required may be determined as a function of the type of control function 14. In this way, it is possible to ascertain whether it is even feasible to carry out a control, or whether even multiple controls are possible simultaneously. After the identification of the transmission resources required for the imminent control functions, taking features, such as technology (latency), bandwidth and redundancy (functional safety) into consideration, these may be allocated by the dispatcher across systems, e.g., using a shared database, and assigned to vehicle 11 and ToD service providers 18 for implementing the driving maneuver or the driving function.
As a function of the above-mentioned properties and the availability or the training of operators 12, either entire driving maneuvers in real time, up to certain speeds, or only the release of individual actions or, if necessary, only the transmission of trajectories for a vehicle 11 or only a monitoring of pieces of sensor information is possible for a ToD operation. As a function of the above-mentioned properties and the availability or the training of operators 12, the different ToD operations may possibly be implemented simultaneously for different vehicles or only sequentially in accordance with a prioritization by dispatchers.
All actions described here should take place taking the functional safety [FuSa] into consideration. A recording of the implemented actions, as it is practiced in the aviation industry with the aid of a so-called black box, for example, should take place in vehicle 11 or also additionally at ToD service provider 18.
The regular mode of operation of a dispatcher 20 during the coupling of a vehicle (11) with a ToD operator 12 shall now be explained with additional reference to
A handover between service providers 18, e.g., because a vehicle 11 identifies the change into a new area of responsibility of a service provider 18, could then take place as follows:
A handover between ToD operators 12, e.g., because a ToD operator 12 is not able to complete his or her present task, e.g., because an operator does not have the necessary release level (qualification level), or because the vehicle is leaving the area of responsibility of the ToD operator, is thus as follows on this basis:
The behavior in special situations warrants attention. For example, if two semi-automated or even autonomous vehicles 11, e.g., when encountering one another on a narrow road, block one another, this blockage (deadlock) may be resolved by both vehicles 11 transmitting a ToD request, operators 12 establishing contact with one another, and resolving the situation. The establishment of contact with another operator 12 is possible, for example, by the first operator 12, e.g., indicating the official license number of the other vehicle 11, transmitting a contact request via dispatcher 20.
It may become necessary to manage requests in queues, comparable to the “on-hold loops” known from call centers, in the event of a lack of availability of ToD operators 12 or an overload of the transmission channel or other resources. A processing of requests deviating from the order in which they were received may be advisable, for example, in the event of imminent danger, e.g., on expressways at high speed or in emergencies, for the dispersion of traffic jams through tactical action based on the positions of the individual vehicles 11, in light of the scope and complexity of the imminent intervention or as a function of the type of the acquired service (premium, standard, basic, eco, etc.).
To save transmission bandwidth and resources at the ToD service provider 18, (transmission) resources may be pooled under predefined boundary conditions. It is also possible that recently carried out driving maneuvers are reused in the same place in a partially automated manner. This applies when, for example in the case of jammed traffic, e.g., due to an accident, an obstacle which was already overcome by another teleoperated vehicle 11 was successfully circumnavigated, and one of the following vehicles in the same situation requires the same assistance, given the circumstances and system properties. For example, a trajectory may thus be recorded by a ToD operator (12) during the remotely controlled driving and made available to other ToD operators 12 or semi-automatedly following vehicles 11. Here as well, the request to have multiple vehicles 11 consecutively follow one another to form a convoy (platoon) for pooling requests, which should then all follow an identical trajectory to circumnavigate the hazardous situation, is a suitable method.
Example embodiments of the present invention are further described in the following paragraphs.
Paragraph 1. A method (10) for teleoperating a vehicle (11), characterized by the following features:
Paragraph 2. The method (10) as recited in Paragraph 1, characterized by the following features:
Paragraph 3. The method (10) as recited in Paragraph 2, wherein the service offer encompasses at least one of the following:
Paragraph 4. The method (10) as recited in Paragraph 3, characterized by the following features:
Paragraph 5. The method (10) as recited in Paragraph 4, wherein the assignment of the operators (12) of the control centers (19) takes place based on at least one of the following criteria:
Paragraph 6. The method (10) as recited in Paragraph 4 or 5, characterized by the following features:
Paragraph 7. The method (10) as recited in Paragraph 4, 5 or 6, characterized by the following features:
Paragraph 8. The method (10) as recited in one of Paragraphs 1 through 6, characterized by the following features:
Paragraph 9. A computer program, which is configured to carry out the method (10) as recited in one of Paragraphs 1 through 7.
Paragraph 10. A machine-readable storage medium on which the computer program as recited in Paragraph 8 is stored.
Paragraph 11. A device (20), which is configured to carry out the method (10) as recited in one of Paragraphs 1 through 7.
Number | Date | Country | Kind |
---|---|---|---|
102019207547.9 | May 2019 | DE | national |
The present application claims the benefit under 35 U.S.C. § 119 of German Patent Application No. DE 102019207547.9 filed on May 23, 2019, which is expressly incorporated herein by reference in its entirety.