Interaction method and interactive device, terminal equipment and storage medium

Abstract

This application discloses an interactive method for a remote vehicle chauffeur service, comprising: responding to a user-initiated call service request, presenting a call service order corresponding to the call service request within the cabin of the remote chauffeur service, the call service request being used by the user to summon a vehicle to a designated location; simultaneously, responding to the safety officer's processing of the call service order within the cabin, presenting the completion status information of the call service order within the cabin. This allows the remote vehicle chauffeur service to display the user-initiated call service order and the completion status information of the call service order, enabling the safety officer to process the call service order and better complete the call service. Furthermore, this interactive method eliminates the need for the user to contact the chauffeur, making the handover smoother, faster, and more efficient, while also preventing the safety issues associated with the chauffeur entering the vehicle. This application also discloses an interactive device, a terminal device, and a storage medium.

Description

Technical Field

[0001] This application relates to the field of transportation, and in particular to an interactive method, interactive device, terminal equipment, and computer-readable storage medium for a remote vehicle chauffeur service. Background Technology

[0002] In daily vehicle use, if users park their vehicles in large shopping malls or supermarkets, the parking spaces may be far from the elevators, requiring a long walk after parking. Alternatively, weather conditions may make retrieving the vehicle inconvenient. While ride-hailing services offer chauffeur services, these are more common when users are under the influence of alcohol and cannot drive. When users call for a chauffeur via their mobile phones, it often takes time for the driver to arrive at the vehicle after the system dispatches the order, and the owner needs to be present to retrieve the car keys before the driver can take the vehicle to the owner's residence. During this process, the driver may also face risks such as inconvenience or property damage due to entering the vehicle. Summary of the Invention

[0003] In view of this, the present application provides an interactive method for a remote vehicle chauffeur service, including:

[0004] In response to a user-initiated summoning service request, a summoning service order corresponding to the summoning service request is displayed in the cabin of the remote chauffeur service. The summoning service request is used to allow the user to summon a vehicle to a specified summoning location.

[0005] In response to the safety officer's processing of the call service order in the cockpit, the completion status information of the call service order is displayed in the cockpit.

[0006] In this way, the user-initiated call service order and its completion status information can be displayed in the remote vehicle chauffeur service, allowing the safety operator to process the order and better complete the call service. Furthermore, the interaction method of this application eliminates the need for the user to contact the chauffeur, making the handover smoother, faster, and more efficient, while also preventing the safety issues associated with items due to the chauffeur entering the vehicle. Simultaneously, by displaying the order completion status information, the safety operator can clearly understand the situation at each stage of the service process, ensuring the vehicle can smoothly reach the user's call location and avoiding potential accidents that may occur given the immaturity of current autonomous driving technology. Moreover, by remotely controlling the vehicle, the safety operator can monitor driving safety without requiring the user to enter the vehicle.

[0007] The process of responding to the call service order by the safety officer in the cockpit, and presenting the completion status information of the call service order in the cockpit, includes:

[0008] When the safety officer in the cockpit accepts the call service order, the remote cockpit displays the order status as "waiting to depart".

[0009] Thus, after the safety officer accepts the summoning service order, the corresponding order status is displayed through the remote cockpit, allowing the safety officer to understand the current order status within the cockpit and begin preparations for the order service based on the waiting departure status.

[0010] After the safety officer in the cockpit accepts the summons service order, the interaction method further includes:

[0011] The vehicle system is in a self-check state within the cockpit.

[0012] If the vehicle system passes the self-test, the remote cockpit will send a prompt to the safety officer indicating that the safety officer can perform a manual inspection, and display a confirmation control for the result of the manual inspection.

[0013] In response to the safety officer's operation of the result confirmation control, the remote cockpit displays a confirmation departure control so that the safety officer confirms departure for the call service order.

[0014] In this way, by responding to the safety officer's order acceptance, the system automatically transitions to vehicle system self-check and safety officer manual inspection, improving the processing efficiency of call service orders. Simultaneously, the inspection process status is displayed to the safety officer, allowing them to clearly understand the current vehicle system self-check status.

[0015] The interaction method also includes:

[0016] If an anomaly is detected during the vehicle system's self-check or during the manual check, the remote cockpit will send an anomaly alert to the safety officer and terminate the call service order.

[0017] In this way, when an anomaly is detected during inspection, the status can be automatically switched, and the safety officer can confirm and determine whether to proceed with the order service, thereby improving order processing efficiency.

[0018] The process of responding to the call service order by the safety officer in the cockpit, and presenting the completion status information of the call service order in the cockpit, further includes:

[0019] After the safety driver confirms the dispatch of the summoning service order, if the area where the vehicle is located belongs to the first area, the remote cockpit displays the vehicle's autopilot activation control, where the first area is the area where the vehicle's autopilot is available.

[0020] In response to the safety operator's operation of the autonomous driving activation control, the process of the vehicle autonomously driving towards the summoned location within the first area is presented in the cockpit.

[0021] In this way, the safety operator can notify the vehicle from inside the cabin that autonomous driving is possible within the first area, allowing the safety operator to take control of the vehicle and engage autonomous driving, thus reducing the operator's workload. Simultaneously, the cabin displays the vehicle's autonomous driving process from the first area to the designated location, enabling the safety operator to remotely monitor the process and ensuring a certain level of safety for autonomous driving.

[0022] The process of responding to the call service order by the safety officer in the cockpit, and presenting the completion status information of the call service order in the cockpit, further includes:

[0023] After the safety driver confirms the dispatch of the summoning service order, if the area where the vehicle is located belongs to the second area, the remote cockpit will provide feedback to the safety driver that the vehicle can be manually driven. The second area is the area where the vehicle's autonomous driving is not available.

[0024] After the safety officer remotely drives the vehicle manually, the vehicle will be displayed as being in manual driving mode inside the cabin.

[0025] Thus, when the vehicle is in the second zone, the safety operator in the remote driving service cabin can remotely and manually drive the vehicle to ensure it can continue moving in areas where autonomous driving is not possible, or, in an emergency, manually take over the vehicle, improving driving safety during the call service. At the same time, clearly distinguishing between autonomous driving and safety operator driving facilitates safer takeover and reduces the need for multiple systems to operate simultaneously.

[0026] The process of responding to the call service order by the safety officer in the cockpit, and presenting the completion status information of the call service order in the cockpit, includes:

[0027] When the vehicle is in a preset scenario, the remote cockpit provides a first prompt to the safety operator, reminding the safety operator to monitor the vehicle's autonomous driving.

[0028] This allows for early warnings of potential driving risks associated with autonomous driving, improving driving safety during summoning services.

[0029] The process of responding to the call service order by the safety officer in the cockpit, and presenting the completion status information of the call service order in the cockpit, includes:

[0030] In response to the safety officer's confirmation of the call service order, the remote cockpit displays the order status as "calling in progress".

[0031] In this way, the real-time status display allows the safety operator to understand and confirm the order status after departure from the cockpit, and remotely control the vehicle to drive to the summoned location according to the contents of the summon service order.

[0032] The process of responding to the call service order by the safety officer in the cockpit, and presenting the completion status information of the call service order in the cockpit, further includes:

[0033] If the parking space corresponding to the target summoning location is available for automatic parking, the remote cockpit displays the process of the vehicle automatically parking into the summoning location parking space.

[0034] This allows safety officers to monitor the safe final parking of vehicles and prevent parking errors.

[0035] The process of the remote cockpit displaying the vehicle automatically parking into the summoned parking space also includes:

[0036] If an abnormal situation occurs during the automatic parking process of the vehicle, the remote cockpit displays a second prompt message to prompt the safety operator to take over the vehicle;

[0037] In response to the safety officer's remote takeover of the vehicle, the remote cockpit displays that the vehicle has entered manual parking driving mode.

[0038] In this way, various abnormal situations that occur during automatic parking can be managed, ensuring that the vehicle can be successfully parked in the summoned parking space.

[0039] The process of responding to the call service order by the safety officer in the cockpit, and presenting the completion status information of the call service order in the cockpit, further includes:

[0040] If the parking space corresponding to the summoning location is unavailable for automatic parking, in response to the vehicle ceasing its automatic driving operation, the remote cockpit displays a third prompt message to prompt the safety driver to remotely take over the vehicle.

[0041] In response to the safety officer's remote takeover of the vehicle, the remote cockpit displays that the vehicle has entered manual parking driving mode.

[0042] In this way, if automatic parking is unavailable, the system can provide a prompt to the safety operator to take over manually, allowing the vehicle to be parked smoothly in the designated parking space.

[0043] The process of responding to the call service order by the safety officer in the cockpit, and presenting the completion status information of the call service order in the cockpit, further includes:

[0044] Once it is confirmed that the vehicle has entered the parking space at the summoning location, the remote cockpit displays the order status as "waiting to pick up the vehicle".

[0045] This allows the safety officer to know from inside the cabin that the vehicle has entered the designated parking space and parked successfully, ready for the user to retrieve the car.

[0046] The process of responding to the call service order by the safety officer in the cockpit, and presenting the completion status information of the call service order in the cockpit, further includes:

[0047] When the remote cockpit detects that the vehicle has been put into parking gear in manual parking mode, it displays an arrival confirmation control.

[0048] In response to the safety officer's operation on the confirmation arrival control, the remote cockpit displays the order status as "waiting to pick up the vehicle".

[0049] In this way, after manually parking, all passengers can see from inside the cabin that the vehicle has entered the summoned parking space and parked successfully, waiting for the user to pick up the car.

[0050] The process of responding to the call service order by the safety officer in the cockpit, and presenting the completion status information of the call service order in the cockpit, further includes:

[0051] When the order status is "waiting for vehicle pickup", the remote cockpit displays a confirmation "service ended" control.

[0052] In response to the safety officer's confirmation that the service has ended, the call service order is closed inside the cockpit.

[0053] Thus, a confirmation control for service termination is displayed, allowing security personnel to control the termination status of the call service by manually confirming whether it has ended.

[0054] The interaction method also includes:

[0055] After the waiting period for vehicle retrieval has lasted for a preset time, the summoning service order is closed inside the cabin.

[0056] Thus, once the order status transitions to the waiting-to-pick-up status, if the safety driver does not activate the service completion confirmation control within the preset time, the summon service order will be automatically closed in the cabin, completing this remote chauffeur service.

[0057] The interaction method also includes:

[0058] When the order status is "waiting for vehicle pickup", in response to the safety driver's remote control of the vehicle to take over manual driving, the remote cockpit displays that the vehicle has entered manual driving mode and the order status is displayed again as "calling".

[0059] In this way, while waiting for the user to pick up the car, the driver can manually take over the driving and put the vehicle back into the summoned state to handle any unexpected situations that may occur while waiting for the user to pick up the car.

[0060] This application also provides an interactive device for remote vehicle chauffeur services, including:

[0061] The first presentation module is used to respond to a user-initiated summoning service request and present a summoning service order corresponding to the summoning service request in the cabin of the remote chauffeur service. The summoning service request is used to allow the user to summon a vehicle to a specified summoning location.

[0062] The second presentation module is used to respond to the safety officer's processing of the call service order in the cockpit and present the completion status information of the call service order in the cockpit.

[0063] This application also provides a terminal device, wherein the vehicle includes a memory and a processor, the memory storing a computer program, which, when executed by the processor, implements the method described in any of the above-mentioned embodiments.

[0064] This application also provides a non-volatile computer-readable storage medium that, when the computer program is executed by one or more processors, implements the method described in any of the above embodiments.

[0065] This application, in response to a user-initiated call service request, presents a corresponding call service order within the remote chauffeur service cabin. The call service request allows the user to summon a vehicle to a designated location. Simultaneously, in response to the safety operator's processing of the call service order within the cabin, the completion status information of the call service order is displayed within the cabin. This allows the display of user-initiated call service orders and their completion status information within the remote vehicle chauffeur service, enabling the safety operator to process the order and better complete the call service. Furthermore, by displaying the order completion status information, the safety operator can clearly understand the status information of each node during the service process, ensuring the vehicle can smoothly reach the user's summoned location and avoiding potential accidents that may occur given the immaturity of current autonomous driving technology. Moreover, remote control of the vehicle by the safety operator allows for safe monitoring of the vehicle's operation without requiring the user to contact a chauffeur, making the handover smoother and faster, while also eliminating the security risks associated with a chauffeur entering the vehicle.

[0066] Additional aspects and advantages of the embodiments of this application will be set forth in part in the description which follows, and in part will be obvious from the description, or may be learned by practice of this application. Attached Figure Description

[0067] The above and / or additional aspects and advantages of this application will become apparent and readily understood from the description of the embodiments taken in conjunction with the following drawings, wherein:

[0068] Figure 1 This is a flowchart illustrating the interaction method of this application;

[0069] Figure 2 This is a schematic diagram of the interactive device of this application;

[0070] Figure 3 This is an example diagram of the interaction method in this application;

[0071] Figure 4 This is a flowchart illustrating the interaction method of this application;

[0072] Figure 5 This is a flowchart illustrating the interaction method of this application;

[0073] Figure 6 This is a flowchart illustrating the interaction method of this application;

[0074] Figure 7 This is a flowchart illustrating the interaction method of this application;

[0075] Figure 8This is a flowchart illustrating the interaction method of this application;

[0076] Figure 9 This is a flowchart illustrating the interaction method of this application. Detailed Implementation

[0077] The embodiments of this application are described in detail below. Examples of the embodiments are shown in the accompanying drawings, wherein the same or similar reference numerals denote the same or similar elements or elements having the same or similar functions throughout. The embodiments described below with reference to the accompanying drawings are exemplary and are only used to explain the embodiments of this application, and should not be construed as limiting the embodiments of this application.

[0078] Please see Figure 1 This application provides an interactive method for a remote vehicle chauffeur service, including:

[0079] 01: In response to a user's call service request, a call service order corresponding to the call service request is displayed in the cabin of the remote chauffeur service. The call service request is used to allow the user to summon a vehicle to the specified call location.

[0080] 02: In response to the safety officer's processing of the call service order in the cockpit, display the completion status information of the call service order in the cockpit.

[0081] Accordingly, please refer to Figure 2 This application also provides an interactive device 100 for remote vehicle chauffeur services. The interactive method for remote vehicle chauffeur services in this application can be implemented by the interactive device 100. The interactive device 100 includes a first presentation module 110 and a second presentation module 120. Step 01 can be implemented by the first presentation module 110, and step 02 can be implemented by the second presentation module 120. Alternatively, the first presentation module 110 is used to respond to a user's call service request and present a call service order corresponding to the call service request in the cabin of the remote chauffeur service. The call service request is used for the user to call a vehicle to a specified call location. The second presentation module 120 is used to respond to the safety officer's processing of the call service order in the cabin and present the completion status information of the call service order in the cabin.

[0082] This application also provides a terminal device. The terminal device includes a memory and a processor. The memory stores a computer program, and the processor is used to respond to a user-initiated call service request, present a call service order corresponding to the call service request in the cabin of the remote chauffeur service, the call service request being used by the user to summon a vehicle to a designated call location; and to respond to the safety officer's processing of the call service order in the cabin, present the completion status information of the call service order in the cabin.

[0083] Specifically, the summoning service is a remote chauffeur service. Users place orders remotely through the summoning service, and safety drivers remotely control the vehicle through a remote cockpit to drive the vehicle from its current location to the user's designated summoning location.

[0084] The remote chauffeur service's cockpit can include a safety management platform and a human safety operator. The safety operator can monitor the vehicle's driving process and manually take over driving when necessary. Through the remote intelligent cockpit, the safety operator can monitor the vehicle's assisted driving system and intervene promptly to ensure safety. For scenarios not covered by assisted driving systems, the safety operator can perform remote driving. Within the remote chauffeur service cockpit, video displays can assist the safety operator in perceiving the vehicle's surroundings, providing support for safety monitoring and driving. Simultaneously, the terminal device can display summoning service order information and order status information to fulfill user-initiated summoning service requests.

[0085] Step 01: In response to the user's summoning service request, a summoning service order corresponding to the summoning service request is presented in the cabin of the remote chauffeur service. The summoning service request is used to allow the user to summon a vehicle to the specified summoning location.

[0086] The summoning service request allows users to summon a vehicle to a specified location. The specific summoning service functions are as described above. Users can initiate a summoning service request via a terminal device, including mobile devices with specific applications installed. For example, a user's mobile phone may have an application providing summoning services, chauffeur services, and other services. The user can open the application and access the summoning service entry to summon the vehicle. The summoning service entry can take several forms: one is an entry displayed in a graphical user interface (GUI) as a specific user interface design element or control; other forms include a voice-activated summoning service entry and an entry activated by specific function buttons within the vehicle's cabin. When the summoning service entry is presented in a GUI, clicking this GUI design element or control will take the user to the service order page. Please refer to [link / reference]. Figure 3 , Figure 3 The relevant page displays a "Call for Service" entry control, which users can click to enter the service order page.

[0087] Upon receiving a user's request for a ride-hailing service, the remote chauffeur service will display a ride-hailing service order corresponding to the request within the vehicle's cabin.

[0088] Within the cabin of the remote chauffeur service, a service request can be displayed via a terminal device. This terminal device includes a display unit, which can be a standalone computer or a non-standalone computer. The service request can be displayed on the display unit. The service request can be displayed on multiple display units simultaneously or on a single display unit.

[0089] Step 02: In response to the safety officer's processing of the call service order in the cockpit, display the completion status information of the call service order in the cockpit.

[0090] During the safety driver's processing of a call service order, the completion status information of the order can be displayed in the cockpit. This processing includes, but is not limited to: safety driver accepting the call service order, safety driver confirming departure, and safety driver confirming arrival. The completion status information includes, but is not limited to: vehicle self-check status, order information, order status, vehicle's own status, and vehicle driving status.

[0091] Step 02 includes:

[0092] When the safety officer in the cockpit accepts the call service order, the remote cockpit displays the order status as "waiting to depart".

[0093] The second presentation module 120 is used to display the order status as "waiting to depart" in the remote cockpit when the safety officer in the cockpit accepts the call service order.

[0094] The processor is used to display the order status as "waiting to depart" in the remote cockpit when the safety officer in the cockpit accepts the call service order.

[0095] Upon receiving a service request, the remote chauffeur service's backend server dispatches the order to the appropriate safety driver. The safety driver's device then displays the order information. Once accepted, the safety driver accesses the order service page, where the order status changes to "awaiting departure." The remote chauffeur service's backend server then sends this "awaiting departure" status message to the user, informing them that their service request has begun processing.

[0096] In this way, after the safety officer accepts the call service order, the corresponding order status is displayed in the cockpit, allowing the safety officer to understand the current order status and begin preparations for the order service based on the waiting departure status.

[0097] Please see Figure 4 After the safety officer in the cockpit accepts the call service order, the interaction methods also include:

[0098] 03: The vehicle system is in a self-check state within the cabin;

[0099] 04: If the vehicle system self-check passes, the remote cockpit will prompt the safety officer that the safety officer can perform a manual inspection and display a confirmation control for the result of the manual inspection.

[0100] 05: In response to the safety officer's operation of the result confirmation control, the remote cockpit displays a confirmation departure control so that the safety officer can confirm the departure of the call service order.

[0101] Steps 03-05 can be implemented by the second presentation module 120. Alternatively, the second presentation module 120 is used to present the vehicle system self-check status within the cockpit; if the vehicle system self-check passes, the remote cockpit provides feedback to the safety officer indicating that manual inspection is possible, and displays a confirmation control for the manual inspection result; in response to the safety officer's operation of the confirmation control, the remote cockpit displays a confirmation departure control so that the safety officer can confirm the dispatch of the call service order.

[0102] The processor is used to display the vehicle system self-check status within the cockpit; if the vehicle system self-check passes, the remote cockpit provides feedback to the safety officer indicating that the safety officer can perform a manual check, and displays a confirmation control for the result of the manual check; in response to the safety officer's operation of the result confirmation control, the remote cockpit displays a confirmation departure control so that the safety officer can confirm the departure of the call service order.

[0103] Once a safety driver accepts a ride request, the remote chauffeur service's backend server will perform a pre-departure vehicle system self-check process on the vehicle corresponding to the request, such as checking whether the vehicle's sensors are functioning properly. The safety driver's cockpit can display the vehicle system self-check status through a display device, showing the current self-check items and their results in real time, allowing the safety driver to clearly understand the current self-check items and results.

[0104] When the vehicle system self-check passes, the display in the cockpit shows the result and simultaneously prompts the safety operator to perform a manual check. This indicates that the safety operator may proceed with the manual check, and a confirmation button for the manual check is displayed on the current screen. The manual check includes, but is not limited to: checking the quality of the remote communication video, assessing the vehicle's surroundings, and verifying that the steering wheel can be manually operated remotely. Once the safety operator's manual check is successful, a confirmation button is displayed in the remote cockpit. The safety operator clicks this confirmation button to confirm the dispatch of the service request.

[0105] In this way, by responding to the safety officer's order acceptance, the system automatically transitions to vehicle system self-check and safety officer manual inspection, improving the processing efficiency of call service orders. Simultaneously, the inspection process status is displayed to the safety officer, allowing them to clearly understand the current vehicle system self-check status.

[0106] After the safety officer in the cockpit accepts the call service order, the interaction methods also include:

[0107] If an anomaly is detected during vehicle system self-check or manual inspection, the remote cockpit will report the anomaly to the safety officer and terminate the call service order.

[0108] The second presentation module 120 is used to remotely alert the safety officer and terminate the call service order when an anomaly is detected during vehicle system self-check or manual inspection.

[0109] The processor is used to remotely alert the safety officer and terminate the call service order when an anomaly is detected during vehicle system self-check or manual inspection.

[0110] When the vehicle system self-checks an abnormality, such as a self-check item failing or the vehicle system self-check stopping, the remote cockpit can report the abnormality to the safety officer and automatically terminate the current call service order.

[0111] If any abnormalities are found during manual inspection, a confirmation control for "Pass" or "Fail" can be displayed in the cockpit. If the safety officer clicks "Fail," the current call service order can be terminated.

[0112] In this way, when an anomaly is detected during inspection, the status can be automatically switched, and the safety officer can confirm and determine whether to proceed with the order service, thereby improving order processing efficiency.

[0113] Please see Figure 5 Step 02 includes:

[0114] 021: After the safety driver confirms the dispatch of the summon service order, if the vehicle's location is in the first zone, the remote cockpit displays the vehicle's autopilot activation control. The first zone is the area where the vehicle's autopilot is available.

[0115] 022: In response to the safety operator's operation of the autonomous driving activation control, the process of the vehicle autonomously driving towards the summoned location in the first area is displayed in the cockpit.

[0116] Steps 021 and 022 can be implemented by the second presentation module 120. Alternatively, the second presentation module 120 is used to display the vehicle's autonomous driving activation control in the remote cockpit when the safety driver confirms the dispatch of the summoning service order and the vehicle's location is in the first area, where the first area is the area where the vehicle's autonomous driving is available; in response to the safety driver's operation of the autonomous driving activation control, the process of the vehicle driving autonomously to the summoning location in the first area is presented in the cockpit.

[0117] The processor is used to display the vehicle's autopilot activation control in the remote cockpit after the safety driver confirms the dispatch of the summon service order, provided that the vehicle's location is within the first zone. The first zone is the area where the vehicle's autopilot is available. In response to the safety driver's operation of the autopilot activation control, the processor displays the process of the vehicle performing autopilot operation towards the summon location within the first zone in the cockpit.

[0118] The ability for users to summon a vehicle to a designated location can be applied to various scenarios, such as a user summoning a vehicle to a current location at the current moment or a user summoning a vehicle to a preset location at a scheduled time.

[0119] For example, if a user finishes shopping and cannot find a parking spot in a parking lot, they can initiate a summoning service order via their mobile phone or other device to summon a vehicle to their current location or a location specified by the user. The vehicle can utilize autonomous driving functions such as memory parking within the parking lot. During the summoning service process, the vehicle can automatically drive to the user's summoned location in the parking lot based on a pre-remembered driving route stored in the memory parking function.

[0120] Once the safety driver confirms the current dispatch service order, the vehicle receives a signal from the remote driving backend server and begins driving. If the vehicle is located in the first zone where autonomous driving is available, the remote cockpit can display the vehicle's autonomous driving activation control. When the vehicle is in the first zone, the remote driving service management platform can monitor the vehicle's arrival in real time. Upon arrival, the cockpit can display a text message or voice announcement stating "Entering the autonomous driving available zone, please stop and activate." The remote cockpit can then display the vehicle's autonomous driving activation control, including resuming or redisplaying the control from a grayed-out state. The safety driver can then activate the autonomous driving system by clicking the control.

[0121] It should be noted that the autonomous driving functions in this application include functions such as unmanned driving on the road, autonomous driving with memory parking, and / or automatic parking, which enable the vehicle to drive automatically without a driver. The specific use of the driving functions can be determined based on actual business needs and limitations.

[0122] In this way, the safety operator can notify the vehicle from inside the cabin that autonomous driving is possible within the first zone, allowing the safety operator to take control of the vehicle and engage autonomous driving, thus reducing the operator's workload. Simultaneously, displaying the vehicle's autonomous driving process towards the designated location within the first zone from inside the cabin allows the safety operator to remotely monitor the process, ensuring a certain level of safety for autonomous driving.

[0123] Please see Figure 5 Step 02 includes:

[0124] 023: After the safety driver confirms the dispatch of the summon service order, if the vehicle is located in the second zone, the remote cockpit will provide the safety driver with a prompt that the vehicle can be manually driven. The second zone is the area where the vehicle's automatic driving is not available.

[0125] 024: After the safety officer remotely starts driving the vehicle manually, the vehicle will be displayed as having entered manual driving mode inside the cabin.

[0126] Steps 023 and 024 can be implemented by the second presentation module 120. Alternatively, the second presentation module 120 is used to, after the safety driver confirms the dispatch of the call service order, and if the vehicle's location is in the second area, provide the safety driver with a prompt that the vehicle can be manually driven. The second area is the area where the vehicle's autonomous driving is unavailable. After the safety driver remotely drives the vehicle manually, the system will display in the cockpit that the vehicle has entered manual driving mode.

[0127] The processor is used to remotely prompt the safety driver that the vehicle can be manually driven after the safety driver confirms the dispatch of the call service order, provided that the vehicle is located in the second zone. The second zone is the area where the vehicle's automatic driving is not available. After the safety driver remotely drives the vehicle manually, the cockpit will display a message indicating that the vehicle has entered manual driving mode.

[0128] During the summoning service, the vehicle can automatically drive to the user's summoned location in the parking lot according to the pre-stored driving route in the memory parking function. However, during this process, there may be transitions between autonomous driving functions, requiring manual operation by a safety driver to connect the autonomous driving capabilities. For example, when crossing floors, the vehicle may use memory parking to reach the end of the memory parking route, then the safety driver may manually drive to the next starting point before reactivating memory parking.

[0129] If the vehicle is located in a second zone where autonomous driving is unavailable, the remote cockpit can notify the safety operator that manual driving is possible. The cockpit can display a message via text or voice stating, "Autonomous driving is temporarily unavailable; please drive manually." The safety operator can then manually take over the vehicle using a driving suite within the remote cockpit, including a simulated steering wheel, simulated brakes, and simulated gear shifting. Simultaneously, the cockpit will display a message indicating that the vehicle has entered manual driving mode. At the same time, the message "Autonomous driving is currently unavailable" will be displayed in the corresponding area, and the autonomous driving controls may be grayed out or not displayed.

[0130] During the safety driver's operation, the remote driving backend server continuously monitors whether the vehicle has reached an area where autonomous driving is available. Upon reaching an available area, the remote driving backend server controls the display device in the remote cockpit to show the autonomous driving activation control and indicates that autonomous driving is available. However, the autonomous driving activation control is initially grayed out and temporarily unavailable. The safety driver must be guided to stop the vehicle before activating autonomous driving. After the safety driver stops the vehicle, the autonomous driving activation control changes from grayed out and becomes highlighted, indicating that the vehicle can then activate autonomous driving.

[0131] Thus, when the vehicle is in the second zone, the safety operator in the remote driving service cabin can remotely and manually drive the vehicle to ensure it can continue moving in areas where autonomous driving is not possible, or, in an emergency, manually take over the vehicle, improving driving safety during the call service. At the same time, clearly distinguishing between autonomous driving and safety operator driving facilitates safer takeover and reduces the need for multiple systems to operate simultaneously.

[0132] Step 02 includes:

[0133] When the vehicle is in a preset scenario, the remote cockpit provides the first alert to the safety operator, prompting the operator to monitor the vehicle's autonomous driving.

[0134] The second presentation module 120 is used to remotely prompt the safety operator when the vehicle is in a preset scenario, so as to prompt the safety operator to supervise the autonomous driving of the vehicle.

[0135] The processor is used to remotely alert the safety driver when the vehicle is in a preset scenario, prompting the safety driver to monitor the vehicle's autonomous driving.

[0136] The preset scenarios can be accident-prone road sections, turning sections, narrow road sections, or road sections with many obstacles that need to be avoided. In order to avoid the driving risks that may occur in the autonomous driving of the vehicle, the remote cockpit can provide the first prompt to the safety driver to warn the safety driver, so that the safety driver can pay attention to possible mistakes and take over the vehicle.

[0137] This allows for early warnings of potential driving risks associated with autonomous driving, improving driving safety during summoning services.

[0138] Step 02 also includes:

[0139] In response to the safety officer's confirmation of the call service order, the remote cockpit displays the order status as "calling in progress".

[0140] The second presentation module 120 is used to respond to the safety officer's confirmation of the call service order, and the remote cockpit displays the order status as "calling".

[0141] The processor is used to respond to the safety officer's confirmation of the call service order, and the remote cockpit displays the order status as "calling".

[0142] In this way, the safety officer can check the order status after departure from the cockpit through the real-time status display, and remotely control the vehicle to drive to the summoned location according to the contents of the summon service order.

[0143] Please see Figure 6 Step 02 also includes:

[0144] 025: When the parking space corresponding to the target summoning location is available for automatic parking, the remote cockpit displays the process of the vehicle automatically parking into the summoning location parking space.

[0145] Step 025 can be implemented by the second presentation module 120. In other words, the second presentation module 120 is used to display the process of the vehicle automatically parking into the parking space when the parking space corresponding to the target summoning location is available for automatic parking in the remote cockpit.

[0146] The processor is used to display the process of the vehicle automatically parking into the parking space corresponding to the target summoning location in the remote cockpit, provided that the parking space is available for automatic parking.

[0147] Automated parking refers to the process where, upon arriving near a designated parking space, the vehicle automatically detects whether it can be entered using the automated parking function. If the space is accessible, the vehicle will activate the automated parking function and park itself. Once successfully parked, the automated driving process is complete. Simultaneously, the remote cockpit can display the entire process of the vehicle automatically parking into the designated parking space.

[0148] This allows safety officers to monitor the safe final parking of vehicles and prevent parking errors.

[0149] The remote cockpit can display the process of the vehicle automatically parking into the summoned parking space, which also includes:

[0150] If an abnormal situation occurs during the automatic parking process, the remote cockpit will display a second prompt message to alert the safety operator to take over the vehicle.

[0151] In response to a safety operator's remote takeover of the vehicle, the remote cockpit displays that the vehicle has entered manual parking driving mode.

[0152] The second presentation module 120 is used to display a second prompt message in the remote cockpit when an abnormal situation occurs during the automatic parking process of the vehicle, so as to prompt the safety operator to take over the vehicle; in response to the safety operator's operation of remotely taking over the vehicle, the remote cockpit displays that the vehicle has entered the manual parking driving state.

[0153] The processor is used to display a second prompt message in the remote cockpit when an abnormal situation occurs during the automatic parking process, so as to prompt the safety operator to take over the vehicle; in response to the safety operator's operation of remotely taking over the vehicle, the remote cockpit displays that the vehicle has entered manual parking driving mode.

[0154] During the automatic parking process into the target charging space, an abnormal situation may occur, such as someone behind the vehicle. In this case, the remote cockpit can display a second prompt message to alert the safety driver to take over the vehicle. If the safety driver intervenes in an emergency (such as by applying the brakes), the remote cockpit can display that the vehicle has entered manual parking mode, and the automatic driving mode has been paused. After confirming the surrounding environment, the safety driver can click the continue button to resume automatic parking into the space.

[0155] Abnormal situations also include the vehicle disengaging from autonomous driving due to malfunction or obstacle avoidance. In this case, since the vehicle's autonomous driving cannot be directly resumed due to an unexpected event, the vehicle will stop, and the remote cockpit can display a second prompt message to alert the safety driver to take over the vehicle. The remote cockpit can also highlight a warning message for the safety driver to take over promptly and inform the safety driver that the vehicle has automatically parked and exited autonomous driving mode.

[0156] In this way, various abnormal situations that occur during automatic parking can be managed, ensuring that the vehicle can be successfully parked in the summoned parking space.

[0157] Please refer to it again. Figure 6 Step 02 also includes:

[0158] 026: If the parking space corresponding to the summoning location is unavailable for automatic parking, in response to the vehicle stopping its automatic driving operation, the remote cockpit displays a third prompt message to prompt the safety driver to remotely take over the vehicle;

[0159] 027: In response to a safety officer's remote takeover of the vehicle, the remote cockpit displays that the vehicle has entered manual parking driving mode.

[0160] Steps 026 and 027 can be implemented by the second presentation module 120. Alternatively, the second presentation module 120 is used to, in response to the vehicle stopping autonomous driving, display a third prompt message in the remote cockpit when the parking space corresponding to the summoned location is unavailable for automatic parking, prompting the safety driver to remotely take over the vehicle; and in response to the safety driver remotely taking over the vehicle, the remote cockpit displays that the vehicle has entered manual parking driving mode.

[0161] When the parking space corresponding to the summoned location is unavailable for automatic parking, the processor, in response to the vehicle stopping its autonomous driving operation, displays a third prompt message in the remote cockpit to prompt the safety driver to remotely take over the vehicle; in response to the safety driver remotely taking over the vehicle, the remote cockpit displays that the vehicle has entered manual parking driving mode.

[0162] When the parking space corresponding to the summoning location is unavailable for automatic parking, the vehicle's autonomous driving function can automatically stop the vehicle. Simultaneously, the remote cockpit can display a third-party notification to prompt the safety driver to remotely take over the vehicle. This third-party notification can be a bright warning indicator, allowing the safety driver to directly take over the vehicle. Once the safety driver has remotely taken over the vehicle, the remote cockpit can display that the vehicle has entered manual parking mode.

[0163] It should be noted that in the summoning service, the summoned parking space can be specifically set up for the service. The summoned parking space can be pre-locked at the start of the service and managed according to corresponding rules, such as using ground locks. Abnormal situations during the automatic parking process may include: firstly, if autonomous driving is unavailable, the safety operator can manually park the vehicle in the space. Secondly, if the parking space is unavailable for other reasons, such as being blocked by an object, the safety operator should contact the property management for resolution. Furthermore, in the summoning service process, the next step is for the user to get into the car. Contacting the property management for resolution would be time-consuming and cumbersome; therefore, the user can be simultaneously notified to retrieve their car from the summoned parking space. The safety operator must ensure the vehicle is parked in the designated space or the user is already inside, and cannot simply stop the vehicle on the roadside to end the service, preventing vehicles from obstructing traffic or creating safety hazards.

[0164] In this way, if automatic parking is unavailable, the system can provide a prompt to the safety operator to take over manually, allowing the vehicle to be parked smoothly in the designated parking space.

[0165] Please see Figure 7 Step 02 also includes:

[0166] 028: Once the vehicle is confirmed to be in the designated parking space, the remote cockpit displays the order status as "waiting to pick up the vehicle".

[0167] Step 028 can be implemented by the second presentation module 120. Alternatively, the second presentation module 120 is used to display the order status as "waiting to pick up the vehicle" in the remote cockpit when it is determined that the vehicle has entered the summoned parking space.

[0168] The processor is used to display the order status as "waiting to pick up the vehicle" in the remote cockpit when it is determined that the vehicle has entered the summoned parking space.

[0169] When the vehicle enters the summoned parking space via GPS, Beidou, or other positioning methods and the vehicle's environment, the remote cockpit can display the order status changing to "waiting to pick up the car." At this time, a text message or voice announcement can be made to indicate "Parking complete, user has been contacted to pick up the car."

[0170] This allows the safety officer to know from inside the cabin that the vehicle has entered the designated parking space and parked successfully, ready for the user to retrieve the car.

[0171] Please see Figure 7 Step 02 also includes:

[0172] 029: When the vehicle is detected to be in parking gear in manual parking mode, the remote cockpit displays a confirmation control.

[0173] 0210: In response to the safety officer's operation on the confirmation arrival control, the remote cockpit displays the order status as "waiting for vehicle pickup".

[0174] Steps 029 and 0210 can be implemented by the second presentation module 120. Alternatively, the second presentation module 120 is used to display a confirmation arrival control in the remote cockpit when the vehicle is detected to be in parking gear in manual parking driving mode; in response to the safety driver's operation on the confirmation arrival control, the remote cockpit displays the order status as waiting to pick up the vehicle.

[0175] The processor is used to display an arrival confirmation control in the remote cockpit when it detects that the vehicle has been engaged in parking mode in manual parking driving mode; in response to the safety driver's operation on the arrival confirmation control, the remote cockpit displays the order status as waiting to pick up the vehicle.

[0176] Because the vehicle's automatic driving function stops during manual parking, it cannot effectively detect whether it has been parked in the target parking space. After the safety operator manually parks the vehicle in the space and puts it in P gear, the "Arrived" button appears. The safety operator manually clicks to confirm that the vehicle has arrived and the parking is completed. The remote cockpit can then display the order status as "Waiting to pick up the vehicle".

[0177] In this way, after manually parking, all passengers can see from inside the cabin that the vehicle has entered the summoned parking space and parked successfully, waiting for the user to pick up the car.

[0178] Please see Figure 8 Step 02 also includes:

[0179] 0211: When the order status is "waiting for vehicle pickup", the remote cockpit displays a confirmation control for the service ending;

[0180] 0212: In response to the safety officer's confirmation that the service has ended, close the call service order inside the cockpit.

[0181] Steps 0211 and 0212 can be implemented by the second presentation module 120. Alternatively, the second presentation module 120 is used to display a confirmation service completion control in the remote cockpit when the order status is in the waiting for vehicle pickup state; and to close the call service order in the cockpit in response to the safety driver's confirmation of service completion.

[0182] The processor is used to display a confirmation control for the end of service in the remote cockpit when the order status is "waiting for vehicle pickup"; and to close the call service order in the cockpit in response to the safety officer's confirmation of the end of service.

[0183] Once the order status enters the "waiting for vehicle pickup" state, the remote cockpit displays "call complete" and a confirmation button for service termination, allowing the safety driver to manually confirm and close the order. If the safety driver continues driving at this point, the system automatically transitions back to the "calling" state, and the safety driver resumes driving.

[0184] Thus, a confirmation control for service termination is displayed, allowing security personnel to control the termination status of the call service by manually confirming whether it has ended.

[0185] Interaction methods also include:

[0186] After waiting for the vehicle to be picked up for a preset time, close the summon service order from inside the cabin.

[0187] The second presentation module 120 is used to close the summoning service order inside the cabin after the waiting period for vehicle retrieval has lasted for a preset time.

[0188] The processor is used to close the summon service order inside the cabin after the waiting period for vehicle retrieval has lasted for a preset time.

[0189] If the safety driver does not close the order for an extended period while waiting for a vehicle, the order will be automatically closed after a preset time, such as one minute, returning the user to the safety driver's homepage and ending the service call. Once the waiting period for vehicle pickup is reached, the safety driver's service can end, and the remote chauffeur service's backend server will begin a countdown to remind the user to get in the car as soon as possible. The user's app will display the countdown and payment status, reminding them to pick up the vehicle promptly.

[0190] Thus, once the order status transitions to the waiting-to-pick-up status, if the safety driver does not activate the service completion confirmation control within the preset time, the summon service order will be automatically closed in the cabin, completing this remote chauffeur service.

[0191] Interaction methods also include:

[0192] When the order status is "waiting for vehicle pickup", in response to the safety driver's remote control of the vehicle to take over manual driving, the remote cockpit displays that the vehicle has entered manual driving mode and the order status is displayed as "calling".

[0193] The second presentation module 120 is used to respond to the safety officer's operation of remotely controlling the vehicle to take over manual driving when the order status is in the waiting to pick up state. The remote cockpit displays that the vehicle has entered the manual driving state and the order status is displayed again as the calling state.

[0194] When the order status is "waiting for vehicle pickup", the processor is used to respond to the safety driver's remote control of the vehicle to take over manual driving. The remote cockpit displays that the vehicle has entered manual driving mode and the order status is displayed again as "calling".

[0195] When the order status is "waiting for vehicle pickup," if the driver needs to continue driving, the safety officer can choose not to click the "confirm arrival" button. Instead, the safety officer can remotely control the vehicle to take over manual driving. The remote cockpit can display that the vehicle has entered manual driving mode and re-show the order status as "calling."

[0196] Please see Figure 9 , Figure 9 This is an example diagram of an order flow. After the safety officer accepts the order, the order status shows "Waiting to be triggered". When the safety officer confirms departure, it shows "Calling". When the automatic parking space is completed or the "Arrived" control is clicked after manually parking the car, the status changes to "Waiting to pick up the car". If the driver needs to continue driving, the safety officer can take over the status flow and return to the "Calling" status.

[0197] In this way, while waiting for the user to pick up the car, the driver can manually take over the driving and put the vehicle back into the summoned state to handle any unexpected situations that may occur while waiting for the user to pick up the car.

[0198] This application also provides a computer-readable storage medium. One or more non-volatile computer-readable storage media storing a computer program implement the methods of any of the above embodiments when the computer program is executed by one or more processors. Those skilled in the art will understand that all or part of the processes in the methods of the above embodiments can be implemented by a computer program instructing related software. The program can be stored in a non-volatile computer-readable storage medium, and when executed, the program can include the processes of the embodiments of the methods described above. The storage medium can be a magnetic disk, optical disk, read-only memory (ROM), etc.

[0199] Thus, this application, in response to a user-initiated summoning service request, presents a summoning service order corresponding to the request within the remote chauffeur service cabin. The summoning service request allows the user to summon a vehicle to a designated location. Simultaneously, in response to the safety operator's processing of the summoning service order within the cabin, the completion status information of the summoning service order is displayed within the cabin. This allows the display of user-initiated summoning service orders and their completion status information within the remote vehicle chauffeur service, enabling the safety operator to process the summoning server order and better complete the summoning service. Furthermore, by displaying the order completion status information, the safety operator can clearly understand the status information of each node during the service process, ensuring that the vehicle can smoothly drive to the user's summoning location and avoiding potential accidents that may occur given the immaturity of current autonomous driving technology. Moreover, by remotely controlling the vehicle through the safety operator, driving safety monitoring can be performed without requiring the user to contact a chauffeur, making the handover smoother, faster, and more efficient, while also eliminating the security risks associated with a chauffeur entering the vehicle.

[0200] In the description of this specification, the terms "one embodiment," "some embodiments," "illustrative embodiment," "example," "specific example," or "some examples," etc., refer to specific features, structures, materials, or characteristics described in connection with the described embodiment or example that are included in at least one embodiment or example of this application. In this specification, the illustrative expressions of the above terms do not necessarily refer to the same embodiment or example. Furthermore, the specific features, structures, materials, or characteristics described can be combined in any suitable manner in one or more embodiments or examples. In addition, those skilled in the art can combine and integrate the different embodiments or examples described in this specification and the features of different embodiments or examples without contradiction. Meanwhile, the terms "first," "second," etc., are intended to distinguish similar or related operations. There is a logical relationship between "first" and "second" in some embodiments, but not necessarily in others. This relationship needs to be determined based on the actual embodiments and should not be judged solely by the literal meaning of the terms.

[0201] Any process or method described in the flowchart or otherwise herein can be understood as representing a module, segment, or portion of code comprising one or more executable instructions for implementing a particular logical function or process, and the scope of the preferred embodiments of this application includes additional implementations in which functions may be performed not in the order shown or discussed, including substantially simultaneously or in reverse order depending on the function involved, as will be understood by those skilled in the art to which embodiments of this application pertain.

[0202] Although embodiments of this application have been shown and described above, it is understood that the above embodiments are exemplary and should not be construed as limiting this application. Those skilled in the art can make changes, modifications, substitutions and variations to the above embodiments within the scope of this application.

Claims

1. An interactive method for remote vehicle chauffeur services, characterized in that, include: In response to a user-initiated summoning service request, a summoning service order corresponding to the summoning service request is displayed in the cabin of the remote chauffeur service. The summoning service request is used to allow the user to summon a vehicle to a specified summoning location. In response to the safety officer's processing of the call service order in the cockpit, the completion status information of the call service order is displayed in the cockpit; The process of responding to the call service order by the safety officer in the cockpit, and presenting the completion status information of the call service order in the cockpit, further includes: After the safety driver confirms the dispatch of the summoning service order, if the area where the vehicle is located belongs to the first area, the remote cockpit displays the vehicle's autopilot activation control, where the first area is the area where the vehicle's autopilot is available. In response to the safety operator's operation of the autonomous driving activation control, the process of the vehicle autonomously driving towards the summoned location within the first area is presented in the cockpit.

2. The interaction method according to claim 1, characterized in that, The process of responding to the call service order by the safety officer in the cockpit, and presenting the completion status information of the call service order in the cockpit, includes: When the safety officer in the cockpit accepts the call service order, the remote cockpit displays the order status as "waiting to depart".

3. The interaction method according to claim 2, characterized in that, After the safety officer in the cockpit accepts the summons service order, the interaction method further includes: The vehicle system is in a self-check state within the cockpit. If the vehicle system passes the self-test, the remote cockpit will send a prompt to the safety officer indicating that the safety officer can perform a manual inspection, and display a confirmation control for the result of the manual inspection. In response to the safety officer's operation of the result confirmation control, the remote cockpit displays a confirmation departure control so that the safety officer confirms departure for the call service order.

4. The interaction method according to claim 3, characterized in that, The interaction method also includes: If an anomaly is detected during the vehicle system's self-check or during the manual check, the remote cockpit will send an anomaly alert to the safety officer and terminate the call service order.

5. The interaction method according to claim 1, characterized in that, The process of responding to the call service order by the safety officer in the cockpit, and presenting the completion status information of the call service order in the cockpit, further includes: After the safety driver confirms the dispatch of the summoning service order, if the area where the vehicle is located belongs to the second area, the remote cockpit will provide feedback to the safety driver that the vehicle can be manually driven. The second area is the area where the vehicle's autonomous driving is not available. After the safety officer remotely drives the vehicle manually, the vehicle will be displayed as being in manual driving mode inside the cabin.

6. The interaction method according to claim 1, characterized in that, The process of responding to the call service order by the safety officer in the cockpit, and presenting the completion status information of the call service order in the cockpit, includes: When the vehicle is in a preset scenario, the remote cockpit provides a first prompt to the safety operator, reminding the safety operator to monitor the vehicle's autonomous driving.

7. The interaction method according to any one of claims 3-5, characterized in that, The process of responding to the call service order by the safety officer in the cockpit, and presenting the completion status information of the call service order in the cockpit, includes: In response to the safety officer's confirmation of the call service order, the remote cockpit displays the order status as "calling in progress".

8. The interaction method according to claim 1, characterized in that, The process of responding to the call service order by the safety officer in the cockpit, and presenting the completion status information of the call service order in the cockpit, further includes: If the parking space at the target summoning location is available for automatic parking, the remote cockpit displays the process of the vehicle automatically parking into the summoning location parking space.

9. The interaction method according to claim 8, characterized in that, The process of the remote cockpit displaying the vehicle automatically parking into the summoned parking space also includes: If an abnormal situation occurs during the automatic parking process of the vehicle, the remote cockpit displays a second prompt message to prompt the safety operator to take over the vehicle; In response to the safety officer's remote takeover of the vehicle, the remote cockpit displays that the vehicle has entered manual parking driving mode.

10. The interaction method according to claim 1, characterized in that, The process of responding to the call service order by the safety officer in the cockpit, and presenting the completion status information of the call service order in the cockpit, further includes: If the parking space corresponding to the summoning location is unavailable for automatic parking, in response to the vehicle ceasing its automatic driving operation, the remote cockpit displays a third prompt message to prompt the safety driver to remotely take over the vehicle. In response to the safety officer's remote takeover of the vehicle, the remote cockpit displays that the vehicle has entered manual parking driving mode.

11. The interaction method according to any one of claims 8-10, characterized in that, The process of responding to the call service order by the safety officer in the cockpit, and presenting the completion status information of the call service order in the cockpit, further includes: Once it is confirmed that the vehicle has entered the parking space at the summoning location, the remote cockpit displays the order status as "waiting to pick up the vehicle".

12. The interaction method according to claim 11, characterized in that, The process of responding to the call service order by the safety officer in the cockpit, and presenting the completion status information of the call service order in the cockpit, further includes: When the remote cockpit detects that the vehicle has been put into parking gear in manual parking mode, it displays an arrival confirmation control. In response to the safety officer's operation on the confirmation arrival control, the remote cockpit displays the order status as "waiting to pick up the vehicle".

13. The interaction method according to claim 11, characterized in that, The process of responding to the call service order by the safety officer in the cockpit, and presenting the completion status information of the call service order in the cockpit, further includes: When the order status is "waiting for vehicle pickup", the remote cockpit displays a confirmation "service ended" control. In response to the safety officer's confirmation that the service has ended, the call service order is closed inside the cockpit.

14. The interaction method according to claim 11, characterized in that, The interaction method also includes: After the waiting period for vehicle retrieval has lasted for a preset time, the summoning service order is closed inside the cabin.

15. The interaction method according to claim 11, characterized in that, The interaction method also includes: When the order status is "waiting for vehicle pickup", in response to the safety driver's remote control of the vehicle to take over manual driving, the remote cockpit displays that the vehicle has entered manual driving mode and the order status is displayed again as "calling".

16. An interactive device for a remote vehicle chauffeur service, characterized in that, include: The first presentation module is used to respond to a user-initiated summoning service request and present a summoning service order corresponding to the summoning service request in the cabin of the remote chauffeur service. The summoning service request is used to allow the user to summon a vehicle to a specified summoning location. The second presentation module is used to respond to the processing of the call service order by the safety officer in the cockpit and present the completion status information of the call service order in the cockpit. The second presentation module is also used to display the vehicle's autopilot activation control in the remote cockpit when the vehicle's location is in the first area after the safety driver confirms the departure of the summoning service order; the first area is the area where the vehicle's autopilot is available. In response to the safety operator's operation of the autonomous driving activation control, the process of the vehicle autonomously driving towards the summoned location within the first area is presented in the cockpit.

17. A terminal device, characterized in that, The terminal device includes a memory and a processor. The memory stores a computer program, which, when executed by the processor, implements the method described in any one of claims 1-15.

18. A non-volatile computer-readable storage medium for a computer program, characterized in that, When the computer program is executed by one or more processors, it implements the method according to any one of claims 1-15.

Images