CN113759914A

CN113759914A - Remote control request processing method, related device and cloud server

Info

Publication number: CN113759914A
Application number: CN202111049542.4A
Authority: CN
Inventors: 郑鹏杰; 孙庆瑞; 冯靖超; 夏黎明; 李震宇; 王云鹏; 陈竞凯; 王亮; 陈卓
Original assignee: Beijing Baidu Netcom Science and Technology Co Ltd
Current assignee: Beijing Baidu Netcom Science and Technology Co Ltd
Priority date: 2021-09-08
Filing date: 2021-09-08
Publication date: 2021-12-07
Anticipated expiration: 2041-09-08
Also published as: CN113759914B

Abstract

The disclosure provides a remote control request processing method and device, electronic equipment, a computer readable storage medium, a computer program product, a cloud server, an automatic driving vehicle and a cloud cockpit, and relates to the technical fields of automatic driving, remote control, intelligent transportation and the like. The method comprises the following steps: determining a target vehicle initiating a request according to the received remote control request; determining a designated remote cockpit corresponding to the key guarantee identifier in response to the association of the key guarantee identifier with the target vehicle, wherein the association relationship between the target vehicle and the key guarantee identifier is determined based on a travel plan and/or an actual security level of the target vehicle; and issuing a first remote control instruction to a specified remote control cabin. According to the embodiment, whether key guarantee identification needs to be associated with the vehicle is determined based on the travel plan and/or the actual security level of the vehicle, and the designated remote cockpit is distributed to the vehicle according to the key guarantee identification, so that the safety guarantee capability of the vehicle is further improved.

Description

Remote control request processing method, related device and cloud server

Technical Field

The present disclosure relates to the field of data processing technologies, and in particular, to the field of technologies such as autonomous driving, remote driving, and intelligent transportation, and in particular, to a method and an apparatus for processing a remote control request, an electronic device, a computer-readable storage medium, a computer program product, a cloud server, an autonomous vehicle, and a cloud deck.

Background

With the development of the automatic driving technology, an auxiliary automatic driving technology that can be used for an unmanned or manned vehicle has been developed in succession, but the current auxiliary automatic driving technology has been difficult to cope with complicated traffic situations, and thus a remote driving technology by remotely controlling the vehicle has been developed.

How to give consideration to various scenes and requirements which may be faced under the application of remote driving technology and provide better remote control service is a problem to be solved urgently by technical personnel in the field.

Disclosure of Invention

The embodiment of the disclosure provides a remote control request processing method and device, electronic equipment, a computer readable storage medium and a computer program product.

In a first aspect, an embodiment of the present disclosure provides a remote control request processing method, including: determining a target vehicle initiating a request according to the received remote control request; determining a designated remote control cabin corresponding to the key guarantee identification in response to the key guarantee identification associated with the target vehicle; the method comprises the following steps that an incidence relation between a target vehicle and a key guarantee identifier is determined based on a trip plan and/or an actual security level of the target vehicle; issuing a first remote control instruction to a specified remote control cabin; the first remote control instruction is used for indicating a designated remote control cabin to remotely control the target vehicle.

In a second aspect, an embodiment of the present disclosure provides a remote control request processing apparatus, including: a remote control request receiving unit configured to determine a target vehicle that initiates a request according to a received remote control request; a designated remote cockpit determination unit configured to determine a designated remote cockpit corresponding to a key safeguard identification in response to the target vehicle being associated with the key safeguard identification; the method comprises the following steps that an incidence relation between a target vehicle and a key guarantee identifier is determined based on a trip plan and/or an actual security level of the target vehicle; a first remote control instruction issuing unit configured to issue a first remote control instruction to a specified remote cockpit; the first remote control instruction is used for indicating a designated remote control cabin to remotely control the target vehicle.

In a third aspect, an embodiment of the present disclosure provides an electronic device, including: at least one processor; and a memory communicatively coupled to the at least one processor; wherein the memory stores instructions executable by the at least one processor to enable the at least one processor to implement the remote control request processing method as described in any implementation manner of the first aspect when executed.

In a fourth aspect, the disclosed embodiments provide a non-transitory computer-readable storage medium storing computer instructions for enabling a computer to implement the remote control request processing method as described in any implementation manner of the first aspect when executed.

In a fifth aspect, the disclosed embodiments provide a computer program product comprising a computer program, which when executed by a processor is capable of implementing the remote control request processing method as described in any implementation manner of the first aspect.

In a sixth aspect, an embodiment of the present disclosure provides a cloud server, including the electronic device as described in the third aspect.

In a seventh aspect, an embodiment of the present disclosure provides an autonomous vehicle, including:

initiating a remote control request to a cloud server; the cloud server is the cloud server described in the sixth aspect;

receiving a remote control parameter sent by a designated remote control cabin responding to a first remote control instruction sent by a cloud server; the first remote control instruction is issued to a cloud control cabin corresponding to a key guarantee identifier when the cloud server confirms that the automatic driving vehicle which initiates the remote control request is associated with the key guarantee identifier.

In an eighth aspect, the embodiment of the present disclosure provides a cloud cockpit, including:

receiving a first remote control instruction sent by a cloud server; the first remote control instruction is issued to a cloud control cabin corresponding to a key guarantee identifier when the cloud server confirms that the automatic driving vehicle initiating the remote control request is associated with the key guarantee identifier, wherein the cloud server is the cloud server described in the sixth aspect, and the automatic driving vehicle is the automatic driving vehicle described in the seventh aspect;

and issuing remote control parameters to the automatic driving vehicle according to the first remote control instruction.

The remote control request processing method provided by the embodiment of the disclosure comprises the following steps: determining a target vehicle initiating a request according to the received remote control request; determining a designated remote control cabin corresponding to the key guarantee identification in response to the key guarantee identification associated with the target vehicle; the method comprises the following steps that an incidence relation between a target vehicle and a key guarantee identifier is determined based on a trip plan and/or an actual security level of the target vehicle; issuing a first remote control instruction to a specified remote control cabin; the first remote control instruction is used for indicating a designated remote control cabin to remotely control the target vehicle.

Compared with the existing processing mode that each remote control request is processed by each remote control cabin based on an automatic order receiving mode, the method determines whether to associate key guarantee identifications for designating some remote control cabins for the remote control cabins based on the travel plan and/or the actual security level of the vehicles, so that more comprehensive and more effective remote control services are provided for the vehicles associated with the key guarantee identifications by designating the remote control cabins, a new remote control request processing mode is expanded, and more various requirements and scenes can be covered.

It should be understood that the statements in this section do not necessarily identify key or critical features of the embodiments of the present disclosure, nor do they limit the scope of the present disclosure. Other features of the present disclosure will become apparent from the following description.

Drawings

Other features, objects and advantages of the disclosure will become more apparent upon reading of the following detailed description of non-limiting embodiments thereof, made with reference to the accompanying drawings in which:

FIG. 1 is an exemplary system architecture to which the present disclosure may be applied;

fig. 2 is a flowchart of a remote control request processing method according to an embodiment of the disclosure;

fig. 3 is a flowchart of a method for associating key guarantee identifiers with vehicles based on a travel plan in the remote control request processing method provided in the embodiment of the present disclosure;

fig. 4 is a flowchart of a method for associating key safeguard identifications with a vehicle based on an actual security level in a remote control request processing method provided in the embodiment of the present disclosure;

FIG. 5 is a flow chart of a remote driving method for providing other control modes based on an included multi-mode control flag in the remote control request processing method provided by the embodiment of the disclosure;

fig. 6 is a flowchart of an active remote driving control method in the remote control request processing method provided in the embodiment of the present disclosure;

FIG. 7 is a complete remote control request processing timing diagram provided in connection with an actual application according to an embodiment of the present disclosure;

fig. 8 is a block diagram illustrating a remote control request processing apparatus according to an embodiment of the present disclosure;

fig. 9 is a schematic structural diagram of an electronic device adapted to execute a remote control request processing method according to an embodiment of the present disclosure.

Detailed Description

Exemplary embodiments of the present disclosure are described below with reference to the accompanying drawings, in which various details of the embodiments of the disclosure are included to assist understanding, and which are to be considered as merely exemplary. Accordingly, those of ordinary skill in the art will recognize that various changes and modifications of the embodiments described herein can be made without departing from the scope and spirit of the present disclosure. Also, descriptions of well-known functions and constructions are omitted in the following description for clarity and conciseness. It should be noted that, in the present disclosure, the embodiments and features of the embodiments may be combined with each other without conflict.

In the technical scheme of the disclosure, the collection, storage, use, processing, transmission, provision, disclosure and other processing of the personal information of the related user are all in accordance with the regulations of related laws and regulations and do not violate the good customs of the public order.

Fig. 1 illustrates an exemplary system architecture 100 to which embodiments of the remote control request processing method, apparatus, electronic device, and computer-readable storage medium of the present disclosure may be applied.

As shown in fig. 1, the system architecture 100 may include

vehicles

101, 102, 103 supporting remote control functionality (where the vehicle 102 is associated with a key support identification based on travel plans and/or actual security levels in advance), a network 104, and a server 105. The network 104 is used to provide a medium for communication links between the

vehicles

101, 102, 103 and the server 105. Network 104 may include various connection types, such as wired, wireless communication links, or fiber optic cables, to name a few.

The

vehicles

101, 102, 103 interact with the server 105 through the network 104 to receive or transmit messages and the like, for example, the

vehicles

101, 102, 103 transmit real-time vehicle driving states to the server 105 through the network 104, the server 105 transmits control instructions for remote driving to the

vehicles

101, 102, 103 through the network 104, and the like. The

vehicles

101, 102, 103 and the server 105 may be installed with various applications for communicating information therebetween, such as an automatic driving assistance application, a vehicle condition diagnosis application, a remote driving application, and the like.

The

vehicles

101, 102, 103 and the server 105 may be direct hardware products or may be software simulation products. When the

vehicles

101, 102, 103 are hardware products, they may be various vehicles having a function for supporting the implementation of a remote control service; when the

vehicles

101, 102, 103 are software simulation products, they may be implemented as virtual products simulated by running a plurality of software or software modules, or implemented as a single software or software module, and are not limited in this respect. When the server 105 is hardware, it may be implemented as a distributed server cluster composed of multiple servers, or may be implemented as a single server; when the server is software, the server may be implemented as a plurality of software or software modules, or may be implemented as a single software or software module, which is not limited herein.

The server 105 can provide various services through various built-in applications, taking a remote control type application that can provide a remote control request processing service for a vehicle supporting the remote control service as an example, the server 105 can achieve the following effects when running the remote control type application: first, a remote control request initiated by the

vehicles

101, 102, 103 is received through the network 104; determining whether a corresponding vehicle is associated with a key guarantee identifier according to the received remote control request, wherein the association relationship between the vehicle and the key guarantee identifier is determined based on a travel plan and/or an actual security level of the vehicle; determining a designated remote cockpit (a portion of all remote cockpit not shown in FIG. 1) corresponding to the key security identification for the vehicle 102 associated with the key security identification; the

vehicles

101 and 103 which are not associated with the important guarantee marks are distributed to the idle remote control cabins according to a preset distribution mode, so that the remote control cabins distributed with the remote control requests control the

vehicles

101, 102 and 103 in a remote control mode.

The remote control request processing method provided in the subsequent embodiments of the present disclosure is generally performed by the server 105 interposed between the vehicle and the remote cockpit, and accordingly, a remote control request processing device is also generally provided in the server 105.

It should be understood that the number of vehicles, networks, and servers in FIG. 1 is merely illustrative. There may be any number of vehicles, networks, and servers, as desired for implementation.

Referring to fig. 2, fig. 2 is a flowchart of a remote control request processing method according to an embodiment of the disclosure, where the process 200 includes the following steps:

step 201: determining a target vehicle initiating a request according to the received remote control request;

this step is intended to determine, by an execution subject (for example, the server 105 shown in fig. 1) of the remote control request processing method, a vehicle that has initiated a certain vehicle as a target vehicle according to a remote control request, after receiving the remote control request initiated by the vehicle.

The target vehicle may be an unmanned vehicle or a manned vehicle, but the vehicle supports an automatic driving function and a remote control (driving) function, the automatic driving function refers to the ability of a vehicle control center to automatically control the vehicle to run according to collected vehicle conditions without driver control, and the remote control function refers to the ability of the vehicle to receive remote control commands transmitted from the outside and achieve normal driving effects by executing the remote control commands.

According to whether a person is on the target vehicle and whether the automatic driving function is started, the generation mode of the remote control request can be divided into one of the following types: the driver of the target vehicle actively initiates the remote control request through the target vehicle; the second step is as follows: the target vehicle starting the automatic driving function actively generates and initiates the remote control request based on the analysis of the vehicle condition, namely the reason for initiating the remote control request is mainly that the driving capability provided by the current driver or the automatic driving function cannot meet the requirements of the current scene, so that external assistance is required to improve the safety.

Specifically, the remote control request generally includes, in addition to information that enables the receiver to recognize the remote control request as a request for providing a remote control service as a whole, a plurality of different fields for recording different information about the target vehicle or the reason for initiating the remote control request, for example, a field for recording a vehicle identification code, a field for recording an "organization (or an actual group under a predetermined grouping rule)" where the vehicle is located, a field for recording a recent vehicle condition, a field for recording a request initiation type (whether initiated actively by the driver or initiated actively by the automatic driving function), and the like.

Further, in order to improve the efficiency of extracting specific fields or specific information from the remote control request, the fields recording different information may be arranged according to a preset sequence or a fixed sequence, so that the remote control request based on the arrangement may directly extract the desired information at a preset extraction position in the future, without extracting the information of all the fields and then identifying which fields are desired.

Step 202: determining a designated remote control cabin corresponding to the key guarantee identification in response to the key guarantee identification associated with the target vehicle;

on the basis of step 201, this step is intended to further determine a designated remote cockpit corresponding to a key safeguard identification in the case where it is determined by the execution subject that the target vehicle is associated with the key safeguard identification according to the remote control request. In practical situations, the association relationship is usually established between the identity of the designated target vehicle and the important guarantee identity, and for simplifying the description, the identity of the vehicle is not emphasized in the following, and the target vehicle is directly used.

As the name implies, the critical guarantee identification means that critical guarantees need to be made on the driving safety of the vehicle, and therefore the present disclosure determines whether the critical guarantee identification should be associated for a vehicle based on a trip plan of a target vehicle that can affect driving safety and/or an actual security level that characterizes the level of importance. Of course, there may be other influence factors capable of characterizing whether the key guarantee identifier should be associated with the trip plan and the actual security level, and these other influence factors may also participate together according to the influence degree according to the requirement in the actual application scenario, whether the key guarantee identifier should be associated with the trip plan and the actual security level.

That is, the binding relationship between the key safeguard identifier and some remote control cabins is pre-established in the present disclosure, that is, in this step, the binding relationship is referred to as an assigned remote control cabin, and the assigned remote control cabin may be a part of remote control cabins selected from all common remote control cabins and having the capability of meeting specific key safeguard requirements, or may be other remote control cabins different from the common remote control cabins and having the capability of meeting specific key safeguard requirements.

On the contrary, if the target vehicle is not associated with the key safeguard identification, the key safeguard identification is not needed, so that the target vehicle can be directly allocated to the common remote cockpit processing.

Under the condition that the remote control request contains a special field for recording key guarantee identification, determining whether key guarantee identification is associated or not can be directly carried out according to the content recorded in the special field; in the case where the remote control request does not include the dedicated field, the identification code-key guarantee identifier correspondence table maintained by the execution subject may be queried and determined according to the identification code of the target vehicle extracted from the remote control request, and further, the correspondence table may not be directly maintained by the execution subject, but only may be accessed by the execution subject.

Step 203: and issuing a first remote control instruction to a specified remote control cabin.

On the basis of step 202, this step is intended to issue, by the execution main body, a first remote control instruction to the designated remote cockpit, where the first remote control instruction is used to instruct the designated remote cockpit to remotely control the target vehicle, that is, the designated remote cockpit receiving the control instruction provides remote control service for the target vehicle by issuing the control instruction to the designated remote cockpit.

Specifically, the designated remote control cabin generally needs to establish a control connection with the target vehicle according to the first remote control instruction, and after the control connection is established, the designated remote control cabin can transmit subsequent remote control parameters actually used for controlling the target vehicle to the target vehicle, so that the control center of the target vehicle can control the vehicle by executing the received remote control parameters.

Compared with the existing processing mode that each remote control request is processed by each remote control cabin based on an automatic order receiving mode, the remote control request processing method provided by the embodiment of the disclosure determines whether to associate key guarantee identifiers for designating some remote control cabins for the remote control cabins based on travel plans and/or actual security levels of vehicles, so that more comprehensive and more effective remote control services are provided for the vehicles associated with the key guarantee identifiers by designating the remote control cabins, a new remote control request processing mode is expanded, and more various requirements and scenes can be covered.

Referring to fig. 3, fig. 3 is a flowchart of a method for associating a key guarantee identifier with a vehicle based on a travel plan in a remote control request processing method provided in an embodiment of the present disclosure, where the process 300 includes the following steps:

step 301: extracting a travel plan of the target vehicle from the remote control request, or inquiring the travel plan matched with the target vehicle from a pre-uploaded travel plan set;

that is, the trip plan may be input in advance by the driver or the passenger of the target vehicle and synchronized to the execution subject, or may be directly included in the initiated remote control request. The travel plan includes at least a destination for travel, and at least one route to the destination,

step 302: determining a menstruation position set according to a travel plan;

on the basis of step 301, this step is intended to determine, from a route to a destination, the positions to be traversed in the route, i.e. at least one position in the set of positions to be traversed by the route, the different positions to be traversed being arranged in the set in chronological order of the passage, in order to better combine the influence of time differences on the degree of risk of the respective positions.

Step 303: responding to the situation that more than a preset number of the passing positions with more than a preset danger degree exist in the passing position set, and associating a first key guarantee identifier for the target vehicle;

the preset number can be dynamically adjusted according to the number of different menstruation positions in the menstruation position set, so that the condition of travel planning is better combined.

The risk degree is determined based on at least one of terrain complexity, traffic density and driving slowness, and under the condition that the actual risk degree is determined jointly by combining multiple influence factors, the multiple influence factors participating in the joint decision can be weighted according to the weight corresponding to the influence degrees of the multiple influence factors, so that the accuracy of the final conclusion is improved.

Specifically, since the embodiment associates the key safeguard identification for the travel plan based on the travel plan passing through a plurality of dangerous positions, the first key safeguard identification also represents the key safeguard requirement corresponding to the dangerous position caused by the travel.

On the contrary, if there are no more than a preset number of passing positions with more than a preset risk degree in the passing position set, the first key guarantee identifier does not need to be associated with the target vehicle, and the bound designated remote cockpit does not need to be deployed for the target vehicle.

Step 304: and determining the remote cockpit associated with the high drivability label as the designated remote cockpit corresponding to the first key guarantee identifier.

Wherein the high drivability label is generated based on the drivability having a driving risk that solves the driving risk exceeding the preset risk level. Different remote cabins can be pre-rated with respect to the remote driving ability for dangers of different danger levels, so that different ability labels can be attached to them depending on the evaluated remote driving ability to cope with the danger, for example, in addition to the high driving ability label, there can also be a common driving ability label.

Referring to fig. 4, fig. 4 is a flowchart of a method for associating a key security identification with a vehicle based on an actual security level in a remote control request processing method provided in an embodiment of the present disclosure, where the process 400 includes the following steps:

step 401: determining the actual security level of the target vehicle according to a preset security allocation rule;

the step aims to determine the actual security level corresponding to the target vehicle according to the security equipping rule which is recorded with the corresponding relation between different vehicles and different security levels in advance by the execution main body. Wherein the security provisioning rule is generally recorded in the execution body.

Further, the influence of time factors on the security level can be considered, and the determined actual security level is specifically determined to the actual security level of the target vehicle in the current time period, that is, different vehicles correspond to different security levels in different time periods, so as to correspond to the attribution property of the vehicle and the influence on the driving safety due to different time. In addition to being affected by conventional time factors, it may also be determined jointly based on whether the vehicle needs to engage in an important activity, the identity, number, etc. of the passengers seated therein.

Step 402: associating a second key guarantee identifier for the target vehicle in response to the fact that the actual security level exceeds the preset security level;

on the basis of step 401, this step is intended to associate a second key security identification with the target vehicle by the execution subject in the case that the actual security level exceeds the preset security level.

Further, considering that a target vehicle may pass through a certain area in a certain scene, and the road condition or driving environment of the area is not good, and the remote control safety of the distance needs to be ensured in a critical manner, a preset time length can be set for the second critical guarantee identifier by predicting the time consumption of the distance, that is, the preset time length is used for representing the holding time length of the association relationship between the second critical guarantee identifier and the target vehicle, and if the actual time length exceeds the preset time length, the adjustment can be performed in various manners, such as adjusting the security level of one level, adjusting the critical guarantee degree of the critical guarantee identifier, and even directly removing the associated critical guarantee identifier.

The specific time length of the preset duration may be combined with the estimated time consumption for passing through the dangerous road segment, which is mentioned above, with the actual security level, the duration of the surrounding activities, the average driving speed in the current driving environment, the number of passengers, the identity, and the like.

On the contrary, if the actual security level does not exceed the preset security level, the second key security identification does not need to be associated with the target vehicle, and the bound designated remote cockpit does not need to be allocated for the target vehicle.

Step 403: and determining the remote cockpit with the high security level label as the designated remote cockpit with the second key guarantee identifier.

Wherein the high security level label is generated based on a security capability that provides a security level that exceeds a preset security level. Different remote cockpit may have been previously assessed to provide what degree of security, where the security level referred to herein includes, in addition to the necessary driving capabilities, safe driving capabilities, awareness of security awareness, sensitivity capabilities, etc., so that different capability labels may be attached to them based on the assessed security, for example, in addition to a high security level label, a common security level label may also be present.

Fig. 3 and 4 respectively show a specific implementation manner of whether to associate a key guarantee identifier with a corresponding vehicle from two aspects of a travel plan and an actual security level, or combine the implementation manners shown in fig. 3 and 4 under the guidance idea to obtain a scheme of determining whether to associate a key guarantee identifier with a travel plan and an actual security level at the same time, so as to implement a finer degree of differentiation, which is not listed here.

On the basis of any of the above embodiments, in order to improve the reliability of the remote control service provided to the target vehicle associated with the important safeguard identification as much as possible, the number of the designated remote control cabins corresponding to each target vehicle associated with the important safeguard identification can be set to be multiple (for example, 2, 3 or more), and further controls at least a preset number (e.g. set to 1 or 2) of the designated remote cabins to be in a take-over preparation state, or controls the number of the specified remote cabs in the take-over ready state to be not less than a preset percentage (e.g., 1/3 or 30%), to avoid the problem of control interruption due to sudden or unknown factors in a given remote cockpit that previously provided remote control services for the target vehicle, the take-over preparation state refers to a state in which a designated remote cockpit providing remote control service for the target vehicle can be replaced with itself within a preset time period.

On the basis that any of the above embodiments provides a scheme of designating a remote cockpit for a corresponding vehicle for a key guarantee identifier, considering complexity and diversity in a remote control service scenario, the present disclosure further provides a target remote cockpit, which is different from a common remote cockpit and a designated remote cockpit that remotely control a target vehicle in a synchronous control manner, through fig. 5 and fig. 6, respectively, so as to meet the requirement that a vehicle needs to be accessed for remote control through another control manner in some vehicles or some scenarios through the target remote cockpit.

Referring to fig. 5, fig. 5 is a flowchart of a remote driving method for providing other control modes based on an included multi-mode control identifier in a remote control request processing method provided in an embodiment of the present disclosure, where the process 500 includes the following steps:

step 501: responding to the fact that the remote control request contains the multi-mode control identification, and sending the remote control request containing the multi-mode control identification to a preset first target remote cockpit;

wherein the plurality of control modes corresponding to the multi-mode control identifier include: direct control, indirect control, and synchronous control. I.e. the inclusion of the multi-mode control identity means that the vehicle issuing the remote control request supports other control modes than the default used synchronization control, this step therefore sends a remote control request including such identity to the preset first target remote cockpit to better handle such remote control request by means of the target remote cockpit possessing the multi-control mode processing capability.

The indirect control mode is a control mode which requires that the vehicle is in a static state before the remote control cabin is accessed to the vehicle for remote control; the direct control mode is a control mode which is executed by directly transmitting a control instruction of a remote cockpit to a vehicle without the vehicle being in a static state; the synchronous control mode is a control mode updated on the basis of the direct control mode, and is different from a mode of directly transmitting a control command of a remote control cabin to the vehicle.

Step 502: controlling a first target remote control cabin to determine a first target control mode corresponding to a target vehicle according to the multi-mode control identifier;

on the basis of step 501, this step is intended to determine a first target control mode corresponding to the target vehicle according to the multi-mode control identifier by the execution subject controlling the first target remote cockpit, and the selection among the multiple control modes can be performed according to the actual situation of the vehicle or the preference of the first target remote cockpit, which is not specifically limited herein.

Step 503: and issuing a second remote control instruction to the first target remote control cabin.

And the second remote control instruction is used for instructing the first target remote control cabin to remotely control the target vehicle according to the first target control mode.

Unlike the passive control method provided in fig. 5, fig. 6 provides a flowchart of an active remote driving control method, wherein the process 600 includes the following steps:

step 601: acquiring automatic driving data returned by each automatic driving vehicle;

step 602: receiving an active remote control request initiated by a second target remote control cabin according to the automatic driving data;

in this step, the execution main body receives an active remote control request initiated by the second target remote cockpit according to the autopilot data, that is, the autopilot data of each vehicle obtained in step 601 will be presented to the second target remote cockpit, the second target remote cockpit analyzes the autopilot data by itself or by other analysis equipment, determines that some problems exist according to the analysis result, and needs to correct the problems in time through remote driving, and ensures the vehicle driving safety, and initiates the active remote control request to the vehicle.

Of course, besides the scenario of trying to correct the problem, an active remote control request may be actively initiated for a certain test vehicle in combination with the test requirement in the test scenario.

Step 603: determining a vehicle to be controlled and a second target control mode supported by the vehicle to be controlled according to the active remote control request;

on the basis of step 602, this step is intended to determine, by the executing body, the vehicle to be controlled, the second target control mode supported by the vehicle to be controlled, according to the active remote control request, so as to subsequently cause the second target remote control room to control it by the control mode supported by it.

Step 604: and responding to the condition that the vehicle to be controlled allows the second target remote control cabin to access, and issuing a third remote control instruction to the second target remote control cabin.

And the third remote control instruction is used for instructing the second target remote control cabin to remotely control the vehicle to be controlled according to the second target control mode.

For further understanding, the present disclosure further provides a specific implementation scheme in combination with a specific application scenario, please refer to the timing chart shown in fig. 7, and fig. 7 is a complete remote control request processing timing chart provided in combination with an actual application according to an embodiment of the present disclosure:

as shown in fig. 7, the whole is divided into three stages: the dispatching stage, the processing stage and the returning stage relate to a plurality of terminals, wherein the leftmost terminal is a vehicle terminal (an automatic driving vehicle, a task initiator of a system and an object needing service), a cloud dispatching terminal (a Channel, which receives a vehicle terminal task request, executes dispatching, and is communicated with the dispatching information through a Sim service task, and an intermediate service terminal (Sim service, a cockpit control interface and an intermediate service of the dispatching service, which is responsible for displaying the task information and collecting feedback of a driver for task dispatching) and a cockpit terminal (user/seat).

Tasks in the scheduling stage are mainly divided into five states:

SCHEDULE START (SCHEDULE _ START),

SCHEDULE REQUEST (SCHEDULE REQUEST queue scheduler),

SCHEDULE acceptance (SCHEDULE _ queue _ ACCEPT),

SCHEDULE rejection (SCHEDULE _ delay _ release),

SCHEDULE request TIMEOUT (SCHEDULE _ grant _ TIMEOUT),

And scheduling a whole TIMEOUT (SCHEDULE TIMEOUT), the scheduling whole architecture also expands around the five states:

a new work order request

When a vehicle needs remote access, the vehicle sends out a work order request; and the cloud scheduling terminal receives the request and informs the intermediate server terminal to create the work order, so as to obtain the id of the work order. At this time, the scheduling process is in the above five states: SCHEDULE START (SCHEDULE _ START).

Secondly, scheduling and starting:

starting a scheduling process:

1. creating task request overtime timing, wherein each task scheduling stage does not exceed 35s scheduling time; TIMEOUT not ending modify state SCHEDULE overall TIMEOUT (SCHEDULE TIMEOUT);

2. pushing tasks to a scheduling queue and triggering one execution of a scheduling cycle:

before the scheduling cycle is executed, the tasks are sequenced according to the urgency of the tasks reported by the vehicles; each task in the circular scheduling queue is in an order to be allocated, and a resource allocation algorithm is called to refer to the next step; task loops in the allocated schedule are ignored; the task in the ending state modifies the task state to be invalid.

3. And calling resource allocation: selecting a corresponding cockpit according to the resource pool range and the scheduling interference strategy, and selecting the state of the corresponding cockpit at the moment:

in dispatch (SCHEDULE _ REQUEST _ pod), if there is no matching cockpit then it is still: SCHEDULE START (SCHEDULE _ START) state.

Scheduling the resource pool: the system is presented in an organization form, and a system administrator defines the organization of remote driving and determines which people, vehicles and cabins are in a resource pool; while these resources and organizations are not in a 1-to-1 relationship, one resource (person/vehicle/cabin) may belong to multiple organizations; but when in use, one person only occupies one cabin, and one cabin can run in one organization.

When a vehicle sends a remote distress request, a non-specialized setting will find the cockpit in all organizations related to the vehicle change.

4. For a task in a scheduling REQUEST (SCHEDULE _ REQUEST _ task), the matched cockpit user end asks whether the generation driver takes an order or not, the generation driver has three choices, if the order driver ACCEPTs, the task state is changed to scheduling acceptance (SCHEDULE _ task _ ACCEPT), if the order driver rejects, the task state is changed to scheduling rejection (SCHEDULE _ task _ return), or if the task state is changed to scheduling rejection after waiting for 10s scheduling:

scheduling rejection (SCHEDULE _ delay _ TIMEOUT).

5. If the task state is a scheduling request TIMEOUT (SCHEDULE _ locomotive _ TIMEOUT), one execution of the scheduling loop is triggered again to reach step 2, namely the next matched cockpit is replaced, and whether the next generation driver of the cockpit takes the order or not is continuously inquired until the total waiting time exceeds 35s or one generation driver selects to accept.

Thirdly, scheduling end state:

three end states: scheduling acceptance, scheduling rejection and scheduling overall timeout; and after the dispatching is received, the task flow is in a processing stage, and the other two tasks are directly finished and prompt the vehicle end to carry out self-processing.

The above corresponds to the upper half of fig. 7, the lower half shows the processing flow of three kinds of automatic driving, it should be firstly clear that the automatic driving vehicle originally sending the remote control request triggers automatic driving because the remote control service has been provided or cannot be provided or the vehicle end requires active release, so the vehicle end will restore to the original automatic driving mode again, case1 shows a situation that the vehicle end requires active release, in which case the cloud scheduling end will trigger an end flow, thereby releasing the cab resources previously occupied by the vehicle and marking the garage status as end; case2 shows a situation that a remote control service has been provided, in which case the cloud scheduling end triggers the end of the flow only when confirming that the vehicle end successfully enters into the automatic driving, so as to guarantee the safety of the subsequent automatic driving of the vehicle end in a way of really exiting from the synchronous driving; case3 shows a situation where remote control service cannot be provided, that is, after the cockpit chooses to reject the order, the cloud scheduling end will prompt the vehicle end to process itself, and thus the vehicle will trigger automatic driving.

On the basis of the remote control request processing scheme shown in fig. 7, the remote control service of the designated remote control cabin provided based on the key guarantee identifier and the remote control service of other modes different from the synchronous control mode provided by the embodiments of the present disclosure, which are provided based on the key guarantee identifier, can be classified as a supplementary interference policy on the above basic scheme.

In addition, the workload can be controlled to be the same as much as possible based on the order receiving amount and the order receiving designated driving time in the remote control cabins of the same type based on a load balancing strategy.

With further reference to fig. 8, as an implementation of the methods shown in the above-mentioned figures, the present disclosure provides an embodiment of a remote control request processing apparatus, which corresponds to the method embodiment shown in fig. 2, and which is particularly applicable to various electronic devices.

As shown in fig. 8, the remote control request processing apparatus 800 of the present embodiment may include: a remote control request receiving unit 801, a specified remote cockpit determining unit 802, and a first remote control instruction issuing unit 803. Wherein the remote control request receiving unit 801 is configured to determine a target vehicle that initiates a request according to a received remote control request; a designated remote cockpit determination unit 802 configured to determine a designated remote cockpit corresponding to a key safeguard identification in response to the target vehicle being associated with the key safeguard identification; the method comprises the following steps that an incidence relation between a target vehicle and a key guarantee identifier is determined based on a trip plan and/or an actual security level of the target vehicle; a first remote control instruction issuing unit 803 configured to issue a first remote control instruction to a specified remote cockpit; the first remote control instruction is used for indicating a designated remote control cabin to remotely control the target vehicle.

In the present embodiment, in the remote control request processing apparatus 800: the detailed processing and the technical effects of the remote control request receiving unit 801, the designated remote cockpit determining unit 802, and the first remote control instruction issuing unit 803 can refer to the related descriptions of step 201 and step 203 in the corresponding embodiment of fig. 2, which are not described herein again.

In some optional implementations of this embodiment, the remote control request processing apparatus 800 may further include:

a trip plan acquisition unit configured to extract a trip plan of the target vehicle from the remote control request or query a trip plan matching the target vehicle in a previously uploaded trip plan set;

a menstruation position set determination unit configured to determine a menstruation position set according to a travel plan;

a first key safeguard identification association unit configured to associate a first key safeguard identification for the target vehicle in response to there being more than a preset number of the passing positions in the set of passing positions having more than a preset risk degree; wherein the danger degree is determined based on at least one of terrain complexity degree, traffic density and driving slowness degree;

correspondingly, the designated remote cockpit determination unit is further configured to:

determining the remote cockpit with the tag with the high drivability as a designated remote cockpit with the first key guarantee identifier; wherein the high drivability label is generated based on the drivability having a driving risk that solves the driving risk exceeding the preset risk level.

an actual security level determination unit configured to determine an actual security level of the target vehicle according to a preset security equipping rule; wherein, the corresponding relation between different vehicles and different security levels is recorded in the security allocation rule;

a second key safeguard identification association unit configured to associate a second key safeguard identification for the target vehicle in response to the actual security level exceeding the preset security level;

determining the remote cockpit with the high security level label as a designated remote cockpit with a second key guarantee identifier; wherein the high security level label is generated based on a security capability that provides a security level that exceeds a preset security level.

the redundancy protection unit is configured to respond to the fact that the number of the designated remote control cabins is multiple, control at least a preset number of the designated remote control cabins to be in a take-over preparation state, or control the number of the designated remote control cabins in the take-over preparation state to be not smaller than a preset ratio; the take-over preparation state refers to a state in which a designated remote control cabin providing remote control service for the target vehicle can be replaced with itself within a preset time period.

the multi-control identification processing unit is configured to respond to the fact that the multi-mode control identification is contained in the remote control request, and send the remote control request containing the multi-mode control identification to a preset first target remote cockpit;

a first target control mode determination unit configured to control the first target remote cockpit to determine a first target control mode corresponding to the target vehicle according to the multi-mode control identifier; wherein the plurality of control modes corresponding to the multi-mode control identifier include: direct control, indirect control and synchronous control;

the second remote control instruction issuing unit is configured to issue a second remote control instruction to the first target remote control cabin; and the second remote control instruction is used for instructing the first target remote control cabin to remotely control the target vehicle according to the first target control mode.

an automatic driving data acquisition unit configured to acquire automatic driving data returned by each of the automatically driven vehicles;

an active remote control request receiving unit configured to receive an active remote control request initiated by a second target remote cockpit according to autopilot data;

a vehicle to be controlled and a second target control mode determination unit configured to determine the vehicle to be controlled, a second target control mode supported by the vehicle to be controlled, according to the active remote control request; wherein the control mode includes: direct control, indirect control and synchronous control;

the third remote control instruction issuing unit is configured to issue a third remote control instruction to the second target remote control cabin in response to the vehicle to be controlled allowing the second target remote control cabin to access; and the third remote control instruction is used for instructing the second target remote control cabin to remotely control the vehicle to be controlled according to the second target control mode.

The present embodiment exists as an apparatus embodiment corresponding to the above method embodiment, and the remote control request processing apparatus provided in the present embodiment determines whether to associate a key safeguard identifier for specifying some remote control cabins for the vehicle based on a trip plan and/or an actual security level of the vehicle, so as to provide a more comprehensive and effective remote control service for the vehicle associated with the key safeguard identifier by specifying the remote control cabin, and simultaneously, also expands a new remote control request processing manner, and can cover more diverse requirements and scenes.

According to an embodiment of the present disclosure, the present disclosure also provides an electronic device including: at least one processor; and a memory communicatively coupled to the at least one processor; wherein the memory stores instructions executable by the at least one processor to cause the at least one processor to perform the method of processing remote control requests as described in any of the above embodiments when executed.

According to an embodiment of the present disclosure, there is also provided a readable storage medium storing computer instructions for enabling a computer to implement the remote control request processing method described in any of the above embodiments when executed.

The disclosed embodiments provide a computer program product, which when executed by a processor is capable of implementing the remote control request processing method described in any of the above embodiments.

On this basis, the embodiment of the present disclosure further provides a cloud server including the above electronic device, so as to serve as a processing or scheduling platform for implementing the whole remote control request of the above technical scheme of the present disclosure.

Correspondingly, the embodiment of the present disclosure may further provide an autonomous vehicle, including:

initiating a remote control request to the cloud server described in the above embodiment;

Correspondingly, this disclosed embodiment can also provide a high in clouds cockpit, includes:

receiving a first remote control instruction sent by the cloud server described in the above embodiment; when the cloud server confirms that the automatic driving vehicle initiating the remote control request (namely, the automatic driving vehicle described in the above embodiment) is associated with the key guarantee identifier, the first remote control instruction is issued to the cloud cockpit corresponding to the key guarantee identifier;

FIG. 9 illustrates a schematic block diagram of an example electronic device 900 that can be used to implement embodiments of the present disclosure. Electronic devices are intended to represent various forms of digital computers, such as laptops, desktops, workstations, personal digital assistants, servers, blade servers, mainframes, and other appropriate computers. The electronic device may also represent various forms of mobile devices, such as personal digital processing, cellular phones, smart phones, wearable devices, and other similar computing devices. The components shown herein, their connections and relationships, and their functions, are meant to be examples only, and are not meant to limit implementations of the disclosure described and/or claimed herein.

As shown in fig. 9, the apparatus 900 includes a computing unit 901, which can perform various appropriate actions and processes in accordance with a computer program stored in a Read Only Memory (ROM)902 or a computer program loaded from a storage unit 908 into a Random Access Memory (RAM) 903. In the RAM 903, various programs and data required for the operation of the device 900 can also be stored. The calculation unit 901, ROM 902, and RAM 903 are connected to each other via a bus 904. An input/output (I/O) interface 905 is also connected to bus 904.

A number of components in the device 900 are connected to the I/O interface 905, including: an input unit 906 such as a keyboard, a mouse, and the like; an output unit 907 such as various types of displays, speakers, and the like; a storage unit 908 such as a magnetic disk, optical disk, or the like; and a communication unit 909 such as a network card, a modem, a wireless communication transceiver, and the like. The communication unit 909 allows the device 900 to exchange information/data with other devices through a computer network such as the internet and/or various telecommunication networks.

The computing unit 901 may be a variety of general and/or special purpose processing components having processing and computing capabilities. Some examples of the computing unit 901 include, but are not limited to, a Central Processing Unit (CPU), a Graphics Processing Unit (GPU), various dedicated Artificial Intelligence (AI) computing chips, various computing units running machine learning model algorithms, a Digital Signal Processor (DSP), and any suitable processor, controller, microcontroller, and so forth. The computing unit 901 performs the respective methods and processes described above, such as the remote control request processing method. For example, in some embodiments, the remote control request processing method may be implemented as a computer software program tangibly embodied in a machine-readable medium, such as storage unit 908. In some embodiments, part or all of the computer program may be loaded and/or installed onto device 900 via ROM 902 and/or communications unit 909. When the computer program is loaded into the RAM 903 and executed by the computing unit 901, one or more steps of the remote control request processing method described above may be performed. Alternatively, in other embodiments, the computing unit 901 may be configured to perform the remote control request processing method by any other suitable means (e.g., by means of firmware).

Various implementations of the systems and techniques described here above may be implemented in digital electronic circuitry, integrated circuitry, Field Programmable Gate Arrays (FPGAs), Application Specific Integrated Circuits (ASICs), Application Specific Standard Products (ASSPs), system on a chip (SOCs), load programmable logic devices (CPLDs), computer hardware, firmware, software, and/or combinations thereof. These various embodiments may include: implemented in one or more computer programs that are executable and/or interpretable on a programmable system including at least one programmable processor, which may be special or general purpose, receiving data and instructions from, and transmitting data and instructions to, a storage system, at least one input device, and at least one output device.

Program code for implementing the methods of the present disclosure may be written in any combination of one or more programming languages. These program codes may be provided to a processor or controller of a general purpose computer, special purpose computer, or other programmable data processing apparatus, such that the program codes, when executed by the processor or controller, cause the functions/operations specified in the flowchart and/or block diagram to be performed. The program code may execute entirely on the machine, partly on the machine, as a stand-alone software package partly on the machine and partly on a remote machine or entirely on the remote machine or server.

In the context of this disclosure, a machine-readable medium may be a tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. The machine-readable medium may be a machine-readable signal medium or a machine-readable storage medium. A machine-readable medium may include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. More specific examples of a machine-readable storage medium would include an electrical connection based on one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

To provide for interaction with a user, the systems and techniques described here can be implemented on a computer having: a display device (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor) for displaying information to a user; and a keyboard and a pointing device (e.g., a mouse or a trackball) by which a user can provide input to the computer. Other kinds of devices may also be used to provide for interaction with a user; for example, feedback provided to the user can be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user may be received in any form, including acoustic, speech, or tactile input.

The systems and techniques described here can be implemented in a computing system that includes a back-end component (e.g., as a data server), or that includes a middleware component (e.g., an application server), or that includes a front-end component (e.g., a user computer having a graphical user interface or a web browser through which a user can interact with an implementation of the systems and techniques described here), or any combination of such back-end, middleware, or front-end components. The components of the system can be interconnected by any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include: local Area Networks (LANs), Wide Area Networks (WANs), and the Internet.

The computer system may include clients and servers. A client and server are generally remote from each other and typically interact through a communication network. The relationship of client and server arises by virtue of computer programs running on the respective computers and having a client-server relationship to each other. The Server may be a cloud Server, which is also called a cloud computing Server or a cloud host, and is a host product in a cloud computing service system, so as to solve the defects of high management difficulty and weak service extensibility in the conventional physical host and Virtual Private Server (VPS) service.

Compared with the existing processing mode that each remote control request is processed by each remote control cabin based on an automatic order receiving mode, the embodiment of the disclosure determines whether to associate key guarantee identifiers for designating some remote control cabins for the remote control cabins based on the travel plans and/or the actual security levels of the vehicles, so that more comprehensive and more effective remote control services are provided for the vehicles associated with the key guarantee identifiers by designating the remote control cabins, a new remote control request processing mode is expanded, and more various requirements and scenes can be covered.

It should be understood that various forms of the flows shown above may be used, with steps reordered, added, or deleted. For example, the steps described in the present disclosure may be executed in parallel, sequentially, or in different orders, as long as the desired results of the technical solutions disclosed in the present disclosure can be achieved, and the present disclosure is not limited herein.

The above detailed description should not be construed as limiting the scope of the disclosure. It should be understood by those skilled in the art that various modifications, combinations, sub-combinations and substitutions may be made in accordance with design requirements and other factors. Any modification, equivalent replacement, and improvement made within the spirit and principle of the present disclosure should be included in the scope of protection of the present disclosure.

Claims

1. A remote control request processing method comprises the following steps:

determining a target vehicle initiating a request according to the received remote control request;

determining a designated remote control cabin corresponding to the key guarantee identification in response to the key guarantee identification associated with the target vehicle; the incidence relation between the target vehicle and the key guarantee identification is determined based on a travel plan and/or an actual security level of the target vehicle;

issuing a first remote control instruction to the specified remote control cabin; wherein the first remote control instruction is used for instructing the designated remote cockpit to remotely control the target vehicle.

2. The method of claim 1, further comprising:

extracting a travel plan of the target vehicle from the remote control request, or inquiring a travel plan matched with the target vehicle from a pre-uploaded travel plan set;

determining a menstruation position set according to the travel plan;

responding to the situation that more than a preset number of the passing positions with more than a preset danger degree exist in the passing position set, and associating a first key guarantee identifier for the target vehicle; wherein the danger degree is determined based on at least one of terrain complexity degree, traffic density and driving slowness degree;

correspondingly, the determining the designated remote cockpit corresponding to the key guarantee identifier includes:

determining the remote cockpit with the high drivability label as the designated remote cockpit with the first key guarantee identifier; wherein the high drivability label is generated based on the drivability having a driving risk that solves the driving risk exceeding the preset risk level.

3. The method of claim 1, further comprising:

determining the actual security level of the target vehicle according to a preset security allocation rule; wherein, the corresponding relation between different vehicles and different security levels is recorded in the security allocation rule;

associating a second key guarantee identifier for the target vehicle in response to the fact that the actual security level exceeds a preset security level;

correspondingly, determining the designated remote cockpit corresponding to the key guarantee identifier comprises the following steps:

determining the remote cockpit with the high security level label as a designated remote cockpit with the second key guarantee identifier; wherein the high security level label is generated based on a security capability that provides more than the preset security level.

4. The method of claim 1, further comprising:

in response to the fact that the number of the designated remote control cabins is multiple, controlling at least a preset number of designated remote control cabins to be in a take-over preparation state, or controlling the number ratio of the designated remote control cabins in the take-over preparation state to be not less than the preset ratio; wherein the take-over preparation state refers to a state in which a designated remote cockpit providing remote control service for the target vehicle can be replaced with itself within a preset time period.

5. The method of any of claims 1-4, further comprising:

responding to the fact that the remote control request contains the multi-mode control identification, and sending the remote driving control containing the multi-mode control identification to a preset first target remote driving cabin;

controlling the first target remote cockpit to determine a first target control mode corresponding to the target vehicle according to the multi-mode control identifier; wherein the plurality of control modes corresponding to the multi-mode control identifier include: direct control, indirect control and synchronous control;

issuing a second remote control instruction to the first target remote control cabin; wherein the second remote control instruction is used for instructing the first target remote control cabin to remotely control the target vehicle according to the first target control mode.

6. The method of any of claims 1-4, further comprising:

acquiring automatic driving data returned by each automatic driving vehicle;

receiving an active remote control request initiated by a second target remote cockpit according to the automatic driving data;

determining a vehicle to be controlled and a second target control mode supported by the vehicle to be controlled according to the active remote control request; wherein the control mode includes: direct control, indirect control and synchronous control;

responding to the condition that the vehicle to be controlled allows the second target remote control cabin to be accessed, and issuing a third remote control instruction to the second target remote control cabin; and the third remote control instruction is used for instructing the second target remote control cabin to remotely control the vehicle to be controlled according to the second target control mode.

7. A remote control request processing apparatus comprising:

a remote control request receiving unit configured to determine a target vehicle that initiates a request according to a received remote control request;

a designated remote cockpit determination unit configured to determine a designated remote cockpit corresponding to a key safeguard identification in response to the target vehicle being associated with the key safeguard identification; the incidence relation between the target vehicle and the key guarantee identification is determined based on a travel plan and/or an actual security level of the target vehicle;

a first remote control instruction issuing unit configured to issue a first remote control instruction to the specified remote cockpit; wherein the first remote control instruction is used for instructing the designated remote cockpit to remotely control the target vehicle.

8. The apparatus of claim 7, further comprising:

a travel plan acquisition unit configured to extract a travel plan of the target vehicle from the remote control request or query a travel plan matching the target vehicle from a previously uploaded travel plan set;

a menstruation position set determination unit configured to determine a menstruation position set according to the travel plan;

a first key safeguard identification association unit configured to associate a first key safeguard identification for the target vehicle in response to there being more than a preset number of the travel positions in the set of travel positions having more than a preset risk degree; wherein the danger degree is determined based on at least one of terrain complexity degree, traffic density and driving slowness degree;

9. The apparatus of claim 7, further comprising:

a second key security identity association unit configured to associate a second key security identity for the target vehicle in response to the actual security level exceeding a preset security level;

10. The apparatus of claim 7, further comprising:

a redundancy protection unit configured to control at least a preset number of the designated remote cabins to be in a take-over preparation state or control the number ratio of the designated remote cabins in the take-over preparation state to be not less than a preset ratio in response to the number of the designated remote cabins being plural; wherein the take-over preparation state refers to a state in which a designated remote cockpit providing remote control service for the target vehicle can be replaced with itself within a preset time period.

11. The apparatus of any of claims 7-10, further comprising:

a second remote control instruction issuing unit configured to issue a second remote control instruction to the first target remote cockpit; wherein the second remote control instruction is used for instructing the first target remote control cabin to remotely control the target vehicle according to the first target control mode.

12. The method according to any one of claims 7-10, further comprising:

an active remote control request receiving unit configured to receive an active remote control request initiated by a second target remote cockpit according to the autopilot data;

a third remote control instruction issuing unit configured to issue a third remote control instruction to the second target remote cockpit in response to the vehicle to be controlled allowing the second target remote cockpit to access; and the third remote control instruction is used for instructing the second target remote control cabin to remotely control the vehicle to be controlled according to the second target control mode.

13. An electronic device, comprising:

at least one processor; and

a memory communicatively coupled to the at least one processor; wherein,

the memory stores instructions executable by the at least one processor to enable the at least one processor to perform the remote control request processing method of any of claims 1-6.

14. A non-transitory computer-readable storage medium storing computer instructions for causing a computer to execute the remote control request processing method of any one of claims 1 to 6.

15. A computer program product comprising a computer program which, when executed by a processor, carries out the steps of the remote control request processing method according to any one of claims 1-6.

16. A cloud server comprising the electronic device of claim 13.

17. An autonomous vehicle comprising:

initiating a remote control request to a cloud server; wherein the cloud server is the cloud server of claim 16;

receiving a remote control parameter sent by a designated remote control cabin responding to a first remote control instruction sent by the cloud server; the first remote control instruction is issued to a cloud control cabin corresponding to a key guarantee identifier when the cloud server confirms that the automatic driving vehicle which initiates the remote control request is associated with the key guarantee identifier.

18. A cloud cockpit, comprising:

receiving a first remote control instruction sent by a cloud server; the first remote control instruction is issued to a cloud cockpit corresponding to a key guarantee identifier when the cloud server confirms that an autonomous vehicle initiating a remote control request is associated with the key guarantee identifier, wherein the cloud server is the cloud server of claim 16, and the autonomous vehicle is the autonomous vehicle of claim 17;