Asset management system and asset management method

Abstract

To provide an asset management system for appropriately managing an asset whose existence should not be known to an heir when a customer dies and an asset whose existence must be made known to the heir.SOLUTION: An asset management system includes an asset management device and a work execution device. The asset management device holds asset information indicating asset data owned by a customer and a deletion rank for each asset type, in which the deletion rank includes a first-class rank indicating that data is not be deleted after the customer dies, and a second-class rank indicating that data will be deleted when a predetermined condition is satisfied after the customer dies. The asset management device notifies, when the asset management device acquires information indicating contents of a rule change related to the asset and a type of asset subject to the rule change, the work execution device of the information, and the work execution device updates, on the basis of the contents of the rule change, the deletion rank corresponding to the type of asset subject to the rule change in the asset information.SELECTED DRAWING: Figure 13

Description

[Technical Field]

[0001] The present invention relates to an asset management system and an asset management method. [Background technology]

[0002] Japanese Patent Laid-Open Publication No. 2002-157324 (Patent Document 1) is a background technology of the present invention. This publication states that "When a contracting party who has concluded a contract with a credit card company, an electric company, or the like requests to apply and register the contract details from their user terminal 2, the cancellation agent device 1 registers the contract details in association with the party identification information. When the contracting party himself or a person who has a special relationship with that party requests to apply for cancellation from their user terminal 2, the cancellation agent device 1 obtains the contract details associated with the party identification information, and transmits a request to execute the cancellation procedure, which requires the party identification information and the contract details, to the contracting party terminal 4" (see abstract). [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Japanese Patent Application Laid-Open No. 2002-157324 Summary of the Invention [Problem to be solved by the invention]

[0004] Patent Document 1 describes how, upon the death of a contracting party, the cancellation procedures for the service contracted by the contracting party will be carried out on behalf of the contracting party. However, Patent Document 1 does not describe how the service contract will be taken over by an heir or other person upon the death of the contracting party.

[0005] On the other hand, in asset management systems that manage assets owned by customers, there are heirs who will inherit the assets when the customer dies. Furthermore, among the assets managed by asset management systems, there are assets that the customer does not want heirs to know about when the customer dies, and assets for which rules have been established that require heirs to be informed of their existence.

[0006] Therefore, one aspect of the present invention aims to properly manage assets that a customer does not want their heirs to know about upon their death, and assets whose existence must be made known to their heirs. [Means for solving the problem]

[0007] In order to solve the above problem, one aspect of the present invention employs the following configuration: An asset management system for managing a customer's assets includes an asset management device and a task execution device, wherein the asset management device holds asset information indicating, for each type of asset, data on assets held by the customer and a deletion rank indicating a response to the data after the death of the customer, and the deletion rank includes a first rank indicating that the data will not be deleted after the death of the customer and a second rank indicating that the data will be deleted if a predetermined condition is met after the death of the customer, and when the asset management device acquires information indicating the content of a rule change related to assets and the type of asset that is the subject of the rule change, the asset management device executes the information as a task execution device. The work execution device notifies the work execution device, and the work execution device updates the deletion rank corresponding to the type of asset that is the subject of the rule change in the asset information based on the content of the rule change, and when the asset management device receives a death notification of the first customer, it sends the death notification to the work execution device, and the work execution device executes a deletion process to delete data of an asset type of the first customer whose deletion rank is the second rank from the asset information if the specified condition is satisfied, and sends to the asset management device a list of the assets of the first customer that are included in the asset information and whose data has not been deleted by the deletion process. [Effects of the Invention]

[0008] According to one aspect of the present invention, it is possible to properly manage assets that a customer does not want their heirs to know about upon their death, and assets whose existence must be made known to their heirs.

[0009] Problems, configurations, and effects other than those described above will become apparent from the following description of the embodiments. [Brief explanation of the drawings]

[0010] [Figure 1] FIG. 1 is an explanatory diagram illustrating an example of an outline of a use case of a customer's asset management system during their lifetime in the first embodiment. [Figure 2] FIG. 1 is an explanatory diagram illustrating an example of an outline of a use case of the asset management system at the time of the death of a customer in the first embodiment. [Figure 3] 1 is a block diagram illustrating a configuration example of an asset management device according to a first embodiment. [Figure 4] 1 is a block diagram showing an example of the configuration of a work execution device according to a first embodiment. [Figure 5] 10 is an example of a customer table according to the first embodiment. [Figure 6] 10 is an example of a legal heir table in the first embodiment. [Figure 7] 3 is an example of an asset information table according to the first embodiment. [Figure 8] 10 is an example of a work performing company table according to the first embodiment. [Figure 9] 10 is an example of a simple property inventory table in the first embodiment. [Figure 10] 3 is an example of an encryption key table according to the first embodiment. [Figure 11] 10 is an example of a deletion rank table according to the first embodiment. [Figure 12] 10 is an example of a selectable deletion rank table according to the first embodiment. [Figure 13] 10 is a flowchart illustrating an example of asset information registration processing when a customer is alive according to the first embodiment. [Figure 14] 10 is a flowchart illustrating an example of information registration processing according to the first embodiment. [Figure 15] 10 is a flowchart illustrating an example of encryption processing in the first embodiment. [Figure 16] 10 is a flowchart illustrating an example of a deletion rank update process according to the first embodiment. [Figure 17] 10 is a flowchart illustrating an example of asset information update processing executed during a customer's lifetime in the first embodiment. [Figure 18] 10 is a flowchart showing an example of asset information management processing after the death of a customer in the first embodiment. [Figure 19] 10 is a flowchart illustrating an example of a death information linking process according to the first embodiment. [Figure 20] 10 is a flowchart illustrating an example of a simple property inventory generation process according to the first embodiment. DETAILED DESCRIPTION OF THE INVENTION

[0011] Hereinafter, an embodiment of the present invention will be described in detail with reference to the drawings. In this embodiment, the same components are generally designated by the same reference numerals, and repeated explanations will be omitted. It should be noted that this embodiment is merely an example for realizing the present invention, and does not limit the technical scope of the present invention. [Example]

[0012] 1 is an explanatory diagram showing an example of an outline of a use case of an asset management system during a customer's lifetime. The asset management system includes, for example, an asset management device 100 owned by a servicer company and an operation execution device 200 owned by each of a plurality of operation execution companies. The asset management device 100 and each of the operation execution devices 200 are connected to each other via a network such as the Internet.

[0013] The customer referral company introduces asset management services to clients with assets and then refers those clients to the servicer company. In return for the client referral, the servicer company may pay a referral fee to the customer referral company. The servicer company introduces asset management services to clients.

[0014] A customer applies to a servicer company for the use of asset management services. The customer inputs information about the assets he or she owns, for example, using a terminal owned by the customer (e.g., a personal computer (PC) or a smartphone). The terminal owned by the customer transmits the input asset information to the asset management device 100.

[0015] The asset management device 100 encrypts the received asset information, stores it temporarily, and transmits a list of the encrypted asset information (hereinafter also simply referred to as encrypted asset information) to the work execution device 200 owned by the work execution company. The work execution device 200 stores the encrypted asset information. Note that assets to be registered include financial assets such as cash, deposit accounts, securities, and cryptocurrencies, SNS (Social Networking Service) IDs and passwords, as well as real estate and movable property (in other words, it may include both liquid and inliquid assets).

[0016] A customer can use his / her own terminal to instruct the asset management device 100 to update (for example, add and / or delete) asset information. Upon receiving an instruction to update asset information, the asset management device 100 transmits a contractor notification indicating information identifying the customer who instructed the update of asset information to the work execution device 200 storing the encrypted asset information of the customer, and upon receiving the contractor notification, the work execution device 200 transmits the encrypted asset information to the asset management device 100.

[0017] The asset management device 100 acquires asset information by decrypting the encrypted asset information and presents it to a terminal owned by the customer. The customer refers to the presented asset information and inputs updated details of the asset information into the terminal, and the terminal transmits the updated details to the asset management device 100. The asset management device 100 encrypts and temporarily stores the asset information reflecting the updated details, and transmits the encrypted asset information reflecting the updated details to the work execution device 200. The work execution device 200 updates the encrypted asset information of the customer to encrypted asset information reflecting the updated details.

[0018] The asset information includes, for example, data indicating the content of the asset and a deletion flag indicating how each type of asset should be handled after the death of a customer (for example, not deleting the data even if the death of the customer is confirmed, deleting the data a predetermined number of days after the death of the customer, or deleting the data immediately after the death of the customer is confirmed). The deletion flag is set, for example, according to a request from the customer, but may be automatically changed when there are changes in laws or guidelines, as will be described later.

[0019] The task execution device 200 into which the customer's encrypted asset information is registered may be designated by the customer, designated by the servicer company, or determined randomly. All of a customer's asset information may be registered in one task execution device 200, or may be distributed and registered across multiple task execution devices 200.

[0020] An insurance company used by a customer is an example of a customer referral company. An insurance company or financial institution used by a customer is an example of a servicer company. A judicial scrivener's office or a law firm is an example of a service provider company.

[0021] Figure 2 is an explanatory diagram showing an example of an outline of a use case of the asset management system when a customer dies. When a customer dies, the customer's legal heir notifies the customer-referring company of the death. The customer-referring company then notifies the servicer company of the death.

[0022] The servicer company registers death information in the asset management device 100. The asset management device 100 transmits a death notification and a work instruction based on the death notification to the work execution device 200 that stores the assets of the customer. Upon receiving the death notification and the work instruction, the work execution device 200 deletes asset data as necessary based on the deletion flag for each asset type.

[0023] Each of the work execution devices 200 that received the death notification and work instruction generates a simple asset inventory that shows a list of assets after deletion processing has been performed as necessary, and transmits it to the asset management device 100. Note that the deletion processing and simple asset inventory generation processing described above may be performed manually by the user of the work execution device 200. Specifically, for example, the work execution device 200 decrypts the list of assets including the deletion flag for the customer and displays it on a display device, and receives input from the user of the work execution device 200 via an input device, thereby deleting asset data and generating a simple asset inventory.

[0024] The asset management device 100 merges the received simple asset inventories when it receives a simple asset inventory from each of the multiple work execution devices 200. The servicer company acquires the simple asset inventory (or the merged simple asset inventory if the simple asset inventories have been merged) from the asset management device 100 and sends it to the legal heir.

[0025] 3 is a block diagram showing an example of the configuration of the asset management device 100. The asset management device 100 is configured by a computer having, for example, a CPU (Central Processing Unit) 101, a memory 102, an auxiliary storage device 103, a communication device 104, an input device 105, and a display device 106.

[0026] The CPU 101 includes a processor and executes programs stored in the memory 102. The memory 102 includes a ROM (Read Only Memory), which is a non-volatile storage element, and a RAM (Random Access Memory), which is a volatile storage element. The ROM stores unchanging programs (e.g., a BIOS (Basic Input / Output System)). The RAM is a high-speed, volatile storage element such as a DRAM (Dynamic Random Access Memory), and temporarily stores programs executed by the CPU 101 and data used when the programs are executed.

[0027] The auxiliary storage device 103 is a large-capacity, non-volatile storage device such as a magnetic storage device (HDD (Hard Disk Drive)) or a flash memory (SSD (Solid State Drive)), and stores programs to be executed by the CPU 101 and data to be used when the programs are executed. That is, the programs are read from the auxiliary storage device 103, loaded into the memory 102, and executed by the CPU 101.

[0028] The input device 105 is a device such as a keyboard or mouse that receives input from an operator. The display device 106 is a device such as a display or printer that outputs the results of program execution in a format that can be viewed by the operator.

[0029] The communication device 104 is a network interface device that controls communication with other devices in accordance with a predetermined protocol, and includes a serial interface such as a USB (Universal Serial Bus).

[0030] Some or all of the programs executed by the CPU 101 may be provided to the asset management device 100 from removable media (CD-ROM, flash memory, etc.), which are non-transitory storage media, or from an external computer equipped with a non-transitory storage device via a network, and may be stored in the non-volatile auxiliary storage device 103, which is also a non-transitory storage medium. For this reason, the asset management device 100 should preferably have an interface for reading data from removable media. The same applies to the work execution device 200.

[0031] The asset management device 100 is a computer system configured on one physical computer or on multiple logically or physically configured computers, and may operate in separate threads on the same computer, or may operate on a virtual computer constructed on multiple physical computer resources. The same applies to the work execution device 200.

[0032] The CPU 101 includes, for example, an asset registration unit 111, a key management unit 112, an encryption unit 113, an information linking unit 114, and a death notification receiving unit 115. The asset registration unit 111 acquires customer asset information and registers it in the asset information table 223. The key management unit 112 manages encryption keys for encrypting customer asset data. The encryption unit 113 encrypts customer asset data using the encryption keys. The information linking unit 114 exchanges information with the work execution device 200. The death notification receiving unit 115 receives a death notification indicating that a customer has died.

[0033] For example, the CPU 101 functions as an asset registration unit 111 by operating in accordance with an asset registration program loaded into the memory 102, and functions as a key management unit 112 by operating in accordance with a key management program loaded into the memory 102. The same relationship exists between the programs and the functional units of the other functional units included in the CPU 101. The same relationship exists between the programs and the functional units of the functional units included in the CPU 201 of the work execution device 200, which will be described later.

[0034] Note that some or all of the functions of the CPU 101 and the functional units included in the CPU 201 of the task execution device 200 may be realized by hardware such as an ASIC (Application Specific Integrated Circuit) or an FPGA (Field-Programmable Gate Array).

[0035] The auxiliary storage device 103 holds, for example, a customer table 121, a legal heir table 122, an asset information table 123, a work performing company table 124, a simple asset inventory table 125, an encryption key table 126, a deletion rank table 127, and a selectable deletion rank table 128.

[0036] The customer table 121 holds personal information and death information of customers. The legal heir table 122 holds information about legal heirs of customers. The asset information table 123 holds information about assets owned by customers. The work performing company table 124 holds information about work performing companies that are users of the work performing device 200.

[0037] The simple asset inventory table 125 holds information indicating a simple inventory of a customer's assets that is generated upon the customer's death. The encryption key table 126 holds information regarding encryption keys that encrypt the customer's asset data. The deletion rank table 127 holds information that defines deletion ranks that indicate how to delete the customer's asset data after the customer's death. The selectable deletion rank table 128 holds information indicating selectable deletion ranks for each type of asset.

[0038] In addition, some or all of the information stored in the auxiliary storage device 103 and the auxiliary storage device 203 of the work execution device 200 described later may be stored in the memory 102 and the memory 202 of the work execution device 200 described later, respectively, or may be stored in a database connected to the device.

[0039] In this embodiment, the information used by the asset management system does not depend on the data structure and may be expressed in any data structure. In this embodiment, the information is expressed in a table format, but the information can be stored in an appropriately selected data structure from, for example, a list, a database, or a queue.

[0040] 4 is a block diagram showing an example of the configuration of the work performing device 200. The work performing device 200 is configured by a computer having a CPU 201, memory 202, auxiliary storage device 203, communication device 204, input device 205, and display device 206, for example.

[0041] The hardware description of CPU 201, memory 202, auxiliary storage device 203, communication device 204, input device 205, and display device 206 is omitted here as it is the same as the hardware description of CPU 101, memory 102, auxiliary storage device 103, communication device 104, input device 105, and display device 106.

[0042] The CPU 201 includes, for example, a data acquisition unit 211, a decryption unit 212, a data storage unit 213, and an information linking unit 214. The data acquisition unit 211 acquires data from various tables held in the auxiliary storage device 103. The decryption unit 212 decrypts encrypted data on the customer's assets. The data storage unit 213 stores information in various tables held in the auxiliary storage device 103. The information linking unit 214 exchanges information with the asset management device 100.

[0043] The auxiliary storage device 203 holds, for example, a customer table 221, an asset information table 223, a simple asset inventory table 225, a deletion rank table 227, and a selectable deletion rank table 228. The information that can be stored in the customer table 221, asset information table 223, simple asset inventory table 225, deletion rank table 227, and selectable deletion rank table 228 is similar to the information that can be stored in the customer table 121, asset information table 123, simple asset inventory table 125, deletion rank table 127, and selectable deletion rank table 128, and therefore a description thereof will be omitted.

[0044] 5 is an example of the customer table 121. The customer table 121 includes, for example, a customer ID field 1211, a name field 1212, an address field 1213, a phone number field 1214, a login ID field 1215, a password field 1216, a date of death field 1217, and a date of death receipt field 1218.

[0045] The customer ID column 1211 holds an ID that identifies a customer. The name column 1212 holds information indicating the name of the customer. The address column 1213 holds information indicating the address of the customer. The phone number column 1214 holds information indicating the phone number of the customer. The login ID column 1215 holds information indicating the login ID used by the customer to log in to the asset management device 100. The password column 1216 holds information indicating the password used to log in to the asset management device 100.

[0046] The date of death column 1217 holds information indicating the date of death of the customer. The date of death receipt column 1218 receives the date on which the customer's death notification was received. If a customer's death notification has not been received, for example, null values ​​are stored in the date of death column 1217 and the date of death receipt column 1218 corresponding to that customer.

[0047] 6 is an example of the legal heir table 122. The legal heir table 122 includes, for example, an heir ID column 1221, a customer ID column 1222, a name column 1223, an address column 1224, a telephone number column 1225, and a relationship column 1226.

[0048] The heir ID column 1221 holds an ID that identifies a legal heir. The customer ID column 1222 holds the customer ID of the customer who is the deceased relative to the legal heir indicated by the heir ID column 1221. The name column 1223 holds information indicating the name of the legal heir. The address column 1224 holds information indicating the address of the legal heir. The telephone number column 1225 holds information indicating the telephone number of the legal heir. The relationship column 1226 holds information indicating the relationship of the legal heir indicated by the heir ID column 1221 to the deceased customer.

[0049] 7 is an example of the asset information table 123. The asset information table 123 includes, for example, an asset ID column 1231, a customer ID column 1232, an encryption key ID column 1233, a deletion rank column 1234, a type column 1235, a registration date column 1236, an update date column 1237, a correspondence date column 1238, and a data column 1239.

[0050] The asset ID column 1231 holds an ID that identifies the asset of the customer indicated in the customer ID column 1232. The customer ID column 1232 holds a customer ID. The encryption key ID column 1233 holds an ID that identifies the encryption key that encrypted the data stored in the data column 1239. The deletion rank column 1234 holds the deletion rank of the data stored in the data column 1239. The type column 1235 holds information that indicates the type of asset.

[0051] The registration date column 1236 holds information indicating the date on which the record was registered. The update date column 1237 holds information indicating the date on which the record was last updated. If the record has not been updated, for example, a null value is stored in the update date column 1237. The response date column 1238 holds information indicating the date on which action was taken, such as including the record in a simple catalog, after notification of the death of the customer indicated in the customer ID column 1232 was received.

[0052] The data column 1239 holds encrypted data indicating assets. If the type of asset is cash, information indicating the location of the cash is an example of data; if the type of asset is a deposit account, information indicating the deposit account is an example of data; if the type of asset is an SNS, the login ID and password for the SNS are an example of data.

[0053] 8 is an example of the work performing company table 124. The work performing company table 124 includes, for example, a company ID column 1241, a company name column 1242, and a contact column 1243. The company ID column 1241 holds an ID that identifies the work performing company. The company name column 1242 holds information indicating the name of the work performing company. The contact column 1243 holds information indicating the contact information of the work performing company.

[0054] 9 is an example of the simple property inventory table 125. The simple property inventory table 125 includes, for example, an inventory ID column 1251, an asset ID column 1252, and a company ID column 1253. The inventory ID column 1251 holds an ID that identifies the simple property inventory. The asset ID column 1252 holds the asset ID of the asset included in the simple property inventory. The company ID column 1253 holds the company ID of the work performing company that created the simple property inventory.

[0055] 10 is an example of the encryption key table 126. The encryption key table 126 includes, for example, an encryption key ID column 1261 and an encryption key column 1262. The encryption key ID column 1261 holds an encryption key ID. The encryption key column 1262 holds an encryption key.

[0056] 11 is an example of the deletion rank table 127. The deletion rank table 127 includes, for example, a deletion rank column 1271 and a posthumous correspondence column 1272. The deletion rank column 1271 holds a deletion rank. The posthumous correspondence column 1272 holds information indicating a customer's posthumous correspondence with respect to asset data for which the deletion rank indicated by the deletion rank column 1271 is set.

[0057] In the example of Figure 11, asset data with a deletion rank set to "A" cannot be deleted even if notification of the customer's death is received. Asset data with a deletion rank set to "B" will be deleted N days (a predetermined period of time) after the date of the customer's death. Asset data with a deletion rank set to "C" will be deleted immediately when notification of the customer's death is received. Note that the deletion rank may include only "A" and either "B" or "C."

[0058] 12 is an example of the selectable deletion rank table 128. The selectable deletion rank table 128 includes, for example, a type column 1281 and a deletion rank column 1282. The type column 1281 holds information indicating the type of asset. The deletion rank column 1282 holds information indicating the deletion ranks that can be selected for data of assets of the type indicated in the type column 1281.

[0059] In the example of Figure 12, for assets subject to inheritance tax, such as cash, savings accounts, and real estate, only deletion rank "A" can be selected (i.e., they cannot be deleted even if a death notice is received). On the other hand, for assets that are not subject to inheritance tax at the time of asset information registration, such as social media and NFTs (Non-Fungible Tokens), any of deletion ranks "A," "B," and "C" can be selected.

[0060] Fig. 13 is a flowchart showing an example of asset information registration processing when a customer is alive. Before the asset information registration processing of Fig. 13 is executed, values ​​of the work performing company table 124, deletion rank table 127, selectable deletion rank table 128, deletion rank table 227, and selectable deletion rank table 228 are registered in advance.

[0061] The customer referral company introduces the asset management service to the customer, who is the deceased (S101). The customer referral company introduces the customer to the servicer company, the servicer company introduces the asset management service to the customer, and the customer applies for the asset management service (S102). Note that the customer may also apply for the asset management service to the servicer company without the customer being introduced by the customer referral company.

[0062] The asset registration unit 111 acquires the customer information, legal heir information, and asset information entered by the customer into the terminal owned by the customer, and executes information registration processing to register the information in the customer table 121, legal heir table 122, and asset information table 123, respectively (S103). Details of step S103 will be described later. The encryption unit 113 executes encryption processing to encrypt asset data using an encryption key (S104). Details of step S104 will be described later.

[0063] The information linking unit 114 transmits the information registered in the asset information table 123 to the work execution device 200, the data storage unit 213 registers the received information in the asset information table 223, and the information linking unit 114 deletes the data registered in the data column 1239 of the asset information table 123 (S105). By the processing of step S105, the asset data is deleted from the asset information table 123 of the asset management device 100, improving security. The information linking unit 114 executes deletion rank update processing based on the rule change (S106), and ends the asset information registration processing. Step S106 will be described in detail later.

[0064] 14 is a flowchart showing an example of the information registration process in step S103. The asset registration unit 111 acquires the customer information, legal heir information, and asset information input by the customer to the terminal owned by the customer (S1031).

[0065] The customer information entered in step S1031 is the value of the fields excluding the customer ID, date of death, and date of death receipt among the values ​​stored in the customer table 121. The legal heir information entered in step S1031 is the value of the fields excluding the heir ID and customer ID contained in the legal heir table 122. The asset information entered in step S1031 is the value of the asset type, deletion rank, and data among the values ​​stored in the asset information table 123.

[0066] When the customer inputs the type of asset, the asset registration unit 111 refers to the selectable deletion rank table 128 and presents the deletion rank corresponding to that type to the customer's terminal, and the customer selects the deletion rank to input from the presented deletion ranks.

[0067] In the above example, in step S103, the asset registration unit 111 acquires the customer information, legal heir information, and asset information entered by the customer into the terminal owned by the customer, but it is also possible for a person in charge of the servicer company to hear the customer information, legal heir information, and asset information from the customer, and for the asset registration unit 111 to accept input of the heard information via the input device 105.

[0068] The asset registration unit 111 generates a new customer ID, links the generated customer ID with the acquired customer information, and stores the generated record in the customer table 121 (S1032). The asset registration unit 111 generates a new heir ID for each legal heir indicated by the acquired legal heir information, and links each heir ID corresponding to the legal heir with the legal heir information corresponding to the heir ID and the customer ID generated in step S1032, and stores the generated record in the legal heir table 122 (S1032).

[0069] The asset registration unit 111 generates a new asset ID for each asset indicated by the asset information, obtains the registration date, and stores the generated record in the asset information table 123 (S1033) by linking each asset ID corresponding to the asset with the customer ID generated in step S1031, the deletion rank corresponding to the asset, the asset type, the registration date, and the asset data corresponding to the asset type, and terminates the information registration process.

[0070] 15 is a flowchart showing an example of the encryption process in step S104. The encryption unit 113 generates an encryption key for encrypting the asset data, and uses the generated encryption key to encrypt the asset data stored in the asset information table 123 in step S1033 (S1041). The encryption unit 113 can generate the encryption key using any encryption key generation algorithm. In this embodiment, the encryption unit 113 generates the encryption key using a common key encryption method.

[0071] Furthermore, in step S1041, the encryption unit 113 may perform encryption using a different encryption key for each asset indicated by the asset information acquired in step S1031, or may perform encryption using a different encryption key for each type of asset indicated by the asset information acquired in step S1031, or may perform encryption using the same encryption key for the assets indicated by the asset information acquired in step S1031, or may use the same encryption key for assets of customers with the same customer ID.

[0072] The key management unit 112 generates a new encryption key ID for each encryption key generated in step S1041, stores each encryption key ID corresponding to the encryption key corresponding to the data encrypted in step S1041 in the asset information table 123, stores the combination of each generated encryption key ID and the corresponding encryption key in the encryption key table 126 (S1042), and terminates the encryption process.

[0073] 16 is a flowchart showing an example of the deletion rank update process in step S106. The information linking unit 114 determines whether a rule change regarding an asset has occurred (S1061). Note that in step S1061, the information linking unit 114 determines that a rule change regarding an asset has occurred when, for example, information regarding a rule change regarding an asset (information indicating the content of the rule change and the type of asset for which the rule change has been made) is input to the input device 105, or when the information indicating a rule change regarding an asset is received from an external system connected to the asset management apparatus 100.

[0074] Examples of rule changes include legal amendments, guideline changes, new precedents, changes to deposit regulations, and changes to the terms of use of social media. The following mainly describes an example in which, in step S1061, the information linking unit 114 determines whether there are any assets of a type that were not subject to inheritance tax before the legal amendments (including legal amendments, guideline changes, or new precedents), but have become subject to inheritance tax due to the legal amendments.

[0075] If the information linking unit 114 determines that there is no asset of a type that was not subject to inheritance tax before the legal revision, etc. but has become subject to inheritance tax due to the legal revision, etc. (S1061: NO), the information linking unit 114 repeats the processing of step S1061. Note that when the processing of step S1061 has been repeated for a predetermined time, the deletion rank update processing may be terminated.

[0076] If the information linking unit 114 determines that there is an asset of a type that was not subject to inheritance tax before the legal amendment, etc. but has become subject to inheritance tax due to the legal amendment, etc. (S1061: YES), it notifies each work execution device 200 of the type of asset, and the data acquisition unit 211 acquires a record including the type from the asset information table 223 (S1062).

[0077] The data storage unit 213 updates the deletion rank of "B" or "C" contained in the acquired record to "A" (S1063), and terminates the deletion rank update process. Furthermore, if the data storage unit 213 determines in step S1063 that the deletion ranks corresponding to the relevant type in the selectable deletion rank table 228 include "B" and "C," it is desirable to delete "B" and "C."

[0078] In step S1063, the asset registration unit 111 may also acquire a record including the relevant type from the asset information table 123, and update the deletion rank of "B" or "C" included in the acquired record to "A." Furthermore, if the asset registration unit 111 determines in step S1063 that the deletion ranks corresponding to the relevant type in the selectable deletion rank table 228 include "B" and "C," it is desirable to delete "B" and "C."

[0079] The deletion rank update process in Figure 16 makes it possible to change the data for assets that were not subject to inheritance tax when the asset information was registered so that they will not be deleted at the time of the customer's death, which means it is possible to respond to legal changes, etc.

[0080] In step S1061, the information linking unit 114 may determine whether there is a type of asset that was subject to inheritance tax before the legal revision, etc. but is no longer subject to inheritance tax due to the legal revision, etc. If the information linking unit 114 determines that there is a type of asset that was subject to inheritance tax before the legal revision, etc. but is no longer subject to inheritance tax due to the legal revision, etc., the information linking unit 114 notifies each work execution device 200 of the type, and the data storage unit 213 may acquire a record of the asset information table 223 that includes the type and update the deletion rank of "A" included in the acquired record to "B" or "C", or may notify the customer via the asset management device 100 that the deletion rank of "A" included in the acquired record can be updated to "B" or "C".

[0081] Furthermore, in step S1061, the information linking unit 114 may determine whether or not the asset of the relevant type can no longer be transferred to anyone other than the principal due to a revision of the rules and regulations related to the asset (for example, the terms of use of an SNS). If the information linking unit 114 determines that the asset of the relevant type can no longer be transferred to anyone other than the principal due to a revision of the rules and regulations related to the asset (for example, the terms of use of an SNS), it notifies each task execution device 200 of the type, and the data storage unit 213 acquires a record of the asset information table 223 that includes the type, and updates the deletion rank of "A" included in the acquired record to "B" or "C".

[0082] The determination in step S1061 may be performed by the information linking unit 214 of the task execution device 200. In the above example, the deletion rank update process in step S106 is performed as part of the information registration process in Fig. 13, but it may also be performed periodically independently of the information registration process.

[0083] 17 is a flowchart showing an example of asset information update processing executed during a customer's lifetime. The customer logs in to the asset management device 100 (S201). Specifically, for example, the customer transmits a login ID and password from their own terminal to the asset management device 100, and if the asset registration unit 111 determines that the combination of the received login ID and password is included in the customer table 121, it determines that the login was successful and acquires the customer ID of the record that includes that combination.

[0084] The asset registration unit 111 acquires all records corresponding to the customer ID from the asset information table 123 (S202). The information linking unit 114 transmits the asset ID to the work execution device 200, the data acquisition unit 211 acquires encrypted data corresponding to the customer ID from the asset information table 223, and the information linking unit 214 transmits the encrypted data to the asset management device 100 (S203).

[0085] The asset registration unit 111 presents the list of records acquired in step S201 to the customer by, for example, transmitting it to a terminal owned by the customer or displaying it on the display device 106 (S204). However, in step S204, the key management unit 112 identifies the encryption key ID included in the record acquired in step S201 and acquires the encryption key corresponding to the encryption key ID, the encryption unit 113 decrypts the data using the encryption key, and the asset registration unit 111 presents the decrypted data in place of the data included in the acquired record.

[0086] The customer transmits the correction details for the presented record (for example, deletion rank, asset type, and / or data correction details) to the asset management device 100 from the customer's own terminal (S205). The asset registration unit 111 updates the record in the asset information table 123 by reflecting the received correction details in the record (S206). The asset registration unit 111 may also store the update date in the updated record.

[0087] When data is updated during record updating, the key management unit 112 obtains the encryption key ID contained in the updated record and obtains the encryption key associated with the obtained encryption key from the encryption key table 126 (S207), and the encryption unit 113 encrypts the data of the record in the asset information table 123 (if the data has been updated) with the obtained encryption key (S208).

[0088] The information linking unit 114 transmits the updated record in the asset information table 123 to the work execution device 200, the data storage unit 213 updates the record in the asset information table 223, and the asset registration unit 111 deletes the data of the record in the asset information table 123 (S209), and the asset information update process is terminated.

[0089] In step S205, the customer may transmit an addition instruction indicating the content to be added to the record from their own terminal. In this case, in step S206, the asset registration unit 111 adds a record generated by linking the customer ID to the content to be added to the asset information table 123. Furthermore, the processing of step S207 is omitted, and in step S208, the encryption unit 113 generates an encryption key and encrypts the record included in the added data with the generated encryption key, the key management unit 112 generates an encryption key ID corresponding to the encryption key, and stores the combination of the encryption key ID and the encryption key in the encryption key table 126. Furthermore, in step S209, the information linking unit 114 transmits the added record in the asset information table 123 to the work execution device 200, the data storage unit 213 adds the record to the asset information table 223, and the asset registration unit 111 deletes the data of the added record from the asset information table 123, thereby terminating the asset information update processing.

[0090] Figure 18 is a flowchart showing an example of asset information management processing after the death of a customer. The legal heirs of a deceased customer notify the customer-referring company of the death by providing information identifying the customer (e.g., customer name, address, telephone number, etc.) and the date of death (S301). The customer-referring company notifies the servicer company of the death (S302). The legal heirs of a deceased customer may also notify the servicer company directly of the death without notifying the customer-referring company of the death.

[0091] The servicer company registers the death information of the customer in the asset management device 100 (S303). Specifically, for example, the death notification receiving unit 115 receives input of the customer ID of the customer (for example, by referring to the customer table 121, the customer ID corresponding to the combination of the customer name, address, and telephone number included in the death notification can be identified) and the date of death from the servicer company to the input device 105, and stores the date of death in the record in the customer table 121 that includes the customer ID.

[0092] The information linking unit 114 executes a death information linking process that links death information with the work execution device 200 (S304). The death information linking process in step S304 will be described in detail later. The data storage unit 213 references the deletion rank of the record corresponding to the customer ID in the asset information table 223, and deletes the record according to the deletion rank (S305). Specifically, the data storage unit 213 deletes records corresponding to the customer ID that have a deletion rank of "B", and if N days have passed since the date of death of the customer, also deletes records corresponding to the ID that have a deletion rank of "C".

[0093] The information linking unit 114 executes a simple asset inventory generation process to generate a simple asset inventory for the customer (S306). Details of the simple asset inventory generation process in step S306 will be described later. The servicer company acquires the simple asset inventory from the asset management device 100 (S307). The servicer company sends the acquired simple asset inventory to the legal heir (S308), and ends the asset information management process after the customer's death. Note that instead of the processes of steps S307 and S308, the asset management device 100 may execute a process to send the simple asset inventory to a terminal owned by the legal heir.

[0094] 19 is a flowchart showing an example of the death information linking process in step S304. Based on the death notice, the information linking unit 114 obtains from the customer table 121 a record corresponding to the customer indicated in the death notice (S3041). The information linking unit 114 obtains from the legal heir table 122 a record including the customer ID and from the asset information table 123 a record including the customer ID (S3042).

[0095] The information linking unit 114 identifies the encryption key ID included in each record of the asset information table 123 acquired in step S3042, and acquires records corresponding to each identified encryption key ID from the encryption key table 126 (S3043). The information linking unit 114 transmits the records acquired from the legal heir table 122 in step S3042, the records acquired from the customer data in step S3041, and the records acquired from the encryption key table 126 in step S3043 to the work execution device 200 (S3044), and terminates the death information linking process.

[0096] 20 is a flowchart showing an example of the simplified asset inventory generation process of step S306. The decryption unit 212 decrypts the data corresponding to the customer ID in the asset information table 123 using each encryption key (contained in the record obtained from the encryption key table 126) received in step S3044 (S3051). The data storage unit 213 stores the data decrypted in step S3051 in the asset information table 223 (S3052).

[0097] The information linking unit 214 generates a simple property inventory based on the record containing the decrypted data in the asset information table 223, generates a new inventory ID, and generates a record linking the generated inventory ID with the simple property inventory (S3053).

[0098] Specifically, for example, the information linking unit 214 generates a record that associates an asset ID corresponding to the decrypted data in the asset information table 223 with the company ID of the work performing company that uses the work performing device 200 and an inventory ID. Note that the information linking unit 214 may also include the decrypted data in the record, but it is desirable not to include data of a predetermined type of asset (for example, a PIN number for a deposit account) in the record.

[0099] The information linking unit 214 transmits the generated record to the asset management device 100, and the information linking unit 114 stores the received record in the simple asset inventory table 125 (S3054), and terminates the simple asset inventory generation process. Note that when the asset management device 100 receives records in which an inventory ID and a simple asset inventory are linked from multiple work execution devices 200, the information linking unit 114 stores the multiple records in the simple asset inventory table 125, thereby generating a merged simple asset inventory.

[0100] As described above, the asset management system of this embodiment receives asset information including asset type, deletion rank, and asset data from the customer during their lifetime, and after the customer's death, it handles post-death actions for each type of asset data (whether to delete or not delete) based on the deletion rank for each asset type, and then generates a simple asset inventory and hands it over to the legal heirs, thereby allowing inheritance to be carried out based on the customer's wishes during their lifetime.

[0101] In particular, for example, a customer can register their SNS account and password combination in the asset management system as a deletion rank "B" or "C", so that the SNS account and password combination will not be passed on to their legal heirs after their death, thereby protecting their privacy.

[0102] In addition, the asset management system of this embodiment can adapt the handling of asset data after a customer's death to the changed rules by changing the deletion rank as necessary when it detects a change in the rules regarding assets.

[0103] The present invention is not limited to the above-described embodiments, but includes various modifications. For example, the above-described embodiments have been described in detail to clearly explain the present invention, and the present invention is not necessarily limited to those including all of the described configurations. Furthermore, it is possible to replace part of the configuration of one embodiment with the configuration of another embodiment, or to add the configuration of another embodiment to the configuration of one embodiment. Furthermore, it is possible to add, delete, or replace part of the configuration of each embodiment with other configurations.

[0104] Furthermore, the above-described configurations, functions, processing units, processing means, etc. may be partially or entirely implemented in hardware, for example, by designing them as integrated circuits. The above-described configurations, functions, etc. may also be implemented in software, with a processor interpreting and executing a program that implements each function. Information such as the programs, tables, and files that implement each function can be stored in a memory, a recording device such as a hard disk or SSD (Solid State Drive), or a recording medium such as an IC card, SD card, or DVD.

[0105] In addition, the control lines and information lines shown are those that are considered necessary for the explanation, and do not necessarily show all the control lines and information lines in the product. In reality, it can be assumed that almost all components are interconnected. [Explanation of symbols]

[0106] 100 Asset management device, 101 CPU, 102 memory, 103 auxiliary storage device, 104 communication device, 105 input device, 111 asset registration unit, 112 key management unit, 113 encryption unit, 114 information linkage unit, 115 death notification receiving unit, 121 customer table, 122 legal heir table, 123 asset information table, 124 work execution company table, 125 simple asset inventory table, 126 encryption key table, 127 deletion rank table, 128 selectable deletion rank table, 200 work execution device, 201 CPU, 202 memory, 203 auxiliary storage device, 204 communication device, 205 input device, 211 data acquisition unit, 212 decryption unit, 213 data storage unit, 214 information linkage unit, 223 asset information table, 227 deletion rank table

Claims

1. An asset management system for managing customer assets, an asset management device and a work execution device; the work execution device holds asset information indicating, for each asset type, data on assets owned by the customer and a deletion rank indicating a response to the data after the death of the customer; The deletion rank includes a first rank indicating that the data will not be deleted after the death of the customer, and a second rank indicating that the data will be deleted if a predetermined condition is satisfied after the death of the customer, When the asset management device acquires information indicating the rule change content related to the asset and the type of the asset that is the target of the rule change, the asset management device notifies the work execution device of the information; the work execution device updates a deletion rank corresponding to the type of asset that is the target of the rule change in the asset information based on the rule change content; When the asset management device receives a death notice of the first customer, the asset management device transmits the death notice to the work execution device; the work execution device executes a deletion process to delete data of an asset of the first customer whose deletion rank is the second rank from the asset information if the predetermined condition is satisfied; The asset management system transmits to the asset management device a list of assets of the first customer that are included in the asset information and whose data has not been deleted by the deletion process.

2. The asset management system according to claim 1, The rule changes include changing a type of asset that was not subject to inheritance tax to a type of asset that is subject to inheritance tax, The work execution device updates the second-class rank among the deletion ranks corresponding to the type of asset that is subject to inheritance tax to the first-class rank, in the asset management system.

3. The asset management system according to claim 1, The rule changes include changing the type of assets that were subject to inheritance tax to types of assets that are not subject to inheritance tax, The work execution device updates the first-class deletion rank corresponding to the type of asset that is subject to inheritance tax to the second-class rank, or notifies the asset management device that the first-class deletion rank corresponding to the type of asset that is subject to inheritance tax can be updated to the second-class rank.

4. The asset management system according to claim 1, The rule changes include making it impossible to transfer assets of a type that was previously transferable to anyone other than the individual, The work execution device updates the first rank among the deletion ranks corresponding to the type of asset that can no longer be transferred to anyone other than the owner to the second rank.

5. The asset management system according to claim 1, The asset management system, wherein the second rank includes a first rank indicating that the data will be deleted immediately if the death of the customer is detected, and a second rank indicating that the data will be deleted after a predetermined period of time has passed since the death of the customer.

6. The asset management system according to claim 1, The asset information holds a record in which encrypted data indicating assets held by the customer is encrypted with an encryption key, a deletion rank indicating a response to the data after the death of the customer, and a type of asset are associated with each other; The asset management device connected to a display device, holding said encryption key; When an instruction to update the record of the first customer in the asset information is received, the record of the first customer in the asset information is acquired from the work execution device; decrypting the encrypted data included in the acquired record with the encryption key; replacing the encrypted data included in the acquired record with the decrypted data, and then displaying the record on the display device; Accept the update details of the acquired record, updating the acquired record based on the update content; encrypting data indicating assets owned by the customer that is included in the updated record with the encryption key, and transmitting the record to the work execution device; The work execution device is receiving a record transmitted from the asset management device; The asset management system reflects the received record in the asset information.

7. An asset management method by an asset management system that manages customer assets, comprising: the asset management system includes an asset management device and an operation execution device; the work execution device holds asset information indicating, for each asset type, data on assets owned by the customer and a deletion rank indicating a response to the data after the death of the customer; The deletion rank includes a first rank indicating that the data will not be deleted after the death of the customer, and a second rank indicating that the data will be deleted if a predetermined condition is satisfied after the death of the customer, The asset management method includes: When the asset management device acquires information indicating the rule change content regarding the asset and the type of the asset that is the target of the rule change, the asset management device notifies the work execution device of the information; the work execution device updates a deletion rank corresponding to the type of asset that is the target of the rule change in the asset information based on the rule change content; When the asset management device receives a death notice of the first customer, the asset management device transmits the death notice to the work execution device; the work execution device executes a deletion process to delete data of an asset of the first customer whose deletion rank is the second rank from the asset information if the predetermined condition is satisfied; An asset management method, in which the work execution device transmits to the asset management device a list indicating the assets of the first customer that are included in the asset information and whose data has not been deleted by the deletion process.

8. 8. The asset management method according to claim 7, The rule changes include changing a type of asset that was not subject to inheritance tax to a type of asset that is subject to inheritance tax, The asset management method is an asset management method in which the work execution device updates the second rank among the deletion ranks corresponding to the type of asset that is subject to inheritance tax to the first rank.

9. 8. The asset management method according to claim 7, The rule changes include changing the type of assets that were subject to inheritance tax to types of assets that are not subject to inheritance tax, The asset management method includes the task execution device updating the first-class deletion rank corresponding to the type of asset that is subject to inheritance tax to the second-class rank, or notifying the asset management device that the task execution device can update the first-class deletion rank corresponding to the type of asset that is subject to inheritance tax to the second-class rank.

10. 8. The asset management method according to claim 7, The rule changes include making it impossible to transfer assets of a type that was previously transferable to anyone other than the individual, The asset management method is an asset management method in which the work execution device updates the first rank among the deletion ranks corresponding to the type of asset that can no longer be transferred to anyone other than the owner to the second rank.

11. 8. The asset management method according to claim 7, The asset management method, wherein the second rank includes a first rank indicating that the data will be deleted immediately if the death of the customer is detected, and a second rank indicating that the data will be deleted after a predetermined period of time has passed since the death of the customer.

12. 8. The asset management method according to claim 7, The asset information holds a record in which encrypted data indicating assets held by the customer is encrypted with an encryption key, a deletion rank indicating a response to the data after the death of the customer, and a type of asset are associated with each other; The asset management device connected to a display device, holding said encryption key; The asset management method when the asset management device receives an instruction to update a record of a first customer in the asset information, the asset management device acquires the record of the first customer in the asset information from the work execution device; the asset management device decrypts the encrypted data included in the acquired record using the encryption key; the asset management device replaces the encrypted data included in the acquired record with the decrypted data, and then displays the record on the display device; the asset management device receives the updated content of the acquired record; the asset management device updates the acquired record based on the update content; the asset management device encrypts data indicating the assets held by the customer, which is included in the updated record, with the encryption key, and transmits the record to the work execution device; the work execution device receives the record transmitted from the asset management device; The asset management method, wherein the work execution device reflects the received record in the asset information.

Images