Configuration management method and device, storage medium, management end and equipment end

Abstract

The invention discloses a configuration management method and device, a storage medium, a management end and an equipment end, and relates to the technical field of operating systems, and the management end can customize source configuration files corresponding to all system function modules under one management level or multiple management levels for all the system function modules on the system side; respectively carrying out merging and serialization processing on the source configuration files included in each management hierarchy to obtain merging and serialization configuration files in each management hierarchy; and packaging the combined serialized configuration file under each management level into a system version of an equipment end. The risk of configuration errors can be effectively reduced, and the configuration management and maintenance efficiency can be improved.

Description

Technical Field

[0001] This application relates to the field of operating system technology, specifically to a configuration management method, apparatus, storage medium, management terminal, and device terminal. Background Technology

[0002] The system side contains various system function modules, which are customized system feature modules based on requirements. Examples include process freeze control modules, health information monitoring modules, and memory management modules. Currently, the configuration behavior control of various system function modules on the system side is usually handled uniformly through a dynamic configuration mechanism, that is, using a single configuration file to centrally manage the configuration of all system function modules.

[0003] Using a single configuration file for management leads to interdependence and coupling between the configurations of multiple system functional modules. This interdependence means that a configuration error in a single system functional module may cause overall control failure, resulting in a high risk of configuration errors. Furthermore, the coupling of configurations increases the complexity of function switching and parameter configuration, reducing management and maintenance efficiency.

[0004] Therefore, the current configuration management method has the problems of high risk of configuration errors and low efficiency in configuration management and maintenance. Summary of the Invention

[0005] This application provides a solution that can effectively reduce the risk of configuration errors in system function modules on the system side and improve configuration management and maintenance efficiency.

[0006] The embodiments of this application provide the following technical solutions:

[0007] According to one embodiment of this application, a configuration management method is applied to a management terminal, comprising: for each system functional module on the system side, customizing source configuration files corresponding to each system functional module under one or more management levels; merging and serializing the source configuration files included under each management level to obtain merged and serialized configuration files under each management level; and packaging the merged and serialized configuration files under each management level into the system version on the device side.

[0008] In some embodiments of this application, before merging and serializing the source configuration files included under each management level, the method further includes: obtaining the configuration specification protocol corresponding to each system functional module; verifying the source configuration files corresponding to each system functional module according to the configuration specification protocol corresponding to each system functional module; and determining whether to merge and serialize the source configuration files included under each management level according to the verification result of the source configuration files under each management level.

[0009] In some embodiments of this application, the step of verifying the source configuration file corresponding to each system functional module according to the configuration specification protocol corresponding to each system functional module includes: coded the configuration specification protocol corresponding to each system functional module to obtain the configuration verification logic corresponding to each system functional module; and verifying the source configuration file corresponding to each system functional module based on the configuration verification logic corresponding to each system functional module.

[0010] In some embodiments of this application, the step of merging and serializing the source configuration files included under each management level to obtain merged serialized configuration files under each management level includes: parsing the source configuration files included under each management level to obtain source configuration content included under each management level; merging and filling the source configuration content included under each management level into a serialized message structure to obtain configuration messages under each management level; and serializing the configuration messages under each management level to obtain merged serialized configuration files under each management level.

[0011] In some embodiments of this application, the source configuration files corresponding to each system functional module include general source configuration files; some or all of the source configuration files corresponding to the system functional modules also include at least one customized source configuration file; the step of customizing the source configuration files corresponding to each system functional module under one or more management levels for each system functional module on the system side includes: at the lowest priority management level, saving the general source configuration files of all the system functional modules on the system side; at non-lowest priority management levels, customizing at least one customized source configuration file corresponding to each system functional module under the corresponding management level.

[0012] In some embodiments of this application, the step of serializing the configuration messages under each management level to obtain the merged serialized configuration file under each management level includes: serializing the configuration messages under each management level in binary form to obtain the merged serialized binary configuration file under each management level.

[0013] According to one embodiment of this application, a configuration management method is applied to a device. The method includes: receiving merged serialized configuration files under different management levels issued by a management terminal, wherein the merged serialized configuration files under each management level are obtained by the management terminal by merging and serializing the source configuration files included under each management level; the management terminal customizes the source configuration files corresponding to each system function module under one or more management levels for each system function module on the system side; and saving the received merged serialized configuration files in a configuration customization resource partition according to the corresponding management level.

[0014] In some embodiments of this application, after the received merged serialized configuration file is saved in the configuration-customized resource partition according to the corresponding management level, the method further includes: assembling the configuration directory according to the basic attribute dimension of the device to obtain the resource configuration directory corresponding to each management level; loading and parsing the configuration file from the configuration-customized resource partition according to the resource configuration directory corresponding to each management level to obtain the module configuration parameters corresponding to each system function module.

[0015] In some embodiments of this application, the step of loading and parsing configuration files from the configuration-customized resource partition according to the resource configuration directory corresponding to each management level to obtain the module configuration parameters corresponding to each system functional module includes: loading the merged serialized configuration files under each management level from the configuration-customized resource partition according to the resource configuration directory corresponding to each management level; deserializing the merged serialized configuration files under each management level in order of priority from low to high to obtain the source configuration files under each management level; and overwriting the source configuration files under the low priority management level with the source configuration files under the high priority management level to obtain the module configuration parameters corresponding to each system functional module.

[0016] According to one embodiment of this application, a configuration management device is applied to a management terminal. The device includes: a customization module, configured to: customize source configuration files corresponding to each system functional module under one or more management levels for each system functional module on the system side; a processing module, configured to: perform merge serialization processing on the source configuration files included under each management level to obtain merge serialized configuration files under each management level; and a packaging module, configured to: package the merge serialized configuration files under each management level into the system version on the device side.

[0017] According to one embodiment of this application, a configuration management device is applied to a device. The device includes: a receiving module, configured to: receive merged serialized configuration files under different management levels issued by a management terminal, wherein the merged serialized configuration files under each management level are obtained by the management terminal by merging and serializing the source configuration files included under each management level, and the management terminal customizes the source configuration files corresponding to each system function module under one or more management levels for each system function module on the system side; and a storage module, configured to: save the received merged serialized configuration files in a configuration customization resource partition according to the corresponding management level.

[0018] According to another embodiment of this application, a storage medium stores a computer program thereon, which, when executed by a processor of a management terminal, causes the management terminal to perform the method executed by the management terminal as described in any embodiment of this application; or, when executed by a processor of a device terminal, causes the device terminal to perform the method executed by the device terminal as described in any embodiment of this application.

[0019] According to another embodiment of this application, a management terminal includes: a memory storing a computer program; and a processor reading the computer program stored in the memory to execute the method executed by the management terminal according to any embodiment of this application.

[0020] According to another embodiment of this application, a device includes: a memory storing a computer program; and a processor reading the computer program stored in the memory to execute the method executed by the device according to any embodiment of this application.

[0021] According to another embodiment of this application, a computer program product or computer program includes computer instructions stored in a computer-readable storage medium. A processor at a management end or device end reads the computer instructions from the computer-readable storage medium and executes the computer instructions, causing the management end or device end to perform the methods provided in the various optional implementations described in the embodiments of this application.

[0022] In this embodiment, the management end can: customize the source configuration files corresponding to each system function module under one or more management levels for each system function module on the system side; perform merge serialization processing on the source configuration files included under each management level to obtain merge serialization configuration files under each management level; and package the merge serialization configuration files under each management level into the system version on the device side.

[0023] In this embodiment of the application, independent source configuration files are configured for each system functional module. Furthermore, source configuration files corresponding to each system functional module are customized under one or more management levels. Layered merging and serialization processes are then performed to obtain merged serialized configuration files for each management level. This allows for reliable decoupling and control of the independent source configuration files for each system functional module at a layered level, reliably preventing overall control failure caused by configuration errors in a single function. The configuration parameters of each module can be efficiently managed and maintained at a layered level. This effectively reduces the risk of configuration errors in system functional modules on the system side and improves configuration management and maintenance efficiency. Attached Figure Description

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

[0025] Figure 1 A flowchart of a configuration management method according to an embodiment of this application is shown.

[0026] Figure 2 A configuration management interaction flowchart according to an embodiment of this application is shown.

[0027] Figure 3 A flowchart of a configuration verification process according to an embodiment of this application is shown.

[0028] Figure 4 A flowchart of a configuration management method according to another embodiment of this application is shown.

[0029] Figure 5 A flowchart illustrating the configuration parsing process according to another embodiment of this application is shown.

[0030] Figure 6 A block diagram of a configuration management apparatus according to an embodiment of this application is shown.

[0031] Figure 7 A block diagram of a configuration management apparatus according to another embodiment of this application is shown.

[0032] Figure 8 A block diagram of a management terminal according to one embodiment of this application is shown.

[0033] Figure 9 A block diagram of a device side according to an embodiment of this application is shown. Detailed Implementation

[0034] The present disclosure will be further described in detail below with reference to the accompanying drawings and embodiments. It should be understood that the embodiments provided herein are merely illustrative of the present disclosure and are not intended to limit the present disclosure. Furthermore, the embodiments provided below are some embodiments for implementing the present disclosure, and not all embodiments for implementing the present disclosure. Unless otherwise specified, the technical solutions described in the embodiments of the present disclosure can be implemented in any combination.

[0035] It should be noted that, in the embodiments of this disclosure, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a method or apparatus that includes a list of elements includes not only the elements expressly described, but also other elements not expressly listed, or elements inherent to implementing the method or apparatus. Without further limitations, an element defined by the phrase "comprising a..." does not exclude the presence of other related elements (e.g., steps in the method or units in the apparatus, such as portions of circuitry, processors, programs, or software, etc.) in the method or apparatus that includes that element.

[0036] For example, the configuration management method provided in this disclosure includes a series of steps, but the configuration management method provided in this disclosure is not limited to the steps described. Similarly, the configuration management device provided in this disclosure includes a series of units, but the device provided in this disclosure is not limited to the units explicitly described, but may also include units that need to be set up for obtaining relevant information or processing based on information.

[0037] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure belongs. The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of this disclosure.

[0038] It is understood that in the specific implementation of this application, relevant data is involved. When the embodiments in this application are applied to specific products or technologies, user permission or consent is required, and the collection, use and processing of relevant data must comply with the relevant laws, regulations and standards of the relevant countries and regions.

[0039] Figure 1 A flowchart illustrating a configuration management method according to an embodiment of this application is shown schematically. Figure 1 The execution entity of the configuration management method shown is the management end, which can be a terminal and / or a server. The terminal is such as a computer, etc., and the server is such as a cloud server or a physical server.

[0040] like Figure 1As shown, the configuration management method executed by the management terminal may include steps S110 to S130.

[0041] Step S110: For each system functional module on the system side, customize the source configuration file corresponding to each system functional module under one or more management levels;

[0042] Step S120: Merge and serialize the source configuration files included in each management level to obtain merged and serialized configuration files under each management level.

[0043] Step S130: Package the merged serialization configuration files under each management level into the system version on the device.

[0044] For example, see Figure 2 During the compilation phase, the management end can merge and serialize the source configuration files included in each management level through step S210 to obtain the merged serialized configuration files of each management level; then, through step S220, the merged serialized configuration files of each management level are packaged into the configuration customization resource partition (e.g., TVcust partition) in the system version of the device.

[0045] Among them, the system function modules on the system side are the system-customized function (Feature) modules customized on the system side according to the requirements. For example, there is a process freezing and control module for freezing and controlling processes, a health information monitoring module for monitoring the health of devices, and a memory management module for managing memory, etc.

[0046] In this embodiment, each system functional module is configured with an independent source configuration file. The source configuration file contains module configuration parameters for the system functional modules defined according to actual needs. Furthermore, for each system functional module on the system side, the source configuration file corresponding to each system functional module is customized under one or more management levels. This customization can be implemented by the user associating the source configuration files corresponding to each system functional module under the corresponding management level through association operations on the management side according to actual needs, or by the customization service in the management side associating the source configuration files corresponding to each system functional module under the corresponding management level according to a user-defined strategy.

[0047] The total number and types of management levels can be customized according to actual needs. Furthermore, the number of source configuration files, their source (i.e., the system functional module to which the source configuration file belongs), and the module configuration parameters within the source configuration files under each management level can also be customized based on actual requirements. For example, ... Figure 3As shown, the total number of levels is n, and there are n management levels from management level 1 to management level n. The number of n can be set according to actual needs. Each management level corresponds to a level type. The number of source configuration files, the source (i.e. the system functional module to which the source configuration file belongs), and the module configuration parameters in the source configuration file under each management level can also be customized according to actual needs.

[0048] In one example, the total number of levels is n=10, which can be divided into 10 management levels, from management level 1 to management level 10. The level types of management levels 1 to 10 are type 1 to type 10, respectively. Each of the 10 management levels includes source configuration files for 3 system functional modules. Under the first management level, source configuration files A1 for system functional module A, B1 for system functional module B, and C1 for system functional module C can be customized. A1, B1, and C1 include module configuration parameters related to type 1. Under the second management level, source configuration files A2 for system functional module A, B2 for system functional module B, and C2 for system functional module C can be customized. A2, B2, and C2 include module configuration parameters related to type 2. And so on, with customized source configuration files under other management levels.

[0049] In another example, the total number of levels is n=5, which can be divided into 5 management levels, from management level 1 to management level 5. The level types of management levels 1 to 5 are type 1 to type 5, respectively. The number of source configuration files customized for the 5 management levels can be different. For example, under the first management level, source configuration files A1, B1, and C1 of system functional module A, B1, and C1 can be customized. A1, B1, and C1 include module configuration parameters related to type 1. Under the second management level, source configuration files B2 and C2 of system functional module B and C can be customized. B2 and C2 include module configuration parameters related to type 2.

[0050] Specifically, in one implementation, the basic attribute dimensions of the device (such as brand, region, series, product, common, project, etc., used to describe and classify device attributes) can be combined according to actual needs to obtain a hierarchical type. For example, brand and region can be assembled together to obtain the "brand-region" hierarchical type; brand, project, and product can be assembled together to obtain the "brand_product_project" hierarchical type; series can be a separate hierarchical type; and common can be a separate hierarchical type. Furthermore, the source configuration file customized under the management level of the "brand-region" hierarchical type can include module configuration parameters related to brand and region, and the source configuration file customized under the management level of the "brand_product_project" hierarchical type can include module configuration parameters related to brand, project, and product, and so on.

[0051] Furthermore, the source configuration files included in each management level are merged and serialized separately to obtain a merged serialized configuration file for each management level. Each management level ultimately yields a single merged serialized configuration file. For example, ... Figure 3 As shown, the source configuration files A1 of system functional module A, B1 of system functional module B, and C1 of system functional module C under management level 1 are merged and serialized to obtain merged and serialized configuration file 1 under management level 1; the source configuration files An of system functional module A and Bn of system functional module B under management level n are merged and serialized to obtain merged and serialized configuration file n under management level n.

[0052] The serialization process can be selected according to the actual situation. In one specific embodiment of this application, the data structure serialization and deserialization framework (Protobuf, ProtocolBuffers) is selected for serialization.

[0053] Finally, the management end packages and pushes the merged serialized configuration files under each management level to the device end. The merged serialized configuration files under each management level are saved in the configuration customization resource partition of the system version on the device end. This allows the device end to configure the corresponding parameters of each system function module in the system version based on the merged serialized configuration files under each management level during the runtime, so that the customized functions of each system can run normally.

[0054] In this embodiment of the application, independent source configuration files are configured for each system functional module, and the source configuration files corresponding to each system functional module are customized under one or more management levels. The merged serialization process is performed hierarchically to obtain the merged serialized configuration files under each management level. This allows for reliable decoupling and control of the independent source configuration files of each system functional module at hierarchical levels, reliably avoiding overall control failure caused by a single function configuration error. The configuration parameters of each module can be efficiently managed and maintained at hierarchical levels.

[0055] The following description Figure 1 Further optional specific embodiments are provided for each step performed during configuration management in the example implementation.

[0056] In one embodiment, the source configuration files corresponding to each system functional module include a general source configuration file; the source configuration files corresponding to some or all of the system functional modules also include at least one customized source configuration file; the step of customizing the source configuration files corresponding to each system functional module at one or more management levels for each system functional module on the system side includes: at the lowest priority management level, saving the general source configuration files of all the system functional modules on the system side; at non-lowest priority management levels, customizing at least one customized source configuration file corresponding to each system functional module at the corresponding management level.

[0057] The source configuration files corresponding to each system functional module include general source configuration files, which can be used to store fixed module configuration parameters of the system functional modules; the source configuration files corresponding to some or all of the system functional modules also include at least one customized source configuration file, which can be used to store module configuration parameters that are further customized according to business needs.

[0058] Each of the predetermined management levels has a corresponding priority. Under the lowest priority management level, the general source configuration files for all system functional modules are stored. For example, the lowest priority management level is management level 1 (such as the "common" management level), under which the general source configuration files for system functional modules A, B, and C can be stored. In management levels 2 and 3 (such as the "brand-region" management level and the "brand_product_project" management level), which have higher priorities than management level 1, customized source configuration files for system functional modules A and B can be stored under management level 2, and customized source configuration files for system functional module C can be stored under management level 3.

[0059] In this way, based on the hierarchical management of the independent configuration files of each system functional module, customized configuration files can be further managed according to the priority of the level, which allows for more flexible control of module configuration parameters.

[0060] In one embodiment, before performing the merged serialization process on the source configuration files included under each of the management levels, the method further includes:

[0061] Obtain the configuration specification protocol corresponding to each system functional module; verify the source configuration file corresponding to each system functional module according to the configuration specification protocol; determine whether to merge and serialize the source configuration files included in each management level according to the verification result of the source configuration files under each management level.

[0062] Each system functional module has a corresponding configuration specification protocol. The configuration specification protocol for each system functional module is the parameter specification (e.g., format, quantity, and type) of the configuration parameters in the source configuration file of each system functional module. The source configuration file of each system functional module is verified according to the configuration specification protocol (i.e., whether the module configuration parameters in the source configuration file conform to the "format, quantity, and type" specifications in the configuration specification protocol). The verification result of the source configuration file of each system functional module is obtained, which is also the verification result of the source configuration file at each management level. If the module configuration parameters in the verified source configuration file conform to the "format, quantity, and type" specifications in the configuration specification protocol, the verification result is "verification passed"; otherwise, if the module configuration parameters in the verified source configuration file do not conform to the "format, quantity, and type" specifications in the configuration specification protocol, the verification result is "verification failed".

[0063] Based on the verification results of the source configuration files under each management level, it is determined whether to merge and serialize the source configuration files included under that management level. Specifically, if the verification results of the source configuration files under each management level are successful, then merging and serializing the source configuration files under that management level is allowed (i.e., continuing to execute steps S120 and S130 is allowed). This further ensures that the configuration of each system functional module conforms to the corresponding specifications and further improves the reliability of configuration management.

[0064] For example, see Figure 3 System functional module A corresponds to configuration specification protocol X1, system functional module B corresponds to configuration specification protocol X2, and system functional module C corresponds to configuration specification protocol X3. Further, such as... Figure 3 As shown, in step S310, the source configuration files (such as A1 and An, etc.) corresponding to system functional modules A under each management level can be verified according to configuration specification protocol X1; the source configuration files (such as B1 and Bn, etc.) corresponding to system functional modules B under each management level can be verified according to configuration specification protocol X2; and the source configuration files (such as C1, etc.) corresponding to system functional modules C under each management level can be verified according to configuration specification protocol X3. In step S320, if the verification result of the source configuration files under each management level is successful, it is allowed to merge and serialize the source configuration files included under the management level to obtain the merged serialized configuration files under each management level. For example, if A1, B1, and C1 in management level 1 all pass the verification, then A1, B1, and C1 can be merged and serialized to obtain merged serialized configuration file 1.

[0065] Furthermore, in one embodiment, the step of verifying the source configuration file corresponding to each system functional module according to the configuration specification protocol corresponding to each system functional module includes: coded the configuration specification protocol corresponding to each system functional module to obtain the configuration verification logic corresponding to each system functional module; and verifying the source configuration file corresponding to each system functional module based on the configuration verification logic corresponding to each system functional module.

[0066] See Figure 2In step S230, the configuration specification protocol is transmitted to the configuration coding processing tool. In step S240, the configuration coding processing tool can code the configuration specification protocols corresponding to each system functional module, outputting the configuration verification logic (i.e., coded configuration parameters) corresponding to each system functional module. Each system functional module can be coded to obtain configuration verification logic for various environments, for use in the corresponding environment, such as configuration verification logic for Java, C++, and Python environments. The configuration verification logic corresponding to each system functional module can be automatically read, parsed, and applied by the program, enabling more efficient and accurate verification of the source configuration files corresponding to each system functional module.

[0067] Furthermore, in one embodiment, the step of merging and serializing the source configuration files included under each management level to obtain merged serialized configuration files under each management level includes: parsing the source configuration files included under each management level to obtain source configuration content included under each management level; merging and filling the source configuration content included under each management level into a serialized message structure to obtain configuration messages under each management level; and serializing the configuration messages under each management level to obtain merged serialized configuration files under each management level.

[0068] The source configuration files included in each management level are parsed to obtain the source configuration content included in each management level. For example, parsing the source configuration file of system functional module A under management level 1 yields source configuration content 1, parsing the source configuration file of system functional module B under management level 1 yields source configuration content 2, and parsing the source configuration file of system functional module C under management level 1 yields source configuration content 3.

[0069] Then, the source configuration content included in each management level is merged and filled into a predetermined serialized message structure (such as the message structure defined by Protocol Buffers (protobuf)) to obtain the configuration message under each management level. For example, source configuration content 1, source configuration content 2, and source configuration content 3 are merged and filled into the serialized message structure to obtain a configuration message under management level 1.

[0070] Then, the configuration messages under each management level are serialized to obtain the binary merged serialized configuration file for each management level. For example, the configuration messages under management level 1 are serialized to obtain the merged serialized configuration file for management level 1, and the configuration messages under management level 2 are serialized to obtain the merged serialized configuration file for management level 2.

[0071] In one embodiment, the step of serializing the configuration messages under each management level to obtain a merged serialized configuration file under each management level includes: serializing the configuration messages under each management level in binary form to obtain a merged serialized binary configuration file under each management level.

[0072] The binary serialization process generates merged serialized binary configuration files for each management level. These merged serialized binary configuration files can be read conveniently and efficiently on the device side. Furthermore, the configuration parameters are encrypted and saved in the form of merged serialized binary configuration files, which enhances system security.

[0073] It is understood that in other alternative embodiments, serialization can be performed in other number systems (such as decimal or octal) to obtain a merged serialization configuration file in decimal or octal formats at each management level.

[0074] Figure 4 A flowchart illustrating a configuration management method according to an embodiment of this application is shown schematically. Figure 4 The execution subject of the configuration management method shown can be a device, such as a TV or other smart devices that require configuration management, such as other smart home devices and industrial control devices.

[0075] like Figure 4 As shown, the configuration management method executed on the device side may include steps S410 to S420.

[0076] Step S410: Receive merged serialized configuration files under different management levels from the management terminal. Each merged serialized configuration file under each management level is obtained by the management terminal merging and serializing the source configuration files included in each management level. The management terminal customizes the source configuration files corresponding to each system function module under one or more management levels for each system function module on the system side. Step S420: Save the received merged serialized configuration files in the configuration customization resource partition according to the corresponding management level.

[0077] On the configuration side: Independent source configuration files are configured for each system functional module. Within one or more management levels, the source configuration files for each system functional module are customized. These files are then merged and serialized hierarchically to obtain merged and serialized configuration files for each management level. The configuration side packages these merged and serialized configuration files for each management level to the device side. The device side saves the received merged and serialized configuration files in a customized configuration resource partition (e.g., a TVcust partition) according to the corresponding management level. The configuration side can reliably decouple and manage the independent source configuration files of each system functional module hierarchically, reliably preventing overall control failure caused by a single function configuration error. The configuration parameters of each module can be efficiently managed and maintained hierarchically.

[0078] Furthermore, in one embodiment, after the received merged serialized configuration file is saved in the configuration-customized resource partition according to the corresponding management level, the method further includes: assembling the configuration directory according to the basic attribute dimension of the device to obtain the resource configuration directory corresponding to each management level; loading and parsing the configuration file from the configuration-customized resource partition according to the resource configuration directory corresponding to each management level to obtain the module configuration parameters corresponding to each system function module.

[0079] For example, see Figure 5 After the device system is powered on, the preset configuration parameter management service can send a configuration directory retrieval request to the customization service in step S510. Upon receiving the configuration directory retrieval request, the customization service assembles the configuration directory according to the device's basic attribute dimensions in step S520, obtaining resource configuration directories corresponding to each management level. The basic attribute dimensions of the device are, for example, brand, region, and series, used to describe and classify the device's attributes. By assembling the configuration directory according to these basic attribute dimensions using a predetermined directory assembly method, resource configuration directories corresponding to each management level that conform to the device's attributes can be obtained. For example, brand and region can be assembled together to obtain "brand-region," where "brand-region" serves as a... Figure 5 This is a management level within the customized directory. Further, in step S530, the customization service returns the resource configuration directory to the configuration parameter management service. The configuration parameter management service can load the merged serialized configuration files from the customized resource partition according to the resource configuration directory corresponding to each management level and parse them to obtain the module configuration parameters corresponding to each system functional module. Then, in step S540, each system functional module on the system side can obtain its corresponding module configuration parameters from the configuration parameter management service.

[0080] Furthermore, in one embodiment, the step of loading and parsing configuration files from the configuration-customized resource partition according to the resource configuration directory corresponding to each management level to obtain the module configuration parameters corresponding to each system functional module includes: loading the merged serialized configuration files under each management level from the configuration-customized resource partition according to the resource configuration directory corresponding to each management level; deserializing the merged serialized configuration files under each management level in order of priority from low to high to obtain the source configuration files under each management level; and overwriting the source configuration files under the low priority management level with the source configuration files under the high priority management level to obtain the module configuration parameters corresponding to each system functional module.

[0081] According to the resource configuration directory corresponding to each management level, the merged serialized configuration files under each management level are loaded from the configuration customized resource partition. The merged serialized configuration files under each management level are deserialized in order of priority from low to high to obtain the source configuration files under each management level. By using the "configuration resource overlay strategy", the source configuration files under the higher priority management level are overwritten with the source configuration files under the lower priority management level. The complete module configuration parameters of each system functional module are obtained. The complete module configuration parameters of the system functional module include general default configuration parameters and configuration parameters customized according to business needs.

[0082] To facilitate better implementation of the configuration management method provided in the embodiments of this application, the embodiments of this application also provide a configuration management device based on the above configuration management method. The meanings of the terms used are the same as in the above configuration management method, and specific implementation details can be found in the descriptions in the method embodiments.

[0083] Figure 6 A block diagram of a configuration management apparatus according to an embodiment of this application is shown. Figure 6 The configuration management device 600 shown can be applied to a management terminal, and the configuration management device 600 may include:

[0084] The customization module 610 can be used to: customize the source configuration files corresponding to each system function module under one or more management levels for each system function module on the system side; the processing module 620 can be used to: merge and serialize the source configuration files included under each management level to obtain the merged serialized configuration files under each management level; the packaging module 630 can be used to: package the merged serialized configuration files under each management level into the system version on the device side.

[0085] In some embodiments of this application, before the source configuration files included under each management level are merged and serialized, the device further includes a verification module, configured to: obtain the configuration specification protocol corresponding to each system functional module; verify the source configuration files corresponding to each system functional module according to the configuration specification protocol corresponding to each system functional module; and determine whether to merge and serialize the source configuration files included under each management level according to the verification result of the source configuration files under each management level.

[0086] In some embodiments of this application, the verification module is used to: code the configuration specification protocol corresponding to each system functional module to obtain the configuration verification logic corresponding to each system functional module; and verify the source configuration file corresponding to each system functional module based on the configuration verification logic corresponding to each system functional module.

[0087] In some embodiments of this application, the processing module is used to: parse the source configuration files included under each management level to obtain the source configuration content included under each management level; merge the source configuration content included under each management level into a serialized message structure to obtain the configuration message under each management level; and perform serialization processing on the configuration message under each management level to obtain the merged serialized configuration file under each management level.

[0088] In some embodiments of this application, the source configuration files corresponding to each system functional module include general source configuration files; some or all of the source configuration files corresponding to the system functional modules also include at least one customized source configuration file; the customized module is used to: save the general source configuration files of all the system functional modules on the system side under the lowest priority management level; and customize at least one customized source configuration file corresponding to each system functional module under the corresponding management level under a non-lowest priority management level.

[0089] Figure 7 A block diagram of a configuration management apparatus according to an embodiment of this application is shown. Figure 7 The configuration management device 700 shown can be applied to the device side, and the configuration management device 700 may include:

[0090] The receiving module 710 can be used to: receive merged serialized configuration files under different management levels issued by the management terminal, wherein the merged serialized configuration files under each management level are obtained by the management terminal by merging and serializing the source configuration files included under each management level, and the management terminal customizes the source configuration files corresponding to each system function module under one or more management levels for each system function module on the system side; the storage module 720 can be used to: save the received merged serialized configuration files in the configuration customized resource partition according to the corresponding management level.

[0091] In some embodiments of this application, after the received merged serialized configuration file is saved in the configuration-customized resource partition according to the corresponding management level, the device further includes a parsing module, configured to: assemble the configuration directory according to the basic attribute dimension of the device to obtain the resource configuration directory corresponding to each management level; and load and parse the configuration file from the configuration-customized resource partition according to the resource configuration directory corresponding to each management level to obtain the module configuration parameters corresponding to each system function module.

[0092] In some embodiments of this application, the parsing module is configured to: load the merged serialized configuration files under each management level from the configuration customization resource partition according to the resource configuration directory corresponding to each management level; deserialize the merged serialized configuration files under each management level in order of priority from low to high to obtain the source configuration files under each management level; and overwrite the source configuration files under the low priority management level with the source configuration files under the high priority management level to obtain the module configuration parameters corresponding to each system function module.

[0093] It should be noted that although several modules or units for the device used to perform actions have been mentioned in the detailed description above, this division is not mandatory. In fact, according to the embodiments of this application, the features and functions of two or more modules or units described above can be embodied in one module or unit. Conversely, the features and functions of one module or unit described above can be further divided and embodied by multiple modules or units.

[0094] In addition, embodiments of this application also provide a management terminal, such as... Figure 8 As shown, Figure 8 A block diagram of a management terminal 800 according to an embodiment of this application is shown, specifically:

[0095] The management terminal 800 may include components such as a processor 801 with one or more processing cores, and a memory 802 with one or more computer-readable storage media. Those skilled in the art will understand that... Figure 5The electronic device structure shown does not constitute a limitation on the management end and may include more or fewer components than shown, or combine certain components, or have different component arrangements.

[0096] Specifically in this embodiment, the processor 801 in the management terminal will load the executable files corresponding to the processes of one or more computer programs into the memory 802 according to the following instructions, and the processor 801 will run the computer programs stored in the memory 802 to realize the various functions in the foregoing embodiments of this application.

[0097] Furthermore, embodiments of this application also provide a device, such as... Figure 9 As shown, Figure 9 A block diagram of a device 900 according to an embodiment of this application is shown, specifically:

[0098] The device 900 may include components such as a processor 901 with one or more processing cores, and a memory 902 with one or more computer-readable storage media. Those skilled in the art will understand that... Figure 9 The electronic device structure shown does not constitute a limitation on the device end and may include more or fewer components than shown, or combine certain components, or have different component arrangements.

[0099] Specifically, in this embodiment, the processor 901 in the device will load the executable files corresponding to the processes of one or more computer programs into the memory 902 according to the following instructions, and the processor 901 will run the computer programs stored in the memory 902 to realize the various functions in the foregoing embodiments of this application.

[0100] Those skilled in the art will understand that all or part of the steps in the various methods of the above embodiments can be performed by a computer program, or by a computer program controlling related hardware. The computer program can be stored in a computer-readable storage medium and loaded and executed by a processor.

[0101] Therefore, embodiments of this application also provide a storage medium storing a computer program that can be loaded by a processor to execute the steps in any of the methods provided in embodiments of this application.

[0102] The storage medium can be a computer-readable storage medium, which may include: read-only memory (ROM), random access memory (RAM), disk or optical disk, etc.

[0103] Since the computer program stored in the storage medium can execute the steps of any of the methods provided in the embodiments of this application, the beneficial effects that the methods provided in the embodiments of this application can achieve can be realized. For details, please refer to the previous embodiments, which will not be repeated here.

[0104] According to another embodiment of this application, a computer program product or computer program includes computer instructions stored in a computer-readable storage medium. A processor at a management end or device end reads the computer instructions from the computer-readable storage medium and executes the computer instructions, causing the management end or device end to perform the methods provided in the various optional implementations described in the embodiments of this application.

[0105] Other embodiments of this application will readily occur to those skilled in the art upon consideration of the specification and practice of the embodiments disclosed herein. This application is intended to cover any variations, uses, or adaptations of this application that follow the general principles of this application and include common knowledge or customary techniques in the art not disclosed herein.

[0106] It should be understood that this application is not limited to the embodiments described above and shown in the accompanying drawings, but various modifications and changes can be made without departing from its scope.

Claims

1. A configuration management method, characterized in that, Applied to the management end, the method includes: For each system functional module on the system side, the source configuration file corresponding to each system functional module is customized under one or more management levels; The source configuration files included under each management level are merged and serialized to obtain the merged and serialized configuration files under each management level. The merged serialized configuration files under each management level are packaged into the system version on the device.

2. The method according to claim 1, characterized in that, Before performing the merged serialization process on the source configuration files included under each of the management levels, the method further includes: Obtain the configuration specification protocol corresponding to each of the system functional modules; According to the configuration specification protocol corresponding to each of the system functional modules, the source configuration files corresponding to each of the system functional modules are verified. Based on the verification results of the source configuration files under each management level, determine whether to merge and serialize the source configuration files included under each management level.

3. The method according to claim 2, characterized in that, The step of verifying the source configuration files corresponding to each system functional module according to the configuration specification protocol of each system functional module includes: The configuration specification protocol corresponding to each of the system functional modules is coded to obtain the configuration verification logic corresponding to each of the system functional modules. Based on the configuration verification logic corresponding to each of the system functional modules, the source configuration files corresponding to each of the system functional modules are verified respectively.

4. The method according to claim 1, characterized in that, The step of merging and serializing the source configuration files included under each management level to obtain merged and serialized configuration files under each management level includes: The source configuration files included under each management level are parsed to obtain the source configuration content included under each management level; The source configuration content included under each management level is merged and filled into the serialized message structure to obtain the configuration message under each management level; The configuration messages under each management level are serialized to obtain the merged serialized configuration file under each management level.

5. The method according to claim 1, characterized in that, The source configuration files corresponding to each of the system functional modules include general source configuration files; some or all of the source configuration files corresponding to the system functional modules also include at least one customized source configuration file; The method for customizing source configuration files for each system functional module on the system side, under one or more management levels, includes: At the lowest priority management level, save the general source configuration files of all system functional modules on the system side; Under a non-lowest priority management level, at least one customized source configuration file corresponding to each of the system functional modules is customized under the corresponding management level.

6. The method according to claim 4, characterized in that, The step of serializing the configuration messages under each management level to obtain the merged serialized configuration file under each management level includes: The configuration messages under each management level are serialized in binary form to obtain the merged serialized binary configuration file under each management level.

7. A configuration management method, characterized in that, Applied to the device side, the method includes: The system receives merged serialized configuration files under different management levels from the management terminal. The merged serialized configuration files under each management level are obtained by the management terminal by merging and serializing the source configuration files included under each management level. The management terminal customizes the source configuration files corresponding to each system function module under one or more management levels for each system function module on the system side. The received merged serialization configuration files are saved in the configuration-customized resource partition according to the corresponding management level.

8. The method according to claim 7, characterized in that, After saving the received merged serialization configuration file in the configuration-customized resource partition according to the corresponding management level, the method further includes: The configuration catalog is assembled according to the basic attribute dimensions of the device to obtain the resource configuration catalog corresponding to each management level. According to the resource configuration directory corresponding to each management level, the configuration files are loaded and parsed from the configuration customization resource partition to obtain the module configuration parameters corresponding to each system function module.

9. The method according to claim 8, characterized in that, The configuration file is loaded and parsed from the customized resource partition according to the resource configuration directory corresponding to each management level to obtain the module configuration parameters corresponding to each system functional module, including: According to the resource configuration directory corresponding to each management level, the merged serialized configuration file under each management level is loaded from the configuration customized resource partition; The merged serialized configuration files under each management level are deserialized in order of priority from low to high to obtain the source configuration files under each management level. The source configuration files under the higher priority management level are overwritten with the source configuration files under the lower priority management level to obtain the module configuration parameters corresponding to each system functional module.

10. A configuration management device, characterized in that, The device, used in the management terminal, includes: Customization module, used to: customize the source configuration file corresponding to each system functional module on the system side under one or more management levels; The processing module is used to: merge and serialize the source configuration files included under each management level to obtain merged and serialized configuration files under each management level; The packaging module is used to package the merged serialized configuration files from each of the aforementioned management levels into the system version on the device.

11. A configuration management device, characterized in that, Applied to the device side, the device includes: The receiving module is used to: receive merged serialized configuration files under different management levels issued by the management terminal, wherein the merged serialized configuration files under each management level are obtained by the management terminal by merging and serializing the source configuration files included under each management level, and the management terminal customizes the source configuration files corresponding to each system function module under one or more management levels for each system function module on the system side. The storage module is used to save the received merged serialization configuration files in the configuration-customized resource partition according to the corresponding management level.

12. A storage medium, characterized in that, It stores a computer program that, when executed by a processor at a management end, causes the management end to perform the method described in any one of claims 1 to 6; or, when executed by a processor at a device end, causes the device end to perform the method described in any one of claims 7 to 9.

13. A management terminal, characterized in that, include: Memory, which stores computer programs; A processor reads a computer program stored in memory to perform the method described in any one of claims 1 to 6.

14. A device terminal, characterized in that, include: Memory, which stores computer programs; A processor reads a computer program stored in memory to perform the method according to any one of claims 7 to 9.

Images