# US 2018/0025455 A1 · Registry > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 2018/0025455 A1 - Document ID: US20180025455A1 - Status: Published application - Kind: A1 - Application number: 15/683,354 - Filed: 2017-08-22 - Published: 2018-01-25 - Earliest claimed: 2011-10-28 - Assignees: Ydf Global Pty Ltd - Applicants: Ydf Global Pty Ltd - Inventors: Jamie Robert Wilson; Craig Steven Wright - Web page: https://patentgrep.com/patent/US20180025455A1 ## CPC - G06Q 50/186: {Estate planning} - G06Q 10/10: Office automation; Time management - G06Q 50/265: {Personal security, identity or safety} - H04L 63/0428: {wherein the data content is protected, e.g. by encrypting or encapsulating the payload} - H04L 63/10: {for controlling access to devices or network resources} - 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 - H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M) ## Abstract A system, method, server processing system, and computer program product for operating a registry. In one aspect, the server processing system is configured to: receive, from a user processing system in data communication with the server processing system, document data relating to an entity; receive, from the user processing system, access data indicative of an accessing party to be provided access to the document data if a defined trigger event occurs; store, in a data store associated with the server processing system, a registry for the entity indicative of the document data and the access data; determine that a defined trigger event has occurred; and in response to determining that that a defined trigger event has occurred, provide the accessing party read-only access to the document data via an access processing system in data communication with the server processing system. ## Claims ### Claim 1 A server processing system for operating a registry, wherein the server processing system is configured to: receive, from a user processing system in data communication with the server processing system, document data relating to an entity; receive, from the user processing system, access data indicative of an accessing party to be provided access to the document data if a defined trigger event occurs; store, in a data store associated with the server processing system, a registry for the entity indicative of the document data and the access data; determine that a defined trigger event has occurred; and in response to determining that a defined trigger event has occurred, provide the accessing party read-only access to the document data via an access processing system in data communication with the server processing system. ### Claim 2 (depends on 1) The server processing system according to claim 1, wherein the registry is an estate registry, and wherein: the entity is an individual; the document data is estate data indicative of estate information relating to the estate of an individual; the access data is executor data indicative of an executor for the estate; and, a defined trigger event includes the individual dying. ### Claim 3 (depends on 1) The server processing system according to claim 1, wherein the registry is a corporate registry, and wherein: the entity is a corporate entity; the document data is entity data indicative of entity information relating to the entity; the access data is liquidator data indicative of a liquidator for the entity; and, a defined trigger event includes the entity being placed into liquidation. ### Claim 4 (depends on 1) The server processing system according to claim 1, wherein the server processing system is configured to: receive, from the user processing system, authorisation data indicative of a third party authorised by the entity to read-only access at least a portion of the registry; receive, from the third party via a third party processing system, an access request; determine, based upon the authorisation data, if the third party is authorised to access at least a portion of the registry; and in response to identifying the third party as being authorised, provide the third party with access to at least a portion of the registry. ### Claim 5 (depends on 4) The server processing system according to claim 4, wherein the server processing system is configured to: receive permission data indicative of the entity authorising the third party being able to access a portion of the registry; store the permission data in the data store; and in response to receiving the access request and upon identifying the third party as being authorised, provide the third party with read-only access to the portion of the registry corresponding to the permission data for the third party. ### Claim 6 (depends on 4) The server processing system according to claim 4, wherein the server processing system is configured to: maintain read only access to documents stored in the registry; maintain a secure timestamp of all documents stored in the registry; and, allow documents stored in the registry to be digitally signed; ### Claim 7 (depends on 4) The server processing system according to claim 4, wherein the access request includes one or more identity fields and the data store has stored therein identity data for the entity associated with the registry, wherein the server processing system is configured to compare the one or more identity fields to the identity data to uniquely identify the registry associated with the entity. ### Claim 8 (depends on 1) The server processing system according to claim 1, wherein the server processing system is configured to monitor electronic announcements to determine if a defined trigger event has occurred. ### Claim 9 (depends on 1) The server processing system according to claim 1, wherein the server processing system is configured to: receive, from a notifying party, a notification indicative that a defined trigger event has occurred; and in response to receiving the notification, provide the accessing party read-only access to the document data. ### Claim 10 (depends on 1) The server processing system according to claim 1, wherein the server processing system is configured to: receive, from the entity via the user processing system, an indication of an authorised notifying party; store, in the data store, the indication of the authorised notifying party; receive, from a notifying party, an indication that a defined trigger event has occurred; determine if the notifying party is the authorised notifying party; and in response to the notifying party corresponding to the authorised notifying party, provide the accessing party read-only access to the document data. ### Claim 11 (depends on 1) The server processing system according to claim 1, wherein the data store has stored therein one or more reminder rules, wherein the server processing system is configured to: automatically execute the one or more reminder rules to determine if a reminder notice is required to be sent to the entity to remind the entity to review and update the registry; and in the event of a positive determination, transfer, to the entity, the reminder notice. ### Claim 12 (depends on 1) The server processing system according to claim 1, wherein the server processing system is configured to encrypt the document data when stored in the registry. ### Claim 13 A method for operating a registry, wherein the method includes, in a server processing system: receiving, from a user processing system in data communication with the server processing system, document data relating to the entity; receiving, from the user processing system, access data indicative of an accessing party to be provided access to the document data if a defined trigger event occurs; storing, in a data store associated with the server processing system, a registry for the entity indicative of the document data and the access data; determining that a defined trigger event has occurred; and in response to determining that a defined trigger event has occurred, providing the accessing party read-only access to the document data via an access processing system in data communication with the server processing system. ### Claim at position 14 -91. (canceled) ### Claim 92 (depends on 2) The server processing system according to claim 2, wherein the defined trigger event includes receiving a death notification indicating that the individual has died. ### Claim 93 (depends on 3) The server processing system according to claim 3, wherein the defined trigger event includes receiving a liquidation notification indicating that the entity has been placed into liquidation. ### Claim 94 (depends on 1) The server processing system according to claim 1, wherein the server processing system is configured to: obtain a digital signature of an individual, the digital signature being at least partially indicative of document content of the document data and an identity of the individual; encrypt the document data so that the document data can be decrypted using a decryption key; and, store the encrypted document data in the registry, wherein the decryption key is defined by at least three key fragments, each key fragment being associated with a respective entity and the key fragments being arranged so that the decryption key can be constructed from any two key fragments thereby allowing the document data to be decrypted and accessed using the key fragments of any two of the entities. ### Claim 95 (depends on 94) The server processing system according to claim 94, wherein the server processing system is configured to: validate the digital signature of the individual; and, store the encrypted document in response to a successful validation. ### Claim 96 (depends on 94) The server processing system according to claim 94, wherein the digital signature is generated by encrypting information using a private key of a public/private key pair, and wherein the server processing system is configured to: receive the digital signature, the digital signature being generated by encrypting information using a private key of a public/private key pair; and, decrypt the digital signature using the public key to thereby validate the identity of at least one of the individual and the entities. ### Claim 97 (depends on 1) The server processing system according to claim 1, wherein the document data is encrypted so that the document data can be decrypted using a decryption key, the decryption key being defined by at least three key fragments, each key fragment being associated with a respective entity and the key fragments being arranged so that the decryption key can be constructed from any two key fragments, and wherein the server processing system is configured to: determine the document data is to be accessed; construct the decryption key from the key fragments associated with at least two of the entities; and, use the constructed decryption key to decrypt and thereby provide access to the document data. ### Claim 98 (depends on 97) The server processing system according to claim 97, wherein the key fragments are stored in a store together with an indication of an identity of the respective entity, and wherein the server processing system is configured to: determine at least two entities authorised to access the document data; retrieve key fragments associated with the at least two entities from the store; and, provide access to the document data using the key fragments associated with the at least two entities.