JP7613161B2 - Rescue support system, rescue support method, and rescue support program - Google Patents

Description

The present invention relates to a rescue support system, a rescue support method, and a rescue support program.

Conventionally, systems are known that enable evacuees in the middle of evacuation to rescue those in need of rescue when a disaster, accident, etc. occurs. For example, Patent Document 1 discloses a system that acquires a rescue request and current location information of a person in need of rescue, as well as the current location information of the evacuee, and presents the evacuee with information on the evacuation site, evacuation route, and the person in need of rescue.

JP 2013-25785 A

However, with conventional technology, there is a problem that rescue efforts for the person in need of rescue are delayed if circumstances arise that make it difficult to rescue the person in need of rescue, such as when an evacuee who has received a rescue request is injured while moving to the rescue location for the person in need of rescue, or when traffic on the road to the rescue location is restricted.

The object of the present invention is to provide a rescue support system, a rescue support method, and a rescue support program that can quickly rescue a person in need of rescue.

A rescue support system according to one aspect of the present invention is a system including an acquisition processing unit that acquires a rescue request from a person in need of rescue, a decision processing unit that decides a rescuer for the person in need of rescue based on the rescue request, an output processing unit that outputs the rescue request to the rescuer, an allocation processing unit that assigns the rescuer to the person in need of rescue when a response indicating acceptance of the rescue request is acquired from the rescuer, and a release processing unit that releases the allocation of the rescuer to the person in need of rescue when a predetermined condition is satisfied after the rescuer is assigned to the person in need of rescue by the allocation processing unit.

In this way, the rescue support system can quickly release the rescuer from the rescue request when a certain condition is met after the rescuer has been assigned to the rescue request, and can quickly determine another rescuer who can rescue the rescue request. This prevents delays in rescue operations for the rescue request, and makes it possible to quickly rescue the rescue request.

A rescue support method according to another aspect of the present invention is a method in which one or more processors execute an acquisition step of acquiring a rescue request from a person in need of rescue, a decision step of deciding a rescuer for the person in need of rescue based on the rescue request, an output step of outputting the rescue request to the rescuer, an assignment step of assigning the rescuer to the person in need of rescue when a response indicating acceptance of the rescue request is obtained from the rescuer, and a release step of releasing the assignment of the rescuer to the person in need of rescue when a predetermined condition is satisfied after the rescuer is assigned to the person in need of rescue in the assignment step.

A rescue support program according to another aspect of the present invention is a program for causing one or more processors to execute the following steps: an acquisition step of acquiring a rescue request from a person in need of rescue; a decision step of deciding a rescuer for the person in need of rescue based on the rescue request; an output step of outputting the rescue request to the rescuer; an allocation step of assigning the rescuer to the person in need of rescue when a response indicating acceptance of the rescue request is obtained from the rescuer; and a release step of canceling the allocation of the rescuer to the person in need of rescue when a predetermined condition is met after the rescuer is assigned to the person in need of rescue in the allocation step.

The present invention provides a rescue support system, a rescue support method, and a rescue support program that can quickly rescue a person in need of rescue.

FIG. 1 is a functional block diagram showing a configuration of a rescue support system according to an embodiment of the present invention. FIG. 2 is a diagram showing an example of user information used in the rescue support system according to the embodiment of the present invention. FIG. 3 is a diagram showing an example of rescue requester information used in the rescue support system according to the embodiment of the present invention. FIG. 4 is a diagram showing an example of rescue candidate information used in the rescue support system according to the embodiment of the present invention. FIG. 5 is a diagram showing an example of a display screen displayed on the rescue requester terminal of the rescue support system according to the embodiment of the present invention. FIG. 6 is a diagram showing an example of a display screen displayed on the rescuer terminal of the rescue support system according to the embodiment of the present invention. FIG. 7 is a diagram showing an example of a display screen displayed on the rescuer terminal of the rescue support system according to the embodiment of the present invention. FIG. 8 is a diagram showing an example of a display screen displayed on the rescue requester terminal of the rescue support system according to the embodiment of the present invention. FIG. 9 is a diagram showing an example of a display screen displayed on the rescuer terminal of the rescue support system according to the embodiment of the present invention. FIG. 10 is a diagram showing an example of a display screen displayed on the rescue requester terminal of the rescue support system according to the embodiment of the present invention. FIG. 11 is a diagram showing an example of a display screen displayed on the rescuer terminal of the rescue support system according to the embodiment of the present invention. FIG. 12 is a diagram showing an example of a display screen displayed on the rescuer terminal of the rescue support system according to the embodiment of the present invention. FIG. 13 is a diagram showing an example of a display screen displayed on the rescuer terminal of the rescue support system according to the embodiment of the present invention. FIG. 14 is a flowchart showing an example of a procedure of a rescue support process executed in the rescue support system according to the embodiment of the present invention. FIG. 15 is a diagram showing an example of a display screen displayed on the rescuer terminal of the rescue support system according to the embodiment of the present invention. FIG. 16 is a diagram showing an example of a display screen displayed on the rescuer terminal of the rescue support system according to the embodiment of the present invention. FIG. 17 is a diagram showing an example of a display screen displayed on the rescuer terminal of the rescue support system according to the embodiment of the present invention.

The following describes embodiments of the present invention with reference to the attached drawings to facilitate understanding of the present invention. Note that each of the following embodiments is an example of the present invention and does not limit the technical scope of the present invention.

[Rescue support system 100]
1, a rescue support system 100 according to an embodiment of the present invention includes a rescue support device 1 and one or more user terminals 2 (a rescue requester terminal 2X and a rescuer terminal 2Y). The rescue support device 1 and the user terminals 2 can communicate with each other via a communication network N1 such as the Internet, a LAN, a WAN, or a public telephone line.

The rescue support device 1 is a system that, when it receives a rescue request from a person in need of rescue, searches for a rescuer who can rescue the person in need of rescue and outputs the rescue request to the rescuer, thereby supporting the rescue of the person in need of rescue. The rescue support device 1 provides a user with a rescue support service that supports the rescue of the person in need of rescue in response to the rescue request from the person in need of rescue. The rescue support device 1 is an information processing device that can receive a rescue request from the user terminal 2 (rescuer terminal 2X) of the person in need of rescue, output the rescue request to the user terminal 2 (rescuer terminal 2Y) of the rescuer, and display a route (travel route) from the current position of the rescuer to the rescue position of the person in need of rescue on a map of the rescuer terminal 2Y. The user terminal 2 is an information processing device that is operated by a user (rescuer) who requests rescue and a user (rescuer) who rescues the person in need of rescue, and acquires rescue information, route information, map information, and the like from the rescue support device 1.

In this embodiment, the user terminal 2 includes a user terminal 2 (hereinafter referred to as "rescuer terminal 2X") used by a user (rescuer) who uses the rescue support service to make a rescue request, and a user terminal 2 (hereinafter referred to as "rescuer terminal 2Y") used by a user (rescuer) who uses the rescue support service to rescue the rescuer in response to a rescue request. The rescue support system 100 may include multiple rescuer terminals 2X and multiple rescuer terminals 2Y. The user terminals 2 (rescuer terminal 2X, rescuer terminal 2Y) are examples of operation terminals of the present invention.

In this embodiment, the rescue support device 1 alone corresponds to the rescue support system of the present invention, but the rescue support system of the present invention may include one or more components of the rescue support device 1 and the user terminal 2. For example, if the components of the rescue support device 1, the rescue requester terminal 2X, and the rescuer terminal 2Y work together to share and execute the rescue support process (see FIG. 14) described below, a system including multiple components that execute the process may constitute the rescue support system of the present invention. For example, the rescue support device 1, the rescue requester terminal 2X, and the rescuer terminal 2Y may constitute the rescue support system of the present invention.

[Rescue support device 1]
As shown in Fig. 1, the rescue support device 1 includes a control unit 11, a storage unit 12, an operation display unit 13, a communication I/F 14, etc. The rescue support device 1 is an information processing device such as a personal computer. The rescue support device 1 is not limited to a single computer, and may be a computer system in which multiple computers work together. In addition, various processes executed by the rescue support device 1 may be executed in a distributed manner by one or multiple processors.

The communication I/F 14 is a communication interface that connects the rescue support device 1 to the communication network N1 by wire or wirelessly and performs data communication in accordance with a predetermined communication protocol with external devices such as the rescue requester terminal 2X and the rescuer terminal 2Y via the communication network N1.

The operation display unit 13 is a user interface that includes a display unit such as a liquid crystal display or an organic EL display that displays various information, and an operation unit such as a mouse, keyboard, or touch panel that accepts operations.

The storage unit 12 is a non-volatile storage unit including a semiconductor memory, a hard disk drive (HDD), or a solid state drive (SSD) that stores various information. For example, the storage unit 12 stores a control program such as a rescue support program for causing the control unit 11 to execute a rescue support process (see FIG. 14) described later. For example, the rescue support program is non-temporarily recorded on a computer-readable recording medium such as a USB, CD, or DVD (all of which are registered trademarks), and is read by a reading device (not shown) such as a USB drive, CD drive, or DVD drive that is electrically connected to the rescue support device 1 and stored in the storage unit 12. The rescue support program may be downloaded from an external device via the communication network N1 and stored in the storage unit 12.

The storage unit 12 also includes data such as user information D1, rescue requester information D2, and rescue candidate information D3. The storage unit 12 may also include road information (regulation information, traffic congestion information, accident information, etc.) obtained from an external server.

Figure 2 is a diagram showing an example of user information D1. User information D1 includes information on a user who can use the rescue support service. For example, user information D1 includes information such as a user ID, user name, email address, age, gender, current location, and rescue skills. The user installs an application for the rescue support service on, for example, the user terminal 2, and registers personal information such as a user ID, password (not shown), user name, email address, age, and gender on a registration screen. The user ID and password can be arbitrarily set by the user, and are used as login information when using the rescue support service. The email address is, for example, an email address for sending and receiving various information to and from the rescue support device 1.

The rescue skills are information indicating the rescue capabilities (rescue techniques, rescue knowledge, etc.) of the user. The rescue skills are set, for example, based on the user's past rescue activity performance (rescue history), rescue performance, attendance history of lifesaving courses, first aid courses, skill training courses, disaster prevention courses, etc., and the presence or absence of certification related to rescue and disaster prevention. The control unit 11 may register the rescue skills in the user information D1 based on the past rescue performance, etc., or may register the rescue skills in the user information D1 based on the user's registration operation. The control unit 11 registers, for example, a five-level evaluation value as the rescue skill based on each of the above information.

The current location is information that indicates the user's current location. For example, the control unit 11 registers location information obtained from the user's user terminal 2 in the user information D1. The control unit 11 updates the current location in real time.

A user registered in user information D1 can request rescue as a person in need of rescue if he or she becomes affected by a disaster or is injured, and can also participate in rescue activities to rescue a person in need of rescue as a rescuer. For example, if the rescue support service is introduced as part of mutual aid in a specific area, information on residents of the specific area is registered in user information D1. This enables residents of the specific area to use the rescue support service to request rescue and carry out rescue activities. Note that users aged 65 or older (elderly people) may be prohibited from acting as rescuers.

3 is a diagram showing an example of rescue requester information D2. Rescue requester information D2 includes information about a rescue requester who has made a rescue request. For example, rescue requester information D2 includes information such as a user ID, a current location, a rescue request time, and a rescue level. The current location is information indicating the current location of the rescue requester (an example of a rescue location of the present invention). For example, the control unit 11 registers location information acquired from the rescue requester's rescue requester terminal 2X in the rescue requester information D2. The control unit 11 updates the current location in real time. Note that the rescue location of the present invention is not limited to the current location of the rescue requester, and may be a location specified by the rescue requester. The rescue request time is the time when the rescue requester made the rescue request, i.e., the time when the control unit 11 acquired the rescue request from the rescue requester's rescue requester terminal 2X of the rescue requester.

The rescue level is information indicating the degree of difficulty or urgency of rescuing the person requiring rescue. For example, if the person requiring rescue is elderly and cannot walk on his/her own or is injured, the rescue level is set to the maximum level "3". Also, for example, if the person requiring rescue is not elderly and can walk on his/her own or is not injured, the rescue level is set to the minimum level "1". In this way, the rescue level is set according to the attributes of the person requiring rescue (age, sex, etc.), walking condition, injury condition, etc. In addition, the rescue level may be set according to the current location of the person requiring rescue. For example, if the current location of the person requiring rescue is in a place where disasters are likely to occur (along the mountains, along the sea, along the river, etc.), the rescue level is set to a high level. When the control unit 11 receives a rescue request from the person requiring rescue, it determines the rescue level based on each of the information related to the person requiring rescue and registers it in the rescue request information D2. The rescue level of the present invention is set based on at least one of information on whether the person requiring rescue can walk or not and information on whether the person requiring rescue is injured or not.

Figure 4 is a diagram showing an example of rescue candidate information D3. The rescue candidate information D3 includes information about users (rescue candidates) who are candidates for rescuers to be assigned (matched) to the rescue requester. The control unit 11 searches for rescue candidates from among the users registered in the user information D1 based on information such as the attributes (age, sex, etc.) of the rescue requester, the current location, and the rescue level. For example, if the rescue requester is an elderly male who cannot walk on his/her own and is injured, the control unit 11 searches for young males with high rescue skills as rescue candidates. For example, if the rescue requester is an elderly female who can walk on her/her own and is not injured, the control unit 11 searches for young females as rescue candidates regardless of rescue skills. In addition, if one of the roads leading to the current location of the rescue requester is subject to traffic restrictions, the control unit 11 searches for users who can use the other road as rescue candidates. The control unit 11 determines (matches) a rescuer to be assigned to the rescue requester from among the rescue candidates.

The rescue candidate information D3 includes information such as candidate rank, user ID, current location, and estimated arrival time. The candidate rank is information indicating the priority order determined for the rescuer. For example, if a user (user A5) with candidate rank "1" is determined as the rescuer but is not assigned to the rescue requester A2, the next user with candidate rank "2" (user A8) is determined as the rescuer. The current location is information indicating the current location of the rescuer. For example, the control unit 11 registers location information obtained from the rescuer's rescuer terminal 2Y in the rescue candidate information D3. The control unit 11 updates the current location in real time.

The estimated arrival time is information indicating the estimated time when a rescuer will arrive at the current location of the person in need of rescue. When the control unit 11 acquires a rescue request, it calculates the estimated arrival time based on the distance from the current location of the rescue candidate to the current location of the person in need of rescue and the travel speed of the means of transportation (car, walking, etc.), and registers it in the rescue candidate information D3. The control unit 11 may also calculate the remaining time from the current time to the estimated arrival time, and register it in the rescue candidate information D3.

The control unit 11 may set the candidate ranking in order of earliest expected arrival time, or in order of proximity to the current location of the person in need of rescue, or in order according to the attributes of the rescuer (e.g., from youngest to oldest), or in order according to the rescue skills of the user information D1 (e.g., from highest to lowest rescue skills).

Rescue candidate information D3 is stored in the memory unit 12 for each person in need of rescue. Figure 4 is an example of rescue candidate information D3 corresponding to rescue requester A2 (user ID "0002") (see Figure 3). Each time the control unit 11 receives a rescue request from a person in need of rescue, it generates rescue candidate information D3 corresponding to each person in need of rescue individually and stores it in the memory unit 12.

At least one of the user information D1, rescue requester information D2, and rescue candidate information D3 in the memory unit 12 may be stored in a data server (not shown) installed outside the rescue support device 1. The data server may be configured as a single physical server, or may be configured as a cloud server constructed from multiple physical servers.

The control unit 11 has control devices such as a CPU, a ROM, and a RAM. The CPU is a processor that executes various arithmetic processes. The ROM is a non-volatile storage unit in which control programs such as a BIOS and an OS for causing the CPU to execute various arithmetic processes are stored in advance. The RAM is a volatile or non-volatile storage unit that stores various information, and is used as a temporary storage memory (work area) for various processes executed by the CPU. The control unit 11 controls the rescue support device 1 by executing the various control programs stored in advance in the ROM or the storage unit 12 by the CPU.

However, in conventional technology, if circumstances arise that make it difficult to rescue the person in need of rescue, such as when a rescuer who receives a rescue request is injured while moving to the rescue location for the person in need of rescue, or when traffic on the road to the rescue location is restricted, there is a problem that rescue efforts for the person in need of rescue are delayed. In contrast, the rescue support device 1 according to this embodiment makes it possible to quickly rescue the person in need of rescue.

Specifically, as shown in FIG. 1, the control unit 11 includes various processing units such as a reception processing unit 111, an acquisition processing unit 112, a decision processing unit 113, an output processing unit 114, an allocation processing unit 115, a notification processing unit 116, and a release processing unit 117. The control unit 11 functions as the various processing units by executing various processes according to the rescue support program with the CPU. Some or all of the processing units included in the control unit 11 may be configured with electronic circuits. The rescue support program may be a program for causing multiple processors to function as the various processing units.

The reception processing unit 111 receives an application to use the rescue support service from a user. For example, the user starts an application for the rescue support service on his/her own user terminal 2 and inputs a user ID and password on a login screen. The reception processing unit 111 acquires the user ID and password from the user terminal 2. If the acquired user ID and password are registered in user information D1 (see FIG. 2), the reception processing unit 111 authenticates the user and permits the use of the rescue support service. This allows the user to use the rescue support service. For example, the user (rescuer) can input a rescue request on the rescuer terminal 2X. In addition, the user (rescuer) can input his/her intention to accept the rescue request and participate in the rescue activity.

The acquisition processing unit 112 acquires the rescue request from the rescue requester's terminal 2X. The rescue request includes at least the current location (rescue location) of the rescue requester. The rescue request may also include at least one of the walking status and injury status of the rescue requester.

Here, as an example, the rescue request includes the current location, walking status, and injury status of the rescue requester. For example, as shown in FIG. 5, the rescue requester A2 (user ID "0002") inputs the current location in the input field K11 on the operation screen of the rescue requester terminal 2X. The control unit 11 may display the current location information on the rescue requester terminal 2X based on the location information acquired from the rescue requester terminal 2X. Also, as shown in FIG. 5, the rescue requester A2 may be able to select whether the current location is at home or outside the home. Also, the rescue requester A2 inputs the walking status in the input field K12 on the operation screen of the rescue requester terminal 2X. For example, the rescue requester A2 selects "cannot walk" if he/she cannot walk by himself/herself, and selects "can walk" if he/she can walk by himself/herself. Also, the rescue requester A2 inputs the injury status in the input field K13 on the operation screen of the rescue requester terminal 2X. For example, the rescue requester A2 selects "injured" if he/she is injured, and selects "not injured" if he/she is not injured.

When the rescue requester A2 inputs each item (K11 to K13) and presses the operation button K14 for "request rescue", the rescue requester terminal 2X of the rescue requester A2 outputs a rescue request associated with the user ID "0002" to the rescue support device 1. As a result, the acquisition processing unit 112 acquires the rescue request of the rescue requester A2 from the rescue requester terminal 2X. Here, an example is shown in which the acquisition processing unit 112 acquires the rescue request of the rescue requester A2 at "12:30" (see FIG. 5). When the acquisition processing unit 112 acquires the rescue request of the rescue requester A2, it registers each piece of information in the rescue requester information D2 (see FIG. 3). For example, since the rescue requester A2 is elderly ("84 years old"), unable to walk on his/her own, and injured, the acquisition processing unit 112 sets the rescue level to the maximum level "3" and registers it in the rescue requester information D2 (see FIG. 3). The acquisition processing unit 112 is an example of the acquisition processing unit of the present invention.

The determination processing unit 113 determines a rescuer for a person requiring rescue based on the rescue request of the person requiring rescue. That is, the determination processing unit 113 matches a rescuer suitable for the person requiring rescue. Specifically, the determination processing unit 113 searches for one or more rescue candidates corresponding to the person requiring rescue based on the rescue request of the person requiring rescue, and determines a rescuer for the person requiring rescue from among the multiple rescue candidates. The determination processing unit 113 also determines a rescuer based on at least any of the following information: the rescue location of the person requiring rescue, the scheduled time of arrival at the rescue location of the person requiring rescue (estimated arrival time), the attributes of the person requiring rescue (age, gender, etc.), the rescue level of the person requiring rescue, and the rescue skills of the rescue candidates.

For example, the determination processing unit 113 extracts one or more users who have not requested rescue, are under 65 years old, have a current location within a predetermined distance from the current location P2 of the rescue requester A2, and have rescue skills that meet the rescue level of the rescue requester A2, from among the users registered in the user information D1 (see FIG. 2). The determination processing unit 113 identifies the extracted users as rescue candidates and registers information about the rescue candidates in the rescue candidate information D3 (see FIG. 4). Here, the determination processing unit 113 identifies users A1, A5, and A8 as rescue candidates, sets the candidate ranking in order of the earliest scheduled time of arrival at the current location P2 of the rescue requester A2, and registers the rescue candidate information D3.

For example, if the rescue level of the person requiring rescue is "3", the decision processing unit 113 extracts users with rescue skills of "4" or "5" that satisfy the rescue level. Also, for example, if the rescue level of the person requiring rescue is "2", the decision processing unit 113 extracts users with rescue skills of "3" or "4" that satisfy the rescue level. Also, for example, if the rescue level of the person requiring rescue is "1", the decision processing unit 113 extracts users with rescue skills of "1" or "2" that satisfy the rescue level. In this way, by extracting users with rescue skills according to the rescue level and determining them as rescue candidates, it becomes possible to efficiently assign rescuers to a large number of people requiring rescue.

The determination processing unit 113 determines a rescuer for the rescue requester A2 from one or more rescue candidates A1, A5, A8 registered in the rescue candidate information D3. For example, the determination processing unit 113 determines a rescuer based on at least one of the following information: the current location P2 of the rescue requester A2, the estimated arrival time at the current location P2 of the rescue requester A2, the attributes of the rescue requester A2, the rescue level of the rescue requester A2, and the rescue skills of the rescue candidates A1, A5, A8. Here, the determination processing unit 113 determines the rescue candidate A5 (see FIG. 4), who is ranked first among the rescue candidates A1, A5, A8 and has the earliest estimated arrival time, as the rescuer.

In another embodiment, the decision processing unit 113 may determine multiple rescuers based on at least one of the following information: the current location P2 of the rescue requester A2, the estimated arrival time at the current location P2 of the rescue requester A2, the attributes of the rescue requester A2, the rescue level of the rescue requester A2, and the rescue skills of the rescue candidates A1, A5, and A8. The decision processing unit 113 is an example of a decision processing unit of the present invention.

The output processing unit 114 outputs a rescue request to the rescuer determined by the determination processing unit 113. Here, the output processing unit 114 outputs a rescue request from the rescue requester A2 to the rescuer terminal 2Y of the rescuer A5. The rescue request includes information such as the name, age, sex, current position P2, walking status, and injury status of the rescue requester A2. The output processing unit 114 is an example of the output processing unit of the present invention.

When the rescuer terminal 2Y of the rescuer A5 receives the rescue request from the rescue support device 1, it displays a rescue request screen on the operation display unit 23 (see FIG. 1). FIG. 6 shows an example of the rescue request screen displayed on the rescuer terminal 2Y of the rescuer A5. As shown in FIG. 6, the rescue request screen displays information related to the rescue request (rescuer information), a current position P5 of the rescuer A5, a current position P2 of the rescuer A2, a route R1 from the current position P5 to the current position P2, and map information M1 including a route R2 from the current position P2 to the evacuation shelter H1. Note that in the present invention, the display of the route R2 from the current position P2 to the evacuation shelter H1 may be omitted.

The rescue request screen shown in FIG. 6 also displays operation buttons K21 and K22 for the rescuer A5 to select whether or not to accept the rescue request from the rescue requester A2. When accepting the rescue request from the rescue requester A2, the rescuer A5 presses the "Go to rescue" operation button K21, and further selects the means of transportation (e.g., "car" or "walk") to the current position P5 of the rescue requester A2.

When rescuer A5 presses the "Go to rescue" operation button K21 on the rescue request screen, the allocation processing unit 115 acquires a response from rescuer A5 indicating that the rescue request of rescue requester A2 is accepted. When the allocation processing unit 115 acquires a response from rescuer A5 indicating that the rescue request of rescue requester A2 is accepted, the allocation processing unit 115 assigns rescuer A5 to rescue requester A2 (matches them). That is, the allocation processing unit 115 assigns user A5 as the rescuer for rescue requester A2. After pressing the "Go to rescue" operation button K21, rescuer A5 heads to rescue rescue requester A2 while checking map information M1. In addition, after rescuing rescue requester A2, rescuer A5 heads to evacuation shelter H1 together with rescue requester A2 while checking map information M1.

In response to this, rescuer A5 presses the "No rescue" operation button K22 if he does not accept the rescue request from rescue requester A2. When rescuer A5 presses the "No rescue" operation button K22 on the rescue request screen, the decision processing unit 113 decides on rescue candidate A8 (see FIG. 4), who is ranked second in the candidate order, as the rescuer. Here, the decision processing unit 113 decides on rescue candidate A8, who has the next earliest estimated arrival time after rescue candidate A5, as the rescuer, out of rescue candidates A1 and A8. Then, the output processing unit 114 outputs the rescue request from rescue requester A2 to rescuer terminal 2Y of rescuer A8.

When the rescuer terminal 2Y of the rescuer A8 receives the rescue request from the rescue support device 1, it displays a rescue request screen on the operation display unit 23 (see FIG. 1). FIG. 7 shows an example of the rescue request screen displayed on the rescuer terminal 2Y of the rescuer A8. As shown in FIG. 7, the rescue request screen displays information related to the rescue request (rescuer information), the current position P8 of the rescuer A8, the current position P2 of the rescuer A2, the route R1 from the current position P8 to the current position P2, and map information M1 including the route R2 from the current position P2 to the evacuation shelter H1. When accepting the rescue request from the rescuer A2, the rescuer A8 presses the "Go to rescue" operation button K21, and further selects a means of transportation (e.g., "car" or "walk") to the current position P5 of the rescuer A2.

When the rescuer A8 presses the "Go to rescue" operation button K21 on the rescue request screen, the allocation processing unit 115 acquires a response from the rescuer A8 indicating that the rescue request of the rescue requester A2 is accepted. When the allocation processing unit 115 acquires a response from the rescuer A8 indicating that the rescue request of the rescue requester A2 is accepted, the allocation processing unit 115 assigns the rescuer A8 to the rescue requester A2 (matches them). That is, the allocation processing unit 115 assigns the user A8 as a rescuer for the rescue requester A2. After the rescuer A8 presses the "Go to rescue" operation button K21, the rescuer A8 heads to rescue the rescue requester A2 while checking the map information M1. In addition, after rescuing the rescue requester A2, the rescuer A8 heads to the evacuation shelter H1 together with the rescue requester A2 while checking the map information M1. On the other hand, if the rescuer A8 does not accept the rescue request of the rescue requester A2, the rescuer A8 presses the "No rescue" operation button K22. The allocation processing unit 115 is an example of an allocation processing unit of the present invention.

In this way, the determination processing unit 113 repeats the process of determining a rescuer from among the rescue candidates until a rescuer who will accept the rescue request is found. If no rescuer who will accept the rescue request is found among the rescue candidates, the output processing unit 114 outputs (reports) the rescue request from rescue requester A2 to a rescue organization such as a fire department or city hall.

The notification processing unit 116 notifies the rescue requester's terminal 2X of the result of the allocation process (matching result) of rescuers to rescue requesters performed by the allocation processing unit 115. For example, when rescuer A5 is assigned to rescue requester A2, the notification processing unit 116 notifies the rescue requester's terminal 2X of rescue requester A2 of information about rescuer A5 (name, age, gender, etc.) and expected arrival information T1 such as the expected arrival time and the remaining time from the current time to the expected arrival time.

When the rescue requester's terminal 2X of the rescue requester A2 acquires the matching result from the rescue support device 1, it displays rescue information on the operation display unit 23 (see FIG. 1). FIG. 8 shows an example of a rescue information screen displayed on the rescue requester's terminal 2X of the rescue requester A2. As shown in FIG. 8, the rescue information screen displays information about the rescuer A5, and map information M1 including the current position P5 of the rescuer A5, the current position P2 of the rescue requester A2, a route R1 from the current position P5 to the current position P2, and a route R2 from the current position P2 to the evacuation shelter H1.

The rescue information screen shown in FIG. 8 also displays an operation button K31 for notifying rescue requester A2 that his/her rescue request has been accepted, and an operation button K32 for rescue requester A2 to cancel the rescue request. Rescue requester A2 presses the "Confirmed" operation button K31 when he/she confirms that the rescue request has been accepted by rescuer A5 and waits for rescue from rescuer A5. On the other hand, rescue requester A2 presses the "Cancel rescue request" operation button K32 when rescue is no longer necessary and he/she wishes to cancel the rescue request.

The notification processing unit 116 also notifies the rescuer terminal 2Y of an inquiry to confirm that the rescuer is heading to rescue the rescuer. For example, when rescuer A5 is assigned to rescue requester A2, the notification processing unit 116 notifies the rescuer terminal 2Y of rescuer A5 of expected arrival information T1, such as the expected arrival time and the remaining time from the current time to the expected arrival time, and an inquiry to confirm that rescuer A5 is moving toward the current location P2 of rescue requester A2.

When the rescuer terminal 2Y of the rescuer A5 receives the inquiry from the rescue support device 1, it displays a rescue confirmation screen on the operation display unit 23 (see FIG. 1). FIG. 9 shows an example of the rescue confirmation screen displayed on the rescuer terminal 2Y of the rescuer A5. As shown in FIG. 9, the rescue confirmation screen displays expected arrival information T1, and map information M1 including the current position P5 of the rescuer A5, the current position P2 of the rescue requester A2, a route R1 from the current position P5 to the current position P2, and a route R2 from the current position P2 to the evacuation shelter H1.

The rescue confirmation screen shown in FIG. 9 also displays an operation button K41 for notifying that the rescuer A5 has confirmed that he/she is moving to rescue the rescue requester A2, and an operation button K42 for notifying that the rescuer A5 is unable to rescue the rescue requester A2. When the rescuer terminal 2Y receives the inquiry while the rescuer A5 is moving along the route R1 to rescue the rescue requester A2, the rescuer A5 presses the operation button K41. The rescuer A5 can confirm the information of the rescue requester A2 (rescuer information) by pressing the operation button K43. On the other hand, the rescuer A5 presses the operation button K42 when the rescuer A5 is injured or injured while moving along the route R1 and it becomes difficult to rescue the rescue requester A2, when the passage along the route R1 during the movement is restricted, or when the scheduled arrival time is likely to be significantly delayed due to traffic congestion.

The notification processing unit 116 notifies the rescuer terminal 2Y of the rescuer A5 of the inquiry at a predetermined period (e.g., every three minutes) until the rescuer A5 rescues the rescuer A2, i.e., until the current location P5 of the rescuer A5 coincides with the current location P2 of the rescuer A2, in order to confirm that the rescuer A5 is on his way to rescue the rescuer A2. The notification processing unit 116 may increase the frequency of the inquiry notification if the estimated arrival time calculated when the rescuer A5 was assigned to the rescuer A2 is likely to be delayed while the rescuer A5 is moving. The rescuer A5 inputs a response each time the inquiry is received. The notification processing unit 116 is an example of a notification processing unit of the present invention.

The release processing unit 117 releases the allocation of a rescuer to a rescue requester when a predetermined condition is met after the allocation processing unit 115 has assigned a rescuer to the rescue requester. In the above example, for example, the release processing unit 117 releases the allocation of user A5 who was assigned as a rescuer to rescue requester A2. The release processing unit 117 is an example of the release processing unit of the present invention.

For example, the release processing unit 117 releases the allocation of the rescuer to the rescue requester when a response to the inquiry is not received from the rescuer's rescuer terminal 2Y within a predetermined time. For example, when the notification processing unit 116 does not receive a response indicating that rescuer A5 is on his way to rescue (operation of the operation button K41 in FIG. 9 ) within a predetermined time (e.g., 2 minutes) after sending an inquiry to the rescuer terminal 2Y to confirm that rescuer A5 is on his way to rescue the rescue requester A2, the release processing unit 117 releases the allocation of rescuer A5 to rescue requester A2. This makes it possible for the release processing unit 117 to release the allocation of rescuer A5 to rescue requester A2 when, for example, rescuer A5 is affected by a disaster on the way to rescue and is unable to respond to the inquiry.

In addition, when the rescuer A5 presses an operation button K42 (see FIG. 9) in response to the inquiry to notify that he or she is no longer able to rescue the rescue requester A2, the release processing unit 117 releases the allocation of rescuer A5 to the rescue requester A2.

In another embodiment, if the rescuer does not move continuously for a predetermined time after being assigned to the rescue requester by the assignment processing unit 115, or if the rescuer moves in a direction different from the direction of the rescue requester's current location, the release processing unit 117 may release the assignment of the rescuer to the rescue requester. For example, if the current location P5 of rescuer A5 does not move for a predetermined time or more, or if rescuer A5 moves along a route different from route R1 (such as a route in the opposite direction), the release processing unit 117 releases the assignment of rescuer A5 to rescue requester A2.

In another embodiment, the release processing unit 117 may release the allocation of the rescuer A5 to the rescue requester A2 when the current time passes the estimated arrival time of the rescuer A5 at the current location P2 of the rescue requester A2 when the rescuer A5 receives a response indicating acceptance of the rescue request from the rescuer A5. For example, when it is expected that the rescuer A5 will not be able to arrive at the current location P2 of the rescue requester A2 by the original estimated arrival time of "12:45", the release processing unit 117 releases the allocation of the rescuer A5 to the rescue requester A2. The original estimated arrival time means the estimated arrival time calculated at the time the rescuer is allocated to the rescue requester. The release processing unit 117 may also release the allocation of the rescuer A5 to the rescue requester A2 when it is expected that the rescuer A5 will not be able to arrive at the current location P2 of the rescue requester A2 by the time obtained by adding an additional time (for example, 5 minutes) to the original estimated arrival time.

In another embodiment, the release processing unit 117 may release the allocation of rescuer A5 to rescuer A2 when a release request is received from rescue requester A2 requesting release of the allocation of rescuer A5. For example, when the current time has passed the estimated arrival time, the notification processing unit 116 notifies the rescue requester A2 of progress information T2 indicating that the current time has passed the estimated arrival time. When the rescue requester terminal 2X of rescue requester A2 receives the progress information T2 from the rescue support device 1, it displays the progress information T2 on the operation display unit 23 (see FIG. 1). FIG. 10 shows an example of a rescue confirmation screen displayed on the rescue requester terminal 2X of rescue requester A2. As shown in FIG. 10, the rescue confirmation screen displays progress information T2, including information indicating that the estimated arrival time has passed and information about the changed estimated arrival time, as well as map information M1, including the current location P5 of rescuer A5, the current location P2 of person in need of rescue A2, the route R1 from the current location P5 to the current location P2, and the route R2 from the current location P2 to the evacuation shelter H1.

The rescue confirmation screen shown in FIG. 10 also displays an operation button K51 that allows the rescue requester A2 to request rescue from another rescuer, an operation button K52 that notifies the rescue requester A2 of waiting for rescue from rescuer A5, and an operation button K53 that cancels the rescue request. When the rescue requester A2 presses the operation button K51 on the rescue confirmation screen, the release processing unit 117 acquires a release request from the rescue requester A2 requesting release of the allocation of rescuer A5, and releases the allocation of rescuer A5 to the rescue requester A2.

In another embodiment, the release processing unit 117 may release the allocation of the rescuer A5 to the rescue requester A2 when a response indicating that the acceptance of the rescue request is cancelled is received from the rescuer A5. For example, when the current time has passed the estimated arrival time, the notification processing unit 116 notifies the rescuer A5 of progress information T2 indicating that the current time has passed the estimated arrival time. When the rescuer terminal 2Y of the rescuer A5 receives the progress information T2 from the rescue support device 1, the rescuer terminal 2Y of the rescuer A5 displays the progress information T2 on the operation display unit 23 (see FIG. 1). FIG. 11 shows an example of a rescue confirmation screen displayed on the rescuer terminal 2Y of the rescuer A5. As shown in FIG. 11, the rescue confirmation screen displays the progress information T2 including information indicating that the estimated arrival time has passed and information on the changed estimated arrival time, and the current position P5 of the rescuer A5, the current position P2 of the rescue requester A2, the route R1 from the current position P5 to the current position P2, and the route R2 from the current position P2 to the evacuation shelter H1.

The rescue confirmation screen shown in FIG. 11 also displays an operation button K61 for notifying that the rescuer A5 is on his/her way to rescue, and an operation button K62 for notifying that it has become difficult to rescue the rescue requester A2. When the rescuer A5 presses the operation button K62 on the rescue confirmation screen, the release processing unit 117 acquires a release request from the rescuer A5 requesting release of the allocation of the rescuer A5, and releases the allocation of the rescuer A5 to the rescue requester A2.

In another embodiment, the release processing unit 117 may release the allocation of the rescuer A5 to the rescue requester A2 when a response to the progress information T2 is not received from the rescuer A5 within a predetermined time. For example, when the notification processing unit 116 does not receive a response indicating that the rescuer A5 is on his way to rescue (operation of the operation button K61) within a predetermined time (e.g., 2 minutes) after notifying the rescuer terminal 2Y of the rescuer A5 of the progress information T2 indicating that the current time has passed the estimated arrival time, the release processing unit 117 releases the allocation of the rescuer A5 to the rescue requester A2. This makes it possible for the release processing unit 117 to release the allocation of the rescuer A5 to the rescue requester A2 when, for example, the rescuer A5 is affected by a disaster on the way to rescue and is unable to respond to the progress information T2.

In another embodiment, the release processing unit 117 may release the allocation of rescuer A5 to rescue requester A2 when traffic is restricted, traffic is congested, or an accident occurs on route R1 connecting the current location P2 of rescue requester A2 and the current location P5 of rescue candidate A5. The release processing unit 117 determines the traffic conditions of route R1 based on road information stored in the memory unit 12 or road information acquired from an external server. For example, when traffic is restricted, traffic is congested, or an accident occurs on route R1 while rescuer A5 is traveling along route R1, the release processing unit 117 releases the allocation of rescuer A5 to rescue requester A2.

When the release processing unit 117 releases the allocation of a rescuer to a rescue requester, the determination processing unit 113 determines another rescuer for the rescue requester. For example, when the release processing unit 117 releases the allocation of rescuer A5 to rescue requester A2, the determination processing unit 113 determines rescue candidate A8, who is ranked second among multiple rescue candidates (see FIG. 4), as the rescuer. In this case, the output processing unit 114 outputs a rescue request for rescue requester A2 to rescuer terminal 2Y of rescuer A8.

When the rescuer terminal 2Y of the rescuer A8 acquires the rescue request from the rescue support device 1, it displays a rescue request screen on the operation display unit 23 (see FIG. 1). FIG. 12 shows an example of the rescue request screen displayed on the rescuer terminal 2Y of the rescuer A8. As shown in FIG. 12, the rescue request screen displays information about the rescue request (rescuer information), the current position P8 of the rescuer A8, the current position P2 of the rescuer A2, the route R1 from the current position P8 to the current position P2, and map information M1 including the route R2 from the current position P2 to the evacuation shelter H1. When accepting the rescue request of the rescuer A2, the rescuer A8 presses the operation button K21 "Go to rescue" and further selects a means of transportation (for example, "car" or "walk") to the current position P5 of the rescuer A2. After pressing the operation button K21 "Go to rescue", the rescuer A8 heads to rescue the rescuer A2 while checking the map information M1. After rescuing the rescuer A2, the rescuer A8 heads to the evacuation shelter H1 together with the rescuer A2 while checking the map information M1. On the other hand, if the rescuer A8 does not accept the rescue request from the rescuer A2, the rescuer A8 presses the "No rescue" operation button K22.

With this configuration, for example, if the initially determined rescuer A5 is unable to arrive at the current location P2 of the rescue requester A2 at the estimated arrival time, rescuer A8 who is closest to the rescue requester A2 can be assigned to the rescue requester A2 at the point when the current time passes the estimated arrival time (for example, 12:46).

In another embodiment, when the allocation of a rescuer to a rescue requester is cancelled by the cancellation processing unit 117, the determination processing unit 113 may determine a rescuer who can reach the current location of the rescue requester using a second route different from the first route. For example, when the allocation of rescuer A5 to rescue requester A2 is cancelled because a traffic restriction is imposed on the route R1 connecting the current location P5 of rescuer A5 and the current location P2 of rescue requester A2, the determination processing unit 113 determines user A8 as the rescuer who can reach the current location P2 of rescue requester A2 using route R1 that does not pass through the location of the traffic restriction (indicated by the "x" mark in FIG. 13).

[User terminal 2]
As shown in FIG. 1, the user terminal 2 (rescuer terminal 2X, rescuer terminal 2Y) includes a control unit 21, a storage unit 22, an operation display unit 23, a communication I/F 24, a GPS receiver unit 25 (GPS: Global Positioning System, registered trademark), and the like. The rescuer terminal 2X is a mobile terminal carried by a user (rescuer) who uses the rescue support service to make a rescue request, and is an information processing device such as a smartphone, a mobile phone, or a tablet terminal. The rescuer terminal 2Y is a mobile terminal carried by a user (rescuer) who uses the rescue support service to perform rescue activities for the rescuer, and is an information processing device such as a smartphone, a mobile phone, or a tablet terminal. The rescuer terminal 2Y may be an in-vehicle device mounted on a vehicle. Hereinafter, when a function common to the rescuer terminal 2X and the rescuer terminal 2Y is described, it is referred to as the user terminal 2.

The GPS receiver unit 25 receives signals (GPS signals) transmitted from multiple GPS satellites (not shown) via an antenna (not shown) and detects positioning data (latitude, longitude, altitude) indicating the position of the user terminal 2 and the current time.

The communication I/F 24 is a communication interface that connects the user terminal 2 to the communication network N1 by wire or wirelessly and performs data communication in accordance with a specified communication protocol with an external device such as the rescue support device 1 via the communication network N1.

The operation display unit 23 is a user interface that includes a display unit such as a liquid crystal display or an organic EL display that displays various information, and an operation unit such as a mouse, keyboard, or touch panel that accepts operations.

The storage unit 22 is a non-volatile storage unit such as a flash memory that stores various types of information. For example, various control programs are stored in the storage unit 22. The control programs are non-temporarily recorded on a computer-readable recording medium such as a USB, CD, or DVD (all of which are registered trademarks), and are read by a reading device (not shown) such as a USB drive, CD drive, or DVD drive that is electrically connected to the user terminal 2 and stored in the storage unit 22. The control programs may be downloaded from an external device via the communication network N1 and stored in the storage unit 22.

The control unit 21 has control devices such as a CPU, a ROM, and a RAM. The CPU is a processor that executes various arithmetic operations. The ROM is a non-volatile storage unit in which control programs such as a BIOS and an OS for causing the CPU to execute various processes are stored in advance. The RAM is a volatile or non-volatile storage unit that stores various information, and is used as a temporary storage memory (work area) for the various processes executed by the CPU. The control unit 21 controls the user terminal 2 by having the CPU execute various control programs that are stored in advance in the ROM or the storage unit 22.

Specifically, the control unit 21 includes various processing units such as a reception processing unit 211, a position detection processing unit 212, and a display processing unit 213. The control unit 21 functions as the various processing units by executing various processes according to the control program with the CPU. Some or all of the processing units included in the control unit 21 may be configured with electronic circuits. The control program may be a program for causing multiple processors to function as the various processing units.

The reception processing unit 211 acquires operation information operated by the user on the operation display unit 23 of the user terminal 2. For example, the rescue requester A2 starts the application for the rescue support service on his/her own rescue requester terminal 2X and inputs a user ID and password on the login screen. The reception processing unit 211 of the rescue requester terminal 2X transmits the acquired user ID and password to the rescue support device 1. The reception processing unit 211 of the rescue requester terminal 2X also accepts various operations for a rescue request from the rescue requester A2 on the operation screen (see FIG. 5) displayed on the rescue requester terminal 2X. The reception processing unit 211 of the rescuer terminal 2Y also accepts an operation to select whether or not to accept the rescue request from the rescuer A5 on the rescue request screen (see FIG. 6, etc.) displayed on the rescuer terminal 2Y.

The position detection processing unit 212 detects the current position of the user based on the positioning data detected by the GPS receiving unit 25. For example, the position detection processing unit 212 of the rescue requester terminal 2X of the rescue requester A2 detects the current position P2 and transmits position information including the current position P2 and the current time to the rescue support device 1. Also, for example, the position detection processing unit 212 of each of the rescuer terminals 2Y of the rescue candidates A1, A5, and A8 detects their respective current positions P1, P5, and P8 and transmits position information including the current position and the current time to the rescue support device 1.

The display processing unit 213 displays various types of information on the operation display unit 23 (see Figs. 5 to 13). For example, when the display processing unit 213 of the rescue requester's terminal 2X of the rescue requester A2 receives display data of an operation screen for making a rescue request from the rescue support device 1, it displays the operation screen (see Fig. 5) on the operation display unit 23. For example, when the display processing unit 213 of the rescuer's terminal 2Y of the rescuer A5 receives a rescue request from the rescue support device 1, it displays the rescue request screen (see Fig. 6) on the operation display unit 23. For example, when the display processing unit 213 of the rescue requester's terminal 2X of the rescue requester A2 receives the matching result from the rescue support device 1, it displays the rescue information screen (see Fig. 8) on the operation display unit 23.

For example, when the display processing unit 213 of the rescuer terminal 2Y of the rescuer A5 receives an inquiry from the rescue support device 1 to confirm that the rescuer A5 is on his way to rescue the rescue requester A2, the display processing unit 213 displays a rescue confirmation screen (see FIG. 9) on the operation display unit 23. For example, when the display processing unit 213 of the rescuer terminal 2Y of the rescuer A5 receives from the rescue support device 1 progress information T2 indicating that the current time has passed the estimated arrival time, the display processing unit 213 displays a rescue confirmation screen (see FIG. 11) on the operation display unit 23.

In addition, when the display processing unit 213 acquires the map information M1 from the rescue support device 1, it causes the operation display unit 23 to display a route guidance screen (navigation screen).

[Rescue support processing]
The rescue support process executed by the control unit 11 of the rescue support device 1 will be described below with reference to Fig. 14. The control unit 11 starts the execution of the rescue support program in response to an operation in which the rescue requester inputs a rescue request on the operation screen (see Fig. 5) displayed on the rescue requester's terminal 2X, thereby starting the execution of the rescue support process. The control unit 11 can also execute the rescue support process in parallel for each rescue requester's terminal 2X in response to a rescue request from each rescue requester's terminal 2X. Note that the rescue support process may be terminated midway in response to a predetermined operation on the rescue requester's terminal 2X.

The present invention can be considered as a rescue support method that executes one or more steps included in the rescue support process.

In addition, one or more steps included in the rescue support process described here may be omitted as appropriate. Furthermore, the steps in the rescue support process may be executed in a different order as long as the same action and effect is achieved. Furthermore, although an example is described here in which the control unit 11 executes each step in the rescue support process, in other embodiments, multiple processors may execute each step in the rescue support process in a distributed manner. Here, the rescue support process will be described using an example of the above-mentioned embodiment.

First, in step S11, the control unit 11 determines whether or not a rescue request has been received from a person in need of rescue. For example, when the control unit 11 receives a rescue request from the rescue requester terminal 2X of the rescue requester A2 (S11: Yes), the process proceeds to step S12. The control unit 11 waits until a rescue request is received from any person in need of rescue. Step S11 is an example of an acquisition step of the present invention.

Next, in step S12, the control unit 11 searches for one or more rescue candidates corresponding to the rescue requester A2. For example, the control unit 11 extracts one or more users who have not requested rescue, are under 65 years old, are currently located within a predetermined distance from the current location P2 of the rescue requester A2, and have rescue skills that meet the rescue level of the rescue requester A2, from among the users registered in the user information D1 (see FIG. 2). The control unit 11 identifies the extracted users as rescue candidates and registers information about the rescue candidates in the rescue candidate information D3 (see FIG. 4). Here, the control unit 11 identifies users A1, A5, and A8 as rescue candidates, and registers the rescue candidate information D3 by ranking the candidates in order of the earliest expected time of arrival at the current location P2 of the rescue requester A2.

Next, in step S13, the control unit 11 determines whether or not a rescuer has been determined. Specifically, the control unit 11 determines a rescuer for the rescue requester from one or more rescue candidates registered in the rescue candidate information D3. For example, the control unit 11 determines a rescuer based on at least any of the following information: the current location P2 of the rescue requester A2, the estimated arrival time at the current location P2 of the rescue requester A2, the attributes of the rescue requester A2, the rescue level of the rescue requester A2, and the rescue skills of the rescue candidates A1, A5, and A8. Here, the control unit 11 determines the rescue candidate A5 (see FIG. 4), who is ranked first among the rescue candidates A1, A5, and A8 and has the earliest estimated arrival time, as the rescue candidate.

In another embodiment, the control unit 11 may determine multiple rescuers for one rescue requester. For example, the control unit 11 may determine two rescue candidates A5 and A8 as rescuers based on the rescue level of the rescue requester A2 and the rescue skills of the rescue candidates. That is, the control unit 11 may match the rescue requester with a rescuer based on the rescue request of the rescue requester, and may also match multiple rescuers with each other. For example, when the rescue requester has a high rescue level, the control unit 11 may determine multiple users with high rescue skills as rescuers. The control unit 11 may also determine multiple rescuers who can arrive at the current location of the rescue requester within a predetermined time. The control unit 11 may also determine multiple rescuers who have the same route to the current location of the rescue requester.

In another embodiment, for example, if the person in need of rescue A2 inputs age, gender, and other desired conditions for a rescuer when making a rescue request, the control unit 11 may determine a rescuer who meets the desired conditions. For example, if the person in need of rescue inputs a female user, the control unit 11 determines a female user as the rescuer.

In another embodiment, the control unit 11 may determine a rescuer for the rescue requester A2 based on the traffic conditions of a route connecting the current location P2 of the rescue requester A2 and the current location of a rescue candidate. For example, as shown in FIG. 15, if a route R1 connecting the current location P5 of the rescuer A5 and the current location P2 of the rescue requester A2 is restricted in the middle and cannot be passed through (indicated by an "x" mark in FIG. 15), the control unit 11 determines, as the rescuer, user A8 who can reach the current location P2 of the rescue requester A2 using route R1 that does not pass through the restricted area.

When a rescuer is determined in step S13 (S13: Yes), the process proceeds to step S14. On the other hand, when a rescuer is not determined in step S13, i.e., when there is no rescuer capable of rescuing the rescue requester A2 (S13: No), the process proceeds to step S131. Step S13 is an example of a determination step of the present invention.

In step S131, the control unit 11 outputs (reports) a rescue request from the rescue requester A2 to a rescue organization such as a fire department or a city hall. The control unit 11 then ends the rescue support process.

In step S14, the control unit 11 outputs a rescue request to the determined rescuer. For example, the control unit 11 outputs a rescue request for the rescue requester A2 to the rescuer terminal 2Y of the rescuer A5. The rescue request includes information such as the name, age, sex, current location P2, walking status, and injury status of the rescue requester A2. The output processing unit 114 is an example of the output processing unit of the present invention. When multiple rescuers are determined, the control unit 11 outputs a rescue request to each rescuer.

In step S15, the control unit 11 determines whether or not a response accepting the rescue request has been received from the rescuer. For example, when the rescuer terminal 2Y of the rescuer A5 receives the rescue request from the rescue support device 1, it displays a rescue request screen on the operation display unit 23 (see FIG. 6).

When accepting the rescue request from the rescue requester A2, the rescuer A5 presses the "Go to rescue" operation button K21 and further selects the means of transportation (e.g., "car" or "walk") to the current location P5 of the rescue requester A2. When the rescuer A5 presses the "Go to rescue" operation button K21 on the rescue request screen, the control unit 11 acquires a response from the rescuer A5 indicating that the rescue request from the rescue requester A2 is accepted. When the control unit 11 acquires a response from the rescuer accepting the rescue request (S15: Yes), the process proceeds to step S16.

In response to this, when rescuer A5 presses the "No rescue" operation button K22 on the rescue request screen, the control unit 11 obtains a response from rescuer A5 indicating that the rescue request from rescue requester A2 will not be accepted. When the control unit 11 obtains a response from the rescuer not accepting the rescue request (S15: No), the process returns to step S13. When returning to step S13, the control unit 11 determines the rescue candidate A8 (see FIG. 4), who is ranked second in the candidate ranking, as the rescuer (S13: Yes), and in the following step S14, outputs a rescue request for rescue requester A2 to the rescuer terminal 2Y of rescuer A8. In this way, the control unit 11 repeats the processes of steps S13 to S15 until a rescuer who will accept the rescue request is found.

In step S16, the control unit 11 assigns (matches) rescuers to the rescue requester. For example, if rescuer A5 accepts the rescue request, the control unit 11 assigns rescuer A5 to rescue requester A2. Step S16 is an example of an assignment step of the present invention.

Next, in step S17, the control unit 11 notifies the rescue requester's terminal 2X of the result of the process of allocating rescuers to the rescue requester (matching result). For example, the control unit 11 notifies the rescue requester's terminal 2X of the rescue requester A2 of information about the rescuer A5 (name, age, gender, etc.) and expected arrival information T1, such as the expected arrival time and the remaining time from the current time to the expected arrival time.

When the rescue requester A2's rescue requester terminal 2X acquires the matching result from the rescue support device 1, it displays a rescue information screen (see FIG. 8). On the rescue information screen, the rescue requester A2 confirms that the rescue request has been accepted by the rescuer A5, and presses the "Confirmed" operation button K31 when waiting for rescue from the rescuer A5. On the other hand, the rescue requester A2 presses the "Cancel rescue request" operation button K32 when rescue is no longer necessary and the rescue request is to be canceled. When the rescue requester A2 presses the operation button K32, the control unit 11 ends the rescue support process. Step S17 is an example of an output step of the present invention.

Next, in step S18, the control unit 11 notifies the rescuer terminal 2Y of an inquiry to confirm that the rescuer is heading to rescue the rescuer. For example, the control unit 11 notifies the rescuer terminal 2Y of the rescuer A5 of expected arrival information T1, such as the expected arrival time and the remaining time from the current time to the expected arrival time, and an inquiry to confirm that the rescuer A5 is moving toward the current position P2 of the rescue requester A2.

When the rescuer terminal 2Y of the rescuer A5 receives the inquiry from the rescue support device 1, it displays a rescue confirmation screen (see FIG. 9). When the rescuer terminal 2Y receives the inquiry while traveling along the route R1 to rescue the rescue requester A2, the rescuer A5 presses the operation button K41. On the other hand, the rescuer A5 presses the operation button K42 if the rescuer A5 becomes injured while traveling along the route R1 and it becomes difficult to rescue the rescue requester A2, if the passage along the route R1 during the travel is restricted, or if the scheduled arrival time is likely to be significantly delayed due to traffic congestion.

Next, in step S19, the control unit 11 determines whether or not a response (rescue confirmation) indicating that the inquiry has been confirmed has been obtained from the rescuer. For example, when the rescuer A5 presses the operation button K41 on the rescue confirmation screen (see FIG. 9), the control unit 11 obtains the rescue confirmation from the rescuer and determines that the rescuer A5 has confirmed the inquiry (S19: Yes). When the control unit 11 obtains the rescue confirmation from the rescuer, the process proceeds to step S20. On the other hand, for example, when the rescuer A5 presses the operation button K42 on the rescue confirmation screen (see FIG. 9), the control unit 11 does not obtain the rescue confirmation from the rescuer A5 (S19: No), and the process proceeds to step S191.

The control unit 11 may notify the rescuer terminal 2Y of the rescuer A5 of the inquiry repeatedly at a predetermined interval (e.g., every three minutes). The control unit 11 may also transition to step S191 if the rescue confirmation is not obtained multiple times in succession in response to the inquiry.

In step S20, the control unit 11 determines whether the current time has passed the estimated arrival time. For example, the control unit 11 determines whether the current time has passed the estimated arrival time of 12:45, the time at which rescue requester A2 is scheduled to arrive at his/her current position P2. If the current time has passed the estimated arrival time (S20: Yes), the process proceeds to step S21. On the other hand, if the current time has not passed the estimated arrival time (S20: No), the process proceeds to step S22.

In step S21, the control unit 11 determines whether or not a response (cancellation request) requesting a change of rescuer has been received from the rescue requester. Specifically, when the current time passes the estimated arrival time, the control unit 11 notifies the rescue requester that the current time has passed the estimated arrival time. For example, the control unit 11 notifies the rescue requester A2 of progress information T2 indicating that the current time has passed the estimated arrival time of "12:45". When the rescue requester terminal 2X of the rescue requester A2 receives the progress information T2 from the rescue support device 1, it displays a rescue confirmation screen (see FIG. 10) including the progress information T2. When the rescue requester A2 presses the operation button K51 on the rescue confirmation screen, the control unit 11 receives the cancellation request. If the control unit 11 receives the cancellation request (S21: Yes), the process proceeds to step S191.

On the other hand, when rescue requester A2 presses operation button K52 on the rescue confirmation screen to notify that he/she will wait for rescue from rescuer A5, the control unit 11 does not acquire the rescuer change instruction (S21: No), and the process proceeds to step S22.

In another embodiment, if the current time passes the estimated arrival time "12:45" at the current location P2 of the rescue requester A2 (S20: Yes), the process may proceed to step S191. In other words, step S21 may be omitted.

In step S191, the control unit 11 cancels the allocation of the rescuer to the rescue requester. For example, in step S19, if the control unit 11 does not receive the rescue confirmation from the rescuer A5 (S19: No), the control unit 11 cancels the allocation of the rescuer A5 to the rescue requester A2. Also, for example, in step S21, if the control unit 11 receives a cancellation request from the rescue requester A2 requesting the cancellation of the allocation of the rescuer A5 (S19: Yes), the control unit 11 cancels the allocation of the rescuer A5 to the rescue requester A2. When the control unit 11 cancels the allocation of the rescuer A5 to the rescue requester A2, the process returns to step S13. Step S191 is an example of a cancellation step of the present invention.

Returning to step S13, the control unit 11 executes a process of determining another rescuer for the rescue requester A2. For example, the control unit 11 determines the rescue candidate A8 (see FIG. 4), who is ranked second in the candidate ranking, as the rescuer. When the control unit 11 changes the rescuer, it executes the above-mentioned processes again.

In step S22, the control unit 11 determines whether or not the rescue of the person in need of rescue is complete. For example, when rescuer A5 arrives at the current location P2 of rescue requester A2, or when rescuer A5 arrives at the evacuation shelter H1 together with rescue requester A2, he or she presses a rescue completion button (not shown) on the rescuer terminal 2Y. When the control unit 11 acquires the operation of the rescue completion button, it determines that the rescue of rescue requester A2 is complete. When the rescue of the person in need of rescue is completed (S22: Yes), the control unit 11 ends the rescue support process. When the rescue of the person in need of rescue is not completed (S22: No), the process proceeds to step S18. The control unit 11 repeats the processes of steps S18 to S22 until the rescue of the person in need of rescue is completed (S22: No). The control unit 11 executes the rescue support process in the above manner.

As described above, the rescue support system 100 according to an embodiment of the present invention acquires a rescue request from a person in need of rescue, searches for multiple rescue candidates corresponding to the person in need of rescue based on the rescue request, and determines a rescuer for the person in need of rescue from among the multiple rescue candidates. In addition, the rescue support system 100 outputs the rescue request to the determined rescuer, and when a response indicating that the rescue request is accepted is obtained from the rescuer, the rescue support system 100 assigns the rescuer to the person in need of rescue.

In this way, the rescue support system 100 can identify in advance multiple rescue candidates that can be assigned to a person in need of rescue. This makes it possible to quickly assign a replacement user from among the rescue candidates to person in need of rescue A2 as a rescuer, even if, for example, after user A5 has been assigned as the rescuer for person in need of rescue A2, user A5 is unable to rescue person in need of rescue A2 while en route to the rescue. This makes it possible to prevent delays in rescue operations for the person in need of rescue, and to quickly rescue the person in need of rescue.

The rescue support system 100 according to an embodiment of the present invention also acquires a rescue request from a person in need of rescue, and determines a rescuer for the person in need of rescue based on the rescue request. The rescue support system 100 also outputs the rescue request to the determined rescuer, and assigns the rescuer to the person in need of rescue if a response indicating acceptance of the rescue request is obtained from the rescuer. Furthermore, the rescue support system 100 releases the assignment of the rescuer to the person in need of rescue if a predetermined condition is met after the rescuer has been assigned to the person in need of rescue.

For example, the rescue support system 100 cancels the allocation of rescuer A5 to the rescue requester A2 when traffic is restricted, when congestion occurs, or when an accident occurs on the route R1 connecting the current location P2 of the rescue requester A2 and the current location P5 of the rescue candidate A5. Also, for example, the rescue support system 100 cancels the allocation of rescuer A5 to the rescue requester A2 when a response to an inquiry confirming that rescuer A5 is moving toward the rescue location of the rescue requester A2 is not obtained from rescuer A5 within a predetermined time. In this way, when a predetermined condition is satisfied after a rescuer is assigned to the rescue requester, the allocation of the rescuer to the rescue requester can be quickly canceled, and another rescuer who can rescue the rescue requester can be quickly determined. This prevents delays in rescue operations for the rescue requester, and enables the rescue requester to be quickly rescued.

The rescue support system 100 of the present invention is not limited to the above-described embodiment, but may be any of the following embodiments:

In another embodiment, when the control unit 11 receives a rescue request from a rescuer, the control unit 11 may display rescuer information including the rescue location of the rescuer on the user terminal 2 (rescuer terminal 2Y) of a user such as a rescue candidate. FIG. 16 shows a display screen of the rescuer terminal 2Y showing an example of rescuer information. For example, when a user logs in to the rescue support service on the user terminal 2, the control unit 11 displays the rescuer information on the user terminal 2. For example, the control unit 11 displays the current location P5 of user A5, information (such as name, age, current location P2, P3, P6, etc.) of rescuers A2, A3, and A6 who are currently requesting rescue (see FIG. 3) and are within a predetermined distance from the current location P5, and map information M1 including each current location on the user terminal 2 of user A5. As shown in FIG. 16, the control unit 11 displays the information of rescuers in order of proximity to the current location P5 of user A5.

Furthermore, the control unit 11 displays an operation button K71 for user A5 to select a rescuer who can be rescued (see FIG. 16). For example, when user A5 selects rescuer A3, the control unit 11 (determination processing unit 113) determines user A5 as the rescuer for rescuer A3. Note that the user may select a rescuer who can be rescued by selecting an icon image indicating the rescue position (current position) displayed on the map information M1.

With the above configuration, each user can quickly identify people in need of rescue who are requesting rescue and can select people in need of rescue that they can rescue, making it possible to quickly rescue people in need of rescue.

In the above configuration, the control unit 11 may further cause the rescue candidate's rescue location to be displayed on the rescuer terminal 2Y of the rescue candidate, among multiple rescue recipients, where the user (rescue candidate) can reach the rescue location of the rescue recipient. For example, as shown in FIG. 17, when there is a place where traffic is restricted or an accident has occurred (indicated by an "x" in FIG. 17), the control unit 11 omits the display of information on rescue recipients A2 and A6 who are difficult for user A5 to rescue (difficult to reach) on the screen displaying information on rescue recipients, and displays only information on rescue recipient A3 who is rescueable (reachable) by user A5. This allows the user to easily identify rescue recipients who can be rescued by the user.

The rescue support system 100 of the present invention can be applied to rescue support that arises in various situations, not only when a disaster occurs, but also when a user is injured or becomes ill.

In another embodiment of the present invention, the control unit 21 of the user terminal 2 may be provided with one or more processing units provided in the control unit 11 of the rescue support device 1. The information stored in the memory unit 22 may be acquired from an external device. The control unit 21 may download the rescue support program to the memory unit 22 via the Internet and execute the rescue support process, or may execute the rescue support process by executing the rescue support program stored in an external server. The rescue support system of the present invention may be composed of the rescue support device 1, may be composed of the user terminal 2, or may be composed of the rescue support device 1 and the user terminal 2.

1: rescue support device 2: user terminal 2X: rescue requester terminal 2Y: rescuer terminal 100: rescue support system 111: reception processing unit 112: acquisition processing unit 113: decision processing unit 114: output processing unit 115: allocation processing unit 116: notification processing unit 117: release processing unit 211: reception processing unit 212: position detection processing unit 213: display processing unit

Claims (9)

an acquisition processing unit that acquires a rescue request from a person in need of rescue;
a determination processing unit that determines a rescuer for the rescue requester based on the rescue request;
an output processing unit that outputs the rescue request to the rescuer;
an allocation processing unit that allocates the rescuer to the rescue requester when a response indicating acceptance of the rescue request is received from the rescuer;
a canceling processing unit that cancels the allocation of the rescuer to the rescue requester when a first route connecting a rescue position of the rescue requester and a current position of the rescuer is restricted after the allocation processing unit has assigned the rescuer to the rescue requester;
A rescue support system comprising: The determination processing unit, when the allocation of the rescuer to the rescue requester is released by the release processing unit, determines a rescuer who can reach a rescue position of the rescue requester by using a second route different from the first route.
The rescue support system according to claim 1 . an acquisition processing unit that acquires a rescue request from a person in need of rescue;
a determination processing unit that determines a rescuer for the rescue requester based on the rescue request;
an output processing unit that outputs the rescue request to the rescuer;
an allocation processing unit that allocates the rescuer to the rescue requester when a response indicating acceptance of the rescue request is received from the rescuer;
a notification processing unit that, when the rescuer is assigned to the rescue requester by the assignment processing unit, notifies an operation terminal of the rescuer of arrival schedule information regarding a schedule time when the rescuer will arrive at a rescue position of the rescue requester and an inquiry to confirm that the rescuer is moving toward the rescue position of the rescue requester;
a release processing unit that releases the allocation of the rescuer to the rescue requester when a response to the inquiry is not received from the operation terminal within a predetermined time ;
A rescue support system comprising: The notification processing unit displays, on the operation terminal of the rescue requester, at least any one of the arrival schedule information of the scheduled time and the remaining time from the current time to the scheduled time.
The rescue support system according to claim 3 . When the acquisition processing unit acquires the rescue request from the rescue requester, the acquisition processing unit displays a rescue location of the rescue requester on an operation terminal of a rescue candidate.
The rescue support system according to any one of claims 1 to 4 . When the acquisition processing unit acquires the rescue requests from the plurality of rescue requesters, the acquisition processing unit displays rescue positions of the plurality of rescue requesters that can be reached by a rescue candidate on an operation terminal of the rescue candidate.
The rescue support system according to any one of claims 1 to 4 . When the rescue candidate selects the rescue requester on the operation terminal, the determination processing unit determines the rescue candidate as a rescuer for the rescue requester.
The rescue support system according to claim 5 or 6 . One or more processors
An acquisition step of acquiring a rescue request from a person requiring rescue;
a determining step of determining a rescuer for the rescue requester based on the rescue request;
an output step of outputting the rescue request to the rescuer;
an allocation step of allocating the rescuer to the rescue requester when a response indicating acceptance of the rescue request is received from the rescuer;
a canceling step of canceling the allocation of the rescuer to the rescue requester when a first route connecting a rescue position of the rescue requester and a current position of the rescuer is restricted after the rescuer is assigned to the rescue requester in the assignment step;
A rescue assistance method. An acquisition step of acquiring a rescue request from a person requiring rescue;
a determining step of determining a rescuer for the rescue requester based on the rescue request;
an output step of outputting the rescue request to the rescuer;
an allocation step of allocating the rescuer to the rescue requester when a response indicating acceptance of the rescue request is received from the rescuer;
a canceling step of canceling the allocation of the rescuer to the rescue requester when a first route connecting a rescue position of the rescue requester and a current position of the rescuer is restricted after the rescuer is assigned to the rescue requester in the assignment step;
A rescue support program for causing one or more processors to execute the above.