Methods, programs, devices, and systems for managing schedules

Abstract

In a system where schedules registered by registered users are automatically communicated to the target individuals, a support system should be established in advance for cases where the target individuals do not respond to the schedule communication. [Solution] A method executed by a processor for managing the schedule of a subject 100. The method includes the steps of: sending a schedule-related message to a terminal device 11 in step S405; outputting the message from the terminal device 11 to the subject 100 in step S601; and, if no response from the subject 100 to the message is detected, sending a request for assistance to at least one supporter 30, 40, 50 in steps S421, S431, S441.

Description

Technical Field

[0001] This disclosure relates to a configuration for managing schedules.

Background Art

[0002] Conventionally, configurations for managing schedules have been known. For example, Japanese Patent Application Laid-Open No. 2000-253109 (Patent Document 1) discloses a telephone having a personal schedule management function. The telephone includes a dial button for designating the date and time of a schedule, a microphone for inputting a voice message, a registration control unit for performing control to register the date and time of the schedule and the message, a memory for storing the input voice message under the control of the registration control unit, a notification control means for performing control to notify when the designated date and time of the schedule arrives, and a speaker for reproducing the voice message stored in the memory under the control of the notification control unit. According to this telephone, by diverting the dial button, microphone, speaker, and answering machine function that the telephone already has, as well as the clock and memory functions that have already become common due to the multifunctionality of the telephone, a scheduler function convenient for personal use can be realized.

[0003] Further, Japanese Patent Application Laid-Open No. 2008-148205 (Patent Document 2) discloses a mobile terminal having a schedule management function. According to the mobile terminal with a speaker, since the schedule notification alarm is implemented in imitation of a normal incoming call, it becomes difficult to distinguish between the two, so the user can surely receive schedule information.

Prior Art Documents

Patent Documents

[0004]

Patent Document 1

Patent Document 2

Summary of the Invention

Problems to be Solved by the Invention

[0005] The person who registers a schedule in a configuration like those disclosed in Patent Documents 1 and 2 (the registrant) is not necessarily the same person who acts according to that schedule (the subject). For example, if the registrant (for example, the child of an elderly person) is in a position to support the actions of the subject (for example, an elderly person), the two may be different. If the subject does not respond to the schedule notification registered by the registrant, it is possible that the subject has encountered a situation that is difficult for them to resolve on their own. Since the registrant may not be able to quickly confirm such a situation, it is necessary to establish a support system in advance for when the subject does not respond to the schedule notification. However, such a support system is not considered in the configurations disclosed in Patent Documents 1 and 2.

[0006] This disclosure is made to solve the aforementioned problems, and its purpose is to establish a support system in advance for cases where the target person does not respond to the schedule notification in a configuration where the schedule registered by the registrant is automatically notified to the target person. [Means for solving the problem]

[0007] The method disclosed herein is a processor-driven method for managing a subject's schedule. The method includes the steps of: sending a schedule-related message to a terminal device; outputting the message from the terminal device to the subject; and, if no response from the subject to the message is detected, sending a request for assistance to at least one support person.

[0008] The program disclosed herein is a program for managing a subject's schedule. When executed by a processor, the program causes the processor to send a schedule-related message to a terminal device, the terminal device to output the message to the subject, and if no response from the subject is detected, it sends a request for assistance to at least one support person.

[0009] The device of this disclosure comprises a schedule processing unit and a notification processing unit. The schedule processing unit manages the schedule of the subject. The notification processing unit sends a notification regarding the schedule to a terminal device. The terminal device outputs the notification to the subject. If the schedule processing unit does not detect a response from the subject to the notification, it sends a request for assistance to at least one supporter via the notification processing unit.

[0010] The system described herein comprises a schedule management device and a terminal device. The schedule management device manages the schedule of the subject. The terminal device receives schedule-related communications from the schedule management device. The terminal device outputs the communications to the subject. If the schedule management device does not detect a response from the subject to the communications, it sends a support request to at least one support person. [Effects of the Invention]

[0011] According to this disclosure, in a configuration where schedules registered by registrants are automatically communicated to the target person, a support system can be established in advance for cases where the target person does not respond to the schedule notification. [Brief explanation of the drawing]

[0012] [Figure 1] Figure 1 is a perspective view of the exterior of an HGW (home gateway), which is an example of a schedule management device according to one embodiment of the present disclosure. [Figure 2] Figure 2 shows an example of the configuration of the HGW in Figure 1. [Figure 3] Figure 3 shows an example network configuration for supporting individuals whose schedules are managed by the HGW in Figures 1 and 2. [Figure 4] Figure 4 is a sequence diagram showing an example of the flow of schedule registration to the HGW in normal mode by a registered user. [Figure 5] Figure 5 is a sequence diagram showing an example of the processing flow when the HGW successfully contacts the target person with their schedule. [Figure 6] FIG. 6 is a sequence diagram showing an example of a processing flow when support is provided by an emergency reporting receiving institution when the schedule notification from the HGW to the target person fails for a schedule with a high level of importance. [Figure 7] FIG. 7 is a sequence diagram showing an example of a processing flow when support is provided by a related person when the schedule notification from the HGW to the target person fails. [Figure 8] FIG. 8 is a sequence diagram showing an example of a processing flow when support is provided by a support organization when the schedule notification from the HGW to the target person fails. [Figure 9] FIG. 9 is a sequence diagram showing an example of a flow when the schedule notification from the HGW to the target person fails for a schedule with a medium level of importance. [Figure 10] FIG. 10 is a sequence diagram showing an example of a flow when the schedule notification from the HGW to the target person fails for a schedule with a low level of importance. [Figure 11] FIG. 11 is a sequence diagram showing an example of a processing flow when the schedule notification from the HGW to the target person fails for a schedule with no importance.

MODE FOR CARRYING OUT THE INVENTION

[0013] [Description of Embodiments of the Present Disclosure] First, the embodiments of the present disclosure will be listed and described.

[0014] (1) The method according to an embodiment of the present disclosure is a method executed by a processor for managing the schedule of a target person. The method includes a step of transmitting a notification regarding the schedule to a terminal device, a step of outputting the notification from the terminal device to the target person, and a step of transmitting a support request to at least one supporter when a response from the target person to the notification is not detected.

[0015] According to the above method, if the response of the target person to the schedule notification is not detected, a support request is made to at least one supporter. Therefore, in a configuration where the schedule registered by the registrant is automatically notified to the target person, a support system in the case where the target person does not respond to the schedule notification can be constructed in advance.

[0016] (2) In the method of (1) above, in the step of sending a support request, as the importance of the schedule is higher, the number of at least one supporter may be increased.

[0017] According to the above method, the scale of the support system can be adjusted according to the importance of the schedule.

[0018] (3) In the method of (2) above, at least one supporter may include a first supporter and a second supporter. In the step of sending a support request, the support request may be sent to the first supporter. The method may further include the step of sending the support request to the second supporter if the response of the first supporter to the support request is not detected.

[0019] According to the above method, by changing the supporter who supports the target person step by step, it is possible to achieve both cost reduction and support certainty associated with organizational support for the target person.

[0020] (4) In the method of (3) above, at least one supporter may further include an emergency reporting receiving agency. The method may further include the step of sending an emergency report to the emergency reporting receiving agency if the response of the second supporter to the support request is not detected.

[0021] According to the above method, since a support request is made to the emergency reporting receiving agency at the final stage of the support request, the safety confirmation of the target person can be surely performed.

[0022] (5) In any one of the methods described in (1) to (4) above, the method may further include the step of receiving information about the schedule via a network.

[0023] According to the method described above, schedule registration can be done remotely. (6) In the method described in (5) above, the information regarding the schedule may include voice. The terminal device may include an IP phone or a landline phone that can make calls over a network.

[0024] According to the method described above, by including a relatively easy-to-operate landline telephone as a terminal device, it becomes possible to encourage individuals unfamiliar with operating the latest equipment to habitually respond to scheduled communications.

[0025] (7) A program relating to another embodiment of the present disclosure is a program for managing a subject's schedule. When executed by the processor, the program causes the processor to send a schedule-related message to a terminal device, the terminal device to output the message to the subject, and if no response from the subject to the message is detected, to send a request for assistance to at least one support person.

[0026] According to the program described above, if the target individual does not respond to the schedule notification, a support request will be sent to at least one support person. Therefore, in a configuration where schedules registered by registered users are automatically notified to the target individual, a support system can be established in advance for cases where the target individual does not respond to the schedule notification.

[0027] (8) Apparatuses relating to other embodiments of the present disclosure include a scheduling processing unit and a notification processing unit. The scheduling processing unit manages the schedule of the subject. The notification processing unit sends a notification regarding the schedule to a terminal device. The terminal device outputs the notification to the subject. If the scheduling processing unit does not detect a response from the subject to the notification, it sends a request for assistance to at least one supporter via the notification processing unit.

[0028] According to the above device, if no response is detected from the target individual to the schedule notification, a support request is sent to at least one support person. Therefore, in a configuration where schedules registered by registered individuals are automatically notified to the target individual, a support system can be established in advance for cases where the target individual does not respond to the schedule notification.

[0029] (9) A system relating to another embodiment of the present disclosure comprises a schedule management device and a terminal device. The schedule management device manages the schedule of the subject. The terminal device receives schedule-related communications from the schedule management device. The terminal device outputs communications to the subject. If the schedule management device does not detect a response from the subject to the communications, it sends a request for assistance to at least one supporter via a notification processing unit.

[0030] According to the system described above, if the target person does not respond to the schedule notification, a support request will be sent to at least one support person. Therefore, in a configuration where schedules registered by registered users are automatically notified to the target person, a support system can be established in advance for cases where the target person does not respond to the schedule notification.

[0031] [Details of the embodiments of this disclosure] Embodiments of this disclosure will be described below with reference to the drawings. In the drawings, identical or corresponding parts are denoted by the same reference numerals, and their descriptions will not be repeated.

[0032] Figure 1 is a perspective view of the exterior of an HGW (home gateway) 1, which is an example of a schedule management device according to one embodiment of the present disclosure. In Figure 1, the X, Y, and Z axes are orthogonal to each other. The negative direction of the Z axis is the direction of gravity.

[0033] As shown in Figure 1, HGW1 is located in the home (Hm1) of the subject 100 and relays the connection of the terminal device 10 to the network (e.g., the internet) NW. The terminal device 10 automatically notifies the subject 100 in a timely manner of the schedule registered in HGW1 by the registrant via the network Nw. The terminal device 10 has, for example, an IP (Internet Protocol) telephone function and notifies the subject 100 of the schedule by playing the schedule content as voice. The terminal device 10 includes, for example, a landline telephone 11, a smart speaker 12, or a mobile terminal 13 (e.g., a smartphone or mobile phone). HGW1 and terminal device 10 constitute a schedule management system 1000.

[0034] The HGW1 has a rectangular parallelepiped shape. Multiple LED (Light Emitting Diode) lamps Ld and a confirmation button Btn (for example, a wireless setting button) are located on the front surface Ff of the HGW1, which is parallel to the XZ plane. Depending on the operating status of the HGW1, the lighting patterns of the multiple LED lamps Ld (for example, the number of lights illuminated, the blinking interval, or the color of the lights) change.

[0035] On the rear Fb of the HGW1, which is parallel to the XZ plane, are the power button Bpw, the LAN (Local Area Network) port Pla (e.g., an RJ (Registered Jack) 45 port), the WAN (Wide Area Network) port Pwa (e.g., an RJ45 port), and the telephone line port Pte (e.g., an RJ11 port). The WAN port is connected to the host device 61, which is connected to the network Nw. The telephone line port Pte is connected to the landline telephone 11. When the landline telephone 11 is connected to the telephone line port Pte, the HGW1 relays the wired connection of the terminal device 10 to the network Nw.

[0036] The HGW1 incorporates a wireless module 110. The wireless module 110 relays wireless connections (for example, Wi-Fi® connections) of devices wirelessly connected to the wireless module 110 (for example, smart speaker 12 or mobile terminal 13) to the network Nw. The wireless module 110 is configured, for example, as a circuit board on which a wireless chip is mounted.

[0037] Figure 2 shows an example of the configuration of HGW1 shown in Figure 1. As shown in Figure 2, in addition to the configuration shown in Figure 1, HGW1 further includes a router management unit 120, a schedule management unit 130, and a VoIP (Voice over Internet Protocol) management unit 140.

[0038] The router management unit 120 is connected to the WAN port Pwa, the wireless module 110, the schedule management unit 130, and the VoIP management unit 140. The router management unit 120 includes a routing processing unit 121 and a wireless processing unit 122.

[0039] The routing processing unit 121 performs the processing necessary for sending and receiving IP packets via the WAN port Pwa. If the IP packet from the WAN port Pwa conforms to SIP (Session Initiation Protocol), the routing processing unit 121 sends the IP packet to the VoIP management unit 140. The wireless processing unit 122 is connected to the wireless module 110 and performs the processing necessary for wireless communication between the network Nw and the terminal device 10.

[0040] The schedule management unit 130 includes a notification processing unit 131 and a schedule processing unit 132. The notification processing unit 131 notifies the target person of the schedule details (for example, what the target person should do) via the terminal device 10. The schedule processing unit 132 registers the schedule in a schedule table stored in memory (not shown) based on a schedule registration request from the registrant, and processes to request support for the target person 100 in response to the notification of the schedule.

[0041] Regarding the living arrangements between the person who should follow the schedule and the person who registered for that schedule, both living separately and living together are possible. If both live together, or if they live separately but the registrant lives within a few kilometers of the person's home Hm1 and the registrant has no time commitment (e.g., working hours), the registrant can quickly check the status of person 100 if no response from the person to the schedule is detected (when the person is abnormal). On the other hand, even if both live together or the registrant lives within a few kilometers of the person's home Hm1, if the person has time commitment (e.g., working hours), the registrant may not be able to visit the person's home Hm1 depending on the time of the abnormality. Also, if the registrant lives in a remote location from the person's home Hm1, even if the registrant has no time commitment, the registrant may not be able to quickly visit the person's home Hm1 when the person is abnormal.

[0042] In order to accommodate these various living conditions, the scheduling processing unit 132 switches the operating mode of the HGW1 to one of the following modes: normal mode, retry mode, support request 1 mode, support request 2 mode, or support request 3 mode, depending on whether or not a response from the subject to the schedule is detected and the status of support provided to the subject.

[0043] Normal mode is the operating mode for initially contacting person 100 with a schedule that has arrived. Retry mode is the operating mode for contacting person 100 again with the schedule if no response from the person is detected to the schedule that was contacted in normal mode. Support request 1 mode is the mode for requesting support for person 100 from a first supporter (for example, a person related to person 100 who can be expected to provide support free of charge) if no response from person 100 to the schedule that was contacted in retry mode is detected. Support request 2 mode is the mode for requesting support for person 100 from a second supporter (for example, a support organization such as a business that provides services for a fee) if a response from the first supporter to the support request made in support request 1 mode cannot be confirmed. Support request 3 mode is the mode for sending an emergency call to an emergency call receiving agency if a response from the second supporter to the support request made in support request 2 mode cannot be confirmed. Thus, in this embodiment, by gradually changing the supporters providing assistance to the target person 100, it is possible to achieve both a reduction in the costs associated with providing organized support to the target person 100 and the certainty of the support provided. In particular, by requesting assistance from an emergency call receiving agency at the final stage of the support request, the safety of the target person can be reliably confirmed. Note that the number of stages of support for the target person 100 is not limited to three; it may be two stages, or four or more stages.

[0044] Table 1 below shows an example of parameters that can be set for schedules registered in HGW1.

[0045] [Table 1]

[0046] Table 2 below shows an example of a schedule registered in HGW1.

[0047] [Table 2]

[0048] The VoIP management unit 140 includes a VoIP processing unit 141 and a B2BUA (Back-to-Back User Agent) processing unit 142. The VoIP processing unit 141 converts the voice signal from the telephone line port Pte into a digital signal to generate an IP packet and sends the IP packet to the router management unit 120. The VoIP processing unit 141 converts the digital signal contained in the IP packet from the router management unit 120 into a voice signal and sends it to the telephone line port Pte. In other words, the VoIP processing unit 141 realizes IP telephony. The B2BUA processing unit 142 performs processing to realize voice communication and security between different networks.

[0049] Furthermore, the HGW1 only needs to relay at least one of the wired and wireless connections of the terminal device 10 to the network Nw. For example, if the HGW1 only relays the wired connection from the fixed telephone 11, it does not need to have a wireless module 110, a wireless processing unit 122, and a B2BUA processing unit. Also, some of the functions of the HGW1 (for example, the schedule management unit 130) may be implemented by a processor that executes a schedule management program.

[0050] Figure 3 shows an example network configuration for supporting individuals whose schedules are managed by HGW1 in Figures 1 and 2. As shown in Figure 3, this example network configuration is built via a network Nw. The network Nw is connected to higher-level devices 61, 62, mobile terminals 70, stakeholders 30 (first supporters), support organizations 40 (second supporters), and emergency call receiving agencies 50. Stakeholders 30 include registered individuals 31, family members 32, relatives 33, and friends 34.

[0051] The home of registered user 31 (registered user's home) Hm2 is equipped with an HGW2 and a terminal device 20. If the terminal device 20 is a portable device, it may be carried by registered user 31 and moved outside of the registered user's home Hm2. The HGW2 is connected to a higher-level device 62. The terminal device 20 is connected to the HGW2. Registered user 31 can remotely register a schedule with desired settings to the HGW1 of the target user's home Hm1 via the terminal device 20. The terminal device 20 includes, for example, a landline telephone, a portable device such as a smartphone, and a smart speaker. Table 1 below shows an example of a schedule registered to the HGW1.

[0052] The mobile terminal 70 is connected to the host device 62. The mobile terminal 70 is, for example, the mobile terminal of a party 30.

[0053] The support organizations 40 include 31 registered individuals, 41 service providers (e.g., care service providers or security companies), and 42 local communities 42 in the areas where the beneficiaries reside (e.g., neighborhood associations, women's associations, or youth groups). The emergency call receiving agencies 50 include 51 police agencies and 52 fire departments.

[0054] Figure 4 is a sequence diagram showing an example of the flow of schedule registration to HGW1 in normal mode by the registrant 31. Hereafter, steps will simply be referred to as S. From Figure 4 onward, we will explain the case where the terminal device 10 at the target resident's home Hm1 and the terminal device 20 at the registrant's home Hm2 are both landline telephones. That is, terminal devices 10 and 20 will be described as landline telephones 11 and 20, respectively.

[0055] As shown in Figure 4, in S101, registrant 31 picks up the handset of the landline telephone 20 (off-hook) and instructs HGW1 to start schedule registration. In S201, landline telephone 20 receives the instruction to start schedule registration from registrant 31 and in S202 instructs HGW2 to start schedule registration. In S301, HGW2 receives the instruction to start schedule registration from landline telephone 20 and in S302 transmits an audio guidance message to landline telephone 20 regarding the start of schedule registration.

[0056] In S204, the landline telephone 20 plays a registration start guidance voice message through the handset speaker. In S102, the registrant 31 follows the registration start guidance played and in S103, inputs the schedule details by voice into the handset microphone. In S205, the landline telephone 20 receives the schedule voice message from the registrant 31 and transmits the voice message to the HGW2 in S206. In S303, the HGW2 receives the schedule voice message from the landline telephone 20 and in S304 transmits the schedule voice message to the HGW1, requesting the HGW1 to register the schedule corresponding to the schedule voice message.

[0057] In S401, HGW1 receives a schedule registration request from HGW2, and in S402, adds the schedule corresponding to the schedule registration request to the schedule table. In S403, HGW1 notifies HGW2 that the schedule registration is complete, and then in S404, waits for the date and time of the registered schedule to arrive. When the date and time of the schedule arrives, HGW1 starts the process shown in Figure 5.

[0058] HGW2 receives a schedule registration completion notification from HGW1 in S305 and sends an audio message corresponding to the schedule registration completion to terminal device 20 in S306. Terminal device 20 receives the audio message in S207 and plays it back as a registration completion guidance message through the handset speaker in S208. After the registrant 31 confirms the registration completion guidance in S104, they hang up the handset (on hook) in S105. After the landline telephone 20 confirms the on hook status in S209, it notifies HGW2 in S210 that the call related to the schedule registration has ended. In S307, HGW2 receives the end-of-call notification from landline telephone 20 and terminates the schedule registration process to HGW1.

[0059] In S404, when the scheduled date and time arrive, HGW1 starts the process shown in Figure 5. Figure 5 is a sequence diagram showing an example of the process flow when HGW1 successfully contacts the person with the schedule.

[0060] As shown in Figure 5, in S405, HGW1 notifies the landline telephone 11 of a simulated first incoming call (information about the schedule) as the initial contact. In S501, the landline telephone 11 receives the initial contact from HGW1 and in S502 generates a ringtone for a predetermined time interval. In S601, the subject 100 notices the ringtone and in S602 picks up the receiver of the landline telephone 11 (off-hook). In S503, the landline telephone 11 confirms that the call has been off-hook.

[0061] In S406, HGW1 transmits an audio message corresponding to the schedule content for which the date and time has arrived to the landline telephone 11. In S504, the landline telephone 11 receives the audio message and in S505, plays the audio data.

[0062] In S603, the subject 100 listens to the audio played from the handset speaker and in S604 inputs an audio response (subject response) to the audio into the handset microphone. In S506, the landline telephone 11 receives the audio input by the subject 100 and in S507 transmits the audio to the HGW1. In S407, the HGW1 registers the audio as the subject response to the schedule notified to the subject 100. By using a relatively easy-to-operate landline telephone 11 as the terminal device 10 that directly contacts the subject 100 with the schedule, the subject 100, who may be unfamiliar with operating the latest equipment, can be made accustomed to responding to schedule notifications.

[0063] At S605, the subject 100 hangs up (on hook). At S508, the landline telephone 11 confirms that the call is on hook and at S509 notifies HGW1 of the end of the call due to the subject's response. At S408, HGW1 receives the call termination notification from landline telephone 11 and at S409 notifies landline telephone 20 that the schedule contact with subject 100 was successful. At S410, HGW1 removes the schedule contacted with subject 100 from the schedule table. At S211, landline telephone 20 receives the schedule contact success notification. The schedule contact success notification may also be sent to the relevant parties 30, the support organization 40, or the emergency call receiving agency 50, and is sent to their respective landline telephones, mobile terminals, or servers.

[0064] Figure 6 is a sequence diagram showing an example of the process flow when support is provided by the emergency call receiving agency 50 in the event that schedule communication from HGW1 to the subject fails for a schedule of high importance. Steps S405, S410, S501, S502, and S601 in Figure 6 are the same as in Figure 5, so no explanation will be repeated.

[0065] As shown in Figure 6, if HGW1 cannot confirm the off-hook status corresponding to S601, it switches from normal mode to retry mode and, in S411, notifies the landline telephone 11 of a simulated incoming call. In S510, the landline telephone 11 receives the incoming call notification from HGW1 and, in S511, generates a ringtone for a predetermined time interval. In S606, if the subject notices the ringtone and picks up the handset of the landline telephone 11, the same processing as from S406 onwards in Figure 5 is performed. By attempting the scheduled contact again in retry mode, a scheduled contact that failed in normal mode due to a minor malfunction of the subject 100 (e.g., carelessness or forgetfulness) can be made successful in retry mode.

[0066] If HGW1 cannot confirm that the landline phone 11 is off-hook during the ringtone time in S511, it determines in S412 whether the number of incoming calls has reached (or is equal to) the specified number. If the number of incoming calls has not reached the specified number (NO in S412), HGW1 performs S411 again. If the number of incoming calls has reached the specified number (YES in S412), HGW1 proceeds to S421 and transitions from retry mode to support request 1 mode. Note that HGW1 may also transition directly from normal mode to support request 1 mode without going through retry mode.

[0067] In S421, HGW1 sends a schedule contact failure notification (support request) to the person 100, indicating that the schedule contact failed, to the person 30, who is registered as the recipient in the first support request mode. In S701, person 30 receives the schedule contact failure notification. The schedule contact failure notification includes, for example, a request for confirmation of the person's safety, and a request and method for canceling the support request mode if the person's safety can be confirmed.

[0068] In S422, HGW1 waits for a certain period of time for contact from the relevant party 30. If HGW1 does not receive contact from the relevant party 30, it proceeds to S431 and switches from support request mode 1 to support request mode 2. The process when contact is received from the relevant party is explained in Figure 7.

[0069] In S431, HGW1 sends a message to support organization 40, which is registered as a notification recipient in support request mode 2, informing it that the schedule notification to target person 100 failed. Support organization 40 receives the schedule notification failure in S801. In S432, HGW1 waits for a certain period of time for contact from support organization 40. If HGW1 does not receive contact from support organization 40, it proceeds to S441 and moves from support request mode 2 to support request mode 3. The process when support organization 40 contacts HGW1 is explained in Figure 8.

[0070] In S441, HGW1 transmits an actual incoming call (an emergency call, e.g., a 110 or 119 call) to the emergency call receiving agency 50. In S442, HGW1 plays an audio message corresponding to information about the failed schedule (e.g., the person's name, address, and schedule details). After the emergency call receiving agency 50 confirms the audio message in S901, in S903, it dispatches a person in charge (e.g., a police officer, firefighter, or paramedic) to the person's home Hm1. After the person in charge confirms the situation of the person 100 at the person's home Hm1, the emergency call receiving agency 50 notifies HGW1 in S904 that the call related to assisting the person 100 has ended. In S443, after receiving the end-of-call notification from the emergency call receiving agency 50, HGW1 switches from the third assistance request mode to the normal mode and performs S410 as in Figure 5.

[0071] Figure 7 is a sequence diagram showing an example of the process flow when support is provided by stakeholders 30 in the event that scheduling communication from HGW1 to the target person fails. Steps S405, S410-S412, S421, S501, S502, S510, S511, S601, S606, and S701 in Figure 7 are the same as in Figure 6, so the explanation will not be repeated.

[0072] After HGW1 performs S405, S411, S412, and S421 as in Figure 6, the person in charge 30 performs a safety check of the subject 100 in S702 (for example, by visiting the subject's home Hm1 or by contacting the subject 100), and then performs a safety check completion operation in S703 (for example, by calling a designated number to HGW1 or by pressing the confirmation button Btn on HGW1). In S423, after receiving the safety check completion operation from the person in charge 30, HGW1 switches from support request mode 1 to normal mode and performs S410 as in Figure 6.

[0073] Figure 8 is a sequence diagram showing an example of the processing flow when support is provided by the support organization 40 in the event that scheduling communication from HGW1 to the target person fails. Steps S405, S410-S412, S421, S422, S431, S501, S502, S510, S511, S601, S606, S701, and S801 in Figure 7 are the same as in Figure 6, so the explanation will not be repeated.

[0074] After HGW1 performs S405, S411, S412, S421, S422, and S431 as in Figure 6, the person in charge of support organization 40 performs a safety check of the subject 100 in S802 (for example, visiting the subject's home Hm1 or contacting the subject 100), and then performs a safety check completion operation in S803 (for example, calling a designated number to HGW1 or pressing the confirmation button Btn on HGW1). After receiving the safety check completion operation from support organization 40 in S433, HGW1 switches from support request mode 2 to normal mode and performs S410 as in Figure 6.

[0075] It should be noted that HGW1 does not need to operate in all three support request modes (mode 1 to mode 3). For example, HGW1 may be configured to operate in support request modes 1 and 2 for schedules with medium (< high) importance, as shown in Figure 9, but not in support request mode 3. Similarly, HGW1 may be configured to operate in support request mode 1 for schedules with low (< medium) importance, as shown in Figure 10, but not in support request modes 2 and 3. Furthermore, HGW1 may be configured not to operate in any of the support request modes (mode 1 to mode 3) for schedules with no importance, as shown in Figure 11. In this way, with HGW1, the number of supporters can be increased as the importance of the schedule increases, allowing the scale of the support system to be adjusted according to the importance of the schedule.

[0076] As described above, the schedule management method and schedule management device according to the embodiment allow for the establishment of a support system in advance for cases where the target person does not respond to the schedule notification, in a configuration where schedules registered by the registrant are automatically communicated to the target person.

[0077] The embodiments disclosed herein should be considered in all respects to be illustrative and not restrictive. The scope of the present invention is indicated by the claims rather than by the embodiments described above, and all modifications within the meaning and scope of the claims are intended to be included. [Explanation of Symbols]

[0078] 1,2 HGW 10,20 Terminal devices 11 Landline telephone 12 Smart Speakers 13.70 Mobile devices 30 people involved 31 registered users 32 families 33 Relatives 34 Friends 40 Supporting organizations 41 Service Providers 42 Local Communities 50 Emergency Call Receiving Agencies 51 Police Agency 52 Firefighting Organizations 61,62 Higher-level equipment 100 target individuals 110 Wireless Module 120 Router Management Department 121 Routing Processing Unit 122 Wireless Processing Unit 130 Schedule Management Department 131 Notification Processing Unit 132 Schedule Processing Unit 140 VoIP Management Department 141 VoIP Processing 142 B2BUA Processing Unit 1000 Schedule Management System Bpw Power Button Btn Confirmation button Fb back Ff front Hm1 Target Person's House Hm2 Registered Home LED lamp Network Pla LAN port Pwa WAN port Pte telephone line port

Claims

1. A processor-driven method for managing the schedule of a subject, The steps include sending a notification regarding the aforementioned schedule to a terminal device, The steps include outputting the aforementioned message from the terminal device to the target person, A method comprising the step of sending a request for assistance to at least one supporter if no response from the subject to the aforementioned contact is detected.

2. The method according to claim 1, wherein the step of sending the request for assistance increases the number of at least one supporter as the importance of the schedule increases.

3. The aforementioned at least one supporter includes the first supporter and the second supporter, The step of sending the support request involves sending the support request to the first supporter, The method according to claim 2, further comprising the step of sending the support request to a second supporter if no response from the first supporter to the support request is detected.

4. The aforementioned at least one supporter further includes an emergency call receiving agency, The method according to claim 3, further comprising the step of sending an emergency call to the emergency call receiving agency if no response from the second supporter to the request for support is detected.

5. The method according to any one of claims 1 to 4, further comprising the step of receiving information about the schedule via a network.

6. The aforementioned information includes audio, The method according to claim 5, wherein the terminal device includes a fixed telephone capable of making an IP phone call via the network.

7. A program for managing the schedule of a subject, wherein when the program is executed by a processor, the processor... The terminal device will send a message regarding the aforementioned schedule. The terminal device outputs the aforementioned message to the target person. A program that, if no response is detected from the subject to the aforementioned contact, will send a request for assistance to at least one supporter.

8. A scheduling processing unit that manages the schedule of the target person, The system includes a notification processing unit that transmits information regarding the aforementioned schedule to a terminal device. The terminal device outputs the communication to the target person. The schedule processing unit, if no response from the subject to the contact is detected, transmits a request for assistance to at least one supporter via the notification processing unit, according to the importance of the schedule.

9. A schedule management device for managing the schedules of the target individuals, The system includes a terminal device that receives communications regarding the schedule from the schedule management device, The terminal device outputs the communication to the target person. The schedule management device is a system that, if no response from the subject to the contact is detected, sends a request for assistance to at least one supporter according to the importance of the schedule.

Images