JP7354207B2 - Programs, information processing methods, terminals - Google Patents

Description

The present disclosure relates to programs, information processing methods, terminals, servers, etc.

There is a technique for notifying a warning using a mobile terminal when a disaster occurs (for example, Patent Document 1).

Japanese Patent Application Publication No. 2016-151799

According to the first aspect of the present invention, a program executed by a terminal that performs processing related to a chat with a user of the first terminal is configured to perform processing related to a chat with a user of the first terminal based on an input to the first terminal by a user of the first terminal. receiving first information regarding the safety of the user of the terminal by the communication unit of the terminal; and displaying the first information associated with the chat information related to the user of the first terminal on the display unit of the terminal. executed.
According to the second aspect of the present invention, an information processing method of a terminal that performs processing related to a chat with a user of the first terminal is based on an input to the first terminal by the user of the first terminal. The method includes receiving first information regarding the user's safety by a communication unit of the terminal, and displaying first information associated with chat information related to the user of the first terminal on a display unit of the terminal.
According to the third aspect of the present invention, the terminal that performs processing related to chatting with the user of the first terminal determines the safety of the user of the first terminal based on the input to the first terminal by the user of the first terminal. The communication device includes a communication unit that receives the first information, and a display unit that displays the first information associated with chat information related to the user of the first terminal.
According to a fourth aspect of the present invention, a terminal that performs processing related to chatting with a user of the first terminal includes a processor that reads a program stored in a memory and executes processing based on the program, and the processor includes: receiving, by a communication unit of the terminal, first information regarding the safety of the user of the first terminal based on an input to the first terminal by the user of the first terminal; and associating it with chat information related to the user of the first terminal; displaying the obtained first information on the display section of the terminal.

FIG. 1 is a diagram illustrating an example of a system configuration of a communication system according to an embodiment. FIG. 3 is a diagram illustrating an example of functions realized by the control unit of the server according to the first embodiment. FIG. 3 is a diagram showing an example of information etc. stored in the storage unit of the server according to the first embodiment. FIG. 3 is a diagram showing an example of account registration data according to the first embodiment. The figure which shows an example of the account management database based on 1st Example. FIG. 3 is a diagram illustrating an example of functions realized by the control unit of the terminal according to the first embodiment. FIG. 3 is a diagram showing an example of information stored in a storage unit of the terminal according to the first embodiment. FIG. 3 is a diagram showing an example of a screen displayed on the display unit of the terminal according to the first embodiment. FIG. 3 is a diagram showing an example of a screen displayed on the display unit of the terminal according to the first embodiment. FIG. 3 is a diagram showing an example of a screen displayed on the display unit of the terminal according to the first embodiment. 5 is a flowchart illustrating an example of the flow of processing executed by each device according to the first embodiment. The figure which shows an example of the screen displayed on the display part of the terminal based on the 1st modification. The figure which shows an example of the screen displayed on the display part of the terminal based on the 1st modification. 7 is a flowchart illustrating an example of the flow of processing executed by each device according to the first modification. The figure which shows an example of the information etc. which are memorize|stored in the memory|storage part of the server based on the 1st modification. The figure which shows an example of the group management database based on a 1st modification. The figure which shows an example of the screen displayed on the display part of the terminal based on the 1st modification. The figure which shows an example of the screen displayed on the display part of the terminal based on the 1st modification. The figure which shows an example of the screen displayed on the display part of the terminal based on the 1st modification. FIG. 7 is a diagram illustrating an example of a screen displayed on a display unit of a terminal according to a second embodiment. 7 is a flowchart showing an example of the flow of processing executed by each device according to the second embodiment. 7 is a flowchart showing an example of the flow of safety confirmation processing according to the second embodiment. FIG. 7 is a diagram illustrating an example of the timing of processing executed by each device according to the second embodiment. The figure which shows an example of the screen displayed on the display part of the terminal based on a 2nd modification. The figure which shows an example of the timing of the process which each apparatus based on the 2nd modification performs. The figure which shows an example of the screen displayed on the display part of the terminal based on a 2nd modification. FIG. 7 is a diagram showing an example of a screen displayed on a display unit of a terminal according to a third embodiment. FIG. 7 is a diagram showing an example of a screen displayed on a display unit of a terminal according to a third embodiment. 12 is a flowchart showing an example of the flow of processing executed by each device according to the third embodiment. FIG. 7 is a diagram illustrating an example of a screen displayed on a display unit of a terminal according to a fourth embodiment. FIG. 7 is a diagram illustrating an example of a screen displayed on a display unit of a terminal according to a fourth embodiment. FIG. 7 is a diagram illustrating an example of the timing of processing executed by each device according to the fourth embodiment. The figure which shows an example of the screen displayed on the display part of the terminal based on the 4th modification. The figure which shows an example of the timing of the process which each apparatus based on the 4th modification performs. FIG. 7 is a diagram showing an example of a screen displayed on a display unit of a terminal according to a fifth embodiment. FIG. 7 is a diagram showing an example of a screen displayed on a display unit of a terminal according to a fifth embodiment. FIG. 7 is a diagram showing an example of a screen displayed on a display unit of a terminal according to a fifth embodiment. 10 is a flowchart illustrating an example of the flow of processing executed by each device according to the fifth embodiment. FIG. 7 is a diagram showing an example of the timing of processing executed by each device according to the fifth embodiment. The figure which shows an example of the screen displayed on the display part of the terminal based on the 5th modification. The figure which shows an example of the screen displayed on the display part of the terminal based on the 5th modification. The figure which shows an example of the screen displayed on the display part of the terminal based on the 5th modification. 12 is a flowchart illustrating an example of the flow of processing executed by each device according to a fifth modification. 12 is a flowchart illustrating an example of the flow of a safety registration request process according to a fifth modification. FIG. 7 is a diagram showing an example of timing of processing executed by each device according to a fifth modification. The figure which shows an example of the screen displayed on the display part of the terminal based on the 5th modification. The figure which shows an example of the screen displayed on the display part of the terminal based on the 5th modification. FIG. 7 is a diagram showing an example of timing of processing executed by each device according to a fifth modification. FIG. 7 is a diagram showing an example of a screen displayed on a display unit of a terminal according to a sixth embodiment. FIG. 7 is a diagram showing an example of the timing of processing executed by each device according to the sixth embodiment. The figure which shows an example of the screen displayed on the display part of the terminal based on the 6th modification. FIG. 7 is a diagram showing an example of a screen displayed on a display unit of a terminal according to a seventh embodiment. FIG. 7 is a diagram showing an example of the timing of processing executed by each device according to the seventh embodiment. The figure which shows an example of the account management database based on the 7th modification. The figure which shows an example of the screen displayed on the display part of the terminal based on the 7th modification. FIG. 7 is a diagram showing an example of timing of processing executed by each device according to a seventh modification. The figure which shows an example of the screen displayed on the display part of the terminal based on the 7th modification. FIG. 7 is a diagram showing an example of a screen displayed on a display unit of a terminal according to an eighth embodiment. FIG. 7 is a diagram showing an example of the timing of processing executed by each device according to the eighth embodiment. FIG. 7 is a diagram showing a combination of first safety information and second safety information according to the eighth embodiment. FIG. 9 is a diagram showing an example of a screen displayed on a display unit of a terminal according to a ninth embodiment. The figure which shows an example of the screen displayed on the display part of the terminal based on the 9th modification.

<Compliance with legal matters>
Please note that the disclosures described herein are subject to compliance with the host country's legal requirements necessary for the implementation of the disclosures, such as confidentiality of communications.

<Embodiment>
In this specification, for the sake of clarity, there are places where the phrase ``as an example, not a limitation'' is written, but the description is not limited to only those places, and the entire embodiment described below. Please note that.

Embodiments for implementing programs and the like according to the present disclosure will be described with reference to the drawings.

A system may include, by way of example and not limitation, a plurality of devices.
The plurality of devices may be a combination of devices of the same type, devices of different types, or a combination of devices of the same type and devices of different types.
Note that a system can also be thought of as, by way of example and not limitation, a plurality of devices working together to perform some kind of processing.

Further, the system relating to a client (client device) and a server can be considered to be at least one of the following, by way of example and not limitation.
(1) Terminal & Server (2) Server (3) Terminal

(1) is a system that includes, by way of example and not limitation, at least one terminal and at least one server. An example of this is a client-server system.

The server is configured by the following devices, by way of example and not limitation, and may be a single device or a combination of multiple devices.

In particular, the server may include, by way of example and not limitation, at least one processor (for example, without limitation, a CPU: Central Processing Unit, a GPU: Graphics Processing Unit, an APU: Accelerated Processing Unit, a DSP: a Digital Signal Processor). (ASIC: Application Specific Integrated Circuit, FPGA: Field Programmable Gate Array), etc.), a computer device (processor + memory), a control device, an arithmetic device, a processing device, etc. or configurations that include multiple devices of the same type (for example, not limited to, CPU+CPU, homogeneous multi-core processor, etc.), or configurations that include multiple types of different types of any one device (for example, but not limited to, CPU+DSP, heterogeneous multi-core processors, etc.) etc.), or a combination of multiple devices (for example, without limitation, a processor + computer device, processor + arithmetic device, heterogeneous multiple devices, etc.).
Note that the processor may be a virtual processor.

Further, when a server executes some processing and is configured with a single device, the processing described in the embodiment is executed by the single device. Furthermore, in the case of a configuration including a plurality of devices, the configuration may be such that one device executes some of the processes and the other device executes the other processes. By way of example and not limitation, when the computer is configured to include a processor and an arithmetic device, the processor may execute the first process and the arithmetic device may execute the second process.
Furthermore, when the system is configured with a plurality of devices, each device may be configured to be arranged at physically distant positions from each other.

Moreover, the functions of the server may be provided in the form of PaaS, IaaS, or SaaS in cloud computing, by way of example and not limitation.

Further, the control unit of the system can be at least one of a terminal control unit and a server control unit. In other words, by way of example and not limitation, (1A) only the terminal control section, (1B) only the server control section, or (1C) both the terminal control section and the server control section, the system It can be a control unit of.

In addition, the control and processing performed by the system control unit (hereinafter collectively referred to as "control, etc.") may be performed only by (1A) the terminal control unit, or (1B) server control. (1C) It may be performed by both the control unit of the terminal and the control unit of the server.
In addition, in (1C), as an example and not a limitation, some of the controls performed by the control unit of the system are performed by the control unit of the terminal, and the remaining control etc. are performed by the control unit of the server. You can do it like this. In this case, the allocation (allocation) of control etc. may be divided equally, or may be allocated at different ratios instead of equally.

In addition, when the communication unit of a server is configured by a single device, the communication unit itself provided in the single device may be used. Further, when the server is configured to include a plurality of devices, the communication section of the server may include a communication section of each device.
By way of example and not limitation, if the server includes a first device and a second device, the first device has a first communication section, and the second device has a second communication section, the communication section of the server includes: The concept may include a first communication section and a second communication section.

(2) may be, by way of example and not limitation, a system (hereinafter referred to as a "server system") that includes a plurality of servers. In this case, the configuration described above can be similarly applied to each server.

The control etc. performed by the server system may be performed by (2A) only one server among a plurality of servers, (2B) only another server, or (2C) one server. This may be done by the server and other servers.
Furthermore, in (2C), as an example and not a limitation, one server may perform some of the controls performed by the server system, and the remaining controls may be performed by another server. good. In this case, the allocation (allocation) of control etc. may be divided equally, or may be allocated at different ratios instead of equally.

(3) may be a system configured by a plurality of terminals, by way of example and not limitation.
This system may be, by way of example and not limitation, as follows.
- A system that provides server functionality to terminals (distributed system). This can be accomplished using blockchain technology, by way of example and not limitation.
- A system in which terminals communicate wirelessly with each other. This can be achieved, by way of example and not limitation, by communicating in a P2P (peer-to-peer) manner using short-range wireless communication technology such as Bluetooth (registered trademark).

Note that the above applies not only to the control unit but also to each functional unit that can be a component of the system, such as an input/output unit, a communication unit, a storage unit, and a clock unit.

The following embodiments illustrate, by way of example and not limitation, a system that includes a terminal and a server (by way of example and not limitation, a client-server system).
Note that it is also possible to apply the server system (2) above as the server.

Further, instead of the system including a terminal and a server, it is also possible to apply a system not including a server, and by way of example and not limitation, the system (3) above.
The embodiment in this case can be configured based on the aforementioned blockchain technology or the like. Specifically, by way of example and not limitation, data stored and managed by a server described in the embodiments below is stored on a blockchain. The terminal can then generate a transaction to the blockchain, and when the transaction is confirmed on the blockchain, the data stored on the blockchain can be updated.

Note that even when expressed as a terminal, this is not limited to the meaning of the terminal as a client device in a client server.
That is, a terminal may include the concept of a device other than that of a client server.

Further, in this specification, the expression "by communication I/F" is used as appropriate. This indicates, by way of example and not limitation, that the device transmits and receives various information and data via the communication I/F (via the communication unit) based on the control of the control unit (processor, etc.). may be used.

In addition, in this specification, when referring to terms such as "related to" or "associated with," "B related to A" or "B related to A," the term "B related to A" is used as an example and not a limitation. ``B'' may mean ``B''. A specific example of this will be described later.

In this specification, when a device performs processing on two or more things, such as "sending A and B" or "receiving A and B,""A" is used. This includes cases in which "B" is performed at the same timing (hereinafter referred to as "simultaneous") and cases in which "A" and "B" are performed at different timings (hereinafter referred to as "non-simultaneous"). shall be deemed acceptable.
As an example and not a limitation, when transmitting the first information and the second information, there is a case where the first information and the second information are sent at the same timing, and a case where the first information and the second information are sent at different timings. It is acceptable to include the concepts of both "transmission" and "transmission."
Note that in consideration of lag (time lag), "simultaneously" may include "almost simultaneously".

Note that even if "A" and "B" are performed at different timings, it is only necessary to process "A" and "B", and the purpose is not necessarily the same. It may be omitted.
As an example and not a limitation, when transmitting the first information and the second information as described above, it is only necessary to transmit the first information and the second information, and the first information and the second information may be transmitted for the same purpose. In addition to the case where the first information and the second information are sent for different purposes, this may include the case where the first information and the second information are sent for different purposes.

In the following embodiments, a messaging service will be exemplified as an example of a service for users to chat (hereinafter referred to as "chat service"). Further, an application for implementing a chat service is referred to as a "chat application", and an application for implementing a messaging service is referred to as a "messaging application".
By way of example and not limitation, a chat application may allow users to chat in chat rooms. Additionally, the chat application may allow, by way of example and not limitation, the ability to make phone calls (voice calls, video calls, etc.) between users.

Note that the messaging service: MS (including the instant message service: IMS) can also be considered as one form (one form) of the social networking service: SNS. For this reason, messaging services and social networking services may or may not be distinguished. In other words, social networking services may include messaging services.

In addition, in the following embodiments, as an example of a messaging service, an instant messaging service: IMS (Instant Messaging Service).
Instant messaging applications, by way of example and not limitation, may enable users to conduct conversations in chat rooms. Additionally, instant messaging applications may, by way of example and not limitation, allow for telephone calls (such as voice calls and video calls) to be made between users.

A chat room (for example, but not limited to, a talk room) can be a UI (User Interface) or GUI (Graphical User Interface) that allows each user to view content sent and received between multiple users' terminals. .

In addition, talk rooms include one-on-one user talk rooms (hereinafter referred to as "one-on-one talk rooms"), group talk rooms including multiple users (hereinafter referred to as "group talk rooms"), A talk room with users of official accounts (hereinafter referred to as "OA talk room"), etc. can be included.

For data management purposes, a one-on-one talk room can be managed as a talk room for one-on-one users or one-on-one accounts, or as a talk room for a group consisting of two users or two accounts. You may.

An official account is an account of a business operator (an account of a user of a business operator), not a general user, and users of this official account may also use terminals similar to those of general users, by way of example and not limitation. , it is possible to send and receive content (messages) to and from other devices via the server.

In this specification, content may be information transmitted from a transmission source to a transmission destination. Further, the content may be one or more pieces of content.

Examples of content include, but are not limited to, text content in text format, image content in image (including at least one of still images and moving images) format, sound content in sound (including audio) format, etc. May be included.
In addition to this, operation content such as buttons and icons used for user operations, and link content such as link information (including, by way of example and not limitation, URI (Uniform Resource Identifier), etc.) may also be included. shall be taken as a thing.

By way of example and not limitation, the text may include at least one of the following: characters of each country represented by character codes, extended characters, model-dependent characters, numbers, symbols, figures, and codes.
Note that the text does not need to include at least one of the above characters, extended characters, model-dependent characters, numbers, symbols, figures, and codes, and may include other text.

The image can include, by way of example and not limitation, at least one of various types of image information such as an icon, a button, a stamp, a pictogram, and a banner image.

Further, in the following embodiments, a safety confirming service will be exemplified as an example of a service for users to confirm their safety when a disaster (such as a large-scale disaster) occurs. Furthermore, an application for realizing the safety confirmation service is referred to as a "safety confirmation application."
In the safety confirmation application, by way of example and not limitation, a user can register information regarding his or her own safety and refer to information regarding the safety of other users.

As a form for realizing the safety confirmation service (safety confirmation application), any of the following forms can be applied, by way of example and not limitation.
(A) A configuration in which the function of a safety confirmation service is provided as a function of a messaging application (B) A configuration in which an application (integrated application) having a function of a safety confirmation service and a function of a messaging service is configured (C) A configuration in which the safety confirmation service is provided as a function of the messaging application Form in which the messaging application is configured as a separate application from other applications (D) Form in which the safety confirmation application is configured as a standalone application

In forms (A) and (B), by way of example and not limitation, the safety confirmation service provider may be the same provider as the messaging service provider.
Further, in this case, one method is to make the user's account in the messaging application and the user's account in the safety confirmation application a common account.
Further, in this case, as another method, the user's account in the messaging application and the user's account in the music application can be automatically associated (linked).

In form (C), by way of example and not limitation, the safety confirmation service provider may be a different provider than the messaging service provider.
Furthermore, in the form (C), a process for associating a user's account in the messaging application with a user's account in the safety confirmation application (cooperation process) can be performed.

Note that, different from the above, it is also possible to provide a messaging service function as one function of the safety confirmation application.

<First example>
The first embodiment provides, by way of example and not limitation, that when a disaster such as a large-scale disaster occurs, one terminal 20 (hereinafter referred to as a "terminal" as appropriate) is connected to another terminal 20 (hereinafter referred to as a "terminal" as appropriate). This is an embodiment in which information related to safety confirmation (hereinafter referred to as "safety confirmation information") registered by a user of a terminal (hereinafter referred to as "first user") (hereinafter referred to as "first user") is displayed.

Here, the "safety confirmation information" can be roughly divided into the following three types of information, by way of example and not limitation.
(A1) Safety status information Class information regarding the safety level indicating the situation in which the user is placed.
In this embodiment, by way of example and not limitation, the safety status information registered by the user is classified into two classes: "safe" and "dangerous."
Note that the safety status information is not limited to two classes. As an example and not a limitation, the safety status information may include a class such as "unknown" indicating that the safety status is unknown, and a class "outside area" indicating that the person is outside the disaster area.

(A2) Safety comment information Content information such as messages regarding safety to convey the safety of the user.
In this embodiment, the safety comment information is assumed to be text, by way of example and not limitation.
Note that the safety comment information may be, by way of example and not limitation, audio, video, icons, etc.

(A3) Safety location information Information regarding the location of the user who registers safety confirmation information.
In this embodiment, by way of example and not limitation, the safety location information is an area defined by an address (by way of example and not limitation, city, ward, town, village).
Note that the safety location information may be, by way of example and not limitation, location coordinates defined by latitude and longitude, or areas connected by location coordinates defined by latitude and longitude. Further, the safety location information may include information regarding altitude.

As the safety confirmation information, any combination of safety status information, safety comment information, and safety location information can be used.
Note that it is desirable that the safety confirmation information includes at least safety status information or safety comment information. However, it is not limited to this.

Furthermore, the safety confirmation information on the display screen may be displayed in Japanese or in another language (such as English).
By way of example and not limitation, "safety" may be displayed as "Safe," danger (unsafe) may be indicated as "Danger" or "Not Safe," and outside the area may be indicated as "Not IN Area."

Furthermore, hereinafter, a user account that registers safety confirmation information will be referred to as a "safety registration account," and a user account that refers to "safety information" based on registered safety confirmation information will be referred to as a "safety reference account."
In general, one user account can serve as both a safety registration account and a safety reference account.

Further, as described above, hereinafter, a business that provides a messaging service using a messaging application will be referred to as a "messaging service business".
Note that the messaging service provider can also be expressed as a provider that provides a messaging application or a provider of the server 10.
It can also be expressed as a messaging service provider in the sense of a provider that provides messaging services.

Further, in the following, the name of the messaging application will be appropriately referred to as "Messaging App" for illustration and explanation.

By way of example and not limitation, the messaging application can be configured so that accounts registered as friends on the server 10 can have one-on-one conversations with each other. Further, by way of example and not limitation, a group including two or more accounts may be formed, and the accounts included in the group may be configured to have a group talk with each other.

Additionally, the messaging application may be configured to allow a list of messages sent to one user account to be viewed as a talk list, by way of example and not limitation.

As an example and not a limitation, the format for displaying information for confirming the safety confirmation information registered by the user (hereinafter referred to as "safety information" as appropriate) on each terminal 20 is the following configuration in a messaging application. One example is the format in which the requirements are displayed.
(B1) Display in friend list (B2) Display in talk list (B3) Display in talk room

Note that, as an example of the association of users (accounts), "friends" in a messaging service will be mainly illustrated below, but the association is not limited to this.
As an example and not a limitation, on SNS, "Follow" indicates other users (accounts) who have registered themselves because they are interested in them, or other users (accounts) who have registered themselves because they are interested in them. Relationships such as "follower", which indicates "users" (accounts), can also be included in the association between users (accounts).

As an example and not a limitation, a list of users in a "follow" relationship or users in a "follower" relationship in an SNS can correspond to the above configuration requirement (B1).
Furthermore, by way of example and not limitation, in the SNS, a list of posts by users in a "follow" relationship (by way of example, not limitation, "timeline") can be made to correspond to the above configuration requirement (B2).
Furthermore, by way of example and not limitation, posting to a specific user (by way of example and not limitation, "direct message") on SNS can be made to correspond to the above configuration requirement (B3).

The content described in the first embodiment is applicable to each of the other embodiments and other modifications.
In addition, the same reference numerals are given to the same constituent elements as those already mentioned, and the explanation thereof will be omitted.

<System configuration>
FIG. 1-1 is a diagram illustrating an example of a system configuration of a communication system 1 in an embodiment of the present disclosure.
In the communication system 1, by way of example and not limitation, a server 10 and a plurality of terminals 20 (terminal 20A, terminal 20B, terminal 20C, . . . ) are connected via a network 30.

The server 10 has a function of providing predetermined services (for example, but not limited to, a messaging service, a safety confirmation service, etc.) to a terminal 20 owned by a user via the network 30. Server 10 can also be expressed as a messaging server, a safety confirmation server, etc., by way of example and not limitation.
In this embodiment, the users of the server 10 are a messaging service provider (operator) and a safety confirmation service provider (operator).

Note that the number of servers 10 and the number of terminals 20 connected to the network 30 are not limited.

The terminals 20 (terminal 20A, terminal 20B, terminal 20C, . . . ) may be any information processing terminal that can implement the functions described in each embodiment. Terminal 20 may include, by way of example and not limitation, a smartphone, a mobile phone (feature phone), a computer (by way of example and not limitation, a desktop, laptop, tablet, etc.), a media computer platform (by way of example and not limitation, a cable, satellite set, etc.). top boxes, digital video recorders), handheld computing devices (by way of example and not limitation, personal digital assistants, e-mail clients, etc.), wearable terminals (glass-like devices, watch-like devices, etc.), VR (Virtual Reality) including a terminal, smart speaker (speech recognition device), or other type of computer or communication platform. Further, the terminal 20 may be expressed as an information processing terminal.

By way of example and not limitation, the configurations of terminal 20A, terminal 20B, and terminal 20C may be the same. Furthermore, if necessary, the terminal used by user X may be expressed as terminal 20X, and the user information in a predetermined service associated with user You don't have to.
Note that the user information is user information associated with an account used by the user in a predetermined service. User information includes, by way of example and not limitation, the user's name, the user's icon image, the user's age, the user's gender, the user's address, and the user's hobbies, entered by the user or provided by a predetermined service. It includes information associated with the user such as preferences and user identifiers, and may be any one or a combination of these, or may not be the same.

The network 30 plays a role of connecting one or more terminals 20 and one or more servers 10. That is, the network 30 refers to a communication network that provides a connection path so that the various devices described above can transmit and receive data after being connected.

One or more portions of network 30 may or may not be a wired network or a wireless network. Network 30 may include, by way of example and not limitation, an ad hoc network, an intranet, an extranet, a virtual private network (VPN), a local area network (LAN), a wireless LAN (wireless LAN: WLAN), wide area network (WAN), wireless WAN (WWAN), metropolitan area network (MAN), part of the Internet, public switched telephone network (Public Switched Telephone Network (PSTN), mobile phone network, ISDN (integrated service digital networks), wireless LAN, LTE (long term evolution), CDMA (code division multiple access), Bluetooth (registered trademark), satellite communication, etc., or a combination of two or more of these. Network 30 may include one or more networks 30.

The server 10 (not limited to, but an example of a server, an information processing device, or an information management device) has a function of providing a predetermined service to the terminal 20. The server 10 may be any information processing device that can implement the functions described in each embodiment. Server 10 may include, by way of example and not limitation, a server device, a computer (such as, by way of example and not limitation, a desktop, laptop, tablet, etc.), a media computer platform (by way of example and not limitation, a cable, satellite set-top box, digital video recorder, etc.). ), handheld computing devices (by way of example and not limitation, PDAs, email clients, etc.), or other types of computers or communication platforms. Further, the server 10 may be expressed as an information processing device. If there is no need to distinguish between the server 10 and the terminal 20, the server 10 and the terminal 20 may or may not be each expressed as an information processing device.

[Hardware (HW) configuration of each device]
The HW configuration of each device included in the communication system 1 will be explained.

(1) HW configuration of terminal FIG. 1-1 shows an example of the HW configuration of the terminal 20.
The terminal 20 includes a control section 21 (CPU: central processing unit), a storage section 28, a communication I/F 22 (interface), an input/output section 23, a clock section 29A, and a position calculation information detection section 29B. . Each component of the HW of terminal 20 is interconnected via bus B, by way of example and not limitation. Note that it is not essential that the HW configuration of the terminal 20 includes all the components. By way of example and not limitation, terminal 20 may or may not be configured to have individual components or components removed.

The communication I/F 22 transmits and receives various data via the network 30. Communication may be performed by wire or wirelessly, and any communication protocol may be used as long as mutual communication can be performed. The communication I/F 22 has a function of communicating with various devices such as the server 10 via the network 30. The communication I/F 22 transmits various data to various devices such as the server 10 according to instructions from the control unit 21. Furthermore, the communication I/F 22 receives various data transmitted from various devices such as the server 10 and transmits the received data to the control unit 21 . Moreover, the communication I/F 22 may be simply expressed as a communication section. In addition, when the communication I/F 22 is composed of a physically structured circuit, it may be expressed as a communication circuit.

The input/output unit 23 includes a device for inputting various operations to the terminal 20, a device for outputting processing results processed by the terminal 20, and the like. In the input/output section 23, the input section and the output section may be integrated, or may be separated into an input section and an output section, or may not be.

The input unit is realized by any one or a combination of all types of devices that can receive input from the user and transmit information related to the input to the control unit 21. The input unit includes, by way of example and not limitation, a touch panel, a touch display, hardware keys such as a keyboard, a pointing device such as a mouse, a camera (operation input via moving images), and a microphone (operation input via voice).

The output unit is realized by any one of all types of devices capable of outputting the processing results processed by the control unit 21 or a combination thereof. Output units include, by way of example and not limitation, a touch panel, a touch display, a speaker (audio output), a lens (including, by way of non-limiting example, 3D (three dimensions) output or hologram output), a printer, and the like.

Although this is just an example, the input/output section 23 includes a display section 24, a sound input section 25, a sound output section 26, and an imaging section 27, by way of example and not limitation.

The display unit 24 is realized by any one or a combination of all types of devices capable of displaying data according to the display data written in the frame buffer. The display unit 24 may include, by way of example and not limitation, a touch panel, a touch display, a monitor (by way of example and not limitation, a liquid crystal display or an OELD (organic electroluminescence display)), a head mounted display (HDM), a projection mapping, and a hologram. , devices capable of displaying images, text information, etc. in air (which may or may not be a vacuum). Note that these display units 24 may or may not be capable of displaying display data in 3D.

The sound input unit 25 is used for inputting sound data (including audio data; the same applies hereinafter). The sound input section 25 includes a microphone and the like.
The sound output section 26 is used to output sound data. The sound output unit 26 includes a speaker and the like.
The imaging unit 27 is used to obtain image data (including still image data and moving image data; the same applies hereinafter). The imaging unit 27 includes a camera and the like.

When the input/output unit 23 is a touch panel, the input/output unit 23 and the display unit 24 may have substantially the same size and shape and may be disposed facing each other.

The clock unit 29A is a built-in clock of the terminal 20, and outputs time information (timekeeping information). The clock section 29A includes, by way of example and not limitation, a clock using a crystal oscillator. The clock section 29A can also be expressed as a clock section or a time information detection section, by way of example and not limitation.

Note that the clock unit 29A may or may not have a clock to which the NITZ (Network Identity and Time Zone) standard or the like is applied.

The position calculation information detection unit 29B has a function of detecting (measuring) information (hereinafter referred to as “position calculation information”) necessary for the control unit 21 to calculate (measure) the position of its own terminal 20. Department. The position calculation information detection unit 29B can also be expressed as a position calculation sensor unit, by way of example and not limitation.

The position calculation information detection unit 29B includes, by way of example and not limitation, a satellite positioning sensor (satellite positioning sensor) which is a sensor or unit for calculating the position of the terminal 20 using a satellite positioning system such as GPS (Global Positioning System). unit), an inertial measurement sensor (IMU (Inertial Measurement Unit)) which is a sensor or unit for calculating the position of the terminal 20 using an inertial navigation system, and UWB (Ultra Wide Wireless). This includes a UWB positioning sensor (UWB positioning unit), which is a sensor or unit for calculating the position of the terminal 20 using the UWB band.

The satellite positioning unit includes, by way of example and not limitation, an RF receiving circuit that converts an RF (Radio Frequency) signal including a positioning satellite signal transmitted from a positioning satellite received by an antenna (not shown) into a digital signal; A positioning satellite signal is captured by performing correlation calculation processing on the digital signal output from the RF receiving circuit, and information such as satellite orbit data and time data extracted from the positioning satellite signal is used as position calculation information. It has a baseband processing circuit etc. for output.

The inertial measurement unit has an inertial sensor that is a sensor that detects information necessary for calculating the position of the terminal 20 by inertial navigation calculation. Inertial sensors include, by way of example and not limitation, a 3-axis acceleration sensor and a 3-axis gyro sensor, and use the acceleration detected by the acceleration sensor and the angular velocity detected by the gyro sensor as position calculation information. Output.

By way of example and not limitation, the UWB positioning unit is an ultra-wideband RF (Radio Frequency) signal that converts into a digital signal an ultra-wideband RF (Radio Frequency) signal including an ultra-wideband pulse signal for positioning transmitted from a positioning beacon that is received by an antenna (not shown). It includes a relative position calculation processing circuit that calculates the relative position between the terminal 20 and the positioning beacon based on the digital signal output from the wideband RF reception circuit and the ultra-wideband RF reception circuit.
Note that, by way of example and not limitation, the UWB positioning unit may cause the terminal 20 to function as a positioning beacon by transmitting an ultra-wideband RF signal including an ultra-wideband pulse signal for positioning from an antenna (not shown). You don't have to do that.

By way of example and not limitation, the control unit 21 calculates the position of its own terminal 20 at regular timing or at a specific timing based on the position calculation information detected by the position calculation information detection unit 29B. The position of a terminal is referred to as a "terminal position", and the calculated terminal position is referred to as a "calculated terminal position". The control unit 21 may or may not store the calculated terminal position in the storage unit 28 as calculated terminal position history data in association with the date and time when the calculated terminal position was calculated.

The control unit 21 has a physically structured circuit for executing functions realized by codes or instructions included in a program, and includes, by way of example and not limitation, a data processing device built into hardware. This is realized by Therefore, the control unit 21 may or may not be expressed as a control circuit.

The control unit 21 may include, by way of example and not limitation, a central processing unit (CPU), a microprocessor, a processor core, a multiprocessor, an ASIC (application-specific integrated circuit), and a FPGA (field programmable). gate array).

The storage unit 28 has a function of storing various programs and various data necessary for the terminal 20 to operate. The storage unit 28 includes various storage media such as, by way of example and not limitation, an HDD (hard disk drive), an SSD (solid state drive), a flash memory, a RAM (random access memory), and a ROM (read only memory). Furthermore, the storage unit 28 may or may not be expressed as a memory.

In the terminal 20, the program P is stored in the storage unit 28, and by executing the program P, the control unit 21 executes processing as each unit included in the control unit 21. That is, the program P stored in the storage unit 28 causes the terminal 20 to realize each function executed by the control unit 21. Furthermore, this program P may or may not be expressed as a program module.

(2) HW configuration of server FIG. 1-1 shows an example of the HW configuration of the server 10.
The server 10 includes a control section 11 (CPU), a storage section 15, a communication I/F 14 (interface), an input/output section 12, and a clock section 19. The HW components of server 10 are interconnected via bus B, by way of example and not limitation. Note that the HW of the server 10 does not necessarily include all the components as the HW configuration of the server 10 . By way of example and not limitation, the HW of server 10 may or may not be configured to allow removal of individual components, or multiple components.

The control unit 11 has a physically structured circuit for executing functions realized by codes or instructions included in a program, and includes, by way of example and not limitation, a data processing device built into hardware. This is realized by

The control unit 11 is typically a central processing unit (CPU), and may or may not be a microprocessor, processor core, multiprocessor, ASIC, or FPGA. In the present disclosure, the control unit 11 is not limited to these.

The storage unit 15 has a function of storing various programs and various data necessary for the operation of the server 10. The storage unit 15 is realized by various storage media such as HDD, SSD, and flash memory. However, in the present disclosure, the storage unit 15 is not limited to these. Furthermore, the storage unit 15 may or may not be expressed as a memory.

The communication I/F 14 transmits and receives various data via the network 30. Communication may be performed by wire or wirelessly, and any communication protocol may be used as long as mutual communication can be performed. The communication I/F 14 has a function of communicating with various devices such as the terminal 20 via the network 30. The communication I/F 14 transmits various data to various devices such as the terminal 20 according to instructions from the control unit 11. Further, the communication I/F 14 receives various data transmitted from various devices such as the terminal 20 and transmits the received data to the control unit 11. Moreover, the communication I/F 14 may be simply expressed as a communication section. Furthermore, when the communication I/F 14 is composed of a physically structured circuit, it may be expressed as a communication circuit.

The input/output unit 12 includes a device for inputting various operations to the server 10, a device for outputting processing results processed by the server 10, and the like. In the input/output section 12, the input section and the output section may be integrated, or may be separated into an input section and an output section, or may not be.

The input unit is realized by any one or a combination of all types of devices that can receive input from the user and transmit information related to the input to the control unit 11. The input unit is typically implemented using hardware keys such as a keyboard or a pointing device such as a mouse. Note that the input unit may or may not include, by way of example and not limitation, a touch panel, a camera (operation input via a moving image), or a microphone (operation input via voice).

The output unit is realized by any one of all types of devices capable of outputting the processing results processed by the control unit 11 or a combination thereof. Output units include, by way of example and not limitation, a touch panel, a touch display, a speaker (sound output), a lens (including, by way of non-limiting example, 3D (three dimensions) output or hologram output), a printer, and the like.

Although this is just an example, the input/output section 12 includes a display section 13 by way of example and not limitation.

The display unit 13 is realized by a display or the like. The display is typically implemented as a monitor (for example, but not limited to, a liquid crystal display or an organic electroluminescence display (OELD)). Note that the display may or may not be a head mounted display (HDM). Note that these displays may or may not be capable of displaying display data in 3D. In this disclosure, the display is not limited to these.

The clock unit 19 is a built-in clock of the server 10, and outputs time information (timekeeping information). The clock unit 19 includes, by way of example and not limitation, an RTC (Real Time Clock) as a hardware clock, a system clock, and the like. The clock section 19 can also be expressed as a timekeeping section or a time information detection section, by way of example and not limitation.
(3) Others The server 10 stores the program P in the storage unit 15, and by executing the program P, the control unit 11 executes processes as each unit included in the control unit 11. That is, the program P stored in the storage unit 15 causes the server 10 to realize each function executed by the control unit 11. This program P may or may not be expressed as a program module.
The same applies to other devices.

In each embodiment of the present disclosure, description will be made assuming that the CPU of the terminal 20 and/or the server 10 executes the program P.

Note that the control unit 21 of the terminal 20 and/or the control unit 11 of the server 10 may be formed not only in a CPU having a control circuit but also in an integrated circuit (IC (Integrated Circuit) chip, LSI (Large Scale Integration)), etc. Each process may or may not be realized by a dedicated logic circuit (hardware) or a dedicated circuit. Further, these circuits may be realized by one or more integrated circuits, and the plurality of processes shown in each embodiment may or may not be realized by one integrated circuit. Further, LSIs are sometimes called VLSIs, super LSIs, ultra LSIs, etc. depending on the degree of integration. Therefore, the control unit 21 may or may not be expressed as a control circuit.

Further, the program P (by way of example, but not limitation, a software program, computer program, or program module) of each embodiment of the present disclosure may be provided in a state stored in a computer-readable storage medium, or It doesn't have to be done. The storage medium can store the program P in a "non-temporary tangible medium". Further, the program P may or may not be for realizing a part of the functions of each embodiment of the present disclosure. Furthermore, it may or may not be a so-called difference file (difference program) that can realize the functions of each embodiment of the present disclosure in combination with a program P already recorded on a storage medium.

Furthermore, when referring to a system program (a program executed by the system), the system is as described above. The system program described above is a program that can be executed by the entire system, and this program may be composed of programs for individual devices constituting the system, by way of example and not limitation. It is assumed that the programs stored in each device may be different. In other words, the program does not have to be common to each device that makes up the system.
As an example and not a limitation, if a system is composed of a terminal and a server, and the program of the system is P1, the program P1 of the system is composed of a program P2 stored in the terminal and a program P3 stored in the server. P2 and P3 are for executing system programs, and may be different programs. By way of example and not limitation, the program P2 stored on the terminal is a program that executes a first process and sends the result of the first process to the server, and the program P3 stored on the server is a program that executes a first process and sends the result of the first process to the server. The program may be a program that performs a second process on the result of the first process and sends the result of the second process to the terminal.

The storage medium may include one or more semiconductor-based or other integrated circuits (ICs), such as, by way of example and not limitation, a field programmable gate array (FPGA) or an application specific integrated circuit (ASIC), a hard・Disk drive (HDD), hybrid hard drive (HHD), optical disk, optical disk drive (ODD), magneto-optical disk, magneto-optical drive, floppy diskette, floppy disk drive (FDD), magnetic tape, solid state (SSD), a RAM drive, a secure digital card, or any other suitable storage medium, or a suitable combination of two or more thereof. Storage media may be volatile, non-volatile, or a combination of volatile and non-volatile, where appropriate. Note that the storage medium is not limited to these examples, and may be any device or medium that can store the program P. Further, the storage medium may or may not be expressed as a memory.

The server 10 and/or the terminal 20 can realize the functions of the plurality of functional units shown in each embodiment by reading the program P stored in the storage medium and executing the read program P.

Further, the program P of the present disclosure may or may not be provided to the server 10 and/or the terminal 20 via any transmission medium (communication network, broadcast waves, etc.) that can transmit the program. . By way of example and not limitation, the server 10 and/or the terminal 20 realize the functions of the plurality of functional units shown in each embodiment by executing a program P downloaded via the Internet or the like.

Furthermore, each embodiment of the present disclosure may be implemented in the form of a data signal in which the program P is embodied by electronic transmission.
At least part of the processing in the server 10 and/or the terminal 20 may or may not be realized by cloud computing configured by one or more computers.
At least part or all of the processing in the terminal 20 may or may not be performed by the server 10. In this case, at least some or all of the processing of each functional unit of the control unit 21 of the terminal 20 may or may not be performed by the server 10.
At least part or all of the processing in the server 10 may be performed by the terminal 20, or may not be performed. In this case, at least some or all of the processing of each functional unit of the control unit 11 of the server 10 may or may not be performed by the terminal 20.

Unless explicitly stated, the configuration of the determination in the embodiments of the present disclosure is not essential, and a predetermined process may be performed when the determination condition is met, or a predetermined process is performed when the determination condition is not met. You may or may not.

Note that the program of this disclosure uses scripting languages such as ActionScript and JavaScript (registered trademark), compiler languages such as Objective-C and Java (registered trademark), markup languages such as HTML Living Standard, etc., by way of example and not limitation. It is implemented using

<Functional configuration>
(1) Functional Configuration of Server FIG. 1-2 is a diagram showing an example of the functions realized by the control unit 11 of the server 10 in this embodiment.
The control unit 11 includes, by way of example and not limitation, an application management processing unit 111 as a functional unit for executing application management processing according to an application management processing program 151 stored in the storage unit 15.

FIG. 1-3 is a diagram showing an example of information stored in the storage unit 15 of the server 10 in this embodiment.
The storage unit 15 stores, by way of example and not limitation, an application management processing program 151 executed as an application management process, account registration data 153, and an account management database 155.

The account registration data 153 is registration data regarding an account of an application (messaging application in this embodiment), and an example of the data structure is shown in FIG. 1-4.
The account registration data 153 stores, by way of example and not limitation, a user name, an application ID, and other registration information in association with each other.

The user name is the name of the account of the terminal 20 that uses this application, and by way of example and not limitation, the name that the user of the terminal 20 registers when using the application is stored.

The application ID is information used to identify an application's account, or the account itself.
This application ID is preferably a unique value for each account, and is set and stored by the server 10 as a unique value (unique value) for each account, by way of example and not limitation.
The application ID is information associated with the terminal 20 or the user of the terminal 20, and is an example of information regarding the terminal or information regarding the user of the terminal.

Other registered information includes, by way of example and not limitation, identification information for identifying the terminal 20, telephone number of the terminal 20 (terminal telephone number), email address (terminal email address), and information used for various types of authentication in applications. Various information such as authentication information such as a password (login password, authentication password, etc.) can be included.

The identification information for identifying the terminal 20 may be, by way of example and not limitation, a terminal ID (by way of example and not limitation, IMEI (International Mobile Equipment Identity)).
Furthermore, the identification information for identifying the user of the terminal 20 may be, by way of example and not limitation, an application ID for general users or an application ID for official users.

Note that a "user ID" may or may not be used instead of the application ID.
In addition, if the application allows only one account to be registered for one terminal 20, it is not limited, but as an example, "Identification information for identifying the terminal 20 = Identification information for identifying the user of the terminal 20 = Application ID".

Further, as an example and not a limitation, it may be possible to assign a plurality of terminal IDs to one application ID, or it may not be necessary to do so. In this case, applications may or may not be activated simultaneously on a plurality of terminals 20 using one application ID as a target for identification (login).

Furthermore, instead of using various IDs such as application IDs, it is also possible to apply a method of managing accounts using information such as terminal phone numbers.
In this case, instead of storing ID information such as an application ID in the account registration data 153, information such as a terminal telephone number may be stored in the account registration data 153. Note that instead of replacing ID information such as an application ID with information such as a terminal telephone number, ID information such as an application ID may be made to have a one-to-one correspondence with information such as a terminal telephone number. You don't have to.

Note that in the following various embodiments, for the sake of simplicity, it is assumed that one account is registered for one terminal 20.
In this case, as described above, "identification information for identifying the terminal 20 = identification information for identifying the user of the terminal 20 = application ID", so the "account user" used in the following explanation is The term may be substantially synonymous with "account terminal."

The account management database 155 is a database for managing information related to accounts registered in the account registration data 153, and an example of the data structure of the account management database 155A is shown in FIG. 1-5.
Account management data is stored in the account management database 155A as management data for each account.

Each account management data stores, by way of example and not limitation, an application ID, friend management data, and safety registration data.

The application ID is information for identifying an account managed by account management data, and as an example and not a limitation, an application ID registered in the account registration data 153 is stored.

Friend management data is data for storing application IDs of accounts that are friends with the account with this application ID. As an example and not a limitation, when a user registers as a friend, the server will store information about the user who has registered as a friend. Application ID is added and updated.

The safety registration data is data for storing safety-related registration associated with the account of this application ID, and includes, by way of example and not limitation, safety status information.

By way of example and not limitation, the safety registration data for each account can be changed based on user input such as user operation on the terminal 20.
Note that the initial value (default) of the safety registration data may be, by way of example and not limitation, information indicating that the server 10 has not received safety confirmation information (by way of example and not limitation, information indicating that the safety confirmation information is unknown). "Unknown" flag) may be preset.

Further, as the safety registration data, any combination of safety status information, safety comment information, and safety location information among the safety confirmation information registered by the terminal 20 of this account may be stored in association with each other. .

(2) Functional configuration of terminal FIG. 1-6 is a diagram showing an example of the functions realized by the control unit 21 of the terminal 20 in this embodiment.
The control unit 21 includes, by way of example and not limitation, an application processing unit 211 as a functional unit for executing application processing according to an application processing program 281 stored in the storage unit 28.

FIG. 1-7 is a diagram showing an example of data etc. stored in the storage unit 28 of the terminal 20 in this embodiment.
The storage unit 28 stores, by way of example and not limitation, an application processing program 281 executed as application processing and an application ID 283 corresponding to the terminal 20 or the account of the user of the terminal 20.
Note that the friend management data of the account management database 155A may be stored in the storage unit 28 of the terminal 20 in a synchronized manner.

<Display screen>
In the display screen in this embodiment, an example in which only safety status information is registered as safety confirmation information will be exemplified.
Below, as an example and not a limitation, a case where the terminal 20 is a smartphone including the display section 24 of a vertically long display will be exemplified.

By way of example and not limitation, a smartphone is provided with a touch panel that functions as an input unit and is placed opposite its display, thereby forming a touch screen. When an element such as an icon, button, item, or input area is displayed on the display, if a part of the touch panel that is opposite to the area where the element is displayed is operated by the user, The program associated with the element or a subroutine of that program is executed.

Note that the transition of the display screen described below is only an example of the transition of the display screen for realizing the method of the present disclosure. Regarding the transition of display screens illustrated below, display of some display screens may be omitted, or other display screens may be added.

FIGS. 1-8 to 1-10 are diagrams showing examples of transitions of screens displayed on the display unit 24 of the terminal 20 in this embodiment.
here,
・Safety registration account = User Y of terminal 20Y. Account of user Y (not limited, but an example of the user of the first terminal) - Safety reference account = user An example of a display screen when the account is X (not limited, but an example of a terminal user) will be explained.

The left side of FIG. 1-8 is the home screen of a messaging application (an example of a chat application, not limited to), and the words "Messaging App" are displayed at the top center of the screen as the name of the messaging application. Further, on the right side at the top of the screen, an icon image and a user name ("user Y.Y" in this example) in the messaging application of the user of this terminal 20Y are displayed.

Also, below that, there is an area that shows the current location, page, etc. within the messaging application (hereinafter collectively referred to as the "in-app location display area"). In this example, the home screen Based on this, the word "Home" is displayed.

Below the in-app location display area is a disaster information display area, which is an area that displays disaster information to notify that a disaster has occurred.In this example, based on the occurrence of an earthquake, Disaster information (as an example, but not limited to, map information showing the epicenter, the words ``Disaster Occurred'', the words ``Announced on 20XX/08/04 09:39'', and the words ``Maximum seismic intensity: Upper 5'') , "Epicenter: Off the coast of Ibaraki Prefecture" and "Magnitude: 6.5") are displayed. In addition, at the bottom right inside the disaster information display area, there is a safety registration button BT1 indicated by an icon containing the words "Safety registration" for registering safety for each account of the messaging application (registering safety confirmation information). Displayed.

A friend/group list display area is configured below the disaster information display area in which a list of friends and groups in the messaging application is displayed.
In this example, the friend/group list display area includes a friend list for displaying a list of friends of the account of this terminal 20 (in this example, "user Y.Y") and the account of this terminal 20 as members. The screen is configured so that a group list for displaying a list of groups is displayed. In this example, by way of example and not limitation, the friends list is tapped and displayed in an expanded state.

The group list includes, by way of example and not limitation, the word "Group" and user Y. The number of groups to which Y belongs ("8" in this example) is displayed.
The friend list below has the word "friend" and user Y. The number of users (accounts) that Y has registered as friends ("4" in this example) is displayed.

When a user taps a group list or friend list, those lists expand and display. Specifically, by way of example and not limitation, a group icon, a group name, and the number of members belonging to the group are displayed as items in the group list below the group list. Further, by way of example and not limitation, friend icons and user names are displayed as a list of friend list items below the friend list.

On this screen, user X. Icon and user name corresponding to X, user C. The icon and user name corresponding to C, the user D. A list of icons, user names, etc. corresponding to D is displayed.

By way of example and not limitation, when the safety registration button BT1 is tapped by the user, a display as shown in the center of FIG. 1-8 is displayed, by way of example and not limitation.
This home screen is configured so that a safety registration area R1 for registering (setting) one's own safety information is displayed in an elevated manner, superimposed on the home screen on the left side of FIG. 1-8.

In the safety registration area R1, a message prompting the user to register (set) safety information (in this example, the words "Register safety" and "Let's tell everyone about safety") is displayed. ing. Below that, there is a safety button SBT (in this example, a button indicated by a smiley face icon and the word "safe") for setting safety as safety information, and a safety button SBT for setting unsafe as safety information. A danger button DBT (in this example, a button indicated by an icon of a non-smiling face and the word "danger") for setting the selected safety information, and a registration button BT3 for setting the selected safety information are displayed.

As an example and not a limitation, suppose that the danger button DBT is tapped by the user and the registration button BT3 is tapped by the user in the safety registration area R1 in the center of FIG. 1-8.
In this case, user Y. User X who is friends with Y. By way of example and not limitation, a screen as shown on the right side of FIG. 1-8 is displayed on the terminal 20X of X.

The right side of FIG. 1-8 shows an example of the home screen displayed on the display unit 24 of the terminal 20X, where user Y. Icon and user name corresponding to Y, user A. Icon and user name corresponding to user A, user B. A list of icons, user names, etc. corresponding to B is displayed.

In this case, user Y. Based on the fact that Y has set (registered) "danger" as safety information, in this example, user Y. In association with the Y icon, an icon DIC1 indicating danger (in this example, an icon with a non-smiling face, hereinafter appropriately referred to as a "first danger icon") is displayed in a superimposed manner.

In addition, user Y. If user Y has set "safety" as safety information, user Y. An icon SIC1 (in this example, a smiley face icon, hereinafter appropriately referred to as "first safety icon") indicating safety is displayed superimposed on the Y icon.

User X. X can check the safety information of users who are registered as friends.

The left side of FIG. 1-9 shows user Y. This is an example of a home screen on terminal 20Y of computer Y.
In this example, in the safety registration area R1 on the left side of FIG. 1-9, by way of example and not limitation, when the user taps the danger button DBT and taps the registration button BT3, the user X. By way of example and not limitation, a screen like the one shown in the center of FIG. 1-9 is displayed on the display unit 24 of the terminal 20X.

On the home screen displayed on the display unit 24 of this terminal 20X, user Y. Although user Y has set "danger" as safety information, unlike the example shown on the right side of Figure 1-8, user Y. No icon indicating danger is superimposed on the Y icon.

As an example and not as a limitation, if the user taps the talk item at the bottom of the screen on the home screen in the center of Figure 1-9, the display will transition to the talk list screen on the right side of Figure 1-9. do.

The talk list screen can be, by way of example and not limitation, a screen that allows a list of talk rooms in which messages have been sent to this terminal 20X to be confirmed.
In the in-app location display area of this talk list screen, based on the fact that it is a talk list screen, the word "Talk" and a back button indicated by the character "<" to return to the previous screen are displayed. ing.

Below the in-app location display area, a list of information about the talk rooms to which messages were sent to this terminal 20X is displayed. The talk room list item (talk list item) corresponding to each talk room contains the icon of the talk room (hereinafter referred to as the "talk room icon"), the talk room name, and whether the talk room is a group talk room. If it is, it is displayed in association with the number of members.
Here, in the case of a one-on-one talk room, the icon of the user to talk with can be used as an example, not as a limitation, and in the case of a group talk room, as an example and not as a limitation, the talk room icon can be the icon of the user set for the group. It can be an icon (group icon).
In addition, in the case of a one-on-one talk room, the talk room name can be the username of the talk partner, by way of example and not limitation, and in the case of a group talk room, it can be the group name, by way of example and not limitation. .

In this example, by way of example and not limitation, user Y. A talk room list item corresponding to the talk room with user A. A's talk room list item and user B. B's talk room list items, etc. are displayed.

In this example, each talk room list item is configured to be displayed in association with the number of unread messages, by way of example and not limitation.
By way of example and not limitation, user Y. In Y's talk room, user X. of terminal 20X. Based on the fact that X has one unread message (not viewed by user X.X), user Y. The number "1" is displayed in association with Y's talk room list item.

In this case, user Y. Based on the fact that user Y has set "danger" as safety information, user Y. In the talk room list item of Y, the talk room icon is <Icon DIC2 indicating that it is dangerous> (in this example, an icon indicating the word "danger", hereinafter referred to as "second danger icon") ) are displayed superimposed.

In addition, user Y. If user Y has set "safety" as safety information, user Y. In the talk room list item of Y, the talk room icon is <Icon SIC2 indicating that it is safe> (in this example, an icon with the word "safety" indicated, hereinafter referred to as the "second safety icon") ) are displayed superimposed.

User X. X can confirm the safety information of the user who sent the message to the terminal 20X.

In addition, instead of displaying the second safety icon SIC2 or the second danger icon DIC2 on the talk room icon, a "blue" icon is displayed for "safe" and a "red" icon is displayed for "danger". may be displayed. Further, the color and font of the characters indicating the name of the talk room may be changed and displayed.
Note that these methods of changing the display mode can be similarly applied to the friend list and group list.

On the left side of FIG. 1-10, user X. The talk list screen of X's terminal 20X is displayed. This talk list screen is different from the talk list screen shown on the right side of FIG. 1-9, and is different from the talk list screen shown on the right side of FIG. Although user Y has set "danger" as safety information, user Y. In the talk room list item of Y, the second danger icon DIC2 is not displayed superimposed on the talk room icon.

By way of example and not limitation, on the talk list screen on the left side of FIG. 1-10, user Y. When the user taps the talk room list item corresponding to Y, by way of example and not limitation, the talk room screen shown in the center of FIG. 1-10 is displayed.
This talk room screen shows, by way of example and not limitation, which page within the messaging application (in this example, the talk room) is currently displayed, below the area where the name of the messaging application is displayed at the top of the screen. A talk room name display area that includes the name of the talk room (hereinafter referred to as "talk room name") is provided as a type of area that indicates whether the talk room is currently in use. The chat room name display area can also be said to be an area indicating the page within the messaging application (in this example, the chat room) where the user is currently located.

In this example, the talk room name display area includes, by way of example and not limitation, a back button of "<" for returning to the previous screen, and a back button of "<" for returning to the previous screen. X is user Y. Characters indicating that this is a talk room for talking with Y as the other party (in this example, "Y.Y") and a safety information display icon IC1 for displaying safety information of users belonging to this talk room. Displayed.
Also, below that, user X and user Y. A talk area is configured for conversational conversation with user Y. Y's message is displayed on the right side of the screen as user X.Y. It is configured so that the message X is displayed.

At the top of the talk area, by way of example and not limitation, user Y. Safety information in the talk room to notify the safety information set by Y in the talk room (in this example, the text "Mr. Y has responded to the safety confirmation", the icon of the user of the terminal, and information related to the safety A user status icon ICYD (an icon of user Y.Y, the word "danger", and an icon without a smiling face) including information is displayed. Hereinafter, the user status icon will be appropriately referred to as a "user status icon (character and face icon corresponding to user name (icon), safe or dangerous)".

Note that in this display screen example, the user status icon is an icon that is a combination of the user's icon, the characters (safety/danger) corresponding to the safety status information, and the icon corresponding to the safety status information. but not limited to.
As an example and not a limitation, an icon that is a combination of the user's icon and characters (safety/danger) corresponding to the safety status information, or an icon that is a combination of the user's icon and an icon that corresponds to the safety status information. You may also do this.

As an example and not as a limitation, when the safety information display icon IC1 is tapped by the user on the talk room screen in the center of Figure 1-10, the talk room name is displayed as shown on the right side of Figure 1-10. User-specific safety information for displaying the safety information of each user included in this talk room is displayed in a format expanded below the area.
In this example, a user-specific safety information display area is configured to display user-specific safety information including safety information of users belonging to the talk room, and in this example, user-specific safety information , the second danger icon DIC2 is superimposed on the user Y. User X.Y icon and second safety icon SIC2 are displayed superimposed. An X icon is displayed.

<Processing>
FIG. 1-11 is a flowchart showing an example of the flow of processing executed by each device in this embodiment.
This figure shows an example of a process executed by the control unit 21 of the terminal 20X, a process executed by the control unit 21 of the terminal 20Y, and a process executed by the control unit 11 of the server 10, in order from the left side.

Note that the processing described below is only an example of processing for realizing the technique of the present disclosure, and is not limited thereto.
Another step may be added to the process described below, or some steps may be omitted (deleted) from the process described below.

Here, similar to the display screen,
・Safety registration account = User Y of terminal 20Y. Account of user Y (not limited, but an example of the user of the first terminal) - Safety reference account = user The following is an example of processing when the account is X (an example of a user of a terminal, not limited).

First, the control unit 21 of the terminal 20X, the control unit 21 of the terminal 20Y, and the control unit 11 of the server 10 execute a chat process, by way of example and not limitation (X110, Y110, S110).
In the chat process, by way of example and not limitation, each terminal 20 The control unit 21 executes content transmission/reception processing and display processing in the messaging service. Further, the control unit 11 of the server 10 executes relay processing of content transmitted from each terminal 20, by way of example and not limitation.

Note that the chat process may be executed between arbitrary steps during the process. Further, in this system, chat processing does not need to be executed.

Next, the control unit 11 of the server 10 performs the control based on, by way of example and not limitation, an input to the input/output unit 12 of the server 10 (by way of example and not limitation, user input (operation input, sound input, etc. by the user of the server 10)). Then, disaster information including the fact that a disaster has occurred and a request to register the safety of the users of each terminal 20 in this disaster is transmitted to each terminal 20 via the communication I/F 14 (S120).

Here, the disaster information may be configured to include, by way of example and not limitation, any combination of the following disaster elements A to H, and requesting the user to register their safety status.
・Disaster element A: A disaster has occurred.
・Disaster element B: Type of disaster (for example, not limited to, earthquake, flood, large-scale fire, etc.).
・Disaster element C: Scale of disaster (examples include seismic intensity, magnitude, river water level, fire spread range, etc., but not limited to).
・Disaster element D: Date and time of disaster occurrence.
・Disaster element E: Location of disaster occurrence.
・Disaster element F: Secondary effects of the disaster (examples include, but are not limited to, power outage, water outage, transportation status, etc.).
・Disaster Element G: How to deal with disasters (examples include evacuation sites and evacuation routes, etc., but not limited to).
・Disaster element H: Other disaster-related information.
Note that the disaster information may include information regarding the period and deadline for safety registration in the disaster.

In addition, when an arbitrary disaster occurs, the control unit 11 of the server 10 receives disaster situation information that is information related to the disaster that has occurred from a disaster information providing server (not shown) (as an example and not a limitation, the above-mentioned disaster elements A to D (information configured by). Then, the control unit 11 of the server 10 determines, based on the disaster situation information, that the disaster that has occurred is larger than a predetermined scale (for example, without limitation, a maximum seismic intensity of 5 or heavy rain) or is larger than a predetermined scale. In this case, disaster information may be automatically transmitted to each terminal 20.

Furthermore, when a disaster occurs and disaster situation information is received from the disaster information providing server, the control unit 11 of the server 10 causes the display unit 13 to display a display screen for selecting whether or not to transmit disaster information. You can do it like this. Then, the control unit 11 of the server 10 may transmit disaster information to each terminal 20 based on user input on the selection display screen.

When disaster information is received from the server 10 through the communication I/F 22, the control unit 21 of each terminal 20 displays the received disaster information on the display unit 24 (X120, Y120).

By way of example, and not limitation, when safety confirmation information is input based on the input to the input/output unit 23 of the terminal 20Y of the safety registration account, the control unit 21 of the terminal 20Y, by way of example and not limitation, The safety confirmation registration information including the confirmation information and the application ID of the safety registration account is transmitted to the server 10 via the communication I/F 22 (Y140).

When the communication I/F 14 receives the safety confirmation registration information from the terminal 20Y of the safety registration account, the control unit 11 of the server 10 generates safety information based on the received safety confirmation registration information.
The safety information can include, by way of example and not limitation, the application ID of the safety registration account transmitted in the safety confirmation registration information and the safety confirmation information.

Note that the control unit 11 of the server 10 may include, in the safety information, a user name linked to the application ID of the safety registration account transmitted in the safety confirmation registration information. In addition, the control unit 11 of the server 10 includes any combination of safety status information, safety comment information, and safety location information in the safety confirmation information transmitted in the safety confirmation registration information, as the safety information. (As an example, not a limitation, if safety status information and safety location information are included in the safety confirmation information, only the safety status information) may be included.

Then, by way of example and not limitation, the control unit 11 of the server 10 searches the account management database 155A and refers to accounts registered as friends in the friend management data of the safety registration account. Then, the safety information is transmitted to the terminal 20 of each account registered as a friend through the communication I/F 14 (S140).

Note that the control unit 11 of the server 10 may transmit the safety information to all terminals 20 in step S140.

When the safety information is received from the server 10 through the communication I/F 22, the control unit 21 of the terminal 20X displays the received safety information on the display unit 24 (X160).
In addition, in the terminal 20 of the safety reference account, the determination conditions for displaying the safety information on the display unit 24 include, by way of example and not limitation, any combination in the following cases.
・Display unconditionally (push notifications, etc.)
- When viewing the friend list (group list), it will be displayed in association with the safety registration account. - When viewing the talk list, it will be displayed in association with the safety registration account. - Viewing one-on-one talk rooms between the safety reference account and the safety registration account.・Displayed when viewing a group talk room of a group that includes a safety registration account

Furthermore, in the step S140, when the server 10 transmits the safety information to all the terminals 20, the control unit 21 of the terminal 20 of the safety reference account transmits the friend management data stored in the storage unit 28, by way of example and not limitation. See. If the friend management data includes the application ID of the safety registration account, the safety information may be displayed on the display unit 24.

<Effects of the first embodiment>
This embodiment describes processing related to chat (not limited, but an example of chat) with the user of the safety registration account (not limited, but an example of the user of the first terminal). The terminal 20 of the user (not limited to, but an example of a terminal user) of the safety reference account who performs the following operations (example) will collect safety information (or safety confirmation registration information) based on the input to the own terminal 20 by the user of the safety registration account. (an example of first information regarding the safety of the user of the first terminal) is received by the communication I/F 22. The terminal 20 of the user of the safety reference account is configured to display on the display unit 24 safety information associated with talk information (not limited to, but an example of chat information) related to the user of the safety registration account. ing.
As an example of the effect of the embodiment obtained by such a configuration, after receiving the first information regarding the safety of the user of the first terminal based on the input to the first terminal by the user of the first terminal, the first terminal The first information associated with the chat information related to the user can be displayed on the display section of the terminal to notify the user of the terminal. It is possible to realize a display that is easy for the terminal user to understand in a form associated with chat information.

Note that receiving the first information regarding the safety of the user of the first terminal based on the input to the first terminal by the user of the first terminal may include, but is not limited to, receiving the first information from the first terminal to the server. and the server receives the first information, the first information is transmitted from the server to the terminal and the terminal receives the first information, and the first information is transmitted from the first terminal to the terminal without going through the server. The first information may be transmitted directly and received by the terminal.

In addition, chat-related processing includes, but is not limited to, various processing for chatting, such as processing to send and receive information for chatting, processing to display content related to chatting, etc. It can be a concept that includes various types of processing to realize the above.
In addition, chat information is a concept that includes, by way of example and not limitation, a "friend list", "talk list", "talk room", etc. corresponding to (B1) to (B3) mentioned above in a messaging application. be able to. Note that the same applies to the above-mentioned "follow", "follower", etc.

Further, in this case, the terminal 20 of the user of the safety reference account can receive the safety information (or safety confirmation registration information) through the communication I/F 22 via the server 10.
As an example of the effect of the embodiment obtained by such a configuration, the first information can be appropriately received via the server.

In addition, in this case, the above talk information (an example of chat information, not a limitation) is a talk in a messaging application (an example of a chat, not a limitation), and a list of users associated with the user of the safety reference account. (an example, but not a limitation, of a list of users).
As an example of the effect of the embodiment obtained by such a configuration, after receiving the first information regarding the safety of the user of the first terminal based on the input to the first terminal by the user of the first terminal, the user of the terminal The first information associated with the chat information included in the list of users associated with the first information can be displayed on the display section of the terminal to notify the user of the terminal.

In addition, in this case, the above talk information (not limited, but an example of chat information) is used by the user of the safety registration account (not limited, but an example of the user of the first terminal) and the user of the safety reference account (not limited, but an example of the user of the first terminal). The first chat room may include information about a chat room (an example, but not limited to, a first chat room) that includes a first chat room (an example of a user of a terminal).
As an example of the effect of the embodiment obtained by such a configuration, after receiving the first information regarding the safety of the user of the first terminal based on the input to the first terminal by the user of the first terminal, the first terminal The first information associated with the first chat room including the user and the user of the terminal can be displayed on the display of the terminal to inform the user of the terminal. It is possible to realize a display that is easy for the terminal user to understand in a form associated with information about the first chat room including the first terminal user and the terminal user.

In addition, in this case, the above talk information is the icon of the one-on-one talk room (talk partner) included in the talk list (not limited to, but an example of a list of chat rooms) of the talk room that includes the user of the safety reference account. Information such as images (not limited to this, but an example of information about the first chat room included in the list of chat rooms that include the user of the device), and information that is included in the group list of the group chat room that includes the user of the safety reference account It is possible to include information such as an icon image of a group talk room (group) (not limited to this, but an example of information regarding the first chat room included in the list of chat rooms in which the user of the terminal is included).
As an example of the effect of the embodiment obtained by such a configuration, after receiving the first information regarding the safety of the user of the first terminal based on the input to the first terminal by the user of the first terminal, the user of the terminal The user of the terminal can be informed of the first information associated with the information about the first chat room included in the list of chat rooms including the first chat room by displaying the first information on the display section of the terminal.

Furthermore, in this case, the control unit 21 of the terminal 20 of the user of the safety reference account can perform control to change the display mode of the icon images and the like, based on the safety information.
As an example of the effect of the embodiment obtained by such a configuration, by changing the display mode of information regarding the first chat room including the user of the first terminal and the users of the terminal based on the first information, It is possible to realize a display that is easy for users to understand.

In addition, in this case, the safety information (not limited, an example of first information) is the user of the safety registration account (not limited, but an example of the user of the first terminal) and the user of the safety reference account (not limited, but the terminal This can be displayed in a chat room (an example, but not limited to, a first chat room) that includes (an example of a first chat room).
As an example of the effect of the embodiment obtained by such a configuration, the first information is displayed in an easy-to-understand manner in a first chat room that includes the user of the first terminal and the users of the terminal. It is possible to notify the terminal user of the safety status.

In addition, in this case, the safety information (not a limitation, but an example of first information) may be an image ( This is not limited to, but may be displayed in the above-mentioned talk room in association with the first image (an example of the first image).
As an example of the effect of the embodiment obtained by such a configuration, since the first information is displayed in the first chat room in association with the first image set by the user of the first terminal, the user of the first terminal The user of the terminal can easily recognize that the information is about the safety of the user.

<First modification (1)>
In the embodiment described above, an example in which only safety status information is registered as safety confirmation information is illustrated, but the present invention is not limited to this. Further, in the above embodiment, an example in which the safety registration account and the safety reference account are different is illustrated, but the present invention is not limited to this.

The left side of FIG. 1-12 shows user A. An example of a home screen displayed on the display unit 24 of the terminal 20A of A is shown.
On this home screen, user Y. Unlike the home screen of the terminal 20Y of the terminal 20Y, the user A. An icon image and a user name ("A.A" in this example) in A's messaging application are displayed.

The group list displays a list of icons and group names (number of members) corresponding to tennis circles, icons and group names (number of members) corresponding to seminar friends, etc. as group list items.
The friend list also includes user B as an item in the friend list. Icon and user name corresponding to user B, user C. The icon and user name corresponding to C, the user D. A list of icons, user names, etc. corresponding to D is displayed.

By way of example and not limitation, when the safety registration button BT1 is tapped by the user, a display as shown in the center of FIG. 1-12 is displayed, by way of example and not limitation.
In this example, a safety message input area for inputting a safety message, which is a type of safety comment information, is configured below the safety button SBT and the danger button DBT in the safety registration area R1.

The safety message input area includes the characters "safety message" as well as an area for inputting a safety message (an area where the input safety message is displayed).
Furthermore, below that, there is an area for selecting a standard message for a safety message. In this example, the standard text for a safety message is, by way of example and not limitation, the text ``Injured'', the text ``Trapped'', the text ``Caught in a fire'', and the text ``Evacuating''. Text is prepared in advance, and each is displayed as an icon that can be selected by tapping.

Further, below that, a current location input area is configured for inputting the current location, which is a type of safety location information. The current location input area displays the text "Current location", an area for inputting the current location (an area that displays the entered current location), and a current location acquisition button for obtaining the current location. has been done.

A registration button BT3 for setting the selected/input safety information is provided at the bottom of the screen.

Note that the safety registration area R1 may be configured to register only one of the safety comment information and the safety location information.

As an example and not a limitation, in the safety registration area R1 in the center of FIG. After being tapped by user A, the registration button BT3 is pressed by user A.A. When tapped by user A. An example of the home screen displayed on A's terminal 20A is shown on the right side of FIG. 1-12.

In the disaster information display area, the safety registration button BT1 is not displayed, and a user status icon is displayed instead. In this example, user A. A user status icon ICAS indicating the status of A (in this example, user A.A, safe) is displayed.

Also, user B. Based on the fact that user B has set "danger" as safety information, user B. A first danger icon DIC1 is displayed superimposed on the icon corresponding to B. User C. Based on the fact that user C has set "danger" as safety information, user C. A first danger icon DIC1 is displayed superimposed on the icon corresponding to C. User D. Based on the fact that user D has set "safety" as the safety information, user D. A first safety icon SIC1 is displayed superimposed on the icon corresponding to D.

The left side of FIG. 1-13 shows user A. The talk list screen of A's terminal 20A is displayed. This talk list screen is different from the talk list screen on the right side of Figure 1-9, and is located below the in-app location display area, and displays a list of information about talk rooms in which messages have been sent to this terminal 20A. A second disaster information display area, which is an area showing second disaster information for notifying on the talk list screen that a disaster has occurred, is configured above the area. In this example, based on the occurrence of an earthquake, the second disaster information (as an example, not a limitation) and the words "Announced on 20XX/08/04 09:39" and "Maximum seismic intensity: 5 upper" are added. and the words "Earthquake Occurrence" are displayed.Furthermore, based on the fact that User A.A has set himself to be "safe," a user status icon ICAS (User A.A. A.Safety)) is displayed in the second disaster information display area.

In this example, by way of example and not limitation, the talk room list items include a talk room list item for a tennis circle, user D. D's talk room list item, user B. B's talk room list item, seminar buddy's talk room list item, user C. C's talk room list item, user E. E's talk room list items, etc. are displayed.

In this example, the unread number "13" is displayed in association with the tennis circle talk room list item, and user D. The unread number "2" is displayed in association with the talk room list item of user B. An unread count of "1" is displayed in association with user B's talk room list item, an unread count of "2" is displayed in association with the seminar companion's talk room list item, and user C. The unread number "2" is displayed in association with the talk room list item of user E.C. The unread number "1" is displayed in association with E's talk room list item.

Also, user D. Based on the fact that user D has set "safety" as the safety information, user D. A second safety icon SIC2 is displayed superimposed on the icon corresponding to the talk room list item D. User B. Based on the fact that user B has set "danger" as safety information, user B. A second danger icon DIC2 is superimposed on the icon corresponding to the talk room list item B. User C. Based on the fact that user C has set "danger" as safety information, user C. A second danger icon DIC2 is superimposed on the icon corresponding to the talk room list item C. User E. Based on the fact that user E has set "safety" as the safety information, user E. A second safety icon SIC2 is superimposed on the icon corresponding to the talk room list item E.

In this example, even if any member belonging to the group talk room has set safety information, an icon based on the safety information is not superimposed on the icon corresponding to the group talk room.
In this case, even if any member belonging to the tennis circle group talk room has set safety information, the icon corresponding to the tennis circle talk room list item will have the second safety icon SIC2 and None of the second danger icons DIC2 is displayed in a superimposed manner. Even if one of the members belonging to the group talk room of seminar friends sets safety information, the second safety icon SIC2 and the second danger icon will be displayed on the icon corresponding to the talk room list item of seminar friends. None of the icons DIC2 are displayed in a superimposed manner.

In addition, on this talk list screen, below the user name corresponding to the talk room list item, the safety location information entered and registered by the user in the current location input area described above and the safety message input area described above are displayed. Information based on input and registered safety comment information is displayed.
In this example, by way of example and not limitation, user B. Below the characters "B.B" corresponding to B. The current location "Tsukuba City" registered by user B. The composite safety information "Tsukuba/I'm injured" is displayed as information that is a combination of the safety message "I'm injured" registered by B.
User C. C and user E. Regarding E, the registered information is similarly displayed.

In this display screen example, composite safety information is displayed under the user name of the talk room list item, but the present invention is not limited to this.
As an example and not a limitation, composite safety information may be displayed to the right of the user name. Further, in this case, information based on the latest content (message) in the talk room may or may not be displayed below the user name in the talk room list item.

In addition, as an example and not a limitation, an icon based on safety status information that is displayed superimposed on the user's icon (based on tapping the second safety icon SIC2 or second danger icon DIC2, a speech bubble, etc.) Composite safety information may be displayed.

Furthermore, it is not essential to display both the safety location information and the safety comment information on the talk list, and they may be displayed on separate screens.

Further, the composite safety information may be displayed on a screen (such as a home screen) on which the friend list mentioned above is displayed.
Further, either one of the safety location information and the safety comment information may be displayed on a screen (such as a home screen) on which the friend list described above is displayed.

By way of example and not limitation, on the talk list screen on the left side of Figure 1-13, user B. When the talk room list item B is tapped by the user, by way of example and not limitation, the talk room screen on the right side of FIG. 1-13 is displayed. This screen differs from the talk room screen shown in the center of Figure 1-10, in that while safety information within the talk room is not displayed in the talk area, safety information for each user is displayed in the user-specific safety information display area. There is.

In this example, the chat room name display area includes, by way of example and not limitation, user A. A is user B. Characters (in this example, "B.B") indicating that this is a talk room for talking with B as the other party are displayed.
In addition, in the user-specific safety information display area below the user B, the second danger icon DIC2 is superimposed and displayed as user-specific safety information, by way of example and not limitation. User A.B's icon and the second safety icon SIC2 are displayed superimposed. A icon is displayed.

Also, user B. The text content sent from B is displayed on the left side of the talk area, informing that B has injured his leg in the earthquake and is unable to move.

FIG. 1-14 is a flowchart showing an example of the flow of processing executed by each device in this modification.
This figure shows an example of a process executed by the control unit 21 of the terminal 20X, a process executed by the control unit 21 of the terminal 20Y, and a process executed by the control unit 11 of the server 10, in order from the left side.

Here, unlike the display screen,
・Safety registration account and safety reference account = User X. of terminal 20X. X (user A.A of terminal 20A on the display screen)
・Safety registration account = User Y of terminal 20Y. Y (users of terminals 20B to 20E on the display screen)
The following is an example of the processing when

By way of example and not limitation, the control unit 21 of the terminal 20X displays disaster information on the display unit 24 (X120), based on the input to the input/output unit 23 of the terminal 20X of the safety registration account, by way of example and not limitation. , it is determined whether or not to input safety confirmation information (X130). If it is determined that the safety confirmation information is to be input (X130: YES), the control unit 21 of the terminal 20X accepts the safety confirmation information and transmits the safety confirmation registration information to the server 10 (X140). If it is determined that safety confirmation information is not input (X130: NO), the control unit 21 of the terminal 20X skips step X140.

Similarly, the control unit 21 of the terminal 20Y executes steps Y110 to Y140.

When receiving safety confirmation registration information from the terminal 20X through the communication I/F 14 (S130), the control unit 11 of the server 10 generates safety information based on the received safety confirmation registration information and transmits it to each terminal 20. (S140). The same applies to the case where safety confirmation registration information is received from another terminal (by way of example and not limitation, the terminal 20Y).

If the communication I/F 22 determines that the safety information has been received from the server 10 (X150: YES), the control unit 21 of the terminal 20X displays the received safety information on the display unit 24 (X160).
Note that if it is determined that the safety information has been received multiple times, the control unit 21 of the terminal 20X may display the received safety information on the display unit 24 each time it is received, or if the safety information is registered differently. The safety information received only by the user may be displayed on the display unit 24.

Similarly, the control unit 21 of the terminal 20Y executes steps Y150 to Y160.

In this modification, the terminal 20 of the user of the safety reference account generates safety information (or safety confirmation registration information) regarding the safety of the user of the own terminal 20 based on the input to the own terminal 20 by the user of the own terminal 20. (This is not a limitation, but is an example of the third information regarding the safety of the user of the terminal) which is transmitted through the communication I/F 122.
As an example of the effect of the modified example obtained by such a configuration, third information regarding the safety of the terminal user is transmitted based on input to the terminal by the terminal user to inform others of the terminal user's safety. be able to.

<First modification (2)>
In the above-mentioned embodiment, an example in which safety information is displayed in association with a user account is exemplified, but the present invention is not limited to this. By way of example and not limitation, safety information may be displayed in association with a group account to which the safety registration account belongs.

FIG. 1-15 is a diagram showing an example of information stored in the storage unit 15 of the server 10 in this modification.
The storage unit 15 stores, by way of example and not limitation, an application management processing program 151 executed as application management processing, account registration data 153, an account management database 155, and a group management database 157.

The group management database 157 is a database for managing information regarding groups, and an example of the data structure of the group management database 157 is shown in FIG. 1-16.
Group management data is stored in the group management database 157 as management data for each group.

Each group management data stores, by way of example and not limitation, a group ID, a group name, and group member data.

The group ID is information for identifying a group managed by group management data.
This group ID is preferably a unique value for each group, and is set and stored by the server 10 as an example and not a limitation.

The group name is the name of this group, and by way of example and not limitation, the name registered by the user of the terminal 20 when creating a group is stored.

Group member data is data for storing the application ID of an account that is a member of this group (belongs to the group).As an example and not a limitation, when a user registers to participate in a group, the server registers for group participation. The application ID of the user who made the request is added and updated.

Note that the group management data may be stored in association with the application ID of the account representing the group.

The left side of FIG. 1-17 shows user A. The talk list screen of A's terminal 20A is displayed. On this talk list screen, from the display screen on the left side of Figure 1-13, B. Based on the fact that the talk room with B was viewed, B. The number of unread messages with B is "0" (not displayed).

As an example, and not as a limitation, when a user taps a talk room list item for seminar mates on the talk list screen on the left side of Figure 1-17, the talk room screen on the right side of Figure 1-17 is displayed, as an example and not as a limitation. Ru.
This screen differs from the display screen on the right side of FIG. 1-13 in that the talk room name display area includes user A. Characters (in this example, "Seminar Friends (4)" (the number is the number of members)) indicating that A is a talk room for talking with a group of seminar friends are displayed.

In the user-specific safety information display area, user B. is displayed with a second danger icon DIC2 superimposed as user-specific safety information. User A.B's icon and the second safety icon SIC2 are displayed superimposed. User D.A's icon and the second safety icon SIC2 are displayed superimposed. User F.D icon and second danger icon DIC2 are displayed superimposed. The F icon is displayed.

Also, in the talk area, user D. As the content sent from user B. Text content confirming that user B is scheduled to present at an academic conference in Tsukuba today is displayed, and below that is text content confirming that user F. The content sent from user B was that an earthquake with a seismic intensity of lower 5 occurred in Tsukuba. Text content that worries B is displayed.

On the left side of FIG. 1-18, user A. The talk list screen of A's terminal 20A is shown.
This talk list screen differs from the talk list screen on the left side of Figure 1-13 in that if any member belonging to a group talk room has set safety information, the icon corresponding to the group talk room will display the safety information. FIG. 3 is a diagram illustrating an example in which images (such as icons) based on information are displayed in association with each other.

In this example, when a member belonging to a group talk room is setting safety information, effect safety information based on the safety information is additionally displayed on the icon corresponding to the group talk room.
As an example and not a limitation, if the safety information of all members belonging to a group talk room is set to "safe", the first effect information SFA (white object, not a limitation) corresponds to the group talk room. will be displayed in addition to the icon.
As an example and not a limitation, if the safety information of one or more members belonging to a group talk room is set to "danger", the second effect information DFA (as an example and not a limitation, a red object) will be displayed in the group talk room. will be added to the corresponding icon.

In this example, the first effect information SFA is displayed on the icon corresponding to the tennis circle group talk room based on the fact that all members belonging to the tennis circle group talk room have set their safety information to "safe". It is additionally displayed.
In addition, in this example, based on the fact that one of the members belonging to the group talk room of seminar friends has set "danger" as the safety information, the icon corresponding to the group talk room of seminar friends is displayed as follows. 2 effect information DFA is additionally displayed.

As an example, and not as a limitation, when a user taps the talk room list item of seminar mates on the talk room list screen on the left side of Figure 1-18, the talk room screen on the right side of Figure 1-18 is displayed, as an example and not as a limitation. be done.
This screen is similar to the talk room screen on the right side of FIG. 1-17, so the explanation will be omitted.

Note that the method of changing the display mode is not limited to the above.
As an example and not a limitation, if the safety information of all members belonging to a group talk room is set to "safe", an icon corresponding to the group talk room will be displayed in "blue" and one person belonging to the group talk room will be displayed. If the safety information of the above members is set to "danger", an icon corresponding to the group talk room may be displayed in "red".
This can be further subdivided, and icons corresponding to the group talk room can be displayed in yellow or red based on the number (or percentage) of members who belong to the group talk room and are set to be at risk. , the above effects may be displayed.
Further, the present invention is not limited to these, and the color and font of the characters indicating the name of the group talk room may be changed and displayed.

When displaying in the talk list, by way of example and not limitation, upon receiving the safety confirmation registration information, the control unit 11 of the server 10 refers to the group management database 157 and searches for the group to which the safety registration account belongs. Then, for each group to which the safety registration account belongs, the safety registration data of each application ID registered in the group member data is referred to.
When the safety registration data of all application IDs registered in a certain group member data is "safe", the control unit 11 of the server 10 provides safety information for that group (hereinafter referred to as "group safety information"). is generated in a first manner indicating that all members are "safe". If the safety registration data of all application IDs are not "safe," the control unit 11 of the server 10 generates group safety information for that group in a second manner indicating that all members are not "safe."
Then, the control unit 11 of the server 10 transmits the group safety information to the terminals 20 of all accounts registered in the group member data through the communication I/F 14.

In the above embodiment and this modification, the terminal 20 of the user of the safety reference account is connected to a talk room (not limited to, but an example of a first chat room) such as a one-on-one talk room or a group talk room that includes safety information. A configuration is shown in which the control unit 21 controls to change the display mode of information regarding the talk room based on the information regarding the safety of the included users.
As an example of the effect of the embodiment obtained by such a configuration. Appropriately changing the display mode of information regarding the first chat room based on information regarding the safety of users included in the first chat room including the user of the first terminal and the user of the terminal, including the first information. can.

<First modification (3)>
In the above embodiment, the safety status information is classified into two classes, "safe" and "dangerous", but the present invention is not limited to this. Other safety status information may also be included.
As an example and not a limitation, safety information may be set in three classes: "safe,""dangerous," and "outside area."

The left side of FIG. 1-19 shows user A. The home screen of A's terminal 20A is displayed. This screen is different from the home screen in the center of Figure 1-12, in the safety registration area R1, there are two safety buttons SBT for setting safe as safety information and one for setting unsafe as safety information. In addition to the danger button DBT, this is a diagram showing an example in which an out-of-area button ABT (in this example, a button indicated by the characters "outside the area") is displayed for setting out of the area as safety information. be.

By way of example and not limitation, being "out of area" means that the user is located in a location that is not affected by the currently occurring disaster, and by way of example and not limitation, the disaster is an earthquake. In this case, the current location indicated by the user's terminal 20 is located at a position more than a set distance (for example, not limited to 200 km) from the epicenter.

As an example and not a limitation, in the safety registration area R1 on the left side of FIG. 1-19, the safety button SBT is pressed when the user A. After being tapped by user A, the registration button BT3 is pressed by user A.A. It is tapped by A, and the display changes to the home screen (not shown). On this home screen, when the user taps the talk item at the bottom of the screen, by way of example and not limitation, the talk list screen shown on the right side of FIG. 1-19 is displayed on the display unit 24 of the terminal 20A.

In this talk list screen, unlike the talk list screen on the left side of FIG. 1-13, user E. Based on the fact that user E has set "outside area" as the safety information, user E. An out-of-area icon AIC (in this example, an icon containing the words "outside area") indicating that the area is outside the area is displayed superimposed on the icon corresponding to E.

In addition to these, as an example and not a limitation, there are other words such as "genki" to indicate that you are feeling well, "a little energetic" to indicate that you are a little energetic, "not very energetic" to indicate that you are not very energetic, and "not very energetic" to indicate that you are not very energetic. The safety status information may include information such as "not feeling well" indicating that the person is not well.

<First modification (4)>
In the above embodiment, the safety information based on the safety confirmation registration information is generated in the server 10, but the present invention is not limited thereto. By way of example and not limitation, the safety information may be generated at the terminal 20.

In this case, by way of example and not limitation, the control unit 21 of the terminal 20Y of the safety registration account generates safety information upon receiving the safety confirmation registration information. Then, the control unit 21 of the terminal 20Y of the safety registration account refers to the friend management data of the safety registration account, and sends safety information to each terminal 20 of the safety registration account and the account that has been registered as a friend, by way of example and not limitation. do.

Note that, by way of example and not limitation, the control unit 21 of the terminal 20Y of the safety registration account may transmit safety information to each terminal 20 via the server 10. Moreover, the control unit 21 of the terminal 20Y of the safety registration account may transmit the safety information to all the terminals 20 by using broadcast communication, by way of example and not limitation.

<Second example>
In the first embodiment, an example is illustrated in which safety registration is performed only once on the terminal 20 of the safety registration account. The second embodiment is an example in which safety information is updated in the terminal 20 of the safety reference account by the user of the terminal 20 of the safety registration account repeatedly registering safety.

The content described in the second embodiment is applicable to any of the other embodiments and other modifications.
In addition, the same reference numerals are given to the same constituent elements as those already mentioned, and the explanation thereof will be omitted.

<Display screen>
In the display screen in this embodiment, an example in which only safety status information is registered as safety confirmation information will be exemplified. Also, a case will be illustrated in which safety information is displayed only in the talk room on the terminal 20 of the safety reference account.

On the home screen on the left side of FIG. 2-1, user Y. Based on the fact that Y has set "danger" as the safety information, the user status icon ICYD (user Y.Y, danger) is displayed.

Also, user Y. The safety registration area R1 is displayed in an elevated manner superimposed on the home screen of the terminal 20Y of Y. This safety registration area R1 is used in this embodiment to change safety information.

In the safety registration area R1, a message prompting the user to set safety information (in this example, the words "Confirm safety" and "Let's tell everyone about safety") is displayed. Below that, a safety button SBT and a danger button DBT are provided. Further, at the bottom of the screen, a change button BT5 for changing the safety information to the selected safety information is displayed.

By way of example and not limitation, user X. An example of the talk list screen displayed on the terminal 20X of X is shown in the center of FIG. 2-1. This talk list screen is similar to the display screen on the left side of FIG. 1-10, so a description thereof will be omitted.

By way of example and not limitation, on the talk list screen in the center of FIG. 2-1, user Y. When the user taps the talk room list item corresponding to Y, the talk room screen on the right side of FIG. 2-1 is displayed, by way of example and not limitation.

At the top of the talk area of this talk room screen, user Y. The first notification information NI1 (in this example, the text "Mr. Y. has responded to the safety confirmation") and the user status icon ICYD (user Y. Y, Danger)) is displayed.
Below that, by way of example and not limitation, user Y. Text content (``Was the earthquake okay?'') is displayed as the content from Y.

Also, below that, user Y. Based on the fact that Y has changed his safety information from "dangerous" to "safe," the second notification information NI2 whose safety status has been changed to safe (in this example, "Mr. Y. ” and the user status icon ICYS (user Y.Y, safe) are displayed.
Below that, by way of example and not limitation, user Y. Text content (“We have evacuated!”) is displayed as the content from Y.

<Processing>
FIG. 2-2 is a flowchart showing an example of the flow of processing executed by each device in this embodiment.
This figure shows an example of a process executed by the control unit 21 of the terminal 20X, a process executed by the control unit 21 of the terminal 20Y, and a process executed by the control unit 11 of the server 10, in order from the left side.

By way of example and not limitation, when steps S120, X120, and Y120 are executed, a safety confirmation process is executed (X210, Y210, S210).

FIG. 2-3 is a flowchart showing an example of the flow of safety confirmation processing. The diagram can be viewed in the same way as Figure 2-2.
By way of example and not limitation, the control unit 21 of the terminal 20X executes steps X2130 to X2160, similar to steps X130 to X160 in FIG. 1-14. Further, the control unit 21 of the terminal 20Y executes steps Y2130 to Y2160, by way of example and not limitation, similar to steps Y130 to Y160 in FIG. 1-14. By way of example and not limitation, the control unit 11 of the server 10 executes steps S2130 to S2140, similar to steps S130 to S140 in FIG. 1-14.

Returning to FIG. 2-2, when the safety confirmation process is executed, the control unit 21 of the terminal 20X, the control unit 21 of the terminal 20Y, and the control unit 11 of the server 10 determine whether or not to end the process. (X220, Y220, S220). Here, the conditions for determining whether or not to terminate the process include, but are not limited to, a case where a specific period of time (one week, not a limitation) has elapsed since the date and time of the disaster, and a condition based on user input on the server 10. Examples include a case where the confirmation service is selected to be stopped.

If it is determined that the process should be terminated (X220: YES, Y220: YES, S220: YES), the control unit 21 of each terminal 20 and the control unit 11 of the server 10 terminate the process.
If it is determined that the process is not to end (X220: NO, Y220: NO, S220: NO), the control unit 21 of each terminal 20 and the control unit 11 of the server 10 cause the safety confirmation process to be executed again (X210, Y210). , S210).

Note that the control unit 21 of each terminal 20 and the control unit 11 of the server 10 may execute the chat process at any timing before or after the safety confirmation process.

FIG. 2-4 is a timing chart showing an example of the timing of processing executed by each device in this embodiment.
Here, similar to the display screen,
・Safety registration account = User Y of terminal 20Y. Account of user Y (not limited, but an example of the user of the first terminal) - Safety reference account = user The following is an example of processing when the account is X (an example of a user of a terminal, not limited).

As an example and not a limitation, when the safety confirmation process is executed and the terminal 20Y receives input (operation input, etc.) of the safety confirmation registration information (Y2130), the first safety confirmation registration information is transmitted to the server 10 ( Y2140) (timing "TM110"). Then, the server 10 receives the first safety confirmation registration information (S2130: YES).
The control unit 11 of the server 10 generates first safety information based on the first safety confirmation registration information and transmits it to each terminal 20 (S2140) (timing "TM120").
Upon receiving the first safety information, the terminal 20X executes display processing (X2160) (timing "TM130").

The safety confirmation process is executed again, and when the input of safety confirmation registration information is accepted at the terminal 20Y (Y2130), the first safety confirmation registration information is transmitted to the server 10 (Y2140) (timing "TM140"). Then, the server 10 receives the second safety confirmation registration information (S2130: YES).
The control unit 11 of the server 10 generates second safety information based on the second safety confirmation registration information and transmits it to each terminal 20 (S2140) (timing "TM150").
Upon receiving the second safety information, the terminal 20X executes display processing (X2160) (timing "TM160").

Note that when the control unit 11 of the server 10 receives the second safety confirmation registration information, it may perform a safety comparison process between the first safety confirmation registration information and the second safety confirmation registration information. Then, if there is no difference between the first safety confirmation registration information and the second safety confirmation registration information, the second safety information may not be transmitted to each terminal 20.

In addition, if there is a difference between the first safety confirmation registration information and the second safety confirmation registration information as a result of the safety comparison process, the control unit 11 of the server 10 determines that the safety status of the safety registration account has changed. Safety change information indicating that the situation has occurred may be transmitted to each terminal 20.

Although this timing chart shows an example in which the safety confirmation registration information is input twice on the terminal 20Y of the safety registration account, the same process can be executed when the safety confirmation registration information is input three or more times. can.

<Effects of the second embodiment>
In this embodiment, the terminal 20 of the user of the safety reference account receives the first safety information (not a limitation, but an example of the first information) by the user of the safety registration account (not a limitation, but an example of the user of the first terminal). ) is changed to the second safety information (not a limitation, but an example of the second information), a configuration is shown in which the second safety information is received by the communication I/F 22.
As an example of the effect of the embodiment obtained by such a configuration, even if the first information regarding the safety of the user of the first terminal is changed to second information by the user of the first terminal, the terminal is 2 information can be reliably acquired.

In addition, in this case, the second safety information includes the user of the safety registration account (not limited, an example of the user of the first terminal) and the user of the safety reference account (not limited, but an example of the user of the terminal) It may be displayed in a chat room (an example, but not limited to, a first chat room).
As an example of the effect of the embodiment obtained by such a configuration, the second information can be notified to the terminal user in an easy-to-understand form by displaying it in a first chat room that includes the first terminal user and the terminal users. I can do it.

<Second modification (1)>
In the above embodiment, when the second safety confirmation registration information is registered on the terminal 20 of the safety registration account, the terminal 20 of the safety reference account automatically receives the second safety information. It is not limited to this.
As an example and not a limitation, the second safety information may be received when a set condition is met, such as when a specific display element is displayed on the terminal 20 of the safety reference account.

In the display screen in this modification, an example will be exemplified in which only safety status information is registered as safety confirmation information. Further, a case will be illustrated in which safety information is displayed on the friend list and the user's profile screen on the terminal 20 of the safety reference account. Note that the safety information may be displayed on the talk list screen or the talk room screen.

The left side of FIG. 2-5 shows user Y. A safety information change area for changing the safety information that has already been set is displayed in an elevated manner superimposed on the home screen of the terminal 20Y of Y. This home screen is similar to the display screen on the left side of FIG. 2-1, so a description thereof will be omitted.

By way of example and not limitation, user X. An example of the home screen displayed on the terminal 20X of X is shown in the center of FIG. 2-5.

On this home screen, user Y. Icon and user name corresponding to Y, user A. Icon and user name corresponding to user A, user B. A list of icons, user names, etc. corresponding to B is displayed. In this example, user Y. Based on the fact that Y has set "danger" as safety information, user Y. The first danger icon DIC1 is superimposed and displayed in association with the icon of user A.Y. Based on the fact that A has set "safety" as the safety information, user A. The first safety icon SIC1 is displayed superimposed in association with the icon of user B. Based on the fact that user B has set "danger" as safety information, user B. A first danger icon DIC1 is displayed in a superimposed manner in association with the icon B.

By way of example and not limitation, on the home screen in the center of FIG. 2-5, user Y. When the user taps the friend list item corresponding to Y. As an example and not a limitation, user Y.Y. on the right side of FIG. The display changes to the profile screen corresponding to Y.

A profile screen may be, by way of example and not limitation, a screen that displays information regarding the selected user's profile. This profile screen includes, by way of example and not limitation, the icon image of each user's messaging application, user name, information regarding safety, a button for talking with that user, and voice information for that user. A button for making a call, a button for making a video call with this user, etc. can be displayed.

In this example, user Y. Based on the fact that Y has changed his safety information from "dangerous" to "safe," by way of example and not limitation, a message appears at the top of the screen that indicates user Y. Text indicating that Y has changed his safety information (Y.Y's status has changed), icons (user Y.Y's icon and second danger icon DIC2 → second safety icon SIC2), etc. Push notification PN1 displayed in push format is displayed.

Also, user Y. Below the icon representing Y's profile and the user name is the user Y. A second safety icon SIC2 is displayed as information regarding Y's safety.
More specifically, on the home screen in the center of FIG. 2-5, user Y. The first danger icon DIC1 was displayed in association with the Y icon. User Y. The first information (danger) regarding safety is changed to the second information (safety) by user Y. Based on the display of user Y's profile screen, user Y. A second safety icon SIC2 is displayed in association with the Y icon.

In this example, on the home screen in the center of FIG. 2-5, user Y. When the user taps the friend list item corresponding to user Y, the control unit 21 of the terminal 20X controls the user Y. Display the profile screen corresponding to Y. Then, the control unit 21 of the terminal 20X transmits the safety update request information to the server 10 via the communication I/F 22, and based on this, the information to be displayed in the push notification described above is transmitted from the server 10 to the terminal 20X. be done. Then, the control unit 21 of the terminal 20X displays the push notification described above based on the received information, and also displays an icon (in this example, the icon corresponding to the changed safety information) The second safety icon SIC2) is displayed.

Note that when the control unit 21 of the terminal 20X transmits the safety update request information to the server 10, based on this, the changed safety information (in this example, safety) is transmitted from the server 10 to the terminal 20X. . Based on the received information, the control unit 21 of the terminal 20X displays an icon (in this example, a second safety icon SIC2 corresponding to safety) corresponding to the changed safety information. Furthermore, the control unit 21 of the terminal 20X distinguishes between the previously received safety information before the change (“danger” in this example) and the newly received safety information after the change (“safe” in this example). Based on the above information, information for displaying the push notification may be generated and the push notification may be displayed.

Note that even if the profile screen on the right side of FIG. 2-5 is displayed, the push notification described above may not be displayed.
In addition, in the friend list on the home screen in the center of Figure 2-5, safety information (first safety icon SIC1 or first danger icon DIC1) is not displayed in association with the users included in the list, but the right side of Figure 2-5 The above push notification may be displayed when the profile screen of the user is displayed.

Also, on the home screen in the center of FIG. 2-5, user Y. When the user taps the friend list item corresponding to user Y, the control unit 21 of the terminal 20X controls the user Y. The profile screen corresponding to Y is displayed, but the icon corresponding to the safety information before the change (in this example, the second danger icon DIC2 corresponding to danger) is also displayed. Then, the control unit 21 of the terminal 20X transmits safety update request information to the server 10, and based on this, the changed safety information (in this example, safety) is transmitted from the server 10 to the terminal 20X. do. Then, the control unit 21 of the terminal 20X changes the display of the icon corresponding to the safety information before the change (in this example, the second danger icon DIC2 corresponding to danger) to the icon corresponding to the safety information after the change (in this example, the second danger icon DIC2 corresponding to danger). Then, control may be performed to change to the second safety icon SIC2) corresponding to safety.

In addition, as an example and not a limitation, an icon (second safety icon SIC2 or second danger icon DIC2) based on safety status information displayed superimposed on the icon corresponding to the user's talk room list item on the talk list screen described above. ) may cause the user's profile screen to be displayed.
By way of example and not limitation, user B. When the second danger icon DIC2 displayed superimposed on the icon corresponding to B's talk room list item is tapped, user B ．． B's profile screen may be displayed. In this case, user B. A second danger icon DIC2 can be displayed on B's profile screen.

In addition, when safety information is registered by the safety registration account, the terminal 20 of the safety reference account displays the user's talk room list item (as an example and not a limitation, an icon corresponding to the user's talk room list item) An icon based on safety status information) may be illuminated and displayed. Then, when a glowing item is tapped, the user's profile screen may be displayed.

Furthermore, as described above, the safety location information and the safety comment information may be displayed on separate screens.As an example and not a limitation, one of these information may be displayed on the talk list screen, and the other information may be displayed on separate screens. may be displayed on the profile screen.

Further, the composite safety information may be displayed on the profile screen.
Further, either one of the safety location information and the safety comment information may be displayed on the profile screen.

Further, although different from the above example, safety information may not be displayed on the profile screen. As an example, the safety information is displayed on the home screen described above, but may not be displayed on the profile screen described above.

Further, instead of the profile screen described above, a dedicated screen for displaying safety information may be displayed.

FIG. 2-6 is a timing chart showing an example of the timing of processing executed by each device in this modification.
Here, similar to the display screen,
・Safety registration account = User Y of terminal 20Y. Account of user Y (not limited, but an example of the user of the first terminal) - Safety reference account = user The following is an example of processing when the account is X (an example of a user of a terminal, not limited).

As an example and not a limitation, when the safety confirmation process is executed and the input of safety confirmation registration information is accepted at the terminal 20Y (Y2130), the first safety confirmation registration information is transmitted to the server 10 (Y2140) (timing " TM210”). Then, the server 10 receives the first safety confirmation registration information (S2130: YES).
The control unit 11 of the server 10 generates first safety information based on the first safety confirmation registration information and transmits it to each terminal 20 (S2140) (timing "TM220").
Upon receiving the first safety information, the terminal 20X executes display processing (X2160) (timing "TM230").

The safety confirmation process is executed again, and when the input of safety confirmation registration information is accepted at the terminal 20Y (Y2130), the first safety confirmation registration information is transmitted to the server 10 (Y2140) (timing "TM240"). Then, the server 10 receives the second safety confirmation registration information (S2130: YES). The control unit 11 of the server 10 generates second safety information based on the second safety confirmation registration information.

At terminal 20X, by way of example and not limitation, user X. Based on the user's operation on the terminal 20 of X, a display process for displaying a specific display element in the messaging application is executed (timing "TM250").
Here, the specific display elements include, by way of example and not limitation, the following display elements.
・Profile screen of the user of the safety registration account ・One-on-one talk room between the safety registration account and the safety reference account ・Group talk room including the safety registration account ・Talk list screen including the safety registration account ・Official account profile screen of the safety confirmation service・Talk room between the official account of the safety confirmation service and the safety reference account ・Talk list screen including the official account of the safety confirmation service In addition, on the talk list screen, in order to prevent excessive safety information from being displayed, specific display is displayed. It may be excluded from the element.

Then, the control unit 21 of the terminal 20X transmits safety update request information for requesting safety information of a predetermined safety registration account to the server 10 via the communication I/F 22 (timing "TM260").

When receiving the safety update request information, the control unit 11 of the server 10 transmits the second safety information to the terminal 20X of the safety reference account (S2140) (timing "TM270").
Note that, if there is no difference between the first safety confirmation registration information and the second safety confirmation registration information as a result of the safety comparison process, the control unit 11 of the server 10 transmits the second safety information to the terminal 20X. You may choose not to do so. In this case, information indicating that there is no change in the safety status may be transmitted to the terminal 20X.
In addition, if there is a difference between the first safety confirmation registration information and the second safety confirmation registration information as a result of the safety comparison process, the control unit 11 of the server 10 determines that the safety status of the safety registration account has changed. Safety change information indicating that the situation has occurred may be transmitted to the terminal 20X.

When the terminal 20X receives the second safety information, it executes display processing (X2160) (timing "TM280").

Although this timing chart shows an example in which the safety confirmation registration information is input twice on the terminal 20Y of the safety registration account, the same process can be executed when the safety confirmation registration information is input three or more times. can.

In this modification, after the terminal 20 of the user of the safety reference account receives the first safety information (an example of the first information, not a limitation) through the communication I/F 22, the terminal 20 of the user of the safety reference account , an example of the user of the first terminal) and a user of the safety reference account (an example of the user of the terminal, not limited) is displayed on the display unit 24. In this case, a configuration is shown in which the second safety information (not a limitation, but an example of the second information) is received by the communication I/F 22.
As an example of the effect of the embodiment obtained by such a configuration, after the terminal receives the first information, the terminal displays the first chat room including the user of the first terminal and the user of the terminal. can acquire the second information. Moreover, by doing so, it is possible to avoid receiving the second information unnecessarily and to prevent the user of the terminal from feeling bothered.

In addition, the terminal 20 of the user of the safety reference account displays information on the user of the safety registration account, such as profile information of the user of the safety registration account (not limited to, but an example of information on the user of the first terminal), on the display unit 24. In this case, the second safety information may be received by the communication I/F 22.
As an example of the effect of the embodiment obtained by such a configuration, the terminal can acquire the second information when the terminal displays the information of the user of the first terminal. Moreover, by doing so, it is possible to avoid receiving the second information unnecessarily and to prevent the user of the terminal from feeling bothered.

In addition, in this case, the information of the user of the safety registration account may include information regarding the status of the user of the safety registration account, including information related to the safety of the user of the safety registration account (safety, danger, etc.). can.
As an example of the effects of the modified example obtained by such a configuration, when the terminal displays information regarding the status of the user of the first terminal, including first information related to the safety of the user of the first terminal, The terminal can be enabled to obtain the second information. Moreover, by doing so, it is possible to avoid receiving the second information unnecessarily and to prevent the user of the terminal from feeling bothered.

<Second modification (2)>
In the above embodiment, when the second safety confirmation registration information is registered on the terminal 20 of the safety registration account, the terminal 20 of the safety reference account automatically receives the second safety information. It is not limited to this.
As an example and not a limitation, the second safety information may be received based on the relationship between the safety reference account and the safety registration account.

As an example and not a limitation, the degree of intimacy between the safety reference account and the safety registration account is defined as follows.
Intimacy (safety reference account, safety registered account) = Average number of messages sent and received per day between the safety reference account and the safety registered account

In this case, as an example and not a limitation, if the degree of familiarity is greater than or equal to a set value (for example, not a limitation, "10") or greater than the set value, the control unit 11 of the server 10 transmits the second safety information to The information may be sent to the terminal 20 of the reference account.

Note that if the intimacy level is greater than or equal to the set value, the terminal 20 of the safety reference account sends safety update request information to the server 10 at set time intervals (for example, "5 minutes", not limited). do. When receiving the safety update request information, the control unit 11 of the server 10 may transmit the second safety information to the terminal 20 of the safety reference account.

This modification shows a configuration in which the second safety information (not a limitation, but an example of the second information) is transmitted based on the relationship between the user of the safety reference account and the user of the safety registration account.
As an example of the effect of the embodiment obtained by such a configuration, it is possible to enable the terminal to receive the second information appropriately transmitted based on the relationship between the user of the first terminal and the user of the terminal. can.

<Second modification (3)>
In the above-mentioned embodiment, an example is illustrated in which the safety registration account and the safety reference account are different, but the present invention is not limited to this. here,
・Safety registration account and safety reference account = User A of terminal 20A. A case where the account is A's account will be exemplified.

The left side of FIG. 2-7 shows user A. An example of the talk list screen of A's terminal 20A is shown. This talk list screen is similar to the display screen on the left side of FIG. 1-13, and is for user A. Based on the fact that A has set that he/she is "safe," information including a user status icon (user A.A, safe) indicating this is displayed in the second disaster information display area. . That is, in this example, user A. A's account functions as a safety registration account.

By way of example and not limitation, on the talk list screen on the left side of FIG. 2-7, user C. When the talk room list item C is tapped by the user, by way of example and not limitation, the talk room screen shown in the center of FIG. 2-7 is displayed. This screen differs from the talk room screen shown on the right side of FIG. 1-13 in that the talk room name display area includes user A. A is user C. Characters (in this example, "C.C") indicating that this is a talk room for talking with C as the other party are displayed.
In addition, in the user-specific safety information display area below that, as an example and not a limitation, a second danger icon DIC2 is superimposed on the user C. User A.C icon and second safety icon SIC2 are displayed superimposed. A icon is displayed.

The talk area includes, by way of example and not limitation, user C. The content from user A.C (for example, but not limited to, the text content of "It's an earthquake - the shaking is amazing" and the text content of "The elevator has stopped") and the content from user A.C. The content transmitted by A (text content such as "Are you okay with the earthquake? Are you with someone?" as an example and not limited to the text content) is displayed.

By way of example and not limitation, user C. When the safety information of user A.C is changed by user A.C. An example of the talk room screen displayed on A's terminal 20A is shown on the right side of FIG. 2-7.
In this example, user C. Based on the fact that C has changed the safety information from "danger" to "safe," by way of example and not limitation, a message is displayed at the top of the screen that sends the message from the messaging application (server 10) to user C.C. A push notification PN3 is displayed that includes text and an icon indicating that C has changed his safety information (CC's status has changed).

Also, in the talk area, by way of example and not limitation, a new user C. The content from C (not limited to, but as an example, text content of "The elevator stopped", text content of "I'm alone! I'm scared! Oh, the elevator moved!", text content of "I got out!") Displayed.

In addition, in this display screen example, user C. As an example, but not limited to, as a notification information that notifies the safety information changed by user Y.Y in the chat room, below the text content of C "I got it!", "C. The third notification information NI3 is displayed, which includes the characters "changed" and a user status icon ICCD (user C.C, dangerous) → user status icon ICCS (user C.C, safe).

Also, under this third notification information NI3, user A. Content sent by A (text content of "Good for you" as an example, but not limited to it) is displayed.

That is, in this example, user A. A's account also functions as a safety reference account.

<Third Example>
The third embodiment is an example in which connection control is performed based on registered safety status information, by way of example and not limitation, when a call is made between terminals 20 of two or more safety registration accounts.

Hereinafter, the user account of the caller, who is the person who makes the call to make a call, will be referred to as the "caller account," and the user account of the receiver, who is the person who receives the call, will be referred to as the "destination account."

The content described in the third embodiment is applicable to any of the other embodiments and other modifications.
In addition, the same reference numerals are given to the same constituent elements as those already mentioned, and the explanation thereof will be omitted.

<Display screen>
In the display screen in this embodiment, the originating account is user A of the terminal 20A. A. transfers the destination account to user B. of the terminal 20B. B and user C of terminal 20C. Let it be C. Further, the originating account and the destination account are exemplified as safety registration accounts that have completed safety registration.

The left side of FIG. 3-1 shows user A. The talk room screen of A's terminal 20A is displayed. This screen is similar to the display screen shown on the right side of FIG. 1-13, so a description thereof will be omitted.

By way of example and not limitation, user A. An example of a call screen displayed on A's terminal 20A is shown on the right side of FIG. 3-1.

The call screen includes, by way of example and not limitation, a call status display area below the area at the top of the screen where the name of the messaging application, etc. is displayed. The call status includes, by way of example and not limitation, user A. A is user B. "Calling" indicating that user A.B is calling. A is user B. A message such as "in a call" indicating that the call is being made with B is provided.

Below that, there is an icon image of the messaging application of the user on the other end of the call, the user name, the duration of the call, and a microphone off button to turn off the microphone (in this example, a microphone-shaped image and the words "Mic Off") , a video call button to make a video call with that user (in this example, a video camera-shaped image and the text "Start a video call"), and a speaker on button to turn on the speaker (in this example). , a speaker-shaped image, the text "Speaker on"), and an end call button for ending the call are displayed.

In this example, the text "In call" is displayed in the call status display area, and below that, user B. B icon image, the letters "B.B", the number "1:47" as the call time, a microphone off button, a video call button, a speaker on button, and a call end button are displayed.

The left side of FIG. 3-2 shows user A. The talk room screen of A's terminal 20A is displayed. This screen is similar to the talk room screen shown on the right side of Figure 2-7, but the talk room name display area includes, by way of example and not limitation, a back button of "<" to return to the previous screen, and a user A. A is user C. Characters indicating that this is a talk room for talking with person C (in this example, "C.C"), a call button, etc. are displayed.

By way of example and not limitation, when the user taps the call button BT7 on the right side of the talk room name display area on the talk room screen on the left side of FIG. 3-2, a display as shown in the center of FIG. 3-2 is displayed.

In this talk room screen, user A. A and user B. Based on the fact that B's safety status is "safe," the call refrain request information CRI1 is displayed superimposed on the talk room screen on the left side of Figure 3-2 to refrain from making unnecessary and non-urgent calls in the event of a disaster. ing.
In this example, the call refraining request information CRI1 contains a message that urges (alerts) people to refrain from making unnecessary and non-urgent calls in the event of a disaster (in this example, the message "Unnecessary calls due to the occurrence of a large-scale disaster" is included). Please refrain from making non-urgent calls", a character image), a cancel button to cancel the call (in this example, a button that includes the words "cancel"), and a button to cancel the call. 2. A call button (in this example, a button that includes the words "Call by all means") is displayed.

By way of example and not limitation, user A. An example of a call screen displayed on A's terminal 20A is shown on the right side of FIG. 3-2.

In this example, the text "In call" is displayed in the call status display area, and below that, user C. The icon image of C, the letters "C.C", the number "0:12" as the call time, a microphone off button, a video call button, a speaker on button, and a call end button are displayed.

<Processing>
FIG. 3-3 is a flowchart showing an example of the flow of processing executed by each device in this embodiment.
In this figure, examples of processing executed by the control unit 21 of the terminal 20X of the originating account, processing executed by the control unit 21 of the terminal 20Y of the destination account, and processing executed by the control unit 11 of the server 10 are shown in order from the left. It shows.

By way of example and not limitation, when the control unit 21 of the terminal 20X executes the safety confirmation process (X210), the control unit 21 of the terminal 20X performs the following operations based on the input (user operation, etc.) to the input/output unit 23 of the terminal 20X. For example, call request information including the application ID of the destination account is transmitted to the server 10 via the communication I/F 22 (X310).

When determining that the communication I/F 14 has received the call request information from the terminal 20X of the originating account, the control unit 11 of the server 10 executes a safety status determination process (S310).

In the safety status determination process, the control unit 11 of the server 10 refers to the account management database 155A, and compares the safety status information (hereinafter referred to as "source status") in the safety registration data of the source account and the destination account. The safety status information in the safety registration data (hereinafter referred to as the "destination status") is acquired.
Then, the control unit 11 of the server 10 determines, by way of example and not limitation, whether the source status is "safe" and the destination status is "safe."

If it is determined that the caller status is "safe" and the call destination status is "safe" (S310: "safety" - "safety"), the control unit 11 of the server 10 requests that the caller refrain from making a call. The communication I/F 14 transmits call refrain request information to the terminal 20X of the originating account (S320).

If it is determined that the source status is "safe" and the destination status is other than "safe" (S310: "safe" - other than "safe"), the control unit 11 of the server 10 causes the step of S320 to be skipped. .

If the communication I/F 22 determines that the call refraining request information has been received from the server 10 (X320: YES), the control unit 21 of the terminal 20X displays the received call refraining request information on the display unit 24 (X330). .
If it is determined that the call refraining request information is not received (X320: NO), the control unit 21 of the terminal 20X skips step X330.

After that, the control unit 11 of the server 10 starts call processing (S340). Furthermore, the control units 21 of the terminals 20X and 20Y start call processing (X340, Y340).
In the call processing, the control unit 21 of the terminal 20Y causes the sound output unit 26 to output a ringtone indicating that a call has arrived, by way of example and not limitation. As a result, user X. Have X hear a ringtone to notify him that a call is requested. Further, the control unit 21 of the terminal 20Y causes the display unit 24 to display an incoming call display including information on the originating account (by way of example and not limitation, user name).
Note that information including the sender status may be displayed on the display unit 24 of the terminal 20 of the sender account as the sender account information.

By way of example and not limitation, when a call is accepted based on input to input/output unit 23 of terminal 20Y, control unit 21 of terminal 20X and control unit 21 of terminal 20Y may communicate with server 10, by way of example and not limitation. VoIP processing for calls between users is performed via the . Note that when the call is accepted, the control unit 21 of the terminal 20X and the control unit 21 of the terminal 20Y may perform peer-to-peer communication and perform VoIP processing on the call.

By way of example and not limitation, when the call ends and is disconnected based on the input to the input/output unit 23 of the terminal 20X or 20Y, the control unit 11 of the server 10 ends the process. Further, the control unit 21 of the terminal 20X and the terminal 20Y ends the process.

Note that the call refraining request information may include a display for selecting whether to cancel the call. In this case, the call refraining request information is displayed on the terminal 20X of the originating account, and as an example and not a limitation, if the user chooses to cancel the call based on the input to the call refraining request information, the terminal 20X of the originating account The control unit 21 of the 20X transmits call cancellation information indicating that the call is to be canceled to the server 10 via the communication I/F 22. If the communication I/F 14 determines that the call cancellation information has been received from the terminal 20X of the originating account, the control unit 11 of the server 10 may not start the call processing between the terminal 20X and the terminal 20Y. . If it is selected to continue making a call based on the input operation for the call refraining request information, the control unit 11 of the server 10 may start call processing between the terminal 20X and the terminal 20Y.

Further, in the safety status determination process, if the control unit 11 of the server 10 determines that the source status is "safe" and the destination status is "safe" (S310: "safe" - "safe"), Call connection rejection information indicating that the call will not be connected may be sent to the terminal 20X of the originating account via the communication I/F 14. When the control unit 21 of the terminal 20X receives the call connection rejection information, the control unit 21 of the terminal 20X may cause the display unit 24 to display the call connection rejection information. Then, the control unit 11 of the server 10 may not start call processing.
That is, in the safety status determination process, if it is determined that the calling source status is "safe" and the calling destination status is "safe", the call is forcibly canceled.

<Effects of the third embodiment>
This embodiment has a configuration in which the terminal 20 of the user of the originating account uses the control unit 21 to perform processing related to the call based on information regarding the safety of the user of the originating account and information regarding the safety of the user of the destination account. It shows.
As an example of the effect of the embodiment obtained by such a configuration, processing related to the call can be appropriately performed based on information regarding the safety of the user related to the call.

In addition, in this case, the process related to calls is to suppress (prohibit) calls when the information regarding the safety of the user of the originating account and the information regarding the safety of the user of the destination account are both "safe". Processing may be included.
As an example of the effect of the embodiment obtained by such a configuration, if the information regarding the safety of the user of the originating account and the information regarding the safety of the user of the destination account satisfy set conditions, calls may be suppressed ( prohibited).

<Third modification (1)>
In the above embodiment, it was determined whether or not to suppress calls based on the safety status determination process, but the present invention is not limited thereto. As an example and not as a limitation, if the caller status is determined to be "dangerous" in the safety status determination, the control unit 11 of the server 10 increases the connection priority of the call and processes the call. Good too.

If the caller status is "at risk," the call originating by the user of the caller account is considered to be highly urgent. Therefore, when the caller status is determined to be "dangerous", by increasing the connection priority of the call, it is possible to make it easier to connect a call that is likely to be urgent.

Note that when the caller status is "dangerous", in the call processing, by way of example and not limitation, the call ringtone on the terminal 20Y of the callee account may be output as a ringtone in a more conspicuous manner. Further, when the caller status is "dangerous", in call processing, by way of example and not limitation, the call display on the terminal 20Y of the call destination account may be displayed as a more conspicuous incoming call display.
This allows the user of the originating account to more easily distinguish incoming calls from the originating account that is likely to be taking actions such as asking for help.

Note that in the safety status determination, if the destination status is determined to be "dangerous", the connection priority of the call may be increased.

<Third modification (2)>
In the above embodiment, the safety status determination process is executed in the server 10, but the present invention is not limited thereto. By way of example and not limitation, the safety status determination process may be executed at the terminal 20X of the originating account.

By way of example, but not limitation, when the control unit 21 of the terminal 20X of the originating account executes the safety confirmation process, the control unit 21 of the terminal 20X of the originating account may make a call based on the input (user operation, etc.) to the input/output unit 23 of the terminal 20X. Accept the destination account. Then, the control unit 21 of the terminal 20X transmits, by way of example and not limitation, safety information request information including the application ID of the originating account and the application ID of the originating account to the server 10 via the communication I/F 22.
When receiving the safety information request information from the terminal 20X through the communication I/F 14, the control unit 11 of the server 10 refers to the account management database 155A and acquires the sender status and the sender status. Then, safety information including the sender status and the sender status is transmitted to the terminal 20X via the communication I/F 14.

Upon receiving the safety information from the server 10 through the communication I/F 22, the control unit 21 of the terminal 20X executes a safety status determination process based on the received safety information. If it is determined that the caller status is "safe" and the call destination status is "safe," the control unit 21 of the terminal 20X causes the display unit 24 to display call refrain request information.

Note that if the terminal 20X has acquired the destination status as safety information prior to starting the call, the control unit 21 of the terminal 20X does not transmit the safety information request information to the server 10, and the outgoing call stored in the storage unit 28 The safety status determination process may be executed based on the source status and the destination status.

<Fourth Example>
The fourth embodiment is an example in which, when safety confirmation registration information is registered on the terminal 20 of the safety registration account, a response is automatically made to a message sent to the safety registration account thereafter.

The content described in the fourth embodiment is applicable to any of the other embodiments and other modifications.
In addition, the same reference numerals are given to the same constituent elements as those already mentioned, and the explanation thereof will be omitted.

<Display screen>
The left side of FIG. 4-1 shows user A. The home screen of A's terminal 20A is displayed. This screen differs from the home screen in the center of FIG. 1-12 in that a safety message input by the user (in this example, "I am traveling by bicycle") is displayed in the safety message input area. Furthermore, in the current location input area below that, the current location ("Mitaka City" in this example) input by the user is displayed.

As an example and not a limitation, in the safety registration area R1 on the left side of FIG. 4-1, the registration button BT3 is pressed by the user A. When tapped by A, the display changes to the safety registration area R1 in the center of FIG. 4-1.

In this case, in the safety registration area R1, displays such as the safety button SBT, danger button DBT, safety message input area, current location input area, etc. are erased, and a safety information confirmation area for confirming the set safety information is configured. There is. The safety information confirmation area includes, by way of example and not limitation, the text "Registered with the following content", the text "Safety message", the user status icon ICAS (user A.A, safe), and "Mitaka/bicycle". "Moving" is displayed.

Further, below that, an automatic response setting area for setting the automatic response mode is configured. The automatic response setting area includes, as an example and not a limitation, the words "Do you want to switch to automatic response mode?" and the "Yes" button BT11 to set the automatic response mode (switch the mode to automatic response mode). , a "No" button BT12 for not setting the automatic response mode (in this example, a button indicated by the characters "No") are displayed.

As an example and not a limitation, in the safety registration area R1 in the center of FIG. 4-1, the "Yes" button BT11 is pressed by the user A. Suppose that it is tapped by A. In this case, a screen like the one shown on the right side of Figure 4-1 will be displayed.

The right side of FIG. 4-1 shows user A. An example of a talk list screen displayed on the display unit 24 of A's terminal 20A is shown. This screen differs from the talk list screen on the left side of Figure 1-13. When automatic response mode is set, this screen displays messages sent from other users after automatic response mode is set to the chat room list item. Auto-reply information is displayed indicating that the chat room has been answered (replyed via auto-reply).

In this example, when automatic response mode is set, a message will be sent at the earliest time among the chat room list items of the chat room in which another user sent a message after automatic response mode was set. from the talk room list item corresponding to the talk room where the message was sent (user B.B's talk room) to the talk room list item corresponding to the talk room where the message was sent most recently (tennis circle group talk room). , automatic response completed information (in this example, a telop showing the characters "Automatic response completed") is displayed in a superimposed manner.

The left side of FIG. 4-2 shows user D. The talk room screen of D's terminal 20D is displayed. This screen differs from the talk room screen shown on the right side of FIG. 1-13 in that the talk room name display area includes user D. D is user A. Characters (in this example, "A.A") indicating that this is a talk room for talking with A as the other party are displayed.
In addition, in the user-specific safety information display area below the user A. User D.A's icon and the second safety icon SIC2 are displayed superimposed. A D icon is displayed.

The talk area includes, by way of example and not limitation, user A. Content from user A (by way of example, but not limitation, text content of "Okay, good night~") and user D. The content sent by D (as an example, but not limited to, the text content ``See you tomorrow~'', the text content ``Is the earthquake shaking?'', the text content ``Are you okay? Have you left home yet?'') are displayed. There is.

In addition, below that, there is automatic response confirmation information ARI (as an example, but not limited to, that is sent from the OA account (in this example, the safety confirmation response service). 20XX/08/04 9: It has been confirmed that Mr. A.A. is safe in the disaster that occurred on March 39th.Information that includes the words ``Currently set to automatic response to save battery power, etc.'' is displayed.

Here, "read" can be defined as a term relative to "unread".
As a condition for a message (content) to be read (hereinafter referred to as a "read condition"), any of the following conditions may be applied, by way of example and not limitation.
(A) A message was displayed.
(B) A certain amount of time (not limited to a few seconds to 10 seconds) has passed since the message was displayed.
(C) After the message is displayed, the displayed message is tapped (clicked).
(D) A reply was made to the message after it was displayed.
(E) If the message is a video message, the video has been played.
(F) If the message is a video message, a certain amount of time (not limited to a few seconds to 10 seconds) has passed since the video was played.

In this case, the "unread" state can be defined, by way of example and not limitation, as a state in which the above-mentioned read condition is not satisfied.
The "unread" state is a type of state where the user has not yet viewed the message (content).

In this example, user D. Among the contents sent by D, based on the fact that the text content "See you tomorrow~" has already been read, as an example and not a limitation, the text "already read" is displayed at the lower left of the speech bubble of this text content. is displayed, and based on the fact that the text content "I'm shaking ~ Earthquake?" and the text content "Are you okay? Have you left home yet?" are in an unread state, a message is displayed at the bottom left of the speech bubble for these text content. The word "read" is not displayed.

By way of example and not limitation, user A. When user A. is set to automatic response mode by A. An example of the talk room screen displayed on A's terminal 20A is shown on the right side of FIG. 4-2.

This screen differs from the talk room screen shown on the left side of FIG. 4-2, in that the talk room name display area includes user A. A is user D. Characters (in this example, "D.D") indicating that this is a talk room for talking with D as the other party are displayed.

The talk area includes, by way of example and not limitation, user A. The content sent by A (as an example, not limited to, the text content "Well then, good night~", the text content "Sorry for the late reply, B. I was helping Mr. B because he seemed to have injured his leg;") , user D. The content from D (as an example and not a limitation, the text content ``See you tomorrow~'', the text content ``I'm shaking~earthquake?'', the text content ``Are you okay? Have you left home yet?'') are displayed.

Also, user D. Among the content from D, as an example and not a limitation, after the text content "It's shaking ~ Earthquake?" is sent, but before the text content "Are you okay? Have you left home yet?" At the timing of , user A. Based on the automatic response mode being set by A, automatic response setting information ARSI including the characters "Automatic response mode has been set" is displayed between these text contents.

Also, user D. Among the contents from D, as an example and not a limitation, the timing after the text content "Are you okay? Have you left home yet?" is sent to user A. As an example, but not a limitation, of the content from A, the user may receive the following text before the text content is sent: ``Sorry for the late reply. Mr. B seems to have hurt his leg, so I was helping him;'' A. Based on the fact that the automatic response mode has been canceled by A, automatic response cancellation information ARRI with the words "Automatic response mode canceled" is displayed between these text contents.

<Processing>
The processing executed by each device in this embodiment can be executed according to FIGS. 2-2 to 2-3, by way of example and not limitation.

FIG. 4-3 is a timing chart showing an example of the timing of processing executed by each device in this embodiment.
here,
・Safety registration account for automatic response = User X. of terminal 20X. Account of user Y of terminal 20Y (an example of a terminal user, not limited to this) - Account that sends a message to the safety registration account that automatically responded = user Y of terminal 20Y. The processing for the case where the account is Y (not limited, but an example of the user of the first terminal) will be illustrated.

As an example and not a limitation, when the safety confirmation process is executed and an input operation for safety confirmation registration information is accepted at the terminal 20Y (Y2130), the first safety confirmation registration information is transmitted to the server 10 (Y2140) (timing "TM310"). Then, the server 10 receives the first safety confirmation registration information (S2130: YES).
The control unit 11 of the server 10 generates first safety information based on the first safety confirmation registration information and transmits it to each terminal 20 (S2140) (timing "TM315").
Upon receiving the first safety information, the terminal 20X executes display processing (X2160) (timing "TM320").

When the input operation for safety confirmation registration information is accepted at the terminal 20X (X2130), the second safety confirmation registration information is transmitted to the server 10 (X2140) (timing "TM325"). Then, the server 10 receives the second safety confirmation registration information (S2130: YES).
The control unit 11 of the server 10 generates second safety information based on the second safety confirmation registration information and transmits it to each terminal 20 (S2140) (timing "TM330").
Upon receiving the second safety information, the terminal 20Y executes display processing (Y2160) (timing "TM335").

The control unit 21 of the terminal 20X causes the display unit 24 to display a display for determining whether or not to start automatic response (timing "TM340").
As an example and not a limitation, if starting an automatic response is selected based on an input operation on the determination display displayed on the terminal 20X, the control unit 21 of the terminal 20X requests to start an automatic response. The communication I/F 22 transmits automatic response start request information to the server 10 (timing "TM345").

When the communication I/F 14 determines that automatic response start request information has been received from the terminal 20X, the control unit 11 of the server 10 starts message automatic response processing for the terminal 20 that has transmitted the automatic response start request information (timing "TM350").

In the chat process, by way of example and not limitation, user X. When a message for X is input, the control unit 21 of the terminal 20Y inputs, by way of example and not limitation, the input message, the application ID of the terminal 20Y that is the message source, and the application of the terminal 20X that is the message destination. Message transmission request information including the ID is transmitted to the server 10 via the communication I/F 22 (timing "TM355").

Upon receiving the message transmission request information from the terminal 20Y through the communication I/F 14, the control unit 11 of the server 10 determines whether automatic response processing for the message destination account is being executed based on the message transmission request information. do. In this example, the automatic message response process for the terminal 20X is executed between timings "TM350" and "TM375".
Therefore, if it is determined that the timing at which the message transmission request information was received is after the timing "TM350" and before the timing "TM375", the control unit 11 of the server 10 receives the automatic message response information. is transmitted to the terminal 20Y via the communication I/F 14 (timing "TM360").

When the message automatic response information is received from the server 10 through the communication I/F 22, the control section 21 of the terminal 20Y displays the received message automatic response information on the display section 24 (timing "TM365").

As an example and not a limitation, if it is selected to end the automatic response based on an input operation on the terminal 20X, the control unit 21 of the terminal 20X issues an automatic response termination request to request that the automatic response be terminated. The information is transmitted to the server 10 via the communication I/F 22 (timing "TM370").

When the communication I/F 14 receives the automatic response termination request information from the terminal 20X, the control unit 11 of the server 10 terminates the automatic message response process for the terminal 20X (timing "TM375").
Then, the control unit 11 of the server 10 stores message automatic response response history information including messages sent to the terminal 20X within the message automatic response processing period (in this case, between timings "TM350" and "TM375"). It is transmitted to the terminal 20X via the communication I/F 14 (timing "TM380").

When the message automatic response history information is received from the server 10 through the communication I/F 22, the control unit 21 of the terminal 20X displays the received message automatic response history information on the display unit 24 (timing "TM385").

Note that although this timing chart shows an example in which the server 10 receives message transmission request information for the terminal 20X once within the message automatic response processing period, the same applies to the case where the server 10 receives message transmission request information two or more times. processing can be executed. The same applies when the server 10 receives message transmission request information from a plurality of terminals 20 to the terminal 20X within the message automatic response processing period.

Note that when the control unit 11 of the server 10 receives message transmission request information again from the terminal 20Y within the message automatic response processing period (in this case, between timings "TM350" and "TM375"), the control unit 11 of the server 10 transmits the message automatic response information. The information may not be transmitted to the terminal 20Y.

In addition, when receiving message transmission request information for a group talk room that includes the account of the terminal 20X within the message automatic response processing period, the control unit 11 of the server 10 transmits the message automatic response information to each terminal 20 You may choose not to send it to

Furthermore, in the terminal 20X, a display for determining whether or not to start an automatic response is displayed on the display unit 24 prior to the timing "TM320" or the timing "TM325", and automatic response start request information is transmitted to the server 10. You can do it like this.

<Effects of the fourth embodiment>
In this embodiment, the terminal 20 collects safety information (or safety confirmation registration information) (not limited to the terminal An example of third information regarding the safety of the user) is transmitted by the communication I/F 22.
As an example of the effect of the embodiment obtained by such a configuration, third information regarding the safety of the terminal user is transmitted based on the input to the terminal by the terminal user to inform others of the terminal user's safety. be able to.

In addition, in this case, the terminal 20 transmits information (not limited to chat, but not limited to) for determining whether to start an automatic response to chat (not limited to chat) based on the above-mentioned transmission of the safety information. An example of information regarding automatic responses) is displayed on the display unit 24. Then, the terminal 20 performs a process of transmitting automatic response start request information for requesting the start of an automatic response based on the input by the user of its own terminal 20 with respect to this determination information. The control unit 21 can perform processing related to an automatic response to a talk (chat), such as processing to display information regarding the start of a chat.
As an example of the effect of the embodiment obtained by such a configuration, information regarding automatic chat response is displayed on the display section based on the transmission of the third information described above, and the terminal indicates that automatic chat response is possible. users can be notified. Furthermore, processing related to automatic chat response can be appropriately performed based on the input by the user of the terminal to the displayed information regarding automatic response.

<Fourth modification (1)>
In the above-mentioned embodiment, an example was exemplified in which automatic response start request information is transmitted based on an input operation to the terminal 20X that starts an automatic response, but the present invention is not limited to this.
As an example and not a limitation, if the remaining battery level of the terminal 20X is less than or equal to a set value (for example and not as a limitation, "20%"), the control unit 21 of the terminal 20X automatically sends automatic response start request information to the server 10. It may also be possible to send it explicitly.

Also, by way of example and not limitation, the control unit 21 of the terminal 20X may automatically transmit automatic response start request information to the server 10 upon receiving disaster information from the server 10.

Further, by way of example and not limitation, upon receiving disaster information from the server 10, the control unit 21 of the terminal 20X acquires the current position via the position calculation information detection unit 29B, by way of example and not limitation. Then, the control unit 21 of the terminal 20X automatically responds to the server 10 when it is determined that the current location is close to the disaster occurrence location included in the disaster information (as an example and not a limitation, within 10 km from the observation point of the maximum seismic intensity). The start request information may be automatically transmitted.

Furthermore, if the communication state of the terminal 20X is poor (for example, but not limited to, if the radio field strength is below a set value), the control unit 21 of the terminal 20X automatically sends automatic response start request information to the server 10. You may also send it.

In addition, the usage state (situation) of the application executed on the terminal 20X (as an example, not limited to, being used in the background), and the state (situation) of position calculation by the position calculation information detection unit 29B (not limited to For example, the terminal 20X The control unit 21 may automatically transmit automatic response start request information to the server 10.

In this modification, the terminal 20 determines whether to start automatic response to talk (an example of chat, not limited to) based on the state of the terminal 20, such as the remaining battery level of the terminal 20. information (not limited, but an example of information regarding automatic chat responses) is displayed on the display unit 24. Then, the terminal 20 performs a process of transmitting automatic response start request information for requesting the start of an automatic response based on the input by the user of its own terminal 20 with respect to this determination information. A configuration is shown in which the control unit 21 performs processing related to automatic response to talk (chat), such as processing to display information regarding the start of chat.
As an example of the effect of the embodiment obtained by such a configuration, information regarding automatic chat response is displayed on the display unit based on the status of the terminal to notify the terminal user that automatic chat response is possible. be able to. Furthermore, processing related to automatic chat response can be appropriately performed based on the input by the user of the terminal to the displayed information regarding automatic response.

<Fourth modification (2)>
In the above embodiment, the automatic response is ended based on the input to the terminal 20X that starts the automatic response, but the present invention is not limited to this.
As an example and not a limitation, if the control unit 11 of the server 10 receives message transmission request information for the terminal 20X N times ("N" is a predetermined natural number) within the automatic message response processing period, the control unit 11 of the server 10 ends the automatic message response processing. The automatic message response response history information may be transmitted to the terminal 20X.

As an example and not a limitation, if the control unit 11 of the server 10 receives message transmission request information for the terminal 20X N times ("N" is a predetermined natural number) within the message automatic response processing period, the control unit 11 of the server 10 sends a message to the terminal 20X. Automatic response termination suggestion information for suggesting termination of the automatic response process may be transmitted.
In this case, upon receiving the automatic response termination suggestion information, the control unit 21 of the terminal 20X causes the display unit 24 to display the received automatic response termination suggestion information. As an example and not a limitation, if it is selected to terminate the automatic response based on the input operation for the displayed automatic response termination suggestion information, the control unit 21 of the terminal 20X transmits the automatic response termination request information to the server. 10 may be transmitted.

The left side of FIG. 4-4 shows user A. An example of a talk list screen displayed on the display unit 24A of the terminal 20A of A is shown.
This screen differs from the talk list screen on the right side of FIG. 4-1, and by way of example and not limitation, user F. F's talk room list item is displayed. Also, user F. The unread number "4" is displayed in association with the talk room list item F. Also, user F. Based on the fact that user F has set "safety" as the safety information, user F. A second safety icon SIC2 is displayed superimposed on the icon corresponding to the talk room list item F.

In this example, based on the auto-reply mode setting, the message is displayed in the oldest time among the chat room list items of the chat room where another user sent a message after the auto-reply mode was set. From the talk room list item corresponding to the message sent (user B.B's talk room) to the talk room list item corresponding to the talk room where the message was sent most recently (user F.F's talk room) , automatic response completion information (in this example, a telop displaying the words "Automatic response completion") is displayed in a superimposed manner.

In this example, user A. Based on the fact that A has received a set number of messages (10) since setting the auto-response mode, by way of example and not limitation, a message is displayed at the top of the screen indicating that user A has sent messages from the messaging application (server 10). ．． Text indicating that A has received the set number of messages (10 as an example, not a limitation) since A set auto-response mode (10 messages have been received during auto-response. Do you want to continue auto-replying?) A push notification PN5 including the following is displayed.

By way of example and not limitation, in the display screen on the left side of FIG. 4-4, push notification PN5 is sent to user A. When tapped by A, by way of example and not limitation, a display like the one on the right side of FIG. 4-4 is displayed.

This display screen is configured so that the safety registration area R1 is displayed raised, superimposed on the talk list screen on the left side of FIG. 4-4.
In this case, the safety registration area R1 constitutes a safety information confirmation area for confirming the set safety information. In the safety information confirmation area, for example, but not limited to, the text "Registered with the following content", the text "Safety message", the user status icon ICAS (user A.A, safety), and "Mitaka/Bicycle" are displayed. "Currently moving" is displayed.
Further, below that, an automatic response cancellation area for canceling the automatic response mode is configured. In the automatic response cancellation area, as an example and not a limitation, the text "Do you want to cancel automatic response mode?" and the "Yes" button BT13 for canceling automatic response mode (in this example, "Yes" button BT13) are displayed. A "No" button BT14 (in this example, a button indicated by "No" characters) for not canceling the automatic response mode is displayed.

<Fourth modification (3)>
In the above embodiment, the automatic message response process is executed in the server 10, but the present invention is not limited thereto. By way of example and not limitation, the message automatic response process may be executed at the terminal 20X selected to start the automatic response.

FIG. 4-5 is a timing chart showing an example of the timing of processing executed by each device in this modification.
As an example and not a limitation, if starting an automatic response is selected based on an input operation on the determination display displayed on the terminal 20X, the control unit 21 of the terminal 20X starts an automatic message response process ( Timing "TM410").

Upon receiving the message transmission request information from the terminal 20Y through the communication I/F 14, the control unit 11 of the server 10 transmits the message information to the terminal 20X based on the message transmission request information (timing "TM420").

When message information is received from the server 10 through the communication I/F 22, the control unit 21 of the terminal 20X determines whether automatic response processing is being executed. In this example, the automatic message response process at the terminal 20X is executed between timings "TM410" and "TM440".
Therefore, if it is determined that the timing at which the message information was received is after the timing "TM410" and before the timing "TM440", the control unit 21 of the terminal 20X transmits the message automatic response information. It is transmitted to the terminal 20Y via the I/F 22 (timing "TM430"). Note that the control unit 21 of the terminal 20X may transmit the message automatic response information to the terminal 20Y via the server 10.
Further, the control unit 21 of the terminal 20X does not display the received message information on the display unit 24.

By way of example and not limitation, if it is selected to end the automatic response based on an input operation on the terminal 20X, the control unit 21 of the terminal 20X ends the automatic response process. Then, message automatic response response history information is generated based on the message information received during the message automatic response processing period (timing "TM440").

The control unit 21 of the terminal 20X causes the display unit 24 to display the generated automatic message response history information (timing "TM450").

<Fifth example>
As an example and not a limitation, in the case of a disaster such as a large-scale disaster, the fifth embodiment uses one terminal 20 (hereinafter referred to as a "terminal") to register safety confirmation (as an example and not a limitation). An embodiment in which, when a user of another terminal 20 (hereinafter referred to as the "first terminal") requests the input and transmission of confirmation information, a request for safety confirmation registration to the terminal is made based on setting conditions. It is.

Hereinafter, as mentioned above, a business that provides a safety confirmation service using a safety confirmation application will be referred to as a "safety confirmation service provider."
Note that the safety confirmation service provider can also be expressed as a provider of a safety confirmation application or a provider of the server 10.
In addition, it can also be expressed as a safety confirmation service provider in the sense of a company that provides a safety confirmation service.

Further, in the following, the name of the safety confirmation application will be appropriately referred to as "Safety Confirmation App" and will be illustrated and explained.

By way of example and not limitation, the safety confirmation application can be configured such that accounts registered in the server 10 as targets for safety confirmation can request safety confirmation registration. Further, by way of example and not limitation, when one account registered in the server 10 as a safety confirmation target registers for safety confirmation, other accounts can refer to the registered safety confirmation information.

Hereinafter, a user account for which safety confirmation registration is requested will be referred to as a "safety registration requesting account," and a user account that requests safety confirmation registration to the safety registration requesting account will be referred to as a "safety registration requesting account." In general, one user account can serve as both a safety registration request account and a safety registration request account.

Note that the method of safety confirmation registration is not limited to the method of inputting and registering safety confirmation information using the safety confirmation application or the above-mentioned messaging application. As an example and not a limitation, a method of transmitting safety confirmation information by means such as telephone or fax without using a safety confirmation application or a messaging application, or a method of transmitting safety confirmation information as a message in a messaging application may be used. Good too.

The contents described in the fifth embodiment can be applied to any of the other embodiments and other modifications.
In addition, the same reference numerals are given to the same constituent elements as those already mentioned, and the explanation thereof will be omitted.

<Display screen>
The left side of FIG. 5A is the main menu screen of the safety confirmation application, and the words "Safety Confirmation App" are displayed at the top center of the screen as the name of the safety confirmation application. Further, on the right side at the top of the screen, an icon image and a user name ("user Y.Y" in this example) in the messaging application of the user of this terminal 20Y are displayed.

Further, below that, an in-app position display area in the safety confirmation application is configured, and in this example, based on the main menu screen, the words "main menu" are displayed.

Below the in-app location display area is a disaster information display area, which is an area that displays disaster information to notify that a disaster has occurred.In this example, based on the occurrence of an earthquake, Disaster information is displayed. Also, at the bottom right inside the disaster information display area, user Y. Based on the fact that Y has set "safety" as the safety information, the words "my status" and a user status icon (user A.A, safe) are displayed.

Below the disaster information display area, user Y. A member list display area is configured in which a list of users (hereinafter illustrated and described as "members") associated with Y is displayed.

As an example and not as a limitation, if a certain organization uses a safety confirmation application (safety confirmation service), a user such as a representative of the organization may register members on the server 10. It can be done. By doing this, people belonging to the organization can be associated as members in the safety confirmation application.

Note that it is also possible to set members by individuals rather than by organizations.
In this case, in the same way as registering friends in the messaging application described above, by way of example and not limitation, the user of the individual terminal 20 registers the member using a phone number, application ID, etc. be able to.

In this example, the member list display area is configured to display a member list for displaying a list of members associated with the account of this terminal 20Y (in this example, "user Y.Y"). .

The member list is user Y. When tapped by Y, those lists are expanded and displayed. Specifically, by way of example and not limitation, member icons and user names are displayed in a list as items in the member list. In this example, by way of example and not limitation, the member list is tapped and displayed in an expanded state.

On this screen, user X. Icon and user name corresponding to X, user C. The icon and user name corresponding to C, the user D. A list of icons, user names, etc. corresponding to D is displayed.
Also, user X. Based on the fact that user X has not set safety information, user A second unknown icon UIC2 (in this example, an icon on which the characters "unknown" are shown) is displayed superimposed on the icon corresponding to X. User C. Based on the fact that user C has set the safety information to "safe", user C. A second safety icon SIC2 is displayed superimposed on the icon corresponding to C. User D. Based on the fact that user D has set the safety information to "danger", user D. A second danger icon DIC2 is displayed superimposed on the icon corresponding to D.

By way of example and not limitation, on the main menu screen on the left side of FIG. When the user taps the member list item corresponding to X, the display changes to the member screen on the right side of FIG. 5-1, by way of example and not limitation.

By way of example and not limitation, the member screen can be a screen that displays information regarding the safety status of the selected user. The member screen includes, by way of example and not limitation, an icon image in the safety confirmation application of each member, a user name, information regarding safety (in this example, the characters "safety status", a second unknown icon UIC2), A safety registration request button BT2a or the like may be displayed to prompt the user to register safety information.

By way of example and not limitation, in the member screen on the right side of Figure 5-1, user X. The safety registration request button BT2a for user X is pressed by user Y. When tapped by Y, the safety registration request confirmation information SRI1 shown on the left side of FIG. 5-2 is superimposed and displayed on the member screen, by way of example and not limitation.

Safety registration request confirmation information SRI1 includes, by way of example and not limitation, an image related to the icon image of the safety confirmation application, the text "A request for safety registration has been made to X.X", and a request for safety registration. This includes an OK button indicated by an icon including the word "OK" for confirming that the request has been made and for terminating the display of the safety registration request confirmation information SRI1.

The OK button is tapped and user Y. User X by Y. Assume that a safety registration request is made for X as the other party.
In this case, user X. By way of example and not limitation, a screen as shown on the right side of FIG. 5-2 is displayed on the terminal 20X of X.

On the right side of Figure 5-2, there is a safety registration request confirmation area R2 that is superimposed on the main menu screen displayed on the display section 24X of the terminal 20X to notify that a request has been made to set safety information. It is displayed upward.

This main menu screen differs from the main menu screen shown on the left side of FIG. 5-1, in that the icon image and user name (in this example " "User X.X") is displayed.

Also, in the lower right corner of the disaster information display area, user X. Based on the fact that X has not set safety information, the words "Register your status" and a safety registration button BT2 similar to the safety registration button BT1 described above are displayed.

Also, user Y. A list of icons, user names, etc. corresponding to Y is displayed.
Also, user Y. Based on the fact that user Y has set the safety information to "safe", user Y. A second safety icon SIC2 is displayed superimposed on the icon corresponding to Y.

In the safety registration request confirmation area R2, user X. User Y for X. A message indicating that Y. is prompting you to set your safety information (in this example, the text "Safety Registration Request", the text "Y.Y has requested you to register your safety status", and the user Y.Y. icon→User X.X icon) is displayed. Below that, an answer button BT4a for setting safety information is displayed.

The left side of FIG. 5-3 shows user Y. On the display section 24Y of the terminal 20Y of the user Y.Y. User X by Y. Based on the second safety registration request made with X as the other party, a safety registration request confirmation area is displayed on the member screen of the safety confirmation application. This display screen is similar to the display screen on the left side of FIG. 5-2, so a description thereof will be omitted.

By way of example and not limitation, user Y. User X by Y. Assume that a second safety registration request (which may be considered as a safety registration reminder) is made with X as the other party.
In this case, user X. By way of example and not limitation, a screen as shown on the right side of FIG. 5-3 is displayed on the terminal 20X of X.

On the right side of FIG. 5-3, a main menu screen is displayed on the display section 24X of the terminal 20X. This main menu screen corresponds to the display screen on the right side of FIG. 5-3, but even though a safety registration request has been made, the safety registration request confirmation area R2 is not displayed superimposed on the main menu screen.

<Processing>
FIG. 5-4 is a flowchart showing an example of the flow of processing executed by each device in this embodiment.
This figure shows an example of a process executed by the control unit 21 of the terminal 20X, a process executed by the control unit 21 of the terminal 20Y, and a process executed by the control unit 11 of the server 10, in order from the left side.

Here, similar to the display screen,
・Safety registration request account = User Y of terminal 20Y. Account of user Y (not limited, but an example of the user of the first terminal) ・Safety registration request account = user X of terminal 20X. The following is an example of processing when the account is X (an example of a user of a terminal, not limited).

By way of example and not limitation, when displaying disaster information (Y120), the control unit 21 of the terminal 20Y displays a screen for determining whether or not to make a safety registration request for requesting safety confirmation registration in the safety registration request account. is displayed on the display unit 24 (Y410).

As an example and not as a limitation, if it is determined that it is selected to make a safety registration request based on the input operation on the determination screen (Y410: YES), the control unit 21 of the terminal 20Y, as an example and not as a limitation, Safety registration request information including the application ID of the safety registration request account is transmitted to the server 10 via the communication I/F 22 (Y420).
If it is determined that making a safety registration request is not selected (Y410: NO), the control unit 21 of the terminal 20Y skips step Y420.

By way of example and not limitation, upon transmitting disaster information (S120), the control unit 11 of the server 10 determines whether or not the communication I/F 14 has received safety registration request request information for the safety registration request account (S410). ).
When determining that the safety registration request request information has been received (S410: YES), the control unit 11 of the server 10 determines whether the setting conditions regarding the safety registration request account are satisfied (S420). The setting conditions will be described later.

If it is determined that the setting conditions are satisfied (S420: YES), the control unit 11 of the server 10 transmits safety registration request information for requesting safety confirmation registration to the terminal 20X of the safety registration request account ( S430).

Note that the safety registration request information may or may not include information regarding the safety registration request account (as an example and not a limitation, an application ID).
Further, the safety registration request information may be transmitted by directly relaying the received safety registration request information.

When determining that the setting condition is not satisfied (S420: NO), the control unit 11 of the server 10 causes the step of S430 to be skipped.

When determining that the safety registration request request information is not received (S410: NO), the control unit 11 of the server 10 skips steps S420 to S430.

By way of example and not limitation, the control unit 21 of the terminal 20X displays disaster information (X120) and determines whether safety registration request information has been received through the communication I/F 22 (X430).
When determining that the safety registration request information has been received (X430: YES), the control unit 21 of the terminal 20X displays the received safety registration request information on the display unit 24 (X440).
When determining that the safety registration request information has not been received (X430: NO), the control unit 21 of the terminal 20X skips step X440.

The control unit 21 of the terminal 20X, the control unit 21 of the terminal 20Y, and the control unit 11 of the server 10 determine whether to end the process (X450, Y450, S450). Here, the conditions for determining whether or not to terminate the process include, but are not limited to, a case where a specific period of time (one week, not a limitation) has elapsed since the date and time of the disaster, and a condition based on user input on the server 10. Examples include a case where the confirmation service is selected to be stopped.

If it is determined that the process should be terminated (X450: YES, Y450: YES, S450: YES), the control unit 21 of each terminal 20 and the control unit 11 of the server 10 terminate the process.

If it is determined that the process is not to end (X450: NO, Y450: NO, S450: NO), the control unit 21 of the terminal 20X returns the process to step X430, by way of example and not limitation. Moreover, the control unit 21 of the terminal 20Y returns the process to step Y410, by way of example and not limitation. Further, the control unit 11 of the server 10 returns the process to step S410, by way of example and not limitation.

Note that in this flowchart, the processes of S120, X120, and Y120 may be omitted, and the transmission of disaster information at the server 10 and the display of disaster information at each terminal 20 may not be performed.

Further, steps X430 to X440 in the terminal 20X are not essential. This is because there is a possibility that the terminal 20X of the account requesting safety registration is in an offline state due to a disaster.

FIG. 5-5 is a timing chart showing an example of the timing of processing executed by each device in this embodiment. An example of the above-mentioned setting conditions will be explained using this timing chart. Here, the setting condition is "when the first safety registration request is made to the safety registration request account".

As an example and not a limitation, when the terminal 20Y performs a safety registration request request operation for the terminal 20X (Y410: YES), first safety registration request information is transmitted to the server 10 (Y420) (timing "TM510"). ).
Then, the control unit 11 of the server 10 determines that the setting condition is satisfied (420: YES), and transmits the first safety registration request information to the terminal 20X (S430) (timing "TM520").

Upon receiving the first safety registration request information, the control unit 11 of the terminal 20X displays the first safety registration request information on the display unit 24 (X440) (timing "TM530").

Thereafter, by way of example and not limitation, when the terminal 20Y performs a safety registration request request operation for the terminal 20X again (Y410: YES), second safety registration request information is transmitted to the server 10 (Y420) (timing "TM540").
Then, the control unit 11 of the server 10 determines that the setting condition is not satisfied (S420: NO), and does not transmit the second safety registration request information to the terminal 20X.

As an example and not a limitation, when the safety registration request request operation for the terminal 20X is performed again at the terminal 20Y (Y410: YES), the third safety registration request request information is transmitted to the server 10 (Y420) (timing "TM550"). ”).
Then, the control unit 11 of the server 10 determines that the setting condition is not satisfied (S420: NO) and does not transmit the third safety registration request information to the terminal 20X.

In this setting condition, when multiple safety registration requests are made from a safety registration requesting account to one safety registration requesting account, only the first time the safety registration is registered to the terminal 20 of the safety registration requesting account. An example of how a request is made is shown. By determining the setting conditions in this manner, the user of the account requesting safety registration can be relieved from the trouble of being repeatedly asked to register the safety status in the event of an emergency.

Note that, different from the above setting condition, the setting condition may be "when a safety registration request is made for the Nth time ("N" is a natural number) to the safety registration request account". In this case, when safety registration request requests are made N times from one safety registration request account to one safety registration request account, the control unit 11 of the server 10 transfers safety registration request request information to the safety registration request account for the first time. The information is sent to the terminal 20 of

<Effects of the fifth embodiment>
In this embodiment, the server 10 (not limited to, an example of a server that communicates with a terminal) sends first safety registration request information ( An example of the first information (not a limitation) is received by the communication I/F 14 from the terminal 20 (an example of the first terminal, not a limitation) of the user of the safety registration request account. Based on the received first safety registration request information and the set conditions, the server 10 transmits the first safety registration request information (not limited to, but an example of second information related to safety confirmation) to the communication interface. /F14 shows a configuration in which the message is sent to the terminal 20 of the user of the account requesting safety registration.
As an example of the effect of the embodiment obtained by such a configuration, first information regarding a request to confirm the safety of the user of the terminal is received from the first terminal, and based on the first information and the set conditions, Second information related to safety confirmation can be sent to a terminal to inquire about the safety of the user of the terminal.

<Fifth modification (1)>
In the above embodiment, the server 10 transmits the safety registration request information only once to the safety registration request account based on the setting conditions, but the present invention is not limited to this. By way of example and not limitation, the server 10 may transmit the safety registration request information multiple times based on the setting conditions.
Further, in the above embodiment, the safety registration request account and the safety recipient registration request account are described as different accounts, but the present invention is not limited to this.

The screen diagrams described below illustrate implementation examples in a messaging application.

FIG. 5-6 shows user A. when the method of this embodiment is applied to a messaging application. An example of the home screen of the messaging application displayed on the display unit 24 of A's terminal 20A is shown.
On this home screen, unlike the home screen shown on the left side of Figure 1-12, the friend list includes user B. Icon and user name corresponding to user B, user C. The icon and user name corresponding to C, the user D. The icon and user name corresponding to D, the user E. Icon and user name corresponding to user F.E. A list of icons, user names, etc. corresponding to F is displayed.

Also, user B. Based on the fact that user B has not set safety information, user B. On the icon corresponding to B, a first unknown icon UIC1 (in this example, an icon indicating the character "?") is displayed in a superimposed manner. User C. Based on the fact that user C has set "danger" as safety information, user C. A first danger icon DIC1 is displayed superimposed on the icon corresponding to C. User D. Based on the fact that user D has set "safety" as the safety information, user D. A first safety icon SIC1 is displayed superimposed on the icon corresponding to D. User E. Based on the fact that user E has set "safety" as the safety information, user E. A first safety icon SIC1 is displayed superimposed on the icon corresponding to E. User F. Based on the fact that user F has set "safety" as the safety information, user F. A first safety icon SIC1 is displayed superimposed on the icon corresponding to F.

By way of example and not limitation, on the home screen on the left side of FIG. 5-6, user B. When the user taps the friend list item corresponding to user B, as an example and not a limitation, user B.B in the center of FIG. The display changes to B's profile screen.

This profile screen is different from the example shown on the right side of FIG. 2-5, and this profile screen is for user B. Below the icon and username representing B's profile, user B. A second unknown icon UIC2 is displayed as information regarding B's safety. In addition, below the button for talking with that user, the button for making a voice call with that user, and the button for making a video call with that user, A safety registration request button BT2b similar to the safety registration request button BT2a described above is displayed to prompt the user to set safety information.

By way of example and not limitation, on the profile screen in the center of Figures 5-6, user B. When the user taps the safety registration request button BT2b for B as the other party, the safety registration request confirmation information SRI2 is displayed superimposed on the profile screen, by way of example and not limitation, as shown on the right side of FIG. 5-6.

Safety registration request confirmation information SRI2 includes, by way of example and not limitation, an image related to the icon image of the safety confirmation application, the text "A request for safety registration has been made to B.B.", and a request for safety registration. This includes an OK button indicated by an icon including the word "OK" for confirming that the request has been made and for terminating the display of the safety registration request confirmation information SRI2.

The left side of FIG. 5-7 shows user B. An example of the talk room screen displayed on the display unit 24 of the terminal 20B of B is shown.
In this talk room screen, unlike the talk room screen shown in the center of FIG. 1-10, the talk room name display area includes user B. Characters (in this example, "Safety Confirmation Service") indicating that B is a talk room for talking with the OA account of the safety confirmation service registered in the messaging application as an official account are displayed. .

In the talk area, as an example and not a limitation, the text "This is a safety confirmation response service. 20XX/08/04 9:39 An earthquake with its epicenter off the coast of Ibaraki Prefecture has occurred" is displayed as content from an OA account. Disaster occurrence content DCT1 including the content DCT1 is displayed.
Below that, as content from the OA account, "Safety Registration Request The following friends have requested you to register their safety status" and user A. Safety registration request content RCT1 including the icon image and user name of A, and a response button BT4b for responding to the request is displayed.

By way of example and not limitation, user A. A by user B. After a safety registration request is made for user B, user C. C by user B. Assume that a safety registration request is made for B as the other party.
In this case, user C. On the terminal 20C of C, safety registration request confirmation information SRI3 is displayed superimposed on a profile screen as shown in the center of FIG. 5-7, by way of example and not limitation.

In this profile screen, unlike the profile screen shown on the right side of FIG. 5-6, the icon image and user name (in this example, "user C. ”) is displayed.

Safety registration request confirmation information SRI3 includes, by way of example and not limitation, an image related to the icon image of the safety confirmation application, the text "A request for safety registration has been made to B.B.", and a request for safety registration. An OK button indicated by an icon including the word "OK" is displayed for confirming that the request has been made and for terminating the display of the safety registration request confirmation information SRI3.

By way of example and not limitation, user A. A by user B. After a safety registration request is made for user B, user C. C by user B. Assume that a safety registration request is made for B as the other party.
In this case, user B. By way of example and not limitation, a talk room screen as shown on the right side of FIG. 5-7 is displayed on B's terminal 20B.

In this display example of the talk room screen, user C. C by user B. Even though a safety registration request was made with B as the other party, no new safety registration request content is displayed in the talk area, and the display screen is the same as the one on the left side of Figure 5-7.

The left side of FIG. 5-8 shows user B. An example of the talk room screen displayed on the display unit 24 of the terminal 20B of B is shown. This talk room screen is similar to the display screen on the left side of FIG. 5-7, so a description thereof will be omitted.

By way of example and not limitation, user A. A by user B. After a safety registration request is made for user B, user C. C by user B. Assume that a safety registration request is made for B as the other party. Furthermore, user B. Assume that a safety registration request is made for B as the other party.
In this case, user B. By way of example and not limitation, a talk room screen as shown on the right side of FIG. 5-8 is displayed on B's terminal 20B.

In this display example of the talk room screen, unlike the talk room screen shown on the right side of FIG. The content from the OA account is ``Safety Registration Request: The following friends have requested safety registration.'' User A. A's icon image and user name, user C. C's icon image and user name, user D. D's icon image and user name, user F. A new safety registration request content RCT2 for ``10:43'', 60 minutes after ``9:43'' above, is displayed, including the icon image and user name of F, and a response button BT4b for responding to the request. ing.

Note that information such as the safety registration request content may be displayed on another screen instead of being displayed on the talk room screen of the OA account of the safety confirmation service as described above.
By way of example and not limitation, in the example display screens of FIGS. 5-7, user A. The safety registration request content from user A. It may be displayed on the talk room screen for talking with A, on the friend list screen, or on the talk list screen.

FIG. 5-9 is a flowchart showing an example of the flow of processing executed by each device in this modification.
This figure shows an example of a process executed by the control unit 21 of the terminal 20X, a process executed by the control unit 21 of the terminal 20Y, and a process executed by the control unit 11 of the server 10, in order from the left side.

Here, unlike the display screen,
・User X of terminal 20X. X=user A. of terminal 20A on the display screen. A
- User Y of terminal 20Y. Y=User B of terminal 20B on the display screen. B
The following is an example of the processing when
Note that it is possible to perform the same processing on other terminals such as 20C and the like as well as on the terminals 20X and 20Y.

By way of example and not limitation, the control unit of each device executes a safety registration request process (X480, Y480, S480) after executing a safety confirmation process (X210, Y210, S210).

FIG. 5-10 is a flowchart showing an example of safety registration request processing. The view of the figure is the same as Figure 5-9.
By way of example and not limitation, the control unit 21 of the terminal 20X controls user Y. of the terminal 20Y. Determine whether or not to make a safety registration request to the terminal 20Y by displaying on the display unit 24 a screen for determining whether or not to make a safety registration request to request safety confirmation registration to Y. (Y4410y).

As an example and not a limitation, if it is determined that making a safety registration request has been selected based on the input operation on the determination screen (X4410y: YES), the control unit 21 of the terminal 20X, as an example and not a limitation, Safety registration request information including the application ID of the terminal 20Y is transmitted to the server 10 via the communication I/F 22 (X4420y).
If it is determined that making a safety registration request is not selected (X4410y: NO), the control unit 21 of the terminal 20X skips step X4420y.

The control unit 11 of the server 10 determines whether or not safety registration request information in which the account of the terminal 20Y is the safety registration request account has been received through the communication I/F 14 (S4410y).
When determining that the safety registration request request information for the terminal 20Y has been received (S4410y: YES), the control unit 11 of the server 10 determines that the composite setting condition regarding the terminal 20 (in this case, the terminal 20Y) of the safety registration request account is satisfied. It is determined whether or not (S4420y). The composite setting conditions will be described later.

If it is determined that the composite setting condition for the terminal 20Y is satisfied (S4420y: YES), the control unit 11 of the server 10 sends safety registration request information for requesting safety confirmation registration to the terminal 20Y of the safety registration request account. (S4430y). Note that the safety registration request information may or may not include information regarding the safety registration request account (as an example and not a limitation, an application ID).

When determining that the composite setting condition for the terminal 20Y is not satisfied (S4420y: NO), the control unit 11 of the server 10 causes the step of S4430y to be skipped.

When determining that the safety registration request request information for the terminal 20Y is not received from any terminal 20 (S4410y: NO), the control unit 11 of the server 10 skips steps S4420y to S4430y.

By way of example and not limitation, the control unit 21 of the terminal 20Y controls the user X. of the terminal 20X. When making a safety registration request for X, safety registration request information is transmitted to the server 10 (Y4410x/Y4420x). Each step can be performed similarly to X4410y and X4420y, by way of example and not limitation.

The control unit 11 of the server 10 executes each step of S4410x to S4430x using the safety registration request account as the account of the terminal 20X. Each step can be performed similarly to S4410y-S4430y, by way of example and not limitation.

Further, the control unit 21 of the terminal 20X executes the same process as X4410y and X4420y using the account of the other terminal 20 as the safety registration request account. The control unit 11 of the server 10 executes the same processing as each step of S4410x to S4430x while changing the safety registration request account.

The same applies to other terminals 20.

The control unit 21 of the terminal 20Y determines whether safety registration request information has been received through the communication I/F 22 (Y4430).
When determining that the safety registration request information has been received (Y4430: YES), the control unit 21 of the terminal 20Y displays the received safety registration request information on the display unit 24 (Y4440).
When determining that the safety registration request information has not been received (Y4430: NO), the control unit 21 of the terminal 20Y skips step Y4440.

The same applies to other terminals 20.

Returning to FIG. 5-9, the control unit 21 of the terminal 20X, the control unit 21 of the terminal 20Y, and the control unit 11 of the server 10 determine whether to end the process (X490, Y490, S490). Here, the conditions for determining whether or not to terminate the process include, but are not limited to, a case where a specific period of time (one week, not a limitation) has elapsed since the date and time of the disaster, and a condition based on user input on the server 10. Examples include a case where the confirmation service is selected to be stopped.

If it is determined that the process should be terminated (X490: YES, Y490: YES, S490: YES), the control unit 21 of each terminal 20 and the control unit 11 of the server 10 terminate the process.

If it is determined that the process is not to be terminated (X490: NO, Y490: NO, S490: NO), the control unit 21 of each terminal 20 and the control unit 11 of the server 10 may execute the safety confirmation process again, by way of example and not limitation. Execute (X210, Y210, S210).

The same applies to other terminals 20.

Note that, in FIG. 5-9, the transmission of disaster information to each terminal 20 in the server 10 and the display process of disaster information in each terminal 20 do not need to be executed.
Further, the chat process may be executed at any timing.

Here, as an example and not a limitation, the composite setting condition for each terminal 20 is defined as a combination of the following two conditions.
- "Initial transmission setting conditions": Conditions for transmitting safety registration request information for the first time to the terminal 20 of the safety registration requesting account.
- "Retransmission setting condition": Condition for transmitting the safety registration request information again after transmitting the safety registration request information to the terminal 20 of the safety registration request account.

The initial transmission setting conditions include, by way of example and not limitation, the following examples.
(X1). When the server 10 receives safety registration request information for the terminal 20 of one safety registration request account for the first time.
(X2). When the server 10 receives safety registration request information for the terminal 20 of one safety registration request account L times (“L” is a natural number).
(X3). When the server 10 first receives safety registration request request information from the terminal 20 of one safety registration request account to the terminal 20 of one safety registration request account.
(X4). When the server 10 receives safety registration request information M times (“M” is a natural number) from the terminal 20 of one safety registration request account to the terminal 20 of one safety registration request account.
(X5). After the server 10 receives the safety registration request information for the terminal 20 of one safety registration request account for the first time, the first set time (for example, but not limited to, "0 minute 0 second of every hour") is reached.
(X6). When the first set time (by way of example, not limitation, "5 minutes") has elapsed after the server 10 first received the safety registration request information for the terminal 20 of one safety registration request account.
(X7). A case where the server 10 transmits disaster information again after receiving the safety registration request request information for the terminal 20 of one safety registration request account for the first time.
(X8). Any combination of the above (X1) to (X7).

In addition, the retransmission setting conditions include, by way of example and not limitation, the following examples.
(Y1). When the server 10 receives safety registration request information for the terminal 20 of one safety registration request account P times (“P” is a natural number). Note that P times may or may not include the number of times the server 10 receives the safety registration request information until the initial transmission setting condition is satisfied.
(Y2). For the first time, the server 10 receives safety registration request request information for the terminal 20 of one safety registration requesting account from a terminal 20 of a safety registration requesting account different from the terminal 20 of one safety registration requesting account that satisfies the initial transmission setting conditions. if you did this.
(Y3). The server 10 sends safety registration request request information Q times to the terminal 20 of one safety registration requesting account from a terminal 20 of a safety registration requesting account different from the terminal 20 of one safety registration requesting account that satisfies the initial transmission setting conditions. (“Q” is a natural number) When received. Note that Q times may or may not include the number of times the server 10 receives the safety registration request information until the initial transmission setting condition is satisfied.
(Y4). When the server 10 receives safety registration request information R times (“R” is a natural number) from the terminal 20 of one safety registration requesting account that satisfies the initial transmission setting conditions to the terminal 20 of one safety registration requesting account. . Note that R times may or may not include the number of times the server 10 receives the safety registration request information until the initial transmission setting condition is satisfied.
(Y5). After the server 10 sends the safety registration request information to the terminal 20 of one safety registration request account, the second set time (for example, but not limited to, "0:00:00 when the date changes" or "disaster occurrence time") +T hours later” (“T” is a natural number)).
(Y6). When the second set time (by way of example, not limitation, "60 minutes") has elapsed after the server 10 sent the safety registration request information to the terminal 20 of one safety registration request account.
(Y7). A case where the server 10 sends disaster information again after sending safety registration request information to the terminal 20 of one safety registration request account.
(Y8). Any combination of the above (Y1) to (Y7).

By way of example and not limitation, the examples in FIGS. 5-6 to 5-8 are examples where the composite setting condition is (X1)+(Y6).

FIG. 5-11 is a timing chart showing an example of the timing of processing executed by each device when the composite setting condition is (X1)+(Y1), by way of example and not limitation.

By way of example and not limitation, when a safety registration request request operation for the terminal 20X is performed in the terminal 20Y, first safety registration request information is transmitted to the server 10 (timing "TM610").
Then, the control unit 11 of the server 10 determines that the initial transmission setting condition (X1) is satisfied, and transmits the first safety registration request information to the terminal 20X (timing "TM620").
Upon receiving the first safety registration request information, the control unit 21 of the terminal 20X displays the first safety registration request information on the display unit 24 (timing "TM630").

Thereafter, by way of example and not limitation, when the safety registration request request operation for the terminal 20X is performed again at the terminal 20Y, the second safety registration request request information is transmitted to the server 10 (timing "TM640").
Then, the control unit 11 of the server 10 determines that the retransmission setting condition (Y1) is not satisfied, and does not transmit the second safety registration request information to the terminal 20X (timing "TM650").

A safety registration request request operation for the terminal 20X is executed in each terminal 20, and the server 10 receives the P+1th safety registration request request information (timing "TM660"). Then, the control unit 11 of the server 10 determines that the retransmission setting condition (Y1) is satisfied, and transmits the second safety registration request information to the terminal 20X (timing "TM670").
Upon receiving the second safety registration request information, the control unit 21 of the terminal 20X displays the second safety registration request information on the display unit 24 (timing "TM680").

The initial transmission setting conditions and retransmission setting conditions can be set according to the following idea, by way of example and not limitation.

・First idea: Once the initial transmission setting conditions are satisfied in one safety registration request account and the safety registration request information is sent once, it is basically not retransmitted. This prevents the same type of information from being repeatedly sent to the terminal 20 of the safety registration requesting account in an emergency situation when communication bandwidth is at a premium and the operating time of the terminal 20 is likely to be limited. be able to. However, since the user of the safety registration request account may have forgotten to perform the safety confirmation registration, if the retransmission setting conditions are met, the safety registration request information is sent again as a reminder.

-Second idea: If the initial transmission setting conditions are met for one safety registration request account, the safety registration request information is immediately sent. Thereafter, even if the retransmission setting conditions are met, the safety registration request information is immediately transmitted. This makes it possible to control the frequency at which the server 10 sends safety registration request information to the terminal 20 of the safety registration request account, and to prevent the user from being bothered by the frequent display of safety registration request information on the terminal 20. can be released.

Note that the composite setting condition may be only the initial transmission setting condition. In this case, retransmission of the safety registration request information is not executed.

Also, by way of example and not limitation, conditions regarding the number of retransmissions may be added to the retransmission setting conditions. As a condition regarding the number of retransmissions, by way of example and not limitation, an upper limit number of times the safety registration request information can be retransmitted to the terminal 20 of the safety registration requesting account may be determined.

In this modification, the above-mentioned setting conditions are based on initial transmission setting conditions (not a limitation, but an example of conditions for transmitting the second information to the terminal when the server first receives the first information for the user of the terminal). including conditions for transmitting based on a retransmission setting condition (not limited to, but an example of a first setting condition in which the second information is sent to the terminal after first receiving the first information for the user of the terminal) It shows the configuration.
As an example of the effect of the embodiment obtained by such a configuration, when the server first receives the first information and the first information for the user of the terminal, it transmits the second information to the terminal and provides the first information for the user of the terminal. After first receiving the first information, the second information is sent to the terminal based on the first setting condition, and the second information regarding safety confirmation is sent to the terminal to inquire about the safety of the user of the terminal. be able to

In addition, in this case, the retransmission setting condition is to send the safety registration request information (not limited, an example of secondary information) to the safety registration request account based on the set time or the set time (time interval). It may include conditions for transmitting to the user's terminal 20.
As an example of the effect of the embodiment obtained by such a configuration, the first information and the set time or the condition for transmitting the second information to the terminal based on the set time can be used to 2 information can be sent to a terminal to inquire about the safety of the user of that terminal.

In addition, in this case, the retransmission setting condition is such that after the server 10 first receives the safety registration request information (an example of the first information, not a limitation), and then the safety registration request information (an example of the first information, not a limitation) that the server 10 receives It is possible to include a condition for transmitting the safety registration request information (not limited to, an example of the second information) to the terminal 20 of the user of the safety registration request account based on the number of items (an example of the first information). can.
As an example of the effect of the embodiment obtained by such a configuration, after first receiving the first information, the server transmits the second information to the terminal based on the number of first information received. Based on the conditions, it is possible to send second information regarding safety confirmation to the terminal and inquire about the safety of the user of the terminal.

In addition, in this case, the retransmission setting conditions are based on information such as information indicating that a disaster has occurred again (not a limitation, but an example of disaster-related information), and based on safety registration request information (not a limitation, but an example of information related to a disaster). For example, it may include a condition for transmitting a message (for example) to the terminal 20 of the user of the account requesting safety registration.
As an example of the effect of the embodiment obtained by such a configuration, second information regarding safety confirmation is transmitted to the terminal based on the first information and a condition for transmitting the second information to the terminal based on information regarding the disaster. You can ask about the safety of the user of that terminal.

In addition, in this case, the safety registration request information (not a limitation, but an example of secondary information) is a chat room (not a limitation, but an example of a terminal user) that includes the user of the safety registration request account (not a limitation, but an example of a terminal user). (for example, a room).
As an example of the effect of the embodiment obtained by such a configuration, the second information related to safety confirmation is displayed in a chat room that includes terminal users, so that terminal users can be informed of their safety in an easy-to-understand manner. you can ask.

<Fifth modification (2)>
In the above modification, the server 10 transmits the safety registration request information to the terminal 20 of the safety registration request account when the composite setting condition is satisfied, but the present invention is not limited to this. As an example and not a limitation, if the transmission stop setting conditions described below are satisfied, the server 10 does not send safety registration request information to the terminal 20 of the safety registration requesting account even if the initial transmission setting conditions and retransmission setting conditions are met. You can do it like this.

The left side of FIG. 5-12 shows user B. An example of the talk room screen displayed on the display unit 24 of the terminal 20B of B is shown. This talk room screen is similar to the display screen on the left side of FIG. 5-7, so a description thereof will be omitted.

As an example and not a limitation, when the user taps the answer button BT4b included in the safety registration request content RCT1 on the talk room screen on the left side of Figure 5-12, the home page shown in the center of Figure 5-12 is displayed. The display changes on the screen.

This home screen differs from the home screen shown on the left side of FIG. ”) is displayed.

As an example and not a limitation, in the safety registration area R1 in the center of FIG. 5-12, the danger button DBT is set to user B. When tapped by user B, the text "I was injured" is displayed as a standard message for safety messages. After being selected by user B.B, the registration button BT3 is selected by user B.B. When tapped by user A. An example of the talk list screen displayed on A's terminal 20A is shown on the right side of FIG. 5-12. This talk list screen is similar to the talk list screen on the right side of FIG. 1-19, so a description thereof will be omitted.

By way of example and not limitation, on the talk list screen on the right side of FIG. 5-12, user B. When the icon image of the chat room list item of B is tapped by the user, as an example and not a limitation, the user B. The display changes to the profile screen corresponding to B.

In this profile screen, unlike the example shown in the center of FIG. 5-6, the icon image and user name (in this example, "user A.A." ) is displayed. Also, user B. Below the icon representing B's profile and the user name, user B. A second danger icon DIC2 is displayed as information regarding B's safety.

By way of example and not limitation, in the profile screen on the left side of Figure 5-13, user B. When the user taps the safety registration request button BT2b for B as the other party, the safety registration request confirmation information SRI4 shown in the center of FIG. 5-13 is displayed superimposed on the profile screen, by way of example and not limitation.
This safety registration request confirmation information SRI4 is the same as the safety registration request confirmation information SRI2 on the right side of FIG. 5-6, so a description thereof will be omitted.

By way of example and not limitation, user B. After user B responds to the safety registration request, user A. A by user B. Assume that a safety registration request is made for B as the other party.
In this case, user B. By way of example and not limitation, a talk room screen as shown on the right side of FIG. 5-13 is displayed on B's terminal 20B.

In this talk room screen, user A. A by user B. Even though a safety registration request was made for party B, the safety registration request content from the OA account that corresponds to the new safety registration request is not displayed in the talk area, similar to the left side of Figure 5-12. This is the display screen.

In this modification, the transmission stop setting conditions include the following examples, but are not limited to them.
(Z1). When the server 10 receives safety confirmation registration information from the terminal 20 of one safety registration request account.
(Z2). When the server 10 receives safety registration request information for the terminal 20 of one safety registration request account U times (“U” is a natural number).
(Z3). When the server 10 receives safety registration request information for the terminal 20 of one safety registration requesting account V times (“V” is a natural number) from the terminal 20 of a specific safety registration requesting account.
(Z4). When the third set time (as an example and not a limitation, it is "disaster occurrence time + 72 hours later").
(Z5). When the third set time (by way of example, not limitation, "36 hours") has elapsed after the server 10 sent the safety registration request information to the terminal 20 of one safety registration request account.
(Z6). When the server 10 transmits disaster information again.
(Z7). Any combination of the above (Z1) to (Z6).

By way of example and not limitation, the examples in FIGS. 5-12 and 5-13 are examples where the transmission stop setting condition is (Z1).

FIG. 5-14 is a timing chart showing an example of the timing of processing executed by each device when the composite setting condition is (X1) + arbitrary retransmission setting condition + (Z1), by way of example and not limitation. .

As an example and not a limitation, when a safety registration request request operation for the terminal 20X is performed in the terminal 20Y, first safety registration request information is transmitted to the server 10 (timing "TM710").
Then, the control unit 11 of the server 10 determines that the initial transmission setting condition (X1) is satisfied, and transmits the first safety registration request information to the terminal 20X (timing "TM720").
Upon receiving the first safety registration request information, the control unit 21 of the terminal 20X displays the first safety registration request information on the display unit 24 (timing "TM730").

Thereafter, by way of example and not limitation, a safety confirmation process is executed, and when an input operation for safety confirmation registration information is accepted at the terminal 20X, first safety confirmation registration information is transmitted to the server 10 (timing "TM740"). . Then, the server 10 receives the first safety confirmation registration information.
The control unit 11 of the server 10 generates first safety information based on the first safety confirmation registration information and transmits it to each terminal 20 (timing "TM750").
Upon receiving the first safety information, the terminal 20Y executes display processing (timing "TM760").

Thereafter, by way of example and not limitation, when a safety registration request request operation for the terminal 20X is performed in the terminal 20Y, second safety registration request request information is transmitted to the server 10 (timing "TM770").
Then, the control unit 11 of the server 10 determines that the transmission stop setting condition (Z1) is satisfied, and does not transmit the second safety registration request information to the terminal 20X (timing "TM780").

Note that when the control unit 21 of the terminal 20Y receives the safety information regarding the account of the terminal 20X, it may not accept a safety registration request request operation for the account of the terminal 20X thereafter.

In this modification, the server 10 transmits safety confirmation registration information (not limited to third information including information related to the safety of the user of the terminal) based on transmission of safety registration request information (not limited to, but an example of second information). example) is received by the communication I/F 14. Based on the reception of this safety confirmation registration information, the server 10 receives safety registration request request information (not limited, but an example of third information) for the safety registration request account after receiving this safety confirmation registration information. In this case, the control unit 11 controls not to transmit the safety registration request information based on the safety registration request information.
As an example of the effect of the embodiment obtained by such a configuration, based on the transmission of the second information, third information including information regarding the safety of the user of the terminal is received from the terminal, and upon reception of this third information. Based on the above, if the first information for the terminal user is received after receiving the third information, the safety of the terminal user can be confirmed once by not transmitting the second information based on the first information. This eliminates the need to confirm the information again in the event of a failure, thereby eliminating the need for the terminal user to feel inconvenienced. It also eliminates unnecessary communication and reduces communication volume.

<Fifth modification (3)>
In the above embodiment, the setting conditions (composite setting conditions) are determined in the server 10, but the present invention is not limited thereto. As an example and not a limitation, the setting conditions (composite setting conditions) may be determined by the terminal 20 of the safety registration requesting account.

In this case, upon receiving the safety registration request information from the terminal 20Y of the safety registration requesting account to the terminal 20X of the safety registration requesting account, the control unit 11 of the server 10 transmits the safety registration request information to the terminal 20X.
Upon receiving the safety registration request information, the control unit 21 of the terminal 20X determines whether a setting condition (composite setting condition) is satisfied. When the control unit 21 of the terminal 20X determines that the setting condition (composite setting condition) is satisfied, the control unit 21 of the terminal 20X causes the display unit 24 to display the received safety registration request information.
When determining that the setting condition (composite setting condition) is not satisfied, the control unit 21 of the terminal 20X does not display the received safety registration request information on the display unit 24.

<Fifth modification (4)>
In the above embodiment, the setting conditions (composite setting conditions) are determined in the server 10, but the present invention is not limited thereto. As an example and not a limitation, the setting conditions (composite setting conditions) may be determined by the terminal 20 of the safety registration request account.

In this case, when a safety registration request request operation is performed on the terminal 20X of the safety registration request account, the control unit 21 of the terminal 20Y of the safety registration request account determines whether the setting condition (composite setting condition) is satisfied. do. Then, when determining that the setting condition (composite setting condition) is satisfied, the control unit 21 of the terminal 20Y transmits safety registration request information to the server 10.
Upon receiving the safety registration request information for the terminal 20X from the terminal 20Y, the control unit 11 of the server 10 transmits the safety registration request information to the terminal 20X.
Upon receiving the safety registration request information, the control unit 21 of the terminal 20X causes the display unit 24 to display the information.

When determining that the setting condition (composite setting condition) is not satisfied, the control unit 21 of the terminal 20Y does not transmit safety registration request information to the server 10.

Note that when determining setting conditions (composite setting conditions) on the terminal 20 of the safety registration request account, it is not possible to determine whether another terminal 20 has sent safety registration request request information to the terminal 20 of the safety registration request account. . Therefore, in this case, the setting conditions (compound setting conditions) include the number of times the safety registration request request operation is performed on the own terminal, the time, the time since the safety registration request request operation was accepted on the own terminal, and whether disaster information has been received again. limited to.

<Sixth Example>
The sixth embodiment is an example in which a safety registration requesting account that has requested a safety registration request to the safety registration requesting account can be confirmed on the terminal 20 of the safety registration requesting account.

The content described in the sixth embodiment is applicable to any of the other embodiments and other modifications.
In addition, the same reference numerals are given to the same constituent elements as those already mentioned, and the explanation thereof will be omitted.

<Display screen>
FIG. 6-1 is a diagram showing an example of a messaging application screen displayed on the display unit 24 of the terminal 20B.
On the left side of Figure 6-1, in the safety registration request content RCT6 indicated as "Safety registration request" in the talk area, in addition to the answer button BT4b, there is also a safety information that has requested a safety registration request for yourself (user B.B). A "friend confirmation" button BT6 is provided for confirming the registration requesting account (friend). When this "friend confirmation" button BT6 is tapped, a display as shown on the right side of FIG. 6-1 is displayed.

Specifically, a safety registration request requesting user list area SRR that includes information about the safety registration requesting account that requested the safety registration request for himself (user B.B) is displayed rising from the bottom of the screen. . In this example, along with the text "The following friends have asked you to register their safety status," the message "User A. A. User C. C. User D. D. User F. Icons and user names are displayed for each of the four users F. Moreover, on each user's icon, an icon based on the safety status information registered by that user is superimposed and displayed.

<Processing>
FIG. 6-2 is a timing chart showing, by way of example and not limitation, an example of the timing of processing executed by each device in this embodiment.
This figure shows an example of a process executed by the control unit 21 of the terminal 20X, a process executed by the control unit 21 of the terminal 20Y, and a process executed by the control unit 11 of the server 10, in order from the left side.

Here, unlike the display screen,
・Safety registration request account = User Y of terminal 20Y. Account Y = User of terminal 20A and terminal 20C to terminal 20F on the display screen - Safety registration request account = User X. of terminal 20X. Account of X = User B of terminal 20B on the display screen. B
The following is an example of the processing when

Further, a case where the composite setting condition is the above-mentioned (X1)+(Y1) will be exemplified.

By way of example and not limitation, when a safety registration request request operation for the terminal 20X is performed in the terminal 20Y, first safety registration request information is transmitted to the server 10 (timing "TM810").
Then, the control unit 11 of the server 10 determines that the initial transmission setting condition (X1) is satisfied, and transmits the first safety registration request information to the terminal 20X (timing "TM820").
Upon receiving the first safety registration request information, the control unit 21 of the terminal 20X displays the first safety registration request information on the display unit 24 (timing "TM830").

Thereafter, by way of example and not limitation, when a safety registration request request operation is performed on the terminal 20X in another terminal 20, second safety registration request request information is transmitted to the server 10.
Then, the control unit 11 of the server 10 determines that the retransmission setting condition (Y1) is not satisfied, and does not transmit the second safety registration request information to the terminal 20X (timing "TM840").

The same applies to the safety registration request information transmitted from other terminals 20 to the server 10.

Then, by way of example and not limitation, the control unit 21 of the terminal 20X executes a safety registration request request user information request operation (timing "TM850"). In the safety registration request request user information request operation, the control unit 21 of the terminal 20X sends the safety registration request request information to the terminal 20X, by way of example and not limitation, based on the user operation on the first safety registration request information. Determine whether it is selected to confirm the registration request account. If it is determined that checking the safety registration request account has been selected, the control unit 21 of the terminal 20X transmits safety registration request user information request information to the server 10 via the communication I/F 22.

When the communication I/F 14 receives the safety registration request request user information request information from the terminal 20X (timing "TM860"), the control unit 11 of the server 10 transmits the safety registration request request user list information to the terminal 20X via the communication I/F 14. Transmit (timing "TM870").
Here, the safety registration request request user list information includes, by way of example and not limitation, information regarding the safety registration request account in the safety registration request information for the terminal 20X received before timing "TM860" (by way of example, not limitation). (including application ID, user name, etc.).

When the communication I/F 22 receives the safety registration request user list information from the server 10, the control unit 21 of the terminal 20X displays the received safety registration request user list information on the display unit 24 (timing "TM880").

<Effects of the sixth embodiment>
In this embodiment, on the terminal 20 of the safety registration request account, based on the reception of the safety registration request information (not limited to, but an example of second information), the display of the safety registration request information and the display of the safety registration request information A display related to the safety registration requesting account that requested the safety registration request (not limited to, but an example of a first display related to safety confirmation) is displayed on the display unit 24. Then, the server 10 sends safety registration request information (not a limitation, but an example of first information) on the terminal 20 of the safety registration request account, based on the input by the user of the safety registration request account in response to the display. A configuration is shown in which information on the transmitted safety registration request account (not limited to, but an example of information on the user who transmitted the first information) is transmitted to the terminal 20 of the safety registration request account through the communication I/F 14.
As an example of the effect of the embodiment obtained by such a configuration, a first display related to safety confirmation is displayed on the display section of the terminal based on reception of the second information, and input by the user of the terminal to the first display is By transmitting the information of the user who transmitted the first information to the terminal based on the above, it is possible to inform the user of the terminal of the information of the user who transmitted the first information.

In addition, in this case, the server 10 receives the safety registration request information for the safety registration request account transmitted from the terminal 20 (not limited to, but an example of the first terminal) of one safety registration request account. Registration request information (not limited, but an example of second information) is transmitted to the terminal 20 of the safety registration request account via the communication I/F 14. Further, after receiving the safety registration request request information for the safety registration requesting account from the terminal 20 of one safety registration requesting account, the server 10 transmits the safety registration request request information for the safety registration requesting account to the other safety registration requesting account. is received from the terminal 20 (not limited, but an example of a second terminal) by the communication I/F 14. Furthermore, if the set conditions are not met, the server 10 transfers the safety registration request information based on the safety registration request information received from the terminal 20 (second terminal) of the other safety registration requesting account to the safety registration requesting account. The control unit 11 controls not to transmit data to the terminal 20. In this case, the server 10 transmits the safety registration request account to which the safety registration request information (an example of the first information, not a limitation) was sent based on the input by the user of the safety registration request account in response to the above display. information (not a limitation, but an example of the information of the user of the first terminal) and information of another safety registration request account (not a limitation, but an example of the information of the user of the second terminal) are received by the communication I/F 14. A configuration is shown in which the information is sent to the terminal 20 of the safety registration request account.
As an example of the effect of the embodiment obtained by such a configuration, first information for the user of the terminal is received from the first terminal, first information for the user of the terminal is received from the second terminal, and the set condition is If the second information is not satisfied, the second information based on the first information received from the second terminal is not transmitted to the terminal, so that the user of the terminal does not feel troubled. Further, in the terminal, a first display related to safety confirmation is displayed on the display section based on the reception of the second information, and a first display that transmitted the first information is displayed on the display section based on the input by the user of the terminal on the first display. By transmitting the user information including the information of the user of the terminal and the information of the user of the second terminal to the terminal, the information of the user of the first terminal and the user of the second terminal who transmitted the first information are transmitted to the terminal. information to the terminal user.

<Sixth modification (1)>
In the above embodiment, when the safety registration request request user information request operation is executed on the terminal 20X of the safety registration request account, the safety registration request request user information is transmitted from the server 10 to the terminal 20X. It is not limited to this.

FIG. 6-3 is a diagram showing an example of a display screen in this modification.
The left side and center of FIG. 6-3 are the same as the left side and center of FIG. 5-7, respectively.

In this modification, the safety registration request requesting user list information is transmitted from the server 10 to the terminal 20B at a timing to be described later. As a result, a display as shown on the right side of FIG. 6-3 is displayed on the display unit 24 of the terminal 20B. This screen corresponds to the left side of FIG. 6-3, but the content from user B. B is user A. A and user C. Safety registration request content RCT7 indicating that safety registration is requested from C is shown.

The control unit 11 of the server 10 can transmit the safety registration request requesting user list information to the terminal 20X if it is determined that the safety registration request requesting user list information transmission condition is satisfied at any timing.

Here, the conditions for transmitting the user list information requesting safety registration request include the following examples, but are not limited to them.
- When a set period (for example, "30 minutes", not limited) has elapsed since the safety registration request request information was last received from an arbitrary terminal 20.
- When the set time (for example, not limited, "noon") has arrived after the safety registration request request information was last received from an arbitrary terminal 20.
- When safety registration request request information is received from a given terminal 20 more than a set number of times or more than a set number of times.
- When a set period (for example, 30 minutes, not limited) has elapsed since the safety registration request request information was last received from each terminal 20.
- When the set time (for example, not limited, "noon") comes after the last safety registration request request information is received from each terminal 20.
- When safety registration request request information is received from each terminal 20 more than a set number of times or more than a set number of times.
- When safety confirmation registration information is received from terminal 20X.
- When sending safety registration request information to terminal 20X.

Note that the processing in this modification may be performed as follows.
By way of example and not limitation, when the control unit 11 of the server 10 receives safety registration request information from the terminal 20 of the safety registration request account, the control unit 11 of the server 10 controls the terminal regardless of the composite setting condition of whether or not to send the safety registration request information. Sends information regarding the received safety registration request account to 20X. Hereinafter, by way of example and not limitation, information regarding a safety registration request account corresponding to individual safety registration request request information will be referred to as "safety registration request request user information."

In this case, upon receiving the safety registration request user information from the server 10, the control unit 21 of the terminal 20X stores it in the storage unit 28, by way of example and not limitation.
When the control unit 21 of the terminal 20X determines that the safety registration request request user display condition is satisfied, the control unit 21 of the terminal 20X causes the display unit 24 to display the safety registration request request user information stored in the storage unit 28.

Here, as the user display condition for requesting a safety registration request, the following examples may be given, by way of example and not limitation.

- When the safety registration request request user information request operation is executed and it is selected to confirm the safety registration request account that sent the safety registration request request information for the terminal 20X.
- When a set period (for example, "30 minutes", not limited) has elapsed since the last time the safety registration request information was received from the server 10.
- When the set time (for example, not limited, "noon") has arrived after the safety registration request information was last received from the server 10.
- When the user information requesting safety registration request is received from the server 10 more than a set number of times or more than a set number of times.
- When safety confirmation registration information is entered on the terminal 20X.

<Seventh Example>
The seventh embodiment is an example in which a safety confirmation service does not accept safety confirmation registration when the safety registration period for one disaster has ended.

The content described in the seventh embodiment is applicable to any of the other embodiments and other modifications.
In addition, the same reference numerals are given to the same constituent elements as those already mentioned, and the explanation thereof will be omitted.

<Display screen>
FIG. 7-1 is a diagram showing an example of a messaging application screen displayed on the display unit 24 of the terminal 20B in this embodiment.
In this example, the user A. A. User C. C. User D. D. User F. Under the safety registration request content RCT8, which shows that four users of F have requested safety confirmation registration, there is a safety registration from the OA account due to the earthquake that occurred at 9:39 am on August 4, 20XX. Safety registration stop confirmation content SCT1 indicating that the safety registration is to be stopped is displayed. In this state, when the answer button BT4b in the safety registration request content RCT8 is tapped, a display as shown on the right side of FIG. 7-1 is displayed.

In this example, based on the fact that the period in which safety registration is possible has already passed, the words ``Safety registration period has ended'' and a character image are displayed in the center of the screen on the left side of Figure 7-1. Safety confirmation registration acceptance period end information EPI1 including the following and an "OK" button is displayed. When the "OK" button is tapped, the display of the safety confirmation registration acceptance period end information EPI1 is cleared, but the safety confirmation registration is not accepted and user B. B is configured so that it cannot register for safety confirmation.

<Processing>
FIG. 7-2 is a timing chart showing, by way of example and not limitation, an example of the timing of processing performed by each device in this embodiment.
This figure shows an example of a process executed by the control unit 21 of the terminal 20X, a process executed by the control unit 21 of the terminal 20Y, and a process executed by the control unit 11 of the server 10, in order from the left side.

Here, unlike the display screen,
・Safety registration request account = User Y of terminal 20Y. Account Y = User of terminal 20A and terminal 20C to terminal 20F on the display screen - Safety registration request account = User X. of terminal 20X. Account of X = User B of terminal 20B on the display screen. B
The following is an example of the processing when

By way of example and not limitation, when a safety registration request request operation for the terminal 20X is performed in the terminal 20Y, first safety registration request information is transmitted to the server 10 (timing "TM910").
Then, the control unit 11 of the server 10 determines that the initial transmission setting condition (X1) is satisfied, and transmits the first safety registration request information to the terminal 20X (timing "TM920").
Upon receiving the first safety registration request information, the control unit 21 of the terminal 20X displays the first safety registration request information on the display unit 24 (timing "TM930").

Next, the control unit 11 of the server 10 executes safety confirmation registration acceptance period end processing (timing "TM940").

In the safety confirmation registration acceptance period termination process, the control unit 11 of the server 10 determines whether or not to terminate the safety confirmation process or the safety registration request process based on the input operation by the user of the server 10, by way of example and not limitation. I do. When it is determined that the safety confirmation process or the safety registration request process is to be terminated, the control unit 11 of the server 10 transmits safety information in response to receiving safety confirmation registration information, and sends safety registration request information in response to receiving safety registration request information. and stop the transmission.

In addition, in the safety confirmation registration acceptance period termination process, the control unit 11 of the server 10 may perform safety confirmation processing and safety registration based on, for example and not limitation, whether or not a set period has elapsed from the date and time of disaster occurrence in the disaster information. It may be determined whether or not to terminate the request processing. Further, by way of example and not limitation, the control unit 11 of the server 10 may determine whether or not to end the safety confirmation process or the safety registration request process based on the end date and time of safety confirmation reception in disaster information. good.

After that, when the terminal 20X receives the safety confirmation registration information based on the input operation for the first safety registration request information, by way of example and not limitation, the first safety confirmation registration information is transmitted to the server 10 (timing "TM950"). Then, the server 10 receives the first safety confirmation registration information (timing "TM960").

Note that it is not essential that the safety registration request request operation is executed on the terminal 20Y and that the terminal 20X receives the safety registration request information.

If the control unit 11 of the server 10 determines to end the safety confirmation process or the safety registration request process at the timing "TM940" and receives the safety confirmation registration information after the timing "TM940" (as an example and not a limitation, the timing "TM960"), and sends safety confirmation registration acceptance period end information indicating that acceptance of safety confirmation registration has ended to the terminal 20X of the safety registration account via the communication I/F 14 (timing "TM970").

Upon receiving the safety confirmation registration acceptance period end information from the server 10, the control unit 21 of the terminal 20X displays the received safety confirmation registration acceptance period termination information on the display unit 24 (timing "TM980").

Note that the control unit 11 of the server 10 determines to end the safety confirmation process and the safety registration request process at the timing "TM940", and if the safety registration request request information is received after the timing "TM940", the control unit 11 terminates the safety confirmation registration reception. The period end information may be sent to the terminal 20 of the safety registration request account.

Further, by way of example and not limitation, when receiving the above-mentioned safety registration request user information request information from the terminal 20X after timing "TM940", the control unit 11 of the server 10 transmits the safety confirmation registration acceptance period end information to the terminal. 20X may be transmitted.

<Effects of the seventh embodiment>
In this embodiment, the above-described first display is displayed on the display unit 24 at the terminal 20 of the safety registration request account based on the reception of the safety registration request information (not limited to, but an example of the second information). Then, if the safety confirmation registration acceptance period (not limited, but an example of acceptance of safety confirmation) has ended, the server 10, based on the input by the user of the safety confirmation registration request account on the first display, A configuration is shown in which information on the end of the safety confirmation registration acceptance period (not limited, but an example of information regarding the fact that acceptance of safety confirmation has ended) is transmitted to the terminal 20 of the user of the account requesting safety confirmation registration via the communication I/F 14. There is.
As an example of the effect of the embodiment obtained by such a configuration, when the first display regarding safety confirmation is displayed on the display section of the terminal based on the reception of the second information, and the reception of the safety confirmation has ended, Based on the input by the terminal user on the first display, information regarding the termination of acceptance of safety confirmation is sent to the terminal, thereby informing the terminal user that acceptance of safety confirmation has been terminated. I can let you know.

<Seventh modification (1)>
In the above embodiment, when it is determined to end the safety confirmation process or the safety registration request process in the safety confirmation registration acceptance period termination process, the control unit 11 of the server 10 requests safety confirmation registration information or safety registration request after that. Although an example has been exemplified in which, upon receiving the information, information on the end of the safety confirmation registration acceptance period is returned, but the present invention is not limited to this.
By way of example and not limitation, if the safety confirmation registration acceptance period for the first disaster information has ended and the second disaster information is transmitted, the control unit 11 of the server 10 may It may also be possible to accept safety confirmation registration.

FIG. 7-3 is an example of the data structure of the account management database 155B, which is an example of the account management database 155 in this modification.
The account management database 155B stores account management data as management data for each account.

Each account management data stores, by way of example and not limitation, an application ID, friend management data, and safety registration data.

The application ID and friend management data can be configured similarly to account management database 155A, by way of example and not limitation.

The safety registration data is data for storing safety-related registration associated with the account of this application ID, and includes, by way of example and not limitation, a disaster ID, safety status information, safety comment information, and safety location information. are stored in association with each other.

The disaster ID is information for identifying a disaster that has occurred or disaster information that corresponds to the disaster that has occurred. This disaster ID is preferably a unique value for each disaster (disaster information), and as an example and not a limitation, a unique value (unique value) is set and stored by the server 10 for each disaster (disaster information). Ru.

The safety status information, the safety comment information, and the safety location information are set and stored based on the safety confirmation registration information input by the terminal 20 of the safety registration account, by way of example and not limitation. Note that any element among the safety status information, safety comment information, and safety location information may be omitted.

FIG. 7-4 is a diagram showing an example of a messaging application screen displayed on the display unit 24 of the terminal 20B in this embodiment.
In the screen on the left side of Figure 7-4, the safety information indicating that the safety registration due to the earthquake that occurred on "August 4, 20XX, 9:39 a.m." (not limited, but an example of the first disaster) will be stopped is displayed from the OA account. Below registration suspension confirmation content SCT1, disaster occurrence content DCT2 indicating that an earthquake (not limited to, but an example of a second disaster) occurred at "19:23 on August 14, 20XX" from the OA account is displayed. has been done. By way of example and not limitation, when the answer button BT4b in the safety registration request content RCT8 is tapped, a display as shown in the center of FIG. 7-4 is displayed.

Specifically, although the period for accepting safety confirmation registration (safety registration period) for the first disaster has ended, it is possible to register for safety for the second disaster, and confirm whether or not to register for safety. Safety registration confirmation information RCI1 is displayed in the center of the screen in a pop-up format. When the "OK" button included in this information is tapped and the display returns to the home screen, a display like the one on the right side of Figure 7-4 will appear.

This home screen displays information regarding the occurrence of the second disaster.
Further, a safety registration area R1 for performing safety registration is displayed rising from the bottom of the home screen. The configuration example of this safety registration area R1 is as described above, so the explanation will be omitted.

FIG. 7-5 is a timing chart showing, by way of example and not limitation, an example of the timing of processing executed by each device in this embodiment.
First, by way of example and not limitation, the control unit 11 of the server 10 performs first disaster safety confirmation registration for starting safety confirmation processing and safety registration request processing in the first disaster based on an input operation by a user of the server 10. Execute reception processing (timing "TM1005"). In the first disaster safety confirmation registration reception process, the control unit 11 of the server 10 generates a disaster ID to be associated with the first disaster. In addition, the control unit 11 of the server 10 may transmit the first disaster information to each terminal 20 in conjunction with the first disaster safety confirmation registration reception process. Further, the first disaster information may include a disaster ID associated with the first disaster.

Note that the control unit 11 of the server 10 may execute the first disaster safety confirmation registration reception process based on disaster situation information received from a disaster information server (not shown).

Next, by way of example and not limitation, when a safety registration request request operation for the terminal 20X is performed in the terminal 20Y, first safety registration request information is transmitted to the server 10 (timing "TM1010").
Then, the control unit 11 of the server 10 determines that the initial transmission setting condition is satisfied, and transmits the first safety registration request information to the terminal 20X (timing "TM1015").
Upon receiving the first safety registration request information, the control unit 21 of the terminal 20X displays the first safety registration request information on the display unit 24 (timing "TM1020").

Next, the control unit 11 of the server 10 executes a safety confirmation registration acceptance period termination process in the first disaster (timing "TM1025").
Thereafter, the control unit 11 of the server 10 executes a second disaster safety confirmation registration reception process to start the safety confirmation process and safety registration request process in the second disaster (timing "TM1030"). In addition, the control unit 11 of the server 10 may transmit the second disaster information to each terminal 20 in conjunction with the second disaster safety confirmation registration reception process. Further, the second disaster information may include a disaster ID associated with the second disaster.

After that, when the terminal 20X receives the safety confirmation registration information based on the input operation for the first safety registration request information, by way of example and not limitation, the first safety confirmation registration information is transmitted to the server 10 (timing "TM1035"). Then, the server 10 receives the first safety confirmation registration information (timing "TM1040"). Note that the first safety confirmation registration information may include a disaster ID associated with the first disaster.

Note that it is not essential that the safety registration request request operation is executed in the terminal 20Y and that the terminal 20X receives the first safety registration request information.

The control unit 11 of the server 10 determines to end the safety confirmation processing and safety registration request processing in the first disaster at timing "TM1025", and includes the disaster ID linked to the first disaster after timing "TM1025". When safety confirmation registration information is received (timing "TM1040", as an example and not a limitation), the first disaster safety confirmation registration acceptance period end information indicating that acceptance of safety confirmation registration in the first disaster has ended is sent to the communication I/I/ It is sent to the terminal 20X of the safety registration account by F14 (timing "TM1045").

In addition, by way of example and not limitation, when the control unit 11 of the server 10 transmits information on the end of the first disaster safety confirmation registration reception period, if the second disaster safety confirmation registration reception process is being executed, Second disaster safety confirmation registration reception start information indicating that confirmation registration is being accepted is transmitted to the terminal 20X of the safety registration account (timing "TM1050"). Note that the second disaster safety confirmation registration acceptance start information may include a disaster ID associated with the second disaster.

Upon receiving the first disaster safety confirmation registration acceptance period end information from the server 10, the control unit 21 of the terminal 20X causes the display unit 24 to display the received first disaster safety confirmation registration acceptance period end information (timing "TM1055"). .
Further, upon receiving the second disaster safety confirmation registration reception start information from the server 10, the control unit 21 of the terminal 20X displays the received second disaster safety confirmation registration reception start information on the display unit 24 (TM1050).

Here, the second disaster safety confirmation registration reception start information may be information indicating that a new safety confirmation registration different from the first disaster has started, or information about safety confirmation registration for the second disaster that includes the second disaster information. Information regarding acceptance display may also be used.

The control unit 11 of the server 10 determines to end the safety confirmation processing and safety registration request processing in the first disaster at timing "TM1025", and after timing "TM1025", the safety registration associated with the first disaster is completed. When the request request information is received, information on the end of the first disaster safety confirmation registration acceptance period may be sent to the terminal 20 of the safety registration request account.

Furthermore, when the control unit 11 of the server 10 receives the safety registration request information after the timing "TM1030", the control unit 11 transmits the safety registration request request for the second disaster to the terminal 20 of the safety registration request account. good.

In addition, when the control unit 11 of the server 10 determines to end the safety confirmation process and the safety registration request process in the first disaster in the safety confirmation registration acceptance period termination process in the first disaster, the control unit 11 receives the safety confirmation registration information from the terminal 20. The information on the end of the first disaster safety confirmation registration acceptance period may be transmitted to each terminal 20 without receiving the information.
In this case, upon receiving the end information of the first disaster safety confirmation registration acceptance period, the control unit 21 of the terminal 20X may control the terminal 20X not to accept the safety confirmation registration for the first disaster.

Note that if the first safety confirmation registration information does not include a disaster ID, the control unit 11 of the server 10 determines that the first safety confirmation registration information is received after timing "TM1025" and before timing "TM1030". In this case, information on the end of the first disaster safety confirmation registration acceptance period may be sent to the terminal 20X of the safety registration account.
In addition, if the first safety confirmation registration information does not include a disaster ID and the first safety confirmation registration information is received at timing "TM1025" or later and timing "TM1030" or later, the control unit 11 of the server 10 Based on the received first safety confirmation registration information, safety information for the second disaster may be generated and transmitted to each terminal 20.

Note that, as an example and not a limitation, if the control unit 11 of the server 10 receives the safety registration request user information request information in the first disaster from the terminal 20X after the timing "TM1030", the control unit 11 accepts the first disaster safety confirmation registration. The period end information and the second disaster safety confirmation registration reception start information may be transmitted to the terminal 20X.

In this modification, a safety registration request is made on the terminal 20 of the safety registration account based on safety registration request request information (not a limitation, but an example of the first disaster) for one disaster (not a limitation, but an example of the first disaster). Based on the reception of the information (not a limitation, but an example of the second information), the first display described above is displayed on the display unit 24 for that one disaster. Then, the server 10 determines whether the registration acceptance period for safety confirmation for one disaster has ended (not a limitation, but an example of accepting safety confirmation for the first disaster), and for another disaster (not a limitation, but an example of accepting safety confirmation for the second disaster). If the safety confirmation registration acceptance period (not limited, but an example of acceptance of safety confirmation for the second disaster) has started, the first message will be displayed based on the input by the user of the safety confirmation registration requesting account for the first display. Information on the end of the registration period for disaster safety confirmation (not limited, but an example of information regarding the end of acceptance of safety confirmation for the first disaster) and information on the start of registration for second disaster safety confirmation (not limited, but for the second disaster) The configuration is shown in which an example of information regarding the start of acceptance of disaster safety confirmation) is transmitted to the terminal 20 of the user of the safety registration request account via the communication I/F 14.
As an example of the effect of the embodiment obtained by such a configuration, a first display related to safety confirmation is displayed on the display section of the terminal based on the reception of second information based on the first information of the first disaster, When acceptance of safety confirmation for disaster has ended and acceptance of safety confirmation for second disaster has started, acceptance of safety confirmation for first disaster will be completed based on the input by the terminal user on the first display. By sending information on what is being done and information on the fact that acceptance of safety confirmation for the second disaster has started to the terminal, it is possible to confirm that acceptance of safety confirmation for the first disaster has ended and information on the start of acceptance of safety confirmation for the second disaster. It is possible to notify the terminal user that acceptance of safety confirmation for two disasters has started.

Further, in this modification, the above-described first display is displayed on the display unit 24 based on the reception of the safety registration request information (not a limitation, but an example of the second information) at the terminal 20 of the safety registration request account. . Then, if the safety confirmation registration acceptance period (not limited, but an example of acceptance of safety confirmation) has ended, the server 10 receives information through the communication I/F 14 indicating that it does not accept input for the first display. A configuration is shown in which the information is sent to the terminal 20 of the safety registration request account.
As an example of the effect of the embodiment obtained by such a configuration, when the first display regarding safety confirmation is displayed on the display section of the terminal based on the reception of the second information, and the reception of the safety confirmation has ended, By transmitting information for disabling input to the first display to the terminal, it is possible to prevent input to the first display from being accepted.

<Seventh modification (2)>
In the above embodiment, the user of the terminal 20X could not know whether the safety confirmation registration acceptance period had ended before sending the safety confirmation registration information, but the present invention is not limited to this. By way of example and not limitation, the safety registration request information may include information regarding a safety registration period (period in which safety registration is possible) and a safety registration deadline (terminus of safety registration).

Note that these pieces of information may be information regarding the display period for displaying the first display described above on the display unit 24 (information regarding the display deadline). Further, information regarding an input period (information regarding an input deadline) during which input for responding to a safety confirmation (safety registration) can be made from the first display described above may also be provided.

The left side of FIG. 7-6 is a diagram showing an example of a messaging application screen displayed on the display unit 24 of the terminal 20B in this modification.
On this screen, in the safety registration request content RCT9 in the talk area, an answer button BT4c is provided that includes information on the remaining time until the answer deadline, as information regarding the answer period during which the answer to confirm the safety can be made.

In this example, safety registration is to be stopped at "9:41". Then, the remaining time until that time is displayed. If ``9:41'' arrives without a response to confirm whether the person is safe or not, a message similar to the one on the right side of Figure 7-6 will be displayed.

In this example, below the safety registration request content RCT9, the safety registration suspension confirmation content SCT1 indicating that the safety registration due to the earthquake that occurred on "August 4, 20XX, 9:39 am" from the OA account will be suspended is displayed. has been done. In addition, the display of information regarding the response period in the response button BT4c of the safety registration request content RCT9 is erased, and the response button BT4c is grayed out, and even if you tap the response button BT4c, you will not be able to respond to your safety status. It is now impossible to do so.

If the safety registration period or safety registration deadline included in the safety registration request information has passed, the control unit 21 of the terminal 20X may, by way of example and not limitation, input the safety confirmation registration information based on the input to the safety registration request information. You can choose not to accept it.

In this modification, the safety registration request information (not limited, but an example of second information) includes information regarding the safety registration period, the safety registration deadline, and the like. Then, in the terminal 20 of the safety registration request account, the above-mentioned first display is displayed on the display unit 24 based on the reception of this safety registration request information (not limited to, but an example of the second information). There is.
As an example of the effect of the embodiment obtained by such a configuration, in the terminal, the first display displays information regarding the expiration date displayed on the display section of the terminal, or information regarding the expiration date that can be input to the first display. Based on the reception of the second information including the second information, a first display related to safety confirmation can be displayed so that the user of the terminal can confirm the first display.

<Seventh modification (3)>
In the above embodiment, the server 10 determines whether to accept safety confirmation registration for one disaster, but the present invention is not limited to this. As an example and not a limitation, each terminal 20 may be able to determine whether or not to accept a safety confirmation registration or a safety registration request request.

In this case, by way of example and not limitation, the control unit 11 of the server 10 transmits the disaster information to each terminal 20, including information regarding the acceptance deadline for safety confirmation registration for the disaster. Then, the control unit 21 of each terminal 20 determines whether to accept the safety confirmation registration information or the safety registration request request at the time of the safety confirmation registration operation or the safety registration request request operation, based on the received information regarding the acceptance deadline for the safety confirmation registration. It is possible to determine whether
As an example and not a limitation, the control unit 21 of each terminal 20 may not accept the transmission of the safety confirmation registration information or the safety registration request request if the acceptance deadline has passed.

<Seventh modification (4)>
Even if the safety registration period or the safety registration deadline has passed, registered safety information may be displayed on the terminal 20 of the safety reference account, or may not be displayed.

<Eighth Example>
The eighth embodiment is an embodiment regarding blocking of members in a safety confirmation service or friends in a messaging application.

Hereinafter, a user account to be blocked will be referred to as a "block target account," and a user account that blocks content sent from the blocked account will be referred to as a "block execution account."

The contents described in the eighth embodiment can be applied to any of the other embodiments and other modifications.
In addition, the same reference numerals are given to the same constituent elements as those already mentioned, and the explanation thereof will be omitted.

<Display screen>
FIG. 8-1 is a diagram showing an example of a messaging application screen displayed on the display unit 24 of the terminal 20 in this embodiment.
The left side of FIG. 8-1 is the home screen of the messaging application displayed on the display unit 24 of the terminal 20B. When the danger button DBT is tapped in the safety registration area R1, the safety message "I'm injured" and the current location are displayed. A state is shown in which "Tsukuba City" has been input and the registration button BT3 has been tapped.

The center of FIG. 8-1 is the talk list screen of the messaging application displayed on the display unit 24 of the terminal 20A in this case. User A. A is user B. User B. on the talk list who is not blocked by B. In the item B, user B.B on which the second danger icon DIC2 is superimposed. In addition to the icon image and user name of B, the above-mentioned composite safety information "Tsukuba/I'm injured" is displayed.

On the other hand, the right side of FIG. 8-1 is the talk list screen of the messaging application displayed on the display unit 24 of the terminal 20G in this case. User G. G is user B. Unlike the screen of the terminal 20A in the center of FIG. 8-1, user B.B on the talk list is blocked by user B. In the item B, user B.B on which the second danger icon DIC2 is superimposed. Only the icon image and user name of B are displayed. In other words, the above-mentioned composite safety information "Tsukuba/I'm injured" is not displayed, and although it is known that the patient is in danger, the safety message and whereabouts are not displayed.

Note that instead of displaying both the safety location information and the safety comment information on the terminal 20 of the blocked user, one of the information may be displayed.

<Processing>
FIG. 8-2 is a timing chart showing, by way of example and not limitation, an example of the timing of processing performed by each device in this embodiment.
This figure shows an example of a process executed by the control unit 21 of the terminal 20X, a process executed by the control unit 21 of the terminal 20Y, and a process executed by the control unit 11 of the server 10, in order from the left side.

Here, unlike the display screen,
- Blocked account = user Y of terminal 20Y. Account Y = User A. of terminal 20A on the display screen. A
・Block execution account = User X of terminal 20X. Account of X = User B of terminal 20B on the display screen. B
The following is an example of the processing when

As an example and not a limitation, the control unit 21 of the terminal 20X sends block request information for blocking content from an account to be blocked (in this case, the account of the terminal 20Y) to the server via the communication I/F 22 based on a user operation. 10 (timing "TM1105"). The block request information may include the application ID of the terminal 20Y.

Upon receiving the block request information from the terminal 20X through the communication I/F 14, the control unit 11 of the server 10 executes block processing (timing "TM1110"). After executing the block process, the control unit 11 of the server 10 transmits message information based on the message sending request information to the terminal 20X when receiving message sending request information from the terminal 20Y to the terminal 20X in chat processing, by way of example and not limitation. do not send.

Next, by way of example and not limitation, when a safety registration request request operation for the terminal 20X is performed in the terminal 20Y, first safety registration request information is transmitted to the server 10 (timing "TM1115").
Then, the control unit 11 of the server 10 determines that the initial transmission setting conditions are satisfied, and transmits the first safety registration request information to the terminal 20X (timing "TM1120").
Upon receiving the first safety registration request information, the control unit 21 of the terminal 20X displays the first safety registration request information on the display unit 24 (timing "TM1125").

Note that when receiving safety registration request information from the terminal 20Y of the blocked account to the terminal 20X of the blocking account, the control unit 11 of the server 10 prevents the safety registration request information from being sent to the terminal 20X of the blocking account. You can also do this.

By way of example and not limitation, the control unit 21 of the terminal 20X receives safety status information based on an input operation on the second display in the first safety registration request information, and displays the received first safety status information. The status information is transmitted to the server 10 via the communication I/F 22 (timing "TM1130").
Further, by way of example and not limitation, the control unit 21 of the terminal 20X receives safety comment information based on an input operation on the third display in the first safety registration request information, and receives safety comment information from the received first safety comment information. safety comment information is transmitted to the server 10 via the communication I/F 22 (timing "TM1135").

Note that, as illustrated in the screen diagram, the second display and the third display are not limited to being included in the same display screen. As an example and not a limitation, the control unit 21 of the terminal 20X may display a third display on the display unit 24 when an input operation is performed on the second display, and may accept an input operation on the third display.

The control unit 11 of the server 10 receives first safety status information and first safety comment information from the terminal 20X. Then, the control unit 11 of the server 10 transmits the first safety information including only the first safety status information to the terminal 20Y of the blocked account (timing "TM1140").
Furthermore, the control unit 11 of the server 10 transmits first safety information including first safety status information and first safety comment information to each terminal 20 other than the blocked account (timing "TM1150"). .

Upon receiving the first safety information including only the first safety status information from the server 10, the control unit 21 of the terminal 20Y causes the display unit 24 to display the received first safety information (timing "TM1145").

Note that the combinations of safety confirmation registration information accepted in the second display and the third display are not limited to the above combinations.
Here, the safety registration information input for the second display will be referred to as "first safety information", and the safety registration information input for the third display will be referred to as "second safety information". When the first safety information and the second safety information are input to the terminal 20 of the blocking account, the safety information including only the first safety information is transmitted to the terminal 20 of the blocked account. Further, safety information including first safety information and second safety information is transmitted to each terminal 20 other than the blocked account.

Note that safety information including first safety information and second safety information may be transmitted to the terminal 20 of the account to be blocked.

FIG. 8-3 is a table showing combinations of first safety information and second safety information.
Here, as an example and not a limitation, the components of the safety registration information are illustrated as safety status information, safety comment information, and safety location information, but when other components are added, the same applies to the first safety information and the first safety information. 2. Safety information can be determined.

By way of example and not limitation, the example of FIG. 8-1 corresponds to the case of pattern (C).
In patterns (A) to (C), safety status information is displayed on the terminal 20 of the blocked account, but safety comment information and safety location information are not displayed. However, when entering safety confirmation registration, inputting safety comment information and safety location information takes more time than inputting safety status information, so users with safety registration accounts only input safety status information, and input safety comment information and safety location information. It is highly conceivable to omit inputting location information. Therefore, if only the safety status information is displayed on the terminal 20 of the blocked account, it is possible to distinguish whether the user of the blocked account is not displaying safety comment information or safety location information, or whether they have not been entered in the first place. Can not do it. Therefore, it is difficult for the user of the blocked account to recognize that he or she has been blocked by the user of the blocking account.

In addition, when receiving the safety confirmation registration information from the terminal 20X of the blocking account, the control unit 11 of the server 10 prevents the safety confirmation information based on the received safety confirmation registration information from being sent to the terminal 20Y of the blocked account. Good too.

<Effects of the eighth embodiment>
In this embodiment, the above-mentioned first display is displayed on the display unit 24 based on the reception of safety registration request information (not a limitation, but an example of second information) in the terminal 20 of the safety registration request account. Based on the input for the first display, a second display and a third display different from the second display are displayed on the display unit 24. Based on the input to the second display displayed on the terminal 20 of the account requesting safety registration, the server 10 displays one piece of safety information (not limited to the first An example of safety information) is received by the communication I/F 14, and based on the input on the third display, another safety information (not limited to the second safety information) input by the user of the terminal 20 of the account requesting safety registration is received. example) is received by the communication I/F 14. The server 10 then manages a user associated with the user of the safety registration requesting account, such as being registered as a friend by the user of the safety registration requesting account (an example of a user associated with the user of the terminal, not limited to). A configuration is shown in which one safety information (first safety information) is transmitted to the terminal 20, and another safety information (second safety information) is transmitted to the terminal 20 of the user set by the user of the safety registration request account. ing.
As an example of the effect of the embodiment obtained by such a configuration, the first display related to safety confirmation is displayed on the terminal based on the reception of the second information, and the second display and the second display are displayed based on the input to the first display. , a third display different from the second display are displayed. Then, based on the input on the second display, the first safety information input by the terminal user is received from the terminal, and the second safety information input by the terminal user is received from the terminal based on the input on the third display. You can receive safety information. Further, the first safety information can be transmitted to the user associated with the terminal user to inform the user of the terminal's safety. Further, the second safety information can be sent to the user set by the user of the terminal to notify the user of the terminal's safety.

In addition, in this case, the user set by the user of the account requesting safety registration is one of the users associated with the user of the account requesting safety registration, such as those who are registered as friends by the user of the account requesting safety registration. It is possible to include users other than the users blocked by the user of the safety registration requesting account.
As an example of the effect of the embodiment obtained by such a configuration, the users set by the user of the terminal include users other than the users who have been blocked by the user of the terminal among the users associated with the user of the terminal. By making it possible to send the second safety information to users other than the users blocked by the user of the terminal.

<Eighth modification (1)>
In the above embodiment, the safety information including only the first safety information is sent to the terminal 20 of the blocked account, and the first safety information and the second safety information are sent to each terminal 20 other than the blocked account. Although it was decided that safety information including safety information will be transmitted, it is not limited to this. As an example and not a limitation, safety information including first safety information and second safety information is transmitted to each terminal 20, but only the first safety information is displayed on the terminal 20 of the blocked account. You can also do this.

In this case, by way of example and not limitation, upon receiving the block request information from the terminal 20X of the block execution account, the control unit 11 of the server 10 sends the block execution account information (as an example and not limitation) to the terminal 20Y of the block target account. , application ID) is transmitted.
As an example and not a limitation, the control unit 21 of the terminal 20Y of the account to be blocked sets the blocking execution account as a safety registration account after receiving the safety display block request information, and stores safety information including the first safety information and the second safety information. When receiving, only the first safety information is displayed on the display unit 24.

<Ninth Example>
The ninth embodiment is an example in which the safety confirmation registration status of members in a safety confirmation service or friends in a messaging application can be easily viewed.

The content described in the ninth embodiment is applicable to any of the other embodiments and other modifications.
In addition, the same reference numerals are given to the same constituent elements as those already mentioned, and the explanation thereof will be omitted.

<Display screen>
FIG. 9-1 is a diagram showing an example of a messaging application screen displayed on the display unit 24 of the terminal 20B in this embodiment.
The left side of FIG. 9-1 is a chat screen with the OA account of the above-mentioned messaging application, and in this example, a state in which the safety registration request content RCT1 from the OA is tapped is shown. In this case, the home screen shown on the right side of FIG. 9-1 is displayed.

This home screen is the home screen of the messaging application, and user A. The icon and user name corresponding to A, the user D. The icon and user name corresponding to D, the user F. Icon and user name corresponding to F, user G. An icon, user name, etc. corresponding to G are displayed. Further, each user's icon is displayed in association with the aforementioned first safety icon, first danger icon, and first unknown icon as icons indicating safety information registered by that user. In other words, a list screen of safety confirmation registration status is displayed.

Furthermore, in this example, user B. Based on the fact that B has not yet registered his/her safety, the safety registration button BT1 is highlighted (by way of example and not limitation, it is displayed blinking).

Note that instead of transitioning to the friend list screen as described above, the screen may be transitioned to a talk list screen, or it may be transitioned to a screen displaying a list of safety confirmation registration status.

<Ninth modification (1)>
In the above embodiment, the screen transitions to a list screen of safety confirmation registration status based on the user's operation on safety registration request information, but the present invention is not limited to this. By way of example and not limitation, a transition to the safety confirmation registration screen may be made based on a user operation in response to a push notification from a safety confirmation application or a messaging application.

・Display safety registration request information in the smart chat area (tap to go to safety confirmation registration screen)
・Transition from safety registration request information to safety confirmation registration screen with app push

FIG. 9-2 is a diagram showing an example of a screen displayed on the display unit 24 of the terminal 20B in this modification.
The left side of Figure 9-2 is the talk list screen of the messaging application displayed on the display unit 24 of the terminal 20B. At the bottom right inside the information display area, user B. Since B has not yet registered his safety, the safety registration button BT1 is displayed.
Also, below that, user B. A list of icons and user names of users who have made a safety registration request to B is displayed.

If a certain period of time passes without any operation on the terminal 20B, a lock screen as shown in the center of FIG. 9-2 is displayed. In this example, a push notification PN7 of safety registration request information sent from a messaging application is displayed as an app push on the lock screen. When this push notification PN7 is tapped, by way of example and not limitation, the home screen of the messaging application shown on the right side of FIG. 9-2 is displayed.

On this home screen, a safety registration area R1 is displayed rising from the bottom of the screen, and is configured so that safety registration can be performed immediately.

Note that if the area on the left screen in Figure 9-2 where a list of users who have made safety registration requests is displayed (four users in this example) is tapped, the home screen on the right side of Figure 9-2 will be displayed. It may be displayed.

Also, by way of example and not limitation, the safety registration request information may be displayed at the top of any talk room screen. Then, it may be possible to transition to the safety confirmation registration screen based on a user operation on the safety registration request information displayed at the top.

<Other Examples>
<Other Examples (1)>
In the above embodiment, the safety confirmation registration information inputted by the safety registration account is used to send safety information to the user of the safety confirmation application or the messaging application, but the present invention is not limited thereto. As an example and not a limitation, the control unit 11 of the server 10 may aggregate the safety confirmation registration information received from each terminal 20, and use the aggregate result as big data for relief activities.

As an example and not a limitation, the control unit 11 of the server 10 aggregates the safety status information and safety location information received from each terminal 20, and determines the bias in areas where the safety status information is input as "dangerous." Then, the control unit 11 of the server 10 calculates rescue target area information, which is positional information regarding areas where "danger" is frequently input. The control unit 11 of the server 10 may cause the display unit 13 to display the calculated rescue target area information.

Note that the control unit 11 of the server 10 may transmit the calculated rescue target area information to a disaster response headquarters server (not shown) via the communication I/F 14.

<Other Examples (2)>
In the embodiment described above, an example was exemplified in which safety registration request information is transmitted to prompt the terminal 20 of the safety registration request account to input and transmit safety confirmation registration information, but the present invention is not limited to this. More generally, the control unit 11 of the server 10 may transmit request information for prompting input and transmission of arbitrary information.

By way of example and not limitation, an example of a request (hereinafter referred to as a "request") requesting repayment of a debt will be exemplified as request information.
Further, hereinafter, an account of a user who is forced to repay a debt will be referred to as a "desired request account", and an account of a user who requests the requested requested account to repay a debt will be referred to as a "request request account". Here, the request request account is a plurality of accounts, and will be referred to as a "first request request account" and a "second request request account" by way of example and not limitation.

By way of example and not limitation, the terminal 20 of the first request requesting account transmits first request request information to the server 10 for conveying the request to the requested requesting account, based on a user operation.
When the control unit 11 of the server 10 receives the first request information from the terminal 20 of the first request account, it determines whether a setting condition (composite setting condition) is satisfied. When determining that the setting condition (composite setting condition) is satisfied, the control unit 11 of the server 10 generates first request information (in this example, prompting for debt repayment) based on the first request request information. information) is sent to the terminal 20 of the requesting account.
The control unit 21 of the terminal 20 of the requested requested account causes the display unit 24 to display the received first request information.

Then, by way of example and not limitation, the terminal 20 of the second request requesting account transmits second request request information to the server 10 for conveying the request to the requested requesting account, based on the user's operation.
When the control unit 11 of the server 10 receives the second request information from the terminal 20 of the second request account, it determines whether the setting condition (composite setting condition) is satisfied. Then, when determining that the setting condition (composite setting condition) is satisfied, the control unit 11 of the server 10 transmits second request information based on the second request request information to the terminal 20 of the requested request account. do. The control unit 21 of the terminal 20 of the requested requested account causes the display unit 24 to display the received second request information.
When determining that the setting condition (composite setting condition) is not satisfied, the control unit 11 of the server 10 does not transmit the second request information based on the second request request information to the terminal 20 of the requested request account. .

That is, when a request requesting account including a plurality of accounts notifies a desired requesting account of an arbitrary request, the following correspondence relationship can be applied by way of example and not limitation.
・"Safety registration request request information" = "Request request information"
・"Safety registration request information" = "Request information"
・"Safety registration request account" = "Request request account"
・"Safety registration request account" = "Request request account"

In this case, the presence or absence of request information transmission based on the request request information at any timing can be controlled in the same manner as the control based on the composite setting condition of the fifth embodiment, by way of example and not limitation. That is, taking the above embodiment into consideration, when receiving safety registration request request information for one requested account for the first time, the server 10 transmits the request information to the terminal 20 of the requested requested account. Then, when the server 10 subsequently receives safety registration request request information for the requested requested account, it is possible to implement control such that the requested information is not sent again to the terminal 20 of the requested requested account. Furthermore, when the server 10 receives the safety registration request request information for the requested requested account, it is also possible to perform control such that if a predetermined condition is met, the requested information is sent again to the terminal 20 of the requested requested account as a reminder. .

Note that the terminal 20 of the request requesting account may transmit to the server 10 a request for transmission of any content (referred to as "content transmission request information") to the terminal 20 of the requesting account. When the control unit 11 of the server 10 receives the content transmission request information, it controls whether or not to transmit the content information based on the content transmission request information to the terminal 20 of the request request account based on the composite setting condition. You can also do this.

In this embodiment, the server 10 communicating with the terminal 20 of the requested account (not limited to, but an example of a terminal) sends information (not limited to, but not limited to) regarding a request for content transmission to the user of the terminal 20 of the requested requested account. An example of first information regarding a request for content transmission) is received from the terminal 20 of one request requesting account (an example of the first terminal, not limited to). Then, the server 10 transmits information regarding the content to the terminal 20 of the requesting account via the communication I/F 14 based on the received information regarding the request to transmit the content.
In addition, the server 10 transmits information regarding a request for content transmission to the user of the terminal 20 of the requested request account (an example of first information regarding a request to transmit content) to the terminal 20 of the other request requesting account. (an example, but not a limitation) of the second terminal. The server 10 is configured to transmit information regarding the content to the terminal 20 of the requested account through the communication I/F 14 based on the received information regarding the content transmission request and the set conditions. .
As an example of the effect of the embodiment obtained by such a configuration, first information regarding a request to transmit content to the user of the terminal is received from the first terminal, and then second information regarding the content is transmitted based on the first information. By sending a message to a terminal, by way of example and not limitation, a user of the terminal may be prompted to send content. Further, after receiving first information regarding a request to send content to the user of the terminal from the second terminal, the second information regarding the content is transmitted to the terminal based on the first information and the set conditions. By way of example and not limitation, a user of a terminal may be prompted to submit content.

<Others>
The content realized by the messaging application (messaging service) explained in the above embodiments and modified examples can basically be similarly applied to the safety confirmation application (safety confirmation service) explained in the fifth embodiment. .

1 Communication system 10 Server 20 Terminal 30 Network

Claims (16)

A program executed by a terminal that performs processing related to chatting with a user of a first terminal,
receiving, by a communication unit of the terminal, first information regarding the safety of the user of the first terminal based on an input to the first terminal by the user of the first terminal;
displaying on a display section of the terminal a chat room that includes a user of the first terminal and a user of the terminal and that includes a first area that displays content transmitted and received between the first terminal and the terminal; ,
A first image indicating the user of the first terminal set by the user of the first terminal and the first information associated with the first image are stored in the first area of the chat room. The control unit of the terminal performs control to display the image in a different second area. The program according to claim 1,
When the first information regarding the safety of the user of the first terminal is changed to second information by the user of the first terminal, receiving the second information by the communication unit is performed by the terminal. . The program according to claim 2,
The second information is changed from the first information and displayed in the second area of the chat room. 4. The program according to claim 3,
When the chat room is displayed on the display unit after the first information is received by the communication unit, receiving the second information by the communication unit is executed by the terminal. The program according to claim 2 or 3,
When the information of the user of the first terminal is displayed on the display unit, the terminal receives the second information by the communication unit. 6. The program according to claim 5,
The information of the user of the first terminal includes information regarding the status of the user of the first terminal, including the first information related to the safety of the user of the first terminal. The program according to claim 2 or 3,
The second information is transmitted based on the relationship between the user of the first terminal and the user of the terminal. The program according to any one of claims 1 to 7,
Based on the first information, the terminal controls the control unit to change a display mode of information regarding the chat room. 9. The program according to claim 8,
The terminal controls the control unit to change a display mode of information regarding the chat room based on information regarding the safety of the user included in the chat room, including the first information. The program according to any one of claims 1 to 9,
The terminal performs control by the control unit to display the first information in a list of users associated with the user of the terminal. The program according to any one of claims 1 to 10,
The terminal transmits third information regarding the safety of the user of the terminal by the communication unit based on the input to the terminal by the user of the terminal. 12. The program according to claim 11,
Displaying information regarding the automatic chat response on the display unit based on the transmission of the third information;
The terminal causes the control unit to perform a process related to the automatic chat response based on input by a user of the terminal to information regarding the automatic response. The program according to any one of claims 1 to 12,
Displaying information regarding the automatic chat response on the display unit based on the state of the terminal;
The terminal causes the control unit to perform a process related to the automatic chat response based on input by a user of the terminal to information regarding the automatic response. The program according to any one of claims 1 to 13,
Receiving the first information by the communication unit via a server is performed by the terminal. An information processing method for a terminal that performs processing related to a chat with a user of a first terminal, the method comprising:
receiving, by a communication unit of the terminal, first information regarding the safety of the user of the first terminal based on an input to the first terminal by the user of the first terminal;
displaying on a display section of the terminal a chat room that includes a user of the first terminal and a user of the terminal and that includes a first area that displays content transmitted and received between the first terminal and the terminal; ,
A first image indicating the user of the first terminal set by the user of the first terminal and the first information associated with the first image are stored in the first area of the chat room. and controlling display in a different second area by a control unit of the terminal. A terminal that performs processing related to chatting with a user of the first terminal,
a communication unit that receives first information regarding the safety of the user of the first terminal based on an input to the first terminal by the user of the first terminal;
a display unit that displays a chat room that includes a user of the first terminal and a user of the terminal, and that includes a first area that displays content transmitted and received between the first terminal and the terminal;
A first image indicating the user of the first terminal set by the user of the first terminal and the first information associated with the first image are stored in the first area of the chat room. and a control unit that performs control of displaying in a different second area.

Images