Monitoring Systems and Programs

Abstract

To provide a monitoring system and a program that, when a user makes an assistance request and another user goes to assist the user in response to the request, allow a user other than the other user to know that the other user has an intention to assist.SOLUTION: A monitoring system comprises: a plurality of terminals 2; a state detection unit that detects a state of a monitored person D; and a state transmission unit that transmits state information to the plurality of terminals 2 in response to detection of a predetermined state by the state detection unit, the state information being information indicating the result of detection by the state detection unit. Each terminal 2 includes: a request input unit 20 that receives an input operation of an assistance request; a request transmission unit that transmits request information as information indicating the assistance request to the outside; a request reception unit that receives request information transmitted from another terminal 2; an intension input unit 20 that receives an input operation of an assistance intension corresponding to the assistance request; and an intension transmission unit that transmits intension information as information indicating the assistance intension to the outside.SELECTED DRAWING: Figure 7

Description

[Technical Field]

[0001] The present invention relates to a monitoring system and a program. [Background technology]

[0002] Patent Document 1 describes a monitoring system that monitors a monitored person. In this monitoring system (called a "monitoring system" in Patent Document 1), when a predetermined event (such as a fall) occurs in the monitored person (called a "target person" in Patent Document 1), a notification is sent to a terminal (called a "mobile terminal" in Patent Document 1).

[0003] 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 a user who owns a terminal to request help from users who own other terminals. [Prior art documents] [Patent documents]

[0004] [Patent Document 1] Japanese Patent Application Publication No. 2020-140418 Summary of the Invention [Problem to be solved by the invention]

[0005] In the monitoring system described in Patent Document 1, when a user makes a request for help and another user goes to help in response to the request, the user who made the request for help is unable to know that the other user is on his way to help.

[0006] Furthermore, particularly in cases where there are three or more users, if one user makes a support request and another user responds to the support 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. As a result, there is a possibility of inefficiencies, such as duplicate support, occurring.

[0007] The object of the present invention is to provide a monitoring system and program that, when a user makes a request for support and another user goes to support in response to the request for support, allows users other than the other user to know that the other user has an intention to support. [Means for solving the problem]

[0008] A feature of the monitoring system according to the present invention is that it is a monitoring system comprising a plurality of terminals, a status detection unit that detects the status of a monitored person, and a status transmission unit that transmits status information indicating the 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, wherein the terminals each comprise a request input unit that accepts an input operation of a support request, a request transmission unit that transmits the request information indicating the support request to the outside, a request reception unit that receives the request information transmitted from another of the terminals, an intention input unit that accepts an input operation of an intention to support in response to the support request, and an intention transmission unit that transmits the intention information indicating the intention to support to the outside, and an intention receiving unit that receives the intention information transmitted from another of the terminals, wherein the terminal receives the request information and, when receiving the intention information related to the request information, causes the intention input unit of the terminal to be in a state that does not accept an input operation of the intention to support. The purpose is to have.

[0009] The program according to the present invention is characterized in 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 includes a request input function that accepts an input operation for a support request, a request transmission function that transmits the request information indicating the support request to the outside, a request reception function that receives the request information from the outside, 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 that transmits the intention information indicating the intention to support to the outside. an intention receiving function that receives the intention information from an external device; and a cooperation processing function that receives the request information and, when the intention information related to the request information is received, causes the intention input function to be in a state in which the input operation of the intention to support is not accepted; The object of the present invention is to have the terminal realize the above.

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

[0011] 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.

[0012] Furthermore, in the present invention ,before 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.

[0013] According to this configuration, when a user makes a support request and another user responds to the support request and comes to support, the user who made the support request can be notified 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 knowing that the other user will come to support.

[0014] Furthermore, in the present invention, it is preferable that the terminal has a completion input unit that accepts an input operation for completing support in response to the support request.

[0015] According to this configuration, the monitoring system can utilize information indicating that the support has been completed, which makes it easier for each user to take appropriate action based on the information.

[0016] Furthermore, in the present invention, it is preferable that the terminal has a completion transmission unit that transmits completion information, which is information indicating that the support has been completed, to an external device.

[0017] According to this configuration, completion information indicating the completion of the support is transmitted to an external device. Therefore, for example, if another device receives the completion information, the user of the device that received the completion information can know that the support has been completed.

[0018]

[0019]

[0020] Furthermore, in the present invention, it is preferable that the terminal has a cancellation input unit that accepts an input operation to cancel the support request after the terminal accepts the input operation to cancel the support request, and a cancellation transmission unit that transmits cancellation information, which is information indicating the cancellation, to the outside.

[0021] According to this configuration, cancellation information indicating the cancellation of the support request is transmitted to an external device. Therefore, if another device receives the cancellation information, the user of the device that received the cancellation information can know that the support request has been canceled.

[0022] 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 receiving the cancellation 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.

[0023] According to this configuration, the intention input unit of the terminal is put into a state in which 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 the support request has been canceled.

[0024] 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 intention to support and receives the cancellation information regarding the intention to support, notifies the user of the terminal based on the cancellation information.

[0025] According to this configuration, if a user is heading to provide support in response to a support request and the support request is canceled, the user can be notified by the cancellation notification unit that the support request has been canceled. This makes it easier to avoid a situation in which the user continues to take action to provide support (for example, moving toward the room where the user who made the support request is located) despite the support request being canceled.

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

[0027] According to this configuration, the user of the device that receives the request information can know the person who input the support request and the time when the support request was input. This makes it easier for the user to appropriately determine whether or not to go to provide support compared to when the request information does not include requester information and request time information.

[0028] 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 the input operation to the request input unit, and it is preferable that the request information includes the content information.

[0029] According to this configuration, the user of the device that received the request information can know the details of the requested support, which 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.

[0030] Furthermore, in the present invention, the request input unit is configured to be able to input attributes of the person to whom the support request is made, and the terminal has an attribute information generation unit that generates attribute information indicating the attributes based on the input operation to the request input unit, and it is preferable that the request information includes the attribute information.

[0031] According to 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, which makes it easier for the user to appropriately determine whether or not to go and provide support compared to when the request information does not include attribute information.

[0032] Furthermore, in the present invention, it is preferable that the intention information includes supporter information that is information indicating a person who has performed an operation to input the support intention.

[0033] According to this configuration, the intention information including the supporter information 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 the person who input the support intention. This makes it easier for each user to take appropriate action after knowing the person they are going to support. [Brief explanation of the drawings]

[0034] [Figure 1] FIG. 1 is a diagram illustrating an overview of a monitoring system. [Figure 2] FIG. 2 is a block diagram showing the configuration of a monitoring device. [Figure 3] FIG. 10 is a block diagram showing a configuration related to a support request. [Figure 4] FIG. 10 is a diagram showing a request input screen. [Figure 5] FIG. 10 is a diagram showing a request input screen. [Figure 6] FIG. 10 is a diagram showing a request input screen. [Figure 7] 10A and 10B are diagrams showing the display screens of the terminals after an operation to input a support request has been performed on the first terminal. [Figure 8] 10A and 10B are diagrams showing the display screens of the terminals after an operation to input an intention to support is performed on the second terminal. [Figure 9] 10 is a flowchart of a support process flow. [Figure 10] FIG. 10 is a diagram showing a first cancellation screen. [Figure 11] 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. [Figure 12] FIG. 10 is a diagram showing a second cancellation screen. DETAILED DESCRIPTION OF THE INVENTION

[0035] DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS An embodiment of the present invention will be described with reference to the drawings.

[0036] [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.

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

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

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

[0040] 1, the terminal 2 has a touch panel 20 (corresponding to the "request input unit," "intention input unit," "completion input unit," and "cancellation input unit" according to the present invention). More specifically, the above-mentioned alert may be issued by displaying the state of the monitored person D on the touch panel 20, or may be issued by a sound generated from the terminal 2, vibration of the terminal 2, or the like, although this is not particularly limited.

[0041] [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 .

[0042] The imaging unit 3 captures images of the area where the monitoring device 1 is installed. In this embodiment, the imaging unit 3 is configured with 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 where 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 including depth information. The captured image acquired by the imaging unit 3 may be a video or a still image.

[0043] The imaging unit 3 sends the acquired 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 the status detection unit 4 that detects the status of the monitored person D.

[0044] 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 received captured image. The skeletal model is generated by analyzing the captured image to recognize the positions of the joints of the monitored person D in three dimensions and connecting each joint with a straight line.

[0045] 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.

[0046] Although not particularly limited, the predetermined state may be a dangerous state (for example, a state of falling) of the monitored person D. Note that the technology for detecting a dangerous state such as a fall based on a captured image or a skeletal model is well known, and therefore description thereof will be omitted.

[0047] When the status detection unit 4 detects a predetermined status of the monitored person D, the status detection unit 4 sends status information to the status transmission unit 5. The status information is information indicating the detection result 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.

[0048] That is, the monitoring system A is equipped with a status transmission unit 5 that transmits status information, which is information indicating the detection result by the status detection unit 4, to multiple terminals 2 in response to the detection of a predetermined status by the status detection unit 4.

[0049] Based on the received status information, the status receiving unit 21 displays information indicating the status of the monitored person D on the touch panel 20. 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 the monitored person D is located (for example, a message such as "1F East Toilet"), or may include an image showing the skeleton of the monitored person D.

[0050] [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.

[0051] In this embodiment, the terminals 2 have the same configuration as each other. That is, the first terminal 2A, the second terminal 2B, and the third terminal 2C have the same configuration as each other.

[0052] 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.

[0053] Terminal 2 is configured to be able to accept an input operation for a support request. A support request is a request from user E of terminal 2 to user E of another terminal 2 for support. The configuration related to the support request will be described in detail below.

[0054] 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.

[0055] As shown in FIG. 4, the request input screen includes a content input section 40, a target person input section 41, and a request button .

[0056] 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. That is, the touch panel 20 is configured to allow the content of the support request to be input in a selective manner.

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

[0058] 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. That is, the touch panel 20 is configured to allow the attributes of the target person for the support request to be input.

[0059] The options for attributes that can be input to the subject input unit 41 are not particularly limited, but may be, for example, "unselected," "management staff," "female," "male," or "nurse," as shown in FIG.

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

[0061] 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 allows the input operation of the support request to be accepted. 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.

[0062] In this way, the terminal 2 has a touch panel 20 that accepts an input operation for a support request. Specifically, the "input operation for a support request" 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 may involve only operating the request button 42.

[0063] 3, the request sending unit 23 has a content information generating unit 25 and an attribute information generating unit 26. The content information generating unit 25 generates content information based on an input operation to the content input unit 40. The content information is information indicating the content of the support. The request information generated by the request sending unit 23 includes the content information.

[0064] In this way, the terminal 2 has the content information generating unit 25 that generates content information indicating the content of the support based on an input operation on the touch panel 20. Furthermore, the request information includes the content information.

[0065] The attribute information generation unit 26 generates attribute information based on an input operation to the target person input unit 41. The attribute information is information that indicates the attributes of the target person of the support request. The request information generated by the request transmission unit 23 includes the attribute information.

[0066] In this way, the terminal 2 has an attribute information generating unit 26 that generates attribute information indicating attributes based on an input operation on the touch panel 20. Furthermore, the request information includes the attribute information.

[0067] Furthermore, 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 when the operation to input the support request was performed (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.

[0068] Furthermore, attribute information may be automatically generated based on the requested location information described above. For example, a configuration may be adopted in which, 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 is identified among the other terminals 2, and the name of user E of the identified terminal 2 is indicated by the attribute information.

[0069] Furthermore, although not particularly limited, the request information generated by the request sending unit 23 may include requester information and request time information. The requester information is information indicating the person (user E) who performed the input operation of the support request. The request time information is information indicating the time when the input operation of the support request was performed. In other words, the request information may include requester information, which is information indicating the person who performed the input operation of the support request, and request time information, which is information indicating the time when the input operation of the support request was performed.

[0070] 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 may transmit the request information to a terminal other than the terminal 2 (for example, a management server, etc.).

[0071] In this way, the terminal 2 has a request transmission unit 23 that transmits request information, which is information indicating a support request, to the outside.

[0072] 3, the request receiving unit 24 is configured to receive request information transmitted from another terminal 2. The request receiving unit 24 may receive the request information directly from another terminal 2, or may receive the request information via a management server or the like.

[0073] 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.

[0074] In this way, the terminal 2 has a request receiving unit 24 that receives request information transmitted from another terminal 2.

[0075] Each functional unit, such as the status detection unit 4, the status transmission unit 5, the status reception unit 21, the control unit 22, and the request transmission unit 23 included in the control unit 22, may be a physical device such as a microcomputer, or may be a software functional unit. For example, a configuration may be adopted in which a program corresponding to each functional unit included in the control unit 22 is stored in a ROM or nonvolatile memory (not shown), and the program is loaded into and executed by a CPU, thereby executing a process corresponding to each functional unit.

[0076] [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. Note that a support intention is an intention to provide support. The configuration related to input of a support intention will be described in detail below.

[0077] As shown in FIG. 3, the control unit 22 includes an intention transmitting unit 27 and an intention receiving unit . Furthermore, when the terminal 2 receives the above-mentioned request information, it is configured to display an intention input screen on the touch panel 20 based on the request information. 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.

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

[0079] 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 ("I need a wheelchair").

[0080] There is no particular limitation on the content displayed in the detailed information display unit 43. 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.

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

[0082] In this way, the terminal 2 has the touch panel 20 that accepts an input operation of a support intention in response to a support request. Note that operating the support button 44 corresponds to the "input operation of a support intention" according to the present invention.

[0083] In this embodiment, the intention information generated by the intention transmitting unit 27 includes supporter information. The supporter information is information indicating the person (user E) who input the cheering intention. That is, the intention information includes supporter information that indicates the person who input the cheering intention.

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

[0085] In this way, the terminal 2 has the intention transmitting unit 27 that transmits intention information, which is information indicating the intention to support, to the outside.

[0086] 3, the intention receiving unit 28 is configured to receive intention information transmitted from another terminal 2. The intention receiving unit 28 may receive the intention information directly from another terminal 2, or may receive it via a management server or the like.

[0087] 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.

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

[0089] [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 completion of support will be described in detail below.

[0090] 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 any 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.

[0091] As shown in Fig. 8, the first cheering screen, the second cheering screen, and the 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 the intention information. In the example shown in Fig. 8, the cheering details display section 45 displays the location indicated by the requested location information ("1F East Toilet") and supporter information ("Staff Member Y is cheering", etc.). The content displayed in the cheering details display section 45 is not particularly limited.

[0092] As shown in FIG. 8, the second support screen also 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 causes the input operation of completing support in response to the support request to be accepted. The completion sending unit 30 generates completion information based on the signal. The completion information is information indicating that support in response to the support request has been completed.

[0093] In this way, the terminal 2 has the touch panel 20 that accepts an input operation for completing support in response to a support request. Note that operating the complete button 46 corresponds to the "input operation for completing support" according to the present invention.

[0094] 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 may transmit the completion information to a terminal other than the terminal 2 (for example, a management server, etc.).

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

[0096] 3, the completion receiving unit 31 is configured to receive completion information transmitted from another terminal 2. The completion receiving unit 31 may receive the completion information directly from the other terminal 2, or may receive the information via a management server or the like.

[0097] 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.

[0098] [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 a support request. The configuration relating to the cancellation of a support request will be described in detail below.

[0099] 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.

[0100] As shown in Fig. 7, the requesting screen includes a request details display section 47 and a cancel button 48. Detailed information about the support request is displayed in the request details display section 47 based on the request information. In the example shown in Fig. 7, the request details display section 47 displays the location indicated by the above-mentioned requested location information ("1F East Toilet") and the content of the support indicated by the content information ("Wheelchair required").

[0101] There are no particular limitations on the content displayed in the request details display section 47. The request details display section 47 may display attributes indicated by the above-mentioned attribute information, or the above-mentioned requester information and request time information.

[0102] When the cancel button 48 is operated, a predetermined signal is sent from the touch panel 20 to the control unit 22, as shown in Fig. 3. 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.

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

[0104] 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 may transmit the cancellation information to a terminal other than the terminal 2 (for example, a management server, etc.).

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

[0106] 3, the cancellation receiving unit 33 is configured to receive cancellation information transmitted from another terminal 2. The cancellation receiving unit 33 may receive the cancellation information directly from another terminal 2, or may receive it via a management server or the like.

[0107] 3, cancellation information is transmitted from the cancellation transmitting unit 32 of the first terminal 2A. The cancellation information is received by the cancellation receiving units 33 of the second terminal 2B and the third terminal 2C.

[0108] In this way, the terminal 2 has a cancellation receiving unit 33 that receives cancellation information transmitted from another terminal 2.

[0109] [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.

[0110] When this support processing flow starts, first, the processing of step S01 is executed. In step S01, the above-mentioned request input screen (see FIGS. 4 to 6) is displayed on the touch panel 20. Thereafter, the processing proceeds to step S02.

[0111] In step S02, the control unit 22 determines whether or not 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.

[0112] 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 the request input screen, and the process repeats steps S02 and S03.

[0113] If the touch panel 20 receives an input operation for a support request ("Yes" in step S03 of FIG. 9), the process proceeds to step S04.

[0114] In step S04, the request sending unit 23 generates request information. Then, the request sending unit 23 transmits the generated request information to all other terminals 2. After that, the process proceeds to step S05.

[0115] In step S05, the above-mentioned requesting screen (see touch panel 20 of first terminal 2A in FIG. 7) is displayed on touch panel 20. After that, the process proceeds to step S06.

[0116] In step S06, the control unit 22 determines whether or not 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.

[0117] In step S07, the cancellation transmission unit 32 generates cancellation information. Then, the cancellation transmission unit 32 transmits the generated cancellation information to all other terminals 2. After that, the process proceeds to step S08.

[0118] 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.

[0119] In step S09, the control unit 22 determines whether the intention receiving unit 28 has received 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. That is, 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.

[0120] If the intention receiving unit 28 receives the intention information ("Yes" in step S09 of FIG. 9), the process proceeds to step S10.

[0121] 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 the "notification based on intention information" according to the present invention.

[0122] 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.

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

[0124] That is, the terminal 2 has an intention notification unit 34 that, when the terminal 2 accepts an input operation for a support request and receives intention information regarding the support request, notifies the user E of the terminal 2 based on the intention information.

[0125] As shown in FIG. 8, the first cheering screen includes a cancel button 48. The function of the cancel button 48 on the first cheering screen is the same as the function of the cancel button 48 on the requesting screen.

[0126] After step S10, the process proceeds to step S11. In step S11, the control unit 22 determines whether or not 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.

[0127] 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. That is, 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.

[0128] If the completion information is received by the completion receiving unit 31 ("Yes" in step S12 of FIG. 9), the process proceeds to step S13.

[0129] In step S13, a 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.

[0130] 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 ("1F East Toilet") and support person information ("Staff member Y has responded," etc.). The display content in the completion details display section 49 is not particularly limited.

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

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

[0133] 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.

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

[0135] 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 (for example, grayed out). In this way, when the cancellation receiving section 33 receives cancellation information, the cancellation processing section 35 causes the touch panel 20 of the terminal 2 to be in a state in which it does not accept input operations for support intentions.

[0136] That is, the terminal 2 has a cancellation processing unit 35 that, when receiving cancellation information, causes the touch panel 20 of the terminal 2 to enter a state in which it does not accept an input operation of an intention to support.

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

[0138] 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 process proceeds to step S18. If the intention receiving unit 28 has received the intention information ("Yes" in step S17 of FIG. 9), the process proceeds to step S26.

[0139] 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 the intention input screen, and the process repeats steps S15, S17, and S18.

[0140] When the touch panel 20 receives an input operation of a cheering intention (more specifically, when the cheer button 44 on the intention input screen is operated) ("Yes" in step S18 of FIG. 9), the process proceeds to step S19.

[0141] In step S19, the intention transmitting unit 27 generates intention information. Then, the intention transmitting unit 27 transmits the generated intention information to all other terminals 2. After that, the process proceeds to step S20.

[0142] In step S20, the above-mentioned second cheering screen (see touch panel 20 of second terminal 2B in FIG. 8) is displayed on touch panel 20. Thereafter, the process proceeds to step S21.

[0143] 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.

[0144] In step S22, the control unit 22 determines whether the touch panel 20 has received an input operation for cheering completion. If the touch panel 20 has not received an input operation for cheering completion (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 for cheering completion, the display on the touch panel 20 remains at the second cheering screen, and the process repeats steps S21 and S22.

[0145] When the touch panel 20 receives an input operation for completing cheering (more specifically, when the Complete button 46 on the second cheering screen is operated) ("Yes" in step S22 of FIG. 9), the process proceeds to step S23.

[0146] In step S23, the completion transmission unit 30 generates completion information. Then, the completion transmission unit 30 transmits the generated completion information to all other terminals 2. After that, the process proceeds to step S24.

[0147] In step S24, the above-mentioned second completion screen (see touch panel 20 of second terminal 2B in FIG. 11) is displayed on touch panel 20. After that, this support processing flow ends for the time being.

[0148] 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 the user E of the 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 the "notification based on cancellation information" of the present invention.

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

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

[0151] That is, terminal 2 has a cancellation notification unit 36 ​​that, when terminal 2 accepts an input operation of a support intention and receives cancellation information regarding the support intention, notifies user E of terminal 2 based on the cancellation information.

[0152] As shown in Fig. 3, control unit 22 has cooperation processing unit 37. In step S26 of Fig. 9, based on the request information received in step S02 and the intention information received in step S17, cooperation processing unit 37 causes touch panel 20 to display the above-mentioned third cheering screen (see touch panel 20 of third terminal 2C in Fig. 8). As a result, the display on touch panel 20 switches from the intention input screen to the third cheering screen.

[0153] 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 in which it does not accept an input operation of an intention to cheer. In this way, when the request receiving unit 24 receives request information and the intention receiving unit 28 receives intention information, the cooperation processing unit 37 puts the touch panel 20 of the terminal 2 in a state in which it does not accept an input operation of an intention to cheer.

[0154] That is, the terminal 2 has a collaboration processing unit 37 that, when it receives request information and intention information related to the request information, causes the touch panel 20 of the terminal 2 to enter a state in which it does not accept input operations for intentions to support.

[0155] After step S26, the process proceeds to step S27.

[0156] 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.

[0157] 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. That is, 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 supporting screen, and the process repeats steps S27 and S28.

[0158] If the completion information is received by the completion receiving unit 31 ("Yes" in step S28 of FIG. 9), the process proceeds to step S13.

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

[0160] [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.

[0161] First, as shown in Fig. 1, monitored person D falls into a predetermined state (for example, a fallen state). In response to this, 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.

[0162] Then, the first user EA operates the first terminal 2A to input a support request. As a result, as shown in FIG. 7, a requesting 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).

[0163] This allows the second user EB and the third user EC to know that the first user EA is requesting support.

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

[0165] This allows the second user EB and the third user EC to know that support for the first user EA is not required.

[0166] In this example, in the state shown in Fig. 7, it is assumed that the second user EB operates the cheer button 44 without the first user EA operating the cancel button 48. 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). Then, the second user EB goes to cheer on the first user EA.

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

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

[0169] This allows the second user EB and the third user EC to know that support for the first user EA is not required.

[0170] In this example, in the state shown in Fig. 8, the cheering by the second user EB is completed 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, a first completion screen is displayed on the first terminal 2A and the third terminal 2C (step S13 in Fig. 9), and a second completion screen is displayed on the second terminal 2B (step S24 in Fig. 9).

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

[0172] According to 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 another user E has an intention to cheer. As a result, it is possible to prevent inefficient situations, such as duplicate cheering, from occurring.

[0173] Thus, according to the configuration described above, when a user E (e.g., a first user EA) makes a request for support and another user E (e.g., a second user EB) goes to support in response to the support request, users E other than the other user E (e.g., the second user EB) (e.g., the first user EA and the third user EC) can know that the other user E (e.g., the second user EB) intends to support.

[0174] 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.

[0175] In this case, it is preferable that the terminal 2 is configured to receive status information, which is information indicating the detection result by the status detection unit 4, when a specified status is detected by the status detection unit 4 that detects the status of the monitored person D.

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

[0177] (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 an input operation for a support request and transmitting request information to the outside. In this case, the some of the terminals 2 may be incapable of accepting an input operation for an intention to support and transmitting intention information to the outside. Furthermore, in this case, it is preferable that the other terminals 2 be capable of accepting an input operation for an intention to support and transmitting intention information to the outside.

[0178] Also, for example, only some of the multiple terminals 2 may be capable of accepting an input operation of an intention to support and transmitting intention information to the outside. In this case, the some of the terminals 2 may be incapable of accepting an input operation of a support request and transmitting request information to the outside. Furthermore, in this case, it is preferable that the other terminals 2 be capable of accepting an input operation of a support request and transmitting request information to the outside.

[0179] (4) The first cheering screen may include a complete 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 regarding the cheering request, and then accepts an input operation for completing the cheering for the cheering request.

[0180] (5) The second cancel screen does not have to include the cheer button 44. In this case, the second cancel screen is displayed on the touch panel 20, and the touch panel 20 enters a state in which it cannot accept an input operation of an intention to cheer.

[0181] (6) The third cheering screen may include the cheering button 44 in an inoperable state (for example, grayed out state). In this case, the third cheering screen is displayed on the touch panel 20, and the touch panel 20 enters a state in which it cannot accept an input operation of an intention to cheer.

[0182] (7) Instead of the first or second cancel screen, a normal screen (for example, a standby screen or a home screen) or a request input screen may be displayed.

[0183] (8) Support time information may be included in the intention information generated by the intention transmitting unit 27. The support time information is information indicating the time when the operation to input the support intention was performed.

[0184] (9) The terminal 2 may have an input device such as a keyboard, buttons, or a mouse that accepts input operations by the user E, instead of the touch panel 20. 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.

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

[0186] (11) 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.

[0187] (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 selection format (for example, by inputting characters into an input field).

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

[0189] The configurations disclosed in the above-described embodiments (including other embodiments, the same applies hereinafter) can be applied in combination with the configurations disclosed in other embodiments, unless a contradiction arises. Furthermore, the embodiments disclosed in this specification are merely examples, and the present invention is not limited to these, and can be modified as appropriate within the scope of the purpose of the present invention. [Industrial Applicability]

[0190] The present invention can be used not only in elderly care facilities but also in various other facilities such as medical facilities and public facilities, and can also be used outdoors. [Explanation of symbols]

[0191] 2: Terminal 4: Status detection unit 5: Status transmission unit 20: Touch panel (request input section, intention input section, completion input section, cancellation input section) 23:Request transmission section 24:Request receiving section 25:Content information generation section 26: Attribute information generation section 27: Intention transmission unit 28: Intention receiving unit 30: Completion sending part 32: Cancellation sending section 33: Cancellation receiver 34: Intention Notification Department 35: Cancellation processing section 36: Cancellation notification section 37: Collaboration processing section A: Surveillance system D :Monitored person E: User

Claims

1. 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.

2. 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.

3. The monitoring system according to claim 1 or 2, wherein the terminal has a completion input unit that accepts an input operation for completing support in response to the support request.

4. The monitoring system according to claim 3 , wherein the terminal has a completion transmitting unit that transmits completion information indicating the completion of the support to an external device.

5. 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.

6. 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.

7. 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.

8. The monitoring system described in claim 1 or 2, wherein 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.

9. 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.

10. 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.

11. The monitoring system according to claim 1 or 2, wherein the intention information includes supporter information that indicates a person who has input the support intention.

12. 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.

Images