In-vehicle application activation method, in-vehicle device, and vehicle

The use of a virtual code to identify vehicle manufacturer information in in-vehicle application activation methods encrypts and anonymizes vehicle identification numbers, addressing security risks and improving user experience by preventing personal information exposure.

JP2025532572APending Publication Date: 2025-10-01BYD CO LTD
View PDF 4 Cites 0 Cited by

Patent Information

Application Number
JP2025515595
Authority / Receiving Office
JP · JP
Patent Type
Applications
Current Assignee / Owner
Priority Date
2022-09-30
Filing Date
2023-04-26
Publication Date
2025-10-01

AI Technical Summary

Technical Problem

Existing in-vehicle application activation methods expose users' personal information, such as vehicle identification numbers, during activation processes, leading to security risks and legal concerns.

Method used

An in-vehicle application activation method using a virtual code that identifies vehicle manufacturer information, collected and sent to the in-vehicle application, ensuring security by encrypting and anonymizing the vehicle identification number.

Benefits of technology

Guarantees the security of users' personal privacy data and enhances user experience by preventing the leakage of personal information and complying with data protection regulations.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 2025532572000001_ABST
    Figure 2025532572000001_ABST
Patent Text Reader

Abstract

An in-vehicle application activation method, an in-vehicle device, and a vehicle, which relate to the vehicle technical field, include collecting a virtual code (S101), the virtual code being configured to identify vehicle manufacturer information, and sending the virtual code to an in-vehicle application (S102), such that the in-vehicle application performs an activation operation according to the virtual code.
Need to check novelty before this filing date? Find Prior Art

Description

[Technical Field]

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS This disclosure claims priority to and the benefit of Chinese Patent Application No. 202211215678.2, entitled "IN-VEHICLE APPLICATION ACTIVATION METHOD AND APPARATUS, VEHICLE-MOUNTED DEVICE, VEHICLE, AND STORAGE MEDIUM," filed on September 30, 2022. The entire contents of the above application are incorporated herein by reference.

[0002] The present disclosure relates to the field of vehicle technology, and in particular to an in-vehicle application activation method, an in-vehicle device, and a vehicle. [Background technology]

[0003] Currently, there are two methods for activating in-vehicle applications: offline activation and online activation. These two methods have one thing in common: both require the vehicle's unique identification number (VIN), used as activation information, to be sent to the third-party application. The differences are as follows: During offline activation, the verification operation is performed locally on the vehicle. Specifically, before the application is installed on the vehicle, the original equipment manufacturer sends the VINs of the current batch of vehicles to the third-party application supplier. The third-party application supplier generates an offline verification program based on the given list of VINs and installs it locally on the vehicle along with the application installation package. When a new vehicle is delivered to a user, the application is started to collect the vehicle's VIN and checks whether the VIN is on the list of activated VINs. If the VIN is on the list, the verification is passed and the application is activated. During online activation, the verification operation is performed via the third-party application supplier's cloud server. Specifically, when the vehicle is connected to the Internet, the application collects the vehicle's VIN through the vehicle system interface and then uploads the VIN to a third-party application supplier's cloud server. After the activation information is verified, an activated status is returned.

[0004] Both methods have significant risks: the vehicle's VIN is the user's personal information; the user's personal information is transmitted without any encryption, which is insecure and can easily lead to the leakage of user's personal information, among other issues; and there are legal risks of directly exposing user's personal information to third-party application suppliers. Summary of the Invention [Problem to be solved by the invention]

[0005] The present disclosure is intended to solve at least one of the technical problems in the related art to some extent. Therefore, a first objective of the present disclosure is to provide an in-vehicle application activation method in which a virtual code is collected to enable an in-vehicle application to perform an activation operation based on the virtual code. In this way, the security of a user's personal privacy data is greatly guaranteed and the user experience is improved using a simple and efficient method.

[0006] A second object of the present disclosure is to provide an in-vehicle application activation device.

[0007] A third object of the present disclosure is to provide an in-vehicle device.

[0008] A fourth object of the present disclosure is to provide a vehicle.

[0009] A fifth object of the present disclosure is to provide a computer-readable storage medium. [Means for solving the problem]

[0010] To achieve the above object, one embodiment of a first aspect of the present disclosure provides an in-vehicle application activation method, the method including: collecting a virtual code, the virtual code configured to identify vehicle manufacturer information; and sending the virtual code to an in-vehicle application to enable the in-vehicle application to perform an activation operation based on the virtual code.

[0011] According to the in-vehicle application activation method of this embodiment of the present disclosure, a virtual code configured to identify vehicle manufacturer information is collected and sent to the in-vehicle application so that the in-vehicle application can identify the vehicle manufacturer based on the vehicle manufacturer information in the virtual code to perform an activation operation. The virtual code only contains the vehicle manufacturer information and does not contain any user personal information. In this way, the security of the user's personal privacy data is greatly guaranteed and the user experience is improved using a simple and efficient method.

[0012] In some embodiments, the virtual code includes an encrypted code and an activation verification code, where the encrypted code is obtained by encrypting information other than vehicle manufacturer information, and the activation verification code is configured to identify the name of the vehicle manufacturer.

[0013] In some embodiments, collecting the virtual code includes collecting a vehicle identification number, performing a cryptographic operation on the vehicle identification number to obtain a first sequence code, collecting an activation verification code, and generating the virtual code based on the activation verification code and the first sequence code.

[0014] In some embodiments, collecting the virtual code includes collecting a vehicle identification number, collecting a random code, generating a second sequence code based on the random code and the vehicle identification number, performing a cryptographic operation on the second sequence code to obtain a third sequence code, collecting an activation verification code, and generating a virtual code based on the activation verification code and the third sequence code. In some embodiments, collecting the random code includes determining a vehicle model, and generating a random code based on the vehicle model.

[0015] In some embodiments, collecting the activation verification code includes determining a vehicle manufacturer identifier, where the vehicle manufacturer identifier indicates vehicle manufacturer information; and determining the activation verification code based on the vehicle manufacturer identifier.

[0016] In some embodiments, the encryption operation is performed by using the MD5 encryption algorithm.

[0017] In some embodiments, collecting the vehicle identification number includes receiving a vehicle identification number sent by the vehicle in response to a request to transmit from the vehicle, the request to transmit being generated by the vehicle each time the vehicle is powered on or reconnects to the network after being disconnected, and when the virtual code is not detected.

[0018] In some embodiments, sending the virtual code to the in-vehicle application includes the vehicle sending the virtual code to the in-vehicle application when the in-vehicle application is first started.

[0019] To achieve the above object, one embodiment of a second aspect of the present disclosure provides an in-vehicle application activation device, including: a collection module configured to collect a virtual code, wherein the virtual code is configured to identify vehicle manufacturer information; and a transmission module configured to send the virtual code to an in-vehicle application to enable the in-vehicle application to perform an activation operation based on the virtual code.

[0020] According to the in-vehicle application activation device of this embodiment of the present disclosure, the collection module collects the virtual code, and the transmission module sends the virtual code to the in-vehicle application to enable the in-vehicle application to perform an activation operation based on the virtual code. In this way, the security of the user's personal privacy data is greatly guaranteed and the user experience is improved using a simple and efficient method.

[0021] To achieve the above object, an embodiment of a third aspect of the present disclosure provides an in-vehicle device including a memory, a processor, and an in-vehicle application activation program stored in the memory and executable on the processor, wherein when the processor executes the in-vehicle application activation program, the in-vehicle application activation method according to the embodiment of the first aspect is implemented.

[0022] According to the in-vehicle device of this embodiment of the present disclosure, the above-mentioned in-vehicle application activation method is used, thus using a simple and efficient method, the security of the user's personal privacy data is greatly guaranteed, and the user experience is improved.

[0023] To achieve the above object, one embodiment of the fourth aspect of the present disclosure provides a vehicle including the above in-vehicle application activation apparatus or the above in-vehicle device.

[0024] According to the vehicle in this embodiment of the present disclosure, which includes the above-mentioned in-vehicle application activation device or the above-mentioned in-vehicle device, the security of the user's personal privacy data can be greatly guaranteed using a simple and efficient method, and the user experience is improved.

[0025] To achieve the above object, an embodiment of a fifth aspect of the present disclosure provides a computer-readable storage medium having stored thereon an in-vehicle application activation program, which, when executed by a processor, performs the in-vehicle application activation method according to the embodiment of the first aspect.

[0026] According to the computer-readable storage medium of this embodiment of the present disclosure, the above-mentioned in-vehicle application activation method is used, thus using a simple and efficient method to greatly ensure the security of users' personal privacy data and improve the user experience.

[0027] Additional aspects and advantages of the disclosure will be set forth in the description that follows, and in part will be apparent from the description, or may be learned by practice of the disclosure.

[0028] The above and / or additional aspects and advantages of the present disclosure will become apparent and understandable from the following description of implementations, taken in conjunction with the accompanying drawings. [Brief explanation of the drawings]

[0029] [Figure 1] 1 is a schematic flowchart of an in-vehicle application activation method according to one embodiment of the present disclosure. [Figure 2] 1 is a schematic flowchart of an in-vehicle application activation method according to one embodiment of the present disclosure. [Figure 3] 1 is a schematic diagram of the structure of an in-vehicle application activation device according to one embodiment of the present disclosure. DETAILED DESCRIPTION OF THE INVENTION

[0030]

[0023] The embodiments of the present disclosure are described in detail below. Examples of the embodiments are shown in the accompanying drawings, and the same or similar reference numerals in all the accompanying drawings indicate the same or similar components or elements having the same or similar functions. The embodiments described below with reference to the accompanying drawings are exemplary and are intended to explain the present disclosure and cannot be construed as limitations on the present disclosure.

[0031] The following describes an in-vehicle application activation method, an in-vehicle device, and a vehicle according to embodiments of the present disclosure, with reference to the accompanying drawings.

[0032] 1 is a schematic flowchart of an in-vehicle application activation method according to one embodiment of the present disclosure. As shown in FIG. 1, the in-vehicle application activation method is applied to an in-vehicle device. The method may include the following steps:

[0033] S101: A virtual code is collected, where the virtual code is configured to identify vehicle manufacturer information.

[0034] In particular, the in-vehicle device collects a virtual code including vehicle manufacturer information. The virtual code is configured to identify the vehicle manufacturer information. After the in-vehicle device sends the virtual code to the in-vehicle application, the in-vehicle application may identify the vehicle based on the virtual code including the vehicle manufacturer information.

[0035] A virtual code configured to identify vehicle manufacturer information is collected, and the virtual code is sent to an in-vehicle application to enable the in-vehicle application to identify the vehicle manufacturer based on the vehicle manufacturer information in the virtual code so as to perform an activation operation. The virtual code includes only the vehicle manufacturer information, thereby avoiding the transmission of personal information of the user. In this way, the security of the user's personal privacy data can be greatly guaranteed and the user experience can be improved using a simple and efficient method.

[0036] In some embodiments, the virtual code includes an encrypted code and an activation verification code, where the encrypted code is obtained by encrypting information other than vehicle manufacturer information, and the activation verification code is configured to identify the name of the vehicle manufacturer.

[0037] Furthermore, the virtual code further includes encrypted information obtained by encrypting information other than the vehicle manufacturer information. The other information may be user personal information, vehicle model information, vehicle body information, engine manufacturer information, vehicle factory information, etc. The other information is not particularly limited in this specification. By encrypting the other information using a simple and efficient method, the security of the user's personal privacy data is greatly guaranteed, thereby improving the user experience.

[0038] In some embodiments, the virtual code may be collected by collecting a vehicle identification number, performing a cryptographic operation on the vehicle identification number to obtain a first sequence code, collecting an activation verification code, and generating a virtual code based on the activation verification code and the first sequence code. Specifically, the in-vehicle device must first collect the actual vehicle identification number. After the vehicle identification number is collected, the vehicle identification number may be first encrypted. For example, a one-way encryption algorithm may be used to encrypt the vehicle identification number to obtain the first sequence code. The in-vehicle device then generates the activation verification code. Because the final virtual code must be effective in identifying the vehicle, the activation verification code may be data related to vehicle-specific information. The in-vehicle device generates the virtual code based on the activation verification code and the first sequence code. For example, the activation verification code and the first sequence code may be combined to obtain the virtual code.

[0039] In some embodiments, the vehicle identification number may be collected by receiving a vehicle identification number sent by the vehicle in response to a transmission request from the vehicle, the transmission request being generated by the vehicle each time the vehicle is powered on or reconnects to the network after being disconnected, and when the virtual code is not detected. The virtual code is a unique vehicle identification number obtained by anonymizing and encrypting the vehicle identification number and intended for use in in-vehicle application activation.

[0040] In particular, an in-vehicle application is pre-installed in the vehicle, and the in-vehicle application must be activated for normal use. Furthermore, the vehicle is provided with a built-in network card, e.g., a 4G network SIM (Subscriber Identity Module) card, to provide Internet service for the vehicle. Each time the vehicle is powered on (connected to a power source and started) or reconnects to the network after a disconnection, the vehicle first detects whether a virtual code has been generated. If the vehicle detects that a virtual code has not been generated, this means that the in-vehicle application has not been activated. In this case, the vehicle actively sends an in-vehicle application activation request to the host server. In response to the vehicle's request, the host server collects the actual vehicle identification number from the vehicle identification number interface of the vehicle system.

[0041] In some embodiments, the virtual code may alternatively be collected by collecting a vehicle identification number, collecting a random code and generating a second sequence code based on the random code and the vehicle identification number, performing a cryptographic operation on the second sequence code to obtain a third sequence code, collecting an activation verification code and generating a virtual code based on the activation verification code and the third sequence code.

[0042] Specifically, the in-vehicle device first collects the actual vehicle identification number. After collecting the vehicle identification number, the in-vehicle device generates a random code. The generated virtual code must be valid for identifying the vehicle, and therefore the random code may be data related to the vehicle's unique information. Next, the in-vehicle device generates a second sequence code based on the random code and the vehicle identification number. For example, the random code and the vehicle identification number may be combined to obtain the second sequence code. Next, an encryption operation is performed on the second sequence code. For example, the second sequence code may be encrypted using a one-way encryption algorithm to obtain a third sequence code. Finally, the in-vehicle device generates an activation verification code. The generated virtual code must be valid for identifying the vehicle, and therefore the activation verification code may also be data related to the vehicle's unique information. The in-vehicle device generates the virtual code based on the activation verification code and the third sequence code. In this way, the actual vehicle identification number is encrypted using multi-layer encryption to obtain the virtual code. The resulting virtual code is not only used to identify the vehicle, but also prevents the disclosure of the vehicle identification number, thereby ensuring the security of the user's personal privacy data. Furthermore, the virtual code has high security and cannot be easily cracked.

[0043] In this embodiment, it should be noted that in the above embodiments regarding specific methods for collecting vehicle identification numbers, reference may be made to methods for collecting vehicle identification numbers.

[0044] In one implementation, the random code may be collected by determining a vehicle model and generating the random code based on the vehicle model. In other words, the random code may be generated based on the vehicle model. As an example, the random code may be generated based on the vehicle model by using a random code generator.

[0045] Specifically, when collecting the actual vehicle identification number through the vehicle identification number interface of the vehicle system, the on-board device detects the vehicle model through the vehicle model interface. After determining the vehicle model, the on-board device generates a secret code corresponding to the vehicle model, i.e., a random code. The lengths of the vehicle identification number and the random code are not limited and are determined based on actual conditions. For example, a vehicle identification number generally consists of 17 characters, and the random code may be set to 4 characters. After the vehicle identification number and the random code are obtained, the 4-character random code may be added to the 17-character vehicle identification number to obtain a second sequence code having a length of 21 characters.

[0046] It should be noted that the method for generating the second sequence code based on the vehicle identification number and the random code is not limited. For example, the random code may be added directly to the beginning or end of the vehicle identification number, or the random code may be fragmented and inserted into the vehicle identification number. This is not limited in this specification.

[0047] In one implementation, in the two embodiments described above for encrypting the vehicle identification number, the specific encryption method used may be to perform the encryption operation using the MD5 (Message Digest Algorithm) encryption algorithm. Note that MD5 is a one-way hash (HASH) encryption algorithm that is irreversible. Therefore, except for brute-force cracking, no results can generally be obtained by using the inverse algorithm. A one-way hash function is also called a message digest function, hash function, or hashing function. The input message is also called a pre-image, and the output hash value is also called a message digest or fingerprint, which is equivalent to the message ID. For example, a second sequence code may be used as the pre-image input, and the output message digest is called the fourth sequence code. Another MD5 value with a fixed length may be generated by performing an operation on data of any length using the MD5 encryption algorithm. For example, an encryption operation may be performed on a 21-character second sequence code to obtain a 16-character third sequence code.

[0048] In one implementation, the activation verification code may be collected by determining a vehicle manufacturer identifier, where the vehicle manufacturer identifier indicates vehicle manufacturer information, and determining an activation verification code based on the vehicle manufacturer identifier.

[0049] In particular, after obtaining the first sequence code or the third sequence code, the in-vehicle device further adds an identifier to the virtual code. The identifier may be a character that allows identification of the name of the company to which the vehicle belongs. In particular, the activation verification code may be generated based on vehicle manufacturer information, such as the vehicle's company logo information, and the activation verification code may be added to the first sequence code to obtain a virtual code. The length of the activation verification code is not limited and is determined based on actual conditions. For example, the activation verification code may be set to three characters. After obtaining a three-character activation verification code and a 16-character third sequence code, the three-character activation verification code may be added to the 16-character third sequence code to obtain a virtual code with a length of 19 characters.

[0050] Please note that the vehicle manufacturer information (such as the vehicle's company logo information) may be characters that can identify the manufacturer's name. The length and character type of the vehicle manufacturer information / identifier may be set according to actual needs. The characters may be letters, numbers, special symbols, etc., and are not particularly limited in this specification. Furthermore, the vehicle manufacturer information may be identification information previously agreed upon by the in-vehicle application supplier and the vehicle manufacturer.

[0051] Furthermore, the method for generating the virtual code based on the activation verification code and the first sequence code, and the activation code and the third sequence code, is not limited. For example, the activation verification code may be directly added to the beginning or end of the second sequence code and the fourth sequence code. The generated virtual code has a one-to-one correspondence with the vehicle identification number, and one unique virtual code is generated for each vehicle identification number.

[0052] Based on the above description, it can be learned that the vehicle identification number undergoes three encryption operations and cannot be recovered to its true value, thereby effectively ensuring high confidentiality of the vehicle identification number. Given that MD5 is a public encryption algorithm, anyone familiar with commonly used encryption algorithms can easily obtain a pre-image by decryption and decoding. Therefore, the vehicle identification number is mapped both before and after encryption, which is equivalent to adding two layers of encryption logic to personal information, preventing third parties from collecting actual personal privacy data, targeting users, threatening users, and violating their privacy rights. This method can reduce manual input due to the use of existing encryption algorithms, improving work efficiency. Furthermore, the addition of an identifier simplifies the operation method and ensures high confidentiality of the vehicle identification number. Furthermore, since the encryption operations for the vehicle identification number in the embodiments of the present disclosure are performed entirely on the on-board device, the amount of operating memory used in the vehicle can be reduced.

[0053] Therefore, the use of the above encryption method for a vehicle identification number makes it impossible to gather the secret code indicating the vehicle model (i.e., the vehicle model identifier) ​​and the method for adding the vehicle model identifier (i.e., the method for generating the second sequence code) even if the user's vehicle identification number, vehicle model, and encryption algorithm type are collected. This eliminates the possibility of obtaining the encrypted virtual code through inference. Alternatively, even if the virtual code and the encryption algorithm for the vehicle identification number are collected, it is impossible to gather the vehicle model and secret code of the vehicle. This eliminates the possibility of obtaining the user's actual vehicle identification number through inference. In this way, the unidirectionality and irreversibility of data transmission are largely guaranteed, thereby ensuring the security of the user's personal privacy data.

[0054] It should be noted that the various methods for collecting vehicle identification numbers shown in the above examples are merely examples and are not intended to be specific limitations on the present disclosure. In a particular application, the method can be selected based on actual conditions or determined based on past experience.

[0055] S102: Sending the virtual code to the in-vehicle application to enable the in-vehicle application to perform an activation operation based on the virtual code.

[0056] In particular, after collecting the virtual code, the in-vehicle device may send the virtual code to the in-vehicle application so that an activation operation may be performed based on the virtual code when the in-vehicle application is first started.

[0057] In one implementation, sending the virtual code to the in-vehicle application includes sending the virtual code to the in-vehicle application when the in-vehicle application is first started.

[0058] Specifically, after generating the virtual code, the in-vehicle device transmits the generated virtual code to the vehicle and stores the code in the vehicle's local memory. The virtual code must be placed in a non-deletable directory, so that the virtual code cannot be erased when the factory settings are restored or data is cleared. In other words, the vehicle has only one fixed virtual code, and even after reclaiming and recollecting, the virtual code remains the same as the virtual code that was originally generated.

[0059] When the in-vehicle application is first launched, the vehicle sends a virtual code to the in-vehicle application to enable the in-vehicle application to perform activation operations based on the virtual code. For example, when the in-vehicle application is first launched while online, the vehicle's display screen immediately displays a prompt about the in-vehicle application activation operations. After the user clicks / tap to agree, the in-vehicle application interacts with the vehicle system via the virtual code interface to retrieve the vehicle's virtual code.

[0060] If the virtual code is successfully retrieved, an in-vehicle application activation program is initiated. At this time, the in-vehicle application generates an in-vehicle application activation request based on the unique, non-repeating virtual code and sends the request to the in-vehicle application supplier's cloud server. After receiving the in-vehicle application activation request, the in-vehicle application supplier's cloud server verifies the validity of the virtual code, for example, by verifying whether the virtual code includes the vehicle's company logo and determining whether the region where the virtual code was uploaded matches the region of the in-vehicle application supplier's cloud server. If the virtual code is verified to be valid, an activation success indication is returned to the in-vehicle application.

[0061] After the in-vehicle application is successfully activated, all functions of the in-vehicle application can be used normally, and the vehicle's display screen does not display a prompt about the in-vehicle application activation operation. If the in-vehicle application activation fails, the in-vehicle application cannot be used normally, a prompt saying "Application not activated. Contact your dealer" is displayed on the vehicle's display screen, and the virtual code is automatically re-collected from the vehicle system via the virtual code interface. After the in-vehicle application is successfully activated, the vehicle system no longer responds to the in-vehicle application's virtual code retrieval request.

[0062] Please note that there are many reasons why an in-vehicle application may not be activated. The first reason may be that the network connection is poor during activation, and after the in-vehicle application collects the virtual code, the virtual code fails to be sent to the cloud server, or the verification time is too long and exceeds the reaction time range. The second reason may be that an error occurs in the in-vehicle application supplier's cloud server, and the cloud server fails to return an activation success indication.

[0063] Furthermore, since the virtual code is refreshed each time the vehicle is powered on or reconnects to the network after disconnection, it is necessary to detect the generation status of the virtual code each time the vehicle is powered on or reconnects to the network after disconnection. If the virtual code is not detected, the above operations of collecting the VID, encrypting the VID, and generating and storing the virtual code are repeated. The virtual codes generated based on a secret encryption algorithm are independent and non-repeating, ensuring that the user's personal information is not obtained by third-party application suppliers and reducing the risk of user privacy data leakage.

[0064] In order to enable those skilled in the art to understand the present disclosure more clearly, the following is described in detail with reference to specific examples. As shown in Figure 2, an in-vehicle application activation method may include:

[0065] S201: Every time the vehicle is powered on or reconnects to the network after being disconnected, and when the virtual code is not detected, the vehicle outputs a transmission request to the in-vehicle device and sends the vehicle identification number to the in-vehicle device.

[0066] S202: The in-vehicle device receives a vehicle identification number sent by the vehicle in response to the vehicle's transmission request, and encrypts the vehicle identification number to obtain a virtual code.

[0067] S203: The in-vehicle device sends an encrypted virtual code to the vehicle.

[0068] S204: The vehicle stores the virtual code.

[0069] S205: The vehicle sends a virtual code to the in-vehicle application when the in-vehicle application is first started.

[0070] S206: After collecting the virtual code, the in-vehicle application sends the virtual code to the cloud server of the in-vehicle application supplier.

[0071] S207: The in-vehicle application supplier's cloud server verifies the validity of the virtual code.

[0072] S208: If the virtual code is verified to be valid, the cloud server of the in-vehicle application supplier returns an activation success indication to the in-vehicle application.

[0073] S209: The cloud server of the in-vehicle application supplier checks whether the in-vehicle application is successfully activated. If the in-vehicle application is successfully activated, S210 is executed; if the in-vehicle application is not successfully activated, S211 is executed.

[0074] S210: The in-vehicle application is used normally.

[0075] S211: The vehicle's display screen will prompt, "Application not activated. Please contact your dealer."

[0076] In the above embodiment, the in-vehicle device performs multiple encryption operations after collecting the vehicle identification number from the vehicle to generate a new virtual code that prevents the user's actual vehicle identification number from being identified. The in-vehicle application collects the encrypted virtual code through the vehicle system interface and sends it to the in-vehicle application supplier's cloud server for verification. When the virtual code is verified to be in the correct format, the activation request is determined to be valid. The in-vehicle application supplier's cloud server returns an activation success indication to the in-vehicle application, in which case the application can be used normally. In this way, confidential information such as the vehicle identification number is protected, the anonymity of data from third-party suppliers is guaranteed, and overseas data protection regulations are complied with, so that the security of the user's personal privacy data can be greatly guaranteed and the user experience can be improved using a simple and efficient method.

[0077] In conclusion, according to the in-vehicle application activation method in this embodiment of the present disclosure, a vehicle identification number is collected, the vehicle identification number is encrypted to obtain a virtual code, and the virtual code is sent to the in-vehicle application to enable the in-vehicle application to perform an activation operation based on the virtual code. In this way, using a simple and efficient method, the risk of privacy data leakage can be significantly reduced, the security of users' personal privacy data can be greatly guaranteed, and the user experience can be improved.

[0078] FIG. 3 is a schematic diagram of the structure of an in-vehicle application activation device according to one embodiment of the present disclosure.

[0079] As shown in FIG. 3, the in-vehicle application activation device 300 may include a collection module 301 and a transmission module 303 .

[0080] The collection module 301 is configured to collect a virtual code. The virtual code is configured to identify vehicle manufacturer information. The transmission module 303 is configured to send the virtual code to an in-vehicle application to enable the in-vehicle application to perform an activation operation based on the virtual code.

[0081] In some embodiments, the collection module 301 is configured to, among other things, collect a vehicle identification number, perform a cryptographic operation on the vehicle identification number to obtain a first sequence code, collect an activation verification code, and generate a virtual code based on the activation verification code and the first sequence code.

[0082] In some embodiments, the collection module 301 is further configured to collect a vehicle identification number, collect a random code and generate a second sequence code based on the random code and the vehicle identification number, perform a cryptographic operation on the second sequence code to obtain a third sequence code, and collect an activation verification code and generate a virtual code based on the activation verification code and the third sequence code.

[0083] In some embodiments, the collection module 301 is configured to, among other things, determine a vehicle model and generate a random code based on the vehicle model.

[0084] In some embodiments, the collection module 301 is further configured to determine a vehicle manufacturer identifier, where the vehicle manufacturer identifier indicates vehicle manufacturer information, and determine an activation verification code based on the vehicle manufacturer identifier.

[0085] In some embodiments, the collection module 301 further performs encryption operations by using the MD5 encryption algorithm.

[0086] In some embodiments, the collection module 301 is configured, among other things, to receive a vehicle identification number sent by a vehicle in response to a transmission request from the vehicle, the transmission request being generated by the vehicle each time the vehicle is powered on or reconnects to the network after being disconnected, and when the virtual code is not detected.

[0087] In some embodiments, the transmission module 302 is configured to, among other things, send a virtual code to the in-vehicle application when the in-vehicle application is first launched.

[0088] It should be noted that for details not disclosed in the in-vehicle application activation device, reference is made to the details disclosed in the in-vehicle application activation method, which again will not be described herein.

[0089] According to the in-vehicle application activation device of this embodiment of the present disclosure, the collection module collects the vehicle identification number, and the encryption module encrypts the vehicle identification number. A virtual code is collected, and the transmission module sends the virtual code to the in-vehicle application to enable the in-vehicle application to perform an activation operation based on the virtual code. In this way, using a simple and efficient method, the risk of privacy data leakage can be significantly reduced, the security of users' personal privacy data can be greatly guaranteed, and the user experience can be improved.

[0090] In accordance with the above embodiment, an embodiment of the present disclosure further provides an in-vehicle device including a memory, a processor, and an in-vehicle application activation program stored in the memory and executable on the processor, wherein the above-described in-vehicle application activation method can be implemented when the processor executes the in-vehicle application activation program.

[0091] According to the in-vehicle device of this embodiment of the present disclosure, the above-mentioned in-vehicle application activation method is used, which can significantly reduce the risk of privacy data leakage using a simple and efficient method, greatly ensure the security of users' personal privacy data, and improve the user experience.

[0092] Corresponding to the above embodiment, an embodiment of the present disclosure further provides a vehicle including the above in-vehicle application activation apparatus or the above in-vehicle device.

[0093] According to the vehicle in this embodiment of the present disclosure, which includes the above-mentioned in-vehicle application activation device or the above-mentioned in-vehicle device, the security of the user's personal privacy data can be greatly guaranteed using a simple and efficient method, and the user experience is improved.

[0094] Corresponding to the above embodiment, an embodiment of the present disclosure further provides a computer-readable storage medium having an in-vehicle application activation program stored thereon, the in-vehicle application activation program, when executed by a processor, performing the above-described in-vehicle application activation method.

[0095] According to the computer-readable storage medium of this embodiment of the present disclosure, the above-mentioned in-vehicle application activation method is used, which can significantly reduce the risk of privacy data leakage, greatly protect the security of users' personal privacy data, and improve the user experience using a simple and efficient method.

[0096] It should be noted that the logic and / or steps illustrated in a flowchart or otherwise described herein, e.g., an ordered list that may be thought of as executable instructions configured to implement a logical function, may be embodied in any computer-readable medium, particularly to be used by or in combination with an instruction execution system, apparatus, or device (e.g., a computer-based system, a system including a processor, or another system that can obtain instructions from and execute the instructions of an instruction execution system, apparatus, or device). In the specification of this disclosure, a "computer-readable medium" may be any device that can contain, store, communicate, propagate, or transmit a program to be used by or in combination with an instruction execution system, apparatus, or device. More specific examples (non-exhaustive list) of computer-readable media include the following: an electrical connection having one or more wires (an electronic device), a portable computer diskette (a magnetic device), a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), a fiber optic device, and a portable compact disc read-only memory (CDROM). Furthermore, the computer-readable medium may even be paper or another suitable medium on which a program can be printed, since the program may be obtained electronically, for example, by optically scanning paper or another medium, then compiled, interpreted, or processed in any other suitable manner if necessary, and then stored in computer memory.

[0097] It should be understood that portions of the present disclosure can be implemented using hardware, software, firmware, or a combination thereof. In the above implementations, steps or methods may be implemented using software or firmware stored in a memory and executed by a suitable instruction execution system. For example, when hardware is used for implementation, as in other implementations, the implementation may be performed using any one or combination of the following techniques well known in the art: discrete logic circuitry including logic gate circuits configured to implement logical functions of data signals, appropriate combinations of logic gate circuits, special purpose integrated circuits including programmable gate arrays (PGAs), field programmable gate arrays (FPGAs), etc.

[0098] In the description herein, the use of reference terms such as "one embodiment," "some embodiments," "one example," "specific example," "some examples," etc., means that a particular feature, structure, material, or characteristic described in connection with an embodiment or example is included in at least one embodiment or example of the present disclosure. In the description herein, the use of the above-mentioned exemplary terms does not necessarily refer to the same embodiment or example. Furthermore, the described particular feature, structure, material, or characteristic may be combined in any suitable manner in any one or more of the embodiments or examples. Furthermore, the terms "first" and "second" used in the embodiments of the present disclosure are intended to describe the subject matter only and cannot be understood as indicating or implying the relative importance or quantity of the technical features described in the embodiment. Therefore, a feature qualified by "first" or "second" in the embodiments of the present disclosure may explicitly or implicitly indicate that the embodiment includes at least one of such features. In the description of the present disclosure, unless explicitly specified in the embodiment, the term "plurality" means at least two or more, for example, two, three, or four. Although the embodiments of the present disclosure have been illustrated and described above, it may be understood that the above embodiments are illustrative and should not be understood as limitations of the present disclosure. Those skilled in the art may make changes, modifications, replacements, or variations to the above embodiments within the scope of the present disclosure.

Claims

1. 1. A method for in-vehicle application activation, comprising: collecting a virtual code, the virtual code configured to identify vehicle manufacturer information; sending the virtual code to an in-vehicle application to enable the in-vehicle application to perform an activation operation based on the virtual code; A method for in-vehicle application activation comprising:

2. 2. The in-vehicle application activation method of claim 1, wherein the virtual code includes an encrypted code and an activation verification code, the encrypted code being obtained by encrypting information other than the vehicle manufacturer information, and the activation verification code being configured to identify the name of the vehicle manufacturer.

3. said collecting virtual codes; collecting vehicle identification numbers; performing a cryptographic operation on the vehicle identification number to obtain a first sequence code; collecting an activation verification code and generating the virtual code based on the activation verification code and the first sequence code; The in-vehicle application activation method of claim 1 , comprising:

4. said collecting virtual codes; collecting vehicle identification numbers; collecting a random code and generating a second sequence code based on the random code and the vehicle identification number; performing a cryptographic operation on the second sequence code to obtain a third sequence code; collecting an activation verification code and generating the virtual code based on the activation verification code and the third sequence code; The in-vehicle application activation method of claim 1 , comprising:

5. said collecting random codes; determining a vehicle model; generating the random code based on the vehicle model; The in-vehicle application activation method of claim 4, comprising:

6. said collecting an activation verification code; determining a vehicle manufacturer identifier, the vehicle manufacturer identifier indicating the vehicle manufacturer information; determining the activation verification code based on the vehicle manufacturer identifier; 5. The method of claim 2, wherein the activation of an in-vehicle application is performed by a vehicle.

7. The in-vehicle application activation method according to any one of claims 2 to 5, wherein the encryption operation is performed by using the MD5 encryption algorithm.

8. collecting a vehicle identification number; receiving the vehicle identification number sent by the vehicle in response to a transmission request from the vehicle, the transmission request being generated by the vehicle each time the vehicle is powered on or reconnects to a network after being disconnected and when the virtual code is not detected; 6. The method of claim 3, wherein the activation of an in-vehicle application comprises:

9. sending the virtual code to the in-vehicle application; sending the virtual code to the in-vehicle application when the in-vehicle application is first launched; 6. The method of claim 1, further comprising:

10. 10. An in-vehicle device comprising: a memory; a processor; and an in-vehicle application activation program stored in the memory and executable on the processor, the in-vehicle application activation program, when executed by the processor, implementing the in-vehicle application activation method of any one of claims 1 to 9.

11. A vehicle comprising an on-board device according to claim 10.

Citation Information

Patent Citations

  • Vehicle machine service method and device

    CN110210822A

  • Vehicle, vehicle machine equipment and vehicle-mounted third-party application software automatic activation method

    CN111199030A

  • Vehicle full life cycle part management system and method

    CN113689011A

  • How to protect personal property, especially motor vehicles, from unauthorized use

    JP2009531893A