A vehicle management method, device, storage medium, and electronic device

Abstract

Embodiments of the present application disclose a vehicle management method, device, storage medium and electronic device. Among them, the method includes: obtaining first vehicle information of a vehicle and signature information, where the signature information is generated based on second vehicle information of the vehicle and a private key, obtaining a public key for the vehicle from a service platform based on the first vehicle information, and determining a vehicle authentication status of the vehicle based on the public key, the signature information and the first vehicle information. By adopting the embodiments of the present application, vehicle management can be optimized and information misappropriation can be avoided.

Description

Technical Field

[0001] This application relates to the field of computer technology, and in particular, to a vehicle management method, apparatus, storage medium, and electronic device. Background Art

[0002] With the rapid development of the economy, people's living standards have also improved. Vehicles such as cars, electric vehicles, and trucks have become common tools in people's daily lives. People can use a mobile terminal in conjunction with a vehicle and use the mobile terminal to manage the vehicle. For example, the display data of the mobile terminal can be sent to the vehicle for screen projection display. Summary of the Invention

[0003] Embodiments of this application provide a vehicle management method, apparatus, storage medium, and electronic device. The technical solutions are as follows:

[0004] In a first aspect, an embodiment of this application provides a vehicle management method applied to a mobile terminal. The method includes:

[0005] Obtain first vehicle information and signature information of a vehicle sent by a vehicle-mounted terminal;

[0006] Based on the first vehicle information, obtain a public key for the vehicle from a service platform;

[0007] Use the public key to decrypt the signature information to obtain second vehicle information;

[0008] Match the second vehicle information and the first vehicle information to determine the vehicle authentication status of the vehicle.

[0009] In a second aspect, an embodiment of this application provides another vehicle management method applied to a vehicle-mounted terminal. The method includes:

[0010] Obtain first vehicle information and signature information, where the signature information is generated based on second vehicle information of the vehicle;

[0011] Transmit the first vehicle information and the signature information to a mobile terminal. The first vehicle information and the signature information are used to instruct the mobile terminal to decrypt the signature information with a public key obtained from a service platform to obtain second vehicle information, so as to determine the vehicle authentication status of the vehicle based on the second vehicle information and the first vehicle information.

[0012] In a third aspect, an embodiment of this application provides another vehicle management method applied to a service platform. The method includes:

[0013] Sign the second vehicle information of the vehicle using the private key to obtain signature information, and send the signature information to the in-vehicle terminal; or, send the private key to the in-vehicle terminal, where the private key is used to instruct the in-vehicle terminal to sign the second vehicle information to obtain signature information;

[0014] Receive the first vehicle information sent by the mobile terminal and send the public key of the vehicle to the mobile terminal. The first vehicle information is sent after the mobile terminal obtains the first vehicle information and signature information of the vehicle from the in-vehicle terminal. The public key is used for the vehicle to decrypt the signature information to obtain the second vehicle information, so as to determine the vehicle authentication status of the vehicle based on the second vehicle information and the first vehicle information.

[0015] Fourthly, an embodiment of the present application provides a vehicle management device, and the device includes:

[0016] An information acquisition module, configured to acquire the first vehicle information and signature information of the vehicle sent by the in-vehicle terminal;

[0017] A public key acquisition module, configured to acquire the public key of the vehicle from the service platform based on the first vehicle information;

[0018] A status determination module, configured to decrypt the signature information using the public key to obtain the second vehicle information; perform information matching on the second vehicle information and the first vehicle information to determine the vehicle authentication status of the vehicle.

[0019] Fifthly, an embodiment of the present application provides another vehicle management device, and the device includes:

[0020] An information acquisition module, configured to acquire the first vehicle information and signature information, where the signature information is generated based on the second vehicle information of the vehicle;

[0021] An information transmission module, configured to transmit the first vehicle information and the signature information to the mobile terminal. The first vehicle information and the signature information are used to instruct the mobile terminal to decrypt the signature information based on the public key obtained from the service platform to obtain the second vehicle information, so as to determine the vehicle authentication status of the vehicle based on the second vehicle information and the first vehicle information.

[0022] Sixthly, an embodiment of the present application provides another vehicle management device, and the device includes:

[0023] An information processing module, configured to sign the second vehicle information of the vehicle using the private key to obtain signature information, and send the signature information to the vehicle; or, send the private key to the vehicle, where the private key is used to instruct the vehicle to sign the second vehicle information to obtain signature information;

[0024] A public key sending module, configured to, after the mobile terminal obtains the signature information and the first vehicle information, receive the first vehicle information sent by the mobile terminal and send a public key for the vehicle to the mobile terminal, where the public key is used for the vehicle to decrypt the signature information with the public key to obtain second vehicle information, so as to determine the vehicle authentication status of the vehicle based on the second vehicle information and the first vehicle information.

[0025] In a third aspect, an embodiment of the present application provides a computer storage medium, which stores multiple instructions, and the instructions are suitable for being loaded and executed by a processor to perform the above method steps.

[0026] In a fourth aspect, an embodiment of the present application provides an electronic device, which may include: a processor and a memory; wherein, the memory stores a computer program, and the computer program is suitable for being loaded and executed by the processor to perform the above method steps.

[0027] The beneficial effects brought by the technical solutions provided by some embodiments of the present application at least include:

[0028] In one or more embodiments of the present application, the mobile terminal sends the first vehicle information and the signature information of the vehicle to the vehicle-mounted terminal, and then obtains the public key for the vehicle from the service platform based on the first vehicle information; then uses the public key to decrypt the signature information to obtain second vehicle information, and matches the second vehicle information and the first vehicle information, and the vehicle authentication status of the vehicle can be determined. The entire vehicle management process does not rely on a dedicated chip on the vehicle side for vehicle security management, optimizes the vehicle management process, can detect the misappropriation of vehicle information, and improves the security of vehicle management services (such as screen mirroring display services). BRIEF DESCRIPTION OF THE DRAWINGS

[0029] In order to more clearly illustrate the technical solutions in the embodiments of the present application or the prior art, the following will briefly introduce the drawings required for use in the description of the embodiments or the prior art. Obviously, the drawings in the following description are only some embodiments of the present application, and those of ordinary skill in the art can also obtain other drawings based on these drawings without creative efforts.

[0030] Figure 1 is a schematic flowchart of a vehicle management method provided by an embodiment of the present application;

[0031] Figure 2 is a schematic flowchart of another vehicle management method provided by an embodiment of the present application;

[0032] Figure 3It is a schematic diagram of an interface of a target interface involved in an embodiment of the present application;

[0033] Figure 4 It is a schematic diagram of a scenario of vehicle identification operation input involved in an embodiment of the present application;

[0034] Figure 5 It is a schematic flowchart of another vehicle management method provided by an embodiment of the present application;

[0035] Figure 6a It is a schematic flowchart of another vehicle management method provided by an embodiment of the present application;

[0036] Figure 6b It is a schematic flowchart of another vehicle management method provided by an embodiment of the present application;

[0037] Figure 6c It is a schematic diagram of the architecture of a vehicle management system provided by an embodiment of the present application;

[0038] Figure 7 It is a schematic diagram of the structure of a vehicle management device provided by an embodiment of the present application;

[0039] Figure 8 It is a schematic diagram of the structure of a status determination module provided by an embodiment of the present application;

[0040] Figure 9a It is a schematic diagram of the structure of another vehicle management device provided by an embodiment of the present application;

[0041] Figure 9b It is a schematic diagram of the structure of another vehicle management device provided by an embodiment of the present application;

[0042] Figure 9c It is a schematic diagram of the structure of another vehicle management device provided by an embodiment of the present application;

[0043] Figure 10 It is a schematic diagram of the structure of an electronic device provided by an embodiment of the present application;

[0044] Figure 11 It is a schematic diagram of the structure of an operating system and a user space provided by an embodiment of the present application;

[0045] Figure 12 It is Figure 10 The architecture diagram of the Android operating system in

[0046] Figure 13 It is Figure 10 The architecture diagram of the IOS operating system in

[0047] Figure 14 It is a schematic diagram of the structure of a vehicle-mounted terminal provided by an embodiment of the present application;

[0048] Figure 15 It is a schematic structural diagram of a service platform provided by an embodiment of the present application. Specific embodiments

[0049] Next, the technical solutions in the embodiments of the present application will be clearly and completely described in conjunction with the accompanying drawings in the embodiments of the present application. Obviously, the described embodiments are only a part of the embodiments of the present application, rather than all the embodiments. Based on the embodiments in the present application, all other embodiments obtained by those of ordinary skill in the art without making creative efforts shall fall within the protection scope of the present application.

[0050] In the description of the present application, it should be understood that the terms "first", "second", etc. are only used for descriptive purposes and cannot be construed as indicating or implying relative importance. In the description of the present application, it should be noted that unless otherwise clearly specified and limited, "including" and "having", as well as any variations thereof, are intended to cover non-exclusive inclusion. For example, a process, method, system, product or device that includes a series of steps or units is not limited to the listed steps or units, but optionally further includes steps or units not listed, or optionally further includes other steps or units inherent to these processes, methods, products or devices. For those of ordinary skill in the art, the specific meanings of the above terms in the present application can be understood according to specific circumstances. In addition, in the description of the present application, unless otherwise stated, "a plurality of" means two or more. "And / or" describes the association relationship of associated objects and indicates that three relationships can exist. For example, A and / or B can represent: A exists alone, A and B exist simultaneously, and B exists alone. The character " / " generally represents an "or" relationship between the associated objects before and after.

[0051] The present application will be described in detail below in conjunction with specific embodiments.

[0052] In one embodiment, as Figure 1As shown in the figure, a vehicle management method is proposed. This method can be implemented relying on a computer program and can run on a vehicle management device based on the von Neumann architecture. The computer program can be integrated into an application or run as an independent tool-type application. The vehicle management device can be a mobile terminal, including but not limited to: personal computers, tablet computers, handheld devices, in-vehicle devices, wearable devices, computing devices, or other processing devices connected to a wireless modem, etc. In different networks, mobile terminal devices can be called different names, such as: user equipment, access mobile terminal, user unit, user station, mobile station, mobile platform, remote station, remote mobile terminal, mobile device, user mobile terminal, mobile terminal, wireless communication device, user agent or user device, cellular phone, cordless phone, devices in 5G networks or future evolved networks, etc.

[0053] Specifically, the vehicle management method includes:

[0054] S101: Obtain the first vehicle information and signature information of the vehicle sent by the in-vehicle terminal.

[0055] It can be understood that in actual applications, the in-vehicle terminal can be used in conjunction with the vehicle. For example, the in-vehicle terminal can be installed on the vehicle. In some implementation scenarios, the in-vehicle terminal can be part of the vehicle. The in-vehicle terminal usually stores the first vehicle information and signature information of the vehicle. In some embodiments, the signature information is generated based on the second vehicle information and private key of the vehicle;

[0056] It can be understood that the in-vehicle terminal usually has a communication function and is a hardware device capable of communicating and transferring information with other devices inside the vehicle through a Controller Area Network (CAN) bus. The in-vehicle terminal can be a communication device, supplemented with a microphone and speaker, and can communicate in real time with other communication terminals (such as mobile terminals), such as making and answering calls, sending and receiving text messages, and accessing the Internet, etc., for establishing communication with the mobile terminal. It can also be used to collect vehicle-related information including location information, vehicle status information, etc., to complete the reporting of vehicle information and the reception of instructions, etc.;

[0057] With the rapid popularization of vehicles, the application interaction scenarios based on vehicles and mobile terminals in daily life are becoming more and more extensive. For example, the mobile terminal projects the display interface onto the display screen of the in-vehicle terminal used in conjunction with the vehicle, and the mobile terminal can establish a communication connection with the in-vehicle terminal used in conjunction with the vehicle. In these application interaction scenarios, it usually involves vehicle management from the mobile terminal to the vehicle, such as vehicle identity authentication of the vehicle by the mobile terminal. After vehicle identity authentication, application interaction between the mobile terminal and the in-vehicle terminal used in conjunction with the vehicle can be carried out.

[0058] The vehicle information may be understood as the vehicle model information, license plate information, vehicle component information (such as engine number, etc.), owner information, etc. corresponding to the vehicle, which is at least necessary information that uniquely represents the identity of the vehicle.

[0059] The first vehicle information can be understood as the vehicle information of the vehicle acquired by the mobile terminal from the vehicle terminal.

[0060] The second vehicle information can be understood as the original vehicle information corresponding to the signature information, and the signature information is usually obtained by encrypting the original vehicle information with a private key (also called a digital signature). Generally, when the vehicle is compliant or legal, the first vehicle information is consistent with the second vehicle information. When there is a vehicle non-compliant or illegal situation such as vehicle information fraud, the first vehicle information and the second vehicle information may be inconsistent.

[0061] In some implementation scenarios, the vehicle's signature information can be obtained by requesting the service platform for a digital signature based on the original vehicle information (i.e., the second vehicle information) on the vehicle side (e.g., the vehicle manufacturer or the vehicle itself) when the vehicle leaves the factory or is in use. In specific implementations, the second vehicle information can be sent to the service platform when the vehicle leaves the factory, and the service platform digitally signs the second vehicle information with a private key to obtain the signature information, and then sends the signature information to the vehicle side and stores it on the vehicle terminal. In some implementation scenarios, the vehicle's signature information can be obtained by requesting the service platform for a private key for digital signature based on the vehicle's vehicle terminal when the vehicle leaves the factory or is in use, and the vehicle terminal digitally signs the original vehicle information (i.e., the second vehicle information) based on the private key to obtain the signature information.

[0062] Furthermore, the private keys and vehicles mentioned above may have a one-to-one correspondence, that is, different private keys are used to digitally sign the (second) vehicle information of different vehicles, such as the service platform assigns different private keys for digital signatures to different vehicles.

[0063] It is understandable that the mobile terminal may first establish a communication connection with the vehicle terminal, and after the communication connection is established, obtain the first vehicle information and signature information from the software development kit (SDK) of the vehicle terminal. That is, after obtaining the signature information, the vehicle terminal may store or write the first vehicle information and signature information to the software development kit (SDK) running on the vehicle terminal, and after subsequently establishing a communication connection with the mobile terminal, the mobile terminal may read the first vehicle information and signature information from the software development kit (SDK) running on the vehicle.

[0064] It can be understood that the first vehicle information and the signature information can also be stored by the in-vehicle terminal corresponding to the vehicle at a set target storage location. After the mobile terminal establishes a communication connection, the vehicle can send the first vehicle information and the signature information from the target storage location to the mobile terminal. At this time, the mobile terminal completes the acquisition step.

[0065] Optionally, the mobile terminal or the vehicle may have a communication sensing range, which is determined based on the communication connection protocol between the mobile terminal and the vehicle. It can be understood that the in-vehicle terminal used in cooperation with the mobile terminal and the vehicle does not need to establish a communication connection. As long as the communication sensing range of the mobile terminal covers the vehicle (such as the sensing range corresponding to the near-field communication signal), the mobile terminal can sense the vehicle. At this time, the mobile terminal can obtain the first vehicle information and the signature information of the vehicle.

[0066] For example, when the mobile terminal uses the energy of the included power supply component (such as an internal battery) to provide a radio frequency field, and the radio frequency range corresponding to the radio frequency field can cover the vehicle, the vehicle can receive the radio frequency signal of the mobile terminal. At this time, the vehicle uses the load modulation technology to feedback the response data (such as the first vehicle information and the signature information for vehicle management) to the mobile terminal at the same speed. After the mobile terminal receives the first vehicle information and the signature information, the mobile terminal can complete the acquisition step.

[0067] S102: Obtain the public key for the vehicle from the service platform based on the first vehicle information.

[0068] It is possible that the public key and the private key for the vehicle are a key pair obtained through a key generation algorithm (that is, a public key and a private key). The public key is public to the mobile terminal, and the private key may not be made public. It can be stored only in the service platform or the vehicle. For example, the service platform can generate the public key and the private key for the vehicle based on a key generation algorithm (such as using the vehicle identification of the vehicle as the data source). In actual applications, the signature information is obtained by encrypting the vehicle information with the private key.

[0069] In this application, generally, the public key and the private key exist in pairs and correspond to each other. The method of using the public key and the private key to encrypt and decrypt data (such as the vehicle information involved in this application) is generally called the asymmetric encryption method. Among them, the public key and the private key can be allocated based on an asymmetric encryption algorithm, and the asymmetric encryption algorithm includes but is not limited to the RSA encryption algorithm, the Elgamal encryption algorithm, the knapsack algorithm, the Rabin encryption algorithm, the ECC (elliptic curve encryption algorithm), and so on.

[0070] In some implementation scenarios, in the vehicle management scenario involved in the present application, the service platform assigns a private key and a public key for the vehicle; the vehicle side is not involved in the generation of the private key and the public key. On the service platform side, a key mapping relationship between the vehicle information of multiple vehicles and the key pair (private key and / or public key) can be established. In the actual application environment, the mobile terminal can obtain the public key for the vehicle from the service platform based on the first vehicle information of the vehicle.

[0071] In some implementation scenarios, the service platform is the server associated with the mobile terminal. The service platform and the mobile terminal are jointly used to implement the vehicle authentication process for the vehicle before providing vehicle application services, and verify whether the vehicle is a compliant or legal device. That is to say, after the vehicle authentication is passed, the mobile terminal can safely respond to the human-computer interaction operations based on the vehicle, such as casting the display interface of the mobile terminal to the vehicle, transmitting the multimedia data of the mobile terminal to the vehicle for playback, etc.; and can avoid the situation of poor interaction experience when the vehicle with risks interacts with the mobile terminal in the subsequent human-computer interaction scenario. For example, if the vehicle is a risk vehicle and not a vehicle that has passed the authentication, since the vehicle may be modified, misappropriated, pirated, etc., in the case of vehicle management on the mobile terminal side such as vehicle and mobile terminal interaction (such as screen mirroring interaction, data sharing), the interaction experience and vehicle management effect will be reduced.

[0072] It can be understood that the mobile terminal can send a public key acquisition request carrying the first vehicle information to the service platform. The service platform responds to the public key acquisition request, determines the public key for the vehicle based on the first vehicle information in the key mapping relationship, and then sends the public key to the mobile terminal. At this time, the mobile terminal has completed obtaining the public key for the vehicle.

[0073] S103: Use the public key to decrypt the signature information to obtain the second vehicle information, match the second vehicle information and the first vehicle information, and determine the vehicle authentication status of the vehicle.

[0074] It can be understood that after the mobile terminal obtains the public key for the vehicle from the server through the saved vehicle information, it uses the public key to decrypt the signature information to obtain the second vehicle information.

[0075] Schematically, usually when the first vehicle information data source of the vehicle is normal, the correct public key of the vehicle can usually be successfully obtained at this time. The second vehicle information decrypted using the public key usually matches the first vehicle information. For example, the first vehicle information and the second vehicle information are consistent. In the case where the first vehicle information data source of the vehicle is abnormal (such as vehicle information being misused, tampered with, lost, etc.), the public key of the vehicle obtained at this time is usually incorrect, and it is difficult to decrypt the correct second vehicle information using the incorrect public key. That is to say, at this time, the decrypted second vehicle information usually does not match the first vehicle information.

[0076] It can be understood that the mobile terminal encrypts the first vehicle information using the obtained public key to obtain the second vehicle information. The mobile terminal matches the first vehicle information with the second vehicle information and determines the vehicle authentication status of the vehicle based on the matching result.

[0077] Optionally, the similarity (i.e., the matching result) between the first vehicle information and the second vehicle information can be calculated. When the similarity

[0078] meets the threshold, the mobile terminal determines that the vehicle authentication of the vehicle passes;

[0079] When the similarity does not meet the threshold, the mobile terminal determines that the vehicle authentication of the vehicle fails;

[0080] In some implementation scenarios, the threshold can be 100%, that is, the first vehicle information and the second vehicle information need to be exactly the same in terms of data.

[0081] In some implementation scenarios, the threshold can be determined based on the actual vehicle information coding rules. For example, for vehicles of the same category or the same series, the difference in their vehicle information is relatively small. Considering that there are a large number of vehicles, if the vehicle information coding is detailed to a specific vehicle, it will occupy too much vehicle management resources (such as storage resources). The threshold can be set to a value less than or equal to 100%. It can be understood that the threshold is set based on the vehicle display coding rules. For example, the threshold is determined based on the number of vehicles of the same category or the same series.

[0082] In the embodiments of the present application, the mobile terminal can obtain the first vehicle information and the signature information of the vehicle sent by the in-vehicle terminal. The signature information is generated based on the second vehicle information and the private key of the vehicle. Then, based on the first vehicle information, the mobile terminal obtains the public key for the vehicle from the service platform; and then determines the vehicle authentication status of the vehicle based on the public key, the signature information, and the first vehicle information. The entire vehicle management process does not rely on a dedicated chip on the vehicle side for vehicle security management, optimizes the vehicle management process, can detect the misuse of vehicle information, and improves the security of vehicle management services (such as screen mirroring display services) on the mobile terminal side.

[0083] Please refer to Figure 2 , Figure 2 which is a schematic flowchart of another embodiment of a vehicle management method proposed in this application. Specifically:

[0084] S201: Obtain the first vehicle information and signature information sent by the in-vehicle terminal.

[0085] Specifically, please refer to step S101, which will not be elaborated here.

[0086] S202: Based on the first vehicle information, obtain the public key for the vehicle from the service platform, and use the public key to decrypt the signature information to obtain the second vehicle information;

[0087] Specifically, please refer to step S102, which will not be elaborated here.

[0088] S203: Match the second vehicle information and the first vehicle information to obtain an information matching result.

[0089] In some embodiments, vehicle information can be understood as necessary information that at least uniquely characterizes the vehicle identity, such as vehicle model information, license plate information, vehicle component information (such as engine number, etc.), owner information, etc. The information data type of vehicle information can be information data types such as text, image, audio, video, etc., which is specifically determined based on the actual application situation. In this application, the "first" and "second" in the first vehicle information and the second vehicle information are only for descriptive purposes. The first vehicle information is used to represent the vehicle information obtained by the mobile terminal from the in-vehicle terminal corresponding to the vehicle, and the second vehicle information is used to represent the vehicle information obtained by the mobile terminal by decrypting the signature information.

[0090] It can be understood that matching the second vehicle information and the first vehicle information: Vehicle features can be extracted from the second vehicle information and the first vehicle information respectively, and the vehicle features are used for matching and comparison to obtain an information matching result. Further, vehicle features can include, but are not limited to, one or more fittings of vehicle model features corresponding to the vehicle model information, license plate features corresponding to the license plate information, owner features corresponding to the owner information, vehicle appearance features corresponding to the vehicle appearance information, etc.

[0091] Optionally, the mobile terminal extracts the first vehicle features in the first vehicle information, extracts the second vehicle features in the second vehicle information, and performs feature matching (such as vehicle model feature matching, license plate feature matching, vehicle appearance feature matching, etc.) on the first vehicle features and the second vehicle features to obtain an information matching result including each feature matching result.

[0092] Among them, the matching processing method for feature matching of the first vehicle feature and the second vehicle feature: It can be calculating the similarity between the first vehicle feature and the second vehicle feature, or calculating the similarity distance between the first vehicle feature and the second vehicle feature; It can be calculating the differential feature information of the first vehicle feature and the second vehicle feature, and then performing rating or scoring based on the differential feature information; and so on.

[0093] Specifically, after the mobile terminal obtains the information matching result according to the above matching processing method, it judges the information matching result according to the preset vehicle authentication rule. When the information matching result meets the set vehicle authentication requirement, it determines that the information matching result is passed; when the information matching result meets the set vehicle authentication requirement, it determines that the information matching result is failed.

[0094] Optionally, when the information matching result is based on calculating the similarity between the first vehicle feature and the second vehicle feature, the vehicle authentication rule can be setting a similarity threshold. When the similarity of the information matching result reaches the similarity threshold, it is determined that the information matching result is passed; when the similarity of the information matching result does not reach the similarity threshold, it is determined that the information matching result is failed.

[0095] Optionally, when the information matching result is based on calculating the similarity distance between the first vehicle feature and the second vehicle feature, the vehicle authentication rule can be setting a similarity distance threshold. When the similarity distance of the information matching result reaches the similarity distance threshold, it is determined that the information matching result is passed; when the similarity distance of the information matching result does not reach the similarity distance threshold, it is determined that the information matching result is failed.

[0096] Optionally, when the information matching result is based on the rating or scoring of the differential feature information calculated from the first vehicle feature and the second vehicle feature, the vehicle authentication rule can be setting a rating threshold or a scoring threshold. When the rating of the information matching result reaches the rating threshold or the scoring reaches the scoring threshold, it is determined that the information matching result is passed; otherwise, it is determined that the information matching result is failed.

[0097] It can be understood that in actual applications, there are usually multiple types of vehicle features. In actual applications, it can be based on the vehicle features of at least one of the above vehicle feature types for reference, that is, when the mobile terminal determines that the first vehicle feature and the second vehicle feature of a certain type match, it determines that the vehicle is in a vehicle authentication passed state; it can be based on the comprehensive reference of the vehicle features of multiple vehicle feature types, such as comprehensively referring to the vehicle type feature matching, vehicle appearance feature and license plate feature matching to determine the vehicle authentication status of the vehicle.

[0098] S204: If the information matching result is a pass, determine that the vehicle authentication status of the vehicle is a passed status;

[0099] For details, refer to step S203, which will not be elaborated here.

[0100] S205: If the information matching result is a failure, determine that the vehicle authentication status of the vehicle is a failed status.

[0101] For details, refer to step S203, which will not be elaborated here.

[0102] In some implementation scenarios, vehicle management can be performed based on S201 - S205 to determine the vehicle authentication status of the vehicle.

[0103] S206: Display the first vehicle information in the target interface.

[0104] It can be understood that the target interface can refer to an interactive interface developed by a third party or provided by the mobile terminal operating system, including the target interfaces for vehicle management in some third - party developed applications, applets, plugins, application services, etc.

[0105] The target interface is usually an interactive interface with interactive functions and vehicle management functions. Such a target interface can at least realize the interaction between the vehicle and the mobile terminal. For example, the user can control the vehicle status through the target interface on the mobile terminal - mobile phone; for example, the mobile terminal can display the current status information of the vehicle (such as current battery level, connection status, etc.) or vehicle information.

[0106] Schematically, as Figure 3 shown, Figure 3 is a schematic diagram of a target interface involved in this application. In the Figure 3 shown target interface, the target interface can be a vehicle management interface. The mobile terminal can display second vehicle information such as vehicle identification images, vehicle models, owners, license plates, etc. in the controls of the target interface. Further, there is at least one function control in the target interface, such as a control for car - machine screen mirroring, a control for car - machine authentication, a control for car - machine connection, etc. Based on this target interface, the interaction between the vehicle and the mobile terminal can be realized, and the mobile terminal can display the target interface to the user, and further realize the vehicle management of the vehicle based on the user's human - machine interaction operations.

[0107] Optionally, the execution order of S206 can be after S202, that is, the mobile terminal can directly display the first vehicle information after obtaining it; the execution order of S206 can also be after S204 or S205, that is, the mobile terminal displays the first vehicle information only after determining the vehicle authentication status of the vehicle. For example, the mobile terminal can display the first vehicle information only when it determines that the vehicle authentication status is the vehicle authentication passed status. It can be understood that when the vehicle authentication fails, considering the legality or compliance of the vehicle, the vehicle is not displayed to avoid wasting unnecessary vehicle management resources. It can be understood that: if the information matching result is a match, the step of displaying the first vehicle information in the target interface is executed.

[0108] It can be understood that the first vehicle information is usually displayed in a control in the target interface. For example, the vehicle information is displayed according to the display rules corresponding to the target interface. The control can be understood as the "encapsulation of data and methods" corresponding to the display content for developing and constructing the user display interface (i.e., the UI interface) of the mobile terminal. Through the control, certain method functions can be realized. For example, the functions of interface elements such as windows, text boxes, buttons, and drop-down menus can be provided. In this application, specific vehicle display information can be displayed based on, for example, display controls. Common display controls include text controls for displaying text and image controls for displaying images. In this application, in addition to being used for vehicle display, the target interface can also provide operable controls for receiving user input and performing vehicle management on the vehicle, such as command controls. The command control can be used to start specific functions (such as screen mirroring functions, connection functions), and can be a button control, an icon control, a hyperlink control, etc. Another example is that the input control is used to input data, and the selection control is used to provide selection options or data, and so on.

[0109] In a feasible implementation manner, the vehicle management interaction between the in-vehicle terminal and the mobile terminal is often mainly on the mobile terminal side. When the mobile terminal performs vehicle management on a vehicle, vehicle authentication needs to be performed on the vehicle to avoid situations such as misappropriation of vehicle information. In this application, vehicle authentication can be implemented based on the vehicle information saved by the in-vehicle terminal for the vehicle according to S201 - S205; in some scenarios, to further improve the accuracy of vehicle authentication, ensure the security of vehicle interaction, and enhance the experience of vehicle interaction; vehicle authentication can also be performed based on the vehicle identification information input by the user on the target interface. It can be understood that on the basis of the first-round authentication based on the first vehicle information and the second vehicle information, vehicle secondary authentication is also performed based on the vehicle identification information input by the user on the target interface to improve the accuracy of vehicle authentication in vehicle management. In some implementation manners, it can avoid misappropriating the vehicle information of legal or compliant vehicles during the factory stage or use stage of the vehicle. Further, the keys (public key, private key) usually assigned by the service platform to the vehicle are usually fixed in quantity or fixed for the vehicle type, and vehicle dealers may misappropriate the vehicle information of legal or compliant vehicles to save costs. At this time, it is usually difficult to identify the actual status of the vehicle based on the vehicle management by the service platform. Based on this, the user can be prompted to perform vehicle secondary authentication with the vehicle identification information input on the target interface.

[0110] In a feasible implementation manner, the mobile terminal can also perform vehicle authentication only based on the vehicle identification information input by the user on the target interface.

[0111] S207: Receive the vehicle identification information input for the target interface, and determine the vehicle authentication status of the vehicle based on the vehicle identification information.

[0112] The vehicle identification information is the information input by the user based on the second vehicle information displayed on the target interface for instructing the mobile terminal to determine the vehicle authentication status. It can be understood that: the second vehicle information may be different from the actual condition of the vehicle. For example, vehicle dealers misappropriate vehicle information to save authentication costs, that is, misappropriate the vehicle information of other vehicle models to the target vehicle, thereby saving the cost of requesting the key for authentication from the service platform (the key information for authentication is usually only valid for the target quantity or single model vehicle).

[0113] In this application, determining the vehicle authentication status of the vehicle based on the vehicle identification information may be: during the vehicle management process, for the first time determining the vehicle authentication status of the vehicle based on the vehicle identification information; or it may be updating the vehicle authentication status of the vehicle based on the vehicle identification information on the basis of obtaining the vehicle authentication status of the vehicle by matching the first vehicle information and the second vehicle information. The vehicle authentication status can be understood as the final authentication status for the vehicle. In some embodiments of this application, both the vehicle authentication status and the vehicle authentication status can be understood as the authentication status of the mobile terminal for the vehicle, that is, they are the same concept. In some scenarios, for better distinction, the "vehicle authentication status" is used to describe the authentication status of the mobile terminal for the vehicle.

[0114] The information data types of the vehicle identification information include but are not limited to text type, image type, voice type (where the user inputs in a voice input manner), human-computer interaction instruction type (such as when the user inputs corresponding instruction operations), and so on.

[0115] In a feasible implementation manner: The mobile terminal can receive the vehicle identification operation input by the user for the target interface, and the mobile terminal can further determine the vehicle authentication status of the vehicle based on the type of the vehicle identification operation.

[0116] It can be understood that the mobile terminal displays the second vehicle information in the target interface for presenting to the user, and the user can input the vehicle identification operation based on the second vehicle information displayed in the target interface in combination with the vehicle information of the current vehicle in the actual environment.

[0117] The vehicle identification operation can be an "identification confirmation operation" in which the user determines that the second vehicle information matches the real information of the actual vehicle;

[0118] The vehicle identification operation can be an "identification error operation" in which the user determines that the second vehicle information does not match the real information of the actual vehicle. At this time, there may be a situation where the manufacturer misuses the information of other vehicles during the vehicle production stage.

[0119] That is: If the vehicle identification operation is an identification confirmation operation, the mobile terminal determines that the vehicle authentication status of the vehicle is the (vehicle authentication) passed status; if the vehicle identification operation is an identification error operation, the mobile terminal determines that the vehicle authentication status of the vehicle is the (vehicle authentication) failed status.

[0120] Optionally, the vehicle identification operation input by the user on the target interface of the mobile terminal can be implemented by selecting the icon of the corresponding function control through an external device mouse connected to the mobile terminal; it can be implemented by collecting the voice signal input by the user for device management through the voice collection device of the vehicle identification operation, such as voice input "The vehicle information does not match the actual vehicle", and it can also be the gesture control operation of collecting the specific gesture input by the user through the camera of the vehicle identification operation. By identifying the gesture control operation, a specific vehicle identification operation can be determined, and so on.

[0121] In a specific implementation scenario, the mobile terminal can have a touch screen. The touch screen can be a touch screen that can implement a single touch function, such as: a capacitive touch screen, an electromagnetic touch screen, or it can be a touch screen that can simultaneously implement capacitive induction, electromagnetic induction, and infrared induction. As Figure 4 shown, Figure 4 is a schematic diagram of a vehicle identification operation input scenario. The current display interface of the mobile terminal is the display screen of the "vehicle management interface" (i.e., the aforementioned target interface). The user can Figure 4 obtain the displayed second vehicle information on the target interface shown, such as model: Vehicle A, owner: Liming, license plate.... There is a "vehicle prompt information" pop-up control on the target interface. In a scenario, if the user believes that the actual vehicle information does not match the displayed second vehicle information, the user can input an identification error operation by touching the "error" control in a finger-touching manner. In this way, the mobile terminal can obtain the identification error operation to confirm that the vehicle authentication status of the vehicle is a failure status.

[0122] In this application, the mobile terminal can receive the vehicle identification operation input by the user for the target interface to improve the accuracy of vehicle authentication, and at the same time, it can prevent car dealers from misusing compliant or legal vehicle information and affecting the vehicle interaction experience.

[0123] In a specific implementation scenario, considering that it is difficult for users to accurately perceive the actual vehicle information, that is, the user's cognition of the vehicle cannot accurately achieve vehicle authentication. At this time, the mobile terminal can further determine the actual vehicle information of the vehicle based on the image of the actual vehicle or the input vehicle text by the user, that is, perform information recognition based on the vehicle identification image and / or vehicle identification text to determine the third vehicle information, and then determine whether the third vehicle information matches the first vehicle information to determine the vehicle authentication status of the vehicle.

[0124] The third vehicle information is the actual vehicle information determined by recognition based on the vehicle identification image and / or vehicle identification text input by the user.

[0125] Specifically, the mobile terminal can receive the vehicle recognition image and / or vehicle recognition text input by the user for the target interface, determine the third vehicle information corresponding to the vehicle recognition image and / or vehicle recognition text, and then determine the vehicle authentication status of the vehicle based on the third vehicle information and the first vehicle information.

[0126] It can be understood that the mobile terminal displays the second vehicle information in the target interface and at the same time provides an operation control for the user to input vehicle recognition information (such as the image of the actual vehicle or the vehicle text input by the user). The user can take a picture of the actual vehicle, that is, the vehicle recognition image, with the mobile terminal. The mobile terminal uses image recognition technology to recognize the vehicle recognition image to determine the third vehicle information corresponding to the vehicle recognition image; or, the user can input vehicle recognition text such as vehicle identification, vehicle model, vehicle license plate, etc. on the target interface to determine the third vehicle information corresponding to the vehicle recognition image. Then, the third vehicle information and the first vehicle information are matched to determine the vehicle authentication status of the vehicle. Further, if the third vehicle information matches the first vehicle information, it is determined that the vehicle authentication status of the vehicle is a passed status; if the third vehicle information does not match the first vehicle information, it is determined that the vehicle authentication status of the vehicle is a failed status.

[0127] Further, the mobile terminal can output information for prompting the user to take a picture of the image at a specified position of the actual vehicle, or the mobile terminal can output information for prompting the vehicle identification at a specified position of the actual vehicle, such as the engine number, license plate, etc. In this way, the user can perform corresponding image taking operations or text output operations based on the prompt information output by the mobile terminal.

[0128] Among them, the process of matching the third vehicle information and the first vehicle information can refer to "matching the second vehicle information and the first vehicle information" in step S203. The two only have different information matching objects, and the information matching process is similar, so it will not be elaborated here.

[0129] In an embodiment of the present application, the mobile terminal can obtain the first vehicle information and signature information of the vehicle, the signature information is generated based on the second vehicle information and the private key of the vehicle, and then obtain the public key for the vehicle from the service platform based on the first vehicle information; then based on the public key, the signature information and the first vehicle information, the vehicle authentication status of the vehicle is determined, and the entire vehicle management process does not rely on the dedicated chip on the vehicle side for vehicle safety management, which optimizes the vehicle management process, can realize the detection of vehicle information misuse, and improve the security of vehicle management services on the mobile terminal side (such as screen projection display services); and, can realize the detection of scenarios in which vehicle information of legal or compliant vehicles is misused during the factory stage or use stage of the vehicle; and can perform vehicle authentication based on the vehicle identification information entered by the user in the target interface to improve the accuracy of vehicle authentication in vehicle management.

[0130] See also Figure 5 , Figure 5 This is a flow chart of another embodiment of a vehicle management method proposed in this application. Specifically:

[0131] S301: Acquire first vehicle information and signature information of the vehicle sent by the vehicle terminal;

[0132] For details, please refer to other embodiments of the present application, which will not be described again here.

[0133] S302: using the public key to decrypt the signature information to obtain second vehicle information, matching the second vehicle information with the first vehicle information, and determining a vehicle authentication status of the vehicle;

[0134] For details, please refer to other embodiments of the present application, which will not be described again here.

[0135] S303: Enable the screen projection mode based on the vehicle authentication status, and send the display interface to the vehicle terminal for screen projection display.

[0136] The mobile terminal that is the executive subject of the present application may be a transmitter of projection data, which may be understood as being used to send projection content, such as a display interface, to the vehicle terminal corresponding to the projection display device-the vehicle for display. A communication connection is established between the mobile terminal and the projection display device. When a communication connection is established between the mobile terminal and the vehicle terminal, the mobile terminal may send the projection content to the vehicle terminal based on the vehicle authentication status, and the vehicle terminal displays the projection content, such as the display interface.

[0137] In some embodiments, if the vehicle authentication status of the vehicle is a passed status, the mobile terminal can turn on the screen mirroring mode after establishing a communication connection with the vehicle, and send the display interface to the vehicle for screen mirroring display; if the vehicle authentication status of the vehicle is a failed status, the mobile terminal outputs a vehicle prompt message for vehicle authentication failure to inform the user that the vehicle authentication of the current vehicle has not passed; further, the mobile terminal can not turn on the screen mirroring mode in the case of vehicle authentication failure, or, the mobile terminal can output a vehicle prompt message for vehicle authentication failure in the case of vehicle authentication failure, and turn on the screen mirroring mode based on the user's selection instruction (such as selecting to continue screen mirroring); in this way, the user can accurately obtain the vehicle authentication status of the current vehicle to confirm whether to continue screen mirroring, avoiding poor vehicle management service effects caused by directly performing screen mirroring on a vehicle with failed vehicle authentication, such as poor screen mirroring experience, and facilitating accurate prompting of relevant vehicle authentication status to the user.

[0138] S304: Obtain interface operation information from the in-vehicle terminal, and update the authentication status of the vehicle based on the operation response feature.

[0139] The interface operation information is used to characterize the operation information of the user on the screen mirroring interface of the in-vehicle terminal, and the type of the operation information can be operation position feature, operation frequency feature, operation response feature, etc.

[0140] Specifically, based on the vehicle operation information, the human-computer interaction operation input by the user on the screen mirroring interface of the vehicle can be accurately obtained. In this way, as the screen mirroring data source end of the vehicle screen mirroring scenario, the vehicle can quickly respond to the human-computer interaction operation input by the user on the in-vehicle terminal, generate screen mirroring data corresponding to the responded human-computer interaction operation, and send the screen mirroring data to the vehicle for display.

[0141] The operation response feature is used to characterize the response status information of the vehicle in response to the user operation, which can be an interface rendering parameter (such as the speed and time of rendering the screen mirroring data) for feedback on the vehicle loading screen mirroring data status, or an operation perception parameter (such as the speed and time of recognizing the operation) for feedback on perceiving the user operation input.

[0142] In practical applications, there are differences in the operation response characteristics between the vehicle using the vehicle information fraudulently and the legal / compliant vehicle corresponding to the vehicle information. Based on this, in the vehicle screen projection scenario, the operation response characteristics can be obtained to identify whether the vehicle is the vehicle type indicated by the first vehicle information. In actual implementation, the operation response characteristics of the vehicles corresponding to each vehicle information can be collected to set the reference operation response characteristics. In the actual vehicle management process, the operation response characteristics of the current vehicle can be obtained in the vehicle screen projection scenario, and the operation response characteristics of the current vehicle are matched with the reference response characteristics of the vehicle indicated by the first vehicle information of the vehicle (i.e., the reference response characteristics of the reference vehicle are determined), and the vehicle authentication status is updated based on the feature matching result. That is to say, the mobile terminal can update the authentication status of the vehicle based on the operation response characteristics.

[0143] Specifically, the mobile terminal obtains the interface operation information from the in-vehicle terminal, extracts the operation response characteristics (such as interface rendering parameters, operation perception parameters, etc.) in the interface operation information, and then matches the operation response characteristics with the reference response characteristics, and updates the vehicle authentication status based on the matching result. Further, the reference response characteristics can be determined based on the reference vehicle corresponding to the first vehicle information.

[0144] Optionally, the operation response characteristics are matched with the reference response characteristics, the feature similarity between the operation response characteristics and the reference response characteristics is calculated, and the vehicle authentication status is updated based on the feature similarity. For example, a similarity threshold can be set. If the feature similarity is greater than or equal to the similarity threshold, the vehicle authentication status of the vehicle can be updated to the vehicle authentication passed status; if the feature similarity is less than the similarity threshold, the vehicle authentication status of the vehicle can be updated to the failure status.

[0145] It can be understood that through multiple authentication matches, from the authentication matching process based on the first vehicle information before screen projection, the authentication matching process based on the input of the user on the target interface (vehicle identification operation, vehicle identification image, etc.), and the authentication matching process based on the operation response characteristics of the vehicle, the three can be combined arbitrarily to perform vehicle authentication involved in vehicle management by multiple means and measures, effectively improving the success rate of detecting vehicle information fraud, avoiding missed inspections, optimizing vehicle management, and avoiding vehicle information fraud.

[0146] S305: Detect the device distance from the in-vehicle terminal. If the device distance is greater than the distance threshold, turn off the screen projection mode.

[0147] The device distance can be understood as the device distance between the mobile terminal and the vehicle. In practical applications, the vehicle is equipped with an in-vehicle terminal, and what is actually detected is the device distance between the mobile terminal and the in-vehicle terminal corresponding to the vehicle;

[0148] The distance threshold is set for the device distance, which can be understood as the threshold value for the device distance. When the device distance is greater than the distance threshold, it can be considered that the mobile terminal held by the user is far from the vehicle. At this time, the mobile terminal can automatically disconnect the screen mirroring mode, and the mobile terminal can display the interface normally at this time.

[0149] Furthermore, the determination of the distance threshold can be a value defined by the user or preset at the factory.

[0150] It can be understood that the determination of the device distance can be based on the position coordinates of the mobile terminal and the vehicle, and a device distance obtained by calculating the distance based on the two position coordinates. The determination of the device distance can be based on the signal strength detected by the mobile terminal for the vehicle, and the device distance between the two devices can be calculated by obtaining the signal strength of the peer device.

[0151] The signal strength refers to the received signal strength indication value, which is a physical quantity used to characterize the strength of the transmitted signal of the signal transmitter received by the receiver.

[0152] Based on the signal strength RSSI, the device distance d between the two devices can be calculated using the following formula:

[0153] d = 10 ∧ [(abs(RSSI) - A) / (10 * n)]

[0154] Among them, abs() represents the absolute value function, A is the reference signal strength value (the absolute value of the rssi value when measuring the device distance from the reference device by 1m, such as the mobile terminal is 1m away from the vehicle), and n is the environmental attenuation factor.

[0155] Optionally, after establishing the above distance measurement formula, it also includes correcting the model parameters (A, n) in the distance measurement formula.

[0156] In a feasible implementation manner, the correction of the model parameters (A, n) in the distance measurement formula can be to correct the model parameters using the error backpropagation algorithm according to the calculation loss corresponding to at least one set of sample data groups.

[0157] Specifically, the training result obtained by the distance measurement formula is compared with the labeled sample data result to obtain the calculation loss, and the calculation loss is used to indicate the error between the training result and the data result.

[0158] In practical applications, after measuring the signal strength RSSI of the peer device, the signal strength is input into the above distance measurement formula, and the device distance d can be output.

[0159] In a feasible implementation, when the mobile terminal approaches and connects to the in-vehicle terminal corresponding to the vehicle, the display interface on the mobile terminal (such as the display interface of a certain application) will be automatically projected onto the in-vehicle terminal. After connection, the application program on the mobile terminal will be converted into a screen mirroring mode and projected onto the in-vehicle terminal. The specific projection method can be as follows: The mobile terminal detects the device distance from the vehicle. If the device distance is less than or equal to the distance threshold, the mobile terminal automatically establishes a communication connection with the in-vehicle terminal. The mobile terminal sends the interface data of the display interface (such as the display interface of a certain application) to the in-vehicle terminal for screen mirroring. It can be understood that the interface data is loaded on the in-vehicle terminal for display. During this process, the user can directly operate on the in-vehicle terminal corresponding to the vehicle. The in-vehicle terminal can collect the interface operation data during the user's operation. The in-vehicle terminal sends the interface operation data to the mobile terminal. At this time, the interface operation data of the in-vehicle terminal can be received to implement the operation response to the interface operation data. Similarly, when the mobile terminal is far away from the in-vehicle terminal and usually automatically disconnects, the mobile terminal will stop screen mirroring to the in-vehicle terminal and switch the application program that was previously screen mirrored to the running mode, and continue to run the application program on the mobile phone.

[0160] In an embodiment of the present application, the mobile terminal can obtain the first vehicle information and the signature information of the vehicle. The signature information is generated based on the second vehicle information and the private key of the vehicle. Then, based on the first vehicle information, the mobile terminal obtains the public key for the vehicle from the service platform; and then, based on the public key, the signature information, and the first vehicle information, the vehicle authentication status of the vehicle is determined. The entire vehicle management process does not rely on a dedicated chip on the vehicle side for vehicle security management, optimizing the vehicle management process, enabling the detection of vehicle information fraud, and enhancing the security of vehicle management services (such as screen mirroring display services) on the mobile terminal side; and, it can detect the scenario of fraudulently using the vehicle information of a legitimate or compliant vehicle during the factory stage or usage stage of the vehicle; and it can perform vehicle authentication based on the vehicle identification information input by the user on the target interface to improve the accuracy of vehicle authentication in vehicle management; and, it can perform vehicle authentication involved in vehicle management through multiple means and measures, effectively improving the success rate of detecting vehicle information fraud, avoiding missed detections, optimizing vehicle management, and avoiding vehicle information fraud.

[0161] In one embodiment, as Figure 6a shown, a vehicle management method is specifically proposed. This method can be implemented depending on a computer program and can run on a vehicle management device based on the von Neumann architecture. The computer program can be integrated in an application or run as an independent tool application. The vehicle management device can be an in-vehicle terminal.

[0162] Specifically, the vehicle management method includes:

[0163] S401: Obtain the first vehicle information and the signature information, where the signature information is generated based on the second vehicle information of the vehicle.

[0164] It can be understood that the in-vehicle terminal can be a part of the vehicle. The in-vehicle terminal usually stores the first vehicle information and the signature information for the vehicle. In some embodiments, the signature information is generated by the service platform after digital signature of the second vehicle information of the vehicle using a private key;

[0165] In a feasible implementation manner, the signature information of the vehicle can be obtained by requesting the service platform to perform digital signature based on the original vehicle information (i.e., the second vehicle information) on the vehicle side (such as the vehicle manufacturer, the vehicle itself) during vehicle factory production or vehicle use. Specifically, during the vehicle factory production stage, the second vehicle information can be sent to the service platform. The service platform uses the private key to perform digital signature on the second vehicle information to obtain the signature information, and then the service platform sends the signature information to the corresponding in-vehicle terminal on the vehicle side and stores it in the in-vehicle terminal.

[0166] In a feasible implementation manner, during vehicle factory production or vehicle use, the in-vehicle terminal can request the private key for digital signature from the service platform, and the in-vehicle terminal performs digital signature on the original vehicle information (i.e., the second vehicle information) based on the private key to obtain the signature information and save it.

[0167] It can be understood that the first vehicle information is the vehicle information for the vehicle stored in the in-vehicle terminal. In the actual application process, the first vehicle information can be written into the in-vehicle terminal by the vehicle manufacturer, service provider, dealer, etc.; before the vehicle interconnection service based on the mobile terminal, the mobile terminal needs to perform vehicle authentication on the vehicle to maintain the in-vehicle interconnection ecosystem of the mobile terminal and ensure the user experience; it can be understood that during the actual application process of the vehicle (such as during sales, maintenance, etc.) by the manufacturer, service provider, dealer, etc., there may be situations where the vehicle has been modified, misused, pirated, etc., and at this time, it may impersonate the vehicle information of a legitimate vehicle. That is to say, there is a situation where the first vehicle information stored on the in-vehicle terminal impersonates the vehicle information of a legitimate vehicle, and the confidence level of the first vehicle information for the user of the mobile terminal is not high, and there may be a situation where the vehicle information of a legitimate vehicle is impersonated. Thus, in situations involving vehicle management on the mobile terminal side, such as when the vehicle interacts with the mobile terminal (such as screen mirroring interaction, data sharing), the interaction experience and vehicle management effect are reduced.

[0168] S402: Transmit the first vehicle information and the signature information to the mobile terminal. The first vehicle information and the signature information are used to instruct the mobile terminal to decrypt the signature information based on the public key obtained from the service platform to obtain the second vehicle information, so as to determine the vehicle authentication status of the vehicle based on the second vehicle information and the first vehicle information.

[0169] In some embodiments, the in-vehicle terminal may send the first vehicle information and the signature information to the mobile terminal. After receiving them, the mobile terminal obtains the public key for the vehicle from the service platform based on the first vehicle information. The mobile terminal uses the public key to decrypt the signature information to obtain the second vehicle information, and matches the second vehicle information and the first vehicle information to determine the vehicle authentication status of the vehicle.

[0170] In the embodiments of the present application, the in-vehicle terminal may send the first vehicle information and the signature information of the vehicle to the mobile terminal. The signature information is usually generated by the service platform based on the second vehicle information and the private key of the vehicle. Then the mobile terminal can obtain the public key for the vehicle from the service platform based on the first vehicle information; and then determine the vehicle authentication status of the vehicle based on the public key, the signature information, and the first vehicle information. The entire vehicle management process does not rely on a dedicated chip on the vehicle side for vehicle security management, optimizes the vehicle management process, can detect the misappropriation of vehicle information, and improves the security of vehicle management services (such as screen mirroring display services).

[0171] In one embodiment, as Figure 6b shown, a vehicle management method is proposed. This method can be implemented depending on a computer program and can run on a vehicle management device based on the von Neumann architecture. The computer program can be integrated into an application or run as an independent tool-type application. The vehicle management device can be a service platform.

[0172] S501: Sign the second vehicle information of the vehicle with the private key to obtain the signature information, and send the signature information to the in-vehicle terminal;

[0173] In some embodiments, during vehicle factory production or vehicle use, the service platform can obtain the second vehicle information of the vehicle, that is, the original vehicle information. The service platform then digitally signs the second vehicle information with the private key to obtain the signature information. The service platform then sends the signature information to the in-vehicle terminal and stores it on the in-vehicle terminal.

[0174] S502: Send the private key to the in-vehicle terminal. The private key is used to instruct the in-vehicle terminal to sign the second vehicle information to obtain the signature information.

[0175] It can be understood that during vehicle factory production or vehicle use, the user can control the in-vehicle terminal corresponding to the vehicle to request the private key for digital signature from the service platform; the service platform sends the private key to the in-vehicle terminal; the in-vehicle terminal digitally signs the original vehicle information (that is, the second vehicle information) based on the private key to obtain the signature information.

[0176] S502: Receive the first vehicle information sent by the mobile terminal and send the public key of the vehicle to the mobile terminal. The first vehicle information is sent after the mobile terminal obtains the first vehicle information and the signature information of the vehicle from the in-vehicle terminal. The public key is used for the vehicle to decrypt the signature information to obtain the second vehicle information, so as to determine the vehicle authentication status of the vehicle based on the second vehicle information and the first vehicle information.

[0177] In some embodiments, the in-vehicle terminal may send the first vehicle information and the signature information to the mobile terminal. After receiving them, the mobile terminal obtains the public key of the vehicle from the service platform based on the first vehicle information. At this time, the service platform can receive the first vehicle information sent by the mobile terminal and send the public key of the vehicle to the mobile terminal. The mobile terminal uses the public key to decrypt the signature information to obtain the second vehicle information, and matches the second vehicle information and the first vehicle information to determine the vehicle authentication status of the vehicle.

[0178] In the embodiments of the present application, the service platform can at least generate signature information based on the second vehicle information and the private key of the vehicle and send it to the in-vehicle terminal for storage. The in-vehicle terminal can send the first vehicle information and the signature information of the vehicle to the mobile terminal, and then the mobile terminal can obtain the public key of the vehicle from the service platform based on the first vehicle information. Then, based on the public key, the signature information, and the first vehicle information, the vehicle authentication status of the vehicle is determined. The entire vehicle management process does not rely on a dedicated chip on the vehicle side for vehicle security management, optimizes the vehicle management process, can detect the misappropriation of vehicle information, and improves the security of vehicle management services (such as screen mirroring display services).

[0179] Please refer to Figure 6c , which is a schematic diagram of the architecture of a vehicle management system provided by the embodiments of the present application. As Figure 6c shown, the vehicle management system 10 includes a mobile terminal 100, a vehicle 110, and a service platform 120.

[0180] The mobile terminal 100 may be an electronic device with communication functions, and such electronic devices include but are not limited to: wearable devices, handheld devices, personal computers, tablet computers, vehicle-mounted devices, smart phones, computing devices, or other processing devices connected to a wireless modem, etc. In different networks, the electronic device may be called by different names, such as: user equipment, access mobile terminal, user unit, user station, mobile station, mobile platform, remote station, remote mobile terminal, mobile device, user mobile terminal, mobile terminal, wireless communication device, user agent or user device, cellular phone, cordless phone, personal digital assistant (PDA), device in a 5G network or future evolved network, etc.

[0181] The service platform 120 may be a separate server device, such as: a rack-mounted, blade, tower, or cabinet-style server device, or a hardware device with strong computing capabilities such as a workstation or a mainframe computer; it may also be a server cluster composed of multiple servers. The servers in the service cluster may be composed symmetrically, where each server is equivalent in function and status in the service link, and each server can provide services independently. The independent provision of services can be understood as not requiring the assistance of another server.

[0182] The vehicle 110 can be used in cooperation with the in-vehicle terminal. For example, the in-vehicle terminal can be installed on the vehicle 110. In some implementation scenarios, the in-vehicle terminal can be a part of the vehicle 110. The in-vehicle terminal usually stores the first vehicle information and signature information of the vehicle 110. In some embodiments, the signature information is generated by the service platform based on the second vehicle information and private key of the vehicle.

[0183] According to some embodiments, the mobile terminal 100 and the in-vehicle terminal corresponding to the vehicle 110 can establish a communication connection, and data interaction is completed during the data transfer process based on this communication connection. The communication connection includes but is not limited to Bluetooth connection, infrared connection, near-field communication connection, etc.

[0184] The mobile terminal 100, the in-vehicle terminal corresponding to the vehicle 110, and the service platform 120 can interact and communicate with each other through a network. For example, a vehicle management connection is established based on the network. The network can be a wireless network or a wired network. The wireless network includes but is not limited to a cellular network, a wireless local area network, an infrared network, or a Bluetooth network. The wired network includes but is not limited to Ethernet, universal serial bus (USB), or controller area network.

[0185] In addition, the vehicle management system embodiments provided in the above embodiments and the vehicle management method in some embodiments belong to the same concept. For the specific implementation process, please refer to the method embodiments, which will not be elaborated here.

[0186] Next, in conjunction with Figure 7 , the vehicle management device provided in the embodiments of the present application will be introduced in detail. It should be noted that Figure 7 The vehicle management device shown is used to execute the method of the embodiments of the present application Figure 1 ~ the method of the embodiments shown in FIG. 6. For the sake of convenience of description, only the parts related to the embodiments of the present application are shown. For the specific technical details not disclosed, please refer to the embodiments of the present application Figure 1 ~ the embodiments shown in FIG. 6.

[0187] Please refer to Figure 7 , which shows a schematic structural diagram of the vehicle management device of the embodiments of the present application. The vehicle management device 1 can be implemented as all or part of the user mobile terminal through software, hardware, or a combination of both. According to some embodiments, the vehicle management device 1 includes an information acquisition module 11, a public key acquisition module 12, and a status determination module 13, and is specifically used for:

[0188] The information acquisition module 11 is used to acquire the first vehicle information and signature information of the vehicle sent by the in-vehicle terminal;

[0189] The public key acquisition module 12 is used to obtain the public key for the vehicle from the service platform based on the first vehicle information;

[0190] The status determination module 13 is used to decrypt the signature information with the public key to obtain the second vehicle information; match the second vehicle information and the first vehicle information to determine the vehicle authentication status of the vehicle.

[0191] Optionally, as Figure 8 shown, the status determination module 13 includes:

[0192] The information decryption unit 131 is used to decrypt the signature information with the public key to obtain the second vehicle information.

[0193] The information matching unit 132 is used to match the second vehicle information and the first vehicle information to obtain an information matching result;

[0194] If the information matching result is a match, it is determined that the vehicle is in a vehicle authentication passed state;

[0195] If the information matching result is a mismatch, it is determined that the vehicle is in a vehicle authentication failed state.

[0196] Optionally, the device 1 is specifically configured to:

[0197] Perform information matching on the second vehicle information and the first vehicle information to obtain an information matching result;

[0198] If the information matching result is a pass, display the first vehicle information in the target interface, receive the vehicle identification information input through the target interface, and determine the vehicle authentication status of the vehicle based on the vehicle identification information;

[0199] If the information matching result is a failure, determine that the vehicle authentication status of the vehicle is a failure status.

[0200] Optionally, the device 1 is specifically configured to:

[0201] Receive a vehicle identification operation input for the target interface. If the vehicle identification operation is an identification confirmation operation, determine that the vehicle authentication status of the vehicle is a passed status; if the vehicle identification operation is an identification error operation, determine that the vehicle authentication status of the vehicle is a failure status; and / or,

[0202] Receive a vehicle identification image and / or vehicle identification text input for the target interface, determine third vehicle information corresponding to the vehicle identification image and / or the vehicle identification text, perform information matching based on the third vehicle information and the first vehicle information, and determine the vehicle authentication status of the vehicle. Optionally, as Figure 9a shown, the device 1 further includes:

[0203] A screen mirroring control module 14, configured to turn on a screen mirroring mode based on the vehicle authentication status and send a display interface to the vehicle head unit for screen mirroring display;

[0204] Obtain interface operation information from the vehicle head unit and update the vehicle status based on the interface operation information.

[0205] Optionally, the device 1 is specifically configured to:

[0206] Obtain interface operation information from the vehicle, and extract operation response features from the interface operation information;

[0207] Update the vehicle authentication status of the vehicle based on the operation response features.

[0208] Optionally, the device 1 is specifically configured to:

[0209] Match the operation response features with reference response features, and update the vehicle authentication status of the vehicle based on the matching result. The reference response features are determined based on a reference vehicle corresponding to the first vehicle information.

[0210] Optionally, the device 1 is specifically configured to:

[0211] Detect the distance from the device of the vehicle. If the device distance is greater than the distance threshold, turn off the screen mirroring mode.

[0212] It should be noted that when the vehicle management device provided in the above embodiments executes the vehicle management method, only the division of the above functional modules is used for illustration. In practical applications, the above functions can be allocated to different functional modules as needed, that is, the internal structure of the device is divided into different functional modules to complete all or part of the functions described above. In addition, the vehicle management device provided in the above embodiments and the vehicle management method embodiments belong to the same concept. The implementation process is detailed in the method embodiments and will not be elaborated here.

[0213] The serial numbers of the embodiments of the present application above are only for description and do not represent the superiority or inferiority of the embodiments.

[0214] Please refer to Figure 9b , which shows a schematic structural diagram of another vehicle management device according to an embodiment of the present application. The vehicle management device 2 can be implemented as all or part of a user mobile terminal through software, hardware, or a combination of both. According to some embodiments, the vehicle management device 2 includes an information acquisition module 21 and an information transmission module 22, and is specifically configured to:

[0215] The information acquisition module 21 is configured to acquire first vehicle information and signature information, and the signature information is generated based on second vehicle information of the vehicle;

[0216] The information transmission module 22 is configured to transmit the first vehicle information and the signature information to the mobile terminal. The first vehicle information and the signature information are used to instruct the mobile terminal to decrypt the signature information based on the public key obtained from the service platform to obtain second vehicle information, so as to determine the vehicle authentication status of the vehicle based on the second vehicle information and the first vehicle information.

[0217] It should be noted that when the vehicle management device provided in the above embodiments executes the vehicle management method, only the division of the above functional modules is used for illustration. In practical applications, the above functions can be allocated to different functional modules as needed, that is, the internal structure of the device is divided into different functional modules to complete all or part of the functions described above. In addition, the vehicle management device provided in the above embodiments and the vehicle management method embodiments belong to the same concept. The implementation process is detailed in the method embodiments and will not be elaborated here.

[0218] The serial numbers of the embodiments of the present application above are only for description and do not represent the superiority or inferiority of the embodiments.

[0219] Please refer toFigure 9c , which shows a schematic structural diagram of another vehicle management device according to an embodiment of the present application. The vehicle management device 3 can be implemented as all or part of a user mobile terminal through software, hardware, or a combination of both. According to some embodiments, the vehicle management device 3 includes an information processing module 31 and a public key sending module 32, and specifically is used for:

[0220] The information processing module 31 is used for signing the second vehicle information of the vehicle with a private key to obtain signature information, and sending the signature information to the vehicle; or, sending the private key to the vehicle, and the private key is used to instruct the vehicle to sign the second vehicle information to obtain signature information;

[0221] The public key sending module 32 is used for receiving the first vehicle information sent by the mobile terminal and sending the public key of the vehicle to the mobile terminal. The first vehicle information is sent after the mobile terminal obtains the first vehicle information and signature information of the vehicle from the vehicle terminal. The public key is used for the vehicle to decrypt the signature information to obtain the second vehicle information, so as to determine the vehicle authentication status based on the second vehicle information and the first vehicle information.

[0222] It should be noted that when the vehicle management device provided in the above embodiment executes the vehicle management method, only the above-mentioned division of each functional module is used for illustration. In actual application, the above functions can be allocated to different functional modules according to needs, that is, the internal structure of the device is divided into different functional modules to complete all or part of the functions described above. In addition, the vehicle management device provided in the above embodiment and the vehicle management method embodiment belong to the same concept, and the implementation process is shown in the method embodiment, which will not be elaborated here.

[0223] The serial numbers of the above embodiments of the present application are only for description and do not represent the advantages or disadvantages of the embodiments.

[0224] An embodiment of the present application further provides a computer storage medium, and the computer storage medium can store multiple instructions, and the instructions are suitable for being loaded and executed by a processor as the Figures 1 to 6c vehicle management method shown in the above Figures 1 to 6c embodiment. The specific execution process can refer to the specific description of the

[0225] embodiment shown above, and will not be elaborated here. Figures 1 to 6c The present application also provides a computer program product, and the computer program product stores at least one instruction, and the at least one instruction is loaded and executed by the processor as the Figures 1 to 6c vehicle management method shown in the above

[0226] Please refer to Figure 10 , which shows a block diagram of the structure of an electronic device provided by an exemplary embodiment of the present application. The electronic device in the present application may include one or more of the following components: a processor 110, a memory 120, an input device 130, an output device 140, and a bus 150. The processor 110, the memory 120, the input device 130, and the output device 140 may be connected through the bus 150.

[0227] The processor 110 may include one or more processing cores. The processor 110 uses various interfaces and lines to connect various parts within the entire electronic device, and by running or executing instructions, programs, code sets, or instruction sets stored in the memory 120, as well as calling data stored in the memory 120, it executes various functions of the electronic device 100 and processes data. Optionally, the processor 110 may be implemented in at least one hardware form of digital signal processing (DSP), field-programmable gate array (FPGA), or programmable logic array (PLA). The processor 110 may integrate one or several combinations of a central processing unit (CPU), a graphics processing unit (GPU), and a modem, etc. Among them, the CPU mainly processes the operating system, user interface, application programs, etc.; the GPU is responsible for rendering and drawing the display content; the modem is used to process wireless communication. It can be understood that the above modem may not be integrated into the processor 110 and may be implemented separately through a communication chip.

[0228] The memory 120 may include a random access memory (RAM) or a read-only memory (ROM). Optionally, the memory 120 includes a non-transitory computer-readable storage medium. The memory 120 may be used to store instructions, programs, codes, code sets or instruction sets. The memory 120 may include a program storage area and a data storage area, wherein the program storage area may store instructions for implementing an operating system, instructions for implementing at least one function (such as a touch function, a sound playback function, an image playback function, etc.), instructions for implementing the following various method embodiments, etc. The operating system may be an Android system, including a system deeply developed based on the Android system, an IOS system developed by Apple, including a system deeply developed based on the IOS system or other systems. The data storage area may also store data created by the electronic device during use, such as a phone book, audio and video data, chat record data, etc.

[0229] See also Figure 11 As shown, the memory 120 can be divided into an operating system space and a user space. The operating system runs in the operating system space, and native and third-party applications run in the user space. In order to ensure that different third-party applications can achieve good operating results, the operating system allocates corresponding system resources to different third-party applications. However, different application scenarios in the same third-party application also have different requirements for system resources. For example, in the local resource loading scenario, the third-party application has higher requirements for disk reading speed; in the animation rendering scenario, the third-party application has higher requirements for GPU performance. The operating system and third-party applications are independent of each other, and the operating system often cannot perceive the current application scenario of the third-party application in a timely manner, resulting in the operating system being unable to perform targeted system resource adaptation according to the specific application scenario of the third-party application.

[0230] In order for the operating system to distinguish the specific application scenarios of third-party applications, it is necessary to open up data communication between third-party applications and the operating system so that the operating system can obtain the current scenario information of third-party applications at any time, and then perform targeted system resource adaptation based on the current scenario.

[0231] Taking the Android operating system as an example, the programs and data stored in the memory 120 are as follows: Figure 12As shown, the memory 120 may store a Linux kernel layer 320, a system runtime library layer 340, an application framework layer 360 and an application layer 380, wherein the Linux kernel layer 320, the system runtime library layer 340 and the application framework layer 360 belong to the operating system space, and the application layer 380 belongs to the user space. The Linux kernel layer 320 provides underlying drivers for various hardware of electronic devices, such as display drivers, audio drivers, camera drivers, Bluetooth drivers, Wi-Fi drivers, power management, etc. The system runtime library layer 340 provides the main feature support for the Android system through some C / C++ libraries. For example, the SQLite library provides database support, the OpenGL / ES library provides 3D drawing support, and the Webkit library provides browser kernel support, etc. The Android runtime library (Android runtime) is also provided in the system runtime library layer 340, which mainly provides some core libraries that allow developers to use the Java language to write Android applications. The application framework layer 360 provides various APIs that may be used when building applications. Developers can also use these APIs to build their own applications, such as activity management, window management, view management, notification management, content provider, package management, call management, resource management, and location management. At least one application runs in the application layer 380. These applications can be native applications that come with the operating system, such as contact applications, text messaging applications, clock applications, camera applications, etc.; they can also be third-party applications developed by third-party developers, such as game applications, instant messaging applications, photo beautification applications, etc.

[0232] Taking the operating system as an IOS system as an example, the programs and data stored in the memory 120 are as follows: Figure 13As shown in the figure, the IOS system includes: Core OS layer 420, Core Services layer 440, Media layer 460, and Cocoa Touch Layer 480. The Core OS layer 420 includes the operating system kernel, drivers, and underlying program frameworks, which provide functions closer to the hardware for the program frameworks located in the Core Services layer 440 to use. The Core Services layer 440 provides the system services and / or program frameworks required by applications, such as the Foundation framework, Account framework, Advertising framework, Data Storage framework, Network Connection framework, Location framework, Motion framework, and so on. The Media layer 460 provides interfaces related to audio-visual aspects for applications, such as interfaces related to graphics and images, audio technology-related interfaces, video technology-related interfaces, and the wireless playback (AirPlay) interface for audio and video transmission technology. The Cocoa Touch Layer 480 provides various commonly used interface-related frameworks for application development and is responsible for the touch interaction operations of users on electronic devices. For example, Local Notification Service, Remote Push Service, Advertising framework, Game Tools framework, Message User Interface (UI) framework, User Interface UIKit framework, Map framework, and so on.

[0233] In Figure 13 Among the frameworks shown, the frameworks related to most applications include but are not limited to: the Foundation framework in the Core Services layer 440 and the UIKit framework in the Cocoa Touch Layer 480. The Foundation framework provides many basic object classes and data types, provides the most basic system services for all applications, and is independent of the UI. The classes provided by the UIKit framework are the basic UI class libraries, used to create touch-based user interfaces. iOS applications can provide the UI based on the UIKit framework, so it provides the infrastructure for applications to build user interfaces, draw, process, and handle user interaction events, respond to gestures, and so on.

[0234] Among them, the methods and principles for implementing data communication between third-party applications and the operating system in the IOS system can refer to the Android system, and will not be elaborated in this application.

[0235] Among them, the input device 130 is used to receive input instructions or data. The input device 130 includes, but is not limited to, a keyboard, a mouse, a camera, a microphone, or a touch device. The output device 140 is used to output instructions or data. The output device 140 includes, but is not limited to, a display device, a speaker, etc. In one example, the input device 130 and the output device 140 can be combined. The input device 130 and the output device 140 are a touch display screen, which is used to receive touch operations of a user using any suitable object such as a finger or a stylus on or near it, and to display the user interfaces of various application programs. The touch display screen is usually arranged on the front panel of the electronic device. The touch display screen can be designed as a full-screen, a curved screen, or a special-shaped screen. The touch display screen can also be designed as a combination of a full-screen and a curved screen, or a combination of a special-shaped screen and a curved screen. The embodiments of the present application do not limit this.

[0236] In addition, those skilled in the art can understand that the structure of the electronic device shown in the above drawings does not constitute a limitation on the electronic device. The electronic device may include more or fewer components than shown in the drawings, or combine some components, or have different component arrangements. For example, the electronic device also includes components such as a radio frequency circuit, an input unit, a sensor, an audio circuit, a wireless fidelity (WiFi) module, a power supply, and a Bluetooth module, which will not be elaborated here.

[0237] In the embodiments of the present application, the execution subject of each step can be the electronic device introduced above. Optionally, the execution subject of each step is the operating system of the electronic device. The operating system can be the Android system, the IOS system, or other operating systems. The embodiments of the present application do not limit this.

[0238] In the electronic device according to the embodiment of the present application, a display device may also be installed thereon. The display device may be various devices capable of implementing a display function, such as a cathode ray tube display (CR for short), a light-emitting diode display (LED for short), an electronic ink screen, a liquid crystal display (LCD for short), a plasma display panel (PDP for short), etc. The user can use the display device on the electronic device 101 to view information such as text, images, and videos displayed. The electronic device may be a smart phone, a tablet computer, a gaming device, an AR (Augmented Reality) device, an automobile, a data storage device, an audio playback device, a video playback device, a notebook, a desktop computing device, a wearable device such as an electronic watch, electronic glasses, an electronic helmet, an electronic bracelet, an electronic necklace, an electronic clothing, etc.

[0239] In Figure 10 In the electronic device shown, the electronic device may be a mobile terminal. The processor 110 may be used to call an application program stored in the memory 120 and specifically perform the following operations:

[0240] Obtain the first vehicle information and the signature information of the vehicle sent by the vehicle-mounted terminal;

[0241] Based on the first vehicle information, obtain the public key for the vehicle from the service platform;

[0242] Use the public key to decrypt the signature information to obtain the second vehicle information;

[0243] Match the second vehicle information and the first vehicle information to determine the vehicle authentication status of the vehicle.

[0244] In one embodiment, when the processor 110 performs the operation of matching the second vehicle information and the first vehicle information to determine the vehicle authentication status of the vehicle, it includes:

[0245] Match the second vehicle information and the first vehicle information to obtain an information matching result;

[0246] If the information matching result is a match, determine that the vehicle authentication status of the vehicle is a passed status;

[0247] If the information matching result is a mismatch, determine that the vehicle authentication status of the vehicle is a failed status.

[0248] In one embodiment, when the processor 110 performs the information matching of the second vehicle information and the first vehicle information to determine the vehicle authentication status of the vehicle, it includes:

[0249] Perform information matching on the second vehicle information and the first vehicle information to obtain an information matching result;

[0250] If the information matching result is a pass, display the first vehicle information in the target interface, receive the vehicle identification information input in the target interface, and determine the vehicle authentication status of the vehicle based on the vehicle identification information;

[0251] If the information matching result is a failure, determine that the vehicle authentication status of the vehicle is a failure status.

[0252] In one embodiment, when the processor 110 performs the receiving of the vehicle identification information input for the target interface and determines the vehicle authentication status of the vehicle based on the vehicle identification information, it includes:

[0253] Receive the vehicle identification operation input for the target interface. If the vehicle identification operation is an identification confirmation operation, determine that the vehicle authentication status of the vehicle is a passed status; if the vehicle identification operation is an identification error operation, determine that the vehicle authentication status of the vehicle is a failure status; and / or,

[0254] Receive the vehicle identification image and / or vehicle identification text input for the target interface, determine the third vehicle information corresponding to the vehicle identification image and / or the vehicle identification text, and perform information matching based on the third vehicle information and the first vehicle information to determine the vehicle authentication status of the vehicle.

[0255] In one embodiment, when the processor 110 performs the method, it specifically performs the following steps:

[0256] Based on the vehicle authentication status, turn on the screen mirroring mode and send the display interface to the in-vehicle terminal for screen mirroring display;

[0257] Obtain the interface operation information from the in-vehicle terminal and update the vehicle status based on the interface operation information.

[0258] In one embodiment, when the processor 110 performs the obtaining of the interface operation information from the vehicle and updating the vehicle status based on the interface operation information, it includes:

[0259] Obtain the interface operation information from the vehicle and extract the operation response characteristics in the interface operation information;

[0260] Update the vehicle authentication status of the vehicle based on the operation response feature.

[0261] In one embodiment, when the processor 110 executes the update of the vehicle authentication status of the vehicle based on the operation response feature, it includes:

[0262] Match the operation response feature with a reference response feature, and update the vehicle authentication status of the vehicle based on the matching result. The reference response feature is determined based on a reference vehicle corresponding to the first vehicle information.

[0263] In one embodiment, when the processor 110 executes the vehicle management method, it specifically performs the following operations:

[0264] Detect the device distance from the vehicle. If the device distance is greater than the distance threshold, turn off the screen mirroring mode.

[0265] Please refer to Figure 14 , which provides a schematic structural diagram of another electronic device according to an embodiment of the present application. As Figure 14 shown, the electronic device 1000 may include: at least one processor 1001, at least one network interface 1004, a user interface 1003, a memory 1005, and at least one communication bus 1002.

[0266] Among them, the communication bus 1002 is used to realize the connection and communication between these components.

[0267] Among them, the user interface 1003 may include a display screen (Display) and a camera (Camera). Optionally, the user interface 1003 may further include a standard wired interface and a wireless interface.

[0268] Among them, the network interface 1004 may optionally include a standard wired interface and a wireless interface (such as a WI-FI interface).

[0269] Among them, the processor 1001 may include one or more processing cores. The processor 1001 connects various parts within the entire server 1000 through various interfaces and lines. By running or executing instructions, programs, code sets, or instruction sets stored in the memory 1005, and by invoking the data stored in the memory 1005, it executes various functions of the server 1000 and processes data. Optionally, the processor 1001 may be implemented in at least one hardware form of digital signal processing (DSP), field-programmable gate array (FPGA), or programmable logic array (PLA). The processor 1001 may integrate a combination of one or several of a central processing unit (CPU), a graphics processing unit (GPU), and a modem, etc. Among them, the CPU mainly processes the operating system, user interface, application programs, etc.; the GPU is responsible for rendering and drawing the content to be displayed on the display screen; the modem is used to process wireless communication. It can be understood that the above-mentioned modem may not be integrated into the processor 1001 and may be implemented separately through a single chip.

[0270] Among them, the memory 1005 may include random access memory (RAM) and may also include read-only memory. Optionally, the memory 1005 includes a non-transitory computer-readable storage medium. The memory 1005 can be used to store instructions, programs, code, code sets, or instruction sets. The memory 1005 may include a program storage area and a data storage area. Among them, the program storage area can store instructions for implementing the operating system, instructions for at least one function (such as touch function, sound playback function, image playback function, etc.), instructions for implementing the above-mentioned various method embodiments, etc.; the data storage area can store the data involved in the above-mentioned various method embodiments. Optionally, the memory 1005 may also be at least one storage device located far from the aforementioned processor 1001. As Figure 14 shown, the memory 1005, as a computer storage medium, may include an operating system, a network communication module, a user interface module, and application programs.

[0271] In Figure 14In the electronic device 1000 shown, the electronic device 1000 can be a vehicle-mounted terminal. The user interface 1003 is mainly used to provide an input interface for the user and obtain the data input by the user. The processor 1001 can be used to call the application program stored in the memory 1005 and specifically perform the following operations:

[0272] Obtain the first vehicle information and the signature information, where the signature information is generated based on the second vehicle information of the vehicle;

[0273] Transmit the first vehicle information and the signature information to the mobile terminal. The first vehicle information and the signature information are used to instruct the mobile terminal to decrypt the signature information based on the public key obtained from the service platform to obtain the second vehicle information, so as to determine the vehicle authentication status of the vehicle based on the second vehicle information and the first vehicle information.

[0274] Please refer to Figure 15 which provides a schematic structural diagram of another electronic device according to an embodiment of the present application. As Figure 15 shown, the electronic device 2000 may include: at least one processor 2001, at least one network interface 2004, a user interface 2003, a memory 2005, and at least one communication bus 2002.

[0275] Among them, the communication bus 2002 is used to implement the connection and communication between these components.

[0276] Among them, the user interface 2003 may include a display screen (Display) and a camera (Camera). Optionally, the user interface 2003 may further include a standard wired interface and a wireless interface.

[0277] Among them, the network interface 2004 may optionally include a standard wired interface and a wireless interface (such as a WI-FI interface).

[0278] Among them, the processor 2001 may include one or more processing cores. The processor 2001 is connected to various parts within the entire server 2000 through various interfaces and circuits. By running or executing instructions, programs, code sets, or instruction sets stored in the memory 2005, and by invoking the data stored in the memory 2005, it executes various functions of the server 2000 and processes data. Optionally, the processor 2001 may be implemented in at least one hardware form of digital signal processing (DSP), field-programmable gate array (FPGA), or programmable logic array (PLA). The processor 2001 may integrate a combination of one or several of a central processing unit (CPU), a graphics processing unit (GPU), and a modem, etc. Among them, the CPU mainly processes the operating system, user interface, application programs, etc.; the GPU is responsible for rendering and drawing the content to be displayed on the display screen; the modem is used to process wireless communication. It can be understood that the above-mentioned modem may not be integrated into the processor 2001 and may be implemented separately by a single chip.

[0279] Among them, the memory 2005 may include random access memory (RAM) and may also include read-only memory. Optionally, the memory 2005 includes a non-transitory computer-readable storage medium. The memory 2005 can be used to store instructions, programs, code, code sets, or instruction sets. The memory 2005 may include a program storage area and a data storage area. Among them, the program storage area may store instructions for implementing the operating system, instructions for at least one function (such as touch function, sound playback function, image playback function, etc.), instructions for implementing the above-mentioned method embodiments, etc.; the data storage area may store the data involved in the above-mentioned method embodiments. Optionally, the memory 2005 may also be at least one storage device located far from the aforementioned processor 2001. As Figure 14 shown, the memory 2005, as a computer storage medium, may include an operating system, a network communication module, a user interface module, and application programs.

[0280] In Figure 15In the electronic device 2000 shown, the electronic device 2000 can be a service platform. The user interface 2003 is mainly used to provide an interface for the user to input data and obtain the data input by the user. The processor 2001 can be used to call the application program stored in the memory 2005 and specifically perform the following operations:

[0281] Sign the second vehicle information of the vehicle with the private key to obtain the signature information, and send the signature information to the in-vehicle terminal; or, send the private key to the in-vehicle terminal, and the private key is used to instruct the in-vehicle terminal to sign the second vehicle information to obtain the signature information;

[0282] Receive the first vehicle information sent by the mobile terminal and send the public key of the vehicle to the mobile terminal. The first vehicle information is sent after the mobile terminal obtains the first vehicle information and the signature information of the vehicle from the in-vehicle terminal. The public key is used for the vehicle to decrypt the signature information to obtain the second vehicle information, so as to determine the vehicle authentication status of the vehicle based on the second vehicle information and the first vehicle information.

[0283] Those of ordinary skill in the art can understand that all or part of the processes of implementing the methods in the above embodiments can be completed by instructing relevant hardware through a computer program. The program can be stored in a computer-readable storage medium. When the program is executed, it can include the processes of the embodiments of the above methods. Among them, the storage medium can be a magnetic disk, an optical disk, a read-only memory or a random access memory, etc.

[0284] The above-disclosed are only the preferred embodiments of the present application. Of course, the scope of the rights of the present application cannot be limited thereby. Therefore, equivalent changes made according to the claims of the present application still fall within the scope covered by the present application.

Claims

1. A vehicle management method, characterized in that, applied to a mobile terminal, the method includes: Obtain the first vehicle information and signature information of the vehicle sent by the in-vehicle terminal; Obtain the public key for the vehicle from the service platform based on the first vehicle information; Use the public key to decrypt the signature information to obtain the second vehicle information; Match the second vehicle information and the first vehicle information to determine the vehicle authentication status of the vehicle; Based on the vehicle authentication status, turn on the screen mirroring mode, detect the device distance from the vehicle. If the device distance is less than or equal to the distance threshold, automatically establish a communication connection with the in-vehicle terminal and send the display interface to the in-vehicle terminal for screen mirroring display; Obtain interface operation information from the in-vehicle terminal and update the vehicle status based on the interface operation information; If the device distance is greater than the distance threshold, turn off the screen mirroring mode; Wherein, the obtaining interface operation information from the vehicle and updating the vehicle status based on the interface operation information includes: Obtain interface operation information from the vehicle and extract the operation response characteristics in the interface operation information; Update the vehicle authentication status of the vehicle based on the operation response characteristics; Wherein, the updating the vehicle authentication status of the vehicle based on the operation response characteristics includes: Match the operation response characteristics with the reference response characteristics, and update the vehicle authentication status of the vehicle based on the matching result. The reference response characteristics are determined based on the reference vehicle corresponding to the first vehicle information.

2. The method according to claim 1, characterized in that, The matching the second vehicle information and the first vehicle information to determine the vehicle authentication status of the vehicle includes: Match the second vehicle information and the first vehicle information to obtain an information matching result; If the information matching result is a pass, determine that the vehicle authentication status of the vehicle is a passed status; If the information matching result is a failure, determine that the vehicle authentication status of the vehicle is a failed status.

3. The method according to claim 1, characterized in that, The matching the second vehicle information and the first vehicle information to determine the vehicle authentication status of the vehicle includes: Match the second vehicle information and the first vehicle information to obtain an information matching result; If the information matching result is a pass, display the first vehicle information in the target interface, receive the vehicle identification information input in the target interface, and determine the vehicle authentication status of the vehicle based on the vehicle identification information; If the information matching result is a failure, determine that the vehicle authentication status of the vehicle is a failed status.

4. The method according to claim 3, characterized in that, The receiving the vehicle identification information input for the target interface and determining the vehicle authentication status of the vehicle based on the vehicle identification information includes: Receive a vehicle identification operation input for the target interface. If the vehicle identification operation is an identification confirmation operation, determine that the vehicle authentication status of the vehicle is a passed status; if the vehicle identification operation is an identification error operation, determine that the vehicle authentication status of the vehicle is a failed status; and / or, Receive a vehicle identification image and / or vehicle identification text input for the target interface, determine third vehicle information corresponding to the vehicle identification image and / or the vehicle identification text, perform information matching based on the third vehicle information and the first vehicle information, and determine the vehicle authentication status of the vehicle.

5. A vehicle management method Characterized in that Applied to a vehicle-mounted terminal, the method includes: Obtain first vehicle information and signature information, where the signature information is generated based on second vehicle information of the vehicle; Transmit the first vehicle information and the signature information to a mobile terminal, where the first vehicle information and the signature information are used to instruct the mobile terminal to decrypt the signature information based on a public key obtained from a service platform to obtain second vehicle information, so as to determine the vehicle authentication status of the vehicle based on the second vehicle information and the first vehicle information; Receive and display a display interface sent by the mobile terminal; where the display interface is sent by the mobile terminal when the mobile terminal automatically establishes a communication connection with the vehicle-mounted terminal; before the mobile terminal automatically establishes a communication connection with the vehicle-mounted terminal, it further includes: the mobile terminal enables a screen mirroring mode based on the vehicle authentication status, and the mobile terminal detects and determines that the device distance between the mobile terminal and the vehicle is less than or equal to a distance threshold; Send interface operation information to the mobile terminal, so that the mobile terminal updates the vehicle status based on the interface operation information; Based on the mobile terminal detecting and determining that the device distance is greater than the distance threshold, the mobile terminal closes the screen mirroring mode; Wherein, the mobile terminal updates the vehicle status based on the interface operation information, including: Obtain interface operation information from the vehicle, and extract an operation response feature in the interface operation information; Update the vehicle authentication status of the vehicle based on the operation response feature; Wherein, the mobile terminal updates the vehicle authentication status of the vehicle based on the operation response feature, including: Match the operation response feature with a reference response feature, and update the vehicle authentication status of the vehicle based on the matching result, where the reference response feature is determined based on a reference vehicle corresponding to the first vehicle information.

6. A vehicle management method Characterized in that Applied to a service platform, the method includes: Sign the second vehicle information of the vehicle with a private key to obtain signature information, and send the signature information to the vehicle-mounted terminal; or, send the private key to the vehicle-mounted terminal, where the private key is used to instruct the vehicle-mounted terminal to sign the second vehicle information to obtain signature information; Receive the first vehicle information sent by the mobile terminal and send the public key for the vehicle to the mobile terminal. The first vehicle information is sent by the mobile terminal after obtaining the first vehicle information and signature information of the vehicle from the in-vehicle terminal. The public key is used for the vehicle to decrypt the signature information to obtain the second vehicle information, so as to determine the vehicle authentication status of the vehicle based on the second vehicle information and the first vehicle information; Wherein, the mobile terminal enables the screen mirroring mode based on the vehicle authentication status, detects the device distance between the mobile terminal and the vehicle, and if the device distance is less than or equal to the distance threshold, the mobile terminal automatically establishes a communication connection with the in-vehicle terminal, and sends the display interface to the in-vehicle terminal for screen mirroring display; obtains the interface operation information from the in-vehicle terminal based on the mobile terminal, and updates the vehicle status based on the interface operation information; if the device distance is greater than the distance threshold, the mobile terminal closes the screen mirroring mode; Wherein, the mobile terminal updates the vehicle status based on the interface operation information, including: Obtain the interface operation information from the vehicle, and extract the operation response feature in the interface operation information; Update the vehicle authentication status of the vehicle based on the operation response feature; Wherein, the mobile terminal updates the vehicle authentication status of the vehicle based on the operation response feature, including: Match the operation response feature with the reference response feature, and update the vehicle authentication status of the vehicle based on the matching result. The reference response feature is determined based on the reference vehicle corresponding to the first vehicle information.

7. A vehicle management device, Characterized in that, The device includes: An information acquisition module, configured to acquire the first vehicle information and signature information of the vehicle sent by the in-vehicle terminal; A public key acquisition module, configured to obtain the public key for the vehicle from the service platform based on the first vehicle information; A status determination module, configured to decrypt the signature information with the public key to obtain the second vehicle information; match the second vehicle information and the first vehicle information to determine the vehicle authentication status of the vehicle; A screen mirroring control module, configured to enable the screen mirroring mode based on the vehicle authentication status, detect the device distance from the vehicle, and if the device distance is less than or equal to the distance threshold, automatically establish a communication connection with the in-vehicle terminal, and send the display interface to the in-vehicle terminal for screen mirroring display; Obtain the interface operation information from the in-vehicle terminal, and update the vehicle status based on the interface operation information; If the device distance is greater than the distance threshold, close the screen mirroring mode; The vehicle management device is specifically configured to: Obtain the interface operation information from the vehicle, and extract the operation response feature in the interface operation information; Update the vehicle authentication status of the vehicle based on the operation response feature; The vehicle management device is specifically configured to: Match the operation response feature with the reference response feature, and update the vehicle authentication status of the vehicle based on the matching result. The reference response feature is determined based on a reference vehicle corresponding to the first vehicle information.

8. A vehicle management device Characterized in that The device includes: An information acquisition module, configured to acquire first vehicle information and signature information, where the signature information is generated based on second vehicle information of the vehicle; An information transmission module, configured to transmit the first vehicle information and the signature information to a mobile terminal. The first vehicle information and the signature information are used to instruct the mobile terminal to decrypt the signature information based on a public key obtained from a service platform to obtain second vehicle information, so as to determine the vehicle authentication status of the vehicle based on the second vehicle information and the first vehicle information; And receive and display a display interface sent by the mobile terminal; wherein, the display interface is sent by the mobile terminal when the mobile terminal automatically establishes a communication connection with a vehicle terminal. Before the mobile terminal automatically establishes a communication connection with the vehicle terminal, it further includes: the mobile terminal enables a screen mirroring mode based on the vehicle authentication status, and the mobile terminal detects and determines that the device distance between the mobile terminal and the vehicle is less than or equal to a distance threshold; Send interface operation information to the mobile terminal, so that the mobile terminal updates the vehicle status based on the interface operation information; When the mobile terminal detects and determines that the device distance is greater than the distance threshold, the mobile terminal turns off the screen mirroring mode; The vehicle management device is specifically configured to: Obtain interface operation information from the vehicle, and extract an operation response feature in the interface operation information; Update the vehicle authentication status of the vehicle based on the operation response feature; The vehicle management device is specifically configured to: Match the operation response feature with a reference response feature, and update the vehicle authentication status of the vehicle based on the matching result. The reference response feature is determined based on a reference vehicle corresponding to the first vehicle information.

9. A vehicle management device Characterized in that The device includes: An information processing module, configured to sign second vehicle information of the vehicle with a private key to obtain signature information, and send the signature information to the vehicle; or, send the private key to the vehicle, and the private key is used to instruct the vehicle to sign the second vehicle information to obtain signature information; A public key sending module, configured to receive first vehicle information sent by a mobile terminal and send a public key for the vehicle to the mobile terminal. The first vehicle information is sent after the mobile terminal obtains the first vehicle information and signature information of the vehicle from the vehicle terminal. The public key is used for the vehicle to decrypt the signature information to obtain second vehicle information, so as to determine the vehicle authentication status of the vehicle based on the second vehicle information and the first vehicle information; Wherein, the mobile terminal enables the screen mirroring mode based on the vehicle authentication status, detects the device distance between the mobile terminal and the vehicle based on the mobile terminal, and if the device distance is less than or equal to the distance threshold, the mobile terminal automatically establishes a communication connection with the in-vehicle terminal, and sends the display interface to the in-vehicle terminal for screen mirroring display based on the mobile terminal; obtains the interface operation information from the in-vehicle terminal based on the mobile terminal, and updates the vehicle status based on the interface operation information; if the device distance is greater than the distance threshold, the mobile terminal turns off the screen mirroring mode; Wherein, the mobile terminal updates the vehicle status based on the interface operation information, including: Obtaining the interface operation information from the vehicle and extracting the operation response features in the interface operation information; Updating the vehicle authentication status of the vehicle based on the operation response features; Wherein, the mobile terminal updates the vehicle authentication status of the vehicle based on the operation response features, including: Matching the operation response features with the reference response features, and updating the vehicle authentication status of the vehicle based on the matching result, where the reference response features are determined based on the reference vehicle corresponding to the first vehicle information.

10. A computer storage medium, Characterized in that, The computer storage medium stores multiple instructions, and the instructions are adapted to be loaded and executed by a processor to perform the method steps of any one of claims 1 to 4 or 5 or 6.

11. An electronic device, Characterized in that, Including: A processor and a memory; wherein, the memory stores a computer program, and the computer program is adapted to be loaded and executed by the processor to perform the method steps of any one of claims 1 to 4 or 5 or 6.

Images