Right and interest data authentication registration method and device, block chain node and storage medium

Abstract

The invention provides a right and interest data authentication registration method and device, a block chain node and a storage medium, and relates to the technical field of block chains. The evidence storage node receives the verification application sent by the registration node; the verification application is generated by the registration node according to second right data in the registration application sent by the user and sent to the evidence storage node; and verifying the second right and interest data according to the at least one evidence storage report, and sending a verification result to the registration node, so that the registration node issues a registration certificate to the user under the condition that the verification result represents that the verification is passed, thereby carrying out right confirmation on the second right and interest data. Through the method, the right of the right and interest data of the user can be confirmed, the user is prevented from tampering the right and interest data, and therefore certain legal risks are avoided.

Description

Technical Field

[0001] The present application relates to the field of blockchain technology, and specifically, to a rights and interests data authentication and registration method, device, blockchain node and storage medium. Background Art

[0002] At present, in some scenarios, it is necessary to store or notarize the rights and interests data through blockchain technology. However, since the current storage and notarization technology is not perfect, it is impossible to confirm the ownership of the rights and interests data. This may cause users to tamper with the rights and interests data, resulting in certain legal risks in some subsequent scenarios. Summary of the invention

[0003] In view of this, the purpose of this application is to provide a rights and interests data authentication and registration method, device, blockchain node and storage medium to solve the problem that the current evidence storage and notarization technology is not perfect and the rights and interests data cannot be confirmed, which leads to certain legal risks in some subsequent scenarios.

[0004] In order to achieve the above purpose, the technical solution adopted in the embodiment of the present application is as follows: In a first aspect, the present application provides a method for authenticating and registering rights and interests data, which is applied to a storage node in a blockchain network, wherein at least one storage report is stored in the storage node, and the storage report is generated according to first rights and interests data uploaded by a user, and the blockchain network further includes a registration node, and the storage node is in communication connection with the registration node, and the method includes: Receiving a verification application sent by the registration node; the verification application is generated by the registration node according to the second equity data in the registration application sent by the user and sent to the evidence storage node; The second equity data is verified according to at least one of the evidence reports, and the verification result is sent to the registration node, so that the registration node can issue a registration certificate to the user to confirm the ownership of the second equity data if the verification result indicates that the verification has passed.

[0005] In an optional implementation manner, the second equity data includes a proof report to be verified; the proof report and the proof report to be verified both include a hash value, and verifying the second equity data according to at least one of the proof reports includes: According to the hash value in the evidence report to be verified, a target evidence report corresponding to the evidence report to be verified is obtained from at least one of the evidence reports; the target evidence report has the same hash value as the evidence report to be verified; If the target evidence report matches the evidence report to be verified, it is determined that the second equity data verification has passed.

[0006] In an optional implementation, the blockchain network further includes a plurality of consensus nodes, and the evidence storage node is communicatively connected to the plurality of consensus nodes, and the method further includes: Receiving a certificate storage application sent by a user; wherein the certificate storage application includes first equity data; A storage report is generated according to the first equity data, and the storage report is distributedly stored in each of the consensus nodes and the registration nodes.

[0007] In an optional implementation manner, generating a storage report according to the first equity data includes: Calculating a hash value corresponding to the first equity data, and generating identification information corresponding to the first equity data; The evidence report is generated according to the first equity data, the hash value, the identification information and the current time.

[0008] In an optional implementation, the first equity data includes equity name, industry type, data source, ownership information, security compliance information, content type and file size; the second equity data includes equity name, industry type, application scenario, data source, structure scale, update frequency, algorithm description and evidence report to be verified.

[0009] In a second aspect, the present application provides a rights and interests data authentication and registration method, which is applied to a registration node in a blockchain network, wherein the blockchain network further includes a storage node, and the storage node is communicatively connected with the registration node, and the storage node stores at least one storage report, wherein the storage report is generated according to first rights and interests data uploaded by a user, and the method includes: Receiving a registration application sent by a user; the registration application includes second rights and interests data; Generate a verification application according to the second equity data, and send the verification application to the evidence storage node, so that the evidence storage node verifies the second equity data according to at least one of the evidence storage reports, and sends the verification result to the registration node; When the verification result indicates that the verification is passed, a registration certificate is issued to the user to confirm the ownership of the second equity data.

[0010] In a third aspect, the present application provides a rights and interests data authentication and registration device, which is applied to a storage node in a blockchain network, wherein the storage node stores at least one storage report, and the storage report is generated according to first rights and interests data uploaded by a user, and the blockchain network also includes a registration node, and the storage node is communicatively connected with the registration node, and the device includes: A first receiving module, configured to receive a verification application sent by the registration node; the verification application is generated by the registration node according to the second equity data in the registration application sent by the user and sent to the evidence storage node; A verification module is used to verify the second equity data according to at least one of the evidence reports, and send the verification result to the registration node, so that the registration node can issue a registration certificate to the user to confirm the ownership of the second equity data when the verification result indicates that the verification has passed.

[0011] In a fourth aspect, the present application provides a rights and interests data authentication and registration device, which is applied to a registration node in a blockchain network, wherein the blockchain network further includes a storage node, and the storage node is communicatively connected with the registration node, and the storage node stores at least one storage report, wherein the storage report is generated according to first rights and interests data uploaded by a user, and the device includes: A second receiving module, used to receive a registration application sent by a user; the registration application includes second rights and interests data; a sending module, configured to generate a verification application according to the second equity data, and send the verification application to the evidence storage node, so that the evidence storage node verifies the second equity data according to at least one of the evidence storage reports, and sends the verification result to the registration node; The registration module is used to issue a registration certificate to the user to confirm the ownership of the second equity data when the verification result indicates that the verification is passed.

[0012] In a fifth aspect, the present application provides a blockchain node, comprising a processor and a memory, wherein the memory stores a computer program that can be executed by the processor, and the processor can execute the computer program to implement any of the methods described in the aforementioned embodiments, or the methods described in the aforementioned embodiments.

[0013] In a sixth aspect, the present application provides a computer-readable storage medium having a computer program stored thereon, and when the computer program is executed by a processor, the method described in any one of the aforementioned embodiments, or the method described in the aforementioned embodiments, is implemented.

[0014] The rights and interests data authentication and registration method, device, blockchain node and storage medium provided in the embodiment of the present application, at least one evidence report is stored in the evidence node, and the evidence report is generated based on the first rights and interests data uploaded by the user, and the registration node generates a verification application based on the second rights and interests data in the registration application sent by the user and sends it to the evidence node, then the evidence node can verify the second rights and interests data according to at least one evidence report stored in advance, and then send the verification result to the registration node, and the registration node will issue a registration certificate to the user when the verification result indicates that the verification has passed, so as to confirm the second rights and interests data. Through this method, the rights and interests data of the user can be confirmed, and the user can be prevented from tampering with the rights and interests data, thereby avoiding certain legal risks.

[0015] In order to make the above-mentioned objects, features and advantages of the present application more obvious and easy to understand, preferred embodiments are specifically cited below and described in detail with reference to the attached drawings. BRIEF DESCRIPTION OF THE DRAWINGS

[0016] In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings required for use in the embodiments will be briefly introduced below. It should be understood that the following drawings only show certain embodiments of the present application and therefore should not be regarded as limiting the scope. For ordinary technicians in this field, other related drawings can be obtained based on these drawings without paying creative work.

[0017] Figure 1 A block diagram of a blockchain network is shown; Figure 2 A block diagram of a blockchain node provided by an embodiment of the present application is shown; Figure 3 A schematic diagram of a process of a rights and interests data authentication and registration method applied to a proof storage node provided in an embodiment of the present application is shown; Figure 4 A schematic diagram of a process of a rights data authentication registration method applied to a registration node provided in an embodiment of the present application is shown; Figure 5 A functional module diagram of a rights data authentication and registration device applied to a proof storage node provided in an embodiment of the present application is shown; Figure 6 A functional module diagram of a rights data authentication and registration device applied to a registration node provided in an embodiment of the present application is shown.

[0018] Icon: 10-blockchain network; 100-evidence node; 110-registration node; 120-consensus node; 20-blockchain node; 200-memory; 210-processor; 220-communication module; 300-first receiving module; 310-verification module; 400-second receiving module; 410-sending module; 420-registration module. DETAILED DESCRIPTION

[0019] The following will be combined with the drawings in the embodiments of the present application to clearly and completely describe the technical solutions in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. The components of the embodiments of the present application described and shown in the drawings here can be arranged and designed in various different configurations.

[0020] Therefore, the following detailed description of the embodiments of the present application provided in the accompanying drawings is not intended to limit the scope of the present application for which protection is sought, but merely represents selected embodiments of the present application. Based on the embodiments of the present application, all other embodiments obtained by those skilled in the art without creative work are within the scope of protection of the present application.

[0021] It should be noted that relational terms such as "first" and "second" are used only to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Moreover, the terms "include", "comprises" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, an element defined by the sentence "comprises a ..." does not exclude the existence of other identical elements in the process, method, article or device including the element.

[0022] Figure 1 A schematic diagram of a block diagram of a blockchain network 10 is shown in FIG. Figure 1 The blockchain network 10 includes a proof node 100, a registration node 110 and multiple consensus nodes 120, and the proof node 100 is communicated with the registration node 110 and the multiple consensus nodes 120 respectively.

[0023] Optionally, at least one evidence report is stored in the evidence node 100, and the evidence report is generated according to the first equity data uploaded by the user.

[0024] Optionally, the first rights and interests data refers to a rights and interests file of the user, such as a rights and interests file related to data intellectual property rights, and the rights and interests file may include basic attribute information related to the rights and interests.

[0025] In one possible implementation, the first equity data may include equity name, industry type, data source, ownership information, security compliance information, content type, and file size.

[0026] For example, the rights and interests name can be the name of the data intellectual property file, the industry type can be scientific research type, etc., the data source can be proprietary production data or external data, the ownership information can be holding rights, processing and use rights, product operation rights, etc., the security compliance information can be whether the file has undergone a compliance assessment by a certain organization, the content type can be the type to which the content of the data intellectual property file belongs, such as digital human type, communication type, etc., and the file size refers to the size of the data intellectual property file.

[0027] Optionally, the consensus node can be a professional institution node, such as a court node, a notary office node, an appraisal node, a law firm node, a digital identity authentication center node, etc.

[0028] Optionally, a storage platform may be deployed on the storage node to process related storage services and verification services, and a registration platform may be deployed on the registration node to process related registration services.

[0029] In one possible implementation, as the application expands, multiple evidence storage platforms may be deployed on the evidence storage node, such as scientific research rights and interests data evidence storage platform, political and legal rights and interests data evidence storage platform, financial rights and interests data evidence storage platform, etc. Based on this, the evidence storage node needs to perform initialization operations every time a new evidence storage platform is deployed, that is, to file with the relevant platform in accordance with regulations, and to join each blockchain consensus node through the consensus protocol.

[0030] exist Figure 1 On the basis of Figure 2 A block diagram of a blockchain node 20 provided in an embodiment of the present application is shown in Figure 2 The blockchain node 20 includes a memory 200, a processor 210, and a communication module 220. The memory 200, the processor 210, and the communication module 220 are electrically connected to each other directly or indirectly to achieve data transmission or interaction. For example, these components can be electrically connected to each other through one or more communication buses or signal lines.

[0031] The memory 200 is used to store computer programs or data that can be executed by the processor. The memory 200 can be, but is not limited to, a random access memory (RAM), a read only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable read-only memory (EEPROM), etc.

[0032] The processor 210 is used to read / write data or programs stored in the memory, and execute the computer program to implement the rights data authentication and registration method provided in the embodiment of the present application.

[0033] The communication module is used to establish a communication connection between the blockchain node and other communication terminals through the network, and to send and receive data through the network.

[0034] It is understandable that the blockchain node 20 can refer to the above Figure 1 The evidence node 100 in the above Figure 1 The registration node 110 in .

[0035] It should be understood that Figure 2 The structure shown is only a schematic diagram of the structure of the blockchain node. The blockchain node may also include Figure 2 More or fewer components as shown, or with Figure 2 Different configurations are shown. Figure 2 Each component shown in the figure can be implemented by hardware, software or a combination thereof.

[0036] Next, the above Figure 1 The evidence storage node 100 in the embodiment is the execution subject, and the equity data authentication and registration method provided in the embodiment of the present application is introduced as an example in combination with the flowchart. Specifically, Figure 3 A flowchart of a method for authenticating and registering rights and interests data applied to a proof storage node provided in an embodiment of the present application is provided in FIG. Figure 3 , the method comprising: Step S20, receiving a verification application sent by the registration node.

[0037] Optionally, the verification application is generated by the registration node based on the second equity data in the registration application sent by the user and sent to the evidence storage node.

[0038] Optionally, the user may send a registration application to the registration node, and the registration node may generate a verification application based on the second equity data in the registration application and send it to the evidence storage node to verify the second equity data.

[0039] Step S21, verify the second equity data according to at least one evidence report, and send the verification result to the registration node, so that the registration node can issue a registration certificate to the user to confirm the ownership of the second equity data if the verification result indicates that the verification has passed.

[0040] Optionally, the verification result may be characterized as verification passed, or may be characterized as verification failed.

[0041] In this embodiment, if the verification result indicates that the verification is passed, the registration node may issue a registration certificate to the user.

[0042] Optionally, the registration certificate may record the registration number, registration date, applicant information and important second interest data.

[0043] In the rights and interests data authentication and registration method provided in the embodiment of the present application, at least one evidence report is stored in the evidence node, and the evidence report is generated based on the first rights and interests data uploaded by the user. The registration node generates a verification application based on the second rights and interests data in the registration application sent by the user and sends it to the evidence node. The evidence node can verify the second rights and interests data based on at least one evidence report stored in advance, and then send the verification result to the registration node. The registration node issues a registration certificate to the user when the verification result indicates that the verification has passed, thereby confirming the second rights and interests data. Through this method, the rights and interests data of the user can be confirmed, and the user can be prevented from tampering with the rights and interests data, thereby avoiding certain legal risks.

[0044] In this embodiment, the user may perform equity data authentication on the evidence storage node before sending a registration application to the registration node.

[0045] Optionally, the user may send a certificate application to the certificate storage node by uploading the first equity data, and the certificate storage node may authenticate the user based on the first equity data.

[0046] Specifically, the evidence node can receive an evidence application sent by a user. Since the evidence application includes the first equity data, the evidence node can generate an evidence report based on the first equity data, and perform distributed evidence storage on the evidence report in each consensus node and registration node.

[0047] It can be understood that in this embodiment, in order to ensure the uniqueness of the evidence report, the evidence node may store the evidence report in a distributed manner in each consensus node and registration node, thereby ensuring that the evidence report will not be tampered with at will.

[0048] In one possible implementation, after receiving the first equity data sent by the user, the evidence node may first calculate the hash value corresponding to the first equity data and generate identification information corresponding to the first equity data, and then generate an evidence report based on the first equity data, the hash value, the identification information and the current time.

[0049] In this embodiment, the evidence storage node can generate a unique hash value based on all the first equity data.

[0050] Optionally, the identification information may be information such as a QR code, a barcode or a code.

[0051] Optionally, the current time may represent the generation time of the evidence report.

[0052] Optionally, the evidence report may record all of the first equity data, or may only record part of the first equity data.

[0053] For example, if the first equity data includes the equity name, industry type, data source, ownership information, security compliance information, content type and file size, and the identification information is a QR code, then the evidence report may only record the equity name, content type, file size, hash value, QR code and current time in the first equity data.

[0054] Optionally, after generating the evidence report, the evidence node may also send the evidence report to the user terminal device so that the user can obtain the corresponding evidence report.

[0055] Optionally, after obtaining the corresponding evidence report, the user can send a registration application to the registration node.

[0056] Optionally, the user may send a registration application to the registration node by uploading registration data.

[0057] In this embodiment, the registration data may include second equity data.

[0058] Optionally, the second equity data may include a proof report to be verified. It is understandable that the user can upload the proof report by himself when applying for registration, but since the proof report is uploaded by the user himself, there may be a risk of tampering. Based on this, the registration node needs to verify the proof report to be verified through the proof node to ensure the authenticity of the data in the proof report to be verified.

[0059] In this embodiment, since both the evidence report and the evidence report to be verified include hash values, the evidence node can obtain the target evidence report corresponding to the evidence report to be verified from at least one evidence report according to the hash value in the evidence report to be verified.

[0060] It can be understood that the target evidence report has the same hash value as the evidence report to be verified.

[0061] In this embodiment, if the target evidence report matches the evidence report to be verified, it is determined that the second equity data verification has passed.

[0062] It can be understood that the evidence storage node can send the second equity data verification as a verification result to the registration node, so that the registration node can determine the verification result and issue a registration certificate to the user.

[0063] In addition, the registration node can also directly verify the evidence report to be verified based on the evidence report sent by the evidence node.

[0064] Optionally, in addition to the evidence report to be verified, the second equity data may also include other equity information. In one possible implementation, the second equity data may include equity name, industry type, application scenario, data source, structure scale, update frequency, algorithm description, and the evidence report to be verified.

[0065] Optionally, the registration data may also include applicant information, such as applicant name, ID number or unified social credit code, applicant address, and applicant contact information.

[0066] Optionally, considering that the registration data uploaded by the user may be missed or transmitted incorrectly, the registration node may review the registration data uploaded by the user through manual review or format review after receiving the registration data, and generate a verification application based on the second equity data if the review is passed.

[0067] In this embodiment, if the verification result indicates that the verification has failed or the review has not passed, the registration node may prompt the user to re-upload the registration data for re-review.

[0068] In an example, the following situations may require users to re-upload registration data: 1. Failure to store data or preserve evidence before registration; 2. Disputes over the ownership of rights and interests data; 3. Duplicate registration, or re-application for registration without a valid reason after the registration application is voluntarily withdrawn; 4. Applicants conceal facts or engage in fraud; 5. Situations that do not comply with relevant laws and regulations.

[0069] Optionally, the registration certificate may record the registration number, registration date, applicant name, ID number or unified social credit code, applicant address, applicant contact information, equity name, industry type, application scenario, structure scale, algorithm description and evidence report to be verified.

[0070] Optionally, in order to ensure the security of the data, the evidence nodes, registration nodes, consensus nodes and user-end devices can interact with each other through data encryption. That is, the sender can use the receiver's public key to encrypt the data and send the encrypted data to the receiver. The receiver can then use the private key to decrypt the encrypted data to obtain the corresponding data.

[0071] For example, when the evidence node sends the evidence report to each consensus node and registration node for distributed evidence, it can first encrypt the evidence report according to the public key of each consensus node and the public key of the registration node, and send the encrypted evidence report to each consensus node and registration node respectively. After receiving the encrypted evidence report, the consensus node and the registration node can decrypt it using the private key of the consensus node and the private key of the registration node to obtain the evidence report.

[0072] Next, the above Figure 1 The registration node 110 in the embodiment is the execution subject, and the rights data authentication registration method provided by the embodiment of the present application is introduced exemplarily in combination with the flowchart. Specifically, Figure 4 A flowchart of a method for registering rights and interests data authentication applied to a registration node provided in an embodiment of the present application is shown in FIG. Figure 4 , the method comprising: Step S30: receiving a registration application sent by a user.

[0073] Among them, the registration application includes second interest data.

[0074] Step S31, generating a verification application according to the second equity data, and sending the verification application to the evidence storage node, so that the evidence storage node verifies the second equity data according to at least one evidence storage report, and sends the verification result to the registration node.

[0075] Step S32: When the verification result indicates that the verification has passed, a registration certificate is issued to the user to confirm the ownership of the second equity data.

[0076] In the rights and interests data authentication and registration method provided in the embodiment of the present application, at least one evidence report is stored in the evidence node, and the evidence report is generated based on the first rights and interests data uploaded by the user. The registration node generates a verification application based on the second rights and interests data in the registration application sent by the user and sends it to the evidence node. The evidence node can verify the second rights and interests data based on at least one evidence report stored in advance, and then send the verification result to the registration node. The registration node issues a registration certificate to the user when the verification result indicates that the verification has passed, thereby confirming the second rights and interests data. Through this method, the rights and interests data of the user can be confirmed, and the user can be prevented from tampering with the rights and interests data, thereby avoiding certain legal risks.

[0077] In order to execute the corresponding steps in the above embodiments and various possible methods, a method for implementing a rights data authentication and registration device is given below. Figure 5 , Figure 5 This is a functional module diagram of a rights and interests data authentication and registration device applied to a proof node provided in an embodiment of the present application. It should be noted that the basic principle and technical effects of the rights and interests data authentication and registration device provided in this embodiment are the same as those in the above embodiment. For the sake of brief description, for parts not mentioned in this embodiment, reference can be made to the corresponding contents in the above embodiment. The rights and interests data authentication and registration device includes: a first receiving module 300 and a verification module 310.

[0078] The first receiving module 300 is used to receive a verification application sent by a registration node; the verification application is generated by the registration node according to the second equity data in the registration application sent by the user and sent to the evidence storage node.

[0079] It can be understood that the first receiving module 300 can also be used to execute the above step S20.

[0080] The verification module 310 is used to verify the second equity data according to at least one evidence report, and send the verification result to the registration node, so that the registration node can issue a registration certificate to the user to confirm the ownership of the second equity data when the verification result indicates that the verification has passed.

[0081] It can be understood that the verification module 310 can also be used to execute the above step S21.

[0082] Optionally, the second equity data includes an evidence report to be verified; the verification module 310 is also used to obtain a target evidence report corresponding to the evidence report to be verified from at least one evidence report according to a hash value in the evidence report to be verified; the target evidence report has the same hash value as the evidence report to be verified; if the target evidence report matches the evidence report to be verified, it is determined that the second equity data verification has passed.

[0083] Optionally, the first receiving module 300 is also used to receive an evidence application sent by a user; wherein the evidence application includes first equity data; generate an evidence report based on the first equity data, and perform distributed evidence storage on the evidence report in each consensus node and registration node.

[0084] Optionally, the first receiving module 300 is further used to calculate a hash value corresponding to the first equity data and generate identification information corresponding to the first equity data; and generate a proof report according to the first equity data, the hash value, the identification information and the current time.

[0085] For further information, see Figure 6 , Figure 6 A functional module diagram of a rights data authentication and registration device applied to a registration node provided in an embodiment of the present application. It should be noted that the basic principle and technical effect of the rights data authentication and registration device provided in this embodiment are the same as those in the above embodiment. For the sake of brief description, for parts not mentioned in this embodiment, reference can be made to the corresponding contents in the above embodiment. The rights data authentication and registration device includes: a second receiving module 400, a sending module 410 and a registration module 420.

[0086] The second receiving module 400 is used to receive a registration application sent by a user; the registration application includes the second rights and interests data.

[0087] It can be understood that the second receiving module 400 can also be used to execute the above step S30.

[0088] The sending module 410 is used to generate a verification application based on the second equity data, and send the verification application to the evidence storage node, so that the evidence storage node verifies the second equity data according to at least one evidence storage report, and sends the verification result to the registration node.

[0089] It can be understood that the sending module 410 can also be used to execute the above step S31.

[0090] The registration module 420 is used to issue a registration certificate to the user to confirm the ownership of the second equity data when the verification result indicates that the verification has passed.

[0091] It can be understood that the registration module 420 can also be used to execute the above step S32.

[0092] Optionally, the above modules can be stored in the form of software or firmware. Figure 2 The memory shown in the figure may be fixed in the operating system (OS) of the blockchain node and can be Figure 2 Meanwhile, the data and program codes required for executing the above modules can be stored in the memory.

[0093] The embodiment of the present application also provides a computer-readable storage medium on which a computer program is stored. When the computer program is executed by a processor, the rights and interests data authentication and registration method provided in the embodiment of the present application can be implemented.

[0094] In several embodiments provided in the present application, it should be understood that the disclosed devices and methods can also be implemented in other ways. The device embodiments described above are merely schematic. For example, the flowcharts and block diagrams in the accompanying drawings show the possible architecture, functions and operations of the devices, methods and computer program products according to multiple embodiments of the present application. In this regard, each box in the flowchart or block diagram can represent a module, a program segment or a part of the code, and a part of the module, program segment or code contains one or more executable instructions for implementing the specified logical function. It should also be noted that in some alternative implementations, the functions marked in the box can also occur in a different order from the order marked in the accompanying drawings. For example, two consecutive boxes can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each box in the block diagram and / or flowchart, and the combination of boxes in the block diagram and / or flowchart can be implemented with a dedicated hardware-based system that performs a specified function or action, or can be implemented with a combination of dedicated hardware and computer instructions.

[0095] In addition, the functional modules in the various embodiments of the present application may be integrated together to form an independent part, or each module may exist separately, or two or more modules may be integrated to form an independent part.

[0096] If the function is implemented in the form of a software function module and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application, or the part that contributes to the prior art or the part of the technical solution, can be embodied in the form of a software product. The computer software product is stored in a storage medium, including a number of instructions to enable a computer device (which can be a personal computer, server, or network device, etc.) to execute all or part of the steps of the various embodiments of the present application. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), disk or optical disk and other media that can store program codes.

[0097] The above description is only the preferred embodiment of the present application and is not intended to limit the present application. For those skilled in the art, the present application may have various modifications and variations. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application shall be included in the protection scope of the present application.

Claims

1. A rights and interests data authentication and registration method, characterized in that: A storage node is applied to a blockchain network, wherein at least one storage report is stored in the storage node, and the storage report is generated according to first equity data uploaded by a user. The blockchain network also includes a registration node, and the storage node is in communication connection with the registration node. The method includes: Receiving a verification application sent by the registration node; the verification application is generated by the registration node according to the second equity data in the registration application sent by the user and sent to the evidence storage node; The second equity data is verified according to at least one of the evidence reports, and the verification result is sent to the registration node, so that the registration node can issue a registration certificate to the user to confirm the ownership of the second equity data if the verification result indicates that the verification has passed.

2. The method according to claim 1, characterized in that The second equity data includes a proof report to be verified; the proof report and the proof report to be verified both include a hash value, and verifying the second equity data according to at least one of the proof reports includes: According to the hash value in the evidence report to be verified, a target evidence report corresponding to the evidence report to be verified is obtained from at least one of the evidence reports; the target evidence report has the same hash value as the evidence report to be verified; If the target evidence report matches the evidence report to be verified, it is determined that the second equity data verification has passed.

3. The method according to claim 1, characterized in that The blockchain network further includes a plurality of consensus nodes, and the evidence storage node is communicatively connected with the plurality of consensus nodes, and the method further includes: Receiving a certificate storage application sent by a user; wherein the certificate storage application includes first equity data; A storage report is generated according to the first equity data, and the storage report is distributedly stored in each of the consensus nodes and the registration nodes.

4. The method according to claim 3, characterized in that The generating of the evidence report according to the first equity data includes: Calculating a hash value corresponding to the first equity data, and generating identification information corresponding to the first equity data; Generate the evidence report according to the first equity data, the hash value, the identification information and the current time.

5. The method according to claim 1, characterized in that The first equity data includes equity name, industry type, data source, ownership information, security compliance information, content type and file size; the second equity data includes equity name, industry type, application scenario, data source, structure scale, update frequency, algorithm description and evidence report to be verified.

6. A rights and interests data authentication and registration method, characterized in that: The method is applied to a registration node in a blockchain network, wherein the blockchain network further includes a certificate node, and the certificate node is in communication connection with the registration node, and the certificate node stores at least one certificate report, and the certificate report is generated according to first equity data uploaded by a user, and the method includes: Receiving a registration application sent by a user; the registration application includes second rights and interests data; Generate a verification application according to the second equity data, and send the verification application to the evidence storage node, so that the evidence storage node verifies the second equity data according to at least one of the evidence storage reports, and sends the verification result to the registration node; When the verification result indicates that the verification is passed, a registration certificate is issued to the user to confirm the ownership of the second equity data.

7. A rights data authentication and registration device, characterized in that: A storage node applied to a blockchain network, wherein at least one storage report is stored in the storage node, and the storage report is generated according to first equity data uploaded by a user. The blockchain network also includes a registration node, and the storage node is connected to the registration node in communication. The device includes: A first receiving module, configured to receive a verification application sent by the registration node; the verification application is generated by the registration node according to the second equity data in the registration application sent by the user and sent to the evidence storage node; A verification module is used to verify the second equity data according to at least one of the evidence reports, and send the verification result to the registration node, so that the registration node can issue a registration certificate to the user to confirm the ownership of the second equity data when the verification result indicates that the verification has passed.

8. A rights data authentication and registration device, characterized in that: A registration node in a blockchain network, wherein the blockchain network further comprises a certificate node, and the certificate node is in communication connection with the registration node, and the certificate node stores at least one certificate report, and the certificate report is generated according to first equity data uploaded by a user, wherein the device comprises: A second receiving module, configured to receive a registration application sent by a user; the registration application includes second rights and interests data; a sending module, configured to generate a verification application according to the second equity data, and send the verification application to the evidence storage node, so that the evidence storage node verifies the second equity data according to at least one of the evidence storage reports, and sends the verification result to the registration node; The registration module is used to issue a registration certificate to the user to confirm the ownership of the second equity data when the verification result indicates that the verification is passed.

9. A blockchain node, characterized in that: The method comprises a processor and a memory, wherein the memory stores a computer program executable by the processor, and the processor can execute the computer program to implement the method according to any one of claims 1 to 5, or the method according to claim 6.

10. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the method according to any one of claims 1 to 5 or the method according to claim 6 is implemented.

Images