Identity verification method and device for vehicle combination instrument, medium, product and vehicle

Abstract

The invention provides an identity verification method and device for a vehicle combination instrument, a medium, a product and a vehicle, and relates to the technical field of vehicles. The method comprises the steps of obtaining a first identification code of a combination instrument in a vehicle in response to detection of vehicle ignition; determining a target identification code of the combination instrument according to the first identification code; based on the target identification code, determining a primary identity verification result of the combination instrument; when the primary identity verification result represents that the combination instrument passes the primary identity verification, determining a serial number matching result of the combination instrument according to the target identification code; and determining a final identity verification result of the combination instrument based on the serial number matching result. According to the invention, the identity verification efficiency and accuracy of the vehicle combination instrument are improved.

Description

Technical Field

[0001] This application relates to the field of vehicle technology, and in particular to an authentication method, device, medium, product, and vehicle for a vehicle combination instrument. Background Technology

[0002] The instrument cluster in commercial vehicles is a core component used to display critical status information such as vehicle speed, engine speed, fuel level, and fault alarms. Compared to passenger vehicles, the instrument cluster functions of commercial vehicles are relatively simplified, but their application characteristics in commercial transportation dictate stringent requirements for high reliability and safety. However, in the aftermarket after vehicles leave the factory, due to relatively outdated repair equipment and the ease with which the functions of replacement or upgrade parts (aftermarket products) provided by third parties can be cracked and counterfeited, users may end up having non-original parts installed during repairs. These non-original parts often do not meet the original manufacturer's technical specifications and may even pose potential safety hazards, threatening the normal operation of the vehicle and the safety of the user.

[0003] Currently, the authentication methods for commercial vehicle instrument clusters mainly rely on external diagnostic tools to manually write simple configuration words such as vehicle identification codes into the instrument cluster for static binding. The instrument cluster internally stores this configuration word as its identity identifier and compares it with the actual information to achieve instrument cluster authentication. However, the above-mentioned static binding and manual comparison verification method suffers from inefficiency and is prone to errors. Summary of the Invention

[0004] This application provides a method, device, medium, product, and vehicle for authenticating vehicle instrument clusters, in order to improve the efficiency and accuracy of vehicle instrument cluster authentication.

[0005] In a first aspect, this application provides an authentication method for a vehicle instrument cluster, comprising:

[0006] Upon detecting vehicle ignition, the system retrieves the first identification code from the vehicle's instrument cluster.

[0007] The target identification code of the instrument cluster is determined based on the first identification code;

[0008] Based on the target identifier code, determine the initial identity verification result of the instrument cluster;

[0009] When the initial authentication result indicates that the instrument cluster has passed the initial authentication, the serial number matching result of the instrument cluster is determined based on the target identification code.

[0010] Based on the serial number matching results, the final authentication result of the instrument cluster is determined.

[0011] In one possible implementation, determining the target identifier code of the instrument cluster based on the first identifier code includes:

[0012] Determine whether the first identifier code conforms to the identifier code rules;

[0013] If the first identifier does not conform to the identifier rule, the target identifier is determined based on the second identifier of the combined instrument obtained from the cloud platform.

[0014] If the first identifier code conforms to the identifier code rules, then the first identifier code will be used as the target identifier code.

[0015] In one possible implementation, determining the target identifier code based on the second identifier code of the combined instrument obtained from the cloud platform includes:

[0016] Based on the Internet of Things (IoT) communication protocol, the second identification code of the combined instrument is obtained from the cloud platform, and the second identification code is determined as the target identification code.

[0017] In one possible implementation, the initial authentication result of the instrument cluster is determined based on the target identifier code, including:

[0018] If the target identifier is the first identifier, then the initial identity verification result is determined to be successful.

[0019] If the target identifier is the second identifier, then determine whether the cloud platform and the combined instrument have been authenticated through the asymmetric key handshake protocol.

[0020] When the result of the judgment indicates that the authentication of the asymmetric key handshake protocol has been passed, the initial identity verification result is determined to be passed.

[0021] If the result of the judgment indicates that the authentication of the asymmetric key handshake protocol has failed, the initial identity verification result is determined to be an initial identity verification failure.

[0022] In one possible implementation, when the initial authentication result indicates that the instrument cluster has passed the initial authentication, the serial number matching result of the instrument cluster is determined based on the target identifier code, including:

[0023] When the initial authentication result indicates that the instrument cluster has passed the initial authentication, the third identification code of the instrument cluster is determined based on the target identification code.

[0024] Based on the third identification code, generate the first serial number corresponding to the instrument cluster;

[0025] The first serial number is matched with the second serial number corresponding to the instrument cluster obtained from the cloud platform to determine the serial number matching result of the instrument cluster.

[0026] In one possible implementation, a first serial number corresponding to the instrument cluster is generated based on the third identification code, including:

[0027] The first serial number corresponding to the instrument cluster is generated based on the third identifier, supplier code, part number of the instrument cluster, and timestamp factor corresponding to the first identifier. The supplier code, part number, and timestamp factor are obtained from the cloud platform through the Network Control Model (NCM) protocol.

[0028] In one possible implementation, it also includes:

[0029] When the initial authentication result and / or the final authentication result indicate that the instrument cluster has failed the corresponding authentication, the abnormal display of the instrument cluster is triggered and the first prompt message is output. The first prompt message is used to remind the user that there is an abnormal situation with the instrument cluster.

[0030] And / or, when the final authentication result indicates that the instrument cluster has passed the corresponding authentication, a second prompt message is output, which is used to inform the user that there is no abnormality in the instrument cluster.

[0031] Secondly, this application provides an authentication device for a vehicle instrument cluster, comprising:

[0032] The acquisition module is used to acquire the first identification code of the vehicle's instrument cluster in response to the detection of vehicle ignition.

[0033] The determination module is used to determine the target identification code of the instrument cluster based on the first identification code; and to determine the initial authentication result of the instrument cluster based on the target identification code.

[0034] The determination module is also used to determine the serial number matching result of the instrument cluster based on the target identifier code when the initial authentication result indicates that the instrument cluster has passed the initial authentication; and to determine the final authentication result of the instrument cluster based on the serial number matching result.

[0035] In one possible implementation, the determining module is specifically used for:

[0036] Determine whether the first identifier code conforms to the identifier code rules;

[0037] If the first identifier does not conform to the identifier rule, the target identifier is determined based on the second identifier of the combined instrument obtained from the cloud platform.

[0038] If the first identifier code conforms to the identifier code rules, then the first identifier code will be used as the target identifier code.

[0039] In one possible implementation, the determining module is specifically used for:

[0040] Based on the Internet of Things (IoT) communication protocol, the second identification code of the combined instrument is obtained from the cloud platform, and the second identification code is determined as the target identification code.

[0041] In one possible implementation, the determining module is specifically used for:

[0042] If the target identifier is the first identifier, then the initial identity verification result is determined to be successful.

[0043] If the target identifier is the second identifier, then determine whether the cloud platform and the combined instrument have been authenticated through the asymmetric key handshake protocol.

[0044] When the result of the judgment indicates that the authentication of the asymmetric key handshake protocol has been passed, the initial identity verification result is determined to be passed.

[0045] If the result of the judgment indicates that the authentication of the asymmetric key handshake protocol has failed, the initial identity verification result is determined to be an initial identity verification failure.

[0046] In one possible implementation, the determining module is specifically used for:

[0047] When the initial authentication result indicates that the instrument cluster has passed the initial authentication, the third identification code of the instrument cluster is determined based on the target identification code.

[0048] Based on the third identification code, generate the first serial number corresponding to the instrument cluster;

[0049] The first serial number is matched with the second serial number corresponding to the instrument cluster obtained from the cloud platform to determine the serial number matching result of the instrument cluster.

[0050] In one possible implementation, the determining module is specifically used for:

[0051] The first serial number corresponding to the instrument cluster is generated based on the third identifier, supplier code, part number of the instrument cluster, and timestamp factor corresponding to the first identifier. The supplier code, part number, and timestamp factor are obtained from the cloud platform through the Network Control Model (NCM) protocol.

[0052] In one possible implementation, the authentication device of the vehicle instrument cluster further includes an output module, which is specifically used for:

[0053] When the initial authentication result and / or the final authentication result indicate that the instrument cluster has failed the corresponding authentication, the abnormal display of the instrument cluster is triggered and the first prompt message is output. The first prompt message is used to remind the user that there is an abnormal situation with the instrument cluster.

[0054] And / or, when the final authentication result indicates that the instrument cluster has passed the corresponding authentication, a second prompt message is output, which is used to inform the user that there is no abnormality in the instrument cluster.

[0055] Thirdly, this application provides an electronic device, including: a memory and a processor;

[0056] The memory stores the instructions that the computer executes;

[0057] The processor executes computer execution instructions stored in memory, causing the processor to perform the first aspect and / or various possible implementations of the first aspect as described above.

[0058] Fourthly, this application provides a computer-readable storage medium storing computer-executable instructions, which, when executed, are used to implement the first aspect and / or various possible embodiments of the first aspect.

[0059] Fifthly, this application provides a computer program product, including a computer program that, when executed, implements the first aspect and / or various possible implementations of the first aspect.

[0060] In a sixth aspect, this application provides a vehicle, including a vehicle body and various possible embodiments of the first aspect.

[0061] This application provides a method, device, medium, product, and vehicle for authenticating a vehicle instrument cluster, relating to the field of vehicle technology. The method includes: in response to detecting vehicle ignition, acquiring a first identification code of the instrument cluster in the vehicle; determining a target identification code of the instrument cluster based on the first identification code; determining an initial authentication result of the instrument cluster based on the target identification code; when the initial authentication result indicates that the instrument cluster has passed the initial authentication, determining a serial number matching result of the instrument cluster based on the target identification code; and determining a final authentication result of the instrument cluster based on the serial number matching result. This application, by acquiring the first identification code of the instrument cluster in the vehicle in response to detecting vehicle ignition and determining the target identification code of the instrument cluster based on the first identification code, enables precise positioning of the instrument cluster; performing an initial identity verification of the instrument cluster based on the target identification code, and determining a serial number matching result of the instrument cluster based on the target identification code when the initial identity verification result indicates that the instrument cluster has passed the initial authentication; and determining a final authentication result of the instrument cluster based on the serial number matching result, improves the accuracy of vehicle instrument cluster authentication through the above two authentication operations; furthermore, the above two authentication operations do not require manual operation, thus improving the efficiency of vehicle instrument cluster authentication. Attached Figure Description

[0062] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this application and, together with the description, serve to explain the principles of this application.

[0063] Figure 1 A flowchart illustrating the authentication method for a vehicle instrument cluster provided in this application embodiment. Figure 1 ;

[0064] Figure 2 A flowchart illustrating the authentication method for a vehicle instrument cluster provided in this application embodiment. Figure 2 ;

[0065] Figure 3 A schematic diagram of the system structure corresponding to the authentication method of the vehicle instrument cluster provided in the embodiments of this application;

[0066] Figure 4 A schematic diagram of the authentication device for a vehicle instrument cluster provided in an embodiment of this application;

[0067] Figure 5 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application.

[0068] The accompanying drawings illustrate specific embodiments of this application, which will be described in more detail below. These drawings and descriptions are not intended to limit the scope of the concept in any way, but rather to illustrate the concept of this application to those skilled in the art through reference to particular embodiments. Detailed Implementation

[0069] Exemplary embodiments will now be described in detail, examples of which are illustrated in the accompanying drawings. When the following description relates to the drawings, unless otherwise indicated, the same numbers in different drawings denote the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with this application. Rather, they are merely examples of apparatuses and methods consistent with some aspects of this application as detailed in the appended claims.

[0070] First, let me explain the terms used in this application:

[0071] Master: Responsible for providing support for virtual network interface cards (NICs) and implementing transparent control of platform data transmission. It manages and coordinates the creation and operation of virtual network interfaces, while ensuring efficient and secure direct data transmission between different components or systems, thus playing a key role in network virtualization and data flow management.

[0072] Cipher-based Message Authentication Code (CMAC) is implemented based on the Advanced Encryption Standard (AES) algorithm.

[0073] Network Control Model (NCM) protocol: It belongs to the CDC subclass protocol defined by USB-IF and is mainly used for efficient transmission between hosts and devices, supporting high-speed network scenarios (such as 4G / 5G modems, USB network cards, etc.).

[0074] Identification code: This is a unique identification code assigned to each vehicle by the manufacturer. It consists of 17 characters and contains information such as the vehicle manufacturer, year, model, body type, engine code, and assembly location.

[0075] The Remote Network Driver Interface Specification (RNDIS) is used to implement TCP / IP network communication via USB devices.

[0076] Existing commercial vehicle instrument clusters typically employ a method of manually writing simple configuration characters, such as vehicle identification codes, into the instrument cluster via an external diagnostic tool for authentication. These codes are then statically stored within the instrument cluster as an identifier for subsequent diagnostics or comparisons. This establishes a strong association between original equipment (OEM) products and specific vehicles, relying on diagnostic tools for configuration. However, for aftermarket products, the lack of an inherent strong association between the device and the vehicle, coupled with the uncontrollability of offline manual operation scenarios, makes the aforementioned diagnostic tool-based configuration settings and static binding mode difficult to apply. Therefore, aftermarket products are generally designed to eliminate the need for diagnostic tool configuration, reflecting a consideration for installation and usage flexibility.

[0077] To address the aforementioned issues, this application provides an authentication method for a vehicle instrument cluster. The method involves detecting vehicle ignition in response to an error, determining a target identifier for the instrument cluster based on a first identifier obtained from the instrument cluster, determining the initial authentication result of the instrument cluster based on the target identifier, determining the serial number matching result of the instrument cluster based on the target identifier, and determining the final authentication result of the instrument cluster based on the serial number matching result.

[0078] The technical solution of this application and how the technical solution of this application solves the above-mentioned technical problems are described in detail below with specific embodiments. These specific embodiments can be combined with each other, and the same or similar concepts or processes may not be described again in some embodiments. The embodiments of this application will now be described with reference to the accompanying drawings.

[0079] Figure 1 A flowchart illustrating the authentication method for a vehicle instrument cluster provided in this application embodiment. Figure 1 ,like Figure 1As shown, the method includes:

[0080] S101. Upon detecting vehicle ignition, obtain the first identification code of the instrument cluster in the vehicle.

[0081] In this step, it can be understood that when the response detects vehicle ignition, it is necessary to obtain the first identification code of the instrument cluster in the vehicle. The first identification code is an identification code built into the instrument cluster, which serves as the identification and matching certificate of the instrument cluster and the vehicle, and is used to ensure the correctness of the instrument cluster's identity.

[0082] S102. Determine the target identification code of the instrument cluster based on the first identification code.

[0083] Because the primary identification code is built into the instrument cluster, its security and tamper-proof capabilities are relatively weak. Once the primary identification code is illegally altered, an aftermarket-manufactured instrument cluster can be installed in a vehicle as a legitimate one.

[0084] The characteristics of the aforementioned first identification code not only severely weaken the security of instrument cluster identity verification, rendering matching and identification based on the first identification code ineffective, but also directly lead to the proliferation of non-original products in the aftermarket, posing a huge hidden danger to vehicle performance, reliability, and even driving safety.

[0085] Therefore, in this embodiment of the application, after determining the first identifier code, the target identifier code of the instrument cluster is determined based on the first identifier code. For example, determining the target identifier code of the instrument cluster based on the first identifier code includes: determining whether the first identifier code conforms to the identifier code rules; if the first identifier code does not conform to the identifier code rules, then determining the target identifier code based on the second identifier code of the instrument cluster obtained from the cloud platform; if the first identifier code conforms to the identifier code rules, then using the first identifier code as the target identifier code.

[0086] In this example, determining the target identifier code requires first judging whether the first identifier code conforms to the identifier code rules. Based on the judgment result, the target identifier code is determined. Specifically, if the first identifier code does not conform to the identifier code rules, the target identifier code is determined based on the second identifier code of the instrument cluster obtained from the cloud platform. This means that the identifier code of the instrument cluster exists not only internally within the instrument cluster but also on the cloud platform. This operation ensures that even if the identifier code built into the instrument cluster, i.e., the first identifier code, is tampered with, the true identifier code of the instrument cluster can still be determined, i.e., the target identifier code of the instrument cluster, providing an accurate data foundation for subsequent instrument cluster authentication.

[0087] Whether the first identifier code has been tampered with is determined by checking whether the first identifier code conforms to the identifier code rules. The identifier code rules can be set according to actual needs. For example, the identifier code rules can be set to check whether the identifier code is empty, and / or set to match and compare the identifier code built into the instrument cluster with the identifier code of the instrument cluster obtained from the cloud platform.

[0088] Furthermore, based on the above embodiments, determining the target identifier code according to the second identifier code of the combined instrument obtained from the cloud platform includes: obtaining the second identifier code of the combined instrument from the cloud platform based on the Internet of Things (IoT) communication protocol, and determining the second identifier code as the target identifier code. The IoT communication protocol can be a lightweight IoT communication protocol (Message Queuing Telemetry Transport, abbreviated as MQTT), which supports efficient data interaction between different devices and the cloud platform. It should be noted that this is merely an example, and the embodiments of this application do not limit the setting of the IoT communication protocol.

[0089] In one implementation, the identifier code of the combined instrument stored in the cloud platform is read through the / ***_master / read_***_VIN command in MQTT.

[0090] In summary, by using the IoT communication protocol to obtain the second identification code of the combined instrument from the cloud platform, the real-time, automated, remote, and secure acquisition of the second identification code can be achieved, thus providing a solid foundation for subsequent efficient identity verification.

[0091] S103. Based on the target identifier code, determine the initial identity verification result of the instrument cluster.

[0092] In this step, it can be understood that the instrument cluster is initially authenticated based on the target identifier code determined in S102, thereby obtaining the initial authentication result of the instrument cluster. Next, based on the initial authentication result of the instrument cluster, subsequent targeted processing measures are determined. If the initial authentication result indicates that the instrument cluster has failed the initial authentication, then the final authentication result of the instrument cluster can be directly determined as authentication failure; if the initial authentication result indicates that the instrument cluster has passed the initial authentication, then S104 is executed.

[0093] S104. When the initial authentication result indicates that the instrument cluster has passed the initial authentication, determine the serial number matching result of the instrument cluster based on the target identification code.

[0094] Since the first identification code is built into the instrument cluster, it is at risk of being illegally tampered with, potentially allowing the initial identity verification to be bypassed. Even if the instrument cluster is illegally tampered with, it could still pass the initial identity verification, posing a security risk. Therefore, in this embodiment, after the instrument cluster passes the initial identity verification, the target identification code is used to determine the serial number matching result of the instrument cluster. This reduces the risk of bypassing the initial identity verification by illegally tampering with the first identification code built into the instrument cluster, and improves the accuracy of identity verification to a certain extent.

[0095] S105. Based on the serial number matching result, determine the final identity verification result of the instrument cluster.

[0096] In this step, it can be understood that the instrument cluster undergoes secondary authentication based on the serial number matching result to obtain the final authentication result. Specifically, if the serial number matching result indicates that the instrument cluster failed the serial number matching, it can be determined that the secondary authentication result of the instrument cluster failed, and therefore the final authentication result of the instrument cluster failed, meaning that the instrument cluster is an aftermarket modified instrument cluster. Conversely, if the serial number matching result indicates that the instrument cluster passed the serial number matching, it can be determined that the secondary authentication result passed, and therefore the final authentication result of the instrument cluster passed, meaning that the instrument cluster is not an aftermarket modified instrument cluster.

[0097] In summary, it can be understood that only when the instrument cluster passes two authentication attempts can it be confirmed that the instrument cluster has passed authentication and is not an aftermarket modified instrument cluster. If even one authentication attempt fails, it can be confirmed that the instrument cluster has failed authentication and is therefore an aftermarket modified instrument cluster.

[0098] In this embodiment, upon detecting vehicle ignition, a first identification code of the vehicle's instrument cluster is obtained. Based on the first identification code, a target identification code of the instrument cluster is determined, enabling precise positioning of the instrument cluster. Based on the target identification code, an initial identity verification is performed on the instrument cluster. Upon successful initial identity verification, the instrument cluster's serial number is matched using the target identification code. Based on the serial number matching result, the final identity verification result of the instrument cluster is determined. Through these two identity verification operations, the accuracy of vehicle instrument cluster identity verification is improved. Furthermore, none of these two identity verification operations require manual intervention, thus improving the efficiency of vehicle instrument cluster identity verification.

[0099] Based on the above embodiments, S103 describes determining the initial identity verification result of the combined instrument based on the target identifier code, including: if the target identifier code is a first identifier code, then determining that the initial identity verification result is passed; if the target identifier code is a second identifier code, then determining whether the cloud platform and the combined instrument have passed the authentication of the asymmetric key handshake protocol; if the determination result indicates that the authentication of the asymmetric key handshake protocol has been passed, then determining that the initial identity verification result is passed; if the determination result indicates that the authentication of the asymmetric key handshake protocol has not been passed, then determining that the initial identity verification result is failed.

[0100] In this embodiment, it can be understood that the determination of the initial authentication result of the instrument cluster is based on the target identifier code. Specifically, if the target identifier code determined in S102 is the first identifier code, it can be directly determined that the instrument cluster has passed the initial authentication, that is, the initial authentication result is determined to be passed the initial identity verification; if the target identifier code determined in S102 is the second identifier code, it is necessary to determine whether the cloud platform and the instrument cluster have passed the authentication through the asymmetric handshake protocol.

[0101] Optionally, the core of determining whether the cloud platform and the instrument cluster have been authenticated through the asymmetric handshake protocol lies in verifying whether the cloud platform and the instrument cluster have successfully exchanged keys, and verifying the identities and message integrity of both parties through CMAC based on the keys.

[0102] Specifically, the authentication between the cloud platform and the instrument cluster via the asymmetric handshake protocol can be determined as follows: The instrument cluster verifies the legitimacy of the cloud platform's digital certificate, ensuring its certificate chain is trustworthy and not expired. This is the foundation for establishing trust between the instrument cluster and the cloud platform. The cloud platform and the instrument cluster successfully negotiate a session key based on asymmetric encryption technology, which is crucial for subsequent secure communication. Using the negotiated session key, the instrument cluster and the cloud platform independently calculate the CMAC value for specific data agreed upon during the handshake process and perform a rigorous comparison. Only when the two CMAC values ​​are completely identical can the authentication between the cloud platform and the instrument cluster be confirmed as successful. This not only proves the validity of the session key but also verifies the integrity of the communication data and the authenticity of both parties' identities.

[0103] The session key negotiated above is a multi-mode key combination, which increases the complexity of the session key, making it impossible for illegal aftermarket products to crack the session key, thereby improving the security level of the instrument cluster. This solves the problem that existing authentication methods support 8-bit fixed keys, which have a relatively low security level.

[0104] To improve the accuracy of information retrieval during communication, a multi-round handshake identification mechanism is introduced during the handshake process. Through multiple rounds of interactive verification, the validity of the device or data can be more reliably confirmed.

[0105] Only after successful authentication between the cloud platform and the instrument cluster will the instrument cluster accept and execute data write updates, thereby ensuring the reliability of the data source, the integrity of data transmission, and the legality of the operation. In other words, before writing the target identifier code into the instrument cluster's first identifier code, the security of this write operation must be determined, i.e., whether the cloud platform and the instrument cluster have been authenticated through the asymmetric handshake protocol.

[0106] Furthermore, if the result of the judgment indicates that the authentication of the asymmetric key handshake protocol has been passed, the initial identity verification result can be determined as having passed the initial identity verification; if the result of the judgment indicates that the authentication of the asymmetric key handshake protocol has not been passed, the initial identity verification result can be determined as having failed the initial identity verification.

[0107] In summary, the embodiments of this application can improve the security of instrument authentication by determining whether the cloud platform and the instrument have been authenticated through the asymmetric key handshake protocol.

[0108] Based on the above embodiments, in some examples, when the initial authentication result indicates that the instrument cluster has passed the initial authentication, the serial number matching result of the instrument cluster is determined according to the target identifier code, including: when the initial authentication result indicates that the instrument cluster has passed the initial authentication, determining the third identifier code of the instrument cluster according to the target identifier code; generating the first serial number corresponding to the instrument cluster according to the third identifier code; and matching the first serial number with the second serial number corresponding to the instrument cluster obtained from the cloud platform to determine the serial number matching result of the instrument cluster.

[0109] In this embodiment, it can be understood that when performing a serial number matching operation on the instrument cluster, the third identification code of the instrument cluster must first be determined based on the target identification code. Optionally, a specific number of digits can be extracted from the target identification code and determined as the third identification code.

[0110] Furthermore, it can be understood that determining the first serial number (SN) corresponding to the instrument cluster requires first determining the third identification code of the instrument cluster based on the target identification code, and then using the third identification code to generate the first serial number. The first serial number is a unique identifier for the instrument cluster generated by combining the identification code with the part number, supplier code, and timestamp factor. This prevents counterfeiters from bypassing identity verification by tampering with the identification code.

[0111] Specifically, based on the third identifier, a first serial number corresponding to the instrument cluster is generated. This includes generating the first serial number corresponding to the instrument cluster based on the third identifier, the supplier code, the part number of the instrument cluster, and the timestamp factor corresponding to the first identifier. The supplier code, part number, and timestamp factor are obtained from the cloud platform via the NCM protocol. The NCM protocol can solve the communication inefficiency problem caused by the RNDIS protocol.

[0112] In one implementation, the instrument cluster combines a third identifier with its part number, supplier code, and the timestamp factor corresponding to the first identifier. Using a specific XOR algorithm, a first serial number is generated for the instrument cluster. This first serial number is then saved to a non-lossable EPPROM module, and a flag is simultaneously written to 0. After generating the first serial number, it is sent to the platform via the MQTT / ***_IPK / seed_***_SN instruction. Upon receiving the first serial number, the platform matches it with the second serial number calculated by the platform itself. The matching result is then sent to the Master module via the MQTT / ***_master / seed_***_SN_StAtus instruction. In another implementation, both the generation and matching of the first serial number are performed within the Master module.

[0113] Furthermore, to determine the final authentication result of the instrument cluster, the first serial number and the second serial number need to be matched to obtain the serial number matching result of the instrument cluster. If the serial number matching result indicates that the instrument cluster passes the serial number matching, the final authentication result is determined to be successful; if the serial number matching result indicates that the instrument cluster fails the serial number matching, the final authentication result is determined to be unsuccessful.

[0114] In other words, to determine the final authentication result of the instrument cluster, the serial number obtained through the above embodiments needs to be compared with the serial number of the instrument cluster calculated by the cloud platform itself.

[0115] This application embodiment performs secondary authentication of the instrument cluster by matching serial numbers, thereby preventing counterfeiters from bypassing identity verification by tampering with the identification code and improving the reliability of instrument cluster authentication.

[0116] Existing instrument cluster authentication methods generally lack effective third-party detection and alarm mechanisms, preventing users from promptly detecting authentication anomalies. This means that other electrical assemblies in the vehicle lack the capability to identify the instrument cluster's authentication status. Although the instrument cluster itself can theoretically integrate anomaly detection and alarm display functions, for aftermarket replacement products, considering their installation flexibility and diversity, as well as their decoupling from the original vehicle system, developing such functions is often of little practical significance and fails to realize their intended purpose.

[0117] Therefore, the vehicle instrument cluster authentication method provided in this application embodiment further includes: when the initial authentication result and / or the final authentication result indicate that the instrument cluster has failed the corresponding authentication, triggering an abnormal display of the instrument cluster and outputting a first prompt message, the first prompt message being used to remind the user that there is an abnormal situation with the instrument cluster; and / or, when the final authentication result indicates that the instrument cluster has passed the corresponding authentication, outputting a second prompt message, the second prompt message being used to inform the user that there is no abnormal situation with the instrument cluster.

[0118] In this embodiment, it can be understood that during the authentication of the instrument cluster, if authentication fails even once, an anomaly display should be triggered and a first prompt message should be output. This first prompt message is used to alert the user that there is an anomaly with the instrument cluster. Only when the instrument cluster successfully completes two authentication attempts should a second prompt message be output, informing the user that there is no anomaly with the instrument cluster.

[0119] Optionally, when the initial authentication result and / or final authentication result indicate that the instrument cluster has failed the corresponding authentication, the corresponding status of the instrument cluster is sent to the signal forwarding module via a CAN message. The signal forwarding module performs characteristic signal processing on the instrument cluster, which can trigger an abnormal display and record the status of the instrument cluster.

[0120] This application embodiment enables users to understand the status of the instrument cluster in a timely manner by providing targeted prompts on the authentication results, that is, to understand the compliance of the instrument cluster.

[0121] Next, we will illustrate how to use the vehicle instrument cluster authentication method provided in the embodiments of this application. Figure 2 A flowchart illustrating the authentication method for a vehicle instrument cluster provided in this application embodiment. Figure 2 ,like Figure 2 As shown, the method includes the following:

[0122] 1. The timestamp factors corresponding to the part number, supplier code, and identification code of the instrument cluster are entered into the big data system of the remote platform through the remote platform APP software. The platform's functions are as follows: to effectively enter the timestamp factors corresponding to the part number, supplier code, and identification code of the instrument cluster; and to calculate the serial number (SN) by the remote platform itself. The remote platform can also be referred to as a cloud platform.

[0123] 2. Assign a specific DID code to the instrument cluster. The DID code is used to store and read the SN and supports diagnostic commands 22 and 2E.

[0124] 3. Each time the vehicle is ignited (IGN off→on), the Master module first reads the Vehicle Identification Number (VIN) built into the instrument cluster via the UDS 22 command. If the built-in VIN is empty or incorrect, the Master module will read the corresponding VIN from the cloud platform via the MQTT / ***_master / read_***_VIN command and initiate the UDS 2E command to complete the VIN writing operation. To enhance security, before initiating the VIN writing operation, the cloud platform and the instrument cluster will first perform a CMAC asymmetric key handshake protocol to establish a secure communication channel. The key to this key protocol is that the key is stored only on the remote commercial vehicle and the supplier side, i.e., only on the cloud platform and the supplier side, and the key length has been upgraded from 8 bits to 16 bits, significantly enhancing security. Furthermore, after completing the VIN writing operation, a write flag needs to be set inside the instrument cluster. If the write flag is set to 1, it indicates that a new VIN has been written to the instrument cluster; this is the initial authentication measure.

[0125] It is also understandable that when initiating the UDS 2E command to complete the instrument cluster identification code writing operation, it is necessary to determine whether the Diagnostic 27 command satisfies the CMAC algorithm. The Diagnostic 27 command, as a core service for secure access in automotive diagnostics, establishes a secure connection through the challenge-response mechanism in the asymmetric handshake protocol. During this process, its underlying security mechanism can further employ the CMAC algorithm to enhance the security of key calculation or message authentication, ensuring the integrity and authenticity of communication.

[0126] It should be noted that the initial authentication result is determined based on whether the cloud platform and the instrument cluster have been authenticated through the asymmetric key handshake protocol.

[0127] 4. The instrument cluster determines the write flag bit. If the write flag bit is 1, it reads the written identification code and extracts a specific number of digits from the identification code. Through the NCM protocol, it combines the part number, supplier code, and timestamp factor, and generates the SN through a specific XOR calculation. The SN is then saved to the non-lost storage space EPPROM module, and the flag bit is written to 0 simultaneously.

[0128] 5. Each time the vehicle is started (IGN off→on), the instrument cluster will check if the SN is empty. If the SN has been generated, that is, if the SN is not empty, the instrument cluster will send it to the cloud platform via MQTT / ***_IPK / seed_***_SN within 2 minutes after the vehicle is started. When the cloud platform receives the SN, it will compare it with the SN calculated by the cloud platform itself. The comparison result will be sent to the Master module via MQTT / ***_master / seed_***_SN_Status. This is the second authentication measure.

[0129] 6. If the instrument cluster passes both authentications, the Master module will not require special processing, and the vehicle will function normally.

[0130] 7. If the instrument cluster fails either of the two authentication attempts, the instrument cluster identification is considered to have failed. The Master module sends the status to the signal forwarding module via CAN message. The signal forwarding module performs development feature signal processing, which can trigger the instrument cluster to display an abnormality and record a Diagnostic Trouble Code (DTC). The remote cloud platform will send an identification failure SMS to the customer.

[0131] It is understandable that Master supports cloud platform data reading and uses the CMAC asymmetric key handshake protocol to automatically complete the writing of the VIN code of the replacement instrument combination.

[0132] Furthermore, from Figure 2 It is also known that before authenticating the instrument cluster, a factory verification is required. Only after the instrument cluster passes the factory verification can subsequent identity verification be performed. The factory verification of the instrument cluster can be performed as follows: During the vehicle's first ignition, at the end-of-line (EOL) stage, a diagnostic 27 command request containing a CMAC value is written using an electronic testing device. Based on the returned response, it is determined whether the diagnostic 27 command satisfies the CMAC algorithm. The result determines whether the vehicle's instrument cluster conforms to the development strategy. Specifically, if the result is negative, the vehicle's instrument cluster does not conform to the development strategy, and production must be stopped; if the result is positive, the instrument cluster is then authenticated.

[0133] Furthermore, Figure 3 This is a schematic diagram of the system structure corresponding to the authentication method for the vehicle instrument cluster provided in this application embodiment. For example... Figure 3 As shown, the system includes a cloud platform, a main controller, and a combination instrument. The combination instrument and the main controller are connected via a USB cable; that is, they are connected through a USB link, and the main controller is connected to the cloud platform via the same USB cable. The combination instrument supports MQTT special commands, thereby enabling direct data interaction with the cloud platform.

[0134] The following are embodiments of the apparatus described in this application, which can be used to execute the embodiments of the method described in this application. For details not disclosed in the apparatus embodiments of this application, please refer to the embodiments of the method described in this application.

[0135] Figure 4 This is a schematic diagram of the structure of the authentication device for the vehicle instrument cluster provided in the embodiments of this application, as shown below. Figure 4 As shown, the vehicle instrument cluster authentication device 400 provided in this embodiment includes:

[0136] The acquisition module 401 is used to acquire the first identification code of the combination instrument in the vehicle in response to the detection of vehicle ignition;

[0137] The determination module 402 is used to determine the target identification code of the instrument cluster based on the first identification code; and to determine the initial authentication result of the instrument cluster based on the target identification code.

[0138] The determination module 402 is further configured to determine the serial number matching result of the instrument cluster based on the target identifier code when the initial authentication result indicates that the instrument cluster has passed the initial authentication; and to determine the final authentication result of the instrument cluster based on the serial number matching result.

[0139] In one possible implementation, the determining module 402 is specifically used for:

[0140] Determine whether the first identifier code conforms to the identifier code rules;

[0141] If the first identifier does not conform to the identifier rule, the target identifier is determined based on the second identifier of the combined instrument obtained from the cloud platform.

[0142] If the first identifier code conforms to the identifier code rules, then the first identifier code will be used as the target identifier code.

[0143] In one possible implementation, the determining module 402 is specifically used for:

[0144] Based on the Internet of Things (IoT) communication protocol, the second identification code of the combined instrument is obtained from the cloud platform, and the second identification code is determined as the target identification code.

[0145] In one possible implementation, the determining module 402 is specifically used for:

[0146] If the target identifier is the first identifier, then the initial identity verification result is determined to be successful.

[0147] If the target identifier is the second identifier, then determine whether the cloud platform and the combined instrument have been authenticated through the asymmetric key handshake protocol.

[0148] When the result of the judgment indicates that the authentication of the asymmetric key handshake protocol has been passed, the initial identity verification result is determined to be passed.

[0149] If the result of the judgment indicates that the authentication of the asymmetric key handshake protocol has failed, the initial identity verification result is determined to be an initial identity verification failure.

[0150] In one possible implementation, the determining module 402 is specifically used for:

[0151] When the initial authentication result indicates that the instrument cluster has passed the initial authentication, the third identification code of the instrument cluster is determined based on the target identification code.

[0152] Based on the third identification code, generate the first serial number corresponding to the instrument cluster;

[0153] The first serial number is matched with the second serial number corresponding to the instrument cluster obtained from the cloud platform to determine the serial number matching result of the instrument cluster.

[0154] In one possible implementation, the determining module 402 is specifically used for:

[0155] The first serial number corresponding to the instrument cluster is generated based on the third identifier, supplier code, part number of the instrument cluster, and timestamp factor corresponding to the first identifier. The supplier code, part number, and timestamp factor are obtained from the cloud platform through the Network Control Model (NCM) protocol.

[0156] In one possible implementation, the authentication device of the vehicle instrument cluster further includes an output module (not shown), which is specifically used for:

[0157] When the initial authentication result and / or the final authentication result indicate that the instrument cluster has failed the corresponding authentication, the abnormal display of the instrument cluster is triggered and the first prompt message is output. The first prompt message is used to remind the user that there is an abnormal situation with the instrument cluster.

[0158] And / or, when the final authentication result indicates that the instrument cluster has passed the corresponding authentication, a second prompt message is output, which is used to inform the user that there is no abnormality in the instrument cluster.

[0159] The vehicle instrument cluster authentication device provided in this embodiment can execute the method provided in the above method embodiment. Its implementation principle and technical effect are similar, and will not be described in detail here.

[0160] It should be noted that the division of the various modules in the above device is merely a logical functional division. In actual implementation, they can be fully or partially integrated into a single physical entity, or they can be physically separated. Furthermore, these modules can be implemented entirely in software via processing element calls; they can be fully implemented in hardware; or some modules can be implemented by processing element calls to software, while others are implemented in hardware. For example, a processing module can be a separate processing element, or it can be integrated into a chip within the device. Alternatively, it can be stored as program code in the device's memory, and its functions can be called and executed by a processing element. The implementation of other modules is similar. Moreover, these modules can be fully or partially integrated together, or they can be implemented independently. The processing element here can be an integrated circuit with signal processing capabilities. During implementation, each step of the above method or each of the above modules can be completed through integrated logic circuits in the hardware of the processor element or through software instructions.

[0161] For example, these modules can be one or more integrated circuits configured to implement the above methods, such as one or more Application Specific Integrated Circuits (ASICs), one or more Digital Signal Processors (DSPs), or one or more Field Programmable Gate Arrays (FPGAs). As another example, when a module is implemented using processing element scheduler code, the processing element can be a general-purpose processor, such as a Central Processing Unit (CPU) or other processor capable of calling program code. Furthermore, these modules can be integrated together as a System-On-a-Chip (SOC).

[0162] Figure 5 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application. Figure 5 As shown, the electronic device 500 provided in this application embodiment may include: a processor 501, and a memory 502 communicatively connected to the processor, wherein:

[0163] The memory stores the instructions that the computer executes;

[0164] The processor executes computer execution instructions stored in memory to implement the method described in the foregoing method embodiments.

[0165] It should be understood that processor 501 can be a Central Processing Unit (CPU), or other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), etc. A general-purpose processor can be a microprocessor or any conventional processor. The steps of the method disclosed in the application can be directly manifested as execution by a hardware processor, or execution by a combination of hardware and software modules within the processor. Memory 502 may include high-speed random access memory (RAM), and may also include non-volatile memory (NVM), such as at least one disk storage device, or a USB flash drive, external hard drive, read-only memory, disk, or optical disc, etc.

[0166] Optionally, the electronic device 500 may also include a communication interface 503. In specific implementations, if the communication interface 503, memory 502, and processor 501 are implemented independently, they can be interconnected via a bus to complete communication. The bus can be an Industry Standard Architecture (ISA) bus, a Peripheral Component Interconnect (PCI) bus, or an Extended Industry Standard Architecture (EISA) bus, etc. Buses can be categorized as address buses, data buses, control buses, etc., but this does not imply that there is only one bus or one type of bus.

[0167] Optionally, in a specific implementation, if the communication interface 503, memory 502, and processor 501 are integrated on a single chip, then the communication interface 503, memory 502, and processor 501 can communicate through an internal interface.

[0168] This application also provides a computer-readable storage medium storing computer-executable instructions, which, when executed, are used to implement the methods described in any of the foregoing embodiments.

[0169] It is understood that the computer-readable storage medium can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as Static Random Access Memory (SRAM), Electrically Erasable Programmable Read Only Memory (EEPROM), Erasable Programmable Read Only Memory (EPROM), Programmable Read Only Memory (PROM), Read Only Memory (ROM), magnetic storage, flash memory, magnetic disk, or optical disk. The readable storage medium can be any available medium accessible to a general-purpose or special-purpose computer.

[0170] An exemplary computer-readable storage medium is coupled to a processor, enabling the processor to read information from and write information to the computer-readable storage medium. Of course, the computer-readable storage medium can also be a component of the processor. The processor and the computer-readable storage medium can reside in an ASIC. Alternatively, the processor and the computer-readable storage medium can exist as discrete components in an electronic device.

[0171] The integrated modules implemented as software functional modules described above can be stored in a computer-readable storage medium. These software functional modules, stored in a computer-readable storage medium, include several instructions to cause an electronic device (which may be a personal computer, server, or network device, etc.) or processor to execute some steps of the methods described in the various embodiments of this application.

[0172] This application also provides a computer program product, including a computer program that, when executed, implements the method described in any of the foregoing embodiments.

[0173] This application also provides a vehicle, including a vehicle body and the method described in any of the foregoing embodiments.

[0174] It should be noted that, for the sake of simplicity, the foregoing method embodiments are all described as a series of actions. However, those skilled in the art should understand that this application is not limited to the described order of actions, as some steps may be performed in other orders or simultaneously according to this application. Furthermore, those skilled in the art should also understand that the embodiments described in the specification are all optional embodiments, and the actions and modules involved are not necessarily essential to this application.

[0175] It should be further noted that although the steps in the flowchart are shown sequentially according to the arrows, these steps are not necessarily executed in the order indicated by the arrows. Unless explicitly stated herein, there is no strict order restriction on the execution of these steps, and they can be executed in other orders. Moreover, at least some steps in the flowchart may include multiple sub-steps or multiple stages. These sub-steps or stages are not necessarily completed at the same time, but can be executed at different times. The execution order of these sub-steps or stages is not necessarily sequential, but can be performed alternately or in turn with other steps or at least some of the sub-steps or stages of other steps.

[0176] In the above embodiments, the descriptions of each embodiment have their own emphasis. For parts not described in detail in a certain embodiment, please refer to the relevant descriptions of other embodiments. The technical features of the above embodiments can be combined arbitrarily. For the sake of brevity, not all possible combinations of the technical features in the above embodiments are described. However, as long as the combination of these technical features does not contradict each other, it should be considered within the scope of this specification.

[0177] Other embodiments of this application will readily occur to those skilled in the art upon consideration of the specification and practice of the invention disclosed herein. This application is intended to cover any variations, uses, or adaptations of this application that follow the general principles of this application and include common knowledge or customary techniques in the art not disclosed herein. The specification and examples are to be considered exemplary only, and the true scope and spirit of this application are indicated by the following claims.

[0178] It should be understood that this application is not limited to the precise structure described above and shown in the accompanying drawings, and various modifications and changes can be made without departing from its scope. The scope of this application is limited only by the appended claims.

Claims

1. A method for authenticating a vehicle instrument cluster, characterized in that, include: Upon detecting vehicle ignition, the first identification code of the instrument cluster in the vehicle is obtained. The target identification code of the instrument cluster is determined based on the first identification code; Based on the target identifier code, determine the initial identity verification result of the combined instrument; When the initial authentication result indicates that the instrument cluster has passed the initial authentication, the serial number matching result of the instrument cluster is determined according to the target identifier code. Based on the serial number matching result, the final identity verification result of the instrument combination is determined.

2. The method according to claim 1, characterized in that, Determining the target identifier code of the instrument cluster based on the first identifier code includes: Determine whether the first identifier code conforms to the identifier code rules; If the first identifier does not conform to the identifier rule, then the target identifier is determined based on the second identifier of the combined instrument obtained from the cloud platform; If the first identifier code conforms to the identifier code rule, then the first identifier code is used as the target identifier code.

3. The method according to claim 2, characterized in that, Determining the target identifier code based on the second identifier code of the combined instrument obtained from the cloud platform includes: Based on the Internet of Things communication protocol, the second identification code of the combined instrument is obtained from the cloud platform, and the second identification code is determined as the target identification code.

4. The method according to claim 3, characterized in that, The step of determining the initial identity verification result of the instrument cluster based on the target identifier code includes: If the target identifier is the first identifier, then the initial identity verification result is determined to be successful. If the target identifier is the second identifier, then determine whether the cloud platform and the combined instrument have been authenticated through the asymmetric key handshake protocol; When the result of the judgment indicates that the authentication has been passed through the asymmetric key handshake protocol, the initial identity verification result is determined to be passed. When the result of the judgment indicates that the authentication of the asymmetric key handshake protocol has failed, the initial identity verification result is determined to be an initial identity verification failure.

5. The method according to any one of claims 1 to 4, characterized in that, When the initial authentication result indicates that the instrument cluster has passed the initial authentication, the serial number matching result of the instrument cluster is determined based on the target identifier code, including: When the initial authentication result indicates that the instrument cluster has passed the initial authentication, the third identification code of the instrument cluster is determined based on the target identification code. Based on the third identification code, a first serial number corresponding to the instrument cluster is generated; The first serial number is matched with the second serial number corresponding to the instrument cluster obtained from the cloud platform to determine the serial number matching result of the instrument cluster.

6. The method according to claim 5, characterized in that, The step of generating the first serial number corresponding to the instrument cluster based on the third identifier includes: A first serial number corresponding to the instrument combination is generated based on the third identifier, the supplier code, the part number of the instrument combination, and the timestamp factor corresponding to the first identifier. The supplier code, the part number, and the timestamp factor are obtained from the cloud platform through the Network Control Model (NCM) protocol.

7. The method according to any one of claims 1 to 4, characterized in that, Also includes: When the initial authentication result and / or the final authentication result indicate that the instrument cluster has failed the corresponding authentication, the abnormal display of the instrument cluster is triggered and a first prompt message is output. The first prompt message is used to remind the user that there is an abnormality in the instrument cluster. And / or, when the final authentication result indicates that the instrument cluster has passed the corresponding authentication, a second prompt message is output, which is used to inform the user that there is no abnormality in the instrument cluster.

8. An authentication device for a vehicle instrument cluster, characterized in that, include: The acquisition module is used to acquire the first identification code of the instrument cluster in the vehicle in response to the detection of vehicle ignition; The determining module is used to determine the target identification code of the combined instrument based on the first identification code; The determining module is further configured to determine the initial identity verification result of the combined instrument based on the target identifier code; The determining module is further configured to determine the serial number matching result of the combined instrument based on the target identification code when the initial authentication result indicates that the combined instrument has passed the initial authentication. The determining module is further configured to determine the final identity verification result of the combined instrument based on the serial number matching result.

9. An electronic device, characterized in that, include: Memory, processor; The memory stores computer-executed instructions; The processor executes computer execution instructions stored in the memory, causing the processor to perform the method as described in any one of claims 1-7.

10. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer-executable instructions, which, when executed, are used to implement the method as described in any one of claims 1-7.

11. A computer program product, characterized in that, Includes a computer program that, when executed, implements the method described in any one of claims 1-7.

12. A vehicle, characterized in that, Includes the vehicle body and the method as described in any one of claims 1 to 7.

Images