A distribution automation master station version management method and system based on process and blockchain
By adopting a process-based and blockchain-based version management method on the power distribution automation main site, the difficulties in software version management are solved, effective version tracking and auditing are achieved, and management efficiency and data security are improved.
Patent Information
- Application Number
- CN202010909188.7
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2020-09-02
- Publication Date
- 2024-11-22
- Estimated Expiration
- 2040-09-02
AI Technical Summary
The lack of effective technical means for the management of the main site software version of the power distribution automation automation, resulting in difficulties in the later management, defect removal and upgrade and maintenance of the main site.
Adopt the process-based version management method, and ensure the version by starting the approval process, repairing or upgrading the functional modules, generating software version data and broadcasting within the blockchain network, using blockchain technology to store and verify data to ensure the version Data integrity and traceability.
It realizes effective management of the software version of the power distribution automation main site, ensures the tracking, rollback and audit of version changes, and improves management efficiency and data security.
Smart Images

Figure CN112052033B_ABST
Abstract
Description
Technical Field
[0001] The present invention belongs to the field of distribution automation, and specifically relates to a distribution automation master station version management method based on processes and blockchain for distribution automation master station software version lifecycle management. Background Art
[0002] The distribution automation master station is the core of distribution automation. With the development of distribution automation, the distribution automation master station has been greatly developed and is committed to maintaining the stability of distribution automation. In the construction and maintenance of distribution automation in my country, the distribution automation master station is a key and core project. In the development of distribution automation, the importance of the distribution automation master station has been increased. On the one hand, it maintains the operation level of distribution automation; on the other hand, it guarantees the power supply quality of the distribution network system and strengthens the use of the distribution automation master station.
[0003] In some provincial power companies, multiple distribution automation master stations are deployed. The master stations come from different manufacturers, and the software versions of the same product from the same manufacturer in different locations are also different. The software version management of the master station lacks effective technical management methods, which brings great trouble to the subsequent master station management, troubleshooting, and upgrade and maintenance work. Summary of the invention
[0004] Purpose of the invention: In order to solve the problem of lack of effective management of distribution automation master station software versions, the present invention provides a distribution automation master station version management method and system based on processes and blockchain.
[0005] Technical solution: A distribution automation master station version management method based on process and blockchain, including the following steps:
[0006] Step 1: Start the approval process, notify the process approver of the corresponding process link to approve according to the pre-configured version upgrade process, and get the approval result. If the approval result is rejected, it will be terminated and wait for the next approval process to start; if the approval result is passed, go to step 2:
[0007] Step 2: Repair or upgrade the functional modules that need to be changed in response to the demand, form a new functional module to be released, determine the version number of the new functional module according to the correspondence between the new functional module and the original functional module, upgrade the master station functional module, archive the version upgrade of the distribution automation master station, and generate the distribution automation master station software version data;
[0008] Step 3: Broadcast the generated distribution automation master station software version data throughout the blockchain network, and nodes within the blockchain network receive the distribution automation master station software version data;
[0009] Step 4: The nodes within the blockchain network will process the functional module data files involved in this change in the received distribution automation master station software version data one by one.
[0010] Furthermore, the construction of the blockchain network includes:
[0011] Perform node initialization configuration for all parties involved in the version management of the distribution automation master station, organize each node into a blockchain network, uniquely identify each node in the blockchain network, perform structured processing on each node to generate new storage data; use the new storage data as the founding block and broadcast it throughout the blockchain network, and all nodes within the blockchain network store the data in the founding block.
[0012] Furthermore, the blockchain network is a private chain network.
[0013] Furthermore, the block structure stored in the blockchain network includes a block header and a block body; the data in the block header includes a version number, a random array and the signature information of the previous block; the data in the block body is composed of distribution automation master station software version data; the distribution automation master station software version data includes: the current version number of all functional modules of the distribution automation master station and the functional module file name corresponding to the version number, the applicant, the application time, the reason for application, the process approver of all process links, the approval time and the approval opinion.
[0014] Furthermore, the HASH value of the data in the function module file is used as the function module file name.
[0015] Furthermore, the step 3 specifically includes the following steps:
[0016] Broadcast the generated distribution automation master station software version data throughout the blockchain network;
[0017] Other nodes within the blockchain network receive the distribution automation master station software version data, and determine the node identity of the distribution automation master station software version data and the authenticity of the distribution automation master station software version data;
[0018] If the node broadcasting the information is a node within the blockchain network, the distribution automation master station software version data will be checked for integrity. If the check succeeds, the distribution automation master station software version data will be uploaded to the chain; if the check fails, the distribution automation master station software version data will not be uploaded to the chain;
[0019] If the node broadcasting the information is a node outside the blockchain network, the nodes in the blockchain network will reach a permission consensus through a consensus mechanism. If the permission of more than half of the nodes in the blockchain network is obtained, the node information of the broadcast version data will be added to the genesis block, and the distribution automation master station software version data will be checked for integrity. If the check is successful, the distribution automation master station software version data will be uploaded to the chain; if the permission consensus is not obtained or the integrity check of the distribution automation master station software version data fails, the distribution automation master station software version data will not be uploaded to the chain.
[0020] The present invention also discloses a distribution automation master station version management system based on process and blockchain, including:
[0021] The version upgrade approval system is used to complete the version upgrade process approval, function module version upgrade and version data generation based on workflow;
[0022] The blockchain system regards all parties involved in the version management of the distribution automation master station as nodes, which are organized by each node and used to broadcast the version data generated by the version upgrade approval system. Nodes within the scope of the blockchain system obtain the version data.
[0023] Furthermore, the version upgrade approval system includes:
[0024] The workflow sub-module is used to process the process data information generated during the version change of the distribution automation master station, and complete the version upgrade of the functional module and the generation of version data; the process data information includes the reason for the version upgrade of the distribution automation master station, the approvers involved in the approval, the testers of the distribution automation master station version, the final version information of the functional modules and sub-functional modules of the distribution automation master station after the upgrade, and the affected sub-functional module file data.
[0025] Furthermore, the workflow submodule includes:
[0026] The file management submodule is used to store the function module file data updated by the distribution automation master station, and uses the HASH value of the function module file data as the file name.
[0027] Furthermore, the blockchain system includes a blockchain sub-module, which is used to deploy multiple blockchain servers to form a private blockchain network and broadcast version data based on the blockchain communication protocol.
[0028] Beneficial effect: The present invention incorporates the maintenance process of the distribution automation master station version into the version management system, and adopts a workflow mechanism to approve the distribution automation master station software version upgrade process. The relevant departments involved in the distribution automation master station business will review and approve it in this management system. After all approval processes are passed and the affected modules of the distribution automation master station software are determined to have been upgraded, the information related to the change will be pushed to the internal private blockchain, ultimately achieving the purpose of tracking, rolling back and auditing the distribution automation master station software version changes. BRIEF DESCRIPTION OF THE DRAWINGS
[0029] Figure 1 It is a schematic diagram of the network structure of the version management system of the present invention;
[0030] Figure 2 It is a system workflow diagram of the present invention;
[0031] Figure 3 It is a block structure schematic diagram of the present invention. DETAILED DESCRIPTION
[0032] Now combined Figure 2 A distribution automation master station version management method based on process and blockchain of the present invention is described. The method comprises the following steps:
[0033] Step 1: Start the approval process, notify the process approvers of the corresponding process links to approve according to the pre-configured version upgrade process, and record the approval opinions and process status of the process approvers of each process link until the entire version upgrade process is approved and the approval result is obtained. If the approval result is rejected, it will be terminated and wait for the next approval process to start; if the approval result is passed, go to step 2:
[0034] This step is now explained as follows: This embodiment uses a workflow to complete the management of the version upgrade process of the distribution automation master station function module, that is, through a pre-configured approval process definition, which includes the content that needs to be filled in each link, the approval account of each link, and other information. After starting the approval process, the corresponding process link approver is notified for approval according to the process definition of the version process upgrade. The workflow submodule will record the approval opinions and process status of the process approver of each link until the entire process is successfully approved or rejected and terminated. The process that is rejected and terminated will not affect the version of the distribution automation master station. Therefore, the process that is rejected and terminated will not be broadcast to the blockchain network, and there is no need to generate this part of the data.
[0035] Step 2: Respond to the demand and perform bug fixes or function upgrades on the functional modules that need to be changed to form new functional modules to be released. Test the new functional modules in the production environment and determine the version number of the new functional modules according to the correspondence between the new functional modules and the original functional modules. Upgrade the master station functional modules, archive the version upgrade of the distribution automation master station, and generate the distribution automation master station software version data;
[0036] This step is described as follows: After the distribution automation master station version process upgrade requirements pass all approval links, the software manufacturer arranges developers to respond to the requirements to fix bugs or upgrade functions of existing functional modules. After the functional modules that have been changed are tested in the production environment, each changed module is upgraded according to the version number upgrade rules to complete the functional module upgrade in the production environment. The rejected and terminated processes will not affect the distribution automation master station version. Therefore, the rejected and terminated processes will not be broadcast to the blockchain network, and there is no need to generate this part of the data.
[0037] Step 3: Based on the communication protocol of blockchain, the generated distribution automation master station software version data is broadcasted in the entire blockchain network, and the nodes within the blockchain network receive the distribution automation master station software version data; and the identity of the node broadcasting the distribution automation master station software version data and the authenticity of the distribution automation master station software version data are determined through digital signature technology;
[0038] If the node broadcasting the information is a node within the blockchain network, the distribution automation master station software version data will be checked for integrity. If the check succeeds, the distribution automation master station software version data will be uploaded to the chain; if the check fails, the distribution automation master station software version data will not be uploaded to the chain;
[0039] If the node broadcasting the information is not a node within the blockchain network, the nodes in the blockchain network will reach a permission consensus through the consensus mechanism. If the permission of more than half of the nodes in the blockchain network is obtained, the node information of the broadcast information will be added to the genesis block, and the distribution automation master station software version data will be checked for integrity. If the check is successful, the distribution automation master station software version data will be uploaded to the chain; if the permission consensus is not obtained or the distribution automation master station software version data integrity check fails, the distribution automation master station software version data will not be uploaded to the chain;
[0040] The blockchain network mentioned above is now explained:
[0041] Blockchain is a new distributed technology. It is composed of blocks of transactions arranged in sequence, and chains are composed of blocks arranged in sequence. Blockchain has four technical characteristics: asymmetric encryption and authorization technology, distributed accounting network, smart contracts and consensus mechanism. The distributed network structure synchronizes data to the entire blockchain to ensure that the process is irreversible, while the consensus mechanism infinitely magnifies the cost of tampering with transaction records.
[0042] The blockchain network construction process of this embodiment is as follows: perform node initialization configuration on all parties involved in the version management of the distribution automation master station, organize each node into a blockchain, uniquely identify each node in the blockchain, perform structured processing on each node to generate new storage data; use the new storage data as the founding block and broadcast it within the entire blockchain, and all nodes within the blockchain range store the data in the founding block.
[0043] Step 3 is now explained as follows: For information security reasons, the business information of the distribution automation master station is not open to the public, so the blockchain used in this embodiment is a private chain, that is, the blockchain data can be publicly read within the business-related departments. Therefore, this embodiment performs node initialization configuration on all parties involved in the version management of the distribution automation master station, organizes the nodes into a private chain through the signing of a private chain treaty by all parties, uniquely identifies each node in the private chain, adds the network initial state parameters after the stored identification, and the state parameters include the number of nodes and the state of each node, and structures it to generate new storage data as the founding block and broadcast it within the entire private chain. All nodes within the private chain store the founding block data.
[0044] The block structure stored in the blockchain is as follows Figure 3 As shown, it includes a block header and a block body. The block header contains a version number, signature information, and a random array. The data in the block body are composed of:
[0045] The current version number of all functional modules of the distribution automation master station and the HASH value of the module file content data corresponding to the version number;
[0046] Applicant, application date and reason for application;
[0047] The approvers, approval time and approval opinions of all approval links.
[0048] Step 4: The nodes within the blockchain network will process the functional module data files involved in this change in the received distribution automation master station software version data one by one, and back up and store the renamed functional module files.
[0049] Now combined Figure 1 The distribution automation master station version management system of the present invention is described with the master station version management method disclosed above.
[0050] The distribution automation master station version management system of this embodiment includes a workflow-based distribution automation master station version upgrade approval system and a blockchain system.
[0051] In order to realize the historical traceability of distribution automation master station version process changes, it is necessary to build a workflow-based distribution automation master station version change approval workflow environment, and configure the database name, user name and password in the built workflow server environment. In addition, it is also necessary to configure the organizational structure and user account information, role information and the correspondence between users and roles at all levels in the workflow-based approval system; in the workflow approval system, it is also necessary to configure the roles or users of each approval link in the master station version approval process.
[0052] After completing the relevant configuration, the distribution automation master station version upgrade approval system implements the following process based on the workflow submodule, namely, the complete process of the distribution automation master station software version change, including proposing change requirements, approving change requirements, responding to demand upgrades or repair functions to form new function modules to be released, testing new function modules, determining the version number of new function modules based on the correspondence between new function modules and original function modules, upgrading the master station function modules, archiving this distribution automation master station version upgrade, and ending this function module version upgrade process. That is, the management of the distribution automation master station function module version upgrade process is completed in the system based on the workflow method. There will be a configured approval process definition in the system, and the approval process definition includes the content that needs to be filled in each link, the approval account number of each link, and other information. After starting the approval process, the workflow submodule in the system will notify the corresponding process link approver for approval according to the process definition of the version process upgrade. The workflow submodule will record the approval opinions and process status of the process approver of each link until the entire process is successfully approved or rejected and terminated.
[0053] The mentioned workflow submodule mainly processes the process data information during the version change of the distribution automation master station. The process data information includes the reasons for the distribution automation master station version upgrade, the review parties involved in the review, the test parties of the distribution automation master station version, the final version information of the module and submodule after the distribution automation master station is upgraded, and the affected submodule file data. The workflow submodule has a file management function, and the file management function is implemented through the file management submodule. Considering that there are many functional modules of the distribution automation master station, and the files submitted by each functional module are large, it is not suitable to upload the file data to the chain. Therefore, the file management submodule is used to store the file data of the functional modules updated by the distribution automation master station. In order to avoid file name conflicts, the HASH value of the functional module file data is used as the form of the file name.
[0054] The blockchain system is a private blockchain network formed by the deployment of multiple blockchain servers, which includes a blockchain sub-module, which is used to store process data information in previous distribution automation master station version upgrades. The process data information includes the reasons for the distribution automation master station version upgrade, the approval parties involved in the review, the testers of the distribution automation master station version, the final version information of the modules and sub-modules after the distribution automation master station is upgraded, and the affected sub-module file data, etc.
[0055] The present invention discloses a distribution automation master station software version management method and system based on process and blockchain, which mainly completes the approval process record of the version upgrade process of the distribution automation master station software module based on the workflow submodule, and uses blockchain technology to record the requirements and approval process information related to the distribution automation master station software version change using a distributed ledger. Compared with the current traditional management method, the present invention adopts electronic process plus blockchain ledger technology, which not only solves the problem of long signing and review time in the traditional management model, but also solves the security risks caused by the easy tampering of data in the electronic process technology.
[0056] Those skilled in the art will appreciate that the embodiments of the present application may be provided as methods, systems, or computer program products. Therefore, the present application may adopt the form of a complete hardware embodiment, a complete software embodiment, or an embodiment in combination with software and hardware. Moreover, the present application may adopt the form of a computer program product implemented in one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) that include computer-usable program code.
[0057] The present application is described with reference to the flowcharts and / or block diagrams of the methods, devices (systems), and computer program products according to the embodiments of the present application. It should be understood that each process and / or box in the flowchart and / or block diagram, as well as the combination of the processes and / or boxes in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to generate a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the processes in the flowchart and / or block diagram. Figure 1 A process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.
[0058] These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the computer-readable memory produce an article of manufacture comprising an instruction device, which implements the process Figure 1A process or multiple processes and / or boxes Figure 1 A function specified in one or more boxes.
[0059] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operating steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions for implementing the process. Figure 1 A process or multiple processes and / or boxes Figure 1 The steps for the functions specified in one or more boxes.
[0060] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention rather than to limit it. Although the present invention has been described in detail with reference to the above embodiments, ordinary technicians in the relevant field should understand that the specific implementation methods of the present invention can still be modified or replaced by equivalents. Any modification or equivalent replacement that does not depart from the spirit and scope of the present invention should be covered within the scope of protection of the claims of the present invention.
Claims
1. A distribution automation master station version management system based on process and blockchain, characterized by: include: The version upgrade approval system is used to complete the version upgrade process approval, function module version upgrade and version data generation based on workflow. The processes rejected in the version upgrade process approval will not be broadcast to the blockchain system; The version upgrade process approval includes: notifying the process approver of the corresponding process link to approve according to the pre-configured version upgrade process to obtain the approval result; the function module version upgrade includes: only when the approval result is passed, repairing or upgrading the function module to be changed to form a new function module to be released; the version data generation includes: determining the version number of the new function module according to the corresponding relationship between the new function module and the original function module, upgrading the master station function module, archiving the version upgrade of the distribution automation master station, and generating version data; The version upgrade approval system includes: The workflow submodule is used to process the process data information generated during the version change of the distribution automation master station, complete the version upgrade of the functional module and the generation of version data; the process data information includes the reason for the version upgrade of the distribution automation master station, the approvers involved in the approval, the testers of the distribution automation master station version, the final version information of all functional modules and sub-functional modules of the distribution automation master station after the upgrade, and the affected sub-functional module file data; the distribution automation master station software version data includes: the current version number of all functional modules of the distribution automation master station and the function module file name corresponding to the version number, the applicant, the application time, the application reason, the process approvers of all process links, the approval time and the approval opinions; Wherein, the workflow submodule includes: The file management submodule is used to store the function module file data updated by the distribution automation master station, and uses the HASH value of the function module file data as the function module file name; The blockchain system treats all parties involved in the version management of the distribution automation master station as nodes, which are organized by each node to broadcast the version data generated by the version upgrade approval system. Nodes within the blockchain system obtain the version data and determine the identity of the node broadcasting the version data and the authenticity of the version data. If the node broadcasting the information is a node within the blockchain network, the version data will be checked for integrity. If the check succeeds, the version data will be uploaded to the chain; if the check fails, the version data will not be uploaded to the chain. If the node broadcasting the information is not a node within the blockchain network, the nodes in the blockchain network will reach a permission consensus through the consensus mechanism. If the permission of more than half of the nodes in the blockchain network is obtained, the node information of the broadcast version data will be added to the genesis block, and the integrity of the version data will be checked. If the check is successful, the version data will be put on the chain; if the permission consensus is not obtained or the version data integrity check fails, the version data will not be put on the chain; The nodes within the blockchain system process the function module data files involved in this change in the received version data one by one; Among them, the block structure stored in the blockchain system includes a block header and a block body; the data in the block header includes a version number, a random array and the signature information of the previous block; the data in the block body is version data.
2. According to a process and blockchain-based distribution automation master station version management system according to claim 1, it is characterized by: The blockchain system includes a blockchain sub-module, which is used to deploy multiple blockchain servers to form a private blockchain network and broadcast version data based on the blockchain communication protocol.
3. According to a process and blockchain-based distribution automation master station version management system according to claim 1, it is characterized by: Follow the steps below to deploy multiple blockchain servers to form a private blockchain network: Perform node initialization configuration for all parties involved in the version management of the distribution automation master station, organize each node into a blockchain network, uniquely identify each node in the blockchain network, perform structured processing on each node to generate new storage data; use the new storage data as the founding block and broadcast it throughout the blockchain network, and all nodes within the blockchain network store the data in the founding block.
