Vehicle information authentication method, device, equipment and storage medium

Abstract

The present invention belongs to the field of automobile technology, and discloses a vehicle-mounted information authentication method, device, equipment and storage medium; the method is applied to a manufacturing management unit in a vehicle-mounted information authentication system, and the manufacturing management unit is connected to a cloud via an intranet, and the method comprises: obtaining a whole vehicle authentication information code of a target vehicle; verifying the validity of the whole vehicle authentication information code to obtain a verification result; when the verification result is successful, sending the whole vehicle authentication information to the cloud via the intranet for vehicle-mounted information authentication; the present invention verifies the validity of the whole vehicle authentication information by the manufacturing management unit when the vehicle-mounted information requires whole vehicle authentication, and when the verification is successful, transmits the whole vehicle authentication information from the intranet to the cloud via the manufacturing management unit, and does not need to transmit information via an external network via TBOX, thereby solving the problem of information authentication failure caused by vehicle data transmission when the external network is unstable, and performing vehicle-mounted information authentication more safely, accurately and effectively.

Description

Technical Field

[0001] The present invention relates to the field of automobile technology, and in particular to a vehicle-mounted information authentication method, device, equipment and storage medium. Background Art

[0002] With the development of electric vehicles, people's demand for remote control functions of cars is gradually increasing. EOL (End of Line) is a solution for engine or car OEM (OEM is the abbreviation of Original Equipment Manufacturer, Chinese called "Original Equipment Manufacturer" or "Branded Manufacturer") manufacturers to manage the production of engines and vehicle ECUs (ECU (Electronic Control Unit) means electronic control unit, also known as "driving computer", "on-board computer", etc.). It usually refers to flashing software code and data into ECU before ECU leaves the factory, and uniformly storing and managing production plans, ECU data, work processes, parts information, etc. based on the database.

[0003] When the vehicle rolls off the assembly line or when the internal functional equipment of the vehicle is updated, it is necessary to associate the internal equipment with the vehicle to realize remote start of the vehicle, remote opening and closing of the air conditioner, Bluetooth unlocking, automatic parking, automatic driving, etc.

[0004] At present, when the vehicle is off the assembly line, the diagnostic instructions of the EOL (End of line) electrical inspection program are directly triggered by the TBOX (Telematics BOX, telematics processor) to upload the vehicle remote control authentication related information (vehicle identification number, full name Vehicle Identification Number, abbreviated VIN), integrated circuit card identification code (full name Integrated circuit card identity, ICCID abbreviation), machine serial number (full name Serial Number, abbreviated SN), media access control address (full name Media Access Control Address, abbreviated MAC address), etc. to the background, and wait for the background to return the result. This path mainly involves data transmission between the TBOX network (external network) and the background (intranet). Summary of the invention

[0005] The main purpose of the present invention is to provide a vehicle-mounted information authentication method, device, equipment and storage medium, aiming to solve the technical problem in the prior art that vehicle data transmission suffers from external network instability resulting in information authentication failure.

[0006] To achieve the above object, the present invention provides a vehicle information authentication method, which is applied to a manufacturing management unit in a vehicle information authentication system. The system includes an electric inspection unit and a manufacturing management unit. The manufacturing management unit is connected to the cloud via an intranet. The method includes:

[0007] Obtaining a vehicle certification information code of the target vehicle, wherein the vehicle certification information is sent by the electrical inspection unit;

[0008] Verifying the validity of the vehicle authentication information code to obtain a verification result;

[0009] When the verification result is successful, the vehicle authentication information is sent to the cloud through the intranet for vehicle information authentication.

[0010] Optionally, the performing validity verification on the vehicle authentication information code to obtain a verification result includes:

[0011] Determining a sending state of the vehicle authentication information code, wherein the sending state includes a new mode and a partial update mode;

[0012] Based on the sending status, the uniqueness and length of the vehicle authentication information code are verified through a maintained database to obtain a verification result, and the maintained database includes the uploaded vehicle authentication information code.

[0013] Optionally, when the verification result is successful, after sending the vehicle authentication information to the cloud through the intranet for vehicle information authentication, the method further includes:

[0014] When the sending state is a brand new mode and the verification result is a successful verification, a successful verification result code is fed back to the electric inspection unit, and the vehicle authentication information is added to the maintained database;

[0015] When the sending state is a brand new mode and the verification result is a verification failure, a verification failure result code is fed back to the electrical inspection unit.

[0016] Optionally, when the sending state is a brand new mode and the verification result is a successful verification, after feeding back a verification failure result code to the electrical inspection unit, the method further includes:

[0017] When the vehicle authentication information is repeatedly received, identifying the VIN code in the vehicle authentication information;

[0018] The VIN code and the verification failure result code are sent to the electrical inspection unit.

[0019] Optionally, when the verification result is successful, after sending the vehicle authentication information to the cloud through the intranet for vehicle information authentication, the method further includes:

[0020] When the sending state is in partial update mode and the verification result is successful verification, feeding back a successful verification result code to the electric inspection unit, and updating the maintained database according to the vehicle authentication information;

[0021] When the sending state is the partial update mode and the verification result is verification failure, a verification failure result code is fed back to the electrical inspection unit.

[0022] Optionally, updating the maintained database according to the vehicle authentication information includes:

[0023] Identify the VIN code in the vehicle certification information;

[0024] searching the maintained database for an associated code according to the VIN code;

[0025] The association code is updated according to the vehicle authentication information.

[0026] Optionally, obtaining the vehicle authentication information code sent by the electrical inspection unit includes:

[0027] Obtain the vehicle certification information code sent by the electrical inspection unit, the vehicle certification information code including: VIN code, ICCID, SN number;

[0028] When the verification result is successful, the vehicle authentication information is sent to the cloud through the intranet for vehicle information authentication, including:

[0029] When the verification result is successful, the whole vehicle authentication information is sent to the cloud through the intranet for vehicle information authentication, so that the cloud can bind the ICCID and SN number of the target vehicle with the VIN code of the vehicle to realize vehicle information authentication.

[0030] In addition, to achieve the above-mentioned purpose, the present invention also proposes a vehicle-mounted information authentication device, the vehicle-mounted information authentication device comprising:

[0031] An acquisition module is used to acquire the vehicle certification information code of the target vehicle, wherein the vehicle certification information is sent by the electric inspection unit;

[0032] A verification module, used to verify the validity of the vehicle authentication information code and obtain a verification result;

[0033] The information authentication module is used to send the vehicle authentication information to the cloud through the intranet for vehicle information authentication when the verification result is successful.

[0034] In addition, to achieve the above-mentioned purpose, the present invention also proposes a vehicle-mounted information authentication device, which includes: a memory, a processor, and a vehicle-mounted information authentication program stored on the memory and executable on the processor, and the vehicle-mounted information authentication program is configured to implement the steps of the vehicle-mounted information authentication method described above.

[0035] In addition, to achieve the above-mentioned purpose, the present invention also proposes a storage medium, on which a vehicle information authentication program is stored, and when the vehicle information authentication program is executed by a processor, the steps of the vehicle information authentication method described above are implemented.

[0036] The present invention verifies the validity of the whole vehicle authentication information by the manufacturing management unit when the on-board information requires whole vehicle authentication. When the authentication is successful, the whole vehicle authentication information is transmitted from the intranet to the cloud through the manufacturing management unit, and there is no need to transmit the information through the external network through TBOX. This solves the problem of information authentication failure caused by vehicle data transmission when the external network is unstable, and performs on-board information authentication more safely, accurately and effectively. BRIEF DESCRIPTION OF THE DRAWINGS

[0037] Figure 1 It is a structural diagram of a vehicle information authentication device in a hardware operating environment involved in an embodiment of the present invention;

[0038] Figure 2 It is a flowchart of the first embodiment of the vehicle information authentication method of the present invention;

[0039] Figure 3 A data link comparison diagram of the first embodiment of the vehicle information authentication method of the present invention;

[0040] Figure 4 It is a flowchart of a second embodiment of the vehicle information authentication method of the present invention;

[0041] Figure 5 It is a structural block diagram of the first embodiment of the vehicle-mounted information authentication device of the present invention.

[0042] The realization of the purpose, functional features and advantages of the present invention will be further explained in conjunction with embodiments and with reference to the accompanying drawings. DETAILED DESCRIPTION

[0043] It should be understood that the specific embodiments described herein are only used to explain the present invention, and are not used to limit the present invention.

[0044] Reference Figure 1 , Figure 1 The diagram is a structural diagram of an in-vehicle information authentication device in a hardware operating environment involved in an embodiment of the present invention.

[0045] like Figure 1As shown, the vehicle information authentication device may include: a processor 1001, such as a central processing unit (CPU), a communication bus 1002, a user interface 1003, a network interface 1004, and a memory 1005. Among them, the communication bus 1002 is used to realize the connection and communication between these components. The user interface 1003 may include a display screen (Display), an input unit such as a keyboard (Keyboard), and the optional user interface 1003 may also include a standard wired interface and a wireless interface. The network interface 1004 may optionally include a standard wired interface and a wireless interface (such as a wireless fidelity (Wireless-Fidelity, Wi-Fi) interface). The memory 1005 may be a high-speed random access memory (Random Access Memory, RAM), or a stable non-volatile memory (Non-Volatile Memory, NVM), such as a disk storage. The memory 1005 may also be a storage device independent of the aforementioned processor 1001.

[0046] Those skilled in the art will understand that Figure 1 The structure shown in does not constitute a limitation on the vehicle-mounted information authentication device, and may include more or fewer components than shown in the figure, or a combination of certain components, or a different arrangement of components.

[0047] like Figure 1 As shown, the memory 1005 as a storage medium may include an operating system, a network communication module, a user interface module, and a vehicle information authentication program.

[0048] exist Figure 1 In the vehicle-mounted information authentication device shown, the network interface 1004 is mainly used for data communication with the network server; the user interface 1003 is mainly used for data interaction with the user; the processor 1001 and the memory 1005 in the vehicle-mounted information authentication device of the present invention can be set in the vehicle-mounted information authentication device, and the vehicle-mounted information authentication device calls the vehicle-mounted information authentication program stored in the memory 1005 through the processor 1001, and executes the vehicle-mounted information authentication method provided by the embodiment of the present invention.

[0049] The embodiment of the present invention provides a vehicle information authentication method, referring to Figure 2 , Figure 2 FIG. 1 is a flow chart of a first embodiment of a vehicle information authentication method according to the present invention.

[0050] In this embodiment, the vehicle information authentication method includes the following steps:

[0051] Step S10: Acquire the vehicle authentication information code of the target vehicle, wherein the vehicle authentication information is sent by the electrical inspection unit.

[0052] It should be noted that the vehicle certification information code may include: VIN code, ICCID, and SN number.

[0053] It should be emphasized that the vehicle authentication information code is sent by the electronic inspection unit, and the electronic inspection unit obtains it from various functional modules or controllers of the vehicle through DID instructions.

[0054] It is understandable that DID instructions may refer to instructions or commands related to digital identity (Decentralized Identifier). Digital identity is an emerging identification method that aims to provide digital identity for individuals, organizations, devices or entities without relying on a centralized registration agency. In the application of DID, there may be a variety of instructions or commands involved for creating, managing, resolving and verifying digital identities.

[0055] In a specific implementation, the electric inspection unit of the present application obtains the vehicle authentication information N code through the DID instruction and uploads it to the manufacturing management unit; it is understandable that a specific DID instruction may be an instruction generated for the information to be obtained.

[0056] It should be emphasized that in the prior art, the electric inspection unit obtains the vehicle authentication information N code through the DID instruction (sends a specific DID instruction to the Internet of Vehicles controller TBOX to obtain its VIN code, ICCID, SN number; sends a specific DID instruction to the Bluetooth controller BLE to obtain its MAC address, SEID code, SN number; sends a specific DID instruction to the vehicle controller IVI to obtain its MAC address and SN number; sends a specific DID instruction to the intelligent driving controller TDA4 to obtain the SN number), and stores it in TBOX through a specific DID instruction. N number; sends a specific DID instruction to the intelligent driving controller TDA4 to obtain the SN number

[0057] Step S20: verify the validity of the vehicle authentication information code to obtain a verification result.

[0058] It is understandable that the verification of the validity of the vehicle authentication information code includes verifying the vehicle authentication information code (VIN code, ICCID, SN number) separately.

[0059] It should be understood that verifying the validity of the vehicle information code may be verifying the uniqueness of the vehicle information code in the maintained database and verifying the length of the vehicle information code.

[0060] It should be noted that when the uniqueness is successful and the length verification is consistent, the authentication of the vehicle authentication information code is considered to be successful. If the uniqueness verification fails or the length verification fails, the authentication of the vehicle authentication information code is considered to have failed.

[0061] Step S30: When the verification result is successful, the vehicle authentication information is sent to the cloud through the intranet for vehicle information authentication.

[0062] It is understandable that the verification result may be verification success or verification failure. At the same time, the verification result needs to be fed back to the electrical inspection unit when the verification succeeds or fails. The verification result may be fed back in a decoding manner.

[0063] It should be understood that what the present application wants to emphasize is that data transmission between the manufacturing unit and the cloud is carried out through the intranet, so there will be no series of problems caused by network instability in the prior art. The verification of the vehicle authentication information can be carried out by the manufacturing management unit, and data binding can be carried out in the cloud.

[0064] It is understandable that the verification of vehicle authentication information is a step in the authentication of vehicle information, and finally it still needs to be uploaded to the cloud for binding. If the binding is successful, the associated control of the vehicle functions can be carried out.

[0065] It should be noted that when the verification result is successful, the vehicle authentication information is sent to the cloud through the intranet for vehicle information authentication, so that the cloud can bind the ICCID, SN number of the target vehicle with the VIN code of the vehicle to realize vehicle information authentication.

[0066] It should be noted that in the prior art, TBOX uploads N codes to the cloud upon receiving a DID instruction, and the TBOX software is pre-set with the data transmission interface address of the cloud. Compared with the prior art, the electric inspection unit triggers TBOX to upload N codes to the cloud through a specific DID instruction, and the cloud verifies the validity of the N code. The electric inspection unit obtains the result code from TBOX through the DID instruction (for example, during the upload of 0x3, 0x2 succeeds, and 0x5 fails), and determines whether the upload is successful or failed based on the result code; the existing solution completely relies on the data transmission between the external network (TBOX network) and the company's intranet (DCVP network), and there are problems such as unstable TBOX network and unstable network connection between the two parties, which lead to problems such as failure to upload information and long information transmission time. This in turn affects the quality of the vehicle and causes problems such as waste of repairs.

[0067] It should be emphasized that during the vehicle off-line process of this application, the diagnostic instructions of the electrical inspection unit are used to obtain the vehicle remote control authentication related information (VIN code, ICCID, SN, MAC address, etc.) and upload it to the manufacturing management unit (manufacturing management system), and the manufacturing management unit transmits the result back. After the vehicle passes the PDI electrical inspection, the DCVP background obtains the vehicle remote control authentication information from the manufacturing management unit for authentication. This path mainly involves data transmission between the electrical inspection unit (intranet) and the manufacturing management unit (intranet), and between the manufacturing management unit (intranet) and the DCVP background (intranet). It can effectively solve problems such as external network instability, thereby avoiding a series of problems such as information authentication failure. In order to more clearly reflect the difference between this application and the prior art, please refer to Figure 3 , Figure 3 It is a data link comparison diagram, wherein the electrical inspection unit can be simply understood as the electrical inspection unit in this application, and the manufacturing management unit can be understood as the manufacturing management unit in this application.

[0068] In this embodiment, when the on-board information requires vehicle authentication, the manufacturing management unit verifies the validity of the vehicle authentication information. When the verification is successful, the manufacturing management unit transmits the vehicle authentication information from the intranet to the cloud, without the need to transmit information through the external network through TBOX. This solves the problem of information authentication failure caused by vehicle data transmission when the external network is unstable, and performs on-board information authentication more safely, accurately and effectively.

[0069] refer to Figure 4 , Figure 4 FIG. 1 is a flow chart of a second embodiment of a vehicle information authentication method according to the present invention.

[0070] Based on the first embodiment, the vehicle information authentication method of this embodiment includes, in step S20:

[0071] Step S21: Determine the sending status of the vehicle authentication information code, where the sending status includes a new mode and a partial update mode.

[0072] It is understandable that the vehicle authentication information code is sent from the electrical inspection unit to the manufacturing management unit, wherein the information sent by the electrical inspection unit can be sent by different electrical inspection stations, and the vehicle authentication information sent by different electrical inspection stations represents different meanings.

[0073] In a specific implementation, the electric inspection station of the electric inspection unit can be divided into a mode1 station, a mode2 station, etc., wherein the mode1 station can represent that the sending state is a brand new mode, and the mode2 station can represent that the sending state is a partial update mode.

[0074] It should be noted that, upon receiving the vehicle authentication information code, the manufacturing management unit can identify the electrical inspection station that sent the authentication information and thus identify the sending status.

[0075] It should be emphasized that the new mode can be understood as the authentication information code of a new vehicle for binding the entire vehicle control, and the partial update mode can be understood as the information of one of the vehicle's controllers needs to be updated or changed and then needs to be re-bound.

[0076] Step S22: Based on the sending status, the uniqueness and length of the vehicle authentication information code are verified through a maintained database to obtain a verification result, and the maintained database includes the uploaded vehicle authentication information code.

[0077] It is understandable that the maintained database may be a database storing information such as the vehicle VIN code, ICCID, SN number, etc. that has been uploaded by each vehicle.

[0078] It should be noted that when the verification result is successful verification, after sending the whole vehicle authentication information to the cloud through the intranet for vehicle information authentication, it also includes: when the sending status is a new mode and the verification result is successful verification, feedback the verification success result code to the electrical inspection unit, and add it to the maintained database according to the whole vehicle authentication information; when the sending status is a new mode and the verification result is a verification failure, feedback the verification failure result code to the electrical inspection unit.

[0079] Among them, it should be emphasized that when the sending state is a new mode and the verification result is a successful verification, after the verification failure result code is fed back to the electrical inspection unit, it also includes: when the whole vehicle authentication information is repeatedly received, identifying the VIN code in the whole vehicle authentication information; sending the VIN code and the verification failure result code to the electrical inspection unit.

[0080] In a specific implementation, if the N code is uploaded by the electrical inspection unit in mode1, its uniqueness and length will be verified based on the data maintained by the manufacturing management unit. If the verification is qualified, it will be added to the system database for maintenance. If the verification fails, an error will be reported and fed back to the electrical inspection unit. If the N code is uploaded in mode1 repeatedly, an error message of VIN code conflict will be reported and fed back to the electrical inspection unit. It can be understood that the N code can be the vehicle authentication information described in this embodiment.

[0081] It should be further explained that when the verification result is successful verification, after sending the whole vehicle authentication information to the cloud through the intranet for vehicle information authentication, it also includes: when the sending status is partial update mode and the verification result is successful verification, feedback the verification success result code to the electrical inspection unit, and update the maintained database data according to the whole vehicle authentication information; when the sending status is partial update mode and the verification result is failed verification, feedback the verification failure result code to the electrical inspection unit.

[0082] Among them, it should be emphasized that the data updating of the maintained database according to the vehicle authentication information includes: identifying the VIN code in the vehicle authentication information; searching for the association code of the maintained database according to the VIN code; and updating the association code according to the vehicle authentication information.

[0083] In the specific implementation, if the N code is uploaded in mode2, the length of the N code will be checked to see if it is OK, and the uniqueness will be checked based on the data maintained by the manufacturing management unit (because only the information of some control functions needs to be updated at this time, the previous authentication information of the vehicle has been saved in the maintained database, and the verification of the whole vehicle authentication information through the maintained database at this time needs to exclude the authentication information that has been uploaded to the cloud). After the length and uniqueness verification is successful, the VIN code is used as the index to update other codes (for example, the ICCID and other codes bound to the VIN code can be found through the VIN code). If the verification error occurs, the corresponding result code will be fed back to the electronic inspection unit.

[0084] It should be noted that before execution, the electrical inspection unit obtains the result code (for example, 01 verification passed, 02 verification failed) from the manufacturing management unit through the data transmission interface to determine whether the upload is successful or failed; when the verification is successful, the manufacturing management unit sends the vehicle authentication information to the cloud. Since the codes are in a scattered state in each controller before loading, they need to be bound to the vehicle's VIN code after loading. After the cloud synchronizes the vehicle's N code information, the vehicle can be remotely started, the air conditioner can be remotely turned on and off, Bluetooth unlocked, automatic parking, automatic driving, etc.

[0085] In this embodiment, the manufacturing management unit identifies the authentication information mode that needs to be bound based on the difference in authentication information at the sending port of the electrical inspection unit, verifies the uniqueness and length of the vehicle authentication information based on different modes in the manufacturing management unit, and binds the authentication information based on the verification result fed back to the cloud through the intranet, thereby quickly completing the vehicle information authentication and avoiding the problem of information authentication failure or slow information authentication due to poor external network signals and errors in information transmission.

[0086] Reference Figure 5 , Figure 5 It is a structural block diagram of the first embodiment of the vehicle-mounted information authentication device of the present invention.

[0087] like Figure 5 As shown, the vehicle information authentication device proposed in the embodiment of the present invention includes:

[0088] The acquisition module 10 is used to acquire the vehicle certification information code of the target vehicle, and the vehicle certification information is sent by the electric inspection unit;

[0089] The verification module 20 is used to verify the validity of the vehicle authentication information code and obtain a verification result;

[0090] The information authentication module 30 is used to send the vehicle authentication information to the cloud through the intranet for vehicle information authentication when the authentication result is successful.

[0091] In this embodiment, when the on-board information requires vehicle authentication, the manufacturing management unit verifies the validity of the vehicle authentication information. When the verification is successful, the manufacturing management unit transmits the vehicle authentication information from the intranet to the cloud, without the need to transmit information through the external network through TBOX. This solves the problem of information authentication failure caused by vehicle data transmission when the external network is unstable, and performs on-board information authentication more safely, accurately and effectively.

[0092] In one embodiment, the verification module 20 is further used to determine the sending state of the vehicle authentication information code, and the sending state includes a new mode and a partial update mode;

[0093] Based on the sending status, the uniqueness and length of the vehicle authentication information code are verified through a maintained database to obtain a verification result, and the maintained database includes the uploaded vehicle authentication information code.

[0094] In one embodiment, the verification module 20 is further used to feed back a verification success result code to the electric inspection unit when the sending state is a new mode and the verification result is a verification success, and add the vehicle authentication information to the maintained database;

[0095] When the sending state is a brand new mode and the verification result is a verification failure, a verification failure result code is fed back to the electrical inspection unit.

[0096] In one embodiment, the verification module 20 is further used to identify the VIN code in the vehicle authentication information when the vehicle authentication information is repeatedly received;

[0097] The VIN code and the verification failure result code are sent to the electrical inspection unit.

[0098] In one embodiment, the verification module 20 is further used to feed back a verification success result code to the electric inspection unit when the sending state is a partial update mode and the verification result is a verification success, and update the maintained database according to the vehicle authentication information;

[0099] When the sending state is the partial update mode and the verification result is verification failure, a verification failure result code is fed back to the electrical inspection unit.

[0100] In one embodiment, the verification module 20 is further used to identify the VIN code in the vehicle authentication information;

[0101] searching the maintained database for an associated code according to the VIN code;

[0102] The association code is updated according to the vehicle authentication information.

[0103] In one embodiment, the acquisition module 10 is further used to acquire the vehicle authentication information code sent by the electric inspection unit, and the vehicle authentication information code includes: VIN code, ICCID, SN number;

[0104] In one embodiment, the information authentication module 30 is also used to send the vehicle authentication information to the cloud through the intranet for vehicle information authentication when the verification result is successful, so that the cloud can bind the ICCID and SN number of the target vehicle with the VIN code of the vehicle to realize vehicle information authentication.

[0105] In addition, to achieve the above-mentioned purpose, the present invention also proposes a vehicle-mounted information authentication device, which includes: a memory, a processor, and a vehicle-mounted information authentication program stored on the memory and executable on the processor, and the vehicle-mounted information authentication program is configured to implement the steps of the vehicle-mounted information authentication method described above.

[0106] Since the vehicle-mounted information authentication device adopts all the technical solutions of all the above embodiments, it has at least all the beneficial effects brought by the technical solutions of the above embodiments, which will not be described one by one here.

[0107] In addition, an embodiment of the present invention further proposes a storage medium, on which a vehicle information authentication program is stored. When the vehicle information authentication program is executed by a processor, the steps of the vehicle information authentication method described above are implemented.

[0108] Since the storage medium adopts all the technical solutions of all the above embodiments, it has at least all the beneficial effects brought by the technical solutions of the above embodiments, which will not be described one by one here.

[0109] It should be understood that the above is only an example and does not constitute any limitation on the technical solution of the present invention. In specific applications, technicians in this field can make settings as needed, and the present invention does not limit this.

[0110] It should be noted that the workflow described above is merely illustrative and does not limit the scope of protection of the present invention. In practical applications, technicians in this field can select part or all of them according to actual needs to achieve the purpose of the present embodiment, and no limitation is made here.

[0111] In addition, for technical details not fully described in this embodiment, reference may be made to the vehicle information authentication method provided in any embodiment of the present invention, and will not be repeated here.

[0112] In addition, it should be noted that, in this article, the terms "include", "comprises" or any other variations thereof are intended to cover non-exclusive inclusion, so that a process, method, article or system including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or system. In the absence of further restrictions, an element defined by the sentence "comprises a ..." does not exclude the existence of other identical elements in the process, method, article or system including the element.

[0113] It should be understood that, although the various steps in the flowchart in the embodiment of the present application are displayed in sequence according to the indication of the arrows, these steps are not necessarily performed in sequence according to the order indicated by the arrows. Unless there is a clear explanation in this article, the execution of these steps does not have a strict order restriction, and it can be performed in other orders. Moreover, at least a portion of the steps in the figure may include a plurality of sub-steps or a plurality of stages, and these sub-steps or stages are not necessarily performed at the same time, but can be performed at different times, and their execution order is not necessarily performed in sequence, but can be performed in turn or alternately with other steps or at least a portion of the sub-steps or stages of other steps.

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

[0115] Through the description of the above implementation methods, those skilled in the art can clearly understand that the above-mentioned embodiment methods can be implemented by means of software plus a necessary general hardware platform, and of course by hardware, but in many cases the former is a better implementation method. Based on such an understanding, the technical solution of the present invention, or the part that contributes to the prior art, can be embodied in the form of a software product, which is stored in a storage medium (such as a read-only memory (ROM) / RAM, a magnetic disk, or an optical disk), and includes a number of instructions for a terminal device (which can be a mobile phone, a computer, a server, or a network device, etc.) to execute the methods described in each embodiment of the present invention.

[0116] The above are only preferred embodiments of the present invention, and are not intended to limit the patent scope of the present invention. Any equivalent structure or equivalent process transformation made using the contents of the present invention specification and drawings, or directly or indirectly applied in other related technical fields, are also included in the patent protection scope of the present invention.

Claims

1. A vehicle information authentication method, characterized in that: The vehicle information authentication method is applied to a manufacturing management unit in a vehicle information authentication system. The system includes an electric inspection unit and a manufacturing management unit. The manufacturing management unit is connected to the cloud via an intranet. The method includes: Obtaining a vehicle certification information code of the target vehicle, wherein the vehicle certification information is sent by the electrical inspection unit, and the vehicle certification information code includes the ICCID, SN number, and VIN code of the target vehicle; Performing validity verification on the vehicle authentication information code to obtain a verification result, wherein the validity verification includes uniqueness verification and length verification; When the verification result is successful, the vehicle authentication information is sent to the cloud through the intranet for vehicle information authentication; When the verification result is successful, the vehicle authentication information is sent to the cloud through the intranet for vehicle information authentication, including: When the verification result is successful, the whole vehicle authentication information is sent to the cloud through the intranet for vehicle information authentication, so that the cloud can bind the ICCID and SN number of the target vehicle with the VIN code of the vehicle to realize vehicle information authentication.

2. The vehicle information authentication method according to claim 1, characterized in that: The validation of the vehicle authentication information code to obtain a validation result includes: Determining a sending state of the vehicle authentication information code, wherein the sending state includes a new mode and a partial update mode; Based on the sending status, the uniqueness and length of the vehicle authentication information code are verified through a maintained database to obtain a verification result, and the maintained database includes the uploaded vehicle authentication information code.

3. The vehicle information authentication method according to claim 2, characterized in that: When the verification result is successful, after sending the vehicle authentication information to the cloud through the intranet for vehicle information authentication, the method further includes: When the sending state is a brand new mode and the verification result is a successful verification, a successful verification result code is fed back to the electric inspection unit, and the vehicle authentication information is added to the maintained database; When the sending state is a brand new mode and the verification result is a verification failure, a verification failure result code is fed back to the electrical inspection unit.

4. The vehicle information authentication method according to claim 3, characterized in that: When the sending state is a new mode and the verification result is a successful verification, after feeding back a verification failure result code to the electrical inspection unit, the method further includes: When the vehicle authentication information is repeatedly received, identifying the VIN code in the vehicle authentication information; The VIN code and the verification failure result code are sent to the electrical inspection unit.

5. The vehicle information authentication method according to claim 2, characterized in that: When the verification result is successful, after sending the vehicle authentication information to the cloud through the intranet for vehicle information authentication, the method further includes: When the sending state is in partial update mode and the verification result is successful verification, feeding back a successful verification result code to the electric inspection unit, and updating the maintained database according to the vehicle authentication information; When the sending state is the partial update mode and the verification result is verification failure, a verification failure result code is fed back to the electrical inspection unit.

6. The vehicle information authentication method according to claim 5, characterized in that: The updating of the maintained database according to the vehicle authentication information includes: Identify the VIN code in the vehicle certification information; searching the maintained database for an associated code according to the VIN code; The association code is updated according to the vehicle authentication information.

7. A vehicle information authentication device, characterized in that: The vehicle-mounted information authentication device comprises: An acquisition module is used to acquire the vehicle certification information code of the target vehicle, wherein the vehicle certification information is sent by the electric inspection unit, and the vehicle certification information code includes the ICCID, SN number and VIN code of the target vehicle; A verification module, used to verify the validity of the vehicle authentication information code and obtain a verification result, wherein the validity verification includes uniqueness verification and length verification; An information authentication module, used to send the vehicle authentication information to the cloud through the intranet for vehicle information authentication when the authentication result is successful; The information authentication module is further used to send the vehicle authentication information to the cloud through the intranet for vehicle information authentication when the authentication result is successful, including: When the verification result is successful, the whole vehicle authentication information is sent to the cloud through the intranet for vehicle information authentication, so that the cloud can bind the ICCID and SN number of the target vehicle with the VIN code of the vehicle to realize vehicle information authentication.

8. A vehicle information authentication device, characterized in that: The device comprises: a memory, a processor, and a vehicle information authentication program stored in the memory and executable on the processor, wherein the vehicle information authentication program is configured to implement the vehicle information authentication method according to any one of claims 1 to 6.

9. A storage medium, characterized in that: The storage medium stores an in-vehicle information authentication program, and when the in-vehicle information authentication program is executed by the processor, the in-vehicle information authentication method according to any one of claims 1 to 6 is implemented.

Images