WO2020258941A1 - Method for data ownership confirmation based on blockchain network, and related apparatus - Google Patents

Abstract

A method, apparatus and system for data ownership confirmation based on a blockchain network. The method comprises: a first blockchain node in a blockchain network sending or receiving communication information; and recording the communication information in a ledger, wherein the blockchain network comprises a usage node and a providing node, the usage node is used for requesting user credit data according to a service request, and the providing node is used for providing the user credit data; and the communication information comprises information between the first blockchain node and another blockchain node or a user client.

Description

Data confirmation method and related device based on blockchain network

This application claims the priority of the Chinese patent application filed with the Chinese Patent Office on June 28, 2019, the application number is 201910575178.1, and the application name is "Blockchain network-based data verification method and related devices". The reference is incorporated in this application.

Technical field

This application relates to the technology in the blockchain field, and in particular to a method and related devices for data verification based on a blockchain network.

Background technique

With the development of information technology, people's daily life is more and more closely integrated with the digital world. When a user needs to apply for business services from some business service providers in daily life, the business service provider needs to check the user's personal information to determine whether to provide the user with the business service requested by the user. For example, a bank can provide users with various types of financial services. After accepting a user’s business request, the bank needs to obtain credible user data from a third-party data provider in order to confirm whether to provide the user with the corresponding service. Third-party data providers can pre-record user data of a large number of users.

In this type of business processing scenario, the organization that uses the data can be called the data user, and the third-party data provider that provides the data can be called the data provider. Before receiving the business request, the data user can The provider signs a data transaction contract, agreeing on the data that the data user is allowed to obtain and use, so that the data user can obtain the required user data from the data user at any time after receiving the user’s business request, and apply for the user’s request The business is processed.

However, with this processing method, since the process information of the user data transaction between the data user and the data provider is only recorded on the server of the data user and the data provider, when the user suspects the leakage of his user data, only Through the process information recorded by the data user and the data provider, it is impossible to determine who leaked the data.

In order to improve the security of user data, there is an urgent need for a traceable data usage method.

Summary of the invention

This application provides a method and related device for data right confirmation based on a blockchain network, which can provide a traceable data usage method to improve the security of user data.

In the first aspect, this application provides a method for data confirmation based on a blockchain network, the method including:

The first blockchain node in the blockchain network sends or receives communication information;

The first blockchain node records the communication information in the ledger of the blockchain network;

Wherein, the blockchain network includes a plurality of blockchain nodes, and the plurality of blockchain nodes includes: using nodes and providing nodes; the using nodes are used to send information to all users according to a service request carrying a user identifier. The providing node requests user credit data corresponding to the user identification; the providing node is configured to provide user credit data to the user node; the communication information includes: the first blockchain node and the plurality of At least one of the information between any other blockchain nodes in the blockchain node, and the information between the first blockchain node and the user client; wherein, the user client is used to The using node sends the service request carrying the user identifier, and/or the user client is used to confirm whether the providing node is allowed to provide the user credit data corresponding to the user identifier to the using node; The first blockchain node is a blockchain node among the plurality of blockchain nodes.

In this application, when using the blockchain network to deploy the use nodes and providing nodes in the data usage scenario, and use the ledger in the blockchain network to record between the blockchain nodes and between the blockchain nodes and the user client The communication information can realize a traceable data usage method.

Exemplarily, the first block chain node does not specifically refer to the block chain node with a specific number among the block chain nodes. In the embodiment of the present application, the first block chain node may be a block chain network. Any one or more of the use nodes, provide nodes, and proxy nodes in each blockchain node. The technical solution provided by the embodiments of the present application can record the communication information between the user node, the providing node, and the agent node, and the communication information between the user node and the user terminal and the user client on the user terminal in the blockchain ledger. To achieve the traceability requirements of data usage.

In a possible implementation manner, the blockchain network further includes: a consensus node; the first blockchain node is a blockchain other than the consensus node among the plurality of blockchain nodes node;

The first blockchain node to record the communication information in the ledger of the blockchain network includes:

The first blockchain node sends the communication information to the consensus node, so that the consensus node sends the communication information to the accounting node in the blockchain network in the form of a block. The account node is used to record the block containing the communication information in the ledger of the blockchain network. For example, the accounting node is a blockchain node other than the consensus node in the blockchain network. Illustratively, the accounting node may be a blockchain node such as a user node, a provider node, etc.

In a possible implementation manner, sending or receiving communication information by the first blockchain node in the blockchain network includes:

The first blockchain node sends the communication information to the second blockchain node; or,

The first blockchain node receives the communication information sent by the second blockchain node; or,

The first blockchain node sends the communication information to the user client; or,

The first blockchain node receives the communication information sent by the user client;

Wherein, the second block chain node is any other block chain node except the first block chain node among the plurality of block chain nodes.

In a possible implementation manner, the first blockchain node is the user node; the user client is configured to send the service request carrying the user identifier to the user node;

The sending or receiving of communication information by the first blockchain node in the blockchain network includes: the user node sending or receiving communication information, wherein the communication information specifically includes: the user node and the plurality of At least one of the information between other blockchain nodes in the blockchain node, and the information between the use node and the user client. Exemplarily, a user node may send communication information to a consensus node after sending or receiving communication information, and the consensus node is any blockchain node other than the user node among the plurality of blockchain nodes .

In a possible implementation manner, the first blockchain node is the providing node; the user client is used to confirm whether the providing node is allowed to provide the user corresponding to the user ID to the user node Credit data;

Sending or receiving communication information by the first blockchain node in the blockchain network includes: the providing node sending or receiving communication information, wherein the communication information specifically includes: the providing node and the plurality of Information between other blockchain nodes in the blockchain node, and at least one of the information between the providing node and the user client; the consensus node is the multiple blockchain nodes Any blockchain node other than the provision node.

In a possible implementation, the first blockchain node is the user node; the first blockchain node in the blockchain network sends or receives communication information, including at least one of the following:

The use node receives the service request sent by the user client;

The use node sends a data transaction request to the providing node, the data transaction request is used to request to obtain user credit data corresponding to the user identification, and the user credit data is used by the use node to process the user Identified business request;

The using node receives a data transaction response sent by the providing node, where the data transaction response includes user credit data corresponding to the user identifier.

Correspondingly, the aforementioned communication information may specifically include at least one of the following:

The service request that is received by the user node and sent by the user client and carries the user identifier;

The data transaction request sent by the using node to the providing node, where the data transaction request is used to request to obtain user credit data corresponding to the user identification, and the user credit data is used by the using node to process the data carrying the Service request of user ID;

The data transaction response received by the using node from the providing node, where the data transaction response includes user credit data corresponding to the user identification.

In a possible implementation, the first blockchain node is the providing node; the first blockchain node in the blockchain network sends or receives communication information, including at least one of the following:

The providing node receives a data transaction request sent by the using node, the data transaction request is used to request to obtain user credit data corresponding to the user identification, and the user credit data is used by the using node to process the data carrying the Service request of user ID;

The providing node sends a data authorization request to the user client, where the data authorization request is used to request permission to provide the user credit data corresponding to the user identifier to the user node;

The providing node receives a data authorization response sent by the user client, where the data authorization response is used to confirm whether the user credit data corresponding to the user identifier is allowed to be provided to the user node;

The providing node sends a data transaction response to the using node, where the data transaction response includes user credit data corresponding to the user identifier.

Correspondingly, the communication information specifically includes at least one of the following:

The data transaction request received by the providing node from the user node, where the data transaction request is used to request to obtain user credit data corresponding to the user identification, and the user credit data is used by the user node to process and carry information The service request of the user ID;

A data authorization request sent by the providing node to the user client, where the data authorization request is used to confirm whether the user credit data corresponding to the user identifier is allowed to be provided to the user node;

A data authorization response received by the providing node from the user client, where the data authorization response includes user credit data corresponding to the user identifier;

The data transaction response sent by the providing node to the using node, where the data transaction response includes user credit data corresponding to the user identifier.

In a possible implementation, the multiple blockchain nodes include: a proxy node; the proxy node is used to receive a data transaction request sent by the user node, and the data transaction request is used to request the User credit data corresponding to the user identification; and, confirming whether the use node has the access authority to the user credit data corresponding to the user identification; and, when confirming that the use node has the access authority, send all the information to the providing node The data transaction request; and receiving a data transaction response sent by the providing node, the data transaction response including user credit data corresponding to the user identification;

The first blockchain node is the proxy node; sending or receiving communication information by the first blockchain node in the blockchain network includes: sending or receiving communication information by the proxy node, wherein The communication information specifically includes: information between the proxy node and the user node, at least one of information between the proxy node and the providing node; the consensus node is the multiple blockchain nodes Any blockchain node other than the proxy node.

In a possible implementation manner, the blockchain network includes: X channels; the blockchain nodes in the blockchain network respectively correspond to one or more of the X channels; wherein, the The channel corresponding to the first blockchain node includes the i-th channel, and the channel corresponding to the second blockchain node in the blockchain network includes the i-th channel;

The first blockchain node recording the communication information in the ledger of the blockchain network includes: the first blockchain node records the channel information of the i-th channel in the ledger corresponding to the i-th channel in;

The channel information of the i-th channel includes: information transmitted between the first block chain node and the second block chain node through the i-th channel, and the first block chain node or the The second blockchain node sends information to the user client based on the information received from the i-th channel, and the first blockchain node passes through the i-th channel based on the information received from the user client Information sent to the second blockchain node, and at least one of the information sent by the second blockchain node to the first blockchain node through the i-th channel based on the information received from the user client Species; where X is an integer greater than 0, and i is an integer greater than 0 and less than or equal to X.

Exemplarily, the first blockchain node can send the channel information of the i-th channel to the consensus node in the blockchain network through the i-th channel, so that the consensus node can package the communication information of the i-th channel to generate a zone Block and send the block to the accounting node whose channel is the i-th channel. The accounting node of the i-th channel can be used to record the channel information of the i-th channel in the ledger of the i-th channel.

In a possible implementation manner, the blockchain network includes M use nodes, the M use nodes respectively correspond to one of the X channels, and any use node transmits information through its corresponding channel and the providing node; The consensus node corresponds to one or more channels;

The first blockchain node is the corresponding channel among the M usage nodes as the jth usage node of the i-th channel, and the second blockchain node is the one that transmits information through the i-th channel and the jth usage node. Providing node; or, the first blockchain node is a providing node that transmits information through the i-th channel with the j-th user node corresponding to the i-th channel, and the second blockchain node is the j-th Use node

Wherein, M is an integer greater than 0, and j is an integer greater than 0 and less than or equal to M.

In a possible implementation manner, the blockchain network includes M use nodes, the M use nodes respectively correspond to one of the X channels, and any use node transmits information through its corresponding channel and the providing node;

The multiple blockchain nodes include: a proxy node; the proxy node is configured to receive a data transaction request sent by the user node, the data transaction request is used to request user credit data corresponding to the user identifier; and , Confirm whether the using node has the access authority to the user credit data corresponding to the user identification; and, when confirming that the using node has the access authority, send the data transaction request to the providing node; and, receive The data transaction response sent by the providing node, where the data transaction response includes user credit data corresponding to the user identifier;

The first blockchain node is the corresponding channel among the M usage nodes as the jth usage node of the i-th channel, and the second blockchain node is the one that transmits information with the jth usage node through the i-th channel Proxy node; or, the first blockchain node is a proxy node that transmits information through the i-th channel with the j-th user node corresponding to the i-th channel, and the second blockchain node is the j-th Use node; or, the first blockchain node is a proxy node that transmits information through the i-th channel with the j-th use node corresponding to the i-th channel, and the second blockchain node is the The first blockchain node transmits the information providing node through the i-th channel;

Wherein, M is an integer greater than 0, and j is an integer greater than 0 and less than or equal to M.

Exemplarily, the consensus node in the blockchain network may correspond to one or more channels.

In a possible implementation manner, the providing node is an operator server; the user credit data is operator credit data corresponding to the user identification.

In the second aspect, this application provides a method for data confirmation based on a blockchain network, the method including:

The consensus node receives the communication information, and records the communication information in the ledger of the blockchain network;

Wherein, the blockchain network includes a plurality of blockchain nodes, and the plurality of blockchain nodes includes: using nodes and providing nodes; the using nodes are used to send information to all users according to a service request carrying a user identifier. The providing node requests user credit data corresponding to the user identifier; the providing node is configured to provide user credit data to the user node; the consensus node is a blockchain node among the plurality of blockchain nodes The communication information includes: information between the blockchain nodes, and at least one of the information between the blockchain nodes and the user client; wherein, the user client is used to send to the user node The service request carrying the user identifier, and/or the user client is used to confirm whether the providing node is allowed to provide the user credit data corresponding to the user identifier to the using node.

Exemplarily, the consensus node may receive communication information from the first blockchain node in the method described in the first aspect. The first blockchain node may be a user node, a provider node, or a proxy node among multiple blockchain nodes in the blockchain network.

In a possible implementation manner, the communication information includes the sender of the communication information;

The recording the communication information in the ledger of the blockchain network includes:

The consensus node verifies the sender of the communication information;

When the verification is successful, the consensus node may encapsulate the communication information into a block and send it to the accounting node, so that the accounting node records the communication information in the account book locally stored by the accounting node;

Among them, the accounting node in the blockchain network is a blockchain node that locally stores a ledger or a copy of the ledger in the blockchain network. Exemplarily, the accounting node may be the first blockchain node in the first aspect.

In a possible implementation manner, the communication information includes: information between the use node and other blockchain nodes among the plurality of blockchain nodes, and the use node and the user At least one of the information between the clients; the user client is used to send the service request carrying the user identifier to the using node;

The consensus node is any blockchain node among the multiple blockchain nodes except the use node;

The receiving of the communication information by the consensus node includes: the consensus node receiving the communication information sent by the using node.

In a possible implementation manner, the communication information includes: information between the providing node and other blockchain nodes among the plurality of blockchain nodes, and the providing node and the user At least one of the information between the clients; the user client is used to confirm whether the providing node is allowed to provide the user credit data corresponding to the user identifier to the using node;

The consensus node is any one of the multiple blockchain nodes except the providing node;

The receiving of the communication information by the consensus node includes: the consensus node receiving the communication information sent by the providing node.

In a possible implementation, the blockchain network further includes: a proxy node; the proxy node is used to receive a data transaction request sent by the user node, and the data transaction request is used to request the user Identifying the corresponding user credit data; and, confirming whether the using node has the access authority to the user credit data corresponding to the user identifier; and, when confirming that the using node has the access authority, sending the providing node A data transaction request; and receiving a data transaction response sent by the providing node, the data transaction response including user credit data corresponding to the user identifier;

The receiving of the communication information by the consensus node includes: the consensus node receiving the communication information sent by the proxy node; wherein the communication information specifically includes: information between the proxy node and the user node, and At least one of the information between the agent node and the providing node.

In a possible implementation manner, the blockchain network includes: X channels; the blockchain nodes in the blockchain network respectively correspond to one or more of the X channels; wherein, the The number of use nodes is M, and the M use nodes respectively correspond to one of the X channels, and any use node transmits information through its corresponding channel and the providing node; the consensus node corresponds to one or more channels;

The receiving of the communication information by the consensus node includes: the consensus node receives the channel information of the i-th channel corresponding to the consensus node, packs the received channel information of the i-th channel into a block, and sends it to the channel to which it belongs. The accounting node of the i-th channel, so that the accounting node records the communication information of the i-th channel in the ledger corresponding to the i-th channel;

The channel information of the i-th channel includes at least one of the following:

The corresponding channel is the information between the use node of the i-th channel and the first user client, and the first user client is configured to send the service request carrying the user identifier to the use node;

The corresponding channel is the information between the using node and the providing node of the i-th channel,

The providing node sends the information to the second user client based on the information received from the i-th channel and the information received from the user terminal; the second user client is used to confirm whether the providing node is allowed to provide all the information to the using node User credit data corresponding to the user identifier;

Wherein, X is an integer greater than 0, M is an integer greater than 0, and i is an integer greater than 0 and less than or equal to X.

In the third aspect, this application provides a method for data right confirmation based on a blockchain network, the method including:

The user client receives a data authorization request sent by a providing node that carries a user ID corresponding to the user client, and the data authorization request is used to request permission to use the node to use the user credit corresponding to the user ID provided by the providing node data;

The user client outputs prompt information through an output device, where the prompt information is used to request confirmation whether the user node is allowed to use the user credit data corresponding to the user identifier provided by the providing node;

Wherein, the use node and the provision node are blockchain nodes in a blockchain network, and the use node is used to request the user credit data corresponding to the user identifier from the provision node.

In this application, when using the blockchain network to deploy the use nodes and providing nodes in the data usage scenario, and use the providing nodes in the blockchain network to request the user client to confirm whether the use nodes are allowed to use the users provided by the providing nodes By identifying the corresponding user credit data, the user can know the usage of the data in time. Therefore, this application can implement a traceable data usage method.

In this application, a user client (such as a second user client) may be deployed on the user terminal, and the user client may be used to communicate with one or more providing nodes, for example, to receive data sent by one or more providing nodes Authorization request, and sending data authorization response to one or more providing nodes. The user client can integrate data authorization requests from multiple providing nodes and output prompt information through an output device. The user client can correspond to a user identification, so that the user can centrally confirm the data authorization request for one or more user credit data from one or more provision nodes. In some cases, the user client can also be used to communicate with one or more user nodes (that is, the user client can have the functions of the first user client at the same time, and the first user client and the second user client correspond to the same The user identifier of the user ID), for example, sending a service request to one or more using nodes, and receiving a service processing result sent by one or more using nodes.

In a possible implementation, the user client receiving the data authorization request sent by the providing node may include: the user client receiving the data authorization request sent by the providing node, where the data authorization request includes the data source list and the corresponding user ID An identification list of user credit data, where the data source list includes identifications of one or more provision nodes. In an embodiment, the data authorization request sent by the providing node may be a second data authorization request, and the providing node may send the second data authorization request after receiving the first data authorization request sent by the proxy node. It should be noted that, When using a node to send a data transaction request to an agent node, it may include a data source list and a list of user credit data identifiers. The agent node may send a first data authorization request to multiple providing nodes in the data source list, and any one of the first The data authorization request may include a list of data sources and an identification list of user credit data.

In a possible implementation, the user client receiving the data authorization request sent by the providing node and carrying the user identification corresponding to the user client includes: the user client receiving the data authorization request sent by at least two providing nodes At least two data authorization requests, the at least two data authorization requests respectively correspond to the at least two providing nodes one-to-one, and any data authorization request is used to request the user client to allow the user node to use the sending data authorization User credit data corresponding to the user ID provided by the requested providing node;

Wherein, the use node is used to request the user credit data corresponding to the user identification from the at least two providing nodes, and the user credit data corresponding to the user identification includes: the user credit data provided by the at least two providing nodes respectively User credit data corresponding to the user identifier;

The prompt information is used to request confirmation whether the user node is allowed to use the user credit data corresponding to the user identifier provided by the at least two providing nodes respectively.

In a possible implementation manner, the method further includes:

The user client outputs prompt information through its own output device, where the prompt information is used to request confirmation whether the user node is allowed to use the user credit data corresponding to the user identifier provided by the at least two providing nodes;

The user client receives input information through an input device, where the input information is used to confirm whether the user node is allowed to use the user credit data corresponding to the user identifier provided by the at least two providing nodes;

When the input information indicates that the user credit data corresponding to the user identification provided by the at least two providing nodes is allowed to be used by the user node, the user terminal sends a data authorization response to the providing node, either The data authorization response is used to confirm that the user node is allowed to use the user credit data corresponding to the user identification provided by the providing node that receives the data authorization response.

In a possible implementation, the data authorization request is used to request permission for the user node to use the user credit data corresponding to the user identifier provided by the providing node when receiving the service request of the first service. .

In a fourth aspect, the present application provides a data right confirmation system based on a blockchain network, the system includes: a plurality of blockchain nodes; the plurality of blockchain nodes includes: use nodes and provide nodes; wherein, The using node is configured to request the user credit data corresponding to the user identifier from the providing node according to a service request carrying a user identifier; the providing node is configured to provide user credit data;

At least one of the multiple blockchain nodes is also used to send or receive communication information, and record the communication information in the ledger of the blockchain network; wherein the communication information includes: At least one of the information between the blockchain nodes and the information between the blockchain node and the user client; wherein the user client is used to send to the user node information that carries the user identifier The service request, and/or, the user client is used to confirm whether the providing node is allowed to provide the user credit data corresponding to the user identifier to the using node.

In the embodiment of the present application, the above-mentioned at least one blockchain node can send communication information to a consensus node in the blockchain network, and the consensus node packages the communication information to generate a block and send it to the accounting node for accounting Nodes can store blocks containing communication information in the ledger of the blockchain network. Exemplarily, the consensus node may be a blockchain node other than the use node or the providing node or the proxy node.

In a possible implementation manner, the at least one blockchain node is a user node; the communication information specifically includes: between the user node and other blockchain nodes among the plurality of blockchain nodes And at least one of the information between the use node and the user client; the user client is configured to send the service request carrying the user identifier to the use node.

Exemplarily, the use node may also be used to send the communication information to the consensus node after sending or receiving the communication information; the consensus node may be the number of blockchain nodes in addition to the Use any blockchain node other than the node.

In a possible implementation manner, the communication information specifically includes at least one of the following:

The service request that carries the user identifier and is sent by the user client received by the user node;

The data transaction request sent by the using node to the providing node, where the data transaction request is used to request to obtain user credit data corresponding to the user identification, and the user credit data is used by the using node to process the data carrying the Service request of user ID;

The data transaction response received by the using node from the providing node, where the data transaction response includes user credit data corresponding to the user identification.

In a possible implementation manner, the at least one blockchain node is a providing node;

The communication information specifically includes: information between the providing node and other blockchain nodes among the plurality of blockchain nodes, and at least among the information between the providing node and the user client One; the user client is used to confirm whether the providing node is allowed to provide the user credit data corresponding to the user identifier to the using node.

Exemplarily, the providing node is further configured to send the communication information to a consensus node after sending or receiving the communication information; the consensus node is the at least two blockchain nodes in addition to the providing Any blockchain node other than the node.

In a possible implementation manner, the communication information specifically includes at least one of the following:

The data transaction request received by the providing node from the user node, the data transaction request is used to request to obtain user credit data corresponding to the user identification, and the user credit data corresponding to the user identification is used for the user node Processing the service request carrying the user identifier;

A data authorization request sent by the providing node to the user client, where the data authorization request is used to request that the user node be allowed to use the user credit data corresponding to the user identifier provided by the providing node;

A data authorization response received by the providing node from the user client, where the data authorization response includes user credit data corresponding to the user identifier;

The data transaction response sent by the providing node to the using node, where the data transaction response includes user credit data corresponding to the user identifier.

In a possible implementation manner, the multiple blockchain nodes further include: proxy nodes;

The proxy node is configured to receive a data transaction request sent by the using node, the data transaction request is used to request user credit data corresponding to the user identification; and to confirm whether the using node has the user identification corresponding And, when confirming that the user node has the access right, send the data transaction request to the providing node; and receive the data transaction response sent by the providing node, the data transaction The response includes user credit data corresponding to the user identification;

The communication information specifically includes: at least one of information between the proxy node and the use node, and information between the proxy node and the providing node.

In a possible implementation manner, the blockchain network includes: X channels; the multiple blockchain nodes respectively correspond to one or more of the X channels; wherein,

The number of the use nodes is M, the M use nodes respectively correspond to one of the X channels, and any use node transmits information to the providing node through its corresponding channel;

The channel information of the i-th channel includes at least one of the following:

The corresponding channel is the information between the use node of the i-th channel and the first user client, and the first user client is configured to send the service request carrying the user identifier to the use node;

The corresponding channel is the information between the using node and the providing node of the i-th channel;

The providing node sends the information to the second user client based on the information received from the i-th channel and the information received from the second user client; the second user client is used to confirm whether the providing node is allowed to use The node provides user credit data corresponding to the user identifier;

Wherein, X is an integer greater than 0, M is an integer greater than 0, and i is an integer greater than 0 and less than or equal to X.

Exemplarily, the number of consensus nodes in the blockchain network is Y, any consensus node corresponds to one or more channels, and the jth consensus node among the Y consensus nodes is specifically used to receive the jth consensus The channel information of the i-th channel corresponding to the node, and the received channel information of the i-th channel is recorded in the ledger corresponding to the i-th channel; Y is an integer greater than 0, and j is an integer greater than 0 and less than or equal to Y.

In this application, any blockchain node in the blockchain network can send information to other blockchain nodes with the same corresponding channel by broadcasting in the corresponding channel.

In a possible implementation manner, the providing node is further configured to send a data authorization request to the user client, and the data authorization request is used to request permission for the user node to use the data provided by the providing node. User credit data corresponding to the user ID.

In a possible implementation manner, the providing node is an operator server; the user credit data is operator credit data corresponding to the user identification.

In a fifth aspect, this application also provides a data right confirmation device based on a blockchain network, which is applied to the first blockchain node in the blockchain network, and the device includes:

The transceiver module is used to send or receive communication information;

Processing module, used to record the communication information in the ledger of the blockchain network;

Wherein, the blockchain network includes a plurality of blockchain nodes, and the plurality of blockchain nodes includes: using nodes and providing nodes; the using nodes are used to send information to all users according to a service request carrying a user identifier. The providing node requests user credit data corresponding to the user identification; the providing node is configured to provide user credit data to the user node; the communication information includes: the first blockchain node and the plurality of At least one of the information between any other blockchain nodes in the blockchain node, and the information between the first blockchain node and the user client; wherein, the user client is used to The using node sends the service request carrying the user identifier, and/or the user client is used to confirm whether the providing node is allowed to provide the user credit data corresponding to the user identifier to the using node; The first blockchain node is a blockchain node among the plurality of blockchain nodes.

Exemplarily, the transceiver module is further configured to send the communication information to the consensus node, so that the consensus node records the communication information in the ledger of the blockchain network; the consensus node is the multiple A block chain node other than the first block chain node among the block chain nodes;

In a possible implementation manner, the transceiver module is specifically used for:

Send the communication information to the second blockchain node; or,

Receiving the communication information sent by the second blockchain node; or,

Sending the communication information to the user client; or,

Receiving the communication information sent by the user client;

Wherein, the second block chain node is any other block chain node except the first block chain node among the plurality of block chain nodes.

In a possible implementation manner, the first blockchain node is the user node; the user client is configured to send the service request carrying the user identifier to the user node;

The transceiver module is specifically configured to send or receive communication information, where the communication information specifically includes: information between the use node and other blockchain nodes among the plurality of blockchain nodes, and, At least one of the information between the usage node and the user client; the consensus node is any blockchain node among the plurality of blockchain nodes except the usage node.

In a possible implementation manner, the first blockchain node is the providing node; the user client is used to confirm whether the providing node is allowed to provide the user corresponding to the user ID to the user node Credit data;

The transceiver module is specifically configured to send or receive communication information, where the communication information specifically includes: information between the providing node and other blockchain nodes among the plurality of blockchain nodes, and, At least one of the information between the providing node and the user client; the consensus node is any one of the plurality of blockchain nodes except the providing node.

In a possible implementation manner, the first blockchain node is the user node; the user client is used to send the service request carrying the user identifier to the user node; The transceiver module is specifically used for at least one of the following:

Receiving the service request carrying the user identifier sent by the user client;

Send a data transaction request to the providing node, the data transaction request is used to request to obtain the user credit data corresponding to the user ID, and the user credit data is used by the user node to process the service request carrying the user ID ；

Receive a data transaction response sent by the providing node, where the data transaction response includes user credit data corresponding to the user identification.

In a possible implementation manner, the first blockchain node is the providing node; the user client is used to confirm whether the providing node is allowed to provide the user corresponding to the user ID to the user node Credit data; the transceiver module is specifically used for at least one of the following:

Receive a data transaction request sent by the use node, the data transaction request is used to request to obtain user credit data corresponding to the user identification, and the user credit data is used by the use node to process the service carrying the user identification request;

Sending a data authorization request to the user client, where the data authorization request is used to request the user client to allow the user client to provide the user credit data corresponding to the user identifier;

Receiving a data authorization response sent by the user client, where the data authorization response is used to confirm whether to allow the user credit data corresponding to the user identification to be provided to the user node;

Send a data transaction response to the use node, where the data transaction response includes user credit data corresponding to the user identification.

In a possible implementation, the multiple blockchain nodes include: a proxy node; the proxy node is used to receive a data transaction request sent by the user node, and the data transaction request is used to request the User credit data corresponding to the user identification; and, confirming whether the use node has the access authority to the user credit data corresponding to the user identification; and, when confirming that the use node has the access authority, send all the information to the providing node The data transaction request; and receiving a data transaction response sent by the providing node, the data transaction response including user credit data corresponding to the user identification;

The first blockchain node is the proxy node; the transceiver module is specifically used to send or receive communication information, where the communication information specifically includes: information between the proxy node and the user node , At least one of the information between the agent node and the providing node.

Exemplarily, the transceiver module may send communication information to a consensus node after sending or receiving communication information, and the consensus node is any one of the plurality of blockchain nodes except the proxy node node.

In a possible implementation manner, the blockchain network includes: X channels; the blockchain nodes in the blockchain network respectively correspond to one or more of the X channels; wherein, the The channel corresponding to the first blockchain node includes the i-th channel, and the channel corresponding to the second blockchain node in the blockchain network includes the i-th channel;

The transceiver module is specifically configured to record the channel information of the i-th channel in the ledger corresponding to the i-th channel;

The channel information of the i-th channel includes: information transmitted between the first block chain node and the second block chain node through the i-th channel, and the first block chain node or the The second blockchain node sends information to the user client based on the information received from the i-th channel, and the first blockchain node passes through the i-th channel based on the information received from the user client Information sent to the second blockchain node, and at least one of the information sent by the second blockchain node to the first blockchain node through the i-th channel based on the information received from the user client Species

Wherein, X is an integer greater than 0, and i is an integer greater than 0 and less than or equal to X.

Exemplarily, the transceiver module may send the channel information of the i-th channel to the consensus node through the i-th channel, so that the consensus node packs the communication information of the i-th channel, generates a block, and sends the block to The accounting node corresponding to the i-th channel, the accounting node of the i-th channel records the communication information of the i-th channel in the ledger corresponding to the i-th channel.

In a possible implementation manner, the blockchain network includes M use nodes, the M use nodes respectively correspond to one of the X channels, and any use node transmits information through its corresponding channel and the providing node; The consensus node corresponds to one or more channels;

The first blockchain node is the corresponding channel among the M usage nodes as the jth usage node of the i-th channel, and the second blockchain node is the one that transmits information through the i-th channel and the jth usage node. Providing node; or, the first blockchain node is a providing node that transmits information through the i-th channel with the j-th user node corresponding to the i-th channel, and the second blockchain node is the j-th Use node

Wherein, M is an integer greater than 0, and j is an integer greater than 0 and less than or equal to M.

In a possible implementation manner, the blockchain network includes M use nodes, the M use nodes respectively correspond to one of the X channels, and any use node transmits information through its corresponding channel and the providing node;

The multiple blockchain nodes include: a proxy node; the proxy node is configured to receive a data transaction request sent by the user node, the data transaction request is used to request user credit data corresponding to the user identifier; and , Confirm whether the using node has the access authority to the user credit data corresponding to the user identification; and, when confirming that the using node has the access authority, send the data transaction request to the providing node; and, receive The data transaction response sent by the providing node, where the data transaction response includes user credit data corresponding to the user identifier;

The first blockchain node is the corresponding channel among the M usage nodes as the jth usage node of the i-th channel, and the second blockchain node is the one that transmits information with the jth usage node through the i-th channel Proxy node; or, the first blockchain node is a proxy node that transmits information through the i-th channel with the j-th user node corresponding to the i-th channel, and the second blockchain node is the j-th Use node; or, the first blockchain node is a proxy node that transmits information through the i-th channel with the j-th use node corresponding to the i-th channel, and the second blockchain node is the The first blockchain node transmits the information providing node through the i-th channel; where M is an integer greater than 0, and j is an integer greater than 0 and less than or equal to M.

Exemplarily, the consensus node in the blockchain network corresponds to one or more channels.

In a possible implementation manner, the providing node is an operator server; the user credit data is operator credit data corresponding to the user identification.

In a sixth aspect, this application also provides a data right confirmation device based on a blockchain network, which is applied to a user client, and the device includes:

The transceiver module is configured to receive a data authorization request carrying a user identification corresponding to the user client sent by a providing node, and the data authorization request is used to request permission to use the node to use the user identification provided by the providing node. User credit data;

An output module, configured to output prompt information through an output device, the prompt information being used to request confirmation whether the user node is allowed to use the user credit data corresponding to the user identifier provided by the providing node;

Wherein, the use node and the provision node are blockchain nodes in a blockchain network, and the use node is used to request the user credit data corresponding to the user identifier from the provision node.

In a possible implementation, the transceiver module is specifically configured to receive at least two data authorization requests sent by at least two providing nodes, and the at least two data authorization requests are the same as those of the at least two providing nodes. One correspondence, any data authorization request is used to request that the user node is allowed to use the user credit data corresponding to the user identifier provided by the provider node that sent the data authorization request;

Wherein, the use node is used to request the user credit data corresponding to the user identification from the at least two providing nodes, and the user credit data corresponding to the user identification includes: the user credit data provided by the at least two providing nodes respectively User credit data corresponding to the user identifier;

The prompt information is used to request confirmation whether the user node is allowed to use the user credit data corresponding to the user identifier provided by the at least two providing nodes respectively.

In a possible implementation manner, the device further includes:

An input module, the input module being configured to receive input information through an input device, the input information being used to confirm whether the user node is allowed to use the user credit data corresponding to the user identifier provided by the at least two providing nodes;

The transceiver module is further configured to send data authorization to the provider node when the input information indicates that the user node is allowed to use the user credit data corresponding to the user identifier provided by the at least two provider nodes In response, any of the data authorization responses is used to confirm that the user node is allowed to use the user credit data corresponding to the user identifier provided by the providing node that receives the data authorization response.

In the seventh aspect, this application also provides a data right confirmation device based on a blockchain network, located at a blockchain node,

One or more processors;

Memory, used to store one or more programs;

When the one or more programs are executed by the one or more processors, the device realizes the method according to any one of the above-mentioned first aspects.

In an eighth aspect, this application also provides a data right confirmation device based on a blockchain network, which is located in a user terminal or a user client,

One or more processors;

Memory, used to store one or more programs;

When the one or more programs are executed by the one or more processors, the device realizes the method according to any one of the above-mentioned first aspects.

In a ninth aspect, the present application provides a computer-readable storage medium, including a computer program, which when executed on a computer, causes the computer to execute any one of the first to third aspects described above method.

In a tenth aspect, this application provides a computer program that, when executed by a computer, implements the method described in any one of the first to third aspects.

Description of the drawings

In order to more clearly describe the technical solutions in the present application or the prior art, the following will briefly introduce the drawings that need to be used in the description of the embodiments or prior art. Obviously, the drawings in the following description are the present For some of the embodiments of the application, for those of ordinary skill in the art, other drawings may be obtained based on these drawings without creative labor.

FIG. 1 is a schematic diagram of a network architecture of a blockchain network involved in an embodiment of this application;

2A is the first schematic diagram of the system architecture applied by the blockchain network-based data verification method provided by an embodiment of this application;

2B is a second schematic diagram of the system architecture applied by the blockchain network-based data verification method provided by an embodiment of this application;

FIG. 3 is the first interactive flowchart of a method for data right confirmation based on a blockchain network provided by an embodiment of the application;

4 is a second interactive flowchart of a method for data right confirmation based on a blockchain network provided by an embodiment of this application;

FIG. 5 is a schematic diagram of an application architecture of a method for data right confirmation based on a blockchain network provided by an embodiment of the application;

FIG. 6 is the third interaction flow chart of the method for data right confirmation based on the blockchain network provided by an embodiment of the application;

FIG. 7 is a structural schematic diagram 1 of a data right confirmation device based on a blockchain network provided by an embodiment of the application;

FIG. 8 is a schematic diagram 2 of the structure of a data right confirmation device based on a blockchain network provided by an embodiment of the application;

FIG. 9 is a schematic structural diagram of a blockchain node provided by an embodiment of the application;

FIG. 10 is a schematic structural diagram of a user terminal provided by an embodiment of the application.

Detailed ways

In order to make the purpose, technical solutions and advantages of this application clearer, the technical solutions in this application will be clearly and completely described below in conjunction with the drawings in this application. Obviously, the described embodiments are part of the embodiments of this application. , Not all examples. Based on the embodiments in this application, all other embodiments obtained by those of ordinary skill in the art without creative work fall within the protection scope of this application.

In order to improve the security of user data, this application provides a technical solution for traceable data usage. The technical solution provided by this application will be implemented based on the blockchain network. The following first describes the system architecture of the blockchain network as an example.

FIG. 1 is a schematic diagram of a network architecture of a blockchain network involved in an embodiment of this application.

As shown in Figure 1, the network can include multiple blockchain nodes. In the embodiments of the present application, each blockchain node in the blockchain network may have one or more network functions and business functions at the same time.

In a blockchain network, blockchain nodes can be preliminarily divided into ordinary nodes (peer), ordering nodes (Orderer), etc. according to network functions. Ordinary nodes can usually be deployed to achieve certain business functions. In some scenarios, a blockchain node can be both an ordinary node and an ordering node.

According to the specific network functions, the ordinary nodes in the blockchain network can be divided into the following types: verification/submission node (Committer peer), endorsement node (Endorse peer), leader node (Leader peer), anchor node (Anchor peer). Among them, the verification/submission node can be used to submit transactions, and receive transaction information (also known as transaction blocks), and verify the transaction information before the transaction information is written into the locally stored ledger; the endorsement node can be used according to this node The smart contract (chain code) installed on the system generates digital signatures for data transactions; the leader node can be used to combine the transaction information (transaction transaction) from the ordering node when the organization (in a channel) includes multiple blockchain nodes ) Is assigned to verification/submission nodes in the organization; anchor nodes can be used to implement communication between nodes within the organization and nodes outside the organization.

An important concept of the blockchain network is the ledger, which can also be called a shared ledger. The ledger is used to record the information sent or received by the nodes in the blockchain network. The ledger can record communication messages through a blockchain (blockchain). The blockchain is composed of several blocks. Each block can contain transaction information for a period of time. The blocks in the blockchain network are connected in sequence in the order of generation. The blockchain network needs to ensure that there are at least two blockchain nodes that store the ledger or copy of the ledger. The blockchain node that stores the ledger or copy of the ledger locally can be called the accounting node, and all blocks in the blockchain network All chain nodes can be accounting nodes. The order of the blocks in the blockchain is not allowed to be changed. If the order or content of the blocks in the blockchain stored by any accounting node changes, the accounting node and other accounting nodes are stored in the same area. Block chains will be inconsistent, and this mechanism can guarantee the integrity, correctness, and non-modification of the information recorded in the block chain network.

The ordering node can be used for consensus processing. Illustratively, the ordering node can verify the communication information in the blockchain network, and generate a block when the verification passes, and the ordering node can also be used to confirm the blockchain network The sequence of generating blocks, and sending the blocks generated in the network to each accounting node, so that the accounting node adds the blocks to the blockchain in the order of block generation.

Using the technology related to the ledger in the blockchain network, the communication messages transmitted through the blockchain network can be stored in the ledger in the form of blocks (that is, stored in the blockchain), and then the application scenarios involved Traceability requirements for communication messages. The embodiments of this application will be described in detail in the following sections.

It should be noted that a blockchain node can simultaneously have the network functions of one or more types of ordinary nodes. Exemplarily, a blockchain node can be a submission node, an endorsement node, an anchor node, and an accounting node at the same time.

In a blockchain network, ordinary nodes can be deployed to implement the business functions of one or more network devices.

When realizing the business functions of network equipment, the ordinary nodes in the blockchain network can be divided into one or more organizations, each organization can include one or more ordinary nodes, and the ordinary nodes in an organization can be independent or cooperate with each other In order to realize the business functions of a certain network device, the ordinary nodes in the organization can also individually or cooperate with each other to realize some network functions of the organization in the blockchain network. Exemplarily, nodes in each organization may communicate through a wide area network (wan).

In the technical solution provided by this application, a related technology of the blockchain network will also be involved. This technology can be called fabric technology. One of the key points of this technology is to support the multi-ledger feature. This technology meets the requirements of the system for the confidentiality and isolation of the ledger by dividing channels in the blockchain network. Channels can be used to limit the scope of data interaction between blockchain nodes. A blockchain node only allows other blockchain nodes with the same channel to communicate. In this technology, each channel can correspond to a ledger, and the ledger corresponding to the channel can be accessed by all members of the channel. When the blockchain network is divided into several channels, the blockchain node in the blockchain network can have the attribute of the channel to which it belongs. It should be noted that a blockchain node can correspond to one or more channels, that is, a zone A block chain node can belong to one or more channels. When the channel attribute of a block chain node indicates that the block chain node corresponds to a certain channel, the block chain node can be called a member of the channel. The channel attribute of a block chain node indicates that when the block chain node corresponds to multiple channels, the block chain node can be a member of multiple channels.

For example, a blockchain network may include multiple blockchain nodes. Among the multiple blockchain nodes, the number of blockchain nodes belonging to channel1 may be A1, and A1 is greater than or equal to 2; multiple blockchain nodes The number of blockchain nodes belonging to channel2 can be A2, and A2 is greater than or equal to 2. For channel1, B1 of the A1 blockchain nodes can store the ledger of channel1; B1 is greater than or equal to 2. , And B1 is less than or equal to A1. Then A1 blockchain nodes in channel1 can be allowed to access the ledger of channel1, and A2 blockchain nodes in channel2 can be allowed to access the ledger in channel2.

It should be noted that there can be one or more channels to which a blockchain node belongs, and the blockchain nodes in different channels can be all different or partly different. In other embodiments of the present application, the blockchain network supporting channel will be exemplarily described in combination with the actual application scenarios of the present application, which will not be repeated here.

An example description will be given below in conjunction with actual application scenarios of the embodiments of the present application.

2A is the first schematic diagram of the system architecture applied by the blockchain network-based data verification method provided by an embodiment of this application. As shown in FIG. 2A, the system can be called a data right confirmation system, and the system can include a blockchain network 100 and a user terminal 10. The blockchain network 100 may include multiple blockchain nodes 20, and the number of user terminals may be one or more. The blockchain nodes in the blockchain network can be used to implement multiple network devices with business functions. One or more user clients can be deployed on the user terminal, and the user clients deployed on the user terminal can interact with various network devices in the blockchain network that are implemented through blockchain nodes.

In the actual application scenario of the embodiment of the present application, the user using the user terminal or the user client may correspond to a user identification. For example, one user can use one or more user terminals, that is, one user terminal can correspond to one user ID, or multiple user terminals can correspond to the same user ID. One or more user clients can be deployed on each user terminal, and the user ID corresponding to the user client can be the user ID corresponding to the user account logged in on the user client, that is, one user client can correspond to one user ID Or, multiple user clients can correspond to the same user ID. In an example, each user terminal used by a user and a user client deployed on each user terminal used by the user may correspond to the same user identification.

In an application scenario of the embodiment of the present application, for example, the system may include user terminals T1, T2, T3, and T4, where the user client deployed on each user terminal may include C1, C2, C3, C4, C5, C6, C7. Table 1-1 is an illustration of the correspondence between users, user terminals, user clients, and network devices communicating through the user clients.

Table 1-1

As shown in Table 1-1, user 1 can use user terminal T1. Three user clients C1, C2, and C3 are installed on T1. User clients C1, C2, and C3 are respectively used to communicate with network device 1, network device 2. , The network device 3 communicates. User 2 can use user terminals T2 and T3. User client C4 installed on T2 can be used to communicate with network device 1, and user client C5 installed on T2 can be used to communicate with network device 2 and network device 3. T3 The user client C6 installed on the device can communicate with the network device 4, and the user 3 can use the user terminal T4. The user client C7 installed on the T4 can be used to communicate with the network device 1, network device 2, network device 3, and network device 4. To communicate.

2B is a second schematic diagram of a system architecture applied by the blockchain network-based data verification method provided by an embodiment of this application. As shown in Figure 2B, each blockchain node in the blockchain network can be used to implement the business functions of certain network devices. The blockchain node corresponding to each network device can be maintained through the corresponding blockchain client.

Exemplarily, in an application scenario of the embodiment of the present application, the blockchain network may include: ordinary nodes P1, P2, P3, P4, P5, P6, and P7. The network devices corresponding to the organizations to which P1 and P2 belong may be data user servers U1 and U2, respectively, and the network devices corresponding to the organizations to which P3, P4, and P5 belong are data provider servers V1, V2, and V3, respectively. In addition, the network devices corresponding to the organizations to which P6 and P7 belong may be data agent servers W1 and W2.

For example, the above-mentioned data users can provide banks and other institutions that provide users with business services, such as Industrial and Commercial Bank of China, Agricultural Bank, and China Construction Bank. Data providers can store various credits of users for telecommunication operators and Internet transaction platforms. Recorded institutions, such as China Mobile, China Unicom, Jingdong Mall, Taobao, Alipay, etc. Any bank client can be installed on the user terminal, and the user can perform operations on the bank client to initiate a business request to the bank.

For ease of description, the common nodes P1 and P2 of the corresponding network equipment type of the data user server can be referred to as user nodes, and the common nodes P3, P4, and P5 of the corresponding network equipment type of the data provider server can be referred to as providing For the node, the normal node P6 whose corresponding network device type is a data agent server can be called an agent node. In the embodiment of this application, the proxy node is not a node that must exist in the blockchain network.

In the actual application scenario of the embodiment of the present application, the use node can communicate with the user client deployed on the user terminal, the use node can communicate with one or more provision nodes, and the provision node can communicate with the user client deployed on the user terminal. End communication. For example, a user client that communicates with one or more use nodes may be installed on the user terminal, and the user terminal may communicate with the server on the use node based on the user client. For example, if the use node is a bank server, then The user client used to communicate with the user node may be a mobile banking client. In addition, a user client that communicates with one or more provider nodes may also be installed on the user terminal. For example, if the provider node is an operator server, The client used to communicate with the providing node may be a mobile phone business hall client of an operator. Table 1-2 is an illustration of the correspondence between the user client deployed on the user terminal and the blockchain node with various business functions when performing business interactions.

Table 1-2

As shown in Table 1-2, user client C1 can be used to communicate with using node U1, user client C5 can communicate with providing nodes V1 and V2, and user client C7 can communicate with using node U1 and providing nodes V1 and V1. V3 communicates.

In the actual application scenario of the embodiment of the present application, the business function of each node in the blockchain network can be exemplified as follows.

The use node can be used to confirm the user credit data corresponding to the required user identification according to the service request carrying the user identification (for example, from receiving the service request carrying the user identification), and to obtain the user credit data corresponding to the user identification, and according to The obtained user credit data processes the service request carrying the user identification. For example, the user node may receive a service request carrying a user ID, and then send a data transaction request to the providing node. The data transaction request may be used to request user credit data corresponding to the user ID required by the service request carrying the user ID. Then, the user credit data corresponding to the user identification provided by the providing node is received, and service processing is performed according to the received data. In the embodiment of the present application, the user credit data corresponding to the user ID may refer to the user credit data corresponding to the user ID logged in on the user client sending the service request, or the user ID of the user who uses the user terminal sending the service request corresponds to The user’s credit data, for example, the user’s credit report, telecommunication service usage record, life payment record, etc.

Provide nodes, which can be used to provide massive user credit data. For example, the providing node can receive a data transaction request from any using node, and then, according to the user ID in the data transaction request, send a data authorization request to the user client corresponding to the user ID. The data authorization request can be used to request confirmation Whether to allow the use node to use the user credit data corresponding to the user ID provided by the providing node, and then, when receiving the data authorization response sent by the user client, if the data authorization response indicates that the data authorization is confirmed, that is, when the authorization is successful, provide The node sends the user credit data corresponding to the user identification previously requested by the node to the user node.

In an actual application scenario of the embodiment of the present application, a proxy node may also be deployed in the system. The user node in the system can communicate with one or more agent nodes, and the agent node can communicate with one or more provider nodes.

The proxy node may sign a data agency contract with the providing node in advance, and the data agency contract may stipulate the scope and period of user credit data that the proxy node obtains from the providing node and allows transactions with the user node. When a proxy node is deployed in the system, the user node can send a data transaction request to the proxy node, and the proxy node can send a data transaction request to the providing node when confirming that the data requested by the user node belongs to the proxy node's proxy range. When the providing node obtains data authorization from the user client, it can send the user credit data requested by the user node to the proxy node, and the proxy node sends the user credit data to the user node.

Among the multiple blockchain nodes in the blockchain network, the above-mentioned blockchain node deployed with certain business functions may be referred to as the first blockchain node. The multiple blockchain nodes in the blockchain network may also include a blockchain node, and the blockchain node may be called a consensus node.

The consensus node can be used to receive the communication information transmitted in the blockchain network and record the communication information in the ledger of the blockchain network.

It should be noted that in the blockchain network, the communication information between blockchain nodes is spread by broadcasting, that is, one blockchain node sends any communication information to another blockchain node At this time, the communication information will also be sent to other neighboring blockchain nodes. In other words, the consensus node can be a blockchain node in addition to sending or receiving certain communication information. For example, the consensus node can be used to verify the sender information carried in the communication information when receiving any communication information transmitted in the blockchain network, and confirm that the communication information is indeed the sender. When sending, confirm that the communication information has passed the verification. After that, the consensus node packs the communication information that has passed the verification to obtain a block, and sends the block containing the communication information to the accounting node in the blockchain network. Make the accounting node record the communication information in the form of blocks in the ledger stored locally by the accounting node. In the embodiment of the present application, the consensus node may be a blockchain node other than using nodes, providing nodes, and proxy nodes. Exemplarily, the consensus node may be a blockchain node with the network function of an ordering node in the blockchain network.

The division of channels to which multiple blockchain nodes belong in the actual application scenario of the embodiment of the present application will be exemplified below. In the actual application scenario of the embodiment of the present application, when multiple nodes are used or provided, multiple channels can also be divided in the blockchain network.

Table 2-1 is an indication of the channel to which multiple blockchain nodes belong.

table 2-1

channel number	Use node	Proxy node	Provide node
channel1	U1	-	V1
channel1	U1	-	V2
channel1	U1	-	V3
channel2	U2	-	V1
channel2	U2	-	V2
channel2	U2	-	V3

Among them, the blockchain nodes in channel1 and channel2 are partly the same. As shown in Table 2-1, the members of channel1 can include using node U1, providing nodes V1, V2, and V3, then the information between U1 and V1, the information between U1 and V2, and the information between U1 and V3 can be recorded In the ledger corresponding to channel1. The members of channel2 can include using node U2, providing nodes V1, V2, and V3. Then the information between U2 and V1, the information between U2 and V2, and the information between U2 and V3 can be recorded in the ledger corresponding to channel2. It should be noted that U2 cannot access the ledger of channel 1, and U1 cannot access the ledger of channel.

Table 2-2 is another indication of the channel that multiple blockchain nodes belong to.

Table 2-2

channel number	Use node	Proxy node	Provide node
channel1	U1	W1	V1
channel1	U1	W1	V2
channel1	U1	W1	V3
channel2	U2	W2	V1
channel2	U2	W2	V2
channel2	U2	W2	V3

Among them, the difference from Table 1 is that there are proxy nodes W1 and W2 deployed in the system. As shown in Table 2-2, the members of channel1 can include using node U1, proxy node W1, and providing nodes V1, V2, and V3. Then the information between U1 and W1, the information between W1 and V1, the information between W1 and V2, and the information between W1 and V3 can be recorded in the ledger corresponding to channel1. The members of channel2 can include using node U2, proxy node W2, providing nodes V1, V2, and V3, then the information between U2 and W2, the information between W2 and V1, the information between W2 and V2, and the information between W2 and V3 The information can be recorded in the ledger corresponding to channel2. It should be noted that U2 and W2 cannot access the ledger of channel1, and U1 and W1 cannot access the ledger of channel2.

The following is an exemplary description of the method for data right confirmation based on the blockchain network provided in the embodiments of the present application.

FIG. 3 is an interactive flowchart 1 of a method for data right confirmation based on a blockchain network provided by an embodiment of this application. The embodiments of the present application relate to user terminals, use nodes, provision nodes, and consensus nodes. As shown in Figure 3, the steps of the embodiment of the present application may include:

S301: The user client on the user terminal sends a service request carrying the user identifier to the using node.

Wherein, for example, a first user client that can be used to communicate with the user node may be installed on the user terminal, and the user terminal may use the first user client to send service requests to the user node, and a server may run on the user node. . The user identification carried in the service request may be a user identification corresponding to the user client or the user terminal.

S301-A, the use node sends a service request to the consensus node.

Among them, the user node can send the service request and the information of the sender of the service request to the consensus node, that is, the identity of the user client or the user terminal.

The user node is located in the blockchain network. When the user node receives the service request sent by the user client, the user node can broadcast the service request to the consensus node in the blockchain network through the communication link connected to itself. , So that the consensus node will verify the business request, package the business request when the verification is passed, generate a block, and send the block to the accounting node in the blockchain network so that the accounting node can Business requests are recorded in the ledger of the blockchain network in the form of blocks. For step S301-A, the consensus node can be any other blockchain node in the blockchain network except the use node.

It should be noted that, in the embodiment of the present application, each blockchain node in the blockchain network can use the communication link in the blockchain network to transmit communication information between the nodes. Each blockchain node in the blockchain network can spread communication information through broadcast. There can be one or more consensus nodes in the blockchain network. Any consensus node can verify the communication information received from another blockchain node. When the verification passes, it will be in the blockchain network. The received communication information is recorded in the ledger of the blockchain network.

In S301-C, the consensus node verifies the business request, and when the verification is correct, records the business request in the ledger.

Among them, if the consensus node receives the service request from the user node, the consensus node confirms that the verification is successful when confirming that the sender information carried in the service request is the user node.

It should be noted that, in the embodiments of this application, the consensus node itself may not be a billing node, and the consensus node can package the received communication information into a block and send it to the billing node so that the billing node can transfer the communication information Recorded in the form of blocks in the ledger stored locally by the accounting node.

S302: The user node determines the user credit data corresponding to the user identifier that needs to be obtained according to the service request.

Wherein, for example, the user node can determine the required user credit data identifier according to the service identifier of the service request.

S303: The using node sends a data transaction request to the providing node.

Wherein, for example, the data transaction request may include: user identification, user credit data identification, service identification of the service applied for by the user terminal, and so on.

S303-A, the use node sends a data transaction request to the consensus node.

Wherein, the using node can send the data transaction request in a similar manner to the sending of the service request in step S301-A.

S303-B, the providing node sends a data transaction request to the consensus node.

Wherein, the providing node can send the data transaction request in a manner similar to that of using the node to send the data transaction request in step S303-A.

It should be noted that S303-A and S303-B in the embodiment of the present application can be executed either. The consensus nodes in step S303-B and step S303-A may be the same consensus node in the blockchain network, or may be different consensus nodes. For step S303-B, the consensus node in this step may be any blockchain node in the blockchain network except the providing node.

In S303-C, the consensus node verifies the data transaction request, and when the verification is correct, records the data transaction request in the ledger.

Among them, step S303-C is similar to step S301-C. Regardless of whether the consensus node receives the data transaction request from the using node or the providing node, the consensus node verifies the sender's information carried in the data transaction request and confirms the data transaction When the sender of the request is a node, confirm that the verification is successful. The manner in which the consensus node records the successfully verified data transaction request in the ledger is similar to the manner in which the business request is recorded in the ledger in step S301-C.

It should be noted that if the communication link between the using node and the providing node passes through the consensus node, in step S303, the using node can send a data transaction request to the providing node through the consensus node, and the consensus node will receive the data transaction request After that, on the one hand, the data transaction request can be forwarded to the providing node, and on the other hand, the data transaction request can be verified and recorded in the ledger.

S304: The providing node sends a data authorization request to the user client on the user terminal.

Wherein, exemplarily, a second user client for communicating with the providing node may be deployed on the user terminal. The user ID corresponding to the user account logged in on the second user client is the same as the user ID corresponding to the user account logged in on the first user client. The second user client and the first user client may also be the same user client, and the user client supports both communication with the use node and communication with the providing node. The data authorization request can be used to request confirmation whether the user node is allowed to use the user credit data corresponding to the user ID provided by the providing node. In an example, the data authorization request may be specifically used to request confirmation whether the user node is allowed to use the user credit data corresponding to the user identifier provided by the providing node when receiving the service request of the first service sent by the first user client. Exemplarily, the data authorization request may include: the identification of the use node, the user identification, the identification of user credit data, the business identification of the service request, and so on.

S304-A, the providing node sends a data authorization request to the consensus node.

Wherein, the providing node can send the data authorization request in a similar manner to the sending of the data transaction request by the node in S303-A.

In S304-C, the consensus node verifies the data authorization request, and when the verification is correct, records the data authorization request in the ledger.

Wherein, step S304-C is similar to step S303-C, the consensus node verifies the information of the sender carried in the data transaction request, and confirms that the verification is successful when confirming that the sender of the data authorization request is the providing node. The manner in which the consensus node records the successfully verified data authorization request in the ledger is similar to the manner in which the data transaction request is recorded in the ledger in step S303-C.

S305: The user client on the user terminal outputs prompt information through the output device, the prompt information is used to request confirmation whether the user credit data provided by the providing node is allowed to be used by the user node.

Among them, the output device may be a display screen, speakers, earphones, etc. on the user terminal. For example, a second user client for communicating with the providing node may be installed on the user terminal, and a display interface for requesting the user to confirm whether the user is allowed to use the user credit provided by the providing node may be displayed on the display interface of the second user client. Information about the data. Exemplarily, the prompt information may include: the identification of the usage node, the user identification, the identification of user credit data, the business identification of the service request, and the selection button of whether to agree to authorization, etc.

S306: The user client on the user terminal receives input information through the input device, and the input information is used to confirm whether the user credit data provided by the user node is allowed to be used by the user node.

Among them, the input device may be a display screen with touch function, keyboard, button, microphone, etc. Exemplarily, the second user client can receive the user's touch operation on the display screen in the display interface. For example, if the user clicks the "Agree" button on the screen, the input information can be to confirm the authorization, if the user clicks the screen On the "Reject" button, the input information can be that authorization is not allowed.

S307: The user client on the user terminal sends a data authorization response to the providing node.

Wherein, for example, the data authorization response may carry indication information that the second user client on the user terminal confirms that it is allowed or confirmed that the use node is not allowed to use the user credit data provided by the providing node. Exemplarily, the data authorization response may include: using node identification, user identification, user credit data identification, service identification of the service request, and indication information of whether to agree to authorization, etc. In some scenarios, the second user client may also send a data authorization response only when the input information indicates that the user allows authorization.

S307-B, the providing node sends a data authorization response to the consensus node.

Wherein, the providing node may send the data authorization response to the consensus node after receiving the data authorization response sent by the second user client on the user terminal.

In S307-C, the consensus node verifies the data authorization response, and when the verification is correct, records the data authorization response in the ledger.

Among them, similar to step S304-C, the consensus node can verify the sender of the data authorization response. When confirming that the sender is the second user client on the user terminal, confirm that the verification is successful, and record the data authorization response In the ledger.

S308: The providing node obtains user credit data corresponding to the user identifier.

Wherein, in an implementation manner of the embodiment of the present application, the providing node may obtain the required user credit data when the confirmation data authorization response indicates that the second user client allows the use node to use the user credit data provided by the providing node. In another implementation manner, it should be noted that steps S304 to S307-C may not be necessary steps in the embodiment of the present application. Illustratively, after the providing node receives the data transaction request of the use node, The data transaction agreement signed in advance with the user node determines whether the user node has the right to use the user credit data corresponding to the requested user ID. Illustratively, the data transaction protocol can be a smart contract (chaincode, also known as chain code) The form of is stored on the providing node and the user node. The data transaction protocol can stipulate the range of user identification allowed by the use node, the range of user credit data identification, and the use period of user credit data.

The providing node may obtain user credit data in many ways. For example, the providing node may obtain the user credit data corresponding to the user ID from the providing node's own database or the provider data server connected to it. In some scenarios, the provider data server may be located in the blockchain network or outside the blockchain network. For example, the provider may be a telecommunications operator, such as China Mobile, China Unicom, and China Telecom. The user credit data provided by the corresponding provider node of China Mobile may be the user credit data provided by the corresponding user terminal when using China Mobile’s telecommunications service. Some credit records, for example, recharge records, arrears records, user star ratings, whether they belong to a blacklist, whether to send malicious text messages or make harassing calls, etc.

S309: The providing node sends a data transaction response carrying user credit data corresponding to the user identifier to the using node.

Wherein, the providing node may send a data transaction response to the using node. Illustratively, the data transaction response may include: user identification, user credit data identification, user credit data use period, and service identification that allows the user node to use user credit data Wait.

In S309-A, the provision node sends a data transaction response to the consensus node.

S309-B, the use node sends a data transaction response to the consensus node.

Among them, step S309-A and step S309-B are similar to S303-A and S303-B.

In S309-C, the consensus node verifies the data transaction response, and when the verification is correct, records the data transaction response in the ledger.

Among them, step S309-C is similar to step S303-C.

S310: The using node processes the service request carrying the user identification according to the user credit data corresponding to the user identification.

Wherein, the user node processes the service request according to the obtained user credit data, and provides the service corresponding to the requested service to the first user client on the user terminal when the user credit data meets the service requirement for the user credit level.

S311: The use node sends the service processing result to the user client on the user terminal.

In the embodiment of the present application, after the above-mentioned various communication information is recorded in the ledger, the blockchain nodes in the blockchain network may be allowed to access the communication information in the ledger.

In the embodiment of this application, the number of consensus nodes and accounting nodes can be multiple. After any consensus node verifies any communication information received, it can send to other blocks in the blockchain network. The chain node broadcasts the verification result. When any accounting node stores any of the above communication information in the form of a block, it can notify other accounting nodes in the blockchain network to record the communication information synchronously to ensure the area The consistency of the ledgers stored in each accounting node in the blockchain network.

In the embodiment of the present application, the number of providing nodes may be multiple. Accordingly, the user credit data corresponding to the user identification may include user credit data corresponding to the user identification provided by multiple providing nodes, and the user node may send Multiple providing nodes respectively send data transaction requests, and any data transaction request can be used to request to obtain user credit data corresponding to the user identifier provided by the providing node that receives the data transaction request. Exemplarily, the user node may be Industrial and Commercial Bank of China, and the multiple providing nodes may be operators such as China Telecom, China Mobile, and China Unicom. Then the user credit data required by the user node may include the user identification in China Telecom, China Mobile, User credit data recorded in China Unicom's database, for example, Zhang's user credit data in China Telecom, China Mobile, and China Unicom.

It should be noted that the interaction steps between each blockchain node and the consensus node and the processing steps of the consensus node in the above embodiments are not the steps that must be performed in this application. In actual applications, it can be based on traceable requirements, such as which Communication information needs to be recorded in the ledger, set on the use node and the providing node, and after receiving or sending the communication information that needs to be recorded in the ledger, the communication information that needs to be recorded is sent to the consensus node. In addition, for the same piece of communication information, the blockchain node sending the communication information can be sent to the consensus node, or the blockchain node receiving the communication information can be sent to the consensus node. For the interaction information between the blockchain node and the user client on the user terminal, it can be set to be sent by the blockchain node to the consensus node.

In the technical solution provided by this application, the communication information between the user client, the user node, and the providing node can all be recorded in the ledger in the blockchain network, so that the use process of user credit data can be traced. Therefore, the technical solution provided by this application improves the security of user credit data.

Not only that, in the technical solution provided by this application, on the basis of providing the node to manage user credit data and signing a data transaction agreement with the user node, before the providing node provides user credit data to the user node, the providing node provides the user client again Confirm whether the data is authorized or not, so that users can understand the usage of their own user data in a timely manner, so that the use process of user credit data can be traced in real time on the user terminal side. In turn, the security of user credit data can be further improved.

The embodiments of the present application also provide an implementation manner, which involves multiple channels. For example, the blockchain network may include: X channels; the blockchain nodes in the blockchain network may correspond to X One or more of the channels; wherein, the channel corresponding to the first blockchain node in the multiple blockchain nodes may include the i-th channel, and the second blockchain node in the multiple blockchain nodes corresponds to The channels include the i-th channel, X is an integer greater than 0, and i is an integer greater than 0 and less than or equal to X. Among them, the first blockchain node may be the sender of communication information, and the second blockchain node may be the receiver of communication information. For example, the first blockchain node may be any of using nodes, providing nodes, and proxy nodes. One kind.

Any first blockchain node sending communication information to a consensus node may include: the first blockchain node sends channel information of the i-th channel to the consensus node through the i-th channel, so that the consensus node will The channel information of the i-th channel is recorded in the ledger corresponding to the i-th channel. Correspondingly, the channel information of the i-th channel may include: information transmitted between the first block chain node and the second block chain node through the i-th channel, and the first block chain node or The second blockchain node sends information to the user client based on the information received from the i-th channel, and the first blockchain node passes the first blockchain node based on the information received from the user client. The information sent by the i-channel to the second blockchain node, and the information sent by the second blockchain node to the first blockchain node through the i-th channel based on the information received from the user client At least one.

In an actual application, the blockchain network may include M use nodes, and the M use nodes respectively correspond to one of the X channels, and any use node transmits information through its corresponding channel and the providing node; the consensus The node corresponds to one or more channels. The first blockchain node is the corresponding channel among the M usage nodes as the jth usage node of the i-th channel, and the second blockchain node is the one that transmits information through the i-th channel and the jth usage node. Providing node; or, the first blockchain node is a providing node that transmits information through the i-th channel with the j-th user node corresponding to the i-th channel, and the second blockchain node is the j-th Use nodes; where M is an integer greater than 0, and j is an integer greater than 0 and less than or equal to M.

The following is an exemplary description of using multiple channels to achieve mutual isolation of communication information storage.

FIG. 4 is the second interaction flowchart of the method for data right confirmation based on the blockchain network provided by an embodiment of the application. The embodiments of the present application may involve user terminal T1, multiple user nodes U1, U2, providing node V1, and consensus nodes Z1, Z2. Among them, user terminal T1 can be deployed to communicate with each user node and providing node User client.

It should be noted that, in the embodiment of the application, the channels corresponding to U1 and U2 are channel1 and channel2, respectively. The communication information between T1 and U1, U1 and V1, U1 and Z1, and between V1 and Z1 and U1 are used The communication link transmission of channel1, the communication information between T1 and U2, U2 and V1, U2 and Z2, and between V1 and Z2 related to U2 are transmitted using the communication link of channel2. The consensus nodes Z1 and Z2 respectively store channel1 locally. And the ledger of channel2. Since the ledger of a channel is only allowed to be accessed by the members of the channel, the communication information maintained by each channel can be isolated from each other.

As shown in Figure 4, the steps of the embodiment of the present application may include:

S401: The user terminal T1 sends a first service request carrying a user identity to the user node U1.

Wherein, for example, the user terminal T1 may send the first service request to U1 through the user client C1, and the user client C1 supports communication with U1. The first service request carries the user ID as user 1, and the service ID as service 1.

S402: The user terminal T1 sends a second service request carrying the user identifier to the user node U2.

Wherein, for example, the user terminal T1 may send the first service request to U2 through the user client C3, and the user client C3 supports communication with U2. The second service request carries the user ID as user 1, and the service ID as service 2.

S401-B, using node U1 to send a first service request to consensus node Z1.

In S401-C, the consensus node Z1 writes the first service request into the ledger corresponding to channel1.

S402-B: Use node U2 to send a second service request to consensus node Z2.

S402-C, the consensus node Z2 writes the second service request into the ledger corresponding to channel2.

S403: The using node U1 determines that the required user credit data identifier is D1 according to the first service request.

For example, the user credit data required by the first service request may be user credit data corresponding to user 1 and identified as D1.

S404: The using node U2 determines that the required user credit data identifier is D2 according to the second service request.

Exemplarily, the user credit data required for the second service request may be user credit data corresponding to user 1 and identified as D2.

S405: The node U1 is used to send a first data transaction request to the providing node V1.

Wherein, the first data transaction request may be used to request user credit data corresponding to user 1 and identified as D1.

S406, the node U2 is used to send a second data transaction request to the providing node V1.

Wherein, the second data transaction request may be used to request user credit data corresponding to user 1 and identified as D2.

S405-A, using node U1 to send a first data transaction request to consensus node Z1.

S405-C, the consensus node Z1 writes the first data transaction request into the ledger corresponding to channel1.

S406-A, using node U2 to send a second data transaction request to consensus node Z2.

S406-C: The consensus node Z2 writes the second data transaction request into the ledger corresponding to channel2.

S407: The providing node V1 sends a first data authorization request to the user terminal T1.

Wherein, the first data authorization request carries the user ID as user 1, the service ID as service 1, and the ID of required user credit data is D1. In an example, the providing node V1 may send a first data authorization request to the user client C1 on the user terminal T1, and the user client C1 supports communication with U1 and V1. In another example, the providing node V1 may The first data authorization request is sent to the user client C2 on the user terminal T1, and the user client C2 supports communication with V1.

S408: The providing node V1 sends a second data authorization request to the user terminal T1.

Among them, the second data authorization request carries the user ID as user 1, the service ID as service 2, and the ID of the required user credit data is D2. In an example, the providing node V1 may send a second data authorization request to the user client C3 on the user terminal T1, and the user client C3 supports communication with U2 and V1. In another example, the providing node V1 may The second data authorization request is sent to the user client C4 on the user terminal T1, and the user client C4 supports communication with V1.

S407-A, the providing node V1 sends the first data authorization request to the consensus node Z1.

S407-C: The consensus node Z1 writes the first data authorization request into the ledger corresponding to channel1.

S408-A, the providing node V1 sends the first data authorization request to the consensus node Z1.

S408-C: The consensus node Z2 writes the second data authorization request into the ledger corresponding to channel2.

S409: The user terminal T1 displays the first data authorization request on the user client and receives the first input information.

Wherein, for example, the user terminal T1 may display the first data authorization request on the user client C3 and receive the first input information.

S410: The user terminal T1 displays the second data authorization request on the user client and receives second input information.

Wherein, for example, the user terminal T1 may display the second data authorization request on the user client C4 and receive the second input information.

S411: The user terminal T1 sends a first data authorization response to the providing node V1 according to the first input information.

Wherein, for example, the user terminal T1 may send the first data authorization response to the providing node V1 through the user client C3.

S412: The user terminal T1 sends a second data authorization response to the providing node V1 according to the second input information.

Wherein, for example, the user terminal T1 may send the first data authorization response to the providing node V1 through the user client C4.

S411-B, the providing node V1 sends the first data authorization response to the consensus node Z1.

S411-C, the consensus node Z1 writes the first data authorization response into the ledger corresponding to channel1.

S412-B, the providing node V1 sends a second data authorization response to the consensus node Z2.

S412-C: The consensus node Z2 writes the second data authorization response into the ledger corresponding to channel2.

S413: The providing node V1 obtains the user credit data D1 according to the first data authorization response.

Wherein, the providing node V1 may obtain the user credit data D1 corresponding to the user 1 according to the first data authorization response.

S414: The providing node V1 obtains the user credit data D2 according to the second data authorization response.

Wherein, the providing node V1 may obtain the user credit data D2 corresponding to the user 1 according to the second data authorization response.

S415: The providing node V1 sends a first data transaction response to the using node U1.

The first data transaction response may include user credit data D1 corresponding to user 1. In some scenarios, the providing node V1 can send the user credit data corresponding to the user ID to the consensus node, so that the consensus node records the user credit data in the blockchain, and the user node can obtain the user ID corresponding to the user ID from the blockchain. User credit data.

S416: The providing node V1 sends a second data transaction response to the using node U2.

The second data transaction response may include user credit data D2 corresponding to user 1.

In S415-A, the provision node V1 sends the first data transaction response to the consensus node Z1.

In S415-C, the consensus node Z1 writes the first data transaction response into the ledger corresponding to channel1.

S416-A, the provision node V1 sends a second data transaction response to the consensus node Z2.

S416-C, the consensus node Z2 writes the second data transaction response into the ledger corresponding to channel2.

S417: Use the node U1 to process the first service request.

Wherein, for example, the node U1 is used to process the first service request according to the user credit data D1 corresponding to the user 1.

S418: Use the node U2 to process the second service request.

Wherein, for example, the use node U2 processes the second service request according to the user credit data D2 corresponding to the user 1.

S419: Use the node U1 to send the first service response to the user terminal T1.

Wherein, for example, the using node U1 may send a first service response to the user client C1 on the user terminal T1, and the first service response may include the processing result of the first service request by the using node U1.

S420: The node UE2 is used to send a second service response to the user terminal T1.

Wherein, for example, the use node U2 may send a second service response to the user client C3 on the user terminal T1, and the second service response may include the processing result of the second service request by the use node U2.

S419-A: Use node U1 to send the first service response to consensus node Z1.

S419-C: The consensus node Z1 writes the first service response into the ledger corresponding to channel1.

S420-A, using node U2 to send a second service response to consensus node Z2.

S420-C, the consensus node Z2 writes the second business response into the ledger corresponding to channel2.

In the embodiments of the present application, the manner in which each user node, the provider node sends communication information to the consensus node, and the manner in which the consensus node records the received communication information in the ledger can refer to the description in the foregoing embodiment. The only difference is: The consensus node writes the communication information of each channel into the ledger corresponding to the corresponding channel, which will not be repeated here.

In the technical solution provided by the embodiments of this application, the user node U1 is only allowed to access the ledger corresponding to channel1, and the user node U2 is only allowed to access the ledger corresponding to channel2, so that it can be ensured that the communication information related to each user node is only allowed to be Member access in the channel. Exemplarily, the use node U1 can be ICBC, and the use node U2 can be China Construction Bank. The storage of communication information during the data verification process of ICBC and China Construction Bank is isolated from each other, and ICBC and China Construction Bank cannot access the other bank. Communication information recorded in the related ledger.

In the embodiment of this application, in an implementation manner, the consensus nodes Z1 and Z2 can be the same blockchain node, that is, the consensus node can store the ledgers corresponding to channel1 and channel2 at the same time, but according to the requirements of isolation , The user node U1 is still only allowed to access the communication information in the ledger corresponding to channel1 on the consensus node, and the user node U2 is only allowed to access the communication information in the ledger corresponding to channel2 on the consensus node.

In other embodiments of the present application, when an agent node is deployed in the system, the communication information between the agent node and the user node and the providing node can also be recorded in the ledger corresponding to the channel according to the channel corresponding to the communication information.

For details and technical effects of other technical solutions of the embodiments of the present application, please refer to the related descriptions in the embodiment shown in FIG. 2, which will not be repeated here.

The following will exemplify the blockchain network-based data verification method provided by the embodiments of the present application in combination with some practical application scenarios of the embodiments of the present application.

In an application scenario, user A can apply for a business from a data user company. In order to reduce business risks, the data user company needs to make a credit evaluation on the user, and decide whether to handle the relevant business for the user according to the user's credit rating. The data user company can request user A’s telecommunication data from the data agent. The data agent checks whether there is any cooperation with the data user company, whether the cooperation has expired, etc., to confirm the authority of the data user company. The enterprise returns a denial of service. If it has permission, the data agent will apply to the operator for user A’s data, and the operator will check the data agent’s authority. If the operator checks that the data agent has no corresponding authority, then the data agent will return a denial , If the data agent has the authority, the data of user A will be returned to the data agent. After that, the data user company can obtain user A's data from the data agent, make a credit evaluation on the user, and decide whether to handle the relevant business.

According to the above business needs, the blockchain nodes corresponding to each organization can be deployed in the blockchain network. In practical applications, data users (ie data users, such as banks) can be deployed as user nodes, data provider companies (ie, data providers, such as operators) can be deployed as providing nodes, and data agents can be deployed as proxy nodes , The terminal used by the user can be a user terminal, and one or more user clients can be deployed on the user terminal to communicate with each user node and each providing node. The user can use the user client deployed on the user terminal to use the data The enterprise initiates a service request carrying the user ID.

FIG. 5 is a schematic diagram of an application architecture of a method for data right confirmation based on a blockchain network provided by an embodiment of the application. As shown in Figure 5, in the actual application business scenario, when a proxy node is deployed in the blockchain network, between the user client on the user terminal and the user node, between the user node and the proxy node, and the proxy node and The providing node, the providing node and the user client on the user terminal can respectively establish a communication connection. The user node can interact with the provider node through the agent node.

In a blockchain network, the business function of the proxy node may include at least one of the following: receiving a data transaction request sent by a user node, wherein the data transaction request is used to request user credit data corresponding to the user ID; and confirming the user node Whether it has the access authority to the user credit data corresponding to the user identification; and, when it is confirmed that the using node has the access authority, sending a data transaction request to the providing node; and receiving a data transaction response sent by the providing node, wherein the data transaction response Including user identification user credit data.

In order to realize the business functions of the above-mentioned proxy node, in an embodiment, the proxy node may sign a data transaction contract with each user node and each provider node. The data transaction contract between the proxy node and the providing node may stipulate the scope of the user credit data corresponding to the user ID obtained from a certain providing node by the proxy node, such as the scope of the user ID, the ID of the user credit data, the usage period, and the permission Use user credit data for business identification, etc. The data transaction contract between the proxy node and the user node can also be similarly agreed. Any agent node can sign data transaction contracts with multiple provider nodes, so that the service user node can be provided with user credit data corresponding to the user identifiers provided by the multiple provider nodes.

In addition, a communication connection can also be established between the proxy node in the blockchain network and any consensus node in the blockchain network. The proxy node receives the communication information from the using node or the providing node, or the proxy node After sending the communication information to the user node or the providing node, the received or sent communication information can be sent to the consensus node so that the consensus node can verify the communication information received from the proxy node, and when the verification is successful, the The communication information received from the agent node is recorded in the ledger of the blockchain network in the form of blocks. With this deployment method, the need for the traceability of communication information between proxy nodes and other blockchain nodes in the blockchain network can be achieved.

Exemplarily, when a proxy node is deployed, the basic process of the data right confirmation method provided in the embodiment of the present application may include the following stages.

Among them, the exchange of communication information between blockchain networks is realized by each blockchain node broadcasting the communication information to be sent to the blockchain network. Illustratively, the blockchain node as the sender of the communication information can communicate with neighbors. Each blockchain node sends the communication information to be sent. Each blockchain node in the blockchain network cooperates with each other according to the deployed business functions and network functions. Using nodes, agent nodes, and providing nodes can be maintained through the data consumer blockchain client, data agent client, and data provider client respectively.

In the first stage, the use node sends a data use request to the blockchain network.

Among them, (1) using the node to receive the service request sent by the user client on the user terminal, and personal data; (2) using the node to package the user ID (such as name, ID number, mobile phone number, etc.) with the requested service ID As a message M, the using node encrypts with its own corresponding public key, adds a private key signature, and sends it to other blockchain nodes (the other blockchain node may be a blockchain node other than the using node).

In the second stage, the proxy node sends a data usage request to the blockchain network.

Among them, (1) the agent node judges whether the using node has the data acquisition authority, if there is no authority, the processing flow is ended, if so, execute (2); (2) the agent node adds the data source list to the message M and packs it into a message M1, sent to other blockchain nodes (the other blockchain nodes may be blockchain nodes other than the proxy node).

In the third stage, the provision node applies to the user client on the user terminal for data usage rights.

Among them, (1) the providing node sends the data source list and data authorization application to the user client on the user terminal (for example, the second user client in the foregoing embodiment, not shown in the figure); (2) user client integration The received data authorization application meets the requirements of the data source list, such as the quantity and applicant ID, and activates the authorization operation; (3) The user client signs each data authorization application (indicating that the user is allowed to provide the node to use the user in the data source list Data), and encrypted with the public key of the corresponding applicant (that is, the corresponding user node providing node) to generate a message M2, and send it to the providing node or other blockchain nodes connected to the user terminal (the other blockchain node may be In addition to providing nodes (blockchain nodes).

In the fourth stage, provide nodes to send user data to the blockchain network.

Among them, (1) The providing node will use the node's information (such as bank information), data usage range, user data encrypted with the node's public key, and private key signature (that is, the signature of the user terminal) into a message M3 and send it to Other blockchain nodes (the other blockchain nodes may be other than the providing node); (2) After the user data is received by the user node (the message M3 can be decrypted and the user data can be extracted), Execute the smart contract, the input of the executed smart contract is the information of the use node and the information of the user terminal, and the output is the data use transaction. The use node can use the generated data use transaction (or the use node can receive it from the providing node or agent node (The user data of the user data) is sent to other blockchain nodes (the other blockchain node may be a blockchain node other than the use node); (3) The use node forwards user data to its own credit evaluation system, and identifies the user The corresponding user makes a credit evaluation, and processes the service request sent by the user client on the user terminal according to the credit evaluation result.

It should be noted that each node has established a cooperative relationship in advance, generates its own corresponding public key and private key pair and corresponding integer, and at the same time discloses their respective public keys in the blockchain network.

In the embodiment of the present application, the communication message transmitted in the above-mentioned blockchain network may adopt a unified message format. For example, the communication information may include the following fields: sender, label, message, and so on. Examples of unified message formats are as follows:

{sender:"",

label:"",

message:""}

The following uses specific examples to illustrate the interaction process and message format of the blockchain network-based data verification method provided in the embodiments of the present application.

FIG. 6 is the third interaction flowchart of the method for data right confirmation based on the blockchain network provided by an embodiment of the application. The embodiment of the application relates to the user client deployed on the terminal used by the user named Zhang, the ICBC blockchain node (i.e. the use node), the Unicom operator blockchain node (i.e. the provision node U1), and mobile operations Business blockchain node (i.e. providing node U2), data agent blockchain node (i.e. agent node W1) and other blockchain nodes (i.e. consensus node).

For example, the actual business requirements of the embodiments of the application may include: Zhang goes to ICBC to handle loan business. In order to reduce business risks, ICBC needs to use Zhang's user data stored in the operator to evaluate Zhang's credit. Before implementation, ICBC, as a data user, can sign a contract with a data agent to establish a data usage relationship. The data agent acts as a unified external interface for the two operators to provide data services and provide data services for data users. Operators are data source companies, and they open user data to data users with authorization.

As shown in Figure 6, the steps of the embodiment of the present application may include:

S600, the user client applies to the ICBC blockchain node for business and submits personal information.

Among them, by way of example, a user can apply for a loan service to ICBC through the user client, and the personal information provided can include name, ID number, mobile phone number, etc.

In S601, the ICBC blockchain node packages Zhang's personal data and business application into a message M, the label field is "bank_request", and the private key signature is added, and the message M is sent to other blockchain nodes.

Exemplarily, the content of the message M may be:

{sender:"bankID",

label:"bank_request",

message:{"name":"张某","ID":"5555555","telephone":"13243793294","business":"bank Loan"}}

Among them, bankID is the ID of Industrial and Commercial Bank of China, bank_request indicates that the message is a request sent by the bank, and the information in the message may include the user ID and the requested service ID.

It should be noted that in the embodiment of the present application, other blockchain nodes may be used to execute the steps performed by the consensus node in the foregoing embodiment.

In S602, other blockchain nodes broadcast the message M, verify the source of the message, and after confirming the consensus, write the message M into the blockchain.

Wherein, for example, after the message M is broadcast by other blockchain nodes, it can be verified that the message originated from ICBC, confirm the consensus, and write the message M into the blockchain (ie, the ledger of the blockchain network).

In S603, the data agent blockchain node checks the label field in the message M. If the value of the label field is "bank_request", execute S604. If the value of the label field is not "bank_request", only the transaction is written.

S604: The data agent blockchain node executes the smart contract, inputs the public key of the ICBC blockchain node, and judges whether the ICBC blockchain node has the authority to obtain user data, and if so, execute S605.

S605: The data agent blockchain node generates a message M1, the label field is "proxy_request", the message field adds a data source list, and the message M1 is sent to other blockchain nodes.

Exemplarily, the content of the message M1 may be:

{sender:"proxyID",

label:"proxy_request",

message:{"name":"Zhang","ID":"5555555","telephone":"13243793294","business":"bank Loan","data_source_list":["Mobile","Unicom"] }}

Among them, proxyID is the identification of the data agent, proxy_request indicates that the message is a request sent by the data agent, and the information in the message can include the user identification (name, ID, telephone), the applied business identification (business), and the data source list (data_source_list).

It should be noted that the data agency blockchain node can sign a data agency contract with the mobile operator blockchain node and the Unicom operator blockchain node in advance. The data agency contract can stipulate that the data agency node allows the use of mobile The scope, time limit, application scope, etc. of user data managed and provided by the blockchain node of the operator and Unicom operator. The application scope may include: permitted banks, permitted business identifications, etc. The data agency can determine the list of data sources that need to be obtained for this business within the scope of the data agency contract, so that the bank can obtain as much user data as possible. Exemplarily, if the data agent represents the data of the mobile operator and the Unicom operator, the identification of the mobile operator and the Unicom operator may be added to the message M1 as the data source list.

S606, other blockchain nodes broadcast the message M1 and verify the source of the message, and after confirming the consensus, write the message M1 into the blockchain.

S607-1: The blockchain node of the Unicom operator checks the label field in the message M1. If the value of the label field is "proxy_request", execute S607-2, and if the value of the label field is not "proxy_request", no operation is performed.

S608-1: The mobile operator blockchain node checks the label field in the message M1. If the value of the label field is "proxy_request", execute S608-2, and if the value of the label field is not "proxy_request", no operation is performed.

S607-2, the Unicom operator blockchain node generates a message M2, the label field value is "user_authorization_request", the message field includes the data source list and data use application, and the private key signature of the Unicom operator blockchain node is added and sent to User client.

Exemplarily, the content of the message M2 may be:

{sender: "data_source_ID",

label:"user_authorization_request",

message:{"data_source_list":["Mobile","Unicom"],"bank":"bankID","msg":"bankID want to use your personal data"}

Among them, data_source_ID is the identification of the data source company (such as Unicom operator blockchain node, mobile operator blockchain node), user_authorization_request indicates that the message is a request issued by the data provider (such as a user authorization request), and the information in the message It can include the data source list (data_source_list), the identification of the bank requesting the use of user data (such as ICBC's identification), and the content requested for authorization (such as ICBC's request to use your personal information).

S608-2, the mobile operator blockchain node generates a message M2', the label field value is "user_authorization_request", the message field includes the data source list and the data use application, and the mobile operator blockchain node’s private key signature is added and sent To the user client.

Exemplarily, the content of the message M2' may be:

{sender: "data_source_ID",

label:"user_authorization_request",

message:{"data_source_list":["Mobile","Unicom"],"bank":"bankID","msg":"bankID want to use your personal data"}

Among them, the meaning of each parameter is the same as that in S607-2.

S609: The user client activates the authorization operation when the number of data use requests received and the requester meets the requirements of the data source list.

Among them, the message M2 and the message M2' may be data use requests. The data use request functions similarly to the data authorization request sent by the use node or the proxy node to the providing node in the foregoing embodiment, and both can request the user client to confirm or know its own data. The situation is used.

Exemplarily, the data source list requirement may include the identification of one or more operators that the user client has negotiated and agreed to authorize, and the range of the amount of data requested to be used. For example, if the user corresponding to the user client is a mobile operator user, the data source list requirement may include the mobile operator's identification, and the range of the requested amount may include the number of user arrears in the past six months.

The user client can activate the authorization operation when confirming that it meets the requirements of the data source list. In an example, the activation authorization operation may include: the user client may confirm that the user confirms the authorization when the identifier of the operator that requests the data authorization request for the use of data and the amount of data requested meet the requirements of the data source list. At the time, the user client can display a prompt message confirming authorization to the user on the display interface to remind the user that the data is being used. In another example, the user client can display on the display interface the identity of the operator requesting the use of data, the amount of data requested, and business information, and prompt the user to confirm whether to authorize the operator to provide the corresponding user to the bank Data, when the user enters to agree to the authorization, the user client confirms the user to confirm the authorization.

S610: When the user confirms the authorization, the user client separately signs the data usage request and encrypts it with the public key of the corresponding requester to generate a message M3, the label field value is "user_authorization", and the message is sent to each operator blockchain node M3.

Among them, the user client separately signs each data usage request sent by each operator's blockchain node,

In the embodiment of the present application, the user client can send a message M3 to each providing node. In some embodiments, if the user client is connected to other blockchain nodes in the blockchain network, it can also send a message M3 to other blockchain nodes. When the user client directly sends a message M3 to other blockchain nodes At this time, S612 may be executed directly without executing S611.

Exemplarily, the content of the message M3 may be:

{sender:username

label:user_authorization

message:{"Mobile":M’,"Unicom":M’}}

Among them, username is the user ID corresponding to the user terminal (such as Zhang), user_authorization indicates that the message is user authorization (such as user authorization response) sent by the user terminal or user client, and the information in the message can include various data sources (such as mobile , China Unicom) and the encrypted data authorization request corresponding to each data source (such as the M'message obtained by encrypting the M2 message with the user's private key signature and the public key of each data source (data_source_ID)).

S611, each operator's blockchain node sends a message M3 to other blockchain nodes.

Among them, by way of example, the mobile operator blockchain node and the China Unicom blockchain node may respectively send a message M3 to other blockchain nodes.

S612, other blockchain nodes broadcast message M3 and verify the source of the message, and after confirming the consensus, write message M3 to the blockchain.

Among them, after the message M3 is broadcast by other blockchain nodes, it can be verified that the message originated from the user client, confirm the consensus, and write the message M into the blockchain (ie, the ledger of the blockchain network).

S613, each operator's blockchain node checks the label field in the message M3, and after confirming the user's signature, it packs the bank data, the data usage range, and the user data encrypted by the ICBC public key, and sends it to the ICBC blockchain node .

among them,

S614: After receiving the user data, the ICBC blockchain node executes a smart contract, inputs ICBC data and user data, generates a data usage transaction, and sends it to other blockchain nodes.

S615: The ICBC blockchain node forwards the received user data to the credit evaluation system, and makes a credit evaluation on the user.

In the embodiments of this application, based on the above-mentioned embodiments, the blockchain network deployed with use nodes, proxy nodes, and provision nodes can interact with the user client deployed on the user terminal, where the use node can be from the user The client receives the service request, and then the use node, proxy node, and provider node in the blockchain network perform their duties. The use node confirms the user credit data corresponding to the user terminal that needs to be obtained, and the proxy node confirms whether the requested data belongs to The agent scope of the agent node, the provision node sends a data authorization request (ie data use request) to the user client, the user client obtains the confirmation information input by the user through the human-computer interaction with the user, and feeds the authorization result back to the providing node. In this process, on the one hand, the ledger of the blockchain network can record the communication information between each blockchain node in the entire business process. At the same time, the blockchain network can also record the relationship between the user client and the blockchain node. It can be seen that the technical solutions provided in the embodiments of this application can achieve a complete record of the user data use process. When there are doubts about the user data use process among the use node, the proxy node, the providing node, and the user client, The preparation process information can be obtained from the ledger of the blockchain network.

In the embodiment of the present application, the user may use one or more user clients deployed on one or more user terminals to communicate with each user node and provider node. In an example, the user can use a user client to communicate with each providing node.

For details of other technical solutions and technical effects of the embodiments of the present application, please refer to the descriptions in the previous embodiments, which will not be repeated here.

The embodiment of the present application also provides a data right confirmation device based on a blockchain network.

FIG. 7 is a structural schematic diagram 1 of a data right confirmation device based on a blockchain network provided by an embodiment of the application; as shown in FIG. 7, an embodiment of this application also provides a data right confirmation device 700 based on a blockchain network. Applied to the first blockchain node in the blockchain network, the device 700 includes:

The transceiver module 701 is used to send or receive communication information;

The processing module 702 records the communication information in the ledger of the blockchain network;

Among them, the blockchain network includes multiple blockchain nodes. The multiple blockchain nodes include: using nodes and providing nodes; using nodes are used to request the providing node for the corresponding user identification according to the service request carrying the user identification User credit data; providing nodes, used to provide user credit data to using nodes; communication information including: information between the first blockchain node and any other blockchain node among the multiple blockchain nodes, and, At least one of the information between the first blockchain node and the user client; wherein the user client is used to send a service request carrying a user identification to the using node, and/or the user client is used to confirm whether to allow The providing node provides user credit data corresponding to the user identifier to the user node; the first blockchain node is a blockchain node among multiple blockchain nodes.

In a possible implementation manner, the processing module 702 may instruct the transceiver module 701 to send communication information to the consensus node, so that the consensus node records the communication information in the ledger of the blockchain network; the consensus node is multiple blockchains Among the nodes, blockchain nodes other than the first blockchain node.

In a possible implementation manner, the transceiver module 701 may be specifically used for:

Send communication information to the second blockchain node; or,

Receive the communication information sent by the second blockchain node; or,

Send communication information to the user client; or,

Receive communication information sent by the user client;

Wherein, the second blockchain node is any other blockchain node except the first blockchain node among the multiple blockchain nodes.

In a possible implementation, the first blockchain node may be a user node; the user client is used to send a service request carrying a user identifier to the user node;

The transceiver module 701 may be specifically used to send or receive communication information, where the communication information specifically includes: information between the use node and other blockchain nodes among multiple blockchain nodes, and the use node and the user client At least one of the information between; the consensus node is any one of the multiple blockchain nodes except the use node.

In a possible implementation manner, the first blockchain node is a providing node; the user client is used to confirm whether the providing node is allowed to provide user credit data corresponding to the user ID to the user node;

The transceiver module 701 may be specifically used to send or receive communication information, where the communication information specifically includes: providing information between the node and other blockchain nodes among multiple blockchain nodes, and providing the node and user clients At least one of the information between the terminals; the consensus node is any one of the multiple blockchain nodes except the providing node.

In a possible implementation manner, the first blockchain node is a user node; the user client is used to send a service request carrying a user identifier to the user node; the transceiver module 701 is specifically used for at least one of the following:

Receive a service request carrying a user ID sent by a user client;

Send a data transaction request to the providing node, the data transaction request is used to request the user credit data corresponding to the user ID, and the user credit data is used to use the node to process the business request carrying the user ID;

The data transaction response sent by the providing node is received, where the data transaction response includes user credit data corresponding to the user identification.

In a possible implementation, the first blockchain node is a providing node; the user client is used to confirm whether the providing node is allowed to provide user credit data corresponding to the user ID to the user node; the transceiver module 701 is specifically used for at least the following One:

Receive a data transaction request sent by the using node, the data transaction request is used to request to obtain user credit data corresponding to the user ID, and the user credit data is used to use the node to process the service request carrying the user ID;

Send a data authorization request to the user client, the data authorization request is used to request the user client to allow the user to provide user credit data corresponding to the user ID;

Receive the data authorization response sent by the user client, the data authorization response is used to confirm whether the user credit data corresponding to the user ID is allowed to be provided to the user node;

Send a data transaction response to the user node, and the data transaction response includes user credit data corresponding to the user ID.

In a possible implementation manner, the multiple blockchain nodes include: proxy nodes; proxy nodes are used to receive data transaction requests sent by the use nodes, and the data transaction requests are used to request user credit data corresponding to the user identification; and, Confirm whether the using node has the access authority to the user credit data corresponding to the user ID; and, when confirming that the using node has the access authority, send a data transaction request to the providing node; and receive the data transaction response sent by the providing node. The data transaction response includes User credit data corresponding to the user ID;

The first blockchain node is a proxy node; the transceiver module 701 is specifically used to send or receive communication information, where the communication information specifically includes: information between the proxy node and the user node, and the information between the proxy node and the providing node At least one.

In a possible implementation manner, the blockchain network includes: X channels; the blockchain nodes in the blockchain network correspond to one or more of the X channels; among them, the first blockchain node The corresponding channel includes the i-th channel, and the channel corresponding to the second blockchain node in the blockchain network includes the i-th channel;

The transceiver module 701 is specifically configured to record channel information of the i-th channel in the ledger corresponding to the i-th channel;

The channel information of the i-th channel includes: the information transmitted between the first block chain node and the second block chain node through the i-th channel, and the first block chain node or the second block chain node is based on the i-th channel The information received by the channel is sent to the user client, and the information sent by the first blockchain node to the second blockchain node through the i-th channel based on the information received from the user client, and the second blockchain At least one of the information sent by the node to the first blockchain node through the i-th channel based on the information received from the user client;

Wherein, X is an integer greater than 0, and i is an integer greater than 0 and less than or equal to X.

In a possible implementation, the blockchain network includes M user nodes, and the M user nodes respectively correspond to one of the X channels, and any user node transmits information through its corresponding channel and the providing node; consensus node Correspond to one or more channels;

The first blockchain node is the corresponding channel among the M usage nodes as the jth usage node of the i-th channel, and the second blockchain node is the providing node that transmits information through the i-th channel and the jth usage node; or , The first blockchain node is a node that provides information through the i-th channel and the j-th user node whose corresponding channel is the i-th channel, and the second blockchain node is the j-th user node;

Wherein, M is an integer greater than 0, and j is an integer greater than 0 and less than or equal to M.

In a possible implementation manner, the blockchain network includes M use nodes, the M use nodes respectively correspond to one of the X channels, and any use node transmits information through its corresponding channel and the providing node;

The multiple blockchain nodes include: proxy node; proxy node, used to receive data transaction requests sent by the user node, the data transaction request is used to request user credit data corresponding to the user ID; and to confirm whether the user node has the corresponding user ID User credit data access rights; and, when the user node is confirmed to have access rights, send a data transaction request to the providing node; and receive a data transaction response sent by the providing node, the data transaction response including user credit data corresponding to the user ID;

The first blockchain node is the corresponding channel among the M usage nodes as the jth usage node of the i-th channel, and the second blockchain node is a proxy node that transmits information through the i-th channel with the jth usage node; or , The first blockchain node is a proxy node that transmits information through the i-th channel and the corresponding channel is the j-th user node of the i-th channel, and the second blockchain node is the j-th user node; or, the first zone The block chain node is a proxy node that transmits information through the i-th channel with the j-th user node whose corresponding channel is the i-th channel, and the second block chain node is the provision of information transmitted through the i-th channel with the first block chain node node;

Wherein, M is an integer greater than 0, and j is an integer greater than 0 and less than or equal to M.

In a possible implementation manner, the providing node is an operator server; the user credit data is operator credit data corresponding to the user identification.

In the embodiment of the present application, for example, when the device 700 is located at the use node, the processing module 702 may be used to confirm the identification of the user credit data required according to the service request. When the device 700 is located at the providing node, the processing module 702 may use To confirm whether the using node has the authority to access user credit data corresponding to the user ID; when the device 700 is located at the proxy node, the processing module 702 can be used to confirm whether the using node has the authority to access the user credit data corresponding to the user ID provided by the providing node For example, please refer to the description of the execution steps of each blockchain node in the previous embodiment.

The data right confirmation device based on the blockchain network provided by the embodiment of the present application can be used to implement the method executed by each blockchain node in any of the foregoing embodiments. For details of the technical solution and technical effects, please refer to the description in the foregoing embodiment .

FIG. 8 is a schematic diagram 2 of the structure of a data right confirmation device based on a blockchain network provided by an embodiment of the application.

As shown in FIG. 8, an embodiment of the present application also provides a data right confirmation device 800 based on a blockchain network, which is applied to a user terminal or a user client. The device 800 includes:

The transceiver module 801 is configured to receive a data authorization request carrying a user ID corresponding to the user client sent by the providing node, and the data authorization request is used to request permission for the user node to use the user credit data corresponding to the user ID provided by the providing node;

The output module 802 is configured to output prompt information through an output device, and the prompt information is used to request confirmation whether the use node is allowed to use the user credit data corresponding to the user identification provided by the providing node;

Among them, the using node and the providing node are the blockchain nodes in the blockchain network, and the using node is used to request the user credit data corresponding to the user identifier from the providing node.

In a possible implementation manner, the transceiver module 801 may be specifically configured to receive at least two data authorization requests sent by at least two providing nodes, and the at least two data authorization requests respectively correspond to at least two providing nodes one-to-one. A data authorization request is used to request that the user node be allowed to use the user credit data corresponding to the user ID provided by the provider node that sent the data authorization request;

Wherein, the use node is used to request user credit data corresponding to the user identification from at least two providing nodes, and the user credit data corresponding to the user identification includes: user credit data corresponding to the user identification respectively provided by the at least two providing nodes;

The prompt information is used to request confirmation whether the use node is allowed to use the user credit data corresponding to the user identification provided by the at least two providing nodes respectively.

In a possible implementation manner, the apparatus 800 may further include:

Input module 802, the input module is used to receive input information through an input device, and the input information is used to confirm whether the use node is allowed to use the user credit data corresponding to the user identification provided by at least two providing nodes;

The transceiver module 801 is further configured to send data authorization responses to the providing nodes when the input information indicates that the user is allowed to use the user credit data corresponding to the user identification provided by the at least two providing nodes, and any data authorization response is used to confirm the permission The using node uses the user credit data corresponding to the user identification provided by the providing node that receives the data authorization response.

In the embodiment of the present application, the device 800 may further include a processing module 804. For example, the processing module 804 may be used to generate a data authorization response according to the input information of the user. Please refer to the steps performed by the user terminal or the user client in the previous embodiment. description of.

The data right confirmation device based on the blockchain network provided by the embodiment of the application can be used to implement the method executed by each user client and the second user client in any of the foregoing embodiments. For details of the technical solution and technical effects, please refer to the foregoing Description in the examples.

An embodiment of the present application also provides a blockchain node that executes the steps in the data identification method described in any of the foregoing embodiments. In an example, the blockchain node may be a server or a terminal.

An embodiment of the present application also provides a user client, which is used to execute the steps in the data identification method described in any of the foregoing embodiments.

The embodiment of the application also provides a blockchain node. FIG. 9 is a schematic diagram of the structure of the blockchain node provided by the embodiment of the application. As shown in FIG. 9, an embodiment of the present application also provides a blockchain node 900, including: one or more processors 901; a memory 902, used to store one or more programs; when the one or more programs It is executed by the one or more processors, so that the one or more processors implement the steps performed by the first blockchain node in the method described in the foregoing embodiment. Exemplarily, the blockchain node may be a server or a terminal. In the embodiment of the present application, the blockchain node 900 may also include an interface 903 for communicating with a user terminal provided with a user client. In addition, the server may also include a bus 904 for implementing internal communication within the server.

The embodiment of the present application also provides a user terminal. FIG. 10 is a schematic structural diagram of the user terminal provided in the embodiment of the present application. As shown in FIG. 10, the user terminal 1000 includes: one or more processors 1001; a memory 1002 for storing one or more programs; when the one or more programs are executed by the one or more processors , Enabling the one or more processors to implement the steps performed by the user terminal and the user client deployed on the user terminal in the method described in the foregoing embodiment. In the embodiment of the present application, the user terminal 1000 may further include an interface 1003 for communicating with blockchain nodes. In addition, the user client 1000 may also include a bus 1004 for implementing internal communication.

The present application provides a computer-readable storage medium, including a computer program, which when executed on a computer, causes the computer to execute the method described in any one of the foregoing embodiments.

This application provides a computer program, when the computer program is executed by a computer, it is used to execute the method described in any one of the foregoing embodiments.

In the above embodiments, it may be implemented in whole or in part by software, hardware, firmware or any combination thereof. When implemented by software, it can be implemented in the form of a computer program product in whole or in part. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on the computer, the processes or functions described in this application are generated in whole or in part. The computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices. The computer instructions may be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions may be transmitted from a website, computer, server, or data center. Transmission to another website, computer, server or data center via wired (such as coaxial cable, optical fiber, digital subscriber line) or wireless (such as infrared, wireless, microwave, etc.). The computer-readable storage medium may be any available medium that can be accessed by a computer or a data storage device such as a server or data center integrated with one or more available media. The usable medium may be a magnetic medium (for example, a floppy disk, a hard disk, and a magnetic tape), an optical medium (for example, a DVD), or a semiconductor medium (for example, a solid state disk).

Claims (38)

1. A method for confirming data rights based on a blockchain network, characterized in that the method includes:

   The first blockchain node in the blockchain network sends or receives communication information;

   The first blockchain node records the communication information in the ledger of the blockchain network;

   Wherein, the blockchain network includes a plurality of blockchain nodes, and the plurality of blockchain nodes includes: using nodes and providing nodes; the using nodes are used to send information to all users according to a service request carrying a user identifier. The providing node requests user credit data corresponding to the user identification; the providing node is configured to provide user credit data to the user node; the communication information includes: the first blockchain node and the plurality of At least one of the information between any other blockchain nodes in the blockchain node, and the information between the first blockchain node and the user client; wherein, the user client is used to The using node sends the service request carrying the user identifier, and/or the user client is used to confirm whether the providing node is allowed to provide the user credit data corresponding to the user identifier to the using node; The first blockchain node is a blockchain node among the plurality of blockchain nodes.
2. The method according to claim 1, wherein the sending or receiving of communication information by the first blockchain node in the blockchain network comprises:

   The first blockchain node sends the communication information to the second blockchain node; or,

   The first blockchain node receives the communication information sent by the second blockchain node; or,

   The first blockchain node sends the communication information to the user client; or,

   The first blockchain node receives the communication information sent by the user client;

   Wherein, the second block chain node is any other block chain node except the first block chain node among the plurality of block chain nodes.
3. The method according to claim 1 or 2, wherein the first blockchain node is the user node; and the user client is used to send all data carrying the user identifier to the user node. The business request;

   The sending or receiving of communication information by the first blockchain node in the blockchain network includes: the user node sending or receiving communication information, wherein the communication information specifically includes: the user node and the plurality of At least one of the information between other blockchain nodes in the blockchain node, and the information between the use node and the user client.
4. The method according to claim 1 or 2, wherein the first blockchain node is the providing node; the user client is used to confirm whether the providing node is allowed to provide the user node User credit data corresponding to the user ID;

   Sending or receiving communication information by the first blockchain node in the blockchain network includes: the providing node sending or receiving communication information, wherein the communication information specifically includes: the providing node and the plurality of At least one of information between other blockchain nodes in the blockchain node, and information between the providing node and the user client.
5. The method according to any one of claims 1 to 3, wherein the first blockchain node is the user node; and the user client is used to send to the user node the user identifier The service request; the first blockchain node in the blockchain network sends or receives communication information, including at least one of the following:

   Receiving, by the use node, the service request sent by the user client and carrying the user identifier;

   The use node sends a data transaction request to the providing node, the data transaction request is used to request to obtain user credit data corresponding to the user identification, and the user credit data is used by the use node to process the user Identified business request;

   The using node receives a data transaction response sent by the providing node, where the data transaction response includes user credit data corresponding to the user identifier.
6. The method according to any one of claims 1, 2 or 4, wherein the first blockchain node is the providing node; and the user client is used to confirm whether the providing node is allowed to send The use node provides user credit data corresponding to the user ID; the first blockchain node in the blockchain network sends or receives communication information, including at least one of the following:

   The providing node receives a data transaction request sent by the using node, the data transaction request is used to request to obtain user credit data corresponding to the user identification, and the user credit data is used by the using node to process the data carrying the Service request of user ID;

   Sending, by the providing node, a data authorization request to the user client, the data authorization request being used to request the user client to allow the user credit data corresponding to the user identification to be provided to the user node;

   The providing node receives a data authorization response sent by the user client, where the data authorization response is used to confirm whether the user credit data corresponding to the user identifier is allowed to be provided to the user node;

   The providing node sends a data transaction response to the using node, where the data transaction response includes user credit data corresponding to the user identifier.
7. The method according to claim 1 or 2, wherein the multiple blockchain nodes comprise: a proxy node; the proxy node is configured to receive a data transaction request sent by the user node, and the data transaction The request is used to request the user credit data corresponding to the user identification; and, confirm whether the use node has the access authority to the user credit data corresponding to the user identification; and, when confirming that the use node has the access authority, send Sending the data transaction request by the providing node; and receiving a data transaction response sent by the providing node, the data transaction response including user credit data corresponding to the user identifier;

   The first blockchain node is the proxy node; sending or receiving communication information by the first blockchain node in the blockchain network includes: sending or receiving communication information by the proxy node, wherein The communication information specifically includes: at least one of information between the agent node and the use node, and information between the agent node and the providing node.
8. The method according to any one of claims 1-6, wherein the blockchain network comprises: X channels; the blockchain nodes in the blockchain network respectively correspond to one of the X channels or Multiple channels; wherein the channel corresponding to the first blockchain node includes the i-th channel, and the channel corresponding to the second blockchain node in the blockchain network includes the i-th channel;

   The first blockchain node recording the communication information in the ledger of the blockchain network includes: the first blockchain node records the channel information of the i-th channel in the ledger corresponding to the i-th channel in;

   The channel information of the i-th channel includes: information transmitted between the first block chain node and the second block chain node through the i-th channel, and the first block chain node or the The second blockchain node sends information to the user client based on the information received from the i-th channel, and the first blockchain node passes through the i-th channel based on the information received from the user client Information sent to the second blockchain node, and at least one of the information sent by the second blockchain node to the first blockchain node through the i-th channel based on the information received from the user client Species

   Wherein, X is an integer greater than 0, and i is an integer greater than 0 and less than or equal to X.
9. The method according to claim 8, wherein the blockchain network includes M use nodes, the M use nodes respectively correspond to one of the X channels, and any use node communicates with the provider through its corresponding channel. Node transmission information;

   The first blockchain node is the corresponding channel among the M usage nodes as the jth usage node of the i-th channel, and the second blockchain node is the one that transmits information through the i-th channel and the jth usage node. Providing node; or, the first blockchain node is a providing node that transmits information through the i-th channel with the j-th user node corresponding to the i-th channel, and the second blockchain node is the j-th Use node

   Wherein, M is an integer greater than 0, and j is an integer greater than 0 and less than or equal to M.
10. The method according to claim 8, wherein the blockchain network includes M use nodes, the M use nodes respectively correspond to one of the X channels, and any use node communicates with the provider through its corresponding channel. Node transmission information;

    The multiple blockchain nodes include: a proxy node; the proxy node is configured to receive a data transaction request sent by the user node, the data transaction request is used to request user credit data corresponding to the user identifier; and , Confirm whether the using node has the access authority to the user credit data corresponding to the user identification; and, when confirming that the using node has the access authority, send the data transaction request to the providing node; and, receive The data transaction response sent by the providing node, where the data transaction response includes user credit data corresponding to the user identifier;

    The first blockchain node is the corresponding channel among the M usage nodes as the jth usage node of the i-th channel, and the second blockchain node is the one that transmits information with the jth usage node through the i-th channel Proxy node; or, the first blockchain node is a proxy node that transmits information through the i-th channel with the j-th user node corresponding to the i-th channel, and the second blockchain node is the j-th Use node; or, the first blockchain node is a proxy node that transmits information through the i-th channel with the j-th use node corresponding to the i-th channel, and the second blockchain node is the The first blockchain node transmits the information providing node through the i-th channel;

    Wherein, M is an integer greater than 0, and j is an integer greater than 0 and less than or equal to M.
11. The method according to claim 1, wherein the providing node is an operator server; and the user credit data is operator credit data corresponding to the user identification.
12. A method for confirming data rights based on a blockchain network, characterized in that the method includes:

    The user client receives a data authorization request sent by a providing node that carries a user ID corresponding to the user client, and the data authorization request is used to request permission to use the node to use the user credit corresponding to the user ID provided by the providing node data;

    The user client outputs prompt information through its own output device, the prompt information is used to request confirmation whether the user node is allowed to use the user credit data corresponding to the user identifier provided by the providing node;

    Wherein, the use node and the provision node are blockchain nodes in a blockchain network, and the use node is used to request the user credit data corresponding to the user identifier from the provision node.
13. The method according to claim 12, wherein:

    The receiving, by the user client, a data authorization request sent by a providing node and carrying a user identifier corresponding to the user client includes: the user client receiving at least two data authorization requests sent by at least two providing nodes, At least two data authorization requests correspond to the at least two providing nodes respectively, and any data authorization request is used to request that the user node is allowed to use the user credit corresponding to the user identifier provided by the providing node that sent the data authorization request data;

    Wherein, the use node is used to request the user credit data corresponding to the user identification from the at least two providing nodes, and the user credit data corresponding to the user identification includes: the user credit data provided by the at least two providing nodes respectively User credit data corresponding to the user identifier;

    The prompt information is used to request confirmation whether the user node is allowed to use the user credit data corresponding to the user identifier provided by the at least two providing nodes respectively.
14. The method of claim 13, wherein the method further comprises:

    The user client receives input information through its own input device, the input information is used to confirm whether the user node is allowed to use the user credit data corresponding to the user identifier provided by the at least two providing nodes;

    When the input information indicates that the user credit data corresponding to the user identification provided by the at least two providing nodes is allowed to be used by the user node, the user client sends data authorization responses to the providing node respectively, and The data authorization response is used to confirm that the user node is allowed to use the user credit data corresponding to the user identification provided by the providing node that receives the data authorization response.
15. The method according to claim 12, wherein the data authorization request is used to request permission to allow the user node to use the user identification provided by the providing node when receiving the service request of the first service. User credit data.
16. A data right confirmation system based on a blockchain network, characterized in that the system includes: a plurality of blockchain nodes; the plurality of blockchain nodes includes: a use node and a provision node; wherein the use A node, configured to request user credit data corresponding to the user identification from the providing node according to a service request carrying a user identification; the providing node is configured to provide user credit data;

    At least one of the multiple blockchain nodes is also used to send or receive communication information, and record the communication information in the ledger of the blockchain network; wherein the communication information includes: At least one of the information between the blockchain nodes and the information between the blockchain node and the user client; wherein the user client is used to send to the user node information that carries the user identifier The service request, and/or, the user client is used to confirm whether the providing node is allowed to provide the user credit data corresponding to the user identifier to the using node.
17. The system according to claim 16, wherein the at least one blockchain node is a user node; the communication information specifically includes: the user node and other blocks in the plurality of blockchain nodes At least one of the information between the chain nodes, and the information between the use node and the user client; the user client is used to send the user identification to the use node Business request.
18. The system according to claim 16 or 17, wherein the communication information specifically includes at least one of the following:

    The service request that carries the user identifier and is sent by the user client received by the user node;

    The data transaction request sent by the using node to the providing node, where the data transaction request is used to request to obtain user credit data corresponding to the user identification, and the user credit data is used by the using node to process the data carrying the Service request of user ID;

    The data transaction response received by the using node from the providing node, where the data transaction response includes user credit data corresponding to the user identification.
19. The system according to claim 16 or 17, wherein the at least one blockchain node is a providing node; the communication information specifically includes: the providing node and other of the plurality of blockchain nodes Information between blockchain nodes, and at least one of the information between the providing node and the user client; the user client is used to confirm whether the providing node is allowed to provide the user node User credit data corresponding to the user identification.
20. The system according to claim 16 or 19, wherein the communication information specifically includes at least one of the following:

    The data transaction request received by the providing node from the user node, the data transaction request is used to request to obtain user credit data corresponding to the user identification, and the user credit data corresponding to the user identification is used for the user node Processing the service request carrying the user identifier;

    A data authorization request sent by the providing node to the user client, where the data authorization request is used to request that the user node be allowed to use the user credit data corresponding to the user identifier provided by the providing node;

    A data authorization response received by the providing node from the user client, where the data authorization response includes user credit data corresponding to the user identifier;

    The data transaction response sent by the providing node to the using node, where the data transaction response includes user credit data corresponding to the user identifier.
21. The system according to any one of claims 16-20, wherein the multiple blockchain nodes further comprise: a proxy node;

    The proxy node is configured to receive a data transaction request sent by the using node, the data transaction request is used to request user credit data corresponding to the user identification; and to confirm whether the using node has the user identification corresponding And, when confirming that the user node has the access right, send the data transaction request to the providing node; and receive the data transaction response sent by the providing node, the data transaction The response includes user credit data corresponding to the user identification;

    The communication information specifically includes: at least one of information between the proxy node and the use node, and information between the proxy node and the providing node.
22. The system according to any one of claims 16-20, wherein the blockchain network comprises: X channels; the plurality of blockchain nodes respectively correspond to one or more of the X channels; among them,

    The number of the use nodes is M, the M use nodes respectively correspond to one of the X channels, and any use node transmits information to the providing node through its corresponding channel;

    The at least one blockchain node is specifically configured to send or receive channel information of the i-th channel, and record the channel information of the i-th channel in a ledger corresponding to the i-th channel;

    The channel information of the i-th channel includes at least one of the following:

    The corresponding channel is the information between the use node of the i-th channel and the first user client, and the first user client is configured to send the service request carrying the user identifier to the use node;

    The corresponding channel is the information between the using node and the providing node of the i-th channel;

    The providing node sends the information to the second user client based on the information received from the i-th channel and the information received from the second user client; the second user client is used to confirm whether the providing node is allowed to use The node provides user credit data corresponding to the user identifier;

    Wherein, X is an integer greater than 0, M is an integer greater than 0, and i is an integer greater than 0 and less than or equal to X.
23. The system according to claim 16, wherein the providing node is further configured to send a data authorization request to the user client, and the data authorization request is used to request permission for the using node to use the providing node User credit data corresponding to the provided user identification.
24. The system according to claim 16, wherein the providing node is an operator server; and the user credit data is operator credit data corresponding to the user identification.
25. A data right confirmation device based on a blockchain network, characterized in that it is applied to the first blockchain node in the blockchain network, and the device includes:

    The transceiver module is used to send or receive communication information;

    Processing module, used to record the communication information in the ledger of the blockchain network;

    Wherein, the blockchain network includes a plurality of blockchain nodes, and the plurality of blockchain nodes includes: using nodes and providing nodes; the using nodes are used to send information to all users according to a service request carrying a user identifier. The providing node requests user credit data corresponding to the user identification; the providing node is configured to provide user credit data to the user node; the communication information includes: the first blockchain node and the plurality of At least one of the information between any other blockchain nodes in the blockchain node, and the information between the first blockchain node and the user client; wherein, the user client is used to The using node sends the service request carrying the user identifier, and/or the user client is used to confirm whether the providing node is allowed to provide the user credit data corresponding to the user identifier to the using node; The first blockchain node is a blockchain node among the plurality of blockchain nodes.
26. The device according to claim 25, wherein the transceiver module is specifically configured to:

    Send the communication information to the second blockchain node; or,

    Receiving the communication information sent by the second blockchain node; or,

    Sending the communication information to the user client; or,

    Receiving the communication information sent by the user client;

    Wherein, the second block chain node is any other block chain node except the first block chain node among the plurality of block chain nodes.
27. The device according to claim 25 or 26, wherein the first blockchain node is the user node; and the user client is used to send all data carrying the user identifier to the user node. The business request;

    The transceiver module is specifically configured to send or receive communication information, where the communication information specifically includes: information between the use node and other blockchain nodes among the plurality of blockchain nodes, and, At least one of the information between the use node and the user client.
28. The device according to claim 25 or 26, wherein the first blockchain node is the provider node; the user client is used to confirm whether the provider node is allowed to provide the user node User credit data corresponding to the user identifier;

    The transceiver module is specifically configured to send or receive communication information, where the communication information specifically includes: information between the providing node and other blockchain nodes among the plurality of blockchain nodes, and, At least one of the information between the providing node and the user client.
29. The device according to any one of claims 25-27, wherein the first blockchain node is the user node; the user client is used to send to the user node the user identifier The service request; the transceiver module is specifically used for at least one of the following:

    Receiving the service request carrying the user identifier sent by the user client;

    Send a data transaction request to the providing node, the data transaction request is used to request to obtain the user credit data corresponding to the user ID, and the user credit data is used by the user node to process the service request carrying the user ID ；

    Receive a data transaction response sent by the providing node, where the data transaction response includes user credit data corresponding to the user identification.
30. The device according to any one of claims 25, 26 or 28, wherein the first blockchain node is the providing node; and the user client is used to confirm whether the providing node is allowed to send The user node provides user credit data corresponding to the user identifier; the transceiver module is specifically used for at least one of the following:

    Receive a data transaction request sent by the use node, the data transaction request is used to request to obtain user credit data corresponding to the user identification, and the user credit data is used by the use node to process the service carrying the user identification request;

    Sending a data authorization request to the user client, where the data authorization request is used to request the user client to allow the user client to provide the user credit data corresponding to the user identifier;

    Receiving a data authorization response sent by the user client, where the data authorization response is used to confirm whether to allow the user credit data corresponding to the user identification to be provided to the user node;

    Send a data transaction response to the use node, where the data transaction response includes user credit data corresponding to the user identification.
31. The device according to claim 25 or 26, wherein the multiple blockchain nodes comprise: a proxy node; the proxy node is configured to receive a data transaction request sent by the user node, and the data transaction The request is used for requesting the user credit data corresponding to the user identification; and, confirming whether the use node has the access authority to the user credit data corresponding to the user identification; and, when confirming that the use node has the access authority, send Sending the data transaction request by the providing node; and receiving a data transaction response sent by the providing node, the data transaction response including user credit data corresponding to the user identifier;

    The first blockchain node is the proxy node; the transceiver module is specifically used to send or receive communication information, where the communication information specifically includes: information between the proxy node and the user node , At least one of the information between the agent node and the providing node.
32. The device according to any one of claims 25-30, wherein the blockchain network comprises: X channels; the blockchain nodes in the blockchain network respectively correspond to one of the X channels or Multiple channels; wherein the channel corresponding to the first blockchain node includes the i-th channel, and the channel corresponding to the second blockchain node in the blockchain network includes the i-th channel;

    The transceiver module is specifically configured to record the channel information of the i-th channel in the ledger corresponding to the i-th channel;

    The channel information of the i-th channel includes: information transmitted between the first block chain node and the second block chain node through the i-th channel, and the first block chain node or the The second blockchain node sends information to the user client based on the information received from the i-th channel, and the first blockchain node passes through the i-th channel based on the information received from the user client Information sent to the second blockchain node, and at least one of the information sent by the second blockchain node to the first blockchain node through the i-th channel based on the information received from the user client Species

    Wherein, X is an integer greater than 0, and i is an integer greater than 0 and less than or equal to X.
33. The device according to claim 32, wherein the blockchain network comprises M usage nodes, and the M usage nodes respectively correspond to one of the X channels, and any usage node communicates with each other through its corresponding channel. Node transmission information;

    The first blockchain node is the corresponding channel among the M usage nodes as the jth usage node of the i-th channel, and the second blockchain node is the one that transmits information through the i-th channel and the jth usage node. Providing node; or, the first blockchain node is a providing node that transmits information through the i-th channel with the j-th user node corresponding to the i-th channel, and the second blockchain node is the j-th Use node

    Wherein, M is an integer greater than 0, and j is an integer greater than 0 and less than or equal to M.
34. The device according to claim 32, wherein the blockchain network comprises M usage nodes, and the M usage nodes respectively correspond to one of the X channels, and any usage node communicates with each other through its corresponding channel. Node transmission information;

    The multiple blockchain nodes include: a proxy node; the proxy node is configured to receive a data transaction request sent by the user node, the data transaction request is used to request user credit data corresponding to the user identifier; and , Confirm whether the using node has the access authority to the user credit data corresponding to the user identification; and, when confirming that the using node has the access authority, send the data transaction request to the providing node; and, receive The data transaction response sent by the providing node, where the data transaction response includes user credit data corresponding to the user identifier;

    The first blockchain node is the corresponding channel among the M usage nodes as the jth usage node of the i-th channel, and the second blockchain node is the one that transmits information with the jth usage node through the i-th channel Proxy node; or, the first blockchain node is a proxy node that transmits information through the i-th channel with the j-th user node corresponding to the i-th channel, and the second blockchain node is the j-th Use node; or, the first blockchain node is a proxy node that transmits information through the i-th channel with the j-th use node corresponding to the i-th channel, and the second blockchain node is the The first blockchain node transmits the information providing node through the i-th channel;

    Wherein, M is an integer greater than 0, and j is an integer greater than 0 and less than or equal to M.
35. The apparatus according to claim 25, wherein the providing node is an operator server; and the user credit data is operator credit data corresponding to the user identification.
36. A data right confirmation device based on a blockchain network, characterized in that it is applied to a user client, and the device includes:

    The transceiver module is configured to receive a data authorization request carrying a user identification corresponding to the user client sent by a providing node, and the data authorization request is used to request permission to use the node to use the user identification provided by the providing node. User credit data;

    An output module, configured to output prompt information through an output device, the prompt information being used to request confirmation whether the user node is allowed to use the user credit data corresponding to the user identifier provided by the providing node;

    Wherein, the use node and the provision node are blockchain nodes in a blockchain network, and the use node is used to request the user credit data corresponding to the user identifier from the provision node.
37. The device according to claim 36, wherein:

    The transceiver module is specifically configured to receive at least two data authorization requests sent by at least two providing nodes, where the at least two data authorization requests correspond to the at least two providing nodes respectively, and any data authorization request is used Requesting permission for the user node to use the user credit data corresponding to the user identifier provided by the providing node that sent the data authorization request;

    Wherein, the use node is used to request the user credit data corresponding to the user identification from the at least two providing nodes, and the user credit data corresponding to the user identification includes: the user credit data provided by the at least two providing nodes respectively User credit data corresponding to the user identifier;

    The prompt information is used to request confirmation whether the user node is allowed to use the user credit data corresponding to the user identifier provided by the at least two providing nodes respectively.
38. The device according to claim 37, wherein the device further comprises:

    An input module, the input module being configured to receive input information through an input device, the input information being used to confirm whether the user node is allowed to use the user credit data corresponding to the user identifier provided by the at least two providing nodes;

    The transceiver module is further configured to send data authorization to the provider node when the input information indicates that the user node is allowed to use the user credit data corresponding to the user identifier provided by the at least two provider nodes In response, any of the data authorization responses is used to confirm that the user node is allowed to use the user credit data corresponding to the user identifier provided by the providing node that receives the data authorization response.

Images