JP2023066275A - Program, information processing method, and terminal - Google Patents

Abstract

To increase the convenience and the like of safety confirmation.SOLUTION: A program executed by a terminal that performs processing related to chatting with a user of a first terminal causes the terminal to perform: receiving, by a communication unit of the terminal, first information about 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 displaying, on a display unit of the terminal, the first information associated with chat information related to the user of the first terminal.SELECTED DRAWING: Figure 1-1

Description

The present disclosure relates to programs, information processing methods, terminals, servers, and the like.

2. Description of the Related Art There is a technique for issuing an alarm using a mobile terminal when a disaster occurs (for example, Patent Literature 1).

JP 2016-151799 A

According to a first aspect of the present invention, a program executed by a terminal that performs processing related to chatting with a user of a first terminal, based on an input to the first terminal by a user of the first terminal, receiving, by the communication unit of the terminal, first information regarding the safety of the user of the first terminal; and displaying, on the display unit of the terminal, the first information associated with chat information related to the user of the first terminal executed.
According to a second aspect of the present invention, an information processing method for a terminal that performs processing related to chatting with a user of a first terminal, based on an input to the first terminal by a user of the first terminal, Receiving first information about the user's safety by a communication unit of the terminal, and displaying the 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, a terminal that performs processing related to a chat with a user of a first terminal is configured to provide 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 communication unit that receives 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 a first terminal comprises a processor that reads a program stored in a memory and executes processing based on the program, the processor comprising: Receiving, by the 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. and displaying the received first information on a display unit of the terminal.

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

<Compliance with legal matters>
Note that the disclosure provided herein is subject to compliance with the legal requirements of the implementing country required for the practice of this disclosure, such as confidentiality of communications.

<Embodiment>
In this specification, there are places described as "as an example, not as a limitation" for the sake of clarity, but not only the relevant places, but also the whole of the embodiments described below are not limited to the contents of that description. Please note.

An embodiment for implementing a program or the like according to the present disclosure will be described with reference to the drawings.

A system, by way of example and not limitation, may be configured with a plurality of devices.
The plurality of devices may be a combination of devices of the same type, a combination of devices of different types, or a combination of devices of the same type and devices of different types.
It should be noted that, by way of example and not limitation, a system can also be considered as a plurality of devices working together to perform some processing.

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

(1) is a system including, 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 made up of, by way of example and not limitation, the following devices, which may be a single device or a combination of multiple devices.

Specifically, the server includes, by way of example and not limitation, at least one processor (examples and not limitation include: CPU: Central Processing Unit, GPU: Graphics Processing Unit, APU: Accelerated Processing Unit, DSP: Digital Signal Processor (not limited to Instead, as an example, ASIC: Application Specific Integrated Circuit, FPGA: Field Programmable Gate Array), etc.), computer device (processor + memory), control device, arithmetic device, processing device, etc. Or a configuration with a plurality of the same type of one device (as a non-limiting example, CPU + CPU, homogeneous multi-core processor, etc.), or a configuration with a plurality of different types of any one device (as a non-limiting example, CPU + DSP, heterogeneous multi-core processor etc.), or a combination of a plurality of devices (as non-limiting examples, a processor + computer device, a processor + arithmetic device, a plurality of heterogeneous devices, etc.).
Note that the processor may be a virtual processor.

Also, in the case where some processing is executed by the server, if it is composed of a single device, the processing described in the embodiments is executed by the single device. Further, in the case of a configuration having a plurality of devices, it may be configured such that one device executes a part of the processing and the other device executes the other processing. By way of example and not limitation, when configured with a processor and an arithmetic device, the processor may be configured to perform the first process and the arithmetic device may be configured to perform the second process.
In addition, when a plurality of devices are used, each device may be arranged at a position physically separated from each other.

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

Also, the control unit of the system can be at least one of the control unit of the terminal and the control unit of the server. That is, as an example and not a limitation, any one of (1A) only the control unit of the terminal, (1B) only the control unit of the server, or (1C) both the control unit of the terminal and the control unit of the server may be used in the system. can be a control unit of

Further, the control and processing performed by the control unit of the system (hereinafter collectively referred to as "control, etc.") may be performed only by (1A) the control unit of the terminal, or (1B) the control of the server (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, part of the control performed by the control unit of the system is performed by the control unit of the terminal, and the rest of the control is performed by the control unit of the server. You may do so. In this case, the allocation (allocation) of control and the like may be equally divided, or may be allocated at different ratios instead of equally divided.

Further, in the case of the communication unit of the server, when the server is composed of a single device, the communication unit itself provided in the single device may be used. Further, when the server is configured to have a plurality of devices, the communication section of the server may be configured to include each communication section provided in each device.
By way of example and not limitation, if a server comprises a first device and a second device, the first device having a first communication portion and the second device having a second communication portion, the communication portion of the server may include: It is good also as a concept containing a 1st communication part and a 2nd communication part.

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

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

(3) can be, by way of example and not limitation, a system composed of a plurality of terminals.
The system may be, by way of example and not limitation, a system such as the following.
・A system in which terminals have server functions (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. As an example and not a limitation, this can be realized by performing communication in a P2P (peer-to-peer) system or the like using short-range wireless communication technology such as Bluetooth (registered trademark).

Note that the above is not limited to the control section, and the same applies to each functional section such as an input/output section, a communication section, a storage section, a clock section, etc., which can be components of the system.

In the following embodiments, by way of example and not by way of limitation, a system including a terminal and a server (by way of example and not by way of limitation, a client-server system) is illustrated.
It is also possible to apply the server system of (2) above as the server.

Also, instead of a system including a terminal and a server, it is possible to apply a system that does not include a server, such as the system of (3) above as an example and not as a limitation.
An embodiment in this case can be configured based on the above-described blockchain technology or the like. Specifically, as an example and not a limitation, data stored and managed in a server described in the following embodiments is saved (stored) on a blockchain. The terminal can then generate a transaction to the blockchain, and when the transaction is approved on the blockchain, the data stored on the blockchain can be updated.

It should be noted that even when the term "terminal" is used, this is not limited to the meaning of a terminal as a client device in a client server.
That is, a terminal may include the concept of a device that is not in a client server.

Also, in this specification, the expression "by communication I/F" is used as appropriate. This indicates that, as an example and not a limitation, the device transmits and receives various types of information and data via a communication I/F (via a communication unit) under the control of a control unit (processor or the like). It shall be acceptable.

In addition, regarding the terms “related” and “related” in this specification, when “B related to A” or “B related to A” is used as an example, not as a limitation, some relationship with “A” shall mean "B" having A specific example of this will be described later.

Further, in this specification, "A" and Including those in which "B" is performed at the same time (hereinafter referred to as "simultaneous") and those in which "A" and "B" are performed at different times (hereinafter referred to as "non-simultaneously"). shall be acceptable.
As an example and not as a limitation, in the case of transmitting the first information and the second information, it is possible to transmit the first information and the second information at the same timing, and to transmit the first information and the second information at the different timings. may include both the concept of what is sent with
In consideration of lag (time lag), "at the same time" may include "almost at the same time."

It should be noted that even though "A" and "B" are performed at different timings, it is only necessary to process "A" and "B" as targets, and the purpose is not necessarily the same. be omitted.
By way of example and not limitation, when it is said that the first information and the second information are transmitted as described above, it is only necessary to transmit the first information and the second information, and the first information and the second information are used for the same purpose. In addition to the case of transmitting the first information and the second information for different purposes, it may also include the case of transmitting the first information and the second information.

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"). Also, an application for realizing a chat service is called a "chat application", and an application for realizing a messaging service is called a "messaging application".
A chat application may, by way of example and not limitation, allow users to chat in a chat room. Chat applications may also, by way of example and not limitation, allow users to make phone calls (eg, voice calls, video calls, etc.).

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

Also, in the following embodiments, as an example of a messaging service, an instant messaging service: IMS (Instant Messaging Service).
An instant messaging application, by way of example and not limitation, may allow users to talk in a talk room. Also, instant messaging applications, by way of example and not limitation, may allow users to make calls (such as voice or video calls) between users.

A chat room (as a non-limiting example, a talk room) can be a UI (User Interface) or a GUI (Graphical User Interface) that allows each user to view content transmitted and received between terminals of multiple users. .

Talk rooms include one-to-one user talk rooms (hereinafter referred to as "one-to-one talk rooms"), group talk rooms including a plurality of users (hereinafter referred to as "group talk rooms"), Talk rooms with users of official accounts (hereinafter referred to as “OA talk rooms”) and the like can be included.

In terms of data management, the one-on-one chat room may be managed as a chat room for one-to-one users or one-to-one accounts, or managed as a group chat room consisting of two users or two accounts. You may

An official account is not a general user's account but a business operator's account (business user's account), and users of this official account also use a terminal similar to a general user's terminal as an example and not a limitation. , through the server, it is possible to send and receive content (messages) to and from other devices.

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

Content includes, by way of example and not limitation, text content in the form of text, image content in the form of images (including at least one of still images and moving images), sound content in the form of sound (including voice), etc. shall be included.
In addition to this, operation contents such as buttons and icons for user operation, and link contents such as link information (including URI (Uniform Resource Identifier) etc. as an example without limitation) may be included. shall be

Text may include, by way of example and not limitation, at least one of national characters represented by character codes, extended characters, machine-dependent characters, numerals, symbols, graphics and symbols.
Note that the text may not include at least one of the characters, extended characters, machine-dependent characters, numerals, symbols, graphics, and symbols described above, and may include other text.

Images can include, by way of example and not limitation, at least one of various types of image information such as icons, buttons, stamps, pictograms, banner images.

Also, 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 (large-scale disaster, etc.) occurs. An application for realizing the safety confirmation service is called a "safety confirmation application".
By way of example and not limitation, the safety confirmation application allows users to register information regarding their own safety and to refer to information regarding the safety of other users.

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

In forms (A) and (B), for example and not limitation, the safety confirmation service provider can be the same provider as the messaging service provider.
In this case, as one method, the user's account in the messaging application and the user's account in the safety confirmation application can be used as a common account.
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 (coordinated).

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

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

<First embodiment>
In the first embodiment, as an example and not a limitation, when a disaster such as a large-scale disaster occurs, one terminal 20 (hereinafter referred to as "terminal" as appropriate) is connected to another terminal 20 (hereinafter, as appropriate "second 1 Terminal”.) User (hereinafter appropriately referred to as “first user”) registered safety confirmation information (hereinafter referred to as “safety confirmation information”).

Here, the "safety confirmation information" can be broadly classified into the following three types of information as an example and not as a limitation.
(A1) Safety Status Information Class information related to the safety level that indicates the situation in which the user is placed.
In this embodiment, as an example and not a limitation, the safety status information registered by the user is classified into two classes, "safe" and "dangerous."
Safety status information is not limited to two classes. As a non-limiting example, the safety status information may include a class of "unknown" indicating that the safety is unknown and a class of "outside area" indicating that the person is outside the affected area of the disaster.

(A2) Safety comment information Content information, such as a message regarding safety, for communicating the user's safety.
In this embodiment, as an example, not a limitation, the safety comment information is text.
Note that the safety comment information may be audio, video, icons, or the like, for example, not limitation.

(A3) Safety location information Information about the location of the user who registers safety confirmation information.
In this embodiment, as an example and not a limitation, the safety location information is defined as an area defined by an address (as an example, not as a limitation, a municipality).
The safety location information may be, for example and not limitation, location coordinates defined by latitude and longitude, or areas connected by location coordinates defined by latitude and longitude. Also, the safety location information may include information about altitude.

Any combination of safety status information, safety comment information, and safety location information can be used as the safety confirmation information.
The safety confirmation information preferably includes at least safety status information or safety comment information. However, it is not limited to this.

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

Further, hereinafter, a user account that registers safety confirmation information is referred to as a "safety confirmation account", and a user account that refers to "safety information" based on the registered safety confirmation information is 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, hereinafter, as described above, a business operator that provides a messaging service using a messaging application is referred to as a “messaging service provider”.
Note that the messaging service provider can also be expressed as a provider of messaging applications or a provider of the server 10 .
It can also be expressed as a messaging service provider in the sense of a provider of messaging services.

Also, hereinafter, the name of the messaging application is appropriately referred to as "Messaging App" in the drawings and explanations.

As an example and not a limitation, the messaging application can be configured to enable one-to-one talk between accounts registered on the server 10 as friends. Also, as an example and not a limitation, a group including two or more accounts may be configured so that group talk can be conducted between the accounts included in the group.

Also, by way of example and not limitation, messaging applications may be configured to allow viewing of a list of messages sent to a user account as a talk list.

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

As an example of association between users (accounts), "friends" in the messaging service will be mainly exemplified below, but the association is not limited to this.
As a non-limiting example, in SNS, "follow" indicating other users (accounts) that you have registered because you are interested in yourself, or other users (accounts) that you have registered because you are interested in yourself Relationships such as "followers" that indicate are associated with users (accounts) can also be included.

As an example and not a limitation, in the SNS, a list of users in a "follow" relationship and a list of users in a "follower" relationship can be associated with the configuration requirement (B1).
In addition, as an example and not a limitation, in the SNS, a list of posts by users in a “following” relationship (“timeline” as an example, not a limitation) can be associated with the configuration requirement (B2).
Also, as an example and not a limitation, a post to a specific user ("direct message" as an example, not a limitation) on an SNS can be associated with the configuration requirement (B3).

The content described in the first embodiment can be applied to each of the other embodiments and each of the other modifications.
Moreover, the same code|symbol is attached|subjected about the component same as an already-appearing component, and description for the second time is abbreviate|omitted.

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

The server 10 has a function of providing a predetermined service (eg, without limitation, a messaging service, a safety confirmation service, etc.) to the terminal 20 owned by the user via the network 30 . Server 10 may also be referred to as a messaging server, a safety confirmation server, and the like, by way of example and not limitation.
In this embodiment, users of the server 10 are messaging service providers (operators) and safety confirmation service providers (operators).

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

The terminal 20 (terminal 20A, terminal 20B, terminal 20C, . . . ) may be any information processing terminal capable of realizing the functions described in each embodiment. Terminal 20 includes, by way of example and not limitation, smart phones, mobile phones (feature phones), computers (including but not limited to desktops, laptops, tablets, etc.), media computer platforms (including but not limited to cable, satellite set top boxes, digital video recorders), handheld computer devices (as non-limiting examples include PDA (personal digital assistant), email clients, etc.), wearable terminals (glass-type devices, watch-type devices, etc.), VR (Virtual Reality) Including terminals, smart speakers (devices for voice recognition), or other types of computers or communication platforms. Also, the terminal 20 may be expressed as an information processing terminal.

The configuration of terminal 20A, terminal 20B and terminal 20C may be identical, by way of example and not by way of limitation. Further, if necessary, the terminal used by the user X may be expressed as the terminal 20X, and the user information in a predetermined service associated with the user X or the terminal 20X may be expressed as the user information X. It doesn't have to be.
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, user's name, user's icon image, user's age, user's gender, user's address, user's hobbies, entered by the user or provided by a given service It may include information associated with the user, such as preferences, user identifiers, etc., and may or may not be any one or combination of these.

The network 30 serves to connect one or more terminals 20 and one or more servers 10 . That is, the network 30 means a communication network that provides a connection path so that the various devices can transmit and receive data after being connected.

One or more portions of network 30 may or may not be wired or wireless networks. 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), wide area network (WAN), wireless WAN (WWAN), metropolitan area network (MAN), part of the Internet, public switched telephone network (Public Part of 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 thereof. 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, and 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 capable of realizing the functions described in each embodiment. Server 10 includes, by way of example and not limitation, server devices, computers (including but not limited to desktops, laptops, tablets, etc.), media computer platforms (including but not limited to cable, satellite set-top boxes, digital video recorders, etc.). ), handheld computing devices (by way of example and not limitation, PDAs, email clients, etc.), or other types of computers or communication platforms. Also, 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 represented as information processing devices.

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

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

Communication I/F 22 transmits and receives various data via 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 executing communication with various devices such as the server 10 via the network 30 . Communication I/F 22 transmits various data to various devices such as server 10 according to instructions from control unit 21 . The communication I/F 22 also receives various data transmitted from various devices such as the server 10 and transmits the data to the control unit 21 . Also, the communication I/F 22 may be simply referred to as a communication section. Moreover, when the communication I/F 22 is configured by 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 unit 23, the input unit and the output unit may be integrated, the input unit and the output unit may be separated, or not.

The input unit is implemented 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, but is not limited to, hardware keys such as a touch panel, a touch display, and a keyboard, a pointing device such as a mouse, a camera (operation input via moving images), and a microphone (operation input by voice).

The output unit is implemented by any one or a combination of all types of devices capable of outputting processing results processed by the control unit 21 . The output unit includes, as non-limiting examples, a touch panel, a touch display, a speaker (audio output), a lens (as non-limiting examples, 3D (three dimensions) output, hologram output), a printer, and the like.

Although it is only an example, the input/output unit 23 includes a display unit 24 , a sound input unit 25 , a sound output unit 26 and an imaging unit 27 as an example and not a limitation.

The display unit 24 is realized by any one or a combination of all kinds of devices capable of displaying according to the display data written to the frame buffer. The display unit 24 includes a touch panel, a touch display, a monitor (as a non-limiting example, a liquid crystal display and an OELD (organic electroluminescence display)), a head mounted display (HDM), projection mapping, and a hologram. , including 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 to input sound data (including voice data; the same applies hereinafter). Sound input unit 25 includes a microphone and the like.
The sound output unit 26 is used for outputting sound data. Sound output unit 26 includes a speaker and the like.
The imaging unit 27 is used to acquire 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 be arranged to face each other with substantially the same size and shape.

The clock unit 29A is a built-in clock of the terminal 20 and outputs time information (clock information). The clock unit 29A is configured with a clock using a crystal oscillator or the like, for example and not limitation. The clock unit 29A can also be expressed as a clock unit or a time information detection unit as an example and not as a 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 necessary for the control unit 21 to calculate (measure) the position of its own terminal 20 (hereinafter referred to as “position calculation information”). Department. The position calculation information detection section 29B can also be expressed as a position calculation sensor section as an example and not as a limitation.

The position calculation information detection unit 29B includes, as a non-limiting example, 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 (inertial measurement unit (IMU (Inertial Measurement Unit))), which is a sensor or unit for calculating the position of the terminal 20 using an inertial navigation system, UWB (ultra wideband radio: Ultra Wide A UWB positioning sensor (UWB positioning unit), etc., which is a sensor or unit for calculating the position of the terminal 20 using a band).

The satellite positioning unit includes, as a non-limiting example, 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, Positioning satellite signals are acquired by performing correlation calculation processing, etc. on the digital signals output from the RF receiving circuit, and information such as satellite orbit data and time data extracted from the positioning satellite signals is used as position calculation information. It has a baseband processing circuit for output.

The inertial measurement unit has an inertial sensor that detects information necessary to calculate the position of terminal 20 by inertial navigation calculation. Examples of inertial sensors include, but are not limited to, triaxial acceleration sensors and triaxial gyro sensors. The acceleration detected by the acceleration sensor and the angular velocity detected by the gyro sensor are used as position calculation information. Output.

As a non-limiting example, the UWB positioning unit converts an ultra-wideband RF (Radio Frequency) signal including an ultra-wideband pulse signal for positioning transmitted from a positioning beacon received by an antenna (not shown) into a digital signal. It has a wideband RF receiving circuit, 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 ultra-wideband RF receiving circuit, and the like.
As an example and not a limitation, the UWB positioning unit may cause the terminal 20 to function as a positioning beacon by transmitting an ultra-wideband RF signal including a positioning ultra-wideband pulse signal from an antenna (not shown), You don't have to.

As a non-limiting example, the control unit 21 calculates the position of its own terminal 20 at regular timings or specific timings based on the position calculation information detected by the position calculation information detection unit 29B. The position of the terminal is called "terminal position", and the calculated terminal position is called "calculated terminal position". The control unit 21 may or may not associate the calculated terminal position with the date and time when the calculated terminal position was calculated and store it in the storage unit 28 as calculated terminal position history data.

The control unit 21 comprises, by way of example and not limitation, a hardware built-in data processing device comprising physically structured circuitry for carrying out the functions implemented by the code or instructions contained within the program. It is realized by Therefore, the control unit 21 may or may not be expressed as a control circuit.

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

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

The terminal 20 stores the program P in the storage unit 28 and executes the program P so that 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 implement each function executed by the control unit 21 . Also, this program P may or may not be expressed as a program module.

(2) Server HW Configuration FIG. 1-1 shows an example of the HW configuration of the server 10. As shown in FIG.
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 . Each component of the HW of server 10 is interconnected via bus B, by way of example and not limitation. It should be noted that the HW of the server 10 does not have to include all 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 remove individual components or multiple components.

The control unit 11 comprises, by way of example and not limitation, a hardware built-in data processing device comprising physically structured circuitry for carrying out the functions implemented by the code or instructions contained within the program. It 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 controller 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. Also, the storage unit 15 may or may not be expressed as a memory.

Communication I/F 14 transmits and receives various data via 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 executing communication with various devices such as the terminal 20 via the network 30 . Communication I/F 14 transmits various data to various devices such as terminal 20 according to instructions from control unit 11 . The communication I/F 14 also receives various data transmitted from various devices such as the terminal 20 and transmits the data to the control unit 11 . Also, the communication I/F 14 may be simply referred to as a communication unit. Moreover, when the communication I/F 14 is configured by 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 unit 12, the input unit and the output unit may be integrated, the input unit and the output unit may be separated, or not.

The input unit is implemented 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 realized by hardware keys typically represented by a keyboard and a pointing device such as a mouse. Note that the input unit may or may not include a touch panel, a camera (operation input via a moving image), and a microphone (operation input by voice) as examples, not limitation.

The output unit is implemented by any one or a combination of all types of devices capable of outputting processing results processed by the control unit 11 . The output unit includes, as non-limiting examples, touch panels, touch displays, speakers (sound output), lenses (three-dimension (3D) output and hologram output as non-limiting examples), printers, and the like.

Although it is only an example, the input/output unit 12 includes the display unit 13 as an example and not as a limitation.

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

The clock unit 19 is an internal clock of the server 10 and outputs time information (timekeeping information). The clock unit 19 includes, for example and not limitation, an RTC (Real Time Clock) as a hardware clock, a system clock, and the like. The clock unit 19 can also be expressed as a clock unit or a time information detection unit as an example and not as a limitation.
(3) Others The server 10 stores the program P in the storage unit 15 and executes the program P so that the control unit 11 executes processing 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 implement each function executed by the control unit 11 . This program P may or may not be expressed as a program module.
The same is true for other devices.

Each embodiment of the present disclosure will be described as being implemented by the CPU of the terminal 20 and/or the server 10 executing the program P. FIG.

Note that the control unit 21 of the terminal 20 and/or the control unit 11 of the server 10 is not only a CPU having a control circuit, but also an integrated circuit (IC (Integrated Circuit) chip, LSI (Large Scale Integration)) or the like. Each process may or may not be implemented by a logic circuit (hardware) or a dedicated circuit. Also, 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. LSIs are also 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.

In addition, the program P of each embodiment of the present disclosure (as a non-limiting example, a software program, a computer program, or a program module) may be provided in a state stored in a computer-readable storage medium, It does not have to be. The storage medium can store the program P in a "non-transitory tangible medium". Also, the program P may or may not be for realizing part of the functions of each embodiment of the present disclosure. Furthermore, the function of each embodiment of the present disclosure may or may not be a so-called difference file (difference program) that can be realized in combination with a program P already recorded on a storage medium.

Also, when referring to a program of the system (a program executed by the system), the system is as described above. The program of the system mentioned above is a program that can be executed by the entire system. This program, as an example and not a limitation, may be composed of a program for each device that constitutes the system. Programs stored in individual devices may be different. In other words, the programs do not have to be common to the individual devices that make up the system.
By way of example and not limitation, if the system consists of a terminal and a server, let the program of the system be P1. P2 and P3 are for executing system programs, and may be different programs. By way of example and not limitation, the program P2 stored in the terminal is a program that performs a first process and sends the results of the first process to the server, and the program P3 that is stored in the server is a program that receives The program may be a program that performs a second process on the result of the first process and transmits 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 without limitation, field programmable gate arrays (FPGAs) or application specific ICs (ASICs)), 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 It may include a drive (SSD), RAM drive, secure digital card or drive, any other suitable storage medium, or any suitable combination of two or more thereof. Storage media may, where appropriate, be volatile, nonvolatile, or a combination of volatile and nonvolatile. Note that the storage medium is not limited to these examples, and any device or medium that can store the program P may be used. Also, the storage medium may or may not be expressed as memory.

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

In addition, 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 wave, etc.) capable of transmitting the program. . As a non-limiting example, the server 10 and/or the terminal 20 implement the functions of the plurality of functional units shown in each embodiment by executing a program P downloaded via the Internet or the like.

Each embodiment of the present disclosure can also 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, the server 10 may or may not perform at least some or all of the processing of the functional units of the control unit 21 of the terminal 20 .
At least part or all of the processing in the server 10 may or may not be performed by the terminal 20 . In this case, the terminal 20 may or may not perform at least some or all of the processing of the functional units of the control unit 11 of the server 10 .

Unless explicitly mentioned, the configuration of determination in the embodiments of the present disclosure is not essential, and predetermined processing is performed when the determination condition is satisfied, or predetermined processing is performed when the determination condition is not satisfied. may or may not.

It should be noted that the programs of the present disclosure use script 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, and the like, for example and not limitation. implemented using

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

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 an application management processing program 151 to be executed as application management processing, account registration data 153, and an account management database 155 as an example and not limitation.

The account registration data 153 is registration data relating to the account of the application (messaging application in this embodiment), and an example of the data configuration is shown in FIG. 1-4.
The account registration data 153 stores, for 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 as an example and not as a 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 the account of the application, or the account itself.
This application ID is preferably a unique value for each account, and as an example and not a limitation, the server 10 sets and stores a unique value (unique value) for each account.
The application ID is information associated with the terminal 20 or the user of the terminal 20, and is an example of information about the terminal or information about the user of the terminal.

The other registration information includes, for example and not limitation, identification information for identifying the terminal 20, the telephone number of the terminal 20 (terminal telephone number), the e-mail address (terminal e-mail address), and the 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 by way of limitation, a terminal ID (by way of example and not by way of limitation, IMEI (International Mobile Equipment Identity)).
In addition, the identification information for identifying the user of the terminal 20 can be an application ID for general users or an application ID for official users, for example and not limitation.

A "user ID" may or may not be used instead of the application ID.
Also, if the application allows only one account to be registered for one terminal 20, as an example without limitation, "identification information for identifying the terminal 20=identification information for identifying the user of the terminal 20= Application ID".

Also, by way of example and not limitation, it may or may not be possible to assign multiple terminal IDs to one application ID. In this case, one application ID may be used as an identification (login) target, and applications may be activated simultaneously on a plurality of terminals 20, or may not be so.

It is also possible to apply a method of managing an account using information such as a terminal telephone number instead of various IDs such as an application ID.
In this case, information such as a terminal telephone number can be stored in the account registration data 153 instead of storing ID information such as an application ID in the account registration data 153 . Instead of replacing the ID information such as the application ID with the information such as the terminal telephone number, the ID information such as the application ID may be associated with the information such as the terminal telephone number on a one-to-one basis. It doesn't have to be.

In addition, in the following various embodiments, for the sake of simplicity of explanation, 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". The term may be substantially synonymous with "account terminal".

The account management database 155 is a database for managing information relating to accounts registered in the account registration data 153, and an example data configuration 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 the account managed by the account management data, and as an example, not limitation, the application ID registered in the account registration data 153 is stored.

The friend management data is data for storing the account of this application ID and the application IDs of the accounts that are friends. As a non-limiting example, when a user registers as a friend, the server manages the name of the user who registered as a friend. Application IDs are added and updated.

The safety registration data is data for storing registration regarding safety associated with the account of this application ID, and safety status information is stored as an example and not limitation.

Safety registration data for each account may be changeable based on user input such as user operations on the terminal 20, for example and not limitation.
As an initial value (default) of the safety registration data, as an example, not a limitation, information indicating that the server 10 has not received the safety confirmation information (as an example, not a limitation, ""Unknown" flag) can be preset.

Further, as 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 associated and stored. .

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

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

<Display screen>
The display screen in this embodiment illustrates an example of registering only safety status information as safety confirmation information.
In the following, as an example and not a limitation, a case where the terminal 20 is a smart phone having a vertically long display unit 24 will be illustrated.

As an example and not a limitation, a smartphone has a touch panel that functions as an input unit facing 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 the user operates an area that is part of the touch panel and faces the area where the element is displayed, A program associated with the element or a subroutine of that program is executed.

Note that the transition of the display screens described below is merely an example of the transition of the display screens for realizing the technique of the present disclosure. Regarding the transition of the display screens illustrated below, the display of a part of the display screens may be omitted, or another display screen may be added.

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

On the left side of FIGS. 1-8 is a home screen of a messaging application (an example, but not a limitation, of a chat application) with the text "Messaging App" displayed at the top center of the screen as the name of the messaging application. An icon image and a user name ("user Y.Y" in this example) of the messaging application of the user of the terminal 20Y are displayed on the right part of the top of the screen.

In addition, below it, an area indicating the current position, page, etc. within the messaging application (hereinafter collectively referred to as "in-app location display area") is configured. In this example, the home screen , the characters "home" are displayed.

Beneath the in-app location display area is a disaster information display 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 a non-limiting example, map information indicating the epicenter, the characters "disaster occurrence", the characters "20XX/08/04 09:39 announcement", and the characters "maximum seismic intensity: 5 upper" , "Hypocenter: Off Ibaraki Prefecture" and "Magnitude: 6.5") are displayed. Also, at the bottom right inside the disaster information display area, there is a safety registration button BT1 indicated by an icon containing characters of "safety registration" for performing safety registration (registration of safety confirmation information) for each account of the messaging application. is displayed.

Below the disaster information display area is a friend/group list display area that displays a list of friends and groups in the messaging application.
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 ("User Y.Y" in this example) and the account of this terminal 20 as a member. A group list for displaying a list of groups is configured to be 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 contains, by way of example and not limitation, the word "group" and the user Y. The number of groups to which Y belongs ("8" in this example) is displayed.
In the friends list below it, the characters "friends" and the user Y.Y. The number of users (accounts) Y has registered as friends ("4" in this example) is displayed.

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

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

As a non-limiting example, when the safety registration button BT1 is tapped by the user, a display such as that shown in the center of FIG. 1-8 is provided as a non-limiting example.
In this home screen, a safety registration area R1 for registering (setting) one's own safety information is superimposed on the home screen on the left side of FIG. 1-8.

In the safety registration area R1, a message (in this example, the characters "Register Safety" and the characters "Let's inform everyone about your safety") is displayed to prompt the user to register (set) safety information. ing. Below that, a safety button SBT (in this example, a button with a smile icon and the word "safe") for setting safety as safety information, and setting unsafe as safety information. (in this example, a button indicated by an icon of a non-smiling face and the letters "danger") and a registration button BT3 for setting the selected safety information are displayed.

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

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

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

It should be noted that user Y.Y. If Y has set "safety" as safety information, user Y.Y. An icon SIC1 indicating safety (in this example, a smiling face icon, hereinafter referred to as a "first safety icon" as appropriate) is superimposed on the Y icon.

By confirming <first danger icon DIC1 indicating danger> or <first safety icon SIC1 indicating safety> displayed in the item of each user in the friend list, user X.E. X can check the safety information of the users registered as friends.

The left side of FIG. 1-9 shows the same user Y.S. It is an example of the home screen in Y's terminal 20Y.
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 danger button DBT is tapped by the user and the registration button BT3 is tapped by the user, the user X.D. As an example and not a limitation, a screen as shown in the center of FIG. 1-9 is displayed on the display unit 24 of the terminal 20X of X. FIG.

On the home screen displayed on the display unit 24 of this terminal 20X, user Y.Y. Y has set "dangerous" as safety information, but unlike the example shown on the right side of FIG. An icon indicating danger is not superimposed on the Y icon.

As a non-limiting example, when the user taps the talk item at the bottom of the screen on the home screen in the center of FIG. 1-9, the display transitions to the talk list screen on the right side of FIG. 1-9 as an example and not a limitation. do.

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

Below the in-app location display area, a list of information about talk rooms to which messages have been sent to this terminal 20X is displayed. Each talk room and its corresponding talk room list item (talk list item) include the icon of the talk room (hereinafter referred to as "talk room icon"), the name of the talk room, and the name of the talk room. If it is, the number of members is associated and displayed.
Here, in the case of a one-to-one chat room, as an example and not as a limitation, the talk room icon can be the icon of the user to talk with. It can be an icon (group icon).
In addition, in the case of a one-to-one chat room, the name of the chat partner can be used as an example without limitation, and in the case of a group talk room, the name of the group can be used as an example without limitation. .

In this example, by way of example and not limitation, a talk room list entry for user Y.Y. A talk room list item corresponding to the talk room with user A.Y (hereinafter referred to as a talk room list item of "user Y.Y") and user A.Y. A's talk room list entry and user B.A. B's talk room list items and the like are displayed.

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

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

It should be noted that user Y.Y. When user Y has set "safety" as safety information, user Y.Y. In Y's talk room list item, the talk room icon is <icon indicating safety SIC2> (in this example, an icon indicating the word "safety", hereinafter referred to as a "second safety icon" as appropriate). ) is superimposed on the display.

By confirming the <icon indicating that it is dangerous> or the <icon indicating that it is safe> displayed in each talk room list item of the talk list, the user X. X can confirm the safety information of the user who sent the message to the terminal 20X.

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 "safety" and a "red" icon is displayed for "dangerous". may be displayed. Alternatively, the name of the talk room may be displayed in a different color or typeface.
It should be noted that these methods of changing the display mode can be similarly applied to the friend list and the 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 differs from the talk list screen shown on the right side of FIG. Y has set "dangerous" as safety information, but user Y.Y. In the Y talk room list item, the second danger icon DIC2 is not superimposed on the talk room icon.

By way of example and not limitation, in the talk list screen on the left side of FIGS. When the talk room list item corresponding to Y is tapped by the user, by way of example and not limitation, the center talk room screen of FIGS. 1-10 is displayed.
On this talk room screen, by way of example and not limitation, any page within the messaging application (talk room in this example) is currently displayed below the area where the name of the messaging application, etc. is displayed at the top of the screen. A talk room name display area including the name of the talk room (hereinafter referred to as "talk room name") is provided as a type of area indicating whether the talk room is connected. The talk room name display area can also be said to be an area indicating the page (talk room in this example) within the messaging application 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 user X. X is user Y.X. Characters ("YY" in this example) indicating that this is a talk room for talking with Y as a partner, and a safety information display icon IC1 for displaying the safety information of users belonging to this talk room. is displayed.
Also, under it, the user X. X and user Y.X. A talk area is configured for interactive talk with user Y.Y. Y's message is displayed on the right side of the screen with the message of user X.Y. It is configured to display X messages.

Above the talk area, by way of example and not limitation, user Y. Safety information in the chat room for notifying the safety information set by Y in the chat room (in this example, the characters "Y.Y has responded to the safety confirmation", the user's icon on the terminal, and the safety information A user status icon ICYD (icon for user Y.Y, letters "danger", icon without a smile) containing information is displayed. Hereinafter, the user status icon is appropriately referred to as "user status icon (icon of user name (icon of), safe or dangerous (character and face icon corresponding to))".

In this display screen example, the user status icon is an icon that combines the icon of the user, characters (safe/danger) corresponding to the safety status information, and an icon corresponding to the safety status information. is not limited to
By way of example and not limitation, an icon combining the user's icon with a letter (safe/danger) corresponding to the safety status information, or an icon combining the user's icon with an icon corresponding to the safety status information and so on.

As a non-limiting example, when the safety information display icon IC1 is tapped by the user on the talk room screen in the center of FIG. Safety information for each user for displaying the safety information of each user included in this talk room is displayed in a form expanded under the area.
In this example, a user-by-user safety information display area for displaying user-by-user safety information including safety information of users belonging to the talk room is configured. , user Y. on which the second danger icon DIC2 is superimposed. The user X.Y icon and the second safety icon SIC2 are displayed superimposed. An X icon is displayed.

<Processing>
FIG. 1-11 is a flow chart showing an example of the flow of processing executed by each device in this embodiment.
In this drawing, an example of processing executed by the control unit 21 of the terminal 20X, processing executed by the control unit 21 of the terminal 20Y, and processing executed by the control unit 11 of the server 10 is shown in order from the left.

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

Here, as with the display screen,
・Safety registration account=User Y. of terminal 20Y. Account of Y (an example of a user of the first terminal, not limited) Safety reference account = user X.Y of terminal 20X The following is an example of the processing for X (an example of a terminal user, not a limitation) as an account.

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 chat processing (X110, Y110, S110) as an example and not a limitation.
In the chat process, as a non-limiting example, input to the input/output unit 23 of each terminal 20 (as a non-limiting example, user input (user operation input, sound input, etc.) The same applies hereinafter), each terminal 20 The control unit 21 executes transmission/reception processing and display processing of contents in the messaging service. In addition, the control unit 11 of the server 10 performs relay processing of content transmitted from each terminal 20 as an example and not as a limitation.

Note that chat processing may be executed between arbitrary steps during processing. Also, chat processing does not have to be executed in this system.

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

Here, as an example and not a limitation, the disaster information may be configured to include any combination of the following disaster elements A to H and requesting the user to register their safety.
・Disaster element A: The occurrence of a disaster.
- Disaster element B: type of disaster (not limited to but examples include earthquakes, floods, large-scale fires, etc.).
・Disaster element C: Scale of disaster (not limited but examples include seismic intensity, magnitude, river water level, fire spread range, etc.).
・Disaster element D: Date and time when the disaster occurred.
・Disaster element E: The place where the disaster occurred.
・Disaster element F: secondary effects of disasters (not limited to but examples include power outages, water outages, operation status of transportation systems, etc.).
・Disaster element G: How to deal with a disaster (not limited to, but an example of an evacuation site, an evacuation route, etc.).
- Disaster element H: Information related to other disasters.
The disaster information may include information on the safety registration period and time limit for the disaster.

In addition, when an arbitrary disaster occurs, the control unit 11 of the server 10 controls the disaster situation information, which is information about the disaster that occurred from the disaster information providing server (not shown) (as an example without limitation, the above disaster elements A to D receive information consisting of Then, based on the disaster situation information, the control unit 11 of the server 10 determines that the scale of the disaster that has occurred is greater than or equal to a predetermined scale (for example, a maximum seismic intensity of 5 or heavy rain). In this case, the disaster information may be automatically transmitted to each terminal 20. FIG.

In addition, when an arbitrary disaster occurs, the control unit 11 of the server 10, upon receiving disaster situation information from the disaster information providing server, causes the display unit 13 to display a display screen for selecting whether or not to transmit the disaster information. You may do so. Then, the control unit 11 of the server 10 may transmit the disaster information to each terminal 20 based on the user's input on the selection display screen.

When disaster information is received from the server 10 via 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).

As an example and not a limitation, when safety confirmation information is input based on an input to the input/output unit 23 of the terminal 20Y of the safety registration account, the control unit 21 of the terminal 20Y, as an example and not a limitation, confirms the input safety information. 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 safety confirmation registration information is received from the terminal 20Y of the safety registration account via the communication I/F 14, 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 sent in the safety confirmation registration information and safety confirmation information.

Note that the control unit 11 of the server 10 may include in the safety information the 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 adds any combination of the safety status information, the safety comment information, and the safety location information in the safety confirmation information transmitted in the safety confirmation registration information to the safety information. (for example, not limitation, only safety status information when safety status information and safety location information are included in safety confirmation information) may be included.

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

Note that the control unit 11 of the server 10 may transmit the safety information to all the 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 causes the display unit 24 to display the received safety information (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 are not limited but include any combination of the following cases.
・Unconditionally displayed (push notification, etc.)
・Browsing the friend list (group list) will be displayed in association with the safety registration account ・Browsing the talk list will be displayed in association with the safety registration account ・Browsing one-on-one chat rooms between the safety reference account and the safety registration account・Displayed when browsing the group chat room of the group that includes the safety registration account

Further, in step S140, when the server 10 transmits safety information to all the terminals 20, the control unit 21 of the terminal 20 of the safety reference account, for example and not limitation, stores the friend management data stored in the storage unit 28. See Then, if the application ID of the safety registration account is included in the friend management data, the safety information may be displayed on the display unit 24 .

<Effect of the first embodiment>
The present embodiment is a process related to a chat (an example of a chat, not a limitation) with a user of a safety registration account (an example of a user of the first terminal, not a limitation) (a process related to a chat, not a limitation). example), the terminal 20 of the user of the safety reference account (not a limitation, but an example of the terminal user) who performs the (Not a limitation, but an example of the first information regarding the safety of the user of the first terminal) is received by the communication I/F 22 . Then, the terminal 20 of the user of the safety reference account displays on the display unit 24 the safety information associated with the chat information (not limited, but an example of the 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 information associated with the chat information associated with 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 user of the terminal to understand in a form associated with the chat information.

It should be noted 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 be performed by way of example, not limitation, when the first information is sent from the first terminal to the server. and based on the fact that the server has received the first information, the first information is transmitted from the server to the terminal and the terminal receives the first information, and from the first terminal to the terminal without going through the server The first information is directly transmitted and received by the terminal.

In addition, chat-related processing includes, but is not limited to, various types of processing for chatting, such as processing for transmitting and receiving information for chatting, processing for displaying content related to chatting, and chatting It can be a concept including various processing etc. for realizing.
In addition, the chat information in the messaging application is not limited, but is a concept that includes "friend list", "talk list", "talk room", etc. corresponding to (B1) to (B3) described above. be able to. The same applies to the aforementioned "follow", "follower", and the like.

Also, in this case, the terminal 20 of the user of the safety reference account can receive safety information (or safety confirmation registration information) via 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 properly received via the server.

Also, in this case, the above chat information (not limited, but an example of chat information) is a chat (not limited, but an example of chat information) in a messaging application, and a list of users associated with the user of the safety reference account (example, non-limiting 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 can be displayed on the display of the terminal to inform the user of the terminal.

Also, in this case, the above-mentioned chat information (not limited, but an example of chat 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, (an example of the user of the terminal) (not limited to, but an example of the first chat room).
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 information associated with the information about the first chat room including the user of the terminal 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 user of the terminal to understand in a form associated with the information about the first chat room including the user of the first terminal and the user of the terminal.

Also, in this case, the above chat information is the icon of the one-to-one chat room (talk partner) included in the talk list of the chat room that includes the user of the safety reference account (not limited, but an example of the list of chat rooms) Information such as images (not a limitation, but an example of information about the first chat room included in the list of chat rooms that include the terminal user), and included in the group list of the group chat room that includes the user of the safety reference account Information such as an icon image of a group talk room (group) (example, non-limiting example of information about the first chat room included in the list of chat rooms in which the user of the terminal is included) may be 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 first information associated with the information about the first chat room included in the list of chat rooms including is displayed on the display of the terminal to inform the user of the terminal.

Also, in this case, the terminal 20 of the user of the safety reference account can perform control to change the display mode of the above-described icon images, etc., by the control unit 21 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 related to the first chat room including the user of the first terminal and the user of the terminal based on the first information, the terminal It is possible to realize a display that is easy for the user to understand.

In this case, the safety information (not limited, but an example of the 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 an example of the terminal (an example of the first chat room, not limited).
As an example of the effect of the embodiment obtained by such a configuration, the user of the first terminal is displayed in an easy-to-understand manner by displaying the first information in the first chat room including the user of the first terminal and the user of the terminal. It is possible to inform the user of the terminal of the safety.

Also, in this case, the safety information (not limited, but an example of the first information) is an image ( It can be displayed in the above-mentioned talk room in association with the first image (example without limitation).
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 It is possible to make it easier for the user of the terminal to recognize that the information is related to the safety of the person.

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

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

In the group list, as group list items, icons and group names (number of members) corresponding to tennis circles, icons and group names (number of members) corresponding to seminar friends, and the like are listed.
In addition, in the friend list, user B. is displayed as an item of the friend list. icon and user name corresponding to user C.B. icon and user name corresponding to user D.C. A list of icons, user names, etc. corresponding to D is displayed.

As a non-limiting example, when the safety registration button BT1 is tapped by the user, a display such as that shown in the center of FIG. 1-12 is provided as a non-limiting example.
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.

In the safety message input area, an area for inputting a safety message (an area where the input safety message is displayed) is configured together with the characters "safety message".
Further, below that, an area for selecting a standard message for the safety message is configured. In this example, as a template for a safety message, by way of example and not limitation, the text "I was injured", the text "I was trapped", the text "I was caught in a fire", and the text "Evacuation". are prepared in advance, and each is displayed as an icon that can be selected by tapping.

Below that, a current location input area is configured for inputting the current whereabouts, which is a kind of safety location information. In the current location input area, the characters "current location", the area for inputting the current location (the area for displaying the input current location), and the current location acquisition button for acquiring the current location are displayed. It is

At the bottom of the screen, there is provided a registration button BT3 for setting the selected/inputted safety information.

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

By way of example and not limitation, in the safety registration area R1 in the center of FIG. After being tapped by user A.A, registration button BT3 is registered to user A.A. User A when tapped by 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 display of the safety registration button BT1 is erased, 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 B.B has set "dangerous" as safety information, user B.B in the friend list is displayed. A first danger icon DIC1 is superimposed on the icon corresponding to B. User C.I. Based on the fact that C.C has set "dangerous" as safety information, user C.C. A first danger icon DIC1 is superimposed on the icon corresponding to C. User D. Based on the fact that D.D has set "safety" as safety information, user D.D. A first safety icon SIC1 is 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. Unlike the talk list screen on the right side of FIG. 1-9, this talk list screen is below the in-app location display area and displays a list of information about talk rooms to 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 that a disaster has occurred on the talk list screen, is configured above the area where the user is. Then, in this example, based on the fact that an earthquake has occurred, the second disaster information (as an example, but not limited to, the characters "20XX/08/04 09:39 announcement" and the characters "maximum seismic intensity: 5 upper") Also, based on the fact that user A.A has set himself to be "safe", the user status icon ICAS (user A.A.) is displayed to indicate that fact. 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 entry for user B.D. B's talk room list items, seminar mate's talk room list items, user C.B. Talk room list entry for user E.C. E's talk room list items and the like are displayed.

In this example, the unread number "13" is displayed in association with the tennis circle talk room list item. The unread number "2" is displayed in association with the talk room list item of user B.D. The unread number "1" is displayed in association with the talk room list item of user C.B, the unread number "2" is displayed in association with the seminar fellow talk room list item, and user C.B's talk room list item is displayed. 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.I. Based on the fact that D.D has set "safety" as safety information, user D.D. A second safety icon SIC2 is superimposed on the icon corresponding to the D talk room list item. User B. Based on the fact that user B has set "dangerous" as safety information, user B.B. A second danger icon DIC2 is superimposed on the icon corresponding to the B talk room list item. User C.I. Based on the fact that C.C has set "dangerous" as safety information, user C.C. A second danger icon DIC2 is superimposed on the icon corresponding to the C talk room list item. User E. Based on the fact that user E.E has set "safety" as safety information, user E.E. A second safety icon SIC2 is superimposed on the icon corresponding to the E talk room list item.

In this example, even if one of the members belonging to the group talk room has set the safety information, the icon corresponding to the group talk room is not overlaid with the icon based on the safety information.
In this case, even if one of the members belonging to the group talk room of the tennis circle has set safety information, the icon corresponding to the talk room list item of the tennis circle will have the second safety icon SIC2 and None of the second danger icons DIC2 are superimposed. Even if one of the members belonging to the group talk room of the seminar mates has set safety information, the icons corresponding to the talk room list items of the seminar mates have the second safety icon SIC2 and the second danger icon. None of the icons DIC2 are superimposed.

In addition, on this talk list screen, under the user name corresponding to the talk room list item, safety location information entered and registered by the user in the above-mentioned current location input area and safety message input area described above are displayed. Information based on the input and registered safety comment information is displayed.
In this example, by way of example and not limitation, user B. Under the letters "B.B" corresponding to B, the user B.B. The current location "Tsukuba City" registered by user B. Composite safety information "Tsukuba/I was injured" is displayed as information combined (combined) with the safety message "I was injured" registered by B.
User C.I. C and user E.C. For E, the registered information is similarly displayed.

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

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

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

Also, the composite safety information may be displayed on the screen (home screen, etc.) on which the friend list is displayed.
Alternatively, either one of the safety location information and the safety comment information may be displayed on the screen (home screen, etc.) on which the friend list is displayed.

By way of example and not limitation, in the talk list screen on the left side of FIG. 1-13, user B. When the B talk room list item is tapped by the user, by way of example and not limitation, the talk room screen on the right side of FIGS. 1-13 is displayed. Unlike the talk room screen shown in the center of Fig. 1-10, this screen does not display safety information in the talk room in the talk area, but displays safety information by user in the safety information display area by user. there is

In this example, the talk room name display area includes, by way of example and not limitation, user A. A is user B.A. Characters (“B.B” in this example) indicating that the room is for talking with B as the other party are displayed.
Further, in the user-by-user safety information display area therebelow, as an example and not by way of limitation, user B.2 is superimposed and displayed with a second danger icon DIC2 as user-by-user safety information. User A.B superimposed on the second safety icon SIC2. An icon of A is displayed.

Also, user B. The text content transmitted from B is displayed on the left side of the talk area, telling that the leg was injured in the earthquake and cannot move.

FIG. 1-14 is a flow chart showing an example of the flow of processing executed by each device in this modified example.
In this drawing, an example of processing executed by the control unit 21 of the terminal 20X, processing executed by the control unit 21 of the terminal 20Y, and processing executed by the control unit 11 of the server 10 is shown in order from the left.

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 display screen)
・Safety registration account=User Y. of terminal 20Y. Y (users of terminals 20B to 20E on the display screen)
The processing in the case of is exemplified.

As a non-limiting example, the control unit 21 of the terminal 20X causes the display unit 24 to display the disaster information (X120). , determines whether or not to input safety confirmation information (X130). If it is determined to input safety confirmation information (X130: YES), the control unit 21 of the terminal 20X accepts the safety confirmation information and transmits safety confirmation registration information to the server 10 (X140). If it is determined not to input the safety confirmation information (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 safety confirmation registration information is received from the terminal 20X via 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 of receiving safety confirmation registration information from another terminal (terminal 20Y as an example, not limitation).

When it is determined that the safety information has been received from the server 10 by the communication I/F 22 (X150: YES), the control unit 21 of the terminal 20X displays the received safety information on the display unit 24 (X160).
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 registration account is different. The safety information received only from the user may be displayed on the display unit 24 .

The control unit 21 of the terminal 20Y similarly executes steps Y150 to Y160.

In this modification, the terminal 20 of the user of the safety reference account, based on the input to the own terminal 20 by the user of the own terminal 20, safety information (or safety confirmation registration information) regarding the safety of the user of the own terminal 20 A configuration for transmitting (not limited to but an example of the third information regarding the safety of the user of the terminal) by the communication I/F 122 is shown.
As an example of the effect of the modification obtained by such a configuration, based on the input to the terminal by the user of the terminal, the third information regarding the safety of the user of the terminal is transmitted to notify others of the safety of the user of the terminal. be able to.

<First modification (2)>
In the above-described embodiment, an example in which safety information is displayed in association with a user account has been illustrated, but the present invention is not limited to this. As an example and not a limitation, the safety information may be displayed in association with the 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 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 as an example and not limitation.

The group management database 157 is a database for managing information about groups, and an example of the data configuration 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.

A 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 as an example and not a limitation, the server 10 sets and stores a unique value (unique value) for each group.

The group name is the name of this group, and as a non-limiting example, the name registered when the user of the terminal 20 creates a group is stored.

Group member data is data for storing application IDs of accounts that are members of this group (belonging to the group). As an example, not limitation, when a user registers for group participation, the server registers group participation. The application ID of the user who performed 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. In this talk list screen, from the display screen on the left side of FIG. 1-13, B. Based on the fact that the talk room with B.B has been browsed, B.B. The number of unread messages with B is "0" (hidden).

By way of example and not limitation, in the talk list screen on the left side of FIG. 1-17, when the talk room list item of a seminar mate is tapped by the user, the talk room screen on the right side of FIG. 1-17 is displayed by way of example and not limitation. be.
This screen differs from the display screen on the right side of FIG. 1-13 in that the talk room name display area includes, by way of example and not limitation, the user A.S. Characters indicating that A is a talk room for talking with a group of seminar friends (in this example, "seminar friends (4)" (the number is the number of members)) are displayed.

In the user-by-user safety information display area, the user B. is superimposed on the second danger icon DIC2 as the user-by-user safety information. User A.B superimposed on the second safety icon SIC2. User D.A superimposed on the second safety icon SIC2. The icon of user F.D and the second danger icon DIC2 are displayed superimposed. An icon F is displayed.

In addition, user D. is displayed in the talk area. As content transmitted from user B.D. A text content confirming that B is scheduled to give a presentation at an academic conference in Tsukuba today is displayed. The content sent from User B.F is 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.A. 4 shows the talk list screen of A's terminal 20A.
This talk list screen is different from the talk list screen on the left side of Figure 1-13. If any member belonging to the group talk room has set the safety information, the icon corresponding to the group talk room will show the safety status. FIG. 4 is a diagram showing an example in which images (icons, etc.) based on information are associated and displayed.

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

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

As an example and not by way of limitation, in the talk room list screen on the left side of FIG. 1-18, when the talk room list item of a seminar mate is tapped by the user, the talk room screen on the right side of FIG. 1-18 is displayed as an example and not by way of limitation. be done.
Since this screen is the same as the talk room screen on the right side of FIG. 1-17, the explanation is omitted.

Note that the method of changing the display mode is not limited to the above.
As a non-limiting example, if the safety information of all members belonging to the group talk room is set to "safe", the icon corresponding to the group talk room is displayed in "blue" and one person belonging to the group talk room is displayed. If the above members' safety information is set to "dangerous", an icon corresponding to the group chat room may be displayed in "red".
Further subdividing it, based on the number (or percentage) of the members who belong to the group chat room and set it as "dangerous", the icons corresponding to the group chat room are displayed in "yellow" and "red". , the above effect display may be performed.
Also, the name of the group talk room is not limited to these, and may be displayed by changing the color or typeface of the characters indicating the name of the group talk room.

In the case of displaying in the talk list, for 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 generates safety information for the group (hereinafter referred to as "group safety information"). is generated in a first manner indicating that all members are "safe". When safety registration data of all application IDs are not "safe", the control unit 11 of the server 10 generates group safety information for the group in a second mode 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 modified example, the terminal 20 of the user of the safety reference account is connected to a chat room such as a one-to-one chat room or a group chat room (not limited to, but an example of the first chat room) containing safety information. It shows a configuration in which the control unit 21 performs control to change the display mode of the information on the talk room based on the included information on the safety of the user.
As an example of the effect of the embodiment obtained by such a configuration. It is possible to appropriately change the display mode of information about the first chat room based on information about 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 has two classes of "safe" and "dangerous", but it is not limited to this. Other safety status information may be included.
As an example and not as a limitation, the safety information may be set in three classes of "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 FIG. 1-12. In the safety registration area R1, this screen has a safety button SBT for setting safety as safety information and a safety button SBT for setting safety as unsafe. In addition to the danger button DBT, an out-of-area button ABT for setting out-of-area as safety information (in this example, a button indicated by the characters "out-of-area") is a diagram showing an example of display. be.

"Out of area" is, by way of example and not limitation, when 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 terminal 20 of the user is located at a distance of a set distance (200 km as an example, not a limitation) from the epicenter.

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

In this talk list screen, unlike the talk list screen on the left side of FIG. Based on the fact that user E has set "out of area" as safety information, user E.E. The icon corresponding to E is overlaid with an out-of-area icon AIC (in this example, an icon containing characters "out of area") indicating that the area is out of area.

In addition to these, as non-limiting examples, "energetic" indicating being in good spirits, "a little energetic" indicating being in good spirits, "not very energetic" indicating not being very energetic, and "not very energetic" The safety status information may include information such as "not feeling well" indicating that the person is not.

<First modification (4)>
In the above embodiment, the server 10 generates safety information based on safety confirmation registration information, but the present invention is not limited to this. As an example and not a limitation, the terminal 20 may generate the safety information.

In this case, as an example and not a 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 for example, not limitation, transmits the safety information to each terminal 20 of the safety registration account and the account that has already been registered as a friend. do.

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

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

The content described in the second embodiment can be applied to each of the other embodiments and each of the other modifications.
Moreover, the same code|symbol is attached|subjected about the component same as an already-appearing component, and description for the second time is abbreviate|omitted.

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

In the home screen on the left side of FIG. 2-1, by way of example and not limitation, user Y.Y. The user status icon ICYD (user YY, dangerous) is displayed based on Y setting "dangerous" as safety information.

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

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

As an example and not a limitation, in the safety information change area on the left side of FIG. An example of the talk list screen displayed on the terminal 20X of X is shown in the center of FIG. 2-1. Since this talk list screen is the same as the display screen on the left side of FIG. 1-10, the description thereof is omitted.

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

At the top of the talk area of this talk room screen, by way of example and not limitation, user Y.Y. The first notification information NI1 for notifying the safety information set by Y in the chat room (in this example, the characters "Mr. Y.Y 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. As content from Y, a text content ("Is the earthquake okay?") is displayed.

User Y.Y. Based on Y changing the safety information from "dangerous" to "safe", as an example and not limitation, the second notification information NI2 in which the safety has been changed to safe (in this example, "Mr. Y confirms safety has been answered" and a user status icon ICYS (user Y. Y, safe)) are displayed.
Below that, by way of example and not limitation, user Y. As the content from Y, text content ("Evacuated!") is displayed.

<Processing>
FIG. 2B is a flow chart showing an example of the flow of processing executed by each device in this embodiment.
In this drawing, an example of processing executed by the control unit 21 of the terminal 20X, processing executed by the control unit 21 of the terminal 20Y, and processing executed by the control unit 11 of the server 10 is shown in order from the left.

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

FIG. 2-3 is a flowchart showing an example of the flow of safety confirmation processing. The view of the figure is the same as in FIG. 2-2.
The control unit 21 of the terminal 20X performs steps X2130 to X2160 in the same manner as steps X130 to X160 in FIG. 1-14, for example and not limitation. Further, as an example and not limitation, the control unit 21 of the terminal 20Y executes steps Y2130 to Y2160 in the same manner as steps Y130 to Y160 in FIG. 1-14. The control unit 11 of the server 10 performs steps S2130 to S2140, for example and not limitation, in the same manner as 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, as a judgment condition for terminating the process, as an example, not a limitation, a case where a specific period (one week as an example, not a limitation) has passed since the date and time of the disaster, or based on the user input of the server 10 For example, when it is selected that the confirmation service is suspended.

If it is determined to end the process (X220: YES, Y220: YES, S220: YES), the control unit 21 of each terminal 20 and the control unit 11 of the server 10 end the process.
If it is determined not to end the process (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 chat processing at any timing before or after the safety confirmation processing.

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

As a non-limiting example, the safety confirmation process is executed, and when the terminal 20Y receives the 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 terminal 20Y accepts the input of the safety confirmation registration information (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").

When receiving the second safety confirmation registration information, the control unit 11 of the server 10 may perform safety comparison processing between the first safety confirmation registration information and the second safety confirmation registration information. Then, if there is no difference between the first registered safety confirmation information and the second registered safety confirmation information, the second safety confirmation information may not be transmitted to each terminal 20 .

In addition, if a difference occurs between the first safety confirmation registration information and the second safety confirmation registration information as a result of the safety comparison processing, the control unit 11 of the server 10 changes the safety status of the safety registration account. You may make it transmit to each terminal 20 the safety change information which shows that it was.

This timing chart illustrates an example in which the safety confirmation registration information is input twice on the terminal 20Y of the safety registration account, but the same process can be executed in the case where the safety confirmation registration information is input three times or more. can.

<Effect of Second Embodiment>
In this embodiment, the terminal 20 of the user of the safety reference account receives the first safety information (not limited but an example of the first information) by the user of the safety registration account (not limited but an example of the user of the first terminal). ) is changed to second safety information (not a limitation, but an example of the second information), 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 user of the first terminal changes the first information regarding the safety of the user of the first terminal to the second information, the terminal can 2 information can be reliably acquired.

In this case, the second safety information includes 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 terminal) It can be made to be displayed in a talk room (an example of a first chat room, not a limitation).
As an example of the effect of the embodiment obtained by such a configuration, the terminal user is notified of the second information in an easy-to-understand manner by displaying it in the first chat room including the user of the first terminal and the user of the terminal. can be done.

<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 a non-limiting example, 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.

The display screen in this modified example illustrates an example in which only safety status information is registered as safety confirmation information. Also, a case where the safety information is displayed on the friend list and the user's profile screen on the terminal 20 of the safety reference account will be illustrated. 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.Y. A safety information change area for changing the safety information that has already been set is superimposed on the home screen of Y's terminal 20Y and displayed. Since this home screen is the same as the display screen on the left side of FIG. 2-1, the description thereof is omitted.

As an example and not a limitation, in the safety information change area on the left side of FIG. 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. is displayed as an item in the friend list. Icon and user name corresponding to user A.Y. An icon and user name corresponding to user B.A. A list of icons, user names, etc. corresponding to B is displayed. And, in this example, user Y. Based on the fact that Y has set "dangerous" as safety information, user Y.Y. A 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 safety information, user A.A. A first safety icon SIC1 is displayed superimposed in association with the icon of user B.A. Based on the fact that B.B has set "dangerous" as safety information, user B.B in the friend list is displayed. A first danger icon DIC1 is superimposed in association with the B icon.

By way of example and not limitation, on the home screen in the center of FIGS. By way of example and not limitation, when the friend list entry corresponding to Y is tapped by the user, user Y.Y on the right side of FIG. The display transitions to the profile screen corresponding to Y.

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

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

Also, user Y.Y. Under the icon and username representing Y's profile, user Y.Y. As information regarding Y's safety, a second safety icon SIC2 is displayed.
More specifically, on the home screen in the center of FIG. 2-5, user Y. in the friend list is displayed. A first danger icon DIC1 was displayed in association with the Y icon. User Y. Y changes the first information about safety (danger) to the second information (safety), and user Y.Y shown on the right side of FIG. 2-5. Based on the user Y's profile screen being displayed, user Y.Y's profile screen is displayed. 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.Y. When the user taps the friend list item corresponding to Y, the control unit 21 of the terminal 20X displays the user Y.Y on the right side of FIG. 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 is transmitted from the server 10 to the terminal 20X. be done. Then, based on the received information, the control unit 21 of the terminal 20X displays the above-described push notification, and based on the received information, an icon corresponding to the changed safety information (in this example, safety to display the second safety icon SIC2).

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. . Then, based on the received information, the control unit 21 of the terminal 20X displays the icon corresponding to the safety information after the change (in this example, the second safety icon SIC2 corresponding to safety). In addition, the control unit 21 of the terminal 20X combines the previously received safety information before change (“dangerous” in this example) with the newly received safety information after change (“safety” in this example). Based on this, information for displaying the push notification may be generated and the push notification may be displayed.

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

Also, on the home screen in the center of FIG. 2-5, the user Y. When the user taps the friend list item corresponding to Y, the control unit 21 of the terminal 20X displays the user Y.Y on the right side of FIG. The profile screen corresponding to Y is displayed, but the icon corresponding to the safety information before change (in this example, the second danger icon DIC2 corresponding to danger) is displayed. Then, the control unit 21 of the terminal 20X transmits the 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 (the second danger icon DIC2 corresponding to danger in this example) to the icon corresponding to the safety information after the change (in this example Then, control may be performed to change to the second safety icon SIC2) corresponding to safety.

As an example and not a limitation, icons based on safety status information (second safety icon SIC2 or second danger icon DIC2 ) is tapped, the user's profile screen may be displayed.
By way of example and not limitation, in the left hand screen of FIGS. 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 talk room list items of the user of the safety registration account (for example, without limitation, icons corresponding to the user's talk room list items). (icons based on safety status information) may be displayed in a luminous manner. Then, when the illuminated item is tapped, the user's profile screen may be displayed.

Further, as described above, the safety location information and the safety comment information may be displayed on separate screens. may be displayed on the profile screen.

Also, the composite safety information may be displayed on the profile screen.
Alternatively, 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, the safety information may not be displayed on the above profile screen. As an example, the safety information may be displayed on the home screen described above, but may not be displayed on the profile screen described above.

Also, instead of the profile screen described above, a screen dedicated to 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 modified example.
Here, as with the display screen,
・Safety registration account=User Y. of terminal 20Y. Account of Y (an example of a user of the first terminal, not limited) Safety reference account = user X.Y of terminal 20X The following is an example of the processing for X (an example of a terminal user, not a limitation) as an account.

As an example and not a limitation, safety confirmation processing is executed, and when terminal 20Y receives input of safety confirmation registration information (Y2130), the first safety confirmation registration information is transmitted to 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 terminal 20Y accepts the input of the safety confirmation registration information (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.X. Based on the user's operation on the terminal 20 of X, display processing for displaying specific display elements in the messaging application is executed (timing "TM250").
Here, specific display elements include, by way of example and not limitation, the following display elements.
・Profile screen of user of safety registration account ・One-to-one chat room between safety registration account and safety reference account ・Group chat room including safety registration account ・Talk list screen including safety registration account ・Official account profile screen of safety confirmation service・Talk room between the official account of the safety confirmation service and the safety reference account ・The talk list screen including the official account of the safety confirmation service It may be excluded from the elements.

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").
If there is no difference between the first registered safety confirmation information and the second registered safety confirmation 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 can choose not to. In this case, information indicating that there is no change in safety may be transmitted to the terminal 20X.
In addition, if a difference occurs between the first safety confirmation registration information and the second safety confirmation registration information as a result of the safety comparison processing, the control unit 11 of the server 10 changes the safety status of the safety registration account. You may make it transmit the safety change information which shows that it was the terminal 20X to the terminal 20X.

Upon receiving the second safety information, the terminal 20X executes display processing (X2160) (timing "TM280").

This timing chart illustrates an example in which the safety confirmation registration information is input twice on the terminal 20Y of the safety registration account, but the same process can be executed in the case where the safety confirmation registration information is input three times or more. can.

In this modification, after the terminal 20 of the user of the safety reference account receives the first safety information (not limited but an example of the first information) via the communication I/F 22, the user of the safety registration account (not limited to , 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). In this case, the communication I/F 22 receives the second safety information (not a limitation, but an example of the second information).
As an example of the effect of the embodiment obtained by such a configuration, after the terminal receives the first information, the terminal is triggered by displaying the first chat room including the user of the first terminal and the user of the terminal. can obtain the second information. In addition, by doing so, it is possible to prevent the user of the terminal from receiving the second information unnecessarily and to avoid annoyance.

In addition, the terminal 20 of the user of the safety reference account displays information of the user of the safety registration account such as profile information of the user of the safety registration account (not limited, but an example of information of 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. In addition, by doing so, it is possible to prevent the user of the terminal from receiving the second information unnecessarily and to avoid annoyance.

In this case, the information on the user of the safety registration account may include information on 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 effect of the modification obtained by such a configuration, when the terminal displays information about 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 terminal can be enabled to obtain the second information. In addition, by doing so, it is possible to prevent the user of the terminal from receiving the second information unnecessarily and to avoid annoyance.

<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 as a limitation, the degree of closeness between the safety reference account and the safety registration account is defined as follows.
Intimacy (safety reference account, safety registration account) = average number of messages sent/received per day between safety reference account and safety registration account

In this case, as a non-limiting example, if the degree of intimacy is greater than or equal to a set value ("10" as an example, not a limitation), the control unit 11 of the server 10 sends the second safety information to the safety information. You may make it transmit to the terminal 20 of a reference account.

If the degree of intimacy is greater than or equal to the set value, the terminal 20 of the safety reference account transmits the safety update request information to the server 10 at set time intervals (for example, not limited to "5 minutes"). do. Then, 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 (an example of the second information, not a limitation) 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 embodiment, an example in which the safety registration account and the safety reference account are different was exemplified, but the present invention is not limited to this. here,
・Safety registration account and safety reference account = User A. of terminal 20A A case of A's account is 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. Information including a user status icon (user A.A, safe) indicating this is displayed in the second disaster information display area based on A setting that he is "safe". . Thus, in this example, user A. A's account functions as a safety registration account.

By way of example and not limitation, in the talk list screen on the left side of FIGS. When the C talk room list item is tapped by the user, by way of example and not limitation, the center talk room screen of FIGS. 2-7 is displayed. This screen is different from the talk room screen shown on the right side of FIG. A is user C. Characters ("C.C" in this example) indicating that the room is for talking with C as the other party are displayed.
Further, in the user-by-user safety information display area therebelow, as an example and not by way of limitation, user C.2 is displayed superimposed with the second danger icon DIC2 as user-by-user safety information. The icon of user A.C and the second safety icon SIC2 are superimposed and displayed. An icon of A is displayed.

The talk area includes, by way of example and not limitation, user C.I. Content from user A.C (as a non-limiting example text content "Earthquake! Shaking is great", text content "Elevator stopped") and user A.C. Content originated by A (as an example, but not as a limitation, text content of "Is earthquake okay? Are you with someone?") is displayed.

By way of example and not limitation, user C.I. User A.C changes the safety information 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.I. Based on user C.C changing his safety information from "dangerous" to "safe", by way of example and not limitation, at the top of the screen, user C.C. A push notification PN3 including an icon and a text indicating that C has changed the safety information (C.'s status has changed) is displayed.

Also, in the talk area, by way of example and not limitation, new user C.I. The content from C (as a non-limiting example, the text content of ``The elevator has stopped'', the text content of ``I'm alone, I'm scared, the elevator has moved! is displayed.

Also, in this display screen example, the user C.I. Under the text content of C "I'm out!" Changed" and user status icon ICCD (user CC, dangerous) -> user status icon ICCS (user CC, safe) are displayed.

Under this third notification information NI3, user A. The content originated by A (as an example, but not by way of limitation, the text content of "Good luck!") is displayed.

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

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

Hereinafter, the user account of the originator, who is the person who originates the call, is referred to as the "source account", and the user account of the destination, who is the recipient of the outgoing call, is referred to as the "destination account".

The content described in the third embodiment can be applied to each of the other embodiments and modifications.
Moreover, the same code|symbol is attached|subjected about the component same as an already-appearing component, and description for the second time is abbreviate|omitted.

<Display screen>
In the display screen of this embodiment, the source account is user A. of terminal 20A. A, the destination account is transferred to the user B. of the terminal 20B. B and user C.B of terminal 20C. Let C. In addition, the source account and the destination account are exemplified as safety registration accounts for which safety registration has been completed.

The left side of FIG. 3-1 shows user A. The talk room screen of A's terminal 20A is displayed. Since this screen is the same as the display screen shown on the right side of FIG. 1-13, the explanation is omitted.

As an example and not a limitation, when the user taps the call button BT7 for making a call on the right side of the talk room name display area on the talk room screen on the left side of FIG. An example of the call screen displayed on A's terminal 20A is shown on the right side of FIG. 3-1.

On the call screen, a call status display area is provided below the area where the name of the messaging application, etc., is displayed at the top of the screen, for example and not limitation, to indicate the call status (state of the call). Call statuses include, by way of example and not limitation, user A.A. A is user B.A. "Calling" indicating that user A.B is calling. A is user B.A. "During a call" or the like is provided to indicate that a call is being made with B.

Below that is the icon image of the user's messaging application, the user name, the duration of the call, and a microphone off button to turn off the microphone (in this example, an image of a microphone and the words "Turn off the microphone"). , a video call button to make a video call with that user (in this example, a video camera-type image and the words "start video call"), and a speaker on button to turn on the speaker (in this example , a speaker-shaped image and the words "speaker on"), a call end button for ending a call, and the like are displayed.

In this example, in the call status display area, the characters "during a call" are displayed, and below it is the user B. An icon image of B, the letters "BB", 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. Although this screen is similar to the talk room screen shown on the right side of FIG. 2-7, the talk room name display area includes, by way of example and not limitation, a "<" back button for returning to the previous screen, a user A. A is user C. Characters (in this example, "C.C") indicating that this is a talk room for talking with C, a call button, etc. are displayed.

As a non-limiting example, 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, the display 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 both B's safety statuses are "safe," call refrain request information CRI1 is displayed superimposed on the talk room screen on the left side of Fig. 3-2 to discourage unnecessary and non-urgent calls in the event of a disaster. ing.
In this example, the call refrain request information CRI1 includes a message (in this example, "Unnecessary due to large-scale disaster occurrence Please refrain from making non-urgent calls.”, a character image), a cancel button for canceling the outgoing call (in this example, a button containing the word “cancel”), and a second button for making a call. 2 Call buttons (in this example, a button containing the characters "call by all means") are displayed.

By way of example and not limitation, in the central talk room screen of FIG. 3-2, when the second call button is tapped by the user, user A. An example of the call screen displayed on A's terminal 20A is shown on the right side of FIG. 3-2.

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

<Processing>
FIG. 3C is a flow chart showing an example of the flow of processing executed by each device in this embodiment.
In this figure, from the left side, an example of processing executed by the control unit 21 of the terminal 20X of the source 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 is shown.

As a non-limiting example, when the control unit 21 of the terminal 20X executes the safety confirmation process (X210), as a non-limiting example, based on an input (user operation, etc.) to the input/output unit 23 of the terminal 20X, As an 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 safety status determination processing (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 in the safety registration data of the sender account (hereinafter referred to as "sender status") and the recipient account. safety status information in the safety registration data (hereinafter referred to as "destination status").
Then, the control unit 11 of the server 10 determines whether or not the originator status is "safe" and the destination status is "safe" as an example and not a limitation.

If it is determined that the originator status is "safe" and the destination status is "safe" (S310: "safe"-"safe"), the control unit 11 of the server 10 requests that the call be refrained from making calls. Refusal request information is sent to the terminal 20X of the originator account via the communication I/F 14 (S320).

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

When the communication I/F 22 determines that the call refrain request information has been received from the server 10 (X320: YES), the control unit 21 of the terminal 20X displays the received call refrain request information on the display unit 24 (X330). .
If it is determined that the call refrain request information has not been 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). Also, 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 call ringtone indicating that a call has been received, for example and not limitation. This allows user X. Have X hear a ring tone to indicate that a call is being requested. Further, the control unit 21 of the terminal 20Y causes the display unit 24 to display an incoming call display including the information of the caller account (user name as an example, not a limitation) as an example and not a limitation.
As the information of the source account, information including the source status may be displayed on the display unit 24 of the terminal 20 of the destination account.

As an example and not a limitation, when a call is accepted based on an input to the input/output unit 23 of the terminal 20Y, the control unit 21 of the terminal 20X and the control unit 21 of the terminal 20Y communicate with the server 10 as an example and not a limitation. perform VoIP processing in calls between users via. 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 execute VoIP processing in the call.

As an example and not a limitation, when the call is terminated and disconnected based on an input to the input/output unit 23 of the terminal 20X or the terminal 20Y, the control unit 11 of the server 10 terminates the process. Also, the control units 21 of the terminals 20X and 20Y terminate the process.

Note that the call refrain request information may include a display for selection as to whether or not to cancel the outgoing call. In this case, the call refrain request information is displayed on the terminal 20X of the originator account, and as an example and not as a limitation, if it is selected to cancel the call based on the input to the call refrain request information, the terminal of the originator account The control unit 21 of 20X transmits to the server 10 via the communication I/F 22 call termination information indicating that the call is to be cancelled. When the communication I/F 14 determines that the call cancellation information has been received from the terminal 20X of the caller 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 the outgoing call based on the input operation for the call refrain request information, the control unit 11 of the server 10 may start call processing between the terminal 20X and the terminal 20Y.

Further, when the control unit 11 of the server 10 determines in the safety status determination process that the caller status is "safe" and the destination status is "safe" (S310: "safe"-"safe"), Call connection refusal information indicating that the call will not be connected may be transmitted to the terminal 20X of the caller account via the communication I/F 14 . Upon receiving the call connection rejection information, the control unit 21 of the terminal 20X may cause the display unit 24 to display it. Then, the control unit 11 of the server 10 may not start the call processing.
In other words, when it is determined in the safety status determination process that the originator status is "safe" and the destination status is "safe", the call is forcibly terminated.

<Effect of the third embodiment>
In this embodiment, the terminal 20 of the user of the originating account performs processing related to the call by the control unit 21 based on 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. is shown.
As an example of the effect of the embodiment obtained by such a configuration, it is possible to appropriately perform processing related to a call based on information regarding the safety of the user related to the call.

Also, in this case, in the processing related to the call, the call is suppressed (prohibited) when both 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 "safe". processing can be included.
As an example of the effect of the embodiment obtained by such a configuration, 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 set, the call is suppressed ( prohibited).

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

If the caller status is "dangerous", the call origination by the user of the caller account is considered to be of high urgency. Therefore, when the caller status is determined to be "dangerous", the connection priority of the call is increased, thereby facilitating the connection of a call with a high possibility of urgency.

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

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

<Third modification (2)>
In the above embodiment, the server 10 executes the safety status determination process, but the present invention is not limited to this. As an example and not a limitation, the terminal 20X of the originator account may execute the safety status determination process.

As a non-limiting example, when the control unit 21 of the terminal 20X of the caller account executes the safety confirmation process, as a non-limiting example, based on an input (user operation, etc.) to the input/output unit 23 of the terminal 20X, the call is performed. Accept the destination account. As a non-limiting example, control unit 21 of terminal 20X then transmits safety information request information including the application ID of the source account and the application ID of the destination account to server 10 via communication I/F 22 .
Upon 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 to obtain the caller status and callee status. Then, the safety information including the caller status and the callee status is transmitted to the terminal 20X through the communication I/F 14 .

When safety information is received from the server 10 via the communication I/F 22, the control unit 21 of the terminal 20X executes safety status determination processing based on the received safety information. Then, when it is determined that the originator status is “safe” and the 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 when the terminal 20X has acquired the destination status as the safety information prior to the start of 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 embodiment>
The fourth embodiment is an embodiment in which, when the safety confirmation registration information is registered in the terminal 20 of the safety registration account, a response is automatically sent to the subsequent messages sent to the safety registration account.

The content described in the fourth embodiment can be applied to each of the other embodiments and each of the other modifications.
Moreover, the same code|symbol is attached|subjected about the component same as an already-appearing component, and description for the second time is abbreviate|omitted.

<Display screen>
The left side of FIG. 4-1 shows user A. The home screen of A's terminal 20A is displayed. Unlike the home screen in the center of FIG. 1-12, this screen displays a safety message input by the user (in this example, "Moving by bicycle") in the safety message input area. In addition, in the current location input area below it, 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. When tapped by A, the display transitions to the safety registration area R1 in the center of FIG. 4-1.

In this case, in the safety registration area R1, the displays of the safety button SBT, the danger button DBT, the safety message input area, the current location input area, etc. are erased, and a safety information confirmation area for confirming the set safety information is formed. there is In the safety information confirmation area, as a non-limiting example, the characters "Registered with the following contents", the characters "safety message", the user status icon ICAS (user A.A, safe), "Mitaka/By bicycle Moving" is displayed.

Further, below that, an automatic response setting area for setting the automatic response mode is configured. In the auto-response setting area, as a non-limiting example, the characters "Do you want to switch to the auto-response mode?" , and a "No" button BT12 (in this example, a button indicated by "No" characters) for not setting the automatic response mode.

As an example and not a limitation, in the safety registration area R1 in the center of FIG. Suppose it is tapped by A. In this case, a screen as shown on the right side of FIG. 4-1 is displayed.

The right side of FIG. 4-1 shows user A. 3 shows an example of a talk list screen displayed on the display unit 24 of A's terminal 20A. Unlike the talk list screen on the left side of Figure 1-13, this screen is different from the talk list screen on the left side of Fig. 1-13. If you have set the automatic answer mode, this screen will show that messages from other users are sent to the talk room list items after the automatic answer mode is set. The auto-answered information is displayed to indicate that the chat room has been sent (replied by auto-response).

In this example, when the automatic response mode is set, the message is sent at the oldest time among the chat room list items of the chat room to which other users sent messages after the automatic response mode was set. From the talk room list item corresponding to the talk room (user B.B's talk room) to the talk room list item corresponding to the talk room (tennis circle group talk room) in which the message was sent at the most recent time , automatic response completed information (in this example, a telop indicating the characters "automatic response completed") is superimposed and displayed.

The left side of FIG. 4-2 shows user D. The talk room screen of D's terminal 20D is displayed. This screen is different from the talk room screen shown on the right side of FIG. D is user A.D. Characters (“A.A” in this example) indicating that this is a talk room for talking with A as a partner are displayed.
Further, in the user-by-user safety information display area therebelow, as an example, but not by way of limitation, user A.2 is superimposed and displayed with a second safety icon SIC2 as user-by-user safety information. User D.A superimposed on the second safety icon SIC2. D icon is displayed.

The talk area includes, by way of example and not limitation, user A. Content from user D.A (as an example, but not limitation, text content of "Well then, good night!") and user D.A. The content sent by D (as a non-limiting example, the text content of "See you tomorrow~", the text content of "Shattering ~ Earthquake?", The text content of "Are you okay? Have you left home yet?") are displayed. there is

Under that, automatic response confirmation information ARI originating from the OA account (in this example, safety confirmation response service) (as a non-limiting example, "This is a safety confirmation service 20XX/08/04 9: Information including characters such as "Mr. A. It has been confirmed that Mr. A is safe in the disaster that occurred in 39. Currently, it is set to automatic response to save battery power, etc.") is displayed.

Here, "read" can be defined as the opposite term to "unread".
As a condition for a message (content) to be read (hereinafter referred to as a "read condition"), one of the following conditions can be applied as an example, not as a limitation.
(A) that the message was displayed;
(B) A certain period of time (a period of several seconds to 10 seconds, not limited) has passed since the message was displayed.
(C) The displayed message was tapped (clicked) after the message was displayed.
(D) A reply was made to the message after it was displayed.
(E) If the message is a moving image message, the moving image has been reproduced.
(F) If the message is a moving image message, a certain period of time (not limited, but about several seconds to 10 seconds) has elapsed since the moving image was played.

In this case, the "unread" state may be defined, by way of example and not limitation, as a state in which the above read conditions are not met.
The "unread" state is a kind of state in which the user has not read the message (content).

In this example, user D.I. As a non-limiting example, among the contents transmitted by D, based on the fact that the text content "see you tomorrow" has been read, the text "read" is displayed at the lower left of the balloon of this text content. is displayed, and based on the fact that the text content of "Shaketeru~ Earthquake?" "Read" is not displayed.

By way of example and not limitation, user A.A. User A.A when set to auto-answer 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 is different from the talk room screen shown on the left side of FIG. A is user D. Characters (“D.D” in this example) indicating that the room 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. Content sent by A (as a non-limiting example, the text content of 'Well then, good night', the text content of 'I'm sorry for the late reply, Mr. BB seems to have injured his leg and was helping;') and , user D. Contents from D (as a non-limiting example, the text content of "See you tomorrow~", the text content of "Shattering~earthquake?", and the text content of "Are you okay? Have you left home yet?") are displayed.

Also, user D.I. By way of example and not limitation of the content from D, after the text content of "Shaking Teru~ Earthquake?" is sent and before the text content of "Are you okay? at the timing of user A. Based on the fact that the automatic response mode has been set by A, the automatic response setting information ARSI including the characters "automatic response mode has been set" is displayed between these text contents.

Also, user D.I. By way of example and not limitation, of the content from user A.D, the timing after the text content "Are you okay? Are you out of the house yet?" As a non-limiting example of the content from A, the user A. Based on the fact that the automatic response mode has been canceled by A, the automatic response cancellation information ARRI with the characters "Automatic response mode canceled" is displayed between these text contents.

<Processing>
The processing performed by each device in this embodiment can be performed according to FIGS. 2-2 to 2-3 as an example and not as a limitation.

FIG. 4C 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 X (not limited, but an example of a user of the terminal) Account that sends a message to the safety registration account that performed an automatic response=User Y.X of the terminal 20Y An example of the process for setting Y (an example of the user of the first terminal, not limiting) as an account will be described.

As a non-limiting example, safety confirmation processing is executed, and when terminal 20Y receives an input operation for safety confirmation registration information (Y2130), the first safety confirmation registration information is transmitted to 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 terminal 20X accepts the input operation of the safety confirmation registration information (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 judgment display indicating whether to start the automatic response (timing "TM340").
As an example and not a limitation, when starting the automatic response is selected based on the input operation on the judgment display displayed on the terminal 20X, the control unit 21 of the terminal 20X requests to start the automatic response. Automatic response start request information for doing so is transmitted to the server 10 via the communication I/F 22 (timing "TM345").

When the communication I/F 14 determines that the 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, as an example and not a limitation, based on an input operation on the terminal 20Y, the user X. When a message for X is input, the control unit 21 of the terminal 20Y, for example and not limitation, stores the input message, the application ID of the terminal 20Y that is the source of the message, and the application of the terminal 20X that is the destination of the message. message transmission request information including the ID is transmitted to the server 10 via the communication I/F 22 (timing "TM355").

When the communication I/F 14 receives the message transmission request information from the terminal 20Y, the control unit 11 of the server 10 determines whether or not the automatic response process for the account of the message transmission destination 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" to "TM375".
Therefore, when it is determined that the timing at which the message transmission request information is received is after the timing "TM350" and before the timing "TM375", the control unit 11 of the server 10 receives the message automatic response information is transmitted to the terminal 20Y through the communication I/F 14 (timing "TM360").

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

As an example and not a limitation, when termination of the automatic response is selected based on an input operation on the terminal 20X, the control unit 21 of the terminal 20X issues an automatic response termination request for requesting termination of the automatic response. 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 message automatic response processing for the terminal 20X (timing "TM375").
Then, the control unit 11 of the server 10 retrieves the message automatic response history information including the messages transmitted to the terminal 20X during the message automatic response processing period (in this case, between the timings "TM350" to "TM375"). It is transmitted to the terminal 20X through 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").

In this timing chart, an example in which the server 10 receives the message transmission request information for the terminal 20X once within the message automatic response processing period has been exemplified. Processing can be performed. The same applies when the server 10 receives message transmission request information for the terminal 20X from a plurality of terminals 20 within the message automatic response processing period.

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

Further, when the control unit 11 of the server 10 receives the message transmission request information for the group chat room in which the account of the terminal 20X is included within the message automatic response processing period, the control unit 11 sends the message automatic response information to each terminal 20 of the member belonging to the group. You may choose not to send to

Also, in the terminal 20X, prior to the timing "TM320" and the timing "TM325", the display unit 24 displays a display for determining whether or not to start the automatic response, and the automatic response start request information is transmitted to the server 10. You may do so.

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

Also, in this case, the terminal 20, based on the transmission of the safety information, information for determining whether or not to start an automatic response to a talk (not limited, but an example of a chat) (not limited, but a chat An example of information about automatic response) 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 the own terminal 20 with respect to the information for determination, and performs an automatic response. The control unit 21 can perform processing related to an automatic response to a talk (chat), such as processing to display information about the start.
As an example of the effect of the embodiment obtained by such a configuration, the information related to the automatic chat response is displayed on the display unit based on the transmission of the third information, and the terminal is notified that the automatic chat response is possible. users can be notified. In addition, it is possible to appropriately perform processing related to chat automatic responses based on the terminal user's input to the displayed information related to automatic responses.

<Fourth Modification (1)>
In the above embodiment, an example in which the automatic response start request information is transmitted based on an input operation to the terminal 20X that starts the automatic response has been illustrated, but the present invention is not limited to this.
As an example, not a limitation, when the remaining battery level of the terminal 20X is below a set value ("20%" as an example, not a limitation), the control unit 21 of the terminal 20X automatically sends automatic response start request information to the server 10. You may make it transmit to the target.

Further, as an example and not a 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 .

Also, as a non-limiting example, when the control unit 21 of the terminal 20X receives the disaster information from the server 10, as a non-limiting example, the control unit 21 acquires the current position via the position calculation information detection unit 29B. 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, not limited, but within 10 km from the observation point of the maximum seismic intensity). The start request information may be automatically transmitted.

Further, when the communication state of the terminal 20X is poor (as an example, not as a limitation, when the radio field intensity is equal to or less than the set value), the control unit 21 of the terminal 20X automatically sends automatic response start request information to the server 10. You may make it transmit.

In addition, the state (situation) of use of the application executed on the terminal 20X (as an example, not limitation, in use in the background), the state (situation) of position calculation by the position calculation information detection unit 29B (not limited to As an example, the terminal 20X is in a state where it is difficult to acquire a positioning satellite such as a so-called indoor environment (indoor environment), a state in which the signal strength when receiving a satellite signal from a positioning satellite is equal to or less than a set value, etc.). The control unit 21 may automatically transmit the automatic response start request information to the server 10 .

In this modification, the terminal 20 determines whether or not to start an automatic response to a talk (not a limitation, but an example of a chat) based on the state of its own terminal 20 such as the remaining battery level of its own terminal 20. (not limited to, but an example of information relating to chat automatic response) 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 the own terminal 20 with respect to the information for determination, and performs an automatic response. It shows a configuration in which the control unit 21 performs a process related to an automatic response to a talk (chat), such as a process of displaying information about the start.
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 state of the terminal, and the user of the terminal is informed that automatic chat response is possible. be able to. In addition, it is possible to appropriately perform processing related to chat automatic responses based on the terminal user's input to the displayed information related to automatic responses.

<Fourth Modification (2)>
In the above embodiment, the automatic response is terminated based on the input to the terminal 20X that initiates the automatic response, but the present invention is not limited to this.
As an example and not a limitation, when 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 message automatic response processing is terminated. Then, the message automatic response response history information may be transmitted to the terminal 20X.

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

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

In this example, based on the fact that the auto-response mode has been set, the message is sent at the oldest time among the chat room list items of the chat rooms to which other users have sent messages after being set to the auto-response mode. From the talk room list items corresponding to the sent chat room (user B.B's talk room), the talk room list item corresponding to the talk room to which the message was most recently sent (user FF's talk room) The auto-answered information (in this example, a telop indicating the characters "automatically answered") is superimposed and displayed.

In this example, user A. Based on the fact that A has received a set number of messages (10) since he turned on auto-answer mode, by way of example and not limitation, at the top of the screen, user A . Text indicating that A has received a set number of messages (10 as an example, not a limit) since A set auto-response mode (10 messages received during auto-response, continue auto-response?) A push notification PN5 containing is displayed.

By way of example and not limitation, in the display screen on the left side of FIG. When tapped by A, by way of example and not limitation, a display such as the right side of FIG. 4-4 is made.

This display screen is configured so that the safety registration area R1 is displayed in a raised manner by being 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, as a non-limiting example, the text "Registered with the following contents", the text "safety message", the user status icon ICAS (user A.A, safe), "Mitaka/bicycle "Moving with" is displayed.
An automatic response cancellation area for canceling the automatic response mode is configured below it. In the auto-response release area, as a non-limiting example, the characters "Are you sure you want to release the auto-response mode?" A button indicated by letters) and a "No" button BT14 for not canceling the automatic response mode (in this example, a button indicated by letters "No") are 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 to this. As an example and not a limitation, the terminal 20X selected to initiate the automatic response may execute the message automatic response process.

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

When 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").

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

As an example and not a limitation, when termination of the automatic response is selected based on an input operation on the terminal 20X, the control unit 21 of the terminal 20X terminates the automatic response process. Then, based on the message information received during the message automatic response processing period, message automatic response response history information is generated (timing "TM440").

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

<Fifth embodiment>
In the fifth embodiment, as an example and not as a limitation, when a disaster such as a large-scale disaster occurs, one terminal 20 (hereinafter referred to as a "terminal" as appropriate) performs safety confirmation registration (as an example, not as a limitation). (input and transmission of confirmation information) is requested by the user of another terminal 20 (hereinafter referred to as a "first terminal"), an embodiment in which a safety confirmation registration request is made to the terminal based on the setting conditions. is.

Hereinafter, as described above, a business operator that provides a safety confirmation service using a safety confirmation application will be referred to as a "safety confirmation service business operator."
The safety confirmation service provider can also be expressed as a provider of a safety confirmation application or a provider of the server 10 .
It can also be expressed as a safety confirmation service provider in the sense of a provider that provides a safety confirmation service.

Further, hereinafter, the name of the safety confirmation application is appropriately referred to as "Safety Confirmation App" for illustration and description.

In the safety confirmation application, as an example and not a limitation, the accounts registered in the server 10 as safety confirmation targets can be configured to request safety confirmation registration. As an example and not a limitation, when one account registered in the server 10 as a safety confirmation target performs safety confirmation registration, the other accounts can refer to the registered safety confirmation information.

Hereinafter, a user account that requests safety confirmation registration is referred to as a "safety confirmation request account", and a user account that requests safety confirmation registration for a safety confirmation request account is referred to as a "safety confirmation request account". In general, one user account can serve as both a safety registration request account and a safety status registration request account.

The safety confirmation registration method is not limited to a method of inputting and registering safety confirmation information using a safety confirmation application or the messaging application described above. As an example and not a limitation, a method of transmitting safety confirmation information by means of telephone, FAX, etc. 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. good too.

The content described in the fifth embodiment can be applied to each of the other embodiments and other modifications.
Moreover, the same code|symbol is attached|subjected about the component same as an already-appearing component, and description for the second time is abbreviate|omitted.

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

Further, below that, an intra-app location display area for the safety confirmation application is configured, and in this example, the characters "main menu" are displayed based on the fact that it is the main menu screen.

Beneath the in-app location display area is a disaster information display 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 lower right inside the disaster information display area, user Y.Y. Based on the fact that Y has set "safety" as safety information, the characters "my status" and the user status icon (user A.A, safe) are displayed.

Under the disaster information display area, user Y. is displayed in the safety confirmation application. A member list display area is configured in which a list of users associated with Y (hereinafter illustrated and described as “members”) is displayed.

As a non-limiting example, when an organization uses a safety confirmation application (safety confirmation service), as a non-limiting example, a user such as a representative of the organization registers members with the server 10. can be By doing so, a person belonging to the organization can be associated as a member in the safety confirmation application.

It should be noted that it is also possible to set the members not by the organization but by individuals.
In this case, as in the case of registering friends in the messaging application described above, the user of the individual terminal 20 registers a member by using a phone number, an application ID, or the like, for example and not limitation. be able to.

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

If the member list is user Y. Tapping with Y expands and displays those lists. Specifically, by way of example and not limitation, member icons and usernames are listed 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. is displayed as an item in the member list. Icon and user name corresponding to user C.X. icon and user name corresponding to user D.C. 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 X. A second unknown icon UIC2 (in this example, an icon showing the characters "unknown") is superimposed on the icon corresponding to X. As shown in FIG. User C.I. Based on the fact that C.C has set the safety information to "safe", user C.C. The icon corresponding to C is superimposed with the second safety icon SIC2. User D. User D.D. A second danger icon DIC2 is superimposed on the icon corresponding to D.

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

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

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

The safety registration request confirmation information SRI1 includes, as a non-limiting example, an image related to the icon image of the safety confirmation application, the characters "A request for safety registration has been made to XX", and a request for safety registration. and an OK button indicated by an icon containing characters "OK" for confirming that the request has been made and ending the display of the safety registration request confirmation information SRI1.

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

On the right side of FIG. 5-2, a safety registration request confirmation area R2 is superimposed on the main menu screen displayed on the display unit 24X of the terminal 20X to notify that the safety information is requested to be set. It is displayed as raised.

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.

User X. is displayed at the bottom right inside the disaster information display area. Based on the fact that X has not set safety information, the characters "Register my status" and a safety registration button BT2 similar to the safety registration button BT1 described above are displayed.

In addition, as an item of the member list, user Y.Y. A list of icons, user names, etc. corresponding to Y is displayed.
Also, user Y.Y. Based on the fact that Y has set the safety information to "safe", user Y.Y. The icon corresponding to Y is superimposed with the second safety icon SIC2.

In the safety registration request confirmation area R2, user X. who has not set safety information is displayed. user Y.X for user Y.X. A message to the effect that Y is urging you to set up your safety information (in this example, the text “request for safety registration” and the text “Y.Y is requesting you to register your safety”, user Y.Y. icon → icon of user X.X) is displayed. Below that, an answer button BT4a for setting safety information is displayed.

The left side of FIG. 5-3 shows user Y.Y. On the display unit 24Y of the terminal 20Y of Y, the user Y.Y. User X.Y by user X.Y. A safety registration request confirmation area is displayed on the member screen of the safety confirmation application based on the second safety registration request made to X. Since this display screen is the same as the display screen on the left side of FIG. 5-2, the description thereof is omitted.

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

On the right side of FIG. 5-3, the 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 the safety registration request confirmation area R2 is not displayed superimposed on the main menu screen even though the safety registration request has been made.

<Processing>
FIG. 5-4 is a flow chart showing an example of the flow of processing executed by each device in this embodiment.
In this drawing, an example of processing executed by the control unit 21 of the terminal 20X, processing executed by the control unit 21 of the terminal 20Y, and processing executed by the control unit 11 of the server 10 is shown in order from the left.

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

As a non-limiting example, the control unit 21 of the terminal 20Y displays the disaster information (Y120). is displayed on the display unit 24 (Y410).

As a non-limiting example, when it is determined that a safety registration request has been selected based on the input operation on the determination screen (Y410: YES), the control unit 21 of the terminal 20Y, as a non-limiting example, The safety registration request 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.

As a non-limiting example, the control unit 11 of the server 10 transmits disaster information (S120), and determines whether or not the communication I/F 14 has received safety registration 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 or not the setting conditions regarding the safety registration request account are satisfied (S420). Setting conditions will be described later.

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

The safety registration request information may or may not include information on the safety registration request account (application ID as an example, not limitation).
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 skips the step of S430.

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

As a non-limiting example, the control unit 21 of the terminal 20X causes the disaster information to be displayed (X120), and determines whether or not the safety registration request information has been received by 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 causes the display unit 24 to display the received safety registration request information (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 processing (X450, Y450, S450). Here, as a judgment condition for terminating the process, as an example, not a limitation, a case where a specific period (one week as an example, not a limitation) has passed since the date and time of the disaster, or based on the user input of the server 10 For example, when it is selected that the confirmation service is suspended.

If it is determined to end the process (X450: YES, Y450: YES, S450: YES), the control unit 21 of each terminal 20 and the control unit 11 of the server 10 end the process.

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

In this flowchart, the processes of S120, X120, and Y120 may be omitted so that the server 10 does not transmit the disaster information and the terminals 20 do not display the disaster information.

Also, steps X430 to X440 in the terminal 20X are not essential. This is because the terminal 20X of the safety status registration request account may be offline 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 aforementioned setting conditions will be described using this timing chart. Here, it is assumed that the setting condition is "when the safety registration request is made for the first time to the safety registration request account".

As an example and not a limitation, when the terminal 20Y performs a safety registration request operation for the terminal 20X (Y410: YES), the 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 causes the display unit 24 to display the first safety registration request information (X440) (timing "TM530").

After that, as an example and not a limitation, when the terminal 20Y performs a safety registration 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 a non-limiting example, when the terminal 20Y again performs a safety registration request operation for the terminal 20X (Y410: YES), the third safety registration 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.

Under this setting condition, when multiple safety confirmation request requests are made from a safety confirmation request account to a single safety confirmation request account, only the first safety confirmation request account can be registered for the terminal 20 of the safety confirmation request account. It shows an example of how a request is made. By defining the setting conditions in this way, the user of the safety status registration request account can be relieved from the annoyance of being repeatedly requested to register the safety status in an emergency.

Note that, unlike the above setting condition, the setting condition may be "when the N-th ("N" is a natural number) safety confirmation request request is made to the safety confirmation request account". In this case, when the safety registration request account makes safety confirmation request requests N times to one safety confirmation request account, the control unit 11 of the server 10 sends the safety registration request information to the safety registration request account for the first time. is transmitted to the terminal 20 of

<Effect of the fifth embodiment>
In this embodiment, the server 10 (not limited, but an example of a server that communicates with a terminal) sends first safety registration request request information ( An example of the first information, not limitation) is received by the communication I/F 14 from the terminal 20 of the user of the safety registration request account (an example of the first terminal, not limitation). Based on the received first safety registration request information and the set conditions, the server 10 communicates the first safety registration request information (not a limitation, but an example of second information regarding safety confirmation). /F14 is used to transmit to the terminal 20 of the user of the safety status registration request account.
As an example of the effect of the embodiment obtained by such a configuration, after receiving the first information regarding the safety confirmation request to the user of the terminal from the first terminal, based on the first information and the set conditions, Second safety confirmation information can be sent to the 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. As an example and not a limitation, the server 10 may transmit the safety registration request information multiple times based on the setting conditions.
Also, in the above embodiment, the safety registration request account and the safety registration request account are different accounts, but the present invention is not limited to this.

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

FIG. 5-6 shows user A.A when the technique 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.
In this home screen, unlike the home screen shown on the left side of FIG. 1-12, the friend list includes user B. icon and user name corresponding to user C.B. icon and user name corresponding to user D.C. icon and user name corresponding to user E.D. 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 B has not set safety information, user B. The icon corresponding to B is superimposed with a first unknown icon UIC1 (in this example, an icon with a character “?”). User C.I. Based on the fact that C.C has set "dangerous" as safety information, user C.C. A first danger icon DIC1 is superimposed on the icon corresponding to C. User D. Based on the fact that D.D has set "safety" as safety information, user D.D. A first safety icon SIC1 is superimposed on the icon corresponding to D. User E. Based on the fact that user E.E has set "safety" as safety information, user E.E. A first safety icon SIC1 is superimposed on the icon corresponding to E. User F. Based on the fact that user F.F has set "safety" as safety information, user F.F. A first safety icon SIC1 is superimposed on the icon corresponding to F.

By way of example and not limitation, on the home screen on the left side of FIGS. By way of example and not limitation, user B.B in the middle of FIGS. The display transitions to B's profile screen.

This profile screen differs from the example shown on the right side of FIG. Under the icon and user name representing B.B's profile, user B.B. A second unknown icon UIC2 is displayed as information about B's safety. In addition, below the button for making a talk with the user, the button for making a voice call with the user, and the button for making a video call with the user, the 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, in the middle profile screen of FIGS. When the safety registration request button BT2b for B is tapped by the user, safety registration request confirmation information SRI2 is displayed superimposed on the profile screen as shown on the right side of FIG. 5-6, for example and not limitation.

The safety registration request confirmation information SRI2 includes, as a non-limiting example, an image related to the icon image of the safety confirmation application, characters "A request for safety registration has been made to BB", and a safety registration request. and an OK button indicated by an icon including characters "OK" for confirming that the request has been made and ending the display of the safety registration request confirmation information SRI2.

The left side of FIG. 5-7 shows user B. 3 shows an example of a talk room screen displayed on the display unit 24 of B's terminal 20B.
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, as an example and not as a limitation, user B. Characters ("safety confirmation service" in this example) indicating that B is a talk room for talking with an OA account of a safety confirmation service registered in the messaging application as an official account are displayed. .

In the talk area, as an example, not as a limitation, as content from the OA account, the text "This is a safety confirmation response service 20XX/08/04 9:39 An earthquake occurred off the coast of Ibaraki prefecture." The disaster occurrence content DCT1 included is displayed.
In addition, below that, as content from the OA account, "Safety registration request The following friends are requesting safety registration", User A. Safety registration request content RCT1 including an icon image of A, a user name, and an answer button BT4b for answering the request is displayed.

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

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

The safety registration request confirmation information SRI3 includes, as a non-limiting example, an image related to the icon image of the safety confirmation application, characters "A request for safety registration has been made to BB", and a safety registration request. An OK button indicated by an icon including characters "OK" is displayed for confirming that the request has been made and ending the display of the safety registration request confirmation information SRI3.

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

In the display example of this talk room screen, user C.I. user B.C. Although a safety registration request has been made for B, no new safety registration request content is displayed in the talk area, and the display screen is the same as that on the left side of FIG. 5-7.

The left side of FIG. 5-8 shows user B. 3 shows an example of a talk room screen displayed on the display unit 24 of B's terminal 20B. Since this talk room screen is the same as the display screen on the left side of FIG. 5-7, the description thereof is omitted.

By way of example and not limitation, user A.A. User B.A. After the safety registration request is made to user C.B as the other party, user C.B is sent as described above. user B.C. Assume that a safety registration request is made to B. Further, other users (in this example, user D.D and user F.F) create user B.F. Assume that a safety registration request is made to B.
In this case, user B. B's terminal 20B displays, by way of example and not limitation, a talk room screen as shown on the right side of FIG. 5-8.

In this display example of the talk room screen, unlike the talk room screen shown on the right side of FIG. As contents from the OA account, "Safety registration request The following friends are requesting safety registration", user A. A's icon image and user name, user C.A. The icon image and user name of user D.C, user D.C. D icon image and user name, user F.D. A new safety registration request content RCT2 at "10:43" 60 minutes after "9:43" is displayed, including the icon image and user name of F, and the reply button BT4b for replying to the request. ing.

Information such as safety registration request content may be displayed on another screen, instead of being displayed on the screen of the talk room 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. The content of the safety registration request from A is sent to user A.A. It may be displayed on the talk room screen for talking with A, may be displayed on the friend list screen, or may be displayed on the talk list screen.

FIG. 5-9 is a flow chart showing an example of the flow of processing executed by each device in this modified example.
In this drawing, an example of processing executed by the control unit 21 of the terminal 20X, processing executed by the control unit 21 of the terminal 20Y, and processing executed by the control unit 11 of the server 10 is shown in order from the left.

Here, unlike the display screen,
- User X. of terminal 20X. X = user A.X of terminal 20A on the display screen. A.
- User Y. of terminal 20Y. Y=User of terminal 20B on display screen B.Y. B.
The processing in the case of is exemplified.
It should be noted that other terminals 20C and the like can also execute processing in the same manner as the terminals 20X and 20Y.

When the control unit of each device executes the safety confirmation process (X210, Y210, S210), as an example and not limitation, it executes the safety registration request process (X480, Y480, S480).

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

As an example and not a limitation, when 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, The safety registration request 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 the safety registration request request information with the account of the terminal 20Y as the safety registration request account is received via the communication I/F 14 (S4410y).
If it is determined that the safety status registration request request information for terminal 20Y has been received (S4410y: YES), the control unit 11 of the server 10 satisfies the composite setting condition regarding the terminal 20 (terminal 20Y in this case) of the safety status registration request account. It is determined whether or not (S4420y). Composite setting conditions will be described later.

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

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

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

The control unit 21 of the terminal 20Y controls, as an example and not a limitation, the user X. of the terminal 20X. When making a safety registration request for X, safety registration request 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 steps S4410x to S4430x using the safety status registration request account as the account of the terminal 20X. Each step, by way of example and not limitation, can be performed in the same manner as S4410y-S4430y.

In addition, the control unit 21 of the terminal 20X performs the same processes as X4410y and X4420y using the account of the other terminal 20 as the safety status registration request account. The control unit 11 of the server 10 executes the same processing as steps S4410x to S4430x while changing the safety status registration request account.

The same applies to other terminals 20 as well.

The control unit 21 of the terminal 20Y determines whether or not the safety registration request information has been received via 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 causes the display unit 24 to display the received safety registration request information (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 as well.

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 processing (X490, Y490, S490). Here, as a judgment condition for terminating the process, as an example, not a limitation, a case where a specific period (one week as an example, not a limitation) has passed since the date and time of the disaster, or based on the user input of the server 10 For example, when it is selected that the confirmation service is suspended.

If it is determined to end the process (X490: YES, Y490: YES, S490: YES), the control unit 21 of each terminal 20 and the control unit 11 of the server 10 end the process.

If it is determined not to terminate the process (X490: NO, Y490: NO, S490: NO), the control unit 21 of each terminal 20 and the control unit 11 of the server 10, for example and not limitation, perform the safety confirmation process again. Execute (X210, Y210, S210).

The same applies to other terminals 20 as well.

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

Here, as an example and not as a limitation, a 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 request account.
"Retransmission setting condition": A condition for retransmitting the safety registration request information after transmitting the safety registration request information to the terminal 20 of the safety registration request account.

By way of example and not limitation, initial transmission setting conditions include the following examples.
(X1). When the server 10 receives for the first time the safety registration request information for the terminal 20 of one safety registration request account.
(X2). When the server 10 receives the safety registration request 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 the safety registration request information for the terminal 20 of one safety registration request account from the terminal 20 of one safety registration request account.
(X4). When the server 10 receives the safety registration request request information for the terminal 20 of one safety registration request account from the terminal 20 of one safety registration request account M times (“M” is a natural number).
(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 (not limited to, but as an example, "every hour 0 minutes 0 seconds").
(X6). After the server 10 receives the safety registration request information for the terminal 20 of one safety registration request account for the first time, a first set time (not limited to, but as an example, "five minutes") has passed.
(X7). When the server 10 receives the safety registration request request information for the terminal 20 of one safety registration request account for the first time, and then transmits the disaster information again.
(X8). Any combination of (X1) to (X7) above.

In addition, the retransmission setting conditions include the following examples, not as a limitation.
(Y1). When the server 10 receives the safety registration request request information for the terminal 20 of one safety registration request account P times (“P” is a natural number). Note that the 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 conditions are satisfied.
(Y2). The server 10 receives safety registration request request information for the terminal 20 of one safety registration request account for the first time from the terminal 20 of the safety registration request account different from the terminal 20 of the safety registration request account that satisfies the initial transmission setting conditions. if you did this.
(Y3). From the terminal 20 with a safety registration request account different from the terminal 20 with a safety registration request account for which the server 10 satisfies the initial transmission setting conditions, safety registration request information is sent Q times to the terminal 20 with one safety registration request account. (“Q” is a natural number) When received. The Q times may or may not include the number of times the server 10 receives the safety registration request request information until the initial transmission setting conditions are satisfied.
(Y4). When the server 10 receives R times ("R" is a natural number) of safety registration request information for the terminal 20 of one safety registration request account from the terminal 20 of one safety registration request account that satisfies the initial transmission setting conditions. . Note that the 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 conditions are met.
(Y5). After the server 10 transmits the safety registration request information to the terminal 20 of one safety registration request account, the second set time (not limited to, but for example, "0:00:00 when the date changes" or "disaster occurrence time") +T hours later"("T" is a natural number)).
(Y6). After the server 10 has transmitted the safety registration request information to the terminal 20 of one safety registration request account, the second set time ("60 minutes" as an example, not a limitation) has passed.
(Y7). When the server 10 transmits the disaster information again after transmitting the safety registration request information to the terminal 20 of one safety registration request account.
(Y8). Any combination of (Y1) to (Y7) above.

By way of example and not limitation, the example of FIGS. 5-6 to 5-8 is an example when 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) as an example and not a limitation.

As an example and not a limitation, when the terminal 20Y performs a safety registration request operation for the terminal 20X, the first safety registration request 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 causes the display unit 24 to display the first safety registration request information (timing "TM630").

Thereafter, as an example and not a limitation, when the terminal 20Y makes a safety registration request request to the terminal 20X again, second safety registration 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 causes the display unit 24 to display the second safety registration request information (timing "TM680").

The initial transmission setting condition and the retransmission setting condition can be set according to the following concept as an example and not as a limitation.

・First idea: Once the initial transmission setting conditions are met for one safety status registration request account, and safety registration request information is once transmitted, it is basically not resent. This prevents repeated transmission of the same type of information to the terminal 20 of the safety confirmation request account in an emergency when the communication bandwidth is tight and the operation time of the terminal 20 is likely to be limited. be able to. However, since there is a possibility that the user of the safety confirmation request account has forgotten to perform the safety confirmation registration, the safety registration request information is sent again as a reminder when the resend setting conditions are met.

・Second idea If the initial transmission setting conditions are satisfied for one safety status registration request account, the safety registration request information is immediately transmitted. After that, even if the retransmission setting condition is satisfied, the safety registration request information is immediately transmitted. This makes it possible to control the frequency with which the server 10 transmits the safety registration request information to the terminal 20 of the safety registration request account. can be released.

It should be noted that the composite setting condition may be a condition consisting only of the initial transmission setting condition. In this case, the safety registration request information is not resent.

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

In this modification, the setting conditions described above are based on the initial transmission setting conditions (not limited, 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) and based on a retransmission setting condition (not a limitation, but an example of a first setting condition to send the second information to the terminal after first receiving the first information for the user of the terminal). showing 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, the second information is transmitted to the terminal, and the first information for the user of the terminal is transmitted. After first receiving the first information, the second information regarding safety confirmation is sent to the terminal based on the conditions for sending the second information to the terminal based on the first set conditions, and the safety of the user of the terminal is asked. be able to

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

In this case, the retransmission setting condition is the safety registration request information received by the server 10 after the server 10 first receives the safety registration request request information (not a limitation, but an example of the first information). However, it is possible to include a condition for transmitting safety registration request information (an example of second information, not limitation) to the terminal 20 of the user of the safety registration request account based on the number of safety confirmation request information (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 and the first information, the second information is transmitted to the terminal based on the number of the first information received by the server. Based on the conditions, second safety confirmation information can be sent to the terminal to inquire about the safety of the user of the terminal.

In this case, the retransmission setting condition is based on information such as information indicating that a disaster has occurred again (not a limitation, but an example of disaster-related information) based on the safety registration request information (not a limitation, but a second information example) to the terminal 20 of the user of the safety status registration request account.
As an example of the effect of the embodiment obtained by such a configuration, the second information regarding safety confirmation is transmitted to the terminal based on the first information and the condition for transmitting the second information to the terminal based on the information regarding the disaster. to inquire about the safety of the terminal user.

Also, in this case, the safety registration request information (not limited, but an example of the second information) is a chat room (not limited, but a chat example of a room).
As an example of the effect of the embodiment obtained by such a configuration, the second information regarding safety confirmation is displayed in a chat room that includes the terminal user, so that the terminal user can easily understand the safety information. can ask

<Fifth Modification (2)>
In the above modified example, 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, the server 10 does not transmit the safety registration request information to the terminal 20 of the safety registration request account even if the initial transmission setting condition and the retransmission setting condition are satisfied when the transmission stop setting condition described later is satisfied. You may do so.

The left side of FIG. 5-12 shows user B. 3 shows an example of a talk room screen displayed on the display unit 24 of B's terminal 20B. Since this talk room screen is the same as the display screen on the left side of FIG. 5-7, the description thereof is omitted.

As a non-limiting example, 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 FIG. 5-12, the home screen shown in the center of FIG. The display transitions to the screen.

In this home screen, unlike the home screen shown on the left side of FIG. 4-1, an icon image and user name (in this example, "user B.B. ”) is displayed.

By way of example and not limitation, in the safety registration area R1 in the center of FIG. User B is tapped by user B, and the text "I am injured" is displayed as a template for the safety message. After being selected by user B.B, the register button BT3 is activated by user B.B. User A.B when tapped by user A.B. 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 the same as the talk list screen on the right side of FIG. 1-19, so the description is omitted.

By way of example and not limitation, in the talk list screen on the right side of FIG. By way of example and not limitation, user B.B on the left side of FIG. The display transitions 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 ("User A.A" in this example) of the messaging application of the user of this terminal 20B are displayed on the right part of the top of the screen. ) is displayed. Also, user B. Below the icon and username representing B.B's profile is the user B.B. A second danger icon DIC2 is displayed as information about B's safety.

By way of example and not limitation, in the left profile screen of FIG. When the user taps the safety registration request button BT2b for B, safety registration request confirmation information SRI4 shown in the center of FIG.
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 B has answered the safety registration request, user A. User B.A. Assume that a safety registration request is made to B.
In this case, user B. B's terminal 20B displays, by way of example and not limitation, a talk room screen as shown on the right side of FIG. 5-13.

In this talk room screen, user A. User B.A. Even though a safety registration request has been made for B, the safety registration request content from the OA account corresponding to the new safety registration request is not displayed in the chat area, similar to the left side of Figure 5-12. is displayed on the screen.

In this modified example, the transmission stop setting conditions include the following examples, not as a limitation.
(Z1). When the server 10 receives the safety confirmation registration information from the terminal 20 of one safety registration request account.
(Z2). When the server 10 receives the safety registration request 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 V times ("V" is a natural number) for the terminal 20 of one safety registration request account from the terminal 20 of a specific safety registration request account.
(Z4). When the third set time (as an example, not as a limitation, when it is "time of disaster + 72 hours later").
(Z5). After the server 10 has transmitted the safety registration request information to the terminal 20 of one safety registration request account, the third set time (not limited to, but as an example, "36 hours") has passed.
(Z6). When the server 10 transmits the disaster information again.
(Z7). Any combination of (Z1) to (Z6) above.

As an example and not a limitation, the examples in FIGS. 5-12 and 5-13 are examples when 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) as an example and not limitation. .

As an example and not a limitation, when the terminal 20Y performs a safety registration request operation for the terminal 20X, the first safety registration request 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 causes the display unit 24 to display the first safety registration request information (timing "TM730").

After that, as an example and not a limitation, safety confirmation processing is executed, and when an input operation of the safety confirmation registration information is received at the terminal 20X, the 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").
When the terminal 20Y receives the first safety information, the terminal 20Y executes display processing (timing "TM760").

After that, as an example and not a limitation, when the terminal 20Y performs a safety registration request operation for the terminal 20X, second safety registration 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 safety information regarding the account of the terminal 20X is received, the control unit 21 of the terminal 20Y may not accept the safety registration request operation for the account of the terminal 20X thereafter.

In this modification, the server 10, based on the transmission of safety registration request information (not limited, but an example of second information), safety confirmation registration information (not limited, third information including information on the safety of the user of the terminal) ) is received by the communication I/F 14 . Then, based on the reception of this safety confirmation registration information, the server 10 receives safety confirmation request request information (not a limitation, but an example of third information) for the safety confirmation 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, after receiving from the terminal the third information including the information regarding the safety of the user of the terminal, Based on this, when the first information for the terminal user is received after receiving the third information, the safety of the terminal user is temporarily confirmed by not transmitting the second information based on the first information. In this case, the user of the terminal does not have to check again, and the user of the terminal does not feel annoyed. In addition, unnecessary communication can be avoided, and the amount of communication can be reduced.

<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 to this. As an example and not a limitation, the setting condition (composite setting condition) may be determined by the terminal 20 of the safety status registration request account.

In this case, when the control unit 11 of the server 10 receives the safety registration request information for the terminal 20X of the safety registration request account from the terminal 20Y of the safety registration request account, it 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 or not the setting condition (composite setting condition) is satisfied. Then, when determining that the setting condition (composite setting condition) is established, 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 to this. As an example and not a limitation, the setting condition (composite setting condition) may be determined by the terminal 20 of the safety registration request account.

In this case, the control unit 21 of the terminal 20Y of the safety registration request account determines whether or not the setting condition (composite setting condition) is satisfied when the safety registration request request operation is performed on the terminal 20X of the safety registration request account. do. Then, when determining that the setting condition (composite setting condition) is established, the control unit 21 of the terminal 20Y transmits the safety registration request information to the server 10 .
When the control unit 11 of the server 10 receives the safety registration request information for the terminal 20X from the terminal 20Y, it 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 it.

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

Note that if the terminal 20 of the safety registration request account is allowed to determine the setting condition (composite setting condition), it cannot be determined whether or not another terminal 20 has transmitted the safety registration request information to the terminal 20 of the safety registration request account. . Therefore, in this case, the setting conditions (composite setting conditions) are the number of safety registration request operations on the own terminal, the time, the time after accepting the safety registration request operation on the own terminal, whether the disaster information was received again, etc. Limited to

<Sixth embodiment>
The sixth embodiment is an embodiment in which the terminal 20 of the safety confirmation request account can confirm the safety confirmation request account that requested the safety confirmation request to the safety confirmation registration request account.

The content described in the sixth embodiment can be applied to each of the other embodiments and each of the other modifications.
Moreover, the same code|symbol is attached|subjected about the component same as an already-appearing component, and description for the second time is abbreviate|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 FIG. 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, the safety information that requested the user (user B.B) to make a safety registration request is displayed. A "friend confirmation" button BT6 is provided for confirming the registration request account (friend). When this "friend confirmation" button BT6 is tapped, a display as shown on the right side of FIG. 6-1 is made.

Specifically, a safety registration request requesting user list area SRR including information on a safety registration requesting account that has requested a safety registration request to itself (user B.B) is displayed so as to rise from the bottom of the screen. . In this example, along with the text "The following friends are requesting your safety registration", in this example, the user A. A, user C. C, user D.C. D, user F. Icons and user names are displayed for four users of F, respectively. An icon based on the safety status information registered by the user is superimposed on the icon of each user.

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

Here, unlike the display screen,
・Safety registration request account=User Y. of terminal 20Y. Y's account=Users of terminal 20A and terminals 20C to 20F on the display screen Safety status registration request account=User of terminal 20X. X's account = user B.X of terminal 20B on display screen. B.
The processing in the case of is exemplified.

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

As an example and not a limitation, when the terminal 20Y performs a safety registration request operation for the terminal 20X, the first safety registration request 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 causes the display unit 24 to display the first safety registration request information (timing "TM830").

After that, as an example and not a limitation, when the other terminal 20 performs a safety registration request operation for the terminal 20X, the 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 safety registration request information transmitted from other terminals 20 to the server 10 .

Then, as an example and not a 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 transmits the safety registration request information to the terminal 20X based on the user operation for the first safety registration request information, as an example and not a limitation. Determine whether confirmation of the registration request account has been selected. When it is determined that confirmation of 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 safety registration request user information request information is received from terminal 20X via communication I/F 14 (timing "TM860"), control unit 11 of server 10 sends safety registration request user list information to terminal 20X via communication I/F 14. transmit (timing "TM870").
Here, the safety registration request user list information includes, as a non-limiting example, information related to the safety registration request account in the safety registration request information for the terminal 20X received before the timing "TM860" (as an example, not a limitation). (including application IDs, user names, etc.).

When the safety registration requesting user list information is received from the server 10 via the communication I/F 22, the control unit 21 of the terminal 20X displays the received safety registration requesting 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 a limitation, but an example of the second information), the safety registration request information is displayed and the safety registration request account is displayed. The display unit 24 displays a display related to the safety registration requesting account that requested the safety registration request to . Then, on the terminal 20 of the safety registration request account, the server 10 transmits the safety registration request information (not limited but an example of the first information) based on the input by the user of the safety registration request account to the display. A configuration is shown in which the information of the transmitted safety registration request account (not limited but an example of the information of the user who transmitted the first information) is transmitted to the terminal 20 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 regarding safety confirmation is displayed on the display unit on the terminal based on the reception of the second information, and input by the user of the terminal to the first display is performed. By transmitting the information of the user who transmitted the first information to the terminal based on , it is possible to notify the user of the terminal of the information of the user who transmitted the first information.

Also, in this case, the server 10, based on the reception of the safety registration request information for the safety registration request account transmitted from the terminal 20 of one safety registration request account (an example of the first terminal, not limited), The registration request information (not a limitation, but an example of the second information) is transmitted to the terminal 20 of the safety status registration request account via the communication I/F 14 . Also, after receiving the safety registration request request information for the safety registration request account from the terminal 20 of one safety registration request account, the server 10 sends the safety registration request request information for the safety registration request account to another safety registration request account. terminal 20 (not limited, but an example of a second terminal) through the communication I/F 14 . If the set condition is not satisfied, the server 10 sends safety registration request information based on the safety registration request information received from the terminal 20 (second terminal) of another safety registration request account to the safety registration request account. The control unit 11 controls not to transmit to the terminal 20 . In this case, the server 10, based on the input by the user of the safety registration request account in response to the above display, is the one safety registration request account that transmitted the safety registration request information (not a limitation, but an example of the first information). information (not limited, but an example of information of the user of the first terminal) and information of another safety registration request account (not limited, but an example of information of the user of the second terminal) are received by the communication I / F 14 The configuration for transmission to the terminal 20 of the safety registration request account is shown.
As an example of the effect of the embodiment obtained by such a configuration, after receiving the first information for the user of the terminal from the first terminal, the first information for the user of the terminal is received from the second terminal, and the set condition is not satisfied, the second information based on the first information received from the second terminal is not transmitted to the terminal, thereby preventing the user of the terminal from feeling annoyed. Also, in the terminal, based on the reception of the second information, the first display regarding safety confirmation is displayed on the display unit, and the first information is transmitted based on the input by the user of the terminal to the first display. By transmitting the user information including the terminal user information and the second terminal user information to the terminal, the first terminal user information and the second terminal user information, which transmitted the first information, are transmitted to the terminal. information can be communicated to the user of the terminal.

<Sixth modification (1)>
In the above embodiment, when the safety registration request user information request operation is executed on the terminal 20X of the safety registration request account, the safety registration 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 modified example.
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 user list information is transmitted from the server 10 to the terminal 20B at the timing described later. As a result, the display on the display unit 24 of the terminal 20B is displayed as shown on the right side of FIG. 6-3. This screen corresponds to the screen on the left side of FIG. 6-3. B is user A.B. A and user C.A. Safety registration request content RCT7 indicating that safety registration is requested from C and C is shown.

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

Here, the conditions for transmitting the safety registration request user list information are not limited to the following examples.
- A set period of time (eg, not limited to "30 minutes") has passed since the safety registration request information was last received from any one terminal 20 .
- When the set time ("noon" as an example, not as a limitation) has arrived after the last safety registration request information was received from any one terminal 20;
- When safety registration request information is received from any one terminal 20 for a set number of times or more, or more than the set number of times.
- A set period of time ("30 minutes" as an example, not a limitation) has passed since the last safety registration request information was received from each terminal 20;
- When the set time ("noon" as an example, not as a limitation) has come after the last safety registration request information was received from each terminal 20;
- When safety registration request information is received from each terminal 20 more than a set number of times or more than the set number of times.
- When the safety confirmation registration information is received from the terminal 20X.
- When transmitting the safety registration request information to the terminal 20X.

Note that the processing in this modified example may be performed as follows.
As an example and not a limitation, when the control unit 11 of the server 10 receives the safety registration request request information from the terminal 20 of the safety registration request account, the terminal Send information about the received safety registration request account to 20X. In the following, as an example and not as a limitation, information related to a safety registration request account corresponding to individual safety registration request request information will be referred to as "safety registration request user information".

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

Here, the conditions for displaying the user requesting the safety registration request include, but are not limited to, the following examples.

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

<Seventh embodiment>
The seventh embodiment is an embodiment in which, in the safety confirmation service, safety confirmation registration is not accepted when the safety registration period for one disaster has expired.

The content described in the seventh embodiment can be applied to each of the other embodiments and each of the other modifications.
Moreover, the same code|symbol is attached|subjected about the component same as an already-appearing component, and description for the second time is abbreviate|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, user A.A. A, user C. C, user D.C. D, user F. Under the safety registration request content RCT8 indicating that safety confirmation registration is being requested by four users of F, safety registration due to the earthquake that occurred at "09:39 on August 4, 20XX" from the OA account is displayed. Safety registration stop confirmation content SCT1 indicating that the safety registration is 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 made.

In this example, based on the fact that the safety registration period has already passed, the text "The safety registration period has expired" and a character image are displayed in the center of the screen on the left side of Figure 7-1. , and an "OK" button. When the "OK" button is tapped, the display of the safety confirmation registration acceptance period end information EPI1 is erased, but the safety confirmation registration is not accepted and user B. B is configured so as not to be able to perform safety confirmation registration.

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

Here, unlike the display screen,
・Safety registration request account=User Y. of terminal 20Y. Y's account=Users of terminal 20A and terminals 20C to 20F on the display screen Safety status registration request account=User of terminal 20X. X's account = user B.X of terminal 20B on display screen. B.
The processing in the case of is exemplified.

As an example and not a limitation, when the terminal 20Y performs a safety registration request operation for the terminal 20X, the first safety registration request 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 causes the display unit 24 to display the first safety registration request information (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 and the safety registration request process based on an input operation by the user of the server 10, for example and not limitation. I do. When it is determined to end the safety confirmation process and the safety registration request process, the control unit 11 of the server 10 transmits the safety information in response to the reception of the safety confirmation registration information and the safety registration request information in response to the reception of the safety registration request information. to stop sending

In the safety confirmation registration acceptance period termination process, the control unit 11 of the server 10 performs the safety confirmation process and the safety registration process based on whether or not a set period has passed since the disaster occurrence date and time. It may be determined whether or not to end the request processing. Further, as an example, not limitation, the control unit 11 of the server 10 may determine whether or not to end the safety confirmation process and the safety registration request process based on the safety confirmation reception end date and time in the disaster information. good.

After that, when the terminal 20X accepts the safety confirmation registration information based on the input operation for the first safety registration request information, 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").

It is not essential that the terminal 20Y executes the safety registration request operation and the terminal 20X receives the safety registration request information.

If the control unit 11 of the server 10 determines to terminate the safety confirmation process and the safety registration request process at the timing "TM940", and the safety confirmation registration information is received after the timing "TM940" (as an example, not as a limitation, the timing "TM960"), and transmits 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 causes the display unit 24 to display the received safety confirmation registration acceptance period end information (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 when the safety registration request request information is received after the timing "TM940", the safety confirmation registration acceptance is performed. The period end information may be transmitted to the terminal 20 of the safety registration request account.

Further, as an example and not as a limitation, when the control unit 11 of the server 10 receives the above-described safety registration request request user information request information from the terminal 20X after the timing “TM940”, the safety confirmation registration acceptance period end information is sent to the terminal 20X. 20X.

<Effects of the seventh embodiment>
In the present embodiment, 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, when the safety confirmation registration acceptance period (not a limitation, but an example of acceptance of safety confirmation) has ended, the server 10, based on the input by the user of the safety registration request account for the first display, Shows a configuration for transmitting safety confirmation registration acceptance period end information (not a limitation, but an example of information regarding the completion of acceptance of safety confirmation) to the terminal 20 of the user of the account requesting safety confirmation via the communication I/F 14. there is
As an example of the effect of the embodiment obtained by such a configuration, when the terminal displays the first display regarding the safety confirmation on the display unit based on the reception of the second information, and the acceptance of the safety confirmation is finished, Based on the terminal user's input to the first display, the terminal user is notified that the acceptance of the safety confirmation has been completed by transmitting information to the terminal that acceptance of the safety confirmation has been completed. can let you know.

<Seventh Modification (1)>
In the above-described embodiment, when it is determined in the safety confirmation registration acceptance period termination process that the safety confirmation process or the safety registration request process is to be terminated, the control unit 11 of the server 10 subsequently generates the safety confirmation registration information and the safety registration request request. Although the example in which the safety confirmation registration acceptance period end information is returned when the information is received has been exemplified, the present invention is not limited to this.
As an example and not a limitation, when the safety confirmation registration acceptance period for the first disaster information has expired, the control unit 11 of the server 10 sends the second disaster information. Safety confirmation registration may be accepted.

FIG. 7-3 is a data configuration example of an account management database 155B, which is an example of the account management database 155 in this modification.
Account management data is stored in the account management database 155B 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.

Application IDs and friend management data can be configured in the same manner as account management database 155A, for example and not limitation.

The safety registration data is data for storing registration regarding safety associated with the account of this application ID. are stored in association with each other.

The disaster ID is information for identifying a disaster that has occurred or disaster information corresponding 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, the server 10 sets and stores a unique value (unique value) for each disaster (disaster information). be.

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, for example and not limitation. Arbitrary elements of the safety status information, the safety comment information, and the 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.
The screen on the left side of Figure 7-4 shows that the safety status registration will be suspended due to the earthquake that occurred at 9:39 on August 4, 20XX from the OA account (not a limitation, but an example of the first disaster). Below the registration stop confirmation content SCT1, disaster occurrence content DCT2 indicating that an earthquake (not a limitation, but an example of a second disaster) occurred at "19:23 on August 14, 20XX" from the OA account is displayed. It is As an example and not a limitation, when the answer button BT4b in the safety registration request content RCT8 is tapped, a display such as that shown in the center of FIG. 7-4 is displayed.

Specifically, the safety confirmation registration acceptance period (safety registration period) for the first disaster has ended, but it is possible to register for the second disaster, so confirm whether or not to register your safety. Safety registration confirmation information RCI1 is displayed in a pop-up format in the center of the screen. When the "OK" button included in this information is tapped to return the display to the home screen, the display shown on the right side of FIG. 7-4 is displayed.

Information about the occurrence of the second disaster is displayed on this home screen.
Also, a safety registration area R1 for performing safety registration is displayed so as to rise from the bottom of the home screen. An example of the configuration of the safety registration area R1 is as described above, so description thereof will be omitted.

FIG. 7-5 is a timing chart showing, by way of example and not limitation, one example of the timing of the processing performed by each device in this embodiment.
First, as a non-limiting example, 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 the user of the server 10. Acceptance processing is executed (timing "TM1005"). In the first disaster safety confirmation registration acceptance process, the control unit 11 of the server 10 generates a disaster ID for linking with the first disaster. Note that the control unit 11 of the server 10 may transmit the first disaster information to each terminal 20 along with the first disaster safety confirmation registration acceptance process. Also, the first disaster information may include the 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 acceptance process based on the disaster situation information received from the disaster information server (not shown).

Next, as an example and not as a limitation, when the terminal 20Y performs a safety registration request operation for the terminal 20X, the first safety registration request 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 causes the display unit 24 to display the first safety registration request information (timing "TM1020").

Next, the control unit 11 of the server 10 executes safety confirmation registration acceptance period end processing for the first disaster (timing "TM1025").
After that, the control unit 11 of the server 10 executes the second disaster safety confirmation registration acceptance process for starting the safety confirmation process and the safety registration request process in the second disaster (timing "TM1030"). Note that the control unit 11 of the server 10 may transmit the second disaster information to each terminal 20 along with the second disaster safety confirmation registration acceptance process. Also, the second disaster information may include the disaster ID associated with the second disaster.

After that, when the terminal 20X accepts the safety confirmation registration information based on the input operation for the first safety registration request information, 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 the disaster ID associated with the first disaster.

It is not essential that the terminal 20Y executes the safety registration request operation and the terminal 20X receives the first safety registration request information.

The control unit 11 of the server 10 determines to end the safety confirmation process and the safety registration request process for the first disaster at the timing "TM1025", and includes the disaster ID linked to the first disaster after the timing "TM1025". When the safety confirmation registration information is received (as an example, not as a limitation, timing "TM1040"), the first disaster safety confirmation registration reception period end information indicating that the reception of safety confirmation registration for the first disaster has been completed It is transmitted to the terminal 20X of the safety registration account by F14 (timing "TM1045").

Further, as an example and not as a limitation, when the control unit 11 of the server 10 transmits the first disaster safety confirmation registration acceptance period end information, if the second disaster safety confirmation registration acceptance process is being executed, the safety confirmation for the second disaster The second disaster safety confirmation registration acceptance start information indicating acceptance of confirmation registration is transmitted to the terminal 20X of the safety registration account (timing "TM1050"). The second disaster safety confirmation registration acceptance start information may include the 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 displays the received first disaster safety confirmation registration acceptance period end information on the display unit 24 (timing "TM1055"). .
Further, when 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 indicating that safety confirmation registration for the second disaster including the second disaster information has started. It may be information related to acceptance display.

Note that the control unit 11 of the server 10 determines to end the safety confirmation process and the safety registration request process for the first disaster at the timing "TM1025", and after the timing "TM1025", the safety registration associated with the first disaster is completed. When the request request information is received, the first disaster safety confirmation registration acceptance period end information may be transmitted to the terminal 20 of the safety registration request account.

Also, when the control unit 11 of the server 10 receives the safety registration request information after the timing "TM1030", the control unit 11 may transmit the safety registration request request for the second disaster to the terminal 20 of the victim's safety registration request account. good.

When the control unit 11 of the server 10 determines to end the safety confirmation process and the safety registration request process for the first disaster in the safety confirmation registration acceptance period end process for the first disaster, the safety confirmation registration information is sent from the terminal 20. The first disaster safety confirmation registration acceptance period end information may be transmitted to each terminal 20 without receiving it.
In this case, the control unit 21 of the terminal 20X may perform control so as not to accept the safety confirmation registration for the first disaster upon receiving the first disaster safety confirmation registration acceptance period end information.

If the first safety confirmation registration information does not include a disaster ID, the control unit 11 of the server 10 determines that the timing at which the first safety confirmation registration information is received is after the timing "TM1025" and before the timing "TM1030". , the first disaster safety confirmation registration acceptance period end information may be transmitted to the terminal 20X of the safety registration account.
Further, when the disaster ID is not included in the first safety confirmation registration information and the timing at which the first safety confirmation registration information is received is after the timing "TM1025" and after the timing "TM1030", 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, when the control unit 11 of the server 10 receives the safety registration request user information request information for the first disaster from the terminal 20X after the timing "TM1030", the first disaster safety confirmation registration acceptance The period end information and the second disaster safety confirmation registration acceptance start information may be transmitted to the terminal 20X.

This modified example is a safety registration request based on the safety registration request information (not limited, but an example of the first information) for one disaster (not limited, but an example of the first disaster) on the terminal 20 of the safety registration account. Based on the reception of the information (an example of the second information, not limitation), the first display described above is displayed on the display unit 24 for the one disaster. Then, the server 10 starts the safety confirmation registration acceptance period for one disaster (not a limitation, but an example of acceptance of a safety confirmation for the first disaster) ends, and another disaster (not a limitation, but an example of a second disaster). If the safety confirmation registration acceptance period (not a limitation, but an example of acceptance of safety confirmation for the second disaster) has started, based on the input by the user of the safety registration request account for the first display, the first Disaster safety confirmation registration acceptance period end information (not limited, but an example of information about the end of acceptance of safety confirmation for the first disaster) and second disaster safety confirmation registration acceptance start information (not limited, second An example of information about the start of acceptance of disaster safety confirmation) is transmitted to the terminal 20 of the user of the safety confirmation request account via the communication I/F 14.
As an example of the effect of the embodiment obtained by such a configuration, the terminal displays a first display regarding safety confirmation on the display unit based on the reception of the second information based on the first information of the first disaster, When the acceptance of safety confirmation for the disaster has ended and the acceptance of safety confirmation for the second disaster has started, the acceptance of the safety confirmation for the first disaster ends based on the input by the terminal user for the first display. and information about the start of acceptance of safety confirmation for the second disaster to the terminal. (2) It is possible to notify the user of the terminal that acceptance of safety confirmation for disasters has started.

In addition, 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 limited, but an example of the second information) at the terminal 20 of the safety registration request account. . Then, when the safety confirmation registration acceptance period (not a limitation, but an example of acceptance of safety confirmation) has expired, the server 10 receives information, through the communication I/F 14, indicating that the input to the first display is not accepted. The configuration for transmission to the terminal 20 of the safety registration request account is shown.
As an example of the effect of the embodiment obtained by such a configuration, when the terminal displays the first display regarding the safety confirmation on the display unit based on the reception of the second information, and the acceptance of the safety confirmation is finished, 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 cannot know whether the safety confirmation registration acceptance period has expired before sending the safety confirmation registration information, but the present invention is not limited to this. As an example, not limitation, the safety registration request information may include information regarding a safety registration period (a period during which safety registration is possible) and a safety registration time limit (end of safety registration).

Note that these pieces of information may be information on the display period for displaying the above-described first display on the display unit 24 (information on the display time limit). Further, it may be information (information on an input deadline) regarding an input period in which an input for answering a safety confirmation (safety registration) can be made from the first display described above.

The left side of FIG. 7-6 shows an example of a messaging application screen displayed on the display unit 24 of the terminal 20B in this modification.
In this screen, the safety registration request content RCT9 in the talk area includes a reply button BT4c including information on the remaining time until the reply deadline as information on the reply period during which the safety confirmation reply can be made.

In this example, safety registration is stopped at "9:41". Then, the remaining time until that time is displayed. If "9:41" arrives without answering about your safety, the display on the right side of Fig. 7-6 will appear.

In this example, under the safety registration request content RCT9, the safety registration stop confirmation content SCT1 indicating that the safety registration will be stopped due to the earthquake that occurred at "9:39 on August 4, 20XX" from the OA account is displayed. It is In addition, the display of the information about the reply period in the reply button BT4c of the safety registration request content RCT9 is erased, and the reply button BT4c is grayed out. I can't do it.

When the safety registration period or the safety registration deadline included in the safety registration request information has passed, the control unit 21 of the terminal 20X prompts the user to input the safety confirmation registration information based on the input to the safety registration request information, as an example, not as a limitation. You can choose not to accept it.

In this modification, the safety registration request information (an example of the second information, not limitation) includes information regarding the safety registration period, the safety registration deadline, and the like. Then, on the terminal 20 of the safety registration request account, the first display described above is displayed on the display unit 24 based on the reception of this safety registration request information (not a limitation, but an example of the second information). there is
As an example of the effect of the embodiment obtained by such a configuration, information on the expiration date for which the first display is displayed on the display unit of the terminal, or information on the expiration date that can be input to the first display is displayed. Upon receipt of the containing second information, a first indication regarding safety confirmation may be displayed to allow the user of the terminal to confirm the first indication.

<Seventh modification (3)>
In the above embodiment, the server 10 determines whether or not 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 configured to be able to determine whether or not to accept safety confirmation registration and safety registration request requests.

In this case, as an example and not a 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 or not 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 about the safety confirmation registration acceptance deadline. can be determined.
As an example and not a limitation, the control unit 21 of each terminal 20 can be configured not to accept transmission of safety confirmation registration information or a safety registration request request when the acceptance deadline has passed.

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

<Eighth embodiment>
The eighth embodiment relates to blocking of members in the safety confirmation service or friends in the messaging application.

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

The content described in the eighth embodiment can be applied to each of the other embodiments and modifications.
Moreover, the same code|symbol is attached|subjected about the component same as an already-appearing component, and description for the second time is abbreviate|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 am injured" and the current location are displayed. A state in which "Tsukuba City" is input and the registration button BT3 is tapped is shown.

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. B and not blocked by user B.B on the talk list. User B.B on which the second danger icon DIC2 is superimposed. In addition to the icon image of B and the user name, the aforementioned composite safety information "Tsukuba/I was 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.G. 8-1, and unlike the screen of terminal 20A in the center of FIG. 8-1, user B.B on the talk list User B.B on which the second danger icon DIC2 is superimposed. Only the icon image of B and the user name are displayed. In other words, the composite safety information "Tsukuba/I'm injured" is not displayed, and although it is known that it is "dangerous", the safety message and whereabouts are unknown.

It should be noted that in the terminal 20 of the blocked user, either one of the safety location information and the safety comment information may be displayed instead of not being displayed.

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

Here, unlike the display screen,
- Account to be blocked = User Y. of terminal 20Y. Y's account = user A.Y of terminal 20A on the display screen. A.
• Block execution account = User X. of terminal 20X. X's account = user B.X of terminal 20B on display screen. B.
The processing in the case of is exemplified.

As an example and not a limitation, the control unit 21 of the terminal 20X sends block request information for blocking content from the block target account (in this case, the account of the terminal 20Y) to the server through the communication I/F 22 based on the user's 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, as an example and not as a limitation, in the chat process, if the control unit 11 of the server 10 receives message transmission request information from the terminal 20Y to the terminal 20X, the control unit 11 sends message information based on the message transmission request information to the terminal 20X. do not send

Next, as an example and not a limitation, when the terminal 20Y performs a safety registration request request operation for the terminal 20X, the first safety registration request 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 condition is 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 causes the display unit 24 to display the first safety registration request information (timing "TM1125").

When receiving safety registration request information from the terminal 20Y of the blocked account to the terminal 20X of the block execution account, the control unit 11 of the server 10 does not transmit the safety registration request information to the terminal 20X of the block execution account. can be

As a non-limiting example, 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 receives the received first safety status information. The status information is transmitted to the server 10 through the communication I/F 22 (timing "TM1130").
Further, as an example and not a limitation, the control unit 21 of the terminal 20X accepts safety comment information based on an input operation on the third display in the first safety registration request information, and receives the received first safety comment information. safety comment information is sent to the server 10 via the communication I/F 22 (timing "TM1135").

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

The control unit 11 of the server 10 receives the first safety status information and the 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").
In addition, the control unit 11 of the server 10 transmits the first safety information including the first safety status information and the 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").

The combinations of safety confirmation registration information received in the second display and the third display are not limited to the above combinations.
Here, the safety registration information input to the second display is referred to as "first safety information", and the safety registration information input to the third display is referred to as "second safety information". When the first safety information and the second safety information are input to the terminal 20 of the blocked account, safety information including only the first safety information is transmitted to the terminal 20 of the blocked account. In addition, safety information including the first safety information and the second safety information is transmitted to each terminal 20 other than the blocked account.

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

FIG. 8-3 is a table showing combinations of first safety information and second safety information.
Here, as a non-limiting example, safety status information, safety comment information, and safety location information are used as components of the safety registration information. 2 safety information can be defined.

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 is more time-consuming than inputting safety status information. It is highly conceivable to omit the entry of location information. Therefore, when only safety status information is displayed on the terminal 20 of the blocked account, it is possible to distinguish whether safety comment information and safety location information are not displayed or input by the user of the blocked account. Can not do it. Therefore, it is difficult for the user of the account to be blocked to recognize that the user of the block execution account has blocked it.

When receiving safety confirmation registration information from the terminal 20X of the block execution account, the control unit 11 of the server 10 does not transmit the safety confirmation information based on the received safety confirmation registration information to the terminal 20Y of the block target account. good too.

<Effects of the eighth embodiment>
In this embodiment, the first display described above 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. A second display and a third display different from the second display are displayed on the display unit 24 based on an input for one display. Based on the input to the second display displayed on the terminal 20 of the safety confirmation request account, the server 10 receives the first 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 to the third display, another safety information (not limited to, the second safety information ) is received by the communication I/F 14 . Then, the server 10 identifies a user associated with the user of the safety status registration request account, such as being registered as a friend by the user of the safety status registration request account (not limited, but an example of a user associated with the user of the terminal). Shows a configuration for transmitting one piece of safety information (first safety information) to the terminal 20 and transmitting other safety information (second safety information) to the terminal 20 of the user set by the user of the account requesting to register the safety status. ing.
As an example of the effect of the embodiment obtained by such a configuration, the first display regarding 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. , and a third display that is different from the second display. Then, based on the input for the second display, the first safety information regarding the safety input by the user of the terminal is received from the terminal, and based on the input for the third display, the second safety information regarding the safety input by the user of the terminal is received. Safety information can be received. Also, the first safety information can be transmitted to a user associated with the user of the terminal to notify the user of the terminal of the safety of the terminal. In addition, the second safety information can be sent to a user set by the user of the terminal to inform the safety of the user of the terminal.

Also, in this case, the user set by the user of the safety status registration request account is the user who is associated with the user of the safety status registration request account, such as being registered as a friend by the user of the safety It is possible to include users other than users blocked by the user of the safety registration request account.
As an example of the effect of the embodiment obtained by such a configuration, the users set by the terminal user include users other than the users blocked by the terminal user among the users associated with the terminal user. The second safety information can be transmitted to users other than users blocked by the user of the terminal.

<Eighth modification (1)>
In the above embodiment, safety information including only the first safety information is transmitted to the terminals 20 of the blocked accounts, and the first safety information and the second safety information are transmitted to the terminals 20 other than the blocked accounts. Although it is assumed that the safety information is transmitted, the present invention 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. can be

In this case, as an example and not a limitation, when the control unit 11 of the server 10 receives the block request information from the block execution account terminal 20X, the block execution account information (as an example, not a limitation) is sent to the block target account terminal 20Y. , application ID).
As a non-limiting example, the control unit 21 of the terminal 20Y of the blocked account, after receiving the safety display block request information, sets the block execution account as the safety registration account, and sends the 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 embodiment>
The ninth embodiment is an embodiment in which it is possible to easily view the safety confirmation registration status of members in the safety confirmation service or friends in the messaging application.

The content described in the ninth embodiment can be applied to each of the other embodiments and each of the other modifications.
Moreover, the same code|symbol is attached|subjected about the component same as an already-appearing component, and description for the second time is abbreviate|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 the chat screen with the OA account of the messaging application described above, 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 on the right side of FIG. 9-1 is displayed.

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

Further, in this example, user B. The safety registration button BT1 is highlighted (blinking as an example, not a limitation) based on the fact that B has not yet registered his safety.

Instead of transitioning to the friend list screen as described above, the screen may be transitioned to the talk list screen, and the screen may be transitioned to a screen displaying a list of safety confirmation registration statuses.

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

・Display safety registration request information in the smart chat area (tap to transition to safety confirmation registration screen)
・Transition from the safety registration request information to the safety confirmation registration screen by pushing the application

FIG. 9B is a diagram showing an example of a screen displayed on the display unit 24 of the terminal 20B in this modified example.
The left side of FIG. 9-2 shows a message 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. The safety registration button BT1 is displayed because B has not yet registered his safety.
Under it, user B. A list of icons and user names of users who have made a safety registration request to B is displayed.

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

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

In addition, when the area where a list of users who have made safety registration requests is displayed (4 users in this example) on the screen on the left side of Figure 9-2 is tapped, the home screen on the right side of Figure 9-2 is displayed. may be displayed.

As an example, not limitation, the safety registration request information may be displayed at the top of any talk room screen. Then, based on the user's operation on the safety registration request information displayed at the top, the screen may be changed to the safety confirmation registration screen.

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

As an example and not a limitation, the control unit 11 of the server 10 aggregates the safety status information and the safety location information received from each terminal 20, and obtains the bias in areas where the safety status information is "dangerous". Then, the control unit 11 of the server 10 calculates the rescue target area information, which is the position information regarding the area where "dangerous" 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 .

<Another embodiment (2)>
In the above-described embodiment, the example of transmitting the safety registration request request information to prompt the terminal 20 of the safety registration request account to input and transmit the safety confirmation registration information was exemplified, 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.

As an example and not a limitation, an example of a request to prompt repayment of a debt (hereinafter referred to as a “request”) will be illustrated as request information.
Further, hereinafter, the account of the user who is forced to repay the debt is referred to as "requested request account", and the account of the user who requests repayment of the debt to the requested request account is referred to as "requested request account". Here, the desired request account is a plurality of accounts, which are referred to as a "first desired request account" and a "second desired request account" as an example and not as a limitation.

As an example and not limitation, the terminal 20 of the first demand request account transmits to the server 10 first demand request information for conveying a demand to the demand request account based on the user's operation.
When receiving the first request request information from the terminal 20 of the first request request account, the control unit 11 of the server 10 determines whether or not the setting condition (composite setting condition) is satisfied. Then, when determining that the setting condition (composite setting condition) is established, the control unit 11 of the server 10 receives the first request information (in this example, prompting repayment of the debt) based on the first request request information. information) to the terminal 20 of the requested request account.
The control unit 21 of the terminal 20 of the requested request account causes the display unit 24 to display the received first request information.

Next, the terminal 20 of the second demand requesting account transmits to the server 10 the second demand request information for conveying the demand to the requested requesting account based on the user's operation as an example and not limitation.
When receiving the second request request information from the terminal 20 of the second request request account, the control unit 11 of the server 10 determines whether or not the 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 transmits the 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 request 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 demand requesting account including multiple accounts notifies a desired demanding account to a demanded demanding account, the following correspondence can be applied as an example and not as a limitation.
・"Safety registration request information" = "request request information"
・"Safety registration request information" = "request information"
・"Safety status 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 information at an arbitrary timing can be controlled in the same manner as the control based on the composite setting conditions in the fifth embodiment, as an example and not as a limitation. That is, considering the above embodiment, when receiving the safety registration request request information for one requested request account for the first time, the server 10 transmits the request information to the terminal 20 of the requested request account. Then, when the server 10 receives the safety registration request request information for the requested request account after that, it is possible to implement control such that the request information is not transmitted to the terminal 20 of the requested request account again. In addition, when the server 10 receives the safety registration request request information for the requested request account and satisfies a predetermined condition, the server 10 can perform control such that, as a reminder, the request information is sent again to the terminal 20 of the requested request account. .

Note that the terminal 20 of the request requesting account may transmit to the server 10 a transmission request for any content (referred to as "content transmission request information") to the terminal 20 of the requested request account. When receiving the content transmission request information, the control unit 11 of the server 10 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. can be

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

<Others>
Basically, the content realized by the messaging application (messaging service) described in the above embodiments and modifications can also be similarly applied to the safety confirmation application (safety confirmation service) described in the fifth embodiment. .

1 communication system 10 server 20 terminal 30 network

Claims (21)

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 the first information associated with the chat information related to the user of the first terminal on a display of the terminal is performed by the terminal. 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, the communication unit receives the second information by the terminal. . The program according to claim 2,
The second information is displayed in a first chat room including the user of the first terminal and the user of the terminal. The program according to claim 3,
When the first 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 performed by the terminal. The program according to claim 2 or claim 3,
When the information of the user of the first terminal is displayed on the display unit, receiving the second information by the communication unit is performed by the terminal. The program according to claim 5,
The information of the user of the first terminal includes information about 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 claim 3,
The second information is transmitted based on a relationship between a user of the first terminal and a user of the terminal. The program according to any one of claims 1 to 7,
The chat information includes information about a first chat room including a user of the first terminal and a user of the terminal. The program according to claim 8,
The chat information includes information about the first chat room included in a chat room list including the user of the terminal. The program according to claim 9,
Based on the first information, the terminal performs control to change the display mode of the information regarding the first chat room by the control unit of the terminal. A program according to claim 10,
The terminal executes control by the control unit to change the display mode of the information about the first chat room based on the information about the safety of the user included in the first chat room, including the first information. be done. The program according to claim 8,
The first information is displayed in the first chat room. 13. The program according to claim 12,
The first information is displayed in the first chat room in association with a first image set by the user of the first terminal. The program according to any one of claims 1 to 7,
The chat information is included in a list of users associated with the user of the terminal in the chat. The program according to any one of claims 1 to 14,
Transmitting, by the communication unit, third information regarding the safety of the user of the terminal is performed by the terminal based on an input to the terminal by the user of the terminal. 16. The program according to claim 15,
displaying information on the automatic chat response on the display unit based on the transmission of the third information;
Based on the input by the user of the terminal with respect to the information about the automatic response, the terminal performs a process regarding the automatic response of the chat by the control unit of the terminal. The program according to any one of claims 1 to 16,
displaying information on the automatic response to the chat on the display unit based on the state of the terminal;
Based on the input by the user of the terminal with respect to the information about the automatic response, the terminal performs a process regarding the automatic response of the chat by the control unit of the terminal. The program according to any one of claims 1 to 17,
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 chatting with a user of a first terminal, 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 the first information associated with the chat information related to the user of the first terminal on a display of the terminal. A terminal that performs processing related to chatting with the 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;
and a display unit for displaying the first information associated with the chat information related to the user of the first terminal. A terminal that performs processing related to chatting with the user of the first terminal,
A processor that reads a program stored in memory and executes processing based on the program,
The processor
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 the first information associated with the chat information related to the user of the first terminal on a display unit of the terminal.

Images