Vehicle software and hardware association matching method and device

Abstract

The invention discloses a vehicle software and hardware association matching method and device, and the method comprises the steps: obtaining a hardware information base of a vehicle and a software and hardware relationship list of software when software version issuing is executed; based on the required hardware model, the required hardware version and the required interface version in the hardware information base and the software and hardware relation list, hardware model existence verification is carried out to obtain a hardware model existence verification result, and then based on the hardware model existence verification result, hardware version compatibility verification and interface version matching verification are respectively carried out to obtain a hardware model compatibility verification result; and correspondingly obtaining a hardware version compatibility verification result and an interface version matching verification result, and further determining a compatibility result of the current software version and the hardware information base. According to the method, automatic association matching of software and hardware versions is realized, the problem of flashing failure caused by version mismatching is effectively avoided, the incidence rate of software and hardware compatibility problems is remarkably reduced, and the collaboration efficiency of the software and hardware versions and the software release reliability in the vehicle development process are improved.

Description

Technical Field

[0001] This invention relates to the field of vehicle software and hardware version management technology, and in particular to a method and apparatus for matching vehicle software and hardware. Background Technology

[0002] Currently, in the pre-development stage of vehicles, the software and hardware systems are undergoing a critical period of high-frequency iteration. Because hardware parameter adjustments and software function optimizations must be carried out simultaneously during the R&D process, the lack of a precise version coordination mechanism can easily lead to version mismatches during software flashing. This mismatch not only directly causes flashing operations to fail but also triggers a series of chain reactions. Technical personnel must spend a significant amount of time troubleshooting version compatibility issues and repeatedly verifying the software and hardware matching logic, thus increasing manpower and time costs. According to statistics from actual projects, the ineffective working hours caused by such problems can account for more than 20% of the total debugging time, severely delaying development progress. Therefore, establishing a dynamic synchronization mechanism for software and hardware versions to achieve unified version management throughout the entire development process has become a core technical challenge that urgently needs to be addressed in current vehicle R&D. Summary of the Invention

[0003] To improve the efficiency of software and hardware version collaboration during vehicle development and to achieve automatic software and hardware version association and matching, this invention provides a vehicle software and hardware association and matching method and apparatus.

[0004] In a first aspect, embodiments of the present invention provide a vehicle hardware and software association matching method, which may include: When executing a software release, the vehicle's hardware information database and the software-hardware relationship list are obtained. Based on the required hardware models in the hardware information database and the software-hardware relationship list, a hardware model existence verification is performed to obtain the hardware model existence verification result. Based on the existence verification result of the hardware model, the required hardware version and required interface version in the hardware information database and the software and hardware relationship list, hardware version compatibility verification and interface version matching verification are performed respectively, and the corresponding hardware version compatibility verification result and interface version matching verification result are obtained. Based on the hardware model existence verification results, hardware version compatibility verification results, and interface version matching verification results, the compatibility result between the current software version and the hardware information database is determined.

[0005] In one or more optional embodiments of this application, the hardware information database includes multiple benchmark information tables corresponding to hardware; the benchmark information table includes benchmark hardware model, benchmark hardware version, and benchmark interface version; Based on the existence verification result of the hardware model, the required hardware version and required interface version in the hardware information database and the software-hardware relationship list, hardware version compatibility verification and interface version matching verification are performed respectively, resulting in corresponding hardware version compatibility verification results and interface version matching verification results, including: If the hardware model existence verification result indicates that the required hardware model exists in the hardware information database, then the baseline information table corresponding to the required hardware model is obtained, and the hardware version compatibility verification result is obtained based on whether the baseline hardware version in the baseline information table is greater than or equal to the required hardware version. If the hardware model existence verification result indicates that the required hardware model exists in the hardware information database, then the baseline information table corresponding to the required hardware model is obtained, and the interface version matching verification result is obtained based on whether the baseline interface version in the baseline information table is equal to the required interface version.

[0006] In one or more optional embodiments of this application, determining the compatibility result between the current software version and the hardware information database based on the hardware model existence verification result, hardware version compatibility verification result, and interface version matching verification result includes: If the hardware model existence verification result indicates that the required hardware model does not exist in the hardware information database, then the compatibility result between the current version of the software and the hardware information database indicates that there is an incompatibility item. If the hardware version compatibility verification result indicates that the baseline hardware version is greater than the required hardware version, then the compatibility result between the current software version and the hardware information database indicates that there is an incompatibility item. If the interface version matching verification result indicates that the baseline interface version is not equal to the required interface version, then the compatibility result between the current software version and the hardware information database indicates that there is an incompatibility item.

[0007] In one or more optional embodiments of this application, the following further includes: The hardware model existence verification, hardware version compatibility verification, and interface version matching verification are integrated into the software's CI / CD process.

[0008] In one or more optional embodiments of this application, the hardware information database is obtained in the following manner: Obtain the benchmark information tables corresponding to multiple hardware components; Each of the aforementioned baseline information tables is subjected to format and uniqueness checks to obtain hardware information verification results. If the hardware information verification result indicates that the benchmark information table has passed the verification, then the benchmark information table is added to the hardware information database.

[0009] In one or more optional embodiments of this application, after obtaining the compatibility result between the current version of the software and the hardware information database, the method further includes: If the compatibility results between the current version of the software and the hardware information database indicate that there are incompatible items in the current version of the software, then the release operation of the software will be stopped, and a difference notification will be generated based on the incompatibility items. If the compatibility result between the current version of the software and the hardware information database indicates that there are no incompatible items in the current version of the software, then the software release operation will continue.

[0010] Secondly, embodiments of the present invention provide a vehicle hardware and software association matching device, which may include: The acquisition module is used to acquire the vehicle's hardware information database and the software-hardware relationship list of the software when executing a software release. The first verification module is used to perform hardware model existence verification based on the required hardware model, required hardware version and required interface version in the hardware information database and the software and hardware relationship list, and obtain the hardware model existence verification result. The second verification module is used to perform hardware version compatibility verification and interface version matching verification based on the hardware model existence verification result, the required hardware version and required interface version in the hardware information database and the software and hardware relationship list, respectively, and obtain the corresponding hardware version compatibility verification result and interface version matching verification result. The determination module is used to determine the compatibility result between the current version of the software and the hardware information database based on the existence verification result of the hardware model, the compatibility verification result of the hardware version, and the matching verification result of the interface version.

[0011] Thirdly, embodiments of the present invention provide a computer-readable storage medium having a computer program / instruction stored thereon, which, when executed by a processor, implements the vehicle hardware and software association matching method as described above.

[0012] Fourthly, embodiments of the present invention provide a computer program product, including a computer program / instruction, which, when executed by a processor, implements the vehicle hardware and software association matching method as described above.

[0013] Fifthly, embodiments of the present invention provide a computer device, including a memory, a processor, and a computer program stored in the memory, wherein the processor executes the computer program to implement the vehicle hardware and software association matching method as described above.

[0014] The beneficial effects of the above-described technical solutions provided in the embodiments of the present invention include at least the following: This invention provides a vehicle hardware and software association matching method. When executing software release, the method obtains the vehicle's hardware information database and the software hardware and software relationship list. Based on the required hardware model, required hardware version, and required interface version in the hardware information database and the software hardware and software relationship list, the method performs hardware model existence verification, hardware version compatibility verification, and interface version matching verification to obtain the compatibility result between the current software version and the hardware information database.

[0015] This method, based on a standardized hardware information database, provides a unified and reliable data benchmark for software and hardware version management. During the software release phase, it automatically retrieves the software's hardware relationship list and performs hardware model existence verification, hardware version compatibility verification, and interface version matching verification based on the hardware information database, ultimately generating accurate compatibility results. This systematic verification mechanism effectively identifies version mismatch issues, preventing flashing failures caused by software and hardware version mismatches from the outset.

[0016] Meanwhile, by integrating the aforementioned verification process into the vehicle development process, automated verification of software and hardware compatibility was achieved. This method not only significantly improves the efficiency of software and hardware version collaboration during vehicle development but also ensures the reliability and stability of software releases, forming a complete closed loop from version management to automated verification, providing a reliable quality assurance mechanism for vehicle development.

[0017] Furthermore, this method reduces manual intervention through a standardized verification process, significantly decreasing version matching errors caused by human error, while improving the efficiency of problem localization and resolution. This automated correlation matching mechanism provides an effective solution for collaborative software and hardware development in complex systems.

[0018] Other features and advantages of the invention will be set forth in the following description, and will be apparent in part from the description, or may be learned by practicing the invention. The objects and other advantages of the invention may be realized and obtained by means of the structures particularly pointed out in the written description and the accompanying drawings.

[0019] The technical solution of the present invention will be further described in detail below with reference to the accompanying drawings and embodiments. Attached Figure Description

[0020] The accompanying drawings are provided to further illustrate the invention and form part of the specification. They are used in conjunction with embodiments of the invention to explain the invention and do not constitute a limitation thereof. In the drawings: Figure 1 A flowchart illustrating the vehicle hardware and software association matching method provided in an embodiment of the present invention; Figure 2 This is an intentional representation of a hardware information database update application provided in an embodiment of the present invention; Figure 3 This is a schematic diagram of the hardware information database update process provided in an embodiment of the present invention; Figure 4 This is a schematic diagram of the software and hardware matching and verification process provided in an embodiment of the present invention; Figure 5 This is a schematic diagram of the vehicle hardware and software association matching device provided in an embodiment of the present invention. Detailed Implementation

[0021] Exemplary embodiments of the present disclosure will now be described in more detail with reference to the accompanying drawings. While exemplary embodiments of the present disclosure are shown in the drawings, it should be understood that the present disclosure may be implemented in various forms and should not be limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the disclosure to those skilled in the art.

[0022] The inventors discovered that the lack of unified hardware version benchmark data and automated verification processes in existing technologies leads to frequent software and hardware version mismatch issues, which currently rely mainly on manual troubleshooting, resulting in low efficiency. Based on this, the inventors conducted further research and development, resulting in this invention, which provides a method and apparatus for matching vehicle software and hardware.

[0023] Example 1 Embodiment 1 of the present invention provides a method for matching vehicle software and hardware, referring to... Figure 1 As shown, the method may include the following steps S101-S104: S101: When executing a software release, obtain the vehicle's hardware information database and the software's hardware-software relationship list.

[0024] S102: Based on the required hardware model in the hardware information database and the software-hardware relationship list, perform a hardware model existence verification to obtain the hardware model existence verification result.

[0025] S103: Based on the hardware model existence verification result, the required hardware version and required interface version in the hardware information database and the software-hardware relationship list, perform hardware version compatibility verification and interface version matching verification respectively, and obtain the corresponding hardware version compatibility verification result and interface version matching verification result.

[0026] S104: Based on the hardware model existence verification result, hardware version compatibility verification result, and interface version matching verification result, determine the compatibility result between the current software version and the hardware information database.

[0027] This invention provides a vehicle hardware and software association matching method. When executing software release, the method obtains the vehicle's hardware information database and the software hardware and software relationship list. Based on the required hardware model, required hardware version, and required interface version in the hardware information database and the software hardware and software relationship list, the method performs hardware model existence verification, hardware version compatibility verification, and interface version matching verification to obtain the compatibility result between the current software version and the hardware information database.

[0028] This method, based on a standardized hardware information database, provides a unified and reliable data benchmark for software and hardware version management. During the software release phase, it automatically retrieves the software's hardware relationship list and performs hardware model existence verification, hardware version compatibility verification, and interface version matching verification based on the hardware information database, ultimately generating accurate compatibility results. This systematic verification mechanism effectively identifies version mismatch issues, preventing flashing failures caused by software and hardware version mismatches from the outset.

[0029] Furthermore, this method reduces manual intervention through a standardized verification process, significantly decreasing version matching errors caused by human error, while improving the efficiency of problem localization and resolution. This automated correlation matching mechanism provides an effective solution for collaborative software and hardware development in complex systems.

[0030] In step S101 above, when the software release is executed, the vehicle's hardware information database and the software hardware-software relationship list are obtained. Specifically, this includes the following steps S1011-S1012: S1011: Obtain the vehicle's hardware information database. The vehicle's hardware information database is obtained through the following steps S10111-S10113: S10111: Obtain the benchmark information table corresponding to multiple hardware components. The benchmark information table includes the benchmark hardware model, benchmark hardware version, and benchmark interface version.

[0031] Specifically, the hardware information database can be constructed using structured database tables to record core hardware information, forming a unified hardware benchmark data source for the project. The structure of the hardware information database can be designed as shown in Table 1 below: Table 1 Hardware Information Database Structure

[0032] Among them, `hardware_id`: data type VARCHAR (50), serves as a unique hardware identifier, composed of the hardware model and version number, facilitating precise location and management of each hardware version. `hardware_model`: data type VARCHAR (100), used to record the hardware model, specifying the hardware type. `interface_version`: data type VARCHAR (50), records the hardware interface version, ensuring compatibility between the hardware and other devices. `hardware_version`: data type VARCHAR (20), records the hardware version number, facilitating tracking hardware updates. `release_date`: data type DATE, records the hardware release date, helping to understand the hardware's usage cycle and timeliness. `min_software_version`: data type VARCHAR (50), specifies the minimum software version supported by the hardware, providing an important basis for hardware-software matching. `update_time`: data type DATETIME, records the time of each information update, facilitating tracing the history of hardware information changes. `parameters`: data type TEXT, uses JSON format to store detailed hardware parameters, enabling flexible and comprehensive recording of various complex parameter information.

[0033] The initial data source and continuous updates of the benchmark information table are the responsibility of the hardware R&D department. After completing the hardware solution design and passing the tests, hardware R&D personnel are responsible for promptly entering or updating accurate and complete hardware information into the hardware information database.

[0034] When hardware developers need to add new hardware information to the hardware database or update existing hardware information, they can fill out a hardware database update application form through a pre-built hardware information management web interface, such as... Figure 2 As shown, fill in all the fields, including hardware model, hardware version number, and interface version, to obtain the baseline information table corresponding to the baseline hardware model, baseline hardware version, and baseline interface version.

[0035] S10112: Perform format verification and uniqueness verification on each reference information table to obtain the hardware information verification result.

[0036] Specifically, to ensure the accuracy and consistency of data in the hardware information database, after completing the hardware information database update application form, it is necessary to perform format verification and uniqueness verification on the obtained baseline information table.

[0037] Format validation refers to the initial validation of the baseline information table, checking whether all required fields are complete and whether the values ​​of each field conform to the preset data format requirements. Format validation can be implemented using front-end JavaScript. For example, it checks whether fields such as `hardware_id` and `hardware_model` are non-empty strings and conform to naming conventions. It checks whether the format of `hardware_version` follows preset semantic versioning rules. It checks whether `release_date` is a valid date format. If all the above checks pass, the format validation is considered successful; otherwise, it is considered unsuccessful, and a clear error message should be displayed next to the corresponding input box on the web interface, such as: "Hardware version number format is incorrect; it must conform to a preset semantic versioning rule," guiding hardware developers to correct and resubmit.

[0038] Uniqueness verification involves sending the entered data to the backend server via an HTTP request (e.g., POST) after the above format verification passes. The backend program then links to the hardware information database and uses the `hardware_model` and `hardware_version` values ​​from the entered data to form a unique identifier `hardware_id`, which is used as the search criterion in the hardware information database. For example, when hardware developers request the submission of a baseline information table for new hardware, it is necessary to check whether the same `hardware_id` already exists in the hardware information database. If the same `hardware_id` already exists, it is considered a duplicate entry, the uniqueness verification fails, the application is returned, and the hardware developers are prompted to verify. If the same `hardware_id` does not exist in the hardware information database, the uniqueness verification passes. When hardware developers request to update the baseline information table of existing hardware in the hardware information database, it is possible to verify whether the new data conforms to the logic of iterative upgrades, such as the new version number being higher than the old version number.

[0039] If both format verification and uniqueness verification pass, the hardware information verification result is determined to be passed; otherwise, the hardware information verification result is determined to be failed, and hardware R&D personnel need to be guided to modify the corresponding data.

[0040] S10113: If the hardware information verification result indicates that the benchmark information table has passed the verification, add the benchmark information table to the hardware information database.

[0041] Specifically, if the hardware information verification result is "pass," it indicates that the benchmark information table has passed the verification. The benchmark information table is then added to the hardware information database.

[0042] In this embodiment of the application, after determining that the hardware information verification result characterization benchmark information table has passed verification, the process may further include pushing the benchmark information table to designated hardware information database maintenance personnel for review. The maintenance personnel need to manually review the rationality and business accuracy of the updated information on a web interface, for example, verifying whether parameter changes conform to hardware design principles, and whether the hardware version or interface version is compatible with other related hardware or software.

[0043] If the review is approved, maintenance personnel will confirm the change on the web interface, and the baseline information table will be automatically added to the hardware information database, completing the write or update operation of the hardware information database. During this process, the update_time field of the data will be automatically updated to record the specific time of the change.

[0044] If the review fails, the maintenance personnel must provide a detailed explanation of the reasons and return the application. The hardware R&D personnel will then modify the application based on the feedback and resubmit it, repeating the above verification and review process.

[0045] To facilitate understanding of this method by those skilled in the art, the following will provide a clearer explanation of step S1011 with reference to the accompanying drawings: (Refer to...) Figure 3 As shown, the entire process begins with a "hardware update application," where hardware R&D personnel submit an application along with a baseline information form. Subsequently, the baseline information form undergoes format and uniqueness verification. If the verification fails, the application process is suspended, and the reason for the failure is noted on the webpage. If the verification passes, it enters the review stage, where hardware database maintenance personnel review the baseline information form. If the review is successful, the hardware database is updated based on the baseline information form, thus ensuring the accuracy and authority of the data in the hardware database.

[0046] In this embodiment, step S1011 establishes a hardware information database, creating a unified data benchmark for vehicle hardware and software matching. The hardware information database uses structured database tables to store core parameters such as hardware model, version number, and interface version, and dynamically maintains the data through an automated process. When the hardware solution is updated, a strict verification process, including format and uniqueness checks, is automatically triggered to ensure that all data entering the database conforms to preset specifications and remains unique. This guarantees the accuracy and timeliness of hardware information, providing a reliable data foundation for subsequent automated hardware and software matching and eliminating version matching errors caused by data inconsistencies from the outset.

[0047] S1012: Obtain the list of software and hardware relationships.

[0048] Specifically, during the software development phase, a structured configuration file (usually in JSON format) predefines the range of compatible hardware required by the software version and its specific conditions. This file constitutes the hardware-software relationship list. The hardware-software relationship list includes the required hardware model, required hardware version, and required interface version.

[0049] In one specific embodiment, the JSON configuration file containing the list of hardware and software relationships includes an array that enumerates all hardware information supported by the software version. Each entry includes the required hardware model, required hardware version, and required interface version. The array in the JSON configuration file can be as follows: "supportedHardware":{ "hardware_id":"XXX", "hardware_model":"XXX", "interface_version":"XXX", "hardware_version":"XXX", "release_date":"XXXXX", "min_software_version":"XXXX", "update_time":"XXXXXXX"} Here, hardware_model is the required hardware model, hardware_version is the required hardware version, and interface_version is the required interface version.

[0050] Once the software release process is triggered and integrated into the Continuous Integration / Continuous Delivery (CI / CD) process, the automation script will automatically read and parse the JSON configuration file to obtain the list of software and hardware relationships. For example, in a Jenkins-based CI process, its `readJSON` method or similar plugins can be used to directly parse the JSON configuration file. In this way, the list of software and hardware relationships for the software to be released is obtained automatically and accurately, providing clear input for subsequent comparison and verification with the hardware database.

[0051] In this embodiment, the software and hardware relationship list obtained in step S1012 provides a standardized software requirements declaration for vehicle software and hardware matching. It clearly defines the hardware models, versions, and interface requirements supported by the software to be released, achieving a structured expression of software dependencies. In the CI / CD process, this configuration file is directly parsed by an automated script, effectively ensuring the accuracy and consistency of requirements acquisition. This avoids errors that may occur with manual input and provides machine-readable input for subsequent automated verification, thereby establishing a reliable connection channel between software requirements and hardware benchmarks.

[0052] In step S102 above, the existence of the required hardware model is verified based on the hardware information database and the software-hardware relationship list, and the existence verification result of the hardware model is obtained.

[0053] Specifically, based on the hardware-software relationship list obtained in step S101, the required hardware model is extracted. Then, a query request is sent to the hardware information database, using the required hardware model as the key query condition, to check if matching data exists in the database. If the hardware information database finds the corresponding data, the hardware model existence verification result is "true," indicating that the required hardware model exists in the database, and the subsequent step S103 is executed. If the hardware information database does not find the corresponding data, the hardware model existence verification result is "false," indicating that the required hardware model exists in the database, and the subsequent step S103 is not executed, determining that the current software version is incompatible with the hardware information database.

[0054] In step S103 above, based on the hardware model existence verification result, the required hardware version and required interface version in the hardware information database and the software-hardware relationship list, hardware version compatibility verification and interface version matching verification are performed respectively, resulting in the corresponding hardware version compatibility verification results and interface version matching verification results. Specifically, this includes the following steps S1031-S1032: S1031: If the hardware model existence verification result indicates that the required hardware model exists in the hardware information database, then obtain the benchmark information table corresponding to the required hardware model, and obtain the hardware version compatibility verification result based on whether the benchmark hardware version in the benchmark information table is greater than or equal to the required hardware version.

[0055] Specifically, after confirming the existence of the required hardware model in the hardware information database, the baseline hardware version is extracted from the hardware-software relationship list obtained in step S101, and the required hardware version is obtained from the hardware-software relationship list. The baseline hardware version and the required hardware version are parsed and compared according to semantic versioning rules (e.g., major version number.minor version number.revision number V1.2.0). If the baseline hardware version is semantically greater than or equal to the required hardware version, the hardware version compatibility check result is determined to be "true," and the subsequent step S1032 is executed. If the baseline hardware version is semantically less than the required hardware version, the hardware version compatibility check result is determined to be "false," and the subsequent step S1032 is not executed, confirming that the current software version is incompatible with the hardware information database.

[0056] S1032: If the hardware model existence verification result indicates that the required hardware model exists in the hardware information database, then obtain the baseline information table corresponding to the required hardware model, and obtain the interface version matching verification result based on whether the baseline interface version in the baseline information table is equal to the required interface version.

[0057] Specifically, after confirming that the hardware version compatibility verification result indicates that the baseline hardware version is greater than or equal to the required hardware version, the baseline interface version is extracted from the software-hardware relationship list obtained in step S101, and the required interface version is obtained from the software-hardware relationship list. A precise matching comparison is performed between the baseline hardware version and the required interface version. If the baseline hardware version and the required interface version are the same, the interface version matching verification result is determined to be "true," and the subsequent step S104 is executed. If the baseline hardware version and the required interface version are different, the interface version matching verification result is determined to be "false," and the compatibility result between the current software version and the hardware information database is determined to be incompatible.

[0058] In step S104 above, the compatibility result between the current software version and the hardware information database is determined based on the hardware model existence verification result, the hardware version compatibility verification result, and the interface version matching verification result.

[0059] Specifically, the software's current version can be determined to be compatible with the hardware information database only when all three verification results—the hardware model existence verification result, the hardware version compatibility verification result, and the interface version matching verification result—pass: that is, when the hardware model existence verification result is "true," the hardware version compatibility verification result is "true," and the interface version matching verification result is "true."

[0060] If the hardware model existence verification result indicates that the required hardware model does not exist in the hardware information database, i.e., the hardware model existence verification result is "false"; or, if the hardware version compatibility verification result indicates that the baseline hardware version is greater than the required hardware version, i.e., the hardware version compatibility verification result is "false"; or, if the interface version matching verification result indicates that the baseline interface version is not equal to the required interface version, i.e., the interface version matching verification result is "false", then the current software version is determined to be incompatible with the hardware information database.

[0061] The multiple verification steps S102-S103 described above constitute a progressive filter. During the verification process, if any data in the software-hardware relationship list fails at any verification node, this method will immediately interrupt subsequent verification of that software version and determine the compatibility result between the current software version and the hardware information database as incompatible. This makes the compatibility result between the current software version and the hardware information database explicitly indicate the existence of incompatible items.

[0062] In this embodiment of the application, after completing step S104, step S105 is further included: determining the subsequent operations for software release based on the compatibility results between the current software version and the hardware information database. Specifically, this includes the following steps S1051-S1052: S1051: If the compatibility results between the current software version and the hardware information database indicate that there are incompatible items in the current software version, then the software release operation is stopped, and a difference notification is generated based on the incompatible items.

[0063] Specifically, when the current version of the software shows incompatibility with the hardware database, a failure logic is immediately executed, halting all subsequent release steps for the software, such as stopping the build archive and suspending the approval process. Simultaneously, a detailed discrepancy notification is automatically generated, precisely listing all incompatible hardware models, specific reasons for failure (e.g., "Model not found," "Version too low: Base hardware version V1.0.0 is lower than the required hardware version V1.1.0," "Interface version mismatch"), and related configuration locations. This notification is then automatically sent to the software development team and hardware database maintenance personnel via preset integration methods, such as email and instant messaging.

[0064] S1052: If the compatibility result between the current software version and the hardware information database indicates that there are no incompatible items in the current software version, then continue to complete the software release operation.

[0065] Specifically, when the compatibility result between the current software version and the hardware information database indicates that there are no incompatible items in the current software version, the CI / CD process will allow the process to continue to execute, automatically performing subsequent release operations, including but not limited to generating the final software release package, pushing it to the version repository, updating the release list to record the software version released this time and its matching hardware information, and automatically notifying relevant personnel that the release was successful.

[0066] To facilitate understanding of this solution by researchers in the field, the following will provide a clearer explanation of steps S102-S104 with reference to the illustrations: (Refer to...) Figure 4 As shown, this process begins with software release triggering, retrieving the required hardware model, required hardware version, and required interface version from the software's hardware / software relationship list as verification criteria. Then, it enters the core three-tiered progressive verification process. First, it checks if the required hardware model exists in the hardware information database; if it does, it proceeds to hardware version compatibility verification and interface version matching verification. Failure at any step immediately halts the process and generates a discrepancy notification to relevant personnel. Only when all verifications pass is it determined that there are no discrepancies, and the software release continues. The entire process is integrated into the CI / CD pipeline, achieving fully automated closed-loop management from "verification" to "processing," effectively preventing version mismatch issues.

[0067] In this embodiment, the method establishes a standardized hardware information database and a structured list of hardware and software relationships, constructing a unified data benchmark for vehicle hardware and software version management. This enables dynamic maintenance of hardware information, ensuring the accuracy and timeliness of the data source. Furthermore, the method is integrated into the CI / CD process, automatically performing checks on hardware model existence, version compatibility, and interface matching before software release. This method achieves a complete closed loop from version management to compatibility verification, effectively preventing flashing failures caused by version mismatches, reducing the incidence of hardware and software compatibility issues by over 90%, and significantly improving R&D collaboration efficiency and software release reliability.

[0068] Example 2 Based on the same inventive concept, embodiments of the present invention also provide a vehicle hardware and software association matching device, referring to... Figure 5 As shown, the device includes: The acquisition module 101 is used to acquire the vehicle's hardware information database and the software-hardware relationship list of the software when executing software release. The first verification module 102 is used to perform hardware model existence verification based on the required hardware model, required hardware version and required interface version in the hardware information database and the software and hardware relationship list, and obtain the hardware model existence verification result. The second verification module 103 is used to perform hardware version compatibility verification and interface version matching verification based on the hardware model existence verification result, the required hardware version and required interface version in the hardware information database and the software and hardware relationship list, respectively, and obtain the corresponding hardware version compatibility verification result and interface version matching verification result. The determination module 104 is used to determine the compatibility result between the current version of the software and the hardware information database based on the hardware model existence verification result, hardware version compatibility verification result, and interface version matching verification result.

[0069] Example 3 Based on the same inventive concept, embodiments of the present invention also provide a computer-readable storage medium storing a computer program / instructions thereon, which, when executed by a processor, implements the vehicle hardware and software association matching method as described in Embodiment 1 above.

[0070] Example 4 Based on the same inventive concept, embodiments of the present invention also provide a computer program product, including a computer program / instruction, which, when executed by a processor, implements the vehicle hardware and software association matching method as described in Embodiment 1 above.

[0071] Example 5 Based on the same inventive concept, this embodiment of the invention also provides a computer device, including a memory, a processor, and a computer program stored in the memory. When the processor executes the computer program, it implements the vehicle hardware and software association matching method as described in Embodiment 1 above.

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

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

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

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

[0076] Obviously, those skilled in the art can make various modifications and variations to this invention without departing from its spirit and scope. Therefore, if these modifications and variations fall within the scope of the claims of this invention and their equivalents, this invention also intends to include these modifications and variations.

Claims

1. A vehicle software and hardware correlation matching method, characterized in that, The application comprises the following steps: When the software version is executed, the hardware information base of the vehicle and the software and hardware relationship list of the software are obtained; Based on the hardware information base and the required hardware model in the software and hardware relationship list, hardware model existence verification is performed to obtain a hardware model existence verification result; Based on the hardware model existence verification result, the required hardware version and the required interface version in the hardware information base and the software and hardware relationship list, hardware version compatibility verification and interface version matching verification are respectively performed to obtain hardware version compatibility verification results and interface version matching verification results; Based on the hardware model existence verification result, the hardware version compatibility verification result and the interface version matching verification result, the compatibility result of the current version of the software and the hardware information base is determined.

2. The method of claim 1, wherein, The hardware information base comprises a plurality of reference information tables corresponding to the hardware; the reference information table comprises a reference hardware model, a reference hardware version and a reference interface version; The hardware version compatibility verification and the interface version matching verification based on the hardware model existence verification result, the hardware information base and the required hardware version and the required interface version in the software and hardware relationship list are performed to obtain the hardware version compatibility verification result and the interface version matching verification result, which comprises: If the hardware model existence verification result indicates that the required hardware model exists in the hardware information base, the reference information table corresponding to the required hardware model is obtained, and based on whether the reference hardware version in the reference information table is greater than or equal to the required hardware version, the hardware version compatibility verification result is obtained; If the hardware model existence verification result indicates that the required hardware model exists in the hardware information base, the reference information table corresponding to the required hardware model is obtained, and based on whether the reference interface version in the reference information table is equal to the required interface version, the interface version matching verification result is obtained.

3. The method of claim 2, wherein, The compatibility result of the current version of the software and the hardware information base is determined based on the hardware model existence verification result, the hardware version compatibility verification result and the interface version matching verification result, which comprises: If the hardware model existence verification result indicates that the required hardware model does not exist in the hardware information base, the compatibility result of the current version of the software and the hardware information base indicates that there is an incompatible item; If the hardware version compatibility verification result indicates that the reference hardware version is greater than the required hardware version, the compatibility result of the current version of the software and the hardware information base indicates that there is an incompatible item; If the interface version matching verification result indicates that the reference interface version is not equal to the required interface version, the compatibility result of the current version of the software and the hardware information base indicates that there is an incompatible item.

4. The method of claim 1, wherein, Further comprising: The hardware model existence verification, the hardware version compatibility verification and the interface version matching verification are integrated into the CI / CD process of the software.

5. The method of claim 1, wherein, The hardware information base is obtained by the following method: A plurality of reference information tables corresponding to the hardware are obtained; The format and uniqueness of each reference information table are checked to obtain a hardware information checking result; If the hardware information checking result indicates that the reference information table passes the check, the reference information table is added to the hardware information library.

6. The method of claim 1, wherein, After the compatibility result of the current software version and the hardware information library is obtained, the following steps are further included: If the compatibility result of the current software version and the hardware information library indicates that there are incompatible items, the software release operation is aborted, and a difference notification is generated based on the incompatible items; If the compatibility result of the current software version and the hardware information library indicates that there are no incompatible items, the software release operation is continued.

7. A vehicle software and hardware correlation matching apparatus characterized by comprising: The method comprises the following steps: An acquisition module is configured to acquire a hardware information library of a vehicle and a software-hardware relationship list of the software when a software release is performed; A first checking module is configured to perform hardware model existence checking based on a required hardware model, a required hardware version, and a required interface version in the hardware information library and the software-hardware relationship list to obtain a hardware model existence checking result; A second checking module is configured to perform hardware version compatibility checking and interface version matching checking based on the hardware model existence checking result, the required hardware version, and the required interface version in the hardware information library and the software-hardware relationship list to obtain a hardware version compatibility checking result and an interface version matching checking result, respectively; A determination module is configured to determine a compatibility result of the current software version and the hardware information library based on the hardware model existence checking result, the hardware version compatibility checking result, and the interface version matching checking result.

8. A computer readable storage medium having stored thereon computer programs / instructions, characterized in that, The computer program / instruction is executed by the processor to implement the vehicle software-hardware correlation matching method of any one of claims 1-6.

9. A computer program product comprising computer programs / instructions, characterized in that, The computer program / instruction is executed by the processor to implement the vehicle software-hardware correlation matching method of any one of claims 1-6.

10. A computer device comprising a memory, a processor, and a computer program stored on the memory, wherein the computer program comprises instructions that, when executed by the processor, cause the processor to perform the method of any one of claims 1-9. The processor executes the computer program to implement the vehicle software-hardware correlation matching method of any one of claims 1-6.

Images