JP7707761B2 - Server device, system, and server device control method and program - Google Patents

Description

The present invention relates to a server device, a system, a method for controlling a server device, and a program.

When a disaster such as a typhoon is predicted, residents will evacuate to evacuation shelters. Various technologies that can be applied to evacuating residents have been developed.

For example, Patent Document 1 describes that it provides an evacuation support system and evacuation support method that concretely visualizes an imminent disaster, stimulates residents' sense of crisis, and leads to evacuation behavior. The evacuation support system of Patent Document 1 includes an information management server, an evacuation shelter information terminal, and a support destination terminal. The information management server works in conjunction with a disaster information system that provides disaster information, and manages status information for multiple evacuation targets and multiple evacuation shelters registered within its jurisdiction. The evacuation shelter information terminal is installed at each of the multiple evacuation shelters and communicates with the information management server. The support destination terminal is carried by each of the multiple evacuation targets and communicates with the information management server. The information management server registers the contact conditions and evacuation destination requests of each of the multiple evacuation targets, and registers evacuation shelter information related to the status of each of the multiple evacuation shelters through the evacuation shelter information terminal. The information management server notifies the support destination terminal of a call for evacuation and evacuation shelter information based on the disaster information in accordance with the contact conditions and evacuation destination requests.

Patent document 2 describes that when a disaster occurs, suitable support information regarding evacuation is provided to the person instructed to evacuate. The information processing device (administrator terminal) in Patent document 2 includes a memory unit and a display control unit. The memory unit stores location information of multiple evacuation sites, movable range information indicating the movable range of people centered on each evacuation site, and information on the number of people scheduled to evacuate indicating the number of people scheduled to evacuate in each area within the movable range. The display control unit displays the evacuation sites and the movable range on the display unit. In addition, when the movable ranges of multiple evacuation sites overlap, the display control unit identifies the number of people who have not yet evacuated in the overlapping area based on the information on the number of people scheduled to evacuate in the area included in the overlapping area and the location information of people who have completed evacuation at each evacuation site. The display control unit displays information on the number of people who have not yet evacuated indicating the number of people who have not yet evacuated on the display unit.

Patent Document 3 states that it provides a disaster evacuation assistance system that can also be effectively used by non-profit organizations (NPOs), which are expanding as the bases for disaster assistance. A disaster assistance center equipped with the disaster evacuation assistance system of Patent Document 3 can receive necessary information for managing evacuation information from registered users in advance via a communication network. From this information, information on stockpiling of evacuation supplies and a delivery plan for when a disaster occurs are sent to the transport company. Appropriate stockpiling is always carried out in accordance with this information for the former, and evacuation supplies are delivered in accordance with the delivery plan for the latter.

JP 2021-071940 A JP 2020-140296 A JP 2004-054516 A

As mentioned above, when a disaster is predicted, residents will evacuate to evacuation shelters. However, when a disaster actually occurs, it may be difficult for residents to evacuate smoothly if they do not decide on an evacuation destination in advance. For example, even if a resident is planning to evacuate to a nearby elementary school, depending on the scale of the typhoon, the elementary school may not be open as an evacuation shelter. In such cases, the resident is required to take measures such as evacuating to the home of a relative.

The above problems cannot be solved by applying the technologies disclosed in Patent Documents 1 to 3. These documents are intended to assume that a disaster has actually occurred and disclose technologies related to the delivery of goods, etc.

The main objective of the present invention is to provide a server device, a system, a method for controlling a server device, and a program that contribute to realizing safer evacuation for residents.

According to a first aspect of the present invention, a server device is provided that includes an acquisition unit that acquires evacuation shelter opening conditions that define the conditions for opening a candidate evacuation shelter as an evacuation shelter for each disaster, and a management unit that manages evacuation action plans including evacuation start conditions that define the conditions for starting evacuation for each disaster and evacuation destinations that are set for each of a plurality of residents based on the evacuation shelter opening conditions.

According to a second aspect of the present invention, a system is provided that includes a resident terminal and a server device, the server device being equipped with an acquisition unit that acquires evacuation shelter opening conditions that define the conditions for opening a candidate evacuation shelter as an evacuation shelter for each disaster, a management unit that manages evacuation action plans including evacuation start conditions that define the conditions for starting evacuation for each disaster and evacuation destinations that are set for each of a plurality of residents based on the evacuation shelter opening conditions, and an evacuation information control unit that acquires a disaster risk level indicating the risk of a disaster from a disaster prevention officer when a disaster occurs or when a disaster is expected to occur, extracts residents who satisfy the evacuation start conditions from among the plurality of residents based on the disaster risk level, and transmits evacuation information including information regarding the evacuation destination to the resident terminal held by the extracted resident.

According to a third aspect of the present invention, a method for controlling a server device is provided, which acquires evacuation shelter opening conditions that define the conditions for opening a candidate evacuation shelter as an evacuation shelter for each disaster in a server device, and manages evacuation action plans including evacuation start conditions that define the conditions for starting evacuation for each disaster and evacuation destinations that are set for each of a plurality of residents based on the evacuation shelter opening conditions.

According to a fourth aspect of the present invention, a program is provided for causing a computer mounted on a server device to execute a process of acquiring evacuation shelter opening conditions that define the conditions for opening a candidate evacuation shelter as an evacuation shelter for each disaster, and a process of managing evacuation action plans including evacuation destinations and evacuation start conditions that define the conditions for starting evacuation for each disaster, which are set for each of a plurality of residents based on the evacuation shelter opening conditions.

According to each aspect of the present invention, a server device, a system, a method for controlling a server device, and a program are provided that contribute to realizing safer evacuation of residents. Note that the effects of the present invention are not limited to the above. The present invention may achieve other effects instead of or in addition to the above effects.

FIG. 1 is a diagram for explaining an overview of an embodiment. FIG. 2 is a diagram illustrating an example of a schematic configuration of the disaster prevention system according to the first embodiment. FIG. 3 is a diagram illustrating an example of a display of the resident terminal according to the first embodiment. FIG. 4 is a diagram for explaining the operation of the disaster prevention system according to the first embodiment. FIG. 5 is a diagram illustrating an example of a display of the disaster prevention terminal according to the first embodiment. FIG. 6 is a diagram for explaining the operation of the disaster prevention system according to the first embodiment. FIG. 7 is a diagram for explaining the operation of the disaster prevention system according to the first embodiment. FIG. 8 is a diagram illustrating an example of a processing configuration of a server device according to the first embodiment. FIG. 9 is a diagram illustrating an example of a resident information database according to the first embodiment. FIG. 10 is a diagram illustrating an example of a display of the disaster prevention terminal according to the first embodiment. FIG. 11 is a diagram illustrating an example of a display of the disaster prevention terminal according to the first embodiment. FIG. 12 is a diagram illustrating an example of the evacuation shelter information database according to the first embodiment. FIG. 13 is a diagram illustrating an example of a display of the disaster prevention terminal according to the first embodiment. FIG. 14 is a flowchart illustrating an example of the operation of the evacuation information control unit according to the first embodiment. FIG. 15 is a diagram illustrating an example of a display of the disaster prevention terminal according to the first embodiment. FIG. 16 is a diagram illustrating an example of a processing configuration of the resident terminal according to the first embodiment. FIG. 17 is a diagram illustrating an example of a display of the resident terminal according to the first embodiment. FIG. 18 is a diagram for explaining the operation of the resident terminal according to the first embodiment. 19A and 19B are diagrams illustrating an example of a display of a resident terminal according to the first embodiment. FIG. 20 is a diagram illustrating an example of a display of the resident terminal according to the first embodiment. FIG. 21 is a diagram illustrating an example of a display of the resident terminal according to the first embodiment. FIG. 22 is a diagram illustrating an example of a display of the resident terminal according to the first embodiment. FIG. 23 is a diagram illustrating an example of a display of the resident terminal according to the first embodiment. FIG. 24 is a sequence diagram showing an example of the operation of the disaster prevention system according to the first embodiment. FIG. 25 is a sequence diagram showing an example of the operation of the disaster prevention system according to the first embodiment. FIG. 26 is a diagram illustrating an example of a processing configuration of a server device according to the second embodiment. FIG. 27 is a diagram illustrating an example of a display of the resident terminal according to the second embodiment. FIG. 28 is a diagram illustrating an example of a display of the resident terminal according to the second embodiment. 29A and 29B are diagrams illustrating an example of a display of a resident terminal according to the second embodiment. FIG. 30 is a diagram for explaining the operation of the disaster prevention system according to the third embodiment. FIG. 31 is a diagram illustrating an example of a processing configuration of a server device according to the third embodiment. FIG. 32 is a diagram illustrating an example of a display of a resident terminal according to the third embodiment. FIG. 33 is a diagram illustrating an example of a processing configuration of a server device according to the fourth embodiment. FIG. 34 is a diagram for explaining the operation of the disaster prevention system according to the fourth embodiment. FIG. 35 is a diagram illustrating an example of a hardware configuration of a server device according to the present disclosure.

First, an overview of one embodiment will be described. The reference numbers in the drawings are added to each element for convenience as an example to aid in understanding, and the description of this overview is not intended to be limiting in any way. Furthermore, unless otherwise specified, the blocks shown in each drawing represent functional units rather than hardware units. The connection lines between blocks in each drawing include both bidirectional and unidirectional lines. Unidirectional arrows are used to show the main signal (data) flow diagrammatically, and do not exclude bidirectionality. In this specification and drawings, elements that can be described in the same way may be given the same reference numbers to avoid duplicated explanations.

The server device 100 according to one embodiment includes an acquisition unit 101 and a management unit 102 (see FIG. 1). The acquisition unit 101 acquires evacuation shelter opening conditions that define the conditions for opening a candidate evacuation shelter as an evacuation shelter for each disaster. The management unit 102 manages evacuation action plans including evacuation start conditions that define the conditions for starting evacuation for each disaster and evacuation destinations that are set for each of a plurality of residents based on the evacuation shelter opening conditions.

During peacetime before a disaster occurs, a local government disaster prevention officer inputs into server device 100 the conditions for opening a facility as an evacuation shelter for each facility that is scheduled to be opened as an evacuation shelter. For example, a disaster prevention officer inputs into server device 100 evacuation shelter opening conditions, such as opening the facility as an evacuation shelter when an alert with a specified alert level is issued. These evacuation shelter opening conditions are provided to residents, who input the conditions for starting evacuation and the evacuation destination into server device 100 as an "evacuation action plan" while checking the evacuation shelter opening conditions. By registering the residents' evacuation action plans in the system, server device 100 can smoothly notify each resident of the pre-set evacuation action plan when an actual disaster occurs.

Residents who receive the notification can smoothly evacuate to a pre-determined evacuation destination. That is, residents can decide on an evacuation destination while checking the evacuation shelter opening conditions, so that a situation in which a evacuation shelter is not open at the time when the resident is thinking of starting evacuation (for example, when an alert accompanied by an alert level is issued) can be avoided. More specifically, residents who are thinking of evacuating at the time when alert level 2 is issued can select an evacuation shelter that is open at the time when alert level 2 is issued as an evacuation destination. In other words, the resident cannot select an evacuation shelter that is not scheduled to be opened at the time when alert level 2 is issued as an evacuation destination. In addition, even if a long period of time has passed between the setting of an evacuation action plan and the actual occurrence of a disaster, if a disaster occurs that matches the evacuation start conditions set by the residents, the server device 100 can inform the residents of this fact. As a result, the evacuation of residents is not delayed. In this way, the disaster prevention system including the server device 100 makes sufficient preparations for the occurrence of a disaster, and in the event of a disaster, residents can safely evacuate according to the evacuation action plan set in advance (they can evacuate to the evacuation destination with plenty of time to spare).

Specific embodiments are described in more detail below with reference to the drawings.

[First embodiment]
The first embodiment will be described in more detail with reference to the drawings.

[System Configuration]
2 is a diagram showing an example of a schematic configuration of the disaster prevention system according to the first embodiment. As shown in FIG. 2, the disaster prevention system includes a server device 10.

The server device 10 is responsible for managing disaster prevention for local residents, operating evacuation shelters, supporting evacuees, etc. The server device 10 is managed and operated by a local government such as a city hall. The server device 10 may be installed in a building such as a city hall, or may be installed on a network (on the cloud).

A local government disaster prevention officer (hereinafter sometimes simply referred to as "officer") uses a disaster prevention terminal 20 to carry out work related to disaster prevention in the area. For example, the officer manages evacuation shelters that are opened when a disaster occurs. Local facilities such as schools and community centers correspond to evacuation shelters. Schools, community centers, and other facilities are used as "evacuation shelters" when a disaster occurs.

Each resident in the area has a resident terminal 30-1 to 30-3. Each resident uses the resident terminal 30-1 to 30-3 to input information to the server device 10 and obtain information from the server device 10.

In the following explanation, unless there is a particular reason to distinguish between resident terminals 30-1 to 30-3, they will simply be referred to as "resident terminal 30."

The devices shown in FIG. 2 are interconnected. Specifically, the server device 10 and the disaster prevention terminal 20 are connected by wired or wireless communication means and are configured to be able to communicate with each other.

The configuration of the disaster prevention system shown in FIG. 2 is an example, and is not intended to be limiting. For example, multiple server devices 10 may be included in the disaster prevention system. Of course, the number of residents in a region is not intended to be limited to "3."

[Operation overview]
Next, an outline of the operation of the disaster prevention system according to the first embodiment will be described.

<Resident registration>
First, local residents pre-register their own information in the disaster prevention system. The residents perform resident registration in the server device 10 that is responsible for disaster prevention in the area. In the following description, the information that the residents register in the server device 10 is referred to as "resident information."

Residents register resident information in the server device 10 using any means. For example, the resident operates the resident terminal 30 that he or she owns to perform resident registration. For example, the resident performs resident registration using a disaster prevention application (hereinafter also referred to simply as a disaster prevention app) installed on the resident terminal 30.

When the disaster prevention app is launched, the resident terminal 30 displays a menu screen as shown in FIG. 3. The resident registers resident information in the server device 10 by selecting "resident registration."

In addition, for residents who have difficulty registering information themselves, such as young children or elderly people, their parents or children may register resident information about the young children, elderly people, etc. on their behalf to the server device 10.

Resident information includes personal information. Personal information includes the four basic pieces of information (name, gender, address, date of birth) as well as contact information (telephone number, email address, etc.).

Alternatively, the resident information may include information about the resident's residence (residential information), information about the family (family information), etc. Examples of residence information include the type of home (detached house, apartment), structure (single-storey, two-storey), location of bedrooms (first floor, second floor), whether or not there is a parking space, etc. Examples of family information include the names of family members living together.

When the resident terminal 30 acquires resident information using a GUI (Graphical User Interface) or the like, it transmits a "resident information registration request" including the acquired resident information to the server device 10 (see FIG. 4).

When the server device 10 acquires resident information (personal information, housing information, etc.) from the resident terminal 30, it generates a resident ID to identify the resident. The server device 10 associates the generated resident ID with the personal information, etc. and stores them in the resident information database. Details of the resident information database will be described later.

The server device 10 issues the generated resident ID to the resident. The server device 10 transmits the generated resident ID to the resident terminal 30. The resident terminal 30 stores the resident ID.

<Advance preparations by local governments>
A disaster prevention officer makes preparations in advance in preparation for the occurrence of a disaster. Specifically, the officer operates the disaster prevention terminal 20 to access the server device 10. The server device 10 displays a menu screen for disaster prevention management on the disaster prevention terminal 20.

For example, the server device 10 displays a screen related to a disaster prevention management menu as shown in FIG. 5. The person in charge selects an item displayed on the menu screen provided by the server device 10 and performs work related to disaster prevention.

The person in charge selects "Register basic data" and registers basic data about the area (target area for disaster prevention work) in the server device 10. For example, the person in charge inputs information identifying the target area (for example, area name such as oaza or hamlet), population, number of staff involved in disaster prevention work in the area, a hazard map for the area, information about potential evacuation shelters, etc. into the server device 10.

A candidate evacuation shelter is a facility (such as an elementary school, junior high school, or community center) that can be used as an evacuation shelter in the event of a disaster. The person in charge registers basic information about the candidate evacuation shelter, such as the facility name, location, capacity, etc., as "evacuation shelter data" in the server device 10.

The person in charge selects "Register evacuation shelter opening conditions" and registers the conditions for opening evacuation shelters in the event of a disaster in the server device 10. For example, the person in charge registers the conditions for using each evacuation shelter candidate (facilities such as elementary schools) as an evacuation shelter for each type of disaster. For example, the person in charge sets conditions for each evacuation shelter candidate, such as "When a typhoon approaches: Alert level 3 or higher issued" or "When an earthquake occurs: Seismic intensity 4 or higher" for each evacuation shelter candidate.

In the following explanation, the conditions for using (opening) a potential evacuation shelter as an evacuation shelter will be referred to as "evacuation shelter opening conditions." The evacuation shelter opening conditions include the evacuation shelter opening risk level, which indicates the risk level of a disaster that will trigger the opening of the potential evacuation shelter as an evacuation shelter. For example, for each disaster (earthquakes, tsunamis, typhoons, heavy rain, floods, tornadoes, volcanic eruptions, etc.), indicators such as alert level, seismic intensity, magnitude, and precipitation are examples of the evacuation shelter opening risk level.

The server device 10 associates the evacuation shelter data (facility name, location, capacity, etc.) of each candidate evacuation shelter with the evacuation shelter opening conditions (risk of evacuation shelter opening for each disaster) and stores them in the evacuation shelter information database. Details of the evacuation shelter information database will be described later.

<Advance preparations by residents>
Before a disaster occurs, local residents register plans for actions to be taken in the event of a disaster (evacuation action plans) in the server device 10. For example, residents register evacuation action plans in the server device 10 using a disaster prevention app installed on the resident terminal 30.

Specifically, a resident launches the disaster prevention application and selects "Register evacuation action plan" as shown in Figure 3.

In response to this selection, the resident terminal 30 sends a "request for evacuation shelter information" including the resident ID to the server device 10 (see Figure 6).

In response to this request, the server device 10 transmits "shelter information" to the resident terminal 30. The shelter information is information about shelters (candidate shelters) that are scheduled to be opened in the event of a disaster. More specifically, the shelter data and shelter opening conditions stored in the shelter information database of the server device 10 correspond to "shelter information."

In other words, in response to a request from the resident terminal 30, the server device 10 transmits to the resident terminal 30 the facility name, location, capacity, and conditions for using the candidate evacuation shelter as an evacuation shelter (conditions for opening the evacuation shelter), etc., of the candidate evacuation shelter.

The resident terminal 30 uses the evacuation shelter information acquired from the server device 10 to provide residents with a GUI (Graphical User Interface) or the like for the residents to input their evacuation action plans. Residents operate the resident terminal 30 to input their evacuation action plans. The evacuation action plans are set by each resident in the area based on the evacuation shelter opening conditions and other conditions included in the evacuation shelter information.

For each disaster that is expected to occur, the evacuation action plan includes evacuation destinations in the event of a disaster (e.g., evacuation shelters or the homes of relatives or acquaintances, etc.) and evacuation start risk levels that indicate the degree of disaster risk that will trigger each resident to begin evacuating in the event of a disaster. For example, evacuation action plans may include content such as "When a typhoon approaches: Alert level 3; evacuate to evacuation shelter A" and "When an earthquake occurs: Seismic intensity 4; evacuate to the home of a relative."

In this way, an evacuation action plan includes the disaster type, evacuation start risk, and evacuation destination. Of these three pieces of information, the disaster type and evacuation start risk constitute the "evacuation start conditions." In other words, an evacuation action plan includes at least one evacuation start condition and one or more evacuation destinations.

The resident terminal 30 transmits the acquired evacuation action plan to the server device 10. Specifically, the resident terminal 30 transmits an "evacuation action plan registration request" including the resident ID and the evacuation action plan to the server device 10.

The server device 10 stores the acquired evacuation action plan in the resident information database.

<Sending evacuation information>
When a disaster occurs or when the occurrence of a disaster is predicted, a disaster prevention officer inputs disaster information into the server device 10 (see FIG. 7).

The disaster information includes the type of disaster and disaster risk information that indicates the risk of the disaster. For example, examples of disaster risk information include indicators such as alert level, seismic intensity, magnitude, and flood depth, as well as the risk of opening evacuation shelters and the risk of starting evacuation.

For example, when a warning accompanied by an alert level is issued due to a typhoon, heavy rain, or the like, the person in charge inputs the alert level as well as the type of disaster into the server device 10 as disaster information. Alternatively, when an earthquake occurs, the person in charge inputs the seismic intensity of the target area into the server device 10.

When the disaster information is acquired, the server device 10 determines whether the evacuation start conditions in each resident's evacuation action plan are met. For residents for whom it is determined that the evacuation start conditions are met, the server device 10 transmits "evacuation information" to the resident terminal 30 of that resident. In contrast, for residents for whom it is determined that the evacuation start conditions are not met, the server device 10 does not transmit "evacuation information."

For example, in FIG. 7, the evacuation start condition for a resident who has resident terminal 30-1 is "approaching typhoon; alert level 3," and the evacuation start condition for a resident who has resident terminal 30-2 is "approaching typhoon; alert level 4." Furthermore, the disaster information is "approaching typhoon; alert level 3."

In this case, the evacuation start condition for the resident of resident terminal 30-1 is satisfied, so server device 10 transmits evacuation information to resident terminal 30-1. In contrast, the evacuation start condition for the resident of resident terminal 30-2 is not satisfied, so server device 10 does not transmit evacuation information to resident terminal 30-2.

The evacuation information here includes information on evacuation destinations registered by residents in their evacuation action plans. For example, the server device 10 transmits evacuation information including the names and locations of evacuation shelters included in the evacuation action plan to the resident terminal 30. The resident terminal 30 notifies the residents of the acquired evacuation information. Residents who receive the evacuation information evacuate to the evacuation destinations they registered in advance.

In this way, the server device 10 determines whether or not evacuation information needs to be sent based on the evacuation action plan entered by each resident, and if it is necessary to send evacuation information, it sends information about the evacuation destination registered in advance to the resident terminal 30. This response by the server device 10 ensures that residents do not evacuate to evacuation shelters that are not open, and that they do not fall behind in their evacuation.

Next, we will explain the details of each device included in the disaster prevention system according to the first embodiment.

[Server device]
Fig. 8 is a diagram showing an example of a processing configuration (processing module) of the server device 10 according to the first embodiment. Referring to Fig. 8, the server device 10 includes a communication control unit 201, a resident registration unit 202, a basic data acquisition unit 203, an opening condition acquisition unit 204, an action plan management unit 205, an evacuation information control unit 206, and a storage unit 207.

The communication control unit 201 is a means for controlling communication with other devices. For example, the communication control unit 201 receives data (packets) from the disaster prevention terminal 20. The communication control unit 201 also transmits data to the disaster prevention terminal 20. The communication control unit 201 passes data received from other devices to other processing modules. The communication control unit 201 transmits data acquired from other processing modules to other devices. In this way, the other processing modules transmit and receive data to and from other devices via the communication control unit 201. The communication control unit 201 has a function as a receiving unit that receives data from other devices and a function as a transmitting unit that transmits data to other devices.

The resident registration unit 202 is a means for realizing the above-mentioned resident registration. The resident registration unit 202 is a means for acquiring resident information for each of a number of residents who may become evacuees in the future. More specifically, the resident registration unit 202 acquires resident information including personal information, housing information, etc., by any means.

For example, the resident registration unit 202 may acquire resident information from a resident terminal 30 operated by the resident. Alternatively, the resident may send a document containing the resident information or an external storage device storing the resident information to a disaster prevention center, and a staff member of the center may input the resident information into the server device 10.

In the first embodiment, the resident registration unit 202 acquires resident information from a disaster prevention application of the resident terminal 30. The resident registration unit 202 receives a "resident information registration request" from the resident terminal 30.

When the resident information is obtained from the request, the resident registration unit 202 generates a resident ID for identifying the resident. The resident ID may be any information that can uniquely identify a registered resident. For example, the resident registration unit 202 may assign a unique value each time a resident is registered as the resident ID.

The resident registration unit 202 associates the generated resident ID, personal information, residence information, etc. and stores them in the resident information database (see Figure 9). As shown in Figure 9, the resident information database includes a personal information field, an evacuation action plan field, a residence information field, a family information field, etc.

The resident information database shown in FIG. 9 is an example and is not intended to limit the items stored. For example, facial images and features generated from the facial images may be registered in the resident information database as biometric information of residents. The residence information and family information shown in FIG. 9 include specific details such as the characteristics of the home and the names of family members living together.

The resident registration unit 202 issues the generated resident ID to the resident (resident terminal 30). If the resident registration unit 202 successfully processes the resident information registration request, it sends a positive response including the resident ID to the resident terminal 30. If the resident registration unit 202 fails to register the resident information, it sends a negative response to that effect to the resident terminal 30.

The basic data acquisition unit 203 is a means for acquiring basic data related to the target area for disaster prevention management. When the disaster prevention officer selects "Register basic data" in the management menu shown in FIG. 5, the basic data acquisition unit 203 acquires basic data for the target area. For example, the basic data acquisition unit 203 displays a GUI (Graphical User Interface) such as that shown in FIG. 10 on the disaster prevention terminal 20.

The basic data acquisition unit 203 uses the GUI to acquire information that identifies the target area (for example, area names such as oaza and koaza), population, the number of staff involved in disaster prevention work in the area, a hazard map for the area, etc. The basic data acquisition unit 203 stores the acquired basic data in the storage unit 207.

Furthermore, the basic data acquisition unit 203 acquires data on the candidate evacuation shelters in the target area. Specifically, when the "Enter evacuation shelter data" button shown in FIG. 10 is pressed, the basic data acquisition unit 203 displays a GUI on the disaster prevention terminal 20 for acquiring the evacuation shelter data for each candidate evacuation shelter.

For example, the basic data acquisition unit 203 displays a GUI as shown in FIG. 11. The basic data acquisition unit 203 acquires information such as the facility name, location, and capacity (number of people that can be accommodated) of each evacuation shelter (a facility that will be used as an evacuation shelter in the future; a candidate evacuation shelter) as evacuation shelter data. Alternatively, the basic data acquisition unit 203 may acquire information regarding the contact information and facilities of the candidate evacuation shelter (for example, facilities that can accommodate people in need of care).

The basic data acquisition unit 203 assigns a shelter ID to each shelter (candidate shelter) for which the disaster prevention officer has entered shelter data. For example, the basic data acquisition unit 203 assigns a shelter ID to each shelter in the order in which the officer entered the shelter data.

The basic data acquisition unit 203 stores the acquired shelter data in a shelter information database (see FIG. 12). As shown in FIG. 12, the shelter information database includes a shelter ID field that stores a shelter ID, a shelter data field, and a shelter opening conditions field.

The evacuation shelter information database shown in FIG. 12 is an example and is not intended to limit the items to be stored. For example, characteristics of the candidate evacuation shelter (e.g., information about the surrounding environment of the candidate evacuation shelter; for example, being near a river, being built on high ground, etc.) may be stored in the evacuation shelter information database.

The opening condition acquisition unit 204 is a means for acquiring evacuation shelter opening conditions that define the conditions for opening an evacuation shelter candidate as an evacuation shelter for each disaster. The opening condition acquisition unit 204 acquires the evacuation shelter opening conditions for opening each facility set as an evacuation shelter candidate as an "evacuation shelter." When the disaster prevention officer selects "Register evacuation shelter opening conditions" in the management menu shown in FIG. 5, the opening condition acquisition unit 204 acquires the evacuation shelter opening conditions for each evacuation shelter candidate.

The opening condition acquisition unit 204 reads out the evacuation shelter data for each evacuation shelter (candidate evacuation shelter) listed in the evacuation shelter information database, and displays on the disaster prevention terminal 20 a GUI for setting evacuation shelter opening conditions for each candidate evacuation shelter. For example, the opening condition acquisition unit 204 displays on the disaster prevention terminal 20 a GUI such as that shown in FIG. 13.

The opening condition acquisition unit 204 acquires the conditions (shelter opening conditions) for opening each evacuation shelter candidate as an evacuation shelter for each disaster. The opening condition acquisition unit 204 stores the acquired evacuation shelter opening conditions in the evacuation shelter information database. Note that, depending on the type of disaster and the characteristics of the evacuation shelter, there are some evacuation shelter candidates that will not be opened as evacuation shelters. For example, evacuation shelter opening conditions are not set for evacuation shelter candidates that are located near rivers, etc. when a typhoon approaches.

The action plan management unit 205 is a means for controlling and managing the registration of evacuation action plans by residents. More specifically, the action plan management unit 205 manages evacuation action plans including evacuation start conditions, which stipulate the conditions for starting evacuation for each disaster, and evacuation destinations, set for each of a number of residents based on the evacuation shelter opening conditions set by the disaster prevention officer.

The action plan management unit 205 processes "requests for evacuation shelter information" and "requests for evacuation action plan registration" received from the resident terminal 30.

When the action plan management unit 205 receives a request for providing evacuation shelter information, it reads out at least one entry stored in the evacuation shelter information database, and transmits the evacuation shelter information (evacuation shelter data, evacuation shelter opening conditions) including the read entry to the resident terminal 30.

The action plan management unit 205 may transmit information on all evacuation shelters (all entries) registered in the evacuation shelter information database to the resident terminal 30 as evacuation shelter information. Alternatively, the action plan management unit 205 may transmit information on some of the evacuation shelters registered in the database to the resident terminal 30 as evacuation shelter information. In other words, the action plan management unit 205 may narrow down the evacuation shelters for which information is to be provided to residents from among the multiple evacuation shelters (candidate evacuation shelters) registered in the evacuation shelter information database.

For example, the action plan management unit 205 may extract evacuation shelters (candidate evacuation shelters) for which information is to be provided to a resident based on the address of the resident. Specifically, the action plan management unit 205 searches the resident information database using the resident ID included in the request for evacuation shelter information as a key, and identifies the resident who is about to enter an evacuation action plan. The action plan management unit 205 may transmit to the resident terminal 30 evacuation shelter information regarding evacuation shelters that exist within a specified range centered on the home (address) of the identified resident.

In addition, the action plan management unit 205 converts the addresses of residents and the locations of each evacuation shelter into latitude and longitude, and uses the converted latitude and longitude to extract evacuation shelters (facilities such as elementary schools, community centers, etc.) that are located within a specified range from the residents' homes.

When sending evacuation shelter information, the action plan management unit 205 may send a text file or the like containing evacuation shelter data and evacuation shelter opening conditions to the resident terminal 30, or may send evacuation shelter information including map data reflecting the evacuation shelter data to the resident terminal 30.

The action plan management unit 205 receives an "evacuation action plan registration request" from the resident terminal 30. The action plan management unit 205 searches the resident information database using the resident ID included in the request as a key, and identifies the corresponding resident (entry). The action plan management unit 205 stores the evacuation action plan included in the evacuation action plan request in the evacuation action plan field of the identified resident.

The evacuation information control unit 206 is a means for controlling the evacuation information sent to local residents. When a disaster occurs or is expected to occur, the evacuation information control unit 206 obtains a disaster risk level indicating the degree of risk of a disaster from a disaster prevention officer. Based on the disaster risk level, the evacuation information control unit 206 extracts residents who satisfy the evacuation start conditions from among multiple residents. The evacuation information control unit 206 transmits evacuation information including information regarding evacuation destinations to the resident terminals 30 held by the extracted residents.

In this way, the evacuation information control unit 206 obtains "disaster information" from the disaster prevention officer, selects residents according to the disaster information, and transmits "evacuation information" to the selected residents (resident terminals 30).

The operation of the evacuation information control unit 206 will be described with reference to FIG. 14. FIG. 14 is a diagram showing an example of the operation of the evacuation information control unit 206 according to the first embodiment.

The evacuation information control unit 206 acquires disaster information from a disaster prevention officer (step S101). Specifically, when a disaster occurs or is expected to occur, the disaster prevention officer operates the disaster prevention terminal 20 to input the disaster information into the server device 10. For example, the officer selects "input disaster information" as shown in FIG. 5.

In response to the selection, the evacuation information control unit 206 displays a GUI for acquiring disaster information on the disaster prevention terminal 20. For example, the evacuation information control unit 206 displays a GUI as shown in FIG. 15.

As shown in FIG. 15, the evacuation information control unit 206 acquires the area to which evacuation information is to be sent, the type of disaster, the disaster risk level (e.g., alert level and seismic intensity), etc.

When disaster information is acquired, the evacuation information control unit 206 accesses the resident information database and acquires the evacuation action plans of residents in the area designated by the disaster prevention officer as being in the target area (step S102). Specifically, the evacuation information control unit 206 reads out the evacuation action plans of residents living in the designated area.

The evacuation information control unit 206 uses the read evacuation action plan (evacuation start conditions, evacuation destination) and disaster information to extract residents to whom the evacuation information is to be sent (evacuation information destination extraction; step S103). The evacuation information control unit 206 uses the disaster information to extract residents for whom the evacuation start conditions are satisfied. More specifically, the evacuation information control unit 206 extracts from among a plurality of residents residents who have set evacuation start conditions with an evacuation start risk level equal to or lower than the disaster risk level for a disaster that matches the disaster type entered by the disaster prevention officer together with the disaster risk level. In other words, the evacuation information control unit 206 extracts residents for whom evacuation start conditions are set that match the disaster type in the disaster information and whose disaster risk level, scale, intensity, etc. according to the evacuation start risk level are equal to or lower than the risk level, etc.

For example, in the example of Figure 9, when a disaster prevention officer inputs disaster information such as "Typhoon; Alert Level 3" as disaster information, a resident with a resident ID of "ID01" is extracted. In contrast, a resident with a resident ID of "ID02" is not extracted because the risk of starting evacuation when a typhoon approaches is "Alert Level 4 (Alert Level 4 or higher)."

The evacuation information control unit 206 generates evacuation information to be sent to the extracted residents (step S104). Specifically, the evacuation information control unit 206 identifies evacuation destinations included in the evacuation action plan of each resident. The evacuation information control unit 206 then generates evacuation information including information about the identified evacuation destinations (e.g., the name of the evacuation destination, the address of the evacuation destination, etc.).

The evacuation information control unit 206 sends the generated evacuation information to the resident's contact information (e.g., an email address that can be received by the resident terminal 30) (step S105).

The evacuation information control unit 206 can include various information in the evacuation information and transmit it to the resident terminal 30. For example, the evacuation information control unit 206 may transmit evacuation information to the resident terminal 30 that includes the route from the resident's home to the evacuation destination (shelter) and the means of transportation (information regarding buses, trains, etc.). In other words, the evacuation information control unit 206 may transmit evacuation information to the resident terminal 30 that includes map information that reflects the extracted resident's home and the location of the evacuation destination.

Alternatively, the evacuation information control unit 206 may transmit evacuation information including map information showing the location of the home and the evacuation shelter, and map information reflecting the route from the home to the evacuation shelter, to the resident terminal 30.

The memory unit 207 is a means for storing information necessary for the operation of the server device 10. A resident information database, an evacuation shelter information database, etc. are constructed in the memory unit 207.

[Resident terminal]
Examples of the resident terminal 30 include mobile terminal devices such as smartphones, mobile phones, game consoles, and tablets, as well as computers (personal computers, notebook computers), etc. The resident terminal 30 can be any equipment or device that can accept operations by the resident and communicate with the server device 10, etc.

Fig. 16 is a diagram showing an example of the processing configuration (processing module) of the resident terminal 30. Referring to Fig. 16, the resident terminal 30 includes a communication control unit 301, a resident registration request unit 302, an action plan control unit 303, an evacuation information processing unit 304, and a memory unit 305.

The communication control unit 301 is a means for controlling communication with other devices. For example, the communication control unit 301 receives data (packets) from the server device 10. The communication control unit 301 also transmits data to the server device 10. The communication control unit 301 passes data received from other devices to other processing modules. The communication control unit 301 transmits data acquired from other processing modules to other devices. In this way, the other processing modules transmit and receive data to and from other devices via the communication control unit 301. The communication control unit 301 has a function as a receiving unit that receives data from other devices and a function as a transmitting unit that transmits data to other devices.

The resident registration request unit 302 is a means for implementing the above-mentioned resident registration. The resident registration request unit 302 is activated, for example, when a resident selects "resident registration" shown in FIG. 3. For example, the resident registration request unit 302 displays a GUI such as that shown in FIG. 17.

The resident operates the resident terminal 30 to input the information shown in FIG. 17. If the resident wishes to register residence information or family information, the resident registration request unit 302 may display a GUI similar to that shown in FIG. 17 for inputting this information.

The resident registration request unit 302 sends a resident information registration request including the acquired resident information (personal information, residence information, family information, etc.) to the server device 10.

The resident registration request unit 302 receives a response (positive response, negative response) from the server device 10 to the resident information registration request. If a negative response is received, the resident registration request unit 302 notifies the resident that resident registration has failed.

If a positive response is received, the resident registration request unit 302 notifies the resident that the resident registration was successful, and stores the resident ID acquired from the server device 10 in the storage unit 305. The resident registration request unit 302 also stores personal information acquired from the resident (such as name and address) in the storage unit 305 together with the resident ID.

The action plan control unit 303 is a means for controlling the evacuation action plan of the resident. The action plan control unit 303 is activated, for example, when a resident selects "Register evacuation action plan" shown in FIG. 3. However, since resident registration must be completed in order to register an evacuation action plan, if resident registration has not been completed (if a resident ID has not been issued), the above "Register evacuation action plan" does not have to be selected.

First, the action plan control unit 303 transmits a request for providing evacuation shelter information, including a resident ID, to the server device 10. In response to the transmission of the request, the action plan control unit 303 acquires the evacuation shelter ID and evacuation shelter information (evacuation shelter data, evacuation shelter opening conditions).

After acquiring the evacuation shelter information, the action plan control unit 303 acquires an evacuation action plan from the resident. First, the action plan control unit 303 uses the evacuation shelter data to extract evacuation shelter candidates (evacuation shelters) that are within a specified range centered on the resident's home.

The action plan control unit 303 generates map information that reflects the locations of the extracted evacuation shelter candidates, with the resident's home at the center. For example, the action plan control unit 303 generates map information as shown in FIG. 18. The map information shown in FIG. 18 shows the resident's home and five evacuation shelter candidates S1 to S5.

The action plan control unit 303 displays a GUI for residents to input an evacuation action plan. For example, the action plan control unit 303 displays a GUI as shown in FIG. 19A and FIG. 19B. The action plan control unit 303 uses the GUI to acquire the type of disaster and the evacuation start risk level that specifies the timing to start evacuation when the disaster occurs.

The action plan control unit 303 determines whether to display or hide (select or not select) the candidate evacuation shelters included in the generated map information according to the resident's selection (disaster type, evacuation start risk level; input of evacuation start conditions). Specifically, the action plan control unit 303 displays on the map the candidate evacuation shelters that will be opened as evacuation shelters when a disaster occurs with a risk level (scale) equivalent to the evacuation start conditions input by the resident. In contrast, the action plan control unit 303 does not display the candidate evacuation shelters that will not be opened as evacuation shelters even when a disaster occurs with a risk level equivalent to the evacuation start conditions input by the resident. For example, in FIG. 19A, of the five candidate evacuation shelters S1 to S5 that exist near the resident's home, evacuation shelters S1 and S3 are displayed (selectable as evacuation destinations).

When a resident changes the disaster type or evacuation start risk level, the action plan control unit 303 displays candidate evacuation shelters according to the changed evacuation start conditions. For example, as shown in FIG. 19B, if a resident postpones the timing of evacuation (delays evacuation), the action plan control unit 303 newly displays candidate evacuation shelters S2 and S5.

In this way, the action plan control unit 303 determines whether to display or hide the above evacuation shelter candidates based on the evacuation start conditions selected by the resident and the evacuation shelter opening conditions for each evacuation shelter candidate included in the evacuation shelter information acquired from the server device 10. Specifically, for each evacuation shelter candidate, if the disaster risk level corresponding to the disaster selected by the resident is higher than the evacuation start risk level selected by the resident, the evacuation shelter candidate for which that disaster risk level is set is not displayed. On the other hand, if the disaster risk level corresponding to the disaster selected by the resident is equal to or lower than the evacuation start risk level selected by the resident, the evacuation shelter candidate for which that disaster risk level is set is displayed.

In the GUI shown in Fig. 19A and Fig. 19B, when a resident touches a candidate evacuation shelter (candidate evacuation shelter icon), the action plan control unit 303 displays detailed information about the candidate evacuation shelter (e.g., facility name, location, capacity, etc.) (see Fig. 20). Furthermore, when the action plan control unit 303 touches a candidate evacuation shelter while the candidate evacuation shelter is selected (detailed information is being displayed), the action plan control unit 303 treats the candidate evacuation shelter as an evacuation destination for the resident. In the drawings including Fig. 20, the selected evacuation shelter (candidate evacuation shelter) is displayed with a "check mark".

A resident may select an evacuation destination other than an evacuation shelter. In this case, the resident presses the "Select other than evacuation shelter" button shown in Figures 19A, 19B, and 20. In response to pressing this button, the action plan control unit 303 displays a GUI that allows the resident to select an evacuation destination other than an evacuation shelter.

For example, the action plan control unit 303 displays a GUI as shown in FIG. 21. If a resident wishes to evacuate to a place other than an evacuation shelter, the action plan control unit 303 provides the resident with a list of evacuation destinations as shown in FIG. 21, allowing the resident to select a destination other than an evacuation shelter.

The action plan control unit 303 may obtain more detailed information about the evacuation destination selected by the resident according to the evacuation destination list. For example, if the resident selects "family home," the action plan control unit 303 may obtain the address, names, and relationships of the selected family members. Alternatively, if a community center or the like that is not managed as an evacuation shelter by the local government is selected, the action plan control unit 303 may obtain the location of the community center, etc.

When an evacuation action plan (evacuation start conditions, evacuation destination) is obtained using a GUI such as that shown in Figures 20 and 21, the action plan control unit 303 sends an "evacuation action plan registration request" including the resident ID and the evacuation action plan to the server device 10.

The evacuation information processing unit 304 is a means for processing the "evacuation information" received from the server device 10. As described above, the evacuation information includes information on the evacuation destination registered by the resident in the evacuation action plan. For example, if an evacuation shelter is registered as the evacuation destination, evacuation information including the name, address, etc. of the evacuation shelter is transmitted to the resident terminal 30.

When the evacuation information processing unit 304 receives evacuation information, it displays and notifies residents (notification by voice or the like) to encourage them to evacuate. For example, the evacuation information processing unit 304 displays a display as shown in FIG. 22. Residents who come across a display as shown in FIG. 22 recognize the need to evacuate and begin evacuating to a preregistered evacuation destination.

If the evacuation information includes map information that reflects the locations of residents' homes and evacuation destinations, the evacuation information processing unit 304 may also display the map information (see FIG. 23).

When providing residents with the evacuation information shown in FIG. 22 or FIG. 23, the evacuation information processing unit 304 may also display a list of items necessary for life in an evacuation shelter, information regarding precautions, and the like. For example, the evacuation information processing unit 304 may warn residents not to forget to bring their regular medications, etc.

The memory unit 305 is a means for storing information necessary for the operation of the resident terminal 30.

[Disaster prevention terminal]
Examples of the disaster prevention terminal 20 include mobile terminal devices such as smartphones, mobile phones, and tablets, and computers (personal computers, notebook computers), etc. The disaster prevention terminal 20 can be any equipment or device that can accept operations by a disaster prevention officer and communicate with the server device 10, etc. The processing configuration, etc. of the disaster prevention terminal 20 are clear to those skilled in the art, so detailed explanations regarding the processing configuration, etc. will be omitted.

[System Operation]
Next, the operation of the disaster prevention system according to the first embodiment will be described. Note that the description of the operation related to resident registration and the operation related to the registration of basic data and evacuation shelter opening conditions will be omitted. Fig. 24 is a sequence diagram showing an example of the operation of the disaster prevention system according to the first embodiment. With reference to Fig. 24, the operation of the disaster prevention system when a resident registers an evacuation action plan in the system will be described.

The resident terminal 30 of a resident who wishes to register an evacuation action plan sends a "request for evacuation shelter information" to the server device 10 (step S01).

The server device 10 transmits the evacuation shelter information (evacuation shelter data, evacuation shelter opening conditions) registered in the evacuation shelter information database to the resident terminal 30 (step S02).

The resident terminal 30 uses the evacuation shelter information entered by the disaster prevention officer to display a GUI that enables the resident to create an evacuation action plan. The resident terminal 30 acquires the evacuation action plan from the resident (step S03).

The resident terminal 30 sends an "evacuation action plan registration request" including the acquired evacuation action plan to the server device 10 (step S04).

The server device 10 stores the acquired evacuation action plan in the resident information database (step S05).

Figure 25 is a diagram showing an example of the operation of the disaster prevention system according to the first embodiment. The operation of the disaster prevention system that transmits evacuation information when a disaster occurs will be described with reference to Figure 25.

When a disaster occurs or is expected to occur, the server device 10 acquires disaster information from a disaster prevention officer (step S11). The server device 10 acquires disaster information (type of disaster, disaster scale information) via the disaster prevention terminal 20.

The server device 10 extracts residents to whom evacuation information should be sent based on the acquired disaster information and the residents' evacuation action plans (extracts destinations for the evacuation information; step S12).

The server device 10 generates evacuation information to be sent to the extracted residents, and sends the generated evacuation information to the resident terminal 30 (step S13).

The resident terminal 30 notifies the resident of the received evacuation information (step S14). The resident terminal 30 displays information based on the acquired evacuation information (for example, a display such as that shown in Figures 22 and 23) and provides the resident with information on evacuation shelters and other information that was registered in advance.

As described above, in the disaster prevention system according to the first embodiment, the disaster prevention officer assumes the occurrence of a disaster and registers the evacuation shelter opening conditions in the server device 10 for opening each facility scattered in the area as an evacuation shelter. The evacuation shelter opening conditions registered in the system by the disaster prevention officer are provided to the residents who are formulating an evacuation action plan. The residents can decide the timing to start evacuation and the evacuation destination while referring to the evacuation shelter opening conditions. For example, the residents can register in the system an evacuation action plan such as evacuating to a nearby evacuation shelter when a typhoon approaches, or evacuating to a relative's house when an earthquake occurs. Furthermore, the residents can register in the system the timing to evacuate to the evacuation destination. For example, the residents input information such as "when alert level 4 is issued" when a typhoon approaches, and "when an earthquake of seismic intensity 5 or more occurs" into the server device 10 when an earthquake occurs. Furthermore, when a disaster actually occurs, the server device 10 provides useful information to the local residents. Specifically, the server device 10 transmits evacuation information, including information about a predetermined evacuation destination, to residents whose evacuation action plans have been met (residents whose predefined evacuation start timing has arrived). As a result, residents can evacuate safely to their evacuation destination without delay (without missing the opportunity to evacuate). In other words, the disaster prevention system including the server device 10 can make sufficient preparations in case of a disaster, and can provide residents with timely information that will be useful in the event of a disaster.

In this way, in the disaster prevention system disclosed in the present application, the timing of opening evacuation shelters created by the local government is shared with residents, allowing residents to select an evacuation destination taking into account the timing of the opening of the evacuation shelter. For example, if the timing of opening an evacuation shelter managed by the local government is when information equivalent to alert level 3 is announced, residents who wish to evacuate when information equivalent to alert level 2 is announced can decide to select an evacuation destination other than the evacuation shelter managed by the local government.

The evacuation shelters that are opened and the timing at which they are opened vary depending on the type and circumstances of the disaster, but the present disclosure employs a configuration in which the local government inputs the evacuation shelter opening conditions into the server 10, and residents create evacuation action plans by referring to the evacuation shelter opening conditions. In other words, residents can create evacuation action plans that suit the type and circumstances of the disaster. Furthermore, when a disaster actually occurs, residents are smoothly notified of the evacuation action plans that suit the type and circumstances of the disaster, and they can evacuate according to the evacuation action plans.

Second Embodiment
Next, the second embodiment will be described in detail with reference to the drawings.

In the second embodiment, we explain a case where a disaster prevention officer checks the registration status of evacuation action plans of local residents and uses the information to help with disaster prevention in the area.

The following will focus on the differences between the first and second embodiments.

The server device 10 provides disaster prevention personnel with the registration status of residents' evacuation action plans using a dashboard (a method of presenting various data related to evacuation action plans in the form of tables and graphs). For example, when "Check disaster countermeasure information" is selected on the menu screen shown in FIG. 5, the server device 10 provides information using the above-mentioned dashboard.

When "Check disaster countermeasure information" is selected, the server device 10 calculates information useful for disaster countermeasures (disaster countermeasure information; various data, indicators, etc.) by performing statistical processing using the evacuation action plans registered by residents. The server device 10 provides the calculated data and indicators to disaster prevention personnel in the form of graphs or charts.

FIG. 26 is a diagram showing an example of a processing configuration (processing module) of the server device 10 according to the second embodiment. Referring to FIG. 26, a disaster countermeasure information generation unit 208 has been added to the configuration of the server device 10 according to the first embodiment.

The disaster countermeasure information generation unit 208 is a means for generating disaster countermeasure information that is effective for disaster countermeasures based on the evacuation action plans set by each of multiple residents.

For example, the disaster countermeasure information generation unit 208 calculates the registration rate of evacuation action plans. The disaster countermeasure information generation unit 208 calculates the ratio of residents who have entered an evacuation action plan to residents who have completed resident registration as the evacuation action plan registration rate. In this case, the disaster countermeasure information generation unit 208 refers to the resident information database, and acquires the number of entries (number of residents) in the database and the number of residents who have set an evacuation action plan (the number of residents whose setting is in the evacuation action plan field). The disaster countermeasure information generation unit 208 calculates the evacuation action plan registration rate using the acquired number of entries and the number of residents who have set an evacuation action plan.

The disaster countermeasures information generating unit 208 may calculate the registration rate of evacuation action plans for each resident's attribute. Specifically, the disaster countermeasures information generating unit 208 may calculate the evacuation action plan registration rate for each resident's address, gender, and age group. When calculating the evacuation action plan registration rate for each address, the disaster countermeasures information generating unit 208 calculates the registration rate for residents included in addresses in a specified area unit (for example, by city/town/village unit, district unit, or street address unit).

The disaster countermeasure information generating unit 208 may calculate the evacuation action plan registration rate for each disaster. For example, the disaster countermeasure information generating unit 208 may calculate the registration rate for typhoons, the registration rate for earthquakes, etc. In this case, the disaster countermeasure information generating unit 208 may calculate the resident attributes and the evacuation action plan registration rate for each disaster.

The disaster countermeasure information generating unit 208 may calculate the number of residents who have set a shelter as their evacuation destination (number of people who have set a shelter). Alternatively, the disaster countermeasure information generating unit 208 may calculate the number of people who have set a shelter for each disaster for each shelter, or the number of people who have set a shelter for each evacuation start risk level (e.g., alert level). In the former example, for example, the disaster countermeasure information generating unit 208 calculates the number of residents who have set the shelter S1 as their evacuation destination when a typhoon approaches, and the number of residents who have set the shelter S1 as their evacuation destination when an earthquake occurs. In the latter example, for example, the disaster countermeasure information generating unit 208 calculates the number of residents who will start evacuating to the shelter S1 at alert level 1, and the number of residents who will start evacuating to the shelter S1 at alert level 2.

The disaster countermeasures information generating unit 208 may use the number of people who have set up evacuation shelters to calculate the evacuation shelter utilization rate for each disaster. The disaster countermeasures information generating unit 208 calculates the evacuation shelter utilization rate by calculating the ratio of the calculated number of people who have set up evacuation shelters to the number of residents who have set up evacuation action plans for each disaster and evacuation shelter. By referring to the evacuation shelter utilization rate, the person in charge can find out whether most of the residents who have decided to evacuate when a typhoon approaches are planning to evacuate to evacuation shelters or to places other than evacuation shelters.

Alternatively, the disaster countermeasure information generating unit 208 may calculate the evacuation action plan registration rate and the evacuation shelter utilization rate using the residence information and family information of each resident. For example, the disaster countermeasure information generating unit 208 may calculate the evacuation action plan registration rate of residents living in detached houses and the evacuation action plan registration rate of residents living in apartment buildings. Alternatively, the disaster countermeasure information generating unit 208 may calculate the evacuation action plan registration rate of single-person households, etc.

The disaster countermeasure information generating unit 208 provides all or part of the generated disaster countermeasure information (various data, indicators) to the disaster prevention personnel in a dashboard format or the like. The disaster countermeasure information generating unit 208 may display a list of various data and indicators, and may display information selected by the personnel in the form of a graph or chart.

For example, the disaster countermeasure information generating unit 208 provides information as shown in FIG. 27. In FIG. 27, the evacuation action plan registration rate for the entire target area is displayed in the form of a pie chart. Furthermore, when a type of disaster displayed in FIG. 27 is selected, the evacuation action plan registration rate for each disaster is displayed. The evacuation action plan registration rate for each disaster may also be displayed in the form of a pie chart.

Alternatively, the disaster countermeasure information generating unit 208 may display map information reflecting the evacuation action plan registration rate for each address (by area; in FIG. 28, by block), as shown in FIG. 28.

The person in charge who comes into contact with the disaster countermeasure information provided by the server device 10 (disaster countermeasure information generating unit 208) will consider measures to further ensure the safety of residents. For example, if the registration rate of evacuation action plans is lower than expected, the person in charge will investigate the cause of the low registration rate. For example, the person in charge will conduct interviews with residents to investigate the cause of the low registration rate. Alternatively, the person in charge will strengthen public relations activities, etc. to improve the registration rate of evacuation action plans.

Alternatively, the person in charge may review the evacuation shelter opening plan based on the disaster countermeasures information. For example, if the person in charge determines that the low evacuation action plan registration rate is due to a small number of evacuation shelters, the person in charge registers a new evacuation shelter in the area with few evacuation shelters in the server device 10. Specifically, the person in charge determines evacuation shelter candidates and inputs the evacuation shelter data and evacuation shelter opening conditions of the evacuation shelter candidates into the server device 10.

Alternatively, the person in charge may effectively increase the number of evacuation shelters by changing the evacuation shelter opening risk level for existing evacuation shelter candidates. For example, the person in charge may increase the number of evacuation shelters that are opened early by lowering the alert level set as the evacuation shelter opening risk level when a typhoon approaches.

For example, referring to Figure 28, if it is determined that the low registration rate of evacuation action plans in Block 3 is due to the number of evacuation shelters or the timing of their opening, new evacuation shelter candidates will be set up in the area, and the risk of opening existing evacuation shelter candidates will be lowered.

When adding a new shelter candidate, the server device 10 may provide the person in charge with an interface similar to that shown in Figures 11 and 13. Similarly, when changing the shelter establishment risk level for an existing shelter candidate, the server device 10 may display a list of the existing shelter candidates and provide an interface that allows the person in charge to change the setting value of the shelter candidate selected by the person in charge.

When the server device 10 receives a request for evacuation shelter information from a resident (resident terminal 30), it transmits to the resident an entry in the evacuation shelter information database to which the disaster prevention officer has added new evacuation shelter candidates, etc. This allows the resident to register an evacuation action plan based on improved evacuation shelter information.

Alternatively, if evacuation shelter information (evacuation shelter data, evacuation shelter opening conditions) is changed, the server device 10 may notify (push notify) the resident terminal 30 of that fact. For example, the server device 10 sends a "evacuation shelter information update notification" to the resident terminal 30. More specifically, the server device 10 sends an evacuation shelter information update notification to the resident terminal 30, which includes the resident's resident ID, the updated evacuation shelter information, and each resident's existing evacuation action plan.

In response to receiving this notification, the resident may review the evacuation action plan and register a new evacuation action plan. For example, when the resident terminal 30 receives an evacuation shelter information update notification, it displays the GUI shown in FIG. 19A or FIG. 19B, which reflects the evacuation action plan already set by the resident, and prompts the resident to re-enter the evacuation action plan.

The server device 10 may transmit a shelter information update notification to the resident terminal 30, clearly indicating the added evacuation shelter information. In this case, the resident terminal 30 (action plan control unit 303) may display an evacuation action plan setting screen, clearly indicating the added evacuation information.

For example, if a resident's existing evacuation action plan is as shown in FIG. 20, and a new evacuation shelter S6 is added, the resident terminal 30 will display a setting screen as shown in FIG. 29A. Also, if the evacuation shelter opening risk level of an existing evacuation shelter candidate is changed (for example, the alert level of evacuation shelter S5 is changed from 3 to 2), the resident terminal 30 will display a setting screen as shown in FIG. 29B.

Residents who see the setting screen shown in Figures 29A and 29B can decide on an evacuation action plan while taking into account the newly added evacuation shelter candidates.

As described above, the server device 10 according to the second embodiment generates disaster countermeasure information useful for disaster countermeasures based on the evacuation action plans input by local residents. The server device 10 displays the generated disaster countermeasure information on a dashboard to assist the work of disaster prevention personnel. In addition, the disaster prevention personnel reviews the evacuation shelter opening conditions based on the disaster countermeasure information provided by the server device 10 and registers them in the server device 10. The revised evacuation shelter opening conditions are provided to the residents, who can also review the evacuation action plans they set themselves. In this way, in peacetime before a disaster occurs, the evacuation shelter opening conditions revised based on the disaster countermeasure information are distributed to the residents, and each resident can also review their evacuation action plans and feedback the results to the local government. Through such feedback (input of evacuation action plans, generation of disaster countermeasure information, review of evacuation shelter opening conditions, review of evacuation action plans, generation of disaster countermeasure information), a more appropriate evacuation action plan is formulated.

[Third embodiment]
Next, a third embodiment will be described in detail with reference to the drawings.

In the third embodiment, a case will be described in which the server device 10 provides advice (useful information) to residents.

The following will focus on the differences between the first to third embodiments.

When the server device 10 receives an "evacuation action plan registration request" from the resident terminal 30, it provides advice (advice) on the evacuation action plan included in the request. Specifically, in response to receiving the evacuation action plan registration request, the server device 10 transmits "advice information" to the resident terminal 30 (see FIG. 30).

Fig. 31 is a diagram showing an example of a processing configuration (processing module) of the server device 10 according to the third embodiment. Referring to Fig. 31, an advice information control unit 209 has been added to the configuration of the server device 10 according to the second embodiment.

The advice information control unit 209 is a means for controlling the advice information sent to the resident terminal 30. Specifically, in response to a resident setting an evacuation action plan, the advice information control unit 209 generates advice information for the set evacuation action plan, and transmits the generated advice information to the resident terminal 30 of the resident who set the evacuation action plan.

If the evacuation start risk level (e.g., alert level or seismic intensity) in the evacuation action plan received from the resident terminal 30 is inappropriate, the advice information control unit 209 notifies the resident of that fact. For example, if the timing to start evacuation is late (the alert level is set high), the advice information control unit 209 transmits that fact to the resident terminal 30 as advice information.

Alternatively, the advice information control unit 209 may generate advice information based on the resident's residence information. For example, the advice information control unit 209 searches the resident information database using the resident ID included in the evacuation action plan registration request as a key to identify the corresponding resident. The advice information control unit 209 generates advice information according to the identified resident's residence information.

For example, the advice information control unit 209 generates different advice information depending on whether the resident lives in a single-story house or a high-rise apartment building. For example, when an earthquake occurs, the advice information control unit 209 advises residents living in high-rise apartment buildings to evacuate earlier than residents living in single-story houses. Specifically, even if the evacuation start risk level is the same, the advice information control unit 209 transmits advice information encouraging residents of high-rise apartment buildings to review the evacuation start risk level and evacuate earlier (set a lower evacuation start risk level).

Alternatively, the advice information control unit 209 may generate advice information based on the attributes of the resident. For example, the advice information control unit 209 may generate advice information based on the age or gender of the resident. For example, for an evacuation action plan for an elderly person, the advice information control unit 209 may generate advice information that urges the resident to evacuate earlier than the timing set by the resident.

The advice information control unit 209 may generate advice information based on the address of a resident. For example, the advice information control unit 209 refers to a hazard map of the area in which the resident lives and determines whether or not there is a possibility that the residential area of the resident will be flooded when a typhoon approaches, etc. If it is determined that there is a possibility of flooding, the advice information control unit 209 generates advice information informing the resident of this fact and encouraging the resident to begin evacuation as soon as possible.

Alternatively, the advice information control unit 209 may generate advice information based on the address and residence information of the resident. For example, the advice information control unit 209 may advise residents who live in a single-story house to start evacuating earlier, even if they live in the same area (residents who live in an area that may be flooded when a typhoon approaches, etc.). In other words, the advice information control unit 209 may advise residents who live in high-rise apartment buildings (especially those who live on higher floors) to wait at home rather than evacuating, or to delay the timing of starting evacuation.

In addition, if there is no advice to give regarding the resident's evacuation action plan, the advice information control unit 209 may not send advice information or may notify the resident terminal 30 that there is no advice.

The resident terminal 30 that receives the advice information presents the information to the resident. For example, the resident terminal 30 displays a screen as shown in FIG. 32. A resident who wishes to revise the evacuation action plan in accordance with the advice presses the "revise plan" button. The resident terminal 30 displays a setting screen (GUI) as shown in FIG. 20, and obtains a new evacuation action plan.

The resident terminal 30 sends an evacuation action plan registration request including the acquired evacuation action plan to the server device 10.

The server device 10 may generate advice information and transmit it to the resident terminal 30 for the second or subsequent evacuation action plan requests, or may not take any action for the second or subsequent evacuation action plan requests.

As described above, the server device 10 according to the third embodiment provides advice on the evacuation action plan set by the resident. More specifically, if the server device 10 determines that the timing for the resident to start evacuation is inappropriate, it notifies the resident of this fact. As a result, the resident can start evacuation at a safer time. In addition, the resident can feel reassured that the validity of the evacuation action plan has been confirmed.

[Fourth embodiment]
Next, the fourth embodiment will be described in detail with reference to the drawings.

In the fourth embodiment, we will explain the case where a new evacuation shelter is added when a disaster actually occurs.

The following will focus on the differences between the first to fourth embodiments.

When a disaster occurs, the server device 10 periodically or at a specified timing verifies the status of evacuation shelters that have already been opened. More specifically, when disaster information is received from a disaster prevention officer, the server device 10 determines that a disaster has occurred and starts verifying the status of the evacuation shelters.

Fig. 33 is a diagram showing an example of the processing configuration (processing module) of the server device 10 according to the fourth embodiment. Referring to Fig. 33, a shelter addition control unit 210 has been added to the configuration of the server device 10 according to the third embodiment.

The shelter addition control unit 210 is a means for controlling the opening of additional shelters. For example, the shelter addition control unit 210 estimates the occupancy rate of a shelter opened in accordance with the shelter opening conditions, and determines whether or not it is necessary to open a new shelter based on the estimated occupancy rate.

First, the shelter addition control unit 210 estimates the capacity of each shelter (the number of residents who have evacuated to the shelter). For example, the server device 10 estimates the capacity from the number of residents who have registered each shelter as an evacuation destination in the evacuation action plan.

For example, the shelter addition control unit 210 estimates the number of evacuees (capacity) evacuated to a particular shelter by multiplying the number of residents who have registered the shelter as an evacuation destination by a specified coefficient. For example, if 30 residents have registered the shelter as an evacuation destination, the shelter addition control unit 210 estimates that the shelter is accommodating 10 times that number of evacuees.

The coefficients used in the estimation are determined in advance based on the past performance of the target area (the actual number of residents who evacuated to evacuation shelters) and the characteristics of the evacuation shelters (the location of the evacuation shelters), and are input to the server device 10. More specifically, the disaster prevention officer determines the coefficients and inputs them to the server device 10.

Next, the shelter addition control unit 210 calculates the occupancy rate using the shelter's capacity and the shelter's capacity (the number of evacuees taking refuge at the shelter). In this way, the shelter addition control unit 210 estimates the capacity of the opened shelter from the number of residents who have registered the opened shelter as an evacuation destination in their evacuation action plan. Next, the shelter addition control unit 210 estimates the occupancy rate of the opened shelter based on the shelter's capacity and the estimated capacity.

The shelter addition control unit 210 determines whether or not an additional shelter needs to be opened based on the estimated occupancy rate. If the estimated occupancy rate exceeds a predetermined threshold, the shelter addition control unit 210 determines that an additional shelter needs to be opened.

When it is determined that an additional shelter needs to be opened, the shelter addition control unit 210 selects an additional shelter to be opened from among the unopened shelters. More specifically, the shelter addition control unit 210 selects an unopened shelter candidate that is close to a shelter whose occupancy rate exceeds a predetermined threshold. The shelter addition control unit 210 displays information about the selected shelter candidate (additionally opened shelter) on the disaster prevention terminal 20 (see step S21 in FIG. 34).

The disaster prevention terminal 20 notifies the disaster prevention person in charge of receiving the proposal to open an additional evacuation shelter, and obtains the disaster prevention person's thoughts (intentions) regarding the opening of an additional evacuation shelter. The disaster prevention terminal 20 obtains whether the disaster prevention person in charge of disaster prevention agrees to the opening of an additional evacuation shelter.

When the person in charge agrees to the opening of an additional evacuation shelter (step S22), the evacuation shelter addition control unit 210 notifies local residents that the evacuation shelter has been opened after the period for opening the evacuation shelter has elapsed. Specifically, the evacuation shelter addition control unit 210 sends "additional evacuation shelter information" including information about the additional evacuation shelter (name, location, etc.) to the resident terminal 30 (step S23).

In this way, when the disaster prevention officer agrees to the opening of a new shelter, the shelter addition control unit 210 transmits shelter addition information, including information about the new shelter, to the resident terminals 30 carried by each of the multiple residents.

The resident terminal 30 provides the acquired additional evacuation shelter information to residents. Residents who come across the additional evacuation shelter information will recognize that a new evacuation shelter has been opened, and will evacuate to that shelter if necessary.

As described above, the server device 10 according to the fourth embodiment estimates the status of evacuation shelters when an actual disaster occurs, and if it determines that there are not enough open evacuation shelters, it notifies the disaster prevention officer of this fact. If the disaster prevention officer agrees to the opening of additional evacuation shelters, the server device 10 notifies residents of information about the newly added evacuation shelter. Residents can decide whether to evacuate to a pre-determined evacuation shelter or to a newly opened evacuation shelter in accordance with the notification.

Next, we will explain the hardware of each device that makes up the disaster prevention system. Figure 35 is a diagram showing an example of the hardware configuration of the server device 10.

The server device 10 can be configured by an information processing device (so-called a computer), and has the configuration shown in FIG. 35. For example, the server device 10 has a processor 311, a memory 312, an input/output interface 313, a communication interface 314, and the like. The components such as the processor 311 are connected by an internal bus or the like, and are configured to be able to communicate with each other.

However, the configuration shown in FIG. 35 is not intended to limit the hardware configuration of the server device 10. The server device 10 may include hardware not shown, and may not include an input/output interface 313 as necessary. Furthermore, the number of processors 311 and the like included in the server device 10 is not intended to be limited to the example shown in FIG. 35, and for example, the server device 10 may include multiple processors 311.

The processor 311 is, for example, a programmable device such as a CPU (Central Processing Unit), an MPU (Micro Processing Unit), or a DSP (Digital Signal Processor). Alternatively, the processor 311 may be a device such as an FPGA (Field Programmable Gate Array) or an ASIC (Application Specific Integrated Circuit). The processor 311 executes various programs including an operating system (OS).

Memory 312 is a RAM (Random Access Memory), a ROM (Read Only Memory), a HDD (Hard Disk Drive), a SSD (Solid State Drive), etc. Memory 312 stores the OS program, application programs, and various data.

The input/output interface 313 is an interface for a display device and an input device (not shown). The display device is, for example, a liquid crystal display. The input device is, for example, a device that accepts user operations such as a keyboard or a mouse.

The communication interface 314 is a circuit, module, etc. that communicates with other devices. For example, the communication interface 314 includes a NIC (Network Interface Card), etc.

The functions of the server device 10 are realized by various processing modules. The processing modules are realized, for example, by the processor 311 executing a program stored in the memory 312. The program can be recorded on a computer-readable storage medium. The storage medium can be a non-transitory medium such as a semiconductor memory, a hard disk, a magnetic recording medium, or an optical recording medium. That is, the present invention can also be embodied as a computer program product. The program can be downloaded via a network, or updated using a storage medium that stores the program. The processing modules may also be realized by a semiconductor chip.

The disaster prevention terminal 20 and the resident terminal 30 can also be configured using information processing devices, just like the server device 10, and their basic hardware configuration is no different from that of the server device 10, so a description of them will be omitted.

The server device 10, which is an information processing device, is equipped with a computer, and the functions of the server device 10 can be realized by causing the computer to execute a program. In addition, the server device 10 executes a control method for the server device 10 by the program.

[Modification]
The configuration, operation, etc. of the disaster prevention system described in the above embodiment are merely examples, and are not intended to limit the system configuration, etc.

In the above embodiment, the server device 10 uses a hazard map to advise residents. However, the hazard map can also be used for other purposes. For example, when the server device 10 determines that the opening of a shelter is inappropriate using the hazard map when the evacuation shelter opening conditions are input, the server device 10 may notify a disaster prevention officer of this fact. For example, the server device 10 may eliminate a shelter opening condition such as opening a shelter in an area where flooding is expected.

Alternatively, the server device 10 may perform control with reference to information on past disasters when a disaster prevention officer considers opening a shelter. For example, in the case of a disaster caused by a typhoon, the server device 10 may provide the disaster prevention officer with information on opening a shelter with reference to the damage situation of a typhoon similar to the approaching typhoon. For example, the server device 10 determines whether the number of shelters registered by the officer is appropriate based on the number of shelters that were opened when a typhoon of the same scale as the currently occurring typhoon occurred. If it is determined that the number of shelters is insufficient, the server device 10 notifies the officer of that effect.

In the above embodiment, it has been described that, in addition to personal information, residential information and family information are registered in the server device 10 when a resident registers. In addition to this information, the resident may also register health information in the server device 10. For example, information such as chronic illnesses and care levels may be registered in the server device 10. Furthermore, the server device 10 may generate advice information based on the resident's health information. For example, when receiving an evacuation action plan for a resident who requires care, the server device 10 may take measures such as recommending an evacuation shelter equipped with care facilities as an evacuation destination.

In the second embodiment, a case has been described in which the local government (disaster prevention personnel) reviews the evacuation shelter opening conditions based on the disaster countermeasures information generated by the server device 10. However, the disaster prevention personnel may also review the number of staff to be assigned to each evacuation shelter, etc., based on the disaster countermeasures information. For example, the disaster prevention personnel may assign a large number of staff to evacuation shelters with a high evacuation action plan registration rate, and a small number of staff to evacuation shelters with a low registration rate. In this way, staff response plans for evacuation shelters that are expected to be crowded may be reviewed based on the disaster countermeasures information.

In the third embodiment, the server device 10 provides advice regarding an evacuation action plan. However, the server device 10 may provide advice from a broader perspective to the resident who has set the evacuation action plan. For example, the server device 10 grasps the family structure of the resident based on the resident's family information. The server device 10 may provide advice regarding stockpiles, etc. based on the family structure. For example, the server device 10 may create a stockpiled item list based on the family structure and provide the information to the resident along with the number of bottles of drinking water to be stockpiled, etc.

In the third embodiment, the server device 10 provides advice on the evacuation action plan set by the resident. However, the server device 10 identifies the resident who sets the evacuation action plan based on the resident ID included in the request for providing evacuation shelter information. The server device 10 may determine an evacuation action plan suitable for the identified resident and present the determined evacuation action plan to the resident as a recommended value (initial value). For example, the server device 10 may present to the resident an evacuation action plan that evacuates the elderly earlier than the young person as an initial value. In this way, the server device 10 may determine the initial value (recommended value) of the evacuation action plan based on the attributes of the resident to improve the convenience of the resident. Alternatively, the server device 10 may display reference information such as an evacuation action plan determined based on the attributes of each resident by pop-up or the like while making the initial value of the evacuation action plan common to each resident.

In the third embodiment, instead of the server device 10, the local government (disaster prevention officer) may provide advice to residents. In this case, the server device 10 transmits the evacuation action plan acquired from the resident to the disaster prevention terminal 20. The disaster prevention terminal 20 acquires advice for the resident from the local government and transmits it to the resident terminal 30 of the corresponding resident.

In the fourth embodiment, the case has been described where the capacity of each evacuation shelter is estimated based on a preset evacuation action plan, and the estimated capacity is used to calculate the occupancy rate (crowding rate). However, the server device 10 according to the fourth embodiment may calculate the occupancy rate using the actual number of residents evacuated to each evacuation shelter. For example, the server device 10 may obtain the number of residents who have evacuated to the evacuation shelter from staff stationed at each evacuation shelter. Alternatively, the server device 10 may obtain biometric information of each resident when registering residents, and ascertain the number of residents who have evacuated to the evacuation shelter through biometric authentication using the biometric information. In this case, the server device 10 may obtain the biometric information of the person to be authenticated from a terminal installed at the evacuation shelter.

In the fourth embodiment, the server device 10 may propose multiple evacuation shelters when proposing a new evacuation shelter to be opened.

The server device 10 may provide information using river water level information. Here, important information regarding the evacuation of residents is water level information of nearby rivers. Because warnings accompanied by alert levels are issued for a certain area, it is expected that there will be areas where evacuation will not be made in time before the river overflows. Therefore, for residents who live in an area within a certain distance from the river, the server device 10 may use the river water level information as the evacuation timing and transmit evacuation information to the residents. In this case, the residents set the water level information as the evacuation start risk level during a disaster such as heavy rain or a typhoon. When the water level of a river flowing near the resident reaches the evacuation start risk level, the server device 10 transmits evacuation information to the residents for whom the risk level has been set, encouraging them to evacuate.

Alternatively, when the water level of a river actually exceeds a designated value, the server device 10 may send a notification urging residents living near the river to evacuate. The targets of the notification urging evacuation are selected to be residents who will be affected by the river overflowing, such as residents living within a certain range of the river location where the river exceeded the designated value and residents who have selected water level information as the evacuation start risk level. In this way, when a disaster occurs and the river water level reaches a dangerous level, the server device 10 notifies surrounding residents that danger is approaching and urges them to evacuate.

The evacuation action plan entered by the resident may be shared (synchronized) with family members living together, family members living far away, acquaintances, and friends. For example, the server device 10 may treat the evacuation action plan entered by a child as the evacuation action plan of the parent living together that the child registered as family information. In this way, the server device 10 enables the child to create an evacuation action plan on behalf of the elderly parent. Alternatively, the server device 10 may notify the family member entered as family information of the evacuation action plan. For example, the server device 10 may transmit the evacuation action plan entered by the child to the resident terminal 30 owned by the parent. This response satisfies the need of the parent to check the evacuation action plan of the family member (for example, the child). In this way, the sharing of the evacuation action plan may be performed by the child entering the parent's evacuation action plan, or the parent checking the child's evacuation action plan.

The server device 10 may identify evacuation shelters that are not known by the local government from the evacuation action plans of multiple residents. There may be evacuation shelters that are managed by voluntary disaster prevention organizations and are not known by the local government. Due to the existence of such evacuation shelters, the local government cannot know how many evacuees are accommodated in each evacuation shelter. However, it is important to know the number of evacuees from the perspective of providing supplies. Therefore, if multiple residents have registered the same place as an evacuation destination, the server device 10 presumes that it is an evacuation shelter decided by a neighborhood association or the like (an evacuation shelter not known by the local government) and registers the evacuation shelter as one of the evacuation destinations. At this time, since the registration of residents from the same family may be a private evacuation destination such as an acquaintance's house, the server device 10 may determine whether or not a evacuation shelter is registered by adding conditions such as when the number of registrations is more than a certain number or when residents with different basic information such as names have registered. In this way, by the local government sharing the evacuation destinations registered by residents, evacuation shelters that the local government does not know are identified.

In the above embodiment, the case where evacuation information is transmitted to residents living in the area managed by the local government has been described. However, the evacuation information may be transmitted to non-residents of the area. For example, the evacuation information may be transmitted to tourists in the target area. For example, a pamphlet is given to tourists who visit a disaster prevention target area (tourist destination). The pamphlet contains a two-dimensional code with information embedded therein for accessing the server device 10. The tourists access the server device 10 using the two-dimensional code and register their contact information, such as an email address. When a disaster occurs, the server device 10 transmits evacuation information including information about evacuation shelters to the acquired contact information. At that time, the server device 10 can notify the tourists that a business hotel or the like is an evacuation destination. Alternatively, the server device 10 may transmit the evacuation information to a digital signage installed in the tourist destination. The digital signage displays the location of the evacuation shelter, etc.

The server device 10 may not only support disaster prevention personnel using disaster countermeasure information, but also provide more proactive support using basic data and evacuation shelter opening conditions input by the disaster prevention personnel. For example, the server device 10 may automatically determine the staff to be assigned to each evacuation shelter and present it to the disaster prevention personnel. Here, the number of staff required to operate the evacuation shelter differs depending on whether the number of residents evacuated to the evacuation shelter is small or large. On the other hand, since there is an upper limit on the number of staff in a local government, it is difficult to make a uniform and generous allocation plan. Therefore, the server device 10 may calculate the number of staff to be assigned to the evacuation shelter based on the expected number of evacuees and present it to the local government (disaster prevention personnel). For example, the server device 10 may estimate the number of evacuees based on the number of people registered in the evacuation action plan at each evacuation shelter, or may calculate the number of evacuees comprehensively based on multiple indicators such as the size of the evacuation shelter and the damage situation in the neighborhood. In addition, with regard to the supplies required at the evacuation shelter, the server device 10 may estimate the number of evacuees at the evacuation shelter, calculate the amount of supplies required, and present it to the local government (disaster prevention personnel). In this way, the server device 10 may estimate the number of staff and supplies to be allocated to each evacuation shelter based on the estimated number of evacuees at each shelter during peacetime before a disaster occurs.

When a disaster occurs, the server device 10 may check the safety of local residents. Specifically, the server device 10 transmits a "safety confirmation notification" to the resident terminal 30 of each registered resident. The resident terminal 30 that receives the notification notifies the server device 10 of the resident's status (e.g., evacuated to evacuation destination, waiting at home). The server device 10 may calculate the evacuation rate of the area from the response results obtained from the resident terminal 30 and present it to disaster prevention personnel. Alternatively, the server device 10 may notify residents who have not yet evacuated of the calculated evacuation rate to encourage those residents (residents who have not yet started evacuating) to evacuate. In other words, the server device 10 makes the residents who have not evacuated recognize that "everyone around them is evacuating" and encourages them to evacuate.

Alternatively, the server device 10 may link the provision of evacuation information with safety confirmation. The server device 10 manages residents who have received evacuation information using a resident information database. When a resident who has received the evacuation information has not evacuated after a specified period of time has passed (when there is no response to the safety confirmation notification), the server device 10 may notify the local government of information about the resident who has not evacuated (such as name and address).

When a resident evacuates to an evacuation shelter (arrives at an evacuation shelter) in accordance with the evacuation action plan, the resident may notify the server device 10 of that fact. Specifically, when a resident arrives at an evacuation shelter, the resident terminal 30 may send an "evacuation completion notification" to the server device 10. The server device 10 may calculate the capacity of each evacuation shelter based on the notification.

In the above embodiment, with reference to FIG. 15, a case has been described in which a disaster prevention officer inputs disaster information into the server device 10. However, the server device 10 may obtain the disaster information from an external server (e.g., a server operated by the Japan Meteorological Agency, etc.). In other words, the server device 10 may automatically obtain the disaster risk level, such as the alert level and seismic intensity, from an external server (external organization).

The server device 10 may not only provide disaster prevention personnel with disaster countermeasure information calculated from the evacuation action plan in dashboard format, but may also provide other information to the personnel in dashboard format. For example, the server device 10 may display a list of settings (combinations of disasters and evacuation shelter opening risk levels) set for each evacuation shelter. Alternatively, the server device 10 may display a list of evacuation shelters with evacuation shelter opening risk levels set to a predetermined value or higher.

The resident terminal 30 may provide an interface that allows residents to check the evacuation action plan that they have set themselves. For example, when the "OK" button in FIG. 20 is pressed, the resident terminal 30 may display a list of evacuation start conditions that have already been set. While displaying the list, the resident terminal 30 may output a message prompting the resident to check whether there are any errors or omissions in the evacuation action plan settings.

In the above embodiment, a case has been described in which the resident information database and the evacuation shelter information database are configured inside the server device 10, but these databases may also be configured on an external database server or the like. That is, some of the functions of the server device 10 may be implemented on another server. More specifically, the above-described "action plan management unit (action plan management means)" and "evacuation information control unit (evacuation information control means)" may be implemented on any of the devices included in the system.

The server device 10 may verify the identity of a resident during resident registration. Specifically, during resident registration, the server device 10 acquires the resident's biometric information (e.g., a facial image) and an identification document (e.g., a passport, a driver's license, etc.) containing the biometric information. The server device 10 performs one-to-one matching using the biometric information on the identification document and the biometric information acquired from the resident. If the matching is successful, the server device 10 may perform resident registration.

The form of data transmission and reception between each device (server device 10, disaster prevention terminal 20, resident terminal 30) is not particularly limited, but data transmitted and received between these devices may be encrypted. Residents' personal information, etc. is transmitted and received between these devices, and in order to appropriately protect this information, it is desirable to transmit and receive encrypted data.

In the flow diagrams (flowcharts, sequence diagrams) used in the above explanation, multiple steps (processes) are described in order, but the order in which the steps are executed in the embodiment is not limited to the order described. In the embodiment, the order of the steps shown in the diagrams can be changed to the extent that does not interfere with the content, such as executing each process in parallel.

The above embodiments have been described in detail to facilitate understanding of the present disclosure, and it is not intended that all of the configurations described above are necessary. Furthermore, when multiple embodiments are described, each embodiment may be used alone or in combination. For example, it is possible to replace part of the configuration of an embodiment with the configuration of another embodiment, or to add the configuration of another embodiment to the configuration of an embodiment. Furthermore, it is possible to add, delete, or replace part of the configuration of an embodiment with other configurations.

The above explanation makes clear the industrial applicability of the present invention, and the present invention can be suitably applied to disaster prevention systems that assist residents in evacuating.

A part or all of the above-described embodiments can be described as, but is not limited to, the following supplementary notes.
[Appendix 1]
an acquisition unit that acquires evacuation shelter opening conditions that define conditions for opening a candidate evacuation shelter as an evacuation shelter for each disaster;
A management unit that manages an evacuation action plan including an evacuation start condition and an evacuation destination, the evacuation start condition being set for each of a plurality of residents based on the evacuation shelter opening conditions and defining a condition for starting evacuation for each disaster;
A server device comprising:
[Appendix 2]
The server device described in Appendix 1 further comprises an evacuation information control unit that, when a disaster occurs or when a disaster is expected to occur, obtains a disaster risk level indicating the degree of risk of a disaster from a disaster prevention officer, extracts residents from the multiple residents who satisfy the evacuation start condition based on the disaster risk level, and transmits evacuation information including information regarding the evacuation destination to a resident terminal carried by the extracted resident.
[Appendix 3]
The server device according to claim 2, wherein the evacuation shelter opening conditions include a evacuation shelter opening risk level indicating the risk of a disaster that will trigger the opening of the evacuation shelter candidate as an evacuation shelter.
[Appendix 4]
The server device according to claim 3, wherein the evacuation start condition includes an evacuation start risk level indicating a disaster risk level that will trigger each resident to start evacuation in the event of a disaster.
[Appendix 5]
The server device described in Appendix 4, wherein the evacuation information control unit extracts from among the plurality of residents residents who have set the evacuation start condition such that the evacuation start risk level is lower than or equal to the disaster risk level for a disaster that matches the type of disaster entered by the disaster prevention officer together with the disaster risk level.
[Appendix 6]
The server device according to any one of appendices 2 to 4, wherein the evacuation information control unit transmits the evacuation information, including map information reflecting the extracted resident's home and the location of the evacuation destination, to the resident terminal.
[Appendix 7]
6. The server device according to claim 2, further comprising a disaster countermeasure information generation unit that generates disaster countermeasure information effective for disaster countermeasures based on the evacuation action plans set by each of the plurality of residents.
[Appendix 8]
The server device according to claim 7, wherein the disaster countermeasures information generation unit calculates a registration rate for the evacuation action plan for each resident attribute as the disaster countermeasures information.
[Appendix 9]
The server device according to any one of appendices 2 to 8, further comprising an advice information control unit that generates advice information for the set evacuation action plan in response to a resident setting the evacuation action plan, and transmits the generated advice information to the resident terminal of the resident who set the evacuation action plan.
[Appendix 10]
The server device according to claim 9, wherein the advice information control unit generates the advice information based on residential information of residents.
[Appendix 11]
A shelter addition control unit is further provided that estimates the occupancy rate of the shelter opened in accordance with the shelter opening conditions and determines whether or not a new shelter needs to be opened based on the estimated occupancy rate;
The server device described in any one of Appendices 2 to 10, wherein the shelter addition control unit sends shelter addition information including information regarding the new shelter to the resident terminal carried by each of the multiple residents when the disaster prevention officer agrees to the opening of the new shelter.
[Appendix 12]
The server device described in Appendix 11, wherein the shelter addition control unit estimates the capacity of the opened shelter from the number of residents who have registered the opened shelter as an evacuation destination in the evacuation action plan, and estimates the occupancy rate of the opened shelter based on the capacity of the opened shelter and the estimated capacity.
[Appendix 13]
A resident terminal;
A server device;
Including,
The server device includes:
an acquisition unit that acquires evacuation shelter opening conditions that define conditions for opening a candidate evacuation shelter as an evacuation shelter for each disaster;
A management unit that manages an evacuation action plan including an evacuation start condition and an evacuation destination, the evacuation start condition being set for each of a plurality of residents based on the evacuation shelter opening conditions and defining a condition for starting evacuation for each disaster;
an evacuation information control unit that, when a disaster occurs or when the occurrence of a disaster is expected, acquires a disaster risk level indicating a degree of risk of a disaster from a disaster prevention officer, extracts residents who satisfy the evacuation start condition from among the plurality of residents based on the disaster risk level, and transmits evacuation information including information regarding the evacuation destination to the resident terminal carried by the extracted resident;
A system comprising:
[Appendix 14]
In the server device,
For each disaster, we obtain evacuation shelter opening conditions that stipulate the conditions for opening a potential evacuation shelter as an evacuation shelter;
A control method for a server device that manages evacuation start conditions, which stipulate conditions for starting evacuation for each disaster, and evacuation action plans, which include evacuation destinations, set for each of a plurality of residents based on the evacuation shelter opening conditions.
[Appendix 15]
A computer installed in the server device
A process of acquiring evacuation shelter opening conditions that define conditions for opening a candidate evacuation shelter as an evacuation shelter for each disaster;
A process of managing an evacuation action plan including an evacuation start condition and an evacuation destination, the evacuation start condition being set for each of a plurality of residents based on the evacuation shelter opening conditions, and the evacuation action plan including an evacuation destination, the evacuation start condition being set for each of a plurality of residents based on the evacuation shelter opening conditions;
A program for executing.

The disclosures of the above cited prior art documents are incorporated herein by reference. Although the embodiments of the present invention have been described above, the present invention is not limited to these embodiments. Those skilled in the art will understand that these embodiments are merely illustrative and that various modifications are possible without departing from the scope and spirit of the present invention. In other words, the present invention naturally includes various modifications and amendments that a person skilled in the art can make in accordance with the entire disclosure, including the scope of the claims, and the technical ideas.

10 Server device 20 Disaster prevention terminal 30 Resident terminal 30-1 Resident terminal 30-2 Resident terminal 30-3 Resident terminal 100 Server device 101 Acquisition unit 102 Management unit 201 Communication control unit 202 Resident registration unit 203 Basic data acquisition unit 204 Opening condition acquisition unit 205 Action plan management unit 206 Evacuation information control unit 207 Memory unit 208 Disaster countermeasure information generation unit 209 Advice information control unit 210 Evacuation shelter addition control unit 301 Communication control unit 302 Resident registration request unit 303 Action plan control unit 304 Evacuation information processing unit 305 Memory unit 311 Processor 312 Memory 313 Input/output interface 314 Communication interface

Claims (13)

an acquisition unit that acquires evacuation shelter opening conditions that define conditions for opening a candidate evacuation shelter as an evacuation shelter for each disaster;
A management unit that manages an evacuation action plan including an evacuation start condition and an evacuation destination, the evacuation start condition being set for each of a plurality of residents based on the evacuation shelter opening conditions and defining a condition for starting evacuation for each disaster;
an evacuation information control unit that, when a disaster occurs or when the occurrence of a disaster is expected, acquires a disaster risk level indicating a degree of risk of a disaster from a disaster prevention officer, extracts residents who satisfy the evacuation start condition from among the plurality of residents based on the disaster risk level, and transmits evacuation information including information regarding the evacuation destination to a resident terminal carried by the extracted resident;
a shelter addition control unit that estimates the occupancy rate of the shelter opened in accordance with the shelter opening conditions and determines whether or not a new shelter needs to be opened based on the estimated occupancy rate;
Equipped with
The shelter addition control unit is a server device that, when the disaster prevention officer agrees to the opening of the new shelter, sends shelter addition information including information regarding the new shelter to the resident terminal carried by each of the multiple residents . The server device according to claim 1 , wherein the evacuation shelter establishment conditions include a degree of risk of a disaster that will trigger the evacuation shelter candidate to be established as a evacuation shelter. The server device according to claim 2 , wherein the evacuation start condition includes an evacuation start risk indicating a disaster risk that will trigger each resident to start evacuation in the event of a disaster. The server device described in claim 3, wherein the evacuation information control unit extracts from among the plurality of residents residents who have set the evacuation start condition such that the evacuation start risk level is lower than or equal to the disaster risk level for a disaster that matches the type of disaster input by the disaster prevention officer together with the disaster risk level . The server device according to claim 1 , wherein the evacuation information control unit transmits the evacuation information, including map information reflecting the extracted resident's house and the location of the evacuation destination, to the resident terminal. The server device according to claim 1 , further comprising a disaster countermeasure information generating unit configured to generate disaster countermeasure information effective for disaster countermeasures based on the evacuation action plans set by each of the plurality of residents. The server device according to claim 6 , wherein the disaster countermeasure information generating unit calculates a registration rate of the evacuation action plan for each attribute of a resident as the disaster countermeasure information. The server device according to any one of claims 1 to 7, further comprising an advice information control unit that generates advice information for the set evacuation action plan in response to a resident setting the evacuation action plan , and transmits the generated advice information to the resident terminal of the resident who set the evacuation action plan. The server device according to claim 8 , wherein the advice information control unit generates the advice information based on residential information of residents. The server device described in claim 1, wherein the shelter addition control unit estimates the capacity of the opened shelter from the number of residents who have registered the opened shelter as an evacuation destination in the evacuation action plan, and estimates the occupancy rate of the opened shelter based on the capacity of the opened shelter and the estimated capacity. A resident terminal;
A server device;
Including,
The server device includes:
an acquisition unit that acquires evacuation shelter opening conditions that define conditions for opening a candidate evacuation shelter as an evacuation shelter for each disaster;
A management unit that manages an evacuation action plan including an evacuation start condition and an evacuation destination, the evacuation start condition being set for each of a plurality of residents based on the evacuation shelter opening conditions and defining a condition for starting evacuation for each disaster;
an evacuation information control unit that, when a disaster occurs or when the occurrence of a disaster is expected, acquires a disaster risk level indicating a degree of risk of a disaster from a disaster prevention officer, extracts residents who satisfy the evacuation start condition from among the plurality of residents based on the disaster risk level, and transmits evacuation information including information regarding the evacuation destination to the resident terminal carried by the extracted resident;
a shelter addition control unit that estimates the occupancy rate of the shelter opened in accordance with the shelter opening conditions and determines whether or not a new shelter needs to be opened based on the estimated occupancy rate;
Equipped with
The system includes a shelter addition control unit that, when the disaster prevention officer agrees to the opening of the new shelter, sends shelter addition information including information regarding the new shelter to the resident terminal carried by each of the multiple residents . In the server device,
For each disaster, we obtain evacuation shelter opening conditions that stipulate the conditions for opening a potential evacuation shelter as an evacuation shelter;
Based on the evacuation shelter opening conditions, an evacuation action plan including an evacuation start condition and an evacuation destination, which is set for each of a plurality of residents and defines a condition for starting evacuation for each disaster , is managed;
When a disaster occurs or when the occurrence of a disaster is expected, a disaster risk level indicating the degree of risk of the disaster is obtained from a disaster prevention officer, residents who satisfy the evacuation start condition are extracted from the plurality of residents based on the disaster risk level, and evacuation information including information regarding the evacuation destination is transmitted to a resident terminal carried by the extracted resident,
Estimating the occupancy rate of the evacuation shelter opened in accordance with the evacuation shelter opening conditions, and determining whether or not it is necessary to open a new evacuation shelter based on the estimated occupancy rate;
A method for controlling a server device , in which, when the disaster prevention officer agrees to the opening of the new evacuation shelter, evacuation shelter addition information including information regarding the new evacuation shelter is sent to the resident terminal carried by each of the plurality of residents . A computer installed in the server device
A process of acquiring evacuation shelter opening conditions that define conditions for opening a candidate evacuation shelter as an evacuation shelter for each disaster;
A process of managing an evacuation action plan including an evacuation start condition and an evacuation destination, the condition being set for each of a plurality of residents based on the evacuation shelter opening conditions, and the evacuation action plan including an evacuation destination and the condition being set for each of a plurality of residents based on the evacuation shelter opening conditions;
When a disaster occurs or when the occurrence of a disaster is expected, a process of obtaining a disaster risk level indicating the degree of risk of a disaster from a disaster prevention officer, extracting residents who satisfy the evacuation start condition from among the plurality of residents based on the disaster risk level, and transmitting evacuation information including information regarding the evacuation destination to a resident terminal carried by the extracted resident;
A process of estimating the occupancy rate of the evacuation shelter opened in accordance with the evacuation shelter opening conditions and determining whether or not it is necessary to open a new evacuation shelter based on the estimated occupancy rate;
When the disaster prevention officer agrees to the opening of the new evacuation shelter, a process of transmitting evacuation shelter addition information including information regarding the new evacuation shelter to the resident terminals possessed by each of the plurality of residents;
A program for executing.