A blockchain-based configuration management method, device, system and storage medium
By using blockchain technology and smart contracts to manage configuration files, the problems of cumbersome modifications and inconsistent configurations in traditional configuration management are solved, enabling dynamic configuration management and efficient configuration file modification.
Patent Information
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- HANGZHOU QULIAN TECHNOLOGY CO LTD
- Filing Date
- 2023-02-28
- Publication Date
- 2026-07-03
Smart Images
Figure CN116204224B_ABST
Abstract
Description
Technical Field
[0001] This application relates to the field of blockchain technology, and in particular to a blockchain-based configuration management method, apparatus, system and storage medium. Background Technology
[0002] When an application service starts up and runs, it needs to configure various system and business requirements. Some applications require configurations that can be modified at runtime, and these configurations need to be maintained and managed by multiple organizations. For example, regulated applications need to support the modification of specific parameter values for relevant configuration rules by the regulatory authorities.
[0003] Traditional application configuration management mostly embeds configuration files in the installation package or file directory, which are read when the application starts. The disadvantage is that when the configuration file is modified, the service needs to be restarted, dynamic modification is not supported, and in the case of distributed cluster deployment, the configuration of each node needs to be modified, which is cumbersome and difficult to ensure configuration consistency. Summary of the Invention
[0004] To address the technical challenge of improving the ease of modifying configuration files, this application provides a blockchain-based configuration management method, apparatus, system, and storage medium.
[0005] Firstly, this application provides a blockchain-based configuration management method, including:
[0006] Obtain the target organization's modification request for the target configuration in the blockchain; the modification request carries the identification information of the target organization;
[0007] Based on the identification information and the preset permission management rules, determine whether the target organization has the permission to modify the target configuration;
[0008] If the target organization has the authority to modify the target configuration, determine whether the modification content carried in the modification request conforms to the preset configuration rules;
[0009] If the modification conforms to the configuration rules, the target configuration is modified according to the modification to manage all node devices using the target configuration based on the target configuration;
[0010] Optionally, before obtaining the target institution's request to modify the target configuration in the blockchain, the method further includes: setting the target configuration in a smart contract to manage all the node devices using the target configuration based on the target configuration through the smart contract;
[0011] Accordingly, obtaining the target institution's modification request for the target configuration in the blockchain includes: obtaining the target institution's modification request for the target configuration in the smart contract;
[0012] Optionally, before obtaining the target institution's request to modify the target configuration in the blockchain, the target configuration is set after the smart contract is executed, and the method further includes:
[0013] The smart contract is deployed, and its permission management rules and configuration rules cannot be changed.
[0014] Optionally, after modifying the target configuration according to the modifications, the method further includes:
[0015] Obtain the configuration read request of the first application; the first application is an application that is not started on the node device when the target configuration is modified;
[0016] Based on the configuration read request, the modified current configuration value of the target configuration is sent to the first application;
[0017] And / or,
[0018] Monitor a second application that is running; the second application is an application that was already running on the node device when the target configuration was modified.
[0019] Apply the modified target configuration to each of the second applications;
[0020] Optionally, the identification information includes the signature of the target organization; the signatures of any two target organizations are different.
[0021] Based on the identification information and preset access control rules, determine whether the target organization has permission to modify the target configuration, including:
[0022] Verify whether the signature is included in the permission management rules;
[0023] If the permission management rule contains the signature, it is determined that the target organization has the permission to modify the target configuration; if the permission management rule does not contain the signature, it is determined that the target organization does not have the permission to modify the target configuration.
[0024] Optionally, after modifying the target configuration according to the modifications, the method further includes:
[0025] Generate change information based on the modifications;
[0026] The change information is stored in the configuration change record.
[0027] Secondly, this application provides a blockchain-based configuration management device, comprising:
[0028] The acquisition module is used to acquire the modification request from the target organization for the target configuration in the blockchain; the modification request carries the identification information of the target organization;
[0029] The first judgment module is used to determine whether the target organization has the authority to modify the target configuration based on the identification information and the preset permission management rules;
[0030] The second judgment module is used to determine whether the modification content carried in the modification request conforms to the preset configuration rules if the target organization has the authority to modify the target configuration.
[0031] The modification module is used to modify the target configuration according to the modification content if the modification content conforms to the configuration rules, so as to manage all node devices using the target configuration based on the target configuration.
[0032] Thirdly, this application provides a blockchain-based configuration management system, including: a target organization, node devices, and a blockchain;
[0033] The blockchain is used to obtain modification requests from target institutions for target configurations within the blockchain; the modification requests carry the identification information of the target institution; based on the identification information and preset permission management rules, it is determined whether the target institution has permission to modify the target configuration; if the target institution has permission to modify the target configuration, it is determined whether the modification content carried in the modification request conforms to preset configuration rules; if the modification content conforms to the configuration rules, the target configuration is modified according to the modification content, so as to manage all node devices using the target configuration based on the target configuration.
[0034] Fourthly, this application provides an electronic device, including a processor, a communication interface, a memory, and a communication bus, wherein the processor, the communication interface, and the memory communicate with each other through the communication bus;
[0035] Memory, used to store computer programs;
[0036] When a processor executes a program stored in memory, it implements the steps of a blockchain-based configuration management method as described in any embodiment of the first aspect.
[0037] Fifthly, this application provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the steps of a blockchain-based configuration management method as described in any embodiment of the first aspect.
[0038] The technical solutions provided in this application have the following advantages compared with the prior art:
[0039] The method provided in this application embodiment obtains a modification request from a target organization regarding a target configuration in a blockchain. The modification request carries the target organization's identification information. Based on the identification information and preset permission management rules, it is determined whether the target organization has permission to modify the target configuration. If the target organization has permission to modify the target configuration, it is determined whether the modification content carried in the modification request conforms to preset configuration rules. If the modification content conforms to the configuration rules, the target configuration is modified according to the modification content to manage all node devices using the target configuration. This method, based on the target configuration in the blockchain, can centrally manage all node devices using the target configuration, eliminating the need to configure a target configuration file separately for each node, thus improving the convenience of configuration file modification. Attached Figure Description
[0040] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with the invention and, together with the description, serve to explain the principles of the invention.
[0041] To more clearly illustrate the technical solutions in the embodiments of the present invention or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, for those skilled in the art, other drawings can be obtained based on these drawings without creative effort.
[0042] Figure 1 A system architecture diagram of a blockchain-based configuration management method provided in one embodiment of this application;
[0043] Figure 2 A schematic flowchart illustrating a blockchain-based configuration management method provided in one embodiment of this application;
[0044] Figure 3 A logical schematic diagram of a blockchain-based configuration management method provided in one embodiment of this application;
[0045] Figure 4 A schematic diagram of the structure of a blockchain-based configuration management device provided in one embodiment of this application;
[0046] Figure 5 This is a schematic diagram of the structure of an electronic device provided in one embodiment of this application. Detailed Implementation
[0047] To make the objectives, technical solutions, and advantages of the embodiments of this application clearer, the technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.
[0048] The first embodiment of this application provides a blockchain-based configuration management method, which can be applied to, for example... Figure 1 The system architecture shown includes at least a target institution 101, a blockchain 102, and node devices 103. The target institution 101 and node devices 103 establish a communication connection through the blockchain 102. The number of target institutions 101 and node devices 103 is not limited.
[0049] Next, based on this system architecture, the blockchain-based configuration management method will be described in detail, such as... Figure 2 The methods include:
[0050] Step 201: Obtain the target organization's modification request for the target configuration in the blockchain. The modification request carries the target organization's identification information.
[0051] There can be multiple institutions on the blockchain. The institution that submits a request to modify the target configuration can be called the target institution, and the target configuration can also be called the target configuration file. The modification request carries the target institution's identification information to identify the institution. Different institutions can have different permissions to modify the target configuration. For example, institution A can be set to modify configurations a, b, and c in the target configuration, while institution B can modify configurations e, f, and g. Of course, some configurations can also be set to have modification permissions for multiple institutions. For example, institution A can be set to modify configurations a, b, c, and d in the target configuration, while institution B can modify configurations d, e, f, and g. Configuration d can be modified by either institution A or institution B.
[0052] In traditional solutions, the configuration files for an organization are placed in the installation package or file directory of a single node device, requiring the configuration of a target configuration file for each node. In this embodiment, the target configuration is set in the blockchain, and all node devices using the target configuration can be managed through the target configuration on the chain. When specific modifications are needed to the configuration, only the target configuration on the chain needs to be modified.
[0053] Of course, the organization's permission to modify the target configuration needs to be set in advance, and once set, it cannot be changed. The specific configurations that the organization can modify in the target configuration can be set as needed. The above content in the embodiments of this application is only for illustrative purposes and does not represent a specific restriction on the configurations that the target organization can modify.
[0054] In one embodiment, before obtaining a modification request from the target organization for the target configuration in the blockchain, the method further includes: setting the target configuration in a smart contract to manage node devices based on the target configuration through the smart contract.
[0055] In this embodiment, the management of the target configuration can be achieved through smart contracts on the blockchain. Obtaining the target organization's modification request for the target configuration in the blockchain includes: obtaining the target organization's modification request for the target configuration in the smart contract.
[0056] The target configuration file is set within a smart contract. Once deployed, this smart contract's permission management and configuration rules are set to be immutable. This means that once deployed, the smart contract's permission management and configuration rules cannot be modified by any organization or individual. Only pre-defined modifications are permitted under the permission management and configuration rules configured at the time of deployment. This ensures the transparency and immutability of the configuration file's rules, preventing human manipulation. Furthermore, if the target organization needs to make modifications, it only needs to modify the target configuration according to the rules, without needing to modify the configuration within individual nodes, thus improving the ease of configuration file modification.
[0057] Step 202: Based on the identification information and the preset permission management rules, determine whether the target organization has the permission to modify the target configuration.
[0058] The identification information can be the signature of the target organization or other information that can uniquely identify the target organization. When the identification information is the signature of the target organization, the signatures of any two target organizations are different.
[0059] Based on the identification information and the preset permission management rules, determine whether the target organization has the authority to modify the target configuration, including: verifying whether the signature is included in the permission management rules; if the permission management rules include the signature, determine that the target organization has the authority to modify the target configuration; if the permission management rules do not include the signature, determine that the target organization does not have the authority to modify the target configuration.
[0060] In this embodiment, the smart contract's permission management rules pre-store the signatures of the institutions authorized to modify it. When the signature of the target institution is obtained, if the signature in the permission management rules includes that institution's signature, then the target institution can be considered to have the permission to modify the target configuration of the smart contract. Including the signature of the relevant institution user when calling the blockchain smart contract's related interfaces can ensure authorization during interface calls. Furthermore, since signatures are non-repudiable, they can be used to trace configuration changes.
[0061] It needs to be clarified again that modifying the target configuration here does not mean modifying the smart contract's permission management rules and configuration rules. Rather, it means modifying the specific values of the specific configuration within the scope permitted by the rules. In fact, once a smart contract is deployed, its permission management rules and configuration rules cannot be modified by any organization or individual.
[0062] Step 203: If the target organization has the authority to modify the target configuration, determine whether the modification content carried in the modification request conforms to the preset configuration rules.
[0063] In this embodiment, if the target organization has the authority to modify the target configuration, it can further determine whether the modification content carried by the modification request conforms to the preset configuration rules. The specific configuration rules can be the range or scope in which the configuration is allowed to be modified.
[0064] Step 204: If the modified content conforms to the configuration rules, modify the target configuration according to the modified content, so as to manage all node devices using the target configuration based on the target configuration.
[0065] For example, if the configuration rule for configuration 'a' is that 'a' is greater than 1 and less than 10, then if the modification request carries the content of changing configuration 'a' to 6, it means that the modification content conforms to the preset configuration rule and the modification is allowed. If the modification request carries the content of changing configuration 'a' to 12, it means that the modification content does not conform to the preset configuration rule and the modification fails.
[0066] It should be noted that configuration rules can be set as needed. The specific scope of configuration 'a' above is only for illustrative purposes and does not represent a specific restriction on the configuration rules.
[0067] In one embodiment, after modifying the target configuration according to the modifications, the processing of running applications and non-started applications using the target configuration is slightly different.
[0068] The first scenario, for applications that are started after modification (i.e., applications that were not started when the modification was made), includes: obtaining the configuration read request of the first application, and sending the current configuration value of the modified target configuration to the first application based on the configuration read request.
[0069] That is, for applications that are not started when modifications are made, the latest current configuration value of the target configuration is read through a configuration read request when the application is started.
[0070] The second scenario involves applications that are already running or started at the time of modification, including: monitoring running second applications and applying the modified target configuration to each of the second applications.
[0071] That is, for applications that are already running when modifications are made, the latest current configuration value of the target configuration is obtained by listening.
[0072] In this embodiment, decentralized trusted configuration management can be achieved in scenarios where multiple parties need to manage and maintain application configurations. Based on the consensus algorithm of blockchain, it has more reliable configuration data consistency guarantee in high-availability deployment.
[0073] It should be noted that the first application refers to the application that was not started on the node device when the target configuration was modified. Different node devices can have multiple identical first applications, and the same node device can also have multiple different first applications. Applications that use the same target configuration and were not started when the target configuration was modified can all be referred to as the first application. There are no other restrictions.
[0074] It should be noted that the second application refers to the application that has been started on the node device when the target configuration is modified. Different node devices can have multiple identical second applications, and the same node device can also have multiple different second applications. Applications that use the same target configuration but have not been started when the target configuration is modified can all be referred to as second applications. There are no other restrictions.
[0075] In one embodiment, after modifying the target configuration according to the modified content, the method further includes: generating change information according to the modified content and storing the change information in the configuration change record.
[0076] In this embodiment, the configuration change record is stored on the blockchain. It can be a configuration change log or any other record form. The configuration change record is stored on the blockchain after the configuration change, which can facilitate the trusted traceability and auditing of the configuration change in the future.
[0077] In one embodiment, a logical diagram of a blockchain-based configuration management method is shown, as follows: Figure 3 The application's target configuration is stored in a smart contract on the blockchain, which manages the permissions for that configuration. The contract stores permission management mappings (which organizations have permission to change which configuration items, also known as permission management rules), configuration rule mappings (the rules for modifying configuration items, also known as configuration rules, such as only allowing the configuration item to be greater than 1 and less than 10), and current configuration value mappings.
[0078] The application startup and runtime configuration management logic is as follows:
[0079] When the new application 1 starts, it reads the current configuration value in the blockchain smart contract to make relevant system business configurations and continuously listens for configuration change events on the blockchain.
[0080] When organization A calls the blockchain to modify configuration a:
[0081] The smart contract checks whether institution A has permission to modify the configuration. If it does not have permission, the process fails. If it has permission, it checks whether the configuration matches the rules. If it does not match the rules, the process fails. If the configuration matches the rules, the smart contract modifies the current value of configuration A and then uses the blockchain's event notification capability to send a configuration modification event to the running application listening for the event.
[0082] Applications 2 and 3, which are already running, listen for the blockchain configuration modification event, parse the current value of configuration 'a', and then modify the value of configuration 'a' in the application.
[0083] In this embodiment, Application 1, Application 2 and Application 3 can be the same application or different applications that apply the same target configuration, without limitation.
[0084] Calling blockchain smart contract-related interfaces requires the signature of the relevant institutional user. This serves two purposes: first, to confirm ownership; and second, because the signature is non-repudiable and can be used to trace configuration changes.
[0085] Target configuration based on blockchain allows for centralized management of all node devices using that target configuration. This eliminates the need to configure a separate target configuration file for each node, thus reducing the need to modify individual node configurations and improving the ease of configuration file modification. In scenarios requiring multi-party management and maintenance of application configurations, decentralized and trusted configuration management is achieved. Based on blockchain consensus algorithms, it provides more reliable configuration data consistency guarantees in high-availability deployments. Furthermore, on-chain storage of configuration change records facilitates reliable traceability and auditing of subsequent configuration changes. Smart contracts, once deployed, cannot be changed, ensuring the transparency and immutability of configuration maintenance rules.
[0086] Based on the same technical concept, the second embodiment of this application provides a blockchain-based configuration management device, such as... Figure 4 The device includes:
[0087] The acquisition module 401 is used to acquire the modification request of the target institution to the target configuration in the blockchain; the modification request carries the identification information of the target institution;
[0088] The first judgment module 402 is used to determine whether the target organization has the authority to modify the target configuration based on the identification information and the preset permission management rules;
[0089] The second judgment module 403 is used to determine whether the modification content carried by the modification application conforms to the preset configuration rules if the target organization has the authority to modify the target configuration.
[0090] Modification module 404 is used to modify the target configuration according to the modification content if the modification content conforms to the configuration rules, so as to manage all node devices using the target configuration based on the target configuration.
[0091] This device, based on the target configuration in the blockchain, can centrally manage all node devices using the target configuration. It does not require configuring a target configuration file for each node separately, and therefore does not require modifying the configuration of each node individually, thus improving the convenience of modifying the configuration file.
[0092] like Figure 5 As shown, the third embodiment of this application provides an electronic device, including a processor 111, a communication interface 112, a memory 113, and a communication bus 114, wherein the processor 111, the communication interface 112, and the memory 113 communicate with each other through the communication bus 114.
[0093] Memory 113 is used to store computer programs;
[0094] In one embodiment, when processor 111 executes a program stored in memory 113, it implements a blockchain-based configuration management method provided in any of the foregoing method embodiments, including:
[0095] Obtain the target organization's modification request for the target configuration in the blockchain; the modification request carries the identification information of the target organization;
[0096] Based on the identification information and the preset permission management rules, determine whether the target organization has the permission to modify the target configuration;
[0097] If the target organization has the authority to modify the target configuration, determine whether the modification content carried in the modification request conforms to the preset configuration rules;
[0098] If the modification conforms to the configuration rules, the target configuration is modified according to the modification to manage all node devices using the target configuration.
[0099] The communication bus mentioned above can be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (EISA) bus, etc. This communication bus can be divided into address bus, data bus, control bus, etc. For ease of illustration, only one thick line is used to represent it in the diagram, but this does not mean that there is only one bus or one type of bus.
[0100] The communication interface is used for communication between the aforementioned terminal and other devices.
[0101] The memory may include random access memory (RAM) or non-volatile memory, such as at least one disk storage device. Optionally, the memory may also be at least one storage device located remotely from the aforementioned processor.
[0102] The processors mentioned above can be general-purpose processors, including central processing units (CPUs), network processors (NPs), etc.; they can also be digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components.
[0103] The fourth embodiment of this application also provides a computer-readable storage medium storing a computer program thereon, which, when executed by a processor, implements the steps of a blockchain-based configuration management method as provided in any of the foregoing method embodiments.
[0104] In the above embodiments, implementation can be achieved entirely or partially through software, hardware, firmware, or any combination thereof. When implemented using software, it can be implemented entirely or partially in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of this application are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via wired (e.g., coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that integrates one or more available media. The available medium can be a magnetic medium (e.g., floppy disk, hard disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium (e.g., solid state disk (SSD)).
[0105] It should be noted that, in this document, relational terms such as "first" and "second" are used merely to distinguish one entity or operation from another, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Furthermore, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element.
[0106] It should be understood that the specific embodiments described herein are merely illustrative of the invention and are not intended to limit the invention. In the description, suffixes such as "module," "part," or "unit" used to denote elements are used only for the purpose of illustrative purposes and have no specific meaning in themselves. Therefore, "module," "part," or "unit" may be used interchangeably.
[0107] The above description is merely a specific embodiment of the present invention, enabling those skilled in the art to understand or implement the invention. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the spirit or scope of the invention. Therefore, the present invention is not to be limited to the embodiments shown herein, but is to be accorded the widest scope consistent with the principles and novel features claimed herein.
Claims
1. A blockchain-based configuration management method, characterized by, The method includes: Obtain the target organization's modification request for the target configuration in the blockchain; the modification request carries the identification information of the target organization; Based on the identification information and the preset permission management rules, determine whether the target organization has the permission to modify the target configuration; If the target organization has the authority to modify the target configuration, it is determined whether the modification content carried in the modification request conforms to the preset configuration rules; wherein, the configuration rules include the range or scope in which the target configuration is allowed to be modified; If the modification conforms to the configuration rules, the target configuration is modified according to the modification to manage all node devices using the target configuration based on the target configuration; Before obtaining the target institution's request to modify the target configuration in the blockchain, the method further includes: setting the target configuration in a smart contract, so as to manage all the node devices using the target configuration through the smart contract; wherein the permission management rules and configuration rules of the smart contract cannot be changed; Accordingly, obtaining the target institution's modification request for the target configuration in the blockchain includes: obtaining the target institution's modification request for the target configuration in the smart contract; The method further includes, after modifying the target configuration according to the modified content: Obtain the configuration read request of the first application; the first application is an application that is not started on the node device when the target configuration is modified; Based on the configuration read request, the modified current configuration value of the target configuration is sent to the first application; And / or, Monitor a second application that is running; the second application is an application that was already running on the node device when the target configuration was modified. Apply the modified target configuration to each of the second applications.
2. The method according to claim 1, characterized in that, Before obtaining a modification request from the target institution for the target configuration in the blockchain, the method further includes setting the target configuration in the smart contract. Deploy the smart contract.
3. The method according to claim 1, characterized in that, The identification information includes the signature of the target organization; the signatures of any two target organizations are different; Based on the identification information and preset access control rules, determine whether the target organization has permission to modify the target configuration, including: Verify whether the signature is included in the permission management rules; If the permission management rule contains the signature, it is determined that the target organization has the permission to modify the target configuration; if the permission management rule does not contain the signature, it is determined that the target organization does not have the permission to modify the target configuration.
4. The method according to claim 1, characterized in that, After modifying the target configuration according to the aforementioned modifications, the method further includes: Generate change information based on the modifications; The change information is stored in the configuration change record.
5. A blockchain-based configuration management device, characterized in that, The device includes: The acquisition module is used to acquire the modification request from the target organization for the target configuration in the blockchain; the modification request carries the identification information of the target organization; The first judgment module is used to determine whether the target organization has the authority to modify the target configuration based on the identification information and the preset permission management rules; The second judgment module is used to determine whether the modification content carried in the modification request conforms to the preset configuration rules if the target organization has the authority to modify the target configuration; wherein, the configuration rules include the range or scope in which the target configuration is allowed to be modified; The modification module is configured to modify the target configuration according to the modification content if the modification content conforms to the configuration rules, so as to manage all node devices using the target configuration based on the target configuration; wherein, after modifying the target configuration according to the modification content, the modification module is further configured to: obtain a configuration read request from a first application; the first application is an application that is not started on the node device when the target configuration is modified; based on the configuration read request, send the modified current configuration value of the target configuration to the first application; and / or, monitor a running second application; the second application is an application that is started on the node device when the target configuration is modified; and modify the modified target configuration to each of the second applications; The acquisition module is further configured to set the target configuration in a smart contract before acquiring the target institution's modification request for the target configuration in the blockchain, so as to manage all the node devices using the target configuration through the smart contract; wherein the permission management rules and configuration rules of the smart contract cannot be changed; the acquisition module is specifically configured to acquire the target institution's modification request for the target configuration in the smart contract.
6. A blockchain-based configuration management system, characterized in that, The system includes: target institutions, node devices, and a blockchain; The blockchain is used to obtain modification requests from target institutions regarding target configurations within the blockchain; the modification requests carry the identification information of the target institution; based on the identification information and preset permission management rules, it is determined whether the target institution has permission to modify the target configuration; if the target institution has permission to modify the target configuration, it is determined whether the modification content carried in the modification request conforms to preset configuration rules; wherein, the configuration rules include the range or scope within which the target configuration is allowed to be modified; if the modification content conforms to the configuration rules, the target configuration is modified according to the modification content, so as to manage all node devices using the target configuration based on the target configuration; wherein, before obtaining the modification requests from target institutions regarding target configurations within the blockchain, the blockchain is also used to: set the target configuration in a smart contract, so as to manage all node devices using the target configuration through the smart contract. The system manages all node devices using the target configuration based on the target configuration; wherein the permission management rules and configuration rules of the smart contract are immutable; correspondingly, it obtains the target organization's modification request for the target configuration in the blockchain, including: obtaining the target organization's modification request for the target configuration in the smart contract; wherein, after modifying the target configuration according to the modification content, the blockchain is further used to: obtain a configuration read request from a first application; the first application is an application that was not started on the node device when the target configuration was modified; based on the configuration read request, send the modified current configuration value of the target configuration to the first application; and / or, monitor a running second application; the second application is an application that was started on the node device when the target configuration was modified; and modify the modified target configuration to each of the second applications.
7. An electronic device, characterized in that, It includes a processor, a communication interface, a memory, and a communication bus, wherein the processor, the communication interface, and the memory communicate with each other through the communication bus; Memory, used to store computer programs; When a processor executes a program stored in memory, it implements the steps of the blockchain-based configuration management method according to any one of claims 1-4.
8. 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 blockchain-based configuration management method as described in any one of claims 1-4.