Accredential storage method and system based on distributed real-name authentication digital identity and storage medium

Abstract

The invention discloses an evidence storage method and system based on a distributed real-name authentication digital identity and a storage medium. According to the embodiment of the invention, the file identification information and the user real name information of the target file are acquired by the client of the user, and the evidence storage information for the target file is generated based on the user public key and the file identification information, and is sent to the evidence storage server; therefore, the evidence storage server can call an evidence storage contract deployed on an evidence storage block chain according to the evidence storage information, so as to execute an evidence storage transaction based on the evidence storage information, and generate evidence storage confirmation information to identify that the evidence storage information is recorded on the evidence storage block chain. According to the evidence storage method based on the distributed real-name authentication digital identity, the target file of the user can be subjected to evidence storage processing on the evidence storage block chain by using the real-name DID information of the user, and the user experience is improved. The evidence storage confirmation information of the target file of the user is generated based on the real-name DID information of the user, so that right confirmation processing based on the real-name identity of the user is realized, and the safety and accuracy of right confirmation of the user data are ensured.

Description

Technical Field

[0001] The present application relates to the field of network technology, and in particular to a method and system for storing digital identities based on distributed real-name authentication, and a storage medium. Background Art

[0002] With the continuous advancement of trusted technologies, especially blockchain technology, distributed digital identity (DID) application solutions have emerged, which has brought revolutionary changes to more and more traditional IT systems. These systems can now use distributed digital identities to enable users to independently control their personal data and assets, and realize decentralized data sharing across departments, industries, and regions. In addition, as the most authoritative and influential standardization organization in the field of Web technology, the World Wide Web Consortium (W3C) launched the first DID standard specification in 2019, which marks an important step forward in the normalization and standardization of DID technology.

[0003] With the widespread use of DID identities, especially the emergence of real-name DID identities, users can also have real-name authenticated digital identities on Internet platforms, but users can often only use this identity to log in and other operations on the Internet, and cannot use it in more application scenarios. In particular, when users send their personal data through the Internet, due to the tamperability of electronic data, it is difficult for other users to confirm the authenticity of the personal data sent through the Internet. For this reason, a technical solution is needed that can use the user's real-name digital identity to store personal data. Summary of the invention

[0004] The embodiments of the present application provide a method and system for storing evidence based on a distributed real-name authentication digital identity, as well as a storage medium, to address the defect in the prior art that real-name identity cannot be used to confirm the ownership of personal data.

[0005] To achieve the above-mentioned purpose, the embodiment of the present application provides a method for storing digital identity based on distributed real-name authentication, the method comprising:

[0006] The user's client obtains the file identification information and user real-name information of the target file, wherein the user real-name information includes the user's real-name DID identification and at least one user public key;

[0007] The client generates evidence information based on the user public key and the file identification information, and sends the information to the evidence server;

[0008] The evidence server calls the evidence contract deployed on the evidence blockchain to generate evidence confirmation information according to the evidence information, wherein the evidence confirmation information indicates that the evidence information is recorded (for example, a block is generated based on consensus) on the evidence blockchain;

[0009] The evidence server receives the evidence confirmation information and the file identification information from the evidence blockchain and forwards them to the client.

[0010] The embodiment of the present application also provides a distributed real-name authentication digital identity based evidence storage system, including: a client, an evidence storage server and an evidence storage blockchain,

[0011] The client is used to obtain file identification information and user real-name information of the target file, wherein the user real-name information includes the user's real-name DID identifier and at least one user public key; generate evidence information based on the user public key and the file identification information to send to the evidence server;

[0012] The evidence server is used to call the evidence contract deployed on the evidence blockchain to generate evidence confirmation information according to the evidence information, wherein the evidence confirmation information indicates that the evidence information is recorded (for example, a block is generated based on consensus) on the evidence blockchain, and send the evidence confirmation information and the file identification information to the client;

[0013] The evidence blockchain is used to generate evidence confirmation information based on the evidence information, and send the evidence confirmation information and the file identification information to the evidence blockchain.

[0014] The present application also provides an electronic device, including:

[0015] Memory, used to store programs;

[0016] A processor is used to run the program stored in the memory, and when the program is running, the method for storing digital identity based on distributed real-name authentication provided in the embodiment of the present application is executed.

[0017] An embodiment of the present application also provides a computer-readable storage medium on which a computer program executable by a processor is stored, wherein when the program is executed by the processor, the method for storing digital identity based on distributed real-name authentication as provided in the embodiment of the present application is implemented.

[0018] The evidence storage method, system and storage medium based on distributed real-name authentication digital identity provided in the embodiment of the present application obtain the file identification information and user real-name information of the target file through the user's client, and generate evidence information for the target file based on the user's public key and file identification information, and send it to the evidence server, so that the evidence server can call the evidence contract deployed on the evidence blockchain according to the evidence information to execute the evidence transaction based on the evidence information, and generate evidence confirmation information to identify that the evidence information is recorded on the evidence blockchain, and forward the evidence confirmation information and file identification information to the client through the evidence server. Therefore, according to the evidence storage method based on distributed real-name authentication digital identity in the embodiment of the present application, the user's real-name DID information can be used to store the user's target file on the evidence blockchain, so that the evidence confirmation information of the user's target file is generated based on the user's real-name DID information, thereby realizing the right confirmation processing based on the user's real-name identity, ensuring the security and accuracy of the right confirmation of user data.

[0019] The above description is only an overview of the technical solution of the present application. In order to more clearly understand the technical means of the present application, it can be implemented in accordance with the contents of the specification. In order to make the above and other purposes, features and advantages of the present application more obvious and easy to understand, the specific implementation methods of the present application are listed below. BRIEF DESCRIPTION OF THE DRAWINGS

[0020] Various other advantages and benefits will become apparent to those of ordinary skill in the art by reading the detailed description of the preferred embodiments below. The accompanying drawings are only for the purpose of illustrating the preferred embodiments and are not to be considered as limiting the present application. Also, the same reference symbols are used throughout the accompanying drawings to represent the same components. In the accompanying drawings:

[0021] Figure 1 It is a schematic diagram showing an application scenario of a distributed real-name authentication digital identity storage solution according to an embodiment of the present application;

[0022] Figure 2 A flowchart of an embodiment of a method for storing digital identity based on distributed real-name authentication provided by this application;

[0023] Figure 3 A schematic diagram of the structure of the evidence storage system based on distributed real-name authentication digital identity provided for this application;

[0024] Figure 4 A schematic diagram of the structure of an electronic device embodiment provided in this application. DETAILED DESCRIPTION

[0025] The exemplary embodiments of the present disclosure will be described in more detail below with reference to the accompanying drawings. Although the exemplary embodiments of the present disclosure are shown in the accompanying drawings, it should be understood that the present disclosure can be implemented in various forms and should not be limited by the embodiments set forth herein. On the contrary, these embodiments are provided to enable a more thorough understanding of the present disclosure and to fully convey the scope of the present disclosure to those skilled in the art.

[0026] Embodiment 1

[0027] The solution provided in the embodiments of the present application can be applied to any data system or server with encryption and decryption functions.

[0028] With the continuous advancement of trusted technologies, especially blockchain technology, distributed digital identity (DID) application solutions have emerged, which has brought revolutionary changes to more and more traditional IT systems. These systems can now use distributed digital identities to enable users to independently control their personal data and assets, and realize decentralized data sharing across departments, industries, and regions. In addition, as the most authoritative and influential standardization organization in the field of Web technology, the World Wide Web Consortium (W3C) launched the first DID standard specification in 2019, which marks an important step forward in the normalization and standardization of DID technology.

[0029] With the widespread use of DID identities, especially the emergence of real-name DID identities, users can also have real-name authenticated digital identities on Internet platforms, but users can often only use this identity to log in and other operations on the Internet, and cannot use it in more application scenarios. In particular, when users send their personal data over the Internet, due to the tamperability of electronic data, it is difficult for other users to confirm the authenticity of the personal data sent over the Internet.

[0030] To this end, this application proposes a storage solution based on distributed real-name authentication digital identity, which can store and confirm the ownership of target files generated or obtained by users through their clients, such as photos, documents, etc., by using the user's real-name authentication digital identity. Figure 1 As shown in Figure 1 is a schematic diagram showing a scenario of a digital identity storage solution based on distributed real-name authentication according to an embodiment of the present application. Figure 1In the scenario shown in , the user can use the client of the application program of the evidence storage method based on the distributed real-name authentication digital identity of the embodiment of the present application to generate or obtain the target file to be stored from the outside. For example, the user can use the camera application program in the client to take pictures, and use the generated photo file as the target file to be stored. In the prior art, after the user takes a digital photo using his own client, the photo will be accompanied by corresponding photo information, such as the shooting time, the device identification of the shooting device, and the parameters of the photo, and when the user transmits the photo obtained by taking such a photo through the Internet, other users who receive the photo can understand the shooting situation of the photo by viewing the photo information, especially confirm that the photo is taken by the user's device. However, due to the property of the electronic file of the digital photo, that is, the tamperability, when it is transmitted via the Internet, the person who obtains or maliciously intercepts the file can modify the file through various digital tools, resulting in other users who finally obtain the photo being unable to determine whether the photo is taken by the user from the photo information itself, or confirm whether the photo is an original file without tampering.

[0031] To this end, according to an embodiment of the present application, after the user generates or obtains a target file such as a photo from the outside through various applications in its client, the file identification information can be first obtained based on the target file, for example, the photo ID of the photo as described above, which can be generated based on the hardware information of the client or based on the photo application, as long as the ID can uniquely identify the photo. Then the client can obtain the real-name information of the user based on the user's information, such as the account information of the user logging into the application or logging into the client. For example, in an embodiment of the present application, the client can obtain information such as the real-name DID identity issued to the user by an authority, for example, in an embodiment of the present application, the user's real-name information can include the user's real-name DID identification and at least one user public key. Specifically, in an embodiment of the present application, the user can store the real-name DID identification obtained from the authority and the corresponding real-name DID document on the client, so that the real-name DID identification stored locally can be directly obtained through the client, and a user public key can be determined from the corresponding real-name DID document as the public key used by the user to log in to the target blockchain, and the corresponding first private key can also be obtained according to the first public key determined in the DID document. For example, in an embodiment of the present application, the public key information of the first public key may be the public key index of the first public key in the user's real-name DID document.

[0032] Then the user can use the first public key determined in the DID document on its client to generate the evidence information of the target file with the file identification information of the target file. For example, in an embodiment of the present application, the client can use an application based on the distributed real-name authentication digital identity evidence method of the present application embodiment to calculate the hash value of the target file and use it as the file identification information of the target file. In addition, in an embodiment of the present application, the client can use the first private key obtained from the first public key determined from the DID document as above to sign the file identification information to obtain the first signature data, and then generate the evidence information based on the first signature data, the hash value obtained based on the file information of the target file as above, the real-name DID identification of the user, and the public key information of the first public key. In an embodiment of the present application, since the evidence information contains the real-name DID information of the user and the file identification information that uniquely identifies the target file, it can allow the user who receives the file to confirm the ownership or source of the target file through such evidence information. However, in this case, since the evidence information still has the risk of being tampered with, and the real-name DID information of the user contained in the evidence information also needs to be verified to confirm the identity of the user.

[0033] Therefore, in an embodiment of the present application, the client can send the evidence information generated in this way to the evidence server, which can be a server set outside the evidence blockchain. And the evidence server can call the evidence contract deployed on the evidence blockchain according to the received evidence information. For example, the evidence server can send an evidence contract call instruction to the evidence blockchain. In an embodiment of the present application, the evidence contract call instruction can include the evidence information, the call address of the evidence contract, and the real-name DID identifier, so that the evidence blockchain can call the evidence contract based on the evidence contract call instruction to execute the corresponding evidence transaction on each node of the evidence blockchain. When a block corresponding to the evidence transaction is generated on each node, the block generation time and the transaction result of the evidence transaction can be written into the block as an evidence record, and the evidence confirmation information is generated based on the block generation time and the record information of the evidence record. Therefore, in an embodiment of the present application, the evidence confirmation information can indicate that the evidence information is recorded on the evidence blockchain. In addition, in an embodiment of the present application, the evidence blockchain can be a blockchain operated by an authoritative organization to issue real-name authenticated DID identities to users, and therefore, when calling the evidence contract, the evidence blockchain can verify the user's real-name identity based on the real-name DID identifier contained in the evidence contract call instruction, and execute the corresponding evidence transaction processing after the verification is passed.

[0034] Then, the evidence server can also receive evidence confirmation information and file identification information from the evidence blockchain and forward it to the client, and the client can store the evidence confirmation information in association with the target file based on the received file identification information, so that the stored target file has the evidence confirmation information recorded on the evidence blockchain, and therefore, when the user transmits the target file with the evidence confirmation information stored in this way through the Internet through the client, another user who receives the target file can send a verification request to the evidence blockchain based on the file identification information of the target file, and the evidence blockchain can query the evidence confirmation information of the target file on the evidence blockchain based on the file identification information, and send the evidence confirmation information to the user who received the target file, so that the user can compare the received evidence confirmation information with the evidence confirmation information received along with the target file, so that when the comparison result is consistent, it can be confirmed that the target file is the original file generated or obtained by the original user on its client.

[0035] In addition, in an embodiment of the present application, when the user obtains the target file and wants to perform the ownership confirmation process, it can be checked whether the real-name DID identity information has been stored. For example, when the user checks and confirms that he has not yet applied for a real-name DID identity, the user can send a real-name DID identification application request to, for example, a proof blockchain through a proof server. In an embodiment of the present application, the real-name DID identification application request may at least include the user's identity information; the proof blockchain generates a real-name DID identification and a real-name DID document for the user based on the real-name DID identification application request, and stores the real-name DID document in the blockchain, wherein the real-name DID document contains at least a first public key, and then the real-name DID identification and the real-name DID document can be sent to the client through the proof server.

[0036] The evidence storage scheme based on distributed real-name authentication digital identity provided by the embodiment of the present application obtains the file identification information and user real-name information of the target file by the user's client, and generates evidence information for the target file based on the user's public key and file identification information, and sends it to the evidence server, so that the evidence server can call the evidence contract deployed on the evidence blockchain according to the evidence information to execute the evidence transaction based on the evidence information, and generate evidence confirmation information to identify that the evidence information is recorded on the evidence blockchain, and forward the evidence confirmation information and file identification information to the client through the evidence server. Therefore, according to the evidence storage method based on distributed real-name authentication digital identity according to the embodiment of the present application, the user's real-name DID information can be used to perform evidence processing on the user's target file on the evidence blockchain, so that the evidence confirmation information of the user's target file is generated based on the user's real-name DID information, thereby realizing the right confirmation processing based on the user's real-name identity, ensuring the security and accuracy of the right confirmation of user data.

[0037] The above embodiments are illustrations of the technical principles and exemplary application frameworks of the embodiments of the present application. The specific technical solutions of the embodiments of the present application are further described in detail below through multiple embodiments.

[0038] Embodiment 2

[0039] Figure 2 This is a flowchart of an embodiment of a method for storing digital identities based on distributed real-name authentication provided by this application. The execution subject of this method can be various terminals or server devices with data encryption and decryption capabilities deployed on the blockchain, or it can be a device or chip integrated on these devices. Figure 2 As shown, the evidence storage method based on distributed real-name authentication digital identity includes the following steps:

[0040] S201, the user's client obtains file identification information of the target file and user real name information.

[0041] In step S201, the user can generate or obtain a target file such as a photo from the outside through various applications in his client, and obtain its file identification information based on the target file. For example, when the user uses the photo application in the client to take a photo, the photo ID can be obtained based on the taken photo. The ID can be generated based on the hardware information of the client or based on the photo application, as long as the ID can uniquely identify the photo.

[0042] The client can also obtain the real-name information of the user based on the information of the user, such as the account information of the user logging into the application or logging into the client. For example, in an embodiment of the present application, the client can obtain information such as the real-name DID identity issued to the user by an authority. For example, in an embodiment of the present application, the user's real-name information can include the user's real-name DID and at least one user public key.

[0043] Specifically, in the embodiment of the present application, the user can store the real-name DID identification and the corresponding real-name DID document obtained from the authority on the client, so that the local stored real-name DID identification can be directly obtained through the client in step S201, and a user public key can be determined from the corresponding real-name DID document as the public key used by the user to log in to the target blockchain, and the corresponding first private key can also be obtained according to the first public key determined in the DID document. For example, in the embodiment of the present application, the public key information of the first public key can be the public key index of the first public key in the user's real-name DID document.

[0044] S202, the client generates evidence information based on the user public key and file identification information, and sends it to the evidence server.

[0045] In step S202, the user can use the first public key determined from the DID document in step S201 and the file identification information of the target file obtained on the client to generate the evidence information of the target file. For example, in an embodiment of the present application, in step S202, the client can use an application based on the distributed real-name authentication digital identity evidence storage method of the embodiment of the present application to calculate the hash value of the target file and use it as the file identification information of the target file.

[0046] In addition, in step S202, the client can use the first private key obtained from the first public key determined from the DID document as above to sign the file identification information to obtain the first signature data, and then generate evidence information based on the first signature data, the hash value obtained based on the file information of the target file as above, the user's real-name DID identification, and the public key information of the first public key. In an embodiment of the present application, since the evidence information contains the user's real-name DID information and the file identification information that uniquely identifies the target file, it can allow the user who receives the file to confirm the ownership or source of the target file through such evidence information. However, in this case, since the evidence information is still at risk of being tampered with, and the user's real-name DID information contained in the evidence information also needs to be verified to confirm the identity of the user.

[0047] S203, the evidence server calls the evidence contract deployed on the evidence blockchain to generate evidence confirmation information based on the evidence information.

[0048] In step S202, the client sends such evidence information to the evidence server, and in step S203, the evidence server can call the evidence contract deployed on the evidence blockchain according to the received evidence information. For example, the evidence server can send an evidence contract call instruction to the evidence blockchain. In an embodiment of the present application, the evidence contract call instruction can include the evidence information, the call address of the evidence contract, and the real-name DID identifier, so that the evidence blockchain can call the evidence contract based on the evidence contract call instruction to execute the corresponding evidence transaction on each node of the evidence blockchain. When a block corresponding to the evidence transaction is generated on each node, the block generation time and the transaction result of the evidence transaction can be written into the block as an evidence record, and the evidence confirmation information is generated based on the block generation time and the record information of the evidence record. In an embodiment of the present application, the evidence confirmation information indicates that the evidence information is recorded (for example, a block is generated based on consensus) on the evidence blockchain.

[0049] Therefore, in the embodiment of the present application, the evidence confirmation information can identify that the evidence information is recorded on the evidence blockchain. In addition, in the embodiment of the present application, the evidence blockchain can be a blockchain operated by an authority to issue a real-name authenticated DID identity to a user, and therefore, when calling the evidence contract, the evidence blockchain can verify the user's real-name identity based on the real-name DID identifier contained in the evidence contract call instruction, and then execute the corresponding evidence transaction processing after the verification is passed.

[0050] S204, the evidence server receives the evidence confirmation information and file identification information from the evidence blockchain and forwards it to the client.

[0051] In step S204, the evidence server can receive the evidence confirmation information and file identification information from the evidence blockchain and forward them to the client, and the client can store the evidence confirmation information in association with the target file based on the received file identification information, so that the stored target file has the evidence confirmation information recorded on the evidence blockchain, and therefore, when the user transmits the target file with the evidence confirmation information stored in this way through the Internet through the client, another user who receives the target file can send a verification request to the evidence blockchain based on the file identification information of the target file, and the evidence blockchain can query the evidence confirmation information of the target file on the evidence blockchain based on the file identification information, and send the evidence confirmation information to the user who received the target file, so that the user can compare the received evidence confirmation information with the evidence confirmation information received along with the target file, and when the comparison result is consistent, it can be confirmed that the target file is the original file generated or obtained by the original user on its client.

[0052] In addition, in an embodiment of the present application, when the user obtains the target file and wants to perform the ownership confirmation process, it can be checked whether the real-name DID identity information has been stored. For example, when the user checks and confirms that he has not yet applied for a real-name DID identity, the user can send a real-name DID identification application request to, for example, a proof blockchain through a proof server. In an embodiment of the present application, the real-name DID identification application request may at least include the user's identity information; the proof blockchain generates a real-name DID identification and a real-name DID document for the user based on the real-name DID identification application request, and stores the real-name DID document in the blockchain, wherein the real-name DID document contains at least a first public key, and then the real-name DID identification and the real-name DID document can be sent to the client through the proof server.

[0053] The evidence storage method based on distributed real-name authentication digital identity provided in the embodiment of the present application obtains the file identification information and user real-name information of the target file by the user's client, and generates evidence information for the target file based on the user's public key and file identification information, and sends it to the evidence server, so that the evidence server can call the evidence contract deployed on the evidence blockchain according to the evidence information to execute the evidence transaction based on the evidence information, and generate evidence confirmation information to identify that the evidence information is recorded on the evidence blockchain, and forward the evidence confirmation information and file identification information to the client through the evidence server. Therefore, according to the evidence storage method based on distributed real-name authentication digital identity in the embodiment of the present application, the user's real-name DID information can be used to perform evidence processing on the user's target file on the evidence blockchain, so that the evidence confirmation information of the user's target file is generated based on the user's real-name DID information, thereby realizing the right confirmation processing based on the user's real-name identity, ensuring the security and accuracy of the right confirmation of user data.

[0054] Embodiment 3

[0055] Figure 3 The schematic diagram of the structure of the evidence storage system based on the distributed real-name authentication digital identity provided by the present application can be used to implement, for example, Figure 2 The embodiment of the present application provides a method for storing evidence based on a distributed real-name authentication digital identity. The system for storing evidence based on a distributed real-name authentication digital identity may include: a client 31, an evidence server 32, and an evidence blockchain 33, wherein the evidence blockchain 33 may include multiple nodes.

[0056] The client 31 can be used to obtain the file identification information and user real name information of the target file; generate evidence information based on the user public key and the file identification information, and send it to the evidence server.

[0057] In an embodiment of the present application, a user can generate or obtain a target file such as a photo from the outside through various applications in his client 31, and obtain its file identification information based on the target file. For example, when a user uses a photo application in the client 31 to take a photo, a photo ID can be obtained based on the taken photo. The ID can be generated based on the hardware information of the client 31, or based on the photo application, as long as the ID can uniquely identify the photo.

[0058] The client 31 may also obtain the real-name information of the user based on the information of the user, such as the account information of the user logging into the application or logging into the client. For example, in the embodiment of the present application, the client 31 may obtain information such as the real-name DID identity issued to the user by an authority. For example, in the embodiment of the present application, the user real-name information may include the user's real-name DID and at least one user public key.

[0059] Specifically, in the embodiment of the present application, the user can store the real-name DID identification and the corresponding real-name DID document obtained from the authority on the client 31, so that the real-name DID identification stored locally can be directly obtained through the client 31, and a user public key can be determined from the corresponding real-name DID document as the public key used by the user to log in to the target blockchain, and the corresponding first private key can also be obtained according to the first public key determined in the DID document. For example, in the embodiment of the present application, the public key information of the first public key can be the public key index of the first public key in the user's real-name DID document.

[0060] The user can use the first public key determined from the DID document and the obtained file identification information of the target file on the client 31 to generate the evidence information of the target file. For example, in an embodiment of the present application, the client 31 can calculate the hash value of the target file and use it as the file identification information of the target file.

[0061] In addition, the client 31 can use the first private key obtained from the first public key determined from the DID document as above to sign the file identification information to obtain the first signature data, and then generate evidence information based on the first signature data, the hash value obtained based on the file information of the target file as above, the user's real-name DID identification, and the public key information of the first public key. In an embodiment of the present application, since the evidence information contains the user's real-name DID information and the file identification information that uniquely identifies the target file, it can allow the user who receives the file to confirm the ownership or source of the target file through such evidence information. However, in this case, since the evidence information is still at risk of being tampered with, and the user's real-name DID information contained in the evidence information also needs to be verified to confirm the identity of the user.

[0062] The evidence server 32 can be used to call the evidence contract deployed on the evidence blockchain to generate evidence confirmation information based on the evidence information and send the evidence confirmation information and file identification information to the client 31; the evidence server 32 calls the evidence contract deployed on the evidence blockchain 33 to generate evidence confirmation information based on the evidence information.

[0063] After the client 31 sends such evidence information to the evidence server 32, the evidence server 32 can call the evidence contract deployed on the evidence blockchain 33 according to the received evidence information. For example, the evidence server 32 can send an evidence contract call instruction to the evidence blockchain 33. In the embodiment of the present application, the evidence contract call instruction can include the evidence information, the call address of the evidence contract, and the real-name DID identifier, so that the evidence blockchain 33 can call the evidence contract based on the evidence contract call instruction to execute the corresponding evidence transaction on each node of the evidence blockchain 33. When a block corresponding to the evidence transaction is generated on each node, the block generation time and the transaction result of the evidence transaction can be written into the block as an evidence record, and the evidence confirmation information is generated based on the block generation time and the record information of the evidence record. In the embodiment of the present application, the evidence confirmation information indicates that the evidence information is recorded (for example, the block is generated based on consensus) on the evidence blockchain 33.

[0064] Therefore, in the embodiment of the present application, the evidence confirmation information can identify that the evidence information is recorded on the evidence blockchain 33. In addition, in the embodiment of the present application, the evidence blockchain 33 can be a blockchain operated by an authority to issue a real-name authenticated DID identity to a user, and therefore, the evidence blockchain 33 can verify the real-name identity of the user based on the real-name DID identifier contained in the evidence contract call instruction when calling the evidence contract, and then execute the corresponding evidence transaction processing after the verification is passed.

[0065] The evidence server 32 can receive the evidence confirmation information and file identification information from the evidence blockchain 33 and forward it to the client 31, and the client 31 can store the evidence confirmation information in association with the target file based on the received file identification information, so that the stored target file has the evidence confirmation information recorded on the evidence blockchain 33, and therefore, when the user transmits the target file with the evidence confirmation information stored in this way through the Internet through the client 31, another user who receives the target file can send a verification request to the evidence blockchain 33 based on the file identification information of the target file, and the evidence blockchain 33 can query the evidence confirmation information of the target file on the evidence blockchain based on the file identification information, and send the evidence confirmation information to the user who received the target file, so that the user can compare the received evidence confirmation information with the evidence confirmation information received along with the target file, and when the comparison result is consistent, it can be confirmed that the target file is the original file generated or obtained by the original user on its client.

[0066] In addition, in an embodiment of the present application, when the user obtains the target file and wants to perform the rights confirmation process, it can be checked whether the real-name DID identity information has been stored. For example, when the user checks and confirms that he has not yet applied for a real-name DID identity, the user can send a real-name DID identification application request to, for example, a proof blockchain through a proof server. In an embodiment of the present application, the real-name DID identification application request may at least include the user's identity information; the proof blockchain generates a real-name DID identification and a real-name DID document for the user according to the real-name DID identification application request, and stores the real-name DID document in the blockchain, wherein the real-name DID document contains at least a first public key and a first private key, that is, a pair of keys. The proof blockchain can then encrypt the first private key using the user's public key that the user has sent in advance to the real-name digital identity blockchain, and then send the real-name DID identification and the real-name DID document to the client through the proof server.

[0067] The evidence storage system based on distributed real-name authentication digital identity provided by the embodiment of the present application obtains the file identification information and user real-name information of the target file by the user's client, and generates evidence information for the target file based on the user's public key and file identification information, and sends it to the evidence storage server, so that the evidence storage server can call the evidence storage contract deployed on the evidence storage blockchain according to the evidence storage information to execute the evidence storage transaction based on the evidence storage information, and generate evidence storage confirmation information to identify that the evidence storage information is recorded on the evidence storage blockchain, and forward the evidence storage confirmation information and file identification information to the client through the evidence storage server. Therefore, according to the evidence storage method based on distributed real-name authentication digital identity according to the embodiment of the present application, the user's real-name DID information can be used to perform evidence storage processing on the user's target file on the evidence storage blockchain, so that the evidence storage confirmation information of the user's target file is generated based on the user's real-name DID information, thereby realizing the right confirmation processing based on the user's real-name identity, and ensuring the security and accuracy of the right confirmation of user data.

[0068] Embodiment 4

[0069] The above describes the internal functions and structure of the evidence storage system based on distributed real-name authentication digital identity, which can be implemented as an electronic device. Figure 4 This is a schematic diagram of the structure of an electronic device embodiment provided by this application. Figure 4 As shown, the electronic device includes a memory 41 and a processor 42 .

[0070] The memory 41 is used to store programs. In addition to the above programs, the memory 41 can also be configured to store various other data to support operations on the electronic device. Examples of such data include instructions for any application or method operating on the electronic device, contact data, phone book data, messages, pictures, videos, etc.

[0071] The memory 41 can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic disk or optical disk.

[0072] The processor 42 is not limited to a processor (CPU), but may also be a processing chip such as a graphics processing unit (GPU), a field programmable gate array (FPGA), an embedded neural network processor (NPU) or an artificial intelligence (AI) chip. The processor 42 is coupled to the memory 41 to execute the program stored in the memory 41 to execute the digital identity storage method based on distributed real-name authentication of the above-mentioned embodiment 2.

[0073] Further, if Figure 4 As shown, the electronic device may also include: a communication component 43, a power component 44, an audio component 45, a display 46 and other components. Figure 4 Only some components are shown schematically, which does not mean that the electronic device only includes Figure 4 Components shown.

[0074] The communication component 43 is configured to facilitate wired or wireless communication between the electronic device and other devices. The electronic device can access a wireless network based on a communication standard, such as WiFi, 3G, 4G or 5G, or a combination thereof. In an exemplary embodiment, the communication component 43 receives a broadcast signal or broadcast-related information from an external broadcast management system via a broadcast channel. In an exemplary embodiment, the communication component 43 also includes a near field communication (NFC) module to facilitate short-range communication. For example, the NFC module can be implemented based on radio frequency identification (RFID) technology, infrared data association (IrDA) technology, ultra-wideband (UWB) technology, Bluetooth (BT) technology and other technologies.

[0075] The power supply assembly 44 provides power to various components of the electronic device. The power supply assembly 44 may include a power management system, one or more power supplies, and other components associated with generating, managing, and distributing power to the electronic device.

[0076] The audio component 45 is configured to output and / or input audio signals. For example, the audio component 45 includes a microphone (MIC), and when the electronic device is in an operating mode, such as a call mode, a recording mode, and a voice recognition mode, the microphone is configured to receive an external audio signal. The received audio signal can be further stored in the memory 41 or sent via the communication component 43. In some embodiments, the audio component 45 also includes a speaker for outputting audio signals.

[0077] The display 46 includes a screen, which may include a liquid crystal display (LCD) and a touch panel (TP). If the screen includes a touch panel, the screen may be implemented as a touch screen to receive input signals from a user. The touch panel includes one or more touch sensors to sense touch, slide, and gestures on the touch panel. The touch sensor may not only sense the boundary of a touch or slide action, but also detect the duration and pressure associated with the touch or slide operation.

[0078] Those skilled in the art can understand that all or part of the steps of implementing the above-mentioned method embodiments can be completed by hardware related to program instructions. The aforementioned program can be stored in a computer-readable storage medium. When the program is executed, the steps of the above-mentioned method embodiments are executed; and the aforementioned storage medium includes: ROM, RAM, disk or optical disk and other media that can store program codes.

[0079] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention, rather than to limit it. Although the present invention has been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the aforementioned embodiments, or replace some or all of the technical features therein with equivalents. However, these modifications or replacements do not cause the essence of the corresponding technical solutions to deviate from the scope of the technical solutions of the embodiments of the present invention.

Claims

1. A method for storing digital identity based on distributed real-name authentication, characterized in that: The method comprises: The user's client obtains the file identification information and user real-name information of the target file, wherein the user real-name information includes the user's real-name DID identification and at least one user public key; The client generates evidence information based on the user public key and the file identification information, and sends the information to the evidence server; The evidence server calls the evidence contract deployed on the evidence blockchain to generate evidence confirmation information according to the evidence information, wherein the evidence confirmation information indicates that the evidence information is recorded (for example, a block is generated based on consensus) on the evidence blockchain; The evidence server receives the evidence confirmation information and the file identification information from the evidence blockchain and forwards them to the client.

2. The method for storing digital identity based on distributed real-name authentication according to claim 1 is characterized in that: Before the user's client obtains the file identification information and the user's real name information of the target file, the method further includes: The client obtains the target file; A hash value of the target file is calculated using a first algorithm based on the file information of the target file to serve as the file identification information.

3. The method for storing digital identity based on distributed real-name authentication according to claim 2 is characterized in that: The step of obtaining the file identification information and user real name information of the target file by the user's client comprises: The client obtains the identity of the user corresponding to the target file based on the file identification information; The client obtains a first real-name DID document of the user based on the identity identifier of the user; The client obtains a first public key from at least one public key in the first real-name DID document; The client obtains a first private key according to the first public key.

4. The method for storing digital identity based on distributed real-name authentication according to claim 3 is characterized in that: The generating of the evidence information by the client based on the user public key and the file identification information comprises: The client uses the first private key to sign the file identification information to obtain first signature data; The evidence information is generated based on the first signature data, the hash value, the real-name DID identifier and the public key information of the first public key.

5. The method for storing digital identity based on distributed real-name authentication according to claim 4 is characterized in that: The step of calling the evidence contract deployed on the evidence blockchain by the evidence server to generate evidence confirmation information according to the evidence information includes: The evidence storage server sends an evidence storage contract call instruction to the evidence storage blockchain, wherein the evidence storage contract call instruction includes the evidence storage information, the call address of the evidence storage contract and the real-name DID identifier; The evidence blockchain calls the evidence contract according to the evidence contract calling instruction to execute the evidence transaction on each node of the evidence blockchain; When a block corresponding to the evidence transaction is generated on each node, the block generation time and the transaction result of the evidence transaction are written into the block as an evidence record; Generate evidence confirmation information based on the block generation time and the record information of the evidence record.

6. The method for storing digital identity based on distributed real-name authentication according to claim 1 is characterized in that: Before the user's client obtains the file identification information and the user's real name information of the target file, the method further includes: The client sends a real-name DID identification application request through the evidence storage server, wherein the real-name DID identification application request at least includes the identity information of the user; The evidence storage blockchain generates a real-name DID identifier and a real-name DID document for the user according to the real-name DID identifier application request, and stores the real-name DID document in the evidence storage blockchain, wherein the real-name DID document contains at least a first public key; The evidence storage server sends the real-name DID identification and the real-name DID document to the client.

7. A distributed real-name authentication digital identity storage system, comprising: The client, the evidence storage server and the evidence storage blockchain are characterized by: The client is used to obtain file identification information and user real-name information of the target file, wherein the user real-name information includes the user's real-name DID identifier and at least one user public key; generate evidence information based on the user public key and the file identification information to send to the evidence server; The evidence server is used to call the evidence contract deployed on the evidence blockchain to generate evidence confirmation information according to the evidence information, wherein the evidence confirmation information indicates that the evidence information is recorded (for example, a block is generated based on consensus) on the evidence blockchain, and send the evidence confirmation information and the file identification information to the client; The evidence blockchain is used to generate evidence confirmation information based on the evidence information, and send the evidence confirmation information and the file identification information to the evidence blockchain.

8. The evidence storage system based on distributed real-name authentication digital identity according to claim 7 is characterized in that: The client is also used to: Obtaining the target file; A hash value of the target file is calculated using a first algorithm based on the file information of the target file to serve as the file identification information.

9. The evidence storage system based on distributed real-name authentication digital identity according to claim 8 is characterized in that: The client is also used to: Acquire the identity of the user corresponding to the target file based on the file identification information; Acquire a first real-name DID document of the user based on the identity identifier of the user; Obtaining a first public key from at least one public key in the first real-name DID document; A first private key is obtained according to the first public key.

10. A computer-readable storage medium having a computer program executable by a processor stored thereon, characterized in that: When the program is executed by the processor, it implements the evidence storage method based on distributed real-name authentication digital identity as described in any one of claims 1 to 6.

Images