Vehicle-mounted controller identification method and related device

Abstract

The invention relates to the technical field of vehicle-mounted controller detection, in particular to a vehicle-mounted controller identification method and a related device. The method comprises the following steps: acquiring software version information identified by the software version identification unit aiming at the vehicle-mounted controller; comparing the software version information with preset baseline version information to obtain a first comparison result; obtaining appearance information recognized by the appearance recognition unit for the vehicle-mounted controller; comparing the appearance information with preset reference appearance information to obtain a second comparison result; and according to the first comparison result and the second comparison result, determining whether the vehicle-mounted controller has a version abnormity, and obtaining a vehicle-mounted controller identification result. According to the method, the vehicle-mounted controller identification result can be accurately obtained, and the identification efficiency and the identification accuracy of the vehicle-mounted controller are improved on the basis of realizing software automatic identification.

Description

Technical Field

[0001] This application relates to the field of vehicle controller detection technology, and in particular to a vehicle controller identification method and related apparatus. Background Technology

[0002] With the rapid development of intelligent, electric, and connected vehicles, the number of onboard control units or controllers is constantly increasing, and the functions of system integration are becoming increasingly complex. This complexity is reflected not only at the hardware level but also at the software level, especially in the management and upgrading of vehicle software versions. Currently, the increasing differentiation of vehicle software versions leads to problems such as incorrect module installation and inconsistent software versions on the production line. These problems not only affect the normal production and testing of automobiles but may also lead to difficulties in subsequent maintenance and upgrades. Therefore, identifying whether there are version anomalies in vehicle controllers is particularly important. Regarding the solution to automatically identify controller software version, supplier assembly number, software part number and other information, and timely detect the problem of incorrect controller installation on the production line and the problem of inconsistent version matching during electrical testing, the existing methods cannot achieve automated management and identification of vehicle software versions, resulting in waste of resources, high costs and low work efficiency. Summary of the Invention

[0003] To address the aforementioned issues, this application provides a vehicle controller identification method and related apparatus, which can improve the automated management and identification of vehicle software versions.

[0004] According to one aspect of the embodiments of this application, a vehicle controller identification method is proposed, applied to a vehicle software identification system, the vehicle software identification system including a software version identification unit and an appearance identification unit, the method comprising: Obtain the software version information identified by the software version identification unit for the vehicle controller; The software version information is compared with the preset baseline version information to obtain the first comparison result; Obtain the appearance information identified by the appearance recognition unit for the vehicle controller; The appearance information is compared with the preset benchmark appearance information to obtain a second comparison result; Based on the first comparison result and the second comparison result, it is determined whether the vehicle controller has a version anomaly, and the vehicle controller identification result is obtained.

[0005] In the above scheme, obtaining the software version information identified by the software version identification unit for the vehicle controller includes: Obtain the software version number, supply-level assembly number, and software part number identified by the software version identification unit for the vehicle controller; The software version number, the supplier-level assembly number, and the software part number are used as the software version information.

[0006] In the above scheme, comparing the software version information with preset baseline version information to obtain a first comparison result includes: The software version number is compared with the preset baseline version information to obtain a comparison sub-result corresponding to the software version number; The supplier-level assembly number is compared with the preset baseline version information to obtain the comparison sub-result corresponding to the supplier-level assembly number; The software part number is compared with the preset baseline version information to obtain a comparison sub-result corresponding to the software part number; The comparison result corresponding to the software version number, the comparison result corresponding to the supplier-level assembly number, and the comparison result corresponding to the software part number are used as the first comparison result.

[0007] In the above scheme, obtaining the appearance information recognized by the appearance recognition unit for the vehicle controller includes: Acquire two-dimensional image information recognized by the appearance recognition unit for the vehicle controller; Acquire the three-dimensional image information identified by the appearance recognition unit for the vehicle controller; The two-dimensional image information and the three-dimensional image information are used as the appearance information.

[0008] In the above scheme, comparing the appearance information with preset benchmark appearance information to obtain a second comparison result includes: The two-dimensional image information is compared with the preset baseline appearance information to obtain a comparison sub-result corresponding to the two-dimensional image information; The three-dimensional image information is compared with the preset baseline appearance information to obtain a comparison sub-result corresponding to the three-dimensional image information; The pairing results corresponding to the two-dimensional image information and the pairing results corresponding to the three-dimensional image information are used as the second pairing results.

[0009] In the above scheme, the step of determining whether the vehicle controller has a version anomaly based on the first comparison result and the second comparison result, and obtaining the vehicle controller identification result, includes: If the first comparison result is that the software version information does not match the preset baseline version information, then it is determined that the vehicle controller has a version abnormality, and the vehicle controller identification result of the vehicle controller abnormality is obtained. If the first comparison result is that the software version information matches the preset baseline version information but the appearance information does not match the preset baseline appearance information, then it is determined that the vehicle controller has a version abnormality, and the vehicle controller identification result of the vehicle controller abnormality is obtained. If the first comparison result shows that the software version information matches the preset baseline version information and the appearance information matches the preset baseline appearance information, then the vehicle controller is determined to be a normal version, and a normal vehicle controller identification result is obtained.

[0010] In the above scheme, the method further includes: If a normal vehicle controller identification result is obtained, then the version difference between the software version information and the preset comparison version information is determined. If the version difference is greater than or equal to a preset version difference threshold, the vehicle controller will be upgraded with software.

[0011] According to one aspect of the embodiments of this application, an in-vehicle controller identification device is proposed, applied to a vehicle software identification system, the vehicle software identification system including a software version identification unit and an appearance identification unit, the device comprising: The first acquisition unit is used to acquire the software version information identified by the software version identification unit for the vehicle controller; The first comparison unit is used to compare the software version information with the preset baseline version information to obtain a first comparison result. The second acquisition unit is used to acquire the appearance information identified by the appearance recognition unit for the vehicle controller; The second comparison unit is used to compare the appearance information with preset benchmark appearance information to obtain a second comparison result; The judgment unit is used to determine whether the vehicle controller has a version abnormality based on the first comparison result and the second comparison result, and to obtain the vehicle controller identification result.

[0012] According to one aspect of the embodiments of this application, an electronic device is provided, including a memory and a processor, wherein the memory stores a computer program, and the processor executes the computer program to implement the vehicle controller identification method as described above. According to one aspect of the embodiments of this application, a computer program product is provided, the computer program product including a computer program, the computer program being read and executed by a processor of an electronic device, causing the electronic device to perform the vehicle controller identification method as described above.

[0013] The beneficial effects of this application are as follows: This application obtains the software version information identified by the software version identification unit for the vehicle controller, and then compares it with preset baseline version information to obtain a first comparison result. By obtaining the appearance information identified by the appearance identification unit for the vehicle controller, it can compare it with preset benchmark appearance information to obtain a second comparison result. By combining the first and second comparison results, it is possible to comprehensively determine whether the vehicle controller has version anomalies, thereby accurately obtaining the vehicle controller identification result. Based on the realization of automated software identification, this application improves the identification efficiency and accuracy of the vehicle controller. Attached Figure Description

[0014] Figure 1 This is a system architecture diagram of the vehicle controller identification method provided in the embodiments of this application; Figure 2 A flowchart illustrating the vehicle controller identification method provided in this application embodiment; Figure 3 This is an architecture diagram of the vehicle software recognition system provided in the embodiments of this application; Figure 4 A block diagram of the vehicle controller identification device provided in the embodiments of this application; Figure 5 This is a schematic diagram of the structure of a terminal provided in an embodiment of this application; Figure 6 This is a schematic diagram of the structure of a server provided in an embodiment of this application. Detailed Implementation

[0015] To enable those skilled in the art to better understand the solutions of this application, the technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, and not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0016] It should be noted that while some processes described in the specification, claims, and accompanying drawings include multiple steps appearing in a specific order, it should be clearly understood that these steps may not be performed in the order they appear herein, or may be performed in parallel. The step numbers are merely used to distinguish different steps and do not themselves represent any execution order. Furthermore, descriptions such as "first," "second," or "objective" in this document are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. "Multiple" in this document refers to at least two.

[0017] It is worth noting that in the specific embodiments of this application, software version information, appearance information, and other related data are involved. When the above embodiments of this application are applied to specific products or technologies, permission or consent from the target object is required, and the collection, use, and processing of related data must comply with relevant laws, regulations, and standards. For example, when an embodiment of this application needs to obtain software version information, appearance information, and other related data, separate permission or consent from the target object can be obtained through pop-up windows or redirection to a confirmation page. After obtaining separate permission or consent from the target object, the necessary software version information, appearance information, and other related data for enabling the embodiments of this application to operate normally can then be obtained.

[0018] Please see Figure 1 , Figure 1 This is a system architecture diagram of the vehicle controller identification method provided in this application embodiment. It includes a terminal 140, an Internet connection 130, a gateway 120, a server 110, etc.

[0019] Terminal 140 can take various forms, including desktop computers, laptops, PDAs (personal digital assistants), mobile phones, vehicle terminals, and dedicated terminals. Furthermore, it can be a single device or a collection of multiple devices. For example, multiple desktop computers can be interconnected via a local area network, sharing a single monitor to work collaboratively, forming a single terminal 140. Terminal 140 can communicate with the Internet 130 via wired or wireless means to exchange data.

[0020] Server 110 refers to a computer system capable of providing certain services to terminal 140. Compared to ordinary terminal 140, server 110 has higher requirements in terms of stability, security, and performance. Server 110 can be a single high-performance computer in a network platform, a cluster of multiple high-performance computers, a portion of a single high-performance computer (e.g., a virtual machine), or a combination of portions of multiple high-performance computers (e.g., virtual machines). Server 110 can also communicate with the Internet 130 via wired or wireless means to exchange data.

[0021] Gateway 120, also known as an internetwork connector or protocol converter, is a computer system or device that acts as a translator, enabling network interconnection at the transport layer. It bridges the gap between two systems using different communication protocols, data formats, languages, or even completely different architectures. Gateways can also provide filtering and security functions. Messages sent from terminal 140 to server 110 are forwarded to the corresponding server 110 via gateway 120. Messages sent from server 110 to terminal 140 are also forwarded to the corresponding terminal 140 via gateway 120.

[0022] The following provides a detailed description of the specific implementation methods of the embodiments of this application: Please see Figure 2 , Figure 2 This is a flowchart illustrating the vehicle controller identification method provided in this application embodiment. The vehicle controller identification method can be implemented by server 110 and / or terminal 140. Figure 2 The vehicle controller identification method shown includes: Step 210: Obtain the software version information identified by the software version identification unit for the vehicle controller; Step 220: Compare the software version information with the preset baseline version information to obtain the first comparison result; Step 230: Obtain the appearance information identified by the appearance recognition unit for the vehicle controller; Step 240: Compare the appearance information with the preset benchmark appearance information to obtain a second comparison result; Step 250: Determine whether the vehicle controller has a version anomaly based on the first comparison result and the second comparison result, and obtain the vehicle controller identification result.

[0023] The complete embodiment of this application will be explained in detail below with reference to steps 210-250: First, the vehicle software identification system of this application includes a software version identification unit and an appearance identification unit. The software version identification unit uses a set of dedicated chips to identify the software version, and identifies and parses the software version information, supply-level assembly number, and software part number of the vehicle controller. This software version identification unit also includes a set of high-precision resistance, capacitance, and voltage sensors for real-time monitoring of the vehicle controller's operating status. The appearance identification unit uses machine vision recognition technology, employing a high-definition camera and optical lens to identify and analyze the appearance features of the vehicle controller, combining the identification results with those from the software version identification unit to improve identification accuracy.

[0024] In step 210, the software version identification unit uses a set of dedicated chips to identify the software version, and identifies and parses the software version information, supplier assembly number, and software part number of the vehicle controller. The software version identification unit also includes a set of high-precision resistance, capacitance, and voltage sensors for real-time monitoring of the vehicle controller's operating status.

[0025] In step 220, the identification result of the software version information is uploaded to the server and compared with the baseline version information preset in the database unit to obtain the first comparison result.

[0026] If the first comparison result is that the software version information does not match the preset baseline version information, then it is determined that the vehicle controller has a version abnormality, and the vehicle controller identification result of the vehicle controller abnormality is obtained. If the first comparison result is that the software version information matches the preset baseline version information but the appearance information does not match the preset baseline appearance information, then it is determined that the vehicle controller has a version abnormality, and the vehicle controller identification result of the vehicle controller abnormality is obtained. If the first comparison result shows that the software version information matches the preset baseline version information and the appearance information matches the preset baseline appearance information, then the vehicle controller is determined to be a normal version, and a normal vehicle controller identification result is obtained.

[0027] If the first comparison result shows that the software version information does not match the preset baseline version information, a prompt message is generated and relevant personnel are notified to handle the issue.

[0028] In some embodiments, comparing the software version information with preset baseline version information to obtain a first comparison result includes: The software version number is compared with the preset baseline version information to obtain a comparison sub-result corresponding to the software version number; The supplier-level assembly number is compared with the preset baseline version information to obtain the comparison sub-result corresponding to the supplier-level assembly number; The software part number is compared with the preset baseline version information to obtain a comparison sub-result corresponding to the software part number; The comparison result corresponding to the software version number, the comparison result corresponding to the supplier-level assembly number, and the comparison result corresponding to the software part number are used as the first comparison result.

[0029] Specifically, the baseline version information contains information from multiple dimensions, such as software version number baseline information, supplier-level assembly number baseline information, and software part number baseline information. These are compared one by one with the software version number, supplier-level assembly number, and software part number to obtain multiple comparison sub-results. Finally, these comparison sub-results are integrated as the first comparison result.

[0030] In step 230, the appearance recognition unit performs appearance feature recognition on the vehicle controller, and combines the software version recognition result (software version information) to further improve the recognition accuracy; the recognition result (appearance information) is stored in a preset database unit to provide a basis for subsequent version monitoring and management.

[0031] In step 240, the appearance information is compared with preset benchmark appearance information to obtain a second comparison result. Here, two-dimensional image information recognized by the appearance recognition unit for the vehicle controller is acquired; three-dimensional image information recognized by the appearance recognition unit for the vehicle controller is acquired; the two-dimensional image information and the three-dimensional image information are used as the appearance information. The two-dimensional image information is compared with the preset benchmark appearance information to obtain a comparison sub-result corresponding to the two-dimensional image information; the three-dimensional image information is compared with the preset benchmark appearance information to obtain a comparison sub-result corresponding to the three-dimensional image information; the comparison sub-result corresponding to the two-dimensional image information and the comparison sub-result corresponding to the three-dimensional image information are used as the second comparison result.

[0032] In step 250, if the first comparison result is that the software version information does not match the preset baseline version information, it is determined that the vehicle controller has a version abnormality, and the vehicle controller identification result of the vehicle controller abnormality is obtained. If the first comparison result is that the software version information matches the preset baseline version information but the appearance information does not match the preset baseline appearance information, then it is determined that the vehicle controller has a version abnormality, and the vehicle controller identification result of the vehicle controller abnormality is obtained. If the first comparison result shows that the software version information matches the preset baseline version information and the appearance information matches the preset baseline appearance information, then the vehicle controller is determined to be a normal version, and a normal vehicle controller identification result is obtained.

[0033] If the first comparison result shows that the software version information does not match the preset baseline version information, a prompt message is generated and relevant personnel are notified to handle the issue.

[0034] If a normal vehicle controller identification result is obtained, then the version difference between the software version information and the preset comparison version information is determined. If the version difference is greater than or equal to a preset version difference threshold, the vehicle controller will be upgraded with software.

[0035] Here, 1) the monitoring terminal collects the vehicle's software version information through various testing equipment; 2) The data analysis unit analyzes the collected version information and calculates the degree of version differences; 3) If the version difference exceeds a preset threshold, an anomaly report will be generated; 4) The monitoring results are uploaded to the server via the network communication unit and stored in the data storage unit. The system also includes a version upgrade management module for dynamic upgrades of the vehicle software version. This module includes: an upgrade terminal for receiving upgrade instructions and software upgrade packages; a version verification unit for verifying the compliance and integrity of the upgraded software; an upgrade execution unit for executing the software upgrade based on the verification results; and an upgrade recording unit for recording relevant information during the upgrade process. The specific steps of the upgrade management are as follows: 1) The upgrade terminal receives the upgrade command and software upgrade package; 2) The version verification unit verifies the compliance of the upgrade software; 3) If the verification passes, the upgrade execution unit executes the software upgrade; 4) After the upgrade is completed, the upgrade recording unit records the upgrade version information; 5) The system automatically performs a self-check on the upgraded version to ensure a successful upgrade. This system, through smart factory technology, achieves intelligent identification of the vehicle controller software version, automatic comparison of version baselines, and real-time anomaly handling, effectively solving problems in existing technologies and improving vehicle production and maintenance efficiency.

[0036] like Figure 3As shown, this application provides a vehicle software identification system, including a software version identification unit, a database unit, a matching analysis unit, an anomaly handling unit, an intelligent identification unit, a workstation terminal, and a network communication unit. The software version identification unit uses a set of dedicated chips to identify software versions, recognizing and parsing the software version information, supplier assembly number, and software part number of the vehicle controller. This unit also includes a set of high-precision resistance, capacitance, and voltage sensors for real-time monitoring of the vehicle controller's operating status. The database unit is constructed from a relational database to store the vehicle's software baseline version information, supplier assembly number, and software part number. This database uses highly reliable storage devices, ensuring good data security and stability. The matching analysis unit uses a dedicated matching algorithm to compare the identification results with the baseline version information in the database one by one, calculating the degree of version difference. When the version difference is less than a preset threshold, it is determined to be a match. When the matching analysis results are inconsistent, the anomaly handling unit generates an anomaly prompt message and sends it to the mobile terminal of relevant personnel via the network communication unit. This unit also includes a set of LED lights and a speaker for on-site anomaly notification. The intelligent recognition unit employs machine vision technology, using a high-definition camera and optical lens to identify and analyze the appearance features of the vehicle controller. Combined with the recognition results from the software version recognition unit, this improves recognition accuracy. The workstation terminal uses an industrial-grade touchscreen to display recognition results, comparison analysis results, and anomaly alerts, enabling human-machine interaction. This terminal also has a printing function, allowing for the printing of recognition reports. The network communication unit utilizes an industrial-grade wireless network architecture to upload recognition and comparison analysis results to the server and receive baseline version information returned by the server. This unit also supports remote control and upgrade functions.

[0037] This application also provides a version monitoring module, including a monitoring terminal, a data analysis unit, a report generation unit, and a data storage unit. The monitoring terminal uses a set of embedded computers to collect vehicle software version information through various testing devices, including software version number, supply-level assembly number, and software part number. The data analysis unit uses data mining algorithms to analyze the collected version information and calculate the degree of version differences. This unit also includes a set of data statistical charts to visually display the version differences. The report generation unit generates a version monitoring report based on the analysis results, including a version difference analysis table, an anomaly cause analysis table, and a recommended action table. The data storage unit adopts a cloud storage architecture to store monitoring data and reports. This unit also includes a set of data backup devices to ensure data security.

[0038] This application also provides a version upgrade management module, including an upgrade terminal, a version verification unit, an upgrade execution unit, and an upgrade recording unit. The upgrade terminal receives upgrade instructions and software upgrade packages via a network communication unit, including the upgrade version number, upgrade content description, and upgrade steps. The version verification unit uses digital signature verification technology to verify the compliance and integrity of the upgraded software. This unit also includes a set of integrity verification codes to verify the integrity of the upgraded software. The upgrade execution unit executes the software upgrade based on the verification results of the version verification unit, including upgrade preparation, upgrade process monitoring, and upgrade completion steps. The upgrade recording unit records relevant information during the upgrade process, including the upgrade version number, upgrade time, upgrade device information, and upgrade results. This unit also includes a set of log analysis software for analyzing the causes of upgrade anomalies. This system, through smart factory technology, achieves intelligent identification of the vehicle controller software version, automatic comparison of version baselines, and real-time anomaly handling, effectively solving problems in existing technologies and improving vehicle production and maintenance efficiency.

[0039] Please see Figure 4 , Figure 4 This is a schematic diagram of the structure of the vehicle controller identification device provided in the embodiments of this application. The vehicle controller identification device is applied to a computer device, and the vehicle controller identification device may include: The first acquisition unit 401 is used to acquire the software version information identified by the software version identification unit for the vehicle controller. The first comparison unit 402 is used to compare the software version information with the preset baseline version information to obtain a first comparison result; The second acquisition unit 403 is used to acquire the appearance information identified by the appearance recognition unit for the vehicle controller; The second comparison unit 404 is used to compare the appearance information with the preset benchmark appearance information to obtain a second comparison result. The judgment unit 405 is used to determine whether the vehicle controller has a version abnormality based on the first comparison result and the second comparison result, and to obtain the vehicle controller identification result.

[0040] Reference Figure 5 , Figure 5 To implement the structural block diagram of a portion of the terminal 140 in this application embodiment, the terminal 140 includes: a radio frequency (RF) circuit 710, a memory 715, an input unit 730, a display unit 740, a sensor 750, an audio circuit 760, a wireless fidelity (WiFi) module 770, a processor 780, and a power supply 790, among other components. Those skilled in the art will understand that... Figure 5 The terminal 140 structure shown does not constitute a limitation on a mobile phone or computer, and may include more or fewer components than shown, or combine certain components, or have different component arrangements.

[0041] The RF circuit 710 can be used to receive and transmit signals during information transmission or calls. In particular, it receives downlink information from the base station and processes it with the processor 780; in addition, it transmits uplink data to the base station.

[0042] The memory 715 can be used to store software programs and modules. The processor 780 executes various terminal functions and vehicle controller identification processing by running the software programs and modules stored in the memory 715.

[0043] The input unit 730 can be used to receive input numeric or character information, and to generate key signal inputs related to the terminal's settings and function control. Specifically, the input unit 730 may include a touch panel 731 and other input devices 732.

[0044] The display unit 740 can be used to display input or provided information, as well as various menus of the terminal. The display unit 740 may include a display panel 741.

[0045] Audio circuitry 760, speaker 761, and microphone 762 provide an audio interface.

[0046] In this embodiment, the processor 780 included in the terminal 140 can execute the vehicle controller identification method of the previous embodiment.

[0047] The terminal 140 in this application embodiment includes, but is not limited to, mobile phones, computers, intelligent voice interaction devices, smart home appliances, vehicle terminals, and aircraft. This application embodiment can be applied to various scenarios, including but not limited to cloud technology, artificial intelligence, smart transportation, and assisted driving.

[0048] Figure 6This is a partial structural block diagram of a server 110 implementing an embodiment of this application. The server 110 can vary significantly due to different configurations or performance characteristics, and may include one or more central processing units (CPUs) 822 (e.g., one or more processors) and memory 832, and one or more storage media 830 (e.g., one or more mass storage devices) for storing application programs 842 or data 844. The memory 832 and storage media 830 can be temporary or persistent storage. The program stored in the storage media 830 may include one or more modules (not shown in the diagram), each module including a series of instruction operations on the server 110. Furthermore, the CPU 822 may be configured to communicate with the storage media 830 and execute the series of instruction operations in the storage media 830 on the server 110.

[0049] Server 110 may also include one or more power supplies 826, one or more wired or wireless network interfaces 850, one or more input / output interfaces 858, and / or one or more operating systems 841, such as Windows Server™, Mac OS X™, Unix™, Linux™, FreeBSD™, etc.

[0050] The central processing unit 822 in server 110 can be used to execute the vehicle controller identification method of the present application embodiments.

[0051] This application also provides a computer-readable storage medium for storing program code for executing the vehicle controller identification method of the foregoing embodiments.

[0052] This application also provides a computer program product, which includes a computer program. The processor of a computer device reads and executes the computer program, causing the computer device to perform the above-described vehicle controller identification method.

[0053] Furthermore, the terms “comprising” and “including”, and any variations thereof, are intended to cover non-exclusive inclusion, such that a process, method, system, product, or apparatus that includes a series of steps or units is not necessarily limited to those steps or units that are explicitly listed, but may include other steps or units that are not explicitly listed or that are inherent to such process, method, product, or apparatus.

[0054] It should be understood that in this application, "at least one (item)" means one or more, and "more than" means two or more. "And / or" is used to describe the relationship between related objects, indicating that three relationships can exist. For example, "A and / or B" can represent three cases: only A exists, only B exists, and both A and B exist simultaneously, where A and B can be singular or plural. The character " / " generally indicates that the preceding and following related objects are in an "or" relationship. "At least one (item) of the following" or similar expressions refer to any combination of these items, including any combination of single or plural items. For example, at least one (item) of a, b, or c can represent: a, b, c, "a and b", "a and c", "b and c", or "a and b and c", where a, b, and c can be single or multiple.

[0055] It should be understood that in the description of the embodiments of this application, "multiple" means two or more, "greater than", "less than", "exceeding" etc. are understood to exclude the number itself, and "above", "below", "within" etc. are understood to include the number itself.

[0056] In the several embodiments provided in this application, it should be understood that the disclosed systems, apparatuses, and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces, or indirect coupling or communication connection between apparatuses or units, and may be electrical, mechanical, or other forms.

[0057] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of the embodiments of this application, depending on actual needs.

[0058] Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit.

[0059] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods of the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0060] It should also be understood that the various implementation methods provided in this application can be combined arbitrarily to achieve different technical effects.

[0061] In the embodiments of this application, the terms "module" or "unit" refer to a computer program or part of a computer program that has a predetermined function and works with other related parts to achieve a predetermined goal, and can be implemented wholly or partially using software, hardware (such as processing circuitry or memory), or a combination thereof. Similarly, a processor (or multiple processors or memory) can be used to implement one or more modules or units. Furthermore, each module or unit can be part of an overall module or unit that includes the functionality of that module or unit.

[0062] The above is a detailed description of the embodiments of this application. However, this application is not limited to the above embodiments. Those skilled in the art can make various equivalent modifications or substitutions without departing from the spirit of this application. All such equivalent modifications or substitutions are included within the scope defined by the claims of this application.

Claims

1. A method for identifying an on-board controller, characterized in that, The method, applied to a vehicle software identification system, which includes a software version identification unit and an appearance identification unit, comprises: Obtain the software version information identified by the software version identification unit for the vehicle controller; The software version information is compared with the preset baseline version information to obtain the first comparison result; Obtain the appearance information identified by the appearance recognition unit for the vehicle controller; The appearance information is compared with the preset benchmark appearance information to obtain a second comparison result; Based on the first comparison result and the second comparison result, it is determined whether the vehicle controller has a version anomaly, and the vehicle controller identification result is obtained.

2. The vehicle controller identification method according to claim 1, characterized in that, The step of obtaining the software version information identified by the software version identification unit for the vehicle controller includes: Obtain the software version number, supply-level assembly number, and software part number identified by the software version identification unit for the vehicle controller; The software version number, the supplier-level assembly number, and the software part number are used as the software version information.

3. The vehicle controller identification method according to claim 2, characterized in that, The step of comparing the software version information with preset baseline version information to obtain a first comparison result includes: The software version number is compared with the preset baseline version information to obtain a comparison sub-result corresponding to the software version number; The supplier-level assembly number is compared with the preset baseline version information to obtain the comparison sub-result corresponding to the supplier-level assembly number; The software part number is compared with the preset baseline version information to obtain a comparison sub-result corresponding to the software part number; The comparison result corresponding to the software version number, the comparison result corresponding to the supplier-level assembly number, and the comparison result corresponding to the software part number are used as the first comparison result.

4. The vehicle controller identification method according to claim 1, characterized in that, The acquisition of appearance information recognized by the appearance recognition unit for the vehicle controller includes: Acquire two-dimensional image information recognized by the appearance recognition unit for the vehicle controller; Acquire the three-dimensional image information identified by the appearance recognition unit for the vehicle controller; The two-dimensional image information and the three-dimensional image information are used as the appearance information.

5. The vehicle controller identification method according to claim 4, characterized in that, The step of comparing the appearance information with preset benchmark appearance information to obtain a second comparison result includes: The two-dimensional image information is compared with the preset baseline appearance information to obtain a comparison sub-result corresponding to the two-dimensional image information; The three-dimensional image information is compared with the preset baseline appearance information to obtain a comparison sub-result corresponding to the three-dimensional image information; The pairing results corresponding to the two-dimensional image information and the pairing results corresponding to the three-dimensional image information are used as the second pairing results.

6. The vehicle controller identification method according to claim 1, characterized in that, The step of determining whether the vehicle controller has a version anomaly based on the first comparison result and the second comparison result, and obtaining the vehicle controller identification result, includes: If the first comparison result is that the software version information does not match the preset baseline version information, then it is determined that the vehicle controller has a version abnormality, and the vehicle controller identification result of the vehicle controller abnormality is obtained. If the first comparison result is that the software version information matches the preset baseline version information but the appearance information does not match the preset baseline appearance information, then it is determined that the vehicle controller has a version abnormality, and the vehicle controller identification result of the vehicle controller abnormality is obtained. If the first comparison result shows that the software version information matches the preset baseline version information and the appearance information matches the preset baseline appearance information, then the vehicle controller is determined to be a normal version, and a normal vehicle controller identification result is obtained.

7. The vehicle controller identification method according to claim 1, characterized in that, The method further includes: If a normal vehicle controller identification result is obtained, then the version difference between the software version information and the preset comparison version information is determined. If the version difference is greater than or equal to a preset version difference threshold, the vehicle controller will be upgraded with software.

8. A vehicle controller identification device, characterized in that, An apparatus for use in a vehicle software identification system, the vehicle software identification system including a software version identification unit and an appearance identification unit, the apparatus comprising: The first acquisition unit is used to acquire the software version information identified by the software version identification unit for the vehicle controller; The first comparison unit is used to compare the software version information with the preset baseline version information to obtain a first comparison result. The second acquisition unit is used to acquire the appearance information identified by the appearance recognition unit for the vehicle controller; The second comparison unit is used to compare the appearance information with preset benchmark appearance information to obtain a second comparison result; The judgment unit is used to determine whether the vehicle controller has a version abnormality based on the first comparison result and the second comparison result, and to obtain the vehicle controller identification result.

9. An electronic device comprising a memory and a processor, wherein the memory stores a computer program, characterized in that, When the processor executes the computer program, it implements the vehicle controller identification method according to any one of claims 1 to 7.

10. A computer program product, the computer program product comprising a computer program, characterized in that, The computer program is read and executed by the processor of the electronic device, causing the electronic device to perform the vehicle controller identification method according to any one of claims 1 to 7.

Images