WO2018055911A1

WO2018055911A1 - Sns server, method which is executed by sns server, information processing device for administrator, method which is executed by information processing device for administrator, and program

Info

Publication number: WO2018055911A1
Application number: PCT/JP2017/027498
Authority: WO
Inventors: 浩市緑間
Original assignee: 株式会社冲セキ
Priority date: 2016-09-23
Filing date: 2017-07-28
Publication date: 2018-03-29
Also published as: JP2018049535A; JP6813174B2

Abstract

Provided is an SNS server 120, which provides an SNS which includes among users thereof a first user (C), and an administrator (B) who administers an SNS account for a decedent (A). Said SNS server 120 comprises: a receiving unit 1221 which receives, from the first user (C), a request for after-death information of the decedent (A); and a presentation unit 1223 which presents to the administrator (B), as response content to the request, content based on the SNS relation between the first user (C) and the decedent (A).

Description

SNS server, method executed by SNS server, information processing apparatus for administrator, method executed by information processing apparatus for administrator, program

The present invention relates to the technology of an SNS server that provides SNS (Social Networking Service).

When you want to visit the grave of a friend or teacher, you may not know where the grave is. Usually, you will contact the bereaved family, but it may be difficult to find contact information. It is convenient if the deceased is a SNS user such as Facebook (registered trademark) and grave information is posted on his / her SNS site. However, since the grave is generally made after death, the grave information cannot be put on its own SNS site before life. On the other hand, after the death, not only the deceased, but also third parties cannot log into the SNS account of the deceased.

However, there are also SNSs that can set an account administrator who manages the account of the deceased (see Non-Patent Document 1, pages 182 to 183).

However, it is not always desirable for the account administrator to post the grave information on the deceased SNS site. For example, if anyone can see the location of the deceased's grave, depending on the relationship with the deceased, there is a risk that the information will be transmitted to those who the bereaved do not want to convey such information.

Therefore, an object of the present invention is to provide a technology for an SNS server that can share information related to the deceased's death within an appropriate range.

An SNS server according to an aspect of the present invention is an SNS server that provides an SNS including a first user and an administrator who manages an SNS account for a deceased user. A receiving unit that receives a request for information related to the death of the user, and a presentation unit that presents to the administrator a response according to the SNS relationship between the first user and the deceased as a response to the request.

The method performed by the SNS server which concerns on 1 aspect of this invention is a method performed by the SNS server which provides SNS which contains a 1st user and the administrator who manages the SNS account for deceased in a user. The administrator receives a request from the first user for information related to the deceased's death, and the content of the response to the request corresponds to the SNS relationship between the first user and the deceased. Presenting.

A program according to an aspect of the present invention provides a SNS server that provides an SNS including a first user and an administrator who manages an SNS account for a deceased user to the SNS server after the death of the deceased. Receiving a request for related information and presenting to the administrator a response corresponding to the request according to the SNS relationship between the first user and the deceased.

An administrator information processing apparatus according to one aspect of the present invention is an administrator information processing apparatus that is connected to an SNS server that provides an SNS to a user via a network and manages an SNS account for a deceased person. When a request for information registered in the SNS server is made from a transmission unit that transmits information related to the death of the deceased to the SNS server for registration and a first user who is one of the users, the SNS server A receiving unit that receives the response content presented according to the SNS relationship between the first user and the deceased as the response content to the request.

A method executed by an administrator information processing apparatus according to an aspect of the present invention is an information processing by an administrator who manages an SNS account for a deceased who is connected to an SNS server that provides an SNS to a user via a network. A method executed by the apparatus, which transmits information related to the death of the deceased to the SNS server for registration, and requests for information registered in the SNS server from a first user who is one of the users Receiving the response content presented according to the SNS relationship between the first user and the deceased as the response content to the request from the SNS server.

A program according to an embodiment of the present invention is connected to an SNS server that provides an SNS to a user via a network, and information related to the deceased's death is stored in an information processing apparatus of an administrator who manages an SNS account for the deceased. When a request for information registered in the SNS server is sent from the first user, one of the users, to the SNS server for registration, the SNS server gives the first response content for the request. Receiving the response content presented in accordance with the SNS relationship between the user and the deceased.

1 is a schematic diagram of an information processing system including an SNS server according to an embodiment. It is a flowchart which shows the process which registers an administrator in the information processing system of FIG. It is a flowchart which shows the process which registers the deceased's death information in the information processing system of FIG. FIG. 2 is a flowchart showing a process of sharing deceased information after death in the information processing system of FIG. 1. It is a figure which shows an example of the table which shows the relationship on the SNS of a requester and a deceased used for the process of FIG. It is a schematic diagram which shows an example of the screen of a deceased SNS site which appears in the process of FIG. It is a schematic diagram which shows an example of the screen of the administrator who appears in the process of FIG. 2B. It is a schematic diagram which shows an example of a requester's screen which appears in the process of FIG. It is a schematic diagram which shows an example of the screen of an administrator who appears in the process of FIG. It is a schematic diagram which shows an example of the screen of an administrator who appears in the process of FIG. It is a schematic diagram which shows an example of the screen of an administrator who appears in the process of FIG. It is a schematic diagram which shows an example of a requester's screen when the deceased's death information is received in the process of FIG. It is the schematic which shows the grave which provided the two-dimensional code, and the information processing system which concerns on embodiment. FIG. 8 is a flowchart showing a reading process when the information processing system of FIG. 7 reads a two-dimensional code. It is a figure which shows an example of the table which recorded the requester's check-in with respect to the grave which provided the two-dimensional code in the reading process of FIG. FIG. 8 is a schematic diagram illustrating an example of a Web site that appears on the screen of a requester's mobile terminal in the reading process of FIG. 7. It is a block diagram which shows the SNS server in the information processing system of FIG. It is a block diagram which shows the client terminal of the administrator in the information processing system of FIG.

Preferred embodiments of the present invention will be described with reference to the accompanying drawings.

As shown in FIG. 1, the information processing system 100 includes a plurality of

client terminals

110A, 110B, 110C-1, 110C-2,... 110C-N (hereinafter may be collectively referred to as “110”). The SNS server 120 is configured to be connectable to the network 130. The network 130 is configured by a LAN, a WAN, a wired or wireless network, the Internet, or the like.

The client terminal 110 can be configured by a communication device or a computer having a display screen, and is configured by, for example, a desktop type, laptop type or tablet type computer, PDA, mobile phone, or smartphone. The client terminal 110 has software (for example, a web browser or an application 140) for using the SNS provided by the SNS server 120. When the client terminal 110 is classified according to the type of SNS user, the client terminal 110A of the deceased (A), the client terminal 110B of the administrator (B), and the requesters (C1, C2,... CN. The client terminals 110C-1, 110C-2,... 110C-N may be divided into “C”. The deceased (A), the administrator (B), and the requester (C) are users who are registered or registered for use in the SNS provided by the SNS server 120. The deceased (A) client terminal 110A is used by the deceased (A) to use his / her SNS site before his / her life. The client terminal 110B of the administrator (B) is used by the administrator (B) to manage the SNS account for the deceased (A). The manager (B) can be, for example, an agent (funeral trader, lawyer, stone trader, cemetery trader, etc.) in addition to the bereaved family or friend of the deceased (A). The client terminals 110C-1, 110C-2,... 110C-N of the requester (C1, C2,... CN) use the requester (C1, C2,... CN) to request the deceased person's (A) death information. It is what you use.

The SNS server 120 is an information processing apparatus that provides the client terminal 110 with an SNS function. The SNS server 120 stores information on users who use the SNS function. User information to be stored includes, for example, the ID and password for the user to log in to his / her SNS account, his / her birth date, hometown, high school, university, work history, hobbies and other profiles, as well as the user Can be included. In addition, various items can be included in the profile or group, and a disclosure range can be set for each item. And in the user's SNS site displayed by logging in to the SNS account, it is possible for SNS users to set up connections, and to create groups with SNS users. It is. In addition, the SNS server 120 may be configured to be able to access contacts stored or registered by the user regarding software different from software for using the SNS. Although details will be described later with reference to FIG. 11, in addition to the above-described user information, the SNS server 120 includes the information on the manager (B), the post-mortem information of the deceased (A), the deceased (A) and the requester Information on the SNS relationship with (C) is also stored.

FIG. 2A is a flowchart showing a process of registering an administrator (B) who manages an SNS account for the deceased (A). When the deceased person (A) registers the manager (B) who manages his / her SNS account after his death, the deceased person (A) transmits the request to the SNS server 120 (S200). If the deceased person (A) did not register before his / her lifetime, the person who should become the administrator (B) transmits an administrator registration request to the SNS server 120 after the deceased person (A) died (S202). The SNS server 120 receives the registration request for the SNS account for the deceased (A) (S204), and registers the administrator (B) (S206). Then, the SNS server 120 transmits the registration confirmation to the administrator (B) (S208), and the administrator (B) receives this (S210). When the deceased person (A) requests administrator registration before his / her lifetime, the registration confirmation is also transmitted to the deceased person (A), and the deceased person (A) receives it (S212). Note that the person who requests registration may be different from the person who actually becomes the administrator. For example, it is also possible for a funeral company or the like to send a registration request to the SNS server 120 to designate the deceased bereaved as the manager (B).

FIG. 2B is a flowchart showing a process for registering post-mortem information of the deceased (A). The administrator (B) transmits a request for registering post-mortem information of the deceased (A) to the SNS server 120 (S220). If the deceased person (A) can register his / her post-mortem information before his / her lifetime, the request can be transmitted to the SNS server 120 (S222). For example, when the grave already exists, the deceased (A) can send a registration request for his / her grave information to the SNS server 120 before his / her life. The SNS server 120 receives the post-death information registration request (S224), and registers the post-death information (S226). Then, the SNS server 120 transmits the registration confirmation to the administrator (B) (S228), and the administrator (B) receives this (S230). Thereby, the administrator (B) can confirm that the deceased information of the deceased (A) is registered in the SNS server 120. When the deceased person (A) requests registration of his / her death information before his / her lifetime, a registration confirmation is also transmitted to the deceased person (A), and the deceased person (A) receives this (S232). The post-death information of the deceased person (A) registered in the SNS server 120 is set to be private.

Here, the post-mortem information of the deceased (A) refers to information related to the deceased (A) after his death, and may include, for example, information on at least one of the deceased (A) funeral, the legal affairs, and the grave. Specifically, the information on the funeral is information on the date, place, mourner, form, etc. of the funeral. The information on the legal affairs is information on the date and time of the legal affairs, the place, the organizer, the presence of meals, and the like. The information on the grave is information on the location of the grave.

FIG. 3 is a flow diagram showing a process for sharing information after the death of the deceased (A). This process starts when the requester (C) sends a request for information on the death of the deceased (A) to the SNS server 120 (S300). The SNS server 120 receives a request for posthumous information (S302), and specifies the SNS relationship between the requester (C) and the deceased (A) (S304). For example, the SNS server 120 specifies that the requester (C) has a connection with the deceased (A) on the SNS, or the requester (C) has a special group on the SNS with the deceased (A). Or that it belongs to a category. As a result, the SNS server 120 transmits the response content corresponding to the identified relationship on the SNS to the administrator (B) in order to present the response content to the request to the administrator (B) (S306). The administrator (B) receives the presented answer content (S308). The presented answer content includes an option (S310) that allows the deceased person (A) to pass after death information, an option (S312) that rejects the option, and an option (S314) that asks questions about the deceased (A). , One or more corresponding to the relationship on the SNS is included.

When the administrator (B) selects a permission option (S310), the fact is transmitted to the SNS server 120 (S316). In response to this, the SNS server 120 transmits the requested post-death information to the requester (C) (S318). Thus, the requester (C) receives the post-death information of the deceased (A) as requested (S320). On the other hand, when the administrator (B) selects a rejection option (S312), the fact is transmitted to the SNS server 120 (S322). In response to this, the SNS server 120 transmits a request rejection message to the requester (C) (S324). Thus, the requester (C) receives a notification that the request has been rejected (S326).

Alternatively, when the administrator (B) selects the question option (S314), the fact is transmitted to the SNS server 120 (S328). In response to this, the SNS server 120 transmits a question regarding the deceased (A) to the requester (C) (S330). When the requester (C) receives the question (S332) and answers the question (S334), the SNS server 120 receives the answer (S336) and determines whether the answer satisfies a predetermined standard. (S338). The predetermined standard can be whether or not there is an answer, or if a score is given to the answer, whether or not the score is a predetermined value or more. When the predetermined standard is satisfied (S340), the SNS server 120 transmits the requested post-death information to the requester (C) (S318). If the predetermined standard is not satisfied (S342), the SNS server 120 transmits a request rejection message to the requester (C) (S324). In any case, the SNS server 120 transmits the answer determination result to the administrator (B) (S344), and the administrator (B) receives this (S346). Therefore, the manager (B) can confirm whether or not the post-death information has been transmitted to the requester (C) who asked the question.

In another embodiment, as shown by a broken line in FIG. 3, an answer to the question may be transmitted to the administrator (B) (S350), and the answer may not be determined by the SNS server 120. That is, the determination subject of the answer may be the administrator (B). In this case, when the administrator (B) receives the answer (S352), an option (S354) that permits the passing of the deceased person (A) 's death information and an option (S356) that rejects it are presented. When a permission option is selected based on the judgment of the administrator (B), a message to that effect is transmitted to the SNS server 120 (S358), and postmortem information is transmitted from the SNS server 120 to the requester (C) (S318). . On the other hand, when a rejection option is selected by the administrator (B), a message to that effect is transmitted to the SNS server 120 (S360), and a request rejection message is transmitted from the SNS server 120 to the requester (C). (S324).

As described above, in the present embodiment, a request for the death information of the deceased (A) is received from the requester (C) using the SNS, and the requester (C) and the deceased (A) are requested in response to the request. The response content corresponding to the relationship on the SNS is presented to the administrator (B). As a result, even if the requester (C) does not know the contact information of the deceased's (A) survivor, or if such contact is known, the survivor will not be explained. It is convenient because it is possible to ask on the SNS after the death of the deceased (A). In addition, for the manager (B), it is necessary to determine how the requester (C) should respond to the request without knowing the relationship between the deceased (A) and his / her life. Is presented, it is possible to provide post-mortem information of the deceased (A) within an appropriate range.

FIG. 4 is a diagram illustrating an example of a table 400 indicating the SNS relationship between the requester (C) and the deceased (A). This table 400 is used, for example, in the specific step (S304) of FIG. 3, and is stored in the SNS server 120. As shown in FIG. 4, the requesters C1 to C4 are connected to the deceased (A) on the SNS. This connection is set, for example, when one of the requests C1 to C4 and the deceased (A) sends a connection application to the other and the other permits the connection application.

Requester C1 further belongs to the same group as the deceased (A). This group was created on the SNS by the requester C1, the deceased (A), or another group member. In this group, the group members are not allowed to share their post-mortem information with other group members. Allowed to. That is, because the requester C1 and the deceased (A) belong to this group, the deceased (A) allows the requester C1 to transmit his / her death information to the requester C1 on the SNS. In other embodiments, the deceased person (A) can individually set such a pre-permission for the requester C1 without belonging to such a group. In view of such attributes of the requester C1, the SNS server 120 has at least an option (FIG. 3: S310) that permits transmission of the deceased person (A) 's death information as a response to the request from the requester C1. Present it to the administrator (B).

Requesters C2 to C4 do not belong to the above group. For this reason, the deceased person (A) does not permit his / her death information to be transmitted to the requesters (C2 to C4) on the SNS. Requesters C2 and C3 share a common profile on the SNS with respect to deceased (A) and categories a and b, respectively. For example, category a is a university and category b is a current workplace. On the other hand, the requester C4 does not have a category that shares the profile with the deceased (A) on the SNS. In view of the attributes of the requesters C2 to C4, the SNS server 120 manages at least an option for asking a question regarding the deceased (A) (FIG. 3: S314) as a response to the request from the requesters C2 to C4. To the person (B). As questions to the requesters C2 and C3, questions corresponding to the common categories a and b are presented. For example, the question to the requester C2 can be a question such as “Please answer the circle, laboratory or seminar to which the deceased (A) belonged when he was a university (category a)”. Since there is no common category as a question to the requester C4, it can be a question about a more general or private content, for example, a hobby, a special skill, a welfare activity, etc. of the deceased (A). In addition, when there are a plurality of common categories, a question corresponding to any one or a plurality of categories may be presented.

The requesters C5 and C6 have no connection with the deceased (A) on the SNS, but the contacts of the deceased (A) that can be accessed by the SNS server 120 and the management that can be accessed by the SNS server 120, respectively. It is a person included in the contact information of the person (B). These contacts are related to software other than the software for using the SNS provided by the SNS server 120, and the deceased person (A) or the administrator (B) can use personal information (name, address, telephone number, E-mail, etc.). In view of the attributes of the requesters C5 and C6, the SNS server 120 manages at least an option for asking a question about the deceased (A) (FIG. 3: S314) as a response to the request from the requesters C5 and C6. To the person (B). The questions to the requesters C5 and C6 may be the same as the questions to the requester C4 described above, but are more difficult than the questions to the requester C4 or are more deceased (A It may be a question of a private thing).

The requester C7 does not have a connection on the SNS with the deceased person (A), and is included in any contact information of the deceased person (A) and the administrator (B) accessible by the SNS server 120. No one. That is, the requester C7 is a person who cannot confirm the relationship between the deceased (A) and the administrator (B) on the data of the SNS server 120 and the data accessible by the SNS server 120. In view of such attributes of the requester C7, the SNS server 120 has at least an option (FIG. 3: S312) to refuse to convey the deceased person's (A) posthumous information as a response to the request from the requester C7. Present it to the administrator (B).

5A to 5F are schematic diagrams showing examples of screens appearing in the process of FIG. 2A, B or FIG. FIG. 5A shows a screen of the SNS site of the deceased (A). This SNS site is associated with the SNS account for the deceased (A), and displays the content in this SNS account. This content includes a field 500 indicating an identifier (name or photo) of the deceased (A), a field 502 leading to the profile of the deceased (A), an administrator-only field 504 for the administrator (B) to log in, A field 506 for the requester (C) to connect to the deceased (A) and send an application, and a field 508 for the requester (C) to request deceased (A) post-mortem information are included. The administrator (B) can manage the SNS account for the deceased (A) by logging in through the administrator dedicated field 504. For example, the administrator (B) can register postmortem information of the deceased (A) and other related information (information on a proxy service, which will be described later) through the administrator dedicated field 504. Note that the screen of FIG. 5A appears, for example, at S300 of FIG.

FIG. 5B shows the screen of the administrator (B) that appears when the administrator (B) registers the deceased's (A) death information. On this screen, fields 510, 512, and 514 for inputting information related to funerals, legal matters, and graves are displayed. For example, the administrator (B) can register the location of the grave of the deceased (A) through the grave field 514. The administrator (B) can also register a photo of the grave of the deceased (A) in the cemetery through the grave field 514. The requester who wants to visit the grave of the deceased (A) can easily find the grave of the deceased (A) by not only the location of the grave but also a picture of the grave in the cemetery. Note that the screen of FIG. 5B appears, for example, at S220 of FIG. 2B.

FIG. 5C shows the screen of the requester (C) that is displayed when the requester (C) inputs (clicks or taps) the field 508 (post-mortem information request) in FIG. 5A. On this screen, fields 520, 522, and 524 for receiving requests for information on funerals, legal matters, and graves are displayed. When the requester (C) inputs (clicks or taps) any of the

fields

520, 522, and 524, a corresponding request is transmitted to the SNS server 120. The field 508 can be an icon, a box, or a link, for example, and accepts a request from the requester (C).

FIGS. 5D to 5F show the screen of the administrator (B) when the content of the response to the request from the requester (C) is presented from the SNS server 120, respectively. As described above, the administrator (B) receives from the SNS server 120 what is presented according to the SNS relationship between the requester (C) and the deceased (A) as the response content to the request. As shown in FIGS. 5D to 5F, the message received by the administrator (B) includes an area 530 indicating which requester (C) has requested, on the SNS of the requester (C) and the deceased (A). And an area 534 indicating one or more options (an attribute of the requester (C)).

As shown in FIG. 5D, when the requester (C) corresponds to the requester C1 of FIG. 4, an option 540 is displayed that permits the provision of post-death information. On the other hand, as shown in FIG. 5E, when the requester (C) corresponds to any of the requesters C2 to C6 in FIG. 4, an option 542 for asking a question regarding the deceased (A) is displayed and allowed. The option 540 is also displayed. In this way, by presenting the two

options

540 and 542 of “question” and “permission”, when the administrator (B) knows the requester (C) well and does not need to ask a question, the post-mortem information is displayed. It becomes possible to provide the requester (C) promptly. As shown in FIG. 5F, when the requester (C) corresponds to the requester C7 in FIG. 4, an option 544 for refusing to provide postmortem information is displayed, and a question option 542 is also displayed. Is displayed. In this way, by presenting the two

options

542 and 544 of “reject” and “question”, the administrator (B) is not connected to the requester (C) in terms of data, but actually the requester ( If you know C), you do not have to reject the request. Note that the screens of FIGS. 5D to F appear, for example, in S308 of FIG.

FIG. 6 is a schematic diagram showing an example of the screen of the requester (C) when the deceased person (A) 's post-death information is received. This screen appears, for example, at S320 in FIG. In other words, it is displayed when the deceased person (A) 's death information is permitted to be provided to the requester (C). 6 to 10 exemplify a case where information on a grave is requested as post-mortem information, the same applies to a case where information on a funeral or a legal matter is requested.

As shown in FIG. 6, the message 600 received by the requester (C) includes a post-death information area 602, a proxy service area 604, and a password area 606. The post-death information area 602 is an area for displaying post-death information requested by the requester (C), and here, information on the location of the deceased (A) grave and a photo of the grave (photo of the grave in the cemetery). It is included.

The proxy service area 604 is an area for displaying information related to the proxy service that can be requested by the requester (C). Such information includes, for example, a visitor acting on behalf of the requester (C), visiting the grave of the deceased (A), cleaning the grave of the deceased (A), and weeding the surrounding area. Information relating to a cleaning agent to perform, a flower agency to provide flowers and incense sticks to the grave of the deceased (A), a purchase agent to purchase flowers and incense sticks, and the like. By transmitting / providing such information regarding the proxy service to the requester (C) along with post-mortem information, the convenience of the requester (C) can be provided. For example, the requester (C) uses a purchase agent service to place an order for flowers before visiting the grave, and places close to the grave (stores such as convenience stores or actually ordered florists, cemeteries with graves, etc. ) To receive the flowers ordered. Information regarding such a proxy service can be registered in the SNS server 120 by a request or input from the administrator (B). For example, a florist near the grave of the deceased (A) can be registered as purchase agent information. The timing for registering such information may be, for example, when requesting registration of the deceased person's (A) death information (see: S220 in FIG. 2B), and thereafter (for example, setting the administrator-specific field 504 in FIG. 5A). When using).

The password area 606 is an area for displaying information related to the two-dimensional code password. This area also includes content explaining the reason for conveying the password. As described in this explanation, the grave of the deceased (A) or the ossuary (cemetery) has a two-dimensional code for the deceased (A), and the person who visited the grave reads the two-dimensional code and enters the password. By doing so, the person who visited the grave can see information on the deceased (A). Sending and providing this password to the requester (C) along with postmortem information, providing the requester (C) with the added value of visiting the grave and providing the administrator (B) with information about the visitor's status of visiting the grave Can do. This will be described next. Note that the password area 606 is automatically registered by the SNS server 120 when a two-dimensional code is provided in the grave of the deceased (A) and is registered in the SNS server 120 by a request or input from the administrator (B). The SNS server 120 may be configured so as to be created automatically.

FIG. 7 is a schematic diagram showing a grave provided with a two-dimensional code and the information processing system 100. The grave 700 of the deceased (A) is provided with a two-dimensional code 702 for the deceased (A) who needs a password. The two-dimensional code 702 is, for example, a QR code (registered trademark), and stores predetermined information so that it can be read by a reader. The two-dimensional code 702 is created by, for example, a tombstone trader and provided in the tomb 700. As described above, such a tombstone trader may serve as an administrator (B). The requester (C) has a mobile terminal 710 such as a smartphone as the client terminal 110 described above. The mobile terminal 710 uses a function of displaying information, a function of a reader for reading a two-dimensional code 702, a function of inputting a password, a function of communicating with the SNS server 120 via the network 130, and a GPS or the like. It has software for realizing various functions such as the function of measuring the position of the machine.

FIG. 8 is a flowchart showing a two-dimensional code reading process. First, when the requester (C) reads the two-dimensional code 702 using the mobile terminal 710 locally (S800), a screen for inputting a password is displayed on the mobile terminal 710 (S802). When the requester (C) further inputs a password using the mobile terminal 710 (S804), password information is transmitted to the SNS server 120. The SNS server 120 receives the password information (S806), and determines whether the received password is compatible (S808). If it is determined that the password is incompatible (S810), the result is transmitted to the mobile terminal 710 (S812). The requester (C) notices that the password is wrong through the mobile terminal 710 that has received the request (S814). Or you realize that you came to someone else's grave by mistake.

On the other hand, if it is determined that the password is appropriate (S816), the SNS server 120 stores that the requester (C) has checked in the deceased (A) 's grave (S818), and that Is transmitted to the administrator (B) (S820). The administrator (B) can notice in real time that the requester (C) has visited the grave of the deceased (A) through the client terminal 110B that has received the notification (S822). The check-in may be automatically performed on the SNS site associated with the SNS account for the deceased (A). If it is determined that the password is suitable (S816), the SNS server 120 transmits information for causing the mobile terminal 710 to display information related to the deceased (A) to the mobile terminal 710 (S826). . The mobile terminal 710 receives this information (S828) and displays information about the deceased (A) (S830). In this way, the requester (C) can confirm that the location of the grave is correct through the information displayed on the mobile terminal 710 and can know more about the deceased (A) in front of the grave. You can also strengthen your feelings for (A).

Here, the information regarding the deceased (A) displayed on the mobile terminal 710 can be an SNS site (for example, the screen of FIG. 5A) associated with the SNS account for the deceased (A). Apart from that, it can also be a website created for the deceased (A). Such an SNS site or website may contain various information, such as the profile of the deceased (A), photo, date of death, age at death, cause of death, name of war, date of bone delivery, prenatal message, In addition to the family tree, information on other people and animals buried in the grave, as well as grave information such as stone materials and design of the grave, and the process of creating the grave, and information on agency services similar to the above be able to. Such information may be not only characters and images but also moving images. In addition, it is possible to take advantage of the fact that such information can be seen if you visit the grave, and it can be said that no sculpture is made in the grave. This is desirable for those who do not want to make their personal information public.

In another embodiment, as shown by a broken line in FIG. 8, the SNS server 120 may receive the location information of the mobile terminal 710 together with the password information (S840). Then, the SNS server 120 may use the received position information when determining the password (S842). By using this location information, the SNS server 120 can determine whether or not the requester (C) has actually entered the grave 700 and entered a password. If the requester (C) determines that the requester (C) has not actually visited the grave 700, the SNS server 120 does not execute the steps (S818, S820, S826) when the password is matched, May be determined to be incompatible (S810). As a result, only the person who actually visits the grave 700 can see the information about the deceased (A), so that the added value of visiting the grave can be further emphasized to the requester (C). it can.

FIG. 9 shows an example of a table 900 showing a record of check-in of the requester (C) with respect to the grave 700. This table 900 is recorded / updated in the check-in recording step (S818) of FIG. 8, for example, and is stored in the SNS server 120. The table 900 stores the visit date and time and the total number of visits to the grave 700 in association with the requester (C). For example, for the requester C1, it is stored that the password is entered by reading the two-dimensional code 702 of the tomb 700 twice, January 1, 2016 and July 1, 2016 in total.

FIG. 10 shows an example of the screen of the mobile terminal 710 of the requester (C) on which the Web site 1000 created for the deceased (A) is displayed. This screen appears, for example, in the display step (S830) of FIG. In this Web site 1000,

fields

1004, 1006, and 1008 connected to the profile of the deceased (A), the grave information, and the proxy service are displayed together with the title 1002 by clicking or tapping. Therefore, for example, when the field 1006 of the tomb information is selected on the mobile terminal 710, the type of stone material of the tomb 700, the design, the process of creating the tomb 700, the contractor involved in the construction of the tomb 700, and the like are displayed.

In the examples of FIGS. 6 to 10 described above, the case where the two-dimensional code 702 is provided in the grave has been described as an example. However, the two-dimensional code 702 may be provided in another place. For example, the two-dimensional code 702 can be provided in the funeral place, legal place, ossuary place, urn and Buddhist altar of the deceased (A). For such places and things, for example, the requester (C) check-in for the funeral place can be recorded by using the two-dimensional code 702 as in the case of the grave described above, or the requester ( For each C), the presence / absence of attendance at the funeral and the presence / absence / date / number of visits to the grave can be linked and stored.

Next, components of the SNS server 120 and the client terminal 110 for realizing the above-described contents will be described with reference to FIG. 11 and FIG.

FIG. 11 is a block diagram showing the SNS server 120. The SNS server 120 includes a network interface 1210, an arithmetic processing unit 1220, and a storage unit 1230. The network interface 1210 connects the SNS server 120 to the network 130. The arithmetic processing unit 1220 includes one or more processors, and is configured by a CPU, an MPU, or the like. The arithmetic processing unit 1220 operates various functional units by executing programs, modules, and / or instructions stored in the storage unit 1230 based on various inputs. This program or the like is stored in a storage medium such as a CD-ROM or a USB memory, or downloaded via the network 130 and installed in a computer. The arithmetic processing unit 1220 includes a reception unit 1221, a registration processing unit 1222, a presentation unit 1223, a determination unit 1224, and a transmission unit 1225 as various functional units.

The receiving unit 1221 receives various information via the network interface 1210. For example, the receiving unit 1221 sends a registration request (FIG. 2A: S204) of the manager (B) from the person or deceased person (A) who should be the manager, and the deceased person (from the manager (B) or the deceased person (A) ( The registration request for post-mortem information (A) (FIG. 2B: S224) is received. Further, the receiving unit 1221 sends a request for the deceased person (A) 's death information (FIG. 3: S302), an answer to the question (FIG. 3: S336), and a two-dimensional code password (FIG. 8: S806). ) And location information of the mobile terminal 710 (FIG. 8: S840).

The registration processing unit 1222 processes various registration requests received by the receiving unit 1221. For example, the registration processing unit 1222 processes the registration request of the manager (B) and the registration request of the deceased person (A) after death, and the storage unit 1230 stores the information of the manager (B) and the deceased person (A) after death. (FIG. 2A: S206, FIG. 2B: S226). The registration processing unit 1222 also processes account registration as a user to the SNS, and registers individual user information in the storage unit 1230. In addition, the registration processing unit 1222 also processes information related to the proxy service and registers the information in the storage unit 1230.

The presenting unit 1223 presents a response according to the SNS relationship between the requester (C) and the deceased (A) as a response to the request for the deceased information of the deceased (A) obtained from the requester (C). (FIG. 3: S304, 306). Specifically, the presentation unit 1223 identifies the relationship on the SNS between the requester (C) and the deceased (A) in order to present the content of the response to the request to the administrator (B). The corresponding response content is extracted from the storage unit 1230.

The determination unit 1224 determines various types of confirmation information received by the reception unit 1221. For example, the determination unit 1224 determines whether or not the answer from the requester (C) to the question satisfies a predetermined standard (FIG. 3: S338). In addition, the determination unit 1224 determines whether or not the two-dimensional code password input to the mobile terminal 710 is suitable (FIG. 8: S808), and whether or not the position of the mobile terminal 710 is within a predetermined range (for example, the requester (C) actually visits the tomb 700 and determines whether or not a password has been entered (FIG. 8: S842).

The transmission unit 1225 transmits various information via the network interface 1210. For example, the transmission unit 1225 transmits the result of processing of the registration request by the registration processing unit 1222 to inform the registration requester and related parties. For example, the transmitting unit 1225 confirms that the administrator has been registered for the deceased person (A) or the person who should become the administrator (FIG. 2A: S208), and the deceased person (A). Alternatively, a registration confirmation (FIG. 2B: S228) that the post-mortem information of the deceased (A) has been registered is transmitted to the manager (B). In addition, the transmission unit 1225 transmits the information presented by the presentation unit 1223, that is, the content of the answer according to the relationship on the SNS to the administrator (B) (FIG. 3: S306). In addition, the transmission unit 1225 transmits the response result based on the response content selected by the administrator (B) and the determination result determined by the determination unit 1224 to the administrator (B) or the requester (C). For example, the transmitter 1225 sends the requested post-submission information (FIG. 3: S318) to the requester (C), the request is rejected (FIG. 3: S324), or a predetermined question (FIG. 3). : S330) and a substitute service and a password for a two-dimensional code are transmitted together with post-mortem information (see: FIG. 6). The transmission unit 1225 transmits an answer to the question (FIG. 3: S350) and the determination result (FIG. 3: S344) to the manager (B), and also sends two answers to the requester (C). A determination result that the password of the dimension code is incompatible is transmitted (FIG. 8: S812). Furthermore, when the password is suitable, the transmission unit 1225 sends the requester (C) to the manager (B) where the two-dimensional code is installed (grave, funeral place, legal place, ossuary place) Etc.) (FIG. 8: S820), the requester (C) receives information about the deceased (A) to be displayed on the mobile terminal 710 (FIG. 8: S826. For example, FIG. 10). Web site).

The storage unit 1230 is configured by a storage device such as a hard disk drive, SSD, or RAM, and stores various programs necessary for executing processing in the arithmetic processing unit 1220, data required for executing various programs, and the like. The storage unit 1230 can include a nonvolatile memory, and the nonvolatile memory includes a non-transitory computer-readable storage medium. For example, the storage unit 1230 stores a user information DB 1232, a post-death use DB 1234, and a check-in DB 1236.

The user information DB 1232 stores SNS user information. For example, for each SNS user, the user information DB 1232 is an SNS account, an ID, a password, a profile, another connected user, a group to which the user belongs, a deceased, and whether it is an administrator. Are stored in association with each other. Therefore, the user information DB 1232 also stores the SNS relationship (for example, the table 400 in FIG. 4) between the deceased person who is one user and the requester who is another user.

The post-death use DB 1234 is for each deceased (A), information on the manager (B), post-death information of the deceased (A), contents of questions to the requester (C), contents of answers to this question, contents of proxy services, And 2D code information (whether or not the 2D code is provided in the grave etc., if provided, its password and installation location, and if provided, displayed by reading the 2D code) Various information such as information on the deceased person (eg, information such as the SNS site in FIG. 5A and the Web site 1000 in FIG. 10) is stored in association with each other.

For each deceased person (A), the check-in DB 1236 associates the requester (C) with a place where a two-dimensional code for the deceased person (A) is provided (the funeral place, legal place, grave and ossuary of the deceased person (A)) Whether or not the user has visited (checked in) or the like in association with the date and number of times. Therefore, the check-in DB 1236 also stores the table of FIG. The check-in DB 1236 is configured to be accessible to the administrator (B) via the network 130, and the administrator (B) visits the grave of the deceased (A) when and how often the user of the SNS. It is possible to appropriately confirm whether or not Note that the SNS server 120 uses the content recorded in the check-in DB 1236 to temporarily or regularly contact a user who has visited the place where the two-dimensional code is installed (for example, one round of excuses, It is also possible to send a notice of a third death, a mourning notice, etc.).

FIG. 12 is a block diagram showing the client terminal 110B of the administrator (B). The client terminal 110B is an information processing apparatus including a network interface 1300, a user interface 1310, an arithmetic processing unit 1320, and a storage unit 1330. The network interface 1300 connects the client terminal 110B to the network 130.

The user interface 1310 includes an input unit 1312 and a display unit 1314. The input unit 1312 receives an input / operation from the administrator (B), and includes, for example, a keyboard, a touch panel, a voice input device, and the like. The display unit 1314 displays images such as the presented answer contents (a plurality of options) on the screen, and is configured by various displays such as liquid crystal. Note that the display unit 1314 can constitute a touch panel, and the display unit 1314 can function as an input unit.

The arithmetic processing unit 1320 includes one or more processors, and is configured by a CPU, an MPU, or the like. The arithmetic processing unit 1320 operates various functional units by executing programs, modules, and / or instructions stored in the storage unit 1330 based on various inputs. This program or the like is stored in a storage medium such as a CD-ROM or a USB memory, or downloaded via the network 130 and installed in a computer. The arithmetic processing unit 1320 includes a receiving unit 1322 and a transmitting unit 1324 as various functional units.

The receiving unit 1322 receives various information from the SNS server 120 via the network interface 1300. For example, the reception unit 1322 performs registration confirmation that the administrator is registered in the SNS server 120 (FIG. 2A: S210) and registration confirmation that the post-mortem information is registered in the SNS server 120 (FIG. 2B: S230). Receive. The receiving unit 1322 receives the response content (a plurality of options) according to the relationship on the SNS presented from the SNS server 120 (FIG. 3: S308). Further, the receiving unit 1322 receives the answer when the requester (C) answers the question (FIG. 3: S352), and when the SNS server 120 determines the answer, the determination result is displayed. Receive (FIG. 3: S346). In addition, if the two-dimensional code password used by the requester (C) is compatible, the receiving unit 1322 receives information that the requester (C) has checked in to the two-dimensional code installation location. (FIG. 8: S822).

The transmission unit 1324 transmits various types of information via the network interface 1300. For example, the transmission unit 1324 transmits an administrator (B) registration request (FIG. 2A: S202) and a post-death information registration request (FIG. 2B: S220) to the SNS server 120. Further, the transmission unit 1324 transmits the selection result of the answer contents selected by the administrator (B) (permission, rejection or question) to the SNS server 120 (FIG. 3: S316, S322, S328), In addition to sending the selection result of the response content options (allowed or rejected) selected by the administrator (B) for the answer to the requester (C) question (FIG. 3: S356, 358).

The storage unit 1330 is configured by a storage device such as a hard disk drive, SSD, or RAM, and stores various programs necessary for executing processing in the arithmetic processing unit 1320, data necessary for executing various programs, and the like. The storage unit 1330 can include a nonvolatile memory, and the nonvolatile memory includes a non-transitory computer-readable storage medium. The storage unit 1330 stores software (for example, a web browser or an application) for using the SNS provided by the SNS server 120. The storage unit 1330 temporarily stores various information transmitted from the SNS server 120.

The SNS server 120 of the present embodiment described above provides an SNS including a requester (C) as a first user and an administrator (B) managing an SNS account for the deceased (A) as users. SNS server 120 that receives a request for information related to the deceased person (A) after death from the requester (C), the first user, A presentation unit 1223 that presents to the administrator (B) information corresponding to the SNS relationship between the requester (C) who is a user and the deceased (A).

Further, the information processing apparatus 110B of the administrator (B) of this embodiment is connected to the SNS server 120 that provides SNS to the user via the network 130, and manages the SNS account for the deceased (A). (B) the information processing apparatus 110B, which transmits information related to the death of the deceased (A) to the SNS server 120 for registration, and a first user (requester (user) who is one of the users. C)), when a request for information registered in the SNS server 120 is made, the first user (requester (C)) and the deceased (A) as the response content to the request from the SNS server 120 And a receiving unit 1322 for receiving the response content presented according to the relationship on the SNS.

According to such an embodiment, information related to the death of the deceased can be shared on the SNS within an appropriate range.

The embodiments of the present invention have been described above with reference to specific examples. The above specific examples are illustrations for explaining the present invention, and are not intended to limit the present invention only to the embodiments. In other words, those specific examples that have been appropriately modified by those skilled in the art are also included in the scope of the present invention as long as they have the characteristics of the present invention. For example, the elements and the like included in each of the specific examples described above are not limited to those illustrated, but can be changed as appropriate.

For example, in the above embodiment, the case where the deceased person (A) registered the SNS account for the deceased person (A) himself before life and was one of the SNS users before his life was explained. However, even if the deceased (A) was not a SNS user before his life, the administrator (B) registers an SNS account for the deceased (A) and manages the SNS account as described above. Can be applied. In other words, the above-mentioned “SNS account for the deceased (A)” refers to the SNS account that the deceased (A) registered before birth, the SNS account that was transferred from this SNS account, and the deceased (A) It also includes an SNS account registered by the administrator (B) for the deceased (A) before or after death.

In addition, the deceased (A) may be configured to automatically or manually classify users who have connections on the SNS before life, and the above questions are presented according to the classified categories. It may be.

Claims

An SNS server for providing an SNS including a first user and an administrator who manages an SNS account for a deceased user,
A receiving unit that receives a request for information related to the deceased's death from the first user;
As a response content to the request, a presentation unit that presents to the administrator what is in accordance with the SNS relationship between the first user and the deceased,
An SNS server comprising:
The SNS server according to claim 1, wherein the information related to the deceased's death includes information on at least one of the deceased's funeral, a legal affair and a grave.
The content in the deceased SNS account includes a field for accepting the request,
The SNS server according to claim 1 or 2, wherein the receiving unit receives the request when the first user inputs the field.
If the relationship on the SNS is that the deceased has allowed the first user to transmit information related to his / her death after the death on the SNS,
4. The display unit according to claim 1, wherein the presenting unit presents, to the administrator, an option that permits the first user to provide information related to the deceased as a response to the request. 5. Item SNS server.
The first user and the deceased belong together in a group created on the SNS;
The SNS server according to claim 4, wherein the group permits a group member to transmit information related to his / her death after death to another group member.
The relationship on the SNS does not permit the deceased on the SNS to transmit information related to the death of the deceased to the first user before the life of the deceased. If you have a connection in
The SNS server according to any one of claims 1 to 3, wherein the presenting unit presents an option for asking a question about the deceased to the administrator as a response content to the request.
In response to the administrator selecting the option, the transmitter includes a transmitter that transmits the question to the first user,
If the answer by the first user to the question meets a predetermined criterion,
The SNS server according to claim 6, wherein the presenting unit presents the manager with an option that allows the first user to provide information related to the deceased person's death.
The SNS server according to claim 7, further comprising a determination unit that determines whether an answer to the question by the first user satisfies a predetermined criterion.
The SNS server according to claim 6, wherein the presenting unit also presents, to the administrator, an option that allows the first user to provide information related to the deceased as a response to the request.
When the first user and the deceased share at least one category among a plurality of categories in each other's profile on the SNS,
The SNS server according to any one of claims 6 to 9, wherein the presenting unit presents the question according to at least one common category.
The relationship on the SNS is that the deceased does not have a connection on the SNS with the first user, but the contact information of the deceased that the SNS server can access and the SNS server can access If the first user is included in at least one of the administrator's contacts,
The SNS server according to any one of claims 1 to 3, wherein the presenting unit presents an option for asking a question about the deceased to the administrator as a response content to the request.
In response to the administrator selecting the option, the transmitter includes a transmitter that transmits the question to the first user,
If the answer by the first user to the question meets a predetermined criterion,
The SNS server according to claim 11, wherein the presenting unit presents the administrator with an option that allows the first user to provide information related to the death of the deceased.
The SNS server according to claim 12, further comprising a determination unit configured to determine whether an answer by the first user to the question satisfies a predetermined criterion.
The SNS server according to claim 11, wherein the presenting unit presents, to the manager, an option that allows the first user to provide information related to the deceased as a response to the request.
The relationship on the SNS is that the deceased has no connection with the first user on the SNS, and the contact information of the deceased that the SNS server can access and the SNS server can access. If the administrator contact does not include the first user,
The SNS server according to any one of claims 1 to 3, wherein the presenting unit presents the manager with an option of refusing to convey information related to the deceased's death to the first user.
The SNS server according to claim 15, further comprising a transmission unit configured to transmit to the first user that the request has been rejected in response to the administrator selecting the option.
The presenting unit is one or more of an option that allows transmission of information related to the deceased person's death, an option of rejecting information related to the deceased person's death, and an option for asking a question about the deceased person The SNS server according to any one of claims 1 to 3, wherein the option is presented to the administrator according to a relationship on the SNS.
18. The transmitter further comprising: a transmission unit configured to transmit, to the first user, an answer content from the manager based on an option selected by the manager from the one or more presented options. The SNS server as described in.
The information processing apparatus according to claim 1, further comprising: a transmission unit configured to transmit information related to the deceased person's death to the first user when the information related to the deceased person's death is permitted to be provided to the first user. The SNS server according to any one of 1 to 3.
The SNS server according to claim 19, wherein the transmission unit transmits information related to a proxy service that the first user can request together with information related to the death of the deceased.
At least one of the deceased funeral place, legal place, grave, ossuary, urn and altar is provided with a two-dimensional code for the deceased,
The SNS server according to claim 19 or 20, wherein the transmission unit transmits a password of the two-dimensional code to the first user together with information related to the death of the deceased.
When the first user reads the two-dimensional code and inputs the password using a mobile terminal capable of communicating with the SNS server via a network, the transmission unit notifies the administrator to that effect. The SNS server according to claim 21, which transmits.
When the first user reads the two-dimensional code and inputs the password using a mobile terminal that can communicate with the SNS server via a network, the first user further includes a storage unit that stores the fact The SNS server according to claim 21.
24. The SNS server according to claim 23, wherein the storage unit stores at least one of a date and time and a number of times when the first user reads the two-dimensional code via a mobile terminal and inputs the password.
The SNS server according to claim 23 or 24, wherein the storage unit is configured to be accessible to the administrator.
When the first user reads the two-dimensional code and inputs the password using a mobile terminal capable of communicating with the SNS server via a network, the transmission unit transmits information on the deceased The SNS server according to claim 21, wherein information to be displayed on a mobile terminal is transmitted to the mobile terminal.
27. The SNS server according to claim 26, wherein the information regarding the deceased includes an SNS site associated with the deceased SNS account.
27. The SNS server according to claim 26, wherein the information regarding the deceased is a website created for the deceased separately from an SNS site associated with the deceased SNS account.
Information related to the deceased's death is information on the tomb of the deceased,
29. The transmission unit according to any one of claims 19 to 28, wherein the transmission unit transmits at least a location of the grave and a photograph of the grave in the cemetery to the first user as information relating to the death of the deceased. SNS server.
30. The SNS server according to any one of claims 1 to 29, further comprising a storage unit that stores a relationship on the SNS.
The deceased is one of the users of the SNS before life,
The SNS server according to any one of claims 1 to 30, wherein the deceased SNS account is registered by the deceased before birth.
A method executed by an SNS server that provides an SNS including a first user and an administrator who manages an SNS account for a deceased user,
Receiving a request from the first user for information relating to the deceased's death;
As an answer content to the request, presenting to the administrator what is in accordance with the SNS relationship between the first user and the deceased,
A method performed by an SNS server, comprising:
To the SNS server that provides the SNS including the first user and the administrator who manages the SNS account for the deceased,
Receiving a request from the first user for information relating to the deceased's death;
As an answer content to the request, presenting to the administrator what is in accordance with the SNS relationship between the first user and the deceased,
A program that executes
An information processing device for an administrator connected to an SNS server that provides SNS to a user via a network and managing an SNS account for the deceased,
A transmitter for transmitting information related to the deceased's death to the SNS server for registration;
When a request for the information registered in the SNS server is made by a first user who is one of the users, the first user and the deceased as response contents to the request from the SNS server. A receiving unit for receiving the response content presented according to the relationship on the SNS with
An information processing device for an administrator.
35. The information processing apparatus for an administrator according to claim 34, wherein the information includes information related to at least one of the deceased funeral, a legal affair, and a grave.
If the relationship on the SNS is that the deceasor has allowed the SNS to live on the SNS to convey the information to the first user,
36. The information processing apparatus for an administrator according to claim 34 or 35, wherein the reply content received by the reception unit includes an option that permits the information to be provided to the first user.
Although the relationship on the SNS does not permit the deceased to transmit the information to the first user before the SNS, the deceased has no connection with the first user on the SNS. If you have
36. The information processing apparatus for an administrator according to claim 34 or 35, wherein the answer content received by the receiving unit includes an option for asking a question regarding the deceased.
The relationship on the SNS is that the deceased does not have a connection on the SNS with the first user, but the contact information of the deceased that the SNS server can access and the SNS server can access If the first user is included in at least one of the administrator's contacts,
36. The information processing apparatus for an administrator according to claim 34 or 35, wherein the answer content received by the receiving unit includes an option for asking a question regarding the deceased.
The relationship on the SNS is that the deceased has no connection with the first user on the SNS, and the contact information of the deceased that the SNS server can access and the SNS server can access. If the administrator contact does not include the first user,
36. The information processing apparatus according to claim 34 or 35, wherein the reply content received by the receiving unit includes an option of refusing to convey the information to the first user.
At least one of the deceased funeral place, legal place, grave, ossuary, urn and Buddhist altar is provided with a two-dimensional code for the deceased that requires a password,
When the first user reads the two-dimensional code and inputs the password using a mobile terminal that can communicate with the SNS server via a network, the receiving unit informs the SNS server of that fact. 40. The information processing apparatus for the manager according to any one of claims 34 to 39, which is received from
A method connected to an SNS server that provides SNS to a user via a network and executed by an information processing device of an administrator who manages an SNS account for the deceased,
Sending information related to the deceased's death to the SNS server for registration;
When a request for the information registered in the SNS server is made by a first user who is one of the users, the first user and the deceased as response contents to the request from the SNS server. Receiving the response content presented according to the relationship on the SNS with
A method executed by an information processing apparatus of an administrator.
An information processing device connected to an SNS server that provides SNS to users via a network and managing an SNS account for the deceased,
Sending information related to the deceased's death to the SNS server for registration;
When a request for the information registered in the SNS server is made by a first user who is one of the users, the first user and the deceased as response contents to the request from the SNS server. Receiving the response content presented according to the relationship on the SNS with
A program that executes