Mobile terminal and report cancellation method
The integration of a cancellation notification function in mobile terminals addresses the issue of false automatic alerts by monitoring user states and sending cancellation notifications, effectively managing resource allocation and user safety.
Patent Information
- Application Number
- PCT/JP2023/018158
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2023-05-15
- Publication Date
- 2024-11-21
AI Technical Summary
Existing mobile terminals often generate false automatic notifications, leading to unnecessary resource consumption and inconvenience, as they lack a mechanism to cancel notifications after determining that the initial alert was erroneous.
Incorporating a cancellation notification function in mobile terminals that monitors the user's state post-automatic notification and sends a cancellation notification to the designated destination if the initial notification is deemed false, thereby reducing unnecessary responses and resource allocation.
This solution allows for appropriate measures to be taken in case of erroneous notifications, reducing the burden on emergency services and ensuring that only necessary responses are initiated, thus conserving resources and alleviating user concern.
Smart Images

Figure JP2023018158_21112024_PF_FP_ABST
Abstract
Description
Mobile device and how to cancel the report
[0001] The present disclosure relates to technologies for mobile terminals and the like.
[0002] Some mobile devices (e.g., information terminal devices) such as smartphones and smartwatches have a function (sometimes referred to as an automatic reporting function) that automatically reports an emergency (e.g., an abnormality or problem) to the user of the mobile device. For example, recent smartphones detect and determine an emergency / abnormal / problem state, such as a user falling and being unable to stand, based on sensing and determining acceleration in response to an impact. The smartphone then automatically issues and sends a report (e.g., an automatic report, SOS, distress signal, etc.) to a predetermined contact point, such as the police or an ambulance, depending on the state. The automatic reporting function of such mobile devices makes it easier to respond quickly to a user's emergency, such as rescue, and may even save the user's life.
[0003] An example of the prior art is Japanese Patent Application Laid-Open No. 2022-37048 (Patent Document 1). Patent Document 1 describes a mobile device that determines a fall of a user based on an impact, a first motion characteristic of the user before the impact, and a second motion characteristic of the user after the impact, and accordingly generates a notification indicating that the user has fallen.
[0004] Japanese Patent Application Laid-Open No. 2022-37048
[0005] However, the automatic reporting function of the mobile device may sometimes generate a false report even when there is nothing wrong with the user, etc. For example, when the user is engaged in an activity such as skiing, the user's smartphone may determine an abnormal state based on impact sensing, etc., and the automatic reporting may generate a false report even when there is actually no abnormality or problem.
[0006] When a false call occurs due to the automatic reporting function of the mobile device, it can be inconvenient for the user. In addition, the systems to which the police and emergency services are contacted may also be in trouble because they need resources to deal with the false call.
[0007] Prior art examples such as Patent Document 1 do not describe what to do after an automatic report or what to do in the case of a false report.
[0008] An object of the present disclosure is to provide a technology relating to the automatic reporting function of the mobile terminal that can appropriately respond even in cases of erroneous reporting, etc.
[0009] A representative embodiment of the present disclosure has the following configuration: A mobile terminal of the embodiment is a mobile terminal having an automatic reporting function, and the automatic reporting function is a function that automatically issues a first report to a first reporting destination that is a predetermined reporting destination when it is determined that a user carrying the mobile terminal is in a first state that is an emergency, abnormality, or problem state according to the state of the mobile terminal, and when the automatic reporting is issued, the mobile terminal monitors the state of the mobile terminal during the time after the automatic reporting, determines whether the first state has been resolved or whether the first report was a false report, and when it determines that the first state has been resolved or that the first report was a false report, issues a release notification to the first reporting destination to inform that the first report has been released.
[0010] According to a representative embodiment of the present disclosure, the technology relating to the automatic reporting function of the mobile terminal enables appropriate responses even in the case of a false report, etc. Problems, configurations, effects, etc. other than those described above will be described in the description of the embodiment of the invention.
[0011] 1 is a diagram showing the configuration of a system including a mobile terminal according to a first embodiment. FIG. 2 is a diagram showing a sequence between a mobile terminal and a notification destination as an overview of a notification cancellation method according to the first embodiment. FIG. 3 is a diagram showing an example of the configuration of a smartphone as a mobile terminal according to the first embodiment. FIG. 4 is a diagram showing an example of the configuration of a smartwatch as a mobile terminal according to the first embodiment. FIG. 5 is a diagram showing an example of the software configuration of a mobile terminal according to the first embodiment. FIG. 6 is a diagram showing a processing flow (1-1) of a mobile terminal according to the first embodiment. FIG. 7 is a diagram showing a processing flow (1-2) of a mobile terminal according to the first embodiment. FIG. 8 is a diagram showing a processing flow (1-3) of a mobile terminal according to the first embodiment. FIG. 9 is a diagram showing a processing flow (1-4) of a mobile terminal according to the first embodiment. FIG. 10 is a diagram showing an example of a screen display of a mobile terminal according to the first embodiment. FIG. 11 is a diagram showing the generation of an automatic notification and a cancellation notification according to the user's state on a time axis in a mobile terminal according to the first embodiment. FIG. 12 is a diagram showing an example of time interval control, such as automatic re-notification, according to the battery state on a time axis in a mobile terminal according to the first embodiment. 10A and 10B are diagrams showing examples of the configuration of an automatic report, a cancellation notice, and related information in the mobile terminal of the first embodiment.
[0012] Hereinafter, embodiments of the present disclosure will be described in detail with reference to the drawings. In the drawings, identical parts are generally designated by the same reference numerals, and repeated explanations will be omitted. In the drawings, the representation of components may not represent their actual positions, sizes, shapes, ranges, etc., in order to facilitate understanding of the invention.
[0013] For the purpose of explanation, when describing processing by a program, the program, functions, processing units, etc. may be described as the main components, but the main hardware components are the processor, or a controller, device, computer, system, etc. that is configured with the processor, etc. The computer executes processing according to the program read into memory using resources such as memory and communication interfaces as appropriate through the processor. This realizes predetermined functions, processing units, etc. The processor is configured, for example, with semiconductor devices such as a CPU / MPU or GPU. Processing is not limited to software program processing, and can also be implemented using dedicated circuits. Dedicated circuits such as FPGAs, ASICs, and CPLDs can be used.
[0014] The program may be pre-installed as data on the target computer, or may be distributed as data from a program source to the target computer. The program source may be a program distribution server on a communication network, or a non-transitory computer-readable storage medium, such as a memory card or disk. The program may be composed of multiple modules. The computer system may be composed of multiple devices. The computer system may be composed of a client-server system, a cloud computing system, an IoT system, etc. Various data and information may be composed of structures such as tables and lists, for example, but are not limited to these. Expressions such as identification information, identifiers, IDs, names, and numbers are interchangeable.
[0015] [Issues, etc.] A further explanation of the issues, etc.: When a user falls, etc., the automatic reporting function of the mobile device generates an automatic report based on impact detection. For example, the mobile device sounds a loud alert, vibrates the device, and starts a countdown. If the user does not stop the countdown, the mobile device determines that the user has been involved in a serious accident or other emergency / abnormal / problem situation, and automatically sends an automatic report to an emergency reporting service, etc.
[0016] However, after the automatic notification is sent, there may be cases where the user is not experiencing any abnormalities or problems, such as when the user has fallen but is not injured, or when the user has made a mistake by operating the device and made an automatic notification. In such cases, no rescue or other response is required from the notification destination to the user, and the automatic notification is essentially unnecessary for both the user and the notification destination.
[0017] Conventionally, when an unnecessary automated report is received by a reporting destination (e.g., police or emergency services), a responder must take action such as checking the user's condition, consuming limited resources such as time and effort.
[0018] Therefore, when an unnecessary automatic notification occurs, or when the user's condition improves after the automatic notification, it is useful to cancel / terminate the automatic notification. In other words, it is useful to inform the reporting party that although an automatic notification has occurred, there is no abnormality or problem with the user, the user has returned to normal, or that it was a false notification, and no response such as a rescue is required.
[0019] The embodiment has a mechanism for canceling the automatic notification after it has occurred, i.e., a notification cancellation function described below, which provides peace of mind to the user, reduces the time and effort required for the party to be notified, and reduces the consumption of limited resources.
[0020] Examples of telephone numbers to call for automated reporting are as follows: In Japan, 110: police, 119: ambulance. In China, 110: police, 120 or 999: ambulance. In the United States, 911: police / ambulance. In Europe, 112: police / ambulance.
[0021] <First Embodiment> A mobile terminal and a notification cancellation method according to a first embodiment of the present disclosure will be described with reference to FIGS. 1 to 14. The mobile terminal according to the first embodiment is a mobile terminal 1 equipped with an automatic notification function F1, as shown in FIG. 1 and other figures. The notification cancellation method according to the first embodiment is a method executed by the mobile terminal according to the first embodiment. The mobile terminal 1 according to the first embodiment has an automatic notification function F1 that automatically issues a first notification, which is an automatic notification 1002, to a first notification destination that is a predetermined notification destination (a notification destination system 2) when it is determined that a user U1 is in a first state, which is an emergency, abnormality, or problem state 1001, according to the state of the mobile terminal 1. The mobile terminal 1 monitors the state of the mobile terminal 1 after the automatic notification 1002, determines whether the first state has been resolved or whether the first notification was a false notification, and, if it is determined that the first state has been resolved or that the first notification was a false notification, issues a cancellation notification 1002 to the first notification destination to inform the first notification destination of the cancellation of the first notification.
[0022] [Reporting System] Fig. 1 shows an example of the overall configuration of a system including a mobile terminal 1 according to embodiment 1. The system of Fig. 1 (for the sake of explanation, also referred to as the reporting system) is a system in which the mobile terminal 1 of a user U1 and a system 2 to which a report should be made, such as to the police or an ambulance, are connected via a communication network 9. Fig. 2 also shows the main sequence between the mobile terminal 1 of Fig. 1 and the system 2 to which a report should be made, as an overview of the report cancellation method according to embodiment 1.
[0023] User U1 carries the mobile terminal 1 of the first embodiment and is a target person who uses functions such as the automatic reporting function F1 and the cancellation notification function F2 of the reporting system. The automatic reporting function F1 and the cancellation notification function F2 are implemented in the mobile terminal 1. Examples of the mobile terminal 1 include a smartphone 1A and a smart watch 1B, and the details are not limited. User U1 may own both the smartphone 1A and the smart watch 1B. The smartphone 1A and the smart watch 1B may be linked via communication.
[0024] The user U1 may fall down while walking or exercising, or may be involved in an accident, resulting in an emergency / abnormal / problem state 1001. This state 1001 is a state that is the target of an automatic notification 1002.
[0025] The mobile terminal 1 determines and detects the abnormal state 1001 (first state) of the user U1 by using the automatic reporting function F1 (step S1 in FIG. 2 ). Then, the mobile terminal 1 transmits the automatic report 1002 to the system 2, which is the predetermined reporting destination, by using the automatic reporting function F1 (step S2 in FIG. 2 ).
[0026] The system 2 to which the police, ambulance, etc. are to be notified includes a telephone 2001, a server 2002, a PC 2003, a mobile terminal 2004, etc., and receives the automatic report 1002 (step S2 in FIG. 3 ). A user U2, who is a responder U2, receives the automatic report 1002 and responds by checking the situation or providing rescue. The responder U2 may carry a mobile terminal 2004 such as a smartphone, and may receive the automatic report 1002 on the mobile terminal 2004. The response by the responder U2 may include calling out to the user U1, checking the user's condition, arranging rescue, etc., and the details are not limited.
[0027] The mobile terminal 1 of user U1 determines whether the abnormality or other condition 1001 of user U1 has been resolved or improved, or whether the previously made automatic report 1002 was a false report, etc., after the automatic report 1002 was made (step S4 in FIG. 2). If the mobile terminal 1 determines that the condition 1001 has been resolved or that the previously made automatic report 1002 was a false report, it transmits a cancellation notification 1003 for canceling the previous automatic report 1002 (the condition 1001 associated with it) to the system 2 that is the same destination as the previous automatic report 1002 (step S5 in FIG. 2).
[0028] The system 2 to which the notification is sent receives the cancellation notification 1003, and the responder U2 receives the cancellation notification 1003 and takes action such as canceling the automatic notification 1002 (step S6 in FIG. 2).
[0029] The automatic notification 1002 is, for example, a notification by telephone using a mobile network (in other words, voice data communication), but the details are not limited thereto. The automatic notification 1002 may be accompanied by data such as text, voice, and images.
[0030] 1 , a business operator's system 3 is connected to the communication network 9 and includes a business operator's server 3001 and a PC 3002. The business operator's system 3 may communicate with the mobile terminal 1 of the user U1 to provide some of its functions, or may communicate with the notification destination system 2 to provide some of its functions, or may be interposed between the mobile terminal 1 of the user U1 and the notification destination system 2. For example, as a cloud computing system or a client-server system, the business operator's server 3001 may perform processes such as detecting and determining the status related to the automatic notification 1002, or may perform processes such as detecting and determining the status related to the release notification 1003.
[0031] 1 also illustrates the components described below. The mobile terminal 1 of user U1 is connected to a mobile terminal 4001 of another user U3, such as a family member or acquaintance, via a communication network 9. Alternatively, the mobile terminal 1 of user U1 may be surrounded (within a relatively close distance range) by a mobile terminal 4001 of another user U3, such as a family member or acquaintance, or may be surrounded (within a relatively close distance range) by a mobile terminal 4001 of an unspecified other user U3. Furthermore, the mobile terminal 1 of user U1 may be surrounded (within a relatively close distance range) by an unspecified arbitrary device 4002. Examples of the surrounding device 4002 include a surveillance camera, a facility server, and a wireless base station.
[0032] 2 is a sequence diagram showing an outline of the notification cancellation method according to embodiment 1. In step S1, the automatic notification function F1 of the mobile terminal 1 of the user U1 determines and detects an emergency / abnormal / problem state 1001, such as a fall of the user U1, based on sensing using various sensors, etc. In step S2, the automatic notification function F1 of the mobile terminal 1 transmits an automatic notification 1002 to the system 2, which is a predetermined notification destination, to inform the system 2 of the user U1 of the state 1001 and request rescue, etc.
[0033] In step S3, the system 2 to which the notification is sent receives the automatic notification 1002 and takes action. For example, a responder U2 checks the automatic notification 1002, contacts the mobile terminal 1 of the user U1 who sent the notification, and checks the status of the user U1. Note that although the action in step S3 is shown to be taken immediately in FIG. 2, it is not necessarily taken immediately.
[0034] In step S4, the mobile terminal 1 determines and detects, using the release notification function F2, whether the emergency / abnormal / problem state 1001 of user U1 has been resolved / improved or whether it was a false report, based on additional monitoring including additional sensing, after the automatic report 1002.
[0035] In step S5, if the cancellation notification function F2 of the mobile terminal 1 determines in step S4 that the problem has been resolved or that the report was a false alarm, it sends a cancellation notification 1003 (in other words, an SOS cancellation notification) to the same destination as the destination of the previous automatic report 1002. In step S6, the destination system 2 receives the cancellation notification 1003, and the responder U2 responds to the cancellation (SOS cancellation) of the previous automatic report 1002 based on the cancellation notification 1003.
[0036] [Automatic Reporting Function] First, a configuration example of the automatic reporting function F1 in Fig. 1 will be described as a basic prerequisite function for performing the automatic reporting 1002. This automatic reporting function F1 can similarly apply, for example, the technology described in Patent Document 1, but is not limited to this. In the first embodiment, a case will be described in which the technology described in Patent Document 1 is similarly applied as the automatic reporting function F1.
[0037] In this automatic reporting function F1, the mobile device 1 uses various sensors to sense the movement, impact, etc. of the mobile device 1 or the user U1. The mobile device 1 compares the user U1's motion characteristics before the detected impact with the user U1's motion characteristics after the detected impact to determine whether the user U1 has fallen or the like. For example, the motion characteristics before the impact show the user U1 walking normally with periodic movements, whereas the motion characteristics after the impact show the user U1's body orientation changing and moving irregularly. The mobile device 1 can estimate an event or state, such as a fall, of the user U1 from such a change in motion characteristics. If the mobile device 1 determines that the user U1 has fallen or the like, i.e., if the mobile device 1 determines that the user U1 is in an emergency / abnormal / problem state 1001, it generates an automatic report 1002. The automatic report 1002 is a report indicating that the user U1 is in an emergency, abnormal, problem, or other state 1001 due to a fall or the like.
[0038] In the case of the technology of Patent Document 1, as shown in the state transition diagram of FIG. 12, before issuing an SOS report, the system waits for a certain period of time (1206b) and makes a determination. If the technology of Patent Document 1 determines during this waiting period that an SOS report is necessary, it issues an SOS report (1202) and returns to the nominal state (1202). Furthermore, if the technology of Patent Document 1 determines during this waiting period that an SOS report is not necessary, it cancels the SOS report (1210) and returns to the nominal state (1202) without issuing an SOS. The technology of Patent Document 1 does not disclose any processing that occurs after issuing the SOS report (1202).
[0039] [Cancellation Notification Function] Next, a description will be given of the cancellation notification function F2, which is a characteristic function in the first embodiment and is a function for issuing the cancellation notification 1003.
[0040] In the first embodiment, after the automatic notification function F1 outputs the automatic notification 1002 ( FIG. 1 ), the release notification function F2 of the mobile terminal 1 continues to monitor the status of the mobile terminal 1 and the user U1, such as their movements. The release notification function F2 of the mobile terminal 1 determines whether the emergency / abnormal / problem state 1001 of the user U1 has been resolved, or whether the previous automatic notification 1002 was a false notification when the user U1 was in a normal state. For example, when the release notification function F2 of the mobile terminal 1 detects a movement such as the user U1 standing up and starting to walk again after falling, it determines that the abnormal state 1001 has been resolved, or that the state was a false notification rather than the abnormal state 1001. Then, the cancellation notification function F2 of the mobile terminal 1 generates a cancellation notification 1003 to the same notification destination as the previous automatic notification 1002 to inform the user U1 that the abnormality or other condition 1002 related to the previous automatic notification 1002 has been resolved or that it was a false notification, and automatically sends the cancellation notification 1003.
[0041] In the first embodiment, the notification cancellation determination process by the cancellation function F2 after the automatic notification 1002 includes the same process as the automatic notification determination process by the automatic notification function F1 (particularly, a comparison of operational characteristics before and after the impact), but also includes additional monitoring processes including additional sensing by increasing the number of parameters such as sensors used. In the first embodiment, the additional parameters such as sensors include a determination of the status of the user U1 by voice input and voice recognition. The mobile terminal 1 turns on the voice input and voice recognition function including the microphone. In this on state, the mobile terminal 1 may input and recognize a voice from the user U1 to communicate his or her status or to cancel the notification, or may pick up voices around the mobile terminal 1 to determine the status.
[0042] If the mobile terminal 1 determines based on the additional sensing that the state 1001 of the user U1, such as an abnormality, has been resolved or that it was a false report, it transmits a cancellation notification 1003 to the previous report destination.
[0043] As described above, in embodiment 1, the process of determining the status of user U1, which includes sensing by the automatic notification function F1, and the process of determining the status of user U1, which includes additional sensing by the release notification function F2 after automatic notification 1002, are partially different, with the latter including additional sensing.
[0044] [Related Information] Furthermore, the release notification function F2 of the mobile terminal 1 includes or attaches related information 1004 to the release notification 1003, which is information that associates the release notification 1003 with the previous automatic report 1002 and makes it easier for the report recipient to identify the previous automatic report 1002. This related information 1004 is information that indicates, for example, that the previous automatic report 1002 was an automatic report generated based on the detection of an impact by the automatic report function F1, that the previous automatic report 1002 and this release notification 1003 are related, etc.
[0045] This related information 1004 includes at least one of the following information: unique information such as the ID and communication address of the device, i.e., the mobile terminal 1; user information such as a telephone number, location information, and the name of user U1; date and time information (e.g., date, time, minutes, and seconds) of the transmission of the automatic notification 1002; and information on the content of the transmission.
[0046] When the notification destination system 2 receives the cancellation notification 1003, it can identify the previous automatic notification 1002 associated with this cancellation notification 1003 from the related information 1004 included in the cancellation notification 1003. The notification destination system 2 can then recognize that the previous automatic notification 1002 is no longer necessary or was a false notification and can be canceled. The responder U2 can determine that no response such as rescue is necessary in response to the previous automatic notification 1002, or that only a simple response is sufficient because the condition of user U1 is minor.
[0047] [Detailed Functions of Release Notification Function F2] Further, detailed functions of the release notification function F2 include the following.
[0048] (1) The mobile terminal 1 has a function of outputting from the mobile terminal 1 a message indicating that the mobile terminal 1 has made an automatic report 1002 to the report destination (in other words, that an automatic report has been made) to inform the user U1. This output is performed at least by display or voice.
[0049] (2) After the automatic notification 1002, the mobile terminal 1 starts additional monitoring for a cancellation notification 1003. In this additional monitoring, in addition to the additional sensing with the increased number of sensors described above, the mobile terminal 1 turns on short-range communication to communicate with devices around the mobile terminal 1 and notify the devices around the mobile terminal 1 of the status of the user U1.
[0050] (3) When the mobile terminal 1 receives a call from the destination or another number on the mobile terminal 1 of the user U1 during the additional monitoring period after the automatic notification 1002, the mobile terminal 1 automatically determines, by searching or the like, whether the caller number is the number of the specified destination, the number of a caller related to the specified destination, or the number of an unrelated third party.The mobile terminal 1 then automatically branches the response process depending on the determined number.For example, the mobile terminal 1 outputs from the mobile terminal 1 what type of contact (caller) it is and makes it clear.
[0051] (4) During the additional monitoring period after the automatic notification 1002, the mobile terminal 1 continues to determine whether the abnormal state 1001 of the user U1 continues or whether the user U1 has returned to a normal state, and if it determines that the abnormal state 1001 continues, it again performs processing such as sending the automatic notification 1002 to a predetermined notification destination. In addition, the mobile terminal 1 may output an alert from the mobile terminal 1 in such a case.
[0052] In such a case, the mobile terminal 1 may send a notification 1011 to a pre-set contact other than the predetermined contact, such as a family member or acquaintance, that the user U1 is in an abnormal state 1001. The user U3 who receives the notification 1011 on the mobile terminal 4001 can recognize that the user U1 is in an abnormal state 1001 even after the automatic notification 1002.
[0053] In such a case, the mobile terminal 1 may transmit, based on short-range communication, a notification 1012 to a nearby third party's mobile terminal 4001 or any device 4002, informing the user U1 that the user U1 is in an abnormal state 1001. These surrounding devices are any devices that can accept short-range communication of the notification 1012. When the surrounding devices receive the notification 1012, they can recognize that the user U1 in need of rescue is nearby after the automatic report 1002.
[0054] (5) If the mobile terminal 1 determines during the additional monitoring period that the user U1's abnormal state 1001 continues, the mobile terminal 1 transitions to a battery save mode in which power is conserved by refraining from operations other than those related to the automatic report 1002. In the battery save mode, the mobile terminal 1 may periodically issue the automatic report 1002 to the report destination again. Furthermore, in the battery save mode, the mobile terminal 1 controls the time interval for periodically repeating the automatic report 1002 or other types of communication so as to change the time interval depending on the remaining battery power. This allows the mobile terminal 1 to wait for the automatic report 1002, make a rescue call to the outside, or perform other actions for as long as possible.
[0055] [Smartphone 1A] Figure 3 shows an example of the hardware configuration of a smartphone 1A as the mobile terminal 1. The smartphone 1A includes a processor 301, memory 302, non-volatile memory 303, a camera / imaging unit 304, a position detection unit 305, an orientation detection unit 306, a biometric information detection unit 307, a first wireless communication unit 311, a second wireless communication unit 312, a third wireless communication unit 313, a wired communication unit 314, a button / operation unit 315, a display / display unit 316, a microphone / audio input unit 317, a speaker / audio output unit 318, a connector / input / output interface 319, a battery / power supply unit 320, a vibration unit 321, a light-emitting unit 322, and the like. These components are interconnected by an architecture such as a bus (not shown). Note that not all of these elements are essential, and some may be omitted.
[0056] For example, the non-volatile memory 303 stores necessary data and information such as an OS, programs, device information, application information, user information, notification destination information, status information, and setting information. The programs are computer programs for configuring the automatic notification function F1 and the release notification function F2. The device information includes unique information such as the ID and communication address information of this smartphone 1A. The application information is information on various application programs. The user information is information such as the name of the user U1 who owns and uses this smartphone 1A. The notification destination information is information such as the telephone number or URL of a specified notification destination when automatic notification 1002 is made. The status information is information that represents the status of the user U1 and the mobile terminal 1. The setting information is system setting information and user setting information related to functions.
[0057] Examples of information included in the device information, app information, and user information include the smartphone 1A's device-specific number, communication address, network ID, telephone number, user U1's name, and user ID in apps such as LINE (a calling app). Examples of status information include whether or not user U1 is in an emergency / abnormal / problem state 1001, whether or not an SOS (automatic report 1002) has been sent, whether or not a contact / response has been made to the SOS by the report destination, and whether or not a release notice 1003 has been sent. Furthermore, the memory 303 or the non-volatile memory 303 may store history information related to functions and processes, including status information at each point in time.
[0058] The automatic notification function F1 and the release notification function F2 may be implemented as part of the OS or as a dedicated application program. If implemented as an application, the application may display an application screen on the display unit 316.
[0059] The smartphone 1A has a flat housing and includes, on the front side thereof, a touch panel display / display unit 316 and an in-camera as the camera / imaging unit 304. The smartphone 1A also has, on the back side thereof, an out-camera as the camera / imaging unit 304. The smartphone 1A also has, on the side of the housing, a button / operation unit 315, a microphone / audio input unit 317, a speaker / audio output unit 318, a connector / input / output interface 319, etc.
[0060] The processor 301 is composed of a CPU or the like and constitutes a controller of the smartphone 1A. The processor 301 reads and writes data and information from the memory 302 and the non-volatile memory 303. The processor 301 executes processing in accordance with a program read onto the memory 302. This realizes various functions and processing units.
[0061] The first wireless communication unit 311 is implemented with, for example, a wireless LAN communication interface (e.g., Wi-Fi). The second wireless communication unit 312 is implemented with, for example, a mobile network communication interface (e.g., LTE, 4G, 5G, etc.). The third wireless communication unit 313 is implemented with, for example, a short-range wireless communication interface (e.g., Bluetooth, NFC, etc.). The wired communication unit 314 is implemented with a wired communication interface (e.g., USB).
[0062] The button / operation unit 315 includes, for example, a power button, a volume button, etc., and is a unit that receives operation input from the user U1. The processor 301 performs control in accordance with the operation input on the button / operation unit 315. The display / display unit 316 includes, for example, an LCD / organic EL touch panel. The microphone / audio input unit 317 inputs audio from a microphone and converts it into audio data. The speaker / audio output unit 318 converts the audio data into audio and outputs it from a speaker. The connector / input / output interface 319 includes, for example, a USB connector that is compatible with USB. The battery / power supply unit 320 supplies power charged in the battery to each unit. The vibration unit 321 generates vibrations as needed. The light-emitting unit 322 generates light as needed.
[0063] The camera / imaging unit 304 captures images using the front camera and rear camera and obtains captured image data. The position detection unit 305 acquires current location information (e.g., latitude, longitude, altitude, etc.) of the smartphone 1A using, for example, a GPS receiver. The position detection unit 305 may also acquire wireless base station location information from a wireless base station. The attitude detection unit 306 includes various sensors, such as a geomagnetic sensor, a gyro sensor, and an acceleration sensor, and detects the current attitude of the smartphone 1A (e.g., the orientation of three orthogonal axes, X, Y, and Z), as well as angular velocity and acceleration. Other sensors included in the mobile terminal 1 may include an illuminance sensor, a proximity sensor, a ranging sensor, and a gaze detection sensor. The illuminance sensor detects the illuminance around the smartphone 1A. The proximity sensor detects the proximity of other objects to the smartphone 1A. The ranging sensor measures the distance from the smartphone 1A to external objects. The gaze detection sensor detects the gaze of the user U1 looking at the smartphone 1A. The biological information detection unit 307 detects the biological information of the user U1.
[0064] When making the automatic notification 1002, the smartphone 1A may use the display / display unit 316, the speaker / audio output unit 318, the vibration unit 321, the light emitting unit 322, etc. to perform a predetermined output.
[0065] [Smartwatch 1B] Figure 4 shows an example of the hardware configuration of a smartwatch 1B as the mobile terminal 1. The smartwatch 1B includes a processor 401, a memory 402, a non-volatile memory 403, a button / operation unit 415, a display / display unit 416, a microphone / audio input unit 417, a speaker / audio output unit 418, a position detection unit 405, an attitude detection unit 406, a biometric information detection unit 407, a communication interface 411, a battery / power supply unit 420, a vibration unit 421, a light-emitting unit 422, a sensor interface 431, and the like. These components are interconnected by an architecture such as a bus (not shown). Note that not all of these elements are essential, and some may be omitted.
[0066] For example, the non-volatile memory 403 stores necessary data and information such as an OS, programs, device information, application information, user information, notification destination information, status information, and setting information. The programs are computer programs for configuring the automatic notification function F1 and the release notification function F2. The device information is unique information such as the ID of this smart watch 1B. The application information is information on various application programs. The user information is information on the user U1 who owns and uses this smart watch 1B. The notification destination information is information such as the telephone number and URL of a specified notification destination when an automatic notification 1002 is made. The status information is information that represents the status of the user U1 and the mobile terminal 1. The setting information is system setting information and user setting information related to the functions.
[0067] Examples of information included in the device information, app information, and user information include the device unique number of the smart watch 1B, a communication address, a network ID, a telephone number, the name of the user U1, and a user ID in an app such as LINE (a calling app). Examples of the status information include whether or not the user U1 is in an emergency / abnormal / problem state 1001, whether or not an SOS (automatic report 1002) has been sent, whether or not there has been a contact / response from the report destination to the SOS, and whether or not a release notice 1003 has been sent. In addition, the memory 403 or the non-volatile memory 403 may store history information related to functions and processes, including status information at each point in time.
[0068] The automatic notification function F1 and the release notification function F2 may be implemented as part of the OS or as a dedicated application program. If implemented as an application, the application may display an application screen on the display unit 416.
[0069] The smartwatch 1B has a wristwatch-like housing and includes a touch panel display / display unit 416 on the front side. The smartwatch 1B also has a button / operation unit 415, a microphone / audio input unit 417, a speaker / audio output unit 418, etc. on the side of the housing.
[0070] The processor 401 is composed of a CPU or the like and constitutes the controller of the smartwatch 1B. The processor 401 reads and writes data and information from the memory 402 and the non-volatile memory 403. The processor 401 executes processing in accordance with the program read onto the memory 402. This realizes various functions and processing units.
[0071] The communication interface 411 is a part in which one or more communication interfaces, for example, a wireless LAN, a mobile network, a short-range wireless communication, etc., are implemented. When the communication interface 411 is to cooperate with the smartphone 1A, a communication interface for the cooperation is implemented in the communication interface 411.
[0072] The button / operation unit 415 includes, for example, a home button, a reset button, etc., and is a unit that receives operation inputs from the user. For example, when the home button is pressed, the processor 401 controls the smart watch 1B main body to be in an initial state and displays an initial screen on the display / display unit 416.
[0073] The display / display unit 416 includes, for example, a liquid crystal / organic EL touch panel. The microphone / audio input unit 417 inputs audio from a microphone and converts it into audio data. The speaker / audio output unit 418 converts the audio data into audio and outputs it from a speaker. The battery / power supply unit 420 supplies power charged in the battery to each unit. The vibration unit 421 generates vibrations as needed. The light emitting unit 422 generates light as needed.
[0074] The position detection unit 405 acquires current position information (e.g., latitude, longitude, altitude, etc.) of the smartwatch 1B using, for example, a GPS receiver. The position detection unit 405 may also acquire wireless base station position information from a wireless base station. The attitude detection unit 406 includes various sensors, such as a geomagnetic sensor, a gyro sensor, and an acceleration sensor, and detects the current attitude of the smartwatch 1B (e.g., the orientation of three orthogonal axes, X, Y, and Z), as well as angular velocity and acceleration. Other sensors included in the smartwatch 1B may also include an illuminance sensor, a proximity sensor, a distance measurement sensor, and a gaze detection sensor. The illuminance sensor detects the illuminance around the smartwatch 1B. The proximity sensor detects the proximity of other objects to the smartwatch 1B. The distance measurement sensor measures the distance from the smartwatch 1B to external objects. The gaze detection sensor detects the gaze of the user U1 looking at the smartwatch 1B. The biometric information detection unit 407 detects biometric information of the user U1.
[0075] The sensor interface 431 is an interface for connecting an external sensor. For example, a physical information measurement sensor 441 is connected to the sensor interface 431. The physical information measurement sensor 441 measures, for example, pulse rate, heart rate, or blood flow. For example, the sensor 441 may be configured to irradiate light onto the arm of the user U1, receive reflected light, and generate a signal corresponding to the amount of received light. Additionally, the smartwatch 1B may be equipped with a camera or the like.
[0076] When making an automatic notification 1002, the smart watch 1B may be configured to make a predetermined output using the display / display unit 416, speaker / audio output unit 418, vibration unit 421, light-emitting unit 422, etc.
[0077] [Functional Blocks] Fig. 5 shows an example of the configuration of software functional blocks of the mobile terminal 1 (here, the case of a smartphone 1A will be described). The functional blocks in Fig. 5 are realized by processing by the processor 301. The automatic reporting function F1 and the release notification function F2 may be implemented mainly by a computer program. The automatic reporting function F1 and the release notification function F2 may be implemented by a dedicated application. Only the release notification function F2 may be implemented by a dedicated application. Furthermore, the release notification function F2 may be implemented integrally with the automatic reporting function F1.
[0078] The automatic reporting function F1 inputs sensor information 501, which is an output value from a sensor such as the posture detection unit 305, and performs process 502 to determine the state of user U1, such as an abnormality, based on the sensor information 501. Process 502 determines whether user U1 has fallen or fallen into an emergency / abnormal / problem state 1001. Note that a state that does not fall under the state of abnormality, etc. 1001 is also referred to as a normal state. If the result of process 502 is the state of abnormality, etc. 1001, the automatic reporting function F1 performs process 503 to generate and send an automatic report 1002 based on report destination information 504, etc. The report destination information 504 is information such as the telephone number of a specified report destination that has been set. The automatic reporting function F1 enters information in the state information 505 (or history information) indicating that user U1 is in the state of abnormality, etc. 1001, and that automatic report 1002 has been made.
[0079] When an automatic notification 1002 is generated by the automatic notification function F1, for example, when the status information 505 indicates an abnormal state and that an automatic notification has been generated (automatic notification completed), the release notification function F2 starts processing for a release notification 1003. After the automatic notification 1002, the release notification function F2 performs processing 512 to continue monitoring using sensor information 511 from the sensor. This monitoring is also referred to as additional monitoring. This additional monitoring includes additional sensing as described above.
[0080] The release notification function F2 performs processing 513 to determine whether the emergency / abnormal / problem state 1001 of the user U1 has been resolved as a result of the additional monitoring, or whether the previous automatic notification 1002 was a false notification.
[0081] If the result of the above determination is that the problem has been resolved or that it was a false report, the release notification function F2 generates a release notification 1003 based on the above-mentioned report destination information 504, status information 505, etc., and performs process 514 of sending the release notification 1003 to the same report destination as the previous automatic report 1002. At this time, as described above, this release notification function F2 includes related information 1004 for relating the release notification 1003 with the previous automatic report 1002 so that the previous automatic report 1002 can be easily identified.
[0082] After sending the release notification 1003, the release notification function F2 records information in the status information 515 (or history information) indicating that the abnormal state 1001 of user U1 has been resolved (in other words, normal state, resolved state) and that the release notification 1003 has been sent (release notification completed).
[0083] [Regarding Correlation and Identification of Notifications] The following describes the correlation and identification between the automatic notification 1002 (which may be considered the first notification) by the automatic notification function F1 and the cancellation notification 1003 (which may be considered the second notification) by the cancellation notification function F2. For example, if these two notifications or notifications, or an unspecified number of notifications including them, cannot be quickly identified in the notification destination system 2 ( FIG. 1 ), which receives them, the response work becomes time-consuming. Therefore, in embodiment 1, the cancellation notification 1003 includes related information 1004 that informs the notification destination that the automatic notification 1002 by the automatic notification function F1 and the cancellation notification 1003 by the cancellation notification function F2 are related information. The notification destination system 2 can easily and quickly correlate the two notifications and notifications and identify the previous automatic notification 1002 from the related information 1004 of the cancellation notification 1003.
[0084] Both the automatic notification 1002 and the cancellation notification 1003 are accompanied by information such as the device ID of the mobile terminal 1, the telephone number, location information, the name of the user U1, the status of the user U1, etc. The cancellation notification 1003 includes related information 1004 indicating the relationship with the previous automatic notification 1001.
[0085] 15 illustrates an example of the configuration of the automatic notification 1002, the release notification 1003, and the related information 1004. In the example (A), the information content of the release notification 1003, such as the device ID, telephone number, location information, and user name, corresponds to the related information 1004.
[0086] As another example of the configuration of the related information 1004, as shown in (B), the release notice 1003 may specify and describe the date and time of transmission of the related automatic report 1002. Furthermore, the release notice 1003 may have data of a copy of the content of the related automatic report 1002.
[0087] As another example of the configuration of the related information 1004, as shown in (C), an ID may be assigned to each of the automatic notification 1002 and the cancellation notification 1003, and the related information 1004 may point to the ID of the automatic notification 1002.
[0088] Furthermore, the system 2 of the report destination may output, based on the above information, for example, a telephone number, one or more reports or notifications from the same telephone number as related reports in the form of a group, tree, thread, etc. This allows the responder U2 of the report destination to easily identify, among the multiple reports received, the automatic report 1002 from the automatic report function F1 and the release notification 1003 from the release notification function F2 as related reports, making it easier to respond to the reports.
[0089] [Processing Flow] Next, a detailed processing flow in the first embodiment will be described. Figures 6 to 9 show processing flow examples of the mobile terminal 1. The flow in Figure 6 is a partial flow, and is designated as (1-1).
[0090] [Processing Flow (1-1)] In FIG. 6, in step S600, initially, the state of user U1 of the mobile device 1 is normal. In step S601, the mobile device 1 continues sensing for a first time period as normal monitoring using the automatic reporting function F1, and acquires sensor information. This first time period refers to the time period before the detection of the impact described below. For example, in the first time period, sensor information indicating the movement status and vibration status of user U1 (e.g., stationary, walking on a level surface, walking up stairs, etc.) is obtained.
[0091] In step S602, the mobile terminal 1 senses peculiar information. The peculiar information is, for example, an impact of a certain magnitude or greater. The impact may be, for example, an impact when the user U1 falls and hits the ground, or an impact when the user U1 is involved in an accident and an external object hits the user U1.
[0092] In step S603, the mobile device 1 continues sensing for a second time period after detecting the peculiar information (e.g., an impact) and acquires sensor information. This second time period refers to the time period after detecting the impact. For example, during the second time period, sensor information indicating the movement status and vibration status of the user U1 (e.g., lying motionless on the ground) is acquired.
[0093] In step S604, the mobile terminal 1 determines whether the state of user U1 is an emergency / abnormal / problem state 1001 such as a fall or an accident, based on the sensor information at the first time, the peculiar information, and the sensor information at the second time. For example, when there is a large change in the behavior characteristics at the first time and the behavior characteristics at the second time, the mobile terminal 1 can estimate that the state is a fall or the like.
[0094] If the result of step S604 is that user U1 is in a state 1001 such as an abnormality, in step S605, the mobile terminal 1 determines whether automatic notification 1002 is necessary based on the situation at the second time. This determination is made so as not to perform automatic notification 1002 if the mobile terminal 1 determines or estimates that user U1 is in a state 1001 such as an abnormality, but user U1 is actually in a normal state. In step S605, for example, the mobile terminal 1 outputs an alert to user U1 and starts a countdown (see (A) in FIG. 10 described below). During this countdown, the mobile terminal 1 accepts an operation input from user U1 (i.e., a confirmation input indicating that there is no problem / automatic notification is not necessary), and if this operation input is received, the mobile terminal 1 determines that user U1 is in a normal state. In this case, the mobile terminal 1 determines that automatic notification 1002 is not necessary. On the other hand, if the countdown time expires without any operational input from the user U1, the mobile terminal 1 determines that an automatic notification 1002 is necessary because the user U1 has not responded.
[0095] The process of step S605 corresponds to the determination of SOS cancellation during the standby time in FIG. 12 in the technology of Patent Document 1.
[0096] If, as a result of step S605, it is determined in step S606 that an automatic report 1002 is necessary (Y), then in step S607 the mobile terminal 1 transmits the automatic report 1002 to a predetermined report destination. The mobile terminal 1 includes in the automatic report 1002 information that can identify the mobile terminal 1, which is the device that is transmitting the automatic report 1002. This information is, for example, the ID of the mobile terminal 1, a telephone number, location information, the name of the user U1, etc. The mobile terminal 1 also includes in the automatic report 1002 information that indicates the status of the user U1 of the mobile terminal 1, i.e., a state 1001 such as a determined abnormality (for example, a state in which the user has fallen and is immobile).
[0097] In step S608, the mobile terminal 1 records the fact and results of sending the automatic report 1002 (such as whether an automatic report was sent, the report destination, the date and time, and the content of the report) in the status information 505 (FIG. 5) or history information, and stores the information in the non-volatile memory 303 or the like within its own device. In addition, the mobile terminal 1 notifies the user U1 that the automatic report 1002 has been sent by, for example, displaying the information on the screen or outputting a voice (see (B) of FIG. 10 described below).
[0098] If it is determined in step S606 that the data is not required (S606-N), the process returns to step S601, for example, and the same process is repeated. After step S608, the process continues to the next flow.
[0099] [Processing Flow (1-2)] Fig. 7 shows the next processing flow (1-2). The process continues from step S608 to step S701. In step S701, the mobile terminal 1 starts processing using the cancellation notification function F2 in response to the generation of the automatic notification 1002. In more detail, processing using the cancellation notification function F2 may start after the automatic notification 1002 is sent in step S607.
[0100] In step S702, the mobile terminal 1 continues monitoring the status of user U1 using sensors. In other words, the mobile terminal 1 considers monitoring using the automatic notification function F1 as the aforementioned normal monitoring, and monitoring using the release notification function F2 as additional monitoring (in other words, post-notification monitoring), and starts this additional monitoring. In this additional monitoring, the types of sensors used are increased compared to the sensing during normal monitoring. For example, sensors to be added include voice input / voice recognition including a microphone, and short-range communication functions such as NFC. The mobile terminal 1 forcibly turns on these additional sensors. This voice input / voice recognition is realized, for example, by the microphone / voice input unit 317 in FIG. 3. This short-range communication function is realized, for example, by the third wireless communication unit 313 in FIG. 3.
[0101] In step S703, the mobile terminal 1 senses the movement status, vibration status, voice input / voice recognition status, short-range communication status, etc. of user U1 for at least a predetermined time (here referred to as the third time) after automatic notification 1002 through additional monitoring including the additional sensing turned on in step S702, and detects and acquires sensor information (in other words, time-series sensor data) at the third time.
[0102] When using voice input / voice recognition as an additional sensor, for example, the voice uttered by the user U1 and the voices around the mobile terminal 1 are acquired as voice data by the mobile terminal 1 through voice input / voice recognition. This voice data becomes material for determining the state of the user U1.
[0103] Furthermore, when short-range communication is used as an additional sensor, for example, the mobile terminal 1 may transmit a signal to the surrounding area by short-range communication and receive a response signal from any device in the surrounding area.
[0104] In step S704, the mobile terminal 1 determines, based on the sensor information for the third time period in step S703, whether the state of user U1 has returned to a normal state from the abnormal state 1001, or whether it was a false alarm and the state remains normal. In other words, the mobile terminal 1 determines, with respect to the previous automatic notification 1002, whether the situation of user U1 has become one in which a rescue or other response is no longer required, whether the abnormal state 1001 has been resolved / improved, that is, whether the previous automatic notification 1002 should be canceled, etc.
[0105] The determination process of step S704 may be the same as that of steps S604 and S605, but may also take additional sensor information into consideration. For example, assume that user U1 fell to the ground at the time of the automatic notification 1002. Thereafter, assume that user U1 is physically and mentally healthy, stands up, and begins walking. The mobile device 1 determines that user U1 has returned to a normal state by assessing and estimating this situation (see FIG. 13, described below). Furthermore, for example, after the automatic notification 1002, user U1 may input a voice message indicating that he or she is physically and mentally healthy, and the mobile device 1 may determine that user U1 has returned to a normal state based on that voice message.
[0106] In step S705, if the result of step S704 above shows that user U1 has returned to a normal state (Y), the mobile terminal 1 branches to step S706, and if the result is that user U1 has not returned to a normal state (N), the mobile terminal 1 branches to step S901 described below.
[0107] In step S706, the mobile terminal 1 generates a cancellation notification 1003 related to the previous automatic report 1002 (step S607) and transmits it to the previous report destination. As described above, this cancellation notification 1003 includes related information 1004 for associating and identifying the previous automatic report 1002. This cancellation notification 1003 is information that informs the report destination that the emergency / abnormal / problem state 1001 of user U1 related to the previous automatic report 1002 has been resolved, or that it is minor and therefore not a problem, that it was a false report, that a response such as rescue is no longer necessary, or that the previous automatic report 1002 may be canceled. The cancellation notification 1003 may also be referred to as an abnormal event resolution notification, etc.
[0108] In the system 2 (FIG. 1) to which the notification is sent, the person in charge U2 can immediately identify the previous automatic notification 1002 associated with the release notification 1003 from the release notification 1003 and the related information 1004 contained therein. The person in charge U2 can then recognize that there is no problem with the status of the user U1 of the mobile terminal 1 related to the previous automatic notification 1002, and that a rescue or other response is no longer necessary.
[0109] When the system 2 to which the report is sent receives an unspecified number of reports, the work of responding to them is difficult, but the cancellation notification 1003 allows the automatic reports 1002 to be canceled to be immediately identified from the unspecified number of reports, thereby reducing the number of reports that require a response. The system 2 to which the report is sent can reduce the consumption of limited resources involved in the work of responding.
[0110] In step S707, the mobile terminal 1 records and stores in the status information 515 (FIG. 5) or history information the fact and result of transmitting the release notification 1003. The status information 515 or history information may include, for example, the date and time when the release notification 1003 was transmitted, the content of the transmission, etc.
[0111] In step S708, the mobile terminal 1 stops the additional monitoring process, in other words, turns off the additional sensing. For example, the voice input / voice recognition and near field communication are forcibly turned off.
[0112] In step S709, the mobile terminal 1 outputs (at least by displaying on the screen or outputting audio) from its own device that the release notification 1003 has been sent to the report destination. For example, the mobile terminal 1 displays on the screen that the release notification 1003 has been sent and outputs audio that the release notification 1003 has been sent (see (A) in FIG. 11 described below).
[0113] In the example of Fig. 7, voice input and near field communication are turned on at step S703. This is preparation for subsequent processing. The timing for turning on these additional sensing functions is not limited to step S703, but may be later. As will be described later, the timing may be changed depending on the battery status of the mobile terminal 1.
[0114] [Processing Flow (1-3)] Figure 8 shows a processing flow (1-3) as a modified example of the processing flow (1-2) of Figure 7. The flow of Figure 8 defines a processing example when an incoming call to contact from a third party is received during the third time period of step S703 after the start of additional monitoring. In Figure 8, step S801 and the like are added after step S703. In step S801, if the mobile terminal 1 receives an incoming call to contact from a third party (Y), the mobile terminal 1 proceeds to step S802. If the call is not received (N), the flow goes to step S704 described above.
[0115] In step S802, the mobile terminal 1 checks whether the call from the third party is a call from the destination of the previous automatic report 1002 (step S607), i.e., a call back to the automatic report 1002. This check is, for example, checking whether the call is from the same telephone number as the previous destination. If it is a call from the destination (Y), the process proceeds to step S803; if it is not (Y), the process proceeds to step S811.
[0116] In step S803, the mobile terminal 1 determines whether user U1 has returned to a normal state (resolved) based on sensor information and the like up to the current time when the mobile terminal 1 received the contact from the report destination. If the result of this determination in step S803 is that user U1 has returned to a normal state (Y), the process proceeds to step S805. In step S805, the mobile terminal 1 responds to the contact from the report destination, informing user U1 that user U1 has returned to a normal state and that there are no problems, i.e., that the automatic report 1002 may be canceled. This response is functionally equivalent to the cancellation notification 1003. This response may be made by user U1 himself / herself by voice on the phone, or may be automatically made by the mobile terminal 1. In the latter case, the effort required of user U1 can be reduced.
[0117] On the other hand, if it is determined in step S803 that the normal state has not been restored (N), the process proceeds to step S806. In step S806, the mobile terminal 1 responds to the contact from the report destination with the determination result, i.e., that it has not yet been determined that the abnormal state of user U1 has been resolved (returned to the normal state), and that monitoring is continuing. This response is automatically made by the mobile terminal 1. The mobile terminal 1 also includes in this response an indication that it will contact again after a predetermined time (e.g., the third time) has elapsed.
[0118] After this response, if the mobile terminal 1 determines that the user U1 has not returned to the normal state after a predetermined time (for example, the third time) has elapsed, it automatically sends a message to the report destination again to inform the user that the user U1 has not returned to the normal state. This message is repeated as many times as necessary.
[0119] After step S805, in step S807, the mobile terminal 1 stops the additional monitoring by the release notification function F2, as in step S708. The process after step S807 is the same as in FIG.
[0120] The processing in step S802 may be, for example, as follows. The predetermined report destination is, for example, 110 or 119. In contrast, it is assumed that the contact from the third party will be from a telephone number different from the telephone number of the predetermined report destination. For example, after the predetermined report destination receives the automatic report 1002, a contact may be sent from that report destination to the mobile terminal 1 of user U1 from another system linked to that report destination. To be able to handle such cases, the mobile terminal 1 may store, for example, a correspondence table in advance. The mobile terminal 1 stores correspondence information regarding information such as telephone numbers related to various report destinations and callers in the correspondence table. When the mobile terminal 1 receives a contact from a third party (any caller), it refers to and searches the correspondence table to determine the correspondence relationship between the report destination and the automatic report 1002.
[0121] As another example of processing, when the mobile terminal 1 receives a call from a third party (any caller), it may search for information on the Internet (communication network 9), such as web information, and determine whether the telephone number of the caller who received the call (a number different from the number of the specified report destination) is a telephone number related to the specified report destination.
[0122] If the call is not from the report destination in step S802 (N), in step S811, the mobile terminal 1 checks, based on the correspondence table or the like, whether the call from the third party is from an entity (caller) associated with the specified report destination, i.e., an entity that can respond to the automatic report 1002, such as an emergency call. If the call is from an associated source in step S811 (Y), the process proceeds to step S803. If the call is not from an associated source in step S811 (N), the process proceeds to step S812.
[0123] In step S812, the mobile terminal 1 performs normal processing, i.e., processing using normal telephone functions. In response to the call from the third party, the mobile terminal 1 performs processing such as calling the user U1 (no response) or performing a set automatic response processing. The user U1 may answer the call himself.
[0124] If user U1 responds to the contact by himself (step S813-Y), the mobile terminal 1 determines that user U1 has returned to the normal state, and stops additional monitoring in step S814. Also, in step S815, the mobile terminal 1 again outputs an alert (at least a visual or audio message) to user U1 to the effect that automatic notification 1002 has been sent.
[0125] [Processing Flow (1-4)] FIG. 9 shows processing flow (1-4). The flow in FIG. 9 is a flow that continues when step S705 of flow (1-2) in FIG. 7 determines that the abnormal state continues and the normal state has not been restored (N). In step S901, the mobile terminal 1 continues additional monitoring after automatic notification 1002. This additional monitoring period after the aforementioned third period is set as the fourth period. In step S902, the mobile terminal 1 performs processing depending on whether or not there is a callback from the report destination. This processing is the same as the processing in flow (1-3) in FIG. 8. If there is no callback from the report destination within the fourth period, the process proceeds to step S903.
[0126] In step S903, the mobile terminal 1 again transmits the same automatic report 1002 as a second automatic report to the previous report destination. The mobile terminal 1 also includes in this second automatic report 1002 information indicating that this is a repeated automatic report (second or later) and information indicating the relationship with the first automatic report 1002. The second automatic report 1002 of step S903 may be similarly repeated depending on the elapsed time.
[0127] Furthermore, in step S904, the mobile terminal 1 also sends an automatic report 1002 to a report destination other than the predetermined report destination in step S607. The predetermined report destination in step S607 is set as the first report destination, and the automatic report 1002 to the first report destination is set as the first automatic report 1002. The predetermined report destination in step S904 is set as the second report destination, and the automatic report to the second report destination is set as the second automatic report 1005.
[0128] The mobile terminal 1 is set in advance for a plurality of report destinations, including the first report destination and the second report destination. The mobile terminal 1 is set in advance for a priority order of reports for the plurality of report destinations. When the second automatic report 1005 is sent to the second report destination, the mobile terminal 1 treats this second automatic report 1005 as a control target, similar to the first automatic report 1002, and similarly issues a release notice 1003 (second release notice) for the second automatic report 1005 as necessary. The second report destination is an entity that can take action, such as rescue.
[0129] The second notification destination may also be any predetermined contact such as user U3, a family member or acquaintance of user U1 in Fig. 1. In this case, the mobile terminal 1 sends a notification 1011 equivalent to the second automatic notification 1005 to, for example, the mobile terminal 4001 of user U3, a family member or acquaintance in Fig. 1. The notification 1011 includes information that user U1 is in a state 1001 such as an abnormality, or that the automatic notification 1002 has already been sent.
[0130] In step S905, the mobile terminal 1 uses short-range communication to send a notification 1012 (in other words, an emergency call) to the surrounding device 4002 ( FIG. 1 ). This notification 1012 is a notification to inform any surrounding device 4002 or a surrounding third party's mobile terminal 4001 that the mobile terminal 1 has already sent the automatic report 1002 and that a state such as an abnormality of the user U1 continues.
[0131] Note that the short-range communication of the mobile terminal 1 has already been turned on when the additional monitoring is started in step S702 described above, and therefore the mobile terminal 1 can immediately transmit the notification 1012 via short-range communication in step S905. However, the present invention is not limited to this, and the short-range communication may be turned on after step S905.
[0132] In step S906, the mobile terminal 1 outputs an alert from its own device. This alert output is an output to notify not only the user U1 but also those around the mobile terminal 1 of a state such as an abnormality of the user U1. This alert is output as an emergency voice or an alert sound using, for example, the speaker / voice output unit 318 in FIG. 3. In addition, the volume of the alert sound (for example, a beep) at this time is adjusted so that it is easily heard by those around.
[0133] A plurality of steps such as steps S903 to S906 may be executed simultaneously in parallel, may be executed in a different order, or may be executed only in part.
[0134] After executing at least a portion of the processing, such as step S906, the mobile terminal 1 transitions to a battery save mode (in other words, a power-saving mode). This is to reduce the power consumption of the mobile terminal 1 in anticipation of future rescue-related processing. The time since entering this battery save mode is designated as the fifth hour. In this battery save mode, operations other than those related to the automatic reporting function F1 and the release notification function F2 are essentially turned off. For example, the screen display is turned off or the display brightness is reduced. For example, cellular communication (mobile communication) is left on. For example, the display and communication are turned off except for specific timings required for alert output, etc. For example, with regard to sensing by various sensors, only motion detection is turned on, and voice input, etc. are turned off.
[0135] During the fifth time period in battery save mode, the mobile terminal 1 periodically outputs an alert at a predetermined time interval (see FIG. 14, which will be described later). This alert output may be the same as the alert output in step S906, or a simple alert output with low power consumption. This periodic processing is not limited to alert output, and may include issuing another automatic notification 1002, similar to step S903, or notifying surrounding devices, similar to step S905.
[0136] The mobile terminal 1 appropriately checks the remaining battery power of its own device and adjusts the range and time interval of the fifth time period for performing periodic processing such as the above-mentioned alert output according to the remaining power. If the remaining power is high, the mobile terminal 1 lengthens the fifth time period and shortens the time interval, and if the remaining power is low, the mobile terminal 1 shortens the fifth time period and lengthens the time interval. Furthermore, the mobile terminal 1 may gradually lengthen the time interval for alert output according to the remaining power.
[0137] Furthermore, when the mobile terminal 1 detects a surrounding device or receives a response from a surrounding device as a result of the short-range communication in step S905, in other words, when it recognizes the presence of another device, the mobile terminal 1 may shorten the time interval between alert outputs by a certain period of time. In other words, the mobile terminal 1 may repeat alert output between the recognized surrounding device and the mobile terminal 1 at a shortened time interval.
[0138] In step S909, the portable terminal 1 continues the above process until the battery power runs out.
[0139] The above flow has been described for one automatic notification 1002, but the same processing can be applied when the automatic notification 1002 occurs for the second or subsequent times.
[0140] [Screen Display Example] Fig. 10 shows an example of a screen display on the display of the mobile terminal 1. Fig. 10 (A) shows an example of a display when the automatic report 1002 is sent by the automatic report function F1. This screen has an SOS button g1 for sending the automatic report 1002 to a report destination (e.g., 119) and a cancel button g2 for canceling the sending of the automatic report 1002. The mobile terminal 1 displays this screen, for example, along with a countdown, and if a button is pressed by user U1 during the countdown time, performs processing according to the pressed button. The mobile terminal 1 automatically sends the automatic report 1002 after the countdown time has elapsed.
[0141] 10B shows an example of a display when the release notification function F2 sends a release notification 1003. This screen has an indicator g3 indicating that the automatic report 1002 has been sent, and a release button g4 for generating the release notification 1003. The mobile terminal 1 may display this screen when it determines that the condition of the user U1 has improved, and send the release notification 1003 when the user U1 presses the release button g4.
[0142] 11 shows other examples of the screen. (A) of Fig. 11 is an example of the display after sending the release notification 1003. This screen has a display g5 indicating that the release notification 1003 has been sent, in addition to a display g3 indicating that the automatic report 1002 has been sent.
[0143] 11B is an example screen in a modified example. This screen has an indicator g5 indicating that the release notification 1003 has already been sent, as well as an SOS button g6 for issuing another automatic notification 1002. For example, the automatic notification 1002 is issued after the user U1 falls, and then the release notification 1003 is issued in response to a determination that the user U1 has returned to a normal state. Furthermore, the mobile terminal 1 may subsequently display the SOS button g6 if it determines, based on sensing, that the user U1 has entered a state 1001 such as an abnormality.
[0144] Figure 12 shows other screen examples. Figure 12 (A) is an example of a screen displayed when an incoming call is received from a caller associated with the report destination during step S802 in Figure 8 described above. This screen includes a display g3 indicating that the automatic report 1002 has been sent, and a display g7 indicating that a call has been received from a caller associated with the report destination as a contact from a third party. Display g7 includes, for example, the caller's telephone number and an indication that the caller's telephone number is the number of a caller associated with the report destination.
[0145] Fig. 12B is an example of a screen displayed after user U1 answers a call from a call source related to the report destination in step S802 of Fig. 8. This screen has a highlight display g8 indicating that the automatic report 1002 has been sent, and a display g9 of the history of responses to telephone numbers from call sources related to the report destination.
[0146] [Situation Determination by Release Notification Function] Figure 13 is a supplementary explanatory diagram illustrating an example of the determination of user U1's status 1001 by the release notification function F2. The determination of user U1's status by the release notification function F2 may use a different processing algorithm than the determination of user U1's status by the automatic reporting function F1. For example, the determination of abnormality or other status 1001 by the automatic reporting function F1 involves comparing motion characteristics before and after an impact such as a fall. In contrast, the determination of user U1's status during additional monitoring by the release notification function F2 involves determining changes in motion characteristics on a time axis in addition to the motion characteristics at the time (second time) after the impact such as a fall.
[0147] In FIG. 13 , the horizontal axis represents time. For example, at time t1, user U1 carrying the mobile device 1 is walking and in a normal state. At time t2, user U1 falls, etc., and the mobile device 1 senses the impact caused by the fall, etc. During a first time T1 up to time t2, user U1 has a first motion characteristic based on the sensing. During a second time T2 after time t2, user U1 has a second motion characteristic based on the sensing. For example, at time t3, user U1 is lying on the ground. The automatic reporting function F1 of the mobile device 1 determines that user U1 is in a state 1001, such as an abnormality, based on a comparison between the first motion characteristic and the second motion characteristic. Then, the mobile device 1 issues an automatic report 1002.
[0148] Thereafter, at a third time T3 after time t3 corresponding to the automatic report 1002, additional monitoring is performed by the release notification function F2. For example, at time t4, user U1 stands up and starts walking. At the third time T3, based on sensing, user U1 has a third behavior characteristic. The release notification function F2 of the mobile terminal 1 determines whether user U1 has returned / improved from the abnormal state 1001 to a normal state based on a comparison between the second behavior characteristic at the second time T2 and the third behavior characteristic at the third time T3. If it is determined that user U1 has returned to a normal state, the mobile terminal 1 transmits a release notification 1003.
[0149] Also, as shown below at time t4, user U1 may input into mobile terminal 1 by voice that there is no problem or that the report should be canceled, and mobile terminal 1 may recognize the input voice, recognize user U1 as an individual from his / her voiceprint, and determine whether automatic report 1002 should be canceled based on words or the like resulting from the voice recognition, and send a cancellation notification 1003.
[0150] [Example of Control in Battery Save Mode] FIG. 14 is a supplementary explanatory diagram illustrating an example of adjustment and control according to the remaining battery level of the mobile terminal 1 in steps S907 and S908 of FIG. 9 . The horizontal axis in FIG. 14 represents time. (A) in FIG. 14 illustrates a case where, at time tA, user U1 enters an abnormality state 1001, generating an automatic notification 1002, and the remaining battery level is, for example, 75%. At time tB, the mobile terminal 1 transitions to battery save mode (step S907). The mobile terminal 1 adjusts the time interval for periodic alert output, etc., according to the remaining battery level. At time tC1, the mobile terminal 1 performs at least one of outputting an alert to the surrounding area, notifying surrounding devices, or issuing a second automatic notification 1002. After a time interval TC1 has elapsed since time tC1, at time tC2, the mobile terminal 1 similarly performs at least one of outputting an alert to the surrounding area, notifying surrounding devices, or issuing a second automatic notification 1002. Thereafter, similar processing is performed periodically at time intervals TC1.
[0151] FIG. 14B illustrates a case where, at time tA, user U1 enters an abnormality state 1001, generating an automatic notification 1002, and the remaining battery level is, for example, 30%. At time tB, the mobile terminal 1 transitions to battery save mode (step S907). The mobile terminal 1 adjusts the time interval for periodic alert output, etc., depending on the remaining battery level. In (B), the remaining battery level is lower than in (A), so the time interval TC2 is set longer than the time interval TC1. At time tC1, the mobile terminal 1 performs at least one of outputting an alert to the surroundings, notifying surrounding devices, or issuing another automatic notification 1002. After time interval TC2 has elapsed since time tC1, at time tC2, the mobile terminal 1 performs at least one of outputting an alert to the surroundings, notifying surrounding devices, or issuing another automatic notification 1002. Thereafter, periodic processing is similarly performed at each time interval TC2.
[0152] Furthermore, the mobile terminal 1 may determine the time range (from start to end) for performing the periodic processing at the fifth hour based on the remaining battery level. Furthermore, the mobile terminal 1 may determine when to transition to the battery save mode based on the remaining battery level after transmitting the automatic notification 1002. For example, the mobile terminal 1 may transition to the battery save mode when the remaining battery level falls below a predetermined level.
[0153] Furthermore, the mobile terminal 1 may select, depending on the remaining battery level, whether to perform the periodic processing by only outputting an alert to the surroundings, by only notifying surrounding devices via short-range communication, by only making another automatic report 1002, or by performing two or more of these. For example, when the remaining battery level is equal to or greater than a first threshold, three or two processes may be performed, when the remaining battery level is less than the first threshold, only one process may be performed, and when the remaining battery level is less than a second threshold that is smaller than the first threshold, all processes may be stopped and only a call back from the report destination may be waited for.
[0154] [Effects of the embodiment] According to the above-described first embodiment, it is possible to appropriately respond to cases such as a false report with respect to the automatic report function F1 of the mobile terminal 1. After the automatic report function F1 of the mobile terminal 1 generates the automatic report 1002 based on the state 1001 of the user U1, the release notification function F2 can automatically issue the release notification 1003 according to the situation of the user U1.
[0155] [Modification] In the first embodiment, the cancellation notification 1003 is automatically transmitted according to the judgment of the mobile terminal 1, even without any operational input from the user U1. However, this is not limited to this, and the cancellation may be transmitted via an operational input from the user U1. When the mobile terminal 1 determines that the automatic notification 1002 should be canceled, it outputs to the user U1 (for example, by displaying on the screen or by voice) that the cancellation will be transmitted before sending the cancellation notification 1003 to the notification destination. For example, as in the example of FIG. 10B , this may be transmitted via the operation of pressing a cancellation button g4 on the screen. When the user U1 performs a confirmation / affirmative operation, for example, pressing the cancellation button g4, the mobile terminal 1 transmits the cancellation notification 1003 to the notification destination. If the user U1 does not perform the affirmative operation, the mobile terminal 1 does not transmit the cancellation notification 1003.
[0156] The user can set detailed functions related to the release notification function F2 in the user settings related to the application of the release notification function F2 of the mobile terminal 1. For example, the user can select whether the release notification 1003 is to be sent automatically or via the operation of pressing the release button g4.
[0157] As a variant example, when various derivative reports or notifications (e.g., contact 1011 or notification 1012) are made in addition to automatic report 1002, release notification 1003 may be similarly applied to these derivative reports, etc.
[0158] Although the embodiments of the present disclosure have been specifically described above, they are not limited to the above-described embodiments and can be modified in various ways without departing from the spirit of the present disclosure. Except for essential components, components can be added, deleted, or replaced in each embodiment. Unless otherwise specified, each component may be singular or plural. A combination of each embodiment and its variations is also possible.
[0159] 1...Mobile terminal, 1A...Smartphone, 1B...Smartwatch, 2...System to report to, 3...Operator's system, 9...Communication network, F1...Automatic reporting function, F2...Cancellation notification function, 1001...Emergency / abnormal / problem status, 1002...Automatic reporting, 1003...Cancellation notification, 1004...Related information, U1...User, U2...Responder.
Claims
1. A mobile terminal having an automatic reporting function, wherein the automatic reporting function automatically makes a first automatic report to a first reporting destination, which is a predetermined reporting destination, when it is determined that a user carrying the mobile terminal is in a first state, which is an emergency, abnormality, or problem state, depending on the state of the mobile terminal, and when the automatic report is made, the mobile terminal monitors the state of the mobile terminal during the time following the automatic report, determines whether the first state has been resolved or whether the first report was a false report, and when it determines that the first state has been resolved or that the first report was a false report, makes a release notification to the first reporting destination to inform the user that the first report has been released.
2. A mobile terminal as described in claim 1, wherein the release notification is accompanied by at least one of the following information: date and time information regarding the first notification, location information of the mobile terminal, telephone number information, unique information, name information of the user, and content information of the first notification, as related information for associating the release notification with the first notification and enabling the first notification destination to identify the first notification.
3. A mobile terminal as claimed in claim 1, wherein in monitoring after the first report, the number of sensing parameters is increased compared to monitoring before the first report by the automatic report function, and one of the parameters to be increased is determination of the user's condition by voice input and voice recognition.
4. A mobile terminal as described in claim 1, wherein when the release notification has been sent, the mobile terminal at least displays or outputs audibly at least one of the following: that the first condition of the user has been resolved, that the report has been determined to have been a false report, or that the release notification regarding the first report has been sent to the first report destination.
5. A mobile terminal as claimed in claim 1, wherein, when an incoming call is received from a number different from the number of the first call destination during the monitoring period following the first call, the number that received the call is searched to see if it is related to the number of the first call destination, and the search results are output from the mobile terminal at least as a display or audio.
6. A mobile terminal as claimed in claim 5, wherein, when the number that received the call is a number related to the number of the first report destination and when the user is able to respond to the call, the monitoring is stopped and the mobile terminal outputs at least a display or a sound indicating that the first report has been made.
7. A mobile terminal according to claim 1, wherein if it is determined that the first condition has not been resolved after the first report, the mobile terminal again makes the automatic report to the first report destination.
8. A mobile terminal as claimed in claim 1, wherein if it is determined that the first condition has not been resolved after the first report, a pre-set contact point different from the first report destination is automatically contacted to inform the user that the user is in the first condition.
9. A mobile terminal as claimed in claim 1, wherein if it is determined that the first state has not been resolved after the first report, the mobile terminal automatically notifies devices in the vicinity of the mobile terminal, based on short-range communication, that the user is in the first state.
10. A mobile terminal according to claim 1, wherein if it is determined that the first condition has not been resolved after the time period following the first report, the mobile terminal outputs at least a voice alert to those in the vicinity.
11. A mobile terminal as claimed in claim 1, wherein if it is determined that the first condition has not been resolved after the time period following the first notification, the mobile terminal is switched to a battery save mode in which operations other than operations related to the automatic notification are refrained from to conserve the battery.
12. A mobile terminal as claimed in claim 11, wherein in the battery save mode, as a periodic process, the mobile terminal outputs at least an audio alert to those in the vicinity, or automatically notifies devices in the vicinity of the mobile terminal that the user is in the first state based on short-range communication, or again makes the automatic report to the first report destination.
13. A portable terminal according to claim 12, wherein in said battery save mode, the time interval for periodically repeating said automatic report or other type of communication is controlled so as to be changed according to the remaining capacity of said battery.
14. A method for canceling a report in a mobile terminal having an automatic reporting function, wherein the automatic reporting function is a function for automatically making a first automatic report to a first reporting destination, which is a predetermined reporting destination, when it is determined that a user carrying the mobile terminal is in a first state, which is an emergency, abnormality, or problem state, according to the state of the mobile terminal, and the method comprises: a step of the mobile terminal making the automatic report; and a step of the mobile terminal, when the automatic report is made, monitoring the state of the mobile terminal during the time following the automatic report, determining whether the first state has been resolved or whether the first report was a false report, and if it is determined that the first state has been resolved or that the first report was a false report, sending a release notification to the first reporting destination to communicate the release of the first report.
Citation Information
Patent Citations
Notifying device for vehicle in emergency
JP2001256581A
Emergency rescue supporting system, portable terminal with emergency rescue function, wireless terminal for receiving emergency rescue information and emergency rescue supporting method
JP2003109160A
Life protecting system and method
JP2005196812A
Safety confirmation server, safety confirmation method and safety confirmation program
JP2015207965A
Method and system to improve accuracy of fall detection using multi-sensor fusion
US20220101710A1
