Power plant data management method, server side, data acquisition side and system

Abstract

The invention provides a power plant data management method, a server side, a data acquisition side and a system. The method comprises the steps that the server side sends a power plant data acquisition instruction to the data acquisition side; the server side receives the power plant data uploading request sent by the data acquisition side and verifies the power plant data uploading request; and after verification succeeds, the server side receives the uploading request of the power plant data, and then stores the power plant data in a chain structure. According to the technical scheme provided by the invention, high security and high efficiency are achieved when the power plant data are stored, and meanwhile, data sharing can be realized.

Description

Technical Field

[0001] The present application relates to the technical field of Internet of Things, and in particular to a power plant data management method, a server, a data collection terminal and a system. Background Art

[0002] At present, power plants mainly use big data technology to manage power plant data. Big data transforms various data information resources from simple processing objects to basic elements of production through the interconnection and interaction of energy systems and the advantages of high intelligence, and realizes the fine-grained collection and storage of power plant data, but it also creates the problem of "data disaster". With cloud computing as the core of power plant data management, there are problems such as high data management cost, low management efficiency and high risk of third-party data privacy leakage. At the same time, the current power plant data cannot be shared in real time with social resources. From an objective point of view, power plant data has become an independent island, which leads to a decrease in the value of power plant data and a waste of software, hardware and resources. Therefore, it is urgent to propose a solution that can ensure the security, efficiency and sharing of power plant data storage. Summary of the invention

[0003] The present application provides a power plant data management method, a server end, a data acquisition end and a system to at least solve the technical problems of low security and storage efficiency of existing power plant data storage and the inability to share data.

[0004] The first embodiment of the present application provides a power plant data management method, which is applied to a server side, and the method includes:

[0005] Send power plant data collection instructions to the data collection terminal;

[0006] Receiving the power plant data upload request sent by the data acquisition terminal and verifying the power plant data upload request;

[0007] When the verification is successful, the upload request of the power plant data is accepted, and then the power plant data is stored in a chain structure.

[0008] Preferably, before sending the power plant data collection instruction to the data collection terminal, the method further includes:

[0009] Create power plant data information chain and IoT smart contracts;

[0010] Wherein, the power plant data information chain includes: a plurality of linked data storage nodes, the data storage node includes a header and a body, the header is used to link to the previous node, and the body is used to record updated power plant data information;

[0011] The IoT smart contract includes: device registration protocol, data collection protocol and data sharing protocol.

[0012] Furthermore, after storing the power plant data in a chain structure, the process further includes:

[0013] The power plant data is shared among the nodes of the power plant data information chain based on the data sharing protocol.

[0014] Further, the receiving the power plant data upload request sent by the data acquisition terminal and verifying the power plant data upload request includes:

[0015] Send a data upload request to the data recording node using the public key of the data collection node as an identifier;

[0016] The data recording node verifies the public key of the data collection node based on the private key of the data collection node, and determines whether the data collection node has the authority to upload data;

[0017] The data acquisition nodes and the data recording nodes are selected from the power plant data information chain based on preset conditions.

[0018] Furthermore, the storing of the power plant data in a chain structure includes:

[0019] The data collection node determines the summary of the collected power plant data using a hash function, and digitally signs the summary of the power plant data using the private key of the data collection node, and then encrypts the signed power plant data using the public key of the data recording node, and packages the encrypted power plant data and sends it to the data recording node;

[0020] The data recording node uses the private key of the data recording node to decrypt the received power plant data, substitutes the decrypted power plant data into the hash function to obtain the hash function value of the power plant data, and then uses the public key of the data acquisition node to decrypt the summary of the power plant data, and compares the decrypted summary of the power plant data with the hash function value of the power plant data. If the summary of the power plant data is consistent with the hash function value of the power plant data, the summary of the power plant data is stored in the header of the data storage node corresponding to the current moment, and the encrypted power plant data is stored in the body of the data storage node corresponding to the current moment.

[0021] Furthermore, the sharing of the power plant data among the nodes of the power plant data information chain based on the data sharing protocol includes:

[0022] The data sending node encrypts the power plant data using the public key of the data receiving node to generate a ciphertext of the power plant data;

[0023] The data sending node calculates the power plant data through a hash function to obtain a summary of the power plant data, and signs the summary of the power plant data using a private key of the data sending node;

[0024] The data sending node sends the ciphertext of the power plant data and the signed summary of the power plant data to the data receiving node;

[0025] The data receiving node decrypts the signed summary of the power plant data and the ciphertext of the power plant data using the public key of the data sending node, and then calculates the summary of the power plant data corresponding to the decrypted ciphertext of the power plant data through a hash function;

[0026] The data receiving node compares the decrypted summary of the power plant data with the summary of the power plant data corresponding to the calculated ciphertext of the power plant data. If the decrypted summary of the power plant data is the same as the summary of the power plant data corresponding to the calculated ciphertext of the power plant data, the data receiving node obtains the complete power plant data;

[0027] The node storing the power plant data in the power plant data information chain is used as a data sending node, and the nodes in the power plant data information chain other than the node storing the power plant data are used as data receiving nodes.

[0028] Furthermore, after storing the power plant data in a chain structure, the process further includes:

[0029] Using an asymmetric encryption algorithm, encrypting and backing up the public key of the data sending node;

[0030] The transmitted power plant data is encrypted using the public key of the data receiving node.

[0031] A second aspect of the present application provides a power plant data management method, which is applied to a data collection end and includes:

[0032] Send a device registration request to the server;

[0033] When the request is approved, the device registration protocol in the IoT smart contract is called to complete the IoT device registration, and the device is registered as an IoT device using the device's unique identifier;

[0034] Receive data collection instructions and perform data collection based on the data collection protocol, and then send a data upload request to the server.

[0035] The third aspect of the present application provides a server for power plant data management, the server comprising:

[0036] An instruction sending module is used to send power plant data collection instructions to the data collection terminal;

[0037] A first verification module, used for receiving the power plant data upload request sent by the data acquisition terminal and verifying the power plant data upload request;

[0038] The storage module is used to accept the upload request of the power plant data after the verification is successful, and then store the power plant data in a chain structure.

[0039] A fourth aspect of the present application provides a data collection terminal for power plant data management, the data collection terminal comprising:

[0040] A first request module, used to send a device registration request to the server;

[0041] The device registration module is used to call the device registration protocol in the IoT smart contract to complete the IoT device registration when the request is approved, and register the device as an IoT device using the device's unique identifier;

[0042] The second request module is used to receive the data collection instruction and perform data collection based on the data collection protocol, and then send a data upload request to the server.

[0043] The technical solution provided by the embodiments of the present application brings at least the following beneficial effects:

[0044] The present application proposes a power plant data management method, a server, a data collection terminal and a system, wherein the method comprises: the server sends a power plant data collection instruction to the data collection terminal; the server receives the power plant data upload request sent by the data collection terminal and verifies the power plant data upload request; when the verification is successful, the server accepts the power plant data upload request, and then stores the power plant data in a chain structure. The technical solution proposed in the present application has high security and efficiency when storing power plant data, and can also realize data sharing.

[0045] Additional aspects and advantages of the present application will be given in part in the description below, and in part will become apparent from the description below, or will be learned through the practice of the present application. BRIEF DESCRIPTION OF THE DRAWINGS

[0046] The above and / or additional aspects and advantages of the present application will become apparent and easily understood from the following description of the embodiments in conjunction with the accompanying drawings, in which:

[0047] Figure 1 A flow chart of a power plant data management method applied to a server side according to an embodiment of the present application;

[0048] Figure 2 A schematic diagram of the structure of a power plant data information chain provided according to an embodiment of the present application;

[0049] Figure 3 A flowchart of chain-structured storage of the power plant data by a server provided according to an embodiment of the present application;

[0050] Figure 4 A flowchart of sharing the power plant data among the nodes of the power plant data information chain based on the data sharing protocol according to an embodiment of the present application;

[0051] Figure 5 A structural diagram of a server end applied to power plant data management provided according to an embodiment of the present application;

[0052] Figure 6 A detailed structural diagram of a power plant data management system provided according to an embodiment of the present application;

[0053] Figure 7 A flow chart of a power plant data management method applied to a data collection terminal according to an embodiment of the present application;

[0054] Figure 8 A flowchart of a power plant data management method provided according to an embodiment of the present application;

[0055] Fig. 9 The present invention is a structural diagram of a power plant data management system provided according to an embodiment of the present application. DETAILED DESCRIPTION

[0056] Embodiments of the present application are described in detail below, and examples of the embodiments are shown in the accompanying drawings, wherein the same or similar reference numerals throughout represent the same or similar elements or elements having the same or similar functions. The embodiments described below with reference to the accompanying drawings are exemplary and are intended to be used to explain the present application, and should not be construed as limiting the present application.

[0057] The present application proposes a power plant data management method, a server, a data collection terminal and a system, wherein the method comprises: the server sends a power plant data collection instruction to the data collection terminal; the server receives the power plant data upload request sent by the data collection terminal and verifies the power plant data upload request; when the verification is successful, the server accepts the power plant data upload request, and then stores the power plant data in a chain structure. The technical solution proposed in the present application has high security and efficiency when storing power plant data, and can also realize data sharing.

[0058] The following describes a power plant data management method, server, data acquisition terminal and system according to an embodiment of the present application with reference to the accompanying drawings.

[0059] Embodiment 1

[0060] Figure 1 A power plant data management method is provided according to an embodiment of the present application. The method is applied to a flow chart of a server side, such as Figure 1 As shown, the method includes:

[0061] Step A1: The server sends a power plant data collection instruction to the data collection terminal;

[0062] Step A2: The server receives the power plant data upload request sent by the data acquisition end and verifies the power plant data upload request;

[0063] Step A3: When the verification is successful, the server accepts the upload request of the power plant data, and then stores the power plant data in a chain structure.

[0064] In the embodiment of the present disclosure, before step A1, the following steps are also included:

[0065] The server creates a power plant data information chain and IoT smart contracts;

[0066] Wherein, the power plant data information chain includes: a plurality of linked data storage nodes, the data storage node includes a header and a body, the header is used to link to the previous node, and the body is used to record updated power plant data information;

[0067] The IoT smart contract includes: device registration protocol, data collection protocol and data sharing protocol.

[0068] It should be noted that if Figure 2 Shown is a schematic diagram of the structure of the power plant data information chain.

[0069] In the embodiment of the present disclosure, in step A2, the server side receives the power plant data upload request sent by the data acquisition side and verifies the power plant data upload request, including:

[0070] Send a data upload request to the data recording node using the public key of the data collection node as an identifier;

[0071] The data recording node verifies the public key of the data collection node based on the private key of the data collection node, and determines whether the data collection node has the authority to upload data;

[0072] The data acquisition nodes and the data recording nodes are selected from the power plant data information chain based on preset conditions, and the preset conditions are set according to the needs of the staff.

[0073] Furthermore, in step A3, the server stores the power plant data in a chain structure, including:

[0074] The data collection node determines the summary of the collected power plant data using a hash function, and digitally signs the summary of the power plant data using the private key of the data collection node, and then encrypts the signed power plant data using the public key of the data recording node, and packages the encrypted power plant data and sends it to the data recording node;

[0075] The data recording node uses the private key of the data recording node to decrypt the received power plant data, substitutes the decrypted power plant data into the hash function to obtain the hash function value of the power plant data, and then uses the public key of the data acquisition node to decrypt the summary of the power plant data, and compares the decrypted summary of the power plant data with the hash function value of the power plant data. If the summary of the power plant data is consistent with the hash function value of the power plant data, the summary of the power plant data is stored in the header of the data storage node corresponding to the current moment, and the encrypted power plant data is stored in the body of the data storage node corresponding to the current moment.

[0076] It should be noted that before the power plant data is stored in a chain structure, data collection nodes and data recording nodes are selected in the power plant data information chain.

[0077] Specifically, Figure 3 As shown, the server side stores the power plant data in a chain structure including:

[0078] Step T.1: Call the data collection protocol and send data collection instructions to the IoT device, i.e., the data collection terminal, through the IoT gateway.

[0079] Step T.2: Select the data collection nodes and data recording nodes in the power plant data information chain.

[0080] Step T.3: On the data collection node side, the power plant data uploaded by the IoT device is received, and the public key of the data collection node is used as an identifier to submit a data upload request to the data recording node.

[0081] Step T.4: On the data recording node side, the public key of the data collection node is verified, and it is determined whether the data collection node has the authority to upload data; if it has the authority to upload data, the request of the data collection node is received.

[0082] Step T.5: On the data acquisition node side, the power plant data summary is obtained by using the hash function calculation, and the power plant data summary is digitally signed using the private key of the data acquisition node. The signed power plant data is then encrypted using the public key of the data recording node, and the encrypted power plant data is packaged and sent to the data recording node.

[0083] Step T.6: On the data recording node side, the received power plant data is decrypted using the private key of the data recording node, and the decrypted power plant data is substituted into the hash function to obtain the corresponding hash function value; the power plant data summary is decrypted using the public key of the data acquisition node, and the decrypted power plant data summary is compared with the hash function value of the power plant data; if the power plant data summary is consistent with the hash function value of the power plant data, the power plant data summary is stored in the node header of the power plant data information chain, and the encrypted power plant data is stored in the node body of the power plant data information chain. If the comparison is correct, the power plant data summary is stored in the header, and the encrypted power plant data is stored in the body.

[0084] It should be noted that in the power plant data information chain, each power plant data contains three basic elements, namely, public key, data summary and power plant data meta information. The public key is mainly used to identify the authority of the node uploading the power plant data; the data summary is mainly used to perform asymmetric encryption calculation on the power plant data to verify whether the power plant data storage is complete; the power plant data meta information stores the descriptive information of the power plant data, such as the generation date and generation type of the power plant data. Finally, the power plant data packet is compiled with function codes. The length of the function code in each power plant data packet is one byte, which is mainly used to notify each slave station of what operation should be performed, and complete the operation of the same function code byte through the corresponding master station requirements in the corresponding power plant data packet. The function code compilation can refer to the following method: the meaning of function code 0x0300 is to read the register, and the main function is to read the power value in one or more current registers; the meaning of function code 0x0600 is to write a single register, and the main function is to write the specified power plant data value into the corresponding single internal register; the meaning of function code 0x0900 is to write multiple registers, and the main function is to write the specified power plant data value into the corresponding multiple internal registers. It is convenient to query power plant data according to different categories in subsequent management, and improve the search speed of power plant data.

[0085] Furthermore, after step A3, the following steps are further included:

[0086] The server shares the power plant data among the nodes of the power plant data information chain based on the data sharing protocol.

[0087] The server shares the power plant data among the nodes of the power plant data information chain based on the data sharing protocol, including:

[0088] The data sending node encrypts the power plant data using the public key of the data receiving node to generate a ciphertext of the power plant data;

[0089] The data sending node calculates the power plant data through a hash function to obtain a summary of the power plant data, and signs the summary of the power plant data using a private key of the data sending node;

[0090] The data sending node sends the ciphertext of the power plant data and the signed summary of the power plant data to the data receiving node;

[0091] The data receiving node decrypts the signed summary of the power plant data and the ciphertext of the power plant data using the public key of the data sending node, and then calculates the summary of the power plant data corresponding to the decrypted ciphertext of the power plant data through a hash function;

[0092] The data receiving node compares the decrypted summary of the power plant data with the summary of the power plant data corresponding to the calculated ciphertext of the power plant data. If the decrypted summary of the power plant data is the same as the summary of the power plant data corresponding to the calculated ciphertext of the power plant data, the data receiving node obtains the complete power plant data;

[0093] The node storing the power plant data in the power plant data information chain is used as a data sending node, and the nodes in the power plant data information chain other than the node storing the power plant data are used as data receiving nodes.

[0094] Specifically, Figure 4 As shown, the server shares the power plant data among the nodes of the power plant data information chain based on the data sharing protocol, including:

[0095] Step R.1: The remaining nodes except the data recording node in the power plant data information chain are used as data receiving nodes, and the power plant data are encrypted using the public key of the data receiving node to generate the power plant data ciphertext.

[0096] Step R.2: Calculate the power plant data through a hash function to obtain the power plant data summary, use the data recording node as the data sending node, and use the private key of the data sending node to sign the power plant data summary.

[0097] Step R.3: Send the generated power plant data ciphertext and the signed power plant data summary to the data receiving node.

[0098] Step R.4: Use the public key of the data sending node to decrypt the signed power plant data summary and the power plant data ciphertext.

[0099] Step R.5: Calculate the power plant data summary through the hash function.

[0100] Step R.6: Compare the power plant data summary received in step R.4 with the power plant data summary calculated in step R.5. If the power plant data summary received in step R.4 is the same as the power plant data summary calculated in step R.5, output the complete power plant data.

[0101] It should be noted that in the above steps R.1 to R.6, the key is jointly held by the sender and the receiver and is not disclosed to a third party to ensure the security of information during the sharing process. At the same time, each piece of power data in the power plant data information chain is authenticated through the public key. The uploaded information and ownership information in the power data can be verified by the public key no matter which node it is stored on.

[0102] In the embodiment of the present disclosure, the step A3 further includes:

[0103] The server uses an asymmetric encryption algorithm to encrypt and back up the public key of the data sending node;

[0104] The server side uses the public key of the data receiving node to encrypt the transmitted power plant data.

[0105] It should be noted that the data distribution on the power plant data information chain is very wide, there are many data collection nodes, the types of power plant data are complex, and the business correlation between data is close. Therefore, it is necessary to manage the power plant data information chain securely, including power plant data storage management and power plant data transmission management. The following steps are included:

[0106] Step Y.1: Use an asymmetric encryption algorithm to encrypt the public key of the data sending node in the power plant data and back it up.

[0107] On the one hand, when there is an illegal intrusion, the data stolen by the intruder is encrypted and stored in ciphertext. If the intruder lacks the private key of the power plant data, the ciphertext cannot be decrypted to prevent the loss of power data. On the other hand, in the power plant data information chain, each power plant data has a backup, and when there is an illegal intrusion, it will not affect the use and management of normal data.

[0108] Step Y.2: During the power plant data transmission process, the power plant data is encrypted using the public key of the data receiving node.

[0109] After the power plant data is encrypted using the public key of the data receiving node, the encrypted file can only be decrypted by the private key shared by the data receiving node and the data sending node. At the same time, the data files shared during the transmission process are encrypted files, not the power plant data itself, so the original power plant data will not be spread in the public network environment, ensuring the security of the power plant data transmission process.

[0110] Based on the same inventive concept, a server end for power plant data management is provided, such as Figure 5 As shown, the server side 1 includes:

[0111] The instruction sending module 100 is used to send the power plant data collection instruction to the data collection terminal;

[0112] A first verification module 200, configured to receive the power plant data upload request sent by the data acquisition terminal 2 and verify the power plant data upload request;

[0113] The storage module 300 is used to accept the upload request of the power plant data after the verification is successful, and then store the power plant data in a chain structure.

[0114] Furthermore, the first verification module 200 includes:

[0115] The data receiving unit 201 is used to receive the power plant data uploaded by the data collection terminal at the data collection node side, and send a data upload request to the data recording node using the public key of the data collection node as an identifier;

[0116] The authority verification unit 202 is used for the data recording node to verify the public key of the data collection node based on the private key of the data collection node, and determine whether the data collection node has the authority to upload data; if it has the data upload authority, receive the request of the data collection node.

[0117] The server side includes: a data collection node and a data recording node.

[0118] Furthermore, the storage module 300 includes:

[0119] The data encryption unit 301 is used for the data collection node to determine the summary of the collected power plant data using a hash function, and digitally sign the summary of the power plant data using the private key of the data collection node, and then encrypt the signed power plant data using the public key of the data recording node, and package the encrypted power plant data and send it to the data recording node;

[0120] The data decryption unit 302 is used for the data recording node to decrypt the received power plant data using the private key of the data recording node, substitute the decrypted power plant data into the hash function to obtain the hash function value of the power plant data, and then use the public key of the data acquisition node to decrypt the summary of the power plant data, and compare the decrypted summary of the power plant data with the hash function value of the power plant data. If the summary of the power plant data is consistent with the hash function value of the power plant data, the summary of the power plant data is stored in the head of the data storage node corresponding to the current moment, and the encrypted power plant data is stored in the body of the data storage node corresponding to the current moment.

[0121] It should be noted that the server side also includes: a node screening unit 400;

[0122] The node screening unit 400 is used to select data collection nodes and data recording nodes in the power plant data information chain before storing the power plant data in a chain structure.

[0123] Among them, Figure 6 As shown, the instruction sending module 100 , the first verification module 200 , the storage module 300 , the data receiving unit 201 , the authority verification unit 202 , the data encryption unit 301 , the data decryption unit 302 , and the data decryption unit 302 may all belong to the data recording module 500 .

[0124] In the embodiments of the present disclosure, Figure 6 As shown, the server side also includes:

[0125] A data link creation module 600 is used to create a power plant data information link;

[0126] A smart contract creation module 700 is used to create an IoT smart contract;

[0127] The power plant data information chain includes: a plurality of linked data storage nodes, wherein the data storage node includes a header and a body, wherein the header is used to link to the previous node, and the body is used to record updated power plant data information;

[0128] The IoT smart contract includes: device registration protocol, data collection protocol and data sharing protocol.

[0129] In the embodiments of the present disclosure, Figure 6 As shown, the server side also includes:

[0130] The data sharing module 800 is used to share the power plant data among the nodes of the power plant data information chain based on the data sharing protocol.

[0131] Further, such as Figure 6 As shown, the data sharing module 800 includes:

[0132] A power plant data ciphertext generating unit 801 is used for the data sending node to encrypt the power plant data using the public key of the data receiving node to generate the power plant data ciphertext;

[0133] A power plant data summary generating unit 802, configured for the data sending node to calculate the power plant data through a hash function to obtain a summary of the power plant data, and to sign the summary of the power plant data using a private key of the data sending node;

[0134] The ciphertext and summary sending unit 803 is used for the data sending node to send the ciphertext of the power plant data and the signed summary of the power plant data to the data receiving node;

[0135] The ciphertext and summary decryption unit 804 is used for the data receiving node to decrypt the signed summary of the power plant data and the ciphertext of the power plant data using the public key of the data sending node, and then calculate the summary of the power plant data corresponding to the decrypted ciphertext of the power plant data by a hash function;

[0136] The data comparison unit 805 is used for the data receiving node to compare the decrypted digest of the power plant data with the digest of the power plant data corresponding to the calculated ciphertext of the power plant data. If the decrypted digest of the power plant data is the same as the digest of the power plant data corresponding to the calculated ciphertext of the power plant data, the data receiving node obtains the complete power plant data;

[0137] The node storing the power plant data in the power plant data information chain is used as a data sending node, and the nodes in the power plant data information chain other than the node storing the power plant data are used as data receiving nodes.

[0138] In the embodiments of the present disclosure, Figure 6 As shown, the server side also includes: a data link security management module 900, wherein the data link security management module 900 includes a storage security management unit 901 and a transmission security management unit 902;

[0139] The storage security management unit 901 is used to encrypt and back up the public key of the data sending node using an asymmetric encryption algorithm;

[0140] The transmission security management unit 902 is used to encrypt the transmitted power plant data using the public key of the data receiving node.

[0141] It should be noted that if Figure 6As shown, the data link security management module 900 may belong to the data sharing module 800 .

[0142] In this method, a power plant data governance method is applied to the data collection end, such as Figure 7 As shown, the method includes:

[0143] Step B1: The data collection end sends a device registration request to the server end;

[0144] Step B2: When the request is approved, the data collection end calls the device registration protocol in the IoT smart contract to complete the IoT device registration, and registers the device as an IoT device using the device's unique identifier;

[0145] Step B3: The data collection end receives the data collection instruction and performs data collection based on the data collection protocol, and then sends a data upload request to the server end.

[0146] Based on the same inventive concept, a data collection terminal for power plant data management is provided, such as Figure 6 As shown, the data acquisition end includes:

[0147] The first request module 1000 is used to send a device registration request to the server;

[0148] The device registration module 2000 is used to call the device registration protocol in the IoT smart contract to complete the IoT device registration when the request is approved, and register the device as an IoT device using the device's unique identifier;

[0149] The second request module 3000 is used to receive a data collection instruction and perform data collection based on a data collection protocol, and then send a data upload request to the server.

[0150] Based on the server side and data collection side in the above embodiments, the present invention proposes a power plant data management method, such as Figure 8 As shown, the method includes

[0151] Step 1: The data collection end sends a device registration request to the server end;

[0152] Step 2: When the request is approved, the data collection end calls the device registration protocol in the IoT smart contract to complete the IoT device registration, and registers the device as an IoT device using the device's unique identifier;

[0153] Step 3: The server sends a power plant data collection instruction to the data collection terminal;

[0154] Step 4: The data collection end receives the data collection instruction and collects data based on the data collection protocol, and then sends a data upload request to the server end;

[0155] Step 5: The server receives the power plant data upload request sent by the data acquisition end and verifies the power plant data upload request;

[0156] Step 6: When the verification is successful, the server accepts the upload request of the power plant data, and then stores the power plant data in a chain structure.

[0157] Based on the server side and data collection side in the above embodiments, the present invention proposes a power plant data management system, such as Fig. 9 As shown, the system includes: a server end 1 and a data collection end 2.

[0158] In summary, the power plant data management method and system proposed in this embodiment have high security and efficiency when storing power plant data, and can realize data sharing.

[0159] Embodiment 2

[0160] In order to implement the above embodiments, the present disclosure further proposes an electronic device, including: a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein when the processor executes the program, the method described in Embodiment 1 is implemented.

[0161] Embodiment 3

[0162] In order to implement the above embodiments, the present disclosure further proposes a computer-readable storage medium on which a computer program is stored. When the program is executed by a processor, the method described in the first embodiment is implemented.

[0163] In the description of this specification, the description with reference to the terms "one embodiment", "some embodiments", "example", "specific example", or "some examples" etc. means that the specific features, structures, materials or characteristics described in conjunction with the embodiment or example are included in at least one embodiment or example of the present application. In this specification, the schematic representations of the above terms do not necessarily refer to the same embodiment or example. Moreover, the specific features, structures, materials or characteristics described may be combined in any one or more embodiments or examples in a suitable manner. In addition, those skilled in the art may combine and combine the different embodiments or examples described in this specification and the features of the different embodiments or examples, without contradiction.

[0164] Any process or method description in a flowchart or otherwise described herein may be understood to represent a module, fragment or portion of code comprising one or more executable instructions for implementing the steps of a custom logical function or process, and the scope of the preferred embodiments of the present application includes alternative implementations in which functions may not be performed in the order shown or discussed, including performing functions in a substantially simultaneous manner or in the reverse order depending on the functions involved, which should be understood by technicians in the technical field to which the embodiments of the present application belong.

[0165] Although the embodiments of the present application have been shown and described above, it can be understood that the above embodiments are exemplary and cannot be understood as limitations on the present application. Ordinary technicians in the field can change, modify, replace and modify the above embodiments within the scope of the present application.

Claims

1. A power plant data management method, which is applied to the server side and is characterized in that: The method comprises: Send power plant data collection instructions to the data collection terminal; Receiving the power plant data upload request sent by the data acquisition terminal and verifying the power plant data upload request; When the verification is successful, the upload request of the power plant data is accepted, and then the power plant data is stored in a chain structure.

2. The method according to claim 1, characterized in that Before sending the power plant data collection instruction to the data collection terminal, the method further includes: Create power plant data information chain and IoT smart contracts; The power plant data information chain includes: a plurality of linked data storage nodes, wherein the data storage node includes a header and a body, wherein the header is used to link to the previous node, and the body is used to record updated power plant data information; The IoT smart contract includes: device registration protocol, data collection protocol and data sharing protocol.

3. The method according to claim 2, characterized in that After storing the power plant data in a chain structure, the following further comprises: The power plant data is shared among the nodes of the power plant data information chain based on the data sharing protocol.

4. The method according to claim 3, characterized in that The receiving the power plant data upload request sent by the data acquisition terminal and verifying the power plant data upload request includes: Send a data upload request to the data recording node using the public key of the data collection node as an identifier; The data recording node verifies the public key of the data collection node based on the private key of the data collection node, and determines whether the data collection node has the authority to upload data; The data acquisition nodes and the data recording nodes are selected from the power plant data information chain based on preset conditions.

5. The method according to claim 4, characterized in that The storing of the power plant data in a chain structure includes: The data collection node determines the summary of the collected power plant data using a hash function, and digitally signs the summary of the power plant data using the private key of the data collection node, and then encrypts the signed power plant data using the public key of the data recording node, and packages the encrypted power plant data and sends it to the data recording node; The data recording node uses the private key of the data recording node to decrypt the received power plant data, substitutes the decrypted power plant data into the hash function to obtain the hash function value of the power plant data, and then uses the public key of the data acquisition node to decrypt the summary of the power plant data, and compares the decrypted summary of the power plant data with the hash function value of the power plant data. If the summary of the power plant data is consistent with the hash function value of the power plant data, the summary of the power plant data is stored in the header of the data storage node corresponding to the current moment, and the encrypted power plant data is stored in the body of the data storage node corresponding to the current moment.

6. The method according to claim 5, characterized in that The step of sharing the power plant data among the nodes of the power plant data information chain based on the data sharing protocol includes: The data sending node encrypts the power plant data using the public key of the data receiving node to generate a ciphertext of the power plant data; The data sending node calculates the power plant data through a hash function to obtain a summary of the power plant data, and signs the summary of the power plant data using a private key of the data sending node; The data sending node sends the ciphertext of the power plant data and the signed summary of the power plant data to the data receiving node; The data receiving node decrypts the signed summary of the power plant data and the ciphertext of the power plant data using the public key of the data sending node, and then calculates the summary of the power plant data corresponding to the decrypted ciphertext of the power plant data through a hash function; The data receiving node compares the decrypted summary of the power plant data with the summary of the power plant data corresponding to the calculated ciphertext of the power plant data. If the decrypted summary of the power plant data is the same as the summary of the power plant data corresponding to the calculated ciphertext of the power plant data, the data receiving node obtains the complete power plant data; The node storing the power plant data in the power plant data information chain is used as a data sending node, and the nodes in the power plant data information chain other than the node storing the power plant data are used as data receiving nodes.

7. The method according to claim 6, characterized in that After storing the power plant data in a chain structure, the following further comprises: Using an asymmetric encryption algorithm, encrypting and backing up the public key of the data sending node; The transmitted power plant data is encrypted using the public key of the data receiving node.

8. A power plant data management method, which is applied to the data collection end, characterized in that: The method comprises: Send a device registration request to the server; When the request is approved, the device registration protocol in the IoT smart contract is called to complete the IoT device registration, and the device is registered as an IoT device using the device's unique identifier; Receive data collection instructions and perform data collection based on the data collection protocol, and then send a data upload request to the server.

9. A server end applied to power plant data management, characterized in that: The server side includes: An instruction sending module is used to send power plant data collection instructions to the data collection terminal; A first verification module, used for receiving the power plant data upload request sent by the data acquisition terminal and verifying the power plant data upload request; The storage module is used to accept the upload request of the power plant data after the verification is successful, and then store the power plant data in a chain structure.

10. A data collection terminal applied to power plant data management, characterized in that: The data collection end comprises: A first request module, used to send a device registration request to the server; The first device registration module is used to call the device registration protocol in the IoT smart contract to complete the IoT device registration when the request is approved, and register the device as an IoT device using the device's unique identifier; The second request module is used to receive the data collection instruction and perform data collection based on the data collection protocol, and then send a data upload request to the server.

Images