Vehicle controller information updating method and device, electronic equipment and storage medium

Abstract

The invention relates to the technical field of vehicles, and discloses a vehicle controller information updating method and device, electronic equipment and a storage medium, and the updating method comprises the steps: obtaining the current controller information of a vehicle; wherein the current controller information comprises original information of the target controller and current associated controller information corresponding to the target controller; determining the current information of the target controller according to the current associated controller information; and if the current information is different from the original information, updating the original information based on the current information. The problem that the configuration information lags behind the real vehicle state change due to dependence on an order system is solved. Meanwhile, low efficiency and error risks caused by manual troubleshooting and input are avoided, quick response and accurate configuration under the scenes of restructuring, part changing, selective configuration changing and the like are achieved, and the consistency, accuracy and timeliness of information of a vehicle controller are ensured while the reliability and maintenance efficiency of a vehicle control system are improved.

Description

Technical Field

[0001] This application relates to the field of vehicle technology, and specifically to a method, apparatus, electronic device, and storage medium for updating vehicle controller information. Background Technology

[0002] The management of vehicle controller information largely relies on the configuration information preset by the order system. This method is significantly lagging when modifications, optional changes, or hardware replacements occur after the vehicle is put into use.

[0003] Because the order system cannot perceive the actual status changes of the vehicle controller in real time, the generated configuration information is inconsistent with the current actual configuration information of the vehicle, which may cause some functions to be unable to be enabled or to malfunction. In addition, manually consulting the technical manual based on the actual vehicle and manually modifying the configuration words is not only inefficient, but also very easy to introduce errors due to human negligence, affecting the stability and consistency of the entire vehicle system. Summary of the Invention

[0004] In view of the above problems, this application provides a method, apparatus, electronic device and storage medium for updating vehicle controller information. By actively acquiring the local information of the target controller and the actual information of the associated controller, comparing and making decisions to update, the consistency, accuracy and timeliness of the vehicle controller information are ensured.

[0005] According to one aspect of this application, a method for updating vehicle controller information is provided. The method includes: obtaining current controller information of a vehicle; wherein the current controller information includes original information of a target controller and current associated controller information corresponding to the target controller; determining the current information of the target controller based on the current associated controller information; and updating the original information based on the current information if the current information is different from the original information.

[0006] In one optional approach, the current associated controller information includes the association order of each current associated controller with the target controller, and information characters of each current associated controller; determining the current information of the target controller based on the current associated controller information includes: determining the character insertion position of each current associated controller based on the association order corresponding to each current associated controller; inserting the information characters corresponding to each current associated controller into their respective character insertion positions to obtain the current information of the target controller.

[0007] In one optional approach, inserting the information characters corresponding to each of the current associated controllers into their respective character insertion positions to obtain the current information of the target controller includes: if the current associated controller is missing from the original associated controller of the target controller, inserting a preset information character into the original character insertion position corresponding to the missing original associated controller, and inserting the information characters corresponding to each of the current associated controllers into their respective character insertion positions to obtain the current information of the target controller.

[0008] In an optional approach, the update method further includes: traversing each original associated controller of the target controller and matching the traversed original associated controller with the current associated controller; if the matching fails, determining that the traversed original associated controller does not exist in the current associated controller, thereby determining that the current associated controller is missing compared to the original associated controller of the target controller.

[0009] In an optional embodiment, the update method further includes: if the model and / or supplier of the current associated controller changes, then updating the information characters corresponding to the current associated controller according to the code of the changed model and / or supplier.

[0010] In an optional embodiment, the update method further includes: determining the character insertion position of each original associated controller according to the association order of the original associated controllers corresponding to the target controller; inserting the information characters corresponding to each original associated controller into their respective character insertion positions to obtain the original information of the target controller.

[0011] In one optional approach, the update method further includes: matching the current information with information characters at the same positions in the original information; if the information character at any position fails to match, it indicates that the current information is different from the original information; if the information characters at all positions match successfully, it indicates that the current information is the same as the original information.

[0012] According to another aspect of this application, a vehicle controller information updating device is provided. The updating device includes: an acquisition module for acquiring current controller information of a vehicle; wherein the current controller information includes original information of a target controller and current associated controller information corresponding to the target controller; a determination module for determining the current information of the target controller based on the current associated controller information; and an update module for updating the original information based on the current information if the current information is different from the original information.

[0013] According to one aspect of this application, an electronic device is provided, comprising: a controller; and a memory for storing one or more programs, which, when executed by the controller, perform the update method described above.

[0014] According to one aspect of this application, a computer-readable storage medium is also provided, on which computer-readable instructions are stored, which, when executed by a computer's processor, cause the computer to perform the above-described update method.

[0015] According to one aspect of this application, a computer program product or computer program is also provided, comprising computer instructions stored in a computer-readable storage medium. A processor of a computer device reads the computer instructions from the computer-readable storage medium and executes the computer instructions, causing the computer device to perform the above-described update method.

[0016] This application dynamically generates the current configuration information of the target controller by obtaining the vehicle's current actual controller information and combining it with the mapping relationship between the target controller and its associated controllers. This information is then automatically updated after being compared with the original information, solving the problem of configuration information lagging behind changes in the actual vehicle status due to reliance on the order system. Simultaneously, it avoids the inefficiency and error risks associated with manual troubleshooting and input, enabling rapid response and accurate configuration in scenarios such as modification, parts replacement, and optional changes. While improving the reliability and maintenance efficiency of the vehicle control system, it ensures the consistency, accuracy, and timeliness of vehicle controller information.

[0017] The above description is only an overview of the technical solution of this application. In order to better understand the technical means of this application and to implement it in accordance with the contents of the specification, and to make the above and other objects, features and advantages of this application more obvious and understandable, the following are specific embodiments of this application. Attached Figure Description

[0018] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this application and, together with the description, serve to explain the principles of this application. It is obvious that the drawings described below are merely some embodiments of this application, and those skilled in the art can obtain other drawings based on these drawings without any inventive effort.

[0019] Figure 1 This is a flowchart illustrating an exemplary embodiment of a method for updating vehicle controller information.

[0020] Figure 2 Based on Figure 1The exemplary embodiment shown illustrates a flowchart of another method for updating vehicle controller information.

[0021] Figure 3 This is a schematic diagram illustrating an application scenario of the vehicle controller information update method of this application.

[0022] Figure 4 This is a schematic diagram of the structure of a vehicle controller information updating device illustrated in an exemplary embodiment of this application.

[0023] Figure 5 This is a schematic diagram of the structure of a computer system for an electronic device illustrated in an exemplary embodiment of this application. Detailed Implementation

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

[0025] The block diagrams shown in the accompanying drawings are merely functional entities and do not necessarily correspond to physically independent entities. That is, these functional entities can be implemented in software, in one or more hardware modules or integrated circuits, or in different network and / or processor devices and / or microcontroller devices.

[0026] The flowcharts shown in the accompanying drawings are merely illustrative and do not necessarily include all content and operations / steps, nor do they necessarily have to be performed in the described order. For example, some operations / steps can be broken down, while others can be combined or partially combined; therefore, the actual execution order may change depending on the specific circumstances.

[0027] In this application, "multiple" refers to two or more. "And / or" describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A alone, A and B simultaneously, or B alone. The character " / " generally indicates that the preceding and following related objects have an "or" relationship.

[0028] As described in the background section, the order system cannot perceive the actual state changes of the vehicle controller in real time, resulting in inconsistencies between the generated configuration information and the vehicle's current actual configuration information. This may lead to some functions being unable to be enabled or operating abnormally. In addition, manually consulting the technical manual based on the actual vehicle and manually modifying the configuration words is not only inefficient, but also prone to errors due to human negligence, affecting the stability and consistency of the entire vehicle system.

[0029] To address this, one aspect of this application provides a method for updating vehicle controller information. This method actively acquires local information from the target controller and actual information from associated controllers, compares and updates the information, thereby ensuring the consistency, accuracy, and timeliness of the vehicle controller information. Please refer to the details below. Figure 1 , Figure 1 This is a schematic flowchart illustrating a method for updating vehicle controller information according to an exemplary embodiment of this application. The update method includes at least steps S110 to S130, which are described in detail below: S110: Obtain the current controller information of the vehicle; wherein, the current controller information includes the original information of the target controller and the current associated controller information corresponding to the target controller.

[0030] The current controller information is connected to the vehicle controller network via an on-board diagnostic interface (such as OBD, On-Board Diagnostics) or other communication buses (such as CAN, Controller Area Network). It sends diagnostic request commands to each ECU (Electronic Control Unit) and collects information from all electronic controllers. The acquired information includes at least the part number, supplier code, software version number, and status data such as the presence or absence of a response for each controller. In some embodiments, the current controller information can also be uploaded to a cloud server for centralized processing via wireless communication (such as Wi-Fi, 4G / 5G) to achieve remote batch configuration updates.

[0031] The target controller is the object on which information is expected to be updated. It can be understood as any controller in the vehicle, such as the air conditioning controller, body controller, or power domain controller.

[0032] Raw information refers to the configuration information currently stored in the non-volatile memory of the target controller. It is usually a string consisting of multiple fields, used to characterize the configuration status of itself and its surrounding systems, components, and controllers.

[0033] The generation method of the original information is illustrated here: the character insertion position of each original associated controller is determined according to the association order of the original associated controllers corresponding to the target controller; the information characters corresponding to each original associated controller are inserted into their respective character insertion positions to obtain the original information of the target controller.

[0034] The association order is predefined and stored in the vehicle configuration management system as structured data, used to indicate the bit field arrangement rules of the target controller's configuration information for each associated controller. For example, in the configuration information generation logic of controller A, associated controllers B, C, and D may correspond to the 1st-2nd, 3rd-4th, and 5th-6th flag bit fields, respectively. This mapping relationship is determined by the association order. The character insertion position is converted into a fixed offset or dynamically calculated byte / bit segment address in the configuration string according to the association order. For example, if the original associated controller 1 corresponds to character bits 0-1 and controller 2 corresponds to character bits 2-3, then their character insertion positions are "0" character bit and "2" character bit, respectively.

[0035] Information characters refer to a string generated according to a preset encoding rule based on the actual state of the original associated controller (such as existence, model, supplier code, etc.). They are typically function flags represented in hexadecimal. For example, if an associated controller exists and is supplied by supplier A, "01" is generated; if it does not exist, "00" is generated. These information characters, as basic data units, are written to a specified position in the target controller's original information string.

[0036] The information character insertion process can be implemented using string concatenation, memory copying, or bit manipulation. Taking the string method as an example, an empty string with a length equal to the total number of flag bits is initially created. Then, the information characters corresponding to each original associated controller are sequentially filled into their corresponding character insertion positions according to the association order. If an original associated controller is missing, a default value (such as "00") is filled in according to the rules to ensure the integrity of the original information structure. Since the original information is not statically stored but dynamically synthesized based on the structure and content of historical associated controllers, it can accurately reflect the true configuration state of the target controller at the time of the last update. This mechanism ensures the consistency of the generation logic between the original information and the current information, avoiding misjudgments caused by inconsistent formats or misaligned fields, thereby improving the reliability of configuration comparison and the accuracy of update decisions. Especially in scenarios where the original configuration needs to be traced back after vehicle modification or hardware replacement, this method significantly enhances the system's compatibility and robustness.

[0037] For example, as shown in Table 1, the original associated controllers corresponding to controller A include controller 1, controller 2, controller 3 and controller 4.

[0038] Table 1: Original Associated Controller Information Table for Controller A The part number RA1 of controller 1 has a supplier code of 1000, which corresponds to the original flag information of "01"; the part number RB1 of controller 2 has a supplier code of 2000, which corresponds to the original flag information of "01"; the part number RC1 of controller 3 has a supplier code of 3000, which corresponds to the original flag information of "01"; the part number RD2 of controller 4 has a supplier code of 4001, which corresponds to the original flag information of "02"; therefore, the original information of controller A is 01010102.

[0039] The current associated controller information is a real-time collection of information about other controllers that are functionally or communicatively dependent on the target controller. The existence, model differences, or supplier changes of the current associated controllers directly affect the behavioral logic or configuration requirements of the target controller. For example, in an air conditioning system, when the compressor controller is the target controller, whether it enables inverter mode may depend on the existence of a motor driver that supports this function (i.e., an associated controller). The information of the motor driver (part number + supplier code) constitutes part of the current associated controller information. This information can be filtered and extracted from the list of vehicle controllers through a preset mapping table or database.

[0040] In some embodiments, a fallback method for obtaining original information is provided, whereby the original information does not come directly from the target controller's local storage, but rather from historical diagnostic records or factory configuration files, facilitating comparative analysis of long-term change trends. For example, if original information cannot be obtained from the vehicle, it can be obtained from historical diagnostic records or factory configuration files stored in the cloud, providing multiple data sources to ensure successful acquisition of original information.

[0041] S120: Determine the current information of the target controller based on the current associated controller information.

[0042] For example, a pre-established configuration rule base transforms the collected actual status of associated controllers into corresponding target controller configuration information. Specifically, it calls the mapping logic defined in the configuration information association system to determine the existence of each associated controller item by item, and looks up the corresponding flag bit encoding value by combining its part number and supplier code. For example, if a certain flag bit is used to indicate "whether it is equipped with a heated seat", then if the associated seat controller exists and its part number belongs to the heated product family and the supplier is factory A, it outputs "01"; if it is supplied by factory B, it outputs "02"; if there is no response or it is not installed, it outputs the default value "00". All flag bits are concatenated to form a complete string to represent the current information of the target controller. To improve robustness, fault tolerance mechanisms can be set, such as trying to resend requests multiple times for controllers that have timed out of communication, or inferring their reasonable existence based on the vehicle architecture.

[0043] The core of this step lies in achieving automatic conversion from physical layer controller states to logical layer configuration information, avoiding the tedious process of manual table lookup and matching. Furthermore, because the rule base can be dynamically maintained, adding new controller models or supplier combinations only requires expanding the rule entries without changing the overall algorithm structure, demonstrating excellent scalability.

[0044] S130: If the current information is different from the original information, then the original information is updated based on the current information.

[0045] The current information is compared with the original information. This comparison can be done by string comparison, for example, matching characters at the same positions in the original information. If any character at any position fails to match, it indicates that the current information is different from the original information; if all characters at any position match successfully, it indicates that the current information is the same as the original information. This allows for a quick determination of whether the current information and the original information are identical.

[0046] The comparison method can also use checksum or hash value comparison to improve efficiency. When the comparison is inconsistent, the new current information is written to the designated storage area of ​​the target controller, thus completing the update of the original information. A security verification mechanism can be added before writing, such as requiring user authorization and checking whether the target controller's current operating mode is in a write-allowed state (such as ignition off or standby mode), to prevent accidental operation from interfering with the normal operation of the vehicle. After the update is completed, a reset or re-initialization can be automatically initiated to make the new configuration take effect.

[0047] In some embodiments, the update operation can be set to a condition-triggered mode, such as performing it only when the vehicle is parked and the battery has sufficient power, to ensure the appropriate timing of the update. A differential update strategy can also be used, modifying only the changed fields instead of rewriting the entire data, reducing write time and flash memory wear. Furthermore, the timestamp of each update, the preceding and following configuration values, and operator information can be recorded to form an audit log, facilitating subsequent traceability and fault analysis.

[0048] This embodiment dynamically generates the current configuration information of the target controller by acquiring the vehicle's current actual controller information and combining it with the mapping relationship between the target controller and its associated controllers. This information is then automatically updated after being compared with the original information, solving the problem of configuration information lagging behind changes in the actual vehicle status due to reliance on the order system. Simultaneously, it avoids the inefficiency and error risks associated with manual troubleshooting and input, enabling rapid response and accurate configuration in scenarios such as modification, parts replacement, and optional changes. While improving the reliability and maintenance efficiency of the vehicle control system, it ensures the consistency, accuracy, and timeliness of vehicle controller information.

[0049] In another exemplary embodiment of this application, it is described in detail how to determine the current information of the target controller based on the current associated controller information. Please refer to [link to relevant documentation] for details. Figure 2 , Figure 2 Based on Figure 1 The illustrated exemplary embodiment presents a flowchart of another method for updating vehicle controller information. This update method, as shown in the example... Figure 1 S120 shown includes S210 to S220; wherein, the current associated controller information includes the association order between each current associated controller and the target controller, as well as the information characters of each current associated controller, detailed as follows: S210: Determine the character insertion position of each current associated controller according to the association order corresponding to each current associated controller.

[0050] The current associated controller can be the same as the original associated controller, or it may be missing. However, the association order here is the original association order. Even if the corresponding original associated controller is missing, the information character at the character insertion position corresponding to the missing original associated controller can be left blank.

[0051] For example, the target controller is controller A in Table 1 above, and its corresponding original associated controllers are controller B (corresponding to associated controller 1 in Table 1), controller C (corresponding to associated controller 3 in Table 1), controller D (corresponding to associated controller 2 in Table 1) and controller E (corresponding to associated controller 4 in Table 1), so that the character insertion position of each current associated controller can be quickly determined, i.e., the corresponding flag bit.

[0052] The current associated controllers corresponding to controller A are controller B (current part number RA1, supplier code 1000), controller C (current part number RC1, supplier code 3000), and controller E (current part number RD2, supplier code 4001). Therefore, it can be seen that the current associated controllers are missing controller D (i.e., associated controller 3 in Table 1) compared to the original associated controllers.

[0053] S220: Insert the information characters corresponding to each currently associated controller into their respective character insertion positions to obtain the current information of the target controller.

[0054] For example, if the target controller is controller A in Table 1, the information character (one of “00”, “01”, or “02”) corresponding to each current associated controller is determined based on the part number and supplier code of the corresponding associated controller in Table 1, and each information character is inserted into its respective character insertion position to obtain the current information of controller A.

[0055] For example, if the current associated controller is missing from the original associated controller of the target controller, a preset information character is inserted into the original character insertion position corresponding to the missing original associated controller, and the information characters corresponding to each current associated controller are inserted into their respective character insertion positions to obtain the current information of the target controller.

[0056] Among them, the preset information character is the information character that represents the missing corresponding associated controller. "00" can be inserted into the original character insertion position corresponding to the missing original associated controller to indicate that the target controller's current information is missing the corresponding original associated controller.

[0057] For example, the target controller is controller A in Table 1 above, and its corresponding original associated controllers are controller B (corresponding to associated controller 1 in Table 1), controller C (corresponding to associated controller 3 in Table 1), controller D (corresponding to associated controller 2 in Table 1) and controller E (corresponding to associated controller 4 in Table 1). The original information of controller A is 01010102.

[0058] The current associated controllers corresponding to controller A are obtained as controller B (current part number RA1, supplier code 1000), controller C (current part number RC1, supplier code 3000), and controller E (current part number RD2, supplier code 4001). It can be seen that the current associated controller is missing controller D (i.e., associated controller 3 in Table 1) compared to the original associated controller. At this time, some characters in the information "0101__02" are missing. The missing characters are inserted into the original character insertion position corresponding to associated controller D as recorded in Table 1, so that the current information of controller A is 01010002.

[0059] The following explains how to determine if the current associated controller is missing from the original associated controller of the target controller: Iterate through each original associated controller of the target controller and match the traversed original associated controller with the current associated controller; if the match fails, it is determined that the traversed original associated controller does not exist in the current associated controller, thus determining that the current associated controller is missing from the original associated controller of the target controller.

[0060] Traversal refers to visiting each controller record in the original associated controller list one by one, ensuring that every associated party that was once defined as affecting the generation of the target controller configuration word is checked without omission.

[0061] The matching process is based on controller identity, such as using the controller's physical address, function name, or unique device identifier as the matching key, performing a one-to-one comparison. The matching algorithm can be a hash lookup, linear search, or a tree-based fast indexing method, suitable for controller network environments of different sizes. In an optional embodiment, when the original associated controller is defined only by its functional role (such as "front radar module") rather than a specific part number, the system can read the current controller's functional description field through diagnostic services to achieve semantic-level matching, thereby supporting cross-model compatibility judgment.

[0062] Matching failure refers to the inability to detect a controller response with the same identity or functional role in the current real-vehicle environment. This may manifest as a diagnostic request timeout, a negative response code, or failure to broadcast a message on the expected bus. Once a matching failure is determined for an original associated controller, it is marked as a "missing item," and the missing event is recorded for subsequent processing. This mechanism supports multi-level missing item identification; for example, it can identify not only the overall controller missing but also extend to the sub-component level (e.g., a controller exists but its key functional units are not activated). In an optional embodiment, a fault tolerance threshold can be set to allow brief communication anomalies to be considered as missing items rather than immediately, but rather by combining multiple sampling results for a comprehensive judgment, thus improving the robustness of the judgment.

[0063] This example demonstrates a refined identification of the differences between the original set of associated controllers and the current vehicle configuration. By iteratively verifying the existence status of each original associated controller item by item, it solves the problem of missing controllers caused by downgrading or modification, which is difficult to detect in traditional configuration management. This effectively supports the integrity and accuracy of the configuration information generation logic, avoids functional abnormalities due to the omission of key flags, and improves the vehicle control system's ability to adapt to configuration changes.

[0064] When the associated controllers upon which the target controller depends still exist in the vehicle system, but their hardware model or supplier changes, continuing to use the original information character generation rules may result in the configuration words failing to accurately reflect the actual vehicle's hardware and software matching status, leading to functional abnormalities or control logic errors. For example, when the same type of controller is provided by different suppliers, their communication protocols, functional support, or internal parameters may differ, requiring identification and adaptation through differentiated coding.

[0065] Therefore, in another exemplary embodiment of this application, if the model and / or supplier of the current associated controller changes, the information characters corresponding to the current associated controller are updated according to the code of the changed model and / or supplier.

[0066] Here, "model number" refers to the specific product model of the controller, usually indicated by a part number, used to distinguish hardware entities of different design versions, performance levels, or functional configurations. "Supplier" refers to the manufacturer that provides the controller, usually identified by a supplier code, such as the OEM manufacturer code defined in the ISO 14229 standard. Any change in either the model number or the supplier will affect the controller.

[0067] The change detection method can employ a comparison mechanism: the model and supplier code of the currently associated controller actually read from the vehicle are compared item by item with the corresponding information (model and / or supplier) in historical records or original configuration data. If any field is inconsistent, it is determined that a change has occurred.

[0068] Information characters are the basic encoding units used to construct the configuration word of the target controller. They are usually fixed-length hexadecimal strings representing the value of a specific flag bit. The generation of these information characters is based on a preset mapping rule library, such as the associated control model-code mapping table shown in Table 2.

[0069] Table 2: Associated Controller Model-Code Mapping Table If a change in the model or supplier of a certain associated controller is detected, the mapping table is automatically queried to find the information character that matches the new parameter combination and replace the original information character.

[0070] In this embodiment, even if the associated controller itself exists but its source or specifications change during vehicle modification, optional changes, or component replacement, it can automatically identify and update the corresponding coding information, avoiding functional mismatch caused by static configuration; it improves the flexibility and accuracy of controller configuration, and is especially suitable for complex working conditions such as multi-source supply, platform-based vehicle co-production, and after-sales modification.

[0071] In another exemplary embodiment of this application, the application scenarios of the above-mentioned multiple update methods are illustrated by way of example. Please refer to the following for details. Figure 3 , Figure 3 This is a schematic diagram illustrating an application scenario of the vehicle controller information update method of this application. It includes a vehicle 100 and a detection and update device 200, which can be connected via physical wiring or wireless communication. This application does not limit the connection method between them.

[0072] The detection and update device 200 can be physically connected to the vehicle 100. The detection and update device 200 can quickly establish a connection with the vehicle 100 through physical wiring, so that both parties enter the detection and update state. The detection and update device 200 can execute any of the above-mentioned update methods, as illustrated below: Obtain the current controller information of vehicle 100; wherein, the current controller information includes the original information of the target controller and the current associated controller information corresponding to the target controller; determine the current information of the target controller based on the current associated controller information; if the current information is different from the original information, update the original information based on the current information.

[0073] Another aspect of this application provides a device for updating vehicle controller information, such as... Figure 4 As shown, Figure 4 This is a schematic diagram illustrating the structure of a vehicle controller information updating device according to an exemplary embodiment of this application. The updating device 400 includes: The acquisition module 410 is used to acquire the current controller information of the vehicle; wherein, the current controller information includes the original information of the target controller and the current associated controller information corresponding to the target controller.

[0074] The determination module 430 is used to determine the current information of the target controller based on the current associated controller information.

[0075] The update module 450 is used to update the original information based on the current information if the current information is different from the original information.

[0076] In another exemplary embodiment, the current associated controller information includes the association order between each current associated controller and the target controller, and information characters for each current associated controller; the determining module 430 includes: The position determination unit is used to determine the character insertion position of each current associated controller according to the association order corresponding to each current associated controller.

[0077] The current information determination unit is used to insert the information characters corresponding to each currently associated controller into their respective character insertion positions to obtain the current information of the target controller.

[0078] In another exemplary embodiment, the current information determination unit includes: The current information determination section is used to determine the current information of the target controller if there is a missing original associated controller compared to the original associated controller of the current associated controller. The preset information character is inserted into the original character insertion position corresponding to the missing original associated controller, and the information characters corresponding to each current associated controller are inserted into their respective character insertion positions to obtain the current information of the target controller.

[0079] In another exemplary embodiment, the updating device 400 further includes: The traversal matching module is used to traverse each original associated controller of the target controller and match the traversed original associated controller with the current associated controller.

[0080] The matching failure module is used to determine if the original associated controller being traversed does not exist in the current associated controller if the matching fails, thus determining that the original associated controller of the current associated controller is missing compared to the original associated controller of the target controller.

[0081] In another exemplary embodiment, the updating device 400 further includes: The change update module is used to update the information characters corresponding to the current associated controller based on the changed model and / or supplier code if the model and / or supplier of the current associated controller changes.

[0082] In another exemplary embodiment, the updating device 400 further includes: The character insertion position determination module is used to determine the character insertion position of each original associated controller according to the association order of the original associated controllers corresponding to the target controller; The insertion module is used to insert the information characters corresponding to each original associated controller into their respective character insertion positions to obtain the original information of the target controller.

[0083] In another exemplary embodiment, the updating device 400 further includes: The character matching module is used to match the current information with characters at the same positions in the original information.

[0084] The character matching failure module indicates that if any character in the information at any position fails to match, the current information is different from the original information.

[0085] The character matching success module is used to indicate that if all characters in the information are matched successfully, the current information is the same as the original information.

[0086] This application's update device dynamically generates the target controller's current configuration information by acquiring the vehicle's current actual controller information and combining it with the mapping relationship between the target controller and its associated controllers. It then automatically updates the information after comparing it with the original information, solving the problem of configuration information lagging behind changes in the actual vehicle status due to reliance on the order system. Simultaneously, it avoids the inefficiency and error risks associated with manual troubleshooting and input, enabling rapid response and accurate configuration in scenarios such as modification, parts replacement, and optional changes. While improving the reliability and maintenance efficiency of the vehicle control system, it ensures the consistency, accuracy, and timeliness of vehicle controller information.

[0087] It should be noted that the updating device provided in the above embodiments and the updating method provided in the foregoing embodiments belong to the same concept. The specific way in which each module and unit performs operations has been described in detail in the method embodiments, and will not be repeated here.

[0088] Another aspect of this application provides an electronic device, including: a controller; and a memory for storing one or more programs, which, when executed by the controller, perform the update method described above.

[0089] Please see Figure 5 , Figure 5 This is a schematic diagram of the structure of a computer system for an electronic device according to an exemplary embodiment of this application, illustrating a schematic diagram of the structure of a computer system suitable for implementing the embodiments of this application.

[0090] It should be noted that, Figure 5 The computer system 500 of the electronic device shown is merely an example and should not impose any limitation on the functionality and scope of use of the embodiments of this application.

[0091] like Figure 5 As shown, the computer system 500 includes a Central Processing Unit (CPU) 501, which can perform various appropriate actions and processes, such as executing the methods described in the above embodiments, based on programs stored in Read-Only Memory (ROM) 502 or programs loaded from storage portion 508 into Random Access Memory (RAM) 503. The RAM 503 also stores various programs and data required for system operation. The CPU 501, ROM 502, and RAM 503 are interconnected via a bus 504. An Input / Output (I / O) interface 505 is also connected to the bus 504.

[0092] The following components are connected to I / O interface 505: an input section 506 including a keyboard, mouse, etc.; an output section 507 including a cathode ray tube (CRT), liquid crystal display (LCD), etc., and speakers, etc.; a storage section 508 including a hard disk, etc.; and a communication section 509 including a network interface card such as a LAN (Local Area Network) card, modem, etc. The communication section 509 performs communication processing via a network such as the Internet. A drive 510 is also connected to I / O interface 505 as needed. Removable media 511, such as a disk, optical disk, magneto-optical disk, semiconductor memory, etc., are installed on drive 510 as needed so that computer programs read from them can be installed into storage section 508 as needed.

[0093] Specifically, according to embodiments of this application, the processes described above with reference to the flowcharts can be implemented as computer software programs. For example, embodiments of this application include a computer program product comprising a computer program carried on a computer-readable medium, the computer program including a computer program for performing the methods shown in the flowcharts. In such embodiments, the computer program can be downloaded and installed from a network via communication section 509, and / or installed from removable medium 511. When the computer program is executed by central processing unit (CPU) 501, it performs various functions defined in the system of this application.

[0094] It should be noted that the computer-readable medium shown in the embodiments of this application can be a computer-readable signal medium or a computer-readable storage medium, or any combination of the two. A computer-readable storage medium can be, for example, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination thereof. More specific examples of a computer-readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer disk, a hard disk, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM), flash memory, optical fiber, portable compact disc read-only memory (CD-ROM), optical storage device, magnetic storage device, or any suitable combination thereof. In this application, a computer-readable storage medium can be any tangible medium containing or storing a program that can be used by or in conjunction with an instruction execution system, apparatus, or device. In this application, a computer-readable signal medium can include a data signal propagated in baseband or as part of a carrier wave, carrying a computer-readable computer program. The transmitted data signal can take various forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination thereof. The computer-readable signal medium can also be any computer-readable medium other than a computer-readable storage medium, which can send, propagate, or transmit a program for use by or in connection with an instruction execution system, apparatus, or device. The computer program contained on the computer-readable medium can be transmitted using any suitable medium, including but not limited to wireless, wired, etc., or any suitable combination thereof.

[0095] The flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of this application. Each block in a flowchart or block diagram may represent a module, segment, or portion of code, which contains one or more executable instructions for implementing a specified logical function. It should also be noted that in some alternative implementations, the functions indicated in the blocks may occur in a different order than those indicated in the drawings. For example, two consecutively indicated blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each block in a block diagram or flowchart, and combinations of blocks in a block diagram or flowchart, may be implemented using a dedicated hardware-based system that performs the specified function or operation, or using a combination of dedicated hardware and computer instructions.

[0096] The units described in the embodiments of this application can be implemented in software or hardware, and the described units can also be located in a processor. The names of these units do not necessarily limit the specific unit itself.

[0097] Another aspect of this application provides a computer-readable storage medium storing a computer program that, when executed by a processor, implements the aforementioned update method. This computer-readable storage medium may be included in the electronic device described in the above embodiments, or it may exist independently and not incorporated into the electronic device.

[0098] Another aspect of this application provides a computer program product or computer program including computer instructions stored in a computer-readable storage medium. A processor of a computer device reads the computer instructions from the computer-readable storage medium and executes the computer instructions, causing the computer device to perform the update methods provided in the various embodiments described above.

[0099] According to one aspect of the embodiments of this application, a computer system is also provided, including a Central Processing Unit (CPU), which can perform various appropriate actions and processes based on a program stored in read-only memory (ROM) or a program loaded from storage into random access memory (RAM), such as performing the methods described above. Various programs and data required for system operation are also stored in the RAM. The CPU, ROM, and RAM are interconnected via a bus. Input / output (I / O) interfaces are also connected to the bus.

[0100] The following components are connected to the I / O interface: input components including keyboards, mice, etc.; output components including cathode ray tubes (CRTs), liquid crystal displays (LCDs), and speakers; storage components including hard drives; and communication components including network interface cards such as LAN (Local Area Network) cards and modems. The communication components perform communication processing via networks such as the Internet. Drives are also connected to the I / O interface as needed. Removable media, such as disks, optical discs, magneto-optical discs, semiconductor memories, etc., are installed on the drive as needed so that computer programs read from them can be installed into the storage components as required.

[0101] The above description is merely a preferred exemplary embodiment of this application and is not intended to limit the implementation of this application. Those skilled in the art can easily make corresponding modifications or alterations based on the main concept and spirit of this application. Therefore, the scope of protection of this application should be determined by the scope of protection claimed in the claims.

Claims

1. A method for updating vehicle controller information, characterized in that, The update method includes: Obtain the current controller information of the vehicle; wherein the current controller information includes the original information of the target controller and the current associated controller information corresponding to the target controller; The current information of the target controller is determined based on the current associated controller information; If the current information differs from the original information, the original information is updated based on the current information.

2. The update method according to claim 1, characterized in that, The current associated controller information includes the association order between each current associated controller and the target controller, as well as the information characters of each current associated controller; The current information of the target controller is determined based on the current associated controller information, including: The character insertion position of each current associated controller is determined according to the association order corresponding to each current associated controller; The information characters corresponding to each of the currently associated controllers are inserted into their respective character insertion positions to obtain the current information of the target controller.

3. The updating method according to claim 2, characterized in that, Inserting the information characters corresponding to each of the currently associated controllers into their respective character insertion positions to obtain the current information of the target controller includes: If the current associated controller is missing from the original associated controller of the target controller, then a preset information character is inserted into the original character insertion position corresponding to the missing original associated controller, and the information characters corresponding to each current associated controller are inserted into their respective character insertion positions to obtain the current information of the target controller.

4. The update method according to claim 3, characterized in that, The update method further includes: Iterate through each original associated controller of the target controller and match the traversed original associated controller with the current associated controller; If the matching fails, it is determined that the original associated controller traversed does not exist in the current associated controller, thus determining that the current associated controller is missing from the original associated controller of the target controller.

5. The updating method according to claim 2, characterized in that, The update method further includes: If the model and / or supplier of the current associated controller changes, the information characters corresponding to the current associated controller are updated according to the code of the changed model and / or supplier.

6. The updating method according to any one of claims 1 to 5, characterized in that, The update method further includes: The character insertion position of each original associated controller is determined according to the association order of the original associated controllers corresponding to the target controller; The information characters corresponding to each original associated controller are inserted into their respective character insertion positions to obtain the original information of the target controller.

7. The update method according to any one of claims 1 to 5, characterized in that, The update method further includes: Match the current information with the information characters at the same position in the original information; If any information character fails to match, it indicates that the current information is different from the original information; If all information characters at all positions match successfully, it indicates that the current information is the same as the original information.

8. A device for updating vehicle controller information, characterized in that, The updating device includes: The acquisition module is used to acquire the current controller information of the vehicle; wherein, the current controller information includes the original information of the target controller and the current associated controller information corresponding to the target controller; The determination module is used to determine the current information of the target controller based on the current associated controller information; An update module is used to update the original information based on the current information if the current information is different from the original information.

9. An electronic device, characterized in that, include: Controller; A memory for storing one or more programs, which, when executed by a controller, cause the controller to implement the update method as described in any one of claims 1 to 7.

10. A computer-readable storage medium, characterized in that, It stores computer-readable instructions that, when executed by the computer's processor, cause the computer to perform the update method as described in any one of claims 1 to 7.

Images