A data ownership multi-party sharing management method based on blockchain

By creating a multi-party shared management smart contract and event mechanism on the blockchain, the problem that a single home party's right confirmation is difficult to meet the cooperation needs of multiple parties is solved, and the rights confirmation and security update of multi-party shared data are realized, and data management is improved. Efficiency and reliability.

CN115242383BActive Publication Date: 2024-11-05CHINA SHIP SCIENTIFIC RESEARCH CENTER +2
View PDF 6 Cites 0 Cited by

Patent Information

Application Number
CN202210833018.4
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2022-07-14
Publication Date
2024-11-05
Estimated Expiration
2042-07-14

AI Technical Summary

Technical Problem

The existing blockchain-based data rights confirmation technology only supports a single attorney’s right confirmation mechanism, which is difficult to meet the rights confirmation needs of multi-party cooperation data.

Method used

Using the blockchain-based data ownership multi-party sharing management method, by creating a multi-party sharing management smart contract, the user public and private keys of each legitimate user are saved, and sample data objects are generated, including encrypted data, ownership list and The ownership key list supports multi-party rights confirmation mechanism, and realizes trustworthy calculation and update of data through the blockchain event mechanism.

Benefits of technology

It realizes data rights confirmation in multi-party sharing scenarios, ensures the uniqueness and security of data access rights, supports data updates and historical records, and reduces the waste of system resources and operation and maintenance workload.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN115242383B_ABST
    Figure CN115242383B_ABST
Patent Text Reader

Abstract

The present application discloses a data ownership multi-party sharing management method based on blockchain, which relates to the field of blockchain technology. The method generates a sample data object in response to a data on-chain request through a multi-party sharing management smart contract. The sample data object includes encrypted data obtained by encrypting original data using an original data key, an ownership list, and an ownership key list. The ownership list includes a user identifier of the original data owner, and the ownership key list includes a number of ownership keys obtained by encrypting the original data key using the user public key of the corresponding owner. The sample data object is sent to the blockchain, and each ownership key is returned to each owner for access, so that a one-to-many permission relationship mapping can be realized, thereby meeting the data right confirmation requirements in the multi-party sharing scenario.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present application relates to the field of blockchain technology, and in particular to a blockchain-based data ownership multi-party shared management method. Background Art

[0002] Data ownership is a core issue that must be addressed in the development of the data industry. For data to become digital assets, the most important thing is to confirm the ownership of the data. Simply put, it is to determine who a certain data belongs to. At present, as the fair accounting, encryption security, difficulty in tampering, and full traceability of blockchain and alliance chain technologies are widely recognized by the industry, the application of digital asset ownership confirmation based on blockchain and alliance chain technologies is also being gradually promoted and put into practice in many industry fields.

[0003] The method of data rights confirmation of blockchain technology is that when users confirm the rights of their own works, the confirmation data will be stored in the form of hash values ​​on the blockchain for preservation. Through the characteristics of blockchain decentralization and distributed accounting, it is effectively guaranteed that the stored electronic data will not be tampered with, and the authenticity and originality of the confirmation data will be guaranteed. The patent number CN201911381869.4, "Data Rights Confirmation Method and System Based on Blockchain", discloses a data rights confirmation method based on blockchain alliance chain, which can realize rights confirmation management based on user identity.

[0004] In current data application scenarios, more and more valuable data, especially high-value sample data for deep mining by artificial intelligence, often require the cooperation of multiple parties to build a complete system environment and work together to complete. However, the current common blockchain-based data rights confirmation technology only supports the confirmation mechanism of a single owner, that is, the data can only have one owner, which is difficult to meet the existing multi-party cooperation data confirmation needs. Summary of the invention

[0005] In response to the above problems and technical requirements, the applicant has proposed a data ownership multi-party sharing management method based on blockchain. The technical solution of this application is as follows:

[0006] A data ownership multi-party sharing management method based on blockchain, the method comprising:

[0007] Create a smart contract for multi-party ownership sharing management. The smart contract for multi-party ownership sharing management stores the public keys of each legitimate user. Each legitimate user stores his or her own private key. The public key and private key of each legitimate user form a pair of keys.

[0008] Obtain a data upload request, which includes the original data and at least two corresponding owners, each of which is a legitimate user;

[0009] The multi-party ownership sharing management smart contract generates a sample data object in response to a data upload request. The sample data object includes encrypted data obtained by encrypting the original data using the original data key, an ownership list, and an ownership key list. The ownership list includes the user identifier of the owner of the original data. The ownership key list includes a number of ownership keys, and each ownership key corresponds to an owner. Each ownership key is obtained by encrypting the original data key with the user public key of the corresponding owner.

[0010] The sample data object is sent to the blockchain through the multi-party shared ownership management smart contract, and each ownership key is returned to each owner so that each owner can access and use the original data using their own ownership key.

[0011] Its further technical solution is to respond to the data on-chain request through the multi-party shared ownership management smart contract, use the original data key to encrypt the original data to obtain the encrypted data, and temporarily store the encrypted data and the original data key in the storage cache; and fill the encrypted data in the storage cache into the sample data object, and destroy the encrypted data in the storage cache; after generating the sample data object and sending it to the blockchain, destroy the original data key in the storage cache.

[0012] Its further technical solution is that the data chain request includes a data type field and a data content field. When the data type field indicates that the original data has not been uploaded to the blockchain, the multi-party shared management smart contract extracts the field information of the data content field to obtain the original data; when the data type field indicates that the original data has been uploaded to the blockchain, the multi-party shared management smart contract reads the original data from the blockchain according to the chain data address index recorded in the data content field.

[0013] Its further technical solution is that the method further comprises:

[0014] The blockchain receives a data usage request for the original data sent by a legitimate user. The data usage request is used to request to trigger the application model of the original data in a predetermined business scenario, and the application model pre-registers the event service with the blockchain as an application event;

[0015] When it is determined that the legitimate user is the owner of the original data, the blockchain builds a trusted computing environment based on the multi-party shared management smart contract according to the data usage request, obtains the sample data object corresponding to the original data, manages the original data and auxiliary parameters, calls the application event under the endorsement of multiple nodes, and returns the execution result to the legitimate user after the application is executed.

[0016] A further technical solution is that the data use request includes a data index, an event code uniquely corresponding to the application event, and a user data key of a legitimate user who is the right holder, and the user data key is obtained by encrypting the original data key with the user private key of the corresponding right holder;

[0017] After receiving the data use request, the blockchain obtains the sample data object in the blockchain account book according to the data index, and detects whether the ownership list of the sample data object contains the legal user. If so, it is determined that the legal user is the owner of the original data. Otherwise, it is determined that the legal user is not the owner of the original data and does not respond to the data use request.

[0018] When it is determined that the legitimate user is the owner of the original data, the blockchain uses the user data key to decrypt the encrypted data in the sample data object to obtain the original data, and uses the event code to call the corresponding application event to trigger the application model of the original data in the predetermined business scenario.

[0019] Its further technical solution is that the method further comprises:

[0020] Determine the application model of raw data in the predetermined business scenario;

[0021] Solidify the application model through smart contracts, deploy the application model smart contracts and register event services on the blockchain as application events;

[0022] The event code uniquely corresponding to the application event is returned to each owner of the original data.

[0023] Its further technical solution is that the method further comprises:

[0024] When the blockchain parses data using a request and detects an automatic update flag, the blockchain synchronizes updates to the original data generated during application execution to the sample data object corresponding to the original data.

[0025] Its further technical solution is that the method further comprises:

[0026] When the original data in the sample data object is updated, the old version of the original data in the sample data object is written into the historical ledger for data tracing.

[0027] Its further technical solution is that the method further comprises:

[0028] The blockchain generates and saves the usage process record of the original data, which includes the caller who requests to use the original data, the call time, the call reason and the call status.

[0029] Its further technical solution is that the method further comprises:

[0030] The blockchain receives an ownership change request sent by any owner of the original data. The ownership change request is used to request a change in the ownership list of the original data.

[0031] The blockchain generates an ownership change notification based on the ownership change request and sends it to the owner of the original data;

[0032] When the consent feedback of the owner in response to the ownership change notification is received, the ownership list and ownership key list of the sample data object of the original data are modified according to the ownership change request through the ownership multi-party sharing management smart contract: when a new owner is added, the newly added owner is added to the ownership list and the corresponding ownership key is generated for the newly added owner and added to the ownership key list of the sample data object; when an existing owner is deleted, the owner requested to be deleted is deleted from the ownership list, and the ownership key corresponding to the owner requested to be deleted is deleted from the ownership key list.

[0033] The beneficial technical effects of this application are:

[0034] The present application discloses a method for managing multi-party shared data ownership based on blockchain. The method supports a property rights confirmation mechanism for multi-party shared ownership, utilizes the tamper-proof and privacy encryption characteristics of blockchain to form a unique sample data object, and the data object maintains a property rights list and a property rights key list, thereby realizing a one-to-many permission relationship mapping, which can meet the data property rights confirmation needs in a multi-party shared ownership scenario.

[0035] The original data key is derived from the user public key of each right holder to form an ownership key. The derived ownership keys are independent of each other and do not affect each other. They can all achieve normal access to the original data. The original data key is automatically destroyed after being derived to form the ownership key, and the data access rights are completely returned to the original data owner.

[0036] This application avoids the usage mode of downloading source data first and then importing source data into the application model in traditional blockchain data applications. The application logic of the original data is solidified through blockchain smart contracts, and then the blockchain event mechanism is used to register the smart contract as an event code. The right holder can call the original data to perform specific business scenario calculations by triggering the event code. The entire calculation process is executed in a trusted blockchain environment. The original data does not need to be separated from the blockchain system environment. The output calculation results are returned to the right holder, realizing the download-free and touch-free use of the original data. At the same time, the blockchain records the entire application trajectory of the original data.

[0037] Traditional blockchain data rights confirmation cannot update the confirmed data. The updated data can only be re-confirmed as a new data asset. Frequent rights confirmation will lead to a large amount of system space and performance waste, and also increase the workload of data operation and maintenance for experimenters. The management method provided by this application encapsulates the original data into sample data objects and manages them on the chain, supports the update of the original data, and the updated original data is used as the current world state to lock the rights confirmation relationship, so as to achieve the superimposed update of the rights confirmation information of the same sample data, avoiding the problems caused by re-confirmation, and is particularly suitable for application scenarios of original data that are frequently updated and necessary, such as experimental data. And the blockchain records the original data of the old version throughout the process, which is convenient for tracing.

[0038] For the update of sample data that has been confirmed, it is extremely important to ensure the reliability of data updates. This application provides a joint signature voting mechanism. With the unanimous consent of all current authorized parties of the original data, the ownership list of the original data can be changed. The ownership change request is initiated by any owner of the original data and confirmed by the signatures of other owners. If any owner rejects it, the change process will be terminated. The voting process is stored by the blockchain to form an unalterable chain of evidence. For the updated original data, the blockchain saves all complete historical versions, which is highly reliable. BRIEF DESCRIPTION OF THE DRAWINGS

[0039] Figure 1 This is a flow chart of a method for uploading original data shared by multiple parties to a blockchain in one embodiment of the present application.

[0040] Figure 2 It is a schematic diagram of the data structure of a sample data object in one embodiment of the present application.

[0041] Figure 3 This is a flow chart of a method in which any right holder accesses and uses original data shared by multiple right holders in a blockchain in one embodiment of the present application.

[0042] Figure 4 It is a flow chart of a method for changing the ownership list of original data shared by multiple parties in one embodiment of the present application. DETAILED DESCRIPTION

[0043] The specific implementation of the present application is further described below in conjunction with the accompanying drawings.

[0044] The present application discloses a data ownership multi-party sharing management method based on blockchain. First, a multi-party sharing management smart contract is created. The multi-party sharing management smart contract of the present application has the function of managing key pairs. When a legitimate user registers information to the blockchain, the blockchain system generates a pair of keys including a user key and a user private key. The multi-party sharing management smart contract saves the legitimate user and his / her public key in correspondence, and returns the user private key to the corresponding legitimate user for each of them to save.

[0045] In the blockchain system, legal users are generally represented by corresponding user identifiers. This application will no longer describe user identifiers in detail, but will directly describe them as legal users.

[0046] For example, a general key algorithm such as RSA and ECC can be used to randomly generate an asymmetric pair of keys according to the specified algorithm type. When a legitimate user registers, the generated user public key will be bound to the legitimate user and stored accordingly, and the user private key will be encrypted through TLS and returned to the legitimate user.

[0047] 1. For the process of uploading the original data to the blockchain, please refer to Figure 1 Flowchart shown.

[0048] Step S1, obtaining a data upload request, which is used to request to upload the original data to the blockchain. The data upload request includes the original data and its corresponding at least two owners, each of which is a legitimate user.

[0049] In one embodiment, the original data included in the data upload request is new data that has not been uploaded to the blockchain. Alternatively, in another embodiment, the original data included in the data upload request is data that has been uploaded to the blockchain.

[0050] Optionally, the data on-chain request also includes an encryption algorithm type, which is used to instruct the multi-party shared ownership management smart contract to encrypt the original data using the specified encryption algorithm type.

[0051] Optionally, the data upload request also includes characteristic information and format specifications of the original data.

[0052] Optionally, the data upload request also includes a request number and a legitimate user who sends the data upload request. The legitimate user is generally one of the owners of the original data.

[0053] Based on the above information carried by the data uplink request, in one embodiment, the data format of the data uplink request is as follows, including the following fields:

[0054] (1) Request number field (Id field): The field information is the request number of the data upload request.

[0055] (2) Requester field (User field): The field information is the legitimate user who sent the data upload request.

[0056] (3) Data type field (Type field): The field information is the data type of the original data carried by the data upload request. When the field information is 0, it indicates that the original data carried has not been uploaded to the blockchain. When the field information is 1, it indicates that the original data carried has been uploaded to the blockchain.

[0057] (4) Data content field (Context field): The field information indicates the original data. In one embodiment, when the original data has not been uploaded to the blockchain, the field information of the data content field is the data content of the original data, and the multi-party sharing management smart contract extracts the field information of the data content field to obtain the original data. When the original data has been uploaded to the blockchain, the field information of the data content field is the on-chain data address index of the original data in the blockchain, and the multi-party sharing management smart contract reads the original data from the blockchain according to the on-chain data address index recorded in the data content field.

[0058] (5) Algorithm type field (Encrypt field): The field information is the encryption algorithm type.

[0059] (6) Ownership object field (AuthList field): The field information is in array form and contains multiple owners of the original data.

[0060] (7) Data feature field (Feature field): The field information is the feature information of the original data.

[0061] (8) Data format field (Format field): The field information is the format specification of the original data.

[0062] For example, the data upload request in an example is as follows:

[0063] {"Id":"123","User":"zhangsan","Type":"0",

[0064] "Context":"WyIwRENEODVCOTZFM0E5RjY0NENCM0YwODY3

[0065] MzhGRkNFQjRDM0U4NzJFIiwiMTU4Njk0NTgwNCJd",

[0066] "Encrypt":"AES","AuthList":["zhangsan","lisi","wangwu"],

[0067] "Feature":[],"Format":[]}

[0068] Based on the data upload request, it can be determined that the request number is 123, the legitimate user who sent the data upload request is zhangsan, the original data has not been uploaded to the blockchain, and the content of the original data carried is The specified encryption algorithm type is AES algorithm. The original data has three owners, namely zhangsan, lisi and wangwu. The above embodiment does not show in detail the content in the characteristic information and format specification of the original data.

[0069] Step S2, generating a sample data object in response to the data on-chain request through the ownership multi-party shared management smart contract.

[0070] The sample data object includes encrypted data obtained by encrypting the original data using the original data key, an ownership list and an ownership key list. The ownership list includes the user identifier of the owner of the original data. The ownership key list includes several ownership keys and each ownership key corresponds to an owner. Each ownership key is obtained by encrypting the original data key with the user public key of the corresponding owner.

[0071] For example, if the ownership list includes zhangsan, lisi, and wangwu, the original data key is encrypted with zhangsan's user public key 1 to obtain the ownership key 1 corresponding to zhangsan, the original data key is encrypted with lisi's user public key 2 to obtain the ownership key 2 corresponding to lisi, and the original data key is encrypted with wangwu's user public key 3 to obtain the ownership key 3 corresponding to wangwu. The resulting ownership key list includes ownership key 1, ownership key 2, and ownership key 3.

[0072] When receiving a data upload request, the multi-party shared management smart contract first responds to the data upload request and uses the original data key to encrypt the original data to obtain the encrypted data. The data upload request specifies the encryption algorithm type, and the multi-party shared management smart contract randomly generates the original data key and encrypts the original data according to the specified encryption algorithm and type using the original data key.

[0073] Then, the encrypted data and the original data key are temporarily stored in the storage cache, and then encapsulated to form a sample data object. The data structure of the sample data object is as follows: Figure 2 The sample data object includes a data header, a data feature field, a data format field, and a data content field, wherein the data header includes a data name field, a data checksum field, a data encryption type field, a property list field, and a property key list field:

[0074] (1) Data name field: The field information is the data name, which is the unique identifier of the original data.

[0075] (2) Data verification code field: The field information is a unique irreversible authentication code of the original data, generally a hash value, and has a data tamper-proof verification function.

[0076] (3) Data encryption type field: The field information is the type of encryption algorithm used for the original data.

[0077] (4) Ownership list field: The field information is the ownership list, generally in array form.

[0078] (5) Ownership key list field: The field information is the ownership key list, generally in array form.

[0079] (6) Data characteristic fields: Field information is the characteristic information of the original data. The characteristic information is an abstraction of key information of the data content with the goal of data application. It generally includes data classification, category, subject, applicable object, creation unit, creation time, scope, precision, etc.

[0080] (7) Data format field: Field information is a standard definition of the data content format. Data content is entered using row scanning, with commas separating the fields in each row. The data definition standardizes the data type, meaning, association, and other element information of each field.

[0081] (8) Data content field: The field information is encrypted data.

[0082] Based on the above data structure, the encrypted data in the storage cache is filled into the data content field in the sample data object. In addition, the encrypted data in the storage cache is filled into the sample data object, and the encrypted data in the storage cache is destroyed. The ownership list is filled into the ownership list field in the sample data object. The original data key is encrypted with the user public key of each owner in turn to obtain the ownership key, and the ownership key list is formed and filled into the ownership key list field in the sample data object. Then fill in the other fields in turn according to the specification, and the sample data object can be encapsulated.

[0083] For example, in one instance, the data header can be described in JSON protocol as follows:

[0084] {"Name":"CruiserX1","Encrypt":"AES","AuthList":["user1","user2","user3"],

[0085] "Key":["JFDURE07F93JFOSA3FCEB4C3E872ERE989FDSJNAQPPOFDS0988

[0086] FDSOEFSF8FDSAAFDDF0","U9FDSFD3FDSAFDSVCV4989OALPNNOSF8FD

[0087] SAAFD23VCWETVK9IJMLE2ARHQNLVPDF0","3JFS9FMMFIN1ABVXFREIMH

[0088] HFGREPPJU3GV658BCDERSLPKFIUHNNBGY5EFCCSSQZZFYYUIMMJHFDTU

[0089] KMOIHGHVRR6F33"]}

[0090] It can be seen that the data name is Name, the hash value of the original data is CruiserX1, the encryption algorithm type is AES algorithm, and the ownership list includes three owners, namely user1, user2 and user3. The ownership key list includes three ownership keys, which are the ownership keys corresponding to the owner user1. Corresponding to the ownership key of the owner user2 And the ownership key corresponding to the owner user3

[0091] Step S3: Send the sample data object to the blockchain through the multi-party shared ownership management smart contract, and return each ownership key to each ownership party.

[0092] In one embodiment, after the sample data object is sent to the blockchain, a feedback signal is returned to each right holder. The feedback signal includes the right holder's right key and the data index of the original data in the blockchain. In addition, it may also include information such as the request number. The feedback signal includes the following fields:

[0093] (1) Request field: The field information is the request number.

[0094] (2) Index field: The field information is the data index of the original data in the blockchain.

[0095] (3) Key field: The field information is the ownership key corresponding to the owner, that is, the result of encrypting the original data key using the user public key of the owner.

[0096] In one example, the feedback signal sent by the multi-party shared management smart contract to one owner is as follows:

[0097] {"Id":"124","Data":""JDS93F2SDU",

[0098] "Key":"JFDURE07F93JFOSA3FCEB4C3E872ERE989F

[0099] DSJNAQPPOFDS0988FDSOEFSF8FDSAAFDDF0"}

[0100] In this example, the request number is 124, the data index is JDS93F2SDU, and the ownership key is

[0101] The right holder can obtain the original data key by decrypting the right key with their own user private key, and then each right holder can use their own right key to access and use the original data in the blockchain. Each right key is independent of each other and does not affect each other, and can achieve normal access to the original data. In addition, after the sample data object is generated and sent to the blockchain, the original data key in the storage cache is destroyed, which ensures that there is no plain text or weakly secure original data key of the original data in the blockchain account book, and the data access rights are completely returned to the original data owner.

[0102] 2. For the application process of raw data, please refer to Figure 3 Flowchart shown.

[0103] Through steps S1 to S3, the original data has been uploaded to the chain, and each right holder can access and use the original data normally. In the conventional blockchain application process, the right holder needs to download the source data first, and then import the usage mode of the source data into the application model. However, one more source data download operation means one more data leakage risk. In the scenario of multi-party ownership sharing, any right holder who directly touches the source data will also bring data security risks to other right holders. Therefore, this application uses the blockchain event mechanism to realize a fully closed application mode of original data to ensure the security of the data access process.

[0104] Step S1, first you need to register the application event, including the following steps:

[0105] 1. Determine the application model of the original data in the predetermined business scenario, and determine the data dependency and output target of the application model. Data dependency includes the original data and other auxiliary parameters. The data format field in the sample data object defines the encrypted data in a standardized manner, and the auxiliary data needs to refer to the application model requirements to clarify the format definition. Consider the application goal, design the output format definition, and the output parameters will be returned to the client used by the right holder as the output target.

[0106] 2. Solidify the application model through smart contracts, deploy the application model smart contract and register the event service as an application event to the blockchain. After clarifying the application model, it is necessary to write the smart contract processing logic based on the input data dependency to produce the output target. The smart contract execution process is an abstraction of the business application logic process and an intelligent training of sample data. After the smart contract is edited, it is deployed in the blockchain alliance chain ownership sharing channel. After deployment, register the event application to the blockchain with the smart contract address and application data model definition as parameters. The blockchain detects the request parameter specification to confirm that there is no duplicate registration of the smart contract.

[0107] 3. Return the event code that uniquely corresponds to the application event to each owner of the original data. After the blockchain event module passes the inspection, a unique event code is generated, bound to the event response address, and the successfully registered event code is returned to each owner of the original data.

[0108] Step S2, triggering an application event, includes the following steps:

[0109] 1. When a legitimate user requests to start an application event of the original data, he / she sends a data usage request for the original data. The data usage request is used to request to trigger the application model of the original data in the predetermined business scenario, and the application model pre-registers the event service as an application event with the blockchain according to the above operation.

[0110] In one embodiment, the data use request includes a data index, an event code uniquely corresponding to the application event, and a user data key of a legitimate user as the right holder. The user data key is obtained by encrypting the original data key with the user private key of the corresponding right holder. Since there is no explicit original data key in the blockchain account book, the user data key needs to be carried in the data use request.

[0111] Optionally, the data use request further includes an update mode field, and when the field information of the update mode field is an automatic update flag, it indicates that the original data is automatically updated. When the field information of the update mode field is a non-update flag, it indicates that the original data is not automatically updated.

[0112] In addition, the data use request may also include a request number, input parameters, etc. In one embodiment, the data use request includes the following fields:

[0113] (1) Request field: The field information is the request number.

[0114] (2) Event code field: The field information is the event code of the application event triggered by the request.

[0115] (3) Index field: The field information is the data index of the original data requested for access in the blockchain.

[0116] (4) Key field: The field information is the user data key of the legitimate user who is the right holder.

[0117] (5) Update mode field: When the field information of the update mode field is True, it is an automatic update flag; when the field information of the update mode field is False, it is a non-update flag.

[0118] (6) Parameter field: The field information is the input parameter.

[0119] In one example, a legitimate user sends a data usage request as follows:

[0120]

[0121] In this example, the request number is 124, the event code is USDFE97FD, the data index is JDS93F2SDU, and the user data key is And it carries the automatic update flag, and the input parameters are not given in detail in this example.

[0122] 2. The blockchain receives a data usage request for original data sent by a legitimate user, and determines whether the legitimate user of the data usage request is the owner of the original data. If so, it means that the legitimate user has the authority to operate the original data and responds to the data usage request. If not, it means that the legitimate user does not have the authority to operate the original data and does not respond to the data usage request.

[0123] Specifically, a sample data object is obtained in the blockchain ledger according to the data index in the data use request, and it is checked whether the legitimate user is included in the ownership list of the sample data object. If so, it is determined that the legitimate user is the owner of the original data. Otherwise, it is determined that the legitimate user is not the owner of the original data and the data use request is not responded to.

[0124] 3. When it is determined that the legitimate user is the owner of the original data, the ownership multi-party sharing management smart contract uses the user public key of the legitimate user to decrypt the user data key in the data use request to obtain the original data key, and uses the original data key to decrypt the encrypted data in the sample data object to obtain the original data. In addition, the blockchain builds a trusted computing environment based on the ownership multi-party sharing management smart contract according to the data use request, obtains the sample data object corresponding to the original data, and manages the original data and auxiliary parameters. Under the endorsement of multiple nodes, the event code is used to call the corresponding application event, triggering the application model of the original data in the predetermined business scenario to achieve secure access. After the application is executed, the execution result is returned to the legitimate user who sent the data access request. When returning the execution structure, the execution result can also be encrypted and returned using the user public key corresponding to the legitimate user.

[0125] As mentioned above, the data access request can carry an automatic update flag, and the blockchain will synchronize the updates to the original data generated during the application execution to the sample data object corresponding to the original data, that is, the updated original data will directly replace the old version of the original data that has been confirmed, without the need to re-confirm it as a new data asset like traditional blockchain applications. This method of updating original data is particularly suitable for experimental sample data with frequent data updates. The accuracy and completeness of the updated original data are higher than those of the old version of the original data, and it can directly replace the old version of the original data, realizing the superimposed update of the confirmation information of the same original data. In addition, when updating the original data in the sample data object, the old version of the original data in the sample data object is written into the historical account book for data tracing.

[0126] During the application process, the blockchain will also generate and save records of the use of the original data, which include the caller who requests to use the original data, the call time, the call reason and the call status.

[0127] 3. Ownership change function, please refer to Figure 4 Flowchart shown.

[0128] The multi-party shared ownership management smart contract also provides an update service for the ownership list. The sample data may be significantly improved and optimized due to the participation of new franchisees. It includes the following steps:

[0129] 1. Any owner of the original data sends an ownership change request, which is used to request a change in the ownership list of the original data.

[0130] The ownership change request includes the data index of the original data in the blockchain, the user data key of the legitimate user who sent the ownership change request, the change type and the owner to be changed, and may also include the request number, etc. In one embodiment, the ownership change request includes the following fields:

[0131] (1) Request field: The field information is the request number.

[0132] (2) Requester field: The field information is the legitimate user who sent the ownership change request.

[0133] (3) Index field: The field information is the data index of the original data requested for access in the blockchain.

[0134] (4) Key field: The field information is the user data key of the legitimate user who is the right holder.

[0135] (5) Change type field: The field information is the type of change requested for the ownership list. When the field information is 1, it requests to add a new owner to the ownership list. When the field information is 0, it requests to delete an existing owner from the ownership list.

[0136] (6) Change data field: The field information is the party whose rights are to be changed.

[0137] For example, in one instance, the ownership change request is as follows:

[0138]

[0139] In this example, the request number is 126, the legal user who sent the ownership change request is zhangsan, the data index is JDS93F2SDU, and the user data key is The field information of the change type field RenewType is 1, and the field information of the change data field RenewData is J83JFNDS0938IF09S098, indicating that the ownership change request is used to request to add a new legal user J83JFNDS0938IF09S098 as the owner in the ownership list.

[0140] 2. The blockchain receives the ownership change request for the original data and first checks whether the ownership change request is legal, including checking whether the legitimate user who sends the ownership change request is the owner of the original data, whether the user data key is correct, etc. If the data is correct, it means that the ownership change request is legal and the next step is executed. Otherwise, the ownership change request will not be responded to.

[0141] 3. When it is determined that the request for change of ownership is legitimate, the blockchain generates a notification of change of ownership based on the request for change of ownership and sends it to the owner of the original data. The blockchain inserts the notification of change of ownership into the blockchain ledger, and the owner of the original data can query the notification of change of ownership. The notification of change of ownership is used to notify each owner that the owner who sent the request for change of ownership requests to change the ownership list. Other owners can respond to the notification of change of ownership and return a consent feedback, indicating that they agree to change the ownership list, or they can respond to the notification of change of ownership and return a rejection feedback, indicating that they do not agree to change the ownership list.

[0142] 4. The change of ownership adopts a one-vote veto system. If the ownership parties unanimously agree, the change of the ownership list will take effect. That is, when the consent feedback of all owners in response to the ownership change notification is received, the ownership list and ownership key list of the sample data object of the original data are modified according to the ownership change request through the ownership multi-party sharing management smart contract, including two situations: when the ownership change request is used to request the addition of a new owner, the ownership multi-party sharing management smart contract will add the newly added owner to the ownership list and generate a corresponding ownership key for the newly added owner and add it to the ownership key list of the sample data object, and also return the generated ownership key to the newly added owner. When the ownership change request is used to request the deletion of an existing owner, the ownership multi-party sharing management smart contract will delete the owner requested to be deleted from the ownership list, and delete the ownership key corresponding to the owner requested to be deleted from the ownership key list. In actual application, the situation of adding a new owner is more commonly used.

[0143] If the owner returns a rejection, no change will be made. The voting results for ownership change will be notified to the owners who participated in the vote and recorded in the blockchain system ledger.

[0144] The above is only a preferred embodiment of the present application, and the present application is not limited to the above embodiments. It is understood that other improvements and changes directly derived or associated by those skilled in the art without departing from the spirit and concept of the present application should be considered to be included in the protection scope of the present application.

Claims

1. A data ownership multi-party sharing management method based on blockchain, characterized in that: The method comprises: Creating a smart contract for multi-party ownership sharing management, through which the public key of each legitimate user is stored, and each legitimate user stores his or her own private key, and the public key and private key of each legitimate user form a pair of keys; Obtain a data upload request, where the data upload request includes the original data and at least two corresponding rights holders, each of which is a legitimate user; Generate a sample data object in response to the data on-chain request through the ownership multi-party sharing management smart contract, the sample data object includes encrypted data obtained by encrypting the original data using the original data key, an ownership list and an ownership key list, the ownership list includes the user identifier of all owners of the original data, the ownership key list includes a plurality of ownership keys and each ownership key corresponds to an owner, and each ownership key is obtained by encrypting the original data key with the user public key of the corresponding owner; The sample data object is sent to the blockchain through the multi-party shared ownership management smart contract, and each ownership key is returned to each ownership party, so that each ownership party can access and use the original data using its own ownership key.

2. The method according to claim 1, characterized in that The multi-party shared ownership management smart contract responds to the data on-chain request, uses the original data key to encrypt the original data to obtain encrypted data, and temporarily stores the encrypted data and the original data key in a storage cache; and fills the encrypted data in the storage cache into the sample data object, and destroys the encrypted data in the storage cache; after generating the sample data object and sending it to the blockchain, destroys the original data key in the storage cache.

3. The method according to claim 1, characterized in that The data on-chain request includes a data type field and a data content field. When the data type field indicates that the original data has not been uploaded to the blockchain, the multi-party sharing management smart contract extracts the field information of the data content field to obtain the original data; when the data type field indicates that the original data has been uploaded to the blockchain, the multi-party sharing management smart contract reads the original data from the blockchain according to the on-chain data address index recorded in the data content field.

4. The method according to claim 1, characterized in that: The method further comprises: The blockchain receives a data usage request for original data sent by a legitimate user, wherein the data usage request is used to request triggering an application model of the original data in a predetermined business scenario, and the application model pre-registers an event service with the blockchain as an application event; When it is determined that the legitimate user is the owner of the original data, the blockchain builds a trusted computing environment based on the multi-party shared management smart contract according to the data usage request, obtains the sample data object corresponding to the original data and manages the original data and auxiliary parameters, calls the application event under the endorsement of multiple nodes, and returns the execution result to the legitimate user after the application is executed.

5. The method according to claim 4, characterized in that The data use request includes a data index, an event code uniquely corresponding to the application event, and a user data key of the legal user as the right holder, wherein the user data key is obtained by encrypting the original data key with the user private key of the corresponding right holder; After receiving the data use request, the blockchain obtains a sample data object in the blockchain account book according to the data index, and detects whether the legitimate user is included in the ownership list of the sample data object. If so, it is determined that the legitimate user is the owner of the original data; otherwise, it is determined that the legitimate user is not the owner of the original data and does not respond to the data use request; When it is determined that the legitimate user is the owner of the original data, the blockchain uses the user data key to decrypt the encrypted data in the sample data object to obtain the original data, and uses the event code to call the corresponding application event to trigger the application model of the original data in the predetermined business scenario.

6. The method according to claim 5, characterized in that The method further comprises: Determine an application model of the original data in a predetermined business scenario; Solidify the application model through a smart contract, deploy the application model smart contract and register the event service as an application event on the blockchain; The event code uniquely corresponding to the application event is returned to each owner of the original data.

7. The method according to claim 4, characterized in that The method further comprises: When the blockchain parses the data usage request and detects an automatic update identifier, the blockchain synchronizes the updates to the original data generated during the application execution process to the sample data object corresponding to the original data.

8. The method according to claim 7, characterized in that The method further comprises: When the original data in the sample data object is updated, the old version of the original data in the sample data object is written into the historical ledger for data tracing.

9. The method according to claim 4, characterized in that The method further comprises: The blockchain generates and saves a usage process record of the original data, wherein the usage process record includes a caller who requests to use the original data, a call time, a call reason, and a call status.

10. The method according to claim 1, characterized in that The method further comprises: The blockchain receives an ownership change request sent by any owner of the original data, where the ownership change request is used to request a change in the ownership list of the original data; The blockchain generates an ownership change notification according to the ownership change request and sends it to the owner of the original data; When the consent feedback of the owner in response to the ownership change notification is received, the ownership list and ownership key list of the sample data object of the original data are modified according to the ownership change request through the ownership multi-party sharing management smart contract: when a new owner is added, the newly added owner is added to the ownership list and a corresponding ownership key is generated for the newly added owner and added to the ownership key list of the sample data object; when an existing owner is deleted, the owner requested to be deleted is deleted from the ownership list, and the ownership key corresponding to the owner requested to be deleted is deleted from the ownership key list.

Citation Information

Patent Citations

  • Data right confirmation method and system based on block chain

    CN111245602A

  • Ownership-based data security transaction method and system

    CN108090769A

  • Data right confirmation method and device

    CN110598480A

  • Data right confirmation method and device, storage medium and electronic device

    CN111934881A

  • Encrypted data asset right confirmation, management and use method and device based on block chain

    CN114329512A