Multistage confidential data right confirmation and sharing management system and management method
By designing a multi-level confidential data rights confirmation and sharing management system in blockchain technology, using smart contracts and digital envelope technology, the security problem of confidential data sharing management in blockchain technology is solved, and data security is achieved. Sequential sharing and dynamic permission management reduce calculation and management costs.
Patent Information
- Application Number
- CN202411127612.7
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-08-16
- Publication Date
- 2024-12-06
AI Technical Summary
Existing blockchain technology is difficult to effectively manage security issues of confidential data, especially in terms of user identity level changes and data permission dynamics, and the proxy re-encryption scheme has too much calculation and storage costs in a large number of confidential data sharing scenarios. high.
A multi-level confidential data rights confirmation and sharing management system is designed, including trusted digital identity application and issuance module, verified business certificate application and issuance module, data hierarchical identification and on-chain evidence storage module, and business identity verification and data Obtain modules, verify user identity and data permissions through smart contracts, and use blockchain and digital envelope technology to ensure data security.
It realizes the secure and orderly sharing of confidential data in blockchain technology, reduces the computing and management costs of the data sharing platform, and is suitable for confidential data sharing scenarios for multiple users. It realizes differentiation through trusted digital identity and business credential management. Users have different permission controls on the same data.
Smart Images

Figure CN119089490A_ABST
Abstract
Description
Technical Field
[0001] The present invention relates to the technical field of blockchain data sharing, and specifically to a multi-level confidential data rights confirmation and sharing management system and method. Background Art
[0002] In recent years, blockchain networks have become the preferred infrastructure for data sharing in various fields due to their decentralization, immutability, and traceability of data sources. However, the public nature of blockchain accounts makes it difficult to solve the security issues of confidential data sharing management alone.
[0003] A blockchain-based encrypted data storage and query method is as follows: 1) deploying alliance chains and smart contracts between members, and all users complete registration; 2) dividing the data uploaded by users into different levels according to the data volume and security level; 3) using different encryption schemes to store data of different levels; 4) for data query requests, first the smart contract verifies the identity, and after the verification is passed, the key management center distributes the decryption key and returns the data to the user.
[0004] The main shortcoming of this solution is that the system statically divides data and users into several levels and matches them, without taking into account that users have different identity levels in different business scenarios and their data permissions change accordingly.
[0005] A data sharing solution that combines proxy re-encryption technology is as follows: 1) Deploy alliance chains and smart contracts between members, and users complete distributed digital identity registration; 2) The data provider uses its own private key to encrypt the data and upload it to the chain. When the user applies for data, the provider uses its own private key and the user's public key to generate a re-encryption key and submit it to the data sharing platform; 3) The data sharing platform uses the re-encryption key to encrypt the ciphertext data on the chain and then uploads it to the chain; 4) The user requests the re-encrypted ciphertext data from the chain and decrypts the data using its own private key.
[0006] The main shortcomings of this solution are: 1) Assuming there are N pieces of data and each piece of data has M users, then each piece of data needs to store N*(1+M) pieces of ciphertext data on the chain if it is only requested once. This is not suitable for data sharing scenarios involving a large amount of confidential data in the blockchain. 2) To achieve accurate data authenticity, each piece of data needs to be re-encrypted with a new key for each user’s request and managed on the data sharing platform, which increases the computing and management costs of the data sharing platform. Summary of the invention
[0007] The purpose of the present invention is to overcome the shortcomings of the prior art and provide a multi-level confidential data rights confirmation and sharing management system and management method to solve the security problems of confidential data sharing management in blockchain technology.
[0008] In order to achieve the above purpose, a multi-level confidential data rights confirmation and sharing management system is designed, including: a trusted digital identity application and issuance module, which is used to receive the identity authentication information submitted by the user, and generate a public-private key pair locally for the user to verify the user's identity. After the identity verification, the trusted digital identity information is created and submitted to the decentralized identity chain, and the trusted digital identity information is returned to the user terminal for storage; a verifiable business credential application and issuance module is used to receive the user's business credential application from the verifiable business credential issuing agency, verify the validity of the user's trusted digital identity through the DID verification contract, and generate the corresponding verifiable business credential after the verification is passed, and submit the generated business credential to the corresponding business The module is used to allow the data provider to conduct confidentiality assessment, identification and encryption of confidential data, receive the data chain evidence request from the data provider to the business system, and verify the user's identity validity and data operation authority through the verifiable business verification contract. After the verification is passed, the evidence data is stored in the corresponding business chain and the on-chain hash is returned to the user; the business identity authentication and data acquisition module is used to process the data acquisition request from the data applicant to the business system, and verify the user's identity validity and data operation authority. After the verification is passed, the data key and evidence data are prepared and returned to the data applicant for obtaining the plain text of the evidence data.
[0009] The present invention also provides a multi-level confidential data rights confirmation and sharing management method, which is as follows: a trusted digital identity application and issuance method: A1. The user submits identity authentication information to the trusted digital identity platform client to apply for DID; A2. The DID issuer generates a public-private key pair locally in the user and completes the user identity verification; A3. After the verification is passed, the DID issuer creates a trusted digital identity information for the user; A4. The DID issuer submits the trusted digital identity information to the DID chain and returns it to the user; A5. The user saves the trusted digital identity information locally; B1. The user applies for a business certificate from a verifiable business certificate issuing agency; B2. The verifiable business certificate issuing agency verifies the validity of the user's trusted digital identity through a DID verification contract; B3. After the verification is passed, the verifiable business certificate issuing agency creates a corresponding verifiable business certificate for the user; B4. The verifiable business certificate issuing agency submits the verifiable business certificate to the corresponding business chain and returns it to the user; B5. The user encrypts and saves the verifiable business certificate locally; also includes data classification identification and on-chain evidence storage method: C1. The data provider evaluates the confidentiality of the data, identifies the data and encrypts the confidential data; C2. The data provider applies to the verifiable business system for data chain evidence storage; C3. The verifiable business system verifies the user's identity validity and data operation authority through the verifiable business verification contract; C4. After the verification is passed, the evidence data is submitted to the corresponding business chain, and the chain hash is returned to the user; including business identity authentication and data acquisition methods: D1. The data applicant applies to the business system for data; D2. The business system verifies the user's identity validity and data operation authority through the verifiable business verification contract; D3. After the verification is passed, the data key and evidence data are prepared and returned to the applicant; D4. The data applicant obtains the plaintext of the evidence data.
[0010] Preferably, the multi-level confidential data rights confirmation and sharing management method provided by the present invention also includes other technical features, wherein, in step B2, the verifiable business credential issuing agency uses a private key to decrypt the application information submitted by the user and triggers the DID verification contract on the DID chain, and the verification logic is: B2.1. User identity authentication: find the DID document according to the DID identifier submitted by the user, and use the user public key in the document to verify the user signature to ensure that the current user is consistent with the DID identity owner; B2.2. DID issuer identity authentication: use the DID issuer public key to verify that the verifiable business credential issuing agency signature in the DID document is a valid signature; B2.3. DID validity period verification: verify that the DID validity period in the DID document is greater than the current time to ensure that the DID is within the validity period; B2.4. If the verification is successful, the verification success identifier and the DID validity period are returned to the verifiable business credential issuing agency system; if the verification fails, the verification failure identifier is returned.
[0011] Preferably, the multi-level confidential data rights confirmation and sharing management method provided by the present invention also includes other technical features, wherein in step B3, the verifiable business credential issuing agency issues a verifiable business credential to the user according to the user's DID type and business application information; the verifiable business credential includes but is not limited to the verifiable business number, user DID identification and type, business purpose, data applicant, data provider, and business identity identification information; wherein the verifiable business validity period must be within the DID validity period; the business purpose can be divided into data storage and data acquisition; if it is data acquisition, the data applicant and data provider company names must be stated; the business identity is The user's identity level in the current business. The same user can have one or more business identity identifiers, and the final data authority is the union of the data permissions owned by each business identity identifier; the verifiable business credential issuing authority uses a private key to sign the credential information and attaches the signature to the verifiable business credential; the business identity identification strategy is as follows: B3.1 Personal DID: Issued for business credentials within the company to which it belongs, and the identity identifier is set based on the degree of relevance between the user and the business and the data confidentiality level; B3.2 Enterprise DID: Issued for business credentials between enterprises, and the identity identifier is set based on the business relevance between the user's company and the data provider and the data confidentiality level.
[0012] Preferably, the multi-level confidential data rights confirmation and sharing management method provided by the present invention also includes other technical features, wherein, in the step C1, the data provider marks the confidentiality level of the data according to the confidential field and confidentiality level of the stored data; uses English letters and numbers to identify the confidentiality level; the public data marked as completely non-confidential is uploaded to the chain in plain text, and the confidential data of other levels are protected by digital envelope technology to protect the data transmission security; the confidential data is symmetrically encrypted with a data key, and the ciphertext is submitted to the chain. When a user applies for data, the data key is asymmetrically encrypted with the public key of the data applicant and returned to the applicant; wherein, the data key generation and encryption and decryption, and the data encryption and decryption algorithm are encapsulated in the key SDK package and provided to the user for local call; the data key is updated using the following strategies: C1.1 is updated in the time dimension, including real-time update C1.2 is updated in the data dimension, including updating every piece of data or updating every few pieces of data; when the data provider applies for evidence storage on the data chain, it is necessary to submit the verifiable business certificate and the evidence data, assemble the verifiable business certificate and the evidence data, sign them, and encrypt them with the public key of the verifiable business system before submitting them; in the step C3, the verifiable business system uses the private key to decrypt the application information submitted by the user, triggering the verifiable business system verification contract on the business chain, and the verification logic is: C3.1 User identity verification: find the verifiable business certificate according to the verifiable business number submitted by the user, find the DID document according to the DID identifier in the certificate, and use the user public key in the DID document to verify the user signature to ensure that the current user's true identity is consistent with the identity of the DID and the verifiable business owner; C3.2 Verifiable business authority identity verification: Use the public key of the verifiable business authority to verify that the authority signature in the verifiable business certificate is a valid signature; C3.3 Verifiable business validity period verification: Verify that the validity period in the verifiable business certificate is greater than the current time to ensure that the verifiable business certificate is within the validity period; C3.4 Verifiable business authority verification: Verify that the business purpose of the verifiable business certificate is data evidence storage, and that the user has evidence storage authority in the target business chain; C3.5 If the verification is successful, a verification success mark is returned to the system; if the verification fails, a verification failure mark is returned.
[0013] Preferably, the multi-level confidential data rights confirmation and sharing management method provided by the present invention also includes other technical features, wherein in step D2, the verifiable business verification system decrypts the application information submitted by the user and triggers the VC verification contract on the business chain. The contract verification logic refers to steps C3.1-C3.5 in C3, wherein the verifiable business authority verification logic is as follows, and the rest of the verification logic remains unchanged: D2.1 If it is an intra-enterprise data application, verify that the DID type is a personal DID, the data applicant and the data provider have the same enterprise name, and according to the permission rules agreed upon in the business, the user's business identity matches the acquisition authority of the applied data; D2.2 If it is an inter-enterprise data application, verify that the DID type is an enterprise DID, the data applicant and the data provider have different names, and according to the permission rules agreed upon in the business, the user's business identity matches the acquisition authority of the applied data; in step D3, the verifiable business verification contract prepares data after successful verification: D3.1 For public data, directly query the public data plaintext from the corresponding business chain, sign it with the private key and return it to the user; D3.2 For confidential data, apply for the corresponding data key from the data provider, and query the confidential data ciphertext from the corresponding business chain; the data provider encrypts the data key with the public key of the data applicant, signs it with the private key and returns it to the verifiable business system. The business system verifies the signature with the public key of the data provider. After the signature is verified, the data key ciphertext is assembled with the confidential data ciphertext, signed with the private key and returned to the user.
[0014] Compared with the prior art, the present invention has the following advantages: 1. This invention uses blockchain and smart contract technology to build a trusted data sharing infrastructure. Through smart contracts, DID verification, VC verification and data on-chain operations are completed to ensure the safe and orderly sharing of public data and confidential data; 2. The present invention realizes identity authentication and data rights confirmation through trusted digital identity technology. For data sharing scenarios within and between enterprises, two types of DIDs are designed: personal and enterprise. VC certificates of different business identity levels are issued for different DID types, corresponding to data permissions of different confidentiality levels, so as to realize different permission management of the same data by different users; 3. The present invention uses digital envelope technology to protect the storage and transmission security of confidential data. The data provider only needs to perform symmetrical encryption on the original data once, which reduces the storage and computing pressure and is more suitable for confidential data sharing scenarios among multiple users. In addition, the data key is designed with a dual-dimensional update strategy of time and data, providing a more flexible way to balance data security and service performance. BRIEF DESCRIPTION OF THE DRAWINGS
[0015] Figure 1 , is a schematic diagram of the trusted digital identity application and issuance process; Figure 2, a schematic diagram of the application and issuance process of verifiable business credentials; Figure 3 , a schematic diagram of the data classification identification and on-chain evidence storage, business identity verification and data acquisition process. DETAILED DESCRIPTION
[0016] In order to make the purpose, principle and structure of the present invention more clear, it is further described below in conjunction with the drawings and specific embodiments.
[0017] The present invention provides a multi-level confidential data rights confirmation and sharing management method, including four modules: application and issuance of trusted digital identity, application and issuance of verifiable business credentials, data classification identification and on-chain evidence storage, business identity authentication and data acquisition: 1. The application and issuance process of a trusted digital identity is as follows: A1. The user submits identity authentication information to the client of the trusted digital identity platform (hereinafter referred to as the DID issuer) to apply for a DID; A2. The DID issuer generates a public-private key pair locally and completes the user identity verification; A3. Once the identity verification is passed, the DID issuer creates a trusted digital identity for the user; A4. The DID issuer submits the trusted digital identity information to the DID chain and returns it to the user; A5. Users save trusted digital identity information locally.
[0018] 2. The application and issuance process of verifiable business credentials is as follows: B1. The user applies for a business certificate from a verifiable business certificate issuing authority (hereinafter referred to as the VC issuer); B2. The VC issuer verifies the validity of the user’s trusted digital identity through the DID verification contract; B3. After verification, the VC issuer creates a corresponding VC credential for the user; B4. The VC issuer submits the VC certificate to the corresponding business chain and returns it to the user.
[0019] B5. The user encrypts the VC credentials and saves them locally.
[0020] 3. The process of data classification identification and on-chain evidence storage is as follows: C1. The data provider evaluates the confidentiality of the data, identifies the data and encrypts the confidential data; C2. The data provider applies to the business system (hereinafter referred to as the VC verifier) for data on-chain evidence storage; C3. The VC verifier verifies the user's identity validity and data operation authority through the VC verification contract; C4. After verification, the evidence data is submitted to the corresponding business chain, and the chain hash is returned to the user.
[0021] 4. The business identity authentication and data acquisition process is as follows: D1. The data applicant applies to the business system for data; D2. The business system verifies the validity of the user's identity and data operation authority through the VC verification contract; D3. After verification, the data key and evidence data are prepared and returned to the applicant; D4. The data applicant obtains the plain text of the stored data.
[0022] The present invention also includes the following technical optimization scheme: Among them, the modules and processes also have the following technical features.
[0023] 1. Application and issuance of trusted digital identity Furthermore, in step A1, when applying for a trusted digital identity certificate, two types of applications are supported: personal DID and corporate DID. For personal DID, personal identity information including but not limited to real name, ID number, facial recognition, mobile phone verification code, etc. must be submitted according to the real-name authentication template; for corporate DID, basic corporate information including but not limited to corporate name, business license, certification letter, legal representative, etc. must be submitted according to the corporate authentication template.
[0024] Furthermore, in step A2, when the DID issuer verifies the user information, it forwards the identity information submitted by the user to the authoritative citizen identity authentication platform or corporate identity authentication platform according to the applied DID type to verify the authenticity and validity of the personal / corporate identity. If the identity verification passes, a public-private key pair is created locally for the user, and the process goes to step A3; if the identity verification fails, a prompt indicating that the personal / corporate identity authentication failed is returned to the user.
[0025] Furthermore, in step A3, the DID issuer creates a trusted digital identity for the user, including a DID identifier and a DID document. The DID document includes, but is not limited to, information such as the DID identifier, DID type, DID validity period, and user public key. The DID issuer signs the document content using a private key and attaches the signature to the DID document.
[0026] Furthermore, in step A4, the smart contract submits the DID identifier and the DID document to the DID chain, and when the DID chain returns the chain hash, it is determined that the chain is successful. The DID issuer assembles the user identity information and the trusted digital identity information, signs them, and returns them to the user.
[0027] Furthermore, in step A5, the user uses the DID issuer's public key to verify the issuer's signature of the data packet and the issuer's signature in the DID document. After the verification is passed, the issued DID identifier and DID document are encrypted and saved locally.
[0028] 2. Application and issuance of verifiable business certificates Furthermore, in step B1, when a user applies for a service credential, he / she needs to submit the DID identification and service application information, sign the above information, encrypt it with the public key of the VC issuer, and then submit it.
[0029] Furthermore, in step B2, the issuer uses the private key to decrypt the application information submitted by the user and triggers the DID verification contract on the DID chain. The verification logic is: a. User identity verification. Find the DID document based on the DID identifier submitted by the user, and use the user's public key in the document to verify the user's signature to ensure that the current user is consistent with the DID identity owner; b. DID issuer identity verification. Use the DID issuer public key to verify that the issuer signature in the DID document is a valid signature; c. DID validity period verification. Verify that the DID validity period in the DID document is greater than the current time to ensure that the DID is within the validity period; d. If the verification is successful, the verification success mark and DID validity period will be returned to the issuing system; if the verification fails, the verification failure mark will be returned.
[0030] Furthermore, in step B3, the VC issuer issues a VC certificate to the user according to the user's DID type and service application information. The VC certificate includes but is not limited to the VC number, user DID identifier and type, service purpose, data applicant, data provider, service identity, and other information.
[0031] Among them, the validity period of VC must be within the validity period of DID; business purposes can be divided into data storage and data acquisition, etc.; if it is data acquisition, the data applicant and data provider company name must be stated; the business identity is the user's identity level in the current business. The same user can have one or more business identities, and the final data permission is the data permission set owned by each business identity. The VC issuer uses the private key to sign the credential information and attaches the signature to the VC credential.
[0032] The above business identity identification strategy is as follows: a. Personal DID: Issued for business credentials within the company to which it belongs. The identity is set based on the user's relevance to the business and the data confidentiality level.
[0033] b. Enterprise DID: Issued for business credentials between enterprises. The identity is set based on the business relevance between the user's enterprise and the data provider and the confidentiality level of the data.
[0034] Furthermore, in step B4, the smart contract submits the VC number and VC certificate to the corresponding business chain, and when the business chain returns the chain hash, it is determined that the chain is successful. The VC issuer assembles the user DID identifier and the issued VC certificate and returns it to the user after signing with the private key.
[0035] Furthermore, in step B5, the user uses the VC issuer's public key to verify the issuer's signature of the data packet and the issuer's signature in the VC certificate. After the verification is passed, the VC certificate is encrypted and saved locally.
[0036] 3. Data classification identification and on-chain evidence storage Furthermore, in step C1, the data provider marks the confidentiality level of the data according to the confidentiality field and confidentiality level of the evidence data. For example, the English letters A, B, C, ... are used to identify the business field, and the numbers 0, 1, 2, ... are used to identify the confidentiality level. Then S0 identifies completely non-confidential public data, SA0 identifies public data of business A, SB1 identifies first-level confidential data of business B, etc.
[0037] S0-level public data is uploaded to the chain in plain text, and other levels of confidential data use digital envelope technology to protect data transmission security. Specifically, confidential data is symmetrically encrypted using data keys and submitted to the chain in ciphertext. When a user applies for data, the data key is asymmetrically encrypted using the public key of the data applicant and returned to the applicant. Among them, data key generation and encryption and decryption, data encryption and decryption algorithms are encapsulated in the key SDK package and provided to users for local calls. Data keys can be updated using the following strategies: a. Update in time dimension, such as real-time update or update at intervals; b. Update by data dimension, such as updating every piece of data or updating every few pieces of data; Furthermore, in step C2, when the data provider applies for evidence storage on the data chain, it is necessary to submit the VC credential and the evidence data (public data in plain text or confidential data in ciphertext), assemble the two and sign them, and encrypt them with the public key of the VC verifier before submitting them.
[0038] Furthermore, in step C3, the VC verifier uses the private key to decrypt the application information submitted by the user, triggering the VC verification contract on the business chain. The verification logic is: a. User identity verification. Find the VC credential based on the VC number submitted by the user, find the DID document based on the DID identifier in the credential, and use the user's public key in the DID document to verify the user's signature to ensure that the current user's true identity is consistent with the identity of the DID and VC owner; b. VC issuer identity verification. Use the VC issuer public key to verify that the issuer signature in the VC certificate is a valid signature; c. VC validity period verification. Verify that the validity period in the VC certificate is greater than the current time to ensure that the VC certificate is within the validity period; d. VC authority verification. The business purpose of verifying the VC credential is data storage, and the user has the authority to store data in the target business chain.
[0039] e. If the permission verification succeeds, a verification success flag is returned to the system; if the verification fails, a verification failure flag is returned.
[0040] Furthermore, in step C4, if the user identity and authority verification is passed, the smart contract submits the evidence data to the corresponding business chain. When the business chain returns the chain hash, it is determined that the chain is successful and the chain hash is returned to the user.
[0041] 4. Business Identity Authentication and Data Acquisition Furthermore, in step D1, when the data applicant applies to the VC verifier for obtaining the evidence data, the VC credential is signed and encrypted using the public key of the VC verifier before submission.
[0042] Furthermore, in step D2, the VC verifier decrypts the application information submitted by the user and triggers the VC verification contract on the business chain. The contract verification logic is as follows: a. If the data application is for an enterprise, verify that the DID type is a personal DID, the data applicant and the data provider have the same company name, and according to the permission rules agreed upon in the business, the user's business identity matches the permission to obtain the data applied for; b. If the data application is between enterprises, verify that the DID type is enterprise DID, the data applicant and the data provider have different names, and according to the permission rules agreed upon in the business, the user's business identity matches the access rights for the data applied for; Further, in step D3, the VC verifies the contract successfully and prepares data: a. For public data, directly query the public data plaintext from the corresponding business chain, sign it with the private key and return it to the user; b. For confidential data, apply for the corresponding data key from the data provider, and query the confidential data ciphertext from the corresponding business chain. The data provider encrypts the data key with the public key of the data applicant, signs it with the private key and returns it to the VC verifier. The business system uses the data provider's public key to verify the signature. After the signature is verified, the data key ciphertext is assembled with the confidential data ciphertext, signed with the private key and returned to the user.
[0043] Furthermore, in step D4, the data applicant uses the VC verifier's public key to verify the signature of the data packet. After the signature is verified, the public data directly obtains the plain text; the confidential data calls the key SDK, uses the local private key to decrypt the data key ciphertext, and further uses the data key to decrypt the confidential data ciphertext to obtain the confidential data plain text.
[0044] The above description is only a specific implementation mode of the present invention, but the protection scope of the present invention is not limited thereto. Any technician familiar with the technical field can make equivalent substitutions or changes according to the technical solutions and novel concepts of the present invention within the technical scope disclosed by the present invention, which should be covered by the protection scope of the present invention.
Claims
1. A multi-level confidential data ownership confirmation and sharing management system, Features include The trusted digital identity application and issuance module is used to receive the identity authentication information submitted by the user, generate a public-private key pair locally, perform user identity verification, create trusted digital identity information after identity verification, submit it to the decentralized identity chain, and return the trusted digital identity information to the user terminal for storage; The verifiable business credential application and issuance module is used to receive the business credential application from the user to the verifiable business credential issuing agency, verify the validity of the user's trusted digital identity through the DID verification contract, and generate the corresponding verifiable business credential after the verification is passed. The generated business credential is submitted to the corresponding business chain and returned to the user terminal for encrypted storage; The data classification identification and on-chain evidence storage module is used to allow data providers to conduct confidentiality assessment, identification and encryption of confidential data, receive data on-chain evidence storage requests from data providers to the business system, and verify the user's identity validity and data operation permissions through a verifiable business verification contract. After the verification is passed, the evidence data is stored in the corresponding business chain and the on-chain hash is returned to the user; The business identity authentication and data acquisition module is used to process the data acquisition request from the data applicant to the business system, and verify the validity of the user's identity and data operation permissions. After the verification is passed, the data key and evidence data are prepared and returned to the data applicant for obtaining the plain text of the evidence data.
2. A multi-level confidential data ownership confirmation and sharing management method, Features The method is as follows: How to apply for and issue a trusted digital identity: A1. The user submits identity authentication information to the trusted digital identity platform client to apply for a DID; A2. The DID issuer generates a public-private key pair locally and completes the user's identity verification; A3. After the verification is passed, the DID issuer creates a trusted digital identity for the user; A4. The DID issuer submits the trusted digital identity information to the DID chain and returns it to the user; A5. Users save their trusted digital identity information locally; B1. The user applies for a business certificate from a verifiable business certificate issuing agency; B2. The verifiable business credential issuing authority verifies the validity of the user's trusted digital identity through the DID verification contract; B3. After the verification is passed, the verifiable business credential issuing authority will create a corresponding verifiable business credential for the user; B4. The verifiable business credential issuing authority submits the verifiable business credential to the corresponding business chain and returns it to the user; B5. The user encrypts and saves the verifiable business credentials locally; It also includes data classification identification and on-chain evidence storage methods: C1. The data provider evaluates the confidentiality of the data, identifies the data and encrypts the confidential data; C2. The data provider can apply for data on-chain evidence storage in the verifiable business system; C3. The verifiable business system verifies the user's identity validity and data operation authority through the verifiable business verification contract; C4. After verification, the evidence data is submitted to the corresponding business chain, and the chain hash is returned to the user; Including business identity authentication and data acquisition methods: D1. The data applicant applies to the business system for data; D2. The business system verifies the validity of the user's identity and data operation authority through a verifiable business verification contract; D3. After verification, the data key and evidence data are prepared and returned to the applicant; D4. The data applicant obtains the plain text of the stored data.
3. A multi-level confidential data rights confirmation and sharing management method as claimed in claim 2, It is characterized in that In step B2, the verifiable business credential issuing agency uses the private key to decrypt the application information submitted by the user and triggers the DID verification contract on the DID chain. The verification logic is: B2.
1. User identity verification: Find the DID document based on the DID identifier submitted by the user, and use the user's public key in the document to verify the user's signature to ensure that the current user is consistent with the DID identity owner; B2.2.DID issuer identity verification: Use the DID issuer public key to verify that the verifiable business credential issuing authority signature in the DID document is a valid signature; B2.3.DID validity period verification: Verify that the DID validity period in the DID document is greater than the current time to ensure that the DID is within the validity period; B2.
4. If the verification is successful, the verification success mark and DID validity period will be returned to the verifiable business credential issuing authority system; if the verification fails, the verification failure mark will be returned.
4. A multi-level confidential data rights confirmation and sharing management method as claimed in claim 2, It is characterized in that In step B3, the verifiable business credential issuing authority issues a verifiable business credential to the user based on the user's DID type and business application information; the verifiable business credential includes but is not limited to the verifiable business number, user DID identifier and type, business purpose, data applicant, data provider, and business identity information; wherein the verifiable business validity period must be within the DID validity period; business purposes can be divided into data storage and data acquisition; if it is data acquisition, the data applicant and data provider company names must be stated; the business identity is the user's identity level in the current business, and the same user can have one or more business identities, and the final data authority is the union of the data permissions owned by each business identity; the verifiable business credential issuing authority uses a private key to sign the credential information and attaches the signature to the verifiable business credential; The business identity identification strategy is as follows: B3.1 Personal DID: Issued for business credentials within the company to which it belongs. The identity is set based on the user's relevance to the business and the data confidentiality level; B3.2 Enterprise DID: Issued for business credentials between enterprises. The identity is set based on the business relevance between the user's enterprise and the data provider and the confidentiality level of the data.
5. A multi-level confidential data rights confirmation and sharing management method as claimed in claim 2, It is characterized in that In the step C1, the data provider marks the confidentiality level of the data according to the confidentiality field and confidentiality level of the stored data; English letters and numbers are used to mark the confidentiality level; Public data marked as completely non-confidential will be uploaded to the blockchain in plain text, and other levels of confidential data will be protected by digital envelope technology to ensure data transmission security; the confidential data will be symmetrically encrypted using the data key and submitted as ciphertext to the blockchain. When a user applies for data, the data key will be asymmetrically encrypted using the public key of the data applicant and returned to the applicant; data key generation and encryption and decryption, data encryption and decryption algorithms are encapsulated in the key SDK package and provided to users for local calls; data keys are updated using the following strategies: C1.1 Update in time dimension, including real-time update or update at intervals; C1.2 Updated by data dimension, including updating every piece of data or every few pieces of data; When a data provider applies for on-chain evidence storage, it is necessary to submit a verifiable business certificate and evidence data, assemble the verifiable business certificate and evidence data, sign them, and encrypt them with the public key of the verifiable business system before submitting them; In step C3, the verifiable business system uses the private key to decrypt the application information submitted by the user, triggering the verifiable business system verification contract on the business chain. The verification logic is: C3.1 User identity verification: Find the verifiable business credential based on the verifiable business number submitted by the user, find the DID document based on the DID identifier in the credential, and use the user's public key in the DID document to verify the user's signature to ensure that the current user's true identity is consistent with the DID and the verifiable business owner's identity; C3.2 Verifiable Business Authority Authentication: Use the public key of the Verifiable Business Authority to verify that the authority signature in the Verifiable Business Credential is a valid signature; C3.3 Verification of the validity period of verifiable business: Verify that the validity period in the verifiable business certificate is greater than the current time to ensure that the verifiable business certificate is within the validity period; C3.4 Verifiable business authority verification: Verify that the business purpose of the verifiable business credential is data storage, and that the user has the authority to store data in the target business chain; C3.5 If verification is successful, a verification success indicator is returned to the system; if verification fails, a verification failure indicator is returned.
6. A multi-level confidential data rights confirmation and sharing management method as claimed in claim 5, It is characterized in that In step D2, the verifiable business verification system decrypts the application information submitted by the user and triggers the VC verification contract on the business chain. The contract verification logic refers to steps C3.1-C3.5 in C3, where the verifiable business authority verification logic is as follows, and the rest of the verification logic remains unchanged: D2.1 If the data application is for an enterprise, verify that the DID type is a personal DID, the data applicant and the data provider have the same company name, and according to the permission rules agreed upon in the business, the user's business identity matches the permission to obtain the data applied for; D2.2 If the data application is between enterprises, verify that the DID type is enterprise DID, the data applicant and the data provider have different names, and according to the permission rules agreed upon in the business, the user's business identity matches the access rights for the data applied for; In step D3, the data can be prepared after the business verification contract verification is successful: D3.1 For public data, query the plain text of the public data directly from the corresponding business chain, sign it with the private key and return it to the user; D3.2 For confidential data, apply for the corresponding data key from the data provider and query the confidential data ciphertext from the corresponding business chain; the data provider encrypts the data key with the public key of the data applicant, signs it with the private key and returns it to the verifiable business system. The business system verifies the signature with the public key of the data provider. After the signature is verified, the data key ciphertext is assembled with the confidential data ciphertext, signed with the private key and returned to the user.
Citation Information
Cited By
Data right confirmation system and data right confirmation method
CN120785595A
