JP6813174B2 - SNS server, method executed by SNS server, information processing device of administrator, method executed by information processing device of administrator, program - Google Patents

Description

The present invention relates to a technology of an SNS server that provides an 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 can be difficult to find the contact information. It is convenient if the deceased is a user of SNS such as Facebook (registered trademark) and has posted grave information on his SNS site. However, since graves are generally created after death, information on graves cannot be posted on their SNS site before they are alive. On the other hand, after the death, not only the deceased but also a third party cannot log in to the deceased's SNS account, so that the grave information cannot be posted on the deceased's SNS site as well.

However, there is also an SNS that can set an account manager who manages the account of the deceased (see: Non-Patent Document 1, pp. 182 to 183).

Link up "Facebook Facebook Smart Guide Starting from Zero" (Technical Review, First Edition, 2016)

However, it is not always desirable for the account manager to post the grave information as it is on the deceased's SNS site. For example, if anyone can see the location of the deceased's grave, the information may be transmitted to those who the bereaved family does not want to convey such information, depending on the relationship with the deceased.

Therefore, an object of the present invention is to provide a technology of an SNS server capable of sharing information related to the death of a deceased person in an appropriate range.

The SNS server according to one 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 the deceased, and the deceased from the first user. It is provided with a receiving unit that receives a request for information related to the death of the user, and a presenting unit that presents to the administrator a response content to the request according to the SNS relationship between the first user and the deceased.

The method executed by the SNS server according to one aspect of the present invention is a method executed by an SNS server that provides an SNS including a first user and an administrator who manages an SNS account for the deceased. Therefore, the step of receiving a request for information related to the deceased's death from the first user and the content of the response to the request according to the SNS relationship between the first user and the deceased are given to the administrator. Includes steps to present.

A program according to one aspect of the present invention provides an SNS server that provides an SNS including a first user and an administrator who manages an SNS account for the deceased, from the first user after the death of the deceased. It is made to receive a request for requesting related information and to present to an administrator a response content to the request according to the relationship between the first user and the deceased person on the SNS.

The administrator's information processing device according to one aspect of the present invention is an administrator's information processing device 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 transmitter that sends information related to the death of the deceased to the SNS server for registration and a first user who is one of the users requests the information registered in the SNS server, the SNS server As a response content to the request, a receiving unit that receives the response content presented according to the SNS relationship between the first user and the deceased is provided.

The method executed by the administrator's information processing device according to one aspect of the present invention is the information processing of the administrator who manages the SNS account for the deceased by being connected to the SNS server that provides the SNS to the user via the network. A method executed by the device, in which a step of transmitting information related to the death of the deceased to the SNS server for registration and a request for information registered in the SNS server from a first user who is one of the users. When this is done, the step of receiving the response content presented from the SNS server according to the SNS relationship between the first user and the deceased as the response content to the request is included.

The program according to one aspect of the present invention is connected to an SNS server that provides an SNS to a user via a network, and sends information related to the death of the deceased to an information processing device of an administrator who manages an SNS account for the deceased. When a request is made to send to the SNS server for registration and to request the information registered in the SNS server from the first user who is one of the users, the first user responds to the request from the SNS server. Receiving the content of the answer presented according to the SNS relationship between the user and the deceased, and executing.

According to the present invention, information related to the death of the deceased can be shared to an appropriate extent.

It is the schematic of the information processing system including the SNS server which concerns on embodiment. FIG. 1 is a flow chart showing a registration process in the information processing system of FIG. 1, (a) is a flow chart for registering an administrator, and (b) is a flow chart for registering post-mortem information of a deceased person. It is a flow chart which shows the process of sharing information after the death of a deceased person in the information processing system of FIG. It is a figure which shows an example of the table which shows the relationship on SNS between a requester and a deceased person used in the process of FIG. It is a schematic diagram which shows an example of the screen appearing in the process of FIGS. 2 and 3, (a) is the screen of the SNS site of the deceased, (b) is the screen of the administrator, (c) the screen of the requester, (d) management. Screen, (e) administrator screen, (f) administrator screen. It is a schematic diagram which shows an example of the screen of the requester when the information after the death of a deceased person is received in the process of FIG. It is a schematic diagram which shows the grave provided with the two-dimensional code and the information processing system which concerns on embodiment. It is a flow chart which shows the reading processing process when the information processing system of FIG. 7 read a two-dimensional code. It is a figure which shows an example of the table which recorded the check-in of the requester to the grave provided with the 2D code in the reading process of FIG. 7. It is a schematic diagram which shows an example of the website appearing on the screen of the 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 above.

As shown in FIG. 1, the information processing system 100 has a plurality of client terminals 110A, 110B, 110C-1, 110C-2, ... 110C-N (hereinafter, may be collectively referred to as "110"). And the SNS server 120 is configured to be connectable to the network 130. The network 130 is composed of a LAN, a WAN, a wired or wireless network, the Internet, or the like.

The client terminal 110 can be composed of a communication device or a computer having a display screen, for example, a desktop type, a laptop type or a tablet type computer, a PDA, a mobile phone or a smartphone. The client terminal 110 has software (for example, a web browser or 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 deceased (A) client terminal 110A, the administrator (B) client terminal 110B, and the requester (C1, C2, ... CN. Hereinafter, collectively It is divided into client terminals 110C-1, 110C-2, ... 110C-N, which may be referred to as "C"). The deceased person (A), the administrator (B), and the requester (C) are users who are registered as members or registered in the SNS provided by the SNS server 120. The client terminal 110A of the deceased (A) was used by the deceased (A) to use his / her own SNS site before he / she was alive. 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, the bereaved family or friend of the deceased (A), as well as an agent (funeral trader, law trader, stone trader, cemetery trader, etc.). The client terminals 110C-1, 110C-2, ... 110C-N of the requester (C1, C2, ... CN) allow the requester (C1, C2, ... CN) to request post-mortem information of the deceased (A). It is to be used.

The SNS server 120 is an information processing device that provides an SNS function to the client terminal 110. The SNS server 120 stores information on users who use the SNS function. The user information to be stored includes, for example, an ID and password for the user to log in to his / her SNS account, a profile such as date of birth, birthplace, high school, university, work history and hobbies, and the user. It is possible to include the group to which the member belongs. In addition, this profile or group can include various items, and it is possible to set the disclosure range for each item. Then, on the user's SNS site displayed by logging in to the SNS account, it is possible for SNS users to set up a connection, and it is also possible for SNS users to create a group. Is. Further, the SNS server 120 may be configured to be able to access contacts stored or registered by the user regarding software other than the software for using the SNS. Details will be described later in FIG. 11, but in addition to the above user information, the SNS server 120 includes information on the administrator (B), post-mortem information on the deceased (A), and the deceased (A) and the requester. Stores information about the relationship on SNS with (C).

FIG. 2A is a flow chart showing a process of registering an administrator (B) who manages an SNS account for the deceased person (A). When the deceased (A) registers the administrator (B) who manages his / her SNS account after his / her death, he / she sends the request to the SNS server 120 (S200). If the deceased (A) did not register before his / her life, the person who should become the administrator (B) sends an administrator registration request to the SNS server 120 after the death of the deceased (A) (S202). The SNS server 120 receives the SNS account registration request 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 the administrator registration before he / she is alive, the registration confirmation is also sent to the deceased person (A), and the deceased person (A) receives this (S212). 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 service provider or the like to send a registration request to the administrator (B) to designate the bereaved family of the deceased to the SNS server 120.

FIG. 2B is a flow chart showing a process of 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 posthumous information before he / she is alive, the request can be transmitted to the SNS server 120 (S222). For example, if the grave already exists, the deceased (A) can send a request for registration of his / her grave information to the SNS server 120 before he / she is alive. The SNS server 120 receives the post-mortem information registration request (S224) and registers the post-mortem information (S226). Then, the SNS server 120 transmits the registration confirmation to the administrator (B) (S228), and the administrator (B) receives this (S230). As a result, the administrator (B) can confirm that the post-mortem information of the deceased (A) is registered in the SNS server 120. When the deceased person (A) requests the registration of his / her posthumous information before he / she is alive, the registration confirmation is also sent to the deceased person (A), and the deceased person (A) receives this (S232). The post-mortem information of the deceased (A) registered in the SNS server 120 is set to be private.

Here, the post-mortem information of the deceased (A) means information related to the post-mortem of the deceased (A), and may include, for example, information regarding at least one of the funeral, the litigation, and the grave of the deceased (A). Specifically, the information about the funeral is information about the date and time, place, mourner, form, etc. of the funeral. Information about the litigation is information about the date and time of the litigation, the place, the organizer, the presence or absence of meals, and the like. Information about the grave is information about the location of the grave.

FIG. 3 is a flow chart showing the process of sharing post-mortem information of the deceased (A). This process starts when the requester (C) sends a request for post-mortem information of the deceased (A) to the SNS server 120 (S300). The SNS server 120 receives the post-mortem information request (S302) and identifies the SNS relationship between the requester (C) and the deceased (A) (S304). For example, the SNS server 120 identifies that the requester (C) has a connection with the deceased (A) on the SNS, or the requester (C) has a special group or category on the SNS with the deceased (A). Identify that it belongs to. As a result, the SNS server 120 transmits the answer contents according to the specified SNS relationship to the administrator (B) in order to present the answer contents to the request to the administrator (B) (S306). The administrator (B) receives the presented response content (S308). The presented answers include the option of allowing the deceased (A) to convey post-mortem information (S310), the option of refusing this (S312), and the option of asking a question about the deceased (A) (S314). , One or more according to the relationship on SNS are included.

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

Alternatively, if the administrator (B) selects the question option (S314), that fact is transmitted to the SNS server 120 (S328). In response to this, the SNS server 120 sends a question about 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 meets the predetermined criteria. (S338). A predetermined criterion can be whether or not there is an answer, or when a score is given to the answer, whether or not the score is equal to or higher than a predetermined value. When the predetermined criterion is satisfied (S340), the SNS server 120 transmits the requested post-mortem information to the requester (C) (S318). If the predetermined criteria are not satisfied (S342), the SNS server 120 transmits a request rejection to the requester (C) (S324). Further, in any case, the SNS server 120 transmits the determination result of the answer to the administrator (B) (S344), and the administrator (B) receives this (S346). Therefore, the administrator (B) can confirm whether or not the post-mortem information has been transmitted to the requester (C) who asked the question.

In another embodiment, as shown by the broken line in FIG. 3, the answer to the question may be transmitted to the administrator (B) (S350) so that the answer is not determined by the SNS server 120. That is, the decision subject of the answer may be the administrator (B). In this case, when the administrator (B) receives the reply (S352), he / she is presented with an option (S354) for permitting the transmission of post-mortem information of the deceased (A) and an option (S356) for rejecting the answer. When the permission option is selected by the judgment of the administrator (B), that fact is transmitted to the SNS server 120 (S358), and the post-mortem information is transmitted from the SNS server 120 to the requester (C) (S318). .. On the other hand, when the rejection option is selected by the judgment of the administrator (B), that fact is transmitted to the SNS server 120 (S360), and the request rejection is transmitted from the SNS server 120 to the requester (C). (S324).

As described above, in the present embodiment, the requester (C) receives a request for post-mortem information of the deceased person (A) using the SNS, and the requester (C) and the deceased person (A) respond to the request. The content of the answer according to the relationship on SNS with the administrator (B) is presented. As a result, even if the requester (C) does not know the contact information of the bereaved family of the deceased (A), or even if such contact information is known, the situation is not explained to the bereaved family. It is convenient because you can ask for post-mortem information of the deceased (A) on SNS. Also, for the administrator (B), it is a judgment material on how to respond to the request without knowing what kind of relationship the requester (C) had with the deceased (A) in his lifetime. Is presented, so that post-mortem information of the deceased (A) can be provided to an appropriate range.

FIG. 4 is a diagram showing an example of a table 400 showing the relationship between the requester (C) and the deceased (A) on SNS. 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, requesters C1 to C4 have a connection with the deceased (A) on SNS. This connection is set, for example, by one of requests C1 to C4 and the deceased (A) sending a connection application to the other and the other permitting the connection application.

Requester C1 also belongs to the same group as the deceased (A). This group was created on SNS by requester C1, the deceased (A) or another group member, in which the group member is informed of his or her post-mortem information to other group members. Allows to. That is, since the requester C1 and the deceased (A) belong to this group, the deceased (A) is permitted on the SNS to convey his / her post-mortem information to the requester C1 before he / she is alive. In another embodiment, the deceased person (A) can individually set such a living permit for the requester C1 without belonging to such a group. In view of such attributes of the requester C1, the SNS server 120 provides an option (FIG. 3: S310) that allows at least the post-mortem information of the deceased (A) to be transmitted as the response content 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 (A) does not allow the requester (C2 to C4) to convey his / her post-mortem information before he / she is alive on SNS. Requesters C2 and C3 share a common profile on SNS with respect to the 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, requester C4 does not have a category that shares a profile with the deceased (A) on SNS. In view of such attributes of requesters C2 to C4, the SNS server 120 manages at least an option (FIG. 3: S314) for asking a question about the deceased (A) as the content of the response to the request from requesters C2 to C4. Present to person (B). Questions for requesters C2 and C3 are presented according to common categories a and b. 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, the question to the requester C4 can be a question about more general or private contents, such as the hobby, special skill, and welfare activity of the deceased (A). If there are a plurality of common categories, questions may be presented according to one or more categories.

Requesters C5 and C6 do not have an SNS connection with the deceased (A), but the contact information of the deceased (A) accessible to the SNS server 120 and management accessible to the SNS server 120, respectively. A person included in the contact information of person (B). These contacts are related to software other than the software for using SNS provided by the SNS server 120, and the deceased (A) or the administrator (B) has personal information (name, address, telephone number, etc.) of another person. The contact that saved or registered the e-mail, etc.). In view of such attributes of the requesters C5 and C6, the SNS server 120 manages at least an option (FIG. 3: S314) for asking a question about the deceased (A) as a response content to the request from the requesters C5 and C6. Present to person (B). As the question for the requesters C5 and C6, the same question as the question for the requester C4 may be presented, but the question is more difficult than the question for the requester C4, or the deceased person (A). ) May be a private question.

Requester C7 has no connection with the deceased (A) on the SNS, and is included in both the contacts of the deceased (A) and the administrator (B) that the SNS server 120 can access. There is 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 to the SNS server 120. In view of such attributes of the requester C7, the SNS server 120 provides at least an option of refusing to convey the post-mortem information of the deceased person (A) as the response content to the request from the requester C7 (FIG. 3: S312). Present it to the administrator (B).

FIG. 5 is a schematic diagram showing an example of a screen appearing in the process of FIGS. 2 and 3. FIG. 5A shows the screen of the SNS site of the deceased person (A). This SNS site is associated with the SNS account for the deceased (A), and displays the contents in this SNS account. This content includes a field 500 indicating the identifier (name and photo) of the deceased (A), a field 502 leading to the profile of the deceased (A), and an administrator-only field 504 for the administrator (B) to log in. It includes 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 post-mortem information of the deceased (A). The administrator (B) can manage the SNS account for the deceased (A) by logging in through the administrator-only field 504. For example, the administrator (B) can register post-mortem information of the deceased (A) and other related information (such as information on a proxy service described later) through the administrator-only field 504. 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 post-mortem information of the deceased (A). The screen displays fields 510, 512 and 514 for entering information about funerals, ceremonies and tombs, respectively. For example, the administrator (B) can register the location of the deceased (A)'s grave through field 514 of the grave. The manager (B) can also register a photograph of the deceased (A)'s grave in the reien through the grave field 514. A requester who wants to visit the grave of the deceased (A) will be able to easily find the grave of the deceased (A) not only by the location of the grave but also by having a photograph of the grave in the reien. The screen of FIG. 5B appears, for example, at S220 of FIG. 2B.

FIG. 5 (c) shows the screen of the requester (C) displayed when the requester (C) inputs (clicks or taps) into the field 508 (post-mortem information request) of FIG. 5 (a). There is. The screen displays fields 520, 522, and 524 that accept requests for information about funerals, ceremonies, and tombs. When the requester (C) inputs (clicks or taps) any of the fields 520, 522, and 524, the corresponding request is transmitted to the SNS server 120. The field 508 can be, for example, an icon, a box, a link, or the like, and accepts a request from the requester (C).

5 (d) to 5 (f) show the screen of the administrator (B) when the response contents to the request from the requester (C) are presented from the SNS server 120, respectively. As described above, the administrator (B) receives from the SNS server 120 what is presented as the response content to the request according to the SNS relationship between the requester (C) and the deceased (A). As shown in FIGS. 5 (d) to 5 (f), the message received by the administrator (B) includes an area 530 indicating from which requester (C) the request was made, the requester (C) and the deceased (A). ) Is included in the area 532 indicating the SNS relationship (attribute of the requester (C)) and the area 534 indicating one or more options.

As shown in FIG. 5 (d), when the requester (C) corresponds to the requester C1 in FIG. 4, an option 540 that allows the provision of post-mortem information is displayed. On the other hand, as shown in FIG. 5 (e), when the requester (C) corresponds to any of the requesters C2 to C6 in FIG. 4, the option 542 for asking a question about the deceased (A) is displayed. At the same time, the permission option 540 is also displayed. By presenting the two options 540 and 542, "question" and "permission" in this way, post-mortem information can be provided when the administrator (B) knows the requester (C) well and does not need to ask a question. It will be possible to promptly provide it to the requester (C). Further, as shown in FIG. 5 (f), when the requester (C) corresponds to the requester C7 in FIG. 4, the option 544 that refuses to provide the post-mortem information is displayed, and the question is asked. Option 542 is also displayed. By presenting the two options 542 and 544, "rejection" and "question" in this way, the administrator (B) has no data connection with the requester (C), but the requester ( If you know C), you don't have to reject the request. The screens of FIGS. 5 (d) to 5 (f) appear, for example, in S308 of FIG.

FIG. 6 is a schematic view showing an example of the screen of the requester (C) when the post-mortem information of the deceased (A) is received. This screen appears, for example, at S320 in FIG. That is, it is displayed when the post-mortem information of the deceased (A) is permitted to be provided to the requester (C). In FIGS. 6 to 10, the case where the information about the grave is requested as the post-mortem information will be described as an example, but the same applies when the information about the funeral or the legal affairs is requested.

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

The agency service area 604 is an area for displaying information about the agency service that the requester (C) can request. Such information includes, for example, another person 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. It includes information about cleaning agents, offering flowers and incense sticks to the grave of the deceased (A), and purchasing flowers and incense sticks. By transmitting and providing the information on the agency service to the requester (C) together with the post-mortem information, the convenience of the requester (C) can be provided. For example, the requester (C) uses the purchase agency service to place an order for flowers before visiting the grave, and a place near the grave (convenience store, a shop such as a flower shop that actually ordered, or a reien with a grave). You will be able to receive the flowers ordered in). Information about such a proxy service can be registered in the SNS server 120 at the request or input from the administrator (B). For example, a flower shop near the grave of the deceased (A) can be registered as information on behalf of the purchaser. The timing for registering such information may be, for example, when requesting the registration of post-mortem information of the deceased (A) (see: S220 in FIG. 2 (b)), or after that (for example, only for the administrator in FIG. 5). When using field 504).

The password area 606 is an area for displaying information related to the password of the two-dimensional code. This area also contains content that explains why the password is given. As described in this explanation, the deceased (A)'s grave or ossuary (reien) is provided with 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 visits the grave can see the information about the deceased (A). By sending and providing this password to the requester (C) together with the post-mortem information, the requester (C) will be provided with the added value of visiting the grave, and the administrator (B) will be provided with information on the visitor's visit to the grave. Can be done. This will be described next. The password area 606 is automatically set in the SNS server 120 when a two-dimensional code is provided in the grave of the deceased (A) or the like is registered in the SNS server 120 by a request or input from the administrator (B). It is preferable to configure the SNS server 120 so as to create the SNS server 120.

FIG. 7 is a schematic view showing a grave provided with a two-dimensional code and an information processing system 100. The grave 700 of the deceased (A) is provided with a two-dimensional code 702 for the deceased (A) who requires 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 gravestone trader and provided in the grave 700, but as described above, such a gravestone trader may serve as the manager (B). The requester (C) has a mobile terminal 710 such as a smartphone as the client terminal 110 described above. The mobile terminal 710 has a function of displaying information, a function as a reader for reading the two-dimensional code 702, a function of inputting a password, a function of communicating with the SNS server 120 via the network 130, and using GPS or the like. It has software to realize various functions such as the function to measure the position of the machine.

FIG. 8 is a flow chart showing a two-dimensional code reading process. First, when the requester (C) reads the two-dimensional code 702 locally using the mobile terminal 710 (S800), the mobile terminal 710 displays a screen for entering a password (S802). When the requester (C) further inputs the password using the mobile terminal 710 (S804), the password information is transmitted to the SNS server 120. The SNS server 120 receives the password information (S806) and determines whether or not the received password matches (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 incorrect through the mobile terminal 710 (S814) that receives this. Or you realize that you accidentally came to someone else's grave.

On the other hand, if it is determined that the password is correct (S816), the SNS server 120 remembers that the requester (C) has checked in to the grave of the deceased (A) (S818), and that fact. 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 (S822) that has received this. The check-in may be automatically posted on the SNS site associated with the SNS account for the deceased (A). If it is determined that the password is compatible (S816), the SNS server 120 transmits information to the mobile terminal 710 for displaying information about the deceased (A) on 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, or the deceased. You can also strengthen your feelings for (A).

Here, the information about the deceased (A) displayed on the mobile terminal 710 can be an SNS site (for example, the screen of FIG. 5 (a)) associated with the SNS account for the deceased (A). Apart from this SNS site, it can also be a website created for the deceased (A). Such SNS sites or websites can contain various information, for example, the profile of the deceased (A), a photograph, the date and time of death, the age at the time of death, the cause of death, the Dharma name, the date of burial, and the message before life. In addition to the family chart, information on other people and animals buried in the grave, grave information such as the stone material and design of the grave and the process of making the grave, and information on the same agency service as above are also included. be able to. Such information may be not only characters and images but also moving images. Taking advantage of the fact that such information can be seen by visiting the grave, it is possible not to engrave anything in the epitaph. This is desirable for people who do not want to make their personal information public.

In another embodiment, as shown by the broken line in FIG. 8, the SNS server 120 may receive the location information of the mobile terminal 710 as well as the password information (S840). Then, the SNS server 120 may use the received location 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 visited the grave 700 and has entered the password. Then, when the SNS server 120 determines that the requester (C) has not actually visited the grave 700, the SNS server 120 does not execute the step (S818, S820, S826) when the above password is matched, and the password May be determined to be non-conforming (S810). As a result, only those who actually visit 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 Table 900 showing the check-in record of the requester (C) for the grave 700. This table 900 is recorded and updated, for example, in the check-in recording step (S818) of FIG. 8, and is stored in the SNS server 120. Table 900 stores the date and time of visit to the grave 700 and the total number of visits in association with the requester (C). For example, it is remembered that the requester C1 has read the two-dimensional code 702 of the grave 700 and entered the password twice in total, on January 1, 2016 and July 1, 2016.

FIG. 10 shows an example of the screen of the mobile terminal 710 of the requester (C) on which the website 1000 created for the deceased (A) is displayed. This screen appears, for example, during the display step (S830) of FIG. In this website 1000, along with the title 1002, fields 1004, 1006, 1008 connected to the profile of the deceased (A), the grave information, and the agency service by clicking or tapping are displayed. Therefore, for example, when the field 1006 of the grave information is selected on the mobile terminal 710, the type and design of the stone material of the grave 700, the process of making the grave 700, the contractor involved in the construction of the grave 700, and the like are displayed.

In the example 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, but the two-dimensional code 702 may be provided in another place. For example, the two-dimensional code 702 can be provided at the funeral place, the legal place, the ossuary, the urn, and the Buddhist altar of the deceased (A). For such places and things, the check-in of the requester (C) to the funeral place can be recorded, for example, by using the two-dimensional code 702 as in the case of the above-mentioned grave. For each C), it is possible to memorize the presence / absence of attendance at the funeral and the presence / absence of visit to the grave, the date and time, and the number of times.

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

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 is composed of a CPU, an MPU, and the like. The arithmetic processing unit 1220 operates various functional units by executing a program stored in the storage unit 1230 based on various inputs. This program 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 has a receiving unit 1221, a registration processing unit 1222, a presenting unit 1223, a determination unit 1224, and a transmitting unit 1225 as various functional units.

The receiving unit 1221 receives various information via the network interface 1210. For example, the receiving unit 1221 requests registration of the administrator (B) from the person who should be the administrator or the deceased (A) (FIG. 2 (a): S204), and the administrator (B) or the deceased (A). Further receives a request for registration of post-mortem information of the deceased (A) (FIG. 2 (b): S224). In addition, the receiving unit 1221 requests the post-mortem information of the deceased (A) from the requester (C) (FIG. 3: S302), answers to the question (FIG. 3: S336), and a two-dimensional code password (FIG. 8: S806). ), And the location information of the mobile terminal 710 (FIG. 8: S840) and the like are received.

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 administrator (B) and the registration request of the post-mortem information of the deceased (A), and stores the information of the administrator (B) and the post-mortem information of the deceased (A) in the storage unit 1230. (FIG. 2 (a): S206, FIG. 2 (b): S226). In addition, the registration processing unit 1222 also processes the account registration as a user in the SNS, and registers the information of each user in the storage unit 1230. In addition, the registration processing unit 1222 also processes information related to the proxy service and registers it in the storage unit 1230.

The presentation unit 1223 presents the content of the response to the request for post-mortem information of the deceased (A) requested by the requester (C) according to the SNS relationship between the requester (C) and the deceased (A). (Fig. 3: S304, 306). Specifically, the presentation unit 1223 identifies the SNS relationship between the requester (C) and the deceased (A) in order to present the response contents to the request to the administrator (B), and determines the specific result. The corresponding answer contents are extracted from the storage unit 1230.

The determination unit 1224 determines various types of confirmation-required 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 criterion (FIG. 3: S338). Further, the determination unit 1224 determines whether or not the password of the two-dimensional code 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). After (C) actually visits the grave 700, it is determined whether or not the password is 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 the registration processing unit 1222 processing the registration request to the registration requester and related parties. As an example, the transmission unit 1225 confirms that the administrator has been registered (FIG. 2 (a): S208) for the deceased (A) or the person who should be the administrator, and the deceased. A registration confirmation (FIG. 2 (b): S228) that the post-mortem information of the deceased (A) has been registered is transmitted to (A) or the administrator (B). In addition, the transmission unit 1225 transmits the information presented by the presentation unit 1223, that is, the response content according to the relationship on the SNS to the administrator (B) (FIG. 3: S306). Further, 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 / requester (C). As an example, the transmission unit 1225 asks the requester (C) the requested post-mortem information (FIG. 3: S318), the request is rejected (FIG. 3: S324), or a predetermined question (FIG. 3). : S330) is transmitted, and the password for the proxy service and the two-dimensional code is transmitted together with the post-mortem information (see: FIG. 6). In addition, the transmission unit 1225 transmits the answer to the question (FIG. 3: S350) and the determination result (FIG. 3: S344) to the administrator (B), and also to the requester (C). The determination result that the password of the dimension code is incompatible is transmitted (FIG. 8: S812). Further, in the transmission unit 1225, if the password is correct, the requester (C) tells the administrator (B) the place where the two-dimensional code is installed (grave, funeral place, legal place, bone burial place). Etc.) (FIG. 8: S820), and information about the deceased (A) to be displayed on the mobile terminal 710 to the requester (C) (FIG. 8: S826. For example, FIG. 10). Website) is sent.

The storage unit 1230 is composed of a storage device such as a hard disk drive, SDD, and RAM, and stores various programs necessary for executing processing in the arithmetic processing unit 1220, data necessary for executing various programs, and the like. For example, the user information DB 1232, the post-mortem use DB 1234, and the check-in DB 1236 are stored in the storage unit 1230.

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

The post-mortem use DB1234 contains information on the administrator (B), post-mortem information on the deceased (A), questions to the requester (C), answers to these questions, and agency services for each deceased (A). And, the information of the two-dimensional code (whether or not the two-dimensional code is provided in the grave, etc., if it is provided, its password and installation location, and if it is provided, it is displayed by reading the two-dimensional code. Various information such as information about the deceased (eg, information such as the SNS site of FIG. 5A and the website 1000 of FIG. 10) is stored in association with each other.

The check-in DB1236 is a place where a two-dimensional code for the deceased (A) is provided for each deceased (A) in association with the requester (C) (funeral place, legal place, grave and bone laying of the deceased (A)). Whether or not you visited (check-in) a place (such as a place) is stored in association with the date and time and the number of times. Therefore, the check-in DB1236 also remembers the table of FIG. The check-in DB1236 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 by which user of the SNS. It is possible to confirm whether or not it has been done as appropriate. In addition, using the contents recorded in the check-in DB1236, the SNS server 120 makes a temporary or regular contact (for example, one-day memorial service) to a user who has visited the place where the two-dimensional code is installed. It is also possible to send a notice of the third anniversary, a notice of mourning, etc.).

FIG. 12 is a block diagram showing a client terminal 110B of the administrator (B). The client terminal 110B is an information processing device 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 has an input unit 1312 and a display unit 1314. The input unit 1312 receives input / operation from the administrator (B), and is composed of, for example, a keyboard, a touch panel, a voice input device, and the like. The display unit 1314 displays an image such as the presented answer contents (plurality of options) on the screen, and is composed of various displays such as a liquid crystal display. It is also possible that the display unit 1314 constitutes a touch panel and the display unit 1314 functions as an input unit.

The arithmetic processing unit 1320 is composed of a CPU, an MPU, and the like. The arithmetic processing unit 1320 operates various functional units by executing a program stored in the storage unit 1330 based on various inputs. This program 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 has 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 receiving unit 1322 confirms the registration that the administrator has been registered in the SNS server 120 (FIG. 2 (a): S210) and the registration confirmation that the post-mortem information has been registered in the SNS server 120 (FIG. 2 (FIG. 2)). b): Receive S230). In addition, the receiving unit 1322 receives the response contents (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 determined. Receive (FIG. 3: S346). In addition, the receiving unit 1322 receives that the requester (C) has checked in to the installation location of the two-dimensional code if the password of the two-dimensional code used by the requester (C) is correct. (FIG. 8: S822).

The transmission unit 1324 transmits various information via the network interface 1300. For example, the transmission unit 1324 transmits a registration request of the administrator (B) (FIG. 2 (a): S202) and a post-mortem information registration request (FIG. 2 (b): S220) to the SNS server 120. In addition, the transmission unit 1324 transmits the selection result of the answer content option (permission, refusal, or question) selected by the administrator (B) to the SNS server 120 (FIG. 3: S316, S322, S328). In addition to transmitting the selection result of the response content options (permission or denial) selected by the administrator (B) for the answer to the question of the requester (C) (FIG. 3: S356, 358).

The storage unit 1330 is composed of a storage device such as a hard disk drive, SDD, and 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 stores software (for example, a web browser or application) for using the SNS provided by the SNS server 120. In addition, 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) who is a first user and an administrator (B) who manages an SNS account for the deceased (A). The receiving unit 1221 that receives a request for information related to the death of the deceased (A) from the requester (C) who is the first user of the SNS server 120, and the first response content to the request. It is provided with a presentation unit 1223 that presents to the administrator (B) what corresponds to the SNS relationship between the requester (C) who is a user and the deceased (A).

Further, the information processing device 110B of the administrator (B) of the present embodiment is connected to the SNS server 120 that provides the SNS to the user via the network 130, and is an administrator who manages the SNS account for the deceased (A). The information processing device 110B of (B), a transmission unit 1324 that transmits information related to the death of the deceased (A) to the SNS server 120 for registration, and a first user (requester (requester)) who is one of the users. When a request for information registered in the SNS server 120 is made from C)), the SNS server 120 asks the first user (requester (C)) and the deceased (A) to answer the request. It includes a receiving unit 1322 that receives the answer contents 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 to an appropriate range.

The embodiments of the present invention have been described above with reference to specific examples. The above specific examples are examples for explaining the present invention, and are not intended to limit the present invention to only the embodiments thereof. That is, those having a design modification appropriately made by those skilled in the art are also included in the scope of the present invention as long as they have the features of the present invention. For example, each element included in each of the above-mentioned specific examples is not limited to the illustrated one, and can be changed as appropriate.

For example, in the above embodiment, the case where the deceased person (A) himself registered the SNS account for the deceased person (A) before his / her life and was one of the users of the SNS before his / her life was described. However, even if the deceased person (A) is not a user of the SNS before his / her life, the administrator (B) registers an SNS account for the deceased person (A) and manages it. Can be applied. That is, the above-mentioned "SNS account for the deceased (A)" includes the SNS account that the deceased (A) registered himself before his / her life, the SNS account that was transferred from this SNS account after his death, and the deceased (A). It also includes SNS accounts registered by the administrator (B) for the deceased (A) before or after his death.

In addition, the deceased (A) may automatically or manually classify the users who have a connection on the SNS into categories before he / she is alive, and the above questions will be presented according to the classified categories. It may be.

100 Information processing system, 110 client terminal, 110A deceased client terminal, 110B administrator client terminal (information processing device), 110C requester client terminal, 120 SNS server, 130 network, 1221 receiver, 1223 presenter, 1224 Judgment unit, 1225 transmitter, 1230 storage, 1322 receiver, 1324 transmitter, 1330 storage, A deceased, B administrator, C requester

Claims (17)

An SNS server that provides an SNS that includes a first user and an administrator who manages an SNS account for the deceased.
A receiving unit that receives a request for information related to the death of the deceased from the first user.
As the content of the response to the request, a presentation unit that presents to the administrator a response content corresponding to the relationship between the first user and the deceased person on the SNS, and
Equipped with a,
The relationship on the SNS does not allow (1) the deceased to convey information related to his or her death to the first user before his / her life on the SNS, but the deceased is with the first user. If it is said that it has a connection on the SNS, or (2) the relationship on the SNS is that the deceased has a connection on the SNS with the first user. However, when the first user is included in at least one of the contact information of the deceased person accessible to the SNS server and the contact information of the administrator accessible to the SNS server.
The presentation unit is an SNS server that presents at least an option for asking a question about the deceased to the administrator as a response content to the request . A transmitter is provided to send the question to the first user in response to the administrator selecting the option.
The SNS server according to claim 1, wherein the transmission unit transmits a response by the first user or a determination result of whether or not the response by the first user satisfies a predetermined criterion to the administrator . When the answer by the first user to the question meets a predetermined criterion
The SNS server according to claim 2 , wherein the transmission unit transmits information related to the death of the deceased to the first user . At least one of the deceased's funeral place, legal place, tomb, ossuary, urn and altar is provided with a two-dimensional code for the deceased.
When it is permitted to provide the information related to the death of the deceased to the first user, the transmission unit that transmits the password of the two-dimensional code to the first user together with the information related to the death of the deceased. with a, SNS server according to claim 1. When the relationship on the SNS allows the deceased to convey information related to his / her death to the first user before his / her life on the SNS.
The presentation unit, as a response made to the request, at least, one that presents the option to allow to provide information relating to death of the deceased in the first user to the administrator,
The relationship on the SNS is such that the deceased has no connection with the first user on the SNS, and the contact information of the deceased and the SNS server accessible by the SNS server are accessible. If the administrator's contact does not include the first user
Any one of claims 1 to 4 , wherein the presenting unit presents to the administrator at least an option of refusing to convey information related to the death of the deceased to the first user as a response content to the request. The SNS server described in item 1. A method executed by an SNS server that provides an SNS that includes a first user and an administrator who manages an SNS account for the deceased.
A step of receiving a request for information related to the death of the deceased from the first user, and
As the response contents to the request, a step of presenting to the administrator a response content corresponding to the SNS relationship between the first user and the deceased, and
Only including,
The relationship on the SNS does not allow (1) the deceased to convey information related to his or her death to the first user before his / her life on the SNS, but the deceased is with the first user. If it is said that it has a connection on the SNS, or (2) the relationship on the SNS is that the deceased has a connection on the SNS with the first user. However, when the first user is included in at least one of the contact information of the deceased person accessible to the SNS server and the contact information of the administrator accessible to the SNS server.
The presented step is a method performed by an SNS server, which comprises presenting to the administrator at least an option to ask a question about the deceased as a response to the request . To an SNS server that provides an SNS that includes a first user and an administrator who manages an SNS account for the deceased.
Receiving a request from the first user for information related to the death of the deceased
As the content of the response to the request, presenting to the administrator the one corresponding to the relationship between the first user and the deceased person on the SNS.
Is a program that executes
The relationship on the SNS does not allow (1) the deceased to convey information related to his or her death to the first user before his / her life on the SNS, but the deceased is with the first user. If it is said that it has a connection on the SNS, or (2) the relationship on the SNS is that the deceased has a connection on the SNS with the first user. However, when the first user is included in at least one of the contact information of the deceased person accessible to the SNS server and the contact information of the administrator accessible to the SNS server.
The presenting is a program including presenting to the administrator at least an option to ask a question about the deceased as a response to the request . An information processing device for an administrator who manages an SNS account for a deceased person by being connected to an SNS server that provides SNS to users via a network.
A transmitter that transmits information related to the death of the deceased to the SNS server for registration,
When a first user who is one of the users requests the information registered in the SNS server, the SNS server responds to the request by the first user and the deceased person. A receiver that receives the response content presented according to the relationship on the SNS with and
Equipped with a,
The relationship on the SNS does not allow (1) the deceased to convey the information to the first user on the SNS before his / her life, but the deceased does not allow the deceased to convey the information to the first user on the SNS. Or (2) the deceased person does not have a connection with the first user on the SNS, but the SNS server can access the above. When the first user is included in at least one of the contact information of the deceased person and the contact information of the administrator who can access the SNS server.
An information processing device of an administrator , wherein the answer content received by the receiver includes at least an option to ask a question about the deceased . When the first user answers the question after the administrator selects the option.
The information processing device of the administrator according to claim 8, wherein the receiving unit receives a response by the first user or a determination result of whether or not the response by the first user satisfies a predetermined criterion. When the relationship on the SNS is that the deceased allows the information to be transmitted to the first user on the SNS before his / her life.
The response content received by the receiver includes at least the option of allowing the information to be provided to the first user .
The relationship on the SNS is such that the deceased has no connection with the first user on the SNS, and the contact information of the deceased and the SNS server accessible by the SNS server are accessible. If the administrator's contact does not include the first user
The information processing device of the administrator according to claim 8 or 9 , wherein the response content received by the receiving unit includes at least an option of refusing to convey the information to the first user . At least one of the deceased's funeral place, legal place, tomb, ossuary, urn and 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 capable of communicating with the SNS server via a network, the receiving unit notifies the SNS server to that effect. The information processing apparatus of the administrator according to any one of claims 8 to 10 , which is received from . It is a method executed by the information processing device of the administrator who manages the SNS account for the deceased by being connected to the SNS server that provides the SNS to the user via the network.
A step of transmitting information related to the death of the deceased to the SNS server for registration, and
When a first user who is one of the users requests the information registered in the SNS server, the SNS server responds to the request by the first user and the deceased person. The step of receiving the answer content presented according to the relationship on the SNS with and
Only including,
The relationship on the SNS does not allow (1) the deceased to convey the information to the first user on the SNS before his / her life, but the deceased does not allow the deceased to convey the information to the first user on the SNS. Or (2) the deceased person does not have a connection with the first user on the SNS, but the SNS server can access the above. When the first user is included in at least one of the contact information of the deceased person and the contact information of the administrator who can access the SNS server.
A method performed by an administrator's information processing device, wherein the received response includes at least the option of asking a question about the deceased . When the first user answers the question after the administrator selects the option.
It is executed by the information processing apparatus of the administrator according to claim 12, which includes a step of receiving a response by the first user or a determination result of whether or not the response by the first user satisfies a predetermined criterion. How to When the relationship on the SNS is that the deceased allows the information to be transmitted to the first user on the SNS before his / her life.
The received response includes at least the option of allowing the information to be provided to the first user .
The relationship on the SNS is such that the deceased has no connection with the first user on the SNS, and the contact information of the deceased and the SNS server accessible by the SNS server are accessible. If the administrator's contact does not include the first user
The method performed by the information processing apparatus of the administrator according to claim 12 or 13, wherein the received response content includes at least an option of refusing to convey the information to the first user. To the information processing device of the administrator who manages the SNS account for the deceased by being connected to the SNS server that provides the SNS to the user via the network.
Sending information related to the death of the deceased to the SNS server for registration, and
When a first user who is one of the users requests the information registered in the SNS server, the SNS server responds to the request by the first user and the deceased person. Receiving the content of the answer presented according to the relationship on the SNS with
Is a program that executes
The relationship on the SNS does not allow (1) the deceased to convey the information to the first user on the SNS before his / her life, but the deceased does not allow the deceased to convey the information to the first user on the SNS. Or (2) the deceased person does not have a connection with the first user on the SNS, but the SNS server can access the above. When the first user is included in at least one of the contact information of the deceased person and the contact information of the administrator who can access the SNS server.
The received response includes at least the option of asking a question about the deceased . When the first user answers the question after the administrator selects the option.
15. The program of claim 15, comprising receiving a response by the first user or a determination result of whether the response by the first user meets a predetermined criterion. When the relationship on the SNS is that the deceased allows the information to be transmitted to the first user on the SNS before his / her life.
The received response includes at least the option of allowing the information to be provided to the first user.
The relationship on the SNS is such that the deceased has no connection with the first user on the SNS, and the contact information of the deceased and the SNS server accessible by the SNS server are accessible. If the administrator's contact does not include the first user
The program according to claim 15 or 16, wherein the received response includes at least an option to refuse to convey the information to the first user.