Vehicle control method, device and related system

Abstract

The invention provides a vehicle control method and device and a related system, and relates to the technical field of vehicle control, in particular to the technical field of automatic driving and intelligent unlocking. The method comprises the following steps: a controller of a vehicle obtains a first order identifier sent by a server and obtains a second order identifier; the first order identifier is used for uniquely identifying the first order of the currently used vehicle. The second order identifier is used for uniquely identifying a second order of the user applying to use the vehicle. And verifying the second order identifier according to the first order identifier. After verification succeeds, the vehicle is controlled to be unlocked; and after verification fails, the vehicle is kept in a locked state. Therefore, the user can only use the order identifier to unlock the vehicle in the current vehicle use process. After the order of using the vehicle this time is finished, the order identifier for unlocking the vehicle automatically loses efficacy, so that the user is effectively prevented from continuously using the order identifier of the historical order to unlock the vehicle, the risk of unlocking the vehicle through an unconventional means is reduced, and the use safety of the vehicle is improved.

Description

TECHNICAL FIELD

[0001] The present disclosure relates to the technical field of vehicle control, in particular to the technical field of automatic driving and intelligent unlocking, and more particularly to a vehicle control method, device, system, electronic device, computer readable storage medium and computer program product. BACKGROUND

[0002] With the rapid development of autonomous driving technology (ADT), ADT has entered the commercialization stage. Some enterprises have relied on ADT to operate full unmanned autonomous taxis (Robotaxi).

[0003] In the process of using full unmanned autonomous taxis, a user first applies to use an unmanned taxi through a client device. After the unmanned taxi arrives at the pickup point of the user, the user unlocks the vehicle using verification information and takes the unmanned taxi to the destination.

[0004] However, after the user uses the verification information, it is difficult to control the verification information to be invalid. In some cases, the user can continue to use the valid verification information to unlock the vehicle by using unconventional means. Unlocking the vehicle by using the verification information that has not been successfully invalidated will seriously affect the safety of the vehicle. At present, there is a lack of a method for controlling the unlocking of the vehicle with high safety. SUMMARY

[0005] The present disclosure provides a vehicle control method, device, system, electronic device, computer readable storage medium and computer program product.

[0006] According to a first aspect, a vehicle control method is provided, the method being applied to a controller of a vehicle, and the method comprising: obtaining a first order identifier sent by a server, the first order identifier being used to uniquely identify a first order currently using the vehicle; obtaining a second order identifier, the second order identifier being used to uniquely identify a second order applied by a user to use a vehicle, the second order identifier being generated by the server based on the second order; in response to successful verification of the second order identifier according to the first order identifier, controlling the vehicle to be unlocked; and in response to failed verification of the second order identifier according to the first order identifier, maintaining the vehicle in a locked state.

[0007] According to a second aspect, a vehicle control method is provided, the method is applied to a server, the method comprises: in response to obtaining a first order creation instruction, creating a first order of a current use vehicle, generating a first order identifier of the first order, the first order identifier being used to uniquely identify the first order; sending the first order identifier to a controller of the vehicle, the first order identifier sent to the controller of the vehicle being used to verify other order identifiers obtained from a server other than the server; sending a second order identifier to a client device, the second order identifier being generated by the server based on a second order creation instruction obtained, the second order identifier being used to uniquely identify a second order of a user applying to use a vehicle, the second order identifier being used to be verified by the controller of the vehicle, the verification being used to control the vehicle to be unlocked after being successful.

[0008] According to a third aspect, a vehicle control system is provided, the system comprises a client device, a server and a controller of a vehicle.

[0009] The server is configured to, in response to obtaining a first order creation instruction, create a first order of a current use vehicle, generate a first order identifier, the first order identifier being used to uniquely identify the first order; and send the first order identifier to a controller of the vehicle.

[0010] The client device is configured to obtain a second order identifier sent by the server, the second order identifier being used to uniquely identify a second order of a user applying to use a vehicle, the second order being created by the server based on a second order creation instruction;

[0011] The controller of the vehicle is configured to obtain the first order identifier sent by the server and obtain the second order identifier; in response to successfully verifying the second order identifier according to the first order identifier, control the vehicle to be unlocked; and in response to failing to verify the second order identifier according to the first order identifier, maintain the vehicle in a locked state.

[0012] According to a fourth aspect, a vehicle control apparatus is provided, the apparatus is applied to a controller of a vehicle, and the apparatus comprises:

[0013] A first obtaining unit is configured to obtain a first order identifier sent by a server, the first order identifier being used to uniquely identify a first order of a current use vehicle;

[0014] A second obtaining unit is configured to obtain a second order identifier, the second order identifier being used to uniquely identify a second order of a user applying to use a vehicle, the second order identifier being generated by the server based on the second order;

[0015] The checking unit is configured to, in response to a successful checking of the second order identifier according to the first order identifier, control the vehicle to be unlocked; and in response to a failed checking of the second order identifier according to the first order identifier, maintain the vehicle in a locked state.

[0016] According to a fifth aspect, a vehicle control apparatus is provided, the apparatus being applied to a server, the apparatus comprising:

[0017] The creating unit is configured to, in response to obtaining a first order creating instruction, create a first order of a current use vehicle, and generate a first order identifier of the first order, the first order identifier being used to uniquely identify the first order.

[0018] The first sending unit is configured to send the first order identifier to a controller of the vehicle, and the first order identifier sent to the controller of the vehicle is used to check other order identifiers obtained from the server.

[0019] The second sending unit is configured to send a second order identifier to a client device, the second order identifier being generated by the server based on an obtained second order creating instruction, the second order identifier being used to uniquely identify a second order of the user applying to use the vehicle, and the second order identifier being used to be checked by the controller of the vehicle, and the checking being used to control the vehicle to be unlocked after a success.

[0020] According to a sixth aspect, an electronic device is provided, comprising:

[0021] at least one processor; and

[0022] a memory connected with the at least one processor in communication; wherein

[0023] The memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor to enable the at least one processor to execute the method described in any implementation manner of the first aspect, or execute the method described in any implementation manner of the second aspect.

[0024] According to a seventh aspect, a non-transitory computer-readable storage medium storing computer instructions is provided, the computer instructions being used to cause the computer to execute the method described in any implementation manner of the first aspect, or execute the method described in any implementation manner of the second aspect.

[0025] According to an eighth aspect, a computer program product is provided, comprising a computer program, the computer program being executed by a processor to implement the method described in any implementation manner of the first aspect, or implement the method described in any implementation manner of the second aspect.

[0026] The present disclosure provides a vehicle control method, device and related system. In the vehicle control method, a server generates a first order identifier based on a first order of a current vehicle usage, and sends the first order identifier to a controller of a vehicle performing the first order. When a user uses the vehicle, a client device applies to the server to create a second order and obtain a second order identifier. The controller of the vehicle obtains the second order identifier. The controller of the vehicle verifies the second order identifier based on the first order identifier obtained from the server. That is, the controller of the vehicle verifies the second order identifier of the second order applied by the user to use the vehicle, using the first order identifier of the first order of the current vehicle usage. In this way, it can be judged from the dimension of the order whether the second order applied by the user is the same as the first order of the current vehicle usage. If the verification of the second order identifier by the first order identifier is successful, it means that the second order applied by the user to use the vehicle is the first order of the current vehicle usage, and the second order identifier is valid. The controller controls the vehicle to be unlocked so that the user can normally use the vehicle. If the verification of the second order identifier by the first order identifier fails, it means that the second order applied by the user to use the vehicle is not the first order of the current vehicle usage, and the second order identifier is invalid. The controller controls the vehicle to maintain a locked state to ensure the safety of the vehicle.

[0027] In this way, the user can only use the order identifier to unlock the vehicle during the current vehicle usage. After the order of the current vehicle usage ends, the order identifier for unlocking the vehicle is automatically invalidated. Even if the user stores the order identifier of the historical order, since the historical order is different from the order of the current vehicle usage, the user cannot use the order identifier of the historical order to unlock the vehicle. Using the order identifier as verification information can ensure that the order identifier is invalidated immediately after the order ends, effectively avoiding the user continuing to use the order identifier of the historical order to unlock the vehicle, reducing the risk of unlocking the vehicle through irregular means, and improving the safety of the vehicle usage.

[0028] It should be understood that the content described in this part is not intended to identify key or important features of the embodiments of the present disclosure, nor to limit the scope of the present disclosure. Other features of the present disclosure will become apparent from the following description. BRIEF DESCRIPTION OF DRAWINGS

[0029] The accompanying drawings are used to better understand the present scheme and do not limit the present disclosure. Among them:

[0030] Figure 1 An exemplary system structure schematic diagram provided for the embodiments of the present disclosure;

[0031] Figure 2 An exemplary application scenario schematic diagram provided for the embodiments of the present disclosure;

[0032] Figure 3 Another exemplary application scenario schematic diagram provided for the embodiments of the present disclosure;

[0033] Figure 4 A flowchart of a vehicle control method provided by an embodiment of the present disclosure is shown in FIG. 1.

[0034] Figure 5 A flowchart of another vehicle control method provided by an embodiment of the present disclosure is shown in FIG. 2.

[0035] Figure 6 A system structure diagram provided by an embodiment of the present disclosure is shown in FIG. 3.

[0036] Figure 7 A structure diagram of a vehicle control device provided by an embodiment of the present disclosure is shown in FIG. 4.

[0037] Figure 8 A structure diagram of another vehicle control device provided by an embodiment of the present disclosure is shown in FIG. 5.

[0038] Figure 9 A structure diagram of a vehicle control system provided by an embodiment of the present disclosure is shown in FIG. 6.

[0039] Figure 10 A structure diagram of an electronic device provided by an embodiment of the present disclosure is shown in FIG. 7. DETAILED DESCRIPTION

[0040] Exemplary embodiments of the present disclosure are described below with reference to the accompanying drawings, which include various details of the embodiments of the present disclosure to help the understanding of the present disclosure. These should be considered in the context of the present disclosure as merely illustrative and not restrictive in nature. Thus, those ordinarily skilled in the art will recognize that various changes and modifications of the embodiments described herein can be made without departing from the scope and spirit of the present disclosure. Also, descriptions of well-known functions and structures are omitted in the following description for the sake of clarity and conciseness.

[0041] In order to facilitate the understanding and explanation of the technical solutions provided by the embodiments of the present disclosure, the background art of the present disclosure will be described first.

[0042] A full unmanned autonomous taxi (Robotaxi) is a taxi service relying on autonomous driving technology. The full unmanned autonomous taxi realizes full automatic driving of the vehicle based on technologies such as sensors, high-precision maps, and artificial intelligence, without the need for human drivers to manually drive.

[0043] When a user needs to use a Robotaxi, the user sends an order creation instruction to a server based on an application deployed on a client device of the user or other associated client devices. The server creates an order based on the order creation instruction and generates verification information, and sends the verification information to the client device that sent the order creation instruction. The server sends an instruction to a Robotaxi corresponding to the order to go to a pickup point to pick up a passenger. When the user waits for the Robotaxi to arrive at the pickup point, the user interacts with the vehicle and sends the verification information to the vehicle. The vehicle verifies the verification information, and after the verification is successful, the vehicle is unlocked. After the user enters the unlocked vehicle, the vehicle automatically drives to a destination set by the user.

[0044] To ensure the safety of the vehicle itself and the safety of driving, the Robotaxi remains in a locked state before the user arrives, and is unlocked by the user after the verification information is verified successfully, so that the user can get on the vehicle. The verification information usually includes information related to the vehicle, so that the controller of the vehicle can verify based on the information of the vehicle itself.

[0045] The verification information can be carried in a two-dimensional code, a verification code, and a Bluetooth key. Taking the Bluetooth key carrying the verification information as an example, the user sends a request to use the vehicle to the server through the client device. The server selects a vehicle to serve the user, and generates a Bluetooth key based on the vehicle information. The server sends the Bluetooth key to the client device. When the user carrying the client device approaches the vehicle, a Bluetooth communication link is established between the client device and the vehicle, and the client device sends the Bluetooth key to the vehicle. The vehicle verifies the vehicle information included in the Bluetooth key based on the vehicle information of the vehicle itself. After the verification is successful, the controller of the vehicle controls the vehicle to be unlocked.

[0046] After the user finishes using the vehicle, the verification information should be invalidated to avoid the user unlocking the vehicle privately again using the verification information, which affects the normal use of the vehicle. However, in the current vehicle control method, there is a problem that the verification information cannot be invalidated.

[0047] For example, taking a Bluetooth key as an example, in one manner, the server sends a deletion instruction for the Bluetooth key to the client device, to instruct the client device to delete the stored Bluetooth key. However, if the client device does not obtain the deletion instruction, the Bluetooth key can be stored all the time. For example, the client device disconnects from the network immediately after unlocking the vehicle by using the check information, and does not receive the deletion instruction. The user can continue to control the vehicle to be unlocked by the Bluetooth key stored by the client device after ending the current trip. In another manner, the controller of the vehicle adds the Bluetooth key to a blacklist, to realize invalidation of the Bluetooth key. However, the storage space of the controller of the vehicle is limited, and in a scenario in which multiple users frequently use the vehicle, the number of Bluetooth keys in the blacklist is too large, which can cause the Bluetooth keys originally stored in the blacklist to overflow. The overflowed Bluetooth keys recover to be valid. The user can use the overflowed Bluetooth key to unlock the vehicle.

[0048] The check information that should be invalid is still valid, which can cause the user to still be able to unlock the vehicle and perform other operations on the vehicle after ending the trip. This affects the safety of the vehicle itself and the driving safety of the vehicle, and can cause the vehicle to be unable to operate normally, and affect the normal use of other users.

[0049] Based on this, the embodiment of the present disclosure provides a vehicle control method, which uses a first order identifier of a first order for currently using a vehicle to check a second order identifier of a second order applied by a user to use the vehicle, to realize control of the vehicle to be unlocked according to whether the orders are consistent. After the order of the user ends, the order identifier immediately becomes invalid, and the user cannot use the order identifier of the historical order to unlock the vehicle again, which effectively avoids the user from continuing to unlock the vehicle by using the order identifier of the historical order, reduces the risk of unlocking the vehicle by using an irregular means, and improves the use safety of the vehicle.

[0050] In addition, compared with the manner of setting the check information to have a fixed valid time, the manner of controlling the order identifier (check information) to be invalid based on the life cycle of the order adopted by the embodiment of the present disclosure can meet the actual needs of the user to use the order, effectively solve the problem that the order does not end, but the check information becomes invalid because the valid time is exceeded, and the user cannot normally use the check information. On the other hand, the manner can avoid the risk that the user continues to use the check information to unlock the vehicle privately within the valid time after ending the order.

[0051] In order to facilitate understanding of the technical solutions provided by the embodiments of the present disclosure, the following describes the technical solutions provided by the embodiments of the present disclosure with reference to the accompanying drawings. Figure 1 The application scenario of the vehicle control method provided by the embodiment of the present disclosure is described.

[0052] Figure 1 A structural schematic diagram of an example vehicle control system 100 in which the various methods and apparatuses described herein can be implemented according to an embodiment of the present disclosure is shown. Referring to FIG. 1, the vehicle control system 100 includes a vehicle 1000 and a client device 2000. Figure 1As shown, the vehicle control system 100 includes a client device 101, a client device 102, a server 103, and a controller 104 of a vehicle. Among others, the client device 101, the client device 102, the server 103, and the controller 104 of the vehicle are connected through a network 105.

[0053] A user operating the client device 101 or the client device 102 can in turn utilize one or more client applications to interact with the server 103 to utilize the services provided by the components. It should be appreciated that various different system configurations are possible, which can vary from the vehicle control system 100. Thus, Figure 1 FIG. 1 is one example of a system for implementing the various methods described herein and is not intended to be limiting.

[0054] A user can use the client device 101 or the client device 102 to generate order information for using a vehicle. As an example, the client device 101 and the client device 102 are deployed with an application program (APP) for using a full autonomous robotaxi.

[0055] Taking the client device 101 as an example, the client device 101 can provide an interface that enables a user of the client device 101 to interact with the client device 101. The client device 101 can also output information to the user via the interface. Although Figure 1 Only two client devices are depicted, but one skilled in the art will appreciate that the present disclosure can support any number of client devices.

[0056] Client device 101 and / or 102 can include various types of computer devices, such as portable handheld devices, general purpose computers (such as personal computers and laptop computers), workstation computers, wearable devices, smart screen devices, kiosk client devices, service robots, gaming systems, thin clients, various messaging devices, sensors or other sensing devices, and the like. These computer devices can run various types and versions of software applications and operating systems, such as MICROSOFT Windows, APPLE iOS, UNIX-like operating systems, Linux or Linux-like operating systems (such as GOOGLE Chrome OS); or include various mobile operating systems, such as MICROSOFT Windows Mobile OS, iOS, Windows Phone, Android. Portable handheld devices can include cellular phones, smartphones, tablet computers, personal digital assistants (PDAs), and the like. Wearable devices can include head-mounted displays (such as smart glasses) and other devices. Gaming systems can include various handheld gaming devices, Internet-enabled gaming devices, and the like. Client device 101 and / or client device 102 can be capable of executing various different applications, such as various Internet-related applications, communication applications (such as email applications), short message service (SMS) applications, and can use various communication protocols.

[0057] Server 103 can run one or more services or software applications that control unlocking of vehicles.

[0058] In some possible implementations, server 103 can also provide other services or software applications, which can include non-virtual environments and virtual environments. In certain embodiments, these services can be provided as web-based services or cloud services, such as under a Software as a Service (SaaS) model, to users of client device 101 or client device 102.

[0059] In Figure 1 In the illustrated configuration, server 103 can include one or more components that implement the functionality performed by server 103. These components can include software components, hardware components, or a combination thereof, executable by one or more processors.

[0060] The server 103 can include one or more general purpose computers, special purpose server computers (e.g., Personal Computer (PC) servers, UNIX servers, mid-range servers, blade servers, mainframe computers, server clusters, or any other appropriate arrangement and / or combination). The server 103 can include one or more virtual machines running virtual operating systems, or other computing architectures involving virtualization (e.g., one or more flexible pools of logical storage devices that can be virtualized to maintain virtual storage devices for the servers). In various embodiments, the server 103 can run one or more services or software applications that provide the functionality described below.

[0061] The computing units in the server 103 can run one or more operating systems including any of the operating systems described above, as well as any commercially available server operating systems. The server 103 can also run any of a variety of additional server applications and / or mid-tier applications, including HyperText Transfer Protocol (HTTP) servers, File Transfer Protocol (FTP) servers, Common Gateway Interface (CGI) servers, JAVA servers, database servers, and the like.

[0062] In some possible implementations, the server 103 can include one or more applications to analyze and consolidate data feeds and / or event updates from the users of the client devices 101 and 102. The server 103 can also include one or more applications to display the data feeds and / or real-time events via one or more display devices of the client devices 101 and 102.

[0063] In addition, the server 103 can be a server of a distributed system, or a server combined with a blockchain. The server 103 can also be a cloud server, or an intelligent cloud computing server or intelligent cloud host with artificial intelligence technology. The cloud server is a host product in the cloud computing service system, to solve the defects of large management difficulty and weak business scalability in traditional physical host and Virtual Private Server (VPS) services.

[0064] The controller 104 of the vehicle can be a combination device including various control functions, responsible for various control operations of the vehicle, such as having Bluetooth function, control function of various vehicle components, computing function, etc.

[0065] The network 105 may be any type of network known to those skilled in the art that can support data communications using any of a variety of available protocols, including but not limited to the Transmission Control Protocol (TCP), the Internet Protocol (IP), the Systems Network Architecture (SNA), the Internetwork Packet Exchange (IPX), etc. By way of example only, the one or more networks 110 may be a local area network (LAN), an Ethernet-based network, a token ring, a wide area network (WAN), the Internet, a virtual network, a virtual private network (VPN), an intranet, an extranet, a blockchain network, a public switched telephone network (PSTN), an infrared network, a wireless network (e.g., Bluetooth, Wireless Fidelity (WIFI)), and / or any combination of these and / or other networks.

[0066] The above is an introduction to the components of the vehicle control system 100, including the equipment and network. Figure 1 The structure of the vehicle control system 100 shown in the figure further briefly introduces the application scenarios of the vehicle control method provided by the embodiment of the present disclosure.

[0067] See also Figure 2 and Figure 3 As shown, during the current time period, user A triggers an order creation instruction via client device 101. Client device 101 sends the order creation instruction to server 103. The server receives the order creation instruction, creates order A based on the order creation instruction, and generates an order identifier A for order A. Server 103 sends order identifier A to client device 101 and vehicle controller 104, respectively.

[0068] As an example, see Figure 2 As shown, client device 101 obtains order identifier A. When user A needs to unlock the vehicle, client device 101 sends order identifier A to vehicle controller 104. Vehicle controller 104 verifies order identifier A obtained from client device 101 using order identifier A obtained from server 103. Since order identifiers A obtained from server 103 and client device 101 both identify order A and therefore the same order, vehicle controller 104 successfully verifies and unlocks the vehicle.

[0069] As another example, referring to Figure 3 As shown, in the historical period, user B triggers the generation of an order creation instruction through the client device 102. The client device 102 sends the order creation instruction to the server 103. The server obtains the order creation instruction, creates an order B according to the order creation instruction, and generates an order identifier B of the order B. The server 103 sends the order identifier B to the client device 102 and the controller 104 of the vehicle. The client device 102 obtains the order identifier B. It should be noted that, Figure 3 The solid line represents the interaction process in the current period, and the dashed line represents the interaction process in the historical period.

[0070] In the current period, user B sends the order identifier B to the controller 104 of the vehicle through the client device 102. The controller 104 of the vehicle verifies the order identifier B obtained from the client device 102 by using the order identifier A currently obtained from the server 103. Since the order A identified by the order identifier A obtained from the server 103 is different from the order B identified by the order identifier B obtained from the client device 102, the controller 104 of the vehicle fails to verify, and maintains the locked state of the vehicle.

[0071] Therefore, the vehicle control method provided by the embodiments of the present disclosure realizes verification from the dimension of orders by comparing the order of using the vehicle created by the client device and the current order of using the vehicle, so as to ensure that the order identifier of the non-current order of using the vehicle cannot successfully unlock the vehicle, and to realize the invalidation of the order identifier of the non-current order of using the vehicle. In this way, it can effectively avoid that the user uses very unconventional means to unlock the vehicle by using the order identifier of the historical order or other order, and improves the safety of the use and operation of the vehicle.

[0072] Those skilled in the art can understand that, Figures 1-3 The schematic diagram shown is only one example in which the embodiments of the present disclosure can be implemented. The scope of application of the embodiments of the present disclosure is not limited by any aspect of the schematic diagram. For example, the above Figure 3 The scenario shown is the case of invalidation of the historical order identifier stored by other client devices. Similarly, the historical order identifier stored by the client device 101 itself will also fail to verify, and the verification process is the same as Figure 3The scenario shown is similar, and the present disclosure will not be repeated here. In addition to the verification process, there can be other implementations of the way to obtain the order identifier. For example, the client device that sends the order creation instruction and the client device that obtains the order identifier can be different devices. For example, the client device 101 sends the order creation instruction, and the order creation instruction includes the device information of the client device 102 that uses the order identifier. After the server generates the order identifier based on the order creation instruction, the server can send the order identifier to the client device 102 to enable the user of the client device 101 to help the user of the client device 102 apply for an order to use the vehicle.

[0073] In terms of application scenarios, Figures 1-3 The vehicle control system 100 shown can be applied to the operation scenario of a fully unmanned autonomous taxi, and can also be applied to other similar scenarios that control the unlocking of the vehicle through the order identifier to improve the safety of the vehicle, such as a car rental scenario, which is not limited by the present disclosure.

[0074] It can be understood that the collection, storage, use, processing, transmission, provision, and disclosure of user personal information involved in the technical solutions of the present disclosure comply with relevant laws and regulations and do not violate public order and good customs.

[0075] In order to facilitate understanding of the technical solutions provided by the embodiments of the present disclosure, the vehicle control method provided by the embodiments of the present disclosure will be described below with reference to the accompanying drawings.

[0076] Referring to Figure 4 As shown in the figure, the figure is a flowchart of a vehicle control method provided by an embodiment of the present disclosure. As Figure 4 As shown, the vehicle control method can include steps S401-S410.

[0077] S401: The client device A sends a first order creation instruction to the server.

[0078] The user of the client device A can generate the first order creation instruction by interacting with the client device A. The first order creation instruction is used to instruct the server to create a first order for the current use of the vehicle. The first order creation instruction includes information related to the creation of the order. For example, the first order creation instruction includes the account information of the user of the client device B and the vehicle use demand information, etc.

[0079] The user of the client device B is the user who actually applies to use the vehicle currently. It should be noted that the user of the client device B and the user of the client device A can be the same user or different users. For example, the user of the client device A can send the first order creation instruction through the client device A to apply to use the vehicle currently. In this case, the user of the client device B is the user of the client device A. The client device B is the same client device as the client device A. For another example, the user of the client device A can help the user of the client device B to apply for the order of using the vehicle currently. In this case, the user of the client device B is different from the user of the client device A. The client device B is different from the client device A. The account information includes, for example, an account identifier (ID) of the user B and a user contact number.

[0080] The vehicle use demand information is used to describe the demand of the user of the client device B for using the vehicle. For example, the vehicle use demand information includes preferred vehicle model, pickup point, destination, and pickup time. In addition, as another example, the first order creation instruction can further include an order validity period. The order validity period refers to the validity period of the created first order. The order validity period can be selected by the user of the client device A who applies to create the first order, or can be default. For example, the order validity period is one hour from the creation of the first order.

[0081] The disclosure does not limit the sending time of the first order creation instruction sent by the client device A to the server. As an example, in response to generating the first order creation instruction, the client device A sends the first order creation instruction to the server. As another example, in response to reaching a preset instruction sending time, the client device A sends the first order creation instruction to the server. The instruction sending time can be preset by the user of the client device A based on the demand for using the vehicle.

[0082] S402: The server acquires the first order creation instruction.

[0083] S403: The server creates the first order of using the vehicle currently and generates a first order identifier of the first order.

[0084] The server creates the first order based on the first order creation instruction. The vehicle performing the first order is determined by the server based on the first order creation instruction and the operation information of each order-acceptable vehicle.

[0085] The server generates the first order identifier of the first order. The first order identifier is used to uniquely identify the first order. The order identifiers of different orders are different. In this way, the order can be identified based on the order identifier, the comparison of the orders is realized, the invalid order identifier is identified, and the safety of unlocking the vehicle is improved.

[0086] As an example, the first order identifier can be composed of one or more characters such as numbers, symbols, and texts. The character length of the first order identifier can also be set based on requirements. As another example, the first order identifier can also be represented by image data or video data. The embodiments of the present disclosure do not limit the data form of the first order identifier.

[0087] The embodiments of the present disclosure do not limit the manner in which the server generates the first order identifier. As an example, the server generates a random number by using a random number generation algorithm, and takes the random number as the first order identifier. Taking the random number as the first order identifier can improve the cracking difficulty of the first order identifier and improve the security of verification by using the first order identifier. As another example, the server takes the serial number of the generation order of the first order in all orders as the first order identifier. As still another example, the server takes the time including the year, month, hour, minute, and second when the first order is created as the first order identifier.

[0088] S404: The server sends the first order identifier to the client device B and sends the first order identifier to the controller of the vehicle.

[0089] Based on the related description of S401 above, the client device B can be the same client device as the client device A, or can be a different client device.

[0090] The embodiments of the present disclosure do not limit the time at which the server sends the first order identifier to the client device B and the controller of the vehicle that executes the first order respectively.

[0091] In a possible implementation, the server can send the first order identifier to the client device B and the controller of the vehicle at the same time. As an example, in response to generating the first order identifier, the server sends the first order identifier to the client device B and the controller of the vehicle at the same time.

[0092] In another possible implementation, the server can also send the first order identifier to the client device B and the controller of the vehicle at different times respectively. For example, in response to generating the first order identifier, the server sends the first order identifier to the client device B. In response to detecting that the vehicle arrives at the pickup point, the server sends the first order identifier to the controller of the vehicle. As another example, in response to generating the first order identifier, the server sends the first order identifier to the client device B. In response to obtaining the order identifier acquisition request sent by the controller of the vehicle, the server sends the first order identifier to the controller of the vehicle.

[0093] Further, in some possible implementation manners, before the server sends the first order identifier to the client device B, the first order identifier can also be subjected to an encryption operation to improve the data security of the first order identifier.

[0094] The server can send the first order identifier to the client device B through a network jointly connected with the client device B. The server can send the first order identifier to the controller of the vehicle through a network jointly connected with the controller of the vehicle.

[0095] S405: The client device B acquires the first order identifier.

[0096] After acquiring the first order, the client device B can store the first order identifier.

[0097] S406: The controller of the vehicle acquires the first order identifier.

[0098] After acquiring the first order identifier, the controller of the vehicle can store the first order identifier.

[0099] S407: The controller of the vehicle acquires the second order identifier.

[0100] The second order identifier is used to uniquely identify a second order of the user of the client device C using the vehicle. The client device C pre-interacts with the server to acquire the second order identifier. The client device C is currently interacting with the controller of the vehicle to try to verify the client device that unlocks the vehicle.

[0101] As an example, the second order identifier can be composed of one or more characters such as numbers, symbols, and texts. As another example, the second order identifier can also be represented by image data or video data. The data form of the second order identifier can be the same as that of the first order identifier for verification.

[0102] It should be noted that based on whether the client device B and the client device C are the same client device and whether the first order identifier and the second order identifier identify the same order, the following three cases can be divided:

[0103] Case one: The client device B and the client device C are the same client device, and the first order identified by the first order identifier and the second order identified by the second order identifier are the same order.

[0104] In case one, the step of the client device C interacting with the server to acquire the second order identifier is the same as the step of the client device B interacting with the server to acquire the first order identifier in steps S401 to S405.

[0105] Case two: the client device B and the client device C are the same client device, and the first order identified by the first order identifier and the second order identified by the second order identifier are different orders.

[0106] Case three: the client device B and the client device C are different client devices, and the first order identified by the first order identifier and the second order identified by the second order identifier are different orders.

[0107] In case two and case three, the client device C interacts with the server to obtain the second order identifier, which is similar to the step of the client device B interacting with the server to obtain the first order identifier in steps S401-S405 described above. For details, please refer to steps S401-S405 described above, which will not be repeated here.

[0108] The embodiments of the present disclosure do not limit the manner in which the controller of the vehicle obtains the second order identifier.

[0109] In one possible implementation, the client device C displays the second order identifier to the user. The user of the client device C can input the second order identifier through an input interface deployed on the vehicle. For example, the vehicle is configured with a screen outside the door. The user of the client device C can input the second order identifier through the screen. The controller of the vehicle obtains the second order identifier through the screen.

[0110] In another possible implementation, the client device C sends the second order identifier to the controller of the vehicle. In this way, the user of the client device C does not need to manually input, reducing user operation, reducing operation cost, and improving the efficiency of verification.

[0111] As an example, the client device C can connect to the vehicle's on-board hotspot, and the client device C sends the second order identifier to the controller of the vehicle through the network. As another example, the client device C can establish a Bluetooth communication link with the controller of the vehicle, and send the second order identifier to the controller of the vehicle through the Bluetooth communication link.

[0112] In a possible case, the server sends the Bluetooth key including the second order identifier to the client device C. The Bluetooth key is used to realize remote control of the vehicle or other device based on Bluetooth technology. The basic data format and content of the Bluetooth key are determined according to the used protocol. The client device C sends the Bluetooth key including the second order identifier to the controller of the vehicle. The controller of the vehicle obtains the second order identifier by parsing the Bluetooth key. Based on the Bluetooth key including the second order identifier, the user of the client device C is in the process of approaching the vehicle, the controller of the vehicle obtains the second order identifier through Bluetooth technology and performs verification, which improves the verification speed. The user using the vehicle does not need to perform other operations, which is more convenient and improves the user experience. For implementation of transmission of the second order identifier through the Bluetooth key, refer to the specific description below.

[0113] S408: The controller of the vehicle verifies the second order identifier according to the first order identifier.

[0114] The embodiments of the present disclosure do not limit the verification method adopted by the vehicle controller.

[0115] In a possible implementation, the second order identifier sent by the server to the client device C is not subjected to other processing operations. The controller of the vehicle directly compares whether the second order identifier is the same as the first order identifier. If the second order identifier is the same as the first order identifier, it is determined that the verification of the second order identifier according to the first order identifier is successful, and step S409 is performed. If the second order identifier is different from the first order identifier, it is determined that the verification of the second order identifier according to the first order identifier fails, and step S410 is performed.

[0116] In another possible implementation, the second order identifier sent by the server to the client device C is subjected to other processing operations.

[0117] For example, the second order identifier sent by the server to the client device C is subjected to an encryption operation. The controller of the vehicle can first decrypt the second order identifier to obtain a decryption result. The controller of the vehicle compares the first order identifier with the decryption result. If the first order identifier is the same as the decryption result, it is determined that the verification of the second order identifier according to the first order identifier is successful. If the first order identifier is different from the decryption result, it is determined that the verification of the second order identifier according to the first order identifier fails, and step S410 is performed. Alternatively, the controller of the vehicle first performs the same encryption operation on the first order identifier, and compares the second order identifier with an encryption result obtained after the encryption. If the encryption result is the same as the second order identifier, it is determined that the verification of the second order identifier according to the first order identifier is successful, and step S409 is performed. If the encryption result is different from the second order identifier, it is determined that the verification of the second order identifier according to the first order identifier fails, and step S410 is performed.

[0118] S409: If the second order identifier is verified according to the first order identifier successfully, the controller of the vehicle controls the vehicle to be unlocked.

[0119] The second order identifier is verified according to the first order identifier successfully, which means that the second order identified by the second order identifier is the same as the first order identified by the first order identifier. For example, case one introduced in step S407. The controller of the vehicle controls the vehicle to be unlocked, so that the user of the client device C can use the vehicle.

[0120] S410: If the second order identifier is verified according to the first order identifier unsuccessfully, the controller of the vehicle maintains the vehicle in the locked state.

[0121] The second order identifier is verified according to the first order identifier unsuccessfully, which means that the second order identified by the second order identifier is different from the first order identified by the first order identifier, and the second order identifier is invalid. For example, case two and case three introduced in step S407. The controller of the vehicle maintains the vehicle in the locked state. That is, if the vehicle is in the unlocked state before, the controller controls the vehicle to be locked. If the vehicle is in the locked state, the vehicle continues to be locked.

[0122] In other possible implementations, the controller of the vehicle can also generate prompt information. The prompt information is used to prompt the verification failure. As an example, the prompt information is voice information. The controller of the vehicle plays the voice information. As an example, the prompt information is text information. In the case where the vehicle is configured with an external screen, the prompt information can be displayed on the screen. Or the controller of the vehicle sends the text information to the client device C. The client device C displays the text information to prompt the user of the client device C of the verification failure.

[0123] In addition, the controller of the vehicle can also generate alarm information. The alarm information is used to record the failed verification process. For example, the alarm information includes the result of the verification failure, the reason of the verification failure, the verification time, the verification location, and the second order identifier of the verification failure. The controller of the vehicle can send the alarm information to the server, so that the server analyzes the operation of unlocking the vehicle by the irregular means based on the alarm information.

[0124] Based on the above related content of S401-S410, it can be known that the second order identifier is verified according to the first order identifier. Only when the second order is consistent with the first order of the currently used vehicle, the vehicle can be unlocked effectively. After the order ends, the order identifier used for verification is invalidated immediately. The user cannot unlock the vehicle by using the order identifier of the order of the non-currently used vehicle (for example, a historical order or an order of another vehicle). In this way, the invalidation of the verification information can be realized, the use of the invalid verification information to unlock the vehicle can be avoided, and the use safety and operation safety of the vehicle can be improved.

[0125] In a possible implementation, the client device C is implemented to be verified by using the Bluetooth key including the second order identifier. The implementation of the verification of the Bluetooth key is described in detail below.

[0126] Referring to Figure 5 As shown in the figure, the figure is a flowchart of another vehicle control method provided by the embodiments of the present disclosure. As shown in the figure, Figure 5 As shown in the figure, the vehicle control method can include steps S501-S511.

[0127] S501: The client device A sends a first order creation instruction to the server.

[0128] S502: The server acquires the first order creation instruction.

[0129] S503: The server creates a first order of the current use vehicle, and generates a first order identifier of the first order.

[0130] Steps S501-S503 are the same as steps S401-S403 described above, and will not be repeated here. For details, please refer to the description of steps S401-S403 above.

[0131] S504: The server generates a Bluetooth key including the first order identifier based on the first order identifier.

[0132] In a possible implementation, the server encrypts the first order identifier to generate a structure of the Bluetooth key. In another possible implementation, the server also acquires vehicle information such as a vehicle identification number (VIN) of the vehicle. The server can also encrypt information such as the vehicle identification number, the first order identifier, and the order validity period to generate the Bluetooth key.

[0133] As an example, referring to Figure 6 As shown in the figure, the server includes a taxi order management system (OMS) and a mobile phone Bluetooth key management system (DKMS). The client device A, the client device B, and the client device C are all the same client device. The OMS acquires a first order creation instruction generated and sent by an application program (APP) deployed by the client device A. The first order and the first order identifier are generated based on the first order creation instruction. The OMS acquires information such as the vehicle identification number, the first order identifier, and the order validity period. The OMS sends the information such as the vehicle identification number, the first order identifier, and the order validity period to the DKMS. For ease of viewing, Figure 5Only the first order identifier is drawn. The DKMS performs desensitization, combination, encryption and other processing on the obtained vehicle identification code, the first order identifier and the order validity period and the like to generate a Bluetooth key including the first order identifier. The present disclosure does not limit the type of encryption algorithm used for encryption. In one possible implementation, the server is configured with an encryption chip. The DKMS can call the encryption chip to implement encryption of data. The Bluetooth key is generated by encryption, improving the security of the data included in the Bluetooth key, reducing the probability of the Bluetooth key being cracked, and further improving the security of vehicle operation. The OMS sends the first order identifier to the controller of the vehicle. The DKMS sends the Bluetooth key including the first order identifier to the APP of the client device A.

[0134] The embodiments of the present disclosure do not limit the data position of the first order identifier in the Bluetooth key. The data position of the first order identifier in the Bluetooth key can be pre-agreed in the protocol.

[0135] For example, a preset bit range of the first order identifier in the Bluetooth key is pre-agreed. The preset bit range is, for example, the i th bit to the i th + n th bit. Wherein, i and n are both positive integers. i + n is less than or equal to the total number of bits of the Bluetooth key. n is equal to the number of bits of the first order identifier. The i th bit is the starting bit of the first order identifier. The i th + n th bit is the ending bit of the first order identifier. In this way, the controller of the vehicle can extract the first order identifier from the preset bit range.

[0136] In addition to pre-agreeing the preset bit range, an indication data can also be set in the Bluetooth key. The indication data is used to indicate the starting bit of the first order identifier in the Bluetooth key. For example, the j th bit of the Bluetooth key is the indication data. j is a positive integer, j is less than the total number of bits of the Bluetooth key. The first order identifier is n-bit data. The value of the indication data indicates that the starting bit of the first order identifier is the m th bit. m is a positive integer, m + n is less than the total number of bits of the Bluetooth key. The controller of the vehicle can identify the indication data of the j th bit, read n-bit data starting from the m th bit according to the indication data and the number of bits of the first order identifier, and obtain the first order identifier.

[0137] S505: The server sends the Bluetooth key including the first order identifier to the client device B, and sends the first order identifier to the controller of the vehicle.

[0138] The server sends the Bluetooth key including the first order identifier to the client device B in a manner similar to that of the server sending the first order identifier to the client device B in the above step S404. For details, please refer to the related description in step S404 above.

[0139] The server sends the first order identifier to the controller of the vehicle in the same manner as in step S404 described above. For details, please refer to the description of step S404 above.

[0140] S506: The client device B acquires the Bluetooth key including the first order identifier.

[0141] After acquiring the Bluetooth key including the first order identifier, the client device B can store the Bluetooth key including the first order identifier for subsequent use.

[0142] S507: The controller of the vehicle acquires the first order identifier.

[0143] S508: The client device C sends the Bluetooth key including the second order identifier to the controller of the vehicle.

[0144] Similarly, the client device C and the client device B can be the same client device. The process of the client device C acquiring the Bluetooth key including the second order identifier is as described in steps S501-S505 above.

[0145] The client device C and the client device B can also be different client devices. The client device C interacts with the server to acquire the Bluetooth key including the second order identifier, which is similar to the process of the client device B interacting with the server to acquire the Bluetooth key including the first order identifier in steps S501-S505 described above. For details, please refer to steps S501-S505 described above, which will not be repeated here.

[0146] When the client device C enters the Bluetooth connection range of the vehicle, it can establish a Bluetooth communication link with the controller of the vehicle and send the Bluetooth key including the second order identifier to the controller of the vehicle through the Bluetooth communication link.

[0147] Specifically, the client device C performs initialization of the Bluetooth module in advance. The Bluetooth module of the vehicle is initialized in advance. The Bluetooth module of the vehicle sends Bluetooth broadcast data. After the Bluetooth module of the client device C acquires the Bluetooth broadcast data, it performs filtering and establishes a Bluetooth connection. The Bluetooth module of the client device C sends a passkey to the Bluetooth module of the vehicle. After the Bluetooth module of the vehicle verifies the communication key successfully, the Bluetooth module of the client device C sends wake-up data. After the Bluetooth module of the client device C acquires the wake-up data, it completes the Bluetooth connection.

[0148] The Bluetooth module of the client device C also performs authentication with the Bluetooth module of the vehicle, such as identity authentication, key negotiation, key authentication, etc.

[0149] After authentication is passed, the client device C sends the Bluetooth key including the second order identifier to the controller of the vehicle through the Bluetooth communication link.

[0150] S509: The vehicle controller obtains the Bluetooth key including the second order identifier, parses the Bluetooth key including the second order identifier, and obtains the second order identifier.

[0151] The vehicle controller obtains the Bluetooth key including the second order identifier through the Bluetooth communication link established with the client device C. The vehicle controller parses the Bluetooth key including the second order identifier.

[0152] Still with the above Figure 5 For example, the vehicle's controller includes a Bluetooth key controller (Passive Keyless Controller, PKC) and a cockpit domain controller (Cockpit Domain Controller, CDC). Assume that client device C and client device B are the same client device. Client device C sends a Bluetooth key including a second order identifier to PKC. PKC uses a decryption algorithm to process the Bluetooth key including the second order identifier to obtain decrypted data. The decryption algorithm corresponds to the encryption algorithm used by the server to generate the Bluetooth key. For example, the vehicle is equipped with an encryption chip. PKC can call the encryption chip to decrypt the Bluetooth key.

[0153] PKC obtains the second order identifier from the decrypted data.

[0154] As an example, the data location of the second order identifier in the Bluetooth key is pre-agreed. The second order identifier is obtained from the decrypted data based on a predetermined range of digits for the second order identifier in the Bluetooth key. For example, the predetermined range of digits is from digit i to digit i+n. The vehicle controller reads digits i to digit i+n of the decrypted data to obtain the second order identifier.

[0155] As another example, the data position of the second order identifier in the Bluetooth key is determined based on the indication data. The indication data is used to indicate the starting position of the second order identifier in the Bluetooth key. For example, the jth position of the Bluetooth key is the indication data. The vehicle controller obtains the jth position of the indication data and, based on the mth position (starting position) indicated by the indication data and the number of bits n of the second order identifier, reads n bits of data starting from the mth position to obtain the second order identifier.

[0156] Based on a preset bit range or indication data, the vehicle controller can determine the data position of the second order identifier in the decrypted data, so as to more accurately extract the second order identifier from the decrypted data for verification.

[0157] The PKC sends a second order identifier to the CDC through a controller area network (CAN). The CDC checks the second order identifier and performs the following steps S510-S512.

[0158] S510: The controller of the vehicle checks the second order identifier according to the first order identifier.

[0159] S511: If the second order identifier is successfully checked according to the first order identifier, the controller of the vehicle controls the vehicle to be unlocked.

[0160] S512: If the second order identifier fails to be checked according to the first order identifier, the controller of the vehicle maintains the vehicle in a locked state.

[0161] Steps S510-S512 are the same as steps S408-S410, and will not be repeated here. For details, please refer to the description of steps S408-S410.

[0162] Based on the vehicle control method provided in the above method embodiment, the embodiment of the application further provides a vehicle control device applied to a controller of a vehicle. The vehicle control device will be described below with reference to the accompanying drawings.

[0163] As shown in FIG. 7, the vehicle control device 700 provided in this embodiment includes: Figure 7

[0164] A first obtaining unit 701, configured to obtain a first order identifier sent by a server, the first order identifier being used to uniquely identify a first order of using the vehicle at present;

[0165] A second obtaining unit 702, configured to obtain a second order identifier, the second order identifier being used to uniquely identify a second order of using the vehicle applied by a user, the second order identifier being generated by the server based on the second order;

[0166] A checking unit 703, configured to control the vehicle to be unlocked in response to that the second order identifier is successfully checked according to the first order identifier, and maintain the vehicle in a locked state in response to that the second order identifier fails to be checked according to the first order identifier.

[0167] Optionally, the second obtaining unit 702, configured to obtain a second order identifier, includes:

[0168] The second obtaining unit 702 is configured to obtain a second order identifier sent by a client device.

[0169] Optionally, the second obtaining unit 702, configured to obtain a second order identifier sent by a client device, includes:​

[0170] The second obtaining unit 702 is configured to establish a Bluetooth communication link with a client device, obtain a Bluetooth key including a second order identifier sent by the client device through the Bluetooth communication link, and parse the Bluetooth key including the second order identifier to obtain the second order identifier. The Bluetooth key including the second order identifier is sent by the server to the client device.

[0171] Optionally, the second obtaining unit 702 is configured to parse the Bluetooth key including the second order identifier to obtain the second order identifier, including:

[0172] The second obtaining unit 702 is configured to process the Bluetooth key including the second order identifier by using a decryption algorithm corresponding to an encryption algorithm used for generating the Bluetooth key including the second order identifier to obtain decryption data, and obtain the second order identifier included in the decryption data.

[0173] Optionally, the second obtaining unit 702 is configured to obtain the second order identifier included in the decryption data, including:

[0174] The second obtaining unit 702 is configured to extract data of a preset bit range included in the decryption data to obtain the second order identifier.

[0175] Alternatively,

[0176] The second obtaining unit 702 is configured to determine indication data included in the decryption data, where the indication data is used to indicate a starting bit of the second order identifier in the decryption data.

[0177] The second obtaining unit 702 is configured to extract the second order identifier from the decryption data according to the starting bit and a bit number of the second order identifier.

[0178] Optionally, the checking unit 703 is configured to check that the second order identifier is successful according to the first order identifier, including:

[0179] The checking unit 703 is configured to determine that the second order identifier is the same as the first order identifier.

[0180] Optionally, the checking unit 703 is configured to check that the second order identifier fails according to the first order identifier, including:

[0181] The checking unit 703 is configured to determine that the second order identifier is different from the first order identifier.

[0182] In the embodiment, the specific processing of each unit in the vehicle control device 700 and the technical effects brought by the specific processing can be respectively referred to the related description of each step in the foregoing embodiments, and will not be described here again.

[0183] Based on the vehicle control method provided in the foregoing method embodiment, the embodiment of the application further provides a vehicle control device applied to a server, which will be described below with reference to the accompanying drawings.

[0184] As shown in Figure 8 the vehicle control device 800 provided in the embodiment includes:

[0185] The creating unit 801 is configured to, in response to obtaining a first order creation instruction, create a first order of a current use vehicle, and generate a first order identifier of the first order, the first order identifier being used for uniquely identifying the first order.

[0186] The first sending unit 802 is configured to send the first order identifier to a controller of the vehicle, and the first order identifier sent to the controller of the vehicle is used for verifying other order identifiers obtained from a server other than the server.

[0187] The second sending unit 803 is configured to send a second order identifier to a client device, the second order identifier being generated by the server based on a second order creation instruction obtained by the server, the second order identifier being used for uniquely identifying a second order of the user applying for using the vehicle, and the second order identifier being used for being verified by the controller of the vehicle, and the verification being used for controlling the vehicle to be unlocked after being successful.

[0188] Optionally, the device further includes:

[0189] The generating unit 804 is configured to generate a Bluetooth key including the second order identifier according to the second order identifier.

[0190] The second sending unit 803 is configured to send the second order identifier to the client device, and includes:

[0191] The second sending unit 803 is configured to send the Bluetooth key including the second order identifier to the client device.

[0192] In the embodiment, the specific processing of each unit in the vehicle control device 800 and the technical effects brought by the specific processing can be respectively referred to the related description of each step in the foregoing embodiments, and will not be described here again.

[0193] The embodiment of the application further provides a vehicle control system applied to a server, which will be described below with reference to the accompanying drawings.

[0194] As shown in Figure 9As shown, the vehicle control system 900 provided by the embodiment includes a client device 901, a server 902, and a controller 903 of a vehicle.

[0195] The server 902 is configured to, in response to obtaining a first order creation instruction, create a first order for current use of the vehicle, and generate a first order identifier for uniquely identifying the first order.

[0196] The server 902 is further configured to send the first order identifier to the controller 903 of the vehicle.

[0197] The client device 901 is configured to obtain the second order identifier sent by the server 902, the second order identifier being used for uniquely identifying a second order for use of the vehicle applied by a user, the second order being created by the server 902 based on a second order creation instruction.

[0198] The controller 903 of the vehicle is configured to obtain the first order identifier sent by the server 902 and obtain the second order identifier, control the vehicle to be unlocked in response to successful verification of the second order identifier according to the first order identifier, and maintain the vehicle in a locked state in response to failed verification of the second order identifier according to the first order identifier.

[0199] Optionally, the client device 901 is further configured to send the second order identifier to the controller 903 of the vehicle.

[0200] Optionally, the client device 901 is configured to send the second order identifier to the controller 903 of the vehicle, including:

[0201] The client device 901 is configured to send a Bluetooth key including the second order identifier to the controller 903 of the vehicle, the Bluetooth key including the second order identifier being generated by the server 902 based on the second order and sent to the client device 901.

[0202] The controller 903 of the vehicle is configured to obtain the second order identifier, including:

[0203] The controller 903 of the vehicle is configured to establish a Bluetooth communication link with the client device 901, obtain the Bluetooth key including the second order identifier through the Bluetooth communication link, and parse the Bluetooth key including the second order identifier to obtain the second order identifier.

[0204] Optionally, the controller 903 of the vehicle is configured to parse the Bluetooth key including the second order identifier to obtain the second order identifier, including:

[0205] The controller 903 of the vehicle is configured to process the Bluetooth key including the second order identifier by using a decryption algorithm corresponding to the encryption algorithm used for generating the Bluetooth key including the second order identifier, to obtain decryption data, and to acquire the second order identifier included in the decryption data.

[0206] Optionally, the controller 903 of the vehicle is configured to acquire the second order identifier included in the decryption data, including:

[0207] The controller 903 of the vehicle is configured to extract data of a preset bit range included in the decryption data, to obtain the second order identifier.

[0208] Alternatively,

[0209] The controller 903 of the vehicle is configured to determine indication data included in the decryption data, and to extract the second order identifier from the decryption data according to a starting bit of the second order identifier and a bit number of the second order identifier indicated by the indication data.

[0210] Optionally, the controller 903 of the vehicle is configured to verify the second order identifier according to the first order identifier, including:

[0211] The controller 903 of the vehicle is configured to determine that the second order identifier is the same as the first order identifier.

[0212] The controller 903 of the vehicle is configured to verify the second order identifier according to the first order identifier, including:

[0213] The controller 903 of the vehicle is configured to determine that the second order identifier is different from the first order identifier.

[0214] In this embodiment, the vehicle control system 900: the specific processing of each device and the technical effects brought by it can be respectively referred to the related description of each step in the foregoing embodiments, which will not be described here.

[0215] Figure 10 A schematic block diagram of an example electronic device 1000 that can be used to implement embodiments of the present disclosure is shown. The electronic device is intended to represent various forms of digital computers, such as laptops, desktops, tablets, personal digital assistants, servers, blade servers, mainframes, and other appropriate computers. The electronic device can also represent various forms of mobile devices, such as personal digital assistants, cellular telephones, smart phones, wearable devices, and other similar computing devices. The components shown here, their connections and relationships, and their functions, are meant to be examples only, and are not intended to limit the implementations of the present disclosure described and / or claimed in this document.

[0216] like Figure 10 As shown, the device 1000 includes a computing unit 1001, which can perform various appropriate actions and processes according to a computer program stored in a read-only memory (ROM) 1002 or a computer program loaded from a storage unit 1008 into a random access memory (RAM) 1003. Various programs and data required for the operation of the device 1000 can also be stored in the RAM 1003. The computing unit 1001, the ROM 1002, and the RAM 1003 are connected to each other via a bus 1004. An input / output (I / O) interface 1005 is also connected to the bus 1004.

[0217] Various components in device 1000 are connected to I / O interface 1005, including an input unit 1006, such as a keyboard, mouse, etc.; an output unit 1007, such as various types of displays, speakers, etc.; a storage unit 1008, such as a magnetic disk, optical disk, etc.; and a communication unit 1009, such as a network card, modem, wireless communication transceiver, etc. The communication unit 1009 allows device 1000 to exchange information / data with other devices via a computer network such as the Internet and / or various telecommunication networks.

[0218] The computing unit 1001 can be a variety of general-purpose and / or specialized processing components with processing and computing capabilities. Some examples of the computing unit 1001 include, but are not limited to, a central processing unit (CPU), a graphics processing unit (GPU), various dedicated artificial intelligence (AI) computing chips, various computing units that run machine learning model algorithms, a digital signal processor (DSP), and any appropriate processor, controller, microcontroller, etc. The computing unit 1001 performs the various methods and processes described above, such as the multimodal content generation method. For example, in some embodiments, the multimodal content generation method can be implemented as a computer software program that is tangibly embodied in a machine-readable medium, such as the storage unit 1008. In some embodiments, part or all of the computer program can be loaded and / or installed onto the device 1000 via the ROM 1002 and / or the communication unit 1009. When the computer program is loaded into the RAM 1003 and executed by the computing unit 1001, one or more steps of the multimodal content generation method described above can be performed. Alternatively, in other embodiments, the computing unit 1001 may be configured to execute the multimodal content generation method in any other appropriate manner (eg, by means of firmware).

[0219] The various embodiments of the systems and techniques described above can be implemented in digital electronic circuitry, integrated circuitry, a field programmable gate array (FPGA), an application specific integrated circuit (ASIC), a system on a chip (SOC), a load programmable logic device (CPLD), computer hardware, firmware, software, and / or combinations thereof. These various embodiments can include implementation in one or more computer programs that are executable and / or interpretable on a programmable system including at least one programmable processor, which can be special or general purpose, coupled to receive data and instructions from, and to transmit data and instructions to, a storage system, at least one input device, and at least one output device.

[0220] Program code for carrying out methods of the present disclosure can be written in any combination of one or more programming languages. The program code can be provided to a processor or controller of a general purpose computer, special purpose computer, or other programmable information processing apparatus to produce a machine, such that the program code, when executed by the processor or controller, implements the functions / acts specified in the flowcharts and / or block diagrams. The program code can be executed entirely on a machine, partially on a machine, partially on a machine as a standalone software package, or entirely on a remote machine or server.

[0221] In the context of the present disclosure, a machine-readable medium can be a tangible medium that contains or stores a program for use by or in connection with an instruction execution system, apparatus, or device. The machine-readable medium can be a machine-readable signal medium or a machine-readable storage medium. A machine-readable medium can include but is not limited to an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. More specific examples of the machine-readable storage medium will include one or more lines of electrical connections, portable computer disks, hard disk drives, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or Flash memory), optical fibers, portable compact disc read-only memories (CD-ROMs), optical storage devices, magnetic storage devices, or any suitable combination of the foregoing.

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

[0223] The systems and techniques described here can be implemented in a computing system that includes a back end component (e.g., as a data server), or that includes a middleware component (e.g., an application server), or that includes a front end component (e.g., a client computer having a graphical user interface or a Web browser through which a user can interact with an implementation of the systems and techniques described here), or any combination of such back end, middleware, or front end components. The components of the system can be interconnected by any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include a local area network (LAN), a wide area network (WAN), and the Internet.

[0224] The computer system can include clients and servers. A client and server are generally remote from each other and typically interact through a communication network. The relationship of client and server is generally established by computer programs running on the respective computers and having a client-server relationship to each other. The server can be a cloud server, a server of a distributed system, or a server combined with a blockchain.

[0225] It should be understood that the various forms of flow shown above can be re-ordered, added to, or deleted from without departing from the spirit and scope of the present disclosure. For example, the steps recited in the present disclosure can be performed in parallel, in series, or in a different order, as long as the desired results of the technology disclosed in the present disclosure are achieved, and the present disclosure is not limited herein.

[0226] The specific embodiments described above are not intended to be limiting, and persons skilled in the art will appreciate that various modifications, combinations, sub-combinations and alternatives can be made to the specific embodiments without departing from the spirit and scope of the disclosure. Any modifications, equivalent substitutions, improvements, and the like, made within the spirit and principles of the disclosure, are intended to be included in the scope of the disclosure.

Claims

1. A vehicle control method, characterized in that: The method is applied to a controller of a vehicle, and the method includes: Obtaining a first order identifier sent by the server, where the first order identifier is used to uniquely identify a first order currently using the vehicle; Obtaining a second order identifier, where the second order identifier is used to uniquely identify a second order for a user to apply for use of a vehicle, and the second order identifier is generated by the server based on the second order; In response to successful verification of the second order identifier according to the first order identifier, controlling the vehicle to unlock; In response to a failure in verifying the second order identifier based on the first order identifier, maintaining the vehicle in a locked state.

2. The method according to claim 1, characterized in that The obtaining of the second order identifier includes: Obtain a second order identifier sent by the client device.

3. The method according to claim 2, characterized in that The obtaining of the second order identifier sent by the client device includes: Establishing a Bluetooth communication link with the client device; Acquire, via the Bluetooth communication link, a Bluetooth key including a second order identifier sent by the client device, wherein the Bluetooth key including the second order identifier is sent by the server to the client device; Parse the Bluetooth key including the second order identifier to obtain the second order identifier.

4. The method according to claim 3, characterized in that The parsing the Bluetooth key including the second order identifier to obtain the second order identifier includes: Processing the Bluetooth key including the second order identifier using a decryption algorithm to obtain decrypted data, wherein the decryption algorithm corresponds to the encryption algorithm used to generate the Bluetooth key including the second order identifier; The second order identifier included in the decrypted data is obtained.

5. The method according to claim 4, characterized in that The obtaining of the second order identifier included in the decrypted data includes: Extracting data within a preset digit range included in the decrypted data to obtain the second order identifier; or, determining indication data included in the decrypted data, where the indication data is used to indicate a starting position of the second order identifier in the decrypted data; The second order identifier is extracted from the decrypted data according to the start bit and the number of bits of the second order identifier.

6. The method according to any one of claims 1 to 5, characterized in that The successfully verifying the second order identifier according to the first order identifier includes: Determining that the second order identifier is the same as the first order identifier; The failure to verify the second order identifier according to the first order identifier includes: It is determined that the second order identifier is different from the first order identifier.

7. A vehicle control method, characterized in that: The method is applied to a server and includes: In response to obtaining the first order creation instruction, creating a first order for the currently used vehicle, and generating a first order identifier for the first order, where the first order identifier is used to uniquely identify the first order; Sending the first order identifier to the controller of the vehicle, where the first order identifier sent to the controller of the vehicle is used to verify other order identifiers obtained from sources other than the server; A second order identifier is sent to the client device. The second order identifier is generated by the server based on the obtained second order creation instruction. The second order identifier is used to uniquely identify the second order for the user to apply for the use of the vehicle. The second order identifier is used to be verified by the controller of the vehicle. The verification is used to control the unlocking of the vehicle after success.

8. The method according to claim 7, characterized in that The method further comprises: generating a Bluetooth key including the second order identifier according to the second order identifier; The sending the second order identifier to the client device includes: Sending a Bluetooth key including the second order identifier to the client device.

9. A vehicle control system, characterized in that: The system includes a client device, a server, and a controller of a vehicle; The server is configured to, in response to obtaining the first order creation instruction, create a first order for currently using the vehicle and generate a first order identifier, where the first order identifier is used to uniquely identify the first order; The server is further configured to send the first order identifier to the controller of the vehicle; The client device is configured to obtain a second order identifier sent by the server, where the second order identifier is used to uniquely identify a second order for a user to apply for use of a vehicle, and the second order is created by the server based on a second order creation instruction; The controller of the vehicle is configured to obtain the first order identifier and the second order identifier sent by the server; In response to successful verification of the second order identifier according to the first order identifier, controlling the vehicle to unlock; In response to a failure in verifying the second order identifier based on the first order identifier, maintaining the vehicle in a locked state.

10. The system according to claim 9, characterized in that The client device is further configured to send a second order identifier to the controller of the vehicle.

11. The system according to claim 10, wherein: The client device is configured to send a second order identifier to the controller of the vehicle, comprising: The client device is configured to send a Bluetooth key including the second order identifier to a controller of the vehicle, where the Bluetooth key including the second order identifier is generated by the server based on the second order and sent to the client device; The controller of the vehicle is configured to obtain the second order identifier, including: The controller of the vehicle is used to establish a Bluetooth communication link with the client device; obtain the Bluetooth key including the second order identifier through the Bluetooth communication link; and parse the Bluetooth key including the second order identifier to obtain the second order identifier.

12. The system according to claim 11, wherein: The controller of the vehicle is configured to parse the Bluetooth key including the second order identifier to obtain the second order identifier, including: The controller of the vehicle is used to use a decryption algorithm to process the Bluetooth key including the second order identifier to obtain decrypted data and acquire the second order identifier included in the decrypted data. The decryption algorithm corresponds to the encryption algorithm used to generate the Bluetooth key including the second order identifier.

13. The system according to claim 12, wherein: The controller of the vehicle is configured to obtain the second order identifier included in the decrypted data, including: The controller of the vehicle is configured to extract data within a preset digit range included in the decrypted data to obtain a second order identifier; or, The controller of the vehicle is used to determine the indication data included in the decrypted data, and extract the second order identifier from the decrypted data based on the starting bit of the second order identifier and the number of bits of the second order identifier indicated by the indication data.

14. The system according to any one of claims 9 to 13, characterized in that: The controller of the vehicle is configured to verify that the second order identifier is successful based on the first order identifier, including: a controller of the vehicle, configured to determine that the second order identifier is the same as the first order identifier; The controller of the vehicle is configured to verify that the second order identifier fails according to the first order identifier, including: The controller of the vehicle is used to determine that the second order identifier is different from the first order identifier.

15. A vehicle control device, characterized in that: The device is applied to a controller of a vehicle, and comprises: A first acquiring unit is configured to acquire a first order identifier sent by the server, where the first order identifier is used to uniquely identify a first order currently using the vehicle; a second acquiring unit, configured to acquire a second order identifier, wherein the second order identifier is used to uniquely identify a second order for a user to apply for use of a vehicle, and the second order identifier is generated by the server based on the second order; A verification unit is used to control the vehicle to unlock in response to a successful verification of the second order identifier based on the first order identifier; and to maintain the vehicle in a locked state in response to a failure to verify the second order identifier based on the first order identifier.

16. A vehicle control device, characterized in that: The device is applied to a server, and includes: a creating unit, configured to create a first order for the currently used vehicle in response to obtaining a first order creating instruction, and generate a first order identifier for the first order, where the first order identifier is used to uniquely identify the first order; a first sending unit, configured to send the first order identifier to the controller of the vehicle, wherein the first order identifier sent to the controller of the vehicle is used to verify other order identifiers obtained from a source other than the server; The second sending unit is used to send a second order identifier to the client device. The second order identifier is generated by the server based on the obtained second order creation instruction. The second order identifier is used to uniquely identify the second order for the user to apply for the use of the vehicle. The second order identifier is used to be verified by the controller of the vehicle. The verification is used to control the unlocking of the vehicle after success.

17. An electronic device, characterized in that: include: at least one processor; as well as a memory communicatively connected to the at least one processor; wherein, The memory stores instructions that can be executed by the at least one processor, and the instructions are executed by the at least one processor to enable the at least one processor to perform the method of any one of claims 1 to 6, or the method of any one of claims 7 and 8.

18. A non-transitory computer-readable storage medium storing computer instructions, characterized in that: The computer instructions are used to enable the computer to execute the method according to any one of claims 1 to 6, or to execute the method according to any one of claims 7 and 8.

19. A computer program product, characterized in that The invention comprises a computer program, which implements the method according to any one of claims 1 to 6, or the method according to any one of claims 7 and 8 when being executed by a processor.

Images