JP7808541B2 - Monitoring Systems and Programs - Google Patents

Description

The present invention relates to a monitoring system and program.

Patent Document 1 describes a monitoring system that monitors a monitored person. In this monitoring system (referred to as a "monitoring system" in Patent Document 1), if a specific event (such as a fall) occurs in relation to the monitored person (referred to as a "target person" in Patent Document 1), a notification is sent to a terminal (referred to as a "mobile terminal" in Patent Document 1).

The terminals in this monitoring system can accept input operations for requests for help (referred to as "staff distress information" in Patent Document 1). When a request for help is input, information indicating the request for help is sent to other terminals. This allows users who own a terminal to request help from users who own other terminals.

Japanese Patent Application Laid-Open No. 2020-140418

In the monitoring system described in Patent Document 1, when a user makes a request for help and another user responds to the request to provide help, the user who made the request is unable to know that the other user is on the way to provide help.

Furthermore, particularly when there are three or more users, if one user makes a request for support and another user responds to that request and heads out to support, the other users (users who are neither the user who made the support request nor the user heading out to support) will not be able to know that the other user is heading out to support. This could result in inefficiencies, such as duplicate support.

The object of the present invention is to provide a monitoring system and program that, when a user makes a request for help and another user responds to the request, allows users other than the other user to know that the other user intends to help.

A feature of the monitoring system of the present invention is that it comprises a plurality of terminals, a status detection unit that detects the status of the monitored person, and a status transmission unit that, in response to the detection of a predetermined status by the status detection unit, transmits status information to the plurality of terminals, which is information indicating the detection result by the status detection unit, wherein the terminals have a request input unit that accepts input operations for a support request, a request transmission unit that transmits the request information indicating the support request to the outside, a request receiving unit that receives the request information transmitted from other terminals, an intention input unit that accepts input operations for an intention to support in response to the support request, an intention transmission unit that transmits intention information indicating the intention to support to the outside, and an intention receiving unit that receives the intention information transmitted from other terminals, and the terminals have a collaboration processing unit that, when they receive the request information and the intention information related to the request information, causes the intention input unit in the terminal to a state in which it does not accept input operations for the intention to support .

A feature of the program of the present invention is that it is a program executed on a terminal that receives status information, which is information indicating the detection result by a status detection unit that detects the status of a monitored person when a predetermined status is detected by the status detection unit, and that the terminal realizes a request input function that accepts input operations for a request for support, a request transmission function that transmits request information indicating the request for support to the outside, a request reception function that receives the request information from the outside, an intention input function that accepts input operations for an intention to support in response to the request for support, an intention transmission function that transmits intention information indicating the intention to support to the outside, an intention receiving function that receives the intention information from the outside, and a collaborative processing function that, when the request information and the intention information related to the request information are received, causes the intention input function to enter a state in which the input operations for the intention to support are not accepted .

According to the present invention, intention information, which is information indicating an intention to cheer, is transmitted outside the device. Therefore, for example, if another device receives the intention information, the user of the device that received the intention information can know that a user other than the user has an intention to cheer. As a result, it is possible to prevent inefficient situations, such as duplicate cheers, from occurring.

Thus, according to the present invention, when a user makes a request for support and another user goes to support in response to the request for support, users other than the other user can know that the other user has an intention to support them.
According to this configuration, the intention input unit of the terminal is put into a state where it does not accept the input operation of the intention to support, so that the user of the terminal can easily and reliably recognize that another user has already input the intention to support.

Furthermore, in the present invention , it is preferable that the terminal has an intention notification unit that, when the terminal accepts the input operation of the support request and receives the intention information regarding the support request, notifies the user of the terminal based on the intention information.

With this configuration, when a user makes a support request and another user responds to the support request and heads out to support, the user who made the support request can learn from the notification by the intention notification unit that the other user intends to support. This makes it easier for the user who made the support request to take appropriate action after learning that the other user will come to support them.

Furthermore, in the present invention, it is preferable that the terminal has a completion input unit that accepts an input operation indicating completion of support in response to the support request.

With this configuration, the monitoring system can use information indicating that support has been completed. As a result, for example, each user can more easily take appropriate action based on this information.

Furthermore, in the present invention, it is preferable that the terminal has a completion transmission unit that transmits completion information indicating the completion of the support to an external device.

With this configuration, completion information indicating that the cheering has been completed is sent externally from the device. Therefore, for example, if another device receives the completion information, the user of the device that received the completion information will know that the cheering has been completed.

Furthermore, in the present invention, it is preferable that the terminal has a cancellation input unit that, after the terminal has accepted an input operation for canceling the support request, accepts an input operation for canceling the support request, and a cancellation transmission unit that transmits cancellation information indicating the cancellation to an external device.

With this configuration, cancellation information, which is information indicating the cancellation of the support request, is sent outside the terminal. Therefore, for example, if another terminal receives the cancellation information, the user of the terminal that received the cancellation information will be able to know that the support request has been canceled.

Furthermore, in the present invention, it is preferable that the terminal has a cancellation receiving unit that receives the cancellation information transmitted from another terminal, and that the terminal has a cancellation processing unit that, when the cancellation information is received, causes the intention input unit of the terminal to enter a state in which the intention to support is not accepted.

With this configuration, the intention input unit on the device will enter a state where it will not accept input operations to indicate an intention to support, making it easier for the user of the device to reliably recognize that the support request has been canceled.

Furthermore, in the present invention, it is preferable that the terminal has a cancellation receiving unit that receives the cancellation information transmitted from another terminal, and that the terminal has a cancellation notification unit that, when the terminal accepts the input operation of the support intention and receives the cancellation information related to the support intention, notifies the user of the terminal based on the cancellation information.

With this configuration, if a user is on their way to provide support in response to a support request and the support request is canceled, the user will be notified by the cancellation notification unit that the support request has been canceled. This makes it easier to avoid a situation where the user continues to take supportive action (for example, moving toward the room where the user who made the support request is located) even though the support request has been canceled.

Furthermore, in the present invention, it is preferable that the request information includes requester information, which is information indicating the person who input the support request, and request time information, which is information indicating the time when the support request was input.

With this configuration, the user of the device that received the request information can learn the person who entered the request for help and the time when the request was entered. This makes it easier for the user to appropriately determine whether or not they should go to help, compared to when the request information does not include information about the requester and the time of the request.

Furthermore, in the present invention, the request input unit is configured to allow selective input of the content of the support requested, and the terminal has a content information generation unit that generates content information indicating the content of the support based on input operations to the request input unit, and the request information preferably includes the content information.

With this configuration, the user of the device that receives the request information can learn the details of the requested support. This makes it easier for the user to appropriately decide whether or not to go and provide support, compared to when the request information does not include content information.

Furthermore, in the present invention, the request input unit is configured to allow input of attributes of the target of the support request, the terminal has an attribute information generation unit that generates attribute information indicating the attributes based on input operations to the request input unit, and the request information preferably includes the attribute information.

With this configuration, the user of the device that receives the request information can learn the attributes of the person who is the target of the support request. This makes it easier for the user to appropriately decide whether or not to go and provide support, compared to when the request information does not include attribute information.

Furthermore, in the present invention, it is preferable that the intention information includes supporter information, which is information indicating the person who input the support intention.

With this configuration, intention information including supporter information is transmitted externally from the device. Therefore, if another device receives the intention information, the user of the device that received the intention information can learn the person who entered their intention to support. This makes it easier for each user to take appropriate action after learning who is heading out to support them.

FIG. 1 is a diagram illustrating an overview of a monitoring system. FIG. 2 is a block diagram showing the configuration of a monitoring device. FIG. 10 is a block diagram showing a configuration related to a support request. FIG. 10 is a diagram showing a request input screen. FIG. 10 is a diagram showing a request input screen. FIG. 10 is a diagram showing a request input screen. 10A to 10C are diagrams illustrating the display screens of the terminals after a support request is input to the first terminal. 10A and 10B are diagrams showing the display screens of the terminals after an operation to input a support intention is performed on the second terminal. 10 is a flowchart of a support process flow. FIG. 10 is a diagram showing a first cancellation screen. 10A and 10B are diagrams showing the display screens of the terminals after an input operation for completing support is performed on the second terminal. FIG. 10 is a diagram showing a second cancellation screen.

The following describes the embodiments of the present invention with reference to the drawings.

[Overall configuration of the monitoring system]
1, a monitoring system A in this embodiment includes a monitoring device 1 and a plurality of terminals 2. The monitoring device 1 and the plurality of terminals 2 are connected to each other via a predetermined network. The plurality of terminals 2 are also connected to each other via the predetermined network.

Monitoring device 1 is installed in an area where monitored person D is present. Monitoring device 1 monitors monitored person D. When monitored person D falls into a predetermined state (for example, a fallen state), monitoring device 1 transmits information indicating the state of monitored person D to multiple terminals 2. When multiple terminals 2 receive this information, they issue an alert.

In this embodiment, although not particularly limited, monitored person D is a resident of a welfare facility for the elderly, and user E of terminal 2 is a staff member of the welfare facility. Monitoring device 1 may be installed, for example, in a toilet, a room, a hallway, etc. Monitoring system A may include one or more monitoring devices 1. Furthermore, monitored person D monitored by monitoring system A may be one or more.

Furthermore, some or all of the multiple terminals 2 included in monitoring system A may be mobile terminals (smartphones, tablets, etc.), or may be computers installed in staff rooms at elderly care facilities.

As shown in FIG. 1, terminal 2 has a touch panel 20 (corresponding to the "request input section," "intention input section," "completion input section," and "cancellation input section" according to the present invention). While not particularly limited, the above-mentioned alert may be issued by displaying the status of monitored person D on the touch panel 20, or by sound emitted from terminal 2, vibration of terminal 2, etc.

[Configuration of monitoring device]
2, the monitoring device 1 has an imaging unit 3, a status detection unit 4, and a status transmission unit 5. The terminal 2 has a status reception unit 21.

The imaging unit 3 captures images of the area in which the monitoring device 1 is installed. In this embodiment, the imaging unit 3 is composed of an infrared camera. However, the present invention is not limited to this, and the imaging unit 3 may be any device other than an infrared camera as long as it is capable of capturing images of the area in which the monitoring device 1 is installed. The imaging unit 3 is preferably a ToF (Time of Flight) camera. The captured image acquired by the imaging unit 3 is preferably a depth image, which is an image containing depth information. The captured image acquired by the imaging unit 3 may be a video or a still image.

The imaging unit 3 sends the captured image to the status detection unit 4. The status detection unit 4 detects the status of the monitored person D based on the captured image received from the imaging unit 3. In other words, the monitoring system A is equipped with a status detection unit 4 that detects the status of the monitored person D.

In this embodiment, the status detection unit 4 generates a skeletal model, which is information indicating the skeleton of the monitored person D, based on the captured image it receives. The skeletal model is generated by analyzing the captured image to recognize the positions of the monitored person D's joints in three dimensions and connecting each joint with a straight line.

Furthermore, the state detection unit 4 is configured to detect the body position (e.g., standing, lying down, sitting) of the monitored person D based on the captured image and the generated skeletal model, and to detect whether the monitored person D is in a predetermined state based on the captured image and the skeletal model.

Although not particularly limited, the specified state may be a dangerous state of the monitored person D (for example, a state of falling). Note that technology for detecting dangerous states such as falls based on captured images or skeletal models is publicly known, so a description thereof will be omitted.

When the status detection unit 4 detects a predetermined status of the monitored person D, status information is sent from the status detection unit 4 to the status transmission unit 5. The status information is information indicating the detection results by the status detection unit 4. The status transmission unit 5 transmits the status information to the status reception unit 21 of each terminal 2.

In other words, monitoring system A is equipped with a status transmission unit 5 that, in response to a predetermined status being detected by the status detection unit 4, transmits status information, which is information indicating the detection results by the status detection unit 4, to multiple terminals 2.

The status receiving unit 21 displays information indicating the status of monitored person D on the touch panel 20 based on the received status information. This causes the above-mentioned alert to be issued. Note that the status information received by the status receiving unit 21 and the information displayed on the touch panel 20 may include, for example, information specifying the area where monitored person D is located (for example, a message such as "1F East Toilet"), or an image showing monitored person D's skeleton.

[Request for support]
3 shows a first terminal 2A, a second terminal 2B, and a third terminal 2C included in the monitoring system A of this embodiment. The first terminal 2A, the second terminal 2B, and the third terminal 2C are all terminals 2. The number of terminals 2 included in the monitoring system A may be two, or may be four or more.

In this embodiment, each terminal 2 has the same configuration. That is, the first terminal 2A, the second terminal 2B, and the third terminal 2C have the same configuration.

As shown in FIG. 3, the terminal 2 has a control unit 22. The control unit 22 is configured to be able to control the display of the touch panel 20.

Terminal 2 is configured to be able to accept input operations for requests for support. Note that a request for support is a request from user E of terminal 2 to user E of another terminal 2 for support. The configuration related to requests for support is described in detail below.

As shown in FIG. 3, the control unit 22 includes a request sending unit 23 and a request receiving unit 24 .
The terminal 2 is also configured to be able to display the request input screens shown in FIGS. 4 to 6 on the touch panel 20.

As shown in Figure 4, the request input screen includes a content input section 40, a target person input section 41, and a request button 42.

As shown in FIG. 5, the content input unit 40 is configured to allow the content of the support request to be input in a selective manner, for example, using a pull-down menu. In other words, the touch panel 20 is configured to allow the content of the support request to be input in a selective manner.

The options for content that can be input into the content input unit 40 are not particularly limited, but may be, for example, "Not selected," "Wheelchair required," "Call a doctor," "Toileting assistance," or "Bathing assistance," as shown in Figure 5.

As shown in FIG. 6, the target person input unit 41 is configured to allow the attributes of the target person for the support request to be input in a selective manner, for example, using a pull-down menu. In other words, the touch panel 20 is configured to allow the attributes of the target person for the support request to be input.

The attribute options that can be input into the subject input unit 41 are not particularly limited, but may be, for example, "unselected," "management staff," "female," "male," or "nurse," as shown in Figure 6.

Furthermore, the "attribute" here may be, for example, being a specific person (e.g., "being a specific person X or Y").

When the request button 42 is operated, as shown in FIG. 3, a predetermined signal is sent from the touch panel 20 to the control unit 22. This accepts the input operation for the support request. The signal includes information indicating the content of the input operation performed in the content input unit 40 and the target person input unit 41. The request sending unit 23 generates request information based on the signal. The request information is information indicating a support request.

As such, the terminal 2 has a touch panel 20 that accepts input operations for support requests. Specifically, the "input operation for support requests" according to the present invention may involve operating the content input section 40, the target person input section 41, and the request button 42, or it may involve only operating the request button 42.

As shown in FIG. 3, the request sending unit 23 includes a content information generating unit 25 and an attribute information generating unit 26. The content information generating unit 25 generates content information based on input operations to the content input unit 40. The content information is information that indicates the content of the support. The request information generated by the request sending unit 23 includes the content information.

In this way, the terminal 2 has a content information generation unit 25 that generates content information indicating the content of the support based on input operations on the touch panel 20. In addition, the request information includes the content information.

The attribute information generation unit 26 generates attribute information based on input operations to the target person input unit 41. Attribute information is information that indicates the attributes of the target person for the support request. The request information generated by the request transmission unit 23 includes attribute information.

In this way, the terminal 2 has an attribute information generation unit 26 that generates attribute information indicating attributes based on input operations on the touch panel 20. In addition, the request information includes the attribute information.

In addition, although not particularly limited, in this embodiment, the request information includes requested location information. The requested location information is information indicating the location of the terminal 2 at the time the support request was input (for example, "1F East Toilet"). The request sending unit 23 may generate the requested location information by calculating the location of the terminal 2 using, for example, a GPS (Global Positioning System) or a beacon.

Attribute information may also be automatically generated based on the requested location information described above. For example, based on the requested location information and information indicating the current locations of the other terminals 2, the terminal 2 located closest to the location indicated by the requested location information may be identified from among the other terminals 2, and the name of user E of the identified terminal 2 may be indicated by the attribute information.

In addition, although not particularly limited, the request information generated by the request sending unit 23 may include requester information and request time information. Requester information is information indicating the person (user E) who performed the operation to input the support request. Request time information is information indicating the time when the operation to input the support request was performed. In other words, the request information may include requester information, which is information indicating the person who performed the operation to input the support request, and request time information, which is information indicating the time when the operation to input the support request was performed.

The request sending unit 23 transmits the generated request information to the outside. In this embodiment, as shown in FIG. 3, the request sending unit 23 transmits the request information to all other terminals 2. However, the present invention is not limited to this. The request sending unit 23 may transmit the request information to some of the other terminals 2, or to a terminal other than the terminal 2 (for example, a management server, etc.).

In this way, terminal 2 has a request sending unit 23 that sends request information, which is information indicating a request for support, to the outside.

As shown in FIG. 3, the request receiving unit 24 is configured to receive request information transmitted from another terminal 2. Note that the request receiving unit 24 may receive the request information directly from the other terminal 2, or may receive it via a management server or the like.

In the example shown in FIG. 3, request information is transmitted from the request transmission unit 23 of the first terminal 2A.
The request information is received by the request receiving unit 24 in the second terminal 2B and the third terminal 2C.

In this way, terminal 2 has a request receiving unit 24 that receives request information sent from other terminals 2.

Functional units such as the status detection unit 4, status transmission unit 5, status reception unit 21, control unit 22, and request transmission unit 23 included in the control unit 22 may be physical devices such as microcomputers, or may be software functional units. For example, a configuration may be adopted in which programs corresponding to each functional unit included in the control unit 22 are stored in ROM or non-volatile memory (not shown), and the programs are loaded into and executed by the CPU, thereby executing the processes corresponding to each functional unit.

[Intention to support]
The terminal 2 is configured to be able to accept an input operation of a support intention in response to a support request. The support intention is an intention to provide support. The configuration related to input of the support intention will be described in detail below.

As shown in FIG. 3, the control unit 22 includes an intention transmitting unit 27 and an intention receiving unit 28 .
Furthermore, upon receiving the request information, the terminal 2 is configured to display an intention input screen based on the request information on the touch panel 20. For example, in Fig. 7, an intention input screen is displayed on the touch panel 20 of the second terminal 2B and the third terminal 2C.

As shown in Figure 7, the intention input screen includes a detailed information display section 43 and a support button 44.

The detailed information display section 43 displays detailed information about the support request based on the request information.
In the example shown in Figure 7, the detailed information display unit 43 displays the location indicated by the above-mentioned requested location information ("1st floor East toilet"), information indicating the ranking of the shortest distance between that location and user E (for example, the ranking among multiple users E whose terminal 2 received request information) ("You are the closest!", etc.), and the content of the support indicated by the content information ("A wheelchair is needed").

The content displayed in the detailed information display unit 43 is not particularly limited. The detailed information display unit 43 may display attributes indicated by the above-mentioned attribute information, or the above-mentioned requester information and request time information.

When the cheer button 44 is operated, as shown in FIG. 3, a predetermined signal is sent from the touch panel 20 to the control unit 22. This accepts the input operation of the intention to cheer in response to the cheer request. The intention sending unit 27 generates intention information based on the signal. The intention information is information indicating the intention to cheer.

In this way, the terminal 2 has a touch panel 20 that accepts input operations of support intentions in response to support requests. Note that operating the support button 44 corresponds to the "input operation of support intentions" according to the present invention.

In this embodiment, the intention information generated by the intention transmission unit 27 includes supporter information. Supporter information is information indicating the person (user E) who performed the operation to input the support intention. In other words, the intention information includes supporter information that indicates the person who performed the operation to input the support intention.

The intention transmission unit 27 transmits the generated intention information to the outside. In this embodiment, as shown in FIG. 3, the intention transmission unit 27 transmits the intention information to all other terminals 2. However, the present invention is not limited to this. The intention transmission unit 27 may transmit the intention information to some of the other terminals 2, or to a device other than the terminal 2 (for example, a management server, etc.).

In this way, terminal 2 has an intention transmission unit 27 that transmits intention information, which is information indicating the intention to support, to the outside.

As shown in FIG. 3, the intention receiving unit 28 is configured to receive intention information transmitted from another terminal 2. Note that the intention receiving unit 28 may receive intention information directly from another terminal 2, or may receive it via a management server or the like.

In the example shown in FIG. 3, intention information is transmitted from the intention transmitting unit 27 of the second terminal 2B.
The intention information is received by the intention receiving unit 28 in the first terminal 2A and the third terminal 2C.

In this way, terminal 2 has an intention receiving unit 28 that receives intention information transmitted from other terminals 2.

[Support completed]
The terminal 2 is configured to be able to accept an input operation for indicating that support has been completed in response to a support request. The configuration for inputting the support completion will be described in detail below.

As shown in FIG. 3, the control unit 22 includes a completion transmitting unit 30 and a completion receiving unit 31 .
Furthermore, when any of the multiple terminals 2 accepts an input operation of an intention to cheer, each terminal 2 displays one of a first cheering screen, a second cheering screen, or a third cheering screen on the touch panel 20. For example, in Fig. 8, the first cheering screen is displayed on the touch panel 20 of the first terminal 2A, the second cheering screen is displayed on the touch panel 20 of the second terminal 2B, and the third cheering screen is displayed on the touch panel 20 of the third terminal 2C.

As shown in FIG. 8, the first cheering screen, second cheering screen, and third cheering screen each include a cheering details display section 45. The cheering details display section 45 displays detailed information about the cheering being done (or planned to be done) based on the request information and intention information. In the example shown in FIG. 8, the cheering details display section 45 displays the location indicated by the requested location information described above ("1F East Restroom") and cheering person information ("Staff Member Y is cheering", etc.). Note that the content displayed in the cheering details display section 45 is not particularly limited.

Also, as shown in FIG. 8, the second support screen includes a completion button 46. When the completion button 46 is operated, a predetermined signal is sent from the touch panel 20 to the control unit 22, as shown in FIG. 3. This accepts an input operation indicating that support has been completed in response to the support request. The completion sending unit 30 generates completion information based on this signal. The completion information is information indicating that support has been completed in response to the support request.

In this way, the terminal 2 has a touch panel 20 that accepts an input operation to indicate that support has been completed in response to a support request. Note that operating the completion button 46 corresponds to the "input operation to indicate that support has been completed" according to the present invention.

The completion transmission unit 30 transmits the generated completion information to the outside. In this embodiment, as shown in FIG. 3, the completion transmission unit 30 transmits the completion information to all other terminals 2. However, the present invention is not limited to this. The completion transmission unit 30 may transmit the completion information to some of the other terminals 2, or to a terminal other than the terminal 2 (for example, a management server, etc.).

In this way, the terminal 2 has a completion transmission unit 30 that transmits completion information, which is information indicating that support has been completed, to the outside.

As shown in FIG. 3, the completion receiving unit 31 is configured to receive completion information sent from another terminal 2. Note that the completion receiving unit 31 may receive the completion information directly from the other terminal 2, or may receive it via a management server or the like.

In the example shown in FIG. 3, completion information is transmitted from the completion transmission unit 30 of the second terminal 2B.
The completion information is received by the completion receiving unit 31 in the first terminal 2A and the third terminal 2C.

[Cancellation of support request]
The terminal 2 is configured to be able to accept an input operation for canceling a support request after accepting an input operation for the support request. The configuration related to canceling a support request will be described in detail below.

As shown in FIG. 3, the control unit 22 has a cancellation sending unit 32 and a cancellation receiving unit 33. Furthermore, when the terminal 2 accepts an input operation for a support request, the terminal 2 displays a requesting screen on the touch panel 20 based on the above-mentioned request information. For example, in FIG. 7, the requesting screen is displayed on the touch panel 20 of the first terminal 2A.

As shown in FIG. 7, the requesting screen includes a request details display section 47 and a cancel button 48. The request details display section 47 displays detailed information about the support request based on the request information. In the example shown in FIG. 7, the request details display section 47 displays the location indicated by the request location information ("1F East Toilet") and the content of the support indicated by the content information ("Wheelchair required").

The content displayed in the request details display section 47 is not particularly limited. The request details display section 47 may display attributes indicated by the attribute information described above, or the requester information and request time information described above.

3, when the cancel button 48 is operated, a predetermined signal is sent from the touch panel 20 to the control unit 22. This accepts the input operation to cancel the support request. The cancellation sending unit 32 generates cancellation information based on the signal.
The cancellation information is information indicating the cancellation of the support request.

In this way, terminal 2 has a touch panel 20 that accepts an input operation to cancel a support request after terminal 2 accepts the input operation to input a support request. Note that operating the cancel button 48 corresponds to the "cancel input operation" according to the present invention.

The cancellation transmission unit 32 transmits the generated cancellation information to the outside. In this embodiment, as shown in FIG. 3, the cancellation transmission unit 32 transmits the cancellation information to all other terminals 2. However, the present invention is not limited to this. The cancellation transmission unit 32 may transmit the cancellation information to some of the other terminals 2, or to a terminal other than the terminal 2 (for example, a management server, etc.).

In this way, terminal 2 has a cancellation transmission unit 32 that transmits cancellation information, which is information indicating cancellation, to the outside.

As shown in FIG. 3, the cancellation receiving unit 33 is configured to receive cancellation information transmitted from another terminal 2. Note that the cancellation receiving unit 33 may receive cancellation information directly from another terminal 2, or may receive it via a management server or the like.

In the example shown in Figure 3, cancellation information is transmitted from the cancellation transmission unit 32 of the first terminal 2A. The cancellation information is received by the cancellation reception units 33 of the second terminal 2B and the third terminal 2C.

In this way, terminal 2 has a cancellation receiving unit 33 that receives cancellation information sent from other terminals 2.

[Support processing flow]
The control unit 22 in each terminal 2 is configured to perform processing related to a support request in accordance with the support processing flow shown in FIG.

When this support processing flow starts, step S01 is executed first. In step S01, the request input screen described above (see Figures 4 to 6) is displayed on the touch panel 20. Then, the processing proceeds to step S02.

In step S02, the control unit 22 determines whether the request receiving unit 24 has received request information transmitted from another terminal 2. If the request receiving unit 24 has not received request information transmitted from another terminal 2 ("No" in step S02 of FIG. 9), the process proceeds to step S03. If the request receiving unit 24 has received request information transmitted from another terminal 2 ("Yes" in step S02 of FIG. 9), the process proceeds to step S14.

In step S03, the control unit 22 determines whether the touch panel 20 has accepted an input operation for a support request. If the touch panel 20 has not accepted an input operation for a support request ("No" in step S03 of FIG. 9), the process returns to step S02. That is, while the request receiving unit 24 has not received request information transmitted from another terminal 2 and the touch panel 20 has not accepted an input operation for a support request, the display on the touch panel 20 remains on the request input screen, and the process repeats steps S02 and S03.

If the touch panel 20 receives an input operation for a support request ("Yes" in step S03 of Figure 9), processing proceeds to step S04.

In step S04, the request sending unit 23 generates request information. The request sending unit 23 then transmits the generated request information to all other terminals 2. After that, processing proceeds to step S05.

In step S05, the above-mentioned requesting screen (see touch panel 20 of first terminal 2A in Figure 7) is displayed on the touch panel 20. Then, processing proceeds to step S06.

In step S06, the control unit 22 determines whether the touch panel 20 has received an input operation to cancel the support request. If the touch panel 20 has received an input operation to cancel the support request (more specifically, if the cancel button 48 on the requesting screen has been operated) ("Yes" in step S06 of FIG. 9), the process proceeds to step S07. If the touch panel 20 has not received an input operation to cancel the support request (more specifically, if the cancel button 48 on the requesting screen has not been operated) ("No" in step S06 of FIG. 9), the process proceeds to step S09.

In step S07, the cancellation transmission unit 32 generates cancellation information. The cancellation transmission unit 32 then transmits the generated cancellation information to all other terminals 2. After that, processing proceeds to step S08.

In step S08, a first cancellation screen shown in Fig. 10 is displayed on the touch panel 20. The first cancellation screen includes information indicating that the support request has been canceled.
Although not particularly limited, the first cancellation screen may include a message indicating that the support request has been canceled (for example, "Support request has been canceled"). After step S08, this support processing flow ends for the time being.

In step S09, the control unit 22 determines whether the intention receiving unit 28 has received the intention information regarding the support request indicated by the request information transmitted in step S04. If the intention receiving unit 28 has not received the intention information ("No" in step S09 of FIG. 9), the process returns to step S06. In other words, while the touch panel 20 has not accepted an input operation to cancel the support request and the intention receiving unit 28 has not received the intention information, the display on the touch panel 20 remains on the requesting screen, and the process repeats steps S06 and S09.

If the intention receiving unit 28 receives the intention information ("Yes" in step S09 of Figure 9), processing proceeds to step S10.

As shown in FIG. 3, the control unit 22 has an intention notification unit 34. In step S10 of FIG. 9, the intention notification unit 34 notifies the user E of the terminal 2 based on the intention information received by the intention receiving unit 28. More specifically, the intention notification unit 34 causes the touch panel 20 to display the above-mentioned first cheering screen (see touch panel 20 of the first terminal 2A in FIG. 8) based on the intention information. Displaying the first cheering screen on the touch panel 20 corresponds to "notification based on intention information" according to the present invention.

However, the present invention is not limited to this. The intention notification unit 34 may be configured to notify the user by sound emitted from the terminal 2, vibration of the terminal 2, or the like, based on the intention information.

With the configuration described above, when the terminal 2 accepts the input operation for a support request ("Yes" in step S03 of FIG. 9) and receives intention information related to the support request ("Yes" in step S09 of FIG. 9), the intention notification unit 34 notifies the user E of the terminal 2 based on the intention information.

In other words, when terminal 2 accepts an input operation for a support request and receives intention information related to the support request, terminal 2 has an intention notification unit 34 that notifies user E of terminal 2 based on the intention information.

As shown in FIG. 8, the first cheering screen includes a cancel button 48 .
The function of the cancel button 48 on the first support screen is the same as the function of the cancel button 48 on the request screen.

After step S10, the process proceeds to step S11. In step S11, the control unit 22 determines whether the touch panel 20 has received an input operation to cancel the support request. If the touch panel 20 has received an input operation to cancel the support request (more specifically, if the cancel button 48 on the first support request screen has been operated) ("Yes" in step S11 of FIG. 9), the process proceeds to step S07. If the touch panel 20 has not received an input operation to cancel the support request (more specifically, if the cancel button 48 on the first support request screen has not been operated) ("No" in step S11 of FIG. 9), the process proceeds to step S12.

In step S12, the control unit 22 determines whether the completion receiving unit 31 has received completion information regarding the support request indicated by the request information transmitted in step S04. If the completion receiving unit 31 has not received the completion information ("No" in step S12 of FIG. 9), the process returns to step S11. In other words, while the touch panel 20 has not accepted an input operation to cancel the support request and the completion receiving unit 31 has not received the completion information, the display on the touch panel 20 remains on the first support in progress screen, and the process repeats steps S11 and S12.

If the completion information is received by the completion receiving unit 31 ("Yes" in step S12 of Figure 9), processing proceeds to step S13.

In step S13, the first completion screen is displayed on the touch panel 20. For example, in FIG. 11, the first completion screen is displayed on the touch panel 20 of the first terminal 2A and the third terminal 2C. Note that in FIG. 11, the second completion screen is displayed on the touch panel 20 of the second terminal 2B.

As shown in FIG. 11, the first completion screen and the second completion screen include a completion details display section 49. The completion details display section 49 displays detailed information about the completed support based on the request information, intention information, and completion information. In the example shown in FIG. 11, the completion details display section 49 displays the location indicated by the requested location information described above ("1F East Toilet") and support person information ("Staff member Y has responded," etc.). Note that the content displayed in the completion details display section 49 is not particularly limited.

After step S13, this support processing flow ends for the time being.

In step S14, based on the request information received in step S02, the above-mentioned intention input screen (see the touch panels 20 of the second terminal 2B and the third terminal 2C in Figure 7) is displayed on the touch panel 20. Then, the process proceeds to step S15.

In step S15, the control unit 22 determines whether the cancellation receiving unit 33 has received cancellation information related to the request information received in step S02. If the cancellation receiving unit 33 has received the cancellation information ("Yes" in step S15 of FIG. 9), the process proceeds to step S16. If the cancellation receiving unit 33 has not received the cancellation information ("No" in step S15 of FIG. 9), the process proceeds to step S17.

As shown in FIG. 3, the control unit 22 has a cancellation processing unit 35. In step S16 of FIG. 9, the cancellation processing unit 35 displays the second cancellation screen (see FIG. 12) on the touch panel 20 based on the request information received in step S02 and the cancellation information received in step S15. As a result, the display on the touch panel 20 switches from the intention input screen to the second cancellation screen.

As shown in FIG. 12, the second cancellation screen, like the intention input screen described above, includes a detailed information display section 43 and a support button 44. However, the support button 44 on the second cancellation screen is in an inoperable state (e.g., grayed out). In this way, when the cancellation receiving section 33 receives cancellation information, the cancellation processing section 35 causes the touch panel 20 on the terminal 2 to be in a state in which it does not accept input operations for intentions to support.

In other words, when the terminal 2 receives cancellation information, it has a cancellation processing unit 35 that sets the touch panel 20 on the terminal 2 to a state in which it does not accept input operations to indicate an intention to support.

After step S16, this support processing flow ends for the time being.

In step S17, the control unit 22 determines whether the intention receiving unit 28 has received intention information transmitted from another terminal 2 regarding the support request indicated by the request information received in step S02. If the intention receiving unit 28 has not received the intention information ("No" in step S17 of FIG. 9), the processing proceeds to step S18. If the intention receiving unit 28 has received the intention information ("Yes" in step S17 of FIG. 9), the processing proceeds to step S26.

In step S18, the control unit 22 determines whether the touch panel 20 has accepted an input operation of an intention to cheer. If the touch panel 20 has not accepted an input operation of an intention to cheer (more specifically, if the cheer button 44 on the intention input screen has not been operated) ("No" in step S18 of FIG. 9), the process returns to step S15. That is, as long as the cancellation receiving unit 33 has not received cancellation information regarding the request information received in step S02, the intention receiving unit 28 has not received intention information transmitted from another terminal 2, and the touch panel 20 has not accepted an input operation of an intention to cheer, the display on the touch panel 20 remains as the intention input screen, and the process repeats steps S15, S17, and S18.

If the touch panel 20 receives an input operation of a cheering intention (more specifically, if the cheer button 44 on the intention input screen is operated) ("Yes" in step S18 of Figure 9), processing proceeds to step S19.

In step S19, the intention transmission unit 27 generates intention information. The intention transmission unit 27 then transmits the generated intention information to all other terminals 2. After that, processing proceeds to step S20.

In step S20, the second cheering screen described above (see touch panel 20 of second terminal 2B in Figure 8) is displayed on the touch panel 20. Then, processing proceeds to step S21.

In step S21, the control unit 22 determines whether the cancellation receiving unit 33 has received cancellation information related to the request information received in step S02. If the cancellation receiving unit 33 has received the cancellation information ("Yes" in step S21 of FIG. 9), the process proceeds to step S25. If the cancellation receiving unit 33 has not received the cancellation information ("No" in step S21 of FIG. 9), the process proceeds to step S22.

In step S22, the control unit 22 determines whether the touch panel 20 has received an input operation to complete cheering. If the touch panel 20 has not received an input operation to complete cheering (more specifically, if the Complete button 46 on the second cheering screen has not been operated) ("No" in step S22 of FIG. 9), the process returns to step S21. That is, as long as the cancellation receiving unit 33 has not received cancellation information regarding the request information received in step S02 and the touch panel 20 has not received an input operation to complete cheering, the display on the touch panel 20 will remain at the second cheering screen, and steps S21 and S22 will be repeated.

If the touch panel 20 receives an input operation to complete cheering (more specifically, if the Complete button 46 on the second cheering screen is operated) ("Yes" in step S22 of Figure 9), processing proceeds to step S23.

In step S23, the completion transmission unit 30 generates completion information. The completion transmission unit 30 then transmits the generated completion information to all other terminals 2. After that, processing proceeds to step S24.

In step S24, the second completion screen described above (see touch panel 20 of second terminal 2B in Figure 11) is displayed on the touch panel 20. After that, this support processing flow is temporarily terminated.

As shown in FIG. 3, the control unit 22 has a cancellation notification unit 36. In step S25 of FIG. 9, the cancellation notification unit 36 notifies user E of terminal 2 based on the cancellation information received by the cancellation receiving unit 33. More specifically, the cancellation notification unit 36 causes the touch panel 20 to display the above-mentioned first cancellation screen (see FIG. 10) based on the cancellation information. Displaying the first cancellation screen on the touch panel 20 corresponds to "notification based on cancellation information" according to the present invention.

However, the present invention is not limited to this. The cancellation notification unit 36 may be configured to issue a notification based on the cancellation information by emitting a sound from the terminal 2, vibrating the terminal 2, or the like.

With the configuration described above, when the terminal 2 accepts the input operation of an intention to support ("Yes" in step S18 of FIG. 9) and receives cancellation information regarding the intention to support ("Yes" in step S21 of FIG. 9), the cancellation notification unit 36 notifies the user E of the terminal 2 based on the cancellation information.

In other words, when terminal 2 accepts an input operation of an intention to support and receives cancellation information related to the intention to support, terminal 2 has a cancellation notification unit 36 that notifies user E of terminal 2 based on the cancellation information.

As shown in FIG. 3, the control unit 22 has a collaboration processing unit 37. In step S26 of FIG. 9, the collaboration processing unit 37 displays the third cheering screen (see touch panel 20 of the third terminal 2C in FIG. 8) on the touch panel 20 based on the request information received in step S02 and the intention information received in step S17. As a result, the display on the touch panel 20 switches from the intention input screen to the third cheering screen.

As shown in FIG. 8, the third cheering screen does not include the cheer button 44. Therefore, when the third cheering screen is displayed on the touch panel 20, the touch panel 20 is in a state where it does not accept input operations for cheering intentions. In this way, when the request receiving unit 24 receives request information and the intention receiving unit 28 receives intention information, the collaboration processing unit 37 puts the touch panel 20 on the terminal 2 in a state where it does not accept input operations for cheering intentions.

In other words, when the terminal 2 receives request information and intention information related to the request information, the cooperation processing unit 37 sets the touch panel 20 of the terminal 2 to a state in which it does not accept input operations for intentions to support.

After step S26, processing proceeds to step S27.

In step S27, the control unit 22 determines whether the cancellation receiving unit 33 has received cancellation information related to the request information received in step S02. If the cancellation receiving unit 33 has received the cancellation information ("Yes" in step S27 of FIG. 9), the process proceeds to step S08. If the cancellation receiving unit 33 has not received the cancellation information ("No" in step S27 of FIG. 9), the process proceeds to step S28.

In step S28, the control unit 22 determines whether the completion receiving unit 31 has received completion information related to the request information received in step S02. If the completion receiving unit 31 has not received the completion information ("No" in step S28 of FIG. 9), the process returns to step S27. In other words, while the cancellation receiving unit 33 has not received cancellation information related to the request information received in step S02 and the completion receiving unit 31 has not received the completion information, the display on the touch panel 20 remains on the third cheering screen, and the process repeats steps S27 and S28.

If the completion information is received by the completion receiving unit 31 ("Yes" in step S28 of Figure 9), processing proceeds to step S13.

The support processing flow described above is executed individually on each terminal 2. For example, if processing on the first terminal 2A proceeds in the order of step S01, step S02, step S03, and step S04, it is conceivable that processing on the second terminal 2B and third terminal 2C will proceed in the order of step S01, step S02, and step S14.

[Example of processing for support requests]
The following describes the process flow for a support request using a specific example. In this example, as shown in Figure 1, a first user EA possesses a first terminal 2A, a second user EB possesses a second terminal 2B, and a third user EC possesses a third terminal 2C. The first user EA, the second user EB, and the third user EC are all user E.

First, as shown in Figure 1, monitored person D falls into a predetermined state (for example, a fallen state). In response, an alert is issued by first terminal 2A, second terminal 2B, and third terminal 2C. In this example, first user EA goes to assist monitored person D.

Then, the first user EA operates the first terminal 2A to input a request for support.
As a result, as shown in FIG. 7, a request screen is displayed on the first terminal 2A (step S05 in FIG. 9), and an intention input screen is displayed on the second terminal 2B and the third terminal 2C (step S14 in FIG. 9).

This allows the second user EB and the third user EC to know that the first user EA is requesting help.

In the state shown in FIG. 7, if the first user EA operates the cancel button 48, the first cancel screen (see FIG. 10) will be displayed on the first terminal 2A (step S08 in FIG. 9), and the second cancel screen (see FIG. 12) will be displayed on the second terminal 2B and the third terminal 2C (step S16 in FIG. 9).

This allows the second user EB and the third user EC to know that support for the first user EA is not necessary.

In this example, in the state shown in FIG. 7, the first user EA does not operate the cancel button 48, and the second user EB operates the cheer button 44. As a result, as shown in FIG. 8, the first cheering screen is displayed on the first terminal 2A (step S10 in FIG. 9), the second terminal 2B displays the second cheering screen (step S20 in FIG. 9), and the third terminal 2C displays the third cheering screen (step S26 in FIG. 9). The second user EB then goes to cheer on the first user EA.

This allows the first user EA and the third user EC to know that the second user EB has the intention to support them.

In the state shown in FIG. 8, if the first user EA operates the cancel button 48, the first cancel screen (see FIG. 10) will be displayed on the first terminal 2A and the third terminal 2C (step S08 in FIG. 9), and the first cancel screen (see FIG. 10) will also be displayed on the second terminal 2B (step S25 in FIG. 9).

This allows the second user EB and the third user EC to know that support for the first user EA is not necessary.

In this example, in the state shown in FIG. 8, the second user EB completes the support without the first user EA operating the cancel button 48, and the second user EB operates the complete button 46. As a result, as shown in FIG. 11, the first completion screen is displayed on the first terminal 2A and the third terminal 2C (step S13 in FIG. 9), and the second completion screen is displayed on the second terminal 2B (step S24 in FIG. 9).

This allows the third user EC to know that support for the first user EA has been completed.

With the configuration described above, intention information, which is information indicating an intention to cheer, is transmitted outside of terminal 2. Therefore, for example, if another terminal 2 receives the intention information, user E of the terminal 2 that received the intention information can know that other users E also have the intention to cheer. As a result, it is possible to prevent inefficient situations, such as duplicate cheers, from occurring.

In this way, with the configuration described above, when user E (e.g., first user EA) makes a request for support and another user E (e.g., second user EB) goes to support in response to the support request, users E other than the other user E (e.g., second user EB) (e.g., first user EA and third user EC) can learn that the other user E (e.g., second user EB) intends to support.

Other Embodiments
(1) The functions of the components in the above embodiment may be configured as a program that causes a computer to realize them. For example, the program may be configured as a program executed on the terminal 2 that causes the terminal 2 to realize a request input function that accepts an input operation for a support request, a request transmission function corresponding to the request transmission unit 23, a request reception function corresponding to the request reception unit 24, an intention input function that accepts an input operation for an intention to support in response to the support request, and an intention transmission function corresponding to the intention transmission unit 27.

In this case, it is preferable that the terminal 2 be configured to receive status information, which is information indicating the detection results by the status detection unit 4, when a predetermined status is detected by the status detection unit 4, which detects the status of the monitored person D.

(2) The monitoring device 1 (more specifically, the imaging unit 3, status detection unit 4, and status transmission unit 5) and the status reception unit 21 do not have to be provided.

(3) The terminals 2 do not need to have the same configuration. For example, only some of the multiple terminals 2 may be capable of accepting input operations for support requests and transmitting request information to the outside. In this case, those some terminals 2 may be unable to accept input operations for support intentions and unable to transmit intention information to the outside. Furthermore, in this case, it is preferable that the remaining terminals 2 be capable of accepting input operations for support intentions and transmitting intention information to the outside.

Also, for example, only some of the multiple terminals 2 may be capable of accepting input operations for support intentions and transmitting such intention information to the outside. In this case, those some terminals 2 may be unable to accept input operations for support requests and unable to transmit request information to the outside. Furthermore, in this case, it is preferable that the remaining terminals 2 be capable of accepting input operations for support requests and transmitting request information to the outside.

(4) The first cheering screen may include a completion button 46. That is, the touch panel 20 of the terminal 2 may be configured so that the terminal 2 accepts an input operation for a cheering request, receives intention information related to the cheering request, and then accepts an input operation for completing the cheering for the cheering request.

(5) The second cancel screen does not have to include the cheer button 44. In this case, when the second cancel screen is displayed on the touch panel 20, the touch panel 20 enters a state in which it does not accept input operations to indicate an intention to cheer.

(6) The third cheering screen may include a cheering button 44 that cannot be operated (for example, grayed out). In this case, when the third cheering screen is displayed on the touch panel 20, the touch panel 20 enters a state in which it cannot accept input operations to indicate an intention to cheer.

(7) Instead of the first or second cancellation screen, a normal screen (e.g., a standby screen or home screen) or a request input screen may be displayed.

(8) The intention information generated by the intention transmission unit 27 may include cheering time information. The cheering time information is information indicating the time when the cheering intention was input.

(9) Instead of the touch panel 20, the terminal 2 may have an input device such as a keyboard, buttons, or mouse that accepts input operations by the user E. In this case, the input device corresponds to the "request input unit," "intention input unit," "completion input unit," and "cancellation input unit" according to the present invention.

(10) The control unit 22 may have elements corresponding to the "request input unit," "intention input unit," "completion input unit," and "cancellation input unit" of the present invention.

(11) The terminal 2 may not have some or all of the content information generation unit 25, attribute information generation unit 26, intention receiving unit 28, completion sending unit 30, completion receiving unit 31, cancellation sending unit 32, cancellation receiving unit 33, intention notification unit 34, cancellation processing unit 35, cancellation notification unit 36, and collaboration processing unit 37.

(12) The content input unit 40 may be configured to allow the content of the requested support to be input in a format other than a multiple-choice format (for example, by entering text into an input field).

(13) The target person input unit 41 may be configured to allow the attributes of the target person for the support request to be input in a format other than a selection format (for example, by entering characters into an input field).

The configurations disclosed in the above-described embodiments (including other embodiments, the same applies hereinafter) can be applied in combination with configurations disclosed in other embodiments, provided no contradictions arise. Furthermore, the embodiments disclosed in this specification are merely examples, and the present invention is not limited to these embodiments. They can be modified as appropriate within the scope of the purpose of the present invention.

This invention can be used not only in elderly care facilities, but also in a variety of other facilities such as medical facilities and public facilities, and can also be used outdoors.

2: Terminal 4: Status detection unit 5: Status transmission unit 20: Touch panel (request input unit, intention input unit, completion input unit, cancellation input unit)
23: Request sending unit 24: Request receiving unit 25: Content information generating unit 26: Attribute information generating unit 27: Intention sending unit 28: Intention receiving unit 30: Completion sending unit 32: Cancel sending unit 33: Cancel receiving unit 34: Intention notifying unit 35: Cancel processing unit 36: Cancel notifying unit 37: Collaboration processing unit A: Monitoring system D: Monitored person E: User

Claims (12)

Multiple devices and
a state detection unit that detects the state of the monitored person;
a status transmission unit that transmits status information indicating a detection result by the status detection unit to the plurality of terminals in response to the detection of a predetermined status by the status detection unit,
The terminal
a request input unit that accepts an input operation for a support request;
a request transmission unit that transmits request information, which is information indicating the support request, to an external device;
a request receiving unit for receiving the request information transmitted from another terminal;
an intention input unit that accepts an input operation of an intention to support in response to the support request;
an intention transmitting unit that transmits intention information, which is information indicating the intention to support, to an external device;
an intention receiving unit that receives the intention information transmitted from the other terminal,
The monitoring system has a collaboration processing unit that, when the terminal receives the request information and also receives the intention information related to the request information, causes the intention input unit in the terminal to enter a state in which it does not accept input operations for the intention to support . The monitoring system of claim 1 , wherein the terminal has an intention notification unit that, when the terminal accepts the input operation of the support request and receives the intention information regarding the support request, notifies the user of the terminal based on the intention information. The monitoring system described in claim 1 or 2, wherein the terminal has a completion input unit that accepts an input operation indicating completion of support in response to the support request. The monitoring system described in claim 3, wherein the terminal has a completion transmission unit that transmits completion information indicating the completion of the support to an external device. The terminal
a cancellation input unit that, after the terminal has accepted an input operation for the support request, accepts an input operation for canceling the support request;
3. The monitoring system according to claim 1, further comprising a cancellation transmission unit that transmits cancellation information indicating the cancellation to an external device. The terminal has a cancellation receiving unit that receives the cancellation information transmitted from another terminal,
The monitoring system according to claim 5 , wherein the terminal has a cancellation processing unit that, when receiving the cancellation information, causes the intention input unit of the terminal to enter a state in which the intention to support is not accepted. The terminal has a cancellation receiving unit that receives the cancellation information transmitted from another terminal,
The monitoring system of claim 5, wherein the terminal has a cancellation notification unit that, when the terminal accepts the input operation of the intention to support and receives the cancellation information regarding the intention to support, notifies the user of the terminal based on the cancellation information. The monitoring system described in claim 1 or 2, wherein the request information includes requester information indicating the person who input the support request, and request time information indicating the time when the support request was input. The request input unit is configured to allow a content of the support to be requested to be input in a selective manner,
the terminal has a content information generation unit that generates content information indicating the content of the support based on an input operation to the request input unit,
The monitoring system according to claim 1 or 2, wherein the request information includes the content information. The request input unit is configured to be able to input attributes of a target person of the support request,
the terminal has an attribute information generation unit that generates attribute information indicating the attribute based on an input operation to the request input unit,
The monitoring system according to claim 1 or 2, wherein the request information includes the attribute information. The monitoring system described in claim 1 or 2, wherein the intention information includes supporter information indicating the person who input the support intention. A program executed on a terminal that receives status information indicating a detection result by a status detection unit that detects a status of a monitored person when the status detection unit detects a predetermined status,
a request input function for receiving an input operation for a support request;
a request transmission function for transmitting request information indicating the support request to an external party;
a request receiving function for receiving the request information from an external device;
an intention input function for receiving an input operation of an intention to support in response to the support request;
an intention transmission function for transmitting intention information, which is information indicating the intention to support, to an external device;
an intention receiving function for receiving the intention information from an external device;
A program that causes the terminal to realize a collaborative processing function that, when the request information and the intention information related to the request information are received, causes the intention input function to be in a state in which the input operation of the intention to support is not accepted .