A data management and cross-platform scheduling method and system based on a consortium chain

Abstract

The application provides a kind of data management and cross-platform scheduling method and system based on alliance chain, comprising deploying alliance chain, and sending smart contract to alliance chain through transaction;Data called party calls data traceability contract to upload extracted abstract data to alliance chain;Data user calls data retrieval contract to access data on alliance chain, in data transmission process, data called party encrypts data for the first time;Data relay server performs second encryption;After receiving re-encrypted ciphertext data, data accesser decrypts to obtain plaintext data using its own private key.The application combines alliance chain and access control technology, introduces data relay server, realizes decentralized management and scheduling of data, effectively alleviates current data circulation barriers and data island problems;And anonymous access of data accesser to data provider can be realized;The application cooperatively manages data in an on-chain and off-chain manner.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of data processing, and in particular to a data management and cross-platform scheduling method and system based on a consortium chain. BACKGROUND

[0002] With the development of mobile Internet technology, data has grown massively. Usually, data is stored in Internet service providers (such as social platforms, shopping platforms, etc.). However, for the sake of security interests, Internet service providers are often unwilling to share the user data they own, and the phenomenon of Internet data islands is increasingly prominent. However, data is difficult to release its value in a single institution. As a new type of production factor, data can greatly stimulate its use value and exchange value in the process of circulation, use and sharing, creating a large number of new businesses for various industries and promoting the development of digital economy.

[0003] Existing data management and scheduling platforms are mainly centralized, and it is difficult to establish trust with data takers, thus causing barriers to data circulation among data takers and making it difficult to maximize the value of data. On the one hand, the barriers to circulation and the phenomenon of data islands are increasingly prominent. Major Internet service providers are difficult to appoint a central management institution to manage data uniformly; on the other hand, users are increasingly attaching importance to privacy. The mode of directly accessing data to data takers is difficult to meet the demand for anonymous access, i.e. the privacy of data accessers is unwilling to be exposed to data takers. SUMMARY

[0004] In view of the deficiencies of the prior art, the present application provides a data management and cross-platform scheduling method and system based on a consortium chain. The present application combines consortium chain and access control technology, introduces a data relay server, realizes the decentralized management and scheduling of data, and enables anonymous access of data accessers to data providers.

[0005] The technical solution of the present application is: a data management and cross-platform scheduling method based on a consortium chain, comprising the following steps:

[0006] S1), deploying a consortium chain and sending a smart contract to the consortium chain through a transaction;

[0007] S2), a data taker calling a data tracing contract to upload the extracted abstract data to the consortium chain;

[0008] S3), a data user calling a data retrieval contract to retrieve data on the consortium chain, and when the data meeting the conditions is retrieved, a data accesser calls an access control contract to perform identity verification, the access control contract authorizes the data accesser according to predetermined rules and returns an authorization credential C to the data accesser;

[0009] S4), after the data visitor obtains the authorized credential C, the data visitor sends a data access request to the data relay server, and the data relay server asks the data callee for data instead of the data visitor;

[0010] S5), the data callee encrypts the data to generate ciphertext data, and returns the ciphertext data and the conversion key to the data relay server;

[0011] S6), the data relay server performs ciphertext conversion to generate re-encrypted ciphertext data and sends it to the data visitor;

[0012] S7), after the data visitor receives the re-encrypted ciphertext data, the data visitor decrypts the plaintext data using its own private key.

[0013] As preferred, in step S1), the smart contract includes a data traceability contract, a data retrieval contract and an access control contract, and the data access operation is written into the alliance chain immutable ledger by calling the function of the smart contract to ensure the data access operation.

[0014] As preferred, in step S1), the data traceability contract is used to store the abstract data DataObject of the data on the chain, and users can search and view detailed information about a single transaction, including its status, timestamp, amount and related fees.

[0015] As preferred, in step S1), the data retrieval contract is used to retrieve and present real-time data from the alliance chain network, including the latest transactions, wallet balances and smart contract interactions; during data sharing, the data retrieval contract is used to retrieve the abstract data information uploaded by the data callee on the chain, and the retrieved data is processed and indexed.

[0016] As preferred, in step S1), the access control contract is used to ensure the legitimacy of the data user and to ensure that the shared data is accessed safely, and the access control contract is also used to manage the addresses of different data visitors, judge the access rights of the users according to the addresses, and support the modification, revocation and change operation of the address rights, and the change operation of the rights is recorded on the alliance chain ledger.

[0017] As preferred, in step S2), the abstract data DataObject extracted by the data callee is represented as:

[0018] DataObject={DataID, DataContent, Owner, Timestamp, Address};

[0019] In the formula, DataID represents the number of data; DataContent represents the content description of data; Owner represents the data owner; Timestamp represents the timestamp of data; and Address represents the address of data access.

[0020] As preferred, in step S2), when there is new data, the data invoker updates the new data to the alliance chain according to the same steps.

[0021] As preferred, in step S5), the data invoker encrypts the data by using the private key to generate ciphertext data and a conversion key, that is,

[0022] CT←Enc(M,SK);

[0023] RK←Setup(λ);

[0024] wherein CT is ciphertext data; M is data to be encrypted; SK is the private key of the data invoker; Enc represents an encryption algorithm; Setup represents an initialization algorithm; RK represents a conversion key; and λ is a random security parameter.

[0025] As preferred, in step S6), the data relay server generates a re-encryption ciphertext expression as follows:

[0026] RCT←ReEnc(RK,PK,CT);

[0027] wherein RCT represents a re-encryption ciphertext; ReEnc represents a re-encryption algorithm; RK represents a conversion key; PK represents the public key of the data access user; and CT is original ciphertext data.

[0028] As preferred, in step S7), the data access user uses the private key to decrypt to obtain a plaintext data expression as follows:

[0029] M←Dec(RCT,SK);

[0030] wherein M is plaintext data; Dec represents a decryption algorithm; RCT represents the re-encryption ciphertext of the data relay server; and SK is the private key of the data access user.

[0031] As preferred, the present application also provides a data management and cross-platform scheduling system based on an alliance chain, comprising:

[0032] a data providing client, configured to call a data traceability contract by a data invoker to upload extracted abstract data to an alliance chain;

[0033] an alliance chain platform, configured to run an intelligent contract, and execute corresponding business operations in response to a request of a data user by the intelligent contract;

[0034] a data access client, configured to invoke a data retrieval contract by a data user to retrieve data on a consortium chain platform, and when data meeting a condition is retrieved, the data access client invokes an access control contract to perform identity authentication, and the access control contract authorizes the data access client according to a predetermined rule and returns an authorization credential C to the data access client;

[0035] a data relay server, configured to verify an access request of a data access request, and after verification, the data relay server replaces the data access client to request data from a data callee, the data callee encrypts the data to generate ciphertext data, and returns the ciphertext data and a conversion key to the data relay server, the data relay server performs ciphertext conversion to generate re-encrypted ciphertext data, and sends the re-encrypted ciphertext data to the data access client, and the data access client decrypts the re-encrypted ciphertext data using a private key of the data access client to obtain plaintext data.

[0036] Preferably, the smart contract includes a data traceability contract, a data retrieval contract and an access control contract, and a function of the smart contract is invoked to perform data access, so as to ensure that data access operations are written into a consortium chain immutable ledger.

[0037] Preferably, the abstract data DataObject extracted by the data callee is represented as:

[0038] DataObject={DataID,DataContent,Owner,Timestamp,Address};

[0039] In the formula, DataID represents a data number, DataContent represents a data content description, Owner represents a data owner, TimeStamp represents a data timestamp, and Address represents a data access address.

[0040] Preferably, the data callee encrypts the data using a private key to generate ciphertext data and a conversion key, that is:

[0041] CT←Enc(M,SK);

[0042] RKtSetup(h):

[0043] In the formula, CT is ciphertext data, M is data to be encrypted, SK is a private key of the data callee, Enc represents an encryption algorithm, Setup represents an initialization algorithm, RK represents a conversion key, and λ is a random security parameter.

[0044] Preferably, the data relay server generates a re-encrypted ciphertext expression as:

[0045] RCT←ReEnc(RK, PK, CT);

[0046] In the formula, RCT represents re-encryption ciphertext; ReEnc represents a re-encryption algorithm; RK represents a conversion key; PK represents a public key of a data visitor, and CT is original ciphertext data.

[0047] As preferred, the expression for the data visitor to decrypt to obtain plaintext data is as follows:

[0048] M←Dec(RCT, SK);

[0049] In the formula, M represents plaintext data; Dec represents a decryption algorithm; RCT represents re-encryption ciphertext of a data relay server; and SK is a private key of the data visitor.

[0050] The present application has the following beneficial effects:

[0051] 1. The present application combines alliance chain and access control technology, introduces a data relay server, realizes decentralized management and scheduling of data, effectively alleviates the current data flow barriers and data island problems, enables anonymous access of data visitors to data providers, does not depend on a central institution, is maintained by all participants, and is automatically executed according to the established rules, realizes decentralized management of data and anonymous access of data users through alliance chain and proxy re-encryption, and does not have a single point of failure.

[0052] 2. The present application cooperatively manages data in an on-chain and off-chain manner, not only saves on-chain storage resources, but also protects data privacy, abstracts data owned by a data callee into abstract data, and uniformly stores the abstract data on a decentralized data ledger.

[0053] 3. The data ledger of the present application is constructed by a block chain, data management and scheduling are executed by a smart contract, and data transmission is replaced by a data relay server to access data, and the data is encrypted and converted by proxy re-encryption. BRIEF DESCRIPTION OF DRAWINGS

[0054] Figure 1 Fig. 1 is a schematic diagram of the framework of the present application;

[0055] Figure 2 Fig. 2 is a schematic diagram of the encryption process in the data transmission process of the present application. DETAILED DESCRIPTION

[0056] The specific embodiments of the present application will be further described below in conjunction with the accompanying drawings:

[0057] Example 1

[0058] As Figure 1 and2 As shown, the embodiment provides a data management and cross-platform scheduling method based on a consortium chain, including the following steps:

[0059] S1), deploy a consortium chain, and send a smart contract to the consortium chain through a transaction;

[0060] In the embodiment, the smart contract includes a data traceability contract, a data retrieval contract, and an access control contract. The functions of the smart contract are called to perform data access to ensure that data access operations are written to the consortium chain immutable ledger. The data traceability contract is used to store the abstract data DataObject of the data on the chain. Users can search and view detailed information about a single transaction, including its status, timestamp, amount, and related fees. The data retrieval contract is used to retrieve and present real-time data from the consortium chain network, including the latest transactions, wallet balances, and smart contract interactions. During data sharing, the data retrieval contract is used to retrieve abstract data information uploaded by the data requester on the chain. The retrieved data is processed and indexed. The access control contract is used to ensure the legitimacy of data users and to ensure that shared data is accessed securely. The access control contract is also used to manage the addresses of different data accessers. According to the address, the access rights of the user are determined. The address rights can be modified, revoked, and changed. The change operation of the rights is recorded on the consortium chain ledger.

[0061] S2), the data requester calls the data traceability contract to upload the extracted abstract data to the consortium chain;

[0062] In the embodiment, the ETL tool is used to extract abstract data. The abstract data DataObject extracted by the data requester is represented as:

[0063] DataObject = {DataID, DataContent, Owner, Timestamp, Address};

[0064] In the formula, DataID represents the number of data; DataCOntent represents the content description of the data; Owner represents the data owner; TimeStamp represents the timestamp of the data, and Address represents the address of data access.

[0065] Moreover, in the embodiment, when there is new data, the data requester updates the new data to the consortium chain according to the same steps.

[0066] S3), the data user calls the data retrieval contract to retrieve the data on the alliance chain, when the data meeting the condition is retrieved, the data user calls the access control contract to verify the identity, the access control contract authorizes the data user according to the predetermined rules and returns the authorization credential C to the data user;

[0067] S4), the data user obtains the authorization credential C and sends a data access request to the data relay server, and the data relay server obtains the data from the data callee on behalf of the data user;

[0068] S5), the data callee encrypts the data to generate ciphertext data, and returns the ciphertext data and the conversion key to the data relay server;

[0069] The data callee encrypts the data using the private key to generate ciphertext data and generates a conversion key, that is:

[0070] CT <- Enc (M, SK) ;

[0071] RK <- Setup (lambda) ;

[0072] Wherein, CT is ciphertext data; M is the data to be encrypted; SK is the private key of the data callee; Enc represents the encryption algorithm; Setup represents the initialization algorithm; RK represents the conversion key; lambda is a random security parameter.

[0073] S6), the data relay server performs ciphertext conversion to generate re-encrypted ciphertext data and sends it to the data user;

[0074] The expression of the re-encrypted ciphertext generated by the data relay server is:

[0075] RCT <- ReEnc (RK, PK, CT) ;

[0076] In the formula, RCT represents the re-encrypted ciphertext; ReEnc represents the re-encryption algorithm; RK represents the conversion key; PK represents the public key of the data user, and CT is the original ciphertext data.

[0077] S7), the data user receives the re-encrypted ciphertext data and decrypts it using the private key to obtain the plaintext data.

[0078] The expression of the data user using the private key to decrypt the plaintext data is:

[0079] M <- Dec (RCT, SK) ;

[0080] Wherein, M is the plaintext data; Dec represents the decryption algorithm; RCT represents the re-encrypted ciphertext of the data relay server; SK is the private key of the data user.

[0081] Embodiment 2

[0082] As Figure 1 shown, the embodiment provides a data management and cross-platform scheduling system based on a consortium chain, comprising:

[0083] A data providing client is configured to upload abstract data extracted by a data callee to the consortium chain by calling a data traceability contract.

[0084] In the embodiment, the data providing client has a visual interface and multiple data interfaces for the data callee to upload updated data.

[0085] The abstract data DataObject extracted by the data callee is represented as:

[0086] DataObject = {DataID, DataContent, Owner, Timestamp, Address);

[0087] In the formula, DataID represents the number of data; DataContent represents the content description of data; Owner represents the data owner; TimeStamp represents the timestamp of data, and Address represents the address of data access.

[0088] A consortium chain platform is configured to run a smart contract, and the smart contract is configured to execute corresponding business operations in response to a request of a data user.

[0089] In the embodiment, the smart contract includes a data traceability contract, a data retrieval contract, and an access control contract, and the access to data is performed by calling the functions of the smart contract to ensure that the data access operations are written into the consortium chain non-tamperable ledger.

[0090] The data traceability contract is configured to store the abstract data DataObject of data on the chain, and a user can search and view detailed information about a single transaction, including its status, timestamp, amount, and related fees. The data retrieval contract is configured to retrieve and present real-time data from the consortium chain network, including the latest transactions, wallet balances, and smart contract interactions. In the process of data sharing, the data retrieval contract is configured to retrieve the abstract data information uploaded by the data callee on the chain, and the retrieved data is processed and indexed. The access control contract is configured to ensure the legitimacy of the data user and to ensure that the shared data is accessed safely. The access control contract is also configured to manage the addresses of different data accessers, to judge the access rights of the users according to the addresses, and to support the modification, revocation, and change operations of the address rights, and the change operations of the rights are recorded on the consortium chain ledger.

[0091] The data access client is used for a data user to call a data retrieval contract to retrieve data on the alliance chain platform, and when data meeting the condition is retrieved, the data access client calls an access control contract to perform authentication, and the access control contract authorizes the data access client according to a predetermined rule and returns an authorization credential C to the data access client.

[0092] Correspondingly, the data access client also has a visual interface to facilitate the data access client to access.

[0093] The data relay server is used for verifying an access request of the data access request, and after the verification is passed, the data relay server replaces the data access client to ask the data callee for data; the data callee encrypts the data to generate ciphertext data, and returns the ciphertext data and a conversion key to the data relay server, wherein the data callee encrypts the data by using a private key to generate the ciphertext data and a conversion key, that is,

[0094] CT <- Enc (M, SK) ;

[0095] RK <- Setup (lambda) ;

[0096] CT is the ciphertext data; M is the data to be encrypted; SK is the private key of the data callee; Enc represents an encryption algorithm; Setup represents initialization; RK represents the conversion key; and lambda is a random security parameter.

[0097] The data relay server performs ciphertext conversion to generate re-encryption ciphertext data, and sends the re-encryption ciphertext data to the data access client;

[0098] The expression of the re-encryption ciphertext generated by the data relay server is:

[0099] RCT <- ReEnc (RK, PK, CT) ;

[0100] RCT represents the re-encryption ciphertext; ReEnc represents a re-encryption algorithm; RK represents the conversion key; PK represents the public key of the data access client; and CT is the original ciphertext data.

[0101] After receiving the re-encryption ciphertext data, the data access client decrypts the re-encryption ciphertext data by using the private key of the data access client to obtain plaintext data.

[0102] The expression of the data access client decrypting the re-encryption ciphertext data by using the private key of the data access client to obtain plaintext data is:

[0103] M <- Dec (RCT, SK) ;

[0104] M is the plaintext data; Dec represents a decryption algorithm; RCT represents the re-encryption ciphertext of the data relay server; and SK is the private key of the data access client.

[0105] The encryption process in the data transmission can be seen from Figure 2 as shown.

[0106] The above embodiments and descriptions in the specification are only to illustrate the principles and the best mode of the present application, and various changes and improvements can be made without departing from the spirit and scope of the present application, and all these changes and improvements fall within the scope of the present application.

Claims

1.A method for data management and cross-platform scheduling based on a consortium chain, characterized in that, The method comprises the following steps: S1), deploying a consortium chain, and sending a smart contract to the consortium chain through a transaction; S2), the data callee calls the data traceability contract to upload the extracted abstract data to the consortium chain; S3), the data user calls the data retrieval contract to retrieve the data on the consortium chain, and when the data meeting the condition is retrieved, the data user calls the access control contract for identity authentication, the access control contract authorizes the data user according to the predetermined rules and returns an authorization credential C to the data user; S4), after obtaining the authorization credential C, the data user sends a data access request to the data relay server, and the data relay server obtains the data from the data callee on behalf of the data user; S5), the data callee encrypts the data to generate ciphertext data, and returns the ciphertext data and a conversion key to the data relay server; S6), the data relay server performs ciphertext conversion to generate re-encrypted ciphertext data and sends it to the data user; S7), after receiving the re-encrypted ciphertext data, the data user decrypts it using its own private key to obtain plaintext data. 2.The data management and cross-platform scheduling method based on the alliance chain according to claim 1, characterized in that: In step S1), the smart contract comprises a data traceability contract, a data retrieval contract and an access control contract, and the data access operation is written into the consortium chain immutable ledger by calling the function of the smart contract to ensure that the data access operation is written into the consortium chain immutable ledger. 3.The data management and cross-platform scheduling method based on the alliance chain according to claim 2, characterized in that: In step S1), the data traceability contract is used to store the abstract data DataObject of the data on the chain; The data retrieval contract is used to retrieve and present real-time data from the consortium chain network; in the data sharing process, the data retrieval contract is used to retrieve the abstract data information uploaded by the data callee on the chain, and the retrieved data is processed and indexed; The access control contract is used to ensure the legitimacy of the data user and ensure that the shared data is accessed safely, and the access control contract is also used to manage the addresses of different data users, judge the access rights of the users according to the addresses, and support the modification, revocation and change operation of the address rights, and the change operation of the rights is recorded on the consortium chain ledger. 4.The data management and cross-platform scheduling method based on the alliance chain according to claim 3, characterized in that: In step S2), the abstract data DataObject extracted by the data callee is represented as: DataObject={DataID,DataContent,Owner,Timestamp,Addres}; In the formula, DataID represents the number of data; DataContent represents the content description of data; Owner represents the data owner; Timestamp represents the timestamp of data, and Address represents the address of data access. 5.The data management and cross-platform scheduling method based on the alliance chain according to claim 1, characterized in that: In step S5), the data callee encrypts the data using a private key to generate ciphertext data and a conversion key, that is: CT←Enc(M,SK); RK←Setup(λ); Wherein, CT is ciphertext data; M is data to be encrypted; SK is the private key of the data callee; Enc represents an encryption algorithm; Setup represents an initialization algorithm; RK represents a conversion key; and λ is a random security parameter. 6.The data management and cross-platform scheduling method based on the alliance chain according to claim 5, characterized in that: In step S6), the data relay server generates an expression of re-encrypted ciphertext as follows: RCT←ReEnc(RK, PK, CT); where RCT represents re-encrypted ciphertext; ReEnc represents a re-encryption algorithm; RK represents a conversion key; PK represents a public key of a data accessor, and CT is original ciphertext data. 7.The data management and cross-platform scheduling method based on the alliance chain according to claim 6, characterized in that: In step S7), the data accessor uses a private key of the data accessor to decrypt to obtain plaintext data, and an expression is as follows: M←Dec(RCT, SK); where M is plaintext data; Dec represents a decryption algorithm; RCT represents re-encrypted ciphertext of the data relay server; and SK is a private key of the data accessor. 8.A data management and cross-platform scheduling system based on a consortium chain, characterized in that, The system implements data management and scheduling through the method of any one of claims 1-7, and the system comprises: a data providing client configured to enable a data callee to call a data traceability contract to upload abstract data extracted by the data callee to a consortium chain; a consortium chain platform configured to run an intelligent contract, and the intelligent contract is configured to execute a corresponding business operation in response to a request of a data user; a data accessing client configured to enable the data user to call a data retrieval contract to retrieve data on the consortium chain platform, and when data meeting a condition is retrieved, the data accessor calls an access control contract to perform identity authentication, the access control contract is configured to authorize the data accessor according to a predetermined rule and return an authorization credential C to the data accessor; a data relay server configured to verify an access request of a data access request, and after the verification is passed, the data relay server is configured to request data from a data callee on behalf of the data accessor; the data callee is configured to encrypt the data to generate ciphertext data, and return the ciphertext data and a conversion key to the data relay server; the data relay server is configured to execute ciphertext conversion to generate re-encrypted ciphertext data, and send the re-encrypted ciphertext data to the data accessor; and the data accessor is configured to use a private key of the data accessor to decrypt to obtain plaintext data after receiving the re-encrypted ciphertext data. 9.The data management and cross-platform scheduling system based on the alliance chain of claim 8, wherein, The intelligent contract running on the consortium chain platform comprises a data traceability contract, a data retrieval contract and an access control contract, and data access is performed by calling a function of the intelligent contract to ensure that the data access operation is written into a consortium chain tamper-proof ledger. 10.The data management and cross-platform scheduling system based on the alliance chain according to claim 8, wherein, The data callee encrypts the data using a private key to generate ciphertext data and a conversion key, that is: CT←Enc(M, SK); RK←Setup(λ); where CT is ciphertext data; M is data to be encrypted; SK is a private key of the data callee; Enc represents an encryption algorithm; Setup represents an initialization algorithm; RK represents a conversion key; and λ is a random security parameter. The data relay server generates an expression of re-encrypted ciphertext as follows: RCT←ReEnc(RK, PK, CT); where RCT represents re-encrypted ciphertext; ReEnc represents a re-encryption algorithm; RK represents a conversion key; PK represents a public key of a data accessor, and CT is original ciphertext data. The data accessor uses a private key of the data accessor to decrypt to obtain plaintext data, and an expression is as follows: M←Dec(RCT, SK); ​ Wherein, M is plaintext data; Dec represents a decryption algorithm; RCT represents re-encryption ciphertext of the data relay server; and SK is a private key of a data visitor.

Images