Component version update method and computing device

Abstract

This application relates to the field of computer technology, specifically providing a method and computing device for updating the version of a component. In response to after-sales replacement needs, it directly obtains vehicle identification information and pulls the configuration data of the whole vehicle controller and the target version dataset of the whole vehicle from the server. Then, it automatically determines the matching firmware version by combining the hardware information of the component to be updated, and finally updates the firmware version to the component to be updated. The entire version matching and update process is executed in a closed loop on the vehicle terminal without the need for external diagnostic equipment. This enables the firmware version update after component replacement to be completed independently on the vehicle terminal, eliminating the dependence on external equipment, simplifying the operation process and improving the flexibility of operation.

Description

Technical Field

[0001] This application relates to the field of computer technology, specifically to a method for updating the version of a component and a computing device. Background Technology

[0002] As the level of automotive intelligence continues to increase, the number of intelligent vehicle systems and various electronic control units (ECUs) is also growing. There are strict matching relationships between the firmware versions of these controllers, and version consistency directly determines the stable operation of functions such as vehicle communication, audio-visual entertainment, and body control. In vehicle production, routine maintenance, and fault repair scenarios, the replacement of damaged intelligent vehicle systems and the replacement of ECU components occur frequently.

[0003] Existing after-sales parts replacement solutions typically require repair personnel to use external diagnostic equipment (such as a diagnostic tool) to perform firmware flashing and verification. This requires connecting the external device to the vehicle's OBD interface, reading vehicle information, querying the target version, and issuing firmware flashing commands.

[0004] However, existing solutions for after-sales parts replacement are limited by the availability of external equipment, and the operation process is cumbersome and lacks flexibility. Summary of the Invention

[0005] This application provides a method for updating the version of a component and a computing device to at least solve the technical problems in the prior art where component replacement operations are limited by the availability of external devices, and the operation process is cumbersome and lacks flexibility.

[0006] Firstly, this application provides a method for updating the version of a component, including: In response to after-sales parts replacement needs, vehicle identification information is obtained. Based on the vehicle identification information, the vehicle's full-vehicle controller configuration data and the vehicle target version dataset are obtained from the server. The hardware information of the component to be updated is obtained. Based on the hardware information, the full-vehicle controller configuration data, and the target version dataset, the firmware version matching the component to be updated is determined, and the firmware version is updated to the component to be updated.

[0007] Secondly, this application provides a component version update device, comprising: The first acquisition unit is used to acquire vehicle identification information in response to after-sales parts replacement needs; The second acquisition unit is used to acquire the full vehicle controller configuration data and the whole vehicle target version dataset of the vehicle from the server based on the vehicle identification information; The determining unit is used to acquire the hardware information of the component to be updated and, based on the hardware information, the vehicle controller configuration data, and the target version dataset, determine the firmware version that matches the component to be updated. The update unit is used to update the firmware version to the component to be updated.

[0008] Secondly, this application provides a method for updating the version of a component, the method comprising: In response to after-sales parts replacement needs, obtain vehicle identification information; Based on the vehicle identification information, determine the vehicle's full-vehicle controller configuration data and the vehicle target version dataset; The hardware information of the component to be updated is obtained, and based on the hardware information, the vehicle controller configuration data, and the target version dataset, the firmware version matching the component to be updated is determined, so that the vehicle system updates the firmware version to the component to be updated.

[0009] Thirdly, this application provides a computing device, comprising: Memory, used to store computer programs; A processor, used to implement the method for updating the version of the components in any of the above technical solutions when executing a computer program.

[0010] Fourthly, this application provides a computer-readable storage medium storing a computer program, wherein when the computer program is executed by a processor, it implements the steps of the version update method for the components in any of the above technical solutions.

[0011] The beneficial effects of this application are: In response to after-sales parts replacement needs, the system directly obtains vehicle identification information and pulls the full vehicle controller configuration data and the whole vehicle target version dataset from the server. Then, it automatically determines the matching firmware version by combining the hardware information of the part to be updated, and finally updates the firmware version to the part to be updated. The entire version matching and update process is executed in a closed loop on the vehicle terminal without the need for external diagnostic equipment. This enables the firmware version update after parts replacement to be completed independently on the vehicle terminal, eliminating the dependence on external equipment, simplifying the operation process and improving the flexibility of operation. Attached Figure Description

[0012] Figure 1 This is a schematic flowchart of the main steps of a component version update method according to an embodiment of this application; Figure 2 This is a schematic diagram of the main structure of a version update device for components provided according to an embodiment of this application; Figure 3 This is a schematic diagram of the main structure of a version update system for components provided according to an embodiment of this application. Detailed Implementation

[0013] 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 of ordinary skill in the art without creative effort are within the protection scope of this application.

[0014] It should be noted that, in the description of this application, the terms "comprising," "including," or any other variations thereof are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. The terms "first," "second," etc., in this application are used to distinguish similar objects and are not used to describe a specific order or sequence.

[0015] To enable those skilled in the art to better understand the present application, the present application will be further described in detail below with reference to the accompanying drawings and specific embodiments.

[0016] As the level of automotive intelligence continues to increase, the number of intelligent vehicle systems and various electronic control units (ECUs) is also growing. There are strict matching relationships between the firmware versions of these controllers, and version consistency directly determines the stable operation of functions such as vehicle communication, audio-visual entertainment, and body control. In vehicle production, routine maintenance, and fault repair scenarios, the replacement of damaged intelligent vehicle systems and the replacement of ECU components occur frequently.

[0017] For the aforementioned parts replacement scenarios, existing after-sales replacement solutions typically require repair personnel to use external diagnostic equipment (such as a diagnostic tool) to perform firmware updates and verification. This necessitates connecting the external device to the vehicle's OBD interface, reading vehicle information, querying the target version, and issuing firmware update commands. This solution relies on external auxiliary equipment to complete the software version update after parts replacement.

[0018] However, the existing solution requires external diagnostic equipment to perform firmware version updates after replacement, and cannot complete the entire process from version matching to firmware update independently on the vehicle's infotainment system. This results in after-sales replacement work being limited by the availability of external equipment, and the operation process is cumbersome and lacks flexibility.

[0019] In view of this, this application provides a method for updating the version of a component, including responding to an after-sales replacement request, obtaining vehicle identification information, obtaining the vehicle's full-vehicle controller configuration data and the vehicle's target version dataset from a server based on the vehicle identification information, obtaining the hardware information of the component to be updated, and determining a firmware version matching the component to be updated based on the hardware information, the full-vehicle controller configuration data, and the target version dataset, and updating the firmware version to the component to be updated. By responding to an after-sales replacement request, the method directly obtains vehicle identification information and pulls the full-vehicle controller configuration data and the vehicle's target version dataset from the server, and then automatically determines the matching firmware version based on the hardware information of the component to be updated, and finally updates the firmware version to the component to be updated. The entire version matching and update process is executed in a closed loop on the vehicle's terminal, without the need for external diagnostic equipment, thereby realizing the independent completion of firmware version updates after component replacement on the vehicle side, eliminating dependence on external equipment, simplifying the operation process, and improving operational flexibility.

[0020] See Figure 1 , Figure 1 The diagram shown is a schematic representation of the main steps of a component version update method provided in an embodiment of this application. Figure 1 As shown, this method can be applied to computing devices. The version update method for the components in this application mainly includes the following steps: S101: Responds to after-sales parts replacement needs by obtaining vehicle identification information.

[0021] The computing device responds to after-sales parts replacement needs by acquiring vehicle identification information.

[0022] The computing device responds to after-sales replacement requests. These requests occur during after-sales repairs when the vehicle's electronic control controller or infotainment system is damaged and requires replacement. After the repair personnel install the hardware to be replaced and connect the wiring harness, they power on the vehicle normally. Subsequently, the repair personnel enter engineering mode via dial-up on the infotainment screen and activate the after-sales firmware update function. This action generates the after-sales replacement request. The computing device refers to the vehicle's infotainment system, which contains an after-sales firmware update module capable of executing version update procedures. When the repair personnel activate the after-sales firmware update function, the computing device receives the replacement request and begins the subsequent version matching and firmware update operations.

[0023] For example, the computing device can acquire vehicle identification information. This information can be the vehicle's VIN (Vehicle Identification Number), a unique alphanumeric combination that identifies the vehicle and records its model, production information, and controller configuration. In response to an after-sales parts replacement request, the computing device automatically reads the vehicle's VIN via the onboard bus. The retrieved VIN is then used to query the server for the vehicle's specific full-vehicle controller configuration data.

[0024] Specifically, if the replaced part is not the vehicle's infotainment system itself, the system already has intranet connectivity and can directly read the VIN code. If the replaced part is the vehicle's infotainment system itself, the newly installed system does not have intranet access in its factory state. In this case, the repair personnel need to log in to the after-sales replacement cloud platform, bind the new vehicle's TUID with the vehicle's VIN, and complete real-name authentication before the infotainment system can gain intranet access, and only then can the computing devices read the vehicle identification information normally.

[0025] After obtaining the vehicle identification number (VIN), the computing device can retrieve the vehicle's full controller configuration data and the target version dataset from the server based on the VIN. The full controller configuration data includes the hardware IDs, controller types, and version matching relationships of all electronic control units in the vehicle. The target version dataset includes the target software version numbers and flashing file information for each controller under the current major vehicle version. This information forms the basis for subsequently determining the matching firmware version for the components to be updated.

[0026] S102: Based on the vehicle identification information, obtain the vehicle controller configuration data and the target version dataset of the whole vehicle from the server.

[0027] The computing device can obtain the vehicle's full-vehicle controller configuration data and the whole vehicle target version dataset from the server based on the vehicle identification information.

[0028] In some possible implementations, the computing device can obtain the vehicle's full-vehicle controller configuration data from the server based on vehicle identification information, parse the full-vehicle controller configuration data, extract the hardware number and controller type of each controller, display the hardware number and controller type on the interactive interface, and in response to the user's selection operation based on the interactive interface, select the corresponding controller as the component to be updated and obtain the corresponding hardware information. In response to the selection operation, the device can obtain the vehicle target version dataset from the server based on the vehicle identification information.

[0029] For example, a computing device can obtain the vehicle's full-vehicle controller configuration data from a server based on vehicle identification information. The vehicle identification information is the vehicle's VIN code, and the server can be a backend server storing vehicle configuration data. The full-vehicle controller configuration data is a collection of configuration information describing all electronic control units of the vehicle, which may include the hardware number of each controller, the controller type, and the version matching relationship between them. The computing device can connect to the server via an in-vehicle network, send the vehicle identification information, and the server returns the corresponding full-vehicle controller configuration data based on the identification information.

[0030] The computing device parses the received vehicle controller configuration data, extracting the hardware number and controller type of each controller. The hardware number is a unique identifier for each electronic control unit (ECU), such as a part number or serial number; the controller type refers to the controller's functional category, such as engine controller, transmission controller, body controller, or battery management system. The computing device displays these hardware numbers and controller types on an interactive interface. This interface is the display screen on the vehicle's infotainment system, allowing maintenance personnel to view a list of all controllers in the vehicle and their hardware information.

[0031] Repair personnel can view the displayed hardware serial numbers and controller types through the interactive interface and perform selection operations based on this interface. The selection operation involves the repair personnel clicking or touching on the interactive interface to select one or more controllers to specify the component that needs a firmware update. The computing device responds to this selection operation, identifying the selected controller as the component to be updated. The component to be updated is the hardware that requires a new firmware update in this after-sales replacement scenario. Simultaneously, the computing device obtains the hardware information corresponding to the component to be updated. The hardware information includes the component's hardware serial number, controller type, and currently installed firmware version, etc. This information is used to subsequently query the server for a matching flashing file.

[0032] In response to the selection operation described above, the computing device retrieves the vehicle target version dataset from the server based on the vehicle identification information. The vehicle target version dataset is a collection of target software version numbers and corresponding flashing file information for each controller under the current major vehicle version. After identifying the component to be updated, the computing device sends the vehicle identification information to the server again. The server returns the vehicle target version dataset for that vehicle based on the vehicle identification information. This dataset includes the target versions corresponding to all controllers. The computing device can then filter the target version and flashing file matching the component to be updated from the vehicle target version dataset based on the hardware information of the component to be updated, preparing for subsequent firmware download and flashing.

[0033] S103: Obtain the hardware information of the component to be updated and, based on the hardware information, the vehicle controller configuration data, and the target version dataset, determine the firmware version that matches the component to be updated.

[0034] The computing device can obtain the hardware information of the component to be updated and, based on the hardware information, the vehicle controller configuration data, and the target version dataset, determine the firmware version that matches the component to be updated.

[0035] In some possible implementations, the computing device can filter out a list of corresponding software part numbers from the vehicle controller configuration data based on the hardware part numbers in the hardware information, search for and obtain the appropriate software version and flashing file information from the target version dataset based on the software part number list, and determine the firmware version based on the software version and flashing file information.

[0036] For example, the computing device can filter out a list of corresponding software part numbers from the vehicle controller configuration data based on the hardware part numbers in the hardware information. Here, the hardware part number is a hardware identification code, such as a part number, for the component to be updated, used to uniquely identify the hardware version of the controller. The vehicle controller configuration data is a configuration file of all electronic control units in the vehicle obtained from the server based on vehicle identification information, which records one or more software part numbers corresponding to each hardware part number. The computing device searches for entries in this configuration data that match the hardware part number of the component to be updated, extracts all associated software part numbers, and these software part numbers constitute a software part number list, representing the set of software version identifiers that the hardware may be compatible with.

[0037] The computing device, based on a list of software part numbers, searches for and retrieves the appropriate software version and flashing file information from the vehicle target version dataset. The vehicle target version dataset is a collection of target software versions and flashing files for each controller under the current vehicle major version, and may include software part numbers, software version numbers, and corresponding installation package information. The computing device iterates through each software part number in the software part number list, performs a matching search in the target version dataset, finds records with the same software part number, and thus obtains the target software version number and flashing file information corresponding to that software part number, such as the size of the flashing package, checksum, and download link. The vehicle major version is a complete set of software version configurations for a specific vehicle, also known as the vehicle target version. This set covers the target software version numbers and corresponding flashing file information for all electronic control controllers on the vehicle under the current vehicle software baseline. The vehicle major version for each vehicle is uniquely determined by its vehicle identification information, reflecting the unified software state that all controllers in the vehicle should reach at the time of manufacture or after each upgrade.

[0038] Based on the acquired software version and flashing file information, the computing device determines the firmware version of the component to be updated. The firmware version refers to the specific software version that the component needs to be flashed. The computing device uses the matched target software version number as the firmware version and prepares the corresponding complete flashing file for subsequent firmware download and flashing operations. In this way, by combining the hardware part number and the vehicle's target version data, the computing device can automatically and accurately match the correct software version for the replaced controller, avoiding errors caused by manual selection.

[0039] In some possible implementations, a list of corresponding software part numbers is filtered from the vehicle controller configuration data, which may specifically include: The hardware part number is matched with the hardware code of each controller in the vehicle controller configuration data to extract the software part number associated with the hardware part number, forming a software part number list.

[0040] In some possible implementations, the compatible software version and flashing file information can be found and obtained from the target version dataset. Specifically, this could be as follows: Iterate through each software part number in the software part number list, search for the software information entry with the same software part number in the target version dataset, and obtain the corresponding software version number and flashing file information from the software information entry.

[0041] For example, the computing device matches the hardware part number of the component to be updated with the hardware codes of each controller in the vehicle controller configuration data, extracts the software part numbers associated with the hardware part number, and forms a software part number list. The hardware part number is a hardware identification code on the component to be updated, used to uniquely identify the hardware version of the controller. The vehicle controller configuration data is a configuration file of all electronic control units of the vehicle obtained from the server based on vehicle identification information. Each record includes a controller's hardware code and one or more software part numbers associated with that hardware code. The computing device scans each controller record in the vehicle controller configuration data one by one, comparing the hardware part number of the component to be updated with the hardware code in each record. When a hardware code matching the hardware part number is found, the computing device extracts all associated software part numbers from that record and combines these software part numbers into a software part number list. This software part number list represents all possible compatible software version identifiers corresponding to the current hardware part number.

[0042] The computing device iterates through each software part number in the software part number list, searches for a matching software information entry in the target version dataset, and retrieves the corresponding software version number and flashing file information from the software information entry. The target version dataset is a collection of target software versions and flashing files for each controller under the current vehicle version, including multiple software information entries. Each entry includes at least a software part number, a software version number, and flashing file information. The computing device sequentially retrieves software part numbers from the software part number list and compares them one by one with the software part numbers in the target version dataset. If a matching software part number is found, the corresponding software version number and flashing file information are retrieved from that software information entry. The software version number represents the specific software version identifier corresponding to the software part number, and the flashing file information includes data used to perform firmware updates, such as the size of the flash package, storage location, or download link. In this way, the computing device can accurately obtain the software version and flashing file that matches the hardware of the component to be updated from the vehicle target version dataset.

[0043] Based on the acquired software version and flashing file information, the computing device determines the firmware version of the component to be updated. The firmware version is the specific software version that needs to be flashed onto the component. The computing device uses the matched software version number as the firmware version and prepares for subsequent firmware download and flashing operations using the flashing file information. This process achieves automatic matching from hardware part number to software part number, then to the specific software version and flashing file, without manual intervention, avoiding version selection errors and ensuring the accuracy of the firmware version during after-sales replacement.

[0044] In some possible implementations, iterating through each software part number in the software part number list, searching for a software information entry with the same part number in the target version dataset, and obtaining the corresponding software version number and flashing file information from the software information entry can be: For the software part number currently being traversed, search in the target version dataset for whether there is a matching software information entry; If it exists, retrieve the corresponding software version number and flashing file information from the corresponding software information entry, and then end the traversal; If it does not exist, determine whether the current software part number is the last software part number in the software part number list. If the current software part number is not the last software part number, continue to traverse the next software part number until it is determined that there is a software information entry with the same software. Obtain the corresponding software version number and flashing file information from the corresponding software information entry.

[0045] The computing device begins traversing the list of software part numbers, searching the target version dataset for a matching software information entry for the currently processed software part number. The target version dataset is a complete vehicle target version dataset retrieved from the server based on vehicle identification information. It stores multiple software information entries, each including the software part number, software version number, and flashing file information. The computing device compares the current software part number with each software information entry in the dataset, searching for records where they are identical.

[0046] If the computing device finds a matching software information entry, it retrieves the corresponding software version number and flashing file information from that entry. The software version number indicates the specific software version that the component to be updated needs to be flashed, and the flashing file information includes the size of the flashing data package, checksum, or download address, etc. Upon successful retrieval, the computing device immediately ends the traversal operation and no longer checks subsequent software part numbers in the software part number list, because the correct firmware version has already been matched for the component to be updated.

[0047] If the computing device does not find a matching software information entry, it determines whether the current software part number is the last software part number in the software part number list. The software part number list records all possible compatible software part numbers associated with the hardware part number of the component to be updated. If the current software part number is not the last one, the computing device continues to take the next software part number in the list as the current traversal object and performs the search operation in the target version dataset again. The computing device tries in this manner until a matching software information entry is found, and obtains the corresponding software version number and flashing file information from that entry to determine the firmware version of the component to be updated.

[0048] S104: Update the firmware version to the component to be updated.

[0049] The computing device can update the firmware version to the component to be updated.

[0050] In some possible implementations, flashing data corresponding to the firmware version can be obtained, and a firmware update operation can be performed on the component to be updated based on the flashing data.

[0051] This application embodiment responds to after-sales parts replacement requests by directly obtaining vehicle identification information and pulling full vehicle controller configuration data and vehicle target version dataset from the server. Then, it automatically determines the matching firmware version by combining the hardware information of the part to be updated, and finally updates the firmware version to the part to be updated. The entire version matching and update process is executed in a closed loop on the vehicle terminal without the need for external diagnostic equipment. This enables the firmware version update after parts replacement to be completed independently on the vehicle terminal, eliminating the dependence on external equipment, simplifying the operation process and improving operational flexibility.

[0052] In this embodiment of the application, after updating the firmware version to the component to be updated, it can also verify whether the version information of the component to be updated matches the firmware version. If they match, it is determined that the firmware update of the component to be updated was successful.

[0053] In some possible implementations, verifying whether the version information of the component to be updated matches the firmware version can specifically include: Read the current software version number and current software part number of the component to be updated. Compare the current software version number with the target software version number corresponding to the firmware version, and compare the current software part number with the target software part number corresponding to the firmware version. If the current software version number and the target software version number are the same, and the current software part number and the target software part number are the same, then a match is determined.

[0054] For example, after updating the firmware version to the component to be updated, the computing device verifies whether the version information of the component to be updated matches the firmware version. The firmware version refers to the target software version matched by the computing device from the vehicle target version dataset based on the hardware part number of the component to be updated, including the target software version number and the target software part number. The component to be updated is the replaced electronic control controller or intelligent vehicle system in an aftermarket vehicle parts replacement scenario. Version information refers to the software information actually running on the component to be updated after the firmware flashing is completed, specifically including the current software version number and the current software part number. The purpose of the verification is to confirm that no errors occurred during the flashing process and to ensure that the component to be updated has indeed installed the expected software version.

[0055] The computing device reads the updated current software version number and current software part number of the component to be updated. The current software version number is the identifier of the software version currently running on the component to be updated, and the current software part number is the unique code of that software. Subsequently, the computing device compares the current software version number with the target software version number corresponding to the firmware version, and compares the current software part number with the target software part number corresponding to the firmware version. The target software version number is the target version identifier specified by the firmware version, and the target software part number is the software code corresponding to the firmware version.

[0056] If the comparison results show that the current software version number and the target software version number are completely identical, and the current software part number is also completely identical to the target software part number, then the computing device determines that the version information matches the firmware version. In this case, the computing device determines that the firmware update of the component to be updated is successful, indicating that the replaced controller has correctly installed firmware compatible with the overall vehicle version and can communicate normally with other electronic control units in the original vehicle. If any comparison is inconsistent, the matching fails, and the computing device can record the error and trigger a retry or alarm.

[0057] Using the above verification method, after updating the firmware version to the component to be updated, the computing device reads the current software version number and the current software part number of the component after the update. It then compares the current software version number with the target software version number corresponding to the firmware version, and simultaneously compares the current software part number with the target software part number corresponding to the firmware version. Only when both match is the version information determined to be a match with the firmware version, and the firmware update is considered successful. This effectively overcomes the problem of incorrect version installation caused by data transmission errors or write anomalies during firmware flashing, because the firmware version is determined by the computing device based on the hardware of the component to be updated. The target software version is matched from the vehicle's large version dataset. This target software version explicitly includes the target software version number and the target software part number. By simultaneously verifying the information in both dimensions, it is possible to accurately confirm whether the software actually running on the component to be updated is consistent with the requirements of the vehicle's large version dataset. This ensures that the replaced electronic control controller or intelligent vehicle system is equipped with the correct firmware, avoiding problems such as hardware and software incompatibility, communication errors, or functional failures between the component to be updated and other original vehicle electronic control units due to incorrect flashing. This guarantees the version uniformity and stable collaborative operation of the vehicle's electronic control system after after-sales component replacement.

[0058] Through the above description of the embodiments, those skilled in the art can clearly understand that the methods according to the above embodiments can be implemented by means of software plus necessary general-purpose hardware platforms. Of course, they can also be implemented by hardware, but in many cases the former is a better implementation method.

[0059] Furthermore, this application also provides a component version update device.

[0060] See appendix Figure 2 , Figure 2 This is a main structural block diagram of a version update apparatus for components according to an embodiment of this application. Figure 2 As shown, the component version update device in this application embodiment mainly includes a first acquisition module 21, a second acquisition module 22, a determination module 23, and an update module 24.

[0061] In some embodiments, one or more of the first acquisition module 21, the second acquisition module 22, the determination module 23, and the update module 24 can be combined into a single module. In some embodiments, the first acquisition module 21 can be used to acquire vehicle identification information in response to after-sales replacement needs. The second acquisition module 22 can be used to acquire the vehicle's full-vehicle controller configuration data and the vehicle target version dataset from a server based on the vehicle identification information. The determination module 23 can be used to acquire the hardware information of the component to be updated and, based on the hardware information, the full-vehicle controller configuration data, and the target version dataset, determine the firmware version matching the component to be updated. The update module 24 can be used to update the firmware version to the component to be updated. In one embodiment, the specific function of the first acquisition module 21 can be described in step S101. In one embodiment, the specific function of the second acquisition module 22 can be described in step S102. In one embodiment, the specific function of the determination module 23 can be described in step S103, and the specific function of the update module 24 can be described in step S104.

[0062] The version update device of the above-mentioned components is used to perform Figure 1 The embodiments of the component version update method shown are similar in technical principle, technical problem solved and technical effect. Those skilled in the art can clearly understand that, for the sake of convenience and brevity, the specific working process and related descriptions of the component version update system can be referred to the contents described in the embodiments of the component version update method, which will not be repeated here.

[0063] like Figure 3 As shown in the illustration, this application also provides a component version update system. The system architecture may include a server (cloud), electronic devices, and multiple electronic control units (ECU_1 to ECU_N) inside the vehicle. The electronic devices refer to the vehicle's intelligent infotainment system, which includes an engineering mode and an aftermarket flashing module. The server stores the vehicle's controller configuration data, the vehicle's target version dataset, and the flashing files corresponding to each electronic control unit. The electronic devices communicate with the server via a wireless network to obtain the aforementioned configuration and version data; simultaneously, the electronic devices are physically connected to each electronic control unit via the vehicle's in-vehicle bus to read controller information and issue firmware flashing commands.

[0064] When a vehicle requires after-sales parts replacement, the repair personnel enter engineering mode through the vehicle's infotainment system interface, activate the after-sales flashing module, and trigger the parts replacement version control process. In response to this replacement request, the electronic equipment automatically reads the vehicle identification number (VIN) and, based on this VIN, retrieves the vehicle's full controller configuration data and the target version dataset from the server. The full controller configuration data includes the hardware number, controller type, and version matching relationships of all electronic control units in the vehicle. The target version dataset includes the target software version number and flashing file information for each controller under the current vehicle version; this information forms the basis for determining the matching firmware version for the parts to be updated.

[0065] The electronic device acquires the hardware information (e.g., hardware part number) of the component to be updated. Based on this hardware information, the vehicle controller configuration data, and the vehicle target version dataset, it performs intelligent version calculation locally to match and determine the firmware version and corresponding flashing file compatible with the component to be updated. Subsequently, the electronic device acquires the flashing data corresponding to this firmware version and performs a firmware update operation on the component to be updated based on this flashing data, updating the firmware version to the corresponding electronic control unit. The entire version matching and update process is executed in a closed loop on the electronic device, without the need for external diagnostic equipment.

[0066] In some possible implementations, some of the methods performed by the electronic device in this embodiment can also be performed by the server. For example, the server can obtain vehicle identification information in response to after-sales parts replacement requests. Based on the vehicle identification information, determine the vehicle's full-vehicle controller configuration data and the vehicle target version dataset; The hardware information of the component to be updated is obtained, and based on the hardware information, the vehicle controller configuration data, and the target version dataset, the firmware version matching the component to be updated is determined, so that the vehicle system updates the firmware version to the component to be updated.

[0067] The specific implementation process can be discussed with Figure 1 The implementation principle of the embodiments shown is similar, and will not be described in detail here.

[0068] Embodiments of this application also provide a computing device, including a memory and a processor, wherein the memory stores a computer program and the processor is configured to run the computer program to perform the steps in the version update method embodiments of any of the above-described components.

[0069] Embodiments of this application also provide a computer-readable storage medium storing a computer program, wherein the computer program is configured to execute the steps in the version update method embodiment of any of the above components when running.

[0070] In one exemplary embodiment, the aforementioned computer-readable storage medium may include, but is not limited to, various media capable of storing computer programs, such as a USB flash drive, read-only memory (ROM), random access memory (RAM), portable hard disk, magnetic disk, or optical disk.

[0071] Embodiments of this application also provide a computer program product, which includes a computer program that, when executed by a processor, implements the steps in the version update method embodiment of any of the above-described components.

[0072] Embodiments of this application also provide another computer program product, including a non-volatile computer-readable storage medium storing a computer program, which, when executed by a processor, implements the steps in the version update method embodiments of any of the above-described components.

[0073] Any of the components, modules, units, parts, methods, and operations described herein can be implemented using software, firmware, hardware (e.g., fixed logic circuitry), manual processing, or any combination thereof. Alternatively or additionally, any functionality described herein can be executed at least in part by one or more hardware logic components, such as, but not limited to, a central processing unit (CPU), a field-programmable gate array (FPGA), an application-specific integrated circuit (ASIC), application-specific standard parts (ASSP), a system-on-a-chip (SoC), a complex programmable logic device (CPLD), a microcontroller unit (MCU), etc. The terms "system," "computing device," or "apparatus" as used herein encompass various means, devices, and machines for processing data, including, for example, one or more programmable processors, computers, SoCs, or combinations thereof. The apparatus may also include code that creates an execution environment for the computer program in question, such as code constituting processor firmware, a protocol stack, a database management system, an operating system, a cross-platform runtime environment, a virtual machine, or a combination thereof. The aforementioned computer program (also known as a program, software, software application, app, script, or code) can be written in any form of programming language, including compiled or interpreted languages, declarative or procedural languages, and can be deployed in any form, including as a standalone program or as a module, component, subroutine, object, or other unit suitable for a computing environment.

[0074] Those skilled in the art will further recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, computer software, or a combination of both. To clearly illustrate the interchangeability of hardware and software, the components and steps of the various examples have been generally described in terms of functionality in the foregoing description. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0075] The foregoing has provided a detailed description of a method for updating a component and a computing device provided in this application. Specific examples have been used to illustrate the principles and implementation methods of this application. The descriptions of the embodiments above are only intended to help understand the method and core ideas of this application. It should be noted that those skilled in the art can make various improvements and modifications to this application without departing from its principles, and these improvements and modifications also fall within the protection scope of the claims of this application.

Claims

1. A method for updating the version of a component, characterized in that, The method includes: In response to after-sales parts replacement needs, obtain vehicle identification information; Based on the vehicle identification information, the system obtains the vehicle controller configuration data and the target version dataset of the vehicle from the server. Obtain the hardware information of the component to be updated and, based on the hardware information, the vehicle controller configuration data, and the target version dataset, determine the firmware version that matches the component to be updated; Update the firmware version to the component to be updated.

2. The method according to claim 1, characterized in that, Based on the hardware information, the vehicle controller configuration data, and the target version dataset, determine the firmware version that matches the component to be updated, including: Based on the hardware part numbers in the hardware information, a list of corresponding software part numbers is selected from the vehicle controller configuration data; Based on the software part number list, the appropriate software version and flashing file information are searched and obtained from the target version dataset; The firmware version is determined based on the software version and the flashing file information.

3. The method according to claim 2, characterized in that, The corresponding software part number list is filtered from the vehicle controller configuration data, including: The hardware part number is matched with the hardware code of each controller in the vehicle controller configuration data to extract the software part number associated with the hardware part number, forming a software part number list.

4. The method according to claim 3, characterized in that, Based on the software part number list, the appropriate software version and flashing file information are searched and obtained from the target version dataset, including: Iterate through each software part number in the software part number list, search for the software information entry with the same software part number in the target version dataset, and obtain the corresponding software version number and flashing file information from the software information entry.

5. The method according to claim 4, characterized in that, Iterate through each software part number in the software part number list, search for a software information entry with the same part number in the target version dataset, and obtain the corresponding software version number and flashing file information from the software information entry, including: For the software part number currently being traversed, search in the target version dataset for whether there is a matching software information entry; If it exists, retrieve the corresponding software version number and flashing file information from the corresponding software information entry, and then end the traversal; If it does not exist, determine whether the current software part number is the last software part number in the software part number list. If the current software part number is not the last software part number, continue to traverse the next software part number until it is determined that there is a software information entry with the same software. Obtain the corresponding software version number and flashing file information from the corresponding software information entry.

6. The method according to claim 1, characterized in that, Updating the firmware version to the component to be updated includes: Obtain the flashing data corresponding to the firmware version; Based on the flashing data, a firmware update operation is performed on the component to be updated.

7. The method according to claim 1, characterized in that, The method further includes: After updating the firmware version to the component to be updated, verify whether the version information of the component to be updated matches the firmware version; If a match is found, the firmware update of the component to be updated is determined to be successful.

8. The method according to claim 7, characterized in that, The step of verifying whether the version information of the component to be updated matches the firmware version includes: Read the current software version number and current software component number of the component to be updated; The current software version number is compared with the target software version number corresponding to the firmware version, and the current software component number is compared with the target software component number corresponding to the firmware version. If the current software version number matches the target software version number, and the current software part number matches the target software part number, then a match is determined.

9. The method according to claim 1, characterized in that, The step of obtaining the vehicle's full-vehicle controller configuration data and the target version dataset from the server based on the vehicle identification information includes: Based on the vehicle identification information, obtain the vehicle's full-vehicle controller configuration data from the server; The vehicle controller configuration data is parsed to extract the hardware number and controller type of each controller; The hardware number and controller type are displayed on the interactive interface; In response to the user's selection operation based on the interactive interface, the corresponding controller is selected as the component to be updated, and the corresponding hardware information is obtained; In response to the selection operation, the target version dataset of the whole vehicle is obtained from the server based on the vehicle identification information.

10. A method for updating the version of a component, characterized in that, The method includes: In response to after-sales parts replacement needs, obtain vehicle identification information; Based on the vehicle identification information, determine the vehicle's full-vehicle controller configuration data and the vehicle target version dataset; The hardware information of the component to be updated is obtained, and based on the hardware information, the vehicle controller configuration data, and the target version dataset, the firmware version matching the component to be updated is determined, so that the vehicle system updates the firmware version to the component to be updated.

11. The method according to claim 10, characterized in that, The step of determining the firmware version matching the component to be updated based on the hardware information, the vehicle controller configuration data, and the target version dataset includes: Based on the hardware part numbers in the hardware information, a list of corresponding software part numbers is selected from the vehicle controller configuration data; Based on the software part number list, the appropriate software version and flashing file information are searched and obtained from the target version dataset; The firmware version is determined based on the software version and the flashing file information.

12. The method according to claim 11, characterized in that, The corresponding software part number list is filtered from the vehicle controller configuration data, including: The hardware part number is matched with the hardware code of each controller in the vehicle controller configuration data to extract the software part number associated with the hardware part number, forming a software part number list.

13. The method according to claim 12, characterized in that, Based on the software part number list, the appropriate software version and flashing file information are searched and obtained from the target version dataset, including: Iterate through each software part number in the software part number list, search for the software information entry with the same software part number in the target version dataset, and obtain the corresponding software version number and flashing file information from the software information entry.

14. A computing device, characterized in that, include: Memory, used to store computer programs; A processor, configured to implement the steps of the version update method for the component as described in any one of claims 1 to 13 when executing the computer program.

Images