An information processing method, device, node management unit and node

By implementing dynamic conversion of node types in the node management unit PMU, the problem of separation of the generation environment and the test environment in the blockchain test solution is solved, the combination of the test environment and the production environment is realized, and the testing accuracy and openness are improved.

CN114328707BActive Publication Date: 2025-04-04CHINA MOBILE COMM LTD RES INST +1
View PDF 2 Cites 0 Cited by

Patent Information

Application Number
CN202011032185.6
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2020-09-27
Publication Date
2025-04-04
Estimated Expiration
2040-09-27

AI Technical Summary

Technical Problem

The separation of the generation environment and the test environment in the existing blockchain testing solution leads to inconvenient resource sharing, and there may be problems such as testing deviation and low testing accuracy.

Method used

By implementing dynamic conversion of node types in the node management unit PMU, nodes are allowed to switch between production environment and test environment, sharing the same smart contract, application and policy.

Benefits of technology

The combination of the test environment and the production environment is realized, the test deviation caused by the inconsistency between the test environment and the production environment is avoided, the test accuracy is improved, and the open testing and supervision of blockchain smart contracts is supported.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN114328707B_ABST
    Figure CN114328707B_ABST
Patent Text Reader

Abstract

The present invention provides an information processing method, device, node management unit and node, wherein the information processing method comprises: in the case of receiving first indication information, sending second indication information to the first node according to the first indication information; receiving node change result information fed back by the first node according to the second indication information; the first indication information is used to indicate that the first node changes the node type; the second indication information includes first sub-information for indicating that the first node deletes the first type information and second sub-information for indicating that the first node adds the second type information; the first type information is information indicating that the node type is a production type, and the second type information is information indicating that the node type is a test type; or the first type information is information indicating that the node type is a test type, and the second type information is information indicating that the node type is a production type. This solution solves the problems of poor development and low test accuracy of information processing solutions in the prior art.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present invention relates to the field of communication technology, and in particular to an information processing method, device, node management unit and node. Background Art

[0002] Blockchain technology, also known as distributed ledger technology, is a technology in which several computing devices jointly participate in "bookkeeping" and jointly maintain a complete distributed database. Blockchain technology has been widely used in many fields because of its decentralization, openness and transparency, each computing device can participate in database records, and data can be quickly synchronized between computing devices.

[0003] At present, the test methods for changes to smart contracts and applications corresponding to existing blockchain networks include: the blockchain test network deploys the changed applications or smart contracts and adds a block reading interface to the traditional blockchain network to obtain the blockchain environment and block data in the production environment (before the change, i.e. the current version) to build a node for the blockchain network to be tested. For more information about the blockchain test network, see Figure 1 .

[0004] However, in existing blockchain testing solutions, the generation environment and the test environment are separated, such as Figure 2 As shown, it is not conducive to resource sharing and may lead to test deviation and low test accuracy. In addition, blockchain data is irrevocable, smart contracts have legal or contractual effects, and generally speaking, smart contracts involve multiple organizations. The closed testing of a single organization has cognitive "blind spots" and is not conducive to discovering problems.

[0005] From the above, we can see that the existing information processing solutions for blockchain testing have problems such as poor development and low testing accuracy. Summary of the invention

[0006] The object of the present invention is to provide an information processing method, device, node management unit and node to solve the problems of poor development and low test accuracy of information processing solutions in the prior art.

[0007] In order to solve the above technical problems, an embodiment of the present invention provides an information processing method, which is applied to a node management unit PMU. The method includes:

[0008] When receiving the first indication information, sending second indication information to the first node according to the first indication information;

[0009] receiving node change result information fed back by the first node according to the second indication information;

[0010] The first indication information is used to instruct the first node to change the node type;

[0011] The second indication information includes first sub-information for instructing the first node to delete first-type information and second sub-information for instructing the first node to add second-type information;

[0012] The first type information is information indicating that the node type is a production type, and the second type information is information indicating that the node type is a test type; or, the first type information is information indicating that the node type is a test type, and the second type information is information indicating that the node type is a production type.

[0013] Optionally, the first indication information carries identification information of the first node;

[0014] The sending second indication information to the first node according to the first indication information includes:

[0015] Acquire the registry information of the first node from the node registry PSR according to the identification information of the first node in the first indication information;

[0016] Send second indication information to the first node according to the IP address information in the registration table information.

[0017] Optionally, after receiving the node change result information fed back by the first node according to the second indication information, the method further includes:

[0018] According to the node change result information, update the node information of the first node and record it in the node registration table PSR;

[0019] The node information includes at least one of node status information, node type information and information of installed contracts.

[0020] Optionally, after receiving the node change result information fed back by the first node according to the second indication information, the method further includes:

[0021] The node change result information is displayed.

[0022] Optionally, the method further includes:

[0023] After a preset time after confirming the existence of the newly added node type, confirm whether the nodes under the newly added node type meet the block consistency conditions;

[0024] If it does not meet the requirements, a block synchronization adjustment instruction is sent to the nodes under the newly added node type to control the nodes under the newly added node type to meet the block consistency conditions.

[0025] Optionally, the second indication information also includes: third sub-information indicating whether the node type indicated by the second type information is a newly added type.

[0026] Optionally, the sending second indication information to the first node according to the first indication information includes:

[0027] Sending first sub-information to the first node according to the first indication information;

[0028] Receiving first response information fed back by the first node according to the first sub-information;

[0029] Send second sub-information to the first node according to the first response information.

[0030] Optionally, the method further includes:

[0031] When the third indication information is received, sending fourth indication information to the second node according to the third indication information;

[0032] receiving node joining result information fed back by the second node according to the fourth indication information;

[0033] The third indication information is used to indicate that the second node marks a node type;

[0034] The fourth indication information includes fourth sub-information for indicating that the second node marks the node type as a production type or a test type and fifth sub-information for indicating a contract to be installed;

[0035] The second node and the first node are the same node or different nodes.

[0036] Optionally, the second indication information carries identification information of the second node;

[0037] The sending fourth indication information to the second node according to the third indication information includes:

[0038] Obtaining the registry information of the second node from the node registry PSR according to the identification information of the second node in the third indication information, and obtaining the information of the contract to be installed from the contract registry;

[0039] Send fourth indication information to the second node according to the IP address information and the information of the contract to be installed in the registration form information.

[0040] Optionally, the sending fourth indication information to the second node according to the third indication information includes:

[0041] Sending fourth sub-information to the second node according to the third indication information;

[0042] receiving second response information fed back by the second node according to the fourth sub-information;

[0043] Send fifth sub-information to the second node according to the second response information.

[0044] Optionally, after receiving the node joining result information fed back by the second node according to the fourth indication information, the method further includes:

[0045] According to the node joining result information, update the node information of the second node and record it in the node registration table PSR;

[0046] The node information includes at least one of node status information, node type information and information of installed contracts.

[0047] Optionally, after receiving the node joining result information fed back by the second node according to the fourth indication information, the method further includes:

[0048] The node joining result information is displayed.

[0049] Optionally, the method further includes:

[0050] When receiving the node information of the third node, sending a node status query request to the third node according to the node information of the third node;

[0051] Receiving the node status and node resource information fed back by the third node according to the node status query request;

[0052] When the node status and the node resource information indicate that the third node is available, recording the node information of the third node into a node registration table PSR;

[0053] The third node and the first node are the same node or different nodes.

[0054] Optionally, after recording the node information of the third node into the node registration table PSR, the method further includes:

[0055] The node status of the third node is displayed as being available.

[0056] Optionally, the method further includes:

[0057] Upon receiving the contract identifier, determining the record information of the contract identifier in the contract registration table;

[0058] Receiving the contract program and test set corresponding to the contract identifier;

[0059] According to the record information, the contract program and the test set are stored in the contract registration table.

[0060] Optionally, determining the record information of the contract identifier in the contract registration table includes:

[0061] Determine whether it is a registered version of the contract according to the contract identifier;

[0062] If yes, obtain the record information corresponding to the contract identifier from the contract registry;

[0063] If not, the contract corresponding to the contract identifier is recorded in a contract registration table to obtain record information corresponding to the contract identifier.

[0064] Optionally, the method further includes:

[0065] Upon receiving a test instruction, determining contract parameter information according to the test instruction;

[0066] According to the contract parameter information, obtain the corresponding test case from the contract registry;

[0067] Obtaining test data according to the test case and the signature data of the PMU;

[0068] Sending the test data to a node whose node type is a test type;

[0069] The contract parameter information includes at least one of a contract number and a contract name.

[0070] Optionally, the method further includes:

[0071] Upon receiving a processing instruction for installing and / or updating a contract, sending contract processing instruction information to a fourth node according to the processing instruction;

[0072] Receiving processing response information fed back by the fourth node according to the contract processing instruction information;

[0073] The contract processing instruction information is used to instruct the installation and / or update of the contract;

[0074] The fourth node and the first node are the same node or different nodes.

[0075] Optionally, sending the contract processing instruction information to the fourth node according to the processing instruction includes:

[0076] According to the processing instruction, obtain the contract program file from the contract registry;

[0077] According to the contract program file, contract processing instruction information is sent to the fourth node.

[0078] Optionally, after receiving the processing response information fed back by the fourth node according to the contract processing instruction information, the method further includes:

[0079] Updating node information of the fourth node;

[0080] The node information includes the information of the installed contract.

[0081] Optionally, after receiving the processing response information fed back by the fourth node according to the contract processing instruction information, the method further includes:

[0082] The processing response information is displayed.

[0083] The embodiment of the present invention further provides an information processing method, which is applied to a node, and the method includes:

[0084] Receiving second indication information sent by the node management unit PMU;

[0085] Changing the node type according to the second indication information, and obtaining node change result information;

[0086] Feedback the node change result information to the PMU;

[0087] The second indication information includes first sub-information for instructing the node to delete the first type of information and second sub-information for instructing the node to add the second type of information;

[0088] The first type information is information indicating that the node type is a production type, and the second type information is information indicating that the node type is a test type; or, the first type information is information indicating that the node type is a test type, and the second type information is information indicating that the node type is a production type.

[0089] Optionally, the changing the node type according to the second indication information includes:

[0090] According to the first sub-information in the second indication information, the first type of information is deleted; and according to the second sub-information in the second indication information, the second type of information is added.

[0091] Optionally, the second indication information also includes: third sub-information indicating whether the node type indicated by the second type information is a newly added type.

[0092] Optionally, when the third sub-information indicates that the node type indicated by the second type information is a newly added type, the changing the node type according to the second indication information further includes:

[0093] After deleting the first type of information and before adding the second type of information, the production area information is copied to the test area.

[0094] Optionally, copying the production area information to the test area includes:

[0095] Use the preset method to copy the production area information to the test area;

[0096] The preset method includes at least one of the following methods:

[0097] Copy the production area data;

[0098] Replicate the access link for production area data.

[0099] Optionally, when the third sub-information indicates that the node type indicated by the second type information is not a newly added type, after changing the node type according to the second indication information, the method further includes:

[0100] Synchronize chain block data with nodes of the same node type.

[0101] Optionally, after changing the node type according to the second indication information, the method further includes:

[0102] Update the contract version.

[0103] Optionally, the method further includes:

[0104] receiving a block synchronization adjustment instruction sent by the PMU;

[0105] According to the block synchronization adjustment instruction, the block data synchronization operation is adjusted.

[0106] Optionally, the receiving second indication information sent by the node management unit PMU includes:

[0107] Receiving first sub-information sent by the PMU;

[0108] Feedback first response information to the PMU according to the first sub-information;

[0109] receiving second sub-information sent by the PMU according to the first response information.

[0110] Optionally, the method further includes:

[0111] Receiving fourth indication information sent by the PMU;

[0112] According to the fourth indication information, marking the node type of the node as a production type or a test type, and an installation contract; and adding result information to the PMU feedback node;

[0113] The fourth indication information includes fourth sub-information for indicating that the node type is a production type or a test type and fifth sub-information for indicating a contract to be installed.

[0114] Optionally, the receiving fourth indication information sent by the PMU includes:

[0115] receiving fourth sub-information sent by the PMU;

[0116] Feedback second response information to the PMU according to the fourth sub-information;

[0117] receiving fifth sub-information sent by the PMU according to the second response information.

[0118] Optionally, marking the node type of the node as a production type or a test type, and installing a contract according to the fourth indication information, includes:

[0119] According to the fourth sub-information, the node type of the node is marked as a production type or a test type; and, according to the fifth sub-information, a contract is installed.

[0120] Optionally, after marking the node type of the node as a production type or a test type according to the fourth indication information and installing the contract, the method further includes:

[0121] When there are nodes of the same node type, chain block data synchronization is performed between nodes of the same node type.

[0122] Optionally, the method further includes:

[0123] Receiving a node status query request sent by the PMU;

[0124] According to the node status query request, the node status and node resource information of the node are fed back to the PMU.

[0125] Optionally, the method further includes:

[0126] Receiving test data sent by the PMU;

[0127] Verifying the signature data in the test data;

[0128] If the verification is passed, the test cases in the test data are executed.

[0129] Optionally, the method further includes:

[0130] Receiving the contract processing instruction information sent by the PMU;

[0131] Verifying the signature data in the contract processing instruction information;

[0132] If the verification is passed, the contract is installed and / or updated according to the contract program file in the contract processing instruction information, and processing response information is fed back to the PMU according to the processing result.

[0133] The embodiment of the present invention further provides an information processing device, which is applied to a node management unit PMU, and the device includes:

[0134] A first sending module, configured to send second indication information to the first node according to the first indication information when receiving the first indication information;

[0135] A first receiving module, configured to receive node change result information fed back by the first node according to the second indication information;

[0136] The first indication information is used to instruct the first node to change the node type;

[0137] The second indication information includes first sub-information for instructing the first node to delete first-type information and second sub-information for instructing the first node to add second-type information;

[0138] The first type information is information indicating that the node type is a production type, and the second type information is information indicating that the node type is a test type; or, the first type information is information indicating that the node type is a test type, and the second type information is information indicating that the node type is a production type.

[0139] Optionally, the first indication information carries identification information of the first node;

[0140] Wherein, the first sending module includes:

[0141] A first acquisition submodule, configured to acquire the registry information of the first node from a node registry PSR according to the identification information of the first node in the first indication information;

[0142] The first sending submodule is used to send second indication information to the first node according to the IP address information in the registration table information.

[0143] Optionally, also include:

[0144] A first processing module is configured to, after receiving the node change result information fed back by the first node according to the second indication information, update the node information of the first node according to the node change result information, and record it in a node registration table PSR;

[0145] The node information includes at least one of node status information, node type information and information of installed contracts.

[0146] Optionally, also include:

[0147] The first display module is used to display the node change result information after receiving the node change result information fed back by the first node according to the second indication information.

[0148] Optionally, the device further comprises:

[0149] A first confirmation module, configured to confirm whether the nodes under the newly added node type meet the block consistency condition after a preset time after confirming the existence of the newly added node type;

[0150] The second processing module is used to send a block synchronization adjustment instruction to the nodes under the newly added node type in case of non-compliance, so as to control the nodes under the newly added node type to comply with the block consistency condition.

[0151] Optionally, the second indication information also includes: third sub-information indicating whether the node type indicated by the second type information is a newly added type.

[0152] Optionally, the first sending module includes:

[0153] A second sending submodule, configured to send first sub-information to the first node according to the first indication information;

[0154] A first receiving submodule, configured to receive first response information fed back by the first node according to the first sub-information;

[0155] The third sending submodule is used to send second sub-information to the first node according to the first response information.

[0156] Optionally, the device further comprises:

[0157] A second sending module is used to send fourth indication information to the second node according to the third indication information when receiving the third indication information;

[0158] A second receiving module, used to receive node joining result information fed back by the second node according to the fourth indication information;

[0159] The third indication information is used to indicate that the second node marks a node type;

[0160] The fourth indication information includes fourth sub-information for indicating that the second node marks the node type as a production type or a test type and fifth sub-information for indicating a contract to be installed;

[0161] The second node and the first node are the same node or different nodes.

[0162] Optionally, the second indication information carries identification information of the second node;

[0163] Wherein, the second sending module includes:

[0164] A first processing submodule, configured to obtain the registry information of the second node from the node registry PSR according to the identification information of the second node in the third indication information, and to obtain the information of the contract to be installed from the contract registry;

[0165] The fourth sending submodule is used to send fourth indication information to the second node according to the IP address information and the information of the contract to be installed in the registration form information.

[0166] Optionally, the second sending module includes:

[0167] a fifth sending submodule, configured to send fourth sub-information to the second node according to the third indication information;

[0168] A second receiving submodule, configured to receive second response information fed back by the second node according to the fourth sub-information;

[0169] The sixth sending submodule is used to send fifth sub-information to the second node according to the second response information.

[0170] Optionally, also include:

[0171] A third processing module is used to update the node information of the second node according to the node joining result information after receiving the node joining result information fed back by the second node according to the fourth indication information, and record it in the node registration table PSR;

[0172] The node information includes at least one of node status information, node type information and information of installed contracts.

[0173] Optionally, also include:

[0174] The second display module is used to display the node joining result information after receiving the node joining result information fed back by the second node according to the fourth indication information.

[0175] Optionally, the device further comprises:

[0176] A third sending module is used to send a node status query request to the third node according to the node information of the third node when receiving the node information of the third node;

[0177] A third receiving module is used to receive the node status and node resource information fed back by the third node according to the node status query request;

[0178] A first recording module, configured to record the node information of the third node into a node registration table PSR when the node status and the node resource information indicate that the third node can be used;

[0179] The third node and the first node are the same node or different nodes.

[0180] Optionally, also include:

[0181] The third display module is used to display the node status of the third node as available for use after recording the node information of the third node into the node registration table PSR.

[0182] Optionally, the device further comprises:

[0183] A first determination module is used to determine the record information of the contract identifier in the contract registration table when receiving the contract identifier;

[0184] A fourth receiving module, used to receive the contract program and test set corresponding to the contract identifier;

[0185] The first storage module is used to store the contract program and the test set in the contract registration table according to the record information.

[0186] Optionally, the first determining module includes:

[0187] A first determination submodule, used to determine whether it is a registered version of the contract according to the contract identifier;

[0188] A second acquisition submodule is used to obtain the record information corresponding to the contract identifier from the contract registration table if yes;

[0189] The first recording submodule is used to record the contract corresponding to the contract identifier in a contract registration table if no, and obtain the recording information corresponding to the contract identifier.

[0190] Optionally, the device further comprises:

[0191] A second determination module is used to determine the contract parameter information according to the test instruction when receiving the test instruction;

[0192] A first acquisition module, used to acquire corresponding test cases from a contract registry according to the contract parameter information;

[0193] A fourth processing module, configured to obtain test data according to the test case and the signature data of the PMU;

[0194] A fourth sending module, used for sending the test data to a node whose node type is a test type;

[0195] The contract parameter information includes at least one of a contract number and a contract name.

[0196] Optionally, the device further comprises:

[0197] a fifth sending module, configured to send contract processing instruction information to the fourth node according to the processing instruction when receiving the processing instruction for installing and / or updating the contract;

[0198] A fifth receiving module, configured to receive processing response information fed back by the fourth node according to the contract processing instruction information;

[0199] The contract processing instruction information is used to instruct the installation and / or update of the contract;

[0200] The fourth node and the first node are the same node or different nodes.

[0201] Optionally, the fifth sending module includes:

[0202] A third acquisition submodule is used to acquire a contract program file from a contract registry according to the processing instruction;

[0203] The seventh sending submodule is used to send contract processing instruction information to the fourth node according to the contract program file.

[0204] Optionally, also include:

[0205] A first updating module, configured to update the node information of the fourth node after receiving the processing response information fed back by the fourth node according to the contract processing instruction information;

[0206] The node information includes the information of the installed contract.

[0207] Optionally, also include:

[0208] The fourth display module is used to display the processing response information after receiving the processing response information fed back by the fourth node according to the contract processing instruction information.

[0209] The embodiment of the present invention further provides an information processing device, applied to a node, the device comprising:

[0210] A sixth receiving module, used for receiving second indication information sent by the node management unit PMU;

[0211] a fifth processing module, configured to change the node type according to the second indication information, and obtain node change result information;

[0212] A first feedback module, used for feeding back the node change result information to the PMU;

[0213] The second indication information includes first sub-information for instructing the node to delete the first type of information and second sub-information for instructing the node to add the second type of information;

[0214] The first type information is information indicating that the node type is a production type, and the second type information is information indicating that the node type is a test type; or, the first type information is information indicating that the node type is a test type, and the second type information is information indicating that the node type is a production type.

[0215] Optionally, the fifth processing module includes:

[0216] The second processing submodule is used to delete the first type of information according to the first sub-information in the second indication information; and to add the second type of information according to the second sub-information in the second indication information.

[0217] Optionally, the second indication information also includes: third sub-information indicating whether the node type indicated by the second type information is a newly added type.

[0218] Optionally, when the third sub-information indicates that the node type indicated by the second type information is a newly added type, the fifth processing module further includes:

[0219] The first copy submodule is used to copy the production area information to the test area after deleting the first type of information and before adding the second type of information.

[0220] Optionally, copying the production area information to the test area includes:

[0221] Use the preset method to copy the production area information to the test area;

[0222] The preset method includes at least one of the following methods:

[0223] Copy the production area data;

[0224] Replicate the access link for production area data.

[0225] Optionally, when the third sub-information indicates that the node type indicated by the second type information is not a newly added type, the method further includes:

[0226] The first synchronization module is used to synchronize the chain block data with nodes of the same node type after the node type is changed according to the second indication information.

[0227] Optionally, also include:

[0228] The second updating module is used to update the contract version after the node type is changed according to the second indication information.

[0229] Optionally, the device further comprises:

[0230] A seventh receiving module, configured to receive a block synchronization adjustment instruction sent by the PMU;

[0231] The first adjustment module is used to adjust the block data synchronization operation according to the block synchronization adjustment instruction.

[0232] Optionally, the sixth receiving module includes:

[0233] A third receiving submodule, configured to receive the first sub-information sent by the PMU;

[0234] A first feedback submodule, configured to feed back first response information to the PMU according to the first sub-information;

[0235] The fourth receiving submodule is configured to receive second sub-information sent by the PMU according to the first response information.

[0236] Optionally, the device further comprises:

[0237] an eighth receiving module, configured to receive fourth indication information sent by the PMU;

[0238] a sixth processing module, configured to mark the node type of the node as a production type or a test type, and an installation contract according to the fourth indication information; and add result information to the PMU feedback node;

[0239] The fourth indication information includes fourth sub-information for indicating that the node type is a production type or a test type and fifth sub-information for indicating a contract to be installed.

[0240] Optionally, the eighth receiving module includes:

[0241] a fifth receiving submodule, configured to receive fourth sub-information sent by the PMU;

[0242] A second feedback submodule, configured to feed back second response information to the PMU according to the fourth sub-information;

[0243] The sixth receiving submodule is configured to receive fifth sub-information sent by the PMU according to the second response information.

[0244] Optionally, the sixth processing module includes:

[0245] The third processing submodule is used to mark the node type of the node as a production type or a test type according to the fourth sub-information; and install the contract according to the fifth sub-information.

[0246] Optionally, also include:

[0247] The second synchronization module is used to mark the node type of the node as a production type or a test type according to the fourth indication information, and after installing the contract, if there are nodes of the same node type, synchronize the chain block data between nodes of the same node type.

[0248] Optionally, the device further comprises:

[0249] A ninth receiving module, configured to receive a node status query request sent by the PMU;

[0250] The second feedback module is used to feed back the node status and node resource information of the node to the PMU according to the node status query request.

[0251] Optionally, the device further comprises:

[0252] a tenth receiving module, configured to receive test data sent by the PMU;

[0253] A first verification module, used for verifying the signature data in the test data;

[0254] The first execution module is used to execute the test case in the test data if the verification passes.

[0255] Optionally, the device further comprises:

[0256] an eleventh receiving module, configured to receive the contract processing instruction information sent by the PMU;

[0257] A second verification module, used to verify the signature data in the contract processing instruction information;

[0258] The seventh processing module is used to install and / or update the contract according to the contract program file in the contract processing instruction information when the verification is passed, and to feed back processing response information to the PMU according to the processing result.

[0259] The embodiment of the present invention further provides a node management unit, the node management unit comprising: a processor and a transceiver;

[0260] The processor is configured to, upon receiving the first indication information, send second indication information to the first node through the transceiver according to the first indication information;

[0261] receiving, by the transceiver, node change result information fed back by the first node according to the second indication information;

[0262] The first indication information is used to instruct the first node to change the node type;

[0263] The second indication information includes first sub-information for instructing the first node to delete first-type information and second sub-information for instructing the first node to add second-type information;

[0264] The first type information is information indicating that the node type is a production type, and the second type information is information indicating that the node type is a test type; or, the first type information is information indicating that the node type is a test type, and the second type information is information indicating that the node type is a production type.

[0265] Optionally, the first indication information carries identification information of the first node;

[0266] The processor is specifically used for:

[0267] Acquire the registry information of the first node from the node registry PSR according to the identification information of the first node in the first indication information;

[0268] According to the IP address information in the registration table information, second indication information is sent to the first node through the transceiver.

[0269] Optionally, the processor is further configured to:

[0270] After receiving the node change result information fed back by the first node according to the second indication information, updating the node information of the first node according to the node change result information, and recording it in the node registration table PSR;

[0271] The node information includes at least one of node status information, node type information and information of installed contracts.

[0272] Optionally, the processor is further configured to:

[0273] After receiving the node change result information fed back by the first node according to the second indication information, the display is controlled to display the node change result information.

[0274] Optionally, the processor is further configured to:

[0275] After a preset time after confirming the existence of the newly added node type, confirm whether the nodes under the newly added node type meet the block consistency conditions;

[0276] In the case of non-compliance, the transceiver sends a block synchronization adjustment instruction to the nodes under the newly added node type to control the nodes under the newly added node type to comply with the block consistency condition.

[0277] Optionally, the second indication information also includes: third sub-information indicating whether the node type indicated by the second type information is a newly added type.

[0278] Optionally, the processor is specifically configured to:

[0279] Sending first sub-information to the first node through the transceiver according to the first indication information;

[0280] receiving, by the transceiver, first response information fed back by the first node according to the first sub-information;

[0281] According to the first response information, second sub-information is sent to the first node through the transceiver.

[0282] Optionally, the processor is further configured to:

[0283] When the third indication information is received, sending fourth indication information to the second node through the transceiver according to the third indication information;

[0284] receiving, by the transceiver, node joining result information fed back by the second node according to the fourth indication information;

[0285] The third indication information is used to indicate that the second node marks a node type;

[0286] The fourth indication information includes fourth sub-information for indicating that the second node marks the node type as a production type or a test type and fifth sub-information for indicating a contract to be installed;

[0287] The second node and the first node are the same node or different nodes.

[0288] Optionally, the second indication information carries identification information of the second node;

[0289] The processor is specifically used for:

[0290] Obtaining the registry information of the second node from the node registry PSR according to the identification information of the second node in the third indication information, and obtaining the information of the contract to be installed from the contract registry;

[0291] According to the IP address information and the information of the contract to be installed in the registration form information, fourth indication information is sent to the second node through the transceiver.

[0292] Optionally, the processor is specifically configured to:

[0293] Sending fourth sub-information to the second node through the transceiver according to the third indication information;

[0294] receiving, by the transceiver, second response information fed back by the second node according to the fourth sub-information;

[0295] According to the second response information, fifth sub-information is sent to the second node through the transceiver.

[0296] Optionally, the processor is further configured to:

[0297] After receiving the node joining result information fed back by the second node according to the fourth indication information, updating the node information of the second node according to the node joining result information, and recording it in the node registration table PSR;

[0298] The node information includes at least one of node status information, node type information and information of installed contracts.

[0299] Optionally, the processor is further configured to:

[0300] After receiving the node joining result information fed back by the second node according to the fourth indication information, the display is controlled to display the node joining result information.

[0301] Optionally, the processor is further configured to:

[0302] When receiving the node information of the third node, sending a node status query request to the third node through the transceiver according to the node information of the third node;

[0303] Receiving, by the transceiver, the node status and node resource information fed back by the third node according to the node status query request;

[0304] When the node status and the node resource information indicate that the third node is available, recording the node information of the third node into a node registration table PSR;

[0305] The third node and the first node are the same node or different nodes.

[0306] Optionally, the processor is further configured to:

[0307] After recording the node information of the third node into the node registration table PSR, the control display shows that the node status of the third node is available.

[0308] Optionally, the processor is further configured to:

[0309] Upon receiving the contract identifier, determining the record information of the contract identifier in the contract registration table;

[0310] Receiving the contract program and test set corresponding to the contract identifier through the transceiver;

[0311] According to the record information, the contract program and the test set are stored in the contract registration table.

[0312] Optionally, the processor is specifically configured to:

[0313] Determine whether it is a registered version of the contract according to the contract identifier;

[0314] If yes, obtain the record information corresponding to the contract identifier from the contract registry;

[0315] If not, the contract corresponding to the contract identifier is recorded in a contract registration table to obtain record information corresponding to the contract identifier.

[0316] Optionally, the processor is further configured to:

[0317] Upon receiving a test instruction, determining contract parameter information according to the test instruction;

[0318] According to the contract parameter information, obtain the corresponding test case from the contract registry;

[0319] Obtaining test data according to the test case and the signature data of the node management unit PMU;

[0320] Sending the test data to a node whose node type is a test type;

[0321] The contract parameter information includes at least one of a contract number and a contract name.

[0322] Optionally, the processor is further configured to:

[0323] In case of receiving a processing instruction for installing and / or updating a contract, sending contract processing instruction information to a fourth node via the transceiver according to the processing instruction;

[0324] Receiving, by the transceiver, processing response information fed back by the fourth node according to the contract processing instruction information;

[0325] The contract processing instruction information is used to instruct the installation and / or update of the contract;

[0326] The fourth node and the first node are the same node or different nodes.

[0327] Optionally, the processor is specifically configured to:

[0328] According to the processing instruction, obtain the contract program file from the contract registry;

[0329] According to the contract program file, the contract processing instruction information is sent to the fourth node through the transceiver.

[0330] Optionally, the processor is further configured to:

[0331] After receiving the processing response information fed back by the fourth node according to the contract processing instruction information, updating the node information of the fourth node;

[0332] The node information includes the information of the installed contract.

[0333] Optionally, the processor is further configured to:

[0334] After receiving the processing response information fed back by the fourth node according to the contract processing instruction information, the display is controlled to display the processing response information.

[0335] An embodiment of the present invention further provides a node, the node comprising: a processor and a transceiver;

[0336] The processor is configured to receive, through the transceiver, second indication information sent by a node management unit PMU;

[0337] Changing the node type according to the second indication information, and obtaining node change result information;

[0338] Feedback the node change result information to the PMU through the transceiver;

[0339] The second indication information includes first sub-information for instructing the node to delete the first type of information and second sub-information for instructing the node to add the second type of information;

[0340] The first type information is information indicating that the node type is a production type, and the second type information is information indicating that the node type is a test type; or, the first type information is information indicating that the node type is a test type, and the second type information is information indicating that the node type is a production type.

[0341] Optionally, the processor is specifically configured to:

[0342] According to the first sub-information in the second indication information, the first type of information is deleted; and according to the second sub-information in the second indication information, the second type of information is added.

[0343] Optionally, the second indication information also includes: third sub-information indicating whether the node type indicated by the second type information is a newly added type.

[0344] Optionally, the processor is further configured to:

[0345] In the case where the third sub-information indicates that the node type indicated by the second type information is a newly added type, the node type is changed according to the second indication information, and the production area information is copied to the test area after deleting the first type information and before adding the second type information.

[0346] Optionally, the processor is specifically configured to:

[0347] Use the preset method to copy the production area information to the test area;

[0348] The preset method includes at least one of the following methods:

[0349] Copy the production area data;

[0350] Replicate the access link for production area data.

[0351] Optionally, when the third sub-information indicates that the node type indicated by the second type information is not a newly added type, the processor is further configured to:

[0352] After the node type is changed according to the second indication information, chain block data is synchronized with nodes of the same node type.

[0353] Optionally, the processor is further configured to:

[0354] After changing the node type according to the second indication information, updating the contract version.

[0355] Optionally, the processor is further configured to:

[0356] Receiving, by the transceiver, a block synchronization adjustment instruction sent by the PMU;

[0357] According to the block synchronization adjustment instruction, the block data synchronization operation is adjusted.

[0358] Optionally, the processor is specifically configured to:

[0359] Receiving, by the transceiver, first sub-information sent by the PMU;

[0360] Feedback first response information to the PMU through the transceiver according to the first sub-information;

[0361] The second sub-information sent by the PMU according to the first response information is received by the transceiver.

[0362] Optionally, the processor is further configured to:

[0363] Receiving, by the transceiver, fourth indication information sent by the PMU;

[0364] According to the fourth indication information, marking the node type of the node as a production type or a test type, and an installation contract; and adding result information to the PMU feedback node through the transceiver;

[0365] The fourth indication information includes fourth sub-information for indicating that the node type is a production type or a test type and fifth sub-information for indicating a contract to be installed.

[0366] Optionally, the processor is specifically configured to:

[0367] Receiving, by the transceiver, fourth sub-information sent by the PMU;

[0368] Feedback second response information to the PMU through the transceiver according to the fourth sub-information;

[0369] The fifth sub-information sent by the PMU according to the second response information is received through the transceiver.

[0370] Optionally, the processor is specifically configured to:

[0371] According to the fourth sub-information, the node type of the node is marked as a production type or a test type; and, according to the fifth sub-information, a contract is installed.

[0372] Optionally, the processor is further configured to:

[0373] After marking the node type of the node as a production type or a test type according to the fourth indication information and installing the contract, if there are nodes of the same node type, chain block data synchronization is performed between nodes of the same node type.

[0374] Optionally, the processor is further configured to:

[0375] Receiving a node status query request sent by the PMU through the transceiver;

[0376] According to the node status query request, the node status and node resource information of the node are fed back to the PMU through the transceiver.

[0377] Optionally, the processor is further configured to:

[0378] Receiving the test data sent by the PMU through the transceiver;

[0379] Verifying the signature data in the test data;

[0380] If the verification is passed, the test cases in the test data are executed.

[0381] Optionally, the processor is further configured to:

[0382] Receiving the contract processing instruction information sent by the PMU through the transceiver;

[0383] Verifying the signature data in the contract processing instruction information;

[0384] If the verification is passed, the contract is installed and / or updated according to the contract program file in the contract processing instruction information, and processing response information is fed back to the PMU through the transceiver according to the processing result.

[0385] An embodiment of the present invention further provides a node management unit, comprising a memory, a processor, and a program stored in the memory and executable on the processor; when the processor executes the program, the information processing method on the node management unit side is implemented.

[0386] An embodiment of the present invention further provides a node, comprising a memory, a processor, and a program stored in the memory and executable on the processor; when the processor executes the program, the above-mentioned node-side information processing method is implemented.

[0387] The embodiment of the present invention further provides a readable storage medium on which a program is stored, and when the program is executed by a processor, the steps in the information processing method on the node management unit side are implemented; or,

[0388] When the program is executed by a processor, the steps in the above-mentioned node-side information processing method are implemented.

[0389] The beneficial effects of the above technical solution of the present invention are as follows:

[0390] In the above scheme, the information processing method sends second indication information to the first node according to the first indication information when receiving the first indication information; receives the node change result information fed back by the first node according to the second indication information; wherein the first indication information is used to instruct the first node to change the node type; the second indication information includes first sub-information for instructing the first node to delete the first type of information and second sub-information for instructing the first node to add the second type of information; the first type of information is information indicating that the node type is a production type, and the second type of information is information indicating that the node type is a test type; or, the first type of information is information indicating that the node type is a test type, and the second type of information is information indicating that the node type is a production type; it can support the conversion of node types, thereby realizing the combination of the test environment and the production environment, and the production environment and the test environment share the same smart contract, application and policy, avoiding the test deviation caused by the inconsistency between the test environment and the production environment, and improving the test accuracy; in addition, it is conducive to the open testing and supervision of blockchain smart contracts, and multiple organizations can join the unified blockchain network for testing, increase the openness and scenario diversity of the test, be more in line with the real scenario, and avoid the incomplete and insufficient testing in the closed environment of the organization; it is a good solution to the problems of poor development and low test accuracy of information processing solutions in the prior art. BRIEF DESCRIPTION OF THE DRAWINGS

[0391] Figure 1 Test network diagram for existing blockchains;

[0392] Figure 2 A schematic diagram of the existing generated and tested blockchain data;

[0393] Figure 3 The information processing method of the embodiment of the present invention is shown in FIG. Figure 1 ;

[0394] Figure 4 The information processing method of the embodiment of the present invention is shown in FIG. Figure 2 ;

[0395] Figure 5 A schematic diagram of component node types according to an embodiment of the present invention;

[0396] Figure 6 A schematic diagram of a blockchain network integrating production and testing according to an embodiment of the present invention;

[0397] Figure 7 A schematic diagram of the logical architecture of a node after adding a PMU unit according to an embodiment of the present invention;

[0398] Figure 8 This is a schematic diagram of the blockchain network organization of the PMU added in an embodiment of the present invention;

[0399] Fig. 9 This is a schematic diagram of the smart contract registration process according to an embodiment of the present invention;

[0400] Fig.10 A schematic diagram of a node registration process according to an embodiment of the present invention;

[0401] Fig.11 A schematic diagram of the process of adding a new node to a blockchain according to an embodiment of the present invention;

[0402] Fig.12 A schematic diagram of a node ownership change process according to an embodiment of the present invention;

[0403] Fig.13 A schematic diagram of a test flow of an embodiment of the present invention;

[0404] Fig.14 This is a schematic diagram of the smart contract installation and upgrade process according to an embodiment of the present invention;

[0405] Fig.15 The structure of the information processing device according to the embodiment of the present invention is shown in FIG. Figure 1 ;

[0406] Fig.16 The structure of the information processing device according to the embodiment of the present invention is shown in FIG. Figure 2 ;

[0407] Fig.17 A schematic diagram of the structure of a node management unit according to an embodiment of the present invention;

[0408] Fig.18 Schematic diagram of a node structure of an embodiment of the present invention. DETAILED DESCRIPTION

[0409] In order to make the technical problems, technical solutions and advantages to be solved by the present invention more clear, a detailed description will be given below with reference to the accompanying drawings and specific embodiments.

[0410] The present invention aims to solve the problems of poor development and low test accuracy of information processing solutions in the prior art, and provides an information processing method applied to a node management unit PMU, such as Figure 3 As shown, the method includes:

[0411] Step 31: upon receiving the first indication information, sending second indication information to the first node according to the first indication information;

[0412] Step 32: Receive the node change result information fed back by the first node based on the second indication information; wherein the first indication information is used to indicate that the first node changes its node type; the second indication information includes first sub-information used to indicate that the first node deletes first type information and second sub-information used to indicate that the first node adds second type information; the first type information is information indicating that the node type is a production type, and the second type information is information indicating that the node type is a test type; or, the first type information is information indicating that the node type is a test type, and the second type information is information indicating that the node type is a production type.

[0413] The above can realize the change of node type. The first node can be a blockchain node. The node type can be the type of the channel connected. Deleting the first type of information can be exiting the first channel, and adding the second type of information can be joining the second channel.

[0414] The information processing method provided by the embodiment of the present invention sends second indication information to the first node according to the first indication information when receiving the first indication information; receives the node change result information fed back by the first node according to the second indication information; wherein the first indication information is used to instruct the first node to change the node type; the second indication information includes first sub-information for instructing the first node to delete the first type of information and second sub-information for instructing the first node to add the second type of information; the first type of information is information indicating that the node type is a production type, and the second type of information is information indicating that the node type is a test type; or, the first type of information is information indicating that the node type is a test type, and the second type of information is information indicating that the node type is a production type; it can support the conversion of node types, thereby realizing the combination of the test environment and the production environment, and the production environment and the test environment share the same smart contract, application and policy, avoiding the test deviation caused by the inconsistency between the test environment and the production environment, and improving the test accuracy; in addition, it is conducive to the open testing and supervision of blockchain smart contracts, and multiple organizations can join the unified blockchain network for testing, increase the openness and scenario diversity of the test, be more in line with the real scenario, and avoid the incomplete and insufficient testing in the closed environment of the organization; it is a good solution to the problems of poor development and low test accuracy of information processing solutions in the prior art.

[0415] The first indication information carries identification information of the first node; the sending of second indication information to the first node according to the first indication information includes: obtaining registry information of the first node from a node registry PSR according to the identification information of the first node in the first indication information; and sending the second indication information to the first node according to the IP address information in the registry information.

[0416] Furthermore, after receiving the node change result information fed back by the first node according to the second indication information, it also includes: updating the node information of the first node according to the node change result information, and recording it in the node registry PSR; wherein the node information includes at least one of node status information, node type information and information of the installed contract.

[0417] Furthermore, after receiving the node change result information fed back by the first node according to the second indication information, the method further includes: displaying the node change result information.

[0418] In an embodiment of the present invention, the method further includes: after a preset time period after confirming the existence of a newly added node type, confirming whether the nodes under the newly added node type meet the block consistency conditions; if not, sending block synchronization adjustment instructions to the nodes under the newly added node type to control the nodes under the newly added node type to meet the block consistency conditions.

[0419] The second indication information further includes: third sub-information indicating whether the node type indicated by the second type information is a newly added type.

[0420] Specifically, sending the second indication information to the first node according to the first indication information includes: sending first sub-information to the first node according to the first indication information; receiving first response information fed back by the first node according to the first sub-information; and sending second sub-information to the first node according to the first response information.

[0421] Corresponding to the following new node joining process, the method also includes: when receiving the third indication information, sending the fourth indication information to the second node according to the third indication information; receiving the node joining result information fed back by the second node according to the fourth indication information; wherein the third indication information is used to indicate the second node to mark the node type; the fourth indication information includes the fourth sub-information used to indicate that the second node marks the node type as a production type or a test type and the fifth sub-information used to indicate the contract to be installed; the second node and the first node are the same node or different nodes.

[0422] Among them, the second node can specifically be a blockchain node.

[0423] Specifically, the second indication information carries the identification information of the second node; wherein, sending the fourth indication information to the second node according to the third indication information includes: obtaining the registry information of the second node from the node registry PSR according to the identification information of the second node in the third indication information, and obtaining the information of the contract to be installed from the contract registry; sending the fourth indication information to the second node according to the IP address information and the information of the contract to be installed in the registry information.

[0424] Among them, sending the fourth indication information to the second node according to the third indication information includes: sending fourth sub-information to the second node according to the third indication information; receiving second response information fed back by the second node according to the fourth sub-information; and sending fifth sub-information to the second node according to the second response information.

[0425] Furthermore, after receiving the node joining result information fed back by the second node according to the fourth indication information, it also includes: updating the node information of the second node according to the node joining result information, and recording it in the node registration table PSR; wherein the node information includes at least one of node status information, node type information and information of the installed contract.

[0426] Furthermore, after receiving the node joining result information fed back by the second node according to the fourth indication information, it also includes: displaying the node joining result information.

[0427] Corresponding to the following node registration process, the method also includes: when receiving the node information of the third node, sending a node status query request to the third node according to the node information of the third node; receiving the node status and node resource information fed back by the third node according to the node status query request; when the node status and node resource information indicate that the third node can be used, recording the node information of the third node in the node registration table PSR; wherein the third node and the first node are the same node or different nodes.

[0428] The third node may specifically be a blockchain node.

[0429] Furthermore, after recording the node information of the third node into the node registration table PSR, it also includes: displaying the node status of the third node as available for use.

[0430] Corresponding to the following contract registration process, the method also includes: when receiving a contract identifier, determining the record information of the contract identifier in the contract registration table; receiving the contract program and test set corresponding to the contract identifier; and storing the contract program and test set in the contract registration table according to the record information.

[0431] Furthermore, after the contract program and the test set are stored in the contract registry, information such as the version of the contract may be displayed.

[0432] Among them, determining the record information of the contract identifier in the contract registration table includes: determining whether it is a registered version of the contract based on the contract identifier; if so, obtaining the record information corresponding to the contract identifier from the contract registration table; if not, recording the contract corresponding to the contract identifier in the contract registration table to obtain the record information corresponding to the contract identifier.

[0433] Corresponding to the following test process, the method also includes: when receiving a test instruction, determining the contract parameter information according to the test instruction; obtaining the corresponding test case from the contract registry according to the contract parameter information; obtaining the test data according to the test case and the signature data of the PMU; sending the test data to a node whose node type is the test type; wherein the contract parameter information includes at least one of a contract number and a contract name.

[0434] Corresponding to the following contract installation and / or upgrade process, the method also includes: when receiving a processing instruction to install and / or update a contract, sending contract processing instruction information to a fourth node according to the processing instruction; receiving processing response information fed back by the fourth node according to the contract processing instruction information; wherein the contract processing instruction information is used to instruct the installation and / or update of the contract; the fourth node and the first node are the same node or different nodes.

[0435] The fourth node may specifically be a blockchain node.

[0436] Among them, sending contract processing instruction information to the fourth node according to the processing instruction includes: obtaining a contract program file from a contract registration table according to the processing instruction; and sending contract processing instruction information to the fourth node according to the contract program file.

[0437] Furthermore, after receiving the processing response information fed back by the fourth node according to the contract processing instruction information, it also includes: updating the node information of the fourth node; wherein the node information includes the information of the installed contract.

[0438] Furthermore, after receiving the processing response information fed back by the fourth node according to the contract processing instruction information, it also includes: displaying the processing response information.

[0439] The above-mentioned display operations can help users know the corresponding processing results.

[0440] The embodiment of the present invention further provides an information processing method, which is applied to a node (which may correspond to the first node, the second node, the third node and / or the fourth node), such as Figure 4 As shown, the method includes:

[0441] Step 41: receiving second indication information sent by the node management unit PMU;

[0442] Step 42: changing the node type according to the second indication information, and obtaining node change result information;

[0443] Step 43: Feedback the node change result information to the PMU; wherein the second indication information includes first sub-information for instructing the node to delete first type information and second sub-information for instructing the node to add second type information; the first type information is information indicating that the node type is a production type, and the second type information is information indicating that the node type is a test type; or, the first type information is information indicating that the node type is a test type, and the second type information is information indicating that the node type is a production type.

[0444] The above can realize the change of node type. The node can be a blockchain node. The node type can be the type of channel connected. Deleting the first type of information can be exiting the first channel, and adding the second type of information can be joining the second channel.

[0445] The information processing method provided by the embodiment of the present invention receives the second indication information sent by the node management unit PMU; changes the node type according to the second indication information, and obtains the node change result information; feeds back the node change result information to the PMU; wherein the second indication information includes a first sub-information for instructing the node to delete the first type of information and a second sub-information for instructing the node to add the second type of information; the first type of information is information indicating that the node type is a production type, and the second type of information is information indicating that the node type is a test type; or, the first type of information is information indicating that the node type is a test type, and the second type of information is information indicating that the node type is a production type; it can support the conversion of node types, thereby realizing the combination of the test environment and the production environment, and the production environment and the test environment share the same smart contract, application and policy, avoiding the test deviation caused by the inconsistency between the test environment and the production environment, and improving the test accuracy; in addition, it is conducive to the open testing and supervision of blockchain smart contracts, and multiple organizations can join the unified blockchain network for testing, increase the openness and scenario diversity of the test, and be more in line with the real scenario, avoiding the incomplete and insufficient testing in the closed environment of the organization; it is a good solution to the problems of poor development and low test accuracy of information processing solutions in the prior art.

[0446] The changing of the node type according to the second indication information includes: deleting first type information according to first sub-information in the second indication information; and adding second type information according to second sub-information in the second indication information.

[0447] Furthermore, the second indication information also includes: third sub-information indicating whether the node type indicated by the second type information is a newly added type.

[0448] Furthermore, in the case where the third sub-information indicates that the node type indicated by the second type information is a newly added type, the changing of the node type according to the second indication information also includes: after deleting the first type information and before adding the second type information, copying the production area information to the test area.

[0449] Wherein, copying the production area information to the test area includes: using a preset method to copy the production area information to the test area; wherein, the preset method includes at least one of the following methods: copying the production area data; copying the access link of the production area data.

[0450] In an embodiment of the present invention, when the third sub-information indicates that the node type indicated by the second type information is not a newly added type, after changing the node type according to the second indication information, it also includes: synchronizing chain block data with nodes of the same node type.

[0451] Furthermore, after changing the node type according to the second indication information, the method further includes: updating the contract version.

[0452] Furthermore, the method further includes: receiving a block synchronization adjustment instruction sent by the PMU; and adjusting the block data synchronization operation according to the block synchronization adjustment instruction.

[0453] The receiving of the second indication information sent by the node management unit PMU includes: receiving the first sub-information sent by the PMU; feeding back the first response information to the PMU according to the first sub-information; and receiving the second sub-information sent by the PMU according to the first response information.

[0454] Corresponding to the following new node joining process, the method also includes: receiving fourth indication information sent by the PMU; marking the node type of the node as a production type or a test type, and installing a contract according to the fourth indication information; and adding result information to the PMU feedback node; wherein the fourth indication information includes fourth sub-information for indicating that the node type is marked as a production type or a test type and fifth sub-information for indicating the contract to be installed.

[0455] The receiving of the fourth indication information sent by the PMU includes: receiving fourth sub-information sent by the PMU; feeding back second response information to the PMU according to the fourth sub-information; and receiving fifth sub-information sent by the PMU according to the second response information.

[0456] Specifically, marking the node type of the node as a production type or a test type and installing the contract according to the fourth indication information includes: marking the node type of the node as a production type or a test type according to the fourth sub-information; and installing the contract according to the fifth sub-information.

[0457] Furthermore, after marking the node type of the node as a production type or a test type according to the fourth indication information and installing the contract, it also includes: when there are nodes of the same node type, synchronizing chain block data between nodes of the same node type.

[0458] Corresponding to the following node registration process, the method further includes: receiving a node status query request sent by the PMU; and feeding back the node status and node resource information of the node to the PMU according to the node status query request.

[0459] Corresponding to the following test process, the method further includes: receiving test data sent by the PMU; verifying the signature data in the test data; and executing the test cases in the test data if the verification passes.

[0460] Corresponding to the following contract installation and / or upgrade process, the method also includes: receiving contract processing instruction information sent by the PMU; verifying the signature data in the contract processing instruction information; if the verification passes, installing and / or updating the contract according to the contract program file in the contract processing instruction information, and feeding back processing response information to the PMU based on the processing result.

[0461] The information processing method provided by the embodiment of the present invention is further described below in conjunction with multiple sides such as a node management unit and a node, wherein the above-mentioned contract is hereinafter referred to as a smart contract, and the above-mentioned node may correspond to each node involved below, which is not limited here.

[0462] First of all, the blockchain network is a technical infrastructure that provides ledger and smart contract services for applications. First, smart contracts are used to generate transactions, which are then distributed to each node in the network and recorded on each node's copy of the ledger and cannot be tampered with.

[0463] In most cases, multiple organizations come together as a consortium to form a network. A blockchain network is mainly composed of a group of nodes. Nodes host ledgers, smart contracts, and policies. An organization joins or exits a blockchain network by deploying or revoking nodes. Therefore, nodes can be considered as physical devices of a blockchain network, while ledgers, smart contracts, policies, etc. are logical units of the blockchain.

[0464] Based on the above, in view of the above technical problems, an embodiment of the present invention provides an information processing method, which can be based on Figure 5 and Figure 6 The blockchain network implementation shown in FIG. Figure 5 , through each organization to increase the production and testing of two types of nodes, such as Figure 6 , generating multiple logically independent virtual blockchain networks in a unified physical blockchain. The production nodes form a unique blockchain production environment, and the test nodes form multiple virtual environments for different purposes, such as performance testing and pre-launch test networks for new versions of smart contracts.

[0465] Specifically, an organization can join the following types of nodes:

[0466] 1. Add production nodes and test nodes at the same time. In this case, there are two configurations for the number of production nodes and test nodes: static configuration, which refers to a fixed number of production nodes and test nodes or a fixed ratio between production nodes and test nodes; and dynamic configuration, which is dynamically adjusted according to the access traffic of the production environment and the test environment.

[0467] 2. Join only production nodes. In this case, from the perspective of the organization, this blockchain is a production blockchain network.

[0468] 3. Only join the test node. In this case, from the perspective of the organization, this blockchain is a test blockchain network. Currently, an online test blockchain network is provided, which is conducive to guiding organizations to use the blockchain network.

[0469] Among them, multiple logical blockchain networks follow the following technical requirements:

[0470] 1. The test blockchain network produced by the mirror follows the relevant smart contracts and policies of the production environment (defining the permissions of each organization to join the blockchain network, etc.);

[0471] 2. The test blockchain network produced by the mirror can read the block data of the nodes in the production environment to build blocks for testing. The block reading can read the genesis block or any intermediate block according to the needs;

[0472] 3. The node can be a production node or a test node. When the node is converted between a production node and a test node, the blockchain data of its production environment is permanently valid. When it is restored from a test node to a production node, it is only necessary to upload the production transaction data of the period of time as a test node to the chain. The test chain data of the test node can be retained or deleted according to the storage status of the node. The data of the test chain and the production chain are strictly separated.

[0473] In addition, in order to realize the above production and test integration of blockchain network, it is necessary to add a Peer Management Unit (PMU) to the existing blockchain network. PMU is a logical functional unit, which can add related functions or new functional modules to the current blockchain network management tool. PMU mainly realizes the following functions:

[0474] (1) Node registration;

[0475] (2) Node configuration;

[0476] (3) Smart contract management;

[0477] (4) Functions such as switching of production test networks.

[0478] Among them, PMU is only responsible for the management process of the node, and does not participate in the business processes such as the status query and on-chain transaction of the blockchain network, and does not change the channels, endorsement strategies, smart contracts and configuration and functions of the application programs of the existing blockchain network. This has little impact on the existing blockchain network itself, and is convenient for the subsequent upgrade and implementation of the blockchain network.

[0479] The blockchain network channel needs to add a type field to indicate the production or test network, and the data storage on the node needs to distinguish between the production area and the test area.

[0480] Two information registries need to be added to the PMU, one is the smart contract registry (SCR) and the other is the peer state registry (PSR). For efficiency reasons, the PMU can store the index information of the SCR and PSR. The index information can only include the code, name, and channel fields.

[0481] The SCR includes but is not limited to the following fields:

[0482] Table 1 Smart Contract Registry

[0483]

[0484] PSR contains but is not limited to the following fields:

[0485] Table 2 Node status registration table

[0486]

[0487]

[0488] The logical architecture of the node after adding the PMU unit can be seen in Figure 7 , where the node management unit technology implementation requirements are as follows:

[0489] a) The node management unit can produce multiple instances in the blockchain network. Generally, each organization in the blockchain needs to install an instance of PMU to manage the nodes and smart contracts belonging to the organization. PMU changes the production and test type of the node by adjusting the configuration parameters of the blockchain system; including the storage configuration of the linked list, certificate configuration, etc.

[0490] b) The node management unit should store the node registry and smart contract registry as well as the certificate issued by the organization (the certificate issuance process is generally that the PMU of each organization generates a public-private key pair and provides the public key and related PMU information to request the affiliated organization to sign), so as to determine the organizational affiliation of the PMU. At the same time, in accordance with the certificate and member management requirements of the blockchain network, the PMU certificate needs to be broadcast to each node and stored in the member service directory of each node. In this way, each node of the organization can allow the PMU to access and control through certificate verification to change the configuration parameters of the node, so as to achieve the function of the PMU setting the node type and reading the block data from the production area. The specific technical implementation is described in conjunction with the following processes.

[0491] The above integers can be understood as signatures. Figure 7 The chain block directory and database access parameters in the blockchain account book include the chain block and the world state. In the implementation, the chain block is the file system, and the world state is the database. Therefore, to store the blockchain, it is necessary to configure its related file directory or database access parameters to store the blockchain account book.

[0492] The blockchain organizational structure after joining the PMU unit can be found in Figure 8 , Among them, PMU does not participate in the transaction query and on-chain business processes of the blockchain, and serves as the node management unit of each organization.

[0493] The following is an example of an information processing method provided by an embodiment of the present invention.

[0494] Example 1: Smart contract registration process, such as Fig. 9 As shown:

[0495] The organization administrator provides a request to register a smart contract to the PMU and provides the contract name (corresponding to the PMU receiving the contract identifier); the PMU checks whether it is a new smart contract or a new version (corresponding to the PMU determining whether it is a registered version of the contract based on the contract identifier); if so, register it on the SCR (corresponding to recording the contract corresponding to the contract identifier in the contract registration table to obtain the record information corresponding to the contract identifier); if not, obtain the smart contract information from the SCR (corresponding to obtaining the record information corresponding to the contract identifier from the contract registration table);

[0496] The organization administrator provides the smart contract program and test set (i.e., the contract program and test set corresponding to the contract identifier mentioned above) to the PMU, and the PMU determines the version number of the smart contract program and test set (the version number can be expressed as a version number or timestamp that increases from 1), and then registers the smart contract program and test set on the SCR. Then, the PMU confirms the completion of the registration and returns the version information to the organization administrator. Specifically, the technical implementation requirements involved are as follows:

[0497] The content of the smart contract is shown in Table 2. It can be stored in a database or configuration file inside or outside the PMU.

[0498] a) To ensure the tamper-proof requirements of smart contracts, when PMU stores smart contracts, it can use its storage content of PMU for signing, and when reading or using peer nodes (peer nodes are a type of block nodes, corresponding to the Peer appearing in the text, translated as peer nodes, referred to as nodes), the PMU certificate can be called for verification to maintain the legitimacy of smart contract data; the signature data can be stored in a column in the smart contract registry or in an independent table or file.

[0499] b) PMU encapsulates smart contracts and provides external access interfaces such as adding, modifying, deleting, and querying. The data returned in the query interface includes smart contract registry information and signature data, allowing external nodes to verify the signature.

[0500] c) Smart contracts include program files and test scripts, so the original data for signing a smart contract can be in the following format:

[0501] Smart contract number Note 1 + smart contract name + SHA1[program file] + SHA1[test file 1] + … + SHA1[test file n]

[0502] Note 1: The format of signature data is bytecode, so both string and numeric types need to be converted to bytecode. For example, A is encoded in bytecode 0x41, B is encoded in 0x42, ..., so "ABC" is converted to bytecode as byte[] = {0x41, 0x42, 0x43}. Generally, the program can implement String.getBytes() to complete the above conversion.

[0503] Example 2: Node registration process, such as Fig.10 As shown:

[0504] The organization administrator provides the node information to the PMU, and the PMU checks whether the corresponding node is available (corresponding to the above-mentioned sending of a node status query request to the third node according to the node information of the third node when the node information of the third node is received), the node Peer returns the status and node resource information to the PMU (corresponding to the above-mentioned receiving the node status and node resource information fed back by the third node according to the node status query request), and the PMU registers the node information to the PSR (corresponding to the above-mentioned recording of the node information of the third node in the node registration table PSR when the node status and node resource information indicate that the third node can be used), and then completes the registration and feeds back to the organization administrator that the node status is available (corresponding to the above-mentioned display that the node status of the third node is available).

[0505] The technical implementation requirements of the node registry are the same as those of the smart contract. The source data of its signature is:

[0506] Node number + node address + node status + channel + organization + smart contract number 1 + ... smart contract number n.

[0507] Example 3: A new node joins the blockchain (production or testing) process, such as Fig.11 As shown:

[0508] The organization administrator provides a request to join the node to the production or test network of the specified channel, and the PMU obtains the node information from the PSR and the smart contract information from the SCR accordingly (corresponding to obtaining the registry information of the second node from the node registry PSR according to the identification information of the second node in the third indication information, and obtaining the information of the contract to be installed from the contract registry); then the PMU notifies the available nodes to join the specified channel (corresponding to sending the fourth sub-information to the second node according to the third indication information); the available nodes run the instruction to join the channel and join the specified channel (corresponding to marking the node type of the node as a production type or a test type according to the fourth sub-information); then the PMU instructs the available nodes to install The smart contract (corresponding to the above-mentioned receiving the second response information fed back by the second node according to the fourth sub-information; sending the fifth sub-information to the second node according to the second response information), the available node installs the smart contract accordingly (corresponding to the above-mentioned installation of the contract according to the fifth sub-information); then the available node returns the result to the PMU (corresponding to the above-mentioned feedback of the node joining result information to the PMU), and the PMU updates the node status and smart contract version information accordingly (corresponding to the above-mentioned updating of the node information of the second node according to the node joining result information, and recording it in the node registry PSR); further, the PMU notifies the organization administrator to complete the joining of the new node (corresponding to the above-mentioned display of the node joining result information).

[0509] In addition, when there is already a node in the designated channel to which the available node belongs, chain block synchronization is performed (corresponding to the above-mentioned case where there are nodes of the same node type, chain block data synchronization is performed between nodes of the same node type).

[0510] in:

[0511] a) The process of adding a new node to the production environment or the test environment is the same.

[0512] b) This example involves the communication between the PMU and the node, the modification of the registry information, the addition of blockchain instructions, the installation of smart contracts, and the synchronization of data between nodes. At the same time, the synchronization between nodes is an asynchronous process. Depending on the difference between the blocks of the newly installed or connected nodes and the existing node blocks, the data synchronization time may last for several minutes or hours.

[0513] c) The Peer node can verify the certificate information of the PMU to confirm that the PMU unit and the Peer node belong to the same organization and have the authority to operate the Peer node. Before installing the smart contract, the Peer node needs to confirm the signature information of the smart contract to ensure that the smart contract has not been tampered with to ensure the correctness of the smart contract.

[0514] Example 4: Node ownership change process, adding nodes from the blockchain production network to the test network. Fig.12 As shown:

[0515] The organization administrator provides the PMU with an instruction to add the node to the test area. The PMU obtains the node information from the PSR accordingly, and then instructs the designated node to exit the production channel (corresponding to the above-mentioned acquisition of the registry information of the first node from the node registry PSR according to the identification information of the first node in the first indication information when the first indication information is received; and sending the first sub-information to the first node according to the IP address information in the registry information); after receiving the instruction, the designated node runs the channel instruction, exits the production channel (corresponding to the above-mentioned deletion of the first type of information according to the first sub-information in the second indication information, and feedback of the first response information to the PMU), and copies the production area data to the test area (corresponding to the above-mentioned copying of the production area information to the test area after deleting the first type of information and before adding the second type of information); then the PMU instructs the designated node to join the test channel (corresponding to the above-mentioned receipt of the first node root According to the first response information fed back by the first sub-information; according to the first response information, the second sub-information is sent to the first node), the designated node runs channel signaling, creates or joins the designated test channel (corresponding to the above-mentioned receiving the second sub-information sent by the PMU according to the first response information, and adding the second type of information according to the second sub-information), and performs smart contract version upgrade (corresponding to the above-mentioned updating of the contract version after changing the node type according to the second indication information), updates the smart contract on the channel, and returns the result to the PMU (corresponding to the above-mentioned feedback of the node change result information to the PMU); the PMU updates the node information accordingly (corresponding to the above-mentioned updating of the node information of the first node according to the node change result information, and recording it in the node registry PSR), and then the PMU notifies the organization administrator to complete the node change (corresponding to the above-mentioned display of the node change result information).

[0516] In addition, when a node already exists in the test channel to which the designated node belongs, chain block synchronization is performed (corresponding to the above-mentioned situation in which the third sub-information indicates that the node type indicated by the second type information is not a newly added type, after the node type is changed according to the second indication information, chain block data synchronization is performed between nodes of the same node type).

[0517] The PMU can also determine that if a new test channel is created, block consistency is checked (corresponding to the above-mentioned confirmation of whether the nodes under the newly added node type meet the block consistency conditions after a preset time after confirming the existence of the newly added node type; if not, a block synchronization adjustment instruction is sent to the nodes under the newly added node type to control the nodes under the newly added node type to meet the block consistency conditions).

[0518] Regarding checking block consistency, PMU can perform block consistency check after confirming the existence of a new channel for a period of time; it can be performed according to the chain block directory (block number and sequence number) and synchronize the inconsistent ones.

[0519] The node information updated by the PMU may specifically include the channel to which the node joins and the corresponding contract information.

[0520] It should be noted that in this solution, after a node joins a channel, it can broadcast to all nodes under the management of the PMU to synchronize the chain block data.

[0521] Specifically, the technical implementation requirements of the node change process are as follows:

[0522] a) If the test area nodes are added to the production area, the data replication process and block consistency check process may not be included.

[0523] b) The above process can add one or more nodes from the production area to the test area at the same time. There are two situations. One is to join the existing test area channel, which may not include the data replication involved above (i.e. copying the production area data to Fig.12 The blockchain test (indicates the blockchain and the test type) process and the block consistency check process in the . Only when a new test channel is created (such as a new version of smart contract testing), it is necessary to copy the block data from the production area and check the data consistency. Specifically, the PMU can inform the node whether it is a new channel.

[0524] c) The purpose of block data consistency check is to avoid data inconsistency when batch nodes are traded after joining the test area from the production area. As mentioned above, block data synchronization is an abnormal operation and may last for a period of time. For example, when node A exits the production environment, the block data is written to production block m, and when node B exits the production environment, the block data is written to production block m+1. If data synchronization is not completed after joining the test environment, the test case execution starts, node A executes the test case, and writes test block m+1, so that the data of m+1 blocks of nodes A and B are inconsistent. Therefore, after joining the test area, PMU checks the synchronization execution, keeps the data of nodes A and B synchronized to production block m+1, and writes test data starting from m+2.

[0525] d) Node information updates include: node status, ownership, and installed smart contract information and versions.

[0526] e) The node is switched to the blockchain network by stopping or starting the node (as above, instructing the node to exit the production channel or join the test channel). The parameters usually included in starting a node include: the node's certificate directory, the node's blockchain storage directory, and the database configuration parameters for the node's storage status data. The configuration parameters of the production or test blockchain network are installed and configured on the node to achieve the purpose of joining the production or test blockchain network.

[0527] f) Replication of blockchain ledger data. The underlying storage of block data is a file system, and the built-in database stores the blockchain index, and the block file number and its offset can be located by the block number or transaction ID. Therefore, there are two ways to replicate the chain block data in the production area: physical replication (specifically, replication of data) and logical replication (specifically, replication of links). Specifically:

[0528] Method 1) Physical copying: The blockchain built-in index database locates the transaction ID or chain block number to be copied to determine the file number and offset. The specified file number and the data and index data before the deviation are copied to the test area, and the directory data of the index data is changed. For example, the original index record:

[0529] Block number 00222–> / prod / blkfile032 offset:1000;

[0530] Change to:

[0531] Block number 00222–> / test / blkfile032 offset:1000.

[0532] Method 2) Logical replication, only copy the index data to the test area. Subsequent test data can be placed in the / test / directory, and the data copied from the production area remains in the production area. In this way, the blockchain index includes two prefixes: prod indicates production area data, and test indicates test area data.

[0533] Example 5, test process, such as Fig.13 As shown:

[0534] The organization administrator requests the PMU to specify the channel test, and the PMU obtains the test case from the SCR (corresponding to the above-mentioned determination of the contract parameter information according to the test instruction upon receipt of the test instruction; and obtaining the corresponding test case from the contract registry according to the contract parameter information); the PMU instructs the node of the affiliated test channel to execute test case 1 (corresponding to the above-mentioned acquisition of test data according to the test case and the signature data of the PMU; and sending the test data to the node whose node type is the test type); the node interacts with the blockchain of the test type (i.e., the blockchain test in the figure) for network consensus and transaction on-chain to complete the test of case 1; subsequently, the PMU can instruct the node of the affiliated test channel to execute test case n, which is similar to test case 1 and will not be repeated here. The above can also be understood as: the organization administrator selects the test channel through the PMU, the PMU provides the smart contract number and name on the test channel, the PMU requests the SCR through the smart contract number, and the SCR returns the test case of the formulated smart contract to the PMU; the PMU sends the test cases one by one to the affiliated channel Peer to execute the cases.

[0535] Specifically, the technical implementation requirements are as follows:

[0536] a) The node can verify the signature data of the smart contract, and if the verification is correct, execute the subsequent test cases (corresponding to the above-mentioned node receiving the test data sent by the PMU; verifying the signature data in the test data; and executing the test cases in the test data if the verification is successful);

[0537] b) The execution of the test case includes a technical process of three stages: proposal, sorting, packaging transactions into blocks, and verification and submission. The specific implementation can be done using existing methods and will not be described in detail here.

[0538] Example 6: Smart contract installation and upgrade process, such as Fig.14 As shown:

[0539] The organization administrator requests the PMU to install or upgrade the smart contract, and the PMU obtains the smart contract from the SCR accordingly, and then instructs the corresponding node to upgrade the smart contract (corresponding to the above-mentioned case where the processing instruction for installing and / or updating the contract is received, the contract program file is obtained from the contract registry according to the processing instruction; and the contract processing instruction information is sent to the fourth node according to the contract program file); after receiving the instruction, the node installs or upgrades the smart contract accordingly (corresponding to the above-mentioned receiving the contract processing instruction information sent by the PMU; verifying the signature data in the contract processing instruction information; if the verification is passed, the contract is installed and / or updated according to the contract program file in the contract processing instruction information), and then the node executes the channel smart contract instance update to the blockchain, and then responds to the PMU (corresponding to the above-mentioned feedback of processing response information to the PMU according to the processing result); the PMU updates the node information to the PSR accordingly (corresponding to the above-mentioned updating of the node information of the fourth node after receiving the processing response information fed back by the fourth node according to the contract processing instruction information), and then notifies the organization administrator that the process is completed (corresponding to the above-mentioned display of the processing response information).

[0540] The above can also be understood as: the organization administrator requests to install or upgrade the smart contract in PMU, selects the smart contract to be installed, and requests SCR to return the program file of the smart contract according to the smart contract number. PMU installs or upgrades the program file of the smart contract to Peer, and Peer performs subsequent operations accordingly (see above).

[0541] The node information to be updated may include the channel and contract to which the node belongs.

[0542] Specifically, the technical implementation requirements are as follows:

[0543] a) The node can verify the signature data of the smart contract. If the verification is correct, the subsequent smart contract installation or upgrade process will be executed;

[0544] b) The installation or upgrade of smart contracts can be implemented using existing methods, which will not be described in detail here.

[0545] The following is an example of the application scenario process of this solution.

[0546] The processes involved in the above examples can be combined and used in various scenarios. For example, the following process can be used in the new version test launch scenario:

[0547] 1. Execute the process involved in Example 1: smart contract registration process, submit a new version of the smart contract and test set.

[0548] 2. Execute the process involved in Example 4: Create a new test channel for some nodes from the production area. You can use the data in the production environment to avoid the preparation of a large amount of test data and test data. If the node resources are insufficient, you can execute the process involved in Example 2 and Example 3 to add new nodes to join the test network.

[0549] 3. Execute the process involved in Example 5 to test the new version of the smart contract. During the testing process, each time the smart contract is updated, the processes involved in Examples 1 and 6 need to be executed.

[0550] 4. After the test is completed, execute the process involved in Example 6 to upgrade the smart contract of the node in the production environment.

[0551] 5. Execute the process involved in Example 4, add the test node to the production area, and restore the block data synchronization from the last time it exited the production area.

[0552] Other typical application scenarios:

[0553] 1. Performance testing: By adjusting the ratio of test nodes to production nodes, increasing the number of test nodes during idle time, and using production data for performance testing, this saves investment in server resources and reduces the cost and time of building test data and test cases.

[0554] 2. Before the new smart contract is officially launched, multiple organizers configure all nodes as test nodes and conduct full pre-launch testing with the joint participation of multiple parties. After the test is completed, the smart contract is launched by adjusting the ratio of production nodes and test nodes.

[0555] As can be seen from the above, this solution proposes the functions and architecture of the node management unit PMU added to the blockchain network, as well as the technical methods for PMU to manage and implement the original peer nodes of the blockchain; thereby achieving:

[0556] 1. It is conducive to the open testing and supervision of blockchain smart contracts. Multiple organizations join the unified blockchain network for testing, which increases the openness and scenario diversity of the test, and is more in line with the real scene; it avoids the incomplete and insufficient testing in the closed environment of the organization. At the same time, due to the irrevocability of the blockchain, "code and law" is proposed. The correctness of the code depends on the programmer. A public and open test network is conducive to various personnel to verify the correctness of the smart contract.

[0557] 2. The production environment and the test environment share the same smart contracts, applications, and policies; avoiding test deviations caused by inconsistencies between the test environment and the production environment.

[0558] 3. Seamless connection for new smart contract testing and release, adjustable node ratio, and smooth transition from test network to production network.

[0559] The embodiment of the present invention further provides an information processing device, which is applied to a node management unit PMU, such as Fig.15 As shown, the device comprises:

[0560] A first sending module 151 is configured to send second indication information to the first node according to the first indication information when receiving the first indication information;

[0561] A first receiving module 152, configured to receive node change result information fed back by the first node according to the second indication information;

[0562] The first indication information is used to instruct the first node to change the node type;

[0563] The second indication information includes first sub-information for instructing the first node to delete first-type information and second sub-information for instructing the first node to add second-type information;

[0564] The first type information is information indicating that the node type is a production type, and the second type information is information indicating that the node type is a test type; or, the first type information is information indicating that the node type is a test type, and the second type information is information indicating that the node type is a production type.

[0565] The information processing device provided by the embodiment of the present invention sends second indication information to the first node according to the first indication information when receiving the first indication information; receives the node change result information fed back by the first node according to the second indication information; wherein the first indication information is used to instruct the first node to change the node type; the second indication information includes first sub-information for instructing the first node to delete the first type of information and second sub-information for instructing the first node to add the second type of information; the first type of information is information indicating that the node type is a production type, and the second type of information is information indicating that the node type is a test type; or, the first type of information is information indicating that the node type is a test type, and the second type of information is information indicating that the node type is a production type; it can support the conversion of node types, thereby realizing the combination of the test environment and the production environment, and the production environment and the test environment share the same smart contract, application and policy, avoiding the test deviation caused by the inconsistency between the test environment and the production environment, and improving the test accuracy; in addition, it is conducive to the open testing and supervision of blockchain smart contracts, and multiple organizations can join the unified blockchain network for testing, increase the openness and scenario diversity of the test, be more in line with the real scenario, and avoid the incomplete and insufficient testing in the closed environment of the organization; it is a good solution to the problems of poor development and low test accuracy of information processing solutions in the prior art.

[0566] Among them, the first indication information carries the identification information of the first node; wherein, the first sending module includes: a first acquisition submodule, used to obtain the registration information of the first node from the node registration table PSR according to the identification information of the first node in the first indication information; a first sending submodule, used to send the second indication information to the first node according to the IP address information in the registration table information.

[0567] Furthermore, the information processing device also includes: a first processing module, which is used to update the node information of the first node according to the node change result information after receiving the node change result information fed back by the first node according to the second indication information, and record it in the node registration table PSR; wherein the node information includes at least one of node status information, node type information and information of the installed contract.

[0568] Furthermore, the information processing device also includes: a first display module, which is used to display the node change result information after receiving the node change result information fed back by the first node according to the second indication information.

[0569] In an embodiment of the present invention, the device also includes: a first confirmation module, used to confirm whether the nodes under the newly added node type meet the block consistency conditions after a preset time after confirming the existence of the newly added node type; a second processing module, used to send block synchronization adjustment instructions to the nodes under the newly added node type if they do not meet the conditions, so as to control the nodes under the newly added node type to meet the block consistency conditions.

[0570] The second indication information further includes: third sub-information indicating whether the node type indicated by the second type information is a newly added type.

[0571] Specifically, the first sending module includes: a second sending sub-module, used to send first sub-information to the first node according to the first indication information; a first receiving sub-module, used to receive first response information fed back by the first node according to the first sub-information; and a third sending sub-module, used to send second sub-information to the first node according to the first response information.

[0572] Corresponding to the following new node joining process, the device also includes: a second sending module, used to send fourth indication information to the second node according to the third indication information when receiving the third indication information; a second receiving module, used to receive the node joining result information fed back by the second node according to the fourth indication information; wherein the third indication information is used to indicate the second node to mark the node type; the fourth indication information includes fourth sub-information used to indicate that the second node marks the node type as a production type or a test type and fifth sub-information used to indicate the contract to be installed; the second node and the first node are the same node or different nodes.

[0573] Specifically, the second indication information carries the identification information of the second node; wherein the second sending module includes: a first processing sub-module, used to obtain the registry information of the second node from the node registry PSR according to the identification information of the second node in the third indication information, and to obtain the information of the contract to be installed from the contract registry; a fourth sending sub-module, used to send a fourth indication information to the second node according to the IP address information and the information of the contract to be installed in the registry information.

[0574] Among them, the second sending module includes: a fifth sending sub-module, used to send fourth sub-information to the second node according to the third indication information; a second receiving sub-module, used to receive second response information fed back by the second node according to the fourth sub-information; and a sixth sending sub-module, used to send fifth sub-information to the second node according to the second response information.

[0575] Furthermore, the information processing device also includes: a third processing module, which is used to update the node information of the second node according to the node joining result information after receiving the node joining result information fed back by the second node according to the fourth indication information, and record it in the node registration table PSR; wherein the node information includes at least one of node status information, node type information and information of the installed contract.

[0576] Furthermore, the information processing device also includes: a second display module, which is used to display the node joining result information after receiving the node joining result information fed back by the second node according to the fourth indication information.

[0577] Corresponding to the following node registration process, the device also includes: a third sending module, which is used to send a node status query request to the third node according to the node information of the third node when the node information of the third node is received; a third receiving module, which is used to receive the node status and node resource information fed back by the third node according to the node status query request; a first recording module, which is used to record the node information of the third node into the node registration table PSR when the node status and node resource information indicate that the third node can be used; wherein the third node and the first node are the same node or different nodes.

[0578] Furthermore, the information processing device further includes: a third display module, which is used to display the node status of the third node as being available after recording the node information of the third node into the node registration table PSR.

[0579] Corresponding to the following contract registration process, the device also includes: a first determination module, used to determine the record information of the contract identifier in the contract registration table when the contract identifier is received; a fourth receiving module, used to receive the contract program and test set corresponding to the contract identifier; a first storage module, used to store the contract program and test set in the contract registration table according to the record information.

[0580] Among them, the first determination module includes: a first determination sub-module, used to determine whether it is a registered version of the contract based on the contract identifier; a second acquisition sub-module, used to obtain the record information corresponding to the contract identifier from the contract registration table if it is the case; and a first recording sub-module, used to record the contract corresponding to the contract identifier in the contract registration table if it is not the case, and obtain the record information corresponding to the contract identifier.

[0581] Corresponding to the following test process, the device also includes: a second determination module, used to determine the contract parameter information according to the test instruction when a test instruction is received; a first acquisition module, used to obtain the corresponding test case from the contract registry according to the contract parameter information; a fourth processing module, used to obtain the test data according to the test case and the signature data of the PMU; a fourth sending module, used to send the test data to a node whose node type is a test type; wherein the contract parameter information includes at least one of a contract number and a contract name.

[0582] Corresponding to the following contract installation and / or upgrade process, the device also includes: a fifth sending module, which is used to send contract processing instruction information to the fourth node according to the processing instruction when receiving the processing instruction of installing and / or updating the contract; a fifth receiving module, which is used to receive the processing response information fed back by the fourth node according to the contract processing instruction information; wherein, the contract processing instruction information is used to instruct the installation and / or update of the contract; the fourth node and the first node are the same node or different nodes.

[0583] Among them, the fifth sending module includes: a third acquisition sub-module, used to obtain the contract program file from the contract registration table according to the processing instruction; and a seventh sending sub-module, used to send contract processing instruction information to the fourth node according to the contract program file.

[0584] Furthermore, the information processing device also includes: a first update module, used to update the node information of the fourth node after receiving the processing response information fed back by the fourth node based on the contract processing indication information; wherein the node information includes information of the installed contract.

[0585] Furthermore, the information processing device also includes: a fourth display module, which is used to display the processing response information after receiving the processing response information fed back by the fourth node according to the contract processing instruction information.

[0586] Among them, the implementation embodiments of the information processing method on the node management unit side are all applicable to the embodiments of the information processing device and can achieve the same technical effects.

[0587] The embodiment of the present invention also provides an information processing device, which is applied to a node, such as Fig.16 As shown, the device comprises:

[0588] A sixth receiving module 161, configured to receive second indication information sent by the node management unit PMU;

[0589] A fifth processing module 162, configured to change the node type according to the second indication information and obtain node change result information;

[0590] A first feedback module 163, configured to feed back the node change result information to the PMU;

[0591] The second indication information includes first sub-information for instructing the node to delete the first type of information and second sub-information for instructing the node to add the second type of information;

[0592] The first type information is information indicating that the node type is a production type, and the second type information is information indicating that the node type is a test type; or, the first type information is information indicating that the node type is a test type, and the second type information is information indicating that the node type is a production type.

[0593] The information processing device provided by the embodiment of the present invention receives the second indication information sent by the node management unit PMU; changes the node type according to the second indication information, and obtains the node change result information; feeds back the node change result information to the PMU; wherein the second indication information includes a first sub-information for instructing the node to delete the first type of information and a second sub-information for instructing the node to add the second type of information; the first type of information is information indicating that the node type is a production type, and the second type of information is information indicating that the node type is a test type; or, the first type of information is information indicating that the node type is a test type, and the second type of information is information indicating that the node type is a production type; it can support the conversion of node types, thereby realizing the combination of the test environment and the production environment, and the production environment and the test environment share the same smart contract, application and policy, avoiding the test deviation caused by the inconsistency between the test environment and the production environment, and improving the test accuracy; in addition, it is conducive to the open testing and supervision of blockchain smart contracts, and multiple organizations can join the unified blockchain network for testing, increase the openness and scenario diversity of the test, be more in line with the real scenario, and avoid the incomplete and insufficient testing in the closed environment of the organization; it is a good solution to the problems of poor development and low test accuracy of information processing solutions in the prior art.

[0594] The fifth processing module includes: a second processing submodule, configured to delete first type information according to first sub-information in the second indication information; and to add second type information according to second sub-information in the second indication information.

[0595] Furthermore, the second indication information also includes: third sub-information indicating whether the node type indicated by the second type information is a newly added type.

[0596] Furthermore, when the third sub-information indicates that the node type indicated by the second type information is a newly added type, the fifth processing module also includes: a first copying sub-module, which is used to copy the production area information to the test area after deleting the first type information and before adding the second type information.

[0597] Wherein, copying the production area information to the test area includes: using a preset method to copy the production area information to the test area; wherein, the preset method includes at least one of the following methods: copying the production area data; copying the access link of the production area data.

[0598] In an embodiment of the present invention, when the third sub-information indicates that the node type indicated by the second type information is not a newly added type, it also includes: a first synchronization module, which is used to synchronize chain block data between nodes of the same node type after the node type is changed according to the second indication information.

[0599] Furthermore, the information processing device also includes: a second update module, used to update the contract version after the node type is changed according to the second indication information.

[0600] Furthermore, the device also includes: a seventh receiving module, used to receive the block synchronization adjustment instruction sent by the PMU; and a first adjustment module, used to adjust the block data synchronization operation according to the block synchronization adjustment instruction.

[0601] Among them, the sixth receiving module includes: a third receiving sub-module, used to receive the first sub-information sent by the PMU; a first feedback sub-module, used to feedback first response information to the PMU based on the first sub-information; and a fourth receiving sub-module, used to receive the second sub-information sent by the PMU based on the first response information.

[0602] Corresponding to the following new node joining process, the device also includes: an eighth receiving module, used to receive the fourth indication information sent by the PMU; a sixth processing module, used to mark the node type of the node as a production type or a test type, and install the contract according to the fourth indication information; and feedback the node joining result information to the PMU; wherein the fourth indication information includes fourth sub-information for indicating that the node type is marked as a production type or a test type and fifth sub-information for indicating the contract to be installed.

[0603] Among them, the eighth receiving module includes: a fifth receiving sub-module, used to receive the fourth sub-information sent by the PMU; a second feedback sub-module, used to feedback second response information to the PMU according to the fourth sub-information; and a sixth receiving sub-module, used to receive the fifth sub-information sent by the PMU according to the second response information.

[0604] Specifically, the sixth processing module includes: a third processing submodule, used to mark the node type of the node as a production type or a test type according to the fourth sub-information; and, according to the fifth sub-information, install the contract.

[0605] Furthermore, the information processing device also includes: a second synchronization module, which is used to mark the node type of the node as a production type or a test type according to the fourth indication information, and after installing the contract, when there are nodes of the same node type, synchronize the chain block data between nodes of the same node type.

[0606] Corresponding to the following node registration process, the device also includes: a ninth receiving module, used to receive a node status query request sent by the PMU; a second feedback module, used to feedback the node status and node resource information of the node to the PMU according to the node status query request.

[0607] Corresponding to the following test process, the device also includes: a tenth receiving module, used to receive the test data sent by the PMU; a first verification module, used to verify the signature data in the test data; and a first execution module, used to execute the test case in the test data if the verification passes.

[0608] Corresponding to the following contract installation and / or upgrade process, the device also includes: an eleventh receiving module, used to receive the contract processing instruction information sent by the PMU; a second verification module, used to verify the signature data in the contract processing instruction information; a seventh processing module, used to install and / or update the contract according to the contract program file in the contract processing instruction information when the verification is passed, and to feedback processing response information to the PMU based on the processing result.

[0609] Among them, the implementation embodiments of the above-mentioned node-side information processing method are all applicable to the embodiments of the information processing device and can achieve the same technical effects.

[0610] The embodiment of the present invention also provides a node management unit, such as Fig.17 As shown, the node management unit includes: a processor 171 and a transceiver 172;

[0611] The processor 171 is configured to send second indication information to the first node through the transceiver 172 according to the first indication information when receiving the first indication information;

[0612] receiving, by the transceiver 172, node change result information fed back by the first node according to the second indication information;

[0613] The first indication information is used to instruct the first node to change the node type;

[0614] The second indication information includes first sub-information for instructing the first node to delete first-type information and second sub-information for instructing the first node to add second-type information;

[0615] The first type information is information indicating that the node type is a production type, and the second type information is information indicating that the node type is a test type; or, the first type information is information indicating that the node type is a test type, and the second type information is information indicating that the node type is a production type.

[0616] The node management unit provided in the embodiment of the present invention sends second indication information to the first node according to the first indication information when receiving the first indication information; receives the node change result information fed back by the first node according to the second indication information; wherein the first indication information is used to instruct the first node to change the node type; the second indication information includes first sub-information for instructing the first node to delete the first type information and second sub-information for instructing the first node to add the second type information; the first type information is information indicating that the node type is a production type, and the second type information is information indicating that the node type is a test type; or, the first type information is information indicating that the node type is a test type, and the second type information is information indicating that the node type is a production type; it can support the conversion of node types, thereby realizing the combination of the test environment and the production environment, and the production environment and the test environment share the same smart contract, application and policy, avoiding the test deviation caused by the inconsistency between the test environment and the production environment, and improving the test accuracy; in addition, it is conducive to the open testing and supervision of blockchain smart contracts, and multiple organizations can join the unified blockchain network for testing, increase the openness and scenario diversity of the test, be more in line with the real scenario, and avoid the incomplete and insufficient testing in the closed environment of the organization; it is a good solution to the problems of poor development and low test accuracy of information processing solutions in the prior art.

[0617] The first indication information carries identification information of the first node; the processor is specifically used to: obtain the registration information of the first node from the node registration table PSR according to the identification information of the first node in the first indication information; and send the second indication information to the first node through the transceiver according to the IP address information in the registration table information.

[0618] Furthermore, the processor is also used to: after receiving the node change result information fed back by the first node according to the second indication information, update the node information of the first node according to the node change result information, and record it in the node registry PSR; wherein the node information includes at least one of node status information, node type information and information of the installed contract.

[0619] Furthermore, the processor is also used to: after receiving the node change result information fed back by the first node according to the second indication information, control the display to display the node change result information.

[0620] In an embodiment of the present invention, the processor is also used to: after a preset time period after confirming the existence of a newly added node type, confirm whether the nodes under the newly added node type meet the block consistency conditions; if not, send a block synchronization adjustment instruction to the nodes under the newly added node type through the transceiver to control the nodes under the newly added node type to meet the block consistency conditions.

[0621] The second indication information further includes: third sub-information indicating whether the node type indicated by the second type information is a newly added type.

[0622] Specifically, the processor is used to: send first sub-information to the first node through the transceiver according to the first indication information; receive first response information fed back by the first node according to the first sub-information through the transceiver; and send second sub-information to the first node through the transceiver according to the first response information.

[0623] Corresponding to the following new node joining process, the processor is also used to: when receiving third indication information, send fourth indication information to the second node through the transceiver according to the third indication information; receive node joining result information fed back by the second node according to the fourth indication information through the transceiver; wherein the third indication information is used to indicate the second node to mark the node type; the fourth indication information includes fourth sub-information for indicating that the second node marks the node type as a production type or a test type and fifth sub-information for indicating the contract to be installed; the second node and the first node are the same node or different nodes.

[0624] Specifically, the second indication information carries the identification information of the second node; wherein the processor is specifically used to: obtain the registry information of the second node from the node registry PSR according to the identification information of the second node in the third indication information, and obtain the information of the contract to be installed from the contract registry; according to the IP address information and the information of the contract to be installed in the registry information, send the fourth indication information to the second node through the transceiver.

[0625] The processor is specifically used to: send fourth sub-information to the second node through the transceiver according to the third indication information; receive second response information fed back by the second node according to the fourth sub-information through the transceiver; and send fifth sub-information to the second node through the transceiver according to the second response information.

[0626] Furthermore, the processor is also used to: after receiving the node joining result information fed back by the second node according to the fourth indication information, update the node information of the second node according to the node joining result information, and record it in the node registration table PSR; wherein the node information includes at least one of node status information, node type information and information of the installed contract.

[0627] Furthermore, the processor is also used to: after receiving the node joining result information fed back by the second node according to the fourth indication information, control the display to display the node joining result information.

[0628] Corresponding to the following node registration process, the processor is also used to: when receiving node information of a third node, send a node status query request to the third node through the transceiver according to the node information of the third node; receive the node status and node resource information fed back by the third node according to the node status query request through the transceiver; when the node status and node resource information indicate that the third node can be used, record the node information of the third node in the node registration table PSR; wherein the third node and the first node are the same node or different nodes.

[0629] Furthermore, the processor is also used to: after recording the node information of the third node into the node registration table PSR, control the display to display the node status of the third node as being available.

[0630] Corresponding to the following contract registration process, the processor is also used to: when receiving a contract identifier, determine the record information of the contract identifier in the contract registration table; receive the contract program and test set corresponding to the contract identifier through the transceiver; and store the contract program and test set in the contract registration table according to the record information.

[0631] Among them, the processor is specifically used to: determine whether it is a registered version of the contract based on the contract identifier; if so, obtain the record information corresponding to the contract identifier from the contract registration table; if not, record the contract corresponding to the contract identifier in the contract registration table to obtain the record information corresponding to the contract identifier.

[0632] Corresponding to the following test process, the processor is also used to: when receiving a test instruction, determine the contract parameter information according to the test instruction; obtain the corresponding test case from the contract registry according to the contract parameter information; obtain the test data according to the test case and the signature data of the node management unit PMU; send the test data to a node whose node type is a test type; wherein the contract parameter information includes at least one of a contract number and a contract name.

[0633] Corresponding to the following contract installation and / or upgrade process, the processor is also used to: upon receiving a processing instruction to install and / or update a contract, send contract processing instruction information to a fourth node through the transceiver according to the processing instruction; receive processing response information fed back by the fourth node according to the contract processing instruction information through the transceiver; wherein the contract processing instruction information is used to instruct the installation and / or update of the contract; the fourth node and the first node are the same node or different nodes.

[0634] The processor is specifically used to: obtain a contract program file from a contract registration table according to the processing instruction; and send contract processing instruction information to a fourth node through the transceiver according to the contract program file.

[0635] Furthermore, the processor is also used to: after receiving the processing response information fed back by the fourth node according to the contract processing indication information, update the node information of the fourth node; wherein the node information includes the information of the installed contract.

[0636] Furthermore, the processor is also used to: after receiving the processing response information fed back by the fourth node according to the contract processing indication information, control the display to display the processing response information.

[0637] Among them, the implementation embodiments of the information processing method on the node management unit side are all applicable to the embodiments of the node management unit and can achieve the same technical effects.

[0638] The embodiment of the present invention also provides a node, such as Fig.18 As shown, the node includes: a processor 181 and a transceiver 182;

[0639] The processor 181 is configured to receive second indication information sent by a node management unit PMU through the transceiver 182;

[0640] Changing the node type according to the second indication information, and obtaining node change result information;

[0641] Feedback the node change result information to the PMU through the transceiver 182;

[0642] The second indication information includes first sub-information for instructing the node to delete the first type of information and second sub-information for instructing the node to add the second type of information;

[0643] The first type information is information indicating that the node type is a production type, and the second type information is information indicating that the node type is a test type; or, the first type information is information indicating that the node type is a test type, and the second type information is information indicating that the node type is a production type.

[0644] The node provided in the embodiment of the present invention receives the second indication information sent by the node management unit PMU; changes the node type according to the second indication information, and obtains the node change result information; feeds back the node change result information to the PMU; wherein the second indication information includes a first sub-information for instructing the node to delete the first type of information and a second sub-information for instructing the node to add the second type of information; the first type of information is information indicating that the node type is a production type, and the second type of information is information indicating that the node type is a test type; or, the first type of information is information indicating that the node type is a test type, and the second type of information is information indicating that the node type is a production type; it can support the conversion of node types, thereby realizing the combination of the test environment and the production environment, and the production environment and the test environment share the same smart contract, application and policy, avoiding the test deviation caused by the inconsistency between the test environment and the production environment, and improving the test accuracy; in addition, it is conducive to the open testing and supervision of blockchain smart contracts, and multiple organizations can join the unified blockchain network for testing, increase the openness and scenario diversity of the test, be more in line with the real scenario, and avoid the incomplete and insufficient testing in the closed environment of the organization; it is a good solution to the problems of poor development of information processing solutions and low test accuracy in the prior art.

[0645] The processor is specifically used to: delete the first type of information according to the first sub-information in the second indication information; and add the second type of information according to the second sub-information in the second indication information.

[0646] Furthermore, the second indication information also includes: third sub-information indicating whether the node type indicated by the second type information is a newly added type.

[0647] Furthermore, the processor is also used to: when the third sub-information indicates that the node type indicated by the second type information is a newly added type, change the node type according to the second indication information, and copy the production area information to the test area after deleting the first type information and before adding the second type information.

[0648] The processor is specifically used to: copy the production area information to the test area in a preset manner; wherein the preset manner includes at least one of the following manners: copying the production area data; copying the access link of the production area data.

[0649] In an embodiment of the present invention, when the third sub-information indicates that the node type indicated by the second type information is not a newly added type, the processor is also used to: after changing the node type according to the second indication information, synchronize chain block data with nodes of the same node type.

[0650] Furthermore, the processor is also used to: update the contract version after changing the node type according to the second indication information.

[0651] Furthermore, the processor is also used to: receive a block synchronization adjustment instruction sent by the PMU through the transceiver; and adjust the block data synchronization operation according to the block synchronization adjustment instruction.

[0652] The processor is specifically used to: receive the first sub-information sent by the PMU through the transceiver; based on the first sub-information, feedback first response information to the PMU through the transceiver; and receive the second sub-information sent by the PMU based on the first response information through the transceiver.

[0653] Corresponding to the following new node joining process, the processor is also used to: receive the fourth indication information sent by the PMU through the transceiver; mark the node type of the node as a production type or a test type, and install the contract according to the fourth indication information; and feedback the node joining result information to the PMU through the transceiver; wherein the fourth indication information includes fourth sub-information for indicating that the node type is marked as a production type or a test type and fifth sub-information for indicating the contract to be installed.

[0654] The processor is specifically used to: receive the fourth sub-information sent by the PMU through the transceiver; based on the fourth sub-information, feedback second response information to the PMU through the transceiver; and receive the fifth sub-information sent by the PMU based on the second response information through the transceiver.

[0655] Specifically, the processor is used to: mark the node type of the node as a production type or a test type according to the fourth sub-information; and install the contract according to the fifth sub-information.

[0656] Furthermore, the processor is also used to: mark the node type of the node as a production type or a test type according to the fourth indication information, and after installing the contract, if there are nodes of the same node type, synchronize the chain block data between nodes of the same node type.

[0657] Corresponding to the following node registration process, the processor is also used to: receive a node status query request sent by the PMU through the transceiver; and according to the node status query request, feedback the node status and node resource information of the node to the PMU through the transceiver.

[0658] Corresponding to the following test process, the processor is also used to: receive the test data sent by the PMU through the transceiver; verify the signature data in the test data; and execute the test case in the test data if the verification passes.

[0659] Corresponding to the following contract installation and / or upgrade process, the processor is also used to: receive the contract processing instruction information sent by the PMU through the transceiver; verify the signature data in the contract processing instruction information; if the verification is passed, install and / or update the contract according to the contract program file in the contract processing instruction information, and feedback processing response information to the PMU through the transceiver based on the processing result.

[0660] Among them, the implementation embodiments of the information processing method on the above-mentioned node side are all applicable to the embodiments of this node and can also achieve the same technical effects.

[0661] An embodiment of the present invention further provides a node management unit, comprising a memory, a processor, and a program stored in the memory and executable on the processor; when the processor executes the program, the information processing method on the node management unit side is implemented.

[0662] Among them, the implementation embodiments of the information processing method on the node management unit side are all applicable to the embodiments of the node management unit and can achieve the same technical effects.

[0663] An embodiment of the present invention further provides a node, comprising a memory, a processor, and a program stored in the memory and executable on the processor; when the processor executes the program, the above-mentioned node-side information processing method is implemented.

[0664] Among them, the implementation embodiments of the information processing method on the above-mentioned node side are all applicable to the embodiments of this node and can also achieve the same technical effects.

[0665] An embodiment of the present invention also provides a readable storage medium on which a program is stored, and when the program is executed by a processor, the steps in the information processing method on the node management unit side are implemented; or, when the program is executed by a processor, the steps in the information processing method on the node side are implemented.

[0666] Among them, the implementation embodiments of the information processing method on the node management unit side or the node side are all applicable to the embodiments of the readable storage medium, and can also achieve the corresponding same technical effects.

[0667] It should be noted that many functional components described in this specification are referred to as modules / sub-modules in order to more particularly emphasize the independence of their implementation methods.

[0668] In the embodiment of the present invention, module / submodule can be implemented with software so that it can be performed by various types of processors. For example, an executable code module of an identification can include one or more physical or logical blocks of computer instructions, for example, it can be constructed as an object, process or function. Nevertheless, the executable code of the identified module does not need to be physically located together, but can include different instructions stored in different positions, and when these instructions are logically combined together, it constitutes a module and realizes the specified purpose of this module.

[0669] In fact, executable code module can be a single instruction or many instructions, and can even be distributed on a plurality of different code segments, distributed among different programs, and distributed across a plurality of memory devices. Similarly, operating data can be identified in the module, and can be implemented and organized in the data structure of any appropriate type according to any appropriate form. The operating data can be collected as a single data set, or can be distributed in different locations (including on different storage devices), and can only be present on a system or network as an electronic signal at least in part.

[0670] When a module can be implemented by software, considering the level of existing hardware technology, a person skilled in the art can build a corresponding hardware circuit to implement the corresponding function of the module that can be implemented by software without considering the cost. The hardware circuit includes a conventional very large scale integration (VLSI) circuit or gate array and existing semiconductors such as logic chips, transistors, or other discrete components. The module can also be implemented by a programmable hardware device, such as a field programmable gate array, a programmable array logic, a programmable logic device, etc.

[0671] The above is a preferred embodiment of the present invention. It should be pointed out that for ordinary personnel in this technical field, several improvements and modifications can be made without departing from the principles of the present invention. These improvements and modifications should also be regarded as the scope of protection of the present invention.

Claims

1. An information processing method, applied to a node management unit PMU in a blockchain, characterized in that: The method comprises: When receiving the first indication information, sending second indication information to the first node according to the first indication information; receiving node change result information fed back by the first node according to the second indication information; The first indication information is used to instruct the first node to change the node type; The second indication information includes first sub-information for instructing the first node to delete first-type information and second sub-information for instructing the first node to add second-type information; The first type information is information indicating that the node type is a production type, and the second type information is information indicating that the node type is a test type; or, the first type information is information indicating that the node type is a test type, and the second type information is information indicating that the node type is a production type.

2. The information processing method according to claim 1, characterized in that: The first indication information carries identification information of the first node; The sending second indication information to the first node according to the first indication information includes: Acquire the registry information of the first node from the node registry PSR according to the identification information of the first node in the first indication information; Send second indication information to the first node according to the IP address information in the registration table information.

3. The information processing method according to claim 1, characterized in that: After receiving the node change result information fed back by the first node according to the second indication information, the method further includes: According to the node change result information, update the node information of the first node and record it in the node registration table PSR; The node information includes at least one of node status information, node type information and information of installed contracts.

4. The information processing method according to claim 1, characterized in that: After receiving the node change result information fed back by the first node according to the second indication information, the method further includes: The node change result information is displayed.

5. The information processing method according to claim 1, characterized in that: The method further comprises: After a preset time after confirming the existence of the newly added node type, confirm whether the nodes under the newly added node type meet the block consistency conditions; If it does not meet the requirements, a block synchronization adjustment instruction is sent to the nodes under the newly added node type to control the nodes under the newly added node type to meet the block consistency conditions.

6. The information processing method according to claim 1, characterized in that: The second indication information also includes: third sub-information indicating whether the node type indicated by the second type information is a newly added type.

7. The information processing method according to claim 1, characterized in that: The sending second indication information to the first node according to the first indication information includes: Sending first sub-information to the first node according to the first indication information; Receiving first response information fed back by the first node according to the first sub-information; Send second sub-information to the first node according to the first response information.

8. The information processing method according to claim 1, characterized in that: The method further comprises: When the third indication information is received, sending fourth indication information to the second node according to the third indication information; receiving node joining result information fed back by the second node according to the fourth indication information; The third indication information is used to indicate that the second node marks a node type; The fourth indication information includes fourth sub-information for indicating that the second node marks the node type as a production type or a test type and fifth sub-information for indicating a contract to be installed; The second node and the first node are the same node or different nodes.

9. The information processing method according to claim 8, characterized in that: The third indication information carries the identification information of the second node; The sending fourth indication information to the second node according to the third indication information includes: Obtaining the registry information of the second node from the node registry PSR according to the identification information of the second node in the third indication information, and obtaining the information of the contract to be installed from the contract registry; Send fourth indication information to the second node according to the IP address information and the information of the contract to be installed in the registration form information.

10. The information processing method according to claim 8, characterized in that: The sending fourth indication information to the second node according to the third indication information includes: Sending fourth sub-information to the second node according to the third indication information; receiving second response information fed back by the second node according to the fourth sub-information; Send fifth sub-information to the second node according to the second response information.

11. The information processing method according to claim 8, characterized in that: After receiving the node joining result information fed back by the second node according to the fourth indication information, the method further includes: According to the node joining result information, update the node information of the second node and record it in the node registration table PSR; The node information includes at least one of node status information, node type information and information of installed contracts.

12. The information processing method according to claim 8, characterized in that: After receiving the node joining result information fed back by the second node according to the fourth indication information, the method further includes: The node joining result information is displayed.

13. The information processing method according to claim 1, characterized in that: The method further comprises: When receiving the node information of the third node, sending a node status query request to the third node according to the node information of the third node; Receiving the node status and node resource information fed back by the third node according to the node status query request; When the node status and the node resource information indicate that the third node is available, recording the node information of the third node into a node registration table PSR; The third node and the first node are the same node or different nodes.

14. The information processing method according to claim 13, characterized in that: After recording the node information of the third node into the node registration table PSR, the method further includes: The node status of the third node is displayed as being available.

15. The information processing method according to claim 1, characterized in that: The method further comprises: Upon receiving the contract identifier, determining the record information of the contract identifier in the contract registration table; Receiving the contract program and test set corresponding to the contract identifier; According to the record information, the contract program and the test set are stored in the contract registration table.

16. The information processing method according to claim 15, characterized in that: The determining of the record information of the contract identifier in the contract registration table includes: Determine whether it is a registered version of the contract according to the contract identifier; If yes, obtain the record information corresponding to the contract identifier from the contract registry; If not, the contract corresponding to the contract identifier is recorded in a contract registration table to obtain record information corresponding to the contract identifier.

17. The information processing method according to claim 1, characterized in that: The method further comprises: Upon receiving a test instruction, determining contract parameter information according to the test instruction; According to the contract parameter information, obtain the corresponding test case from the contract registry; Obtaining test data according to the test case and the signature data of the PMU; Sending the test data to a node whose node type is a test type; The contract parameter information includes at least one of a contract number and a contract name.

18. The information processing method according to claim 1, characterized in that: The method further comprises: Upon receiving a processing instruction for installing and / or updating a contract, sending contract processing instruction information to a fourth node according to the processing instruction; Receiving processing response information fed back by the fourth node according to the contract processing instruction information; The contract processing instruction information is used to instruct the installation and / or update of the contract; The fourth node and the first node are the same node or different nodes.

19. The information processing method according to claim 18, characterized in that: The sending of contract processing instruction information to the fourth node according to the processing instruction includes: According to the processing instruction, obtain the contract program file from the contract registry; According to the contract program file, contract processing instruction information is sent to the fourth node.

20. The information processing method according to claim 18, characterized in that: After receiving the processing response information fed back by the fourth node according to the contract processing instruction information, the method further includes: Updating node information of the fourth node; The node information includes the information of the installed contract.

21. The information processing method according to claim 18, characterized in that: After receiving the processing response information fed back by the fourth node according to the contract processing instruction information, the method further includes: The processing response information is displayed.

22. An information processing method, applied to a node in a blockchain, characterized in that: The method comprises: Receiving second indication information sent by the node management unit PMU; Changing the node type according to the second indication information, and obtaining node change result information; Feedback the node change result information to the PMU; The second indication information includes first sub-information for instructing the node to delete the first type of information and second sub-information for instructing the node to add the second type of information; The first type information is information indicating that the node type is a production type, and the second type information is information indicating that the node type is a test type; or, the first type information is information indicating that the node type is a test type, and the second type information is information indicating that the node type is a production type.

23. The information processing method according to claim 22, characterized in that: The changing the node type according to the second indication information includes: According to the first sub-information in the second indication information, the first type of information is deleted; and according to the second sub-information in the second indication information, the second type of information is added.

24. The information processing method according to claim 23, characterized in that: The second indication information also includes: third sub-information indicating whether the node type indicated by the second type information is a newly added type.

25. The information processing method according to claim 24, characterized in that: In a case where the third sub-information indicates that the node type indicated by the second type information is a newly added type, the changing the node type according to the second indication information further includes: After deleting the first type of information and before adding the second type of information, the production area information is copied to the test area.

26. The information processing method according to claim 25, characterized in that: The step of copying the production area information to the test area includes: Use the preset method to copy the production area information to the test area; The preset method includes at least one of the following methods: Copy the production area data; Replicate the access link for production area data.

27. The information processing method according to claim 24, characterized in that: In a case where the third sub-information indicates that the node type indicated by the second type information is not a newly added type, after changing the node type according to the second indication information, the method further includes: Synchronize chain block data with nodes of the same node type.

28. The information processing method according to claim 22, characterized in that: After the node type is changed according to the second indication information, the method further includes: Update the contract version.

29. The information processing method according to claim 22, characterized in that: The method further comprises: receiving a block synchronization adjustment instruction sent by the PMU; According to the block synchronization adjustment instruction, the block data synchronization operation is adjusted.

30. The information processing method according to claim 22, characterized in that: The receiving node management unit PMU sends the second indication information, including: Receiving first sub-information sent by the PMU; Feedback first response information to the PMU according to the first sub-information; receiving second sub-information sent by the PMU according to the first response information.

31. The information processing method according to claim 22, characterized in that: The method further comprises: Receiving fourth indication information sent by the PMU; According to the fourth indication information, marking the node type of the node as a production type or a test type, and an installation contract; and adding result information to the PMU feedback node; The fourth indication information includes fourth sub-information for indicating that the node type is a production type or a test type and fifth sub-information for indicating a contract to be installed.

32. The information processing method according to claim 31, characterized in that: The receiving fourth indication information sent by the PMU includes: receiving fourth sub-information sent by the PMU; Feedback second response information to the PMU according to the fourth sub-information; receiving fifth sub-information sent by the PMU according to the second response information.

33. The information processing method according to claim 31 or 32, characterized in that: The step of marking the node type of the node as a production type or a test type and installing a contract according to the fourth indication information includes: According to the fourth sub-information, the node type of the node is marked as a production type or a test type; and, according to the fifth sub-information, a contract is installed.

34. The information processing method according to claim 31, characterized in that: After marking the node type of the node as a production type or a test type according to the fourth indication information and installing the contract, the method further includes: When there are nodes of the same node type, chain block data synchronization is performed between nodes of the same node type.

35. The information processing method according to claim 22, characterized in that: The method further comprises: Receiving a node status query request sent by the PMU; According to the node status query request, the node status and node resource information of the node are fed back to the PMU.

36. The information processing method according to claim 22, characterized in that: The method further comprises: Receiving test data sent by the PMU; Verifying the signature data in the test data; If the verification is passed, the test cases in the test data are executed.

37. The information processing method according to claim 22, characterized in that: The method further comprises: Receiving the contract processing instruction information sent by the PMU; Verifying the signature data in the contract processing instruction information; If the verification is passed, the contract is installed and / or updated according to the contract program file in the contract processing instruction information, and processing response information is fed back to the PMU according to the processing result.

38. An information processing device, applied to a node management unit PMU in a blockchain, characterized in that: The device comprises: A first sending module, configured to send second indication information to the first node according to the first indication information when receiving the first indication information; A first receiving module, configured to receive node change result information fed back by the first node according to the second indication information; The first indication information is used to instruct the first node to change the node type; The second indication information includes first sub-information for instructing the first node to delete first-type information and second sub-information for instructing the first node to add second-type information; The first type information is information indicating that the node type is a production type, and the second type information is information indicating that the node type is a test type; or, the first type information is information indicating that the node type is a test type, and the second type information is information indicating that the node type is a production type.

39. The information processing device according to claim 38, characterized in that: The first indication information carries identification information of the first node; Wherein, the first sending module includes: A first acquisition submodule, configured to acquire the registry information of the first node from a node registry PSR according to the identification information of the first node in the first indication information; The first sending submodule is used to send second indication information to the first node according to the IP address information in the registration table information.

40. The information processing device according to claim 38, characterized in that Also includes: A first processing module is configured to, after receiving the node change result information fed back by the first node according to the second indication information, update the node information of the first node according to the node change result information, and record it in a node registration table PSR; The node information includes at least one of node status information, node type information and information of installed contracts.

41. The information processing device according to claim 38, characterized in that Also includes: The first display module is used to display the node change result information after receiving the node change result information fed back by the first node according to the second indication information.

42. The information processing device according to claim 38, characterized in that The device also includes: A first confirmation module, configured to confirm whether the nodes under the newly added node type meet the block consistency condition after a preset time after confirming the existence of the newly added node type; The second processing module is used to send a block synchronization adjustment instruction to the nodes under the newly added node type in case of non-compliance, so as to control the nodes under the newly added node type to comply with the block consistency condition.

43. The information processing device according to claim 38, characterized in that: The second indication information also includes: third sub-information indicating whether the node type indicated by the second type information is a newly added type.

44. The information processing device according to claim 38, characterized in that The first sending module includes: A second sending submodule, configured to send first sub-information to the first node according to the first indication information; A first receiving submodule, configured to receive first response information fed back by the first node according to the first sub-information; The third sending submodule is used to send second sub-information to the first node according to the first response information.

45. The information processing device according to claim 38, characterized in that The device also includes: A second sending module is used to send fourth indication information to the second node according to the third indication information when receiving the third indication information; A second receiving module, used to receive node joining result information fed back by the second node according to the fourth indication information; The third indication information is used to indicate that the second node marks a node type; The fourth indication information includes fourth sub-information for indicating that the second node marks the node type as a production type or a test type and fifth sub-information for indicating a contract to be installed; The second node and the first node are the same node or different nodes.

46. ​​The information processing device according to claim 45, characterized in that The third indication information carries the identification information of the second node; Wherein, the second sending module includes: A first processing submodule, configured to obtain the registry information of the second node from the node registry PSR according to the identification information of the second node in the third indication information, and to obtain the information of the contract to be installed from the contract registry; The fourth sending submodule is used to send fourth indication information to the second node according to the IP address information and the information of the contract to be installed in the registration form information.

47. The information processing device according to claim 45, characterized in that The second sending module includes: a fifth sending submodule, configured to send fourth sub-information to the second node according to the third indication information; A second receiving submodule, configured to receive second response information fed back by the second node according to the fourth sub-information; The sixth sending submodule is used to send fifth sub-information to the second node according to the second response information.

48. The information processing device according to claim 45, characterized in that Also includes: A third processing module is used to update the node information of the second node according to the node joining result information after receiving the node joining result information fed back by the second node according to the fourth indication information, and record it in a node registration table PSR; The node information includes at least one of node status information, node type information and information of installed contracts.

49. The information processing device according to claim 45, characterized in that Also includes: The second display module is used to display the node joining result information after receiving the node joining result information fed back by the second node according to the fourth indication information.

50. The information processing device according to claim 38, characterized in that The device also includes: A third sending module is used to send a node status query request to the third node according to the node information of the third node when receiving the node information of the third node; A third receiving module is used to receive the node status and node resource information fed back by the third node according to the node status query request; A first recording module, configured to record the node information of the third node into a node registration table PSR when the node status and the node resource information indicate that the third node can be used; The third node and the first node are the same node or different nodes.

51. The information processing device according to claim 50, characterized in that Also includes: The third display module is used to display the node status of the third node as available for use after recording the node information of the third node into the node registration table PSR.

52. The information processing device according to claim 38, characterized in that: The device also includes: A first determination module is used to determine the record information of the contract identifier in the contract registration table when receiving the contract identifier; A fourth receiving module, used to receive the contract program and test set corresponding to the contract identifier; The first storage module is used to store the contract program and the test set in the contract registration table according to the record information.

53. The information processing device according to claim 52, characterized in that: The first determining module includes: A first determination submodule, used to determine whether it is a registered version of the contract according to the contract identifier; A second acquisition submodule is used to obtain the record information corresponding to the contract identifier from the contract registration table if yes; The first recording submodule is used to record the contract corresponding to the contract identifier in a contract registration table if no, and obtain the recording information corresponding to the contract identifier.

54. The information processing device according to claim 38, characterized in that: The device also includes: A second determination module is used to determine the contract parameter information according to the test instruction when receiving the test instruction; A first acquisition module, used to acquire corresponding test cases from a contract registry according to the contract parameter information; A fourth processing module, configured to obtain test data according to the test case and the signature data of the PMU; A fourth sending module, used for sending the test data to a node whose node type is a test type; The contract parameter information includes at least one of a contract number and a contract name.

55. The information processing device according to claim 38, characterized in that: The device also includes: a fifth sending module, configured to send contract processing instruction information to the fourth node according to the processing instruction when receiving the processing instruction for installing and / or updating the contract; A fifth receiving module, configured to receive processing response information fed back by the fourth node according to the contract processing instruction information; The contract processing instruction information is used to instruct the installation and / or update of the contract; The fourth node and the first node are the same node or different nodes.

56. The information processing device according to claim 55, characterized in that The fifth sending module includes: A third acquisition submodule is used to acquire a contract program file from a contract registry according to the processing instruction; The seventh sending submodule is used to send contract processing instruction information to the fourth node according to the contract program file.

57. The information processing device according to claim 55, characterized in that: Also includes: A first updating module, configured to update the node information of the fourth node after receiving the processing response information fed back by the fourth node according to the contract processing instruction information; The node information includes the information of the installed contract.

58. The information processing device according to claim 55, characterized in that Also includes: The fourth display module is used to display the processing response information after receiving the processing response information fed back by the fourth node according to the contract processing instruction information.

59. An information processing device, applied to a node in a blockchain, characterized in that: The device comprises: A sixth receiving module, used for receiving second indication information sent by the node management unit PMU; a fifth processing module, configured to change the node type according to the second indication information, and obtain node change result information; A first feedback module, configured to feed back the node change result information to the PMU; The second indication information includes first sub-information for instructing the node to delete the first type of information and second sub-information for instructing the node to add the second type of information; The first type information is information indicating that the node type is a production type, and the second type information is information indicating that the node type is a test type; or, the first type information is information indicating that the node type is a test type, and the second type information is information indicating that the node type is a production type.

60. The information processing device according to claim 59, characterized in that: The fifth processing module comprises: The second processing submodule is used to delete the first type of information according to the first sub-information in the second indication information; and to add the second type of information according to the second sub-information in the second indication information.

61. The information processing device according to claim 60, characterized in that: The second indication information also includes: third sub-information indicating whether the node type indicated by the second type information is a newly added type.

62. The information processing device according to claim 61, characterized in that: In a case where the third sub-information indicates that the node type indicated by the second type information is a newly added type, the fifth processing module further includes: The first copy submodule is used to copy the production area information to the test area after deleting the first type of information and before adding the second type of information.

63. The information processing device according to claim 62, characterized in that: The step of copying the production area information to the test area includes: Use the preset method to copy the production area information to the test area; The preset method includes at least one of the following methods: Copy the production area data; Replicate the access link for production area data.

64. The information processing device according to claim 61, characterized in that In a case where the third sub-information indicates that the node type indicated by the second type information is not a newly added type, the method further includes: The first synchronization module is used to synchronize the chain block data with nodes of the same node type after the node type is changed according to the second indication information.

65. The information processing device according to claim 59, characterized in that: Also includes: The second updating module is used to update the contract version after the node type is changed according to the second indication information.

66. The information processing device according to claim 59, characterized in that The device also includes: A seventh receiving module, configured to receive a block synchronization adjustment instruction sent by the PMU; The first adjustment module is used to adjust the block data synchronization operation according to the block synchronization adjustment instruction.

67. The information processing device according to claim 59, characterized in that: The sixth receiving module comprises: A third receiving submodule, configured to receive the first sub-information sent by the PMU; A first feedback submodule, configured to feed back first response information to the PMU according to the first sub-information; The fourth receiving submodule is configured to receive second sub-information sent by the PMU according to the first response information.

68. The information processing device according to claim 59, characterized in that: The device also includes: an eighth receiving module, configured to receive fourth indication information sent by the PMU; a sixth processing module, configured to mark the node type of the node as a production type or a test type, and an installation contract according to the fourth indication information; and add result information to the PMU feedback node; The fourth indication information includes fourth sub-information for indicating that the node type is a production type or a test type and fifth sub-information for indicating a contract to be installed.

69. The information processing device according to claim 68, characterized in that The eighth receiving module comprises: a fifth receiving submodule, configured to receive fourth sub-information sent by the PMU; A second feedback submodule, configured to feed back second response information to the PMU according to the fourth sub-information; The sixth receiving submodule is configured to receive fifth sub-information sent by the PMU according to the second response information.

70. The information processing device according to claim 68 or 69, characterized in that: The sixth processing module comprises: The third processing submodule is used to mark the node type of the node as a production type or a test type according to the fourth sub-information; and install the contract according to the fifth sub-information.

71. The information processing device according to claim 68, characterized in that Also includes: The second synchronization module is used to mark the node type of the node as a production type or a test type according to the fourth indication information, and after installing the contract, if there are nodes of the same node type, synchronize the chain block data between nodes of the same node type.

72. The information processing device according to claim 59, characterized in that: The device also includes: A ninth receiving module, configured to receive a node status query request sent by the PMU; The second feedback module is used to feed back the node status and node resource information of the node to the PMU according to the node status query request.

73. The information processing device according to claim 59, characterized in that: The device also includes: a tenth receiving module, configured to receive test data sent by the PMU; A first verification module, used for verifying the signature data in the test data; The first execution module is used to execute the test case in the test data if the verification passes.

74. The information processing device according to claim 59, characterized in that The device also includes: an eleventh receiving module, configured to receive the contract processing instruction information sent by the PMU; A second verification module, used to verify the signature data in the contract processing instruction information; The seventh processing module is used to install and / or update the contract according to the contract program file in the contract processing instruction information when the verification is passed, and to feed back processing response information to the PMU according to the processing result.

75. A node management unit in a blockchain, characterized in that: The node management unit includes: a processor and a transceiver; The processor is configured to, upon receiving the first indication information, send second indication information to the first node through the transceiver according to the first indication information; receiving, by the transceiver, node change result information fed back by the first node according to the second indication information; The first indication information is used to instruct the first node to change the node type; The second indication information includes first sub-information for instructing the first node to delete first-type information and second sub-information for instructing the first node to add second-type information; The first type information is information indicating that the node type is a production type, and the second type information is information indicating that the node type is a test type; or, the first type information is information indicating that the node type is a test type, and the second type information is information indicating that the node type is a production type.

76. A node in a blockchain, characterized in that: The node includes: a processor and a transceiver; The processor is configured to receive, through the transceiver, second indication information sent by a node management unit PMU; Changing the node type according to the second indication information, and obtaining node change result information; Feedback the node change result information to the PMU through the transceiver; The second indication information includes first sub-information for instructing the node to delete the first type of information and second sub-information for instructing the node to add the second type of information; The first type information is information indicating that the node type is a production type, and the second type information is information indicating that the node type is a test type; or, the first type information is information indicating that the node type is a test type, and the second type information is information indicating that the node type is a production type.

77. A node management unit in a blockchain, comprising a memory, a processor, and a program stored in the memory and executable on the processor; characterized in that: When the processor executes the program, the information processing method according to any one of claims 1 to 21 is implemented.

78. A node in a blockchain, comprising a memory, a processor, and a program stored in the memory and executable on the processor; characterized in that: When the processor executes the program, the information processing method according to any one of claims 22 to 37 is implemented.

79. A readable storage medium having a program stored thereon, characterized in that: When the program is executed by a processor, the steps of the information processing method according to any one of claims 1 to 21 are implemented; or When the program is executed by a processor, the steps of the information processing method according to any one of claims 22 to 37 are implemented.

Citation Information

Patent Citations

  • Test method, device and system and medium

    CN109815154A

  • System and method for performance testing of scalable distributed network transactional databases

    US20190140935A1