WO2020182005A1 - 数字资产凭证继承转移中的信息处理方法、和相关装置 - Google Patents
数字资产凭证继承转移中的信息处理方法、和相关装置 Download PDFInfo
- Publication number
- WO2020182005A1 WO2020182005A1 PCT/CN2020/077388 CN2020077388W WO2020182005A1 WO 2020182005 A1 WO2020182005 A1 WO 2020182005A1 CN 2020077388 W CN2020077388 W CN 2020077388W WO 2020182005 A1 WO2020182005 A1 WO 2020182005A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- node
- personal security
- heir
- security kernel
- digital asset
- Prior art date
Links
- 238000000034 method Methods 0.000 title claims abstract description 132
- 238000012546 transfer Methods 0.000 title claims abstract description 23
- 230000010365 information processing Effects 0.000 title claims abstract description 20
- 238000012795 verification Methods 0.000 claims abstract description 25
- 230000008569 process Effects 0.000 claims description 51
- 230000004044 response Effects 0.000 claims description 17
- 238000003672 processing method Methods 0.000 claims description 15
- 238000012545 processing Methods 0.000 claims description 13
- 238000012790 confirmation Methods 0.000 claims description 10
- 238000004590 computer program Methods 0.000 claims description 7
- 238000012423 maintenance Methods 0.000 abstract description 2
- 239000000047 product Substances 0.000 description 24
- 230000008901 benefit Effects 0.000 description 13
- 238000011835 investigation Methods 0.000 description 12
- 238000010586 diagram Methods 0.000 description 11
- 230000004913 activation Effects 0.000 description 6
- 230000006870 function Effects 0.000 description 5
- 238000005516 engineering process Methods 0.000 description 4
- 230000000977 initiatory effect Effects 0.000 description 4
- 230000003287 optical effect Effects 0.000 description 4
- 238000012797 qualification Methods 0.000 description 4
- 239000002184 metal Substances 0.000 description 3
- 230000003044 adaptive effect Effects 0.000 description 2
- 238000013459 approach Methods 0.000 description 2
- 238000001514 detection method Methods 0.000 description 2
- 230000008034 disappearance Effects 0.000 description 2
- 230000000694 effects Effects 0.000 description 2
- 239000003999 initiator Substances 0.000 description 2
- 238000004321 preservation Methods 0.000 description 2
- 230000000644 propagated effect Effects 0.000 description 2
- 230000003068 static effect Effects 0.000 description 2
- 230000001960 triggered effect Effects 0.000 description 2
- 230000001133 acceleration Effects 0.000 description 1
- 230000009471 action Effects 0.000 description 1
- 238000003491 array Methods 0.000 description 1
- 230000005540 biological transmission Effects 0.000 description 1
- 230000008859 change Effects 0.000 description 1
- 238000004891 communication Methods 0.000 description 1
- 230000001419 dependent effect Effects 0.000 description 1
- 238000011156 evaluation Methods 0.000 description 1
- 230000008570 general process Effects 0.000 description 1
- 239000013307 optical fiber Substances 0.000 description 1
- 230000002093 peripheral effect Effects 0.000 description 1
- 239000004065 semiconductor Substances 0.000 description 1
- 239000013589 supplement Substances 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/38—Payment protocols; Details thereof
- G06Q20/389—Keeping log of transactions for guaranteeing non-repudiation of a transaction
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q50/00—Information and communication technology [ICT] specially adapted for implementation of business processes of specific business sectors, e.g. utilities or tourism
- G06Q50/10—Services
- G06Q50/18—Legal services
- G06Q50/186—Estate planning
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/38—Payment protocols; Details thereof
- G06Q20/382—Payment protocols; Details thereof insuring higher security of transaction
- G06Q20/3829—Payment protocols; Details thereof insuring higher security of transaction involving key management
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
- H04L9/08—Key distribution or management, e.g. generation, sharing or updating, of cryptographic keys or passwords
- H04L9/0816—Key establishment, i.e. cryptographic processes or cryptographic protocols whereby a shared secret becomes available to two or more parties, for subsequent use
- H04L9/0819—Key transport or distribution, i.e. key establishment techniques where one party creates or otherwise obtains a secret value, and securely transfers it to the other(s)
- H04L9/0825—Key transport or distribution, i.e. key establishment techniques where one party creates or otherwise obtains a secret value, and securely transfers it to the other(s) using asymmetric-key encryption or public key infrastructure [PKI], e.g. key signature or public key certificates
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
- H04L9/32—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials
- H04L9/3236—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials using cryptographic hash functions
- H04L9/3239—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials using cryptographic hash functions involving non-keyed hash functions, e.g. modification detection codes [MDCs], MD5, SHA or RIPEMD
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
- H04L9/32—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials
- H04L9/3247—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials involving digital signatures
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
- H04L9/32—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials
- H04L9/3263—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials involving certificates, e.g. public key certificate [PKC] or attribute certificate [AC]; Public key infrastructure [PKI] arrangements
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L2209/00—Additional information or applications relating to cryptographic mechanisms or cryptographic arrangements for secret or secure communication H04L9/00
- H04L2209/72—Signcrypting, i.e. digital signing and encrypting simultaneously
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
- H04L9/50—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols using hash chains, e.g. blockchains or hash trees
Definitions
- This application relates to the field of user identity information technology, and specifically relates to information processing technology in the inheritance and transfer of digital asset certificates.
- asset transfers are often based on physical asset certificates.
- more and more digital asset certificates are circulating on the Internet at a faster speed.
- the exchange no longer provides physical certificates by default.
- the preservation and transfer of assets often requires logging in to different asset issuance websites or trading websites, and it is difficult for individual users to centrally manage more and more digital asset certificates.
- these digital asset certificates are easily lost when the user's life cycle ends (such as death). For example, after the user's death, his assets are not known by others, resulting in the heirs being unable to inherit or retrieve the asset certificates in accordance with the law.
- a typical example is the accidental illness of the founder of the QuadrigaCX exchange, which caused the failure to withdraw digital currency worth about 147 million U.S. dollars.
- This application proposes an information processing technology that can uniformly maintain the user's digital asset certificate.
- an information processing method in the inheritance and transfer of digital asset certificates is disclosed.
- the method is executed by a judicial institution node, and the method includes:
- Obtain the user’s will, which includes the identity of the user’s personal security kernel node, the identity of each heir’s personal security kernel node, the signature of each digital asset certificate with the public key of the heir’s personal security kernel node, and the judiciary for the will Signature by the node's public key;
- the public key of the judiciary node is used to sign the will and the private key of the judiciary node is used for signature verification, it triggers the personal security core node of the heir to the identity of each heir personal security core node in the will to send the Each digital asset certificate in the will is signed with the public key of the corresponding heir’s personal security kernel node, so that the heir’s personal security kernel node signs the signature and decrypts it with the private key of the heir’s personal security kernel node to obtain the digital asset certificate According to the summary of the obtained digital asset certificate, the inherited digital asset certificate is obtained.
- a judicial institution node including:
- the life cycle end determining unit is used to determine the end of the user's life cycle
- the will acquisition unit is used to acquire the user’s will, the will including the identity of the user’s personal security kernel node, the identity of each heir’s personal security kernel node, the signature of each digital asset certificate with the public key of the corresponding heir’s personal security kernel node, The said will is signed with the public key of the judicial institution node;
- the digital asset certificate signature sending unit is used to if the judiciary node's public key is used to sign the will and the judiciary node's private key is used to verify the signature successfully, trigger the identification of the personal security kernel node to each heir in the will
- the personal security kernel node of the heir to send each digital asset certificate in the will to be signed with the public key of the heir’s personal security kernel node, so that the heir’s personal security kernel node signs the signature with the heir’s personal security kernel node
- the private key is decrypted to obtain the digest of the digital asset certificate, and the inherited digital asset certificate is obtained according to the digest of the obtained digital asset certificate.
- an information processing method in the inheritance and transfer of digital asset certificates is disclosed.
- the method is executed by a judicial institution node, and the method includes:
- the added digital asset certificate is signed with the public key of the personal security kernel node of the heir, and the added digital asset certificate is signed with the public key of the personal security kernel node corresponding to the heir;
- the current content in the will is signed with the public key of the judiciary node, and the obtained signature is placed in the will.
- a judicial institution node including:
- the obtaining unit is used to obtain the heir personal security kernel node identifier corresponding to the added digital asset certificate when the digital asset certificate is added to the user's personal security kernel node, and the heir personal security kernel node identity of the heir personal security kernel node identifier Public key
- the first signature processing unit is used to sign the added digital asset certificate with the public key of the personal security kernel node of the heir to obtain the signature of the added digital asset certificate with the public key of the personal security kernel node corresponding to the heir;
- the adding unit is used to add the signature of the heir’s personal security kernel node identification and the added digital asset certificate with the public key corresponding to the heir’s personal security kernel node to the user’s will, and the will contains useful justice Signature by the public key of the institutional node;
- the second signature processing unit is used to remove the signature with the public key of the judiciary node contained in the will, sign the current content in the will with the public key of the judiciary node, and use the obtained signature Put in the will.
- a judicial institution node including: a memory storing computer-readable instructions; a processor, reading the computer-readable instructions stored in the memory, to execute the method described above.
- a computer program medium on which computer-readable instructions are stored, and when the computer-readable instructions are executed by a processor of the computer, the computer is caused to execute the method as described above.
- a computer program product including instructions is disclosed, which when run on a computer, causes the computer to execute the method as described above.
- the user's digital asset certificate is maintained in the user's personal security kernel node.
- the heir also has the heir’s personal security kernel node to maintain the heir’s digital asset credentials.
- the user will make a will during the life cycle.
- The will includes the identity of each heir’s personal security kernel node, and each digital asset certificate is signed with the public key of the corresponding heir’s personal security kernel node. Key signature.
- the judiciary node determines that the user's life cycle is over, it obtains the user's will and uses its own private key to verify the signature of the judiciary node's public key in the will. If the verification is successful, it means that you are the first judicial authority node designated to execute the inheritance during the lifetime of the user.
- the judiciary node triggers the signature of each digital asset certificate in the will with the public key of the corresponding heir’s personal security kernel node to the corresponding heir’s personal security kernel node. Only the real heir’s personal security kernel node uses the heir’s personal security kernel node. The private key can unlock the signature and obtain the inherited digital asset certificate. The entire inheritance process is automatically executed by the machine, and the judiciary node’s public key is used to sign the will to ensure the reliability of the third-party judicial institution node that performs the inheritance procedure.
- the digital asset certificate is used by the heir’s personal security kernel node’s public key
- the signature is used to ensure that only the real heir can unsign the signature, and to ensure the security of the digital asset certificate during the inheritance process, so that even at the end of the user's life cycle, the relevant digital asset certificate can still be automatically and safely transferred to the heir.
- Figures 1A-B show a system architecture diagram of the application of the information processing method in the transfer of digital asset certificates according to an embodiment of the present application, wherein Figure 1A is a simplified system architecture diagram, and Figure 1B is based on Figure 1A The detailed system architecture diagram of the personal security kernel node.
- 2A-K show the interface diagrams of the application of the information processing method in the inheritance and transfer of digital asset certificates according to an embodiment of the present application in the application scenario of digital asset certificate inheritance after the user's death.
- Fig. 3 shows a flowchart of an information processing method in the inheritance and transfer of digital asset certificates according to an embodiment of the present application.
- Fig. 4 shows a specific flow chart of signing the will with the public key of the judiciary node in the verification of the will according to an embodiment of the present application.
- Fig. 5 shows a flowchart of an information processing method in the inheritance and transfer of digital asset certificates according to an embodiment of the present application.
- Fig. 6 shows a flow chart of the will generation process according to an embodiment of the present application.
- Fig. 7 shows a flowchart of the update process of a will according to an embodiment of the present application.
- Fig. 8 shows a flowchart of the will update process according to an embodiment of the present application.
- Fig. 9 shows a block diagram of a judicial institution node according to an embodiment of the present application.
- Fig. 10 shows a hardware diagram of a judicial institution node according to an embodiment of the present application.
- FIGS. 1A-1B the system architecture applied by the information processing method in the inheritance and transfer of digital asset certificates in an embodiment of the present application will be described.
- the architecture shown in Figure 1A includes a personal security kernel node 107, a relying party node 109, a relying party qualification certifier node 100, a business-level user identity certificate certifier node 104, a legal user identity certificate certifier node 105, and a social operating system.
- Level user identity credential prover node 106, relying party salesperson terminal 108, judicial authority node 145, and investigation node 146 All the above nodes are a block chain node in the block chain network, and various data generated during the embodiments of the present application can be recorded in the block chain, and data can also be obtained from the block chain.
- the personal security core node 107 is a security core that stores the user's digital asset credentials. Each user has a corresponding personal security kernel node 107. It is the core node for managing user digital asset credentials.
- Digital asset certificates are assets in the form of digital deposit certificates, such as electronic storage financial products. Digital asset certificates are often the obligations of the relying party node 109 to the user after the user and the relying party node 109 perform a certain business. For example, an electronic wealth management product is a manifestation of the obligation of paying interest and returning principal to the user as the relying party node 109 of the wealth management company after the user fulfills the purchase.
- the personal security kernel node 107 may include a personal security kernel node client 115 and a personal security kernel node server 116.
- the personal security kernel node client 115 is a client installed on a user terminal for user identity asset management
- the personal security kernel node server 116 is a server that cooperates with the personal security kernel node client 115 to manage user identity assets.
- the relying party node 109 refers to the node of the party on which the user's service is performed, and is generally the server node of the party on which the user depends.
- the server of the wealth management company is the relying party node 109 in the purchase of wealth management products.
- the relying party clerk terminal 108 refers to a terminal used by a clerk who performs business performance operations when the relying party and the user perform specific services.
- the terminal used by the counter staff who specifically connects with the user for purchasing wealth management products is the relying party salesperson terminal 108.
- the legal user identity certificate certifier node 105 is a node where the user’s legal identity is registered, and the legal user identity certificate certifier node 105 is used to prove that the user’s identity is legal before the service is performed, so that the user can perform the performance after the user’s identity is proved legal.
- Business so as to obtain the digital asset certificate generated by performing the business with the relying party node.
- the service-level user identity credential prover node 104 refers to a platform server that has performed a service with the user. Because the platform has performed business with users and verified the user's identity, such a platform can play an indirect role in verifying the user's identity when the level of confidence in identity authentication is not too high.
- the social operating system-level user identity credential prover node 106 is a social operating system-level platform server that provides identity certification for users. These platforms have strong data security protection capabilities and universal service capabilities, such as WeChat platform servers and Facebook platform servers. It can be considered that such a service provider provides a social operating system commonly used in the industry.
- this type of operating system-level identity authentication is not only based on a centralized pre-issued static legal identity certificate as the basis for identity verification, but It combines a multi-dimensional decentralized identity verification system based on social circle and user activity status confirmation to avoid the risk of identity fraud after the static identity verification component issued by the centralized is lost. Therefore, the user’s identity verification confidence level is higher before the service is performed.
- the confidence level evaluation used by the social operating system for identity verification is related to the number of users, applications (such as mini-program applications) and content carried by the social operating system. Since this part is not the focus of this application, it will not be detailed here.
- the relying party qualification proving party node 100 refers to a terminal that authenticates whether the relying party has the authority to require the user to provide the user's identity credentials. Before the service is performed, the user’s identity needs to be certified by the legal user identity certificate certifier node 105, or the business-level user identity certificate certifier node 104, or the social operating system-level user identity certificate certifier node 106, and the qualification of the relying party needs to be verified.
- the relying party qualification prover node 100 is determined. They are all nodes used before performing business to form digital asset certificates such as electronic wealth management products, and are not directly related to the embodiments of the present application, so they will not be repeated.
- the judiciary node 145 is a terminal used by a judiciary (for example, a court) to execute a will, such as a server for a court to process a will.
- the investigation node 146 is a processing terminal of a unit that is entrusted by a judicial institution (for example, a court) to investigate the information being inherited, such as the terminal of the investigation committee of the court.
- a judicial institution for example, a court
- FIG. 2A shows a diagram of a function selection interface displayed on a user terminal associated with a personal security kernel node (Persk) 107.
- the personal security kernel node 107 is a device that maintains the user’s digital asset credentials. It can be embodied as a client in the user terminal, or a chip in the user terminal, or a metal sticker implanted in the human body or attached to the skin. Chips, chips or other units with storage and computing capabilities.
- the user terminal associated with the personal security kernel node 107 refers to a user terminal with a display screen. .
- the user terminal associated with the personal security kernel node 107 refers to the metal patch, chip Or other terminals with storage and computing capabilities that communicate and display digital asset credentials stored in them.
- the user Before the end of the user's life cycle, the user can select the "Create Will" function option on the interface shown in FIG. 2A to enter the interface shown in FIG. 2B.
- the public key of the heir and the designated judicial institution is obtained.
- the heir’s public key is to ensure the security of the digital asset certificate given to the heir after the end of the user’s life cycle.
- the public key of the judiciary is to verify whether the third-party judiciary executing the will is the judiciary that the user really wants, and to improve the confidentiality of the will. Since the user's will is signed with the public key of the judicial institution, only the real judicial institution can unlock the signature, pass the verification, and proceed with the follow-up procedure.
- each heir’s public key to the corresponding digital asset certificate can only be unlocked by the heir himself with the private key, ensuring the security of the digital asset certificate transmission during the inheritance.
- the will signature generated by the public key of the judiciary can only be verified with the private key of the judiciary designated by the user to ensure the credibility of the inheritance process.
- 2F-K is no longer an interface diagram of the user terminal, but an interface diagram of the judicial agency node 145.
- a smart contract with the blockchain network operator when he joined the blockchain network.
- Each node in Figure 1A-B acts as a blockchain network node and can obtain the smart contract.
- the user specifies the initiator and certifier of the succession program after death.
- the interface shown in FIG. 2F is displayed. If B happens to be the initiator of the inheritance procedure specified in the user's smart contract, then the inheritance verification procedure will be started, that is, the certifiers C, D, and E specified in the smart contract will issue a confirmation request for the death of user A, asking to confirm whether user A has really passed away. As shown in Figure 2G.
- the signature verification is successful, take out the signature of the corresponding digital asset certificate in the will with the public key of each heir, and send it to the Persk identified by the heir Persk in the will, as shown in Figure 2K. After receiving it, the heir Persk uses the heir’s private key to decrypt the signature to obtain a summary of the digital asset certificate, and obtain the digital asset certificate with the digest. If you are not the true heir, and you do not have the heir’s private key, you cannot use the private key to decrypt the signature, and you will not get the inherited digital asset certificate.
- Digital asset certificates are asset certificates that exist in digital form, such as electronic wealth management product orders.
- Digital asset certificate inheritance transfer refers to the transfer of the user's digital asset certificate to the corresponding heir after the end of the user's life cycle.
- the life cycle refers to the period from birth to death or declaration of missing.
- the end of the life cycle includes death and declaration of missing.
- the information processing method in the inheritance and transfer of digital asset certificates provided by this application is executed by the judicial institution node 145, and as shown in FIG. 3, the method includes:
- Step 210 The judicial authority node 145 determines that the user's life cycle is over.
- Step 220 The judiciary node 145 obtains the user’s will.
- The will includes the identity of the user’s personal security kernel node, the identity of each heir’s personal security kernel node, and the signature of each digital asset certificate with the public key of the corresponding heir’s personal security kernel node. , The said will is signed with the public key of the node of the judiciary;
- Step 230 If the judiciary node 145 signs the will with the public key of the judiciary node, and the private key of the judiciary node is used for signature verification, it triggers the successor to the identity of the personal security kernel node of each heir in the will
- the personal security kernel node sends each digital asset certificate in the will to be signed with the public key of the heir’s personal security kernel node, so that the heir’s personal security kernel node signs the signature using the heir’s personal security kernel node’s private
- the key is decrypted to obtain the summary of the digital asset certificate, and the inherited digital asset certificate is obtained according to the obtained summary of the digital asset certificate.
- step 210 the judicial authority node 145 determines that the user's life cycle is over.
- the end of the user’s life cycle can be determined by official initiation, private initiation, or joint confirmation by official and private parties.
- step 210 includes:
- the judiciary node 145 determines the end of the life cycle of the user in response to the end of life notification from the investigation node 146.
- the investigation node 146 is a terminal of an institution entrusted by a judicial institution to investigate various situations in testamentary succession.
- the investigation node 146 is the terminal of the investigation committee established by the court.
- the court entrusts the personnel of the investigation committee to investigate the user’s social relationship and make a judgment whether the user really died or should be declared missing.
- the cycle end notification is sent to the judicial agency node 145.
- the end of life notification is a message announcing that the user has passed away or is declared missing.
- the advantage of this embodiment is that the life cycle end notification is obtained by the relevant personnel of the investigation node 146 after actual investigation, which is relatively comprehensive and has small errors.
- step 210 includes:
- the judiciary node 145 receives the activation request of the activation node
- the judiciary node 145 sends the end of user life cycle confirmation message to multiple prover nodes through the social operating system platform;
- the judicial authority node 145 determines that the life cycle of the user's personal security kernel node ends.
- the start node is the terminal for starting the testamentary succession program.
- the starting node user is any terminal (including court terminals, etc.), that is, as long as someone starts it, the inheritance process is started.
- the activation node is a user terminal in the user address book.
- the user's address book can be stored in the personal security kernel node server, and the user address book can be obtained from the personal security kernel node server.
- the startup node is the startup node specified by the user in the smart contract during the life cycle.
- the user can specify a startup node ID in the smart contract, such as the terminal ID of a friend.
- the smart contract can correspond to the user's personal security kernel node identifier and be stored in all blockchain nodes or on the blockchain.
- the activation request contains the user's personal security kernel node identifier.
- the judicial authority node 145 can obtain the user's personal security kernel node identifier from the activation request, and find the smart contract corresponding to the user's personal security kernel node identifier locally or on the blockchain. In order to obtain the starting node ID. If the identity is the identity of the sender of the initiation request, the inheritance process is started. This embodiment improves the security of opening inheritance.
- the smart contract is generated through the following process:
- the filled content is integrated into the smart contract template to generate a smart contract for the user.
- the system provides users with a variety of smart contract templates, in which there are some content that users need to fill in.
- the user can select a smart contract template in the list by, for example, checking, and fill in the content where the content needs to be filled in the template. Integrate the content filled by the user into the selected smart contract template to generate a smart contract.
- the social operating system platform refers to a platform that provides users with identity certification and has stronger data security protection capabilities and universal service capabilities than general application service complete platforms, such as WeChat platform servers and Facebook platform servers. Since a large number of users are registered on the platform, it is possible to send the succession program start confirmation request message to multiple prover nodes through the platform.
- the request for confirmation of the start of the succession program refers to a request to confirm whether the user has passed away or disappeared in order to decide whether to start the succession program.
- the multiple prover nodes are randomly selected from the user address book.
- the user address book can be obtained from the personal security core node server. The advantage of this embodiment is that since the address book is all people that the user knows, they are randomly selected from them, which avoids the risk of the user colluding with some friends to cheat.
- the multiple prover node identities are designated by the user during the user's life cycle, and are recorded in the smart contract like the aforementioned startup node.
- the smart contract corresponds to the user's personal security kernel node identifier and is stored on each blockchain node or on the blockchain.
- Judiciary node 145 obtains the user’s personal security kernel node identifier from the startup request, finds the corresponding smart contract locally or on the blockchain, and finds multiple prover node identifiers from the smart contract.
- Each prover node sends the end of user life cycle confirmation message. This embodiment improves the flexibility of the user to choose the process of execution of the will.
- the predetermined condition here refers to a condition that should be met in advance by the responses of multiple prover nodes.
- the predetermined condition is that the replies of the multiple prover nodes are all replies confirming the end of the user's life cycle.
- the predetermined condition is that more than a predetermined proportion of the replies in the plurality of prover nodes are all replies confirming the end of the user's life cycle.
- the judicial authority node 145 determines that the user's life cycle is over, including:
- the judicial authority node 145 determines that the life cycle of the user's personal security kernel node is over.
- the judiciary node 145 obtains the user’s will, which includes the identity of the user’s personal security kernel node, the identity of each heir’s personal security kernel node, and each digital asset certificate is executed with the public key of the corresponding heir’s personal security kernel node.
- the signature of the will and the signature of the will with the public key of the judicial authority node.
- the judiciary node 145 acquiring the user's will includes: the judiciary node 145 acquiring the user's will corresponding to the identity of the user's personal security kernel node. In other words, the judiciary node 145 can obtain the will of the corresponding user according to the identification of the user's personal security kernel node.
- the identification of the user's personal security kernel node is a mark that distinguishes the user's personal security kernel node from other people's personal security kernel nodes, and it can be represented by letters, numbers, symbols, etc. and combinations thereof.
- the identification of the user's personal security kernel node is recorded in the will for the purpose of finding the corresponding will (the will containing the identification) based on the identification after the user's life cycle ends.
- each heir’s personal security kernel node is a digital asset certificate for the user, and the identity of the person’s personal security kernel node designated by the user is a mark that distinguishes the heir’s personal security kernel node from other people’s personal security kernel nodes.
- the signature of each digital asset certificate with the public key of the corresponding heir’s personal security kernel node means that the digest is generated according to a predetermined digest algorithm for each digital asset certificate of the user, and the digest is encrypted with the public key of the corresponding heir’s personal security kernel node result.
- the digital asset certificate is directly transmitted and intercepted by a third party, and the digital asset certificate can be easily taken away from it. Since the signature is first generated by the digest, and then encrypted by the public key of the corresponding heir’s personal security kernel node, the public key of the heir’s personal security kernel node cannot be unsigned, which improves the security of digital asset certificate transfer during inheritance.
- the signature of the will with the public key of the judiciary node refers to the signature of the current content of the will with the public key of the judiciary node, including generating a summary of the current content of the will according to a predetermined digest algorithm, and using the public key of the judiciary node to extract the summary encryption. It has the function of verifying whether the judicial institution node executing the will is the user-specified judicial institution node, because if the judicial institution node executing the will is not the user-specified judicial institution node, it does not have the judicial institution node private key and cannot successfully verify the signature . It guarantees the credibility of the nodes of the judiciary in inheritance and improves the security of the inheritance procedure.
- the will After the will is generated, it can be recorded on the blockchain or stored in the user's personal security kernel node server. This is because after the end of the user's life cycle, it is very likely that the personal security kernel node client will also be lost with the loss of the user terminal, and the will may also die. Store it on the blockchain or personal security kernel node server. Retrieve the will after the end of the user's life cycle.
- step 220 includes: the judiciary node 145 obtains from the blockchain the will containing the user’s personal security core node identification as the user’s personal security core node identification corresponding to the user’s personal security core node identification. A will, where the will is recorded on the blockchain after it is generated.
- the will includes the identity of the user’s personal security core node, the identity of each heir’s personal security core node, the signature of each digital asset certificate with the public key of the corresponding heir’s personal security core node, and the judiciary node for the will Signature by the public key. Since the activation request contains the identity of the user's personal security kernel node, the judiciary node can search for the will containing the identity on the blockchain, and the will is the will of the user corresponding to the identity of the user's personal security kernel node.
- the will also includes header information.
- the header information contains the character of the will and the length of the will.
- the identified data block it is determined whether the identification of the user's personal security kernel node is contained. If it contains, the identified data block constitutes a will containing the identification of the user's personal security kernel node.
- the header information refers to the block header information of each data block after the will is recorded as a data block on the blockchain.
- Each data block also has a block body, which records the contents of the will.
- the will may include multiple data blocks.
- the will includes the identity of the user’s personal security kernel node, the identity of each heir’s personal security kernel node, the signature of each digital asset certificate with the public key of the heir’s personal security kernel node, and the judiciary node public key for the will.
- the signatures performed by the personal security core nodes of different heirs and the signatures of the corresponding different digital asset certificates with the public keys of the personal security core nodes of the heirs may be recorded in different data blocks.
- the characteristic word of the will is a sign indicating that the data block on the blockchain is the data block of the will. Without the will feature word, it means that the data block recorded is not a will.
- the feature word of the will indicates that the data block records the will. Since various data blocks are recorded on the blockchain, some data blocks are completely unrelated to the will. In order to narrow the search scope, the will feature word is set in the block header of the data block storing the will. The will feature word is found on the blockchain, and the data block containing the will feature word is considered a will data block.
- the length of the will is a sign that the will occupies the number of consecutive data blocks on the blockchain. For example, the length of the will is 7, which means that on the blockchain, 7 data blocks are counted from the current data block. These data blocks are all data blocks associated with the will.
- the data blocks associated with the will can be identified according to the length of the will in the header information, and then it can be determined whether the user’s personal is contained within these data blocks.
- the identifier of the secure kernel node is that compared to searching for the data block containing the identity of the user's personal security kernel node on the entire blockchain, the search range is greatly reduced and the search efficiency is improved.
- the continuous data block range (the number of consecutive data blocks indicated by the length of the will) constitutes the personal security kernel node containing the user Logo of the will.
- the personal security kernel node includes a personal security kernel node client and a personal security kernel node server.
- Step 220 includes: the judiciary node 145 obtains the will from the personal security kernel node server corresponding to the identity of the user’s personal security kernel node as the will of the user corresponding to the identity of the user’s personal security kernel node, wherein the will is made by the individual
- the secure core node client is generated and stored in the personal secure core node server.
- the startup request contains the identification of the user's personal security kernel node. In this way, the personal security core node server corresponding to the identifier can be found, and the will can be obtained from it.
- step 230 if the judiciary node 145 signs the will with the public key of the judiciary node, and the private key of the judiciary node is used for signature verification, it triggers the identification of the personal security kernel node to each heir in the will
- the personal security kernel node of the heir to send each digital asset certificate in the will to be signed with the public key of the heir’s personal security kernel node, so that the heir’s personal security kernel node signs the signature with the heir’s personal security kernel node
- the private key is decrypted to obtain the digest of the digital asset certificate, and the inherited digital asset certificate is obtained according to the digest of the obtained digital asset certificate.
- the judiciary node 145 After the judiciary node 145 obtains the will, the judiciary node 145 should not immediately start the inheritance process. Because if you are not the node of the judicial institution designated by the user, you have no right to perform the subsequent inheritance procedures. Therefore, the judiciary node 145 must first sign the will with the public key of the judiciary node, and verify the signature with the private key of the judiciary node.
- the will also includes a designated node identifier of the judicial institution that executes the will. As shown in FIG. 2B, the user designates the node identifier of the judicial institution that executes the will on the interface, so that the identifier is included in the will in FIG. 2D.
- the judiciary node 145 signs the will with the public key of the judiciary node and successfully verifies the signature with the private key of the judiciary node, including:
- Step 310 The judicial authority node 145 obtains the identifier of the judicial authority node designated in the will to execute the will;
- Step 320 If the identifier of the judicial institution node that executes the will specified in the will is the identifier of the judicial institution node currently executing the method, the judicial institution node 145 signs the will with the public key of the judicial institution node, using the judicial institution The node private key is successfully signed and verified.
- the identifier can be obtained from the will. Since the judicial authority node 145 stores its own identifier locally, the judicial authority node 145 compares the obtained identifier with its own identifier stored locally, and if they are consistent, the private key of the judicial authority node is used for the will in the will. The signature performed by the public key of the judiciary node is verified.
- the advantage of this embodiment is that the judicial authority node identification comparison and the verification of the signature generated by the judicial authority node public key are used to verify the authority of the judicial authority node, which can improve the authority verification of the judicial authority node more than simply checking the signature. Accuracy.
- step 320 includes:
- the node of the judiciary 145 signs the will with the public key of the judiciary node using the private key of the judiciary node Decrypt, get the digest of the will after decryption;
- the judiciary node 145 generates a summary of the will
- the judiciary node 145 determines that the judiciary node's public key is used to sign the will, and the judiciary node's private key is used for signature verification.
- generating a will signature includes a process of generating a digest for the content of the will according to a predetermined digest algorithm (for example, a hash algorithm), and encrypting the digest with the public key of the judicial authority node, the reverse process is followed when verifying the signature.
- a predetermined digest algorithm for example, a hash algorithm
- the digest of the will is generated according to the same digest algorithm when generating the signature. Since when the will signature is generated, no signature has been placed in the will, and the generation of the will signature is based on the contents of the will except the testament signature. Therefore, in one embodiment, generating the summary of the will includes:
- the same predetermined digest algorithm used when generating the will is applied to the will after the signature is removed to generate the digest of the will.
- the judiciary node 145 also needs to store the same predetermined digest algorithm as in the user's personal security kernel node. In this way, the predetermined digest algorithm is applied to the will after the signature is removed, and the generated digest has a consistent basis for comparison with the digest when the will signature was generated.
- the decrypted will digest is compared with the generated digest of the will. If the two are consistent, the signature verification is successful, and it is considered that the judicial authority node currently executing the will is Judiciary node designated by the user. At this time, it can be triggered to send the signature of each digital asset certificate in the will with the public key of the corresponding heir personal security core node to the heir personal security core node identified by each heir personal security core node in the will.
- triggering is that it can be completed by the judicial authority node 145 itself, or can be designated by another other node, or it can start the smart contract in the blockchain network, and the smart contract automatically allocates nodes to complete it.
- the signature of each digital asset certificate is sent instead of the digital asset certificate itself. This is because even if the third-party node intercepts it, it does not have the private key of the heir’s personal security kernel node. It cannot de-sign and therefore cannot obtain the inherited digital asset. Credentials to improve the security of digital asset certificates in inheritance.
- the process of de-signing is also divided into Two steps. First, the personal security kernel node of the successor decrypts the signature with the private key of the personal security kernel node of the successor to obtain a summary of the digital asset certificate. Then, according to the summary of the obtained digital asset certificate, the inherited digital asset certificate is obtained.
- obtaining the inherited digital asset certificate based on the obtained summary of the digital asset certificate includes: obtaining the digital asset certificate corresponding to the obtained summary of the digital asset certificate from the blockchain, wherein the digital asset After the voucher is generated, the summary corresponding to the digital asset voucher is stored on the blockchain.
- This embodiment follows the mode of linking the digital asset certificate immediately after it is generated.
- the user's personal security kernel node and the business relying party node such as a wealth management company terminal
- a business such as signing a contract to purchase a wealth management product
- a digital asset certificate (such as a wealth management product order) with the business relying party node is generated.
- a digest of the digital asset certificate is generated immediately according to a predetermined digest algorithm, and the digest and the digital asset certificate are correspondingly stored on the blockchain. In this way, the digital asset certificate corresponding to the summary of the obtained digital asset certificate can be directly queried from the blockchain.
- the personal security kernel node includes a personal security kernel node client and a personal security kernel node server.
- the obtaining the inherited digital asset certificate according to the obtained summary of the digital asset certificate includes: obtaining the digital asset certificate corresponding to the obtained summary of the digital asset certificate from the personal security kernel node server, wherein the digital asset certificate is controlled by the personal security kernel. After the node client is generated, the summary corresponding to the digital asset certificate is stored on the personal security core node server.
- the personal security kernel node client and the business relying party node after the personal security kernel node client and the business relying party node generate a digital asset certificate, they generate a digest of the digital asset certificate according to a predetermined digest algorithm, and store the digest and the digital asset certificate in the personal security kernel node. On the server. In this way, the digital asset certificate corresponding to the summary of the obtained digital asset certificate can be directly inquired from the personal security core node server.
- the triggering to the heir personal security kernel node identified by each heir personal security kernel node in the will, and sending each digital asset certificate in the will to sign with the public key of the corresponding heir personal security kernel node includes: triggering To the heir’s personal security kernel node identified by each heir’s personal security kernel node in the will, send the signature of each digital asset certificate in the will with the public key corresponding to the heir’s personal security kernel node and the signature of each digital asset certificate The identifier of the business relying party node.
- the obtaining the inherited digital asset certificate according to the summary of the obtained digital asset certificate includes:
- the summary of the obtained digital asset certificate is sent to the business relying party node identified by the business relying party node of the digital asset certificate;
- the digital asset certificate is formed by the user's personal security kernel node and a business relying party node performing the business. After the digital asset certificate is formed, the digital asset certificate and the summary of the digital asset certificate are backed up and stored in the business relying party node. Therefore, the corresponding digital asset certificate can be recalled from the business relying party node based on the summary of the data asset certificate.
- the business relying party node In order to request the business relying party node, the will must contain the identity of the business relying party node. It can be generated based on the business relying party node identity contained in the digital asset voucher when generating the will (the business relying party node ID is the ID of the digital asset voucher Important field, the digital asset cannot be redeemed without this field).
- the business relying party node identification is also sent at the same time.
- the heir’s personal security kernel node can send the obtained summary of the digital asset certificate to the business relying party node identified by the business relying party node of the digital asset certificate.
- the digital asset certificate and its summary are stored correspondingly, so that the digital asset certificate corresponding to the summary of the digital asset certificate can be received from the business relying party node.
- the inherited digital asset certificate contains the identifier of the business relying party node that the digital asset certificate depends on, so that the personal security kernel node of the heir and the business relying party node identified by the business relying party node are based on the inherited
- the digital asset certificate generates the updated digital asset certificate between the successor node and the business relying party node.
- step 230 the heir’s personal security kernel node obtains the inherited digital asset certificate, but the digital asset certificate is only formed by the user’s personal security kernel node and relying party node, not the heir’s personal security kernel node and dependent Therefore, the personal security kernel node of the heir must form an updated digital asset certificate with the relying party node.
- the business relying party node identified with the business relying party node generates the updated digital asset certificate between the heir node and the business relying party node based on the inherited digital asset certificate, including the personal security of the heir.
- the successor’s personal security kernel node sends the inherited digital asset certificate and the successor’s personal security kernel node identification to the business relying party node identified by the business relying party node, so that the business relying party node can follow the inherited digital asset certificate and the successor’s personal security kernel Node ID, generate updated digital asset certificate;
- the personal security kernel node of the heir receives the updated digital asset certificate sent by the business relying party node.
- the obligation of the relying party node in the updated digital asset certificate is exactly the same as the obligation of the relying party node of the inherited digital asset certificate, it is just that the parties have changed from the user's personal security kernel node and the business relying party node to the heir's personal security kernel node and Business relying party node, therefore, only the party information in the content of the inherited digital asset certificate can be updated from the user’s personal security core node identification and business relying party node identification to heir personal security core node identification and business relying party node identification, respectively.
- the post digital asset certificate is sent to the heir’s personal security kernel node.
- the advantage of this embodiment is that, through a convenient procedure, the inherited digital asset certificate is converted, and the efficiency of updating the digital asset certificate is improved.
- the entire inheritance process is completed, and the user's personal security kernel node can be set to a terminated state.
- Setting the user's personal security kernel node to the terminated state may be automatically performed by the smart contract distribution node.
- the user's personal security kernel node has several states: disabled, enabled, suspended, and terminated. Before the user is born, the user's personal security kernel node is correspondingly in an inactive state. After the user is born, the personal security kernel node is enabled after the parent's application. In the process, if there is an event such as reporting a loss, it may be necessary to set the personal security kernel node to a suspended state. In the suspended state, the personal security kernel node may not be operated until the position is restored. After the user's life cycle ends, after the above process is completed, and other processes that may use the user's personal security kernel node are completed, the personal security kernel node can be set to a terminated state. In the terminated state, the personal security kernel node is abolished, and the personal security kernel node cannot be accessed permanently.
- inheritance tax is paid
- inheritance tax is not paid.
- the user on the interface of FIG. 2B, the user not only specifies the personal security kernel node identification of the heir corresponding to each digital asset certificate and the identification of the judicial institution node that executes the will, but also specifies the law applicable to the inheritance of the will. In this way, the will shown in Figure 2D may also contain the law applicable to the succession of the will.
- the trigger sends to the heir personal security kernel node identified by each heir personal security kernel node in the will, and sends each digital asset certificate in the will to the corresponding heir personal security kernel node
- the signature of the public key includes:
- the personal security kernel node of the heir who is identified by the heir's personal security kernel node corresponding to the digital asset certificate in the will is triggered, and what is sent is not only the digital asset certificate in the will.
- the signature is carried out with the public key corresponding to the personal security kernel node of the heir, and the law applicable to the inheritance of the will.
- the inheritance process corresponding to each inheritance applicable law can be programmed in advance and stored on a public server or in each user's personal security kernel node.
- executing the process corresponding to the inherited applicable law includes the following process performed by the heir’s personal security kernel node: according to the received inheritance applicable law, obtain it from the public server or the heir’s personal security kernel node This inherits the program code corresponding to the applicable law, and inputs the inherited digital asset certificate into the program code, thereby executing the process corresponding to the inherited applicable law.
- the advantage of this embodiment is that the inheritance can be performed in accordance with the inheritance applicable law specified by the user, and the fineness of the inheritance is improved.
- the method further includes:
- Step 225 If the judiciary node 145 cannot obtain the user's will, determine the law corresponding to the identity according to the identity of the user's personal security kernel node;
- Step 235 The judiciary node 145 obtains the kinship of the user
- Step 245 The judicial authority node 145 obtains each digital asset certificate of the user
- Step 255 For each digital asset certificate of the obtained user, the judicial authority node 145 determines the personal security kernel node identifier of the heir corresponding to each digital asset certificate in accordance with the determined law and the kinship relationship;
- Step 265 The judiciary node 145 obtains the public key of the heir personal security kernel node identified by the heir personal security kernel node.
- Step 275 The judiciary node 145 signs each digital asset certificate of the user with the public key of the corresponding heir’s personal security kernel node, and sends it to the corresponding heir’s personal security kernel node so that the heir’s personal security kernel node can
- the signature is decrypted with the private key of the personal security kernel node of the heir to obtain the digest of the digital asset certificate, and the inherited digital asset certificate is obtained according to the digest of the obtained digital asset certificate.
- step 225 if the judiciary node 145 cannot obtain the user's will, the law corresponding to the identity is determined according to the identity of the user's personal security kernel node.
- the user’s will cannot be obtained from the blockchain or from the user’s personal security kernel node server, it is likely that the user’s life cycle will end before the will is established. At this time, legal inheritance needs to be initiated. According to the user’s personal security kernel The identity of the node determines the law corresponding to the identity.
- the identity of the user's personal security kernel node must be stored in the personal security kernel node server in advance. According to the identity of the user's personal security kernel node, determining the law corresponding to the identity includes:
- the startup request has the user’s personal security kernel node identifier, it corresponds to a unique set of personal security kernel node clients and servers, so the user’s personal security kernel node in the startup request can be identified with the corresponding personal security kernel node
- the server sends an identity request.
- the identity of the user's personal security kernel node refers to the user's nationality, registration area, etc. For example, if the user is a Chinese, Chinese law may be applied for inheritance. The user is an American and may be inherited under the laws of the United States.
- the corresponding relationship table between the identity of the user's personal security kernel node and the inherited applicable law is stored in the predetermined server or each personal security kernel node, that is, the correspondence relationship table between the identity and the law. From the correspondence table, the law corresponding to the identity can be determined according to the identity of the user's personal security kernel node.
- step 235 the judicial authority node 145 obtains the kinship of the user.
- the user's kinship list is stored in the user's personal security kernel node server. Therefore, the relative relationship of the user can be obtained from the relative relationship list of the user in the user's personal security kernel node server.
- step 245 the judicial authority node 145 obtains each digital asset certificate of the user.
- each digital asset certificate of the user is not only stored in the user's personal security kernel node client, but also stored in the user's personal security kernel node server.
- the user's personal security kernel node client may not be found after the end of the user's life cycle, you can find the corresponding user's personal security kernel node server according to the user's personal security kernel node in the startup request, and obtain the user's digital asset credentials from it .
- step 255 for each acquired digital asset certificate of the user, the judicial authority node 145 determines the personal security kernel node identifier of the heir corresponding to each digital asset certificate in accordance with the determined law and the kinship relationship.
- the program code corresponding to each applicable law is set in a dedicated server or in each personal security kernel node.
- the user's digital asset vouchers and the kinship relationship are entered into the program code corresponding to the determined law to obtain the personal security kernel node identification of the heir corresponding to each digital asset vouchers according to the law.
- step 265 the judicial authority node 145 obtains the public key of the heir personal security kernel node identified by the determined heir personal security kernel node.
- obtaining the public key of the successor's personal security kernel node identified by the successor's personal security kernel node can be realized by requesting a special certification authority server (CA) in the blockchain. Since the certification authority server (CA) is the node that issues the public and private keys of blockchain nodes, it can request the public key of any blockchain node.
- CA certification authority server
- obtaining the public key of the heir personal security kernel node identified by the determined heir personal security kernel node includes: obtaining the heir personal security kernel node corresponding to the determined heir personal security kernel node identity from the blockchain The public key of the heir’s personal security kernel node is generated by the heir’s personal security kernel node and recorded on the blockchain corresponding to the public key identification of the heir’s personal security kernel node.
- the public key is not generated and stored by the certification authority server, but is generated by each individual security kernel node and published on the blockchain. Since the corresponding personal security core node identification is recorded on the blockchain, it can be searched on the blockchain with the personal security core node identification when needed.
- obtaining the public key of the heir personal security kernel node identified by the determined heir personal security kernel node includes:
- a social operating system platform such as WeChat
- WeChat On a social operating system platform (such as WeChat), when two users add friends to each other, the public key of one user will be sent to the personal security kernel node of the other to save.
- the social operating system platform saves the friendship between all the people who add friends to each other. In this way, through the social operating system platform, it is possible to obtain a list of personal security kernel node identifications of all heirs who are friends with the personal security kernel node identification of the heir, and send the public key to any personal security kernel node identified by the personal security kernel node in the list.
- An obtaining request where the public key obtaining request includes the identity of the personal security kernel node of the determined heir.
- the personal security kernel node returns the public key of the heir's personal security kernel node identified by the heir's personal security kernel node.
- step 275 the judiciary node 145 signs each digital asset certificate of the user with the public key of the corresponding heir’s personal security kernel node, and sends it to the corresponding heir’s personal security kernel node, so that the heir’s personal security kernel
- the node decrypts the signature with the private key of the heir’s personal security kernel node to obtain a summary of the digital asset certificate, and obtains the inherited digital asset certificate according to the obtained digest of the digital asset certificate.
- step 230 the heir secure kernel node corresponding to the digital asset certificate in the will sends the signature with the public key of the corresponding heir’s personal secure kernel node, while in step 275, The heir security kernel node corresponding to the digital asset certificate deduced by the law is sent and signed with the public key of the corresponding heir personal security kernel node.
- the general process is the same, so I won't repeat it.
- the advantage of this embodiment is that the automation of legal inheritance is realized and the security in inheritance is guaranteed.
- the will is generated by the user's personal security kernel node through the following process:
- Step 410 For the digital asset certificate in the user's personal security kernel node, receive the user's designation of the personal security kernel node identifier of the heir to the digital asset certificate;
- Step 420 Obtain the public key of the personal security kernel node of the heir identified by the designated heir personal security kernel node;
- each digital asset certificate is signed with the corresponding public key of the heir personal security kernel node identified by the designated heir personal security kernel node, and each digital asset certificate is obtained with the public key of the corresponding heir personal security kernel node.
- Step 440 Put the identity of the user's personal security kernel node, the identity of each heir's personal security kernel node, and the signature of each digital asset certificate with the public key of the corresponding heir's personal security kernel node into the will;
- Step 450 Receive the user's designation of the node identifier of the judicial institution that executes the will;
- Step 460 Obtain the public key of the judicial institution node identified by the judicial institution node.
- Step 470 Sign the current content in the will with the obtained public key of the judicial institution node and put it into the will.
- step 410 for the digital asset certificate in the user's personal security kernel node, the user's designation of the personal security kernel node identifier of the heir to the digital asset certificate is received.
- FIG. 2B shows an interface for the user to specify the identity of the personal security kernel node of the heir for the digital asset certificate in the personal security kernel node.
- step 410 can be implemented by category designation or item designation.
- Fig. 2B is an interface of an example of item designation.
- step 410 includes:
- the user's designation of the personal security kernel node identifier of the heir to the digital asset certificate is received.
- a list of digital asset certificates including all digital asset certificates in the user's personal security kernel node is displayed to the user.
- a drop-down box that specifies the identity of the personal security kernel node of the heir to the digital asset certificate is displayed. Click the arrow on the right of the drop-down box, and the drop-down menu will pop up, displaying all the candidate heir personal security kernel node IDs.
- All candidate heir personal security kernel node identifiers can be directly derived from the user address book stored in the user's personal security kernel node, or directly derived from the kinship list stored in the user's personal security kernel node.
- the advantage of this embodiment is that it is convenient for the user to designate the personal security kernel node identifier of the corresponding heir for each digital asset certificate, which improves the precision of will generation.
- step 410 includes:
- For each digital asset voucher type in the digital asset voucher list receive the user's designation of the personal security kernel node identifier of the heir to the digital asset voucher type, where the designated heir personal security kernel node ID is used for the digital asset voucher type Every digital asset certificate.
- the interface of this embodiment is different from Figure 2B in that the interface of Figure 2B displays a list of all digital asset certificates, and the interface of this embodiment displays all digital asset certificate types (such as wealth management product orders, insurance product orders). , Stock transaction list), this is because usually users want to designate the same heir to inherit the same type of digital asset certificate (financial product list). Then, for each digital asset voucher type in the digital asset voucher list, the user specifies the personal security kernel node identifier of the heir of the digital asset voucher type. After designation, all digital asset certificates of this type are inherited by the designated heir’s personal security kernel node when inherited.
- all digital asset certificates of this type are inherited by the designated heir’s personal security kernel node when inherited.
- the advantage of this embodiment is that generally users want to specify the characteristics of the same inheritance for the same type of digital asset certificate (financial product list), and improve the efficiency of will generation.
- step 420 the public key of the heir personal security kernel node identified by the designated heir personal security kernel node is obtained.
- obtaining the public key of the heir’s personal security kernel node identified by the designated heir’s personal security kernel node can be achieved by requesting a special certification authority server (CA), or it can be obtained from the blockchain, or through social operations.
- CA certification authority server
- the system platform is obtained from the personal security kernel node of the successor and friend. Since the specific implementation has been described above, I will not repeat it here to save space.
- each digital asset certificate is signed with the corresponding public key of the heir’s personal security kernel node identified by the designated heir’s personal security kernel node, and each digital asset certificate is obtained with the public key of the heir’s personal security kernel node. Key signature.
- the process of signing the digital asset certificate with the corresponding public key of the heir’s personal security kernel node identified by the designated heir’s personal security kernel node includes generating a summary of the digital asset certificate based on a predetermined digest algorithm and using the corresponding The process of obtaining the public key of the designated successor personal security kernel node identifier of the successor personal security kernel node to encrypt the digest.
- step 440 the identity of the user's personal security kernel node, the identity of each heir's personal security kernel node, and the signature of each digital asset certificate with the public key of the corresponding heir's personal security kernel node are put into the will.
- the identity of the user's personal security kernel node is put into the will because the will is retrieved through the identity of the user's personal security kernel node in the inheritance procedure.
- the identity of each heir’s personal security kernel node and the signature of each digital asset certificate with the public key of the corresponding heir’s personal security kernel node are placed in the will because the inheritance procedure needs to be sent to the heir’s personal security kernel node corresponding to these identifiers
- the digital asset certificate is signed with the public key corresponding to the personal security kernel node of the heir.
- step 450 the user's designation of the identification of the judicial institution node that executes the will is received.
- the user can specify in the drop-down box of the identifier of the judicial institution node executing the will in the interface. Click the arrow on the right of the drop-down box, and the drop-down menu will pop up, showing all the candidate judicial institution node IDs. These candidate judicial agency node IDs are imported in advance. When the user selects a candidate judicial institution node identifier in the drop-down menu, it is considered that the judicial institution node identifier that executes the will is designated.
- step 460 the public key of the judicial institution node identified by the judicial institution node is obtained.
- this step can also be implemented by requesting a special certification authority server (CA), or it can be obtained from the blockchain, or it can be obtained from the personal security kernel node of the heir’s friend through the social operating system platform, so I will not repeat it. .
- CA certification authority server
- step 470 the current content in the will is signed with the obtained public key of the judicial institution node and placed in the will.
- the significance of putting the signature in the will is as mentioned above, and it can be used in the inheritance procedure to verify whether the judicial authority node performing the inheritance procedure is the judicial authority node that the user really wants. If the judiciary node that executes the inheritance procedure is not the judiciary node designated by the user, without the private key of the judiciary node, the signature verification cannot be successful.
- the advantage of this embodiment is that a will is generated in a quick way, which improves the efficiency of the generation of the will.
- the will includes the identity of the user’s personal security kernel node, the identity of each heir’s personal security kernel node, the signature of each digital asset certificate with the public key of the heir’s personal security kernel node, and the judicial authority for the will In addition to the signature performed by the node's public key, it can also include a designated judicial authority node ID.
- the method for generating a will further includes: putting a designated judicial institution node identifier into the will (not shown).
- step 450 Since in step 450, the user's designation of the node identifier of the judicial institution that executes the will has been received, in this step, the identifier can be put into the will.
- step 220 when obtaining the user's will, it can be obtained from the blockchain or from the user's personal security kernel node server. In fact, it can also be obtained from the user’s personal security kernel node client, but the user’s personal security kernel node client is very easy to be found after the end of the user’s life cycle. Therefore, from the blockchain or the user’s personal security kernel Node server acquisition is more secure. In one embodiment, according to the security requirements of the will configuration, it can be divided into multiple security modes, and each mode has a different security level.
- the will is configured through the following process after generation:
- the security mode list includes a first security mode, a second security mode, and a third security mode.
- the first security mode the will is stored in the user's personal security kernel node client; and the second security mode
- the third security mode the will is stored in the user's personal security core node server and published on the blockchain;
- the will is stored in the user's personal security kernel node server and published on the blockchain.
- the configuration of a will refers to the preservation and maintenance of the will after its creation.
- Security mode refers to the way of storing wills corresponding to different security levels.
- the first security mode the will is stored in the user's personal security kernel node client. In this way, the user may not be able to retrieve the digital asset certificate after the user's mobile phone is lost, and the degree of security is the lowest.
- the second security mode the will is stored in the user's personal security kernel node client and server. In this way, the user’s assets can still be recovered if the user’s mobile phone is lost, with the second degree of security.
- the third security mode the will is stored in the user's personal security kernel node client and server, and published on the blockchain. In this way, if you can't find it in one place, you can find it in another place, which is the most secure.
- the user may continue to generate digital asset certificates, such as forming a new digital asset certificate with the relying party node (such as purchasing a new financial product, generating a new financial product order).
- digital asset certificates such as forming a new digital asset certificate with the relying party node (such as purchasing a new financial product, generating a new financial product order).
- the relying party node such as purchasing a new financial product, generating a new financial product order.
- no corresponding heir personal security kernel node identification is specified. Therefore, after the user's life cycle ends, these new digital asset vouchers cannot be inherited according to the will.
- the digital asset certificate in the user's personal security kernel node increases, there can be a personal security kernel node identifier for the heir to the user to specify the digital asset certificate, and the digital asset certificate can be automatically assigned to the user
- the successor of the personal security kernel node identifies two implementation methods.
- Step 510 When a digital asset certificate is added to the user's personal security kernel node, display to the user an interface specifying the identity of the personal security kernel node of the heir of the digital asset certificate;
- Step 520 Receive, on the interface, the user's designation of the personal security kernel node identifier of the heir to the digital asset certificate;
- Step 530 Obtain the public key of the heir’s personal security kernel node identified by the designated heir’s personal security kernel node;
- Step 540 Sign the added digital asset certificate with the correspondingly obtained public key of the heir personal security kernel node identified by the designated heir personal security kernel node, and use the public key of the corresponding heir personal security kernel node to obtain the added digital asset certificate Signed
- Step 550 The personal security core node identification of the heir designated for the added digital asset certificate, and the added digital asset certificate are signed with the public key of the personal security core node corresponding to the heir, and added to the will;
- Step 560 Remove the current signature of the obtained judiciary node's public key in the will
- Step 570 Sign the current content in the will with the obtained public key of the judicial institution node, and put it into the will.
- Steps 510-570 are described in detail below.
- step 510 when a digital asset certificate is added to the personal security kernel node of the user, an interface specifying the identity of the personal security kernel node of the heir of the digital asset certificate is displayed to the user.
- the user’s personal security kernel node has a detection module.
- the detection module When a new digital asset certificate is written into the personal security kernel node (that is, the user’s personal security kernel node and the relying party node perform the business, the credential is generated, that is, the digital asset When the certificate is written into the personal asset safe of the personal security core node), the detection module will detect this situation and display an interface similar to Figure 2B.
- the interface lists the added digital asset certificates, which are specified below
- the drop-down menu has a list of all candidate heir personal security kernel node IDs for users to choose.
- step 520 the designation of the personal security kernel node identification of the successor of the digital asset certificate by the user is received on the interface.
- step 530 the public key of the heir personal security kernel node identified by the designated heir personal security kernel node is obtained.
- this step can also be implemented by requesting a special certification authority server (CA), or it can be obtained from the blockchain, or it can be obtained from the personal security kernel node of the heir’s friend through the social operating system platform, so I will not repeat it. .
- CA certification authority server
- step 540 the added digital asset certificate is signed with the correspondingly obtained public key of the heir’s personal security kernel node identified by the designated heir’s personal security kernel node, and the added digital asset certificate is obtained with the corresponding heir’s personal security kernel node’s public key. Signature by the public key.
- This step is similar to step 430 and includes a process of generating a digest of the added digital asset certificate according to a predetermined digest algorithm, and encrypting the digest with the correspondingly obtained public key of the heir personal security kernel node identified by the designated heir personal security kernel node.
- step 550 the heir personal security kernel node identification designated for the added digital asset certificate, and the added digital asset certificate are signed with the public key of the heir personal security kernel node and added to the will.
- step 550 is similar to step 440, except that step 550 only adds the personal security kernel node identification and corresponding signature of the heir to the will for the added digital asset certificate, so it will not be repeated.
- step 560 the current signature of the obtained judiciary node's public key in the will is removed.
- the signature of the public key of the judiciary node when generating the will in 470 it is the signature of the current content in the will when the will was generated at that time, the current content of the will is increased by the content added in step 550, resulting in the signature inheritance. Change, therefore, need to re-sign.
- the signature in the will is not part of the basis of the signature.
- the signature must be removed first. On this basis, the current content in the will is used to obtain The public key signature of the judiciary node.
- the current content at this time includes the content added in step 550.
- step 570 the current content in the will is signed with the obtained public key of the judicial institution node and placed in the will.
- the above process provides a simple and easy way to update the will when the user's digital asset certificates increase after the will is generated, avoiding the problem that some newly added digital asset certificates in the will may have no heirs in the future.
- Step 510' when a digital asset certificate is added to the user's personal security core node, the personal security of the heir corresponding to the added digital asset certificate is determined according to the personal security core node identifier of the heir designated for the existing digital asset certificate in the will Core node identifier;
- Step 520' Obtain the public key of the heir’s personal security kernel node identified by the heir’s personal security kernel node corresponding to the added digital asset certificate;
- Step 530' the added digital asset certificate is signed with the correspondingly obtained public key of the heir’s personal security kernel node identified by the heir’s personal security kernel node, and the added digital asset certificate is obtained with the public key of the heir’s personal security kernel node.
- Key signature
- Step 540' the designated heir personal security kernel node identifier for the added digital asset certificate, and the added digital asset certificate is signed with the public key of the corresponding heir personal security kernel node, and added to the will;
- Step 550' remove the current signature of the obtained judiciary node's public key in the will
- Step 560' Sign the current content in the will with the obtained public key of the judicial institution node and put it into the will.
- step 510' when a digital asset certificate is added to the user's personal security kernel node, the heir corresponding to the added digital asset certificate is determined according to the personal security kernel node identifier of the heir designated for the existing digital asset certificate in the will Personal security kernel node ID.
- step 510 The method for judging that the digital asset certificate is added to the personal security kernel node of the user is the same as step 510.
- the determination of the personal security core node identification of the heir corresponding to the added digital asset certificate according to the personal security core node identification of the heir specified for the existing digital asset certificate in the will includes:
- the personal security kernel node identifier of the heir designated for the same type of digital asset certificate in the is the same, the personal security kernel node identifier of the heir designated for the same type of digital asset certificate in the will is determined as the heir corresponding to the added digital asset certificate Personal security kernel node ID.
- the type of the digital asset certificate can be obtained from the type field of the digital asset certificate.
- the personal security kernel node identifier of the heir designated in the will for the digital asset certificate of the wealth management product type. If there are 5 digital asset certificates of financial product types before in the will, there are 5 heir personal security kernel node IDs designated for these digital asset certificates, but these 5 may be the same heir personal security kernel node ID. That is, the personal security kernel node identifiers of the heirs that have been designated for the same type of digital asset certificates in the will are the same. At this time, the user is likely to want to also specify the same heir personal security kernel node to inherit for the newly added digital asset certificates. The personal security core node identifier of the heir that has been designated for the same type of digital asset certificate in the will is determined as the personal security core node identifier of the heir corresponding to the added digital asset certificate.
- the determining the personal security kernel node identification of the heir corresponding to the added digital asset certificate according to the personal security kernel node identification of the heir specified in the will for the existing digital asset certificate further includes:
- the personal security kernel node of the heir with the most personal security kernel node identifiers of the multiple heirs specified for the same type of digital asset certificate in the will be inconsistent, the personal security kernel node of the heir with the most personal security kernel node identifiers of the multiple heirs specified for the same type of digital asset certificate in the will The identifier is determined as the heir personal security kernel node identifier corresponding to the added digital asset certificate.
- the five heirs’ personal security kernel nodes that have been designated for the same type of digital asset certificate in the will will be automatically assigned
- the identity of the personal security kernel node of the heir with the largest number in the identity, that is, the identity of the heir personal security kernel node A, is determined as the identity of the heir personal security kernel node corresponding to the added digital asset certificate.
- This embodiment determines the personal security core node identification of the heir specified for the newly added digital asset certificate based on the personal security core node identification of the heir specified for the same type of digital asset certificate. Because users tend to specify the same type of digital asset certificate The personal security kernel node of the same heir, this embodiment improves the accuracy of automatically assigning the identity of the personal security kernel node of the heir.
- the user can manually select the personal security kernel node identifier of the heir corresponding to the digital asset certificate that he wants to add in a manner similar to steps 510-520.
- the determination of the personal security core node identification of the heir corresponding to the added digital asset certificate according to the personal security core node identification of the heir specified for the existing digital asset certificate in the will includes:
- the personal security kernel node ID of the heir specified in the will for the digital asset certificate with the same business relying party node ID is determined as The identity of the personal security kernel node of the heir corresponding to the added digital asset certificate.
- the business relying party node identification of the added digital asset certificate can be obtained from the relying party node identification field.
- the added digital asset certificate is a wealth management product purchased from wealth management company A. Therefore, the business relying party node ID is the terminal ID of wealth management company A.
- the digital asset certificates such as wealth management products, etc.
- the same heir personal security kernel node identifier is used as the heir personal security kernel node identifier corresponding to the added digital asset certificate.
- the determining the personal security kernel node identification of the heir corresponding to the added digital asset certificate according to the personal security kernel node identification of the heir specified in the will for the existing digital asset certificate further includes:
- the personal security kernel node IDs of the heirs specified for the digital asset vouchers with the same business relying party node ID in the will are inconsistent, the personal security kernel node IDs of multiple heirs that have been specified for the digital asset vouchers with the same business relying party node ID in the will The personal security kernel node identifier of the heir with the largest number of heirs is determined as the personal security kernel node identifier of the heir corresponding to the added digital asset certificate.
- the digital asset certificate that has been identified for the same business relying party node in the will is automatically designated 5
- the personal security core node identification of the heir with the largest number of personal security core node identifications of the heirs, that is, the identification of the personal security core node A of the heir, is determined as the personal security core node identification of the heir corresponding to the added digital asset certificate.
- This embodiment determines the personal security core node identification of the heir specified for the newly added digital asset certificate based on the previous personal security core node identification of the heir specified for the digital asset certificate of the same business relying party node identification.
- the digital asset certificate of the relying party node specifies the personal security kernel node of the same heir. This embodiment improves the accuracy of automatically specifying the identity of the personal security kernel node of the heir.
- step 520' the public key of the heir personal security kernel node identified by the heir personal security kernel node corresponding to the added digital asset certificate is obtained.
- this step can also be implemented by requesting a special certification authority server (CA), or it can be obtained from the blockchain, or it can be obtained from the personal security kernel node of the heir’s friend through the social operating system platform, so I will not repeat it. .
- CA certification authority server
- step 530' the added digital asset certificate is signed with the correspondingly obtained public key of the heir personal security kernel node identified by the designated heir personal security kernel node, and the added digital asset certificate is used for the corresponding heir personal security kernel node. Signed by your public key.
- step 540 This step is similar to step 540, so it will not be repeated.
- step 540' the heir personal security core node identification designated for the added digital asset certificate, and the added digital asset certificate are signed with the public key of the corresponding heir personal security core node and added to the will.
- This step is similar to step 550, so it will not be repeated.
- step 550' the current signature of the obtained judiciary node's public key in the will is removed.
- This step is similar to step 560, so it will not be repeated.
- step 560' the current content in the will is signed with the obtained public key of the judicial institution node and placed in the will.
- step 570 This step is similar to step 570, so it will not be repeated.
- This embodiment realizes the automatic allocation of the heir personal security kernel node identifier to the newly added digital asset certificate based on the existing digital asset certificate in the user's personal security kernel node, which improves the automation degree of will update.
- the user can manually select the heir personal security kernel node ID corresponding to the digital asset voucher to be added in a manner similar to steps 510-520.
- a judicial institution node including:
- the life cycle end determining unit 610 is used to determine the end of the life cycle of the user
- the will obtaining unit 620 is configured to obtain the user’s will, the will including the identity of the user’s personal security kernel node, the identity of each heir’s personal security kernel node, and the signature of each digital asset certificate with the public key of the corresponding heir’s personal security kernel node , The said will is signed with the public key of the node of the judiciary;
- the first digital asset certificate signature sending unit 630 is configured to, if the judiciary node's public key is used to sign the will and the verification of the signature with the judiciary node's private key is successful, trigger the personal security kernel to each heir in the will
- the personal security kernel node of the heir of the node’s identity sends each digital asset certificate in the will signed with the public key corresponding to the heir’s personal security kernel node, so that the heir’s personal security kernel node signs the signature with the heir’s individual
- the private key of the secure kernel node is decrypted to obtain a summary of the digital asset certificate, and the inherited digital asset certificate is obtained according to the obtained digest of the digital asset certificate.
- the end of life determining unit 610 is further configured to:
- the end of life determining unit 610 is further configured to:
- determining that the user's life cycle ends includes:
- the will also includes a designated node identifier of the judicial institution that executes the will.
- the successful signature verification of the will using the public key of the judiciary node with the private key of the judiciary node includes:
- the identification of the node of the judiciary that executes the will specified in the will is the identification of the node of the judiciary that currently executes the method, sign the will with the public key of the judiciary node and use the private key of the judiciary node to verify the success .
- the signature of the will with the public key of the judiciary node is used by the judicial
- the private key of the institutional node is successfully signed and verified, including:
- the identification of the node of the judiciary that executes the will is the identification of the node of the judiciary that currently executes the method, sign the will with the public key of the judiciary node and decrypt it with the private key of the judiciary node to obtain the decryption A summary of the will generated later;
- the inherited digital asset certificate contains the identifier of the business relying party node that the digital asset certificate depends on, so that the personal security kernel node of the heir and the business relying party node identified by the business relying party node are based on the inherited
- the digital asset certificate generates the updated digital asset certificate between the successor node and the business relying party node.
- the will also includes the law applicable to the succession of the will, and the trigger sends the numbers in the will to the heirs personal security kernel nodes identified by the personal security kernel nodes of the heirs in the will
- the asset certificate is signed with the public key corresponding to the personal security kernel node of the heir, including:
- the judicial institution node further includes:
- An identity corresponding law determining unit configured to determine the law corresponding to the identity according to the identity of the user's personal security kernel node if the user's will is not available;
- the kinship acquiring unit is used to acquire the kinship of the user
- the digital asset certificate obtaining unit is used to obtain the user's digital asset certificates
- the successor personal security core node identification determination unit is used to determine the personal security core node identification of the successor corresponding to each digital asset certificate in accordance with the determined law and the kinship for each digital asset certificate of the acquired user;
- the heir personal security kernel node public key obtaining unit is used to obtain the public key of the heir personal security kernel node identified by the heir personal security kernel node;
- the second digital asset certificate signature sending unit is used to sign each digital asset certificate of the user with the public key of the corresponding heir’s personal security kernel node and send it to the corresponding heir’s personal security kernel node so that the heir
- the security kernel node decrypts the signature with the private key of the heir’s personal security kernel node to obtain a digest of the digital asset certificate, and obtains the inherited digital asset certificate according to the digest of the obtained digital asset certificate.
- the will is generated by the user's personal security kernel node through the following process:
- the current content in the will is signed with the obtained public key of the judicial institution node and placed in the will.
- the process of generating the further includes:
- the will is configured through the following process after generation:
- the security mode list includes a first security mode, a second security mode, and a third security mode.
- the first security mode the will is stored in the user's personal security kernel node client; and the second security mode
- the third security mode the will is stored in the user's personal security core node server and published on the blockchain;
- the will is stored in the user's personal security kernel node server and published on the blockchain.
- the will is updated by the user's personal security kernel node through the following process:
- the personal security core node identification of the heir designated for the added digital asset certificate, and the added digital asset certificate will be signed with the public key of the corresponding heir’s personal security core node and added to the will;
- the current content in the will is signed with the obtained public key of the judicial institution node and placed in the will.
- the will is updated by the user's personal security kernel node through the following process:
- the personal security core node identification of the heir designated for the added digital asset certificate, and the added digital asset certificate will be signed with the public key of the corresponding heir’s personal security core node and added to the will;
- the current content in the will is signed with the obtained public key of the judicial institution node and placed in the will.
- the information processing method in the inheritance and transfer of digital asset certificates according to the embodiments of the present application can be implemented by the judicial authority node 145 in FIG. 10.
- the judiciary node 145 is represented in the form of a general-purpose computing device.
- the components of the judicial authority node 145 may include, but are not limited to: the aforementioned at least one processing unit 810, the aforementioned at least one storage unit 820, and a bus 830 connecting different system components (including the storage unit 820 and the processing unit 810).
- the storage unit stores program code, and the program code can be executed by the processing unit 810, so that the processing unit 810 executes the various exemplary methods described in the description section of the exemplary method in this specification.
- the processing unit 810 may perform various steps as shown in FIG. 3.
- the storage unit 820 may include a readable medium in the form of a volatile storage unit, such as a random access storage unit (RAM) 8201 and/or a cache storage unit 8202, and may further include a read-only storage unit (ROM) 8203.
- RAM random access storage unit
- ROM read-only storage unit
- the storage unit 820 may also include a program/utility tool 8204 having a set of (at least one) program module 8205.
- program module 8205 includes but is not limited to: a social operating system, one or more application programs, other program modules, and program data. Each of these examples or some combination may include the implementation of a network environment.
- the bus 830 may represent one or more of several types of bus structures, including a storage unit bus or a storage unit controller, a peripheral bus, a graphics acceleration port, a processing unit, or a local area using any bus structure among multiple bus structures. bus.
- the judicial authority node 145 may also communicate with one or more external devices 700 (such as keyboards, pointing devices, Bluetooth devices, etc.), and may also communicate with one or more devices that enable users to interact with the judicial authority node 145, and/ Or communicate with any device (such as a router, modem, etc.) that enables the judicial authority node 145 to communicate with one or more other computing devices. This communication can be performed through an input/output (I/O) interface 850.
- the judiciary node 145 may also communicate with one or more networks (for example, a local area network (LAN), a wide area network (WAN), and/or a public network, such as the Internet) through the network adapter 860.
- networks for example, a local area network (LAN), a wide area network (WAN), and/or a public network, such as the Internet
- the network adapter 860 communicates with other modules of the judicial authority node 145 through the bus 830. It should be understood that although not shown in the figure, other hardware and/or software modules can be used in conjunction with the Judiciary Node 145, including but not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tapes Drives and data backup storage systems, etc.
- the exemplary embodiments described herein can be implemented by software, or can be implemented by combining software with necessary hardware. Therefore, the technical solution according to the embodiments of the present application can be embodied in the form of a software product, which can be stored in a non-volatile storage medium (can be a CD-ROM, U disk, mobile hard disk, etc.) or on the network , Including several instructions to make a computing device (which may be a personal computer, server, terminal device, or network device, etc.) execute the method according to the embodiment of the present application.
- a non-volatile storage medium can be a CD-ROM, U disk, mobile hard disk, etc.
- Including several instructions to make a computing device which may be a personal computer, server, terminal device, or network device, etc.
- a computer program medium is also provided, on which computer-readable instructions are stored, and when the computer-readable instructions are executed by the processor of the computer, the computer is caused to execute the foregoing method embodiments. Partially described methods.
- the computer program product may adopt a portable compact disk read-only memory (CD-ROM) and include program code, and may run on a terminal device, such as a personal computer.
- CD-ROM portable compact disk read-only memory
- the program product of the present invention is not limited to this.
- the readable storage medium can be any tangible medium that contains or stores a program, and the program can be used by or in combination with an instruction execution system, device, or device.
- the program product can use any combination of one or more readable media.
- the readable medium may be a readable signal medium or a readable storage medium.
- the readable storage medium may be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, device, or device, or a combination of any of the above. More specific examples (non-exhaustive list) of readable storage media include: electrical connections with one or more wires, portable disks, hard disks, random access memory (RAM), read only memory (ROM), erasable Type programmable read only memory (EPROM or flash memory), optical fiber, portable compact disk read only memory (CD-ROM), optical storage device, magnetic storage device, or any suitable combination of the above.
- the computer-readable signal medium may include a data signal propagated in baseband or as a part of a carrier wave, and readable program code is carried therein. This propagated data signal can take many forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination of the foregoing.
- the readable signal medium may also be any readable medium other than a readable storage medium, and the readable medium may send, propagate, or transmit a program for use by or in combination with the instruction execution system, apparatus, or device.
- the program code contained on the readable medium can be transmitted by any suitable medium, including but not limited to wireless, wired, optical cable, RF, etc., or any suitable combination of the foregoing.
- the program code used to perform the operations of the present invention can be written in any combination of one or more programming languages.
- the programming languages include object-oriented programming languages—such as Java, C++, etc., as well as conventional procedural styles. Programming language-such as "C" language or similar programming language.
- the program code can be executed entirely on the user's computing device, partly on the user's device, executed as an independent software package, partly on the user's computing device and partly executed on the remote computing device, or entirely on the remote computing device or server Executed on.
- the remote computing device can be connected to a user computing device through any kind of network, including a local area network (LAN) or a wide area network (WAN), or can be connected to an external computing device (for example, using Internet service providers) Business to connect via the Internet).
- LAN local area network
- WAN wide area network
- Internet service providers Internet service providers
- modules or units of the device for action execution are mentioned in the above detailed description, this division is not mandatory.
- the features and functions of two or more modules or units described above may be embodied in one module or unit.
- the features and functions of a module or unit described above can be further divided into multiple modules or units to be embodied.
- the exemplary embodiments described herein can be implemented by software, or can be implemented by combining software with necessary hardware. Therefore, the technical solution according to the embodiments of the present application can be embodied in the form of a software product, which can be stored in a non-volatile storage medium (can be a CD-ROM, U disk, mobile hard disk, etc.) or on the network , Including several instructions to make a computing device (which may be a personal computer, server, mobile terminal, or network device, etc.) execute the method according to the embodiment of the present application.
- a non-volatile storage medium can be a CD-ROM, U disk, mobile hard disk, etc.
- Including several instructions to make a computing device which may be a personal computer, server, mobile terminal, or network device, etc.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Security & Cryptography (AREA)
- Business, Economics & Management (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Tourism & Hospitality (AREA)
- Strategic Management (AREA)
- Theoretical Computer Science (AREA)
- General Physics & Mathematics (AREA)
- General Business, Economics & Management (AREA)
- Physics & Mathematics (AREA)
- Accounting & Taxation (AREA)
- Technology Law (AREA)
- Primary Health Care (AREA)
- Marketing (AREA)
- Human Resources & Organizations (AREA)
- General Health & Medical Sciences (AREA)
- Economics (AREA)
- Health & Medical Sciences (AREA)
- Operations Research (AREA)
- Finance (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
Abstract
一种数字资产凭证继承转移中的信息处理方法、和相关装置。该方法包括:确定用户的生命周期结束(210);获取用户的遗嘱(220);如果对所述遗嘱用司法机构节点公钥进行的签名,用司法机构节点私钥进行签名验证成功,触发向所述遗嘱中的各继承人个人安全内核节点的标识的继承人个人安全内核节点,发送所述遗嘱中各数字资产凭证用对应继承人个人安全内核节点的公钥进行的签名,实现对用户的数字资产凭证进行统一的维护。
Description
本申请要求于2019年03月08日提交中国专利局、申请号为201910177252.4、申请名称为“数字资产凭证继承转移中的信息处理方法、和相关装置”的中国专利申请,以及于2019年03月08日提交中国专利局、申请号为201910943397.0、申请名称为“数字资产凭证继承转移中的信息处理方法、和相关装置”的中国专利申请的优先权,其全部内容通过引用结合在本申请中。
本申请涉及用户身份信息技术领域,具体涉及数字资产凭证继承转移中的信息处理技术。
在现实生活中,资产转移往往是依据实物资产凭证进行。随着互联网的普及,越来越多的数字资产凭证以更快的速度在互联网上流转。例如,人们在购买理财产品时,由于实时性很高,交易所已经不再缺省提供实物凭证。资产的保存和转移往往需要登录不同的资产发行网站或者交易网站,个人用户难以对越来越多的数字资产凭证进行集中管理。而且,这些数字资产凭证很容易随着用户的生命周期结束(如离世)而丢失。例如,用户离世后,其资产不被人所知,导致继承人无法依法继承或者找回资产凭证。典型的例子是,因QuadrigaCX交易所创始人意外病故,导致价值约1.47亿美元的数字货币无法取出的事件。
现有技术中,缺少一种信息处理技术,能够对用户的数字资产凭证进行统一的管理。
发明内容
本申请提出一种信息处理技术,能够对用户的数字资产凭证进行统一的维护。
根据本申请实施例的一方面,公开了一种数字资产凭证继承转移中的信息处理方法,所述方法由司法机构节点执行,所述方法包括:
确定用户的生命周期结束;
获取用户的遗嘱,所述遗嘱包括用户个人安全内核节点的标识、各继承人个人安全内核节点的标识、各数字资产凭证用对应继承人个人安全内核节点的公钥进行的签名、所述遗嘱用司法机构节点公钥进行的签名;
如果对所述遗嘱用司法机构节点公钥进行的签名,用司法机构节点私钥进行签名验证成功,触发向所述遗嘱中的各继承人个人安全内核节点的标识的继承人个人安全内核节点,发送所述遗嘱中各数字资产凭证用对应继承人个人安全内核节点的公钥进行的签名,以便所述继承人个人安全内核节点对该签名,用所述继承人个人安全内核节点的私钥解密,得到数字资产凭证的摘要,根据得到的数字资产凭证的摘要,得到继承的数字资产凭证。
根据本申请实施例的一方面,公开了一种司法机构节点,包括:
生命周期结束确定单元,用于确定用户的生命周期结束;
遗嘱获取单元,用于获取用户的遗嘱,所述遗嘱包括用户个人安全内核节点的标识、各继承人个人安全内核节点的标识、各数字资产凭证用对应继承人个人安全内核节点的公钥进行的签名、所述遗嘱用司法机构节点公钥进行的签名;
数字资产凭证签名发送单元,用于如果对所述遗嘱用司法机构节点公钥进行的签名,用司法机构节点私钥进行签名验证成功,触发向所述遗嘱中的各继承人个人安全内核节点的标识的继承人个人安全内核节点,发送所述遗嘱中各数字资产凭证用对应继承人个人安全内核节点的公钥进行的签名,以便所述继承人个人安全内核节点对该签名,用所述继承人个人安全内核节点的私钥解密,得到数字资产凭证的摘要,根据得到的数字资产凭证的摘要,得到继承的数字资产凭证。
根据本申请实施例的一方面,公开了一种数字资产凭证继承转移中的信息处理方法,所述方法由司法机构节点执行,所述方法包括:
当用户的个人安全内核节点中增加数字资产凭证时,获取增加的数字资产凭证对应的继承人个人安全内核节点标识,以及所述继承人个人安全内核节点标识的继承人个人安全内核节点的公钥;
对增加的数字资产凭证,用所述继承人个人安全内核节点的公钥进行签名,得到增加的数字资产凭证用对应继承人个人安全内核节点的公钥进行的签名;
将所述继承人个人安全内核节点标识、增加的数字资产凭证用对应继承人个人安全内核节点的公钥进行的签名,添加到所述用户的遗嘱中,所述遗嘱中包含有用司法机构节点公钥进行的签名;
将所述遗嘱中包含的用司法机构节点公钥进行的签名去掉;
将所述遗嘱中的当前内容用所述司法机构节点公钥进行签名,并将得到的签名放入所述遗嘱。
根据本申请实施例的一方面,公开了一种司法机构节点,包括:
获取单元,用于当用户的个人安全内核节点中增加数字资产凭证时,获取增加的数字资产凭证对应的继承人个人安全内核节点标识,以及所述继承人个人安全内核节点标识的继承人个人安全内核节点的公钥;
第一签名处理单元,用于对增加的数字资产凭证,用所述继承人个人安全内核节点的公钥进行签名,得到增加的数字资产凭证用对应继承人个人安全内核节点的公钥进行的签名;
添加单元,用于将所述继承人个人安全内核节点标识、增加的数字资产凭证用对应继承人个人安全内核节点的公钥进行的签名,添加到所述用户的遗嘱中,所述遗嘱中包含有用司法机构节点公钥进行的签名;
第二签名处理单元,用于将所述遗嘱中包含的用司法机构节点公钥进行的签名去掉,将所述遗嘱中的当前内容用所述司法机构节点公钥进行签名,并将得到的签名放入所述遗嘱。
根据本申请实施例的一方面,公开了一种司法机构节点,包括:存储器,存储有计算机可读指令;处理器,读取存储器存储的计算机可读指令,以执行如上所述的方法。
根据本申请实施例的一方面,公开了一种计算机程序介质,其上存储有计算机可读指令,当所述计算机可读指令被计算机的处理器执行时,使计算机执行如上所述的方法。
根据本申请实施例的一方面,公开了一种包括指令的计算机程序产品,当其在计算机上运行时,使得所述计算机执行如上所述的方法。
本申请实施例中,用户的数字资产凭证维护在用户的个人安全内核节点中。继承人也有继承人个人安全内核节点,维护继承人的数字资产凭证。用户在生命周期期间会立有遗嘱,遗嘱中包括各继承人个人安全内核节点的标识,还有各数字资产凭证用对应继承人个人安全内核节点的公钥进行的签名、所述遗嘱用司法机构节点公钥进行的签名。当司法机构节点确定用户生命周期结束后,获取用户的遗嘱,用自己的私钥对遗嘱中用司法机构节点公钥进行的签名进行验证。如果验证成功,说明自己就是用户生前指定执行继承首先的司法机构节点。然后,司法机构节点触发把遗嘱中各数字资产凭证用对应继承人个人安全内核节点的公钥进行的签名发给相应继承人个人安全内核节点,只有真正的继承人个人安全内核节点采用继承人个人安全内核节点的私钥,能够解开该签名,获得继承的数字资产凭证。整个继承过程由机器自动执行,且由用司法机构节点公钥对遗嘱进行的签名来保证执行继承手续的第三方司法机构节点的可靠性,通过将数字资产凭证用继承人个人安全内核节点的公钥签名来保证只有真正的继承人才能解签名,保证继承过程中数字资产凭证的安全性,使得即使在用户生命周期结束时,相关的数字资产凭证仍然能自动安全转移到继承人。
本申请的其他特性和优点将通过下面的详细描述变得显然,或部分地通过本申请的实践而习得。
应当理解的是,以上的一般描述和后文的细节描述仅是示例性的,并不能限制本申请。
通过参照附图详细描述其示例实施例,本申请的上述和其它目标、特征及优点将变得更加显而易见。
图1A-B示出了根据本申请一个实施例的数字资产凭证继承转移中的信息处理方法应 用的系统构架图,其中,图1A是简略的系统构架图,图1B是在图1A的基础上对个人安全内核节点细化后的系统构架图。
图2A-K示出了根据本申请一个实施例的数字资产凭证继承转移中的信息处理方法应用在用户离世后数字资产凭证继承的应用场景下的界面图。
图3示出了根据本申请一个实施例的数字资产凭证继承转移中的信息处理方法的流程图。
图4示出了根据本申请一个实施例的验证遗嘱中用司法机构节点公钥对遗嘱进行的签名的具体流程图。
图5示出了根据本申请一个实施例的数字资产凭证继承转移中的信息处理方法的流程图。
图6示出了根据本申请一个实施例的遗嘱的生成过程流程图。
图7示出了根据本申请一个实施例的遗嘱的更新过程流程图。
图8示出了根据本申请一个实施例的遗嘱的更新过程流程图。
图9示出了根据本申请一个实施例的司法机构节点的框图。
图10示出了根据本申请一个实施例的司法机构节点的硬件图。
现在将参考附图更全面地描述示例实施方式。然而,示例实施方式能够以多种形式实施,且不应被理解为限于在此阐述的范例;相反,提供这些示例实施方式使得本申请的描述将更加全面和完整,并将示例实施方式的构思全面地传达给本领域的技术人员。附图仅为本申请的示意性图解,并非一定是按比例绘制。图中相同的附图标记表示相同或类似的部分,因而将省略对它们的重复描述。
此外,所描述的特征、结构或特性可以以任何合适的方式结合在一个或更多示例实施方式中。在下面的描述中,提供许多具体细节从而给出对本申请的示例实施方式的充分理解。然而,本领域技术人员将意识到,可以实践本申请的技术方案而省略所述特定细节中的一个或更多,或者可以采用其它的方法、组元、步骤等。在其它情况下,不详细示出或描述公知结构、方法、实现或者操作以避免喧宾夺主而使得本申请的各方面变得模糊。
附图中所示的一些方框图是功能实体,不一定必须与物理或逻辑上独立的实体相对应。可以采用软件形式来实现这些功能实体,或在一个或多个硬件模块或集成电路中实现这些功能实体,或在不同网络和/或处理器装置和/或微控制器装置中实现这些功能实体。
下面先参照图1A-1B描述一下本申请实施例的数字资产凭证继承转移中的信息处理方法所应用的体系构架。
如图1A所示的体系构架包括个人安全内核节点107、依赖方节点109、依赖方资格证明方节点100、业务级用户身份凭证证明方节点104、法定用户身份凭证证明方节点105、社交操作系统级用户身份凭证证明方节点106、依赖方业务员终端108、司法机构节点145、调查节点146。上述所有节点都是区块链网络中的一个区块链节点,其在本申请实施例过程中产生的各种数据都可以记录到区块链,也可以从区块链获取数据。
个人安全内核节点107是一个保存用户的数字资产凭证的安全核心。每个用户有一个对应的个人安全内核节点107。它是管理用户数字资产凭证的核心节点。数字资产凭证是以数字化存证形式存在的资产,如电子存储的理财产品。数字资产凭证往往是用户与依赖方节点109履行某一业务后依赖方节点109对用户负有的义务。例如,电子理财产品是在用户履行了购买后,作为理财公司的依赖方节点109对用户负有的支付利息和返还本金的义务的体现。
如图1B所示,个人安全内核节点107可以包括个人安全内核节点客户端115和个人安全内核节点服务器116。个人安全内核节点客户端115是在用户终端上安装的、用于用户身份资产管理的客户端,个人安全内核节点服务器116是与个人安全内核节点客户端115配合进行用户身份资产管理的服务器。
依赖方节点109是指用户的业务履行所要依赖的一方的节点,一般是依赖的一方的服务器节点。例如,在购买理财产品业务中,用户要依赖理财公司来完成购买,理财公司的 服务器就是理财产品购买业务中的依赖方节点109。
依赖方业务员终端108是指依赖方与用户具体业务履行时进行业务履行操作的业务员所用的终端。例如,在理财产品购买业务中,具体与用户进行理财产品购买对接的柜台人员用的终端就是依赖方业务员终端108。法定用户身份凭证证明方节点105是用户法定身份注册的节点,而且法定用户身份凭证证明方节点105用于在业务履行前证明用户的身份合法,使得在用户的身份被证明合法之后,用户才能履行业务,从而获得与依赖方节点履行业务产生的数字资产凭证。业务级用户身份凭证证明方节点104是指曾经与用户履行过业务的平台服务器。因该平台曾经与用户履行过业务,对用户的身份进行过验证,使得在对身份认证确信等级要求不太高的情况下,这样的平台可以起到一个间接验证用户身份的作用。社交操作系统级用户身份凭证证明方节点106是为用户提供身份证明的社交操作系统级平台服务器。这些平台具备较强的数据安全保护能力,并具备普遍服务能力,例如微信平台服务器、Facebook平台服务器。可以认为这样的业务提供方提供了一个行业内普遍使用的社交操作系统,鉴于这类操作系统级的身份鉴别不仅仅是以某个中心化预先发行的静态法定身份凭证为身份核验的依据,而是结合采用了多维的基于社交圈以及用户活动状态确认的非中心化身份核验体系,以避免中心化发行的静态身份核验组件丢失后的身份冒用风险。所以在业务履行前对用户身份的核验确信等级更高,社交操作系统用于身份核验的确信等级评价与社交操作系统承载的用户数目,应用(例如小程序应用)和内容等相关。由于该部分不是本申请重点关注的内容,不在此详述。依赖方资格证明方节点100是指对依赖方是否有权限要求用户提供用户身份凭证的资格进行认证的终端。在业务履行前,用户的身份需要经法定用户身份凭证证明方节点105,或业务级用户身份凭证证明方节点104,或社交操作系统级用户身份凭证证明方节点106证明,而依赖方资格需要经依赖方资格证明方节点100确定。它们都是履行业务从而形成电子理财产品等数字资产凭证之前用到的节点,与本申请实施例不直接相关,故不赘述。
司法机构节点145是司法机构(例如法院)用来对遗嘱进行执行处理的终端,例如法院处理遗嘱业务的服务器。
调查节点146是司法机构(例如法院)委托的调查继承中的信息的单位的处理终端,如法院的调查委员会的终端。
下面结合图2A至图2K描述根据本申请实施例的数字资产凭证继承转移中的信息处理方法应用在用户离世后数字资产凭证继承应用场景下的界面图。
图2A示出了个人安全内核节点(Persk)107关联的用户终端显示的功能选择界面图。如前所述,个人安全内核节点107是维护用户的数字资产凭证的设备,可以体现为用户终端中的一个客户端,或用户终端的一个芯片,或植入人体或贴在皮肤表面的金属贴片、芯片或者其他具备存储和计算能力的单元。当个人安全内核节点107为用户终端中的一个客户端,或用户终端的一个芯片或者其他具备存储和计算能力的单元时,个人安全内核节点107关联的用户终端是指安装有显示屏的用户终端。当个人安全内核节点107为植入人体或贴在皮肤表面的金属贴片、芯片或者其他具备存储和计算能力的单元时,个人安全内核节点107关联的用户终端是指与该金属贴片、芯片或者其他具备存储和计算能力的单元通信并显示其中存储的数字资产凭证的终端。
当用户的生命周期未结束之前,用户可以在图2A所示的界面选择“设立遗嘱”功能选项,进入如图2B所示的界面。
在图2B的界面上,罗列了用户的所有数字资产凭证或者各种数字资产凭证类型,让用户去填写用户希望其每一项数字资产凭证或者每一数字资产凭证类型的继承人,并填写执行遗嘱的司法机构。执行遗嘱的司法机构的作用是启动并见证该数字资产凭证在用户生命周期结束后向指定的继承人转移的过程,起到公信的作用。
当用户在图2B的界面上针对每一项数字资产凭证填写完继承人和见证的司法机构后,如图2C所示,开始获取继承人、指定的司法机构的公钥。继承人的公钥是为了保证用户生命周期结束后给继承人的数字资产凭证的安全性。司法机构的公钥是为了对执行遗嘱的第三方司法机构是否是用户真正想要的司法机构进行验证,提高遗嘱的保密性。由于用户的 遗嘱用司法机构的公钥进行签名,只有真正的司法机构,才能解签名,通过验证,进行后续程序。
获得继承人的公钥后,用继承人的公钥对其对应的数字资产凭证进行签名。将用户Persk标识、继承人Persk标识、用继承人的公钥对数字资产凭证进行的签名放到遗嘱中。获得司法机构的公钥后,用司法机构公钥对当前遗嘱内容进行签名,将该签名也放入遗嘱中。此时遗嘱的内容如图2D所示,包括用户Persk标识、继承人Persk标识、用各继承人的公钥对相应数字资产凭证进行的签名、用司法机构公钥生成的遗嘱签名。各继承人的公钥对相应数字资产凭证进行的签名只有继承人自己用私钥才能解开,保证继承中数字资产凭证传递的安全性。用司法机构公钥生成的遗嘱签名只有用用户指定的司法机构的私钥才能通过验证,保证继承过程的可信性。
然后,如图2E所示,将生成的遗嘱记录到区块链上。
图2F-K不再是用户终端的界面图,而是司法机构节点145的界面图。用户在离世之前,在加入区块链网络时与区块链网络运营商签立智能合约。图1A-B的每个节点都作为一个区块链网络节点,能够获取到该智能合约。该智能合约中,用户指定离世后的继承程序发起人、证明人。
当接收到用户A的亲友B发出的、对用户A已经离世的启动请求时,显示图2F所示的界面。如果B恰恰是用户智能合约中指定的继承程序发起人,则开始继承验证程序,即将智能合约中指定的证明人C、D、E发出用户A离世确认请求,要求确认用户A是否真的离世,如图2G所示。
如果从证明人C、D、E都接到用户A已经离世的应答,确定用户A离世,开始继承程序,如图2H所示。
当司法机构节点145的工作人员在图2H的界面上选择“确认”后,进入图2I所示的界面,从区块链上找到带有用户A的Persk标识的遗嘱。由于区块链上的遗嘱包括用户Persk标识、继承人Persk标识、用各继承人的公钥对相应数字资产凭证进行的签名、用司法机构公钥生成的遗嘱签名,因此可以找到该遗嘱。然后,司法机构对遗嘱中的用司法机构公钥生成的遗嘱进行签名验证,如图2J所示。
如果签名验证成功,将遗嘱中用各继承人的公钥对相应数字资产凭证进行的签名取出,向遗嘱中对应继承人Persk标识的Persk发送,如图2K所示。继承人Persk收到后,用继承人私钥解签名,得到数字资产凭证的摘要,凭该摘要获得数字资产凭证。如果不是真正的继承人,没有继承人私钥,无法用该私钥解签名,也就得不到继承的数字资产凭证。
上述只是围绕用户离世后的数字资产凭证继承的应用场景展开描述,在用户失踪等其他应用场景中过程类似。
根据本申请的一个实施例,提供了一种数字资产凭证继承转移中的信息处理方法。数字资产凭证是以数字化形式存在的资产凭证,如电子理财产品单。数字资产凭证继承转移是指用户生命周期结束后用户的数字资产凭证转移到对应的继承人。生命周期是指用户从出生到离世或宣告失踪的期间,生命周期结束包括离世和宣告失踪。
另外,本申请提供的数字资产凭证继承转移中的信息处理方法由司法机构节点145执行,而且如图3所示,所述方法包括:
步骤210、司法机构节点145确定用户的生命周期结束;
步骤220、司法机构节点145获取用户的遗嘱,所述遗嘱包括用户个人安全内核节点的标识、各继承人个人安全内核节点的标识、各数字资产凭证用对应继承人个人安全内核节点的公钥进行的签名、所述遗嘱用司法机构节点公钥进行的签名;
步骤230、如果司法机构节点145对所述遗嘱用司法机构节点公钥进行的签名,用司法机构节点私钥进行签名验证成功,触发向所述遗嘱中的各继承人个人安全内核节点的标识的继承人个人安全内核节点,发送所述遗嘱中各数字资产凭证用对应继承人个人安全内核节点的公钥进行的签名,以便所述继承人个人安全内核节点对该签名,用所述继承人个人安全内核节点的私钥解密,得到数字资产凭证的摘要,根据得到的数字资产凭证的摘要,得到继承的数字资产凭证。
下面对以上步骤详细描述。
在步骤210,司法机构节点145确定用户的生命周期结束。
确定用户的生命周期结束可以采取官方发起的方式,也可以采用民间发起的方式,也可以采用官方和民间共同确认的方式。
在官方发起的方式中,步骤210包括:
司法机构节点145响应于来自调查节点146的生命周期结束通知,确定用户的生命周期结束。
调查节点146是司法机构委托的调查遗嘱继承中的各种情况的机构的终端。例如,司法机构是法院的情况下,调查节点146是法院设立的调查委员会的终端。当有人在法院报案用户离世或失踪后,法院委托调查委员会的人员调查该用户的社交关系,作出用户是否真正离世或应当被宣告失踪的判断,在调查节点146由该人员根据该判断结果生成生命周期结束通知,发送给司法机构节点145。生命周期结束通知是宣告用户已经离世或宣告失踪的消息。
该实施例的好处是,生命周期结束通知是由调查节点146的相关人员实际调查情况后得到的,比较全面,误差小。
在民间发起的方式中,步骤210包括:
司法机构节点145接收到启动节点的启动请求;
司法机构节点145通过社交操作系统平台,向多个证明方节点发送用户生命周期结束确认消息;
如果所述多个证明方节点的应答满足预定条件,则司法机构节点145确定用户的个人安全内核节点的生命周期结束。
启动节点是对遗嘱继承程序进行启动的终端。
在一个实施例中,启动节点用户是任何终端(包括法院终端等),即只要有人启动,就开启继承过程。
在另一个实施例中,启动节点是用户通讯录中的用户终端。也就是说,只有用户认识的人才能开启继承程序,避免假报案和无关骚扰。由于用户离世或失踪后,其个人安全内核节点客户端很可能也找不到,但用户的通讯录可以存储在个人安全内核节点服务器,从个人安全内核节点服务器中可以获取用户通讯录。
在另一个实施例中,启动节点是用户在生命周期期间在智能合约中指定的启动节点。例如,用户在生命周期期间,可以在智能合约指定一个启动节点标识,如某朋友的终端标识。该智能合约可以与用户个人安全内核节点标识对应,保存在所有区块链节点,也可以保存在区块链上。启动请求中含有用户个人安全内核节点标识,司法机构节点145可以从该启动请求中获得用户个人安全内核节点标识,从本地或者区块链上找到与该用户个人安全内核节点标识对应的智能合约,从而获取其中的启动节点标识。如果该标识是启动请求的发出者的标识,则开启继承过程。该实施例提高了开启继承的安全性。
在一个实施例中,智能合约是通过如下过程生成的:
显示智能合约模板列表;
响应于用户从智能合约模板列表选择智能合约模板并在选择的智能合约模板中填写内容,将填写的内容整合到智能合约模板中,为用户生成智能合约。
也就是说,系统内为用户提供多种智能合约模板,在模板中有一部分用户需要填写的内容。用户可以通过例如勾选的方式在列表中选择一个智能合约模板,并在模板中需要填写内容的位置填写内容。将用户填写的内容整合到选择的智能合约模板中,生成智能合约。
社交操作系统平台是指为用户提供身份证明、比一般应用服务完全平台具备更强的数据安全保护能力和普遍服务能力的平台,例如微信平台服务器、Facebook平台服务器。由于在该平台注册了大量用户,因此,可以通过该平台向多个证明方节点发送继承程序启动确认请求消息。继承程序启动确认请求是指要求确认用户是否离世或失踪,以便决定是否开启继承程序的请求。
在一个实施例中,所述多个证明方节点从用户通讯录中随机选出。用户通讯录如上所 述,可以从个人安全内核节点服务器中获取。该实施例中好处是,由于通讯录都是用户认识的人,从中随机选出,避免用户勾结一些好友作弊的风险。
在一个实施例中,所述多个证明方节点标识由用户在用户生命周期期间指定,并与上述启动节点一样,记录在智能合约中。智能合约与用户个人安全内核节点标识对应,存储在每个区块链节点上,或者存储在区块链上。司法机构节点145从启动请求中获得用户个人安全内核节点标识,在本地或区块链上查找到对应的智能合约,从智能合约中找到多个证明方节点标识,通过社交操作系统平台,向多个证明方节点发送用户生命周期结束确认消息。该实施例提高了用户选择遗嘱执行过程的灵活性。
这里的预定条件是指预先设定、多个证明方节点的应答应满足的条件。在一个实施例中,预定条件是,所述多个证明方节点的应答都是确认用户生命周期结束的应答。在一个实施例中,预定条件是,所述多个证明方节点中预定比例以上的应答都是确认用户生命周期结束的应答。
该民间发起的方式的优点是自动通过机器节点执行,自动化程度高,且避免政府审批调查的冗长耗时。
在官方和民间共同确认的方式中,所述如果所述多个证明方节点的应答满足预定条件,则司法机构节点145确定用户的生命周期结束,包括:
如果所述多个证明方节点的应答满足预定条件,且接收到来自调查节点的生命周期结束通知,则司法机构节点145确定用户的个人安全内核节点的生命周期结束。
也就是说,仅多个证明方节点的应答满足预定条件是不够的,还需要官方也给出了生命周期结束通知,两个条件都满足,才能确定用户的生命周期结束。该实施例提高了确定用户的生命周期结束的安全性。
在步骤220中,司法机构节点145获取用户的遗嘱,所述遗嘱包括用户个人安全内核节点的标识、各继承人个人安全内核节点的标识、各数字资产凭证用对应继承人个人安全内核节点的公钥进行的签名、所述遗嘱用司法机构节点公钥进行的签名。
在一个实施例中,司法机构节点145获取用户的遗嘱包括:司法机构节点145获取与用户的个人安全内核节点的标识对应的用户的遗嘱。也就是说,司法机构节点145可以按照用户的个人安全内核节点的标识,获取对应的用户的遗嘱。
用户个人安全内核节点的标识是将用户个人安全内核节点区别于其它人的个人安全内核节点的标记,它可以由字母、数字、符号等及其组合表示。遗嘱中记录用户个人安全内核节点的标识,是为了当用户生命周期结束后,根据该标识找到对应的遗嘱(包含该标识的遗嘱)。
各继承人个人安全内核节点的标识是针对用户的数字资产凭证,用户指定继承的人的个人安全内核节点的标识,是将该继承人个人安全内核节点区别于其它人的个人安全内核节点的标记。遗嘱中,针对每一项数字资产凭证,可以有不同的继承人个人安全内核节点的标识。
各数字资产凭证用对应继承人个人安全内核节点的公钥进行的签名是指,针对用户的各数字资产凭证,根据预定摘要算法生成摘要,用对应继承人个人安全内核节点的公钥对摘要加密得到的结果。直接传递数字资产凭证,被第三方截获,可以从中方便地取走数字资产凭证。由于签名是先生成摘要,再由对应继承人个人安全内核节点的公钥加密得到的,没有继承人个人安全内核节点的公钥是无法解签名的,提高了继承中数字资产凭证转移的安全性。
所述遗嘱用司法机构节点公钥进行的签名,是指用司法机构节点公钥对遗嘱当前内容进行的签名,包括对遗嘱当前内容按照预定摘要算法生成摘要、和用司法机构节点公钥对摘要加密。它具有验证执行遗嘱的司法机构节点是否是用户指定的司法机构节点的作用,因为如果执行遗嘱的司法机构节点不是用户指定的司法机构节点,它不具有司法机构节点私钥,无法对签名验证成功。它保证了继承中司法机构节点的可信度,提高继承程序的安全性。
在遗嘱生成之后,可以记录到区块链上,也可以存储在用户的个人安全内核节点服务 器。这是因为,用户生命周期结束后,很可能个人安全内核节点客户端也随着用户终端的丢失而丢失,遗嘱也可能消亡,将其存储在区块链上或个人安全内核节点服务器上,可以在用户生命周期结束后找回遗嘱。
在遗嘱上链存储的实施例中,步骤220包括:司法机构节点145从区块链上获取含有用户的个人安全内核节点的标识的遗嘱,作为与用户的个人安全内核节点的标识对应的用户的遗嘱,其中所述遗嘱生成后记录到该区块链上。
如上所述,所述遗嘱包括用户个人安全内核节点的标识、各继承人个人安全内核节点的标识、各数字资产凭证用对应继承人个人安全内核节点的公钥进行的签名、所述遗嘱用司法机构节点公钥进行的签名。由于启动请求中包含用户个人安全内核节点的标识,司法机构节点可以查找区块链上包含该标识的遗嘱,该遗嘱就是与用户的个人安全内核节点的标识对应的用户的遗嘱。
在一个实施例中,遗嘱还包括头信息。该头信息中包含遗嘱特征字和遗嘱长度。从区块链上获取含有用户的个人安全内核节点的标识的遗嘱,包括:
在区块链中识别到带有遗嘱特征字的头信息之后,按照头信息中的遗嘱长度识别遗嘱所关联的数据区块;
在识别出的数据区块中,确定是否含有用户的个人安全内核节点的标识,如含有,则识别出的数据区块构成含有用户的个人安全内核节点的标识的遗嘱。
头信息是指遗嘱作为数据区块记录到区块链上后,每个数据区块的区块头信息。每个数据区块还有区块体,其中记录遗嘱中的内容。遗嘱可能包括多个数据区块。如上所述,遗嘱包括用户个人安全内核节点的标识、各继承人个人安全内核节点的标识、各数字资产凭证用对应继承人个人安全内核节点的公钥进行的签名、所述遗嘱用司法机构节点公钥进行的签名,其中,不同继承人个人安全内核节点的标识、和相应不同的数字资产凭证用对应继承人个人安全内核节点的公钥进行的签名可能记载在不同数据区块中。
遗嘱特征字是表示区块链上的数据区块是关于遗嘱的数据区块的标志。没有该遗嘱特征字,代表该数据区块记录的不是遗嘱。有该遗嘱特征字,代表该数据区块记录的是遗嘱。由于区块链上记录各种数据区块,有一些数据区块与遗嘱完全无关,为了缩小搜索范围,在存放遗嘱的数据区块的区块头中设置遗嘱特征字。在区块链上找到该遗嘱特征字,认为包含该遗嘱特征字的数据区块是遗嘱数据区块。
遗嘱长度是表明遗嘱占用了区块链上连续数据区块的数量的标志。例如,遗嘱长度为7,代表在区块链上,从当前数据区块开始数7个数据区块,这些数据区块都是遗嘱关联的数据区块。
因此,在区块链中识别到带有遗嘱特征字的头信息之后,可以按照头信息中的遗嘱长度识别遗嘱所关联的数据区块,然后在这些数据区块范围内确定是否含有用户的个人安全内核节点的标识。这样做的好处是,相比于在整个区块链上搜索含有用户的个人安全内核节点的标识的数据区块,大大减小了搜索范围,提高了搜索效率。
如果确定在这些连续的数据区块范围内含有用户的个人安全内核节点的标识,该连续的数据区块范围(该遗嘱长度指示的数量的连续数据区块)构成含有用户的个人安全内核节点的标识的遗嘱。
在遗嘱存储在个人安全内核节点服务器的实施例中,所述个人安全内核节点包括个人安全内核节点客户端和个人安全内核节点服务器。步骤220包括:司法机构节点145从用户的个人安全内核节点的标识对应的个人安全内核节点服务器,获取遗嘱,作为与用户的个人安全内核节点的标识对应的用户的遗嘱,其中所述遗嘱由个人安全内核节点客户端生成后存储在个人安全内核节点服务器。
个人安全内核节点客户端生成遗嘱后,将其存储在个人安全内核节点服务器,该个人安全内核节点客户端和个人安全内核节点服务器具有同一个人安全内核节点标识。在启动请求中含有用户的个人安全内核节点的标识。这样,可以找到与该标识对应的个人安全内核节点服务器,从其获得遗嘱。
在步骤230中,如果司法机构节点145对所述遗嘱用司法机构节点公钥进行的签名, 用司法机构节点私钥进行签名验证成功,触发向所述遗嘱中的各继承人个人安全内核节点的标识的继承人个人安全内核节点,发送所述遗嘱中各数字资产凭证用对应继承人个人安全内核节点的公钥进行的签名,以便所述继承人个人安全内核节点对该签名,用所述继承人个人安全内核节点的私钥解密,得到数字资产凭证的摘要,根据得到的数字资产凭证的摘要,得到继承的数字资产凭证。
司法机构节点145获取到遗嘱后,司法机构节点145不应立即开始执行继承过程。因为如果自己并不是用户指定的司法机构节点,则自己无权执行后续的继承程序的。因此,司法机构节点145要先对所述遗嘱用司法机构节点公钥进行的签名,用司法机构节点私钥进行签名验证。
在一个实施例中,所述遗嘱还包括指定的执行该遗嘱的司法机构节点标识。如图2B所示,用户在界面上指定执行该遗嘱的司法机构节点标识,从而在图2D的遗嘱中含有该标识。
在该实施例中,如图4所示,所述司法机构节点145对所述遗嘱用司法机构节点公钥进行的签名,用司法机构节点私钥进行签名验证成功,包括:
步骤310、司法机构节点145获取遗嘱中指定的执行该遗嘱的司法机构节点标识;
步骤320、如果遗嘱中指定的执行该遗嘱的司法机构节点标识是当前执行所述方法的司法机构节点的标识,司法机构节点145对所述遗嘱用司法机构节点公钥进行的签名,用司法机构节点私钥进行签名验证成功。
由于遗嘱中具有指定的执行该遗嘱的司法机构节点标识,因此,可以从遗嘱中获取该标识。由于司法机构节点145本地存储着自己的标识,司法机构节点145将获取的标识与本地存储的自己的标识进行比对,如果一致,则用司法机构节点私钥,对遗嘱中的所述遗嘱用司法机构节点公钥进行的签名进行验证。
该实施例的好处是,综合司法机构节点标识比较和用司法机构节点公钥生成的签名的验证两项,来进行司法机构节点的权限验证,比单纯检验签名,更能提高司法机构节点权限验证的准确性。
在一个实施例中,步骤320包括:
如果遗嘱中指定的执行该遗嘱的司法机构节点标识是当前执行所述方法的司法机构节点的标识,司法机构节点145对所述遗嘱用司法机构节点公钥进行的签名,用司法机构节点私钥解密,得到解密后产生的遗嘱摘要;
司法机构节点145生成所述遗嘱的摘要;
如果解密后产生的遗嘱摘要与生成的遗嘱的摘要一致,则司法机构节点145确定对所述遗嘱用司法机构节点公钥进行的签名,用司法机构节点私钥进行签名验证成功。
由于生成遗嘱签名是包括对遗嘱内容按照预定摘要算法(例如哈希算法)生成摘要、和对摘要用司法机构节点公钥加密的过程,验证签名时遵循相反的过程。首先用司法机构节点私钥对签名解密,得到遗嘱内容的摘要。然后,再按照生成签名时同样的摘要算法,生成所述遗嘱的摘要。由于在生成遗嘱签名时,遗嘱中还没有放入签名,生成遗嘱签名基于的是遗嘱中除遗嘱签名之外的内容,因此,在一个实施例中,生成所述遗嘱的摘要包括:
将遗嘱中的所述遗嘱用司法机构节点公钥进行的签名去除;
对去除所述签名后的遗嘱应用生成所述遗嘱时同样的预定摘要算法,生成遗嘱的摘要。
也就是说,它要遵循生成遗嘱的签名时对生成摘要相同的过程,先将遗嘱中的所述遗嘱用司法机构节点公钥进行的签名去除,因为在生成遗嘱的签名时并没有对包含该签名的遗嘱生成摘要再加密,而是在没有包含该签名之前对遗嘱的内容生成摘要然后加密。另外,在司法机构节点145还要保存与用户的个人安全内核节点中同样的预定摘要算法。这样,对去除所述签名后的遗嘱应用该预定摘要算法,生成的摘要与生成遗嘱签名时的摘要才具有一致的比对基础。
对去除所述签名后的遗嘱应用该预定摘要算法后,将解密后产生的遗嘱摘要与生成的遗嘱的摘要比对,如果二者一致,则签名验证成功,认为当前执行遗嘱的司法机构节点就 是用户指定的司法机构节点。这时,就可以触发向所述遗嘱中的各继承人个人安全内核节点的标识的继承人个人安全内核节点,发送所述遗嘱中各数字资产凭证用对应继承人个人安全内核节点的公钥进行的签名。
触发的含义是可以由司法机构节点145自己完成,也可以指定另一其它节点完成,也可以启动区块链网络中的智能合约,由智能合约自动分配节点完成。
上述过程中,发送的是各数字资产凭证的签名而不是数字资产凭证本身,是因为第三方节点即使截获,也没有继承人个人安全内核节点的私钥,无法解签名,因而无法获得继承的数字资产凭证,提高继承中数字资产凭证的安全性。
由于对数字资产凭证用继承人个人安全内核节点的公钥签名包含对数字资产凭证根据预定摘要算法生成摘要,并对摘要用继承人个人安全内核节点的公钥加密的过程,解签名的过程也分为两步。首先,继承人个人安全内核节点对该签名,用所述继承人个人安全内核节点的私钥解密,得到数字资产凭证的摘要。然后,根据得到的数字资产凭证的摘要,得到继承的数字资产凭证。
根据得到的数字资产凭证的摘要,得到继承的数字资产凭证有多种实施方式。
在一个实施例中,所述根据得到的数字资产凭证的摘要,得到继承的数字资产凭证,包括:从区块链上获取与得到的数字资产凭证的摘要对应的数字资产凭证,其中,数字资产凭证生成后,与该数字资产凭证的摘要对应存储在区块链上。
该实施例遵循着数字资产凭证生成后立即上链的模式。用户个人安全内核节点与业务依赖方节点(例如理财公司终端)履行业务(例如签订购买理财产品的合同)后,生成与业务依赖方节点之间的数字资产凭证(例如理财产品单)。生成数字资产凭证后,立即根据预定摘要算法,生成该数字资产凭证的摘要,将该摘要与该数字资产凭证对应存储在区块链上。这样,从区块链上可以直接查询到得到的数字资产凭证的摘要对应的数字资产凭证。
在一个实施例中,个人安全内核节点包括个人安全内核节点客户端、和个人安全内核节点服务器。所述根据得到的数字资产凭证的摘要,得到继承的数字资产凭证,包括:从个人安全内核节点服务器获取与得到的数字资产凭证的摘要对应的数字资产凭证,其中,数字资产凭证由个人安全内核节点客户端生成后,与该数字资产凭证的摘要对应存储在个人安全内核节点服务器上。
该实施例中,个人安全内核节点客户端与业务依赖方节点生成数字资产凭证后,根据预定摘要算法,生成该数字资产凭证的摘要,将该摘要与该数字资产凭证对应存储在个人安全内核节点服务器上。这样,从个人安全内核节点服务器可以直接查询到得到的数字资产凭证的摘要对应的数字资产凭证。
在一个实施例中,所述遗嘱中还包括各数字资产凭证的业务依赖方节点标识。所述触发向所述遗嘱中的各继承人个人安全内核节点的标识的继承人个人安全内核节点,发送所述遗嘱中各数字资产凭证用对应继承人个人安全内核节点的公钥进行的签名,包括:触发向所述遗嘱中的各继承人个人安全内核节点的标识的继承人个人安全内核节点,发送所述遗嘱中各数字资产凭证用对应继承人个人安全内核节点的公钥进行的签名、以及各数字资产凭证的业务依赖方节点标识。
此时,所述根据得到的数字资产凭证的摘要,得到继承的数字资产凭证,包括:
向数字资产凭证的业务依赖方节点标识的业务依赖方节点发送得到的数字资产凭证的摘要;
从所述业务依赖方节点接收与所述数字资产凭证的摘要对应的数字资产凭证。
数字资产凭证都是用户个人安全内核节点与一个业务依赖方节点履行业务形成的,形成数字资产凭证后该数字资产凭证和该数字资产凭证的摘要在该业务依赖方节点备份保存。因此,可以从该业务依赖方节点,凭数据资产凭证的摘要,调回相应数字资产凭证。为了向业务依赖方节点请求,遗嘱中要包含该业务依赖方节点的标识,它可以在生成遗嘱时根据数字资产凭证中含有的业务依赖方节点标识生成(业务依赖方节点标识是数字资产凭证的重要字段,没有该字段无法兑现该数字资产)。向继承人个人安全内核节点发送数字资产凭证用对应继承人个人安全内核节点的公钥进行的签名时,将该业务依赖方节点标识 也同时发送。这样,继承人个人安全内核节点就可以向数字资产凭证的业务依赖方节点标识的业务依赖方节点发送得到的数字资产凭证的摘要。在业务依赖方节点,数字资产凭证与其摘要对应存储,这样,从所述业务依赖方节点就可以接收到与所述数字资产凭证的摘要对应的数字资产凭证。
在一个实施例中,所述继承的数字资产凭证中包含数字资产凭证依赖的业务依赖方节点标识,以便所述继承人个人安全内核节点与该业务依赖方节点标识的业务依赖方节点,根据继承的数字资产凭证,生成继承人节点与该业务依赖方节点之间的更新后数字资产凭证。
也就是说,虽然在步骤230中,继承人个人安全内核节点得到了继承的数字资产凭证,但该数字资产凭证仅是用户个人安全内核节点与依赖方节点形成的,并非继承人个人安全内核节点与依赖方节点形成的,因此,继承人个人安全内核节点要与依赖方节点形成更新后数字资产凭证。
在一个实施例中,所述与该业务依赖方节点标识的业务依赖方节点,根据继承的数字资产凭证,生成继承人节点与该业务依赖方节点之间的更新后数字资产凭证包括由继承人个人安全内核节点执行的以下过程:
继承人个人安全内核节点向该业务依赖方节点标识的业务依赖方节点,发送继承的数字资产凭证和继承人个人安全内核节点标识,以便所述业务依赖方节点根据继承的数字资产凭证和继承人个人安全内核节点标识,生成更新后数字资产凭证;
继承人个人安全内核节点接收所述业务依赖方节点发送的更新后数字资产凭证。
由于更新后数字资产凭证中的依赖方节点义务与继承的数字资产凭证的依赖方节点义务完全一致,只不过当事人由用户个人安全内核节点和业务依赖方节点分别变成了继承人个人安全内核节点和业务依赖方节点,因此,可以将继承数字资产凭证内容中仅将当事人信息由用户个人安全内核节点标识和业务依赖方节点标识分别变成继承人个人安全内核节点标识和业务依赖方节点标识,得到更新后数字资产凭证,向继承人个人安全内核节点发送。
该实施例的好处是,通过便捷的程序,转换继承的数字资产凭证,提高更新数字资产凭证的效率。
另外,经过上述过程,完成整个继承过程,可以将所述用户的个人安全内核节点设置为终止状态。将所述用户的个人安全内核节点设置为终止状态可以是由智能合约分配节点自动进行的。另外,也可以不在完成上述过程后立即将所述用户的个人安全内核节点设置为终止状态。用户的个人安全内核节点除了在继承中使用,还可能在一些其它的程序中用到。因此,可能除了继承之外,还要等到其它相关程序完成,让所述用户的个人安全内核节点变为终止状态。
用户的个人安全内核节点具有未启用、启用、暂停、终止几种状态。当用户未出生之前,用户的个人安全内核节点相应地处于未启用状态。在用户出生后,经过家长的申请,使该个人安全内核节点处于启用状态。在过程中,如遇到挂失等事件,有可能需要将个人安全内核节点设置到暂停状态,暂停状态下不得对该个人安全内核节点进行操作,直到恢复位置。当用户生命周期结束后,经过上述流程,并完成了其它可能会用到用户的个人安全内核节点的流程后,可以将个人安全内核节点设置为终止状态。终止状态下,该个人安全内核节点被废止,永久不得对该个人安全内核节点进行访问。
另外,有时遗嘱中仅仅指定继承人是不够的,随着继承适用的法律不同,继承的效果可能有很大差别。例如,在某些国家的法律规定,继承交继承税,而另外一些国家的法律规定,继承不交继承税。在一个实施例中,在图2B的界面上,用户不仅指定各数字资产凭证对应的继承人个人安全内核节点标识、和执行遗嘱继承的司法机构节点的标识,还指定遗嘱的继承适用法律。这样,在图2D所示的遗嘱中,可能还包含该遗嘱的继承适用法律。
在该实施例中,步骤230中,所述触发向所述遗嘱中的各继承人个人安全内核节点的标识的继承人个人安全内核节点,发送所述遗嘱中各数字资产凭证用对应继承人个人安全内核节点的公钥进行的签名,包括:
触发向所述遗嘱中的各继承人个人安全内核节点的标识的继承人个人安全内核节点,发送所述遗嘱中各数字资产凭证用对应继承人个人安全内核节点的公钥进行的签名、和遗嘱的继承适用法律,以便所述继承人个人安全内核节点得到继承的数字资产凭证后,执行所述继承适用法律对应的进程。
也就是说,由于遗嘱中还有继承适用法律,因此,触发向遗嘱中的数字资产凭证对应的继承人个人安全内核节点标识的继承人个人安全内核节点,发送的就不仅仅是遗嘱中各数字资产凭证用对应继承人个人安全内核节点的公钥进行的签名,还有遗嘱的继承适用法律。
每一种继承适用法律对应的继承进程可以事先编写好程序代码,存储在公共服务器上或各用户个人安全内核节点中。这样,在一个实施例中,执行所述继承适用法律对应的进程,包括由继承人个人安全内核节点执行的如下过程:根据接收到的继承适用法律,从公共服务器上或继承人个人安全内核节点中获取该继承适用法律对应的程序代码,并将继承的数字资产凭证输入该程序代码,从而执行所述继承适用法律对应的进程。
该实施例的好处是,使得继承能够按照用户指定的继承适用法律进行,提高继承的精细度。
另外,不是所有用户都会在生命周期结束之前设立遗嘱。当用户在生命周期结束之前没有设立遗嘱时,相当于法定继承的情形。除了遗嘱继承的情形,在一个实施例中,还将法定继承的数据处理自动化,实现了自动化缺省遗嘱继承。
如图5所示,在一个实施例中,在步骤210之后,所述方法还包括:
步骤225、如果司法机构节点145获取不到用户的遗嘱,根据所述用户的个人安全内核节点的身份,确定所述身份对应的法律;
步骤235、司法机构节点145获取所述用户的亲属关系;
步骤245、司法机构节点145获取用户的各数字资产凭证;
步骤255、针对获取的用户的每一个数字资产凭证,司法机构节点145按照确定的法律和所述亲属关系,确定各数字资产凭证对应的继承人个人安全内核节点标识;
步骤265、司法机构节点145获取确定的继承人个人安全内核节点标识的继承人个人安全内核节点的公钥;
步骤275、司法机构节点145将用户的每一个数字资产凭证,用对应的继承人个人安全内核节点的公钥进行签名,并发送到对应的继承人个人安全内核节点,以便所述继承人个人安全内核节点对该签名,用所述继承人个人安全内核节点的私钥解密,得到数字资产凭证的摘要,根据得到的数字资产凭证的摘要,得到继承的数字资产凭证。
下面对这些步骤进行详细描述。
在步骤225中,如果司法机构节点145获取不到用户的遗嘱,根据所述用户的个人安全内核节点的身份,确定所述身份对应的法律。
如果从区块链或者从用户个人安全内核节点服务器都获取不到用户的遗嘱,很可能用户没来及设立遗嘱就生命周期结束了,此时需要启动法定继承,根据所述用户的个人安全内核节点的身份,确定所述身份对应的法律。
由于用户生命周期结束后,其个人安全内核节点客户端可能找不到,因此,在一个实施例中,要事先将用户的个人安全内核节点的身份存储在个人安全内核节点服务器。根据所述用户的个人安全内核节点的身份,确定所述身份对应的法律,包括:
向启动请求中的用户的个人安全内核节点标识对应的个人安全内核节点服务器发送身份请求;
从所述个人安全内核节点服务器接收用户的个人安全内核节点的身份;
查找身份与法律对应关系表,确定所述身份对应的法律。
由于启动请求中具有用户的个人安全内核节点标识,它对应着唯一一组个人安全内核节点客户端及服务器,因此,可以向启动请求中的用户的个人安全内核节点标识对应的个人安全内核节点服务器发送身份请求。
用户的个人安全内核节点的身份是指用户的国籍、注册地区等。例如,用户是中国人, 可能适用中国法律进行继承。用户是美国人,可能适用美国法律进行继承。
在预定服务器或每个个人安全内核节点中存储用户的个人安全内核节点的身份与继承适用法律的对应关系表,即身份与法律对应关系表。从该对应关系表,可以根据所述用户的个人安全内核节点的身份,确定所述身份对应的法律。
在步骤235中,司法机构节点145获取所述用户的亲属关系。
在一个实施例中,用户的亲属关系列表存储在用户个人安全内核节点服务器中。因此,从该用户个人安全内核节点服务器中的用户的亲属关系列表,可以获取所述用户的亲属关系。
在步骤245中,司法机构节点145获取用户的各数字资产凭证。
在一个实施例中,用户的各数字资产凭证不仅存储在用户个人安全内核节点客户端中,还存储在用户个人安全内核节点服务器中。虽然用户个人安全内核节点客户端可能随着用户生命周期结束后无法找到,但可以按照启动请求中的用户个人安全内核节点,找到对应的用户个人安全内核节点服务器,从中获取用户的各数字资产凭证。
在步骤255中,针对获取的用户的每一个数字资产凭证,司法机构节点145按照确定的法律和所述亲属关系,确定各数字资产凭证对应的继承人个人安全内核节点标识。
在一个实施例中,在专门的服务器中或在每个个人安全内核节点中设置与各适用的法律对应的程序代码。将用户的各数字资产凭证和所述亲属关系输入该与确定的法律对应的程序代码,就得到按照该法律,各数字资产凭证对应的继承人个人安全内核节点标识。
在步骤265中,司法机构节点145获取确定的继承人个人安全内核节点标识的继承人个人安全内核节点的公钥。
在一个实施例中,获取继承人个人安全内核节点标识的继承人个人安全内核节点的公钥可以通过向区块链中专门的认证中心服务器(CA)请求实现。由于认证中心服务器(CA)是发放区块链节点公私钥的节点,可以从其请求任何区块链节点的公钥。
在另一个实施例中,获取确定的继承人个人安全内核节点标识的继承人个人安全内核节点的公钥,包括:从区块链上获取与确定的继承人个人安全内核节点标识对应的继承人个人安全内核节点的公钥,其中,继承人个人安全内核节点的公钥由继承人个人安全内核节点生成,并与继承人个人安全内核节点的公钥标识对应记录在区块链上。
该实施例中,不是由认证中心服务器生成并存储公钥,而是由各个个人安全内核节点生成并发布在区块链上。由于与个人安全内核节点标识对应记录在区块链上,在需要时可以凭个人安全内核节点标识在区块链上查找。
在另一实施例中,获取确定的继承人个人安全内核节点标识的继承人个人安全内核节点的公钥,包括:
通过社交操作系统平台,向继承人好友个人安全内核节点发送公钥获取请求,所述公钥获取请求包括确定的继承人个人安全内核节点标识;
从继承人好友个人安全内核节点,接收该继承人个人安全内核节点标识的继承人个人安全内核节点的公钥。
在社交操作系统平台上(例如微信),当两个用户互相加好友时,其中一个用户的公钥会发到另一个人的个人安全内核节点保存。而社交操作系统平台保存着所有互相加好友的人之间的好友关系。这样,通过社交操作系统平台,可以获取与该继承人个人安全内核节点标识具有好友关系的所有继承人个人安全内核节点标识列表,向该列表中任何一个个人安全内核节点标识的个人安全内核节点发送公钥获取请求,所述公钥获取请求包括确定的继承人个人安全内核节点标识。该个人安全内核节点返回该继承人个人安全内核节点标识的继承人个人安全内核节点的公钥。
在步骤275中,司法机构节点145将用户的每一个数字资产凭证,用对应的继承人个人安全内核节点的公钥进行签名,并发送到对应的继承人个人安全内核节点,以便所述继承人个人安全内核节点对该签名,用所述继承人个人安全内核节点的私钥解密,得到数字资产凭证的摘要,根据得到的数字资产凭证的摘要,得到继承的数字资产凭证。
该步骤与步骤230的区别仅在于,在步骤230中是按照遗嘱中数字资产凭证对应的继 承人安全内核节点发送用对应的继承人个人安全内核节点的公钥进行的签名,而步骤275中,是按照法律推导出的数字资产凭证对应的继承人安全内核节点发送用对应的继承人个人安全内核节点的公钥进行签名。大体过程相同,故不赘述。
该实施例的好处是,实现了法定继承的自动化,且保证继承中的安全性。
如图6所示,在一个实施例中,所述遗嘱由用户的个人安全内核节点通过以下过程生成:
步骤410、对于用户的个人安全内核节点中的数字资产凭证,接收用户对该数字资产凭证的继承人个人安全内核节点标识的指定;
步骤420、获取指定的继承人个人安全内核节点标识的继承人个人安全内核节点的公钥;
步骤430、将每一个数字资产凭证,用相应获取的指定的继承人个人安全内核节点标识的继承人个人安全内核节点的公钥进行签名,得到各数字资产凭证用对应继承人个人安全内核节点的公钥进行的签名;
步骤440、将用户个人安全内核节点的标识、各继承人个人安全内核节点的标识、各数字资产凭证用对应继承人个人安全内核节点的公钥进行的签名放入遗嘱中;
步骤450、接收用户对执行该遗嘱的司法机构节点标识的指定;
步骤460、获取所述司法机构节点标识的司法机构节点的公钥;
步骤470、将所述遗嘱中的当前内容用获取的司法机构节点的公钥签名,放入所述遗嘱。
下面,对以上过程进行详细描述。
在步骤410中,对于用户的个人安全内核节点中的数字资产凭证,接收用户对该数字资产凭证的继承人个人安全内核节点标识的指定。
图2B示出了一个针对个人安全内核节点中的数字资产凭证,用户指定继承人个人安全内核节点标识的界面。实际上,步骤410可以通过分类指定或分项指定实现。图2B是分项指定的一个例子的界面。
在分项指定的实施例中,步骤410包括:
显示用户的个人安全内核节点中的数字资产凭证列表;
针对数字资产凭证列表中的每个数字资产凭证,接收用户对该数字资产凭证的继承人个人安全内核节点标识的指定。
在该实施例中,图2B的界面上,向用户显示出包含用户的个人安全内核节点中的所有数字资产凭证的数字资产凭证列表。在列表中的每个数字资产凭证的下面,分别显示了指定对该数字资产凭证的继承人个人安全内核节点标识的下拉框。点击下拉框右部的箭头,下拉菜单弹出,显示了所有候选的继承人个人安全内核节点标识。所有候选的继承人个人安全内核节点标识可以从用户的个人安全内核节点中存储的用户通讯录中直接导出,也可以从用户的个人安全内核节点中存储的亲属关系列表中直接导出。当用户在下拉菜单中选择一个候选个人安全内核节点标识后,就认为指定了对该数字资产凭证的继承人个人安全内核节点标识。
该实施例的好处是便于用户针对每一项数字资产凭证分别指定相应继承人个人安全内核节点标识,提高遗嘱生成的精细度。
在分类指定的实施例中,步骤410包括:
显示用户的个人安全内核节点中的数字资产凭证类型列表;
针对数字资产凭证列表中的每个数字资产凭证类型,接收用户对该数字资产凭证类型的继承人个人安全内核节点标识的指定,其中,指定的继承人个人安全内核节点标识用于该数字资产凭证类型的每一个数字资产凭证。
该实施例的界面与图2B的不同之处在于,图2B的界面显示的是所有数字资产凭证的列表,该实施例的界面显示的是所有数字资产凭证类型(如理财产品单、保险产品单、股票交易单)的列表,这是因为通常用户希望针对同一种类型的数字资产凭证(理财产品单),指定同一个继承人继承。然后,针对数字资产凭证列表中的每个数字资产凭证类型,用户 对该数字资产凭证类型的继承人个人安全内核节点标识进行指定。指定后,这种类型的所有数字资产凭证在继承时都由该指定的继承人个人安全内核节点继承。
该实施例的好处是,针对通常用户希望针对同一种类型的数字资产凭证(理财产品单),指定同一个继承人继承的特点,提高遗嘱生成的效率。
在步骤420中,获取指定的继承人个人安全内核节点标识的继承人个人安全内核节点的公钥。
如前所述,获取指定的继承人个人安全内核节点标识的继承人个人安全内核节点的公钥可以向专门的认证中心服务器(CA)请求实现,也可以从区块链上获取,还可以通过社交操作系统平台,向继承人好友个人安全内核节点获取。由于前面已描述具体实现,这里为节约篇幅不再赘述。
在步骤430中,将每一个数字资产凭证,用相应获取的指定的继承人个人安全内核节点标识的继承人个人安全内核节点的公钥进行签名,得到各数字资产凭证用对应继承人个人安全内核节点的公钥进行的签名。
如前所述,将数字资产凭证用相应获取的指定的继承人个人安全内核节点标识的继承人个人安全内核节点的公钥进行签名的过程,包括基于预定摘要算法对数字资产凭证生成摘要、和用相应获取的指定的继承人个人安全内核节点标识的继承人个人安全内核节点的公钥对摘要加密的过程。
在步骤440中,将用户个人安全内核节点的标识、各继承人个人安全内核节点的标识、各数字资产凭证用对应继承人个人安全内核节点的公钥进行的签名放入遗嘱中。
将用户个人安全内核节点的标识放入遗嘱中是因为,在继承程序中要通过用户个人安全内核节点的标识找回遗嘱。将各继承人个人安全内核节点的标识、各数字资产凭证用对应继承人个人安全内核节点的公钥进行的签名放入遗嘱中,是因为在继承程序中需要向这些标识对应的继承人个人安全内核节点发送数字资产凭证用对应继承人个人安全内核节点的公钥进行的签名。
在步骤450中,接收用户对执行该遗嘱的司法机构节点标识的指定。
如图2B所示,用户可以在界面中的执行遗嘱的司法机构节点标识下拉框中进行指定。点击下拉框右部的箭头,下拉菜单弹出,显示了所有候选的司法机构节点标识。这些候选的司法机构节点标识是预先导入的。当用户在下拉菜单中选择一个候选司法机构节点标识后,就认为指定了执行该遗嘱的司法机构节点标识。
在步骤460中,获取所述司法机构节点标识的司法机构节点的公钥。
与步骤420类似,该步骤也可以向专门的认证中心服务器(CA)请求实现,也可以从区块链上获取,还可以通过社交操作系统平台,向继承人好友个人安全内核节点获取,故不赘述。
在步骤470中,将所述遗嘱中的当前内容用获取的司法机构节点的公钥签名,放入所述遗嘱。
该签名放入遗嘱的意义如前所述,其在继承程序中可以用来验证执行继承程序的司法机构节点是否是用户真正想要的司法机构节点。如果执行继承程序的司法机构节点不是用户指定的司法机构节点,没有司法机构节点的私钥,无法签名验证成功。
该实施例的好处是,通过快捷的方式,生成遗嘱,提高了遗嘱生成的效率。
如前所述,遗嘱中除了包括用户个人安全内核节点的标识、各继承人个人安全内核节点的标识、各数字资产凭证用对应继承人个人安全内核节点的公钥进行的签名、所述遗嘱用司法机构节点公钥进行的签名之外,还可以包含指定的司法机构节点标识。在该实施例中,在步骤470之前,生成遗嘱的方法还包括:将指定的司法机构节点标识放入遗嘱中(未示)。
由于在步骤450中,已经接收了用户对执行遗嘱的司法机构节点标识的指定,因此,在本步骤中,可以将该标识放入遗嘱中。
遗嘱在生成后,可以配置在不同的位置。如前所述,在步骤220中,获取用户的遗嘱时,可以从区块链上获取,也可以从用户个人安全内核节点服务器获取。实际上,也可以 从用户个人安全内核节点客户端获取,只不过用户个人安全内核节点客户端非常容易随着用户生命周期结束变得找不到,因此,从区块链上或用户个人安全内核节点服务器获取更有保障。在一个实施例中,根据遗嘱配置的安全性要求,可以分成多种安全模式,每种模式安全性等级不同。
在一个实施例中,所述遗嘱生成后通过以下过程配置:
显示安全模式列表,所述安全模式列表包括第一安全模式、第二安全模式、第三安全模式,其中,第一安全模式中,遗嘱存储在用户个人安全内核节点客户端中;第二安全模式中,遗嘱存储在用户个人安全内核节点客户端和服务器中;第三安全模式中,遗嘱存储在用户个人安全内核节点服务器中,并发布在区块链上;
响应于用户在安全模式列表中选择第一安全模式,将所述遗嘱存储在用户个人安全内核节点客户端中;
响应于用户在安全模式列表中选择第二安全模式,将遗嘱存储在用户个人安全内核节点客户端和服务器中;
响应于用户在安全模式列表中选择第三安全模式,将遗嘱存储在用户个人安全内核节点服务器中,并发布在区块链上。
遗嘱的配置是指遗嘱生成后的保存和维护。安全模式是指对应于不同安全性等级的、存储遗嘱的方式。第一安全模式中,遗嘱存储在用户个人安全内核节点客户端中,这样,用户手机丢失后可能找不回数字资产凭证,安全程度最低。第二安全模式中,遗嘱存储在用户个人安全内核节点客户端和服务器中。这样,用户手机丢失仍可找回资产,安全程度其次。第三安全模式中,遗嘱存储在用户个人安全内核节点客户端和服务器中,并发布在区块链上。这样,在其中一处找不到,还可以在另外一处查找,安全程度最高。
另外,当用户在生命周期期间生成了遗嘱后,用户可能会继续生成数字资产凭证,如与依赖方节点形成新的数字资产凭证(如购入新的理财产品,产生新的理财产品单)。对于这些新的数字资产凭证,并没有指定对应的继承人个人安全内核节点标识,因此,在用户生命周期结束后,这些新的数字资产凭证不能根据遗嘱继承。因此,在用户生成遗嘱后,用户个人安全内核节点中数字资产凭证又增加的情况下,可以有让用户补充指定该数字资产凭证的继承人个人安全内核节点标识,和自动为用户指定该数字资产凭证的继承人个人安全内核节点标识两种实施方式。
在让用户补充指定该数字资产凭证的继承人个人安全内核节点标识的实施例中,如图7所示,所述遗嘱由用户的个人安全内核节点通过以下过程更新:
步骤510、当所述用户的个人安全内核节点中增加数字资产凭证时,向用户显示指定该数字资产凭证的继承人个人安全内核节点标识的界面;
步骤520、在所述界面上接收用户对该数字资产凭证的继承人个人安全内核节点标识的指定;
步骤530、获取指定的继承人个人安全内核节点标识的继承人个人安全内核节点的公钥;
步骤540、对增加的数字资产凭证,用相应获取的指定的继承人个人安全内核节点标识的继承人个人安全内核节点的公钥进行签名,得到增加的数字资产凭证用对应继承人个人安全内核节点的公钥进行的签名;
步骤550、将为增加的数字资产凭证指定的继承人个人安全内核节点标识、增加的数字资产凭证用对应继承人个人安全内核节点的公钥进行的签名,添加到遗嘱中;
步骤560、将遗嘱中当前的用获取的司法机构节点的公钥的签名去掉;
步骤570、将所述遗嘱中的当前内容用获取的司法机构节点的公钥签名,放入所述遗嘱。
下面对步骤510-570进行详细描述。
在步骤510中,当所述用户的个人安全内核节点中增加数字资产凭证时,向用户显示指定该数字资产凭证的继承人个人安全内核节点标识的界面。
在一个实施例中,用户的个人安全内核节点中具有检测模块,当有新的数字资产凭证 写入个人安全内核节点(即用户个人安全内核节点与依赖方节点履行业务后产生凭据,即数字资产凭证,写入个人安全内核节点的个人资产保险箱中)时,检测模块会检测到这一情况,显示一个类似于图2B的界面,该界面中列出了增加的数字资产凭证,在下面有指定继承人个人安全内核节点的下拉框。点击右部的箭头,可以显示下拉菜单,下拉菜单有所有候选继承人个人安全内核节点标识的列表,让用户选择。
在步骤520中,在所述界面上接收用户对该数字资产凭证的继承人个人安全内核节点标识指定。
当用户在下拉菜单中选择一个继承人个人安全内核节点标识,就认为接收到了用户对该数字资产凭证的继承人个人安全内核节点标识的指定。
在步骤530中,获取指定的继承人个人安全内核节点标识的继承人个人安全内核节点的公钥。
与步骤420类似,该步骤也可以向专门的认证中心服务器(CA)请求实现,也可以从区块链上获取,还可以通过社交操作系统平台,向继承人好友个人安全内核节点获取,故不赘述。
在步骤540中,对增加的数字资产凭证,用相应获取的指定的继承人个人安全内核节点标识的继承人个人安全内核节点的公钥进行签名,得到增加的数字资产凭证用对应继承人个人安全内核节点的公钥进行的签名。
该步骤与步骤430类似,包括按预定的摘要算法生成增加的数字资产凭证的摘要,并用相应获取的指定的继承人个人安全内核节点标识的继承人个人安全内核节点的公钥对摘要加密的过程。
在步骤550中,将为增加的数字资产凭证指定的继承人个人安全内核节点标识、增加的数字资产凭证用对应继承人个人安全内核节点的公钥进行的签名,添加到遗嘱中。
该步骤与步骤440类似,只不过步骤550是仅对增加的数字资产凭证,执行将继承人个人安全内核节点标识和相应签名增加到遗嘱中,故不赘述。
在步骤560中,将遗嘱中当前的用获取的司法机构节点的公钥的签名去掉。
由于在470中生成遗嘱用司法机构节点的公钥的签名时,是针对当时生成遗嘱时遗嘱中的当前内容进行的签名,在由于遗嘱当前内容增加了步骤550中添加的内容,导致签名继承有变化,因此,需要重新签名。但是遗嘱中该签名本身不是签名基础的一部分,在形成新的遗嘱用司法机构节点的公钥的签名时,首先要将该签名去掉,在此基础上,将所述遗嘱中的当前内容用获取的司法机构节点的公钥签名。这时的当前内容就包括了步骤550中添加的内容。
在步骤570中,将所述遗嘱中的当前内容用获取的司法机构节点的公钥签名,放入所述遗嘱。
上述过程在遗嘱生成后用户的数字资产凭证增加的情况下,提供了一种简单易行的更新遗嘱的方式,避免了遗嘱中一些新增加的数字资产凭证将来可能没有继承人的问题。
在自动为新增加的数字资产凭证补充该数字资产凭证的继承人个人安全内核节点标识的情况下,在一个实施例中,如图8所示,所述遗嘱由用户的个人安全内核节点通过以下过程更新:
步骤510’、当所述用户的个人安全内核节点中增加数字资产凭证时,根据遗嘱中为已有的数字资产凭证指定的继承人个人安全内核节点标识,确定增加的数字资产凭证对应的继承人个人安全内核节点标识;
步骤520’、获取增加的数字资产凭证对应的继承人个人安全内核节点标识的继承人个人安全内核节点的公钥;
步骤530’、对增加的数字资产凭证,用相应获取的指定的继承人个人安全内核节点标识的继承人个人安全内核节点的公钥进行签名,得到增加的数字资产凭证用对应继承人个人安全内核节点的公钥进行的签名;
步骤540’、将为增加的数字资产凭证指定的继承人个人安全内核节点标识、增加的数字资产凭证用对应继承人个人安全内核节点的公钥进行的签名,添加到遗嘱中;
步骤550’、将遗嘱中当前的用获取的司法机构节点的公钥的签名去掉;
步骤560’、将所述遗嘱中的当前内容用获取的司法机构节点的公钥签名,放入所述遗嘱。
下面对上述步骤进行详细描述。
在步骤510’中,当所述用户的个人安全内核节点中增加数字资产凭证时,根据遗嘱中为已有的数字资产凭证指定的继承人个人安全内核节点标识,确定增加的数字资产凭证对应的继承人个人安全内核节点标识。
判断所述用户的个人安全内核节点中增加数字资产凭证的方法与步骤510相同。
在一个实施例中,所述根据遗嘱中为已有的数字资产凭证指定的继承人个人安全内核节点标识,确定增加的数字资产凭证对应的继承人个人安全内核节点标识,包括:
获取增加的数字资产凭证的类型;
查找遗嘱中已为相同类型的数字资产凭证指定的继承人个人安全内核节点标识;
如果遗嘱中已为相同类型的数字资产凭证指定的继承人个人安全内核节点标识一致,将遗嘱中已为相同类型的数字资产凭证指定的继承人个人安全内核节点标识确定为增加的数字资产凭证对应的继承人个人安全内核节点标识。
由于数字资产凭证中含有数字资产凭证的类型字段,因此,从该数字资产凭证的类型字段可以获取增加的数字资产凭证的类型。
例如,增加的数字资产凭证的类型为理财产品,查找遗嘱中已为理财产品类型的数字资产凭证指定继承人个人安全内核节点标识。如果遗嘱中之前有5个理财产品类型的数字资产凭证,为这些数字资产凭证指定的继承人个人安全内核节点标识就有5个,但这5个可能是相同的继承人个人安全内核节点标识。即,遗嘱中已为相同类型的数字资产凭证指定的继承人个人安全内核节点标识一致,这时,用户很可能希望对于新增加的数字资产凭证也指定同样的继承人个人安全内核节点继承,因此,将遗嘱中已为相同类型的数字资产凭证指定的继承人个人安全内核节点标识确定为增加的数字资产凭证对应的继承人个人安全内核节点标识。
在一个实施例中,所述根据遗嘱中为已有的数字资产凭证指定的继承人个人安全内核节点标识,确定增加的数字资产凭证对应的继承人个人安全内核节点标识,还包括:
如果遗嘱中已为相同类型的数字资产凭证指定的继承人个人安全内核节点标识不一致,将遗嘱中已为相同类型的数字资产凭证指定的多个继承人个人安全内核节点标识中最多的继承人个人安全内核节点标识,确定为增加的数字资产凭证对应的继承人个人安全内核节点标识。
例如,如果遗嘱中之前有5个理财产品类型的数字资产凭证,为这些数字资产凭证指定的继承人个人安全内核节点标识就有5个,其中3个是继承人个人安全内核节点A的标识,2个是继承人个人安全内核节点B的标识,这时两者多的一个,可能是用户更希望指定的,因此,自动将将遗嘱中已为相同类型的数字资产凭证指定的5个继承人个人安全内核节点标识中最多的继承人个人安全内核节点标识,即继承人个人安全内核节点A的标识,确定为增加的数字资产凭证对应的继承人个人安全内核节点标识。
该实施例基于之前为相同类型的数字资产凭证指定的继承人个人安全内核节点标识,来确定为新增加的数字资产凭证指定的继承人个人安全内核节点标识,由于用户倾向于对于同类数字资产凭证,指定同一继承人个人安全内核节点,该实施例提高了自动指定继承人个人安全内核节点标识的准确性。
另外,如果遗嘱中没有找到相同类型的数字资产凭证,则可以按照类似步骤510-520的方式,让用户手动选择希望增加的数字资产凭证对应的继承人个人安全内核节点标识。
在一个实施例中,所述根据遗嘱中为已有的数字资产凭证指定的继承人个人安全内核节点标识,确定增加的数字资产凭证对应的继承人个人安全内核节点标识,包括:
获取增加的数字资产凭证的业务依赖方节点标识;
查找遗嘱中已为相同业务依赖方节点标识的数字资产凭证指定的继承人个人安全内核节点标识;
如果遗嘱中已为相同业务依赖方节点标识的数字资产凭证指定的继承人个人安全内核节点标识一致,将遗嘱中已为相同业务依赖方节点标识的数字资产凭证指定的继承人个人安全内核节点标识确定为增加的数字资产凭证对应的继承人个人安全内核节点标识。
由于数字资产凭证中也含有业务依赖方节点标识字段,因此,从该依赖方节点标识字段可以获取增加的数字资产凭证的业务依赖方节点标识。
例如,增加的数字资产凭证是一个从理财公司A购买的理财产品,因此,业务依赖方节点标识是理财公司A的终端标识。查找遗嘱中为从理财公司A终端形成的数字资产凭证(例如理财产品等)指定的继承人个人安全内核节点标识有5个,但这5个可能是相同的继承人个人安全内核节点标识,这时就将该相同的继承人个人安全内核节点标识作为增加的数字资产凭证对应的继承人个人安全内核节点标识。
在一个实施例中,所述根据遗嘱中为已有的数字资产凭证指定的继承人个人安全内核节点标识,确定增加的数字资产凭证对应的继承人个人安全内核节点标识,还包括:
如果遗嘱中已为相同业务依赖方节点标识的数字资产凭证指定的继承人个人安全内核节点标识不一致,将遗嘱中已为相同业务依赖方节点标识的数字资产凭证指定的多个继承人个人安全内核节点标识中最多的继承人个人安全内核节点标识,确定为增加的数字资产凭证对应的继承人个人安全内核节点标识。
例如,如果遗嘱中之前有5个理财产品是从理财公司A购买的,为这些数字资产凭证指定的继承人个人安全内核节点标识就有5个,其中3个是继承人个人安全内核节点A的标识,2个是继承人个人安全内核节点B的标识,这时两者多的一个,可能是用户更希望指定的,因此,自动将将遗嘱中已为相同业务依赖方节点标识的数字资产凭证指定的5个继承人个人安全内核节点标识中最多的继承人个人安全内核节点标识,即继承人个人安全内核节点A的标识,确定为增加的数字资产凭证对应的继承人个人安全内核节点标识。
该实施例基于之前为相同业务依赖方节点标识的数字资产凭证指定的继承人个人安全内核节点标识,来确定为新增加的数字资产凭证指定的继承人个人安全内核节点标识,由于用户倾向于对于同一业务依赖方节点的数字资产凭证,指定同一继承人个人安全内核节点,该实施例提高了自动指定继承人个人安全内核节点标识的准确性。
在步骤520’中,获取增加的数字资产凭证对应的继承人个人安全内核节点标识的继承人个人安全内核节点的公钥。
与步骤530类似,该步骤也可以向专门的认证中心服务器(CA)请求实现,也可以从区块链上获取,还可以通过社交操作系统平台,向继承人好友个人安全内核节点获取,故不赘述。
在步骤530’中,对增加的数字资产凭证,用相应获取的指定的继承人个人安全内核节点标识的继承人个人安全内核节点的公钥进行签名,得到增加的数字资产凭证用对应继承人个人安全内核节点的公钥进行的签名。
该步骤与步骤540类似,故不赘述。
在步骤540’中,将为增加的数字资产凭证指定的继承人个人安全内核节点标识、增加的数字资产凭证用对应继承人个人安全内核节点的公钥进行的签名,添加到遗嘱中。
该步骤与步骤550类似,故不赘述。
在步骤550’中,将遗嘱中当前的用获取的司法机构节点的公钥的签名去掉。
该步骤与步骤560类似,故不赘述。
在步骤560’中,将所述遗嘱中的当前内容用获取的司法机构节点的公钥签名,放入所述遗嘱。
该步骤与步骤570类似,故不赘述。
该实施例实现了自动根据用户个人安全内核节点中已有的数字资产凭证,为新增加的数字资产凭证分配继承人个人安全内核节点标识,提高了遗嘱更新的自动化程度。
另外,如果遗嘱中没有找到相同业务依赖方节点标识的数字资产凭证,则可以按照类似步骤510-520的方式,让用户手动选择希望增加的数字资产凭证对应的继承人个人安全内核节点标识。
如图9所示,根据一个实施例,还提供了一种司法机构节点,包括:
生命周期结束确定单元610,用于确定用户的生命周期结束;
遗嘱获取单元620,用于获取用户的遗嘱,所述遗嘱包括用户个人安全内核节点的标识、各继承人个人安全内核节点的标识、各数字资产凭证用对应继承人个人安全内核节点的公钥进行的签名、所述遗嘱用司法机构节点公钥进行的签名;
第一数字资产凭证签名发送单元630,用于如果对所述遗嘱用司法机构节点公钥进行的签名,用司法机构节点私钥进行签名验证成功,触发向所述遗嘱中的各继承人个人安全内核节点的标识的继承人个人安全内核节点,发送所述遗嘱中各数字资产凭证用对应继承人个人安全内核节点的公钥进行的签名,以便所述继承人个人安全内核节点对该签名,用所述继承人个人安全内核节点的私钥解密,得到数字资产凭证的摘要,根据得到的数字资产凭证的摘要,得到继承的数字资产凭证。
在一个实施例中,所述生命周期结束确定单元610进一步用于:
响应于来自调查节点的生命周期结束通知,确定用户的生命周期结束。
在一个实施例中,所述生命周期结束确定单元610进一步用于:
接收到启动节点的启动请求;
通过社交操作系统平台,向多个证明方节点发送继承程序启动确认请求;
如果所述多个证明方节点的应答满足预定条件,则确定用户的生命周期结束。
在一个实施例中,所述如果所述多个证明方节点的应答满足预定条件,则确定用户的生命周期结束,包括:
如果所述多个证明方节点的应答满足预定条件,且接收到来自调查节点的生命周期结束通知,则确定用户的生命周期结束。
在一个实施例中,所述遗嘱还包括指定的执行该遗嘱的司法机构节点标识。所述对所述遗嘱用司法机构节点公钥进行的签名,用司法机构节点私钥进行签名验证成功,包括:
获取遗嘱中指定的执行该遗嘱的司法机构节点标识;
如果遗嘱中指定的执行该遗嘱的司法机构节点标识是当前执行所述方法的司法机构节点的标识,对所述遗嘱用司法机构节点公钥进行的签名,用司法机构节点私钥进行签名验证成功。
在一个实施例中,所述如果遗嘱中指定的执行该遗嘱的司法机构节点标识是当前执行所述方法的司法机构节点的标识,对所述遗嘱用司法机构节点公钥进行的签名,用司法机构节点私钥进行签名验证成功,包括:
如果遗嘱中指定的执行该遗嘱的司法机构节点标识是当前执行所述方法的司法机构节点的标识,对所述遗嘱用司法机构节点公钥进行的签名,用司法机构节点私钥解密,得到解密后产生的遗嘱摘要;
生成所述遗嘱的摘要;
如果解密后产生的遗嘱摘要与生成的遗嘱的摘要一致,则确定对所述遗嘱用司法机构节点公钥进行的签名,用司法机构节点私钥进行签名验证成功。
在一个实施例中,所述继承的数字资产凭证中包含数字资产凭证依赖的业务依赖方节点标识,以便所述继承人个人安全内核节点与该业务依赖方节点标识的业务依赖方节点,根据继承的数字资产凭证,生成继承人节点与该业务依赖方节点之间的更新后数字资产凭证。
在一个实施例中,所述遗嘱还包括所述遗嘱的继承适用法律,所述触发向所述遗嘱中的各继承人个人安全内核节点的标识的继承人个人安全内核节点,发送所述遗嘱中各数字资产凭证用对应继承人个人安全内核节点的公钥进行的签名,包括:
触发向所述遗嘱中的各继承人个人安全内核节点的标识的继承人个人安全内核节点,发送所述遗嘱中各数字资产凭证用对应继承人个人安全内核节点的公钥进行的签名、和遗嘱的继承适用法律,以便所述继承人个人安全内核节点得到继承的数字资产凭证后,执行所述继承适用法律对应的进程。
在一个实施例中,所述司法机构节点还包括:
身份对应法律确定单元,用于如果获取不到用户的遗嘱,根据所述用户的个人安全内核节点的身份,确定所述身份对应的法律;
亲属关系获取单元,用于获取所述用户的亲属关系;
数字资产凭证获取单元,用于获取用户的各数字资产凭证;
继承人个人安全内核节点标识确定单元,用于针对获取的用户的每一个数字资产凭证,按照确定的法律和所述亲属关系,确定各数字资产凭证对应的继承人个人安全内核节点标识;
继承人个人安全内核节点公钥获取单元,用于获取确定的继承人个人安全内核节点标识的继承人个人安全内核节点的公钥;
第二数字资产凭证签名发送单元,用于将用户的每一个数字资产凭证,用对应的继承人个人安全内核节点的公钥进行签名,并发送到对应的继承人个人安全内核节点,以便所述继承人个人安全内核节点对该签名,用所述继承人个人安全内核节点的私钥解密,得到数字资产凭证的摘要,根据得到的数字资产凭证的摘要,得到继承的数字资产凭证。
在一个实施例中,所述遗嘱由用户的个人安全内核节点通过以下过程生成:
对于用户的个人安全内核节点中的数字资产凭证,接收用户对该数字资产凭证的继承人个人安全内核节点标识的指定;
获取指定的继承人个人安全内核节点标识的继承人个人安全内核节点的公钥;
将每一个数字资产凭证,用相应获取的指定的继承人个人安全内核节点标识的继承人个人安全内核节点的公钥进行签名,得到各数字资产凭证用对应继承人个人安全内核节点的公钥进行的签名;
将用户个人安全内核节点的标识、各继承人个人安全内核节点的标识、各数字资产凭证用对应继承人个人安全内核节点的公钥进行的签名放入遗嘱中;
接收用户对执行该遗嘱的司法机构节点标识的指定;
获取所述司法机构节点标识的司法机构节点的公钥;
将所述遗嘱中的当前内容用获取的司法机构节点的公钥签名,放入所述遗嘱。
在一个实施例中,在将所述遗嘱用获取的司法机构节点的公钥签名,放入所述遗嘱之前,所述的遗嘱的生成过程还包括:
将指定的司法机构节点标识放入遗嘱中。
在一个实施例中,所述遗嘱生成后通过以下过程配置:
显示安全模式列表,所述安全模式列表包括第一安全模式、第二安全模式、第三安全模式,其中,第一安全模式中,遗嘱存储在用户个人安全内核节点客户端中;第二安全模式中,遗嘱存储在用户个人安全内核节点客户端和服务器中;第三安全模式中,遗嘱存储在用户个人安全内核节点服务器中,并发布在区块链上;
响应于用户在安全模式列表中选择第一安全模式,将所述遗嘱存储在用户个人安全内核节点客户端中;
响应于用户在安全模式列表中选择第二安全模式,将遗嘱存储在用户个人安全内核节点客户端和服务器中;
响应于用户在安全模式列表中选择第三安全模式,将遗嘱存储在用户个人安全内核节点服务器中,并发布在区块链上。
在一个实施例中,所述遗嘱由用户的个人安全内核节点通过以下过程更新:
当所述用户的个人安全内核节点中增加数字资产凭证时,向用户显示指定该数字资产凭证的继承人个人安全内核节点标识的界面;
在所述界面上接收用户对该数字资产凭证的继承人个人安全内核节点标识的指定;
获取指定的继承人个人安全内核节点标识的继承人个人安全内核节点的公钥;
对增加的数字资产凭证,用相应获取的指定的继承人个人安全内核节点标识的继承人个人安全内核节点的公钥进行签名,得到增加的数字资产凭证用对应继承人个人安全内核节点的公钥进行的签名;
将为增加的数字资产凭证指定的继承人个人安全内核节点标识、增加的数字资产凭证用对应继承人个人安全内核节点的公钥进行的签名,添加到遗嘱中;
将遗嘱中当前的用获取的司法机构节点的公钥的签名去掉;
将所述遗嘱中的当前内容用获取的司法机构节点的公钥签名,放入所述遗嘱。
在一个实施例中,所述遗嘱由用户的个人安全内核节点通过以下过程更新:
当所述用户的个人安全内核节点中增加数字资产凭证时,根据遗嘱中为已有的数字资产凭证指定的继承人个人安全内核节点标识,确定增加的数字资产凭证对应的继承人个人安全内核节点标识;
获取增加的数字资产凭证对应的继承人个人安全内核节点标识的继承人个人安全内核节点的公钥;
对增加的数字资产凭证,用相应获取的指定的继承人个人安全内核节点标识的继承人个人安全内核节点的公钥进行签名,得到增加的数字资产凭证用对应继承人个人安全内核节点的公钥进行的签名;
将为增加的数字资产凭证指定的继承人个人安全内核节点标识、增加的数字资产凭证用对应继承人个人安全内核节点的公钥进行的签名,添加到遗嘱中;
将遗嘱中当前的用获取的司法机构节点的公钥的签名去掉;
将所述遗嘱中的当前内容用获取的司法机构节点的公钥签名,放入所述遗嘱。
根据本申请实施例的数字资产凭证继承转移中的信息处理方法可以由图10的司法机构节点145实现。
如图10所示,司法机构节点145以通用计算设备的形式表现。司法机构节点145的组件可以包括但不限于:上述至少一个处理单元810、上述至少一个存储单元820、连接不同系统组件(包括存储单元820和处理单元810)的总线830。
其中,所述存储单元存储有程序代码,所述程序代码可以被所述处理单元810执行,使得所述处理单元810执行本说明书上述示例性方法的描述部分中描述的根据本发明各种示例性实施方式的步骤。例如,所述处理单元810可以执行如图3中所示的各个步骤。
存储单元820可以包括易失性存储单元形式的可读介质,例如随机存取存储单元(RAM)8201和/或高速缓存存储单元8202,还可以进一步包括只读存储单元(ROM)8203。
存储单元820还可以包括具有一组(至少一个)程序模块8205的程序/实用工具8204,这样的程序模块8205包括但不限于:社交操作系统、一个或者多个应用程序、其它程序模块以及程序数据,这些示例中的每一个或某种组合中可能包括网络环境的实现。
总线830可以为表示几类总线结构中的一种或多种,包括存储单元总线或者存储单元控制器、外围总线、图形加速端口、处理单元或者使用多种总线结构中的任意总线结构的局域总线。
司法机构节点145也可以与一个或多个外部设备700(例如键盘、指向设备、蓝牙设备等)通信,还可与一个或者多个使得用户能与该司法机构节点145交互的设备通信,和/或与使得该司法机构节点145能与一个或多个其它计算设备进行通信的任何设备(例如路由器、调制解调器等等)通信。这种通信可以通过输入/输出(I/O)接口850进行。并且,司法机构节点145还可以通过网络适配器860与一个或者多个网络(例如局域网(LAN),广域网(WAN)和/或公共网络,例如因特网)通信。如图所示,网络适配器860通过总线830与司法机构节点145的其它模块通信。应当明白,尽管图中未示出,可以结合司法机构节点145使用其它硬件和/或软件模块,包括但不限于:微代码、设备驱动器、冗余处理单元、外部磁盘驱动阵列、RAID系统、磁带驱动器以及数据备份存储系统等。
通过以上的实施方式的描述,本领域的技术人员易于理解,这里描述的示例实施方式可以通过软件实现,也可以通过软件结合必要的硬件的方式来实现。因此,根据本申请实施方式的技术方案可以以软件产品的形式体现出来,该软件产品可以存储在一个非易失性存储介质(可以是CD-ROM,U盘,移动硬盘等)中或网络上,包括若干指令以使得一台计算设备(可以是个人计算机、服务器、终端装置、或者网络设备等)执行根据本申请实施方式的方法。
在本申请的示例性实施例中,还提供了一种计算机程序介质,其上存储有计算机可读指令,当所述计算机可读指令被计算机的处理器执行时,使计算机执行上述方法实施例部分描述的方法。
在本申请的示例性实施例中,还提供了一种包括指令的计算机程序产品,当其在计算机上运行时,使得所述计算机执行上述方法实施例部分描述的方法。
其中,所述计算机程序产品可以采用便携式紧凑盘只读存储器(CD-ROM)并包括程序代码,并可以在终端设备,例如个人电脑上运行。然而,本发明的程序产品不限于此,在本文件中,可读存储介质可以是任何包含或存储程序的有形介质,该程序可以被指令执行系统、装置或者器件使用或者与其结合使用。
所述程序产品可以采用一个或多个可读介质的任意组合。可读介质可以是可读信号介质或者可读存储介质。可读存储介质例如可以为但不限于电、磁、光、电磁、红外线、或半导体的系统、装置或器件,或者任意以上的组合。可读存储介质的更具体的例子(非穷举的列表)包括:具有一个或多个导线的电连接、便携式盘、硬盘、随机存取存储器(RAM)、只读存储器(ROM)、可擦式可编程只读存储器(EPROM或闪存)、光纤、便携式紧凑盘只读存储器(CD-ROM)、光存储器件、磁存储器件、或者上述的任意合适的组合。
计算机可读信号介质可以包括在基带中或者作为载波一部分传播的数据信号,其中承载了可读程序代码。这种传播的数据信号可以采用多种形式,包括但不限于电磁信号、光信号或上述的任意合适的组合。可读信号介质还可以是可读存储介质以外的任何可读介质,该可读介质可以发送、传播或者传输用于由指令执行系统、装置或者器件使用或者与其结合使用的程序。
可读介质上包含的程序代码可以用任何适当的介质传输,包括但不限于无线、有线、光缆、RF等等,或者上述的任意合适的组合。
可以以一种或多种程序设计语言的任意组合来编写用于执行本发明操作的程序代码,所述程序设计语言包括面向对象的程序设计语言—诸如Java、C++等,还包括常规的过程式程序设计语言—诸如“C”语言或类似的程序设计语言。程序代码可以完全地在用户计算设备上执行、部分地在用户设备上执行、作为一个独立的软件包执行、部分在用户计算设备上部分在远程计算设备上执行、或者完全在远程计算设备或服务器上执行。在涉及远程计算设备的情形中,远程计算设备可以通过任意种类的网络,包括局域网(LAN)或广域网(WAN),连接到用户计算设备,或者,可以连接到外部计算设备(例如利用因特网服务提供商来通过因特网连接)。
应当注意,尽管在上文详细描述中提及了用于动作执行的设备的若干模块或者单元,但是这种划分并非强制性的。实际上,根据本申请的实施方式,上文描述的两个或更多模块或者单元的特征和功能可以在一个模块或者单元中具体化。反之,上文描述的一个模块或者单元的特征和功能可以进一步划分为由多个模块或者单元来具体化。
此外,尽管在附图中以特定顺序描述了本申请中方法的各个步骤,但是,这并非要求或者暗示必须按照该特定顺序来执行这些步骤,或是必须执行全部所示的步骤才能实现期望的结果。附加的或备选的,可以省略某些步骤,将多个步骤合并为一个步骤执行,以及/或者将一个步骤分解为多个步骤执行等。
通过以上的实施方式的描述,本领域的技术人员易于理解,这里描述的示例实施方式可以通过软件实现,也可以通过软件结合必要的硬件的方式来实现。因此,根据本申请实施方式的技术方案可以以软件产品的形式体现出来,该软件产品可以存储在一个非易失性存储介质(可以是CD-ROM,U盘,移动硬盘等)中或网络上,包括若干指令以使得一台计算设备(可以是个人计算机、服务器、移动终端、或者网络设备等)执行根据本申请实施方式的方法。
本领域技术人员在考虑说明书及实践这里公开的发明后,将容易想到本申请的其它实施方案。本申请旨在涵盖本申请的任何变型、用途或者适应性变化,这些变型、用途或者适应性变化遵循本申请的一般性原理并包括本申请未公开的本技术领域中的公知常识或惯用技术手段。说明书和实施例仅被视为示例性的,本申请的真正范围和精神由所附的权利 要求指出。
Claims (26)
- 一种数字资产凭证继承转移中的信息处理方法,所述方法由司法机构节点执行,所述方法包括:确定用户的生命周期结束;获取用户的遗嘱,所述遗嘱包括用户个人安全内核节点的标识、各继承人个人安全内核节点的标识、各数字资产凭证用对应继承人个人安全内核节点的公钥进行的签名、所述遗嘱用司法机构节点公钥进行的签名;如果对所述遗嘱用司法机构节点公钥进行的签名,用司法机构节点私钥进行签名验证成功,触发向所述遗嘱中的各继承人个人安全内核节点的标识的继承人个人安全内核节点,发送所述遗嘱中各数字资产凭证用对应继承人个人安全内核节点的公钥进行的签名,以便所述继承人个人安全内核节点对该签名,用所述继承人个人安全内核节点的私钥解密,得到数字资产凭证的摘要,根据得到的数字资产凭证的摘要,得到继承的数字资产凭证。
- 根据权利要求1所述的方法,所述确定用户的生命周期结束,包括:响应于来自调查节点的生命周期结束通知,确定用户的生命周期结束。
- 根据权利要求1所述的方法,所述确定用户的生命周期结束,包括:接收到启动节点的启动请求;通过社交操作系统平台,向多个证明方节点发送继承程序启动确认请求;如果所述多个证明方节点的应答满足预定条件,则确定用户的生命周期结束。
- 根据权利要求3所述的方法,所述如果所述多个证明方节点的应答满足预定条件,则确定用户的生命周期结束,包括:如果所述多个证明方节点的应答满足预定条件,且接收到来自调查节点的生命周期结束通知,则确定用户的生命周期结束。
- 根据权利要求1所述的方法,所述遗嘱还包括指定的执行该遗嘱的司法机构节点标识,所述对所述遗嘱用司法机构节点公钥进行的签名,用司法机构节点私钥进行签名验证成功,包括:获取遗嘱中指定的执行该遗嘱的司法机构节点标识;如果遗嘱中指定的执行该遗嘱的司法机构节点标识是当前执行所述方法的司法机构节点的标识,对所述遗嘱用司法机构节点公钥进行的签名,用司法机构节点私钥进行签名验证成功。
- 根据权利要求5所述的方法,所述如果遗嘱中指定的执行该遗嘱的司法机构节点标识是当前执行所述方法的司法机构节点的标识,对所述遗嘱用司法机构节点公钥进行的签名,用司法机构节点私钥进行签名验证成功,包括:如果遗嘱中指定的执行该遗嘱的司法机构节点标识是当前执行所述方法的司法机构节点的标识,对所述遗嘱用司法机构节点公钥进行的签名,用司法机构节点私钥解密,得到解密后产生的遗嘱摘要;生成所述遗嘱的摘要;如果解密后产生的遗嘱摘要与生成的遗嘱的摘要一致,则确定对所述遗嘱用司法机构节点公钥进行的签名,用司法机构节点私钥进行签名验证成功。
- 根据权利要求1所述的方法,所述继承的数字资产凭证中包含数字资产凭证依赖的业务依赖方节点标识,以便所述继承人个人安全内核节点与该业务依赖方节点标识的业务依赖方节点,根据继承的数字资产凭证,生成继承人节点与该业务依赖方节点之间的更新后数字资产凭证。
- 根据权利要求1所述的方法,所述遗嘱还包括所述遗嘱的继承适用法律,所述触发向所述遗嘱中的各继承人个人安全内核节点的标识的继承人个人安全内核节点,发送所述遗嘱中各数字资产凭证用对应继承人个人安全内核节点的公钥进行的签名,包括:触发向所述遗嘱中的各继承人个人安全内核节点的标识的继承人个人安全内核节点,发送所述遗嘱中各数字资产凭证用对应继承人个人安全内核节点的公钥进行的签名、和遗嘱的继承适用法律,以便所述继承人个人安全内核节点得到继承的数字资产凭证后,执行 所述继承适用法律对应的进程。
- 根据权利要求1所述的方法,在确定用户的生命周期结束之后,所述方法还包括:如果获取不到用户的遗嘱,根据所述用户的个人安全内核节点的身份,确定所述身份对应的法律;获取所述用户的亲属关系;获取用户的各数字资产凭证;针对获取的用户的每一个数字资产凭证,按照确定的法律和所述亲属关系,确定各数字资产凭证对应的继承人个人安全内核节点标识;获取确定的继承人个人安全内核节点标识的继承人个人安全内核节点的公钥;将用户的每一个数字资产凭证,用对应的继承人个人安全内核节点的公钥进行签名,并发送到对应的继承人个人安全内核节点,以便所述继承人个人安全内核节点对该签名,用所述继承人个人安全内核节点的私钥解密,得到数字资产凭证的摘要,根据得到的数字资产凭证的摘要,得到继承的数字资产凭证。
- 根据权利要求1所述的方法,所述遗嘱由用户的个人安全内核节点通过以下过程生成:对于用户的个人安全内核节点中的数字资产凭证,接收用户对该数字资产凭证的继承人个人安全内核节点标识的指定;获取指定的继承人个人安全内核节点标识的继承人个人安全内核节点的公钥;将每一个数字资产凭证,用相应获取的指定的继承人个人安全内核节点标识的继承人个人安全内核节点的公钥进行签名,得到各数字资产凭证用对应继承人个人安全内核节点的公钥进行的签名;将用户个人安全内核节点的标识、各继承人个人安全内核节点的标识、各数字资产凭证用对应继承人个人安全内核节点的公钥进行的签名放入遗嘱中;接收用户对执行该遗嘱的司法机构节点标识的指定;获取所述司法机构节点标识的司法机构节点的公钥;将所述遗嘱中的当前内容用获取的司法机构节点的公钥签名,放入所述遗嘱。
- 根据权利要求10所述的方法,所述遗嘱生成后通过以下过程配置:显示安全模式列表,所述安全模式列表包括第一安全模式、第二安全模式、第三安全模式,其中,第一安全模式中,遗嘱存储在用户个人安全内核节点客户端中;第二安全模式中,遗嘱存储在用户个人安全内核节点客户端和服务器中;第三安全模式中,遗嘱存储在用户个人安全内核节点服务器中,并发布在区块链上;响应于用户在安全模式列表中选择第一安全模式,将所述遗嘱存储在用户个人安全内核节点客户端中;响应于用户在安全模式列表中选择第二安全模式,将遗嘱存储在用户个人安全内核节点客户端和服务器中;响应于用户在安全模式列表中选择第三安全模式,将遗嘱存储在用户个人安全内核节点服务器中,并发布在区块链上。
- 根据权利要求10所述的方法,所述遗嘱由用户的个人安全内核节点通过以下过程更新:当所述用户的个人安全内核节点中增加数字资产凭证时,根据遗嘱中为已有的数字资产凭证指定的继承人个人安全内核节点标识,确定增加的数字资产凭证对应的继承人个人安全内核节点标识;获取增加的数字资产凭证对应的继承人个人安全内核节点标识的继承人个人安全内核节点的公钥;对增加的数字资产凭证,用相应获取的指定的继承人个人安全内核节点标识的继承人个人安全内核节点的公钥进行签名,得到增加的数字资产凭证用对应继承人个人安全内核节点的公钥进行的签名;将为增加的数字资产凭证指定的继承人个人安全内核节点标识、增加的数字资产凭证 用对应继承人个人安全内核节点的公钥进行的签名,添加到遗嘱中;将遗嘱中当前的用获取的司法机构节点的公钥的签名去掉;将所述遗嘱中的当前内容用获取的司法机构节点的公钥签名,放入所述遗嘱。
- 一种司法机构节点,包括:生命周期结束确定单元,用于确定用户的生命周期结束;遗嘱获取单元,用于获取用户的遗嘱,所述遗嘱包括用户个人安全内核节点的标识、各继承人个人安全内核节点的标识、各数字资产凭证用对应继承人个人安全内核节点的公钥进行的签名、所述遗嘱用司法机构节点公钥进行的签名;第一数字资产凭证签名发送单元,用于如果对所述遗嘱用司法机构节点公钥进行的签名,用司法机构节点私钥进行签名验证成功,触发向所述遗嘱中的各继承人个人安全内核节点的标识的继承人个人安全内核节点,发送所述遗嘱中各数字资产凭证用对应继承人个人安全内核节点的公钥进行的签名,以便所述继承人个人安全内核节点对该签名,用所述继承人个人安全内核节点的私钥解密,得到数字资产凭证的摘要,根据得到的数字资产凭证的摘要,得到继承的数字资产凭证
- 一种数字资产凭证继承转移中的信息处理方法,所述方法由司法机构节点执行,所述方法包括:当用户的个人安全内核节点中增加数字资产凭证时,获取增加的数字资产凭证对应的继承人个人安全内核节点标识,以及所述继承人个人安全内核节点标识的继承人个人安全内核节点的公钥;对增加的数字资产凭证,用所述继承人个人安全内核节点的公钥进行签名,得到增加的数字资产凭证用对应继承人个人安全内核节点的公钥进行的签名;将所述继承人个人安全内核节点标识、增加的数字资产凭证用对应继承人个人安全内核节点的公钥进行的签名,添加到所述用户的遗嘱中,所述遗嘱中包含有用司法机构节点公钥进行的签名;将所述遗嘱中包含的用司法机构节点公钥进行的签名去掉;将所述遗嘱中的当前内容用所述司法机构节点公钥进行签名,并将得到的签名放入所述遗嘱。
- 根据权利要求14所述的方法,所述获取增加的数字资产凭证对应的继承人个人安全内核节点标识,以及所述继承人个人安全内核节点标识的继承人个人安全内核节点的公钥,包括:向用户显示指定增加的数字资产凭证的继承人个人安全内核节点标识的界面;在所述界面上接收用户对所述增加的数字资产凭证的继承人个人安全内核节点标识的指定;获取用户指定的继承人个人安全内核节点标识的继承人个人安全内核节点的公钥。
- 根据权利要求15所述的方法,所述获取用户指定的继承人个人安全内核节点标识的继承人个人安全内核节点的公钥,包括:向区块链中的认证中心服务器请求获取用户指定的继承人个人安全内核节点标识的继承人个人安全内核节点的公钥;或者从区块链上获取与用户指定的继承人个人安全内核节点标识对应的继承人个人安全内核节点的公钥,其中,继承人个人安全内核节点的公钥由继承人个人安全内核节点生成,并与继承人个人安全内核节点的公钥标识对应记录在区块链上;或者通过社交操作系统平台,向继承人好友个人安全内核节点发送公钥获取请求,所述公钥获取请求包括用户指定的继承人个人安全内核节点标识,从继承人好友个人安全内核节点,接收用户指定的继承人个人安全内核节点标识的继承人个人安全内核节点的公钥。
- 根据权利要求14所述的方法,所述获取增加的数字资产凭证对应的继承人个人安全内核节点标识,以及所述继承人个人安全内核节点标识的继承人个人安全内核 节点的公钥,包括:根据所述遗嘱中为已有的数字资产凭证指定的继承人个人安全内核节点标识,确定增加的数字资产凭证对应的继承人个人安全内核节点标识;获取增加的数字资产凭证对应的继承人个人安全内核节点标识的继承人个人安全内核节点的公钥。
- 根据权利要求17所述的方法,所述根据所述遗嘱中为已有的数字资产凭证指定的继承人个人安全内核节点标识,确定增加的数字资产凭证对应的继承人个人安全内核节点标识,包括:获取增加的数字资产凭证的类型;查找所述遗嘱中已为相同类型的数字资产凭证指定的继承人个人安全内核节点标识;如果遗嘱中已为相同类型的数字资产凭证指定的继承人个人安全内核节点标识一致,则将遗嘱中已为相同类型的数字资产凭证指定的继承人个人安全内核节点标识确定为增加的数字资产凭证对应的继承人个人安全内核节点标识。
- 根据权利要求18所述的方法,所述根据所述遗嘱中为已有的数字资产凭证指定的继承人个人安全内核节点标识,确定增加的数字资产凭证对应的继承人个人安全内核节点标识,还包括:如果遗嘱中已为相同类型的数字资产凭证指定的继承人个人安全内核节点标识不一致,则将遗嘱中已为相同类型的数字资产凭证指定的多个继承人个人安全内核节点标识中最多的继承人个人安全内核节点标识,确定为增加的数字资产凭证对应的继承人个人安全内核节点标识。
- 根据权利要求17所述的方法,所述根据所述遗嘱中为已有的数字资产凭证指定的继承人个人安全内核节点标识,确定增加的数字资产凭证对应的继承人个人安全内核节点标识,包括:获取增加的数字资产凭证的业务依赖方节点标识;查找所述遗嘱中已为相同业务依赖方节点标识的数字资产凭证指定的继承人个人安全内核节点标识;如果遗嘱中已为相同业务依赖方节点标识的数字资产凭证指定的继承人个人安全内核节点标识一致,则将遗嘱中已为相同业务依赖方节点标识的数字资产凭证指定的继承人个人安全内核节点标识确定为增加的数字资产凭证对应的继承人个人安全内核节点标识。
- 根据权利要求20所述的方法,所述根据所述遗嘱中为已有的数字资产凭证指定的继承人个人安全内核节点标识,确定增加的数字资产凭证对应的继承人个人安全内核节点标识,还包括:如果所述遗嘱中已为相同业务依赖方节点标识的数字资产凭证指定的继承人个人安全内核节点标识不一致,则将遗嘱中已为相同业务依赖方节点标识的数字资产凭证指定的多个继承人个人安全内核节点标识中最多的继承人个人安全内核节点标识,确定为增加的数字资产凭证对应的继承人个人安全内核节点标识。
- 根据权利要求14至21中任一项所述的方法,所述对增加的数字资产凭证,用所述继承人个人安全内核节点的公钥进行签名,包括:按照预定的摘要算法生成增加的数字资产凭证的摘要;用所述继承人个人安全内核节点的公钥对所述增加的数字资产凭证的摘要进行加密。
- 一种司法机构节点,包括:获取单元,用于当用户的个人安全内核节点中增加数字资产凭证时,获取增加的数字资产凭证对应的继承人个人安全内核节点标识,以及所述继承人个人安全内核节点标识的继承人个人安全内核节点的公钥;第一签名处理单元,用于对增加的数字资产凭证,用所述继承人个人安全内核节 点的公钥进行签名,得到增加的数字资产凭证用对应继承人个人安全内核节点的公钥进行的签名;添加单元,用于将所述继承人个人安全内核节点标识、增加的数字资产凭证用对应继承人个人安全内核节点的公钥进行的签名,添加到所述用户的遗嘱中,所述遗嘱中包含有用司法机构节点公钥进行的签名;第二签名处理单元,用于将所述遗嘱中包含的用司法机构节点公钥进行的签名去掉,将所述遗嘱中的当前内容用所述司法机构节点公钥进行签名,并将得到的签名放入所述遗嘱。
- 一种司法机构节点,包括:存储器,存储有计算机可读指令;处理器,读取存储器存储的计算机可读指令,以执行权利要求1-12中的任一个所述的方法、或者权利要求14-22中的任一个所述的方法。
- 一种计算机程序介质,其上存储有计算机可读指令,当所述计算机可读指令被计算机的处理器执行时,使计算机执行权利要求1-12中的任一个所述的方法、或者权利要求14-22中的任一个所述的方法。
- 一种包括指令的计算机程序产品,当其在计算机上运行时,使得所述计算机执行权利要求1-12中的任一个所述的方法、或者权利要求14-22中的任一个所述的方法。
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US17/237,773 US12022000B2 (en) | 2019-03-08 | 2021-04-22 | Method for information processing in digital asset certificate inheritance transfer, and related device |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN201910177252.4 | 2019-03-08 | ||
CN201910177252.4A CN110245940B (zh) | 2019-03-08 | 2019-03-08 | 数字资产凭证继承转移中的信息处理方法、和相关装置 |
Related Child Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US17/237,773 Continuation US12022000B2 (en) | 2019-03-08 | 2021-04-22 | Method for information processing in digital asset certificate inheritance transfer, and related device |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2020182005A1 true WO2020182005A1 (zh) | 2020-09-17 |
Family
ID=67883022
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/CN2020/077388 WO2020182005A1 (zh) | 2019-03-08 | 2020-03-02 | 数字资产凭证继承转移中的信息处理方法、和相关装置 |
Country Status (3)
Country | Link |
---|---|
US (1) | US12022000B2 (zh) |
CN (2) | CN110766405B (zh) |
WO (1) | WO2020182005A1 (zh) |
Cited By (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20210250181A1 (en) * | 2020-02-06 | 2021-08-12 | International Business Machines Corporation | Entity certification management |
US12022000B2 (en) | 2019-03-08 | 2024-06-25 | Tencent Technology (Shenzhen) Company Limited | Method for information processing in digital asset certificate inheritance transfer, and related device |
Families Citing this family (7)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN111177629A (zh) * | 2019-12-30 | 2020-05-19 | 杨国荣 | 遗留信息和/或遗留物的管理方法、系统以及商业平台 |
CN111563734A (zh) * | 2020-05-06 | 2020-08-21 | 广东工业大学 | 一种数字资产转移方法、装置及电子设备和存储介质 |
US20210390549A1 (en) * | 2020-06-15 | 2021-12-16 | Capital One Services, Llc | Systems and methods for building blockchains for verifying assets for smart contracts |
CN111784550B (zh) * | 2020-07-15 | 2022-08-12 | 支付宝(杭州)信息技术有限公司 | 继承业务的处理方法、装置及设备 |
JP7029874B2 (ja) * | 2020-08-07 | 2022-03-04 | 三菱Ufj信託銀行株式会社 | プログラム、情報管理方法、情報管理装置 |
CN113254168B (zh) * | 2021-06-11 | 2021-10-15 | 北京百度网讯科技有限公司 | 区块链系统的运行方法、装置、设备和存储介质 |
CN115580412B (zh) * | 2022-11-24 | 2023-03-03 | 杭州蚂蚁酷爱科技有限公司 | 基于区块链管理数字遗产的系统、方法和装置 |
Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN105809062A (zh) * | 2016-03-01 | 2016-07-27 | 布比(北京)网络技术有限公司 | 一种合约构建、执行方法及装置 |
CN108809630A (zh) * | 2018-06-19 | 2018-11-13 | 中钞信用卡产业发展有限公司杭州区块链技术研究院 | 一种遗嘱保存方法、系统、设备及计算机可读存储介质 |
CN109063084A (zh) * | 2018-07-24 | 2018-12-21 | 安徽问法信息技术有限公司 | 一种基于区块链智能合约的遗嘱数字资产自动执行方法 |
CN109345259A (zh) * | 2018-09-29 | 2019-02-15 | 腾讯科技(深圳)有限公司 | 基于区块链的虚拟资源转移方法、装置、介质及电子设备 |
CN110245940A (zh) * | 2019-03-08 | 2019-09-17 | 腾讯科技(深圳)有限公司 | 数字资产凭证继承转移中的信息处理方法、和相关装置 |
Family Cites Families (16)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7904722B2 (en) * | 1994-07-19 | 2011-03-08 | Certco, Llc | Method for securely using digital signatures in a commercial cryptographic system |
US20080167994A1 (en) * | 2005-07-22 | 2008-07-10 | Koninklijke Philips Electronics, N.V. | Digital Inheritance |
US7809652B2 (en) | 2007-01-30 | 2010-10-05 | Visa U.S.A. Inc. | Signature based negative list for off line payment device validation |
US20130226810A1 (en) * | 2012-02-24 | 2013-08-29 | Wayne Moffett | System and method for certifying a will |
CN103295126A (zh) * | 2012-03-02 | 2013-09-11 | 刘家焜 | 可被信任的交易凭证方法 |
US20140025591A1 (en) * | 2012-07-13 | 2014-01-23 | Digital Life Legacy, LLC | System and method for recording and delivering a personal legacy to a beneficiary |
CN105469510B (zh) * | 2014-10-12 | 2018-01-09 | 吴思进 | 可预告延时支付或找回的加密货币钱包 |
CN105610578B (zh) * | 2016-01-25 | 2019-05-03 | 杭州复杂美科技有限公司 | 区块链信息存证及隐私保护方法 |
US10586295B2 (en) * | 2016-03-21 | 2020-03-10 | Digistate Planning, Llc. | Updateable electronic digital assets will or trust method and systems with real time access for updated designated will or trust elements |
US20170301048A1 (en) * | 2016-03-23 | 2017-10-19 | Simonetta Turek | Cloud-based estate management and execution |
GB2555476A (en) * | 2016-10-31 | 2018-05-02 | Philip Hartley Robin | Apparatuses and methods for signing a legal document |
CN108154439A (zh) * | 2016-12-02 | 2018-06-12 | 北京金股链科技有限公司 | 资产数据处理装置及方法 |
US20180205546A1 (en) * | 2016-12-31 | 2018-07-19 | Assetvault Limited | Systems, methods, apparatuses for secure management of legal documents |
CN107767267B (zh) * | 2017-10-20 | 2021-04-02 | 上海策赢网络科技有限公司 | 一种虚拟资源的转移方法和装置 |
CN108171609B (zh) * | 2017-12-29 | 2021-05-07 | 苏州朗润创新知识产权运营有限公司 | 一种数字资产互通的方法和计算机可读存储介质 |
CN108460596B (zh) * | 2018-02-27 | 2020-08-25 | 周伟 | 一种基于区块链的量化值分配转移方法 |
-
2019
- 2019-03-08 CN CN201910943397.0A patent/CN110766405B/zh active Active
- 2019-03-08 CN CN201910177252.4A patent/CN110245940B/zh active Active
-
2020
- 2020-03-02 WO PCT/CN2020/077388 patent/WO2020182005A1/zh active Application Filing
-
2021
- 2021-04-22 US US17/237,773 patent/US12022000B2/en active Active
Patent Citations (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN105809062A (zh) * | 2016-03-01 | 2016-07-27 | 布比(北京)网络技术有限公司 | 一种合约构建、执行方法及装置 |
CN108809630A (zh) * | 2018-06-19 | 2018-11-13 | 中钞信用卡产业发展有限公司杭州区块链技术研究院 | 一种遗嘱保存方法、系统、设备及计算机可读存储介质 |
CN109063084A (zh) * | 2018-07-24 | 2018-12-21 | 安徽问法信息技术有限公司 | 一种基于区块链智能合约的遗嘱数字资产自动执行方法 |
CN109345259A (zh) * | 2018-09-29 | 2019-02-15 | 腾讯科技(深圳)有限公司 | 基于区块链的虚拟资源转移方法、装置、介质及电子设备 |
CN110245940A (zh) * | 2019-03-08 | 2019-09-17 | 腾讯科技(深圳)有限公司 | 数字资产凭证继承转移中的信息处理方法、和相关装置 |
CN110766405A (zh) * | 2019-03-08 | 2020-02-07 | 腾讯科技(深圳)有限公司 | 数字资产凭证继承转移中的信息处理方法、和相关装置 |
Cited By (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US12022000B2 (en) | 2019-03-08 | 2024-06-25 | Tencent Technology (Shenzhen) Company Limited | Method for information processing in digital asset certificate inheritance transfer, and related device |
US20210250181A1 (en) * | 2020-02-06 | 2021-08-12 | International Business Machines Corporation | Entity certification management |
US11856109B2 (en) * | 2020-02-06 | 2023-12-26 | International Business Machines Corporation | Entity certification management |
Also Published As
Publication number | Publication date |
---|---|
CN110766405B (zh) | 2021-07-30 |
US20210243037A1 (en) | 2021-08-05 |
US12022000B2 (en) | 2024-06-25 |
CN110245940A (zh) | 2019-09-17 |
CN110766405A (zh) | 2020-02-07 |
CN110245940B (zh) | 2021-07-06 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
WO2020182005A1 (zh) | 数字资产凭证继承转移中的信息处理方法、和相关装置 | |
US10564936B2 (en) | Data processing systems for identity validation of data subject access requests and related methods | |
WO2021068636A1 (zh) | 基于区块链的可验证声明的创建方法、装置、设备及系统 | |
JP6054457B2 (ja) | 制御された情報開示によるプライベート解析 | |
US10091230B1 (en) | Aggregating identity data from multiple sources for user controlled distribution to trusted risk engines | |
US11711433B2 (en) | Systems and methods for asynchronous API-driven external application services for a blockchain | |
WO2021003977A1 (zh) | 违约信息查询方法、装置、计算机设备和存储介质 | |
TWI629658B (zh) | 基於區塊鏈智能合約的kyc資料共享系統及其方法 | |
CN109446259B (zh) | 数据处理方法及装置、处理机及存储介质 | |
US20230208642A1 (en) | Secure data transfer system and method | |
US11824850B2 (en) | Systems and methods for securing login access | |
US20190386968A1 (en) | Method to securely broker trusted distributed task contracts | |
WO2019011187A1 (zh) | 电子账户的挂失、解挂、业务管理方法、装置及设备 | |
KR102131206B1 (ko) | 법인 관련 서비스 제공 방법, 이를 지원하는 방법, 이를 수행하는 서비스 서버 및 인증 서버 | |
WO2021169767A1 (zh) | 一种数据处理方法、装置、设备及介质 | |
CN110442654A (zh) | 违约信息查询方法、装置、计算机设备和存储介质 | |
CN112966309A (zh) | 一种基于区块链的业务实现方法和装置 | |
CN114172663A (zh) | 基于区块链的业务确权方法及装置、存储介质和电子设备 | |
CN110719266B (zh) | 信用数据处理方法及装置 | |
JP2017162353A (ja) | 個人データ不正使用検知方法、個人データ提供元サーバ、プログラム | |
CN118018265A (zh) | 基于nft的登录认证方法、装置、电子设备及存储介质 | |
WO2024197087A1 (en) | Methods and systems for verifying user data | |
CN104753673A (zh) | 一种基于随机关联码的用户多认证凭证关联方法 | |
CN118677593A (zh) | 信息处理方法及装置、电子设备和计算机可读存储介质 | |
KR20210014827A (ko) | 생체 측정 식별 시스템 및 작동 방법 |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 20769696 Country of ref document: EP Kind code of ref document: A1 |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
122 | Ep: pct application non-entry in european phase |
Ref document number: 20769696 Country of ref document: EP Kind code of ref document: A1 |