Contract inquiry system and contract inquiry method

Abstract

To provide a contract inquiry system which enables efficient inquiry about contract information.SOLUTION: A service relevance calculation unit 213 calculates, for each service, service relevance which is a degree of relevance between an ancestor and the service, based on attribute information indicating attributes of the ancestor and past inquiry record information indicating past records of contract inquiry. An inquiry condition creation unit 212 selects, based on the service relevance, an inquiry target service which is a service to be subjected to contract inquiry. A contract inquiry unit 211 performs contract inquiry on the inquiry target service using personal information pertaining to the ancestor.SELECTED DRAWING: Figure 2

Description

[Technical Field]

[0001] The present disclosure relates to a contract inquiry system and a contract inquiry method. [Background technology]

[0002] Following the death of a deceased person, the surviving family members must complete a wide range of complex procedures. Among these, inheritance procedures are particularly time-consuming, as they must begin by identifying financial institutions and other entities that may be holding the inherited assets. For example, in order to organize the deceased's assets, the heirs must review documents such as contracts and bankbooks held by the deceased and contact financial institutions and other entities that may be holding the deceased's assets. However, if the deceased did not leave behind any documents or if the heirs are unaware of financial institutions that may be holding the inherited assets, the heirs must make exhaustive inquiries to various financial institutions and other entities, which is time-consuming. As a result, in some cases, inheritance procedures may not be completed within the three-month deadline for renouncing inheritance.

[0003] In response to this, a technology for understanding a user's contract is disclosed in Patent Document 1. In the technology described in Patent Document 1, a central computer system connected to the computer systems of multiple insurance companies via a dedicated network investigates the existence of an insurance contract for a target person in response to a request received from a user, and provides the user with information on the insurance contract as the investigation results. [Prior art documents] [Patent documents]

[0004] [Patent Document 1] Japanese Patent Application Laid-Open No. 2011-203998 Summary of the Invention [Problem to be solved by the invention]

[0005] In the case of inheritance procedures, the businesses that may hold inherited assets are not limited to insurance companies but also include a wide range of other entities such as banks and securities companies, so querying all of them would increase the load on the system and the amount of communication traffic.The technology described in Patent Document 1 targets only specific insurance companies and does not take into consideration the load on the system and the amount of communication traffic.

[0006] An object of the present disclosure is to provide a contract inquiry system and a contract inquiry method that enable efficient inquiry of contract information. [Means for solving the problem]

[0007] A contract inquiry system according to one aspect of the present disclosure is a contract inquiry system that performs a contract inquiry, which is an inquiry into contract information for each service provided by each of a plurality of service providers, and has: a calculation unit that calculates a service relationship degree, which is the degree of relationship between the subject and the service, for each service based on attribute information that indicates the attributes of the subject of the contract inquiry and inquiry performance information that indicates the performance of the past contract inquiry; a selection unit that selects the queried service, which is the service for which the contract inquiry is to be performed, based on the service relationship degree; and an inquiry unit that performs the contract inquiry for the queried service using personal information about the subject. [Effects of the Invention]

[0008] According to the present invention, it is possible to efficiently inquire about contract information. [Brief explanation of the drawings]

[0009] [Figure 1] 1 is a diagram illustrating an information processing system according to an embodiment of the present disclosure. [Figure 2] FIG. 1 is a diagram illustrating an example of a configuration of a contract inquiry system. [Figure 3] 10 is a flowchart illustrating an example of a contract inquiry process. [Figure 4] FIG. 10 is a diagram showing an example of personal information data for inquiry. [Figure 5] 10 is a flowchart illustrating an example of a detection tendency calculation process. [Figure 6] FIG. 10 is a diagram illustrating an example of attribute item master data. [Figure 7] FIG. 10 is a diagram illustrating an example of attribute information data. [Figure 8] FIG. 10 is a diagram illustrating an example of used attribute item data. [Figure 9] FIG. 10 is a diagram illustrating an example of detection tendency relational expression data. [Figure 10] FIG. 10 is a diagram showing an example of a query setting input screen. [Figure 11] 10 is a flowchart illustrating an example of a service relationship degree calculation process. [Figure 12] FIG. 10 is a diagram illustrating an example of service relationship degree analysis result data. [Figure 13] FIG. 10 is a diagram illustrating another example of service relationship degree analysis result data. [Figure 14] 10 is a flowchart illustrating an example of an information collaboration destination list creation process. [Figure 15] FIG. 10 is a diagram illustrating an example of an information collaboration destination list creation process. [Figure 16] FIG. 10 is a diagram showing an example of query condition data. [Figure 17] 10 is a flowchart illustrating an example of a contract inquiry process. [Figure 18] FIG. 10 is a diagram showing an example of contract inquiry result data. [Figure 19] FIG. 10 is a diagram showing an example of a contract inquiry result screen. [Figure 20] 10 is a flowchart illustrating an example of an inquiry performance analysis process. DETAILED DESCRIPTION OF THE INVENTION

[0010] Hereinafter, embodiments of the present disclosure will be described with reference to the drawings.

[0011] The embodiments described below are examples for explaining the present disclosure, and appropriate omissions and simplifications have been made for clarity of explanation. The present disclosure can be implemented in various other forms. Each component described in the embodiments may be singular or plural unless otherwise specified. While various types of information may be described using expressions such as "table" and "list," the various types of information may also be expressed using data structures other than these. Identification information may also be referred to as an ID or the like.

[0012] In the following description, the person requesting an inquiry into contract information related to the deceased will be referred to as the "user," and the person making the contract inquiry, which is an inquiry into contract information at the user's request, will be referred to as the "touchpoint company." The deceased is the subject of the contract inquiry, and the user is, for example, a representative heir, an heir, an agent formally delegated by an heir, or a person who is organizing the deceased's affairs before death. A touchpoint company is, for example, a person (individual or corporation) formally delegated by the user, or a service provider that has already accepted inheritance procedures related to the deceased. According to this embodiment, the user is an heir, and is legally permitted to obtain contract information from all service providers related to the deceased.

[0013] 1 is a diagram illustrating an information processing system according to an embodiment of the present disclosure. The information processing system 1 includes a platform 100, a touchpoint company terminal 110, and a contract management system 120, which are connected to each other via a network so that they can communicate with each other.

[0014] Platform 100 is a platform for improving the efficiency of inheritance procedures, and includes a contract inquiry system 200. Contract inquiry system 200 is a system that performs contract inquiries, which are inquiries about contract information related to the deceased, in accordance with a contract inquiry request from touchpoint company terminal 110. In addition to contract inquiry system 200, platform 100 may also have, for example, a document creation system 101 that creates documents to be used in inheritance procedures according to the contract information, and a procedure proxy system 102 that performs the inheritance procedures on behalf of the deceased.

[0015] The touchpoint company terminal 110 is a terminal that accepts requests from user 2 and transmits a contract inquiry request to the contract inquiry system 200 in response to the request. The touchpoint company terminal 110 also scrutinizes the information provided by user 2 to confirm the legitimacy of the user as an heir or representative, thereby reducing the work required by each service provider to confirm the legitimacy of the user. The provided information is, for example, information required for inheritance procedures, such as a family register, a power of attorney, and personal information of the user and the deceased.

[0016] The contract management system 120 is a system managed by a service provider that manages inherited assets, etc., and sends back a response to a contract inquiry from the contract inquiry system 200 to the contract inquiry system 200. The service providers are, for example, banks and securities companies. Note that in FIG. 1, there are three service providers, service providers A to C, but the number of service providers is not particularly limited.

[0017] 2 is a diagram showing an example of the configuration of a contract inquiry system 200. The contract inquiry system 200 shown in FIG.

[0018] The memory 202 stores a program (computer program) that defines the operation of the processor 203, as well as various data used and generated by each function implemented by the program. The processor 203 is a computer that reads and executes the program stored in the memory 202 to implement various functions. In this embodiment, the functional units of the contract inquiry system 200 include a contract inquiry unit 211, an inquiry condition creation unit 212, a service relationship degree calculation unit 213, an inquiry tendency calculation unit 214, and an inquiry performance analysis unit 215, which are shown in the memory 202 for convenience. The network interface 204 is communicatively connected to external devices such as the touchpoint company terminal 110 and the contract management system 120, and transmits and receives data to and from these external devices. The auxiliary storage device 205 stores various data used and generated by each function implemented by the program.

[0019] The contract inquiry system 200 is a system that repeatedly makes contract inquiries to service providers (contract management system 120) while updating personal information used for contract inquiries, and has a mechanism for estimating services that are closely related to the deceased and making contract inquiries using the estimated services as the services to be inquired about in order to improve the efficiency of contract inquiries (reduction of load and resources, etc.). In order to estimate services that are closely related to the deceased, inquiry performance information that shows the performance of past contract inquiries is used.

[0020] The contract inquiry unit 211 is an inquiry unit that performs contract inquiries for the service being inquired about. The inquiry condition creation unit 212 is a setting unit that creates and sets inquiry conditions including termination conditions for terminating the contract inquiry. The service relationship degree calculation unit 213 is a calculation unit that calculates the service relationship degree, which is the degree of relationship between the deceased and the service. The inquiry tendency calculation unit 214 is a prediction unit that predicts the detection tendency, which is the tendency to detect the contract of the deceased. The inquiry performance analysis unit 215 is an update unit that updates inquiry performance information based on the results of the contract inquiry.

[0021] FIG. 3 is a flowchart for explaining an example of a contract inquiry process in which the contract inquiry system 200 makes a contract inquiry to a service provider.

[0022] In the contract inquiry process, the contract inquiry unit 211 of the contract inquiry system 200 receives the confirmation result of whether or not user 2 is legitimate and the personal information of the deceased from the touchpoint company terminal 110, and if the confirmation result shows that user 2 is legitimate, it records the personal information of the deceased in the memory 202 as personal information data for inquiry (step S101). Note that if the confirmation result shows that user 2 is not legitimate, the contract inquiry unit 211 returns an error message to the touchpoint company terminal 110 and ends the process.

[0023] FIG. 4 is a diagram showing an example of personal information inquiry data. The personal information inquiry data 300 shown in FIG. 4 stores personal information related to the decedent. Specifically, the personal information inquiry data 300 includes a personal information inquiry data table 301 that stores personal identification information, which is information that can identify an individual (the decedent). The personal identification information is used to perform contract inquiries in the contract management system 120, and in the example of FIG. 4, includes a personal information ID for identifying the personal identification information, an inquiry condition ID for identifying the inquiry conditions that are conditions for performing contract inquiries on the decedent, and the decedent's name, date of birth, gender, and address. In addition to the example of FIG. 4, the personal information inquiry data 300 stores multiple pieces of personal information for one decedent in auxiliary tables 302 to 304, separate from the personal information inquiry data table 301. In the example of FIG. 4, auxiliary table 302 stores telephone numbers, auxiliary table 303 stores former names, and auxiliary table 304 stores former addresses. In addition to the above examples, examples of personal information that may exist multiple times for one decedent include bank account numbers. Furthermore, in this embodiment, the inquiry condition is described as the primary key, but the primary key may be other information such as a personal information ID.

[0024] Returning to the explanation of the contract inquiry process in Fig. 3, the inquiry tendency calculation unit 214 executes a detection tendency calculation process (see Fig. 5) to generate trend analysis data that analyzes the detection tendency, which is the tendency of the service for detecting contracts related to the deceased, based on the inquiry personal information data and the performance data that stores the inquiry performance information related to the performance of past contract inquiries (step S102).

[0025] FIG. 5 is a flowchart illustrating an example of the detection tendency calculation process.

[0026] In the detection tendency calculation process, the inquiry tendency calculation unit 214 first processes the inquiry personal information data using pre-prepared attribute item master data to generate attribute information data that stores attribute information indicating the attributes of the deceased, and records this in the memory 202 (step S201).

[0027] Fig. 6 is a diagram showing an example of attribute item master data. The attribute item master data 400 shown in Fig. 6 includes fields 401 to 403. Field 401 stores an item ID that identifies an attribute item. Field 402 stores the item name of the item identified by the item ID. Field 403 stores an explanation of the item identified by the item ID. The attribute of the item name "constant" is a constant term in a relational equation (regression equation) of the detection tendency, which will be described later.

[0028] FIG. 7 is a diagram showing an example of attribute information data. The attribute information data 410 shown in FIG. 7 has an attribute information data table 420 that stores attribute information indicating the attributes of the decedent. In the example of FIG. 7, the attribute information includes, for each attribute information ID that identifies the attribute information, attribute items such as gender, year of birth, month of birth, and prefecture of residence. Furthermore, similar to the reference personal information data 300 shown in FIG. 4, the attribute information data 410 stores multiple pieces of attribute information for one decedent in an auxiliary table 430 separate from the attribute information data table 420. An example of attribute information that exists multiple times for one decedent is the previous prefecture of residence.

[0029] The inquiry tendency calculation unit 214 generates attribute information data 410 by, for example, extracting attribute information corresponding to each item of the attribute item master data 400 from the inquiry personal information data 300. At this time, the inquiry tendency calculation unit 214 may generate used attribute item data indicating the attributes used in the attribute information data 410 as used attributes and record this in the memory 202. FIG. 8 is a diagram showing used attribute item data 440 as an example of used attribute item data. The used attribute item data 440 includes a field 441 for storing an attribute information ID that identifies attribute information, and a field 442 for storing an item ID that identifies the item used in the attribute information.

[0030] Returning to the explanation of the detection tendency calculation process in Fig. 5, after recording the attribute information data, the inquiry tendency calculation unit 214 selects one of the detection items, which are items of the detection tendency for detecting contracts of the deceased through contract inquiry (step S202). The detection items include, for example, the number of inquiries, which is the number of times contract inquiries are repeated, and the number of detected contracts, which is the number of contracts detected through contract inquiry.

[0031] The inquiry tendency calculation unit 214 calculates the detection tendency of the contract of the deceased for the selected detection item based on the performance data related to past contract inquiry results and in accordance with the attributes of the deceased indicated in the attribute information data (step S203).

[0032] The performance data includes, as inquiry performance information, detection trend analysis result data obtained by analyzing detection trends from contract inquiry performance. In this embodiment, the detection trends are calculated using multiple regression analysis with the detection items as the objective variables and the attributes of the deceased as the explanatory variables, and the detection trend analysis result data is detection trend relational equation data that indicates the regression equation that is the result of the multiple regression analysis.

[0033] FIG. 9 is a diagram showing an example of detection tendency relational expression data. Detection tendency relational expression data 450 shown in FIG. 9 includes fields 451 to 454. Field 451 stores a coefficient ID that identifies the coefficient of the regression equation. Field 452 stores a response variable that is the detection tendency. Field 453 stores an item ID of an attribute that is an explanatory variable. Field 454 stores a coefficient value. In the example of FIG. 9, the multiple regression equation for the detection tendency (y) of the number of inquiries is y=8+33X J001 +42X J002 +14X J0003 +7X J004 The inquiry tendency calculation unit 214 calculates the detection tendency of the number of inquiries by substituting the attribute value, which is the value of the attribute of the deceased, for each objective variable X of this regression equation.

[0034] Returning to the explanation of the detection tendency calculation process in Fig. 5, after calculating the detection tendency of the selected detection items, the inquiry tendency calculation unit 214 determines whether or not all detection items have been selected (step S204). If all detection items have not been selected (step S204: No), the inquiry tendency calculation unit 214 returns to the process of step S202.

[0035] If all detection items have been selected (step S204: Yes), the inquiry tendency calculation unit 214 generates data that associates detection items with detection tendencies for each detection item as detection tendency data regarding the deceased, records this in memory 202 (step S205), and terminates the detection tendency calculation process.

[0036] Returning to the explanation of the contract inquiry process in Fig. 3, when the detection tendency calculation process is completed, the inquiry tendency calculation unit 214 transmits information indicating an inquiry condition input screen that prompts input of inquiry conditions for the contract inquiry to the touchpoint company terminal 110, and displays the inquiry condition input screen on the touchpoint company terminal 110. Thereafter, the inquiry condition creation unit 212 receives an inquiry request requesting execution of the contract inquiry (step S103). The inquiry condition input screen shows detection tendency data as a reference for the inquiry conditions.

[0037] FIG. 10 illustrates an example of a query setting input screen. The query setting input screen 460 illustrated in FIG. 10 includes a query trend display section 461, a query setting input section 462, and an excluded service selection section 463. The query trend display section 461 displays query trend data. The query setting input section 462 and the excluded service selection section 463 are interfaces for inputting query conditions. The query setting input section 462 is an interface for inputting query settings indicating an upper limit for the number of queries and a lower limit for the service relationship level as query conditions. The excluded service selection section 463 is an interface for inputting excluded service providers, which are service providers to be excluded from the reference destinations for contract queries, as query conditions. The service relationship level is the degree of relationship between the deceased and the service. More specifically, it is information indicating, in numerical form, the possibility that the deceased had contracted the service. A detailed description of this will be provided later. The touchpoint company terminal 110 transmits an inquiry request including the input query conditions (query settings and excluded services) to the contract inquiry system 200. Note that input of the query conditions is not required.

[0038] Returning to the explanation of the contract inquiry process in Fig. 3, when the inquiry condition creation unit 212 receives an inquiry request, it determines whether or not the inquiry request includes inquiry conditions (step S104). If the inquiry conditions are not included (step S104: No), the following steps S105 and S106 are skipped. Note that if the inquiry conditions are determined according to the detection tendency, there is no need to prompt the user 2 or the like to input the inquiry conditions for the contract inquiry, and the inquiry condition may be automatically set by the inquiry tendency calculation unit 214 from the detection tendency.

[0039] If the reference condition is included (step S104: Yes), the service relationship degree calculation unit 213 executes a service relationship degree calculation process (see FIG. 11) for calculating the service relationship degree for each service provider (step S105).

[0040] FIG. 11 is a flowchart illustrating an example of the service relationship degree calculation process.

[0041] In the service relationship degree calculation process, the service relationship degree calculation unit 213 generates an excluded inquiry destination list indicating excluded service providers included in the inquiry request (step S301).

[0042] The service relationship degree calculation unit 213 uses the excluded reference list to select service providers from the service providers excluding the excluded service providers included in the reference request as target service providers, which are service providers to be used for calculating the service relationship degree (step S302).

[0043] The service relationship degree calculation unit 213 calculates the service relationship degree between the result data relating to the results of past contract inquiries, the attribute information data of the deceased, and the service relationship degree between the deceased and the service of the target business. (Step S303) Note that a service provider and the service of that service provider are associated with each other in advance, and one service provider may provide multiple services.

[0044] The performance data includes service relationship degree analysis result data obtained by analyzing the service relationship degree from the performance of contract inquiries. In this embodiment, the service relationship degree is calculated using at least one of logistic regression analysis and association analysis.

[0045] FIG. 12 is a diagram showing an example of service relationship degree analysis result data. FIG. 12 shows service relationship degree relational equation data 500, which indicates a regression equation when logistic regression analysis is used, with the presence or absence of a service contract as the objective variable and the attributes of the deceased as the explanatory variables, as the service relationship degree analysis result data. The service relationship degree relational equation data 500 includes fields 501 to 504. Field 501 stores a coefficient ID that identifies the coefficient of the regression equation. Field 502 stores a service ID that identifies the service corresponding to the objective variable. Field 503 stores the item ID of the attribute that is the explanatory variable. Field 504 stores the value of the coefficient.

[0046] Fig. 13 is a diagram showing another example of service relationship degree analysis result data. Fig. 13 shows service relationship degree score data 510 and a condition part list 520 when association analysis is used as the service relationship degree analysis result data. In this association analysis, the presence or absence of a service contract is the conclusion part, and the combination of the attributes of the deceased is the condition part.

[0047] The service relationship score data 510 includes fields 511 to 514. Field 511 stores a score ID that identifies a score (service relationship score) that is a service relationship. Field 512 stores a service ID that identifies a service provider. Field 513 stores a condition part list ID that identifies a condition part list that is a combination of attributes corresponding to the score. Field 514 stores a coefficient value.

[0048] The condition part list 520 includes fields 521 to 523. The field 521 stores a condition part list ID. The field 522 stores an attribute item ID. The field 523 stores an attribute value.

[0049] Returning to the explanation of the service relationship degree calculation process in Fig. 11, after calculating the service relationship degrees related to the selected target businesses, the service relationship degree calculation unit 213 determines whether or not all target businesses have been selected (step S304). If all target businesses have not been selected (step S304: No), the service relationship degree calculation unit 213 returns to the processing of step S302.

[0050] If all target businesses are selected (step S304: Yes), the service relationship degree calculation unit 213 generates service relationship degree data indicating the calculated service relationship degree with each service, records it in the memory 202 (step S305), and terminates the service relationship degree calculation process.

[0051] Returning to the description of the contract inquiry process in Fig. 3, when the service relationship degree calculation process is completed, the inquiry condition creation unit 212 executes an information collaboration destination list creation process (Fig. 14) for generating inquiry condition data and an information collaboration destination list (step S106).

[0052] Fig. 14 is a flowchart illustrating an example of the information collaboration destination list creation process, and Fig. 15 is a diagram illustrating an example of the information collaboration destination list creation process.

[0053] In the information collaboration destination list creation process, the query condition creation unit 212 acquires an operator list, which is a list of service operators, from the memory 202 (step S401). The operator list includes, for example, a field 531 for storing an operator ID that identifies the service operator, and a field 532 for storing an operator name that is the name of the service operator, as in operator list 530 shown in Fig. 15 .

[0054] The query condition creation unit 212 determines whether or not an exclusion query destination list is recorded in the memory 202 (step S402). The exclusion query destination list includes, for example, a field 541 for storing a query condition ID for identifying a query condition, and a field 542 for storing a provider ID for identifying an excluded service provider, like an exclusion query destination list 540 shown in Fig. 15 .

[0055] If an exclusion reference destination list is recorded (step S402: Yes), the query condition creation unit 212 excludes the excluded service providers indicated in the exclusion reference destination list from the business list (step S403). For example, the query condition creation unit 212 deletes from the business list the business IDs that identify the excluded service providers in the exclusion reference destination list. Note that if an exclusion reference destination list is not recorded (step S402: No), the processing of step S403 is skipped.

[0056] Based on the service relationship degree data and the lower limit value of the service relationship degree included in the inquiry request, the inquiry condition creation unit 212 excludes low-relationship providers, which are service providers with a service relationship degree below this lower limit, from the list of providers excluding the excluded service providers (step S404). Then, the inquiry condition creation unit 212 sets the list of providers excluding the low-relationship providers as an information collaboration destination list that specifies the inquiry destination, and records information collaboration destination list data indicating the information collaboration destination list in the memory 202 (step S405). As a result, the information collaboration destination list shows only highly-relationship providers with a service relationship degree equal to or greater than the lower limit value, and the services provided by these highly-relationship providers become the services to be actually queried for contract inquiries. For example, the information collaboration destination list, as shown in the information collaboration destination list 550 in FIG. 15 , includes a field 551 that stores an information collaboration destination list ID that identifies the information collaboration destination list, a field 552 that stores a provider ID that identifies a highly-relationship provider, and a field 553 that stores an inquiry degree. The inquiry degree will be described later.

[0057] Thereafter, the query condition creating unit 212 creates query condition data indicating the correspondence between the query condition and the information collaboration destination list (step S406), and ends the information collaboration destination list creating process.

[0058] Fig. 16 is a diagram showing an example of query condition data. Query condition data 560 shown in Fig. 16 includes fields 561 to 564. Field 561 stores a query condition ID. Field 562 stores an upper limit value for the number of queries. Field 563 stores an information collaboration destination list ID. Field 564 stores a lower limit value for the service relationship degree.

[0059] Returning to the explanation of the contract inquiry process in Fig. 3, when the information collaboration destination list creation process is completed, the contract inquiry unit 211 executes a contract inquiry process to make a contract inquiry to the contract management system 120 based on the inquiry personal information data, the inquiry condition data, and the information collaboration destination list (step S107).

[0060] FIG. 17 is a flowchart illustrating an example of the contract inquiry process.

[0061] In the contract inquiry process, the contract inquiry unit 211 sends an inquiry request including the deceased's personal information data for inquiry to each of the contract management systems 120 corresponding to each service provider indicated in the information sharing destination list (step S501).

[0062] When each contract management system 120 receives an inquiry request, it uses the inquiry personal information included in the inquiry request to perform a confirmation process to confirm whether the deceased is a subscriber of its company's service, and returns the confirmation result to the contract inquiry system 200 as a contract inquiry result, which is the inquiry result of the contract inquiry (step S502). The specific method of the confirmation process is not particularly limited, and it may be performed automatically by the contract management system 120 or manually by a person in charge of the service provider. Furthermore, if personal information that can identify the subscriber but is not included in the inquiry personal information (for example, an email address, telephone number, account number, or personal identification number (My Number)) is discovered during the confirmation process, the contract inquiry result will include the discovered personal information as new personal information.

[0063] When the contract inquiry unit 211 of the contract inquiry system 200 receives the contract inquiry result (step S503), it records the contract inquiry result in the memory 202 as contract inquiry result data (step S504).

[0064] The contract inquiry unit 211 determines whether or not new personal information exists in the contract inquiry result data (step S505). If new personal information does not exist, the contract inquiry unit 211 ends the contract inquiry process.

[0065] If new personal information exists, the contract inquiry unit 211 updates the inquiry personal information data based on the new personal information (step S506). For example, the contract inquiry unit 211 adds the new personal information to the inquiry personal information data.

[0066] Then, the contract inquiry unit 211 updates the information collaboration partner list by excluding the service provider with which the contract has been detected from the information collaboration partner list (step S507).

[0067] Thereafter, the contract reference unit 211 determines whether or not a service provider (information contact point) exists (remains) in the information collaboration destination list (step S508).

[0068] If there are any remaining service providers (step S508: Yes), the contract inquiry unit 211 determines whether the end condition based on the inquiry condition is satisfied (step S509). The end condition may be, for example, that the number of inquiries has reached its upper limit.

[0069] If there are no service providers remaining (step S508: No) or if the termination conditions are met (step S509: Yes), the contract inquiry process ends. If the termination conditions are not met (step S509: No), the process returns to step S501.

[0070] In the above contract inquiry process, if new personal information exists, the contract inquiry is performed again using the new personal information, so there is a possibility that a new contract will be detected.

[0071] 18 is a diagram showing an example of contract inquiry result data 570. Contract inquiry result data 570 shown in FIG.

[0072] Field 571 stores a service ID that identifies the service. Field 572 stores a query condition ID. Field 573 stores the query number, which is the number of contract queries that detected the deceased's contract. Field 574 stores the query result, which indicates whether the deceased had a contract for the service. Field 575 stores the detected route. Field 576 stores the number of steps. Field 577 stores the items of new personal information. Field 578 stores the value of the new personal information.

[0073] Furthermore, the contract inquiry unit 211 transmits information showing a contract inquiry result screen based on the contract inquiry result data to the touchpoint company terminal 110 and displays the contract inquiry result screen on the touchpoint company terminal 110 .

[0074] Fig. 19 is a diagram showing an example of a contract inquiry result screen. The contract inquiry result screen 600 shown in Fig. 19 includes the number of contracts for which a contract inquiry was made 601, the number of detected contracts 602 which is the number of contracts (services) detected, new personal information 603 discovered in the contract inquiry, and contract information 604 indicating the detected contracts.

[0075] User 2 or the touchpoint company can request each service provider to carry out inheritance procedures based on the results of the contract inquiry, and in doing so, the document creation system 101 and procedure proxy system 102 of the platform 100 may be used. Also, the service provider may notify User 2 or the touchpoint company to urge them to carry out the inheritance procedures and start the procedures.

[0076] Furthermore, on the contract inquiry result screen 600, new personal information 603 allows user 2 to obtain information about the deceased that was not previously known, and for example, provides information that can serve as a clue to detecting contracts with service providers that are not covered by the inherited assets.

[0077] Returning to the explanation of the contract inquiry process in Fig. 3, when the contract inquiry process is completed, the inquiry record analysis unit 215 executes an inquiry record analysis process that performs a detection trend analysis and a service relationship degree analysis in order to improve the accuracy of calculation of the detection trend and service relationship degree for the deceased who will be the subject of the contract inquiry from the next time onwards (step S108), and then terminates the process.

[0078] FIG. 20 is a flowchart illustrating an example of the inquiry performance analysis process.

[0079] In the inquiry performance analysis process, the inquiry performance analysis unit 215 processes personal information in the contract inquiry result data into attribute information and records it in the memory 202 as contract inquiry performance data (step S601).

[0080] The inquiry performance analysis unit 215 analyzes the detection trend for each attribute item based on the contract inquiry performance data (step S602). In this embodiment, the analysis of the detection trend is performed using multiple regression analysis. Specifically, the inquiry performance analysis unit 215 acquires a regression equation (relational equation) for multiple regression analysis using each item of the deceased's attribute information as an explanatory variable and detection items such as the number of contracts and the number of inquiries as an objective variable. Note that the method of analyzing the detection trend is not limited to multiple regression analysis as long as it can predict the detection trend.

[0081] The inquiry record analysis unit 215 records the analysis results as detection tendency analysis result data (detection tendency relational expression data) (step S603).

[0082] The inquiry performance analysis unit 215 uses all the contract inquiry performance data to analyze the attribute information and the service relationship degree of each service provider (step S604). In this embodiment, at least one of logistic regression analysis and association analysis is used for the analysis of the service relationship degree.

[0083] In the case of logistic regression analysis, the inquiry record analysis unit 215 acquires a relational equation using each item of the deceased's attribute information as an explanatory variable and the presence or absence of a contract with each service provider (probability of a contract existing) as the objective variable, and updates the service relationship degree relational equation data 315 with the constants of the relational equation and the coefficients of each item. In this case, the probability of a contract existing becomes the service relationship degree.

[0084] In the case of association analysis, the inquiry performance analysis unit 215 performs association analysis using a combination of the deceased's attribute information as the condition part and whether or not a service contract was made as the conclusion part. At this time, the inquiry performance analysis unit 215 adopts combinations whose reliability and lift value are above a certain level as the condition part. The inquiry performance analysis unit 215 stores the support level for each combination of the condition part as a service relationship degree in the service relationship degree score data, and records the condition part as a condition part list in the condition part list data. Note that if a combination of the condition parts already exists in the condition part list, the service relationship degree score data is stored.

[0085] When both logistic regression analysis and association analysis are used, the inquiry record analysis unit 215 calculates the service relationship degree as, for example, a statistical value (such as a maximum value or an average value) of the individual service relationship degrees obtained in each analysis. At this time, the individual service relationship degrees may be normalized to the same scale. Furthermore, the method of analyzing the service relationship degree is not limited to logistic regression analysis and association analysis.

[0086] As described above, according to this embodiment, the service relationship degree calculation unit 213 calculates the service relationship degree, which is the degree of relationship between the deceased and the service, for each service based on attribute information indicating the attributes of the deceased and inquiry record information indicating the record of past contract inquiries. The inquiry condition creation unit 212 selects a service to be queried, which is a service for which a contract inquiry is to be made, based on the service relationship degree. The contract inquiry unit 211 performs a contract inquiry for the service to be queried using personal information about the deceased. In this case, it is possible to perform a contract inquiry for a service that has a high degree of relationship with the deceased, thereby reducing the load and communication volume on the system. Therefore, it is possible to efficiently make inquiries about contract information.

[0087] Furthermore, in this embodiment, the service relationship degree is calculated using at least one of association analysis and logistic regression analysis, so that the service relationship degree can be calculated appropriately.

[0088] Furthermore, in this embodiment, when new personal information is detected by the contract inquiry, the contract inquiry unit 211 uses the new personal information to make a new contract inquiry for the inquiry target service for which no contract was detected by the contract inquiry, which increases the possibility of detecting a contract.

[0089] In this embodiment, the contract inquiry unit 211 repeats the contract inquiry until neither a service contract nor new personal information is detected by the contract inquiry, which increases the possibility of detecting a contract.

[0090] In this embodiment, a termination condition for terminating the contract inquiry, such as the number of times the contract inquiry is repeated, is set according to the detection tendency. This makes it possible to efficiently inquire about contract information while increasing the possibility of detecting a contract.

[0091] Furthermore, in this embodiment, since the performance data is updated based on the results of the contract inquiry, it is possible to improve the efficiency of the inquiry of contract information.

[0092] The above-described embodiments of the present disclosure are merely illustrative examples of the present disclosure, and are not intended to limit the scope of the present disclosure to these embodiments alone. Those skilled in the art may implement the present disclosure in various other forms without departing from the scope of the present disclosure.

[0093] For example, in the above embodiment, the service provider is limited to a service provider that provides services related to inherited assets, but the industry and business type of the service provider are not limited to this example. The present disclosure can also be applied to support contract procedures other than inheritance, such as canceling a subscription service or deleting an account. [Explanation of symbols]

[0094] 1: Information processing system 100: Platform 101: Document creation system 102: Procedure agent system 110: Touch point company terminal 120: Contract management system 200: Contract inquiry system 201: Computer 202: Memory 203: Processor 204: Network interface 205: Auxiliary storage device 211: Contract inquiry unit 212: Inquiry condition creation unit 213: Service relationship degree calculation unit 214: Inquiry tendency calculation unit 215: Inquiry performance analysis unit

Claims

1. A contract inquiry system for making a contract inquiry, which is an inquiry into contract information for each service provided by each of a plurality of service providers, comprising: a calculation unit that calculates, for each service, a service relationship degree that is a relationship degree between the target person and the service based on attribute information that indicates the attributes of the target person who is the subject of the contract inquiry and inquiry performance information related to the performance of the past contract inquiry; a selection unit that selects a reference target service, which is the service for which the contract inquiry is to be made, based on the service relationship degree; A contract inquiry system having an inquiry unit that uses personal information about the subject to make the contract inquiry for the service being inquired about.

2. The contract inquiry system according to claim 1 , wherein the calculation unit calculates the service relationship degree using association analysis in which the presence or absence of a contract for the service is a conclusion part and the combination of the attributes is a condition part.

3. The contract inquiry system according to claim 1 , wherein the calculation unit calculates the service relationship degree using logistic regression analysis in which the presence or absence of a contract for the service is used as a dependent variable and the attribute is used as an explanatory variable.

4. The contract inquiry system of claim 1, wherein when new personal information about the subject is detected through the contract inquiry, the inquiry unit uses the new personal information to conduct a new contract inquiry for the inquired service for which no contract was detected through the contract inquiry.

5. The contract inquiry system according to claim 4 , wherein the inquiry unit repeats the contract inquiry until the contract inquiry does not detect both the contract for the service and the new personal information.

6. a prediction unit that predicts a detection tendency, which is a tendency to detect the contract, based on the attribute information and the inquiry record information; a setting unit that sets a termination condition for terminating the contract inquiry in accordance with the detection tendency, The contract inquiry system according to claim 4 , wherein the inquiry unit repeats the contract inquiry until the termination condition is satisfied.

7. The contract inquiry system according to claim 6 , wherein the detection tendency is at least one of the number of times the contract inquiry is repeated and the number of contracts detected.

8. The contract inquiry system according to claim 6 , wherein the setting unit predicts the detection tendency using multiple regression analysis with the detection tendency as a response variable and the attribute as an explanatory variable.

9. 2. The contract inquiry system according to claim 1, further comprising an update unit that updates the inquiry performance information based on the result of the contract inquiry.

10. A contract inquiry method using a contract inquiry system that performs contract inquiry, which is an inquiry into contract information for each service provided by each of a plurality of service providers, comprising: calculating a service relationship level, which is the degree of relationship between the target person and the service, for each service based on attribute information indicating the attributes of the target person who is the subject of the contract inquiry and inquiry performance information relating to the performance of the past contract inquiry; selecting a reference target service, which is the service for which the contract inquiry is to be made, based on the service relationship degree; A contract inquiry method for making the contract inquiry for the service being inquired about using personal information about the subject.

Images