JP2015111451A - Service support device - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a system for supporting provision of service for object persons registered beforehand by a contractor according to contract contents when the contractor dies.SOLUTION: A contractor confirmation part 50 of a service support device 10 notifies the contractor of an existence confirmation message and receives a reply indicating existence from the contractor. When there is no reply from the contractor, an alarm part 52 instructs a cooperator registered beforehand by the contractor to inquire life and death of the contractor. When the death of the contractor is confirmed, a service instruction part 56 instructs provision of service to object persons. A related person registration part 48 receives registration of the object persons and the cooperator by the contractor, and at the time, the cooperator can be registered from among the object persons.

Description

  The present invention relates to a data processing technique, and more particularly, to an apparatus that supports provision of a service related to human death.

  In March of this year, there was an unprecedented disaster called the Great East Japan Earthquake. Nearly 20,000 lives were lost in a momentary tragedy. Most of us, except the elderly, usually live without being aware of death. It is an event that overturns such consciousness.

  How to deal with sudden death You must consider not only your own problems, but also the remaining family and related parties. Perhaps the healthier people who worked harder witnessed the threat of the earthquake and thought about this.

  Of course, there is a system called life insurance. However, this is a monetary compensation and does not heal the wounds of those who remain. The first thing that the survivors of the earthquake disaster return to their homes in the devastated area is a photograph of their deceased family. Memories cannot be replaced by money.

  People often regret that they could not meet when they died. Whether you can hear the last word is a big problem for those who are left behind. The last word is the aggregation of the life of a whispering person in the relationship with the person to whom the word is given, and that can gently close the relationship between the two. Because of its completeness, those who are left will step into the sorrow that will gradually ease.

  There is also a mechanism called a will (see Patent Document 1 for an electronic one). However, in general, wills often have legal meanings, such as property distribution, and are unlikely to be words of heart that you want to listen to in the last days.

JP-A-2005-115406

  The present inventor felt the necessity of creating a mechanism for a healthy person to make a thorough preparation on a daily basis upon sudden death that anyone can visit. In addition, a mechanism is needed to maximize the healing of those who remain. An object of the present invention is to provide a system that can go further than life insurance and wills and realize perfection and mental care based on IT technology.

  In order to solve the above-described problems, a service support apparatus according to an aspect of the present invention is an apparatus that supports provision of a service to a target person registered in advance by a contractor according to contract contents when the contractor dies. The contractor confirming section that notifies the contractor of the existence confirmation message and receives a reply from the contractor that it is alive, and if there is no reply from the contractor, the contractor registered in advance A warning section for instructing cooperators to inquire about the life and death of the contractor, an instruction section for instructing provision of services if the contractor's death is confirmed, a registration section for registering the target person and cooperators, Is provided. The registration unit is configured to be able to register collaborators among the target persons.

  Another aspect of the present invention is also a service support apparatus. This device is a device that supports the provision of a service to a predetermined target person according to the contents of the contract when the contractor dies, and a message receiving unit that receives a message created by the contractor addressed to the target person from the contractor And a message provider that provides the subject with encrypted data obtained by encrypting the message, and if the contractor's death is confirmed, the subject is provided with a key for decrypting the encrypted data. Enter the message created by the contractor into the one-way function so that the user can view the message after decrypting the encrypted data and the decryption key provider that can confirm that the message that decrypted the encrypted data has not been tampered with And a confirmation data providing unit for providing the result data to the target person.

  It should be noted that any combination of the above-described components, and the present invention expressed by a method, system, recording medium, and computer program are also effective as an aspect of the present invention.

  According to the present invention, it is possible to realize a mechanism in which a user prepares for his own death.

It is a figure which shows the structure of an ending service system. It is a block diagram which shows the function structure of the service assistance apparatus of FIG. It is a figure which shows the structure of the data stored in the service master of FIG. It is a figure which shows the structure of the data stored in the contractor information holding part of FIG. It is a figure which shows the structure of the data stored in the subject information holding | maintenance part of FIG. It is a figure which shows the structure of the data stored in the cooperator information holding part of FIG. It is a figure which shows the structure of the data stored in the document form master of FIG. It is a figure which shows the structure of the data stored in the message holding | maintenance part of FIG. It is a figure which shows the structure of the data stored in the funeral plan master of FIG. It is a figure which shows the structure of the data stored in the funeral information holding part of FIG. It is a figure which shows an example of a related person registration page. It is a block diagram which shows the detailed functional structure of the will support part of FIG. It is a figure which shows an example of a message preparation page. It is a figure which shows an example of a message preparation page. It is a figure which shows an example of a message preparation page. It is a figure which shows an example of a message preparation page. It is a block diagram which shows the detailed functional structure of the funeral support part of FIG. It is a flowchart which shows operation | movement of a service assistance apparatus. It is a flowchart which shows operation | movement of a service assistance apparatus. It is a flowchart which shows operation | movement of a service assistance apparatus. It is a flowchart which shows operation | movement of a service assistance apparatus. It is a flowchart which shows operation | movement of a service assistance apparatus.

  In the present embodiment, a service support apparatus is proposed that provides a user with various services related to the death of a person (hereinafter collectively referred to as an “ending service”). The main target person to whom this service support apparatus provides services is a healthy person who can use the computer terminal by himself, in other words, a person who thinks that he is healthy and far from death. The service support apparatus allows an event related to the death of the user to be designed in advance while the user is healthy, and supports the event being realized according to the design after the user's death. The service support apparatus according to the embodiment mainly includes the following two technical elements.

Technical element 1: It accurately detects that a user has died, and supports execution of an ending service designated in advance by the user.
Technical element 2: When a user dies, the related person can confirm the message that the user left in advance, and the related person can confirm that the content of the message is not falsified. To. The message may be text, sound, an image, a moving image, and digital data obtained by appropriately combining them, and expresses what the user wants to convey to the parties concerned.

  FIG. 1 shows the configuration of an ending service system. The ending service system 100 is collectively referred to as the service support device 10, the contractor terminal 12, the target person terminal 14 a, the target person terminal 14 b, the target person terminal 14 c, and the funeral company terminal 16. A funeral company terminal 16a and a funeral company terminal 16b are provided. These devices are connected via a communication network 18 including a LAN, a WAN, the Internet, and the like.

  The service support apparatus 10 is an information processing apparatus that includes the above-described two technical elements and has a provider of an ending service (hereinafter also referred to as “service provider”). The service support apparatus 10 has a function as a web server, and provides and displays a web page related to the ending service to the contractor terminal 12, the target person terminal 14, and the funeral company terminal 16.

  The contractor terminal 12, the target person terminal 14, and the funeral company terminal 16 are information processing terminals that function as web clients, and may be stationary or portable. As an example of the former, a desktop PC may be used, and as an example of the latter, a mobile phone equipped with a web browser, a smartphone, a tablet terminal, or the like may be used.

  The contractor terminal 12 is an information processing apparatus operated by a user who contracts with a service provider (hereinafter referred to as “contractor”) to execute an ending service when he / she dies. The target person terminal 14 is an information processing apparatus operated by a user (hereinafter referred to as “target person”) designated by a contractor as a ending service provider. The funeral company terminal 16 is an information processing apparatus possessed by a funeral company associated with a service provider.

  FIG. 2 is a block diagram showing a functional configuration of the service support apparatus 10 of FIG. The service support apparatus 10 includes a data holding unit 20 that is a storage area for holding various data, and a control unit 40 that executes various data processing and communication processing. In addition, since the function as a web server is well-known, the following description is abbreviate | omitted.

  Each block shown in the block diagram of the present specification can be realized in terms of hardware by an element such as a CPU of a computer or a mechanical device, and in terms of software, it can be realized by a computer program or the like. The functional block realized by those cooperation is drawn. Therefore, those skilled in the art will understand that these functional blocks can be realized in various forms by a combination of hardware and software. For example, the data holding unit 20 in FIG. 2 may be realized by a storage or main memory of the service support apparatus 10. The control unit 40 may be stored in a recording medium as a computer program and installed in the storage of the service support apparatus 10. When the program is activated, the program modules corresponding to the functional blocks of the control unit 40 are read into the main memory of the service support apparatus 10 and executed by the CPU, whereby the functions of the control unit 40 are performed. It may be realized.

  The data holding unit 20 includes a service master 22, a contractor information holding unit 24, a target person information holding unit 26, a collaborator information holding unit 28, a document form master 30, a message holding unit 32, and a funeral plan master. 34 and a funeral information holding unit 36.

  FIG. 3 shows a configuration of data stored in the service master 22. The service master 22 holds the definition information of each of a plurality of types of ending services as “service master information”. In the service master information, service ID, service name, service details, service implementation time, and price are associated. Of these, the service implementation time indicates the period from the death of the contractor to the implementation of the ending service. In the embodiment, the ending service is provided to the target person on the condition that the number of days indicated by the service implementation time has elapsed since the contractor died. It is assumed that the date of counting that the contractor died is the death date of the contractor notified to the service support apparatus 10 by a cooperator described later.

  FIG. 4 shows a configuration of data stored in the contractor information holding unit 24. The contractor information holding unit 24 holds information on each of a plurality of contractors as “contractor information”. In the contractor information, the contractor ID, the contractor name, the contractor contact information, the service ID, the confirmation date, and the death date are associated with each other. Among these, at least the mail address of the contractor terminal 12 is set as the contractor contact information. As the service ID, the ID of the ending service selected by the contractor from among a plurality of types of ending services presented to the contractor by the service support apparatus 10 is set. In other words, the ID of the ending service contracted by the contractor to be provided to the target person after his / her death is set. As the confirmation date, the latest date when the existence of the contractor is confirmed in the service support apparatus 10 is set. Further, the death date of the contractor confirmed in the service support apparatus 10, specifically, the death date of the contractor notified to the service support apparatus 10 by the cooperator described later is set as the death date.

  The contractor ID, contractor name, and contractor contact information in FIG. 4 are the time when the contractor is registered in the service provider, and the specific ending service may be set when not selected. For example, it may be set manually by the service provider or automatically by the service support apparatus 10 based on the contents of the contract conclusion document with the service provider described by the contractor. In addition, the service support apparatus 10 may further include a contractor registration unit that accepts online registration (sign-up) of contractors. The contractor registration unit provides a contractor information input page to the user terminal (ie, contractor terminal 12), and stores the contractor information in the contractor information holding unit 24 when the registration button is selected on the page. By doing so, the user may be registered as a contractor.

  FIG. 5 shows a configuration of data stored in the target person information holding unit 26. The target person information holding unit 26 holds information regarding each of a plurality of target persons as “target person information”. In the target person information, the target person ID, the target person name, the target person contact information, the contractor ID, the service ID, and the confirmation date are associated with each other. Among these, at least the mail address of the subject terminal 14 is set as the subject contact information. Further, the contractor ID that designates the target person is set as the contractor ID. The service ID is set by the contractor and the ID of the ending service provided to the target person. As the confirmation date, the latest date when the existence of the target person is confirmed in the service support apparatus 10 is set.

  FIG. 6 shows a configuration of data stored in the cooperator information holding unit 28. The collaborator information holding unit 28 stores information on a specific target person (hereinafter also referred to as “cooperator”) designated in advance by the contractor from among one or more target persons as users who cooperate in confirming the existence of the contractor. It is held as "cooperator information". As will be described later, the collaborator is a user who cooperates in the confirmation of the existence of the contractor among the target persons. In the collaborator information, a collaborator ID, a contractor ID, and a collaborator contact address are associated. Among these, as the contractor ID, the ID of the contractor specifying the collaborator is set. Further, at least the mail address of the target person terminal 14 of the collaborator is set as the collaborator contact address.

  FIG. 7 shows the structure of data stored in the document form master 30. The document form master 30 holds a typical message template from the contractor to the subject. In the embodiment, a plurality of types of selection items for specifying the format of a will to be created by a contractor and a plurality of types of document forms as a template of a will are stored. The document form master 30 holds a plurality of types of selection items and a plurality of types of document forms, grouped into a plurality of hierarchies. For example, the major class “property for inheritance” includes the middle class “standard format” and “format for designating inheritance”. The middle class “standard form” includes “real estate inheritance form”, “deposit and saving inheritance form” and “stock inheritance form” as templates of wills. On the other hand, the middle classification “form for designating inheritance” includes “self-designation form” and “third-party consignment form” as templates of wills.

  FIG. 8 shows a configuration of data stored in the message holding unit 32. The message holding unit 32 holds information regarding a message to be transmitted from the contractor to the target person as “message information”. In the message information, a message ID, a contractor ID, a target person ID, an encrypted message, a decryption key, and a hash value are associated with each other. Among these, the ID of the contractor who created the message is set as the contractor ID, and the ID of the target person who is the destination of the message is set as the target person ID. Further, data obtained by encrypting the plaintext message of the contractor is set as the encrypted message, and key information for decrypting the encrypted message is set as the decryption key. A hash value generated from the plaintext message of the contractor is set as the hash value. In order to improve security, the service support apparatus 10 does not permanently hold a message received from a contractor in a plain text state.

  FIG. 9 shows the structure of data stored in the funeral plan master 34. The funeral plan master 34 holds funeral plans proposed by each of a plurality of funeral providers, in other words, definition information of funeral plans that can be selected by the contractor. In this definition information, funeral plan ID, funeral company information, and plan details are associated. Of these, at least the contact information of the funeral company, for example, the mail address of the funeral company terminal 16 is set as the funeral company information. The plan details are information indicating the detailed contents of the funeral plan, and include, for example, the funeral scale, the venue information, the contents of the dinner, the contents of the returned goods, the price (total amount and breakdown) of the funeral.

  FIG. 10 shows a configuration of data stored in the funeral information holding unit 36. The funeral information holding unit 36 holds information related to the funeral itself designed by the contractor as “funeral information”. In the funeral information, the contractor ID, the funeral plan ID, the mourner information, and the funeral details are associated. Among these, as the mourner information, the contact address of the mourner, for example, the mail address of the mourner's target terminal 14 is set. In addition, funeral details include information on the desired attendees, designation of religion, information on desired rituals, information on desired production, information on desired cemeteries and graves, and the like.

  Returning to FIG. 2, the control unit 40 includes a service execution unit 42, a party registration unit 48, a contractor confirmation unit 50, a warning unit 52, a collaborator confirmation unit 54, a service instruction unit 56, and a target person. A confirmation unit 58, a contractor notification unit 60, and a service selection support unit 62 are provided.

  Although not specifically mentioned below, when the contractor terminal 12 accesses the service support apparatus 10, the service support apparatus 10 requests the contractor terminal 12 to log in and requests the input of the contractor ID. As a result, the service support apparatus 10 grasps the contractor ID of the access source contractor terminal 12. Further, in the following, for simplification of explanation, processing for one contractor will be described, but actually, processing for each of a plurality of contractors is executed sequentially or in parallel.

  The service execution unit 42 executes processing related to a plurality of types of ending services, for example, processing for providing an ending service specified in advance by the contractor to a target person specified in advance by the contractor. The service execution unit 42 includes a will support unit 44 that executes processing of a will support service and a funeral support unit 46 that executes processing of a funeral support service. Details of the will support unit 44 and the funeral support unit 46 will be described later.

  The service execution unit 42 may execute a part of a series of processes of each ending service while the contractor is alive. Then, the remaining process, in other words, the process to be executed after the contractor's death is executed in response to an instruction from the service instruction unit 56 described later.

  The service selection support unit 62 provides the contractor terminal 12 with data of a web page (hereinafter also referred to as “service selection page”) that presents a plurality of types of ending services executed by the service execution unit 42. It can be said that the service selection page is a web page for allowing a contractor to select one or more ending services from a plurality of types of ending services. Specifically, the service selection support unit 62 transmits a service selection page in which the service master information held in the service master 22 is set as a list of ending services to the contractor terminal 12 for display.

  In addition, the service selection support unit 62 acquires information indicating the ending service selected by the contractor on the service selection page from the contractor terminal 12 and stores the service ID in the record of the contractor in the contractor information holding unit 24. Store. It can be said that the ending service selected by the contractor is a service contracted to be provided after the contractor's death between the contractor and the service provider.

  For example, some public services such as survivor pensions and private services such as life insurance should be processed within a specified period after the contractor's death. The contractor who wishes to send a message to the target person to instruct him / her to perform the procedure for receiving these services selects the will support service in which the value within the predetermined period is set as the service implementation time. There is a need to.

  The related party registration unit 48 transmits data of a web page (hereinafter referred to as “related party registration page”) for the contractor to register the target person and the collaborator to the contractor terminal 12 for display. FIG. 11 shows an example of a related person registration page. The related person registration page 102 includes a target person name field 104, a contact field 106, a service type field 108, a collaborator check box 110, and a registration button 112. The target person name field 104 is an input field for the target person name, and the contact address field 106 is an input field for the contact information of the target person including the mail address of the target person terminal 14.

  The service type field 108 is an input field for designating the type of ending service to be provided to the target person. The service type field 108 may be a drop-down list in which a contractor can select a specific service from the ending services with which the contractor has contracted. The collaborator check box 110 is a check box for designating a specific target person as a collaborator. In this embodiment, it is not possible to designate a third party who is not involved in the ending service as a collaborator, and it is necessary to select a collaborator from the target persons. For example, when a wife, a child, a father, a mother, a friend, a company colleague, or an attorney at law is designated as a target person, a wife, a child, or a friend can be designated as a collaborator.

  When the registration button 112 is selected on the related party registration page 102, the contractor terminal 12 transmits the target person information input on the related party registration page 102 to the service support apparatus 10. Upon receiving the target person information input on the related party registration page 102 from the contractor terminal 12, the related party registration unit 48 assigns a unique target person ID and refers to the contractor information holding unit 24 to make a contract. The ID of the ending service designated by the person is specified. Then, the target person information is stored in the target person information holding unit 26 in association with the contractor ID of the contractor terminal 12. In addition, the related party registration unit 48 further assigns a unique collaborator ID for the target person for which the collaborator check box 110 is checked, and the collaborator information holding unit 28 uses the target person information as the collaborator information. Store.

  Returning to FIG. 2, when the collaborator information holding unit 28 adds or updates the collaborator information, the collaborator confirmation unit 54 detects the fact. In this case, the collaborator confirmation unit 54 is designated as a target person to whom the ending service is provided for the collaborator target person terminal 14 to which the collaborator information has been added or updated, and is used to confirm the existence of the contractor. Send an email to the effect that you have been designated as a collaborator. In other words, the user selected as a cooperator by the contractor is notified of the fact and encouraged to cooperate in confirming the contractor's existence.

  The contractor confirmation unit 50 periodically transmits an e-mail for confirming the existence of the contractor (hereinafter also referred to as “survival confirmation mail”) to the contractor terminal 12. In the survival confirmation mail, for example, the contents for requesting a reply to the service support apparatus 10 when the contractor is alive are described. When the contractor confirmation unit 50 receives from the contractor terminal 12 a reply to the effect that the contractor is alive, more specifically, a reply email to the survival confirmation mail, the contractor information holding unit 24 Update the confirmation date to the current date. The current date is typically the date of the current date and time managed by the service support apparatus 10, and is a so-called system date.

  When the contractor confirmation unit 50 detects the elapse of a predetermined waiting period from the successful confirmation of the contractor's survival by the survival confirmation mail, the contractor confirmation unit 50 executes the contractor's survival confirmation again. For example, when it is detected that a predetermined number of days have elapsed from the confirmation date in the contractor information of the contractor information holding unit 24, a new survival confirmation mail is transmitted to the contractor terminal 12, and a reply from the contractor terminal 12 is again sent. The confirmation date in the contractor information holding unit 24 is received and updated again. It can be said that this waiting period is a cycle in which the survival confirmation should be repeated for one contractor, and can be said to be an interval from the previous survival confirmation to the next survival confirmation.

  The waiting period is determined as follows. That is, the contractor confirmation unit 50 refers to the contractor information holding unit 24 to identify one or more ending services for which the contractor has been contracted, and is defined for each ending service that has been contracted with reference to the service master 22. Identify when the service will be implemented. Then, the standby period is determined according to the shortest service implementation time (hereinafter also referred to as “reference time”) among the service implementation times defined for each contracted ending service. Specifically, the longer the reference period, the longer the standby period, and the shorter the reference period, the shorter the standby period. For example, the number of days obtained by subtracting 2 to 3 days from the number of days indicated by the reference time may be used as the number of standby days. If the contractor has contracted the will support service B and the inheritance support service B in FIG. 3, the reference time may be specified as 14 days specified in the will support service B, and the waiting time may be determined as 12 days. .

  The warning unit 52 determines whether a reply to the survival confirmation mail has been received from the contractor terminal 12 within a predetermined period after the survival confirmation email is transmitted to the contractor terminal 12 by the contractor confirmation unit 50. . This predetermined period may be a predetermined reply grace period such as several hours to several days. In addition, the warning unit 52 accepts a reply to the survival confirmation email within the time limit when the date obtained by adding the reference time to the confirmation date held in the contractor information holding unit 24 is equal to the current date. It may be determined that there was not. In this case, the difference between the reference time and the standby period becomes the reply grace period. When the warning unit 52 determines that the reply from the contractor terminal 12 has not been received in a predetermined period after the transmission of the survival confirmation mail, the warning unit 52 specifies the contractor ID and cooperates in executing the confirmation process to the collaborator. The person confirmation unit 54 is instructed.

  The collaborator confirmation unit 54 refers to the collaborator information holding unit 28 and specifies the collaborator information associated with the contractor ID designated by the instruction of the warning unit 52. The collaborator confirmation unit 54 transmits a survival confirmation email for confirming the existence of the contractor to the target person terminal 14. In this survival confirmation mail, if the contractor is alive, a message to that effect is requested, and if the contractor is dead, the contents to request the contractor's death date are described.

  The collaborator confirmation unit 54 updates the confirmation date in the contractor information holding unit 24 to the current date when the reply content from the collaborator target person terminal 14 indicates the existence of the contractor. . On the other hand, when the reply content from the partner terminal 14 of the collaborator indicates the death of the contractor, that is, when the description of the contractor's death date is detected in the reply content, the collaborator confirmation unit 54 The death date is recorded in the contractor information of the contractor information holding unit 24.

  When a plurality of cooperators are specified by the contractor, the cooperator confirmation unit 54 transmits a survival confirmation mail to each of the target person terminals 14 of the plurality of cooperators. And the cooperator confirmation part 54 receives a reply from the target person terminal 14 of each of a plurality of cooperators, and determines the life or death of the contractor according to each reply content. Various algorithms can be considered for the life / death determination of the contractor when a plurality of cooperators are designated. For example, when the reply contents from all the collaborators match, the collaborator confirmation unit 54 may determine the contractor's life and death according to the reply contents. Further, when the reply contents from the majority of the collaborators match, the life or death of the contractor may be determined deterministically. In addition, when the reply contents from each cooperator are inconsistent (for example, one indicates the existence of the contractor and the other indicates the death of the contractor), again to the target terminal 14 of each of the cooperators. A survival confirmation email may be sent.

  In determining whether a contractor is alive or not, which algorithm is to be used may be appropriately determined by the designer in accordance with the character that the service support apparatus 10 should have. For example, when accuracy should be emphasized in the life / death determination of the contractor, the determination may be made deterministic when the reply contents from all the collaborators match. In addition, when it is important to determine whether the contractor is alive or not, if the response content from at least one collaborator indicates the contractor's death, the contractor may be determined to have died. Further, when both accuracy and speed should be achieved, the life and death of the contractor may be determined deterministically when the reply contents from the majority of the collaborators match.

  When the death date is set in the contractor information of the contractor information holding unit 24, the service instruction unit 56 specifies the service ID recorded in the contractor information in which the death date is set, and the contractor ID and the service ID Is notified to the service execution unit 42. Specifically, for each ending service contracted by a contractor whose death is confirmed, it is determined whether or not a date obtained by adding the service execution time to the death date has been reached. For example, for a contracted ending service, if it is determined that the current date is equal to the date obtained by adding the service execution time of the service to the death date, the service execution unit 42 is instructed to provide the service.

  The target person confirmation unit 58 is an e-mail for confirming that the target person can be contacted, in other words, an e-mail for confirming that the target person is alive and the target person information is correct (hereinafter referred to as “target person”). (Also referred to as “confirmation mail”) is periodically transmitted to the target person terminal 14. For example, the target person confirmation mail may be transmitted once every six months to one year. The target person confirmation unit 58 is a reply to the target person confirmation mail. When the target person confirmation mail is received from the target person terminal 14 as a reply that the target person confirmation mail has been normally received, the reception date is confirmed by the confirmation date of the target person information holding unit 26. Set to.

  The warning unit 52 receives a reply to the subject confirmation email from the subject terminal 14 within a predetermined period (for example, one week) after the subject confirmation email is transmitted to the subject terminal 14 by the subject confirmation unit 58. It is determined whether or not. If not received within the predetermined period, the warning unit 52 notifies the contractor notification unit 60 that the target person information should be updated by specifying the contractor ID.

  When notified by the warning unit 52 that the target person information should be updated, the contractor notification unit 60 refers to the contractor information holding unit 24 and is associated with the contractor ID specified by the warning unit 52. Identify contractor information. The contractor notifying unit 60 transmits an e-mail to the effect that the target person information should be updated to the contractor terminal 12 specified by the contractor contact information. The contractor who receives this e-mail updates the information of the target person and the collaborator on the related person registration screen.

  FIG. 12 is a block diagram showing a detailed functional configuration of the will support unit 44 of FIG. The will support unit 44 includes a message creation support unit 70, a message receiving unit 72, an encryption unit 74, a hash generation unit 76, a message providing unit 78, a hash providing unit 80, and a decryption key providing unit 82. .

  The message creation support unit 70 provides a contractor who has selected the will support service with a web page (hereinafter also referred to as a “message creation page”) for supporting creation of a message addressed to the subject in an interactive manner. . The message creation support unit 70 sequentially acquires a selection item for specifying the message type and a document form corresponding to the message type selected by the contractor from the document form master 30. And the message creation page which set those data is provided to the contractor terminal 12 sequentially.

  Fig.13 (a)-FIG.13 (d) show an example of a message preparation page. FIG. 13A shows a message creation page 120 for designating a message destination, that is, a target person in the will support service, as step 1. The target person name field 122 is an input field for designating a target person, and may be a drop-down list in which a specific target person can be selected from the target persons registered in advance by the contractor. When the next button 124 is selected by the contractor, a transition is made to the message creation page 120 of the next step.

  FIG. 13B shows a message creation page 120 for selecting a message type as step 2. With the radio button 126, a large classification of messages in the document form master 30 shown in FIG. 7 is displayed so as to be selectable. When the next button 124 is selected by the contractor, the screen transitions to the message creation page 120 of the next step, while when the back button 128 is selected, the screen transitions to the message creation page 120 of the previous step.

  FIG. 13C shows a message creation page 120 for selecting a message type at a more detailed level than Step 2 as Step 3. With the radio button 130, the middle classification of the message in the document form master 30 shown in FIG. 7 (here, the middle classification corresponding to the major classification “will for asset inheritance”) is displayed in a selectable manner. If the “Next” button 124 is selected while “standard format” is selected in the radio button 130, the “message real estate form”, “deposit and saving inheritance form”, “stock” are displayed as the message creation page in step 4. The “Inheritance form” selection screen appears.

  FIG.13 (d) has shown the message preparation page 120 as which the real estate inheritance form was displayed as step 5. FIG. This message creation page 120 displays a standard will template for the case where real estate is the main property. The contractor can create a message as a standard will by inputting information in each input field 132. When a registration button (not shown) is selected on the message creation page 120 in FIG. 10, the contractor terminal 12 uses the target person's information specified in step 1 and the input data to the real estate inheritance form as the target person. Is transmitted to the service support apparatus 10 as a message.

  Returning to FIG. 12, the message receiving unit 72 receives a message to the target person transmitted from the contractor terminal 12 and assigns a unique message ID. The encryption unit 74 encrypts the plaintext message received by the message reception unit 72. In this embodiment, the message is encrypted by a common key method, and the encryption unit 74 determines unique data for each message to be encrypted as a common key. For example, the common key may be determined based on the combination of the target person ID and the date information. The encryption unit 74 associates the message ID with the ID of the contractor who is the creator of the message and the ID of the subject who is the destination of the message, and the encrypted data of the message and its decryption key (that is, the above-mentioned common key). ) Is stored in the message holding unit 32.

  The hash generation unit 76 inputs the plaintext message received by the message reception unit 72 to a predetermined hash function such as SHA-1, and acquires the hash value. The hash generation unit 76 stores the hash value of the message in the message holding unit 32 in association with the message information created by the encryption unit 74.

  When the message providing unit 78 detects that the encrypted message is newly stored in the message holding unit 32, the message providing unit 78 provides the encrypted message to the target person of the will support service. Specifically, an e-mail attached with encrypted data of a message addressed to the target person is transmitted to the target person terminal 14 specified by the ID of the target person specified on the message creation page. When the hash providing unit 80 detects that the hash value is newly stored in the message holding unit 32, the hash providing unit 80 provides the hash value information to the target person of the will support service. Specifically, an e-mail attached with data indicating a hash value of a message addressed to the target person is transmitted to the target person terminal 14 specified by the ID of the target person specified on the message creation page. The encrypted message and the hash value data may be transmitted by a single electronic mail.

  The decryption key providing unit 82 corresponds to the contractor's ID when the service support device 10 confirms the death of the contractor, specifically, when the service instruction unit 56 instructs the provision of the will support service. The attached subject ID and decryption key are acquired from the message holding unit 32. The decryption key providing unit 82 transmits an e-mail attached with decryption key data to the target person terminal 14 specified by the target person ID. Thereby, in the subject terminal 14, the encrypted message previously provided by the message providing unit 78 can be decrypted, and the subject can confirm the message left by the contractor.

  FIG. 14 is a block diagram showing a detailed functional configuration of the funeral support unit 46 of FIG. The funeral support unit 46 includes a funeral plan registration unit 90, a funeral plan presentation unit 92, a funeral information reception unit 94, and a funeral information notification unit 96.

  The funeral plan registration unit 90 receives a funeral plan registration request including the detailed contents of the funeral plan from the funeral company terminal 16 and assigns a unique funeral plan ID. Then, the funeral plan ID, the funeral company information specified by the funeral company terminal 16, and the detailed content of the funeral plan are stored in the funeral plan master 34 in association with each other.

  The funeral plan presentation unit 92 provides a web page (hereinafter also referred to as a “funeral support page”) for assisting a contractor who has contracted a funeral support service to determine the content of the funeral by the contractor himself / herself. provide. Specifically, funeral support page data including information on funeral plans registered in the funeral plan master 34 is transmitted to the contractor terminal 12 and displayed. This funeral support page includes a selection field for a funeral plan desired by the contractor, an input field for mourner information including contact information of the mourner, and an input field for funeral details described in the explanation of FIG.

  The funeral information reception unit 94 acquires the funeral information input to the funeral support page by the contractor from the contractor terminal 12 and stores it in the target person information holding unit 26. As described above with reference to FIG. 10, the funeral information includes the funeral plan selected by the contractor, the information of the mourner designated by the contractor, and the details of hope regarding the funeral contents (the above-mentioned funeral details).

  When the funeral information notifying unit 96 detects that new funeral information is stored in the funeral information holding unit 36, the contractor's information is sent to the funeral company terminal 16 of the funeral company that has proposed the funeral plan selected by the contractor. Notify funeral information including. Moreover, the funeral information reception part 94 notifies funeral information including the contractor's information to the mourner's target terminal 14 designated by the contractor. It should be noted that the funeral information reception unit 94 also confirms that the contractor's death is confirmed in the service support device 10, specifically, when the service instruction unit 56 instructs the provision of the will support service, also at the funeral company terminal 16. The funeral information may be notified to the mourner's target terminal 14.

The operation of the service support apparatus 10 having the above configuration will be described below.
15 to 19 are flowcharts showing the operation of the service support apparatus 10. FIG. 15 shows an operation related to the ending service contract by the contractor and the registration of the related parties by the contractor. A user who wants to prepare for his / her own death in advance, specifically, a user who wants to design the contents of an event that occurs after his / her death before his / her life registers his / her information (ie, contractor information) with the service provider. Thereby, this user is permitted to access the service support apparatus 10 through the contractor terminal 12 as a contractor.

  When the service selection support unit 62 receives a request for providing information on services that can be selected by the contractor from the contractor terminal 12 (Y in S10), the service selection support unit 62 displays the service selection page including the service master information stored in the service master 22. This is provided to the terminal 12 (S12). When it is designated on the service selection page that a contract is made for a specific ending service (Y in S14), the service selection support unit 62 stores information on the designated ending service in the contractor information (S16). Thus, an ending service to be provided to the target person after the contractor's death is set. If it is not specified in the service selection page that a specific ending service is contracted (N in S14), S16 is skipped, and if a request for providing information on services selectable by the contractor is not accepted (N in S10), S12 to S16 are skipped.

  When the related party registration unit 48 receives a request for providing a related party registration page from the contractor terminal 12, the related party registration unit 48 provides the related party registration page illustrated in FIG. 11 to the contractor terminal 12. The contractor inputs the information of the target person for each contracted ending service on the related party registration page, and further designates one or more collaborators from the target persons. When the related party registration unit 48 receives a request for registration of the related party specified on the related party registration page from the contractor terminal 12 (Y in S18), the target person information and the collaborator information holding unit of the target person information holding unit 26 28 collaborator information is updated (S20). When the collaborator is registered, the collaborator confirmation unit 54 notifies the collaborator's target terminal 14 that the collaborator is a target person of the ending service and designated as a collaborator for the contractor's survival confirmation. (S22). If the registration request of the person concerned is not accepted (N of S18), S20 and S22 are skipped.

  FIG. 16 shows an operation related to confirmation of the existence of the contractor. The operation in FIG. 6 is executed in parallel for each contractor who has contracted the ending service, in other words, for each record of contractor information for which one or more service IDs have been set in the contractor information holding unit 24. The contractor confirmation unit 50 determines the waiting period in the survival confirmation according to the service execution time set for the ending service for which the contractor has contracted (S30). When it is detected that the waiting period has elapsed from the date on which the contractor's existence was confirmed in the past (Y in S32), a survival confirmation email regarding the contractor is transmitted to the contractor terminal 12 (S34). The warning unit 52 determines whether or not a reply e-mail to the survival confirmation mail is received from the contractor terminal 12 and whether or not the reply content is a predetermined content indicating that the contractor is alive. Thus, it is determined whether or not the contractor is alive. When the warning unit 52 does not determine that the contractor is alive (N in S36), the collaborator confirmation unit 54 transmits a survival confirmation email regarding the contractor to the target terminal 14 of the collaborator (S38).

  The collaborator confirmation unit 54 determines whether the reply content from the collaborator's target terminal 14 with respect to the survival confirmation mail indicates the contractor's survival or the contractor's death. For example, if the death date of the contractor is described in the reply, it is determined that the contractor has died. When the cooperator confirmation unit 54 determines that the contractor has died (N in S40), the cooperator confirmation unit 54 records the death date of the contractor in the contractor information of the contractor information holding unit 24. The service instruction unit 56 stands by until the date determined by the service execution time for each ending service for which the contractor has contracted (N in S42). When it is detected that the date determined by the service implementation time has been reached (Y in S42), the service execution unit is instructed to execute the ending service (S44). When it is confirmed by the reply from the cooperator that the contractor is alive (Y in S40), S42 and S44 are skipped. Further, when it is confirmed by the reply from the contractor that the contractor is alive (Y in S36), S38 and subsequent steps are skipped. If the standby period has not elapsed since the date when the contractor's existence was confirmed in the past (N in S32), the process from S34 onward is skipped.

  As shown in FIG. 15 and FIG. 16, according to the service support apparatus 10 of the embodiment, it is necessary to select a collaborator who should cooperate with the confirmation of the existence of the contractor from the target persons to whom the ending service is provided. There is. It can be said that the target person is often a user who has a certain degree of connection with the contractor and grasps the state of the contractor. Therefore, the accuracy of the contractor's survival confirmation can be improved by setting the collaborators among the target persons.

  In addition, since the cooperator must correctly answer whether the contractor is alive or not, and is responsible for confirming the existence of the contractor, if the cooperator has no merit, it will be designated as a cooperator. It is also possible not to accept it. In the service support apparatus 10, by designating a collaborator from among persons who enjoy the service, it is easy to attach cooperation for confirming the existence of the contractor, in other words, giving an incentive to accept designation as a collaborator. Can do. Further, when a cooperator is designated by the contractor, the fact that the cooperator is designated as a cooperator can be notified in advance that the cooperator should cooperate in confirmation of the existence of the contractor in the future.

  Further, according to the service support apparatus 10, according to the service implementation time after the contractor's death, in other words, according to the period from the contractor's death until the service is provided to the target person, the contractor's survival confirmation is performed. The period of repeating (that is, the above-described waiting period) is determined. Specifically, a longer period is determined as the period from the contractor's death date to the service provision date to the subject is longer. Thereby, it becomes easy to suppress the survivor confirmation to the contractor, in other words, the survivor confirmation at a frequency that becomes a burden on the contractor, while observing the implementation time of the ending service previously presented to the contractor. In the embodiment, when the contractor contracts with a plurality of ending services, the period of the ending service presented to the contractor in advance is determined by determining the period according to the shortest service execution time among those services. Compliance to.

  FIG. 17 shows an operation related to the correctness check of the target person information. The operation shown in FIG. 11 is executed in parallel for each target person for providing the ending service, in other words, for each record of target person information in the target person information holding unit 26. When the target person confirmation unit 58 detects that a predetermined number of days have passed since the date on which the correctness of the target person information was confirmed in the past (Y in S50), the target person confirmation unit 58 transmits a target person confirmation mail to the target person terminal 14 (S52). When the warning unit 52 detects that there is no reply from the subject or that the reply content indicates an error in the subject information (N in S54), the contractor notifying unit 60 indicates that the subject information has an error, In addition, an e-mail requesting to update the target person information is transmitted to the target person terminal 14 (S56). When it is confirmed that the subject information is correct by the reply from the subject (Y in S54), S56 is skipped. Further, if the predetermined number of days has not elapsed since the date on which the correctness of the target person information was confirmed (N in S50), S52 and subsequent steps are skipped.

  As shown in FIG. 17, according to the service support apparatus 10 of the embodiment, the correctness of the target person information is periodically confirmed. The ending service is a long-lived service that can have an interval of several years to several tens of years after being contracted by the contractor until it is actually provided to the target, and the state of the target can also change over time. According to the service support apparatus 10, it is possible to support the contractor to appropriately review the target person information by reflecting the latest situation such as the change of the contact information of the target person.

  FIG. 18 shows operations related to a will support service. When the message creation support unit 70 of the will support unit 44 receives a message creation request from the contractor terminal 12 (Y in S60), the message creation support unit 70 provides the contractor terminal 12 with a message creation page for supporting the message creation. When the type of message is selected by the contractor (Y in S64), the message creation support unit 70 sequentially updates the display content of the message creation page according to the selection result, and finally the message A document form as a template is displayed (S66). If no message type is selected on the message creation page (N in S64), S66 is skipped. If no message creation request is accepted (N in S60), S62 to S66 are skipped. The contractor can also select the free description form shown in FIG. 7 as the message type. In that case, the contractor is not limited to the general will form, but the thought to the target person (for example, the last word in the final scene) Etc.) can be described freely. The contractor's message may be, for example, a word “Thank you, thank you always”.

  When the message reception unit 72 receives a message uploaded from the contractor terminal 12 (Y in S68), the encryption unit 74 encrypts the message (S70), and the hash generation unit 76 calculates the hash value of the message. (S72). Then, the message providing unit 78 provides the encrypted message to the subject terminal 14, and the hash providing unit 80 provides the hash value data to the subject terminal 14 (S74). When the contractor's death is confirmed and service execution is instructed by the service instruction unit 56 (Y in S76), the decryption key providing unit 82 provides the decryption key of the encrypted message to the target person terminal 14 (S78). . If there is no message upload from the contractor terminal 12 (N in S68), S70 to S74 are skipped, and if the existence of the contractor is confirmed (N in S76), S78 is skipped.

  As shown in FIG. 18, according to the service support apparatus 10 of the embodiment, the decryption key of the encrypted message is provided to the subject of the will support service on the condition that the contractor has died. Thereby, after the contractor's death, the target person can confirm the message left by the contractor. Further, the service support apparatus 10 provides the target person terminal 14 with hash data of the contractor's original message. After decrypting the encrypted message, the target person collates the hash data generated from the decrypted message with the hash data provided from the service support apparatus 10 and confirms their identity, so that the decrypted message is It can be confirmed that it has not been tampered with. In other words, the identity of the contractor's original message and the message provided to the subject can be guaranteed.

  Further, according to the service support apparatus 10, the type of a will that the contractor desires to create is specified in a message creation page in an interactive format, and a document form in a format that matches the type, that is, a standard will prepared in advance. Present the template to the contractor. This makes it easy for a contractor to create a will and helps to describe information necessary for a valid will.

  Further, according to the service support apparatus 10, a message in a free format that is not limited to a general will format can be provided to the subject as a contractor's message. By sending a compassionate message different from a general will to the subject, it is possible to provide a situation equivalent to listening to the final word even if the subject is not in the contractor's final place. Thereby, after the contractor's death, the grief of the remaining person can be relieved.

  In addition, according to the service support apparatus 10, unlike a general will that is widely disclosed to a plurality of parties related to the deceased or that is disclosed within the scope of the bereaved family, the contractor's message is specified by the contractor. It is only open to the target audience. Therefore, the contractor can leave a different message for each target person, and the message to each target person is kept secret from those other than the destination. In general, a contractor wants to disclose to a specific target person, but has a secret that the other party wants to keep secret, and the secret can be entrusted to the apparatus.

  In addition, when a person suddenly dies, for example, the person's chest deposit (or “smile”) may be buried without being noticed by anyone. Such a problem can be prevented if the service support apparatus 10 leaves a message in which the location is recorded in advance. That is, the contractor's message transmitted to the target person by the service support apparatus 10 is not only for transmitting the contractor's feelings about the target person, but also for transmitting notes such as “what is where” and “what do you want to do” It also has a function.

  In this connection, in the above embodiment, the template of the will is provided to the contractor. However, the document form master 30 of the service support apparatus 10 is a typical example such as the location of the chest deposit or the location of the chest stock. While the contractor is still alive, it is an information item that is concealed from others, and is an item that should be transmitted to the subject after the death, but various items that are assumed to be easily forgotten (hereinafter referred to as “memories item”). May also be maintained. Then, the message creation support unit 70 may display a text prompting to create a message for the memorandum item on the message creation page. Further, the document form master 30 may hold a document format (for example, a template for transfer of chest deposits, a template for transfer of chest stock certificates, etc.) for transmitting the memorandum item to the target person, and the message creation support unit 70 stores the memorandum item. A document format corresponding to the selection item of the contractor from among them may be displayed on the message creation page.

  Although not shown in FIG. 18, the message providing unit 78 receives a request for retransmission of the encrypted message from the target person terminal 14 and retransmits the encrypted message held in the message holding part 32 to the target person terminal 14. May be. Similarly, the message providing unit 78 may accept a request for retransmission of the encrypted message from the target person terminal 14 and retransmit the encrypted message held in the message holding part 32 to the target person terminal 14. This service is typically a service in which the interval from message registration to its publication is long, and it is also assumed that the subject loses the encrypted message and hash data. The message holding unit 32 of the service support apparatus 10 holds a backup of the encrypted message and the hash data, and can rescue such a target person.

  FIG. 19 shows operations related to the funeral support service. When the funeral plan registration unit 90 of the funeral support unit 46 accepts a funeral plan registration request from the funeral company terminal 16 (Y in S80), the funeral plan information is stored in the funeral plan master 34 (S82). When the funeral plan presentation unit 92 accepts a request for provision of a funeral support service from the contractor terminal 12 (Y in S84), the funeral plan for introducing each funeral plan and inputting the contractor's own funeral hope as funeral information. A support page is provided to the contractor terminal 12 (S86). If a funeral plan registration request is not accepted (N in S80), S82 is skipped, and if a funeral support service provision request is not accepted (N in S84), S86 is skipped.

  When receiving the funeral information uploaded from the contractor terminal 12 (Y in S88), the funeral information receiving unit 94 records the funeral information in the funeral information holding unit 36 (S90). At the same time, the funeral information notification unit 96 notifies the funeral information to the funeral company terminal 16 and the mourner's target terminal 14 (S92). When the contractor's death is confirmed and service execution is instructed by the service instruction unit 56 (Y in S94), the funeral information notification unit 96 indicates that the contractor has died and that the contractor's funeral should be performed. The funeral company terminal 16 and the mourner's target terminal 14 are notified (S96). If no funeral information is uploaded from the contractor terminal 12 (N in S88), S90 and S92 are skipped, and if the existence of the contractor is confirmed (N in S94), S96 is skipped.

  As shown in FIG. 19, according to the service support device 10 of the embodiment, a funeral support page is provided to the contractor, and the funeral content desired by the contractor is input. Then, the funeral contents are notified to the funeral company and the mourner. Thereby, it is possible to support the contractor to design his / her funeral and to support the funeral being performed in a manner desired by the contractor.

  The present invention has been described based on the embodiments. This embodiment is an exemplification, and it will be understood by those skilled in the art that various modifications can be made to combinations of the respective constituent elements and processing processes, and such modifications are also within the scope of the present invention. is there.

  A first modification will be described. In the embodiment described above, the contractor confirmation unit 50 determines the standby period, which is the contractor's survival confirmation cycle, according to the service implementation timing of the ending service contracted by the contractor. Therefore, the contractor has indirectly designated the waiting period by selecting the ending service. As a modification, the value of the waiting period may be directly specified by the contractor. Specifically, the service support apparatus 10 further includes a confirmation cycle acquisition unit that receives information on a standby period designated by the contractor from the contractor terminal 12 and records the information in the contractor information of the contractor information holding unit 24. Also good. The contractor confirmation unit 50 uses the standby period acquired by the confirmation cycle acquisition unit as a standby period in the contractor survival confirmation process. According to this modification, the contractor's survival confirmation cycle can be set to a period desired by the contractor himself. If the service implementation time of the ending service contracted by the contractor and the waiting period specified by the contractor are inconsistent (for example, the waiting period is longer than the service implementation time), the confirmation cycle acquisition unit A warning that there is a possibility that the provision may be delayed from the time specified in the service implementation time may be sent to the target person terminal 14 to prompt the contractor to correct the waiting period.

  A second modification will be described. In the above embodiment, the target person confirmation unit 58 transmits the target person confirmation mail to each of the target persons specified by the contractor. In the modified example, on the related person registration page, a target person (hereinafter also referred to as “first group target person”) whose correctness of the target person information should be periodically checked and a target person who does not check the correctness of the target person information (hereinafter referred to as “target person”) The contractor may be able to designate "also called" second group target person "". The related person registration unit 48 may add information for identifying whether the person is the first group target person or the second group target person to the target person information. The subject confirmation unit 58 periodically transmits subject confirmation emails to the first group subject, but does not send subject confirmation emails to the second group subject. According to this modification, it is possible to suppress the transmission of the target person confirmation email to the target person who is determined not to notify that the service is provided in the future. In addition, it is considered that the second group target person is not closely related to the contractor (or it is difficult to accurately grasp the state of the contractor) as compared with the first group target person. You may restrict | limit to specify from among subjects. For example, on the related person registration page, the check box of the collaborator may be displayed in a mode that can be set only for the first group target person.

  A third modification will be described. In the will support service in the above embodiment, the encrypted message and the hash data are provided to the target terminal 14 when the message from the contractor to the target is received. However, the provision timing of the encrypted message and the hash data is not limited to this. At least when the decryption key is provided to the target person terminal 14, the encrypted message and the hash data may also be provided to the target person terminal 14. For example, when the contractor's death is confirmed and the service implementation time of the will support service is reached, the encrypted message and the hash data may be provided to the target terminal 14 together with the decryption key.

  A fourth modification will be described. In this modification, the contractor terminal 12 performs encryption of a message created by the contractor addressed to the target person and acquisition of hash data. The will support unit 44 in this modification includes a message creation support unit 70, a decryption key acquisition unit, and a decryption key provision unit 82. The message creation support unit 70 provides the contractor terminal 12 with an application for encrypting a plaintext message and an application for outputting hash data of the plaintext message along with the message creation page. The contractor terminal 12 executes encryption of a message created by the contractor addressed to the target person, setting of a decryption key, and acquisition of hash data. Further, the contractor terminal 12 uploads the decryption key to the target person terminal 14, while directly transmitting the encrypted message and the hash data to the target person terminal 14.

  The decryption key acquisition unit acquires the decryption key from the target person terminal 14. When it is confirmed that the contractor has died and the service implementation time of the will support service is reached, the decryption key providing unit 82 transmits the decryption key to the target person terminal 14. According to this modification, since the service support apparatus 10 does not handle the original message of the target person, the possibility that the service support apparatus 10 may tamper with the original message can be eliminated. Also, by providing a decryption key after the contractor's death, it is possible to make the subject confirm the message left by the contractor after the contractor's death.

  A fifth modification will be described. In the above embodiment, the warning unit 52 instructs the collaborator confirmation unit 54 to confirm the collaborator when the reply to the survival confirmation mail is not received from the contractor terminal 12. In the modification, the warning unit 52 should check with the cooperator for the operator of the service support apparatus 10 (for example, the person in charge of the service provider) when the reply to the survival confirmation mail is not received from the contractor terminal 12. A message to that effect may be notified. In the above embodiment, the service instruction unit 56 instructs the service execution unit 42 to provide the ending service when the contractor's death is confirmed. In the modified example, a message indicating that the ending service providing operation should be performed may be notified to the operator of the service support apparatus 10. The operator who has received these messages may operate the service support apparatus 10 to execute a confirmation process with a collaborator or an ending service provision process.

  A sixth modification will be described. The service support device 10 according to this modification provides a contractor's message in accordance with an event of the subject's life, such as the subject's birthday. Specifically, the will support unit 44 functions as a general-purpose message delivery processing unit that is not limited to a will. The message creation support unit 70 further includes an input field for the contractor to specify the delivery date of the message in the message creation page. The message holding unit 32 further holds a delivery date as message information, and the message receiving unit 72 stores the delivery date specified on the message creation page in the message holding unit 32. For each message stored in the message holding unit 32, the service instruction unit 56 determines whether or not the delivery date is equal to the current date, and when detecting a message with the delivery date equal to the current date, the message Is provided to the will support unit 44.

  As a message provision mode in this modification, as in the embodiment, an encrypted message is provided in advance to the target person terminal 14 before the delivery date, and a decryption key is assigned in accordance with an instruction from the service instruction unit 56. You may provide to the subject person terminal 14. Further, both the encrypted message and the decryption key may be provided to the target person terminal 14 at a time in accordance with an instruction from the service instruction unit 56. Furthermore, a plain text message obtained by decrypting the encrypted message may be provided to the target person terminal 14 in accordance with an instruction from the service instruction unit 56. The provision timing of the hash data may be provided to the target person terminal 14 in advance before the delivery date, or may be provided to the target person terminal 14 in accordance with an instruction from the service instruction unit 56. According to this modification, the message created by the contractor addressed to the target person can be provided to the target person at any timing desired by the contractor.

  A seventh modification will be described. The service support apparatus 10 according to this modification provides a function that effectively prompts the contractor to update the message. Specifically, the message holding unit 32 further holds the update date of the message. When the warning unit 52 refers to the update date of each message held in the message holding unit 32 and detects a message that has not been updated for a predetermined period (for example, one year) (hereinafter also referred to as “unupdated message”), The contractor notifying unit 60 is instructed to prompt the contractor to update the unupdated message. The contractor notifying unit 60 transmits an e-mail for prompting the update of the unupdated message to the contractor terminal 12. This e-mail may include, for example, a sentence including the target person (message destination), the content of the unupdated message, and the update date (date when the unupdated message was registered). Although it is assumed that the message that the contractor wants to leave to the subject changes with the passage of time, this modification makes it easier to provide the subject's latest thoughts to the subject.

  In addition, when a plurality of unupdated messages are detected for one contractor, the contractor notification unit 60 is designed to reduce the burden on the contractor by avoiding concentration of update work and distributing the work. It is desirable to prompt for an update according to the proposed algorithm. For example, after sending an e-mail for prompting an update of one unupdated message, after waiting for a predetermined period (for example, one week), an e-mail for prompting an update of another unupdated message is sent May be. Further, for example, when a plurality of unupdated messages are detected for one contractor, the warning unit 52 may instruct the contractor notifying unit 60 to prompt the update of one of the unupdated messages. As a result, it is possible to avoid applying a large burden (high stress) to the contractor for updating the message, and it is possible to prevent the message from becoming obsolete.

  An eighth modification will be described. The service support device 10 according to this modification provides a function of changing the message transmission mode according to the message viewing environment of the target person. Specifically, the message providing unit 78 further includes a conversion unit that decrypts the encrypted message in response to a notification from the subject (for example, notification via a web page or an e-mail). This notification indicates the browsing environment of the message in the target person terminal 14, and may be, for example, information indicating the presence / absence of a decryption function, identification information of the terminal model, It may be information specifying provision or provision of a voice message. The conversion unit decrypts the encrypted message addressed to the subject in accordance with the content of the notification from the subject, or converts the content of the decrypted message into voice data. When the encrypted message is converted by the conversion unit, the message providing unit 78 transmits the converted data (plain text message or voice data) to the target person terminal 14, and if the encrypted message is not converted by the conversion unit, For example, the encrypted message is transmitted to the target person terminal 14. According to this modification, a message from the contractor can be reliably transmitted to the target person.

  A ninth modification will be described. The service support apparatus 10 according to this modification provides a function of suppressing the existence confirmation of the contractor. Specifically, the contractor information holding unit 24 further holds a survival confirmation inhibiting period as a period for suppressing the survival confirmation for the contractor. The contractor confirmation unit 50 preliminarily sends information indicating a period during which the contractor cannot respond to the survival confirmation mail due to travel or hospitalization (for example, from October 1 to October 20) from the contractor terminal 12. The period is accepted and stored in the contractor information holding unit 24 as the survival confirmation inhibiting period. The contractor confirmation unit 50 confirms the existence of a contractor for the contractor even if it is detected that the waiting period has passed since the date when the existence was confirmed in the past, and the current date is within the survival confirmation suppression period. Suppress sending mail. According to this modification, when it is known in advance that the contractor cannot respond to the survival confirmation mail due to reasons such as travel or hospitalization, the execution of the survival confirmation can be suppressed. As a result, an unnecessary death confirmation mail is transmitted to the cooperator, and unnecessary labor and confusion can be avoided.

  A tenth modification will be described. In this modification, the system automatically selects a collaborator instead of letting the contractor designate the collaborator. Here, the person who the contractor selects as a collaborator usually has an intimate relationship with the contractor such as a family member or a best friend. Whether or not there is an intimate relationship can be estimated from the update frequency of the message and the content of the message. Therefore, the message holding unit 32 further holds information indicating the update frequency of the message, for example, the number of updates and the update interval. The control unit 40 selects a collaborator from the plurality of target persons based on the update frequency of the plurality of messages set by the specific contractor for the plurality of target persons and / or the contents of each message. The cooperator information holding unit 28 is further provided with a cooperator selecting unit.

  The collaborator selection unit may select, as a collaborator, a target person of a message that is updated more frequently than an average update frequency of messages registered by the contractor for one contractor. For example, a message subject who has been updated more times than the average number of updates may be selected as a collaborator, and a message subject who has been updated at an interval shorter than the average update interval as a collaborator. You may choose. In addition, the collaborator selection unit may select a target person of a message that is assumed to be more important than other messages as a collaborator. For example, a message created using a document form of the property inheritance will category may be detected from a plurality of messages, and a target person of the message may be selected as a collaborator.

  An eleventh modification will be described. In the above embodiment, the message registered by the contractor is uniformly encrypted. However, the service support apparatus 10 of this modification autonomously changes the security level of the message according to the content of the message. Specifically, each of a plurality of document forms held in the document form master 30 is associated with either high importance or low importance in advance. For example, high importance may be associated with each document form in the property inheritance will category, while low importance may be associated with other document forms.

  The encryption unit 74 encrypts a message created using a document form with a high importance level in the same manner as in the embodiment, while retaining a message created using a document form with a low importance level in plain text. You may store in the part 32. When the encrypted message is stored in the message holding unit 32, the message providing unit 78 immediately provides the encrypted message to the target person terminal 14 as in the embodiment. On the other hand, when a plaintext message is stored in the message holding unit 32, when the contractor's death is detected, in other words, when the contractor's death is notified from the service instruction unit 56, the plaintext message is stored. Is provided to the target person terminal 14. According to this modification, since the low-importance message is provided to the target person terminal 14 in plain text, the decryption process at the target person terminal 14 becomes unnecessary, and the target person can easily confirm the content of the message.

  As another example, the encryption unit 74 may determine the importance of a message by keyword search. For example, a predetermined keyword (“account number”, “cash”, “inheritance”, etc.) that is assumed to be included in a message with high importance, a character string pattern such as a regular expression, and the like are stored in advance. The included message may be determined as a high importance message, and the message not including those keywords may be determined as a low importance message. In the above modification, the identification information of the document form selected by the contractor at the time of creating the message may be notified from the contractor terminal 12 to the service support apparatus 10 at the time of message registration, and the service support apparatus based on this notification 10 may determine the importance of the message.

  A twelfth modification will be described. The service support apparatus 10 according to the embodiment described above permanently stores the encrypted message and the hash data as a backup so that the target person can retransmit the encrypted message and the hash data when they are lost. In the modification, the message holding unit 32 may hold only the decryption key without holding these data after once providing the encrypted message and the hash data to the target person. For example, the message providing unit 78 may delete the encrypted message in the message holding unit 32 after providing the encrypted message to the target person terminal 14. Similarly, the hash providing unit 80 may delete the hash data of the message holding unit 32 after providing the hash data to the target person terminal 14. According to this modification, the leakage of the encrypted message or hash data to a third party can be prevented more reliably.

  Any combination of the above-described embodiments and modifications is also useful as an embodiment of the present invention. The new embodiment generated by the combination has the effects of the combined embodiment and the modified examples.

  It should also be understood by those skilled in the art that the functions to be fulfilled by the constituent elements recited in the claims are realized by the individual constituent elements shown in the embodiments and the modified examples or by their linkage.

  DESCRIPTION OF SYMBOLS 10 Service support device, 42 Service execution part, 44 Will support part, 46 Funeral support part, 48 Person registration part, 50 Contractor confirmation part, 52 Warning part, 54 Collaborator confirmation part, 56 Service instruction part, 58 Target person Confirmation unit, 60 contractor notification unit, 62 service selection support unit, 70 message creation support unit, 72 message reception unit, 74 encryption unit, 76 hash generation unit, 78 message provision unit, 80 hash provision unit, 82 decryption key provision Department, 90 funeral plan registration department, 92 funeral plan presentation department, 94 funeral information reception department, 96 funeral information notification department, 100 ending service system.

Claims (6)

When the contractor dies, the apparatus supports the provision of services to the target person registered in advance by the contractor according to the contract content,
When the contractor's death is confirmed by a collaborator registered in advance by the contractor, an instruction unit for instructing provision of the service;
A registration unit for registering the target person and the collaborator,
The registration unit displays a screen for registering the collaborator on the terminal of the contractor, and the screen is configured to be able to designate the collaborator from the target person. Service support device.   A collaborator notifying unit is further provided for notifying that the collaborator registered in the registration unit is registered as a person to whom a service is provided and a collaborator who is to cooperate in confirmation of the existence of the contractor. The service support apparatus according to claim 1. A target person confirmation unit for notifying the target person of a message indicating that the service is provided and receiving a reply to the message from the target person;
When there is no reply from the target person, a contractor notifying unit for notifying the contractor of a message for prompting to update the target person,
The service support apparatus according to claim 1, further comprising:   4. A funeral plan presenting unit that presents a plurality of funeral plans to the contractor and causes the contractor to select a funeral plan when the contractor dies, according to any one of claims 1 to 3. The service support apparatus described. A message accepting unit that accepts a message created by the contractor to the target person from the contractor;
A message providing unit that provides encrypted data obtained by encrypting the message to the target person;
When the contractor's death is confirmed, a decryption key that allows the subject to view a message obtained by decrypting the encrypted data by providing the subject with a key for decrypting the encrypted data A providing department;
A confirmation data providing unit that provides the target person with data as a result of inputting the message created by the contractor into a one-way function so that the message obtained by decrypting the encrypted data can be confirmed; and
The service support apparatus according to claim 1, further comprising: A holding section for a plurality of types of information items for identifying the format of the contractor's will,
A screen for creating a message addressed to the target person, wherein the plurality of types of information items are presented to the contractor and selected, and a will creation screen in a format corresponding to the selection result is presented to the contractor. A message creation support department,
The service support apparatus according to claim 5, further comprising:

Images