Configuration file updating method and device, equipment and medium

Abstract

The invention relates to a configuration file updating method and device, equipment, a medium and a product. The method comprises the following steps: analyzing a configuration file of a target functional component of a vehicle to obtain configuration information of each sub-component of the target functional component; constructing a template file of the target functional component according to each piece of configuration information; the template file comprises a corresponding relationship between a configuration field and a field value corresponding to each sub-component, and each configuration field comprises the field value of the configuration field and an operation type field; according to the configuration change information of the to-be-updated sub-component, determining a set field value of an operation type field under a target configuration field corresponding to the to-be-updated sub-component and a target field value of the target configuration field; according to the operation corresponding to the set field value and the target field value, updating the template file to obtain an updated template file; and according to the updated template file, determining a target configuration file of the updated target function component. By adopting the method, the updating efficiency of the configuration file can be improved.

Description

Technical Field

[0001] This application relates to the field of vehicle technology, and in particular to a method, apparatus, device, and medium for updating configuration files. Background Technology

[0002] With the development of automotive electronics technology, AUTOSAR (Automotive Open System Architecture) has been widely used as a standardized software architecture in various automotive ECUs (Electronic Control Units).

[0003] In traditional techniques, updating the configuration file for the AUTOSAR module involves manually locating the configuration components based on the AUTOSAR specification, modifying parameter values, reference relationships, or adding / deleting components.

[0004] However, in multi-module collaborative configuration scenarios, traditional technologies rely solely on engineers' professional experience for configuration, resulting in low efficiency in updating configuration files. Summary of the Invention

[0005] Therefore, it is necessary to provide a configuration file update method, apparatus, device, and medium that can improve the efficiency of configuration file updates, addressing the aforementioned technical problems.

[0006] Firstly, this application provides a method for updating a configuration file, including:

[0007] The configuration files of the target functional components of the vehicle are parsed to obtain the configuration information of each sub-component of the target functional components;

[0008] Based on the configuration information, construct the template file for the target functional component; the template file includes the correspondence between the configuration fields and field values ​​for each sub-component, and each configuration field includes the field value and operation type field;

[0009] Based on the configuration change information of the sub-component to be updated, determine the set field value of the operation type field under the target configuration field of the sub-component to be updated, as well as the target field value of the target configuration field;

[0010] The template file is updated based on the operation corresponding to the set field value and the target field value to obtain the updated template file;

[0011] Based on the updated template file, determine the target configuration file for the updated target functional components.

[0012] In one embodiment, determining the updated target configuration file of the target functional component based on the updated template file includes: updating the configuration information of the sub-component to be updated in the configuration file according to the updated template file to obtain the updated target configuration file of the target functional component; or, mapping the updated template file to a configuration file to obtain the updated target configuration file of the target functional component.

[0013] In one embodiment, updating the configuration information of the sub-component to be updated in the configuration file according to the updated template file includes: determining the set of operation instructions for the sub-component to be updated according to the updated template file; wherein the set of operation instructions is determined based on the set field values ​​of the sub-component to be updated; and updating the configuration information of the sub-component to be updated in the configuration file according to the set of operation instructions for the sub-component to be updated.

[0014] In one embodiment, updating the configuration information of the sub-component to be updated in the configuration file according to the set of operation instructions for the sub-component to be updated includes: if the set of operation instructions for the sub-component to be updated includes a new operation instruction, updating the configuration information of the sub-component to be updated in the configuration file according to the set of operation instructions; wherein, the new operation instruction is determined based on the value of the set field under the component name field in the target configuration field corresponding to the sub-component to be updated.

[0015] In one embodiment, the configuration information of the sub-component to be updated in the configuration file is updated according to the set of operation instructions, including: determining the component set to which the sub-component to be updated belongs according to the new operation instructions, and determining the parent component and reference path of the sub-component to be updated according to the component set; determining the addition position of the sub-component to be updated according to the parent component and reference path; and adding the configuration information of the sub-component to be updated at the addition position in the configuration file according to the set of operation instructions.

[0016] In one embodiment, updating the configuration information of the sub-component to be updated in the configuration file according to the set of operation instructions for the sub-component to be updated includes: deleting the configuration information of the sub-component to be updated in the configuration file if the set of operation instructions for the sub-component to be updated includes a delete operation instruction; wherein the delete operation instruction is determined based on the set field value under the component name field in the target configuration field corresponding to the sub-component to be updated.

[0017] In one embodiment, updating the configuration information of the sub-component to be updated in the configuration file according to the set of operation instructions for the sub-component to be updated includes: if the set of operation instructions for the sub-component to be updated includes configuration operation instructions, determining the first configuration field corresponding to the configuration operation instruction from the target configuration field according to the configuration operation instruction; wherein, the configuration operation instruction is determined based on the set field values ​​of other fields in the target configuration field corresponding to the sub-component to be updated, excluding the component name field; determining the component set to which the sub-component to be updated belongs, and determining the parent component and reference path of the sub-component to be updated according to the component set; determining the update position corresponding to the first configuration field according to the parent component and reference path; and updating the configuration information recorded at the update position to the target field value of the first configuration field.

[0018] Secondly, this application also provides a configuration file updating device, comprising:

[0019] The parsing module is used to parse the configuration files of the target functional components of the vehicle to obtain the configuration information of each sub-component of the target functional components;

[0020] The building module is used to build template files for the target functional components based on the configuration information. The template files include the correspondence between the configuration fields and field values ​​for each sub-component, and each configuration field includes the field value and operation type field.

[0021] The processing module is used to determine the set field value of the operation type field under the target configuration field of the subcomponent to be updated, as well as the target field value of the target configuration field, based on the configuration change information of the subcomponent to be updated.

[0022] The processing module is also used to update the template file according to the operation corresponding to the set field value and the target field value, so as to obtain the updated template file;

[0023] The update module is used to determine the target configuration file for the updated target functional components based on the updated template file.

[0024] Thirdly, this application also provides a computer device, including a memory and a processor, wherein the memory stores a computer program, and the processor executes the computer program to implement the steps in the above-described configuration file update method.

[0025] Fourthly, this application also provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the steps in the above-described configuration file update method.

[0026] Fifthly, this application also provides a computer program product, including a computer program that, when executed by a processor, implements the steps in the above-described configuration file update method.

[0027] The aforementioned configuration file update methods, devices, equipment, media, and products achieve accurate identification of target functional components by precisely parsing the configuration file of the target functional component and extracting the configuration information of each sub-component. Secondly, a template file containing configuration fields, field values ​​attached to the configuration fields, and operation type fields is constructed, providing a standardized and structured unified carrier for configuration changes. Thirdly, based on the configuration change information of the sub-component to be updated, the operation type setting value and target field value of the target configuration field are determined in a targeted manner, achieving precise binding between incremental change requirements and configuration fields. Operations are only performed on the sub-components that need to be changed and their corresponding fields, reducing the cross-module compatibility risks caused by a full replacement of the configuration file. Finally, by updating the template file and generating the target configuration file accordingly, the update efficiency of the configuration file is improved, and the high-frequency iteration needs of configuration files in the automotive electronics field can be met. Attached Figure Description

[0028] To more clearly illustrate the technical solutions in the embodiments of this application or related technologies, the drawings used in the description of the embodiments of this application or related technologies will be briefly introduced below. Obviously, the drawings described below are only some embodiments of this application. For those skilled in the art, other related drawings can be obtained based on these drawings without creative effort.

[0029] Figure 1 This is a schematic diagram of the architecture of a configuration file update method in one embodiment;

[0030] Figure 2 This is a flowchart illustrating a configuration file update method in one embodiment;

[0031] Figure 3 This is a schematic diagram of the structure of a template file in one embodiment;

[0032] Figure 4 This is a schematic diagram of the template file generation process in one embodiment;

[0033] Figure 5 This is a schematic diagram of the configuration file update process in one embodiment;

[0034] Figure 6 This is a flowchart illustrating the configuration file update method in another embodiment;

[0035] Figure 7 This is a structural block diagram of a configuration file update device in one embodiment;

[0036] Figure 8 This is an internal structural diagram of a computer device in one embodiment. Detailed Implementation

[0037] To make the objectives, technical solutions, and advantages of this application clearer, the following detailed description is provided in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative and not intended to limit the scope of this application.

[0038] It should be noted that the terms "first," "second," etc., used in this application can be used to describe various elements, but these elements are not limited by these terms. These terms are only used to distinguish the first element from the second element. The terms "comprising" and "having," and any variations thereof, used in this application, are intended to cover non-exclusive inclusion. The term "multiple" used in this application refers to two or more. The term "and / or" used in this application refers to one of the embodiments, or any combination of multiple embodiments.

[0039] In one exemplary embodiment, such as Figure 2 As shown, a configuration file update method is provided. This method can be applied to a computer device, which can be a terminal or a server. The method is illustrated using the NeuArxml tool, which can be deployed on a terminal or server. The method includes:

[0040] S201, parse the configuration file of the target functional component of the vehicle to obtain the configuration information of each sub-component of the target functional component.

[0041] The target functional component can be an AUTOSAR architecture software module with independent core functions in the vehicle electronic system, including but not limited to CAN, EECUC, CANIF, PDUR, COM, DCM, DEM, and CANTP; the configuration file can be a standardized file in ARXML format, which uses XML structured language to describe the complete configuration parameters, hierarchical relationships, and constraint rules of the functional module; the sub-component can be a configuration unit inside the target functional component, corresponding to container components and their nested structures in ARXML; the configuration information can be a standardized data set extracted from the sub-component, including but not limited to component name, path identifier, parameters, and references.

[0042] Optionally, based on the hierarchical definition rules of components and sub-components in the AUTOSAR specification, the overall structure of the configuration file is traversed to locate the top-level configuration component of the target functional component; then, the configuration sub-components corresponding to all sub-components under the top-level component are parsed layer by layer to extract information such as component name, path identifier, parameters and references within each sub-component; finally, the extracted data are classified and integrated according to the sub-component dimension to form the structured configuration information corresponding to each sub-component.

[0043] For example, the NeuArxml tool employs a modular design, and its modules work together as follows: Figure 1 As shown. It mainly includes the following modules: The business logic module is used to generate standardized template files with external configurability, and also to parse and process the configured template files, extract and encapsulate the input parameter data required by the core library interface, and trigger the execution of corresponding business operations by calling the preset interface of the middleware module;

[0044] The middleware module is the core interface component for external interaction of the core library. It includes two middleware sub-modules: communication and diagnostics. Each module within communication and diagnostics needs to be implemented separately, including the Controller Area Network (CAN) module, Electronic Control Unit Configuration (ECUConfiguration, EECUC) module, CAN Interface (CANIF) module, Protocol Data Unit Router (PDUR) module, Communication Manager (COM) module, Diagnostic Communication Manager (DCM) module, Diagnostic Event Manager (DEM) module, and CAN Transport Protocol (CANTP) module. The business logic module initiates business requests through the middleware module. After processing the business data internally, it calls the interface of the ARXML file processing module to implement specific operations. The middleware module serves as the link between external requirements and internal core capabilities.

[0045] The routing module dynamically instantiates each middleware module and stores the generated module instantiations in the instance pool. When data from a module instantiation is needed, if it already exists in the instance pool, it is used directly; otherwise, a new instantiation is created.

[0046] The ARXML file processing module is the core component for ARXML file operations, and it has functions such as adding and deleting components, adding, deleting and modifying parameters, and adding and deleting references. Because it is necessary to convert the modified ARXML data into JSON synchronously, it relies on the format conversion interface provided by the JSON mirror module, and is the core execution unit for implementing ARXML file editing.

[0047] The JSON mirroring module is used for format conversion components, providing conversion interfaces for the ARXML file processing module to call. It has no other external interaction logic and is a basic component supporting ARXML operations and JSON data synchronization. The logging module is a global logging service component, and all modules rely on its provided logging interface to ensure that the software operation process is traceable.

[0048] It's worth noting that the NeuArxml tool primarily handles communication and diagnostics during operation, such as CAN, EUC, CANIF, PDUR, COM, DCM, DEM, and CANTP in the AUTOSAR module. Each of these AUTOSAR modules has its own business logic module and middleware module; the routing module, ARXML file processing module, and JSON mirroring module are shared.

[0049] S202, Based on the configuration information, construct the template file of the target functional component; wherein, the template file includes the correspondence between the configuration fields and field values ​​corresponding to each sub-component, and each configuration field includes the field value and operation type field of the configuration field.

[0050] The template file can be a structured intermediate configuration file (such as JSON format); the configuration fields include, but are not limited to, parameter fields, reference fields, and field values; the operation type field can be a unique identifier in the template file used to identify the operation performed on the configuration field (such as add, modify, or delete).

[0051] Optionally, for each sub-component, its configuration information is broken down into the correspondence between configuration fields and field values ​​(e.g., the configuration field CanIfTxPduId of the sub-component CanIfTxPduCfgs corresponds to the field value 0x123), and an operation type field is added to each configuration field. The field value of the operation type field can be initially assigned a default identifier (e.g., null, indicating an empty value). All configuration fields, field values, and operation type field association data are integrated according to the hierarchical structure of the target functional component to generate the target functional component template file.

[0052] It is worth noting that the template file format is as follows: Figure 3As shown, the TITLE field identifies a set of components, serving as a classification identifier for the operation object. Configuration fields include NAME, TEXTUAL, NUMERICAL, REFERENCE, LABEL, and value fields. The NAME field represents the name of the component, and its associated components can be added or deleted via an interface based on the corresponding operation type. The TEXTUAL field defines a set of text-type parameters, including but not limited to subtypes such as ENUMERATION, BOOLEAN, and STRING. The NUMERICAL field defines a set of numeric-type parameters, including but not limited to subtypes such as INTEGER, FLOAT, and DOUBLE. The REFERENCE field defines the association relationship of reference types. The LABEL field identifies the smallest unit of the executable operation. The value field stores the specific data value to be operated on (i.e., the field value). The operation field limits the operation type (i.e., the operation type field), with values ​​ranging from add, modify, and delete.

[0053] This implementation method uses CANIF as an example to illustrate the template file generation method, and the template file generation process is as follows: Figure 4As shown in the figure, the business logic module triggers the instantiation operation by calling the interface of the routing module. The routing module has built-in file name parsing logic, which can dynamically generate a unique target instance according to the naming characteristics of the ARXML file name, and store the target instance in a preset instance pool for unified management; CANIF has its own independent business logic module, which calls the routing module object initialization interface to return the routing module instance. The routing module instance contains a file rule (the file rule is the correspondence between the Autosar module name and the corresponding middleware class name, such as Canif<module name>:CanIfConfiguration<canif middleware class name>) and an instance pool (the instance pool saves each Autosar module instance generated later in the format of middleware class name:instance, such as CanIfConfiguration:instance of Canif). The file rule unifies the creation process of each Autosar module instance, and the instance pool ensures the uniqueness of each Autosar module instance, preventing duplicate creation; CANIF calls the interface to obtain the CANIF instance through the routing module instance. The parameter required is the ARXML file name corresponding to the CANIF module, that is, CanIfConfigurationValues.arxml, and obtains the middleware class name (CanIfConfiguration) from the file rule through the ARXML file name. If the CANIF instance already exists, obtain and return the instance from the instance pool according to the middleware class name (CanIfConfiguration); if the CANIF instance does not exist, create a CANIF instance using the middleware class name, store the newly created CANIF instance in the instance pool and return the instance.

[0054] The CANIF module creates a CANIF instance by calling the initialization function of the CANIF middleware module through the routing module; and calls the interface of the logging module during the initialization process of the CANIF middleware module to configure the format of log printing; among them, the initialization function of the ARXML file processing module is called during the initialization process of the CANIF middleware module to create an ARXML file processing instance. During the process of creating the instance, the lxml library parsing interface is used to obtain the CANIF parser instance (the parser instance contains all the information of the ARXML file), and at the same time, the JSON mirror module initialization interface is called to create a CANIF mirror instance.

[0055] The CANIF image instance calls the parsing interface of the JSON image module. The JSON image module's parsing interface uses the lxml library to retrieve all ARXML information from the CANIF parser instance. ARXML information is mainly composed of containers, which include component names, path identifiers, parameters, references, and sub-containers. Sub-containers repeatedly contain the above information, so a recursive approach can be used to parse all container component information. The parsed data is converted into a standard dictionary format and stored in the target instance's dedicated memory space. The business logic module calls the image module's save interface through the CANIF instance to save the above standard dictionary format to the JSON image file, improving the readability of the ARXML file.

[0056] The business logic module calls the CANIF instance's interface to extract the stored dictionary-formatted data and performs format conversion according to the preset template specifications, ultimately generating a template file that can be directly used by the business logic module. The template file strictly adheres to the component naming and hierarchical relationships specified in the AUTOSAR official documentation. Specifically, it predefines the names of each defined component and its corresponding parameters and references according to the AUTOSAR specification. For example, in `canif_txpducfgs_fields`, `CanIfTxPduCfgs` is the component name, `"canif_txpducfgs_enum_fields", "canif_txpducfgs_string_fields", "canif_txpducfgs_integer_fields", and "canif_txpducfgs_bool_fields" are the parameter classification sets under this component, and `"canif_txpducfgs_refer_fields"` is the reference set under this component. The values ​​in the list corresponding to the above keys are labels defined according to the AUTOSR specification. A dictionary-formatted JSON mirror data is obtained through a CANIF middleware instance. The JSON mirror data is iterated through, processing each component encountered. For each component, its name is retrieved, and initialization data is organized based on that name. During this process, predefined parameters and references are read based on the component name. Parameters are read by type and stored in different dictionaries, using the label as the key and a custom type {'value':None, 'operation':None} as the value. References are stored in the same type as parameters, but only in a single dictionary. After organizing the initialization data for the component, the parameters and references in the component are parsed, and the parsed data is stored in the custom type's value according to the label. After processing the parameters and references, the current component can be constructed according to the following format: textual, numerical, and reference formats can be found in [reference missing]. Figure 3 If this component contains child components, the parsing interface needs to be recursively called to further parse the child components. Finally, the constructed component is stored in a dictionary with the component name as the key and written to the template file. The component format is:

[0057] {

[0058] "TreeNodeName":tree_node_name,

[0059] "TEXTUAL":textual,

[0060] "NUMERICAL": numerical,

[0061] "REFERENCE":reference

[0062] }

[0063] S203, based on the configuration change information of the sub-component to be updated, determine the set field value of the operation type field under the target configuration field corresponding to the sub-component to be updated, and the target field value of the target configuration field.

[0064] The subcomponent to be updated can be a functional unit under the target functional component that has configuration adjustment requirements; the configuration change information can include the change type, change basis and related constraints of the subcomponent; the set field value can be the identifier value of the operation type field of the target configuration field, corresponding to the change action; the target configuration field can be the configuration field in the subcomponent to be updated that needs to perform parameter update, including parameter fields and reference fields and other attribute fields; the target field value can be the expected parameter value that the target configuration field needs to achieve after the change.

[0065] Optionally, for the configuration change information of the target functional component, the sub-components to be updated that need to be adjusted are selected from the information. Based on the functional attributes of the sub-components to be updated, all their corresponding configuration fields are matched to determine the target configuration field that needs to be changed. Then, based on the operation type in the configuration change information, the set field value of the operation type field under the target configuration field is determined. At the same time, based on the preset expected value of the parameter in the configuration change information, the target field value corresponding to the target configuration field is determined.

[0066] S204. Update the template file according to the operation corresponding to the set field value and the target field value to obtain the updated template file.

[0067] Optionally, the child component to be updated is located in the template file, and then the operation type field and target configuration field of the child component to be updated in the template file are updated according to the set field value of the operation type field under the target configuration field corresponding to the child component to be updated, and the target field value of the target configuration field, so as to obtain the updated template file. For example, if the field value of the operation type field of the child component to be updated in the model file is null, and the field value is set to add (add), then null is updated to add.

[0068] S205, Based on the updated template file, determine the target configuration file for the updated target functional component.

[0069] The target configuration file can be a standardized configuration document that adapts to configuration change requirements and can be directly loaded into the target functional component to enable it to perform the corresponding function.

[0070] Optionally, the operation type field and target configuration field in the updated template file are obtained. The configuration file is updated according to the field value of the operation type field, and the field value of the target configuration field is updated in the configuration file of the target functional component to obtain the updated target configuration file of the target functional component. For example, if the field value of the operation type field is modify and the field value of the target configuration field is 1, then the field value of the target configuration field in the configuration file is modified to 1 to complete the update of the configuration file.

[0071] In the above-described configuration file update method, the precise parsing of the target functional component configuration file and extraction of configuration information of each sub-component enables refined identification of the target functional component. Secondly, a template file containing configuration fields, field values ​​associated with the configuration fields, and operation type fields associated with the configuration fields is constructed, providing a standardized and structured unified carrier for configuration changes. Thirdly, based on the configuration change information of the sub-component to be updated, the operation type setting value and target field value of the target configuration field are determined in a targeted manner, achieving precise binding between incremental change requirements and configuration fields. Operations are only performed on the sub-components that need to be changed and their corresponding fields, reducing the cross-module compatibility risk caused by a full replacement of the configuration file. Finally, by updating the template file and generating the target configuration file accordingly, the efficiency of configuration file updates is improved, and the high-frequency iteration requirements of configuration files in the automotive electronics field can be met.

[0072] Based on the technical solutions of the above embodiments, this application also provides an optional embodiment. In this optional embodiment, the step of determining the target configuration file in S205 is further refined, including: updating the configuration information of the sub-component to be updated in the configuration file according to the updated template file to obtain the updated target configuration file of the target functional component, or mapping the updated template file to the configuration file to obtain the updated target configuration file of the target functional component.

[0073] Optionally, the original configuration file of the target functional component is retrieved first. Based on the operation instructions of the sub-component to be updated in the updated template file, the configuration information of the sub-component to be updated is located in the original configuration file. The field values ​​of the corresponding configuration fields are replaced with the target field values ​​already determined in the template file. The original configuration information of the unchanged sub-component is retained, and the incremental configuration of the original configuration file is completed to generate the target configuration file. Alternatively, the updated template file is structurally mapped and data converted according to the format requirements of the AUTOSAR configuration specification. The association relationship between the target functional component, sub-component, configuration field and field value in the template is converted into a configuration file hierarchical structure that conforms to the AUTOSAR standard. After data verification, a brand new target configuration file is directly generated. Therefore, this embodiment does not limit this method.

[0074] It's worth noting that the business logic module performs instruction matching based on the TITLE field and the operation field for each instruction in the parsed operation instruction set. Each TITLE field is mapped to a pre-defined set of interfaces (including add, delete, and modify interfaces) in the middleware module. The business logic module selects the corresponding target interface from this set of interfaces based on the value of the operation field (e.g., add for add, modify for modify, and delete for delete).

[0075] In one embodiment, updating the configuration file may further include: determining a set of operation instructions for the sub-component to be updated based on the updated template file; wherein the set of operation instructions is determined based on the set field values ​​of the sub-component to be updated; and updating the configuration information of the sub-component to be updated in the configuration file based on the set of operation instructions for the sub-component to be updated.

[0076] Optionally, the updated template file is parsed, that is, all configuration units (sub-components) whose operation field is not empty (such as not being None) are traversed to generate a set of operation instructions; then, based on the operation type (ADD / MODIFY / DELETE) and the associated component identifier in the instructions, the sub-component to be updated is precisely located in the original configuration file to update the configuration information of the sub-component to be updated in the configuration file.

[0077] It's worth noting that the business logic module reads template file data from a JSON library, iterates through the read template file data, matches it against the TITLE field, and performs special processing on the data under each TITLE. Once the TITLE is matched, the parent component needs to be provided according to the hierarchical relationship defined by AUTOSAR. The module iterates through the components under each TITLE, processing each component and reading its operation. If it's "add," the middleware module's interface for adding the component to the corresponding TITLE is called; if it's "delete," the middleware module's interface for deleting the component to the corresponding TITLE is called; if it's "None," the parameters and references under this component are processed. The processing of component parameters and references is mainly divided into three categories: TEXTUAL, NUMERICAL, and REFERENCE. For TEXTUAL and NUMERICAL, the corresponding middleware module interface is called based on whether the operation is "add," "delete," or "modify." REFERENCE only has "add" and "delete" operations.

[0078] In one embodiment, the method for adding a component may further include: if the set of operation instructions for the sub-component to be updated includes a new operation instruction, then the configuration information of the sub-component to be updated in the configuration file is updated according to the set of operation instructions; wherein the new operation instruction is determined based on the value of the setting field under the component name field in the target configuration field corresponding to the sub-component to be updated.

[0079] Optionally, it can be determined whether the set of operation instructions for the sub-component to be updated contains a new operation instruction for the component. If it exists, the setting value of the component name field in the target configuration field corresponding to the instruction is extracted. Then, the original configuration file of the target functional component is retrieved, the sub-component to be updated is accurately located in the configuration file, and a new configuration component conforming to the AUTOSAR specification is created based on the setting value of the component name field. At the same time, other attribute values ​​(such as parameters and references) corresponding to the target configuration field in the template file are synchronously written into the corresponding fields under the new component to achieve targeted addition and update of the configuration file.

[0080] In one embodiment, the method of adding a new component may further include: determining the component set to which the child component to be updated belongs based on the addition operation instruction, and determining the parent component and reference path of the child component to be updated based on the component set; determining the addition position of the child component to be updated based on the parent component and reference path; and adding the configuration information of the child component to be updated to the addition position in the configuration file based on the operation instruction set.

[0081] The parent component can be a higher-level functional unit that directly contains the child component to be updated in the AUTOSAR configuration hierarchy; the reference path can be a standardized component hierarchy association path from the parent component to the child component to be updated in the AUTOSAR configuration file; and the addition location can be a component hierarchy location in the configuration file that is determined based on the parent component and the reference path and is used to store the configuration information of the child component to be updated.

[0082] Optionally, based on the addition operation instructions of the component, determine the component set to which the child component to be updated belongs (e.g., based on the TITLE field), then identify the parent component and reference path corresponding to the child component to be updated from the component set, determine the location to add the configuration information of the child component to be updated in the configuration file through the hierarchical identifier of the parent component and the component association relationship of the reference path, and finally write the configuration information of the child component to be updated at the addition location according to the addition requirements in the operation instruction set to complete the addition and update of the configuration file.

[0083] It's worth noting that when performing the `add` operation on a component, the configuration information passed from the business logic module is obtained through function parameters. This configuration information is organized in dictionary form. Since each component class interface corresponds to a unique and definite `TITLE`, the parent component and the paths corresponding to its reference parameters are known information. The `REFERENCE` field of the configuration information is then extracted to retrieve the referenced `label` and `value` values, and a preset path is added based on the `label` value and `value` value. After completing the data organization, the `add_container` interface of the ARXML file processing module is called, passing in the component information, parent component, and `TITLE` as parameters. The ARXML file processing module then parses the passed parameters to obtain the name of the target component and checks whether the component corresponding to that name already exists. If the component already exists, return it directly; if the component does not exist, create and initialize its framework information; parse the TEXTUAL type parameter information in the input parameters, call the add_ecuc_textual_param_value interface, and write the information into the TEXTUAL field of the component framework; parse the NUMERICAL type parameter information in the input parameters, call the add_ecuc_numerical_param_value interface, and write the information into the NUMERICAL field of the component framework; parse the REFERENCE type information in the input parameters, call the add_ecuc_textual_param_value interface, and write the information into the REFERENCE field of the component framework, thus completing the component addition.

[0084] In one embodiment, deleting a component may further include: deleting the configuration information of the sub-component to be updated in the configuration file if the set of operation instructions for the sub-component to be updated includes a deletion operation instruction; wherein the deletion operation instruction is determined based on the setting field value under the component name field in the target configuration field corresponding to the sub-component to be updated.

[0085] Optionally, the component name field includes an operation type field. If the value of the operation type field is set to delete, it is a delete operation instruction, which will then execute the component's delete operation and delete the configuration information of the child component to be updated.

[0086] It is worth noting that when performing the delete operation on a component, the parent component and the component to be deleted are obtained from the business logic module through function parameters. The delete_container interface of the ARXML file processing module is then directly called, with the aforementioned parent component and the component to be deleted passed as parameters. This allows the ARXML file processing module to locate the parent component corresponding to the component to be deleted based on the getparent interface in the lxml library. Finally, the remove interface of the lxml utility library is called to remove the component to be deleted based on the parent component hierarchy, thus completing the component deletion.

[0087] In one embodiment, updating the configuration information of a component may further include: if the set of operation instructions for the child component to be updated includes configuration operation instructions, determining the first configuration field corresponding to the configuration operation instruction from the target configuration field according to the configuration operation instruction; wherein the configuration operation instruction is determined based on the set field values ​​of other fields in the target configuration field corresponding to the child component to be updated, excluding the component name field; determining the component set to which the child component to be updated belongs, and determining the parent component and reference path of the child component to be updated according to the component set; determining the update position corresponding to the first configuration field according to the parent component and reference path; and updating the configuration information recorded at the update position to the target field value of the first configuration field.

[0088] The configuration operation instruction can be an instruction used to update parameters of existing configuration fields. The first configuration field includes, but is not limited to, the TEXTUAL field, NUMERICAL field, and REFERENCE field.

[0089] Optionally, it is determined whether the set of operation instructions for the child component to be updated contains configuration operation instructions. If so, the corresponding first configuration field is selected from the target configuration fields according to the instruction. The component set to which the child component to be updated belongs is determined, and its corresponding parent component and reference path are determined from the set. The update position of the first configuration field in the configuration file is determined by the hierarchical identifier of the parent component and the component association relationship of the reference path. Finally, the original configuration information at the update position is updated to the target field value of the first configuration field to complete the targeted parameter update of the configuration file.

[0090] It's worth noting that when performing the parameter addition operation, the middleware module receives parameters passed from the business logic module via function parameters. These parameters include parameter type (such as text and data parameters), parent component name, name of the child component to be updated, LABEL field, and value field. Then, it calls the component location interface of the ARXML file processing module, passing the parent component name and the component name as input parameters to retrieve the element component corresponding to the component name. Finally, it calls the parameter addition interface of the ARXML file processing module, passing the parameter type, element component, LABEL field, value field, parent component name, and component name as input parameters to complete the parameter addition. This allows the ARXML file processing module to use the passed-in component name as the parameter and apply the appropriate method. The `xml` library locates the position of the target component (e.g., the `xpath` method in the `lxml` library); similarly, the `xpath` method in the `lxml` library checks whether the textual data to be added already exists in the target component; if the textual data to be added does not exist, the corresponding data structure is created using the `lxml` library (e.g., the `etree.SubElement` method in the `lxml` library), and the textual data and its value are added to the target component to complete the parameter addition; for `delete_textual_param` and `modify_textual_param`, the component position is obtained based on the input parameter, and then the existence of the data is checked. If it exists, the corresponding deletion and modification are performed.

[0091] Optionally, when performing the parameter deletion operation, the middleware module receives the parameters passed by the business logic module through function parameters, including the parent component name, component name, and LABEL field; then calls the component location interface of the ARXML file processing module, passing the parent component name and component name as input parameters to obtain the element component corresponding to the component name; and then calls the parameter deletion interface of the ARXML file processing module, passing the element component and LABEL field as input parameters to complete the parameter deletion.

[0092] For example, when performing a parameter modification operation, the middleware module receives parameters passed by the business logic module through function parameters. The parameters include the parent component name, the component name, the LABEL field, and the new field value (new_value). The middleware module calls the component location interface of the ARXML file processing module, passing the parent component name and the component name as input parameters to obtain the element component corresponding to the component name. The middleware module then calls the parameter modification interface of the ARXML file processing module, passing the element component, the LABEL field, and the new_value as input parameters to complete the parameter modification.

[0093] The middleware module calls the `add_ecuc_numerical_param_value`, `delete_ecuc_numerical_param_value`, and `modify_ecuc_numerical_param_value` functions in the ARXML file processing module to handle TextUAL type parameters. The processing flow for these types of interfaces is basically the same as that for TextUAL type parameters, so it will not be elaborated further.

[0094] It's worth noting that when performing a component addition operation, the middleware module receives parameters passed by the business logic module through function parameters. These parameters include the parent component name, the component name, the LABEL field, and the referenced component name corresponding to that LABEL field. It then calls the component location interface of the ARXML file processing module, passing the parent component name and the component name as input parameters to obtain the element component corresponding to that component name. Based on the LABEL field, it retrieves the preset referenced component path and combines this preset path with the referenced component name to form the complete reference path. Finally, it calls the add reference interface of the ARXML file processing module, passing the element component, the LABEL field, the complete reference path, the parent component name, and the component name as input parameters to complete the reference addition. When performing a reference deletion operation, the middleware module receives parameters passed by the business logic module through function parameters. The parameters include the parent component name, component name, LABEL field, and the referenced component name corresponding to the LABEL field. The component location interface of the ARXML file processing module is called, passing the parent component name and component name as input parameters to obtain the element component corresponding to the component name. A preset referenced component path is obtained based on the LABEL field, and this preset path is combined with the referenced component name to form a complete reference path. The reference deletion interface of the ARXML file processing module is called, passing the element component, LABEL field, and complete reference path as input parameters to complete the reference deletion. The middleware module calls the add_ecuc_reference_value / delete_ecuc_reference_value interfaces in the ARXML file processing module to handle REFERENCE type parameters. The processing flow for these two types of parameter interfaces is the same, therefore, it will not be described further.

[0095] It's worth noting that, using CANIF as an example to illustrate JSON mirror file synchronization, during the template file generation step, the JSON mirror module's parsing interface uses the lxml library to obtain all ARXML information from the CANIF parser instance. When adding or deleting components, the middleware module simultaneously calls the JSON mirror module's `sync_container_object` interface. For adding a component, this interface constructs a component dictionary based on the input parameters, recursively finds the parent component's location based on its name, and determines whether it's a child container based on the input parameters. If it is, it's added to `sub_containers`; otherwise, it's added to `containers`. For deleting a component, the same process occurs: finding the parent component's location based on its name, then locating the component to be deleted within the parent component based on its name, and finally deleting it. When adding, deleting, or modifying parameter information, the middleware module simultaneously calls the JSON mirror module's `sync_container_textual_param`, `sync_container_numerical_param`, and `sync_container_reference` interfaces. For adding, it constructs a parameter dictionary based on the input parameters, locates the component's position based on its parent component name, and adds the parameter information to the component. The same applies to deletion and modification operations; the JSON mirroring module provides a file output interface, supporting the saving of complete ARXML file information as a JSON file. This function effectively solves the problem of poor readability of ARXML files, generating highly readable JSON files through format conversion, thus improving the convenience of information retrieval.

[0096] For example, the configuration file update process is as follows: Figure 5 As shown, the process starts with input configuration files and template files, which are then passed to the business logic module. Within the business logic module, the input template file is parsed, and the corresponding operation instructions are determined. Based on the matched instructions, the corresponding interface operations (including adding, modifying, and deleting interfaces) are executed. After the interface operations are completed, the process is transferred through the middleware module. The ARXML file is modified to update it, and then the JSON mirror file is updated synchronously to update the JSON file, thus completing the entire process.

[0097] In this embodiment, the updated target configuration file of the target functional component is obtained by updating the configuration information of the sub-component to be updated in the configuration file according to the updated template file; or, the updated template file is mapped to the configuration file to obtain the updated target configuration file of the target functional component. This can meet the needs of the communication diagnostic module to be frequently modified during version iteration in the incremental configuration scenario, and reduce the operational complexity of updating the configuration file.

[0098] To more comprehensively demonstrate this solution, this embodiment provides an optional method for updating configuration files, such as... Figure 6 As shown:

[0099] 1. Generate a template file based on the input ARXML file to be modified;

[0100] 2. Modify the template file according to your requirements;

[0101] If the requirements change only slightly, the template file can be modified manually. If the requirements change significantly, an automated script can be used to process the template file directly. This dual-mode configuration, which supports both automation and manual processing, provides greater convenience.

[0102] Alternatively, the requirement input can be determined based on the target version of the DBC file and the baseline version of the DBC file. By comparing the target version of the DBC file and the baseline version of the DBC file, the magnitude of the requirement change can be determined.

[0103] 3. Modify the ARXML file based on the updated template file;

[0104] 4. Import the modified ARXML file into the AUTOSAR configuration tools;

[0105] 5. Run the AUTOSAR-related configuration tool code generation function;

[0106] 6. Integrate and compile the communication module and the entire software project, and write it into the vehicle electronic control unit for testing and verification.

[0107] The specific process of the above steps can be found in the description of the above method embodiments. The implementation principle and technical effect are similar, and will not be repeated here.

[0108] To more comprehensively demonstrate this solution, this embodiment provides an optional method for updating configuration files, including:

[0109] 1) Parse the configuration file of the target functional component of the vehicle to obtain the configuration information of each sub-component of the target functional component;

[0110] 2) Based on the configuration information, construct the template file for the target functional component; the template file includes the correspondence between the configuration fields and field values ​​for each sub-component, and each configuration field includes the field value and operation type field;

[0111] 3) Based on the configuration change information of the sub-component to be updated, determine the set field value of the operation type field under the target configuration field of the sub-component to be updated, as well as the target field value of the target configuration field;

[0112] 4) Update the template file according to the operation corresponding to the set field value and the target field value to obtain the updated template file;

[0113] 5) Based on the updated template file, determine the set of operation instructions for the child components to be updated; wherein, the set of operation instructions is determined based on the set field values ​​of the child components to be updated;

[0114] 6) If the set of operation instructions for the child component to be updated includes a new operation instruction, update the configuration information of the child component to be updated in the configuration file according to the set of operation instructions; wherein, the new operation instruction is determined based on the value of the setting field under the component name field in the target configuration field corresponding to the child component to be updated; or,

[0115] 7) Map the updated template file to a configuration file to obtain the target configuration file for the updated target functional component.

[0116] The specific process of the above steps can be found in the description of the above method embodiments, and their implementation principles and technical effects are similar, so they will not be repeated here. It should be understood that although the steps in the flowcharts of the above embodiments are shown sequentially according to the arrows, these steps are not necessarily executed in the order indicated by the arrows. Unless explicitly stated herein, there is no strict order restriction on the execution of these steps, and they can be executed in other orders. Moreover, at least some steps in the flowcharts of the above embodiments may include multiple steps or multiple stages. These steps or stages are not necessarily completed at the same time, but can be executed at different times. The execution order of these steps or stages is not necessarily sequential, but can be performed alternately or in turn with other steps or at least a portion of the steps or stages in other steps. It is understood that the steps in different embodiments can be freely combined as needed, and all non-contradictory solutions formed by such combinations fall within the scope of protection of this application.

[0117] Based on the same inventive concept, this application also provides a configuration file updating apparatus for implementing the configuration file updating method described above. The solution provided by this apparatus is similar to the implementation described in the above method; therefore, the specific limitations in one or more configuration file updating apparatus embodiments provided below can be found in the limitations of the configuration file updating method described above, and will not be repeated here.

[0118] In one exemplary embodiment, such as Figure 7 As shown, a configuration file update device is provided, including: a parsing module 71, a building module 72, a processing module 73, and an update module 74, wherein:

[0119] The parsing module 71 is used to parse the configuration file of the target functional component of the vehicle to obtain the configuration information of each sub-component of the target functional component;

[0120] Module 72 is used to build template files for target functional components based on various configuration information; wherein, the template file includes the correspondence between configuration fields and field values ​​for each sub-component, and each configuration field includes the field value and operation type field of the configuration field;

[0121] The processing module 73 is used to determine the set field value of the operation type field under the target configuration field of the sub-component to be updated, and the target field value of the target configuration field, based on the configuration change information of the sub-component to be updated.

[0122] Processing module 73 is also used to update the template file according to the operation and target field value corresponding to the set field value, so as to obtain the updated template file;

[0123] Update module 74 is used to determine the target configuration file of the updated target functional component based on the updated template file.

[0124] In one embodiment, the update module 74 is further configured to:

[0125] Based on the updated template file, update the configuration information of the sub-components to be updated in the configuration file to obtain the updated target configuration file of the target functional component; or, map the updated template file to the configuration file to obtain the updated target configuration file of the target functional component.

[0126] In one embodiment, the update module 74 is further configured to:

[0127] Based on the updated template file, determine the set of operation instructions for the child components to be updated; the set of operation instructions is determined based on the set field values ​​of the child components to be updated; based on the set of operation instructions for the child components to be updated, update the configuration information of the child components to be updated in the configuration file.

[0128] In one embodiment, the update module 74 is further configured to:

[0129] If the set of operation instructions for the child component to be updated includes new operation instructions, the configuration information of the child component to be updated in the configuration file is updated according to the set of operation instructions; wherein, the new operation instruction is determined based on the value of the setting field under the node name field in the target configuration field corresponding to the child component to be updated.

[0130] In one embodiment, the update module 74 is further configured to:

[0131] Based on the new operation instructions, determine the component set to which the child component to be updated belongs, and based on the component set, determine the parent component and reference path of the child component to be updated; based on the parent component and reference path, determine the addition location of the child component to be updated; based on the operation instruction set, add the configuration information of the child component to be updated to the addition location in the configuration file.

[0132] In one embodiment, the update module 74 is further configured to:

[0133] If the set of operation instructions for the child component to be updated includes a delete operation instruction, delete the configuration information of the child component to be updated in the configuration file; wherein, the delete operation instruction is determined based on the value of the setting field under the node name field in the target configuration field corresponding to the child component to be updated.

[0134] In one embodiment, the update module 74 is further configured to:

[0135] If the set of operation instructions for the child component to be updated includes configuration operation instructions, then, based on the configuration operation instructions, the first configuration field corresponding to the configuration operation instructions is determined from the target configuration fields. The configuration operation instructions are determined based on the set field values ​​of all fields in the target configuration fields corresponding to the child component to be updated, excluding the node name field. The component set to which the child component to be updated belongs is determined, and based on the component set, the parent component and reference path of the child component to be updated are determined. Based on the parent component and reference path, the update position corresponding to the first configuration field is determined. The configuration information recorded at the update position is updated to the target field value of the first configuration field.

[0136] The modules in the aforementioned configuration file update device can be implemented entirely or partially through software, hardware, or a combination thereof. These modules can be embedded in or independent of the processor in a computer device, or stored in the memory of a computer device in software form, so that the processor can call and execute the operations corresponding to each module.

[0137] In one exemplary embodiment, a computer device is provided, which may be a terminal, and its internal structure diagram may be as follows: Figure 8As shown, the computer device includes a processor, memory, input / output interfaces, a communication interface, a display unit, and an input device. The processor, memory, and input / output interfaces are connected via a system bus, and the communication interface, display unit, and input device are also connected to the system bus via the input / output interfaces. The processor provides computing and control capabilities. The memory includes non-volatile storage media and internal memory. The non-volatile storage media stores the operating system and computer programs. The internal memory provides an environment for the operation of the operating system and computer programs stored in the non-volatile storage media. The input / output interfaces are used for exchanging information between the processor and external devices. The communication interface is used for wired or wireless communication with external terminals; wireless communication can be achieved through Wi-Fi, mobile cellular networks, Near Field Communication (NFC), or other technologies. When the computer program is executed by the processor, it implements a configuration file update method. The display unit is used to form a visually visible image and can be a display screen, a projection device, or a virtual reality imaging device. The display screen can be an LCD screen or an e-ink screen. The input device of the computer device can be a touch layer covering the display screen, or buttons, trackballs, or touchpads set on the casing of the computer device, or external keyboards, touchpads, or mice, etc.

[0138] Those skilled in the art will understand that Figure 8 The structure shown is merely a block diagram of a portion of the structure related to the present application and does not constitute a limitation on the computer device to which the present application is applied. Specific computer devices may include more or fewer components than those shown in the figure, or combine certain components, or have different component arrangements.

[0139] In one embodiment, a computer device is also provided, including a memory and a processor, wherein the memory stores a computer program, and the processor executes the computer program to implement the steps in the above method embodiments.

[0140] In one embodiment, a computer-readable storage medium is provided having a computer program stored thereon that, when executed by a processor, implements the steps in the above method embodiments.

[0141] In one embodiment, a computer program product is provided, including a computer program that, when executed by a processor, implements the steps in the above method embodiments.

[0142] Those skilled in the art will understand that all or part of the processes in the above embodiments can be implemented by a computer program instructing related hardware. The computer program can be stored in a non-volatile computer-readable storage medium, and when executed, it can include the processes of the embodiments of the above methods. Any references to memory, databases, or other media used in the embodiments provided in this application can include at least one of non-volatile memory and volatile memory. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical memory, high-density embedded non-volatile memory, resistive random access memory (ReRAM), magnetic random access memory (MRAM), ferroelectric random access memory (FRAM), phase change memory (PCM), graphene memory, etc. Volatile memory can include random access memory (RAM) or external cache memory, etc. By way of illustration and not limitation, RAM can take many forms, such as Static Random Access Memory (SRAM) or Dynamic Random Access Memory (DRAM). The databases involved in the embodiments provided in this application may include at least one type of relational database and non-relational database. Non-relational databases may include, but are not limited to, blockchain-based distributed databases. The processors involved in the embodiments provided in this application may be general-purpose processors, central processing units, graphics processing units, digital signal processors, programmable logic devices, quantum computing-based data processing logic devices, artificial intelligence (AI) processors, etc., and are not limited to these.

[0143] The technical features of the above embodiments can be combined in any way. For the sake of brevity, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this application.

[0144] The embodiments described above are merely illustrative of several implementation methods of this application, and while the descriptions are specific and detailed, they should not be construed as limiting the scope of this patent application. It should be noted that those skilled in the art can make various modifications and improvements without departing from the concept of this application, and these all fall within the protection scope of this application. Therefore, the protection scope of this application should be determined by the appended claims.

Claims

1. A configuration file update method, characterized in that, The method includes: The configuration file of the target functional component of the vehicle is parsed to obtain the configuration information of each sub-component of the target functional component; Based on the configuration information, a template file for the target functional component is constructed; wherein, the template file includes the correspondence between the configuration fields and field values ​​for each sub-component, and each configuration field includes the field value and operation type field of the configuration field; Based on the configuration change information of the sub-component to be updated, determine the set field value of the operation type field under the target configuration field corresponding to the sub-component to be updated, and the target field value of the target configuration field; The template file is updated based on the operation corresponding to the set field value and the target field value to obtain the updated template file; Based on the updated template file, determine the updated target configuration file for the target functional component.

2. The method according to claim 1, characterized in that, Based on the updated template file, determine the updated target configuration file for the target functional component, including: Based on the updated template file, update the configuration information of the sub-component to be updated in the configuration file to obtain the updated target configuration file of the target functional component; or, The updated template file is mapped to a configuration file to obtain the updated target configuration file for the target functional component.

3. The method according to claim 2, characterized in that, Based on the updated template file, update the configuration information of the sub-component to be updated in the configuration file, including: Based on the updated template file, a set of operation instructions for the sub-component to be updated is determined; wherein the set of operation instructions is determined based on the set field values ​​of the sub-component to be updated. Update the configuration information of the subcomponent to be updated in the configuration file according to the set of operation instructions of the subcomponent to be updated.

4. The method according to claim 3, characterized in that, Based on the set of operation instructions for the sub-component to be updated, update the configuration information of the sub-component to be updated in the configuration file, including: If the set of operation instructions for the sub-component to be updated includes new operation instructions, the configuration information of the sub-component to be updated in the configuration file shall be updated according to the set of operation instructions. The newly added operation instruction is determined based on the value of the setting field under the component name field in the target configuration field corresponding to the sub-component to be updated.

5. The method according to claim 4, characterized in that, According to the set of operation instructions, the configuration information of the sub-component to be updated in the configuration file is updated, including: Based on the newly added operation instruction, determine the component set to which the child component to be updated belongs, and based on the component set, determine the parent component and reference path of the child component to be updated; Based on the parent component and the reference path, determine the addition location of the child component to be updated; According to the set of operation instructions, the configuration information of the sub-component to be updated is added at the add location in the configuration file.

6. The method according to claim 3, characterized in that, Based on the set of operation instructions for the sub-component to be updated, update the configuration information of the sub-component to be updated in the configuration file, including: If the set of operation instructions for the sub-component to be updated includes a delete operation instruction, the configuration information of the sub-component to be updated in the configuration file is deleted; wherein, the delete operation instruction is determined based on the value of the setting field under the component name field in the target configuration field corresponding to the sub-component to be updated.

7. The method according to claim 3, characterized in that, Based on the set of operation instructions for the sub-component to be updated, update the configuration information of the sub-component to be updated in the configuration file, including: If the set of operation instructions for the sub-component to be updated includes a configuration operation instruction, the first configuration field corresponding to the configuration operation instruction is determined from the target configuration field according to the configuration operation instruction; wherein, the configuration operation instruction is determined based on the set field value under the fields other than the component name field in the target configuration field corresponding to the sub-component to be updated; Determine the component set to which the child component to be updated belongs, and determine the parent component and reference path of the child component to be updated based on the component set; Based on the parent component and the reference path, determine the update position corresponding to the first configuration field; Update the configuration information recorded at the update location to the target field value of the first configuration field.

8. A configuration file update device, characterized in that, The device includes: The parsing module is used to parse the configuration file of the target functional component of the vehicle to obtain the configuration information of each sub-component of the target functional component; The building module is used to build a template file for the target functional component based on the configuration information; wherein, the template file includes the correspondence between the configuration fields and field values ​​for each sub-component, and each configuration field includes the field value and operation type field of the configuration field; The processing module is used to determine the set field value of the operation type field under the target configuration field corresponding to the sub-component to be updated, and the target field value of the target configuration field, based on the configuration change information of the sub-component to be updated. The processing module is further configured to update the template file according to the operation corresponding to the set field value and the target field value, so as to obtain the updated template file; The update module is used to determine the target configuration file of the updated target functional component based on the updated template file.

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

10. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by a processor, it implements the steps of the method according to any one of claims 1 to 7.

Images