WO2022077846A1

WO2022077846A1 - Blockchain-based operation and maintenance method and system, computer device and storage medium

Info

Publication number: WO2022077846A1
Application number: PCT/CN2021/078571
Authority: WO
Inventors: 姜勇; 韩永楠; 陈宇峰
Original assignee: 杭州云链趣链数字科技有限公司
Priority date: 2020-10-15
Filing date: 2021-03-02
Publication date: 2022-04-21
Also published as: CN111930443A; CN111930443B

Abstract

A blockchain-based operation and maintenance method and system, a computer device and a storage medium. The method comprises: updating an on-chain configuration file on a blockchain according to an operation and maintenance request, and pushing an operation and maintenance message to a message queue of each node on the blockchain, wherein the on-chain configuration file corresponds to the operation and maintenance request, and the operation and maintenance message corresponds to the operation and maintenance request; under the condition that the operation and maintenance message is successfully pushed to the message queue, recording the push operation on the blockchain in the form of a transaction; and obtaining the operation and maintenance message from the message queue and according to the operation and maintenance message, performing an operation and maintenance operation corresponding to the operation and maintenance message on the node.

Description

Blockchain-based operation and maintenance method, system, computer equipment and storage medium

Related applications

This application claims the priority of the Chinese patent application filed on October 15, 2020, the application number is 202011101503.X, and the invention name is "blockchain-based operation and maintenance method, system, computer equipment and storage medium", all of which The contents are incorporated herein by reference.

technical field

The present application relates to the field of blockchain technology, in particular to a blockchain-based operation and maintenance method, system, computer equipment and storage medium.

Background technique

Software version iteration is a very common requirement in system operation and maintenance. At present, continuous integration (CI) has become a common practice focusing on ensuring code quality throughout the software development life cycle. It is a practice aimed at Ease and stabilize the software build process. Continuous Delivery (CD for short) is based on continuous integration of CI, deploying the integrated code to a more realistic operating environment. However, in the related art, the existing system operation and maintenance scheme, for example, uses Jenkins as a CI tool, and it is difficult to ensure timeliness and security when multiple systems are unified for operation and maintenance management. For example, if the system time of multiple operation and maintenance systems is inconsistent, there may be a large time difference in the iterative process during iteration, so that each system cannot complete the collaborative work; for another example, multiple operation and maintenance systems cannot ensure that the content of their upgrade and maintenance is consistent. It may lead to vulnerabilities in the upgrade process and cause security issues.

Aiming at the problems of poor timeliness and security in the operation and maintenance scheme in related technologies, no effective solution has been proposed yet.

SUMMARY OF THE INVENTION

Based on this, it is necessary to provide a blockchain-based operation and maintenance method, system, computer equipment and storage medium for the above technical problems.

In a first aspect, an embodiment of the present application provides a blockchain-based operation and maintenance method, including the following steps:

Update the on-chain configuration file on the blockchain according to the operation and maintenance request, and push the operation and maintenance message to the message queue of each node on the blockchain, wherein the on-chain configuration file corresponds to the operation and maintenance request, so The operation and maintenance message corresponds to the operation and maintenance request;

In the case that the operation and maintenance message is successfully pushed to the message queue, record the push operation and maintenance message to the message queue of each node on the blockchain in the form of a transaction on the blockchain;

The operation and maintenance message is acquired from the message queue, and an operation and maintenance operation corresponding to the operation and maintenance message is performed on the node according to the operation and maintenance message.

In one embodiment, the method further includes: updating an on-chain configuration file and an operation and maintenance record on the blockchain according to the operation and maintenance request, and pushing the operation and maintenance message to each a message queue of a node, wherein the operation and maintenance message includes the operation and maintenance record;

The operation and maintenance message is acquired from the message queue, and an operation and maintenance operation corresponding to the operation and maintenance message is performed on the node according to the operation and maintenance record in the operation and maintenance message.

In one embodiment, the operation and maintenance record includes an identifier, a system type, and an operation and maintenance policy.

In one embodiment, when the operation and maintenance request is a version update, the method further includes:

Update the on-chain configuration file on the blockchain according to the operation and maintenance request, upload the bytecode file to the blockchain, and push the operation and maintenance message to the messages of each node on the blockchain a queue, wherein the bytecode file corresponds to the operation and maintenance request;

In the case that the operation and maintenance message is successfully pushed to the message queue, record the message queue that pushes the operation and maintenance message to each node on the blockchain in the form of a transaction on the blockchain ;

Obtain the operation and maintenance message from the message queue, obtain the bytecode file from the blockchain according to the operation and maintenance message, and update the bytecode file to the node.

In one embodiment, when the operation and maintenance request is a version rollback, the method further includes:

Obtain the rollback version number of the operation and maintenance request, and push the operation and maintenance message to the message queue of each node on the blockchain, where the corresponding bytecode file is stored in the blockchain version number;

Obtain the operation and maintenance message from the message queue, obtain the fallback version bytecode file corresponding to the rollback version from the blockchain according to the operation and maintenance message, and store the fallback version A bytecode file is updated to the node corresponding to the message queue.

In one of the embodiments, the method further includes: when a preset rollback process is triggered, obtaining a rollback version number according to the rollback process, and obtaining and matching the rollback version number from the blockchain. A fallback version bytecode file corresponding to the fallback version is updated, and the fallback version bytecode file is updated to the node corresponding to the message queue.

In one of the embodiments, after updating the bytecode file to the node corresponding to the message queue, the method further includes:

The loading of the bytecode file is completed by a hot loader.

In one embodiment, the pushing the operation and maintenance message to the message queue of each node on the blockchain includes:

Push the operation and maintenance message to the message queue through the oracle;

In the case that the operation and maintenance message fails to be pushed, the operation and maintenance message is reissued through the oracle machine until the operation and maintenance message is pushed successfully.

In one embodiment, updating the on-chain configuration file on the blockchain according to the operation and maintenance request, and pushing the operation and maintenance message to the message queue of each node on the blockchain includes:

Update the on-chain configuration file on the blockchain according to the operation and maintenance request, and determine the execution node corresponding to the operation and maintenance request according to the on-chain configuration file;

Push the operation and maintenance message to the message queue of the execution node.

In the second aspect, the embodiments of the present application further provide a blockchain-based operation and maintenance system, the system includes an operation and maintenance system access party and a blockchain platform, and the operation and maintenance system access party is connected in a node manner Enter the blockchain platform and deploy smart contracts on the blockchain platform, and the operation and maintenance system access parties have their own message queues:

The smart contract is used to update the on-chain configuration file on the blockchain according to the operation and maintenance request of the access party of the operation and maintenance system, and push the operation and maintenance message to the message queue of each node on the blockchain. In the case that the operation and maintenance message is successfully pushed to the message queue, the operation and maintenance message pushed to the message queue of each node on the blockchain is recorded on the blockchain in the form of a transaction, wherein the The on-chain configuration file corresponds to the operation and maintenance request, and the operation and maintenance message corresponds to the operation and maintenance request;

The operation and maintenance system access party obtains the operation and maintenance message from the message queue, and performs the operation and maintenance operation corresponding to the operation and maintenance message on the node according to the operation and maintenance message.

In one embodiment, the smart contract includes a data processing module and a message push module:

The data processing module is used to update the bytecode file and the operation and maintenance record on the blockchain according to the operation and maintenance request of the operation and maintenance system access party;

The message pushing module is configured to push the operation and maintenance message to the message queue, wherein the operation and maintenance message includes the operation and maintenance record.

In a third aspect, an embodiment of the present application provides a computer device, including a memory, a processor, and a computer program stored in the memory and running on the processor, the processor implementing the above-mentioned region-based program when executing the computer program The operation and maintenance method of the blockchain.

In a fourth aspect, an embodiment of the present application further provides a computer-readable storage medium on which a computer program is stored, and when the computer program is executed by a processor, the above-mentioned blockchain-based operation and maintenance method is implemented.

The above blockchain-based operation and maintenance method, system, computer equipment and storage medium update the on-chain configuration file on the blockchain according to the operation and maintenance request, and push the operation and maintenance message to the message queue of each node on the blockchain. When the operation and maintenance message is successfully pushed to the message queue, the push operation is recorded on the blockchain as a transaction; the operation and maintenance message is obtained from the message queue, and the operation and maintenance message corresponding to the operation and maintenance message is executed on the node according to the operation and maintenance message. The operation and maintenance operation, through the consensus among the blockchain nodes, realizes that one operation and maintenance operation takes effect on multiple systems at the same time, and realizes the credit endorsement of the whole process to ensure the consistency and security of the operation and maintenance version.

Description of drawings

The drawings described herein are used to provide further understanding of the present application and constitute a part of the present application. The schematic embodiments and descriptions of the present application are used to explain the present application and do not constitute an improper limitation of the present application. In the attached image:

1 is an application scenario diagram of a blockchain-based operation and maintenance method according to an embodiment of the present application;

2 is a flowchart of a blockchain-based operation and maintenance method according to an embodiment of the present application;

Fig. 3 is a processing flow chart of operation and maintenance records in the blockchain-based operation and maintenance method according to an embodiment of the present application;

4 is a schematic structural diagram of a blockchain-based operation and maintenance system according to an embodiment of the present application;

5 is a schematic diagram of the architecture of a blockchain-based operation and maintenance system according to an optional embodiment of the present application;

6 is a flowchart of a blockchain-based operation and maintenance method according to an optional embodiment of the present application;

FIG. 7 is a schematic structural diagram of a blockchain-based operation and maintenance computer device according to an embodiment of the present application.

Detailed ways

In order to make the objectives, technical solutions and advantages of the present application clearer, the present application will be described and illustrated below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present application, but not to limit the present application. Based on the embodiments provided in the present application, all other embodiments obtained by those of ordinary skill in the art without creative work fall within the protection scope of the present application.

Obviously, the accompanying drawings in the following description are only some examples or embodiments of the present application. For those of ordinary skill in the art, the present application can also be applied to the present application according to these drawings without any creative effort. other similar situations. In addition, it will also be appreciated that while such development efforts may be complex and lengthy, for those of ordinary skill in the art to which the present disclosure pertains, the techniques disclosed in this application Some changes in design, manufacture or production based on the content are only conventional technical means, and it should not be understood that the content disclosed in this application is not sufficient.

Reference in this application to an "embodiment" means that a particular feature, structure, or characteristic described in connection with the embodiment can be included in at least one embodiment of the application. The appearances of the phrase in various places in the specification are not necessarily all referring to the same embodiment, nor a separate or alternative embodiment that is mutually exclusive of other embodiments. It is explicitly and implicitly understood by those of ordinary skill in the art that the embodiments described in this application may be combined with other embodiments without conflict.

Unless otherwise defined, the technical or scientific terms involved in this application shall have the usual meanings understood by those with ordinary skill in the technical field to which this application belongs. Words such as "a", "an", "an", "the" and the like mentioned in this application do not denote a quantitative limitation, and may denote the singular or the plural. The terms "comprising", "comprising", "having" and any of their variants referred to in this application are intended to cover non-exclusive inclusion; for example, a process, method, system, product or process comprising a series of steps or modules (units) The apparatus is not limited to the steps or units listed, but may further include steps or units not listed, or may further include other steps or units inherent to the process, method, product or apparatus. Words like "connected," "connected," "coupled," and the like referred to in this application are not limited to physical or mechanical connections, but may include electrical connections, whether direct or indirect. The "plurality" referred to in this application refers to two or more. "And/or" describes the association relationship between associated objects, indicating that there can be three kinds of relationships. For example, "A and/or B" can mean that A exists alone, A and B exist at the same time, and B exists alone. The character "/" generally indicates that the associated objects are an "or" relationship. The terms "first", "second", "third", etc. involved in this application are only to distinguish similar objects, and do not represent a specific order for the objects.

The blockchain is a distributed database, and the data stored by each node participating in the blockchain behavior maintains data consistency through consensus. In order to facilitate the understanding of the blockchain network in the file storage system of this application, the blockchain technology adopted in this application will be illustrated first. In some embodiments, the electronic device runs the blockchain technology to become a node of the blockchain network, and the blockchain platform infrastructure includes a blockchain presentation layer, an application layer, a service layer, and a blockchain core support module.

Among them, the presentation layer is used to display system functions, and then realize user interaction. Each file subject can log in to the interface displayed by the corresponding presentation layer through the system client to access the application layer and obtain information resources, including registration interface, operation execution interface, query interface, application management interface, administrator interface, etc. The application layer is used to display the specific functions of the blockchain network and is an important part of file storage. It can be divided into user management, permission control, and directory management according to different functions. The service layer is used to effectively integrate and manage application-related functions through distributed servers, such as user registration, user identity management, encryption and decryption services, distributed ledger services, smart contract services, and data management services. The core support modules of the blockchain include data layer, network layer, consensus layer and contract layer. Among them, the data layer is used to encapsulate the underlying data blocks and related technologies such as data encryption and time stamping. The network layer encapsulates the P2P networking mode, message dissemination protocol and data verification mechanism of the blockchain network system, so that each node has equal status and is connected and interacted with each other in a flat topology, with distributed, autonomous, open Features such as free entry and exit. Every node in the blockchain network can participate in the verification and accounting process of the block data. Only when the block data is verified by most of the nodes in the entire network can it be recorded in the blockchain. The decentralized design of blockchain ensures that file data cannot be tampered with or forged. The consensus layer encapsulates a method to quickly complete consensus in a topology network with highly decentralized decision-making power to participate in the consensus mechanism of the blockchain network. The contract layer encapsulates the contract code of the data access policy. When the conditions in the contract code are triggered, the corresponding transaction is automatically executed, and the corresponding data can be accessed through the corresponding access conditions specified in the contract content.

FIG. 1 is an application scenario diagram of the blockchain-based operation and maintenance method according to an embodiment of the present application. The blockchain-based operation and maintenance method provided by the present application can be applied to the application environment shown in FIG. 1 . The blockchain network 10 includes an operation and maintenance requester node 12, a first node 14 and a second node 16, and the first node 14, the second node 16 and the operation and maintenance requester node 12 are all access parties of the unified operation and maintenance system. According to the data consistency characteristics of the blockchain, all nodes on the blockchain network 10 share all source code data of the operation and maintenance system. The operation and maintenance requester node 12 has operation authority such as uploading, editing, adding or deleting source code data to the blockchain network 10 . The blockchain network 10 updates the on-chain configuration file on the blockchain according to the operation and maintenance request of the operation and maintenance requester node 12, and pushes the operation and maintenance messages to the operation and maintenance requester node 12, the first node 14 and the operation and maintenance requester node 12 on the blockchain respectively. The message queue of the second node 16 records the push operation on the blockchain network 10 in the form of a transaction when the operation and maintenance message is successfully pushed to the message queue; each node of the blockchain network 10 obtains from the message queue Operation and maintenance messages, and perform operation and maintenance operations corresponding to the operation and maintenance messages on the node according to the operation and maintenance messages. The above-mentioned operation and maintenance requester node 12 , the first node 14 and the second node 16 may specifically be any electronic device, such as a server, a mobile phone, a computer, a tablet computer, and the like. It can be understood that, the above-mentioned operation and maintenance requester node 12, the first node 14 and the second node 16 can communicate with each other. The operation and maintenance requester node may include a file node, the first node may include a user node, and the second node may include an accounting node. In addition, the distinction between the above nodes is determined according to the identity information logged in through the node. In some embodiments, the above blockchain is a private blockchain or a consortium blockchain, and the story is first completed on the blockchain platform. For registration, the corresponding subjects of the above nodes need to complete the registration on the blockchain platform in advance, and obtain the corresponding public and private keys.

In one embodiment, FIG. 2 is a flowchart of a blockchain-based operation and maintenance method according to an embodiment of the present application, which provides a blockchain-based operation and maintenance method, which is applied to the area in FIG. 1 . The blockchain network 10 is used as an example to illustrate, including the following steps:

Step S210: Update the on-chain configuration file on the blockchain according to the operation and maintenance request, and push the operation and maintenance message to the message queue of each node on the blockchain. All access parties of the unified operation and maintenance system access the blockchain network in the form of nodes, and all nodes have all the source code data of the unified operation and maintenance system. Optionally, the source code data is written into the contract ledger by the script calling the smart contract during initialization. In addition, each node needs to build its own message queue service. The node acts as a message producer to push messages to the message queue, and the unified operation and maintenance service access party acts as a message consumer to subscribe to the message queue. As an application that performs operations on the blockchain, the smart contract updates the on-chain configuration file on the blockchain according to the update or modification in the operation and maintenance request when it receives an external operation and maintenance request. The content of the operation and maintenance request generates an operation and maintenance message, and pushes the operation and maintenance message to the message queue of each access party of the unified operation and maintenance system. Each access party of the above unified operation and maintenance system may be each terminal of the same system, or may be access parties of different systems that are applied to the same operation and maintenance management logic but are physically isolated.

Step S220: In the case that the operation and maintenance message is successfully pushed to the message queue, record the operation and maintenance message to the message queue of each node on the blockchain in transaction form on the blockchain. After confirming that the operation and maintenance message has been successfully sent to the message queue of each node, the consensus and placement of on-chain transactions are carried out, and written into the blockchain ledger to ensure that the message queue service of each node has completed the placement of the message. The contract and blockchain consensus mechanism carry out credit endorsement for the operation and maintenance process. Optionally, if the operation and maintenance message is not successfully sent, the transaction is rolled back.

Step S230: Obtain the operation and maintenance message from the message queue, and perform the operation and maintenance operation corresponding to the operation and maintenance message on the node according to the operation and maintenance message. Each operation and maintenance system access node subscribes to the messages in the message queue, obtains the operation and maintenance message from the message queue when receiving the message, and executes the operation according to the operation and maintenance operation indicated in the operation and maintenance message. For example, if the operation and maintenance request requires the unified shutdown of all the operation and maintenance system access parties on the chain, the blockchain sends a shutdown command, and the access end will receive the operation and maintenance message indicating the shutdown. When the configuration information corresponding to the request is at the administrator level, all clients accessing the blockchain will shut down the system.

Through steps S210 to S230, based on the characteristics of the blockchain platform, combined with the message queue to achieve unified operation and maintenance management of multiple systems, since the system time in the blockchain network is unified for each node, the transaction placement time is for each node. The nodes are also consistent, which improves the time consistency of the operation and maintenance system; at the same time, the smart contract and blockchain consensus mechanism are used to endorse the operation and maintenance process, which improves the security and reliability of the operation and maintenance process.

In one embodiment, when the operation and maintenance request is a version update, the blockchain platform updates the on-chain configuration file on the blockchain according to the operation and maintenance request, and receives the uploaded updated bytecode file and saves it to the block On the chain, each operation and maintenance system access node obtains the operation and maintenance message from the message queue, obtains the updated bytecode file from the blockchain according to the operation and maintenance message, and replaces the original on the node with the updated bytecode file. The updated bytecode file is loaded to complete the update.

In one embodiment, when the operation and maintenance request is a version rollback, since the blockchain will save all files and data on the chain in history, it only needs to obtain the bytecode version number that needs to be rolled back, and the node can download Obtain the bytecode file of the lower version corresponding to the version on the blockchain, replace the bytecode file of the higher version on the node with the bytecode file of the lower version, and load the bytecode file of the lower version. Implement version fallback. Optionally, the above version rollback is not necessarily a rollback to the previous version of the existing version, but may be any historical version.

In an embodiment, the access node of the operation and maintenance system can also be downgraded according to its own needs. For example, the access side of the operation and maintenance system has a preset rollback process, and the process indicates that if the update fails during the update process, the node automatically rolls back to the specified version. When the rollback process is triggered, the node will obtain the bytecode corresponding to the rollback version number from the blockchain according to the rollback version number preset in the rollback process, and update the rollback version. The bytecode is loaded to this node, so as to realize the spontaneous version fallback of the access node.

In one embodiment, the on-chain configuration file on the blockchain is updated according to the operation and maintenance request, and the execution node corresponding to the operation and maintenance request is determined according to the on-chain configuration file; the operation and maintenance message is pushed to the message queue of the execution node. In this embodiment, an execution node that performs an operation and maintenance operation may be specified in a configuration file through an operation and maintenance request. If the instruction of the configuration information is a version update, and not all access parties will be updated at the same time, only the access parties indicated in the configuration information will be updated, and other nodes do not need to be updated. In the process of updating, the update needs to be obtained from the blockchain. The manner provided in this embodiment makes the operation and maintenance more flexible.

In one embodiment, in the case where the blockchain also includes operation and maintenance records, FIG. 3 is a flowchart of the processing of operation and maintenance records in the blockchain-based operation and maintenance method according to an embodiment of the present application, as shown in FIG. 3 . As shown, the blockchain-based operation and maintenance method includes the following steps:

Step S310: Update the on-chain configuration file and the operation and maintenance record on the blockchain according to the operation and maintenance request, and push the operation and maintenance message to the message queue of each node on the blockchain. In addition to all the source code data of the unified operation and maintenance system, the blockchain also stores the operation and maintenance records for the source code data. The operation object, operation content, etc. corresponding to each operation and maintenance operation may be recorded in the above operation and maintenance record. When the smart contract receives an external operation and maintenance request, it updates the on-chain configuration file stored on the blockchain according to the update or modification content in the operation and maintenance request, while maintaining the corresponding operation and maintenance record. In addition, the operation and maintenance message pushed to the message queue of each node also includes the operation and maintenance record corresponding to the operation and maintenance message.

Step S320: In the case that the operation and maintenance message is successfully pushed to the message queue, record the push operation on the blockchain in the form of a transaction. As mentioned above, the operation and maintenance message is pushed to the message queue of each node. After confirming that the operation and maintenance message has been successfully sent to the message queue of each node, the consensus and placement of on-chain transactions are carried out and written into the blockchain ledger.

Step S330: Obtain the operation and maintenance message from the message queue, and perform the operation and maintenance operation corresponding to the operation and maintenance message on the node according to the operation and maintenance record in the operation and maintenance message.

In steps S310 to S330, not only source code data but also operation and maintenance records are stored on the blockchain. As far as the blockchain platform is concerned, the process of operation and maintenance can be better managed and tracked, and the security of operation and maintenance can be improved. ; As far as the access party of the operation and maintenance system is concerned, in the case of frequent or complex operation and maintenance operations, the updated content can be accurately obtained from the blockchain according to the operation and maintenance records in the operation and maintenance message, so as to prevent the update of the updated version. Obfuscation further improves the consistency and security of operation and maintenance.

In one embodiment, the operation and maintenance record includes an identifier, a system type, and an operation and maintenance policy. The identifier is unique and is used to indicate the operation and maintenance operation uniquely corresponding to the operation and maintenance record, the system type indicates the system type corresponding to the operation and maintenance operation, and the operation and maintenance strategy can be customized. For example, if the operation and maintenance operation is an urgent bug fix, an automatic pull update is performed; if the operation and maintenance operation is a regular update, the system administrator decides whether to perform it. The operation and maintenance strategy in the smart contract is initialized at the beginning of the construction of the blockchain platform, and the operation and maintenance strategy of each application server, that is, the unified operation and maintenance service access party, can be customized according to the operation and maintenance strategy of the blockchain. The contents included in the above operation and maintenance records can improve the accuracy and flexibility of the operation and maintenance process.

In one embodiment, the smart contract pushes operation and maintenance messages to the message queues of each node through the oracle machine. The function of the oracle machine is to write external information into the blockchain to complete the data exchange between the blockchain and the real world. It allows certain smart contracts to respond to the uncertain external world, and is the way for smart contracts to interact with the outside world, and it is also the interface between the blockchain and the real world. The smart contract runs in the sandbox environment and does not directly interact with external data. The message push process uses the oracle to interact with the outside world. After confirming that the message is successfully sent to the node message queue, the consensus and placement of the on-chain transaction are carried out, and written to the area. Blockchain ledger. In addition, if the operation and maintenance message fails to be pushed, the operation and maintenance message will be re-sent through the oracle machine until the operation and maintenance message is pushed successfully. In this embodiment, the operation and maintenance message push status is obtained through the oracle machine, which can better ensure that the operation and maintenance message is sent to the message queue of each node, so as to better ensure that the operation and maintenance process is executed on each node. Improve the consistency of operation and maintenance. And the message push process uses the oracle machine to interact with the outside world. If the message queue of a node fails to produce messages, the oracle machine re-sends the failed message. The purpose is to ensure that the message queue service of each node has completed the message placement. , so that each access party of the operation and maintenance system can complete the operation and maintenance operation.

In one embodiment, after the node obtains the bytecode version that needs to be updated or the rolled-back bytecode version, the loading of the bytecode file is completed by the hot loader. The hot loader of the code means that the changed code can take effect without restarting the service. The hot loader can significantly improve the efficiency of development and debugging. The system realizes non-stop maintenance through hot loading technology. The system only needs to pull the latest bytecode and replace the bytecode file in its running container, and use the code hot loader to load it into the running environment to complete the maintenance and upgrade process.

In one embodiment, FIG. 4 is a schematic structural diagram of a blockchain-based operation and maintenance system implemented according to the present application. As shown in FIG. 4 , a blockchain-based operation and maintenance system 40 is provided, and the system 40 includes The operation and maintenance system access party 42 and the blockchain platform 44. The operation and maintenance system access party 42 accesses the blockchain platform 44 in the form of a node and deploys a smart contract on the blockchain platform 44. The operation and maintenance system The access party has its own message queue 46;

The smart contract is used to update the on-chain configuration file on the blockchain according to the operation and maintenance request of the operation and maintenance system access party 42 , and push the operation and maintenance message to the message queue 46 , in the case that the operation and maintenance message is successfully pushed to the message queue 46 Next, the push operation is recorded on the blockchain in the form of a transaction, wherein the configuration file on the chain corresponds to the operation and maintenance request, and the operation and maintenance message corresponds to the operation and maintenance request;

The operation and maintenance system access party 42 obtains the operation and maintenance message from the message queue 46, and performs the operation and maintenance operation corresponding to the operation and maintenance message on the node according to the operation and maintenance message.

In one embodiment, the smart contract includes a data processing module and a message push module: the data processing module is used to update the on-chain configuration file and the operation and maintenance record on the blockchain according to the operation and maintenance request of the operation and maintenance system access party 42; the message The push module is used to push the operation and maintenance message to the message queue 46, wherein the operation and maintenance message includes the operation and maintenance record.

It should be noted that Figure 4 only shows the situation that the blockchain-based operation and maintenance system includes three operation and maintenance system access parties, three message queues, and three nodes on the blockchain platform. In an application, there may be more or less than three parties. And in some embodiments, the system may not include the operation and maintenance system access party 42, and is only used for the operation and maintenance of blockchain nodes. The operation and maintenance system access party 42 may be various forms of third-party operation and maintenance tools, operation and maintenance platforms, or operation and maintenance systems. For the specific definition of the operation and maintenance system based on the blockchain, please refer to the definition of the operation and maintenance method based on the blockchain above, which will not be repeated here. Each module in the above-mentioned blockchain-based operation and maintenance system can be implemented in whole or in part by software, hardware and combinations thereof. The above modules can be embedded in or independent of the processor in the computer device in the form of hardware, or stored in the memory in the computer device in the form of software, so that the processor can call and execute the operations corresponding to the above modules.

The above blockchain-based operation and maintenance system updates the on-chain configuration file on the blockchain according to the operation and maintenance request, and pushes the operation and maintenance message to the message queue of each node on the blockchain, wherein the on-chain configuration file and the operation and maintenance The operation and maintenance message corresponds to the request, and the operation and maintenance message corresponds to the operation and maintenance request; when the operation and maintenance message is successfully pushed to the message queue, the push operation is recorded on the blockchain in the form of a transaction; the operation and maintenance message is obtained from the message queue. message, and update the node configuration file corresponding to the operation and maintenance message on the node according to the operation and maintenance message. Through the consensus among the blockchain nodes, one operation and maintenance operation can take effect on multiple systems at the same time, and the credit endorsement of the whole process is realized. Ensure the consistency and security of the operation and maintenance version.

The embodiments of the present application are described and illustrated below by using optional embodiments. Fig. 5 is a schematic diagram of the architecture of a blockchain-based operation and maintenance system according to an optional embodiment of the present application. As shown in Fig. 5, the underlying blockchain platform needs to build multiple nodes, and all access parties of the unified operation and maintenance system use nodes as nodes. way to access. All the nodes have all the source code data of the application system. The source code data is written into the contract ledger by the script calling the smart contract during initialization. The node side needs to build its own message queue service. The node acts as a message producer to push messages to the message queue, and the unified operation and maintenance service access party acts as a message consumer to subscribe to the message queue. As an application that performs operations on the blockchain, smart contracts are divided into two modules in design. Including data processing and message push modules. The data processing module receives and processes external operation and maintenance requests and code bytecode files required for operation and maintenance. Specifically, the data processing module updates the source code file, that is, the bytecode file, on the chain according to the external request, and maintains the corresponding operation and maintenance records. The operation and maintenance records include unique identifiers, system types, and operation and maintenance strategies. The message push module monitors the behavior of the data processing module, and pushes the operation and maintenance messages according to the newly added operation and maintenance records of the data processing module. The smart contract runs in the sandbox environment and does not directly interact with external data. The message push process uses the oracle to interact with the outside world. After confirming that the message is successfully sent to the node message queue, the consensus and placement of the on-chain transaction are carried out, and written to the area. Blockchain ledger, otherwise the transaction is rolled back. If a node fails to produce a message, the oracle machine reissues the failed message, and finally ensures that the message queue service of each node completes the message placement. The access party consumes the messages in its message queue through the unified operation and maintenance subscription service, pulls the latest code bytecode file on the chain according to the system type and operation and maintenance strategy in the operation and maintenance message, and updates the code bytecode file in the running container , and use the hot loader to complete the hot loading of bytecode files to achieve the ultimate goal of operation and maintenance. The operation and maintenance strategy can be customized. If it is an emergency vulnerability patching bugfix, an automatic pull update is performed. If it is a regular update, the system administrator decides whether to perform it. The operation and maintenance strategy in the smart contract is initialized at the beginning of the construction of the blockchain platform. The operation and maintenance strategy of each application server, that is, the unified operation and maintenance service access party, can be customized according to the operation and maintenance strategy of the blockchain.

Based on the above architecture, FIG. 6 is a flowchart of a blockchain-based operation and maintenance method according to an optional embodiment of the present application. As shown in FIG. 6 , the blockchain-based operation and maintenance process includes the following steps:

Step S610: The smart contract obtains a unified operation and maintenance request. A unified operation and maintenance request is initiated from outside the blockchain platform.

Step S620: The smart contract executes data processing logic. Update on-chain source code bytecode files and maintain operation and maintenance records.

Step S630: The smart contract publishes the operation and maintenance message to the message queue through the oracle machine. After the smart contract completes data processing, it publishes operation and maintenance messages to the message queue corresponding to the server where each node is located through the oracle machine.

Step S640: Determine whether the operation and maintenance message is successfully published.

Step S650 : in the case that the publishing of the operation and maintenance message fails, the operation and maintenance operation is rolled back.

Step S660: In the case that the operation and maintenance message is published successfully, a node consensus is performed, and the transaction is placed. After the oracle machine determines that the node corresponding to the message queue receives the message, each node reaches a consensus, synchronizes the transaction data, and completes the transaction.

Step S670: the access party consumes the message from the message queue. The node access party, that is, the unified operation and maintenance service access party, consumes messages and pulls the latest bytecode files on the chain.

Step S680: The application system container updates the bytecode file and performs hot loading. The application system container replaces the existing bytecode file in the system running container with the latest bytecode file obtained on the chain, and uses the hot loader to hot load the bytecode file, and finally completes the entire operation and maintenance process.

The blockchain-based operation and maintenance method in the above-mentioned optional embodiment realizes unified operation and maintenance management of multiple systems, and physical isolation of multiple systems. It is effective for multiple systems, and based on this, the credit endorsement of the entire process is realized to ensure the consistency of operation and maintenance versions, and at the same time, historical updates can be traced back and easily restored. Through this technology, the system can be maintained without downtime. The system only needs to pull the latest bytecode and replace the bytecode file in its running container, and use the code hot loader to load it into the running environment to complete the maintenance and upgrade process. Based on the characteristics of the blockchain platform, combined with message queue and code file hot loading technology to achieve unified operation and maintenance management of multiple systems, use smart contracts and blockchain consensus mechanism to endorse the operation and maintenance process, and finally realize the blockchain-based unified operation and maintenance plan.

It should be noted that the above optional embodiments are mainly aimed at the operation and maintenance of external application systems, but the method provided in this application is not limited to the operation and maintenance scenarios of external application systems in the above optional embodiments, for example, code hot loading The controller can point to the blockchain node in the reverse direction, so as to realize the self-update of the blockchain node. In the distributed network of blockchain nodes, since enterprises and institutions are isolated from each other, in the process of mutual cooperation, there are constantly new access parties and new business accesses, so this solution can also be provided to the blockchain Chain nodes respond to self-update of new business requirements. In addition, the method provided by this application can also be combined with other systems with operation and maintenance requirements, and the modification and improvement of the scheme made under the premise of not departing from the concept of this application all belong to the protection scope of this application.

It should be understood that although the steps in the flowcharts in FIGS. 2 to 6 are sequentially displayed in accordance with the arrows, these steps are not necessarily executed in the order indicated by the arrows. Unless explicitly stated herein, the execution of these steps is not strictly limited to the order, and these steps may be performed in other orders. Moreover, at least a part of the steps in FIG. 2 to FIG. 6 may include multiple sub-steps or multiple stages. These sub-steps or stages are not necessarily executed and completed at the same time, but may be executed at different times. These sub-steps or stages may be executed at different times. The order of execution of the stages is also not necessarily sequential, but may be performed alternately or alternately with other steps or sub-steps of other steps or at least a portion of a stage.

In one embodiment, a computer device is provided, and the computer device can be a terminal. FIG. 7 is a schematic structural diagram of a blockchain-based operation and maintenance computer device according to an embodiment of the present application. As shown in FIG. 7 , its internal The structure diagram can be shown in Figure 7. The computer equipment includes a processor, memory, a network interface, a display screen, and an input device connected by a system bus. Among them, the processor of the computer device is used to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium, an internal memory. The nonvolatile storage medium stores an operating system and a computer program. The internal memory provides an environment for the execution of the operating system and computer programs in the non-volatile storage medium. The network interface of the computer device is used to communicate with an external terminal through a network connection. The computer program is executed by the processor to implement a blockchain-based operation and maintenance method. The display screen of the computer equipment may be a liquid crystal display screen or an electronic ink display screen, and the input device of the computer equipment may be a touch layer covered on the display screen, or a button, a trackball or a touchpad set on the shell of the computer equipment , or an external keyboard, trackpad, or mouse.

Those skilled in the art can understand that the structure shown in FIG. 7 is only a block diagram of a partial structure related to the solution of the present application, and does not constitute a limitation on the computer equipment to which the solution of the present application is applied. Include more or fewer components than shown in the figures, or combine certain components, or have a different arrangement of components.

In one embodiment, a computer device is provided, including a memory, a processor, and a computer program stored in the memory and running on the processor, and the processor implements the above blockchain-based operation and maintenance method when the computer program is executed .

The above-mentioned blockchain-based operation and maintenance computer equipment updates the on-chain configuration file on the blockchain according to the operation and maintenance request, and pushes the operation and maintenance message to the message queue of each node on the blockchain. corresponding to the maintenance request, and the operation and maintenance message corresponds to the operation and maintenance request; when the operation and maintenance message is successfully pushed to the message queue, the push operation is recorded on the blockchain in the form of a transaction; the operation and maintenance message is obtained from the message queue. maintenance message, and execute the operation and maintenance operation corresponding to the operation and maintenance message on the node according to the operation and maintenance message. Through the consensus among the blockchain nodes, one operation and maintenance operation can take effect on multiple systems at the same time, and the credit of the whole process is realized. Endorsement to ensure the consistency and security of the operation and maintenance version.

In one embodiment, a computer-readable storage medium is provided, on which a computer program is stored, and when the computer program is executed by a processor, the foregoing blockchain-based operation and maintenance method is implemented.

The above-mentioned blockchain-based operation and maintenance computer-readable storage medium updates the on-chain configuration file on the blockchain according to the operation and maintenance request, and pushes the operation and maintenance message to the message queue of each node on the blockchain, wherein the on-chain configuration The file corresponds to the operation and maintenance request, and the operation and maintenance message corresponds to the operation and maintenance request; if the operation and maintenance message is successfully pushed to the message queue, the push operation is recorded on the blockchain in the form of a transaction; Obtain the operation and maintenance message from the blockchain, and execute the operation and maintenance operation corresponding to the operation and maintenance message on the node according to the operation and maintenance message. It takes effect and realizes the credit endorsement of the whole process to ensure the consistency and security of the operation and maintenance version.

Those of ordinary skill in the art can understand that all or part of the processes in the methods of the above embodiments can be implemented by instructing relevant hardware through a computer program, and the computer program can be stored in a non-volatile computer-readable storage In the medium, when the computer program is executed, it may include the processes of the above-mentioned method embodiments. Wherein, any reference to memory, storage, database or other medium used in the various embodiments provided in this application may include non-volatile and/or volatile memory. Nonvolatile memory may include read only memory (ROM), programmable ROM (PROM), electrically programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM), or flash memory. Volatile memory may include random access memory (RAM) or external cache memory. By way of illustration and not limitation, RAM is available in various forms such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDRSDRAM), enhanced SDRAM (ESDRAM), synchronous chain Road (Synchlink) DRAM (SLDRAM), memory bus (Rambus) direct RAM (RDRAM), direct memory bus dynamic RAM (DRDRAM), and memory bus dynamic RAM (RDRAM), etc.

The technical features of the above embodiments can be combined arbitrarily. In order to make the description simple, all possible combinations of the technical features in the above embodiments are not described. However, as long as there is no contradiction in the combination of these technical features It is considered to be the range described in this specification.

The above-mentioned embodiments only represent several embodiments of the present application, and the descriptions thereof are specific and detailed, but should not be construed as a limitation on the scope of the invention patent. It should be pointed out that for those skilled in the art, without departing from the concept of the present application, several modifications and improvements can be made, which all belong to the protection scope of the present application. Therefore, the scope of protection of the patent of the present application shall be subject to the appended claims.

Claims

A blockchain-based operation and maintenance method, characterized in that the method includes:

Update the on-chain configuration file on the blockchain according to the operation and maintenance request, and push the operation and maintenance message to the message queue of each node on the blockchain, wherein the on-chain configuration file corresponds to the operation and maintenance request, so The operation and maintenance message corresponds to the operation and maintenance request;

In the case that the operation and maintenance message is successfully pushed to the message queue, record the push operation and maintenance message to the message queue of each node on the blockchain in the form of a transaction on the blockchain;

The operation and maintenance message is acquired from the message queue, and an operation and maintenance operation corresponding to the operation and maintenance message is performed on the node according to the operation and maintenance message.
The method of claim 1, wherein the method further comprises:

Update the on-chain configuration file and the operation and maintenance record on the blockchain according to the operation and maintenance request, and push the operation and maintenance message to the message queue of each node on the blockchain, wherein the operation and maintenance message includes the operation and maintenance records;

The operation and maintenance message is acquired from the message queue, and an operation and maintenance operation corresponding to the operation and maintenance message is performed on the node according to the operation and maintenance record in the operation and maintenance message.
The method of claim 2, wherein the operation and maintenance record includes an identifier, a system type, and an operation and maintenance policy.
The method according to claim 1, wherein, when the operation and maintenance request is a version update, the method further comprises:

Update the on-chain configuration file on the blockchain according to the operation and maintenance request, upload the bytecode file to the blockchain, and push the operation and maintenance message to the messages of each node on the blockchain a queue, wherein the bytecode file corresponds to the operation and maintenance request;

In the case that the operation and maintenance message is successfully pushed to the message queue, record the message queue that pushes the operation and maintenance message to each node on the blockchain in the form of a transaction on the blockchain ;

Obtain the operation and maintenance message from the message queue, obtain the bytecode file from the blockchain according to the operation and maintenance message, and update the bytecode file to the node.
The method according to claim 4, wherein, when the operation and maintenance request is a version rollback, the method further comprises:

Obtain the rollback version number of the operation and maintenance request, and push the operation and maintenance message to the message queue of each node on the blockchain, where the corresponding bytecode file is stored in the blockchain version number;

Obtain the operation and maintenance message from the message queue, obtain the fallback version bytecode file corresponding to the rollback version from the blockchain according to the operation and maintenance message, and store the fallback version A bytecode file is updated to the node corresponding to the message queue.
The method of claim 4, wherein the method further comprises:

When the preset rollback process is triggered, the rollback version number is obtained according to the rollback process, the rollback version bytecode file corresponding to the rollback version is obtained from the blockchain, and The fallback version bytecode file is updated to the node corresponding to the message queue.
The method according to claim 4, wherein after updating the bytecode file to the node corresponding to the message queue, the method further comprises:

The loading of the bytecode file is completed by a hot loader.
The method according to claim 1, wherein the pushing the operation and maintenance message to the message queue of each node on the blockchain comprises:

Push the operation and maintenance message to the message queue through the oracle;

In the case that the operation and maintenance message fails to be pushed, the operation and maintenance message is reissued through the oracle machine until the operation and maintenance message is pushed successfully.
The method according to claim 1, wherein the updating the on-chain configuration file on the blockchain according to the operation and maintenance request, and pushing the operation and maintenance message to the message queue of each node on the blockchain comprises:

Update the on-chain configuration file on the blockchain according to the operation and maintenance request, and determine the execution node corresponding to the operation and maintenance request according to the on-chain configuration file;

Push the operation and maintenance message to the message queue of the execution node.
A blockchain-based operation and maintenance system, characterized in that the system includes an operation and maintenance system access party and a blockchain platform, and the operation and maintenance system access party accesses the blockchain in the form of a node platform and deploy smart contracts on the blockchain platform, and the operation and maintenance system access parties have their own message queues:

The smart contract is used to update the on-chain configuration file on the blockchain according to the operation and maintenance request of the access party of the operation and maintenance system, and push the operation and maintenance message to the message queue of each node on the blockchain, where In the case that the operation and maintenance message is successfully pushed to the message queue, the operation and maintenance message pushed to the message queue of each node on the blockchain is recorded on the blockchain in the form of a transaction, wherein the The on-chain configuration file corresponds to the operation and maintenance request, and the operation and maintenance message corresponds to the operation and maintenance request;

The operation and maintenance system access party obtains the operation and maintenance message from the message queue, and performs the operation and maintenance operation corresponding to the operation and maintenance message on the node according to the operation and maintenance message.
The system according to claim 10, wherein the smart contract comprises a data processing module and a message push module:

The data processing module is configured to update the bytecode file and the operation and maintenance record on the blockchain according to the operation and maintenance request of the operation and maintenance system access party;

The message push module is configured to push the operation and maintenance message to the message queue, wherein the operation and maintenance message includes the operation and maintenance record.
A computer device, comprising a memory, a processor, and a computer program stored in the memory and running on the processor, characterized in that, when the processor executes the computer program, any one of claims 1 to 9 is implemented the steps of the method.
A computer-readable storage medium on which a computer program is stored, characterized in that, when the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 9 are implemented.