Internet of vehicles product verification method and device based on LTE communication module

Abstract

The invention discloses an Internet of Vehicles product verification method based on an LTE communication module, the method is applied to an application end, the application end communicates with the LTE communication module, and the method comprises the following steps: receiving a login request input by a user; determining whether the user is legal or not according to a preset user list; if yes, receiving a login password input by the user; requesting a first key packet file from the LTE communication module; determining whether the login password is legal based on the first key packet file; and if the login request is legal, passing the login request and returning a login result. In conclusion, the risk of being stolen is reduced, a user or an intruder cannot visually see the original text of the secret key, and information safety is guaranteed to the maximum extent.

Description

Technical Field

[0001] This disclosure relates to the field of computer technology, and in particular to a method and apparatus for verifying vehicle networking products based on an LTE communication module. Background Technology

[0002] In the field of connected vehicle products, LTE (Long Term Evolution) communication modules require authentication to prevent security issues such as user information tampering or application deletion / modification. Currently, there are several methods for Linux system login authentication in the connected vehicle product field: 1. Generating the authentication code uniformly during software package generation; 2. Manually generating the authentication code by modifying it on the Linux control terminal; 3. Integrating the communication module login authentication method into the software code, where the generated authentication code contains some unique information about the communication module. However, all three methods have drawbacks in the connected vehicle product field. For example, the unified authentication method cannot achieve a one-device-one-secret security level and is easily compromised; the manually generated authentication code on the Linux control terminal is easily monitored and stolen, leading to information security issues; and finally, integrating the communication module login authentication method into the software code makes it easy to reverse engineer and crack.

[0003] In summary, the field of connected vehicle products urgently needs a secure and reliable login verification method.

[0004] The purpose of this invention is to provide a login verification method for LTE communication modules, which solves the defects of existing login verification methods. It realizes the generation of a unique key externally and then passes it into a certain memory of the LTE communication module to reduce the risk of theft. During verification, after decryption, it is presented as an SHA256 key in the Linux verification system, so that users or intruders cannot see the original key text directly, thus maximizing information security. Summary of the Invention

[0005] To address the aforementioned technical issues, embodiments of this disclosure provide a method, apparatus, and electronic device for verifying vehicle networking products based on an LTE communication module.

[0006] According to one aspect of the present disclosure, a method for verifying vehicle-to-everything (V2X) products based on an LTE communication module is provided, applied to an application terminal, wherein the application terminal communicates with the LTE communication module, wherein the method includes:

[0007] Receive login requests from users;

[0008] Confirm the legitimacy of the user based on the preset user list;

[0009] If valid, accept the login password entered by the user;

[0010] Request the first key packet file from the LTE communication module;

[0011] Determine whether the login password is valid based on the first key package file;

[0012] If the request is valid, the login request will be approved and a login result will be returned.

[0013] Preferably, requesting the first key packet file from the LTE communication module includes:

[0014] A request is sent to the LTE communication module via the QMI interface to obtain the first key packet file.

[0015] Preferably, determining the validity of the login password based on the first key packet file includes:

[0016] The first key packet file is decrypted using AES256 to obtain the first ciphertext, the chipID of the LTE communication module component chip, and the LTE communication module production code from the first key packet file. The second check code is calculated, and the second check code is a cyclic redundancy check code.

[0017] Determine whether the chipID of the LTE communication module component chip, the LTE communication module production code, and the second check code are correct;

[0018] If the chipID of the LTE communication module component chip, the production code of the LTE communication module, and the second verification code are correct, then the validity of the login password is determined based on the first ciphertext.

[0019] Preferably, determining the validity of the login password based on the first ciphertext includes:

[0020] The login password is encrypted using SHA256 to obtain the second password ciphertext;

[0021] Determine whether the first ciphertext and the second ciphertext are consistent;

[0022] If they match, then the login password is confirmed to be valid.

[0023] According to another aspect of the present disclosure, a vehicle-to-everything (V2X) product verification device based on an LTE communication module is provided, applied at an application end, wherein the application end communicates with the LTE communication module, wherein the device includes:

[0024] The second receiving module is used to receive login requests input by the user;

[0025] The first legitimacy verification module is used to verify whether the user is legitimate based on a preset user list;

[0026] The third receiving module is used to receive the login password entered by the user if it is valid;

[0027] The acquisition module is used to request the first key packet file from the LTE communication module;

[0028] The second validity verification module is used to determine whether the login password is valid based on the first key package file;

[0029] The return module is used to process the login request and return the login result if it is valid.

[0030] According to embodiments of this disclosure, an electronic device is also provided, the electronic device comprising:

[0031] processor;

[0032] Memory used to store the processor's executable instructions;

[0033] The processor is configured to read the executable instructions from the memory and execute the instructions to implement the above-mentioned vehicle-to-everything (V2X) product verification based on the LTE communication module.

[0034] This invention discloses a verification method for vehicle-to-everything (V2X) products based on an LTE communication module, applied to an application terminal. The application terminal communicates with the LTE communication module. The method includes: receiving a login request input by a user; confirming the legitimacy of the user according to a preset user list; if legitimate, receiving the login password input by the user; requesting a first key packet file from the LTE communication module; determining the legitimacy of the login password based on the first key packet file; if legitimate, approving the login request and returning the login result, thereby reducing the risk of theft and preventing users or intruders from directly seeing the original key text, thus maximizing information security.

[0035] The technical solutions of this disclosure will be further described in detail below with reference to the accompanying drawings and embodiments. Attached Figure Description

[0036] The above and other objects, features, and advantages of this disclosure will become more apparent from the more detailed description of the embodiments thereof in conjunction with the accompanying drawings. The drawings are provided to further illustrate the embodiments of this disclosure and form part of the specification. They are used together with the embodiments of this disclosure to explain the disclosure and do not constitute a limitation thereof. In the drawings, the same reference numerals generally represent the same components or steps.

[0037] Figure 1This is a flowchart illustrating an exemplary embodiment of the present disclosure of a vehicle-to-everything (V2X) product verification method based on an LTE communication module.

[0038] Figure 2 This is a flowchart illustrating a vehicle-to-everything (V2X) product verification method based on an LTE communication module, provided in another exemplary embodiment of this disclosure.

[0039] Figure 3 This is a schematic diagram of the structure of a vehicle networking product verification device based on an LTE communication module provided in an exemplary embodiment of this disclosure.

[0040] Figure 4 This is a schematic diagram of the structure of a vehicle networking product verification device based on an LTE communication module provided in another exemplary embodiment of this disclosure.

[0041] Figure 5 This is a structural diagram of an electronic device provided in an exemplary embodiment of this disclosure.

[0042] Figure 6 This is a schematic diagram of the interaction process of a vehicle-to-everything (V2X) product verification method based on an LTE communication module provided in an exemplary embodiment of this disclosure. Detailed Implementation

[0043] Hereinafter, exemplary embodiments according to the present disclosure will be described in detail with reference to the accompanying drawings. Obviously, the described embodiments are merely some embodiments of the present disclosure, and not all embodiments of the present disclosure, and it should be understood that the present disclosure is not limited to the exemplary embodiments described herein.

[0044] It should be noted that, unless otherwise specifically stated, the relative arrangement, numerical expressions, and values ​​of the components and steps set forth in these embodiments do not limit the scope of this disclosure.

[0045] Those skilled in the art will understand that the terms "first," "second," etc., in the embodiments of this disclosure are only used to distinguish different steps, devices, or modules, and do not represent any specific technical meaning, nor do they indicate a necessary logical order between them.

[0046] It should also be understood that in the embodiments disclosed herein, "a plurality of" may refer to two or more, and "at least one" may refer to one, two or more.

[0047] It should also be understood that any component, data or structure mentioned in the embodiments of this disclosure can generally be understood as one or more unless expressly defined or given to the contrary in the context.

[0048] Furthermore, the term "and / or" in this disclosure is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, or B existing alone. Additionally, the character " / " in this disclosure generally indicates that the preceding and following related objects have an "or" relationship.

[0049] It should also be understood that the description of the various embodiments in this disclosure emphasizes the differences between the various embodiments, and the similarities or similarities can be referred to each other. For the sake of brevity, they will not be described in detail.

[0050] At the same time, it should be understood that, for ease of description, the dimensions of the various parts shown in the accompanying drawings are not drawn according to actual scale.

[0051] The following description of at least one exemplary embodiment is merely illustrative and is in no way intended to limit this disclosure or its application or use.

[0052] Techniques, methods, and equipment known to those skilled in the art may not be discussed in detail, but where appropriate, such techniques, methods, and equipment should be considered part of the specification.

[0053] It should be noted that similar labels and letters in the following figures indicate similar items; therefore, once an item is defined in one figure, it does not need to be discussed further in subsequent figures.

[0054] The embodiments disclosed herein can be applied to electronic devices such as terminal devices, computer systems, and servers, and can operate together with a wide range of other general-purpose or special-purpose computing system environments or configurations. Examples of well-known terminal devices, computing systems, environments, and / or configurations suitable for use with electronic devices such as terminal devices, computer systems, and servers include, but are not limited to: personal computer systems, server computer systems, thin clients, thick clients, handheld or laptop devices, microprocessor-based systems, set-top boxes, programmable consumer electronics, network PCs, minicomputer systems, mainframe computer systems, and distributed cloud computing environments including any of the above systems, etc.

[0055] Electronic devices such as terminal devices, computer systems, and servers can be described in the general context of computer system executable instructions (such as program modules) executed by a computer system. Typically, program modules can include routines, programs, object programs, components, logic, data structures, etc., which perform specific tasks or implement specific abstract data types. Computer systems / servers can be implemented in distributed cloud computing environments, where tasks are executed by remote processing devices linked through communication networks. In distributed cloud computing environments, program modules can reside on local or remote computing system storage media, including storage devices.

[0056] To enable those skilled in the art to accurately and clearly understand the technical solutions of this disclosure, the technical solutions of this disclosure are described in detail through examples.

[0057] Exemplary methods

[0058] Figure 1 This is a schematic flowchart illustrating a vehicle-to-everything (V2X) product verification method based on an exemplary embodiment of this disclosure. In this embodiment, the V2X product verification method uses an LTE communication module, which includes a modem applied to the LTE communication module, and the LTE communication module communicates with the V2X product application terminal.

[0059] like Figure 1 As shown, the present disclosure of a vehicle-to-everything (V2X) product verification method based on an LTE communication module may include the following steps:

[0060] Step 101: Receive a key generation instruction input by the user of the vehicle networking product application terminal. The key generation instruction includes password length, password complexity, fixed characters, chipID of the LTE communication module component chip, and LTE communication module production code.

[0061] Step 102: Generate a first password based on the password length, the password complexity, and the fixed characters.

[0062] Step 103: Encrypt the first password using SHA256 to obtain the first password ciphertext.

[0063] Step 104: Package the first ciphertext, the chipID of the LTE communication module component chip, the LTE communication module production code, and the preset International Mobile Equipment Identity (IMEI) information to generate the first cipher packet.

[0064] Step 105: Obtain a random code from the general operating system to verify the first password packet and obtain the first password verification packet.

[0065] In some embodiments, a first verification code is generated based on a random code obtained from the general operating system. The first verification code is a cyclic redundancy check (CRC) code. The first verification code is used to verify the password packet to obtain a first password verification packet.

[0066] Step 106: Encrypt the first password verification packet to obtain a first key packet file. The first key packet file is used to verify the user's login password when the user enters a login request, so as to determine the legitimacy of the user.

[0067] The first password verification packet is encrypted using AES256 to obtain the first key packet file.

[0068] Step 107: Store the first key packet file into the modem memory.

[0069] In some embodiments, the first key packet file is transmitted to any address of the modem of the LTE communication module to store the first key packet file in the LTE communication module.

[0070] In some embodiments of this disclosure, the method can also transmit the key packet to any address in the file system on the Modem of the LTE communication module to store the key packet file in the LTE communication module. Furthermore, it can interact with an application. For example, after receiving a user's login request, the method decrypts the key packet file to obtain a second verification code, a first password, the chip ID of the LTE communication module component chip, and the LTE communication module production code; it determines whether the second verification code matches the first verification code; if they match, it determines whether the chip ID and the LTE communication module production code are correct; if correct, it performs AES256 encryption on the first password to obtain a first password ciphertext, which is returned to the application; when the user enters a login password, it determines whether the login password is valid based on the first password ciphertext.

[0071] Specifically, in this disclosure embodiment, regarding Figure 1In the illustrated embodiment, an application software running on the LTE communication module is provided. This application software provides an entry point for customer-customized keys for vehicle networking products. It receives password information input by the user, such as password length, password complexity, and fixed characters. It can also obtain a random code from a general operating system and generate a password (i.e., a first password) based on the password length, complexity, and fixed characters. The first password is then encrypted to obtain the first password ciphertext. Furthermore, it determines whether information such as the LTE communication module chip ID and LTE communication module production code is needed, and incorporates this information into the first password ciphertext according to the user's actual requirements. The process involves several steps: first, obtaining the first cryptographic packet; second, saving the IMEI (International Mobile Equipment Identity) corresponding to the first cryptographic packet into a statistics table; third, generating and calculating a checksum based on a random code (which can have any number of characters and length), i.e., calculating the CRC checksum of the cryptographic packet and incorporating it into the first cryptographic packet to obtain the first cryptographic verification packet; fourth, encrypting the first cryptographic verification packet to obtain the first key packet file; and finally, when the first key packet file is generated, it is loaded into a memory segment of the LTE communication module's modem while the LTE communication module is still on the production line, thus completing the key generation and loading. In this way, the generation and storage of the key are completed within the LTE communication module.

[0072] In some embodiments, such as on a production line, the application software for the LTE communication module provides checkboxes for items such as password length, fixed characters, and password complexity. The application software reads the chipID and IMEI from the LTE communication module, imports a certain random number according to customer requirements, and finally generates a 10-16 digit password key, imports it into the LTE communication module's memory, and sends the IMEI corresponding to the password to a statistical list for later delivery to the customer, thus realizing the key generation process according to customer needs. The password should contain chipID, IMEI (International Mobile Equipment Identity), and random code information, and some of this information should also be hidden in the code.

[0073] Figure 2 This is a flowchart illustrating a vehicle-to-everything (V2X) product verification method based on an LTE communication module, provided in another exemplary embodiment of this disclosure. In this embodiment, the V2X product verification method based on an LTE communication module is applied to an application terminal, where the LTE communication module communicates with the V2X product application terminal.

[0074] like Figure 2 As shown, the present disclosure of a vehicle-to-everything (V2X) product verification method based on an LTE communication module may include the following steps:

[0075] Step 201: Receive the login request input by the user;

[0076] Step 202: Confirm whether the user is legitimate based on the preset user list;

[0077] Step 203: If valid, receive the login password entered by the user;

[0078] Step 204: Request the first key packet file from the LTE communication module;

[0079] In some embodiments, a request can be sent to the LTE communication module via the QMI interface to obtain the first key packet file.

[0080] Step 205: Determine whether the login password is valid based on the first key packet file;

[0081] In some embodiments, step 205 may specifically be: performing AES256 encoding on the first key packet file.

[0082] The decryption process yields the first ciphertext, the chipID of the LTE communication module component chip, the LTE communication module production code, and a second checksum, which is a cyclic redundancy checksum, from the first key packet file. The correctness of the LTE communication module component chipID, the LTE communication module production code, and the second checksum is then determined. If the LTE communication module component chipID, the LTE communication module production code, and the second checksum are correct, the validity of the login password is determined based on the first ciphertext.

[0083] Step 206: If the login request is valid, then proceed with the login request and return the login result.

[0084] The login password is encrypted using SHA256 to obtain the second password ciphertext; the first password is then determined.

[0085] Check if the ciphertext matches the second ciphertext; if they match, confirm that the login password is valid.

[0086] To enable those skilled in the art to clearly and accurately understand the technical solutions of the embodiments of this disclosure, the following will be explained in conjunction with the interactive diagrams (see...). Figure 6 The embodiments of this disclosure will be described in detail below.

[0087] Figure 6This is a schematic diagram of the interaction flow of a vehicle-to-everything (V2X) product verification method based on an exemplary embodiment of this disclosure. The diagram details the key generation process and the user login process. During key generation, user customization of the key is implemented. Specifically, an input interface is provided so that the user can input information such as password length, password complexity, fixed characters, the chip ID of the LTE communication module, and the LTE communication module production code. In addition, a random code (which can be any character and length) can be generated from a general operating system. Then, a first password is generated based on the password length, password complexity, and fixed characters. The first password is then encrypted using SHA256 to obtain the first password ciphertext. The LTE communication module chip ID is incorporated into the first password ciphertext. The first cryptographic packet is generated by packaging information such as the LTE communication module production code and the preset International Mobile Equipment Identity (IMEI) information into a first cryptographic ciphertext file. A CRC checksum is calculated using a random code, and this CRC checksum is then used to verify the first cryptographic packet, resulting in a first cryptographic verification packet. This first cryptographic verification packet is then encrypted using AES256 to obtain the first key file (i.e., the customer-customized key). During production, the first key file can be stored in a memory segment of the modem of the corresponding device based on the LTE communication module production code and other information, thus completing the generation of the user-customized key. In the vehicle-to-everything (V2X) product application, if a user needs to log in, they can enter a username to confirm their login request. The system can then verify the user's legitimacy against a preset user list, for example, by checking if the username is in the list. If it is, the username is valid; otherwise, it is invalid, and the user is forced to log out.After verifying the username's validity, the user is prompted to enter a login password. Upon entering the password, a request is sent to the LTE communication module via the QMI interface to retrieve the first key packet file from the LTE communication module's modem memory. The first key packet file is then decrypted using AES256 to obtain the first ciphertext, the LTE communication module chip ID, the LTE communication module production code, and a second checksum (a Cyclic Redundancy Checksum). The second checksum is then verified against the first checksum to confirm the correctness of the LTE communication module chip ID, production code, IMEI, and other information. If incorrect, the user is logged out. Otherwise, the login password is further encrypted using SHA256 to obtain the second ciphertext. The second ciphertext is then verified against the first ciphertext (e.g., whether they match; if they match, the login password is valid; otherwise, it is invalid). In some embodiments, the encrypted second ciphertext can be passed to a shadow plugin, which checks whether the first and second ciphertexts match. If they match, the user is allowed to log in.

[0088] In summary, the disclosed technical solution reduces the risk of theft of vehicle networking products. In addition, the use of encryption keys for verification prevents users or intruders from directly seeing the original key text, thus maximizing information security.

[0089] In detail, when a customer requests to enable one device, one password, the application reads the chipID, IMEI, and key during the LTE communication module's power-on phase and saves them in an invisible form that is inaccessible to users other than the administrator. When the customer is logging in and has entered their username and password, the application decrypts the key, calculates the checksum, and compares it for consistency. If they match, it means the password packet was obtained correctly or has not been tampered with. Then, the application compares the chipID and IMEI contained in the password packet to see if it is a one-to-one password packet entered on the production line. If both are correct, the application adds a password portion hidden in the code as requested by the customer and directly performs irreversible SHA256 encryption. This is then sent to the shadow for SHA256 key comparison, and finally, the password input is confirmed to be correct. This allows for flexible switching of the login verification method according to customer needs. This solves the defects of existing login verification methods by generating a unique key externally and then passing it into a memory segment of the LTE communication module, reducing the risk of theft. During verification, the key is decrypted and presented as a SHA256 key in the Linux verification system, so that users or intruders cannot see the original key text directly, thus maximizing information security.

[0090] Exemplary device

[0091] Figure 3 This is a schematic diagram of a vehicle-to-everything (V2X) product verification device based on an exemplary embodiment of this disclosure. The device is applied to an LTE communication module, which includes a modem. The LTE communication module communicates with a V2X product application terminal. The device includes:

[0092] The first receiving module 31 is used to receive a key generation instruction input by the user of the vehicle networking product application terminal. The key generation instruction includes password length, password complexity, fixed characters, chipID of the LTE communication module component chip, and LTE communication module production code.

[0093] The first generation module 32 is used to generate a first password based on the password length, the password complexity, and the fixed characters;

[0094] The first encryption module 33 is used to encrypt the first password using SHA256 to obtain the first password ciphertext;

[0095] The second generation module 34 is used to package the first ciphertext, the chipID of the LTE communication module component chip, the LTE communication module production code, and the preset International Mobile Equipment Identity (IMEI) information to generate the first ciphertext packet.

[0096] The third generation module 35 is used to obtain a random code from a general operating system to verify the first password packet and obtain a first password verification packet.

[0097] The second encryption module 36 is used to encrypt the first password verification packet to obtain a first key packet file. The first key packet file is used to verify the user's login password when the user enters a login request, so as to determine the legitimacy of the user.

[0098] Storage module 37 is used to store the first key packet file into the modem memory.

[0099] Figure 4 This is a schematic diagram of a vehicle-to-everything (V2X) product verification device based on an LTE communication module, provided in another exemplary embodiment of this disclosure. The device is applied to an application terminal, which communicates with the LTE communication module. The device includes:

[0100] The second receiving module 41 is used to receive login requests input by the user;

[0101] The first legitimacy verification module 42 is used to verify whether the user is legitimate based on a preset user list;

[0102] The third receiving module 43 is used to receive the login password entered by the user if it is valid;

[0103] The acquisition module 44 is used to request the first key packet file from the LTE communication module;

[0104] The second validity verification module 45 is used to determine whether the login password is valid based on the first key packet file;

[0105] Return module 46 is used to return the login result if the login request is valid.

[0106] The apparatus and method provided in this disclosure have the same principle and effect, and will not be described again here.

[0107] Exemplary electronic devices

[0108] Below, for reference Figure 5 This describes an electronic device according to embodiments of the present disclosure. The electronic device may be either or both of a first device and a second device, or a standalone device independent of them, which may communicate with the first device and the second device to receive acquired input signals from them.

[0109] Figure 5 A block diagram of an electronic device according to an embodiment of the present disclosure is shown.

[0110] like Figure 5 As shown, the electronic device includes one or more processors 501 and memory 502.

[0111] The processor 501 may be a central processing unit (CPU) or other form of processing unit with LTE communication module-based vehicle networking product verification and / or instruction execution capabilities, and may control other components in the electronic device to perform the desired functions.

[0112] The memory 502 may include one or more computer program products, which may include various forms of computer-readable storage media, such as volatile memory and / or non-volatile memory. The volatile memory may include, for example, random access memory (RAM) and / or cache memory. The non-volatile memory may include, for example, read-only memory (ROM), hard disk, flash memory, etc. One or more computer program instructions may be stored on the computer-readable storage medium, and the processor 501 may execute the program instructions to implement the steps related to the verification of the LTE communication module-based vehicle networking product in the various embodiments of this disclosure described above, and / or other desired functions. Various contents such as input signals, signal components, and noise components may also be stored in the computer-readable storage medium.

[0113] In one example, the electronic device may also include an input device 503 and an output device 504, which are interconnected via a bus system and / or other forms of connection mechanism (not shown).

[0114] For example, when the electronic device is a first device or a second device, the input device 503 can be the microphone or microphone array described above, used to capture the input signal from the sound source. When the electronic device is a standalone device, the input device 503 can be a communication network connector, used to receive the acquired input signals from the first device and the second device.

[0115] In addition, the input device 503 may also include, for example, a keyboard, a mouse, etc.

[0116] The output device 504 can output various information to the outside, including determined distance information, direction information, etc. The output device 504 may include, for example, a display, a speaker, a printer, and a communication network and its connected remote output devices, etc.

[0117] Of course, for the sake of simplicity, Figure 5 Only some of the components of the electronic device relevant to this disclosure are shown, omitting components such as buses, input / output interfaces, etc. In addition, the electronic device may include any other suitable components depending on the specific application.

[0118] Exemplary computer program products and computer-readable storage media

[0119] In addition to the methods and devices described above, embodiments of this disclosure may also be computer program products, which include computer program instructions that, when executed by a processor, cause the processor to perform the steps related to vehicle networking product verification based on an LTE communication module according to various embodiments of this disclosure as described in the "Exemplary Methods" section of this specification.

[0120] The computer program product can be written in any combination of one or more programming languages ​​to perform the operations of the embodiments of this disclosure. The programming languages ​​include object-oriented programming languages ​​such as Java and C++, as well as conventional procedural programming languages ​​such as C or similar languages. The program code can be executed entirely on a user's computing device, partially on a user's computing device, as a standalone software package, partially on a user's computing device and partially on a remote computing device, or entirely on a remote computing device or server.

[0121] Furthermore, embodiments of this disclosure may also be computer-readable storage media storing computer program instructions that, when executed by a processor, cause the processor to perform steps related to vehicle-to-everything (V2X) product verification based on LTE communication modules as described in the "Exemplary Methods" section of this specification, according to various embodiments of this disclosure.

[0122] The computer-readable storage medium may be any combination of one or more readable media. A readable medium may be a readable signal medium or a readable storage medium. A readable storage medium may be, for example, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination thereof. More specific examples of readable storage media (a non-exhaustive list) include: an electrical connection having one or more wires, a portable disk, a hard disk, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), optical storage device, magnetic storage device, or any suitable combination thereof.

[0123] The basic principles of this disclosure have been described above with reference to specific embodiments. However, it should be noted that the advantages, benefits, and effects mentioned in this disclosure are merely examples and not limitations, and should not be considered as essential features of each embodiment of this disclosure. Furthermore, the specific details disclosed above are for illustrative and facilitative purposes only, and are not limitations. These details do not limit the scope of this disclosure to the necessity of employing the aforementioned specific details for implementation.

[0124] The various embodiments in this specification are described in a progressive manner, with each embodiment focusing on its differences from other embodiments. Similar or identical parts between embodiments can be referred to interchangeably. For system embodiments, since they largely correspond to method embodiments, the description is relatively simple; relevant parts can be referred to the descriptions in the method embodiments.

[0125] The block diagrams of devices, apparatuses, devices, and systems disclosed herein are merely illustrative examples and are not intended to require or imply that they must be connected, arranged, or configured in the manner shown in the block diagrams. As those skilled in the art will recognize, these devices, apparatuses, devices, and systems can be connected, arranged, and configured in any manner. Words such as “comprising,” “including,” “having,” etc., are open-ended terms meaning “including but not limited to,” and are used interchangeably with them. The terms “or” and “and” as used herein refer to the terms “and / or,” and are used interchangeably with them unless the context clearly indicates otherwise. The term “such as” as used herein refers to the phrase “such as but not limited to,” and is used interchangeably with it.

[0126] The methods and apparatus of this disclosure may be implemented in many ways. For example, they may be implemented by software, hardware, firmware, or any combination of software, hardware, and firmware. The above-described order of steps for the methods is for illustrative purposes only, and the steps of the methods of this disclosure are not limited to the order specifically described above, unless otherwise specifically stated. Furthermore, in some embodiments, this disclosure may also be implemented as a program recorded on a recording medium, the program including machine-readable instructions for implementing the methods according to this disclosure. Thus, this disclosure also covers recording media storing programs for performing the methods according to this disclosure.

[0127] It should also be noted that in the apparatus, devices, and methods of this disclosure, the components or steps can be disassembled and / or recombined. These disassemblies and / or recombinations should be considered as equivalent solutions to this disclosure.

[0128] The above description of the disclosed aspects is provided to enable any person skilled in the art to make or use this disclosure. Various modifications to these aspects will be readily apparent to those skilled in the art, and the general principles defined herein may be applied to other aspects without departing from the scope of this disclosure. Therefore, this disclosure is not intended to be limited to the aspects shown herein, but rather to be carried out within the widest scope consistent with the principles and novel features disclosed herein.

[0129] The above description has been given for purposes of illustration and description. Furthermore, this description is not intended to limit the embodiments of this disclosure to the forms disclosed herein. Although numerous exemplary aspects and embodiments have been discussed above, those skilled in the art will recognize certain variations, modifications, alterations, additions, and sub-combinations therein.

Claims

1. A method for verifying vehicle-to-everything (V2X) products based on an LTE communication module, applied to an application terminal, wherein the application terminal communicates with the LTE communication module, characterized in that... The method includes: Receive login requests from users; Confirm the legitimacy of the user based on the preset user list; If valid, accept the login password entered by the user; Request the first key packet file from the LTE communication module; Determine whether the login password is valid based on the first key package file; If the request is valid, the login request will be approved and a login result will be returned.

2. The method according to claim 1, characterized in that, The step of requesting the first key packet file from the LTE communication module includes: A request is sent to the LTE communication module via the QMI interface to obtain the first key packet file.

3. The method according to claim 1, characterized in that, The step of determining whether the login password is valid based on the first key packet file includes: The first key packet file is decrypted using AES256 to obtain the first ciphertext, the chipID of the LTE communication module component chip, and the LTE communication module production code from the first key packet file. The second check code is calculated, and the second check code is a cyclic redundancy check code. Determine whether the chipID of the LTE communication module component chip, the LTE communication module production code, and the second check code are correct; If the chipID of the LTE communication module component chip, the production code of the LTE communication module, and the second verification code are correct, then the validity of the login password is determined based on the first ciphertext.

4. The method according to claim 3, characterized in that, The step of determining whether the login password is valid based on the first ciphertext includes: The login password is encrypted using SHA256 to obtain the second password ciphertext; Determine whether the first ciphertext and the second ciphertext are consistent; If they match, then the login password is confirmed to be valid.

5. A vehicle-to-everything (V2X) product verification device based on an LTE communication module, applied at an application end, wherein the application end communicates with the LTE communication module, characterized in that, The device includes: The second receiving module is used to receive login requests input by the user; The first legitimacy verification module is used to verify whether the user is legitimate based on a preset user list; The third receiving module is used to receive the login password entered by the user if it is valid; The acquisition module is used to request the first key packet file from the LTE communication module; The second validity verification module is used to determine whether the login password is valid based on the first key package file; The return module is used to process the login request and return the login result if it is valid.

Images