A method, system, and device for identity binding and authentication of vehicle-mounted devices.

Abstract

This invention discloses a method, system, and apparatus for binding and authenticating the identity of in-vehicle devices, belonging to the field of engineering vehicle technology. It includes sending an in-vehicle device identity binding request based on a human-machine interface unit (HMI) to a group of in-vehicle devices, and sending an in-vehicle device identity reading request to a group of in-vehicle devices. The in-vehicle device group includes several in-vehicle devices and stores the identity code corresponding to each in-vehicle device for generating a set of in-vehicle device identity codes. It stores a first set of in-vehicle device identity codes fed back by the in-vehicle device group. In response to vehicle power-on, it reads a second set of in-vehicle device identity codes from the in-vehicle device group. It compares the second set of in-vehicle device identity codes with the first set of in-vehicle device identity codes to obtain the in-vehicle device identity authentication result and sends it to the HMI. This invention achieves automatic binding and authentication of in-vehicle device identities by transmitting in-vehicle device identity codes between the in-vehicle control unit and the in-vehicle device group, improving vehicle production efficiency and safety.

Description

Technical Field

[0001] This invention relates to a method, system, and device for binding and authenticating the identity of in-vehicle equipment, belonging to the field of engineering vehicle technology. Background Technology

[0002] In the field of engineering vehicles, by using unique identifiers for core onboard components, such as specific codes and chip information, a stable and unique binding relationship is established between the identifier and the corresponding engineering vehicle through technical means. This is equivalent to building a dedicated "identity association channel" for components / onboard equipment and vehicles.

[0003] When the vehicle is in normal operation, this binding relationship remains effective, ensuring the coordinated operation of the components and the vehicle. However, if the core component is disassembled or replaced, or if its communication with the vehicle control system is interfered with by external factors, resulting in abnormal information transmission, the on-board control unit can promptly detect these abnormalities using preset detection mechanisms, such as real-time comparison of the component's unique identifier with the vehicle binding information and monitoring the stability and integrity of communication signals.

[0004] Upon detecting an anomaly, the vehicle control unit will take corresponding measures according to the pre-set program, such as immediately issuing an alarm signal to remind staff, suspending the function of relevant components to prevent the fault from escalating, or recording abnormal information for subsequent troubleshooting and maintenance, thereby effectively ensuring the operational safety and stability of the engineering vehicle and reducing the risks caused by component malfunctions. Summary of the Invention

[0005] The purpose of this invention is to provide a method, system, and apparatus for binding and authenticating the identity of in-vehicle devices. By transmitting the in-vehicle device identity code between the in-vehicle control unit and the in-vehicle device group, the automatic binding and authentication of the identity of in-vehicle devices is achieved, thereby improving vehicle production efficiency and safety.

[0006] To achieve the above objectives, the present invention is implemented using the following technical solution.

[0007] In a first aspect, the present invention provides a method for binding and authenticating the identity of an in-vehicle device, executed by an in-vehicle control unit, comprising:

[0008] Based on the vehicle device identity binding request sent by the human-computer interaction unit, a vehicle device identity reading request is sent to the vehicle device group; the vehicle device group includes several vehicle devices and stores the identity code corresponding to each vehicle device, which is used to generate a set of vehicle device identity codes.

[0009] The first set of vehicle device identity codes fed back by the vehicle device group is used to bind the identities of vehicles and each vehicle device.

[0010] In response to vehicle power-on, read the second set of vehicle device identification codes from the vehicle device group;

[0011] The second set of vehicle device identity codes is compared with the first set of vehicle device identity codes to obtain the vehicle device identity authentication result and send it to the human-machine interaction unit.

[0012] In conjunction with the first aspect, optionally, the in-vehicle device identity binding and authentication method further includes:

[0013] Generate the first random code and send it to the vehicle-mounted equipment group;

[0014] The second static key is obtained by decrypting the key information fed back by the vehicle equipment group. The second static key is compared with the first static key of the corresponding vehicle equipment that is stored in advance to obtain the vehicle equipment type comparison result.

[0015] In response to a match between the vehicle-mounted equipment types, a second random code is generated and sent to the vehicle-mounted equipment group.

[0016] The second identity code is obtained by decrypting the identity information fed back by the vehicle equipment group. The second identity code is then compared with the first identity code of the corresponding vehicle equipment that is stored in advance to obtain the identity comparison result of the vehicle equipment.

[0017] In conjunction with the first aspect, the in-vehicle device identity binding and authentication method may optionally include: generating an in-vehicle device authentication result based on the in-vehicle device type comparison result or the in-vehicle device identity comparison result, and sending it to the human-computer interaction unit.

[0018] In conjunction with the first aspect, the in-vehicle device identity binding and authentication method may optionally include: generating a reason for in-vehicle device authentication failure based on the in-vehicle device type comparison result or the in-vehicle device identity comparison result and the in-vehicle device authentication result, and sending it to the human-computer interaction unit.

[0019] Secondly, the present invention provides a method for binding and authenticating the identity of in-vehicle devices, which is executed by a group of in-vehicle devices, the group of in-vehicle devices comprising a plurality of in-vehicle devices, including:

[0020] In response to the vehicle device identity reading request sent by the vehicle control unit, a first set of vehicle device identity codes is sent to the vehicle control unit to realize the identity binding of each vehicle device and the vehicle.

[0021] The in-vehicle device identity binding and authentication method further includes: calculating key information using an encryption algorithm based on a preset third static key for each in-vehicle device and a first random code sent by the in-vehicle control unit, and sending it to the in-vehicle control unit to achieve in-vehicle device type authentication for each in-vehicle device; and calculating identity information using an encryption algorithm based on a preset third identity code for each in-vehicle device and a second random code sent by the in-vehicle control unit, and sending it to the in-vehicle control unit to achieve in-vehicle device identity authentication for each in-vehicle device.

[0022] Thirdly, this invention provides an in-vehicle device identity binding and authentication system, comprising a server, a human-computer interaction unit, an in-vehicle control unit, and an in-vehicle device group:

[0023] The human-computer interaction unit sends an access password request to the server;

[0024] Upon successful authorization password request, the human-machine interaction unit sends a vehicle device identity binding request to the vehicle control unit.

[0025] The vehicle control unit sends a vehicle device identity reading request to the vehicle device group 3 based on the vehicle device identity binding request sent by the human-machine interaction unit; the vehicle device group includes several vehicle devices and stores the identity code corresponding to each vehicle device, which is used to generate a set of vehicle device identity codes.

[0026] In response to the vehicle device identity reading request sent by the vehicle control unit, the vehicle device group sends a first set of vehicle device identity codes to the vehicle control unit;

[0027] The vehicle control unit stores the first set of vehicle device identification codes fed back by the vehicle device group, which is used to bind the vehicle and each vehicle device to their identities.

[0028] The vehicle control unit responds to the vehicle power-on by reading the second set of vehicle device identification codes in vehicle device group 3;

[0029] The vehicle control unit compares the second set of vehicle device identification codes with the first set of vehicle device identification codes to obtain the vehicle device identification authentication result and sends it to the human-machine interaction unit.

[0030] In conjunction with the third aspect, optionally, the in-vehicle device identity binding and authentication system also includes:

[0031] The vehicle control unit generates a first random code and sends it to the vehicle equipment group;

[0032] The vehicle equipment group calculates key information using an encryption algorithm based on the preset third static key of each vehicle equipment and the first random code sent by the vehicle control unit, and sends it to the vehicle control unit.

[0033] The vehicle control unit decrypts the key information fed back by the vehicle equipment group to obtain the second static key. The second static key is compared with the first static key of the corresponding vehicle equipment pre-stored by the vehicle control unit to obtain the vehicle equipment type comparison result.

[0034] The vehicle control unit responds to the vehicle equipment type comparison and generates a second random code, which is then sent to the vehicle equipment group.

[0035] The vehicle equipment group calculates the identity information based on the preset third identity code of each vehicle equipment and the second random code sent by the vehicle control unit through an encryption algorithm, and sends it to the vehicle control unit.

[0036] The vehicle control unit decrypts the identity information fed back by the vehicle equipment group to obtain a second identity code, and compares the second identity code with the first identity code of the corresponding vehicle equipment that is stored in advance to obtain the vehicle equipment identity comparison result.

[0037] In conjunction with the third aspect, optionally, the in-vehicle device identity binding and authentication system further includes: the in-vehicle control unit generating an in-vehicle device authentication result based on the in-vehicle device type comparison result or the in-vehicle device identity comparison result, and sending it to the human-machine interaction unit.

[0038] In conjunction with the third aspect, optionally, the vehicle-mounted device identity binding and authentication system further includes: the vehicle control unit generating a reason for vehicle-mounted device authentication failure based on the comparison result of vehicle-mounted device type or vehicle-mounted device identity, and the vehicle-mounted device authentication result, and sending it to the human-machine interaction unit.

[0039] Fourthly, the present invention provides an in-vehicle device identity binding and authentication device, including a storage medium and a processor;

[0040] The storage medium is used to store instructions;

[0041] The processor is configured to operate according to the instructions to implement the method described in either the first aspect or the second aspect.

[0042] Compared with the prior art, the beneficial effects achieved by the present invention are as follows:

[0043] This invention provides a method for binding and authenticating the identity of vehicles and on-board equipment. By storing a first set of on-board equipment identification codes in the on-board control unit, the system completes the identification reading and recording of the on-board equipment in one step, thus binding the vehicle and the on-board equipment. This avoids the tedious manual binding process, reduces the possibility of human error, and is suitable for the production line rhythm of construction machinery. After binding, each time the vehicle is powered on, the on-board control unit automatically reads the second set of on-board equipment identification codes stored in the on-board equipment group and compares it with the first set of on-board equipment identification codes to perform vehicle and on-board equipment authentication without manual intervention. This complete binding and authentication strategy balances high production efficiency and long-term safety within the same mechanism.

[0044] Furthermore, this invention also provides another method for vehicle and in-vehicle device authentication, dividing the authentication process into two steps. The first step compares the in-vehicle device type based on a first random code, a second static key, and a third static key. Only when the in-vehicle device type matches is the second step triggered. The second step compares the in-vehicle device identity based on a second random code, a second identity code, and a first identity code. Through this dual authentication mechanism, corresponding restrictions are imposed on the vehicle based on the results of each authentication stage, thereby achieving differentiated vehicle management. Even if the in-vehicle device identity does not match, but the in-vehicle device type matches, the in-vehicle device can still be used for a short period. Therefore, this second method for vehicle and in-vehicle device authentication facilitates differentiated vehicle management, with different reasons for authentication failure directly corresponding to different levels of vehicle restrictions.

[0045] Furthermore, the present invention encrypts data transmission between the vehicle control unit and the vehicle equipment group, avoiding plaintext transmission to prevent interference from external data replay and malicious tampering, which could lead to loss of control over the identity authentication results. Attached Figure Description

[0046] To more clearly illustrate the technical solutions in the embodiments of the present invention or the prior art, the drawings used in the embodiments will be briefly described below. Obviously, the drawings described below are only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort, wherein:

[0047] Figure 1 The diagram shown is a flowchart illustrating an identity binding and authentication method for an in-vehicle device according to the present invention.

[0048] Figure 2 The diagram shown is a schematic of the dual authentication process of an identity authentication method for an in-vehicle device according to the present invention.

[0049] Figure 3The diagram shown is a structural schematic of an identity binding and authentication system for an in-vehicle device according to the present invention.

[0050] The components include: 1-Human-Machine Interaction Unit, 11-Vehicle Device Binding Trigger Module, 12-Binding Result Prompt Module, 13-Vehicle Device Authentication Alarm Module, 2-Vehicle Control Unit, 21-Vehicle Device Binding Interaction Module, 211-Dynamic Password Management Module, 212-Binding Result Indication Module, 213-Authentication Result Indication Module, 22-Vehicle Device Binding Execution Module, 221-Vehicle Device Identity Acquisition Module, 222-Vehicle Device Identity Storage Module, 23-Vehicle Device Authentication Module, 231-Authentication Mode Management Module, 232-Vehicle Device Key Management Module, 233- 234-Vehicle device identity acquisition module, 235-Vehicle device identity decryption module, 236-Vehicle device identity comparison module, 237-Authentication result output module, 238-Authentication error parsing module, 3-Vehicle device group, 31-Device group, 311-Driver group, 312-Sensor group, 313-GPS, 314-IO module, 32-Vehicle device identity transmission module, 321-Heartbeat output module, 322-Key management module, 323-Identity code encryption module, 324-Identity code transmission module, 4-Server, 41-Password application module, 42-Ledger management module. Detailed Implementation

[0051] The technical solution of the present invention will be described in detail below with reference to the accompanying drawings and specific embodiments. It should be understood that the embodiments of the present invention and the specific features in the embodiments are detailed descriptions of the technical solution of the present invention, rather than limitations thereof. In the absence of conflict, the embodiments of the present invention and the technical features in the embodiments can be combined with each other.

[0052] Example 1

[0053] like Figure 3 As shown in the figure, this embodiment introduces an in-vehicle device identity binding and authentication system, including a server, a human-computer interaction unit 1, an in-vehicle control unit 2, and an in-vehicle device group 3:

[0054] Human-computer interaction unit 1 sends an access password request to the server;

[0055] Upon successful authorization password request, the human-machine interaction unit 1 sends a vehicle device identity binding request to the vehicle control unit 2.

[0056] Based on the vehicle device identity binding request sent by the human-machine interaction unit 1, the vehicle control unit 2 sends a vehicle device identity reading request to the vehicle device group 3; the vehicle device group 3 includes several vehicle devices and stores the identity code corresponding to each vehicle device, which is used to generate a set of vehicle device identity codes.

[0057] In response to the vehicle device identity reading request sent by the vehicle control unit 2, the vehicle device group 3 sends a first set of vehicle device identity codes to the vehicle control unit 2;

[0058] The vehicle control unit 2 stores the first set of vehicle device identity codes fed back by the vehicle device group 3, which is used to bind the vehicle and each vehicle device to their identities.

[0059] In response to the vehicle power-on, the vehicle control unit 2 reads the second set of vehicle device identification codes from the vehicle device group 3;

[0060] The vehicle control unit 2 compares the second set of vehicle device identity codes with the first set of vehicle device identity codes to obtain the vehicle device identity authentication result and sends it to the human-machine interaction unit 1.

[0061] In one specific embodiment of the present invention, the vehicle-mounted device identity binding and authentication system further includes:

[0062] The vehicle control unit 2 generates a first random code and sends it to the vehicle equipment group 3;

[0063] The vehicle equipment group 3 calculates key information using an encryption algorithm based on the preset third static key of each vehicle equipment and the first random code sent by the vehicle control unit 2, and sends it to the vehicle control unit 2.

[0064] The vehicle control unit 2 decrypts the key information fed back by the vehicle equipment group 3 to obtain the second static key. The second static key is compared with the first static key of the corresponding vehicle equipment pre-stored by the vehicle control unit 2 to obtain the vehicle equipment type comparison result.

[0065] In response to the matching of vehicle equipment types, the vehicle control unit 2 generates a second random code and sends it to the vehicle equipment group 3.

[0066] The vehicle-mounted equipment group 3 calculates the identity information based on the preset third identity code of each vehicle-mounted device and the second random code sent by the vehicle-mounted control unit 2 through an encryption algorithm, and sends it to the vehicle-mounted control unit 2.

[0067] The vehicle control unit 2 decrypts the identity information fed back by the vehicle equipment group 3 to obtain the second identity code, and compares the second identity code with the first identity code of the corresponding vehicle equipment that is stored in advance to obtain the vehicle equipment identity comparison result.

[0068] In one specific embodiment of the present invention, the vehicle device identity binding and authentication system further includes: the vehicle control unit 2 generating a vehicle device authentication result based on the vehicle device type comparison result or the vehicle device identity comparison result, and sending it to the human-computer interaction unit 1.

[0069] In one specific embodiment of the present invention, the vehicle device identity binding and authentication system further includes: the vehicle control unit 2 generating a reason for vehicle device authentication failure based on the vehicle device type comparison result or the vehicle device identity comparison result and the vehicle device authentication result, and sending it to the human-computer interaction unit 1.

[0070] The following section uses an aerial work platform vehicle as an example to describe in detail the vehicle-mounted equipment identity binding and authentication system in this embodiment of the invention, with reference to a specific implementation method. Figure 1-3 As shown, the technical solution of the present invention includes the following steps:

[0071] Step 1, as follows Figure 1 As shown, the binding process during the vehicle assembly and off-line stage is as follows:

[0072] A. Process Triggering:

[0073] The on-site debugging personnel enter the vehicle equipment binding password page through the human-machine interaction unit 1, send an access password request to the password request module 41 of the server 4, obtain a dynamic password for access permission, and after entering the password, the vehicle equipment binding trigger module 11 will send the entered dynamic password to the vehicle equipment binding interaction module 21. After the password is verified by the dynamic password management module 211, the personnel enter the vehicle equipment binding operation page. After entering the page, the personnel follow the on-screen instructions to trigger the vehicle equipment binding process and send the binding request to the vehicle control unit 2.

[0074] The server 4 relies on the database to store the dynamic password application records for identity binding, and implements process management by establishing an audit ledger. The server 4 also includes a ledger management module 42, which is used to record and manage the identity ID of the password applicant, the application time, the application reason and the corresponding vehicle code, so as to realize the closed-loop management of the vehicle bus device binding process.

[0075] B. Binding execution:

[0076] After receiving the binding request, the vehicle device binding interaction module 21 of the vehicle control unit 2 will immediately drive the vehicle device binding execution module 22 to execute the binding process. When binding vehicle devices, the vehicle device identity acquisition module 221 will first request to read the identity codes of all vehicle devices that need to be bound. The vehicle device identity transmission module 32 of the vehicle device group 3 will send the first set of vehicle device identity codes to the vehicle control unit 2 through the identity code transmission module 324. The vehicle device identity storage module 222 will store the first set of vehicle device identity codes, i.e., the identity codes of all vehicle devices, to complete the identity binding process of the entire vehicle and each vehicle device.

[0077] The on-board equipment group 3 includes a common on-board bus equipment group 31 of aerial work platform vehicles, including but not limited to a driver group 311, a sensor group 312, a GPS 313, and an IO module 314. These devices transmit data with the on-board control unit 2 via a bus.

[0078] The vehicle-mounted devices included in the vehicle-mounted device group 3 are each connected to a device identity transmission module 32. The device identity transmission module 32 includes a heartbeat output module 321, which is used to send the online status of each vehicle-mounted device to the vehicle control unit 2.

[0079] The vehicle-mounted device identity transmission module 32 stores the identity code of each vehicle-mounted device and supports external devices to read the identification identity code, ensuring that the vehicle control unit 2 can reliably obtain the identity code of each vehicle-mounted device in the vehicle-mounted device group 3.

[0080] To further enhance the security of data transmission during the vehicle bus device authentication process and improve the ability to prevent replay attacks, a key management module 322 and an identity code encryption module 323 are added to encrypt the data during device authentication.

[0081] C. Result Return

[0082] Once the binding process is complete, the binding result indication module 212 will send the binding result and prompt information to the binding result prompt module 12 of the human-machine interaction unit 1. If all vehicle devices need to be successfully bound, only a binding success message will be sent; if any vehicle device fails to bind, the reason for the failure and the code of the failed vehicle device will be displayed to facilitate troubleshooting by the operator. After all vehicle devices are successfully bound, the vehicle control unit 2 switches from the offline mode to the factory mode.

[0083] D. Identity Authentication

[0084] In offline mode, the vehicle control unit 2 assumes that the vehicle is not fully assembled and the vehicle equipment has not yet been offline bound, so it will not perform identity authentication for the vehicle equipment. When switched to factory mode, the vehicle control unit 2 will automatically perform identity authentication for the vehicle equipment that needs to be authenticated every time the vehicle is powered on. If the identity authentication fails, the vehicle control unit 2 will send an alarm prompt to the vehicle equipment authentication alarm module 13 and trigger the vehicle action logic restriction.

[0085] Step two is only executed when the on-board equipment needs to be replaced. This is the binding process when the on-board equipment needs to be replaced after the vehicle leaves the factory:

[0086] A. Process Trigger: After the service personnel remove the vehicle's on-board equipment that needs to be replaced and replace it with a brand new original on-board equipment, they can also access the on-board equipment binding password page through the human-machine interaction unit 1 and bind their identity by referring to the factory binding process.

[0087] B. Binding Execution: When binding is executed again, the vehicle control unit 2 will also request to read the identity codes of all vehicle devices that need to be bound through the vehicle device identity acquisition module 221. At this time, the new identity code of the vehicle device group 3 will overwrite the original vehicle device identity code and be re-stored in the vehicle control unit 2.

[0088] C. Result Return

[0089] After the rebinding is completed, just like in the offline phase, the binding result indication module 212 will send the binding result and prompt information to the human-machine interaction unit 1. However, the vehicle control unit 2 will not switch modes again and will remain in offline mode.

[0090] D. Identity Authentication

[0091] After the new parts are replaced, the vehicle control unit 2 automatically authenticates the vehicle devices that need to be authenticated each time the vehicle is powered on. When the vehicle device identity verification module 23 performs vehicle device identity verification through the vehicle device identity comparison module 235, it will use the newly bound vehicle device identity code as the verification basis.

[0092] Step 3, as Figure 2 As shown, the vehicle's onboard device encrypted identity authentication process is as follows:

[0093] A. Obtaining the authentication mode:

[0094] Each time the vehicle is powered on, the authentication mode management module 231 automatically obtains the current authentication mode of the vehicle control unit 2. If the current mode is offline, the vehicle device will not be authenticated, but the vehicle's movement speed will be limited, and a prompt message will be sent to the human-machine interface unit 1. If the vehicle is in factory default mode, the vehicle device authentication process will be executed. The above design can ensure normal vehicle debugging while reminding the operator that the vehicle has not yet completed the vehicle device binding. It can also protect control security to a certain extent by slowing down the vehicle's movement if the vehicle is attacked after leaving the factory and the control mode storage area of ​​the vehicle control unit 2 is forcibly written to offline mode. It can also interfere with the vehicle's efficiency and convenience, forcing the OEM service personnel to restore the vehicle to normal working status.

[0095] B. Vehicle-mounted device identity acquisition:

[0096] After the identity authentication process begins, the vehicle device identity acquisition module 233 will automatically read the vehicle device identity codes of all vehicle devices in vehicle device group 3 that need to be authenticated and transmit them to the vehicle device identity comparison module 235.

[0097] C. Vehicle-mounted device identity verification:

[0098] The vehicle device identity comparison module 235 compares and verifies the read vehicle device identity code with the vehicle device identity code previously bound to the storage area of ​​vehicle device unit 2.

[0099] D. Authentication result output:

[0100] After authentication is completed, the identity authentication result is sent to the authentication result indication module 213 and the relevant vehicle action logic control module through the authentication result output module 236. The authentication result indication module 213 transmits the authentication result to the human-machine interaction unit 1.

[0101] E. Authentication Error Analysis:

[0102] If all in-vehicle devices pass authentication, it is assumed that there are no errors. If any in-vehicle device fails authentication, the authentication error parsing module 237 will send the reason for the in-vehicle device authentication failure to the human-machine interaction unit 1 to help the operator troubleshoot the problem.

[0103] If plaintext transmission is used when data is transmitted between the vehicle control unit 2 and the vehicle equipment group 3, it may be subject to interference from external data replay and malicious tampering, resulting in loss of control over the identity authentication results.

[0104] To further enhance the security of data transmission during the vehicle-mounted device authentication process and improve the ability to prevent replay attacks, this invention further encrypts the entire authentication process, relying on the vehicle-mounted device key management module 232 and the vehicle-mounted device identity decryption module 234 in the vehicle-mounted control unit 2, and the key management module 322 and the identity code encryption module 323 in the vehicle-mounted device group 3.

[0105] The entire identity verification process is divided into two steps:

[0106] The first step is to verify the type of vehicle-mounted equipment, which is used to verify whether the manufacturer and type of vehicle-mounted equipment are consistent with the type of vehicle-mounted equipment installed before leaving the factory.

[0107] The second step is to verify the identity of the in-vehicle device, which verifies whether the in-vehicle device identification code is correct, that is, whether it is the same in-vehicle device installed before leaving the factory.

[0108] Based on which step the on-board equipment failed verification, a tiered action logic restriction is implemented. If the first step of authentication passes but the second step fails, a low-risk restriction logic is implemented, which only restricts some working conditions and actions, such as limiting the vehicle's allowable range to half of the normal operating range or limiting the vehicle's speed. However, driving and stopping are not restricted. The purpose is to ensure that users can use the basic functions of the vehicle while providing a temporary means of inspection and troubleshooting.

[0109] When a vehicle's onboard equipment remains original and certification fails, allowing for temporary replacement with the same type of original equipment, the user can remove and install it from another purchased vehicle. If the first certification step is successful after replacement, it indicates a genuine malfunction in the original onboard equipment, and the user can contact the OEM's after-sales service personnel. During the waiting period, the replacement onboard equipment can be used temporarily to ensure basic vehicle operation remains unaffected. If the first certification step fails, it means the onboard equipment is no longer the designated type from the specified manufacturer, and the accuracy and reliability of the onboard equipment data cannot be guaranteed. In this case, high-risk restriction logic must be implemented immediately, restricting the vehicle's boom raising and extending movements, limiting vehicle speed, and allowing the vehicle to operate only for a limited time after retraction and power-on. The user must address the issue immediately to ensure vehicle control safety.

[0110] When the vehicle control unit 2 performs vehicle device authentication, the vehicle device key management module 232 is responsible for managing the static keys corresponding to different vehicle devices. Each type of vehicle device from each manufacturer has its own corresponding static key. The static key can be distributed by the OEM to the corresponding vehicle device manufacturer in advance and written as a factory parameter before the vehicle device leaves the factory. If a higher level of security protection is required for the static key, the OEM can distribute the static key to the corresponding vehicle device material when the vehicle device material group arrives at the vehicle production OEM.

[0111] The first step of the verification process, namely the verification of the vehicle-mounted device type, is as follows:

[0112] When the vehicle control unit 2 requests to read the vehicle device identification code, the vehicle device identification acquisition module 233 first generates a first random code and sends it to the vehicle device group 3. The vehicle device group 3 needs to use the first random code and its own third static key to run a specified encryption algorithm through the identification code encryption module 323, and then return the calculation result to the vehicle device authentication module 23. The vehicle device identification decryption module 234 decrypts the value to obtain the second static key, and then transmits it to the vehicle device identification comparison module 235 to verify whether the static key is correct.

[0113] If the static key is verified to be correct at this point, it indicates that the vehicle device manufacturer and vehicle device type are correct, and the next verification step can be performed. If the verification fails here, the authentication result output module 236 will directly output authentication failure and will not proceed with the subsequent authentication process. The authentication error parsing module 237 will provide an error reason prompt and execute the high-risk restriction logic. The high-risk restriction logic is the vehicle behavior restriction logic, which can be designed with reference to existing technologies and actual conditions.

[0114] If the vehicle has been under high-risk restriction for an extended period of time, reaching the maximum time preset by the OEM, it indicates that the vehicle has been in a high-risk control state for an extended period and needs to be locked. At this point, driving is completely restricted, and only vehicle retrieval is permitted. The user must immediately contact the OEM's after-sales service personnel for assistance.

[0115] The second step of the verification process, namely the specific operation procedure for in-vehicle device identity verification, is as follows:

[0116] After the first step of verification, the vehicle device identity acquisition module 233 generates a second random code and sends it to the vehicle device group 3. The vehicle device group 3 needs to use the second random code and its own stored third identity code to run the specified encryption algorithm through the identity code encryption module 323. The result is returned to the vehicle device identity verification module 23. The vehicle device identity decryption module 234 decrypts the value to obtain the second identity code and transmits it to the vehicle device identity comparison module to verify whether the read identity code is consistent with the first identity code currently bound to the vehicle control unit 2.

[0117] If the identity codes match, the on-board device authentication is successful; if they do not match, the authentication result output module 236 outputs "authentication failed," the authentication error parsing module 237 displays the error reason, and executes low-risk restriction logic. When implementing logic restrictions, different restriction protection logics must be executed according to different material group categories. The low-risk restriction logic is the vehicle's behavior restriction logic, which can be designed with reference to existing technologies and actual conditions.

[0118] After both of the above verification steps are passed, it can be ensured that the on-board equipment currently used in the vehicle is the original on-board equipment when the vehicle left the factory or the on-board equipment that has been replaced through the original factory channels, thus ensuring the legal source of the core on-board equipment and ensuring vehicle control safety.

[0119] Example 2

[0120] Based on the same inventive concept as Embodiment 1, this embodiment introduces a method for binding and authenticating the identity of an in-vehicle device, executed by the in-vehicle control unit 2, including:

[0121] Based on the vehicle device identity binding request sent by the human-computer interaction unit 1, a vehicle device identity reading request is sent to the vehicle device group 3; the vehicle device group 3 includes several vehicle devices and stores the identity code corresponding to each vehicle device, which is used to generate a set of vehicle device identity codes.

[0122] The first set of vehicle device identity codes fed back by the vehicle device group 3 is used to realize the identity binding between the vehicle and each vehicle device;

[0123] In response to vehicle power-on, read the second set of vehicle equipment identification codes in vehicle equipment group 3;

[0124] By comparing the second set of vehicle device identity codes with the first set of vehicle device identity codes, the vehicle device identity authentication result is obtained and sent to the human-machine interaction unit 1.

[0125] In one specific embodiment of the present invention, the in-vehicle device identity binding and authentication method also provides another in-vehicle device identity authentication method, including:

[0126] Generate the first random code and send it to vehicle equipment group 3;

[0127] The second static key is obtained by decrypting the key information fed back by the vehicle equipment group 3. The second static key is compared with the first static key of the corresponding vehicle equipment that is stored in advance to obtain the vehicle equipment type comparison result.

[0128] In response to the matching of the vehicle equipment type, a second random code is generated and sent to vehicle equipment group 3;

[0129] The second identity code is obtained by decrypting the identity information fed back by the vehicle-mounted device group 3. The second identity code is compared with the first identity code of the corresponding vehicle-mounted device that is stored in advance to obtain the identity comparison result of the vehicle-mounted device.

[0130] In one specific embodiment of the present invention, the vehicle device identity binding and authentication method further includes: generating a vehicle device authentication result based on the vehicle device type comparison result or the vehicle device identity comparison result, and sending it to the human-computer interaction unit 1.

[0131] In one specific embodiment of the present invention, the vehicle device identity binding and authentication method further includes: generating a reason for vehicle device authentication failure based on the vehicle device type comparison result or the vehicle device identity comparison result and the vehicle device authentication result, and sending it to the human-computer interaction unit 1.

[0132] Example 3

[0133] Based on the same inventive concept as Embodiments 1 and 2, this embodiment introduces a method for binding and authenticating the identity of in-vehicle devices, executed by an in-vehicle device group 3, which includes several in-vehicle devices, including:

[0134] In response to the vehicle device identity reading request sent by the vehicle control unit 2, a first set of vehicle device identity codes is sent to the vehicle control unit 2 to realize the identity binding of each vehicle device and the vehicle.

[0135] The vehicle-mounted device identity binding and authentication method further includes: calculating key information using an encryption algorithm based on a preset third static key for each vehicle-mounted device and a first random code sent by the vehicle control unit 2, and sending it to the vehicle control unit 2 to achieve vehicle-mounted device type authentication for each vehicle-mounted device; and calculating identity information using an encryption algorithm based on a preset third identity code for each vehicle-mounted device and a second random code sent by the vehicle control unit 2, and sending it to the vehicle control unit 2 to achieve vehicle-mounted device identity authentication for each vehicle-mounted device.

[0136] Example 4

[0137] This invention provides an in-vehicle device identity binding and authentication apparatus, including a storage medium and a processor;

[0138] The storage medium is used to store instructions;

[0139] The processor is used to operate according to the instructions to implement the method of any one of Embodiments 2 or 3.

[0140] Those skilled in the art will understand that embodiments of the present invention can be provided as methods, systems, or computer program products. Therefore, the present invention can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, the present invention can take the form of a computer program product implemented on one or more computer-usable storage media containing computer-usable program code, including but not limited to disk storage, CD-ROM, optical storage, etc.

[0141] This invention is described with reference to flowchart illustrations and / or block diagrams of methods, in-vehicle equipment systems, and computer program products according to embodiments of the invention. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing in-vehicle equipment to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing in-vehicle equipment, generate instructions for implementing the flowchart illustrations and / or block diagrams. Figure 1One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0142] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing vehicle-mounted equipment to operate in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0143] These computer program instructions can also be loaded onto a computer or other programmable data processing onboard equipment, causing a series of operational steps to be performed on the computer or other programmable onboard equipment to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable onboard equipment for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

[0144] The embodiments of the present invention have been described above with reference to the accompanying drawings. However, the present invention is not limited to the specific embodiments described above. The specific embodiments described above are merely illustrative and not restrictive. Those skilled in the art can make many other forms under the guidance of the present invention without departing from the spirit and scope of the claims. All of these forms are within the protection scope of the present invention.

Claims

1. A method for binding and authenticating the identity of an in-vehicle device, executed by an in-vehicle control unit, characterized in that, include: Based on the vehicle device identity binding request sent by the human-computer interaction unit, a vehicle device identity reading request is sent to the vehicle device group; The vehicle-mounted equipment group includes several vehicle-mounted devices and stores the identification code corresponding to each vehicle-mounted device, which is used to generate a set of vehicle-mounted device identification codes. The first set of vehicle device identity codes fed back by the vehicle device group is used to bind the identities of vehicles and each vehicle device. In response to vehicle power-on, read the second set of vehicle device identification codes from the vehicle device group; The second set of vehicle device identity codes is compared with the first set of vehicle device identity codes to obtain the vehicle device identity authentication result and send it to the human-machine interaction unit.

2. The method for binding and authenticating the identity of an in-vehicle device according to claim 1, characterized in that, The in-vehicle device identity binding and authentication method also includes: Generate the first random code and send it to the vehicle-mounted equipment group; The second static key is obtained by decrypting the key information fed back by the vehicle equipment group. The second static key is compared with the first static key of the corresponding vehicle equipment that is stored in advance to obtain the vehicle equipment type comparison result. In response to a match between the vehicle-mounted equipment types, a second random code is generated and sent to the vehicle-mounted equipment group. The second identity code is obtained by decrypting the identity information fed back by the vehicle equipment group. The second identity code is then compared with the first identity code of the corresponding vehicle equipment that is stored in advance to obtain the identity comparison result of the vehicle equipment.

3. The method for binding and authenticating the identity of an in-vehicle device according to claim 2, characterized in that, The method for binding and authenticating the identity of in-vehicle devices further includes: generating an in-vehicle device authentication result based on the comparison result of the in-vehicle device type or the comparison result of the in-vehicle device identity, and sending it to the human-computer interaction unit.

4. The vehicle-mounted device identity binding and authentication method according to claim 3, characterized in that, The method for binding and authenticating the identity of in-vehicle devices further includes: generating a reason for the failure of in-vehicle device authentication based on the comparison result of the in-vehicle device type or the comparison result of the in-vehicle device identity, and sending it to the human-computer interaction unit.

5. A method for binding and authenticating the identity of in-vehicle devices, executed by an in-vehicle device group, wherein the in-vehicle device group comprises a plurality of in-vehicle devices, characterized in that, include: In response to the vehicle device identity reading request sent by the vehicle control unit, a first set of vehicle device identity codes is sent to the vehicle control unit to realize the identity binding of each vehicle device and the vehicle. The in-vehicle device identity binding and authentication method further includes: calculating key information using an encryption algorithm based on a preset third static key for each in-vehicle device and a first random code sent by the in-vehicle control unit, and sending it to the in-vehicle control unit to achieve in-vehicle device type authentication for each in-vehicle device; and calculating identity information using an encryption algorithm based on a preset third identity code for each in-vehicle device and a second random code sent by the in-vehicle control unit, and sending it to the in-vehicle control unit to achieve in-vehicle device identity authentication for each in-vehicle device.

6. A vehicle-mounted device identity binding and authentication system, characterized in that, Includes servers, human-machine interface units, vehicle control units, and vehicle equipment groups: The human-computer interaction unit sends an access password request to the server; Upon successful authorization password request, the human-machine interaction unit sends a vehicle device identity binding request to the vehicle control unit. The vehicle control unit sends a vehicle device identity reading request to the vehicle device group 3 based on the vehicle device identity binding request sent by the human-machine interaction unit; the vehicle device group includes several vehicle devices and stores the identity code corresponding to each vehicle device, which is used to generate a set of vehicle device identity codes. In response to the vehicle device identity reading request sent by the vehicle control unit, the vehicle device group sends a first set of vehicle device identity codes to the vehicle control unit; The vehicle control unit stores the first set of vehicle device identification codes fed back by the vehicle device group, which is used to bind the vehicle and each vehicle device to their identities. The vehicle control unit responds to the vehicle power-on by reading the second set of vehicle device identification codes in vehicle device group 3; The vehicle control unit compares the second set of vehicle device identification codes with the first set of vehicle device identification codes to obtain the vehicle device identification authentication result and sends it to the human-machine interaction unit.

7. The vehicle-mounted device identity binding and authentication system according to claim 6, characterized in that, The in-vehicle device identity binding and authentication system also includes: The vehicle control unit generates a first random code and sends it to the vehicle equipment group; The vehicle equipment group calculates key information using an encryption algorithm based on the preset third static key of each vehicle equipment and the first random code sent by the vehicle control unit, and sends it to the vehicle control unit. The vehicle control unit decrypts the key information fed back by the vehicle equipment group to obtain the second static key. The second static key is compared with the first static key of the corresponding vehicle equipment pre-stored by the vehicle control unit to obtain the vehicle equipment type comparison result. The vehicle control unit responds to the vehicle equipment type comparison and generates a second random code, which is then sent to the vehicle equipment group. The vehicle equipment group calculates the identity information based on the preset third identity code of each vehicle equipment and the second random code sent by the vehicle control unit through an encryption algorithm, and sends it to the vehicle control unit. The vehicle control unit decrypts the identity information fed back by the vehicle equipment group to obtain a second identity code, and compares the second identity code with the first identity code of the corresponding vehicle equipment that is stored in advance to obtain the vehicle equipment identity comparison result.

8. The vehicle-mounted device identity binding and authentication system according to claim 7, characterized in that, The vehicle-mounted device identity binding and authentication system further includes: the vehicle-mounted control unit generates a vehicle-mounted device authentication result based on the vehicle-mounted device type comparison result or the vehicle-mounted device identity comparison result, and sends it to the human-machine interaction unit.

9. The vehicle-mounted device identity binding and authentication system according to claim 8, characterized in that, The vehicle-mounted device identity binding and authentication system further includes: the vehicle control unit generates a reason for vehicle-mounted device authentication failure based on the comparison result of vehicle-mounted device type or vehicle-mounted device identity, and the vehicle-mounted device authentication result, and sends it to the human-machine interaction unit.

10. A vehicle-mounted device identity binding and authentication device, characterized in that, Including storage media and processor; The storage medium is used to store instructions; The processor is configured to operate according to the instructions to implement the method of any one of claims 1-4 or 5.

Images