Will management system, method, computer program product based on multi-source data

Abstract

The application discloses a will management system and method based on multi-source data, and a computer program product. The system comprises a blockchain and an off-chain data access module; the off-chain data access module is connected with a plurality of designated institutions, and the designated institutions are data sources of death information of a testator; each oracle service node generates an initial death judgment result of the testator based on the death information of the testator; a smart contract comprises a consensus judgment module and a decryption execution module; the consensus judgment module generates a consensus judgment result according to a predetermined judgment condition and the initial death judgment result provided by each oracle service node; in the case that the consensus judgment result is that the testator has died, a decryption notification of a will ciphertext of the testator is generated; and the decryption execution module decrypts the will ciphertext based on the authorized key fragments in response to the decryption notification. According to the embodiment of the application, the disclosure time of the will can be accurately judged on the basis of safe storage of the will.

Description

Technical Field

[0001] This application relates to the field of electronic information notarization technology, and in particular to a will management system, method, and computer program product based on multi-source data. Background Technology

[0002] With increasing legal awareness and the development of digital management, more and more individuals need to make wills in advance to ensure the effective execution of their wishes regarding the distribution of their assets. In traditional will management, wills are usually kept by the testator or a family member and only made public after the testator's death. With the development of digital technology, more and more digital wills have emerged, bringing convenience to the creation and preservation of wills.

[0003] However, current digital will services mostly focus on the encryption and storage of wills. At the will retrieval stage, once the testator provides their identity information and verification is successful, the will can be decrypted and provided to them. This means that if the testator's identity information is leaked, the will can be easily obtained by others, posing a risk of premature disclosure. Furthermore, since wills often contain sensitive information such as estate distribution and asset disposal, improper disclosure before the testator's death can easily affect the rights of the true beneficiaries and harm the testator's wishes. Similarly, if the testator fails to inform the beneficiaries when making the will, the beneficiaries may be unaware of its existence, and delays in disclosure after the testator's death can still negatively impact their rights.

[0004] Therefore, accurately determining the timing of will disclosure while ensuring its safe safekeeping is crucial for protecting the rights of beneficiaries and safeguarding the will's wishes. Summary of the Invention

[0005] In view of this, embodiments of this application provide a will management system and method computer program product based on multi-source data to solve at least one technical problem.

[0006] This application provides a will validity determination system based on multi-source oracles and smart contracts, including a blockchain and an off-chain data access module. The off-chain data access module includes multiple oracle service nodes, each interfaced with at least one designated institution, which serves as the data source for the will's death information. The blockchain stores multiple encrypted wills and is configured with smart contracts. The blockchain also stores management information for the corresponding keys of the encrypted wills, including key fragment manager information and key activation conditions. Each oracle service node receives the will's death information from its interfaced designated institution and generates an initial death determination result based on this information. The contract includes a consensus determination module and a decryption execution module. The consensus determination module obtains the initial death determination result of the testator provided by each oracle service node, and generates a consensus determination result based on predetermined determination conditions and the initial death determination result provided by each oracle service node. In the case that the consensus determination result indicates that the testator is dead, it generates a decryption notification for the testator's ciphertext. In response to the decryption notification, the decryption execution module extracts the administrator information of the key fragment corresponding to the testator from the blockchain, requests authorization for the key fragment from the administrator, and extracts the testator's ciphertext from the blockchain if the authorized key fragment meets the key activation conditions, and decrypts the ciphertext based on the authorized key fragment.

[0007] According to an embodiment of this application, optionally, if the death information returned by at least one of the multiple designated institutions connected to the oracle service node includes the fact that the will-maker has died, the oracle service node extracts the death timestamp information and the will-maker's identity identifier from the death information, and requests the will-maker's death information from other designated institutions connected to it; each oracle service node obtains the credibility weight of each designated institution connected to it; and, based on the will-maker's death information provided by each designated institution and the credibility weight of each designated institution, generates an initial death determination result for the will-maker.

[0008] According to an embodiment of this application, optionally, if the death information reported by at least one of the multiple designated institutions connected to the oracle service node includes the death of the testator, the death information of the testator is sent to other oracle service nodes in the system, so that the other oracle service nodes can request the death information of the testator from the designated institution they are connected to based on the testator's identity; each oracle service node digitally signs the initial death determination result generated for each testator based on its exclusive private key, and uploads the signed initial death determination result to the blockchain; the consensus determination module performs integrity verification on the signed initial death determination result based on the public key corresponding to the oracle service node, and if the verification passes, determines whether to generate a decryption notification for the ciphertext of the will for the multiple initial death determination results corresponding to the testator.

[0009] According to an embodiment of this application, optionally, the consensus determination module is further used to obtain the level of evidentiary validity, data update frequency, and historical accuracy of each designated institution, and to generate a credibility weight for the designated institution based on the level of evidentiary validity, data update frequency, and historical accuracy. The level of evidentiary validity is determined based on the establishment basis, functional authority, judicial recognition degree, and legal binding force of the documents issued by the designated institution. The consensus determination module distributes the credibility weight of the designated institution to each oracle service node according to the designated institution connected to each oracle service node.

[0010] According to an embodiment of this application, optionally, when the number of oracle service nodes is N, the will-maker corresponds to N initial death determination results, where N is a positive integer greater than 1; the predetermined determination condition is that if M or more of the N initial death determination results corresponding to the will-maker indicate that the will-maker has died, where N is greater than or equal to M; or, the predetermined determination condition is that if the proportion of the number of results determined to be dead in the N initial death determination results is greater than a preset proportion threshold, then the will-maker has died.

[0011] According to embodiments of this application, optionally, the category of the designated institution includes at least one of the following categories: death information inquiry institution, medical information certification institution, notary information service institution, and insurance service institution.

[0012] This application provides a will management method based on multi-source data, including: determining the living status of the will maker based on the will validity determination system based on multi-source oracles and smart contracts provided in this application, and decrypting the will of the will maker if the will maker is determined to be dead.

[0013] This application provides an electronic device, which includes a processor and a memory storing computer program instructions; the processor executes the computer program instructions to implement the steps of the method described above.

[0014] This application provides a computer-readable storage medium storing computer program instructions, which, when executed by a processor, implement the steps of the method described above.

[0015] This application provides a computer program product, which includes computer program instructions. When the computer program instructions are executed by a processor, they implement the steps of the method described above.

[0016] In the embodiments of this application, multiple oracle service nodes in the off-chain data access module communicate with designated external institutions to obtain data sources of the will's death information. This allows the smart contract to provide external information beyond the blockchain, thereby driving the smart contract to automatically determine whether the will is deceased. During the specific determination process, the consensus determination module further judges whether the will is deceased based on the initial death determination results fed back by multiple oracle service nodes. This reduces the impact of misjudgments from a single data source or malicious behavior, improving the accuracy and reliability of the judgment results. After confirming the will's death, the consensus determination module automatically issues a decryption notification to trigger the decryption execution module in the smart contract. Based on the key management information, the module requests the key manager to authorize decryption of the key, ensuring standardized decryption of the will's encrypted text and further enhancing the will's credibility. Attached Figure Description

[0017] To more clearly illustrate the technical solutions of the embodiments of this application, the accompanying drawings of the embodiments of this application will be briefly described below.

[0018] Figure 1 This is a schematic diagram of the will validity determination system architecture based on multi-source oracles and smart contracts, according to an embodiment of this application.

[0019] Figure 2 This is another schematic diagram of the will validity determination system architecture based on multi-source oracles and smart contracts in this application embodiment.

[0020] Figure 3 This is a schematic diagram of an electronic device used to implement the embodiments of this application. Detailed Implementation

[0021] The features and exemplary embodiments of various aspects of this application will be described in detail below. To make the objectives, technical solutions, and advantages of this application clearer, the application will be further described in detail below with reference to the accompanying drawings and specific embodiments. It should be understood that the specific embodiments described herein are only intended to explain this application and not to limit it. For those skilled in the art, this application can be implemented without some of these specific details. The following description of the embodiments is merely to provide a better understanding of this application by illustrating examples.

[0022] It should be noted that, in this document, relational terms such as "first" and "second" are used merely to distinguish one entity or operation from another, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Furthermore, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising..." does not exclude the presence of additional identical elements in the process, method, article, or apparatus that includes said element.

[0023] It should be understood that the term "and / or" used in this article is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, and B existing alone. Additionally, the character " / " in this article generally indicates that the preceding and following related objects have an "or" relationship.

[0024] Various modifications and variations can be made to this application without departing from its spirit or scope, which will be apparent to those skilled in the art. Therefore, this application is intended to cover modifications and variations falling within the scope of the corresponding claims (the claimed technical solutions) and their equivalents. It should be noted that the implementation methods provided in the embodiments of this application can be combined with each other without contradiction.

[0025] It should be noted that the acquisition, storage, use, and processing of data in this application embodiment all comply with the relevant provisions of laws and regulations.

[0026] Before describing the technical solutions provided in the embodiments of this application, the following detailed explanations of the problems existing in the related technologies are provided to facilitate understanding of the embodiments of this application. As more and more people choose to establish digital wills to ensure the effective execution of their wishes regarding the distribution of property, research has found that current digital will services mainly focus on the encryption and storage of wills. However, during the will retrieval process, the will can be decrypted after the retrieval person's identity is verified, posing a risk of identity information leakage leading to premature disclosure of the will. Especially since the will involves sensitive information such as estate distribution and asset disposal, if it is leaked before the testator's death, it may harm the rights of the beneficiaries and affect the execution of the will. Furthermore, failure to inform the beneficiaries or untimely disclosure may also affect the fairness of the will. Therefore, in addition to securely storing the will, accurately determining the timing of disclosure is also crucial. Based on this, the embodiments of this application provide a will management system and method computer program product based on multi-source data, ensuring that the accuracy of determining the timing of will disclosure can be improved, thereby helping to protect the rights of the beneficiaries and the testator's wishes.

[0027] Figure 1 A schematic diagram of a system architecture according to an embodiment of this application is shown. For example... Figure 1 As shown, the will validity determination system based on multi-source oracles and smart contracts includes a blockchain 110 and an off-chain data access module 120. Specifically, the off-chain data access module 120 includes multiple oracle service nodes, each of which interfaces with at least one designated institution. The designated institution serves as the data source for the will's death information. The blockchain 110 stores multiple encrypted wills and is configured with smart contracts. The blockchain 110 also stores the management information of the corresponding keys for the encrypted wills. The key management information includes the manager information of the key fragments and the key activation conditions.

[0028] Each oracle service node is used to receive the death information of the will-maker from the designated institution it connects to, and to generate the initial death determination result of the will-maker based on the death information.

[0029] The smart contract includes a consensus determination module 111 and a decryption and execution module 112.

[0030] Among them, the consensus determination module 111 obtains the initial death determination result of the testator provided by each oracle service node, and generates a consensus determination result according to the predetermined determination conditions and the initial death determination result provided by each oracle service node; and, in the case that the consensus determination result is that the testator has died, generates a decryption notification of the testator's ciphertext.

[0031] In response to the decryption notification, the decryption execution module 112 extracts the administrator information of the key fragment corresponding to the testator from the blockchain 110, requests authorization of the key fragment from the administrator, and extracts the ciphertext of the testator's will from the blockchain if the authorized key fragment meets the key activation conditions, and decrypts the ciphertext of the will based on the authorized key fragment.

[0032] The above modules will be described in detail below with reference to specific embodiments, as shown in the following figures.

[0033] Blockchain 110 can store encrypted wills. Encrypted wills refer to data processed by encryption algorithms. The will content can include the will itself and its timestamp authentication information. The timestamp authentication information can confirm the time of the will's formation and its legal validity. The will can be made in a compliant form, such as a handwritten will, a will written by another person, a video will, or a blank will.

[0034] Alternatively, Blockchain 110 can employ decentralized storage technologies such as distributed storage networks to distribute the encrypted will across multiple storage nodes, thereby securely storing the encrypted will and reducing the risk of the will's contents being illegally accessed during storage.

[0035] Blockchain 110 provides a trusted operating environment for smart contracts. Data generated during the execution of smart contracts can be recorded in Blockchain 110. For example, key management information after encrypting the content of a will, including the administrator information of the key fragments and the key activation conditions; and rules for determining the timing of will publication can also be recorded in Blockchain 110. By recording this data through the blockchain, the creation and preservation process of each will becomes traceable.

[0036] The off-chain data access module 120 includes multiple oracle service nodes, which can introduce trusted external data into the blockchain network. Specifically, trusted external data can be data sources of death information. Based on these death information data sources, smart contracts can be automatically triggered to determine the appropriate time for the public disclosure of a will.

[0037] In this embodiment, the oracle service nodes are independent of each other, and each oracle has one or more designated institutions that it interfaces with. The oracle service nodes communicate with the designated institutions, thereby obtaining data sources of death information bound to the identity of the will-maker periodically or in real time.

[0038] Oracle service nodes independently make initial death determination results based on death information provided by the designated institutions they interface with.

[0039] For example, designated institutions include official death information inquiry agencies, medical information certification agencies, and notary information service platforms.

[0040] The oracle service node makes a preliminary judgment based on death information provided by external sources, and generates an initial death determination result for the willr, such as death or the willr being alive.

[0041] Smart contracts mainly consist of a consensus determination module 111 and a decryption and execution module 112.

[0042] The initial death determination result provided by the oracle service node is uploaded to the consensus determination module 111 of the smart contract. The consensus determination module 111 merges and determines the results provided by multiple oracle nodes according to the preset consensus rules.

[0043] For example, when the number of oracle service nodes is N, the testator corresponds to N initial death determination results, where N is a positive integer greater than 1; the predetermined determination condition is that if M or more of the N initial death determination results corresponding to the testator indicate that the testator has died, then the testator is determined to be dead, where N is greater than or equal to M.

[0044] For example, if three out of five initial death determinations determine that the testator is deceased, then the testator can be considered dead and the subsequent decryption process can proceed.

[0045] Alternatively, the predetermined judgment condition is that if the proportion of the results judged as deceased among N initial death judgment results is greater than a preset proportion threshold, then the person making the will is judged to be deceased.

[0046] Based on this, by introducing a quantity threshold or a judgment ratio threshold as a triggering condition, we can prevent the will from being prematurely decrypted due to misjudgment or malicious submission by a single data source.

[0047] After the consensus determination module 111 determines that the initial death determination result provided by the oracle service node meets the predetermined determination conditions, it generates a corresponding decryption notification to notify the decryption execution module 112 to execute the decryption process. The entire determination process can be executed automatically, which can reduce human intervention and reduce the risk of inaccurate execution timing.

[0048] Upon receiving the notification, the decryption execution module 112 retrieves the key management information from the smart contract and requests key fragment authorization from the key manager. If the authorized key fragment meets the key activation conditions, the decryption execution module will extract the ciphertext of the will of the target will-maker, decrypt it using the authorized key fragment, and finally obtain the content of the will.

[0049] During key management, the key used to encrypt the will's contents is fragmented, ensuring that each key fragment is an independent piece, and the key activation condition is configured such that the original key cannot be recovered from a single key fragment. Optionally, the key fragmentation can employ Shamir's Secret Sharing algorithm, where the number of key fragments can be determined based on the number of key managers; alternatively, the number of key fragments can be greater than or equal to the number of key managers.

[0050] After key fragmentation, the key fragments are managed by multiple people. Therefore, decrypting the ciphertext of the will requires the joint participation of multiple key managers, thereby reducing the risk of key leakage and malicious extraction of the will, and further improving the security of the will.

[0051] According to the embodiments of this application, through consensus mechanism and automated execution of smart contracts, it is ensured that the contents of the will are only allowed to be decrypted when the conditions for death are met, thereby fully protecting the will's wishes and reducing the risk of improper disclosure and premature publication of the will.

[0052] During the death determination process, multiple independent oracle service nodes are set up in the off-chain data access module. These nodes can generate initial death determination results based on death information provided by multiple designated institutions. Then, the consensus determination module further combines the initial death determination results provided by the multiple oracle service nodes with the consensus mechanism to comprehensively determine whether the testator is dead. This reduces interference from maliciously created false information, further improves the accuracy of determining the timing of will retrieval, and reduces the risk of misjudgment.

[0053] In some embodiments of this application, when the death information returned by at least one of multiple designated institutions connected to the oracle service node includes the death of the will-maker, the oracle service node extracts the death timestamp information and the will-maker's identity identifier from the death information, and requests the will-maker's death information from other designated institutions connected to it; each oracle service node obtains the credibility weight of each designated institution connected to it; and, based on the will-maker's death information provided by each designated institution and the credibility weight of each designated institution, generates an initial death determination result for the will-maker.

[0054] Specifically, when an oracle service node is connected to multiple designated institutions, it can receive death information from different designated institutions. This death information has a certain legal effect and data authority, and therefore has higher credibility.

[0055] In actual operation, when the oracle service node receives death information from any designated institution it connects to, the oracle service node extracts timestamp information and the identity of the person who made the will from the death information. The identity information can be a unique identifier such as an ID card, medical number, or notarized certificate number.

[0056] For example, two oracle service nodes connect to different designated institutions. Oracle service node 1 is responsible for connecting to two different designated institutions, such as a hospital and a credible death registration system, to obtain relevant data; oracle service node 2 is responsible for connecting to one institution. If oracle service node 1 receives death information from the hospital first, it will proactively request the death information of the will holder from the credible death registration system it connects to, in order to improve the accuracy of the initial death determination result generated by oracle service node 1 itself.

[0057] The two data sources that Oracle Service Node 1 connects to may provide the same or different death information. Oracle Service Node 1 can perform preliminary verification on these two data sources before generating an initial death determination result. The preliminary verification may include checking whether the identity information is consistent, comparing whether the time of death matches, and comparing whether the cause of death and other information are reasonable, etc.

[0058] Optionally, before requesting the death information of the will-maker from other designated institutions it connects to, the oracle service node can first query the identity information of the will-maker previously recorded on the blockchain based on the identity identifier, and perform a consistency verification with the identity identifier information in the death information data source. This confirms that the will-maker corresponding to the death status is the same person as the will-maker recorded on the chain, thereby effectively reducing misjudgments caused by identity ambiguity or data errors. After the consistency verification is successful, the oracle service node will proactively initiate information requests to the other designated institutions it connects to obtain the latest death information data source for the will-maker.

[0059] Each designated institution will have a corresponding credibility weight, which can be determined based on factors such as the institution's level of evidentiary validity, data update frequency, and historical accuracy.

[0060] The consensus determination module distributes the credibility weight of the designated institution to each oracle service node based on the institution that each oracle service node is connected to. The credibility weight can be increased by improving the level of proof effectiveness, increasing the data update frequency, and increasing the historical accuracy.

[0061] After receiving all feedback, the oracle service node will generate an initial death determination result based on the death information provided by the designated institution it connects to and its corresponding weights, using methods such as weighted voting or confidence fusion. This initial death determination result indicates that the testator is deceased or that the testator is still alive. The initial death determination result will be transmitted as input data to the consensus determination module 111, serving as the basis for participation in the subsequent multi-node consensus mechanism.

[0062] Specifically, the consensus determination module 111 is also used to obtain the level of evidentiary validity, data update frequency, and historical accuracy of each designated institution, and to generate the credibility weight of the designated institution based on the level of evidentiary validity, data update frequency, and historical accuracy. The level of evidentiary validity is determined based on the establishment basis, functional authority, judicial recognition degree, and legal binding force of the documents issued by the designated institution. The consensus determination module 111 distributes the credibility weight of the designated institution to each oracle service node according to the designated institution connected to each oracle service node.

[0063] As a specific example, different designated institutions correspond to different levels of evidentiary value.

[0064] For example, the designated agencies at the first level may include civil affairs departments, public security household registration management agencies, etc., and these designated agencies can issue death registration certificates with legal validity.

[0065] The second-tier designated institutions can provide accurate information, but this information only has legal effect after being certified by other institutions, or it needs to be combined with information provided by other institutions to further determine whether the person making the will is dead. For example, medical institutions can provide death certificates or medical records that can serve as factual evidence, but they need to be certified by other institutions to have legal effect. Similarly, social security information management departments can provide accurate information on the suspension of medical insurance cards and the termination of social security records, but they still need information from other institutions to further determine whether the person making the will is dead.

[0066] The third-level designated institutions can be those that can provide post-reference information, such as online legal service platforms, insurance companies, etc.

[0067] In some optional embodiments, the credibility weight assignment mechanism can employ a dynamic learning mechanism in addition to statically preset credibility weights. By statistically analyzing the accuracy rate of each designated institution's judgments in historical data, its credibility weight is dynamically adjusted in real time. Specifically, machine learning algorithms such as logistic regression and Bayesian classifiers can be used to determine historical accuracy rates, and then the weight allocation can be iteratively optimized to gradually improve the overall accuracy of the judgments.

[0068] According to the embodiments of this application, the oracle service node communicates with multiple designated institutions and reduces the impact of erroneous information from individual data sources on the actual judgment result through cross-validation and weighted fusion judgment methods, thereby improving the accuracy of the judgment result.

[0069] In some embodiments of this application, all verification results are digitally signed by each oracle, and then the signed data is uploaded to blockchain 110. This reduces the risk of data being tampered with during the transmission process from the oracle to the smart contract.

[0070] According to the embodiments of this application, after the verification is passed and the data is confirmed to have not been tampered with, the subsequent consensus calculation process is carried out to further ensure the reliability of the will decryption notification generation process.

[0071] In some embodiments of this application, when the death information reported by at least one of the multiple designated institutions connected to the oracle service node includes the death of the testator, the death information of the testator is sent to other oracle service nodes in the system, so that the other oracle service nodes can request the death information of the testator from the designated institution they are connected to based on the testator's identity. Each oracle service node digitally signs the initial death determination result generated for each testator based on its exclusive private key, and uploads the signed initial death determination result to the blockchain. The consensus determination module 111 performs integrity verification on the signed initial death determination result based on the public key corresponding to the oracle service node, and if the verification passes, determines whether to generate a decryption notification for the ciphertext of the will for the multiple initial death determination results corresponding to the testator.

[0072] Specifically, by sending the death information of the testator to other oracle service nodes in the system, the other oracle service nodes can request the death information of the testator from the designated institution they are connected to based on the testator's identity, so as to ensure that each oracle service node can generate an initial judgment result for the testator.

[0073] In some optional embodiments, the public key corresponding to each oracle service node is stored in the blockchain, and this public key and the oracle service node's private key form a unique key pair. After the smart contract receives the initial death determination result, the consensus determination module performs an integrity check on the initial death determination result signed with the public key pair corresponding to the private key, to ensure that the data used in the consensus determination process has not been tampered with.

[0074] In some embodiments of this application, the decryption execution module 112, in response to a decryption notification, extracts the manager information of the key fragments from the smart contract and sends authorization requests for the key fragments to the managers of each key fragment. Based on the authorization information of the received key fragments, the decryption execution module extracts and decrypts the signature fragments in the distributed storage network to obtain the key fragments, and determines whether the number of extracted key fragments meets the activation conditions of the key. If the activation conditions of the key are met, the key is restored based on the extracted key fragments, and the will ciphertext is extracted from the distributed storage network. The restored key is used to decrypt the will ciphertext to disclose the will and the timestamp authentication information of the will.

[0075] Specifically, the decryption execution module 112 extracts the corresponding signature fragments from the distributed storage network based on the received authorization information, and verifies whether the number of signature fragments meets the activation conditions of the key, such as whether the received authorization information is greater than or equal to K.

[0076] Optionally, before verifying the number of signature fragments, the decryption execution module can first verify the authenticity of the signature fragments using the public key, and after the verification is successful, proceed to the next key activation stage.

[0077] According to an embodiment of this application, when it is determined that the will can be retrieved and the authorization information meets the activation conditions, the decryption execution module recovers the key based on the authorized key fragments. Subsequently, the ciphertext of the will is extracted from the distributed storage network, and the recovered key is used to decrypt the ciphertext of the will to publicly disclose the complete will and the corresponding timestamp authentication information for relevant personnel to view.

[0078] Based on the will extraction process provided in this application embodiment, since each key fragment has a clear holder and its behavioral credentials, the use of each key fragment is traceable, thereby effectively improving security and anti-tampering capabilities, further enhancing the standardization of the will disclosure process, and improving the credibility of the will.

[0079] In some embodiments of this application, Figure 2 This is another schematic diagram of the will validity determination system architecture based on multi-source oracles and smart contracts, as described in this application. Combined with... Figure 2 As shown, the smart contract may include an encryption processing module 113. The encryption processing module 113 can encrypt the will authentication information and store the management information of the corresponding key of the will ciphertext, thereby improving the security of the entire will management process.

[0080] Specifically, the administrator of the key fragment corresponding to the ciphertext of the will is the administrator of the will-making process, and the administrator includes the witnesses to the will and the beneficiaries of the will.

[0081] The encryption processing module 113 is used to receive the will authentication information of the will maker, which includes the will and the timestamp authentication information of the will; after encrypting the will authentication information, the ciphertext of the will can be obtained; the encryption processing module 113 can store the ciphertext of the will to the blockchain, and perform key fragmentation to generate Z key fragments; organize the identity authentication information of each administrator into administrator information of the key fragments; distribute at least one key fragment to each administrator, so that the administrator terminal can sign the key fragment according to the administrator's exclusive private key to generate a signature fragment, and then each administrator stores its corresponding signature fragment to the blockchain.

[0082] The encryption module encrypts the will authentication information, resulting in a key and the ciphertext of the will. During encryption, the encryption algorithm can be a symmetric encryption algorithm, such as AES or SM4, or other encryption algorithms.

[0083] The identity authentication information of each administrator is verified by a designated institution. Each administrator's identity authentication information includes, for example, ID card information and biometric information. Biometric information includes fingerprints, irises, palm prints, facial features, etc. Based on the identity authentication information, each administrator can be uniquely identified.

[0084] The encryption module 113 distributes a key fragment to each authenticated administrator. Each administrator can use their private key on their terminal device to sign the received key fragment, generating a corresponding signed fragment. This signing ensures that each key fragment has a clear holder and credential of their actions, making its use traceable. After signing the key fragment locally, the signed fragment is uploaded to the distributed storage network.

[0085] In some optional embodiments, each administrator's public key can be stored in the encryption module or in the blockchain. Each administrator's public key can be used to verify the authenticity of the signature fragments on the blockchain, ensuring their authenticity and trustworthiness. Since the original key cannot be recovered from a single fragment, the risk of key leakage and malicious extraction of the will is reduced. Furthermore, based on each administrator's unique key, the use of each key fragment is traceable, further enhancing the credibility of the will disclosure process and preventing arbitrary decryption of the will.

[0086] Specifically, the encryption processing module can generate activation conditions for the key based on the number of signature fragments. Specifically, the activation conditions can be set as a threshold strategy, such as requiring authorization for at least K key fragments out of Z. Based on this, the key reconstruction process can be activated by the signature fragments of any K administrators, thus ensuring the decryption capability of the will remains even when some administrators are unavailable.

[0087] According to the embodiments of this application, by combining the actual number of signature fragments and automatically combining the changes in the number of administrators, key activation conditions are dynamically generated, making key management more flexible and reducing the risk that the will cannot be decrypted due to the inability to use individual keys.

[0088] Corresponding to the method embodiments of this application, this application also provides a will management method based on multi-source data. The method is based on the will validity determination system based on multi-source oracles and smart contracts provided in the embodiments of this application, which determines the living status of the will-maker, and decrypts the will-maker's will if the will-maker is determined to be dead.

[0089] The electronic device in this application embodiment may be a user terminal device, a server, other computing devices, or a cloud server. Figure 3 The diagram shows the hardware structure of an electronic device according to an embodiment of this application. The electronic device may include a processor 301 and a memory 302 storing computer program instructions. When the processor 301 executes the computer program instructions, it implements the process or function of any of the methods described above.

[0090] Specifically, processor 301 may include a central processing unit (CPU), or an application-specific integrated circuit (ASIC), or one or more integrated circuits configured to implement the embodiments of this application. Memory 302 may include a mass storage device for data or instructions. For example, memory 302 may be at least one of the following: a hard disk drive (HDD), read-only memory (ROM), random access memory (RAM), floppy disk drive, flash memory, optical disk, magneto-optical disk, magnetic tape, universal serial bus (USB) drive, or other physical / tangible memory storage device. Alternatively, memory 302 may include removable or non-removable (or fixed) media. Furthermore, memory 302 may be internal or external to the integrated gateway disaster recovery device. Memory 302 may be non-volatile solid-state memory. In other words, typically memory 302 includes a tangible (non-transitory) computer-readable storage medium (such as a memory device) encoded with computer-executable instructions, and when the software is executed (e.g., by one or more processors), it can perform the operations described in the methods of the embodiments of this application. The processor 301 implements the process or function of any of the methods described in the above embodiments by reading and executing computer program instructions stored in the memory 302.

[0091] In one example Figure 3The illustrated electronic device may also include a communication interface 303 and a bus 310. The processor 301, memory 302, and communication interface 303 are connected via bus 310 and communicate with each other. The communication interface 303 is mainly used to realize communication between the various modules, devices, units, and / or equipment in the embodiments of this application. Bus 310 includes hardware, software, or both, and can couple the components of the online data traffic billing device together. For example, the bus may include at least one of the following: Accelerated Graphics Port (AGP) or other graphics bus, Enhanced Industry Standard Architecture (EISA) bus, Front Side Bus (FSB), HyperTransport (HT) Interconnect, Industry Standard Architecture (ISA) bus, Infinite Bandwidth Interconnect, Low Pin Count (LPC) bus, memory bus, Microchannel Architecture (MCA) bus, Peripheral Component Interconnect (PCI) bus, PCI-Express (PCI-X) bus, Serial Advanced Technology Attachment (SATA) bus, Video Electronics Standards Association Local (VLB) bus, or other suitable buses. Bus 310 may include one or more buses. Although specific buses are described or illustrated in the embodiments of this application, any suitable bus or interconnection method may be considered in the embodiments of this application.

[0092] In conjunction with the methods in the above embodiments, this application also provides a computer-readable storage medium storing computer program instructions, which, when executed by a processor, implement the process or function of any of the methods in the above embodiments.

[0093] In addition, this application also provides a computer program product that stores computer program instructions, which, when executed by a processor, implement the process or function of any of the methods described above.

[0094] The flowcharts and / or block diagrams of methods, apparatuses, systems, and computer program products according to embodiments of this application have been exemplarily described above, and related aspects have been described. It should be understood that each block or combination thereof in the flowcharts and / or block diagrams may be implemented by computer program instructions, by dedicated hardware performing a specified function or action, or by a combination of dedicated hardware and computer instructions. For example, these computer program instructions may be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing apparatus to form a machine that enables the implementation of the function / action specified in each block or combination thereof in the flowcharts and / or block diagrams, executable via such processor. Such a processor may be a general-purpose processor, a dedicated processor, a special-purpose application processor, or a field-programmable logic circuit.

[0095] The functional blocks shown in the structural block diagrams of this application can be implemented as hardware, software, firmware, or a combination thereof. When implemented in hardware, they can be, for example, electronic circuits, application-specific integrated circuits (ASICs), appropriate firmware, plug-ins, function cards, etc.; when implemented in software, they are programs or code segments used to perform the required tasks. Programs or code segments can be stored in memory or transmitted over a transmission medium or communication link via data signals carried on a carrier wave. Code segments can be downloaded via computer networks such as the Internet or intranets.

[0096] It should be noted that this application is not limited to the specific configurations and processes described above or shown in the figures. The above descriptions are merely specific embodiments of this application. Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the specific working processes of the described systems, devices, modules, or units can be referred to the corresponding processes in the method embodiments, and need not be repeated here. It should be understood that the scope of protection of this application is not limited thereto. Any person skilled in the art can conceive of various equivalent modifications or substitutions within the scope of the technology disclosed in this application, and these modifications or substitutions should all be covered within the scope of protection of this application.

Claims

1. A will management method based on multi-source data, characterized in that, The method is implemented based on blockchain and an off-chain data access module, wherein, The off-chain data access module includes multiple oracle service nodes, each of which interfaces with at least one designated institution, which is the data source of the death information of the will-maker. The blockchain stores multiple encrypted wills and is configured with smart contracts. The smart contracts include a consensus determination module and a decryption execution module. The blockchain stores management information of the corresponding keys for the encrypted wills. The key management information includes the manager information of the key fragments and the key activation conditions. The will management method based on multi-source data includes: Each oracle service node receives the death information of the will-maker from the designated institution it connects to, and generates an initial death determination result for the will-maker based on the death information; If the death information reported by at least one of the multiple designated institutions connected to the oracle service node includes that the testator has died, then the oracle service node extracts the death timestamp information and the testator's identity identifier from the death information, requests the testator's death information from other designated institutions connected to it, and sends the testator's death information to other oracle service nodes, so that other oracle service nodes can request the testator's death information from their connected designated institutions based on the testator's identity identifier. After receiving all feedback, the oracle service node generates an initial death determination result based on the death information of the testator reported by each designated institution it connects to, and the corresponding credibility weight of each designated institution, through weighted voting or confidence fusion. The initial death determination result is either that the testator is dead or that the testator is alive. Each oracle service node digitally signs the initial death determination result of each testator based on its exclusive private key and uploads the signed initial death determination result to the blockchain. The signed initial death determination result is then passed as input data to the consensus determination module for participation in the subsequent multi-node consensus mechanism. The consensus determination module obtains the initial death determination result of the testator provided by each oracle service node, and generates a consensus determination result based on the predetermined determination conditions and the initial death determination result provided by each oracle service node; and, if the consensus determination result indicates that the testator has died, generates a decryption notification of the testator's ciphertext. In response to the decryption notification, the decryption execution module extracts the administrator information of the key fragment corresponding to the testator from the blockchain, requests authorization for the key fragment from the administrator, and extracts the ciphertext of the testator's will from the blockchain if the authorized key fragment meets the key activation conditions, and decrypts the ciphertext of the will based on the authorized key fragment.

2. The method according to claim 1, characterized in that, The consensus determination module is also used to obtain the level of evidentiary validity, data update frequency and historical accuracy of each designated institution, and generate the credibility weight of the designated institution based on the level of evidentiary validity, data update frequency and historical accuracy. The level of evidentiary validity is determined based on the establishment basis, functional authority, judicial recognition degree and legal binding force of the documents issued by the designated institution. The consensus determination module distributes the credibility weight of the designated institution to each oracle service node based on the institution that each oracle service node is connected to.

3. The method according to claim 1, characterized in that, When the number of oracle service nodes is N, the person making the will corresponds to N initial death determination results, where N is a positive integer greater than 1; The predetermined determination condition is that if, out of N initial death determination results corresponding to the testator, M or more death determination results indicate that the testator is deceased, then the testator is determined to be deceased, where N is greater than or equal to M; or... The predetermined determination condition is that if the proportion of the number of results determined to be dead in the N initial death determination results is greater than a preset proportion threshold, then the person making the will is determined to be dead.

4. The method according to claim 1, characterized in that, The designated institutions include at least one of the following categories: death information inquiry institutions, medical information certification institutions, notary information service institutions, and insurance service institutions.

5. An electronic device, characterized in that, The electronic device includes a processor and a memory storing computer program instructions; when the electronic device executes the computer program instructions, it implements the method as described in any one of claims 1-4.

6. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer program instructions that, when executed by a processor, implement the method as described in any one of claims 1-4.

7. A computer program product, characterized in that, It includes computer program instructions that, when executed by a processor, implement the method as described in any one of claims 1-4.

Images