Method and apparatus for transferring vehicle driving authority

Abstract

To provide a vehicle drive authority transfer method and device capable of being applied to a field of assisted drive and automated drive.SOLUTION: With a method, a state of a system of a vehicle is checked before drive authority of the vehicle is transferred, and the drive authority of the vehicle is transferred only when it is determined that the state of the system of the vehicle is normal, and thereby the state of the system of the vehicle is checked before the drive authority of an intelligent vehicle is transferred. This further helps avoid liability dispute resulting from a traffic accident caused by abnormality in the state of the system of the vehicle after the drive authority of the vehicle is transferred, in particular abnormality in a braking system and / or a steering system that is closely related to operability / maneuverability of the vehicle.SELECTED DRAWING: Figure 2

Description

Technical Field

[0001] Cross-reference to Related Applications This application claims priority to Chinese Patent Application No. 201910625024.9, titled "Vehicle Driving Authority Transfer Method and Device", filed with the China National Intellectual Property Administration on July 11, 2019, which is incorporated herein by reference in its entirety.

[0002] Technical Field This application relates to the field of computer technology and / or mobile communication technology, and in particular, to a vehicle driving authority transfer method and device.

Background Art

[0003] With the continuous development of autonomous driving technology, autonomous driving technology has developed rapidly and is widely used. The level of driving automation is increasing. This greatly reduces the burden on people during driving, gradually liberates people's hands and eyes, enables people to perform activities other than driving activities, and greatly facilitates people's lives.

[0004] Current autonomous driving systems are gradually becoming fully automated, meaning they will complete the entire dynamic driving task. According to the Society of Automotive Engineers (SAE) classification of driving automation levels, there are levels L0 to L5, which are No Automation (L0), Driver Assistance (L1), Partial Automation (L2), Conditional Automation (L3), High Automation (L4), and Full Automation (L5). As the level of driving automation continues to rise, human participation in driving activities decreases. Currently, the number of Level L4 (i.e., high automation) systems entering the market is gradually increasing, including low-speed autonomous driving systems and automated valet parking systems (AVPS). Automated valet parking systems are a typical example.

[0005] An automated valet parking system can provide users with an automated valet parking service. The system can organize multiple parking lots with valet parking capabilities and provide users with information about available parking spaces within the lot. Users may reserve a parking space in advance using a mobile device and drive to the parking lot. Users may leave their vehicles in a designated drop-off area, and the automated valet parking system will automatically guide the vehicle to an available parking space. When a user needs to retrieve their vehicle, they send a retrieval request, and the automated valet parking system will automatically guide the parked vehicle to a designated pickup area. In this case, the user can drive the vehicle again and leave the parking facility. Automated valet parking systems may be used for shopping mall parking lots, airport parking lots, public parking lots, etc. Automated valet parking systems can reduce the time users spend searching for parking spaces, which greatly helps people park.

[0006] In an automated valet parking system, the parking subsystem and the vehicle work together to complete valet parking tasks. Currently, when a user arrives at a designated drop-off area, the parking subsystem needs authorization from the user to transfer driving authority from the user to the automated valet parking system, and primarily to the parking subsystem. When the vehicle arrives at the pickup area, the user needs to regain driving authority; in other words, driving authority needs to be transferred from the parking subsystem to the user. Any accidents that occur after the transfer of driving authority are the responsibility of the party to whom the driving authority was transferred.

[0007] A large number of traffic accidents are caused by abnormal conditions in vehicle systems, particularly malfunctions (failures or failures) in the vehicle's braking and / or steering systems, which are closely related to the vehicle's operability / handling. Therefore, it is extremely important to check the condition of the vehicle's systems, especially the braking and / or steering systems, during the transfer process. [Overview of the project]

[0008] This application provides a method and apparatus for transferring vehicle driving authority to check the status of a vehicle's systems before the driving authority of the vehicle is transferred.

[0009] According to the first aspect, the present application provides a method for transferring vehicle driving authority. This method includes: a communication device acquiring first information. The first information is used to indicate the status of a vehicle's systems, the systems including at least one of a braking system and a steering system. If the status of the vehicle's systems is normal, the communication device initiates the transfer of vehicle driving authority. Based on the above solution, the status of the vehicle's systems is checked before vehicle driving authority is transferred, and vehicle driving authority is transferred only if it is determined that the status of the vehicle's systems is normal, thereby avoiding liability disputes arising from traffic accidents caused by abnormalities in the vehicle's status, particularly abnormalities in the braking system and / or steering system, which are closely related to the vehicle's operability / handling, after vehicle driving authority has been transferred.

[0010] In one possible implementation, the brake system state includes one or more of the following: normal brake system state, abnormal brake system state, loss of longitudinal motion control, and heavy braking. The steering system state includes one or more of the following: normal steering system state, abnormal steering system state, loss of lateral motion control, and heavy steering.

[0011] In one possible implementation, the communication device is a parking subsystem. The parking subsystem sends a first request message to the vehicle. The first request message is used to request a check of the vehicle's system status and includes the vehicle's identification information. The communication device obtaining the first information includes the parking subsystem receiving the first information from the vehicle. In this solution, the parking subsystem verifies the first information and, upon determining that the vehicle's system status is normal, initiates the transfer of authority over the vehicle.

[0012] In one possible implementation, the parking subsystem sending a first request message to a vehicle includes: the parking subsystem sending the first request message to the vehicle by using the vehicle background and / or parking subsystem background. The vehicle background is a background server corresponding to the vehicle, and the parking background is a background server corresponding to the parking subsystem.

[0013] In one possible implementation, the communication device is a parking subsystem. The parking subsystem acquires restricted driving privileges for the vehicle. Restricted driving privileges are driving privileges for a specified duration and / or within a defined area. The parking subsystem sends a second request message to the vehicle. The second request message is used to request that the vehicle perform braking and / or steering operations, and the second request message includes the vehicle's identification information. The communication device acquiring the first information includes: the parking subsystem receiving the first information from the vehicle, and the first information being generated based on the results(s) of the vehicle's braking and / or steering operations; or the parking subsystem generating the first information based on the detected results(s) of the vehicle's braking and / or steering operations. In this solution, the parking subsystem verifies the first information and, when it determines that the vehicle's system state is normal, initiates the transfer of vehicle privileges.

[0014] In one possible implementation, the communication device is the parking subsystem background. The parking subsystem background sends a first request message to the vehicle by using the vehicle background. The vehicle background is the background server corresponding to the vehicle. For the communication device to obtain the first information, this includes the parking subsystem background receiving the first information from the vehicle by using the vehicle background. In this solution, the parking subsystem background verifies the first information and, when it determines that the vehicle's system state is normal, initiates the transfer of authority for the vehicle.

[0015] In one possible implementation, the parking subsystem obtains an operation key. The parking subsystem sends the operation key to the vehicle. The operation key is used to authenticate the parking subsystem's driving authority on the vehicle.

[0016] In one possible implementation, the communication device is the vehicle. The communication device obtaining the first information includes: the vehicle checking the status of its systems and generating the first information. In this solution, the vehicle initiates the transfer of authority when it verifies the first information and determines that the status of the vehicle's systems is normal.

[0017] In one possible implementation, the vehicle receives instruction information from the vehicle background. This instruction information is used to command the vehicle's system status to check, and the vehicle background is a background server corresponding to the vehicle.

[0018] In one possible implementation, the communication device is the vehicle. The communication device obtaining the first information involves the vehicle performing a braking and / or steering operation and generating the first information based on the results (plural or singular) of the braking and / or steering operation. In this solution, the vehicle initiates the transfer of authority when it verifies the first information and determines that the state of the vehicle's systems is normal.

[0019] In one possible implementation, the vehicle receives a third request message from the parking subsystem. This third request message is used to request that the vehicle perform braking and / or steering operations, and it includes vehicle identification information.

[0020] In one possible implementation, the communication device is the vehicle background, which is a background server corresponding to the vehicle. The communication device obtaining the first information includes the vehicle background receiving the first information from the vehicle. In this solution, the vehicle background verifies the first information and initiates the transfer of authority for the vehicle when it determines that the vehicle's system state is normal.

[0021] In one possible implementation, the communication device initiating the transfer of vehicle driving rights includes: the communication device sending a fourth request message to a terminal device, the fourth request message being used to request the transfer of vehicle driving rights, the fourth request message including vehicle identification information; and the communication device receiving a response message from the terminal device, the response message being used to acknowledge the transfer of vehicle driving rights.

[0022] According to a second aspect, the present application provides a vehicle driving authority transfer device. The device may be a communication device or a chip used as a communication device. The device has a function that implements the first aspect or each embodiment of the first aspect. The function may be implemented by hardware or by running corresponding software. The hardware or software includes one or more modules that correspond to the function.

[0023] According to a third aspect, the present application provides a vehicle driving authority transfer device including a processor and memory. The memory is configured to store computer executable instructions, and when the device is in operation, the processor executes the computer executable instructions stored in the memory, thereby the device performs the method according to the first aspect or each embodiment of the first aspect.

[0024] According to a fourth aspect, the present application provides a vehicle driving authority transfer device comprising units or means configured to perform the steps of the first aspect or each embodiment of the first aspect.

[0025] According to the fifth aspect, the present application provides a vehicle driving authority transfer device comprising a processor and an interface circuit. The processor is configured to communicate with another device through the interface circuit and to perform the methods of the first aspect or each embodiment of the first aspect. One or more such processors exist.

[0026] According to the sixth aspect, the present application provides a vehicle driving authority transfer device, which includes a processor configured to connect to a memory and call a program stored in the memory, in order to carry out the methods of the first aspect or each embodiment. The memory may be located inside the device or outside the device. Furthermore, one or more such processors may be present.

[0027] According to a seventh aspect, the present application further provides a computer-readable storage medium. The computer-readable storage medium stores instructions, and when the instructions are executed on a computer, a processor executes the method according to the first aspect or each embodiment of the first aspect.

[0028] According to an eighth aspect, the present application further provides a computer program product including instructions. When the instructions are executed on a computer, the computer executes the method according to the first aspect or each embodiment of the first aspect.

[0029] According to a ninth aspect, the present application further provides a chip system including a processor configured to execute the method according to the first aspect or each embodiment of the first aspect.

Brief Description of Drawings

[0030] [Figure 1] It is a schematic architecture diagram of a possible system according to the present application.

[0031] [Figure 2] It is a schematic flowchart of a vehicle driving authority transfer method according to the present application.

[0032] [Figure 3] It is a schematic flowchart of another vehicle driving authority transfer method according to the present application.

[0033] [Figure 4] It is a schematic flowchart of another vehicle driving authority transfer method according to the present application.

[0034] [Figure 5] It is a schematic flowchart of another vehicle driving authority transfer method according to the present application.

[0035] [Figure 6] It is a schematic flowchart of another vehicle driving authority transfer method according to the present application.

[0036] [Figure 7] This is a schematic flowchart of another method for transferring vehicle driving authority according to this application.

[0037] [Figure 8] This is a schematic diagram of the vehicle driving authority transfer device according to the present invention.

[0038] [Figure 9] This is a schematic diagram of another vehicle driving authority transfer device according to the present invention. [Modes for carrying out the invention]

[0039] To further clarify the purpose, technical solutions, and advantages of this application, the application will be described in detail below with reference to the accompanying drawings. Specific operating methods in the method embodiments may also be applicable to apparatus or system embodiments. In this description, unless otherwise specified, “multiple” means two or more.

[0040] Figure 1 is a schematic architecture diagram of a system to which the present invention can be applied. The system can be any system related to the transfer of driving authority. For example, the system is the automated valet parking system described above. The system includes a parking subsystem, a parking subsystem background, a vehicle, and a vehicle background.

[0041] (1) Parking subsystem

[0042] The parking subsystem may also be referred to as the parking subsystem foreground or parking foreground. The parking subsystem may interact with the vehicle directly to coordinate and direct its actions, or it may interact with the vehicle by using the parking subsystem background.

[0043] The parking subsystem may also interact with the parking subsystem background to provide services such as parking space reservation services.

[0044] Optionally, the parking subsystem may include, or be associated with, a large number of sensor devices (e.g., cameras, radar, and positioning sensors), computing devices, communication devices, etc., to implement functions such as obstacle detection, vehicle positioning, route planning for vehicles, and communication with vehicles, thereby enabling better coordination and control of vehicle operation.

[0045] (2) Parking subsystem background

[0046] The parking subsystem background, also sometimes referred to as the parking background, parking server, parking background server, or parking subsystem server, is used to manage parking facilities (e.g., parking lots). The parking subsystem background is a background server corresponding to the parking subsystem. The server may be a cloud server.

[0047] The parking subsystem and the parking subsystem background may be collectively referred to as the parking system.

[0048] Optionally, the parking subsystem background may interact with the vehicle background to assist in completing communication between the parking subsystem and the vehicle.

[0049] In one implementation, the parking subsystem and the parking subsystem background may be located on different physical devices. Alternatively, in another implementation, the parking subsystem and the parking subsystem background may be integrated into the same physical device.

[0050] (3) Vehicles

[0051] The vehicle may include at least one autonomous driving system.

[0052] In a narrow sense, an autonomous driving system is a system that includes hardware and software that are collectively capable of performing the entire dynamic driving task on a sustained basis, regardless of whether it is limited to a specific operational design domain (ODD).

[0053] In a broad sense, an autonomous driving system is a system that includes hardware and software and is capable of continuously performing part or all of a dynamic driving task.

[0054] A dynamic driving task completes the sensing, decision-making, and execution required to operate a vehicle. In other words, a dynamic driving task includes all the real-time operational and tactical functions required to operate a vehicle in on-road traffic, excluding strategic functions such as trip scheduling and selection of destinations and waypoints.For example, dynamic driving tasks include, but are not limited to, the following subtasks: lateral vehicle motion control via steering (operational), longitudinal vehicle motion control via acceleration and deceleration (operational), monitoring the driving environment via object and event detection, recognition, classification, and response preparation (operational and tactical), object and event response execution (operational and tactical), maneuver planning (tactical), and control of vehicle lighting and signaling devices. gesturing, etc. [improving visibility through lighting, horn honking, signaling, gestures, etc.] (tactical).

[0055] The vehicle and the parking subsystem may interact directly to jointly complete dynamic driving tasks. For example, the parking subsystem may deliver a parking map and location information of available parking spaces to the vehicle, and based on the information about the map and available parking spaces, the vehicle's autonomous driving system may plan a corresponding route, monitor the surrounding environment, and operate the vehicle to arrive at the corresponding parking space. In another example, the parking subsystem may be equipped with a large number of sensor devices (e.g., cameras, radar, and positioning sensors), in which case the parking subsystem may perform functions such as route planning, obstacle detection, and vehicle positioning, and the parking subsystem may exchange real-time operation command information with the vehicle to guide the vehicle to arrive at the parking space.

[0056] Optionally, the vehicle and parking subsystems may interact by using the vehicle background to jointly complete dynamic driving tasks. Further details are not provided here.

[0057] Optionally, the vehicle may further interact with the vehicle background to implement features such as startup, activation, and authentication on the vehicle.

[0058] (4) Vehicle background

[0059] The vehicle background, also sometimes referred to as the vehicle server or vehicle background server, may be used to perform remote startup and initiation on the vehicle and to perform corresponding authentication. The server may be a cloud server.

[0060] Generally, a vehicle background belongs to the original equipment manufacturer (OEM), i.e., the vehicle manufacturer, and the vehicle background is a background server corresponding to the vehicle.

[0061] Optionally, the vehicle background may interact with the parking subsystem background to assist in completing communication between the parking subsystem and the vehicle.

[0062] Optionally, the system shown in Figure 1 may further include a user background and terminal devices.

[0063] (5) Terminal devices

[0064] The terminal device here may be, for example, a mobile phone, computer, tablet computer, in-vehicle display device, or in-vehicle input device. Generally, the services that may be provided to the user by the terminal device's application (APP) may include, but are not limited to, the following services: reserving a parking space, sending a vehicle retrieval request, receiving vehicle status information, etc.

[0065] (6) User background

[0066] The user background, sometimes referred to as the user server or user background server, is primarily used to maintain user information. The server may be a cloud server.

[0067] In one implementation, the parking system (including the parking subsystem and parking subsystem background), vehicles, vehicle background, and user background may all be established and maintained by the vehicle manufacturer. In this case, the parking subsystem background, user background, and vehicle background may be located on different physical devices or on the same physical device.

[0068] In this application, it should be noted that interaction between an external device or system (e.g., a parking subsystem, vehicle background, parking subsystem background, user background, or terminal device) and the vehicle may be interaction between the external device or system and one or more autonomous driving systems of the vehicle, autonomous driving subsystems within the vehicle's autonomous driving systems, or other devices having vehicle control functions. The autonomous driving systems, autonomous driving subsystems, or other devices having vehicle control functions may be part of the vehicle, i.e., used as an in-vehicle device (e.g., configured at delivery or installed later), or they may be third-party standalone devices connected to and communicating with the vehicle wirelessly or wired.

[0069] To address the problems described in the background, this application provides a method for transferring vehicle driving authority. In this method, the status of the vehicle's systems may be checked before the vehicle's driving authority is transferred. This is to avoid liability disputes arising from traffic accidents caused by abnormalities in the vehicle's system status after the vehicle's driving authority has been transferred, particularly abnormalities in the brake and / or steering systems, which are closely related to the vehicle's operability / handling.

[0070] Figure 1 shows the system architecture, and Figure 2 is a schematic flowchart of the vehicle driving authority transfer method according to the present invention.

[0071] It should be noted that this application provides a method for transferring driving rights from the user to the parking subsystem, or from the parking subsystem to the user, using the system architecture shown in Figure 1 as an example. However, this application is not limited to the above scenario. In practical applications, this application may be applied to any scenario in which the driving rights of a vehicle need to be transferred. Correspondingly, the parking subsystem may be replaced with another corresponding functional entity that can complete the technical solution of the embodiment of this application. The method shown in Figure 2 includes the following steps.

[0072] Step 201: The communication device acquires first information, where the first information is used to indicate the status of a vehicle system, and the vehicle system includes at least one of the brake system and the steering system.

[0073] The braking system, also called the deceleration system, is used for controlling the longitudinal motion of the vehicle. The states of the braking system may include one or more of the following: normal braking system, abnormal braking system, loss of longitudinal motion control, and heavy braking.

[0074] The steering system is used for controlling the lateral motion of the vehicle, and the states of the steering system may include one or more of the following: normal steering system state, abnormal steering system state, loss of lateral motion control, and heavy steering.

[0075] It should be noted that the state of a vehicle's system may also be described as the operability of the vehicle's system, the operational status of the vehicle's system, or the operating status of the vehicle's system.

[0076] Optionally, the first piece of information is a status check report or information used to indicate a status check report.

[0077] The first information may indicate the state of the brake system or the state of the steering system. Alternatively, the first information may indicate the state of both the brake system and the steering system. For example, the first information may indicate that the brake system is in a normal state and the steering system is in a normal state.

[0078] Generally, an automated driving system for a vehicle further includes a sensing system, a decision system, and an execution system. The sensing system is configured to sense the environment inside and outside the vehicle, the decision system is configured to make decisions such as route planning, and the execution system is configured to control the movement of the vehicle. Thus, the vehicle system in this application may further include at least one of the sensing system, decision system, and execution system in an automated driving system for a vehicle.

[0079] Optionally, a vehicle's automated driving system may include multiple automated driving subsystems, each subsystem performing a different automated driving function. For example, an automated valet parking system and a low-speed automated driving system perform different functions. Thus, the vehicle system in this application may further include at least one automated driving subsystem within the vehicle's automated driving system.

[0080] Step 202: If the vehicle's systems are functioning correctly, the communication device will begin transferring control of the vehicle.

[0081] The authority to drive a vehicle is sometimes also referred to as vehicle control authority or vehicle operation authority.

[0082] A normal state of a vehicle's systems means that the braking system and the steering system are functioning correctly. Conversely, an abnormal state of a vehicle's systems means that the braking system is abnormal and / or the steering system is abnormal. An abnormal braking system includes either or both loss of longitudinal motion control and / or heavy braking, and an abnormal steering system includes either or both loss of lateral motion control and / or heavy steering.

[0083] Based on the above solution, the status of the vehicle's systems will be checked before the transfer of driving rights, and driving rights will only be transferred if the status of the vehicle's systems is determined to be normal. This will prevent compensation disputes arising from traffic accidents caused by abnormalities in the vehicle's condition after the transfer of driving rights, particularly abnormalities in the brake and / or steering systems, which are closely related to the vehicle's operability / handling.

[0084] Optionally, driving authority may be specific to the entire automated driving system or specific to an automated driving subsystem, which may be configured to perform specific automated driving functions.

[0085] Regarding the above solution, the following provides several specific implementation methods for obtaining the first information by a communication device.

[0086] Case 1: In the embodiment shown in Figure 2, the communication device is either a parking subsystem or a functional module for implementing this embodiment within the parking subsystem. The following description uses an example where the communication device is a parking subsystem, i.e., the parking subsystem initiates the transfer of vehicle driving rights.

[0087] In case 1, the method for obtaining the first information by the parking subsystem may include the following implementation methods 1 and 2.

[0088] Implementation Method 1: The parking subsystem sends a first request message to the vehicle. The first request message is used to request that the vehicle's system status be checked, and the first request message includes the vehicle's identification information. The parking subsystem receives the first information from the vehicle.

[0089] This check is sometimes referred to as detection. Optionally, the check may include diagnosis.

[0090] In this specification, vehicle identification information is used to uniquely identify a vehicle or a system of a vehicle (e.g., an autonomous driving system or a certain autonomous driving subsystem). In some implementations, vehicle identification information may be vehicle identity (ID). In some implementations, vehicle identification information may be a vehicle license plate, a vehicle identification number, or a vehicle engine number.

[0091] For example, the parking subsystem may send a first request message directly to the vehicle, which then checks the status of its systems, generates first information based on the check results, and sends the first information to the parking subsystem.

[0092] In another example, the parking subsystem may send a first request message to the vehicle background, which then sends the first request message to the vehicle, or the vehicle background sends instruction information to the vehicle, which is used to instruct the vehicle to check the status of its systems. The vehicle then checks the status of its systems, generates first information based on the check result, sends the first information to the vehicle background, which then sends the first information to the parking subsystem.

[0093] In another example, the parking subsystem sends a first request message to the parking subsystem background, which then sends the first request message to the vehicle background, which then sends the first request message to the vehicle, or the vehicle background sends instruction information to the vehicle, which is used to instruct the vehicle to check the status of its systems. The vehicle then checks the status of its systems, generates first information based on the check result, which then sends the first information to the vehicle background, which sends the first information to the parking subsystem background, which then sends the first information to the parking subsystem background.

[0094] It should be noted that the check in this implementation method primarily involves the vehicle performing a self-check of the vehicle's system status. Optionally, the vehicle may be stationary during the self-check. Many methods are possible for the vehicle to check the system status. Specific checking methods are not limited in this invention.

[0095] Implementation Method 2: The parking subsystem obtains the vehicle's restricted driving privileges. Restricted driving privileges are driving privileges for a specified duration and / or within a demarcated area. The parking subsystem sends a second request message to the vehicle. The second request message is used to request that braking and / or steering operations be performed on the vehicle, and the second request message includes the vehicle's identification information. The parking subsystem receives first information from the vehicle, which is generated based on the results of the vehicle's braking and / or steering operations, or the parking subsystem generates first information based on the detected results (plural or singular) of the vehicle's braking and / or steering operations.

[0096] The specified duration here may be a fixed period of time, that is, a start time and an end time are specified, or the specified duration may be a fixed duration, that is, a duration is specified without a start time and an end time.

[0097] The restricted driving authority here may also be understood as a prior authority, and is primarily used by the parking subsystem to check the status of the vehicle's systems, particularly the status of the brake and / or steering systems, which are closely related to the vehicle's operability / operability, by using the restricted driving authority.

[0098] In one implementation, the parking subsystem can obtain restricted driving privileges by using the following method:

[0099] The parking subsystem requests restricted driving privileges from the user. After the user agrees, the parking subsystem acquires restricted driving privileges for the vehicle.

[0100] Alternatively, in another implementation, the parking subsystem requests the user to check the status of the vehicle's systems, the user agrees to the vehicle's systems being checked, and provides the parking subsystem with restricted driving privileges to check the vehicle's systems, particularly the brake and / or steering systems, which are closely related to the vehicle's operability / handling.

[0101] Alternatively, in yet another implementation, the parking subsystem background requests the user to check the status of the vehicle's systems, the user agrees that the status of the vehicle's systems be checked, and provides restricted driving privileges for the parking system (including the parking subsystem and parking subsystem background) to check the vehicle's systems, particularly the brake and / or steering systems, which are closely related to the vehicle's operability / handling. Optionally, the parking system grants restricted driving privileges to the parking subsystem to operate the vehicle.

[0102] In this specification, braking operations include deceleration operations and may be used for controlling the vehicle's forward and backward motion, and typically include a brake pedal, etc. Steering operations are used for controlling the vehicle's lateral motion, and typically include a rotary steering wheel, etc.

[0103] It should be noted that in this embodiment, the specific implementation form (plural or singular) of the brake system and / or steering system is not limited. If the vehicle includes devices for controlling the deceleration and / or steering of the vehicle, the vehicle may, instead, not have a conventional brake pedal and / or a rotating steering wheel.

[0104] Optionally, the braking and / or steering operations described herein may be operations(s) performed while the vehicle is in motion.

[0105] In one possible implementation, the parking subsystem requesting a vehicle to perform braking and / or steering operations may also mean that the parking subsystem sends a trajectory to the vehicle and requests the vehicle to move along the trajectory, which may also mean that the parking subsystem requests the vehicle to perform braking and / or steering operations. For example, a given trajectory includes a curve, and the vehicle drives, i.e., performs steering operations, based on that curve. In another example, the trajectory includes at least a start or end point, and the vehicle is requested to stop at the end point, i.e., perform braking operations.

[0106] In this implementation, the vehicle's restricted driving rights may be transferred in advance to a parking subsystem, which may then request the vehicle to perform braking and / or steering operations, and the vehicle may generate first information based on the results(s) of the braking and / or steering operations, or the parking subsystem may generate first information based on the detected results(s) of the vehicle's braking and / or steering operations.

[0107] Case 2: In the embodiment shown in Figure 2, the communication device is the vehicle, or in other words, the vehicle initiates the transfer of driving authority for the vehicle.

[0108] It may be understood that the vehicle may be replaced by another functional module that completes this embodiment. In case 2, the method by which the vehicle obtains the first information may include the following implementation methods 1 and 2.

[0109] Implementation Method 1: The vehicle checks the status of the vehicle's systems and generates the first piece of information.

[0110] The vehicle performs a self-check of the status of its systems. Optionally, the vehicle may remain stationary during the self-check.

[0111] The vehicle can optionally receive instruction information from the vehicle's background. This instruction information is used to command checks on the status of the vehicle's systems.

[0112] Implementation Method 2: The vehicle performs braking and / or steering operations and generates the first information.

[0113] The vehicle performs braking and / or steering operations (see above) and generates first information based on the results(s) of the braking and / or steering operations.

[0114] Optionally, before acquiring full driving rights for the vehicle, the parking subsystem may acquire restricted driving rights for the vehicle (see above description), and then the parking subsystem sends a request message (sometimes referred to hereby as a third request message) to the vehicle. The request message is used to request that the vehicle perform braking and / or steering operations, and the request message includes vehicle identification information. The vehicle then performs braking and / or steering operations and generates first information based on the results(s) of the braking and / or steering operations.

[0115] Case 3: In the embodiment shown in Figure 2, the communication device is the vehicle background, or in other words, the vehicle background initiates the transfer of vehicle driving authority.

[0116] In case 3, the vehicle background obtains the first information in the following way: The vehicle background receives the first information from the vehicle. For example, when the vehicle is in motion, the vehicle performs braking and / or steering operations and generates the first information based on the results (plural or singular) of the braking and / or steering operations. Alternatively, when the vehicle is stationary, the vehicle performs a self-check of the state of its systems and generates the first information. The vehicle then sends the first information to the vehicle background.

[0117] Based on the above implementation methods, the communication device can acquire first information to determine whether the vehicle's system state is normal or abnormal. Optionally, if the vehicle's system state is abnormal, specific abnormalities may be further learned.

[0118] In step 202, in one implementation, the communication device initiates the transfer of driving rights of the vehicle by, for example, sending a request message (which may be referred to in this application as a fourth request message) to a terminal device, which is used to request the transfer of driving rights of the vehicle and which includes vehicle identification information; the communication device then receives a response message from the terminal device, which is used to acknowledge the transfer of driving rights of the vehicle.

[0119] Optionally, the driving authority may be specific to the entire automated driving system or to a particular automated driving subsystem, which is configured to perform a specific automated driving function.

[0120] The communication device sending a request message to a terminal device may involve the request message being forwarded using the user background, and the communication device receiving a response message from a terminal device may involve the response message being forwarded using the user background.

[0121] In one possible implementation, after the communication device sends a request message to the terminal device, the user background or vehicle background may further assign the same operation key to the vehicle and parking subsystem. The operation key is used to perform authentication for driving authority in the parking subsystem. In other words, after the user acknowledges that driving authority can be transferred, the parking subsystem must further send the acquired operation key to the vehicle, which then compares the operation key received from the user background or vehicle background with the operation key received from the parking subsystem. Only after the comparison is successful is the vehicle's driving authority formally transferred from the user to the parking subsystem, thus allowing for a more secure transfer of vehicle driving authority.

[0122] In another possible implementation, after the communication device sends a request message to the terminal device, the user background or vehicle background may further assign an operation key to the parking subsystem. The operation key is used to perform authentication for the driving authority of the parking subsystem. In other words, after the user acknowledges that driving authority can be transferred, the parking subsystem must further send the acquired operation key to the vehicle. One or more operation keys may be pre-configured on the vehicle (for example, configured when the vehicle is delivered from the factory or when the vehicle's software system is upgraded). The vehicle checks whether the operation key received from the parking subsystem is one of the pre-configured keys, and based on the result of the check, decides whether to transfer the vehicle's driving authority from the user to the parking subsystem, thus allowing for a more secure transfer of the vehicle's driving authority.

[0123] In yet another possible implementation, after the communication device sends a request message to the terminal device, the user background or vehicle background may further assign an operation key to the parking subsystem. The operation key is used to perform authentication for the driving authority of the parking subsystem. In other words, after the user acknowledges that driving authority can be transferred, the parking subsystem must further send the obtained key to the vehicle. Key operation rules or key parse rules may be pre-configured on the vehicle (for example, configured when the vehicle is delivered from the factory or when the vehicle's software system is upgraded). The vehicle performs an operation or parse on the operation key received from the parking subsystem and, based on the result of the operation or parse, decides whether to transfer the vehicle's driving authority from the user to the parking subsystem, thus allowing for a more secure transfer of the vehicle's driving authority.

[0124] It should be noted that a parking system may be understood to include both a parking subsystem and a parking subsystem background. The user background or vehicle background can only be concerned with whether driving authority is transferred to the parking system, rather than whether it is transferred to the parking subsystem or the parking subsystem background. Therefore, in the above implementations, the user background or vehicle background may assign an operation key to the parking subsystem background, which then forwards the operation key to the parking subsystem in order to perform authentication for the vehicle's driving authority.

[0125] Referring to Figures 3 through 6, the following provides several specific implementation methods. In the following embodiments, an example is used in which the first information is a status check report. Furthermore, in the following embodiments, an example is used in which vehicle driving rights are transferred from the user to the parking subsystem. In actual use, the process of transferring vehicle driving rights from the parking subsystem to the user is the same as in the following embodiments and will not be described in detail again.

[0126] Figure 3 is a schematic flowchart of another vehicle driving authority transfer method according to the present invention. This method includes the following steps:

[0127] Step 301: The parking subsystem establishes a communication connection to the vehicle.

[0128] After the vehicle moves to the designated drop-off area, identity sensing and identification may be performed between the vehicle and the parking subsystem. The vehicle obtains the parking lot's identification information, and the parking subsystem obtains the vehicle's identification information.

[0129] For an explanation of vehicle identification information, please refer to the description above. Further details will not be provided again here. The parking lot identification information here is used to uniquely identify the parking lot. In some implementations, the parking lot identification information may also be the parking lot ID.

[0130] Next, the vehicle transmits information to the vehicle background. This information includes vehicle identification information and parking lot identification information, and is used to request identity authentication.

[0131] Next, the vehicle background determines the vehicle's identity based on the vehicle's identification information and the parking lot's identity based on the parking lot's identification information. If both are valid, a communication connection between the parking lot subsystem and the vehicle is permitted, and thus the parking lot subsystem establishes a communication connection to the vehicle.

[0132] Optionally, the vehicle background may also send a communication key to the parking subsystem and the vehicle in order to perform reliable communication between the parking subsystem and the vehicle. The communication key sent to the parking subsystem by the vehicle background may be sent using the parking subsystem background.

[0133] This step is optional.

[0134] Step 302: The parking subsystem sends a request message to the vehicle background. Here, the request message contains the vehicle's identification information and is used to request a check of the vehicle's system status. Correspondingly, the vehicle background receives the request message sent by the parking subsystem.

[0135] The parking subsystem may send the request message directly to the vehicle background, or the request message may be forwarded using the parking background.

[0136] Step 303: The vehicle background sends instruction information to the vehicle. Here, the instruction information is used to command the vehicle to check the system status. In response, the vehicle receives the instruction information sent by the vehicle background.

[0137] Alternatively, the vehicle background may send a request message to the vehicle, which is used to ask the vehicle to check the system status.

[0138] Step 304: The vehicle checks the system status.

[0139] Checking the system status here includes, for example, checking brake and / or steering operations, which are closely related to the vehicle's operability / handling.

[0140] It should be noted that the checks described here primarily involve the vehicle performing a self-check of the state of its systems. Optionally, during the self-check, the vehicle is stationary and not in operation. Many methods are possible for a vehicle to check the state of its systems. Specific checking methods are not limited in this invention.

[0141] Step 305: The vehicle sends a status check report to the vehicle background. In response, the vehicle background receives the status check report sent by the vehicle.

[0142] The condition check report is used to indicate the checked status of the brake system and / or the vehicle's steering system.

[0143] Step 306: The vehicle background sends a status check report to the parking subsystem. In response, the parking subsystem receives the status check report sent by the vehicle background.

[0144] The vehicle background may send status check reports directly to the parking subsystem, or the status check reports may be forwarded using the parking subsystem background.

[0145] Step 307: The user transfers driving privileges to the parking subsystem. In response, the parking subsystem acquires driving privileges.

[0146] Based on the status check report, the parking subsystem determines that the vehicle is functioning normally, and that the status of the brake system and / or steering system (plural or singular), which is closely related to the vehicle's operability / handling, is normal (e.g., the deceleration system and steering system are normal), and requests the user to transfer driving authority to the parking subsystem.

[0147] For example, the parking subsystem may send a request message to the terminal device (the request message may be sent directly to the terminal device, or sent to the terminal device using the user background, or sent to the terminal device using the parking subsystem background). The request message is used to request that the vehicle be granted driving rights, and the request message includes the vehicle's identification information. The user then triggers the terminal device's app to acknowledge that the rights will be transferred and to send a response message to the parking subsystem (the response message may be sent directly to the parking subsystem, or the response message may be sent to the parking subsystem using the user background). The response message is used to acknowledge that the vehicle's driving rights will be transferred to the parking subsystem.

[0148] Optionally, driving authority may be specific to the entire automated driving system or specific to a particular automated driving subsystem, which may be configured to perform a specific automated driving function.

[0149] Optionally, after step 307, the user background, parking subsystem, or parking subsystem background may further report the status of the transfer of vehicle driving authority to the vehicle background, in other words, notify the vehicle background that vehicle driving authority has been transferred from the user to the parking subsystem.

[0150] Optionally, prior to step 307, the parking subsystem may acquire additional operating keys. For example, the vehicle background may assign the same operating key separately to the vehicle and the parking subsystem, the parking subsystem sends the operating key to the vehicle, and the vehicle determines whether the parking subsystem has driving authority over the vehicle by comparing the operating key sent by the parking subsystem with the operating key sent by the vehicle background. In another example, the user background or vehicle background may further assign an operating key to the parking subsystem, the parking subsystem sends the operating key to the vehicle, and the vehicle determines whether the parking subsystem has driving authority over the vehicle by checking the operating key received from the parking subsystem against one or more keys pre-configured on the vehicle (for example, configured when the vehicle is delivered from the factory or when the vehicle's software system is upgraded).

[0151] In yet another example, the user background or vehicle background further assigns an operation key to the parking subsystem, the parking subsystem transmits the operation key to the vehicle, and the vehicle performs an operation / parse on the received key based on a pre-configured key operation rule or key parse rule (for example, configured when the vehicle is delivered from the factory or when the vehicle's software system is upgraded), and based on the result of the operation or parse, the parking subsystem determines whether it has driving authority over the vehicle.

[0152] The operation key is used to authenticate the parking subsystem's driving authority over the vehicle. In other words, when the parking subsystem requests a vehicle operation from the vehicle, the vehicle authenticates against the parking subsystem's operation key, and only if authentication is successful does the vehicle operation requested by the parking subsystem become permissible. Alternatively, it should be noted that the operation key may be assigned separately to the vehicle (e.g., sent using the vehicle background) and the parking subsystem (e.g., sent using the parking subsystem background) by the user background.

[0153] It should be noted that the transfer of driving authority may be triggered by the parking subsystem, or by the user, vehicle background, or vehicle. This is not limited to the present invention.

[0154] Based on the above implementation solution, to avoid potential liability disputes, the status of the vehicle's systems, particularly the brake and / or steering systems (single or multiple) which are closely related to the vehicle's operability / handling, will be effectively checked before vehicle driving authority is transferred from the user to the parking subsystem.

[0155] Figure 4 is a schematic flowchart of another vehicle driving authority transfer method according to the present invention. This method includes the following steps:

[0156] Step 401: The parking subsystem establishes a communication connection to the vehicle.

[0157] This step is the same as step 301 in the embodiment shown in Figure 3. Please refer to the description above.

[0158] This step is optional.

[0159] Step 402: The parking subsystem sends a request message to the vehicle. Here, the request message is used to request that the vehicle check the status of its systems. In response, the vehicle receives the request message sent by the parking subsystem.

[0160] It should be noted that, prior to step 402, the parking subsystem must be authorized by the vehicle background. Optionally, after such authorization, the vehicle background may send an authorization key to the parking subsystem. The request message in step 402 carries the authorization key, and therefore the vehicle can determine, based on the authorization key, that the parking subsystem is authorized (either the vehicle checks whether the parking subsystem is authorized, or the vehicle sends the authorization key to the vehicle background, which then checks whether the parking subsystem is authorized).

[0161] Step 403: The vehicle checks the status of the vehicle's systems.

[0162] This step is the same as step 304 in the embodiment shown in Figure 3. Please refer to the description above.

[0163] Step 404: The vehicle sends a status check report to the parking subsystem. In response, the parking subsystem receives the status check report sent by the vehicle.

[0164] The status check report is the same as the status check report in the embodiment shown in Figure 3. Please refer to the description above.

[0165] Step 405: The user transfers driving privileges to the parking subsystem. The parking subsystem then acquires the driving privileges.

[0166] This step is the same as step 307 in the embodiment shown in Figure 3. Please refer to the description above.

[0167] Based on the above implementation solution, to avoid potential liability disputes, the status of the vehicle's systems, particularly the brake and / or steering systems (plural or singular), which are closely related to the vehicle's operability / operability, is effectively checked before the transfer of vehicle driving authority from the user to the parking subsystem. Compared to the implementation solution shown in Figure 3, in this implementation solution, the parking subsystem may be pre-authorized by the vehicle background, thereby allowing the parking subsystem to directly request the vehicle to check the status of its systems, thereby simplifying the signal transmission process, reducing overhead, and improving efficiency.

[0168] Figure 5 is a schematic flowchart of another vehicle driving authority transfer method according to the present invention. This method includes the following steps.

[0169] Step 501: The parking subsystem establishes a communication connection to the vehicle.

[0170] This step is the same as step 301 in the embodiment shown in Figure 3. Please refer to the description above.

[0171] This step is optional.

[0172] Step 502: The user transfers restricted driving privileges to the parking subsystem. In response, the parking subsystem acquires restricted driving privileges.

[0173] In this specification, restricted operating authority may be, for example, operating authority for a specified duration, operating authority in a restricted area, or operating authority for a specified duration and in a restricted area.

[0174] For example, the parking subsystem may send a request message to the terminal device (the request message may be sent directly to the terminal device, or it may be sent to the terminal device using the user background). The request message is used to request the transfer of restricted driving rights for the vehicle and includes vehicle identification information. The user then triggers the terminal device's app to acknowledge that the restricted rights will be transferred and to send a response message to the parking subsystem (the response message may be sent directly to the parking subsystem, or it may be sent to the parking subsystem using the user background). The response message is used to acknowledge that the restricted driving rights for the vehicle will be transferred to the parking subsystem.

[0175] As another example, the parking subsystem may send a request message to the terminal device (the request message may be sent directly to the terminal device, or it may be sent to the terminal device using the user background). The request message is used to request a check of the vehicle's system status and includes the vehicle's identification information. The user then acknowledges on the terminal device's APP that the check should be performed and triggers the terminal device's APP to send a response message to the parking subsystem (the response message may be sent directly to the parking subsystem, or it may be sent to the parking subsystem using the user background). The response message provides the parking subsystem with restricted driving authority for the vehicle.

[0176] Optionally, after step 502, the user background or parking subsystem may further report the status of the transfer of restricted driving rights of the vehicle to the vehicle background, in other words, notify the vehicle background that restricted driving rights of the vehicle have been transferred from the user to the parking subsystem.

[0177] Optionally, prior to step 502, the parking subsystem may acquire an additional first operating key. For example, the vehicle background may separately assign the same first operating key to the vehicle and the parking subsystem, and the parking subsystem sends the first operating key to the vehicle, and the vehicle determines whether the parking subsystem has driving authority over the vehicle by comparing the operating key sent by the parking subsystem with the operating key sent by the vehicle background. In another example, the user background or vehicle background may further assign an additional first operating key to the parking subsystem, and the parking subsystem sends the first operating key to the vehicle, and the vehicle determines whether the parking subsystem has driving authority over the vehicle by checking the first operating key received from the parking subsystem against one or more keys pre-configured on the vehicle (for example, configured when the vehicle is delivered from the factory or configured when the vehicle's software system is upgraded). In yet another example, the user background or vehicle background may further assign a first operation key to the parking subsystem, which transmits the first operation key to the vehicle, and the vehicle performs an operation / parse on the received first operation key based on a pre-configured key operation rule or key parse rule (for example, configured when the vehicle is delivered from the factory or when the vehicle's software system is upgraded), and determines, based on the result of the operation or parse, whether the parking subsystem has driving authority over the vehicle. The first operation key is used to perform authentication for the parking subsystem's restricted driving authority over the vehicle. In other words, when the parking subsystem requests a vehicle operation from the vehicle, the vehicle performs authentication for the parking subsystem's first operation key, and only if authentication is successful does the vehicle allow the restricted vehicle operation requested by the parking subsystem.

[0178] Alternatively, it should be noted that the first operation key may be assigned separately to the vehicle (e.g., transmitted using the vehicle background) and the parking subsystem (e.g., transmitted using the parking subsystem background) by the user background.

[0179] It should be noted that the transfer of restricted driving rights may be triggered by the parking subsystem, or by the user, vehicle background, or vehicle. This is not limited to the present invention.

[0180] Step 503: The parking subsystem sends a request message to the vehicle. Here, the request message is used to ask the vehicle to perform a brake operation and / or steering operation. In response, the vehicle receives the request message sent by the parking subsystem.

[0181] In this specification, braking operation refers to deceleration operation and may be used for controlling the forward and backward movement of the vehicle, and typically includes a brake pedal, etc. Steering operation is used for controlling the lateral movement of the vehicle, and typically includes a rotating steering wheel, etc.

[0182] It should be noted that specific embodiments (plural or singular) of the braking and / or steering systems are not limited to these embodiments. If a vehicle includes devices for controlling the deceleration and / or steering of the vehicle, the vehicle may, instead, not have a conventional brake pedal and / or a rotating steering wheel.

[0183] Optionally, are the braking and / or steering operations described herein operations(s) performed while the vehicle is in motion?

[0184] Step 504: The vehicle performs braking and / or steering operations on the vehicle.

[0185] Step 505: The parking subsystem obtains a vehicle system status check report.

[0186] The status check report is the same as the status check report in the embodiment shown in Figure 3. Please refer to the description above.

[0187] It should be noted that the specific implementation method for obtaining a vehicle system status check report by the parking subsystem is not limited in this invention. For example, the parking subsystem may generate a vehicle system status check report by detecting the trajectory of a moving vehicle using sensor devices placed in the parking lot, or by detecting the results of braking and / or steering operations (plural or singular). In another example, a vehicle may generate a status check report after performing braking and / or steering operations and send that status check report to the parking subsystem.

[0188] Step 506: The user transfers driving rights to the parking subsystem. The parking subsystem then acquires driving rights for the vehicle.

[0189] In this context, driving authority can mean obtaining full driving rights to the vehicle without time or geographical constraints. Based on the status check report, the parking subsystem determines that the vehicle's system status is normal and requests the user to transfer driving authority to the parking subsystem.

[0190] For example, the parking subsystem may send a request message to the terminal device (the request message may be sent directly to the terminal device, or it may be sent to the terminal device using the user background). The request message is used to request that the user acquire driving rights for the vehicle and includes the vehicle's identification information. The user then triggers the terminal device's app to acknowledge that the rights will be transferred and send a response message to the parking subsystem (the response message may be sent directly to the parking subsystem, or it may be sent to the parking subsystem using the user background). The response message is used to acknowledge that driving rights for the vehicle will be transferred to the parking subsystem.

[0191] Optionally, after step 506, the user background, parking subsystem, or parking subsystem background may further report the status of the transfer of vehicle driving rights to the vehicle background, in other words, notify the vehicle background that vehicle driving rights have been transferred from the user to the parking subsystem.

[0192] Optionally, prior to step 506, the parking subsystem may acquire a second operating key. For example, the vehicle background may assign the same second operating key separately to the vehicle and the parking subsystem, and the parking subsystem sends the second operating key to the vehicle, and the vehicle determines whether the parking subsystem has driving authority over the vehicle by comparing the operating key sent by the parking subsystem with the operating key sent by the vehicle background. In another example, the user background or vehicle background may further assign a second operating key to the parking subsystem, and the parking subsystem sends the second operating key to the vehicle, and the vehicle determines whether the parking subsystem has driving authority over the vehicle by checking the second operating key received from the parking subsystem with one or more keys pre-configured on the vehicle (for example, configured when the vehicle is delivered from the factory or configured when the vehicle's software system is upgraded). In yet another example, the user background or vehicle background may further assign a second operating key to the parking subsystem, which transmits the second operating key to the vehicle, and the vehicle performs an operation / parse on the received second operating key based on a pre-configured key operation rule or key parse rule (for example, configured when the vehicle is delivered from the factory or when the vehicle's software system is upgraded), and based on the result of the operation or parse, the parking subsystem determines whether it has driving authority over the vehicle.

[0193] The second operation key is used to authenticate the parking subsystem's driving authority over the vehicle. In other words, when the parking subsystem requests vehicle operation from the vehicle, the vehicle authenticates against the parking subsystem's second operation key, and only if authentication is successful does the vehicle operation requested by the parking subsystem become permissible. Alternatively, it should be noted that the second operation key may be assigned separately to the vehicle (e.g., sent using the vehicle background) and the parking subsystem (e.g., sent using the parking subsystem background) by the user background. The second operation key here may be the same as or different from the first operation key.

[0194] It should be noted that a parking system may be understood to include both a parking subsystem and a parking subsystem background. The user background or vehicle background can only be concerned with whether driving authority is transferred to the parking system, rather than whether it is transferred to the parking subsystem or the parking subsystem background. Therefore, in the above implementations, the user background or vehicle background may assign an operation key to the parking subsystem background, which then forwards the operation key to the parking subsystem in order to perform authentication for the vehicle's driving authority.

[0195] It should be noted that the transfer of driving authority may be triggered by the parking subsystem, or by the user, vehicle background, or vehicle. This is not limited to the present invention.

[0196] Based on the above implementation solution, to avoid potential liability disputes caused by abnormal vehicle conditions, the status of the vehicle's systems, particularly the brake and / or steering systems (plural or singular), which are closely related to the vehicle's operability / operability, is effectively checked before driving authority is transferred from the user to the parking subsystem. Compared to the implementation methods shown in Figures 3 and 4, in this solution, the parking subsystem first acquires restricted driving authority, and thus the parking subsystem can directly control the vehicle, perform braking operations, and then obtain a vehicle system status check report. If the vehicle's system status is determined to be normal, the parking subsystem acquires final driving authority.

[0197] Figure 6 is a schematic flowchart of another vehicle driving authority transfer method according to the present invention. This method includes the following steps.

[0198] Step 601: The parking subsystem establishes a communication connection to the vehicle.

[0199] This step is the same as step 301 in the embodiment shown in Figure 3. Please refer to the description above.

[0200] This step is optional.

[0201] Step 2: The user transfers the restricted driving rights to the parking subsystem. In response, the parking subsystem acquires the driving rights for the vehicle.

[0202] This step is the same as step 307 in the embodiment shown in Figure 3. Please refer to the description above.

[0203] Steps 603 to 605 are the same as steps 503 to 505 in the embodiment shown in Figure 5. Please refer to the description above.

[0204] Step 606: The parking subsystem sends first instruction information to the vehicle. In response, the vehicle receives the first instruction information transmitted by the parking subsystem.

[0205] Based on the status check report, if the parking subsystem determines that the vehicle is functioning normally, it sends a first instruction to the vehicle indicating that the vehicle is functioning normally.

[0206] If the status check report determines that the vehicle's system status is abnormal, the parking subsystem may send a second instruction to the vehicle indicating that the vehicle's system status is abnormal or that the vehicle's driving rights should be relinquished. Alternatively, if the status check report determines that the vehicle's system status is abnormal, the parking subsystem may not send any information to the vehicle. When the vehicle receives the second instruction, or if it does not receive the information, the vehicle or the parking subsystem is triggered to request the terminal device to reclaim the vehicle's driving rights, i.e., to request the user to reclaim the vehicle's driving rights.

[0207] Based on the above implementation solution, to avoid potential liability disputes caused by abnormal vehicle conditions, the status of the vehicle's systems, particularly the brake and / or steering systems (plural or singular), which are closely related to the vehicle's operability / operability, is effectively checked before driving rights are transferred from the user to the parking subsystem. Compared to the implementation methods shown in Figures 3 and 4, in this solution, the parking subsystem first acquires driving rights, and thus the parking subsystem can directly control the vehicle, perform braking operations, and then obtain a vehicle system status check report. If the vehicle's system status is determined to be abnormal, the parking subsystem either sends a second instruction or does not send any information to the vehicle, triggering the user to regain driving rights.

[0208] Figure 7 is a schematic flowchart of another vehicle driving authority transfer method according to the present invention. This method includes the following steps:

[0209] Step 701: The parking subsystem establishes a communication connection to the vehicle.

[0210] This step is optional.

[0211] This step is the same as step 301 in the embodiment shown in Figure 3. Please refer to the description above.

[0212] Optionally, the parking subsystem may also send vehicle identification information to the parking subsystem background.

[0213] Step 702: The parking subsystem background sends a request message to the vehicle background. Here, the request message contains the vehicle's identification information and is used to request a check of the vehicle's system status. Correspondingly, the vehicle background receives the request message sent by the parking subsystem background.

[0214] Step 703: The vehicle background sends instruction information to the vehicle. Here, the instruction information is used to command the vehicle to check the system status. In response, the vehicle receives the instruction information sent by the vehicle background.

[0215] Alternatively, the vehicle background may send a request message to the vehicle, which is used to ask the vehicle to check the system status.

[0216] Step 704: The vehicle checks the system status.

[0217] Checking the system status here includes, for example, checking brake and / or steering operations, which are closely related to the vehicle's operability / handling.

[0218] It should be noted that the checks described here primarily involve the vehicle performing a self-check of the state of its systems. Optionally, during the self-check, the vehicle is stationary, not in operation. Many methods are possible for a vehicle to check the state of its systems. Specific checking methods are not limited in this invention.

[0219] Step 705: The vehicle sends a status check report to the vehicle background. In response, the vehicle background receives the status check report sent by the vehicle.

[0220] The condition check report is used to indicate the checked status of the brake system and / or the vehicle's steering system.

[0221] Step 706: The vehicle background sends a status check report to the parking subsystem background. The parking subsystem receives the status check report sent by the vehicle background. The parking subsystem background receives the status check report sent by the vehicle background.

[0222] Step 707: The user transfers driving privileges to the parking system. The parking system then acquires driving privileges.

[0223] Based on the check report, the parking subsystem background determines that the vehicle is functioning normally, and in particular, that the brake and / or steering systems, which are closely related to the vehicle's operability / handling, are functioning normally (e.g., the deceleration and steering systems are functioning normally), and requests that driving authority be transferred from the user to the parking system.

[0224] For example, the parking subsystem background may send a request message to the terminal device (the request message may be sent directly to the terminal device, or it may be sent to the terminal device using the user background). The request message is used to request the parking system to acquire driving rights for the vehicle, and the request message includes the vehicle's identification information. The user then triggers the terminal device's app to acknowledge that the rights will be transferred and send a response message to the parking subsystem background (the response message may be sent directly to the parking subsystem background, or it may be sent to the parking subsystem background using the user background). The response message is used to acknowledge that driving rights for the vehicle will be transferred to the parking system.

[0225] Optionally, the parking system grants driving authority to the parking subsystem, allowing the parking subsystem to operate the vehicle.

[0226] Optionally, the driving authority may be specific to the entire automated driving system or to a particular automated driving subsystem, which is configured to perform a specific automated driving function.

[0227] It can be understood that a parking system includes both a parking subsystem and a parking subsystem background. A user may only be interested in whether driving authority is transferred to the parking system, rather than whether it is transferred to the parking subsystem or the parking subsystem background. It is also appropriate for the user to transfer driving authority to the parking system.

[0228] Based on the above implementation solution, to avoid potential liability disputes, the status of the vehicle's systems, particularly the brake and / or steering systems (single or multiple) which are closely related to the vehicle's operability / handling, will be checked before vehicle driving authority is transferred from the user to the parking subsystem.

[0229] The solutions provided herein are described above primarily in terms of interaction between network elements. To implement the above functions, it can be understood that each network element includes a corresponding hardware structure and / or software module for implementing each function. Those skilled in the art will readily understand, in combination with the examples described in the embodiments disclosed herein, that units and algorithmic steps can be implemented in hardware or in combination of hardware and computer software. Whether a function is performed by hardware or by hardware driven by computer software depends on the specific application and design constraints of the technical solution. Those skilled in the art may use various methods to implement the described functions for each specific application, but such implementations should not be considered to exceed the scope of the invention.

[0230] Figure 8 is a possible exemplary block diagram of a vehicle driving authority transfer device according to the present invention. The device 800 may exist in software or hardware form. The device 800 may include a processing unit 802 and a communication unit 801. In one implementation, the communication unit 801 may include a receiving unit and a transmitting unit. The processing unit 802 is configured to control and manage the operation of the device 800. The communication unit 801 is configured to support the device 800 when communicating with other network entities.

[0231] The processing unit 802 may be a processor or controller such as a general-purpose central processing unit (CPU), a general-purpose processor, a digital signal processing (DSP), an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA), or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. The processor may implement or run various exemplary logic blocks, modules, and circuits described with reference to what is disclosed herein. The processor may be a combination of processors that implement computing functions, for example, a combination of one or more microprocessors, or a combination of a DSP and a microprocessor. The communication unit 801 is an interface circuit of the device and is configured to receive signals from other devices. For example, if the device is implemented in the form of a chip, the communication unit 801 is an interface circuit of that chip for receiving signals from other chips or devices, or an interface circuit of that chip for transmitting signals to other chips or devices.

[0232] The device 800 may be a communication device in any one of the embodiments described above, or it may be a chip used in such a communication device. For example, if the device 800 is a communication device, the processing unit 802 may be a processor, and the communication unit 801 may be a transceiver. Optionally, the transceiver may include a radio frequency circuit. For example, if the device 800 is a chip used in a communication device, the processing unit 802 may be a processor, and the communication unit 801 may be an input / output interface, pins, circuitry, etc. The processing unit 802 can execute computer executable instructions stored in a memory unit. Optionally, the memory unit is a memory unit on the chip, such as a register or cache. Alternatively, the memory unit may be a memory unit, such as read-only memory (ROM), another type of static memory capable of storing static information and instructions, or random access memory (RAM) located within the communication device and outside the chip.

[0233] In one embodiment, a communication unit 801 is configured to acquire first information, which is used to indicate the status of a vehicle's systems, the systems including at least one of a braking system and a steering system; and a processing unit 802 is configured to initiate the transfer of driving authority of the vehicle when the status of the vehicle's systems is normal.

[0234] In one possible implementation, the state of the brake system includes one or more of the following: normal state of the brake system, abnormal state of the brake system, loss of longitudinal motion control, and heavy braking; and the state of the steering system includes one or more of the following: normal state of the steering system, abnormal state of the steering system, loss of lateral motion control, and heavy steering.

[0235] In one possible implementation, device 800 is a parking subsystem; communication unit 801 is configured to perform the steps of: sending a first request message to a vehicle, the first request message being used to request that the vehicle check the status of its systems, and the first request message including vehicle identification information; and receiving the first information from the vehicle.

[0236] In one possible implementation, the communication unit 801 is configured to send a first request message to the vehicle by specifically using a vehicle background and / or a parking subsystem background. The vehicle background is a background server corresponding to the vehicle, and the parking background is a background server corresponding to the parking subsystem.

[0237] In one possible implementation, device 800 is a parking subsystem; communication unit 801 is configured to perform: a step of acquiring restricted driving rights for a vehicle, where restricted driving rights are driving rights in an area defined by a specified duration and / or boundaries; a step of sending a second request message to the vehicle, where the second request message is used to request that the vehicle perform braking and / or steering operations, and the second request message includes vehicle identification information; and a step of receiving first information from the vehicle, where the first information is generated based on the results(s) of the vehicle's braking and / or steering operations, or generates the first information based on the detected results(s) of the vehicle's braking and / or steering operations.

[0238] In one possible implementation, device 800 is a parking subsystem background; and communication unit 801 is configured to perform the steps of: sending a first request message to a vehicle by using a vehicle background, wherein the vehicle background is a background server corresponding to the vehicle; and receiving first information from a vehicle by using the vehicle background.

[0239] In one possible implementation, the device 800 is further configured to acquire an operation key and transmit the operation key to the vehicle. The operation key is used to perform authentication for the vehicle's driving authority over the parking subsystem.

[0240] In one possible implementation, device 800 is a vehicle; and communication unit 801 is specifically configured to check the status of the vehicle's systems and generate first information.

[0241] In one possible implementation, the communication unit 801 is further configured to receive instruction information from the vehicle background. This instruction information is used to command the vehicle's system status to be checked, and the vehicle background is a background server corresponding to the vehicle.

[0242] In one possible implementation, the device 800 is a vehicle; and the processing unit 802 is further configured to: perform braking and / or steering operations, and generate first information based on the results(s) of the braking and / or steering operations.

[0243] In one possible implementation, the communication unit 801 is further configured to receive a third request message from the parking subsystem. The third request message is used to request that the vehicle perform braking and / or steering operations, and the third request message includes vehicle identification information.

[0244] In one possible implementation, device 800 is a vehicle background, which is a background server corresponding to the vehicle; and communication unit 801 is specifically configured to receive first information from the vehicle.

[0245] In one possible implementation, the processing unit 802 specifically: instructs the communication unit 801 to send a fourth request message to a terminal device, the fourth request message being used to request the transfer of driving rights for the vehicle, the fourth request message including vehicle identification information; and instructs the communication unit 801 to receive a response message from the terminal device, the response message being used to acknowledge the transfer of driving rights for the vehicle.

[0246] For specific implementation processes of device 800 and corresponding beneficial effects when device 800 is used for the above-described method of transferring vehicle driving authority, it can be understood that the relevant descriptions in the above-described embodiment of the method can be referenced. Further details will not be explained again here.

[0247] Figure 9 is a schematic diagram of a vehicle driving authority transfer device according to the present invention. This device may also be a communication device in the embodiments described above. Device 900 includes a processor 902, a communication interface 903, and a memory 901. Optionally, device 900 may further include a communication line 904. The communication interface 903, the processor 902, and the memory 901 may be connected to each other by using the communication line 904. The communication line 904 may be a peripheral component interconnect (PCI) bus, an extended industry standard architecture (EISA) bus, etc. The communication line 904 may be classified as an address bus, a data bus, a control bus, etc. For simplicity of representation, only one thick line is used to represent the communication line in Figure 9, but this does not mean that there is only one bus or only one type of bus.

[0248] The processor 902 may be a CPU, a microprocessor, an ASIC, or one or more integrated circuits configured to control program execution in the solution of the present invention.

[0249] The communication interface 903 is any device, such as a transceiver, and is configured to communicate with other devices or communication networks, such as Ethernet, a radio access network (RAN), a wireless local area network (WLAN), or a wired access network.

[0250] The memory 901 may be a ROM or other type of static storage device capable of storing static information and instructions, or a RAM or other type of dynamic storage device capable of storing information and instructions, or it may be, but is not limited to, an electrically erasable programmable read-only memory (EEPROM), a compact disc read-only memory (CD-ROM), or other compact disc or optical disc storage (including compressed optical discs, laser discs, optical discs, digital multipurpose discs, Blu-ray optical discs, etc.), a magnetic disk storage medium or other magnetic storage device, or any other medium capable of carrying or storing program code expected in the form of instructions or data structures and accessible by a computer. The memory may exist independently and be connected to the processor by using a communication line 904. Alternatively, the memory may be integrated with the processor.

[0251] Memory 901 is configured to store computer-executable instructions for executing the solution of the present invention, and the execution of said computer-executable instructions is controlled by processor 902. Processor 902 is configured to execute the computer-executable instructions stored in memory 901 and implements the vehicle driving authority transfer method provided in the above embodiments of the present invention.

[0252] Optionally, the computer executable instructions in this embodiment of the present application may also be referred to as application program code. This is not particularly limited to this embodiment of the present application.

[0253] Those skilled in the art will understand that the various numbers in this application, such as the first and second, are for the sake of distinction only for the sake of simplicity of explanation and are not intended to limit the scope of the embodiments of this application or to indicate a hierarchy. The term "and / or" describes a relationship between related objects and indicates that three relationships may exist. For example, A and / or B may mean three cases: A only exists, both A and B exist, and B only exists. The symbol " / " generally indicates an "or" relationship between related objects. "At least one" means one or more. "At least two" means two or more. "At least one," "any one," or similar expressions mean any combination of these items, including any combination of one or more of the items. For example, "at least one of a, b, and c" could mean a, b, a and b, a and c, b and c, or a and b and c, where a, b, and c may be singular or plural. "Multiple" means two or more, and so do other quantifiers. Furthermore, the singular elements "a," "an," and "the," unless specified in the context, do not mean that there is "one or only" such element, but rather that there is "one or more" such elements. For example, "a device" means one or more such devices.

[0254] All or part of the embodiments described above may be implemented using software, hardware, firmware, or any combination thereof. When software is used to implement these embodiments, all or part of the embodiments may be implemented in the form of a computer program product. A computer program product includes one or more computer instructions. When computer program instructions are loaded on a computer and executed, all or part of the procedures or functions according to the embodiments of the Application are generated. The computer may be a general-purpose computer, a dedicated computer, a computer network, or other programmable device. Computer instructions may be stored on a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, computer instructions may be transmitted from a website, computer, server, or data center to another website, computer, server, or data center by wired (e.g., coaxial cable, fiber optic cable, or digital subscriber line (DSL)) or wireless (e.g., infrared, radio, or microwave). The computer-readable storage medium may be any available medium accessible by a computer, or a data storage device such as a server or data center that integrates one or more available media. Usable media may include magnetic media (e.g., floppy disks, hard disks, or magnetic tapes), optical media (e.g., DVDs), and semiconductor media (e.g., solid-state disks (SSDs)).

[0255] Various exemplary logic units and circuits described in embodiments of this application can be implemented or operated by using designs of general-purpose processors, digital signal processors, application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic, discrete hardware components, or any combination thereof. The general-purpose processor may be a microprocessor. Optionally, the general-purpose processor may be any conventional processor, controller, microcontroller, or state machine. Alternatively, the processor may be implemented by a computing device, such as a digital signal processor and microprocessor, multiple microprocessors, one or more microprocessors combined with a digital signal processor core, or any other combination of similar configurations.

[0256] Steps of the methods or algorithms described in embodiments of this application may be directly incorporated into hardware, software units executed by a processor, or a combination thereof. The software units may be stored in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disks, removable magnetic disks, CD-ROMs, or any other form of storage medium in the art. For example, the storage medium may be connected to a processor so that the processor can read information from and write information to the storage medium. Optionally, the storage medium may be integrated into the processor. The processor and storage medium may be located within an ASIC.

[0257] These computer program instructions may also be loaded into a computer or other programmable data processing device, thereby executing a series of operations and steps on the computer or other programmable device, thereby generating computer-implemented processing. Thus, the instructions executed on the computer or other programmable device provide steps for implementing a particular function in one or more processes in a flowchart and / or one or more blocks in a block diagram.

[0258] While this application is described with reference to specific features and embodiments thereof, various modifications and combinations can be made to them without departing from the spirit and scope of this application. Correspondingly, this specification and the accompanying drawings are merely illustrative descriptions of this application as defined by the accompanying claims and should be considered as any or all of the modifications, variations, combinations or equivalents that cover the scope of this application. Clearly, a person skilled in the art can make various modifications and variations to this application without departing from the scope of this application. This application is intended to cover these modifications and variations to the extent that they fall within the scope of protection defined by the following claims and their equivalent art.

Claims

1. A method for transferring vehicle driving authority: A step of acquiring first information by a communication device, wherein the first information is used to indicate the state of a vehicle's system, and the system of the vehicle includes at least one of a brake system or a steering system; The step includes, if the state of the vehicle's system is abnormal, the communication device requests the user's terminal device to reclaim the vehicle's driving rights from the parking subsystem, The communication device is the parking subsystem or the vehicle. method.

2. The state of the aforementioned brake system is: This includes one or more of the following: a normal state of the brake system, an abnormal state of the brake system, loss of longitudinal motion control, and heavy braking. The status of the aforementioned steering system is: This includes one or more of the following: a normal state of the steering system, an abnormal state of the steering system, loss of lateral motion control, and heavy steering. The method according to claim 1.

3. The communication device requests the user's terminal device to reclaim the driving rights of the vehicle: The communication device includes transmitting a second instruction information, the second instruction information indicating that the state of the vehicle's system is abnormal, or that the driving authority of the vehicle should be returned. The method according to claim 1 or 2.

4. The aforementioned communication device is a parking subsystem, and the method further: The parking subsystem includes the step of sending a first request message to the vehicle, the first request message being used to request that the vehicle check the status of the system, and the first request message including the vehicle's identification information. The step of acquiring the first information by the communication device is: The parking subsystem includes receiving the first information from the vehicle, The method according to any one of claims 1 to 3.

5. The parking subsystem sends a first request message to the vehicle in the aforementioned step: The parking subsystem includes sending the first request message to the vehicle via the vehicle background and / or the parking subsystem background, wherein the vehicle background is a background server corresponding to the vehicle, and the parking subsystem background is a background server corresponding to the parking subsystem. The method according to claim 4.

6. The parking subsystem can receive the first information from the vehicle: The parking subsystem includes receiving the first information from the vehicle via a vehicle background and / or a parking subsystem background, wherein the vehicle background is a background server corresponding to the vehicle, and the parking subsystem background is a background server corresponding to the parking subsystem. The method according to claim 4 or 5.

7. The aforementioned communication device is a parking subsystem, and the method further: The parking subsystem acquires restricted driving rights for the vehicle, the restricted driving rights refer to driving rights for a specified duration and / or in a specified area; The parking subsystem transmits a second request message to the vehicle, the second request message being used to request that the vehicle perform a brake operation and / or steering operation, and the second request message includes identification information of the vehicle, The aforementioned step of acquiring first information by a communication device is: A step of receiving the first information from the vehicle by the parking subsystem, wherein the first information is generated based on the results (plural or singular) of the vehicle's brake operation and / or steering operation; or a step of generating the first information by the parking subsystem based on the detected results (plural or singular) of the vehicle's brake operation and / or steering operation. The method according to any one of claims 1 to 3.

8. The method further: The parking subsystem includes a step of obtaining a first operating key, the first operating key being used to perform authentication for the restricted driving rights of the vehicle. The method according to claim 7.

9. A vehicle driving authority transfer device: A communication unit configured to acquire first information, the first information being used to indicate the status of a vehicle's system, the system of the vehicle including at least one of a brake system or a steering system; The system has a processing unit configured to request the user's terminal device to reclaim driving rights for the vehicle from the parking subsystem if the state of the vehicle's system is abnormal. The vehicle driving authority transfer device is the parking subsystem or the vehicle. Device.

10. The state of the aforementioned brake system is: This includes one or more of the following: a normal state of the brake system, an abnormal state of the brake system, loss of longitudinal motion control, and heavy braking. The status of the aforementioned steering system is: This includes one or more of the following: a normal state of the steering system, an abnormal state of the steering system, loss of lateral motion control, and heavy steering. The apparatus according to claim 9.

11. The communication unit is configured to transmit a second instruction information, the second instruction information indicating that the state of the vehicle's system is abnormal, or that the driving authority of the vehicle should be returned. The apparatus according to claim 9 or 10.

12. The device in question is a parking subsystem: The communication unit is configured to perform the steps of: sending a first request message to the vehicle, the first request message being used to request that the vehicle check the status of the system, and the first request message including identification information of the vehicle; and receiving the first information from the vehicle. The apparatus according to any one of claims 9 to 11.

13. The communication unit is configured to send the first request message to the vehicle via a vehicle background and / or a parking subsystem background, wherein the vehicle background is a background server corresponding to the vehicle, and the parking subsystem background is a background server corresponding to the parking subsystem. The apparatus according to claim 12.

14. The communication unit is configured to receive the first information from the vehicle by a vehicle background and / or a parking subsystem background, wherein the vehicle background is a background server corresponding to the vehicle, and the parking subsystem background is a background server corresponding to the parking subsystem. The apparatus according to claim 12 or 13.

15. The device is a parking subsystem, and the communication unit further: A step of acquiring restricted driving rights for the vehicle, wherein the restricted driving rights refer to driving rights for a specified duration and / or in a specified area; A step of sending a second request message to the vehicle, the second request message being used to request that the vehicle perform a brake operation and / or steering operation, and the second request message including identification information of the vehicle; The system is configured to perform the steps of: receiving the first information from the vehicle, wherein the first information is generated based on the results (plural or singular) of the vehicle's brake operation and / or steering operation; or generating the first information based on the detected results (plural or singular) of the vehicle's brake operation and / or steering operation. The apparatus according to any one of claims 9 to 11.

16. The device according to claim 15, wherein the device is configured to acquire a first operating key, the first operating key being used to perform authentication for restricted driving privileges of the vehicle.

17. A vehicle driving authority transfer device having a processor and memory, wherein the processor calls a program stored in the memory so that the vehicle driving authority transfer device performs the method according to any one of claims 1 to 8.

18. A vehicle driving authority transfer device having a processor connected to a memory and configured to call a program stored in the memory to perform the method according to any one of claims 1 to 8.

19. A computer-readable storage medium having instructions, wherein when the instructions are executed on a computer, the computer is enabled to perform the method according to any one of claims 1 to 8.

20. A computer program for causing a computer to perform the method described in any one of claims 1 to 8.

Images