Remote driving method and system

Abstract

The application discloses a remote driving method and system. The method comprises the following steps: receiving a remote driving request of a plurality of vehicles sent by a server, the remote driving request comprising a remote driving task; broadcasting the remote driving request of the plurality of vehicles to N operation stations, N being an integer greater than 1; receiving a takeover request for a target remote driving task sent by M first operation stations, the target remote driving task being a remote driving task corresponding to a target vehicle, 1≤M≤N, M being a positive integer; in the case of M>1, determining a target operation station to take over the target remote driving task according to the time when the M first operation stations send the takeover request, and sending takeover success information to the target operation station, so that a user processes the target remote driving task through the target operation station, the target operation station being an operation station that sends the takeover request earliest among the M first operation stations. The remote driving method and system provided by the application can improve the processing efficiency of the remote driving task and ensure the safety of the vehicle.

Description

TECHNICAL FIELD

[0001] The application belongs to the technical field of automatic driving, and particularly relates to a remote driving method and system. BACKGROUND

[0002] With the development of artificial intelligence technology, the application of automatic driving vehicles is becoming more and more widespread.

[0003] In the related art, when an automatic driving vehicle fails during task execution, a remote driving request can be sent to an operation station so that a user processes a remote driving task requested by the remote driving request through the operation station.

[0004] However, in the related art, only one operation station can process a remote driving task requested by a remote driving request of one vehicle at the same time, and when multiple vehicles fail, only one can be processed at a time, which is low in efficiency and cannot guarantee vehicle safety. SUMMARY

[0005] The embodiments of the application provide a remote driving method and system, which can process multiple remote driving tasks at the same time, thereby improving the processing efficiency of remote driving tasks and ensuring vehicle safety.

[0006] In a first aspect, the embodiments of the application provide a remote driving method applied to a scheduling system, which comprises:

[0007] receiving a remote driving request of multiple vehicles sent by a server, the remote driving request comprising a remote driving task,

[0008] broadcasting the remote driving request of the multiple vehicles to N operation stations, N being an integer greater than 1,

[0009] receiving a takeover request for a target remote driving task sent by M first operation stations, the target remote driving task being a remote driving task corresponding to a target vehicle, the multiple vehicles comprising the target vehicle, 1≤M≤N, M being a positive integer,

[0010] In the case of M>1, determining a target operation station to take over the target remote driving task according to the time when the M first operation stations send the takeover request, and sending takeover success information to the target operation station, so that a user processes the target remote driving task through the target operation station, the target operation station being the operation station that sends the takeover request earliest among the M first operation stations.

[0011] In a second aspect, the embodiments of the application provide a remote driving method applied to a target operation station, which comprises:

[0012] receiving a remote driving request of multiple vehicles broadcast by a scheduling system, the remote driving request comprising a remote driving task,

[0013] display a remote driving task corresponding to a plurality of vehicles,

[0014] in response to a first input of a user on a target remote driving task in the plurality of remote driving tasks, send a takeover request on the target remote driving task to a dispatch system,

[0015] in a case where takeover success information sent by the dispatch system is received, in response to a second input of the user, process the target remote driving task.

[0016] In a third aspect, the embodiments of the present application provide a remote driving method, applied to a server, and the method comprises:

[0017] receive a remote driving request of a plurality of vehicles, the remote driving request comprising a remote driving task,

[0018] send the remote driving request of the plurality of vehicles to a dispatch system, so that the dispatch system broadcasts the remote driving request of the plurality of vehicles to N operation stations, and users process the remote driving task through the N operation stations, N being an integer greater than 1.

[0019] In a fourth aspect, the embodiments of the present application provide a remote driving system, which comprises:

[0020] a server, configured to receive a remote driving request of a plurality of vehicles, and send the remote driving request of the plurality of vehicles to a dispatch system, the remote driving request comprising a remote driving task,

[0021] a dispatch system, configured to broadcast the remote driving request of the plurality of vehicles to N operation stations, N being an integer greater than 1,

[0022] N operation stations, configured to display a remote driving task corresponding to a plurality of vehicles, M first operation stations in the N operation stations are configured to send a takeover request on a target remote driving task to the dispatch system in response to a first input of a user on the target remote driving task in the plurality of remote driving tasks, the target remote driving task being a remote driving task corresponding to a target vehicle, the plurality of vehicles comprising the target vehicle, 1≤M≤N, M being a positive integer,

[0023] the dispatch system is further configured to, in a case where M>1, determine a target operation station to take over the target remote driving task according to a time at which the M first operation stations send the takeover requests, and send takeover success information to the target operation station, so that the user processes the target remote driving task through the target operation station, the target operation station being an operation station that sends the takeover request earliest among the M first operation stations, and the target operation station being configured to process the target remote driving task in response to a second input of the user.

[0024] In a fifth aspect, the embodiments of the present application provide a remote driving device, applied to a dispatch system, and the device comprises:

[0025] The first receiving module is configured to receive remote driving requests of a plurality of vehicles sent by a server, wherein the remote driving requests comprise remote driving tasks,

[0026] The first broadcasting module is configured to broadcast the remote driving requests of the plurality of vehicles to N operation stations, wherein N is an integer greater than 1,

[0027] The second receiving module is configured to receive takeover requests of a target remote driving task sent by M first operation stations, wherein the target remote driving task is a remote driving task corresponding to a target vehicle, the plurality of vehicles comprise the target vehicle, 1≤M≤N, and M is a positive integer,

[0028] The first sending module is configured to, in a case where M>1, determine a target operation station to take over the target remote driving task according to a time at which the M first operation stations send the takeover requests, and send takeover success information to the target operation station, so that a user processes the target remote driving task through the target operation station, and the target operation station is an operation station that sends the takeover request earliest among the M first operation stations.

[0029] In a sixth aspect, an embodiment of the present application provides a remote driving device applied to a target operation station, and the device comprises:

[0030] The fourth receiving module is configured to receive remote driving requests of a plurality of vehicles broadcast by a dispatching system, wherein the remote driving requests comprise remote driving tasks,

[0031] The first display module is configured to display the remote driving tasks corresponding to the plurality of vehicles,

[0032] The second sending module is configured to, in response to a first input of a user on a target remote driving task in the plurality of remote driving tasks, send a takeover request of the target remote driving task to the dispatching system,

[0033] The processing module is configured to, in a case where the takeover success information sent by the dispatching system is received, process the target remote driving task in response to a second input of the user.

[0034] In a seventh aspect, an embodiment of the present application provides a remote driving device applied to a server, and the device comprises:

[0035] The seventh receiving module is configured to receive remote driving requests of a plurality of vehicles, wherein the remote driving requests comprise remote driving tasks,

[0036] The third sending module is configured to send the remote driving requests of the plurality of vehicles to a dispatching system, so that the dispatching system broadcasts the remote driving requests of the plurality of vehicles to N operation stations, and a user processes the remote driving tasks through the N operation stations, and N is an integer greater than 1.

[0037] In an eighth aspect, an electronic device is provided, and the device includes a processor and a memory storing computer program instructions.

[0038] The processor, when executing the computer program instructions, implements the remote driving method as shown in any one of the embodiments of the first aspect, the second aspect, or the third aspect.

[0039] In a ninth aspect, a computer storage medium is provided, and the computer storage medium stores computer program instructions, and the computer program instructions, when executed by a processor, implement the remote driving method as shown in any one of the embodiments of the first aspect, the second aspect, or the third aspect.

[0040] In a tenth aspect, a computer program product is provided, and instructions in the computer program product, when executed by a processor of an electronic device, cause the electronic device to perform the remote driving method as shown in any one of the embodiments of the first aspect, the second aspect, or the third aspect.

[0041] The remote driving method and system provided in the embodiments of the present application can broadcast, by a scheduling system, a remote driving request of multiple vehicles sent by a server to N operation stations, and the remote driving request includes a remote driving task. After receiving a takeover request of a target remote driving task sent by M first operation stations, the scheduling system determines that the target remote driving task is taken over by a target operation station that sends the takeover request earliest, so that a user processes the target remote driving task through the target operation station. Since the scheduling system can broadcast the remote driving request of multiple vehicles to multiple operation stations, the multiple operation stations can process different remote driving tasks at the same time, so that multiple remote driving tasks can be processed at the same time, and thus the processing efficiency of the remote driving task can be improved, and the safety of the vehicle can be ensured. BRIEF DESCRIPTION OF DRAWINGS

[0042] In order to more clearly illustrate the technical solutions of the embodiments of the present application, the following will briefly introduce the drawings needed to be used in the embodiments of the present application. For those skilled in the art, other drawings can also be obtained without creative labor on the basis of these drawings.

[0043] Figure 1 is an architecture diagram of a remote driving system provided by an embodiment of the present application;

[0044] Figure 2 is a flowchart of a remote driving method provided by an embodiment of the present application;

[0045] Figure 3 is a flowchart of another remote driving method provided by an embodiment of the present application;

[0046] Figure 4is a state transition diagram of an operating platform provided by one embodiment of the present application;

[0047] Figure 5 is a flowchart of another remote driving method provided by one embodiment of the present application;

[0048] Figure 6 is an architecture diagram of another remote driving system provided by one embodiment of the present application;

[0049] Figure 7 is a structural diagram of a remote driving device provided by one embodiment of the present application;

[0050] Figure 8 is a structural diagram of another remote driving device provided by one embodiment of the present application;

[0051] Figure 9 is a structural diagram of another remote driving device provided by one embodiment of the present application;

[0052] Figure 10 is a structural diagram of an electronic device provided by one embodiment of the present application. DETAILED DESCRIPTION

[0053] The features and exemplary embodiments of the various aspects of the present application will be described in detail below with reference to the drawings. The following detailed description is merely intended to explain the present application, and is not intended to limit the present application. The present application can be implemented without some of the specific details, which are well known to those skilled in the art. The following description of the embodiments is merely intended to provide a better understanding of the present application through showing examples of the present application.

[0054] It should be noted that the relational terms herein such as first and second and the like are used solely to distinguish one entity or action from another, without necessarily requiring or implying any actual such relationship or order between such entities or actions. Moreover, the terms "comprises", "comprising", or any other variations thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but can include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element preceded by "comprises... a" does not, without more constraints, foreclose the existence of additional identical elements in the process, method, article, or apparatus that comprises the listed element.

[0055] As the background technology suggests, with the development of artificial intelligence and 5G technology, a large number of autonomous vehicles can operate in closed areas such as port transportation, mining areas, and closed-loop logistics parks, for example, in the horizontal transport of containers in ports. Remote driving systems, as a supplement and safety guarantee to autonomous driving systems, solve working conditions that autonomous vehicles cannot handle. Existing remote driving systems generally monitor all autonomous vehicles through a console. When a vehicle malfunctions and actively issues a remote driving request, the remote operator processes the remote driving tasks requested by these requests through the console.

[0056] However, since there is only one control panel, only one vehicle's remote driving task can be handled through one control panel at a time. When multiple vehicles malfunction, they can only be dealt with one by one, which is inefficient and cannot guarantee vehicle safety.

[0057] Based on this, embodiments of this application provide a remote driving method and system. A scheduling system broadcasts remote driving requests for multiple vehicles to N control consoles via a server. Each remote driving request includes a remote driving task. Upon receiving takeover requests for a target remote driving task from M first control consoles, the system determines that the target control console that first sent the takeover request will take over the target remote driving task, allowing the user to process the target remote driving task through that console. Since the scheduling system can broadcast remote driving requests for multiple vehicles to multiple control consoles, multiple control consoles can simultaneously process different remote driving tasks. This improves the efficiency of remote driving task processing and ensures vehicle safety.

[0058] Figure 1 An architecture diagram of a remote driving system provided in one embodiment of this application is shown.

[0059] like Figure 1 As shown, the remote driving system may include: a server 110, a scheduling system 120, and N control consoles 130. The N control consoles 130 may include a target control console 131.

[0060] Server 110 can be used to receive remote driving requests from multiple vehicles and send these requests to the dispatch system 120. These remote driving requests may include remote driving tasks.

[0061] The dispatch system 120 can be used to broadcast remote driving requests for multiple vehicles to N control consoles 130, where N can be an integer greater than 1.

[0062] N control panels 130 are provided to display remote driving tasks corresponding to multiple vehicles. M of the M control panels 130 are first control panels that, in response to the user's first input on a target remote driving task among multiple remote driving tasks, send a takeover request for the target remote driving task to the dispatch system 120. The target remote driving task can be a remote driving task corresponding to a target vehicle. Multiple vehicles can include the target vehicle, where 1 ≤ M ≤ N, and M can be a positive integer.

[0063] The scheduling system 120 can also be used, when M > 1, to determine the target operating station 131 to take over the target remote driving task based on the time when the M first operating stations send takeover requests, and send a takeover success message to the target operating station 131 so that the user can process the target remote driving task through the target operating station 131. The target operating station 131 can be the operating station that sent the takeover request earliest among the M first operating stations. The target operating station 131 can be used to process the target remote driving task in response to the user's second input.

[0064] Specifically, in the event of a vehicle malfunction, the autonomous driving system of multiple vehicles can send a remote driving request to the server 110. The server 110 can then send the remote driving request to the dispatch system 120. The dispatch system 120 can then broadcast the remote driving request to N control consoles 130. The N control consoles 130 can then display the remote driving tasks corresponding to the multiple vehicles included in the remote driving request. The user can input the first input to the target remote driving task among the multiple remote driving tasks displayed on the control console, causing the control console to send a takeover request to the dispatch system for the target remote driving task. If M of the N control consoles 130 send a takeover request to the dispatch system 120 for the target remote driving task, and M>1, the dispatch system can determine the target control console 131 that sent the takeover request earliest based on the time when the M control consoles sent the takeover request, and take over the target remote driving task. The dispatch system then sends a takeover success message to the target control console 131. After the target control console 131 receives the takeover success message, the user can control the target control console 131 to process the target remote driving task through a second input.

[0065] Therefore, the dispatch system broadcasts remote driving requests for multiple vehicles to N operator consoles via a server. These requests include remote driving tasks. Upon receiving takeover requests for the target remote driving task from M first operator consoles, the system determines that the target operator console that first sent the takeover request will take over the target remote driving task, allowing the user to process the target remote driving task through that console. Because the dispatch system can broadcast remote driving requests for multiple vehicles to multiple operator consoles, multiple consoles can handle different remote driving tasks simultaneously. This improves the efficiency of remote driving task processing and ensures vehicle safety.

[0066] Figure 2 A flowchart illustrating a remote driving method provided in one embodiment of this application is shown.

[0067] like Figure 2 As shown, this remote driving method can be applied to the dispatch system in a remote driving system and may include the following steps:

[0068] S210 receives remote driving requests from multiple vehicles sent by the server.

[0069] S220 broadcasts remote driving requests for multiple vehicles to N control consoles.

[0070] S230 receives takeover requests for the target remote driving task from M first control consoles.

[0071] S240, when M>1, based on the time when the M first control consoles send takeover requests, determine that the target control console will take over the target remote driving task, and send a takeover success message to the target control console so that the user can process the target remote driving task through the target control console.

[0072] Therefore, the dispatch system broadcasts remote driving requests for multiple vehicles to N operator consoles via a server. These requests include remote driving tasks. Upon receiving takeover requests for the target remote driving task from M first operator consoles, the system determines that the target operator console that first sent the takeover request will take over the target remote driving task, allowing the user to process the target remote driving task through that console. Because the dispatch system can broadcast remote driving requests for multiple vehicles to multiple operator consoles, multiple consoles can handle different remote driving tasks simultaneously. This improves the efficiency of remote driving task processing and ensures vehicle safety.

[0073] Regarding S210, the vehicle's remote driving system can send a remote driving request to the server in the event of a vehicle malfunction. This remote driving request can include a remote driving task. After receiving the remote driving request, the server can send it to the dispatch system.

[0074] In addition, a remote driving request may also include the task level corresponding to the remote driving task, the reason for initiating the remote driving request, remote driving suggestions, and the remote driving task number. Among these, the remote driving suggestions may include remotely driving the vehicle to complete the task or remotely driving the vehicle to leave the work area.

[0075] In S220, the dispatch system broadcasts remote driving requests for multiple vehicles to N control consoles, enabling the N control consoles to display the remote driving tasks corresponding to the multiple vehicles. Here, N can be an integer greater than 1.

[0076] Involving S230, multiple vehicles may include the target vehicle, and the target remote driving task may be the remote driving task corresponding to the target vehicle. The control panel can be used to process remote driving tasks and also to monitor the vehicles. The first input can be the input for taking over the target remote driving task. If the user makes the first input on M of the N control panels, then the M control panels can send a takeover request for the target remote driving task to the scheduling system. Where 1 ≤ M ≤ N, and M can be a positive integer.

[0077] Regarding S240, if M > 1, it indicates that multiple first operating stations have sent takeover requests to the scheduling system for the target remote driving task. A target operating station needs to be selected from these first operating stations to take over the target remote driving task. Specifically, the scheduling system can determine the operating station that sent the takeover request earliest among the M first operating stations as the target operating station based on the time when the takeover requests were sent. Furthermore, a takeover success message can be sent to the target operating station, which can be used to notify the user corresponding to the target operating station that the takeover was successful. The target operating station can be the operating station that sent the takeover request earliest among the M first operating stations. In addition, a takeover failure message can be sent to the operating stations other than the target operating station among the M first operating stations, which can be used to notify the user corresponding to the respective operating station that the takeover failed.

[0078] If M=1, it indicates that only one first operator console sends a takeover request for the target remote driving task to the dispatch system, and this first operator console can be identified as the target operator console.

[0079] The user can then control the target console to handle the target remote driving task via the second input. The second input can be the input for handling the target remote driving task.

[0080] In some implementations, after a user completes a target remote driving task through the target console, the target console can send an exit signal to the scheduling system in response to a third input from the user to exit the remote driving task. The scheduling system can then send the exit signal to the server.

[0081] Here, the dispatch system is robust in managing remote driving requests, so the number of vehicles and the number of control consoles can be increased or decreased according to actual needs.

[0082] In some implementations, to prevent a user from initiating a takeover request for a remote driving task that has already been taken over, the method may further include, after determining that the target console has taken over the target remote driving task:

[0083] Update the target task status corresponding to the target remote driving task to the first status.

[0084] Broadcast the updated target task status to N control panels.

[0085] Here, the first state can be used to indicate that the target remote driving task has been taken over. The scheduling system can update the task status corresponding to multiple remote driving tasks and broadcast the updated task status of multiple remote driving tasks to N control consoles. This includes updating the target task status corresponding to the target remote driving task to the first state and broadcasting the updated target task status to N control consoles.

[0086] In some examples, three task states may be included: "state=0" indicates no takeover, "state=1" indicates takeover, and "state=2" indicates completion. After determining that the target console will take over the target remote driving task, the scheduling system can update the target remote driving task's task state, i.e., the target task state, to "state=1," which is the first state. Then, it can broadcast the target task state "state=1" to N consoles. The N consoles can display the target task state as "state=1," and users who see this state will not choose to take over the target remote driving task.

[0087] In addition, "state=2" indicates that the task has been completed, so users will not choose to take over remote driving tasks with a task status of "state=2".

[0088] In some examples, N consoles can also be configured so that remote driving tasks with task statuses of "state=1" and "state=2" cannot be selected for user takeover.

[0089] In some embodiments, when a user takes over a remote driving task through the console, but has not yet started or finished processing it, and there are other more urgent remote driving tasks that need to be processed first, the user can suspend the current remote driving task to process the more urgent remote driving task. The task status of the suspended remote driving task can then be changed from "state=1" to "state=0".

[0090] In this way, by updating the task status of remote driving tasks and broadcasting the updated task status to N consoles, users can avoid initiating takeover requests for remote driving tasks that have already been taken over, thus avoiding unnecessary burden on the dispatching system.

[0091] In some implementations, if a vehicle goes offline, it cannot be monitored, nor can its remote driving tasks be processed. Therefore, the dispatch system does not need to store the vehicle's information. To save storage space, the method may further include:

[0092] Receive vehicle status information for multiple vehicles sent by the server.

[0093] Record the receiving time of remote driving requests from multiple vehicles and the receiving time of vehicle status information.

[0094] If the time elapsed between the first receiving time corresponding to the first remote driving request of the first vehicle and the second receiving time corresponding to the first vehicle status information of the first vehicle and the current time both exceed the time elapsed threshold, delete the remote driving request and vehicle status information corresponding to the first vehicle.

[0095] Here, the server can also receive vehicle status information uploaded by the autonomous driving systems of multiple vehicles and send this information to the dispatch system. The dispatch system can record the time of receipt of remote driving requests from multiple vehicles and the time of receipt of vehicle status information.

[0096] The multiple vehicles may include the first vehicle. The first remote driving request can be the most recently received remote driving request from the first vehicle, and the first vehicle status information can be the most recently received vehicle status information from the first vehicle. The remote driving request and vehicle status information corresponding to the first vehicle may include the most recently received remote driving request and vehicle status information from the dispatch system, as well as previously received remote driving requests and vehicle status information. The first reception time can be the time when the dispatch system receives the first remote driving request, and the second reception time can be the time when the dispatch system receives the first vehicle status information. If the time elapsed between the first reception time and the current time exceeds a time elapsed threshold, it indicates that the first vehicle has gone offline. The time elapsed threshold can be set according to actual needs.

[0097] Thus, by deleting the remote driving request and vehicle status information of a vehicle when it goes offline, storage space can be saved.

[0098] Figure 3 A flowchart illustrating a remote driving method provided in one embodiment of this application is shown.

[0099] like Figure 3 As shown, this remote driving method can be applied to the target control console in a remote driving system and may include the following steps:

[0100] S310 receives remote driving requests from multiple vehicles broadcast by the dispatch system.

[0101] S320 displays remote driving tasks for multiple vehicles.

[0102] S330, in response to the user's first input on the target remote driving task among multiple remote driving tasks, sends a takeover request for the target remote driving task to the scheduling system.

[0103] Upon receiving a takeover success message from the dispatch system, S340 responds to a second user input and processes the target remote driving task.

[0104] Therefore, the dispatch system broadcasts remote driving requests for multiple vehicles to N operator consoles via a server. These requests include remote driving tasks. Upon receiving takeover requests for the target remote driving task from M first operator consoles, the system determines that the target operator console that first sent the takeover request will take over the target remote driving task, allowing the user to process the target remote driving task through that console. Because the dispatch system can broadcast remote driving requests for multiple vehicles to multiple operator consoles, multiple consoles can handle different remote driving tasks simultaneously. This improves the efficiency of remote driving task processing and ensures vehicle safety.

[0105] The specific details of S310-S340 are described in the relevant descriptions in the foregoing embodiments, and will not be repeated here.

[0106] The remote driving system in the relevant technology has only one control panel, which cannot receive and process remote driving tasks of multiple vehicles at the same time. It can only receive and process them one by one. Only after the previous remote driving task has been processed will the next remote driving task be received. In other words, the existing control panel can only process remote driving tasks in the order of receipt time, and cannot reasonably arrange the processing order of remote driving tasks.

[0107] In some implementations, to enable users to more rationally select the remote driving task to be taken over, the remote driving request may also include the task level corresponding to the remote driving task, and step 320 may include:

[0108] Multiple remote driving tasks are displayed in descending order of their corresponding task levels.

[0109] Here, the task level can be determined by the vehicle's autonomous driving system based on the vehicle's fault level. The higher the fault level, the higher the task level corresponding to the remote driving task. The vehicle's autonomous driving system can upload the task levels corresponding to multiple remote driving tasks to the server. The server can then send these task levels to the dispatch system, which broadcasts them to N control stations. The N control stations can then display the multiple remote driving tasks in descending order of their task levels, and can also display the task level corresponding to each remote driving task. The target control station can be any of the N control stations.

[0110] In some implementations, if there are multiple remote driving tasks with the same task level, they can be arranged and displayed in order of the time when they were received, from earliest to latest.

[0111] Then, the user can select the remote driving task they wish to take over from the displayed list of tasks. This list is for reference only; the user can choose the specific task to take over.

[0112] In this way, by displaying multiple remote driving tasks in descending order of task level, users can more rationally select the remote driving task to take over.

[0113] In some implementations, to prevent a user from initiating a takeover request for a remote driving task that has already been taken over, the method may further include:

[0114] Receive the task status corresponding to multiple remote driving tasks broadcast by the dispatch system.

[0115] Displays the task status of multiple remote driving tasks.

[0116] Here, the scheduling system can update the task status corresponding to multiple remote driving tasks and broadcast the task status corresponding to multiple remote driving tasks to N control consoles. The N control consoles can then display the task status corresponding to the multiple remote driving tasks. The N control consoles can include the target control console.

[0117] In some examples, three task states may be included: "state=0" indicates unprocessed, "state=1" indicates taken over, and "state=2" indicates completed. Users who see a remote driving task with a task state of "state=1" or "state=2" will not choose to take over.

[0118] In this way, by receiving and displaying the task status of multiple remote driving tasks broadcast by the dispatch system, users can avoid initiating takeover requests for remote driving tasks that have already been taken over, thus avoiding unnecessary burden on the dispatch system.

[0119] In some implementations, because network bandwidth cannot meet the needs of multiple control consoles simultaneously monitoring the same vehicle, the dispatch system can broadcast the monitoring status of multiple vehicles to N control consoles to avoid multiple control consoles initiating monitoring requests for the same vehicle. This monitoring status can be used to indicate whether the vehicle is being monitored by a control console. The N control consoles can display the vehicle's monitoring status to prevent users from initiating monitoring requests for vehicles already being monitored by other control consoles.

[0120] In some implementations, to facilitate user handling of remote driving tasks, the method may further include:

[0121] Receive vehicle status information from multiple vehicles broadcast by the dispatch system.

[0122] Displays vehicle status information for multiple vehicles, enabling users to handle remote driving tasks based on this information.

[0123] Here, each of the N control consoles can receive and display the status information of multiple vehicles broadcast by the dispatch system. The vehicle status information can include vehicle location information, vehicle operation information, sensor diagnostic information, and vehicle load information. Sensors can include LiDAR, map modules, and inertial measurement units (IMUs), and may also include other sensors, which are not limited here. This vehicle status information is used to assist users in handling remote driving tasks.

[0124] In some examples, the vehicle's load capacity can determine whether it is currently carrying goods. Upon receiving a remote driving request, if the vehicle is carrying goods, the user can determine the destination of the goods based on the vehicle's operational information and remotely drive the vehicle to deliver the goods to the destination. If the vehicle is not carrying goods, the user can remotely drive the vehicle away from the operational area. During the process of remotely driving the vehicle to deliver goods or leave the operational area, the user can determine the direction and distance of remote driving based on the vehicle's location information.

[0125] In some examples, users can determine whether a vehicle is malfunctioning and the severity of the malfunction based on the vehicle's sensor diagnostic information. Even if no remote driving request for the vehicle is received, users can proactively initiate a takeover request for the vehicle if the malfunction is severe.

[0126] In this way, by receiving and displaying vehicle status information, users can handle remote driving tasks based on the vehicle status information, and also monitor the vehicle status in a timely manner.

[0127] In some implementations, the control console can also send real-time information to the dispatch system, including its status, vehicle takeover status, whether it has taken over a remote driving task, and task suspension status. The control console's status can include idle, monitoring, task takeover, vehicle control, and no vehicle control. The dispatch system can package the status information from N control consoles and send it to a server for storage, forming an operation log.

[0128] In addition, the scheduling system can monitor N consoles in real time. If a console goes offline, the scheduling system will no longer send information to that console.

[0129] For example, the state transition of the control panel can be as follows: Figure 4 As shown, the initial state of the control panel can be idle (S0). When the user selects a vehicle on the control panel, the monitoring page for that vehicle will be displayed, and the control panel will be in monitoring state (S1). If the user exits the monitoring page, the control panel will return to idle state (S0). When the control panel is in idle state (S0) or monitoring state (S1), the user can select a remote driving task. If a takeover success message is received, the control panel will display the task information for the remote driving task and the corresponding vehicle status information, and the control panel will be in takeover state (S2). After taking over the remote driving task, the user can process the task through the control panel, and the control panel will be in vehicle control state (S3). When the remote driving task is completed, the user can control the control panel to exit remote driving and report the exit signal to the dispatch system. The dispatch system will then forward the signal to the server, and the control panel will be in uncontrolled state (S4). If remote driving continues at this point, the control panel can re-enter vehicle control state (S3). If the console is in the takeover task state S2 and the remote driving task is suspended, the console can enter the monitoring state S1. If the console is in the vehicle control state S3 and the remote driving task is suspended, in order to ensure safety, it is necessary to exit the remote driving before suspending it. Therefore, the console can go from the vehicle control state S3 to the non-vehicle control state S4, and then from the non-vehicle control state S4 back to the monitoring state S1.

[0130] Figure 5 A flowchart illustrating a remote driving method provided in one embodiment of this application is shown.

[0131] like Figure 5 As shown, this remote driving method can be applied to the server in a remote driving system and may include the following steps:

[0132] The S510 receives remote driving requests from multiple vehicles.

[0133] S520 sends remote driving requests for multiple vehicles to the dispatch system, so that the dispatch system broadcasts the remote driving requests for multiple vehicles to N control consoles, allowing users to handle remote driving tasks through N control consoles.

[0134] Therefore, the dispatch system broadcasts remote driving requests for multiple vehicles to N operator consoles via a server. These requests include remote driving tasks. Upon receiving takeover requests for the target remote driving task from M first operator consoles, the system determines that the target operator console that first sent the takeover request will take over the target remote driving task, allowing the user to process the target remote driving task through that console. Because the dispatch system can broadcast remote driving requests for multiple vehicles to multiple operator consoles, multiple consoles can handle different remote driving tasks simultaneously. This improves the efficiency of remote driving task processing and ensures vehicle safety.

[0135] The specific details of S510-S520 are described in the relevant descriptions in the foregoing embodiments, and will not be repeated here.

[0136] In some implementations, to avoid excessive remote driving tasks and resulting overload, the remote driving request can be sent by the vehicle's autonomous driving system when the vehicle's fault level is higher than a fault level threshold. To prevent users from ignoring vehicles with fault levels not higher than the fault level threshold, the method may further include:

[0137] Receive the status information of the second vehicle.

[0138] If the fault level of the second vehicle is not higher than the fault level threshold, a warning message is sent to the dispatch system so that the dispatch system can broadcast the warning message to N control consoles.

[0139] Here, the server can receive vehicle status information from multiple vehicles. If a vehicle experiences a malfunction, the vehicle status information can include the malfunction level, which can be determined by the vehicle's autonomous driving system based on its own malfunction information, such as sensor malfunction information. If the malfunction level is higher than a threshold, the vehicle's autonomous driving system can send a remote driving request to the server. If the vehicle experiences a malfunction, but the malfunction level is not higher than the threshold, the vehicle's autonomous driving system can send vehicle status information including the malfunction level to the server. The server can then generate a warning message and send it to the dispatch system. The dispatch system broadcasts this warning message to N control consoles. This warning message can include the remote driving task, the task level corresponding to the remote driving task, the reason for initiating the remote driving request, remote driving suggestions, and the remote driving task number, etc.

[0140] Specifically, the remote driving task included in the warning information can be the work task that the vehicle was performing at the time the warning information was generated. The remote driving task included in the remote driving request can be the work task that the vehicle was performing when the vehicle's autonomous driving system sent the remote driving request. The second vehicle can be any of multiple vehicles, and the second vehicle status information can include the second vehicle's fault level.

[0141] In this way, sending a remote driving request only when the vehicle fault level is higher than the fault level threshold can avoid an excessive number of remote driving tasks and an overburdened user. Sending a warning message when the vehicle fault level is not higher than the fault level threshold allows users to pay attention to vehicles that have faults but have low fault levels.

[0142] Figure 6 An architecture diagram of a remote driving system provided in one embodiment of this application is shown.

[0143] like Figure 6 As shown, Figure 1 The scheduling system 120 may include: an information receiving module 121, a status sending module 122, a task receiving module 123, a task suspension module 124, a status receiving module 125, and an information sending module 126.

[0144] The server 110 can be used to receive remote driving requests and vehicle status information sent by the autonomous driving systems of multiple vehicles, and send the remote driving request, vehicle status information, and warning information generated based on the vehicle status information to the dispatch system 120. It can also be used to receive and store the status information of the control panel sent by the dispatch system 120.

[0145] The information receiving module 121 can be used to receive vehicle status information sent by the server 110 and put it into the vehicle information queue, which can be updated in real time.

[0146] The task receiving module 123 can be used to receive remote driving requests and warning information sent by the server 110 and put them into the task information queue, which can be updated in real time. It is also used to receive the task status of the remote driving task sent by the status receiving module 125 and send the remote driving request, warning information and the task status of the remote driving task to the information sending module 126.

[0147] The status receiving module 125 can be used to receive status information of the operating consoles 130, vehicle monitoring requests, remote driving task takeover requests, exit signals, and remote driving tasks actively taken over and suspended by the user through the operating console. It can also determine the task status of the remote driving task based on the takeover request and exit signal, and determine the vehicle monitoring status based on the vehicle monitoring request. Furthermore, it can send the status information of the operating consoles to the status sending module 122, the task status of the remote driving task to the task receiving module 123, the vehicle monitoring status to the information sending module 126, and the remote driving tasks actively taken over and suspended to the task suspension module 124.

[0148] The task suspension module 124 can be used to send remote driving tasks that have been actively taken over and suspended to the information sending module 126.

[0149] The information sending module 126 can be used to receive vehicle status information sent by the information receiving module 121, remote driving requests and warning information sent by the task receiving module 123, remote driving tasks that are actively taken over and suspended sent by the task suspension module 124, and vehicle monitoring status sent by the status receiving module 125, and send the vehicle status information, remote driving requests, warning information, remote driving tasks that are actively taken over and suspended, and vehicle monitoring status to N operating consoles 130.

[0150] The status sending module 122 can be used to receive the status information of the operating console sent by the status receiving module 125 and send it to the server 110.

[0151] N control consoles 130 can be used to send control console status information, vehicle monitoring requests, remote driving task takeover requests, exit signals, and remote driving tasks actively taken over and suspended by the user through the control console to the status receiving module 125, and to receive vehicle status information, remote driving requests, warning information, actively taken over and suspended remote driving tasks, and vehicle monitoring status sent by the information sending module 126.

[0152] Therefore, the dispatch system broadcasts remote driving requests for multiple vehicles to N operator consoles via a server. These requests include remote driving tasks. Upon receiving takeover requests for the target remote driving task from M first operator consoles, the system determines that the target operator console that first sent the takeover request will take over the target remote driving task, allowing the user to process the target remote driving task through that console. Because the dispatch system can broadcast remote driving requests for multiple vehicles to multiple operator consoles, multiple consoles can handle different remote driving tasks simultaneously. This improves the efficiency of remote driving task processing and ensures vehicle safety.

[0153] Based on the same inventive concept, embodiments of this application also provide a remote driving device. The following, in conjunction with… Figure 7 The remote driving device provided in the embodiments of this application will be described in detail.

[0154] Figure 7 A schematic diagram of the structure of a remote driving device provided in one embodiment of this application is shown.

[0155] like Figure 7 As shown, this remote driving device can be applied to a dispatch system and may include:

[0156] The first receiving module 701 is used to receive remote driving requests from multiple vehicles sent by the server. The remote driving requests include remote driving tasks.

[0157] The first broadcast module 702 is used to broadcast remote driving requests for multiple vehicles to N control consoles, where N is an integer greater than 1.

[0158] The second receiving module 703 is used to receive takeover requests for target remote driving tasks sent by M first operating consoles. The target remote driving task is the remote driving task corresponding to the target vehicle. Multiple vehicles include the target vehicle, 1≤M≤N, and M is a positive integer.

[0159] The first sending module 704 is used to determine, when M>1, the time when the M first operating stations send takeover requests, to take over the target remote driving task, and send a takeover success message to the target operating station so that the user can process the target remote driving task through the target operating station. The target operating station is the operating station that sent the takeover request earliest among the M first operating stations.

[0160] Therefore, the dispatch system broadcasts remote driving requests for multiple vehicles to N operator consoles via a server. These requests include remote driving tasks. Upon receiving takeover requests for the target remote driving task from M first operator consoles, the system determines that the target operator console that first sent the takeover request will take over the target remote driving task, allowing the user to process the target remote driving task through that console. Because the dispatch system can broadcast remote driving requests for multiple vehicles to multiple operator consoles, multiple consoles can handle different remote driving tasks simultaneously. This improves the efficiency of remote driving task processing and ensures vehicle safety.

[0161] In some implementations, to prevent a user from initiating a takeover request for a remote driving task that has already been taken over, the device may further include:

[0162] The update module is used to update the target task status corresponding to the target remote driving task to the first state after determining that the target console has taken over the target remote driving task. The first state indicates that the target remote driving task has been taken over.

[0163] The second broadcast module is used to broadcast the updated target task status to N consoles.

[0164] In some implementations, if a vehicle goes offline, it cannot be monitored, nor can its remote driving tasks be processed. Therefore, the dispatch system does not need to store the vehicle's information. To save storage space, the device may further include:

[0165] The third receiving module is used to receive vehicle status information of multiple vehicles sent by the server.

[0166] The recording module is used to record the time of receipt of remote driving requests from multiple vehicles and the time of receipt of vehicle status information.

[0167] The deletion module is used to delete the remote driving request and vehicle status information corresponding to the first vehicle when the time elapsed between the first receiving time corresponding to the first remote driving request of the first vehicle and the second receiving time corresponding to the first vehicle status information of the first vehicle and the current time exceeds a time elapsed threshold. This includes multiple vehicles, including the first vehicle.

[0168] Based on the same inventive concept, this application also provides another remote driving device. The following describes... Figure 8 The remote driving device provided in the embodiments of this application will be described in detail.

[0169] Figure 8 A schematic diagram of another remote driving device provided in one embodiment of this application is shown.

[0170] like Figure 8 As shown, the remote driving device can be applied to a target control console and may include:

[0171] The fourth receiving module 801 is used to receive remote driving requests from multiple vehicles broadcast by the dispatch system. The remote driving requests include remote driving tasks.

[0172] The first display module 802 is used to display remote driving tasks corresponding to multiple vehicles.

[0173] The second sending module 803 is used to send a takeover request for the target remote driving task to the scheduling system in response to the user's first input on the target remote driving task among multiple remote driving tasks.

[0174] The processing module 804 is used to process the target remote driving task in response to a second input from the user upon receiving a takeover success message sent by the scheduling system.

[0175] Therefore, the dispatch system broadcasts remote driving requests for multiple vehicles to N operator consoles via a server. These requests include remote driving tasks. Upon receiving takeover requests for the target remote driving task from M first operator consoles, the system determines that the target operator console that first sent the takeover request will take over the target remote driving task, allowing the user to process the target remote driving task through that console. Because the dispatch system can broadcast remote driving requests for multiple vehicles to multiple operator consoles, multiple consoles can handle different remote driving tasks simultaneously. This improves the efficiency of remote driving task processing and ensures vehicle safety.

[0176] In some implementations, to enable users to more rationally select the remote driving task to be taken over, the remote driving request may also include the task level corresponding to the remote driving task, and the first display module 802 may include:

[0177] The display submodule is used to display multiple remote driving tasks in descending order of their corresponding task levels.

[0178] In some implementations, to prevent a user from initiating a takeover request for a remote driving task that has already been taken over, the device may further include:

[0179] The fifth receiving module is used to receive the task status corresponding to multiple remote driving tasks broadcast by the dispatch system.

[0180] The second display module is used to display the task status corresponding to multiple remote driving tasks.

[0181] In some embodiments, to facilitate user handling of remote driving tasks, the device may further include:

[0182] The sixth receiving module is used to receive vehicle status information from multiple vehicles broadcast by the dispatch system.

[0183] The third display module is used to display the vehicle status information of multiple vehicles, so that users can handle remote driving tasks based on the vehicle status information.

[0184] Based on the same inventive concept, this application also provides another remote driving device. The following describes... Figure 9 The remote driving device provided in the embodiments of this application will be described in detail.

[0185] Figure 9 A schematic diagram of the structure of another remote driving device provided in one embodiment of this application is shown.

[0186] like Figure 9 As shown, this remote driving device can be applied to a server and may include:

[0187] The seventh receiving module 901 is used to receive remote driving requests from multiple vehicles. These remote driving requests include remote driving tasks.

[0188] The third sending module 902 is used to send remote driving requests for multiple vehicles to the dispatching system, so that the dispatching system broadcasts the remote driving requests for multiple vehicles to N control consoles, so that users can process remote driving tasks through N control consoles, where N is an integer greater than 1.

[0189] Therefore, the dispatch system broadcasts remote driving requests for multiple vehicles to N operator consoles via a server. These requests include remote driving tasks. Upon receiving takeover requests for the target remote driving task from M first operator consoles, the system determines that the target operator console that first sent the takeover request will take over the target remote driving task, allowing the user to process the target remote driving task through that console. Because the dispatch system can broadcast remote driving requests for multiple vehicles to multiple operator consoles, multiple consoles can handle different remote driving tasks simultaneously. This improves the efficiency of remote driving task processing and ensures vehicle safety.

[0190] In some implementations, to avoid excessive remote driving tasks and resulting overload, the remote driving request can be sent by the vehicle's autonomous driving system when the vehicle's fault level is higher than a fault level threshold. To prevent users from ignoring vehicles with fault levels not higher than the fault level threshold, the device may further include:

[0191] The eighth receiving module is used to receive the second vehicle status information, which includes the second vehicle's fault level.

[0192] The fourth sending module is used to send a warning message to the dispatch system when the fault level of the second vehicle is not higher than the fault level threshold, so that the dispatch system can broadcast the warning message to N control consoles.

[0193] Figure 10 A schematic diagram of the structure of an electronic device provided in one embodiment of this application is shown.

[0194] like Figure 10 As shown, the electronic device 10 is a structural diagram of an exemplary hardware architecture of an electronic device capable of implementing the remote driving method, system, and apparatus according to the embodiments of this application. This electronic device may refer to the electronic device in the embodiments of this application.

[0195] The electronic device 10 may include a processor 1001 and a memory 1002 storing computer program instructions.

[0196] Specifically, the processor 1001 may include a central processing unit (CPU), an application-specific integrated circuit (ASIC), or one or more integrated circuits that can be configured to implement the embodiments of this application.

[0197] Memory 1002 may include mass storage for data or instructions. For example, and not limitingly, memory 1002 may include a hard disk drive (HDD), floppy disk drive, flash memory, optical disk, magneto-optical disk, magnetic tape, or Universal Serial Bus (USB) drive, or a combination of two or more of these. Where appropriate, memory 1002 may include removable or non-removable (or fixed) media. Where appropriate, memory 1002 may be internal or external to the integrated gateway disaster recovery device. In a particular embodiment, memory 1002 is non-volatile solid-state memory. In a particular embodiment, memory 1002 may include read-only memory (ROM), random access memory (RAM), disk storage media device, optical storage media device, flash memory device, electrical, optical, or other physical / tangible memory storage device. Therefore, typically, memory 1002 includes one or more tangible (non-transitory) computer-readable storage media (e.g., memory devices) encoded with software including computer-executable instructions, and when the software is executed (e.g., by one or more processors), it is operable to perform the operations described with reference to the method according to one aspect of this application.

[0198] The processor 1001 implements any of the remote driving methods described in the above embodiments by reading and executing computer program instructions stored in the memory 1002.

[0199] In one example, the electronic device may also include a communication interface 1003 and a bus 1004. Wherein, for example... Figure 10 As shown, the processor 1001, memory 1002, and communication interface 1003 are connected through bus 1004 and complete communication with each other.

[0200] The communication interface 1003 is mainly used to realize communication between various modules, devices, units and / or equipment in the embodiments of this application.

[0201] Bus 1004 includes hardware, software, or both, that couples components of an electronic device together. For example, and not limitingly, the bus may include an Accelerated Graphics Port (AGP) or other graphics bus, an Enhanced Industry Standard Architecture (EISA) bus, a Front Side Bus (FSB), HyperTransport (HT) interconnect, an Industry Standard Architecture (ISA) bus, an Infinite Bandwidth Interconnect, a Low Pin Count (LPC) bus, a memory bus, a Microchannel Architecture (MCA) bus, a Peripheral Component Interconnect (PCI) bus, a PCI-Express (PCI-X) bus, a Serial Advanced Technology Attachment (SATA) bus, a Video Electronics Standards Association Local (VLB) bus, or other suitable buses, or combinations of two or more of these. Where appropriate, bus 1004 may include one or more buses. Although specific buses are described and illustrated in embodiments of this application, any suitable bus or interconnect is contemplated herein.

[0202] The electronic device can execute the remote driving method in the embodiments of this application, thereby achieving a combination Figures 1 to 9 Described remote driving methods, systems, and devices.

[0203] Furthermore, in conjunction with the remote driving methods in the above embodiments, this application embodiment can provide a computer storage medium for implementation. The computer storage medium stores computer program instructions; when these computer program instructions are executed by a processor, they implement any of the remote driving methods in the above embodiments.

[0204] It should be clarified that this application is not limited to the specific configurations and processes described above and shown in the figures. For the sake of brevity, detailed descriptions of known methods are omitted here. In the above embodiments, several specific steps are described and shown as examples. However, the method process of this application is not limited to the specific steps described and shown. Those skilled in the art can make various changes, modifications, and additions, or change the order of steps, after understanding the spirit of this application.

[0205] The functional blocks shown in the above-described structural diagram can be implemented as hardware, software, firmware, or a combination thereof. When implemented in hardware, they can be, for example, electronic circuits, application-specific integrated circuits (ASICs), appropriate firmware, plug-ins, function cards, etc. When implemented in software, the elements of this application are programs or code segments used to perform the required tasks. Programs or code segments can be stored on a machine-readable medium or transmitted over a transmission medium or communication link via data signals carried on a carrier wave. "Machine-readable medium" can include any medium capable of storing or transmitting information. Examples of machine-readable media include electronic circuits, semiconductor memory devices, ROM, flash memory, erasable ROM (EROM), floppy disks, CD-ROMs, optical disks, hard disks, fiber optic media, radio frequency (RF) links, etc. Code segments can be downloaded via computer networks such as the Internet, intranets, etc.

[0206] It should also be noted that the exemplary embodiments mentioned in this application describe methods or systems based on a series of steps or apparatus. However, this application is not limited to the order of the above steps; that is, the steps can be performed in the order mentioned in the embodiments, or in a different order, or several steps can be performed simultaneously.

[0207] The aspects of this application have been described above with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of this application. It should be understood that each block in the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing apparatus to produce a machine such that these instructions, executable via the processor of the computer or other programmable data processing apparatus, enable the implementation of the functions / actions specified in one or more blocks of the flowchart illustrations and / or block diagrams. Such a processor can be, but is not limited to, a general-purpose processor, a special-purpose processor, a special application processor, or a field-programmable logic circuit. It is also understood that each block in the block diagrams and / or flowcharts, and combinations of blocks in the block diagrams and / or flowcharts, can also be implemented by dedicated hardware performing the specified functions or actions, or can be implemented by a combination of dedicated hardware and computer instructions.

[0208] The above description is merely a specific implementation of this application. Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the specific working processes of the systems, modules, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here. It should be understood that the protection scope of this application is not limited thereto. Any person skilled in the art can easily conceive of various equivalent modifications or substitutions within the technical scope disclosed in this application, and these modifications or substitutions should all be covered within the protection scope of this application.

Claims

1. A remote driving method, applied to a dispatching system, characterized in that, include: The system receives remote driving requests from multiple vehicles sent by a server, the remote driving requests including remote driving tasks. Broadcast remote driving requests for the multiple vehicles to N control consoles, where N is an integer greater than 1. Receive takeover requests for a target remote driving task from M first control consoles. The target remote driving task is the remote driving task corresponding to a target vehicle. The multiple vehicles include the target vehicle, 1 ≤ M ≤ N, where M is a positive integer. When M > 1, the target operator is determined to take over the target remote driving task based on the time when the M first operators send the takeover request, and a takeover success message is sent to the target operator so that the user can process the target remote driving task through the target operator. The target operator is the operator that sent the takeover request earliest among the M first operators.

2. The method according to claim 1, characterized in that, After determining that the target control console has taken over the target remote driving task, the method further includes: The target task status corresponding to the target remote driving task is updated to a first status, which indicates that the target remote driving task has been taken over. Broadcast the updated target task status to the N control consoles.

3. The method according to claim 1, characterized in that, The method further includes: Receive vehicle status information for multiple vehicles sent by the server. Record the time of receipt of the remote driving request from the multiple vehicles and the time of receipt of the vehicle status information. If the time elapsed between the first receiving time corresponding to the first remote driving request of the first vehicle and the second receiving time corresponding to the first vehicle status information of the first vehicle and the current time exceeds a time elapsed threshold, the remote driving request and vehicle status information corresponding to the first vehicle are deleted, and the multiple vehicles include the first vehicle.

4. A remote driving method, applied to a target control console, characterized in that, include: The system receives remote driving requests from multiple vehicles broadcast by the dispatch system, the remote driving requests including remote driving tasks. Display the remote driving tasks corresponding to the multiple vehicles. In response to the user's first input regarding a target remote driving task among the multiple remote driving tasks, a takeover request for the target remote driving task is sent to the scheduling system. Upon receiving a takeover success message from the scheduling system, the target remote driving task is processed in response to the user's second input. The remote driving request also includes the task level corresponding to the remote driving task, and the display of the remote driving tasks corresponding to the multiple vehicles includes: The multiple remote driving tasks are displayed in descending order of their corresponding task levels.

5. The method according to claim 4, characterized in that, The method further includes: Receive the task status corresponding to multiple remote driving tasks broadcast by the dispatch system. Displays the task status corresponding to multiple remote driving tasks.

6. The method according to claim 4, characterized in that, The method further includes: Receive vehicle status information of multiple vehicles broadcast by the dispatch system. The system displays the vehicle status information of the multiple vehicles, enabling the user to process the remote driving task based on the vehicle status information.

7. A remote driving method applied to a server, characterized in that, include: Receive remote driving requests from multiple vehicles, wherein the remote driving requests include remote driving tasks. Send remote driving requests for the multiple vehicles to the dispatch system, so that the dispatch system broadcasts the remote driving requests for the multiple vehicles to N control consoles, so that users can process the remote driving tasks through the N control consoles, where N is an integer greater than 1; The remote driving request is sent by the vehicle's autonomous driving system when the vehicle's fault level is higher than the fault level threshold. The method further includes: Receive the second vehicle status information, which includes the second vehicle's fault level. If the fault level of the second vehicle is not higher than the fault level threshold, a warning message is sent to the dispatch system so that the dispatch system broadcasts the warning message to the N control consoles.

8. A remote driving system, characterized in that, include: The server is used to receive remote driving requests from multiple vehicles and send these requests to the dispatch system. Each remote driving request includes a remote driving task. The scheduling system is used to broadcast remote driving requests for the multiple vehicles to N control consoles, where N is an integer greater than 1. The N control consoles are used to display the remote driving tasks corresponding to the multiple vehicles. M of the N control consoles are first control consoles used to respond to a user's first input on a target remote driving task among the multiple remote driving tasks, sending a takeover request for the target remote driving task to the scheduling system. The target remote driving task is the remote driving task corresponding to a target vehicle. The multiple vehicles include the target vehicle, 1 ≤ M ≤ N, where M is a positive integer. The scheduling system is also used to determine, when M > 1, the target operating station to take over the target remote driving task based on the time when the M first operating stations send the takeover request, and to send a takeover success message to the target operating station so that the user can process the target remote driving task through the target operating station. The target operating station is the operating station that sent the takeover request earliest among the M first operating stations. The target operating station is used to process the target remote driving task in response to the user's second input.

Images