Emergency detection and notification system

[0001] The present application is a Continuation-In-Part (“CIP”) of U.S. patent application Ser. No. 11/204/482, now U.S. Pat. No. 7,565,132, filed Aug. 17, 2005.

[0002] This invention is directed generally to emergency detection and notification systems and more specifically to a portable device that monitors health signs and that automatically calls a phone number or sends an email when it detects a condition that requires medical attention.

[0003] Existing emergency detection and notification systems comprise a trigger device and a base station connected to a telephone jack that automatically dials an emergency service when a person activates the trigger device. These devices are costly and require a fixed phone line. These devices do not call automatically on detection of a condition that requires attention. Other emergency detection and notification systems use sensors—such as a pulse oximeter—and communicate with a base station using BLUETOOTH. The base station is capable of detecting a health condition and calling a number. This system is cumbersome and not easily portable as it is composed of two parts. Other emergency detection and notification systems use wearable devices to detect emergency conditions, and automatically call support lines. These systems do not interact with the user in a meaningful way, and therefore provide inadequate service and generate frequent false positives.

There is a need for an intelligent emergency detection and notification system that is convenient, portable and reliable.

[0004] A wearable apparatus comprising: a single short wireless transceiver means wherein said single short wireless transceiver establishes a connection with at least one remote terminal, wherein upon detection of a connection drop, said wearable apparatus can issue an audible alarm;

a memory for storing at least one threshold and, at least one emergency phone number and, at least one emergency message;

[0005] a speaker, at least one battery, a means for collecting sensor information, wherein the volume of said wearable apparatus is less than 150 cm3, wherein the emitted energy of said wearable apparatus is less than 100 milliwatts, wherein said wearable apparatus does not include any cellular network transceiver;
wherein upon detection of sensor information not matching said at least one threshold, issuing an audible request through said speaker, waiting for a response selected from the group consisting of: a button push, an voice reply, a motion;
wherein if a valid response is not received within a predetermined period of time, instructing said at least one remote terminal to dial at least one phone number selected from said at least one emergency phone number, wherein upon detection of at a line picked up, sending voice messages corresponding to said at least one emergency message, sending voice corresponding to said sensor information.

[0006] A method comprising: using a wearable apparatus, wherein the wearable apparatus has a volumes less than 150 cm3, wherein the wearable apparatus emits less than 100 milliwatts, wherein the wearable apparatus does not include any cellular network transceiver;

updating the wearable apparatus with information selected from the group consisting of: at least one threshold, at least one emergency phone number, at least one emergency message;

configuring the wearable apparatus to connect with at least one remote terminal using a short wireless transceiver, wherein upon detection of a connection drop, the wearable apparatus can issue an audible alarm;

wherein upon detection of sensor output not matching the at least one threshold, issuing an audible request, waiting for a user response selected from the group consisting of: a button push, an oral reply, a motion;

[0007] wherein if a response is not received within a predetermined period of time, instructing said at least one remote terminal to dial at least one phone number selected from said at least one emergency phone number, wherein upon detection of at a line picked up, sending voice corresponding to said sensor output to said at least one remote terminal.

[0008] A method comprising: using a wearable apparatus, collecting sensor information from sensor means wherein said sensor means are selected from the group consisting of: onboard sensor means, remote wearable sensor means;

wherein the wearable apparatus emits less than 100 milliwatts, wherein the wearable apparatus connects with at least one remote terminal using a short wireless transceiver;

wherein upon detection of a connection drop, the wearable apparatus can issue an audible alarm message;

wherein upon detection of low battery, the wearable apparatus can issue an audible alarm message;

wherein upon detection of sensor information not matching user defined thresholds, issuing an audible request, waiting for a user response selected from the group consisting of: a button push, an oral reply, a motion;

wherein if the user response is not received within a predetermined period of time,

instructing said at least one remote terminal to dial at least one phone number;

wherein upon detection of at a line picked up, sending voice corresponding to said sensor information to at least one remote terminal.

[0021] Similar reference numerals are used in different figures to denote similar components.

[0022] FIG. 1A is schematic of an emergency detection and notification system 10 comprising a processor 11, switches 12, battery 13, antenna 14, communication center 15, BLUETOOTH transceiver 161, sensors 17, sensors interface 171, memory 18 and attachment system 19.

[0023] Switches 12 can be any type of buttons, switches, remote sensor switches, touch sensor switches, contact sensor switches, voice activated switches, motion activated switches, remote control activated switches. Switches 12 are used to receive and capture user input after issuing a message through communication center 15.

[0024] For example, upon detection of an event, communication center 15 issues an audible message “A chock was detected. Do you want to call for assistance? Yes or No?”. The user may answer with a “yes” or “no” command to switches 12, or may press a “yes” switch 12 or a “no” switch 12.

[0025] Battery 13 provides power to some of the components of emergency detection and notification system 10. It will be understood that battery 13 may be a fuel cell, nickel-cadmium, lithium, alkaline or nickel-hydride battery or any other portable source of electric power. Battery 13 can also be replaced with photovoltaic cells.

When emergency detection and notification system 10 is not in operation it remains in a dormant state (“sleep-mode”) to conserve the energy of battery 13.

[0026] Antenna 14 can be any type of antenna including patch antennas and dipole antennas.

[0027] Communication center 15 can be any type of visual, audio, tactile or mechanical user interface means capable of conveying information to the user. An example of visual means is an LED, or any visual information display device. Audio means can be any audio device such as a speaker, a buzzer, a Piezo buzzer. Tactile means can be any tactile sensor such as a heat-generating device. An example of a mechanical means is a vibrator.

[0028] BLUETOOTH transceiver 161 is any type of short range transceiver or a combination of short range transmitter and short range receiver. In a preferred embodiment, BLUETOOTH transceiver 161 used to communicate with a mobile phone, computer or BLUETOOTH sensors. In case of emergency, emergency detection and notification system 10 commands the mobile phone to dial a phone number through BLUETOOTH Hands Free Profile (HFP).

BLUETOOTH transceiver 161 is a low radiation transceiver with emitted energy of less and 100 milliwatt. In a preferred embodiment, the emitted energy is less than 10 milliwatt. In another preferred embodiment, the emitted energy is less than 1 milliwatt.

BLUETOOTH transceiver 161 can discover other compatible transceivers in the vicinity. BLUETOOTH transceiver 161 can establish a temporary two-way connection or a piconet network with other devices equipped with compatible transceivers.

[0029] Sensors 17 can be simple arrangements to collect data such as an infrared detector, a colour detector, a humidity detector, a UV rays detector, a chemical sensor, a NIR sensor.

Sensors 17 can comprise a temperature reader, a blood pressure reader, a heart rate reader, an insulin reader, a prosthesis data reader, a breath analyzer, a scale, a pulse oximeter, a CO2 detector, a carbon monoxide sensor, blood sugar content.

Sensors 17 can comprise a vibration detector, a water detector, an accelerometer, a gyro, a tilt sensor, a motion detector, a microphone.

Sensors 17 can comprise an eye sensor, a cameras, a location sensor, a GPS. In a preferred embodiment, zero or more sensors 17 are onboard the emergency detection and notification system 10.

[0030] Sensors interface 171 enables the emergency detection and notification system 10 communicate with remote sensors through BLUETOOTH, WIBREE, ANT, ANT+ or ZIGBEE or any other short wireless low radiation communication protocol.

Zero or more onboard Sensors 17 and zero or more remote sensors generate output signals that are indicative of sensed conditions. Processor 11 compares the output signals to thresholds.

[0031] Memory 18 is used for storing at least one threshold and, at least one emergency phone number and, at least one emergency message.

[0032] Memory 18 can also store data thresholds such as acceptable temperature, acceptable blood pressure, acceptable heart rate, acceptable insulin level, acceptable pulse, operation hours, operation days, alert messages, recordings, client name, greetings, health conditions, blood type, medications, buzzer type, buzzer volume, buzzer duration, alarm type, and voice messages and recordings.
Memory 18 can be any memory with a size less than 16 Mega bits.
In another embodiment, memory 18 is less than 100 Mega bits.
In another embodiment, memory 18 is less than 1000 Mega bits.
In another preferred embodiment, power consumption is less than 1 mA when the system is in standby.
In another preferred embodiment, power consumption is less than 10 mA when the system is in standby.
In another preferred embodiment, power consumption is less than 100 mA.

[0033] Emergency detection and notification system 10 has an attachment system 19 that can be a bracelet, a watch, a pager, a wearable blood pressure monitor, a belt, a device that attaches around the wrist, a device that attaches around the ankle, a device that attaches around the waist, a device that attaches on the chest or any other wearable form. The attachment system may comprise a clip, a ring, a belt, a VELCRO, a keychain, a fastening mechanism or a safety lock to prevent unwanted removal.

[0034] In a preferred embodiment, the volume of the emergency detection and notification system is less than 150 cm3, and its weight is less than 100 grams. It comprises one or more short wireless transceivers, and does not comprise any cellular network transceiver.

[0035] FIG. 1B is schematic of an emergency detection and notification system 10 comprising a processor 11, switches 12, battery 13, antenna 14, communication center 15, WIFI transceiver 162, sensors 17, sensors interface 171, memory 18 and attachment system 19.

[0036] In another preferred embodiment, WIFI transceiver 162 allows to connect to an access point and to send commands to a VOIP server to dial a phone number.

WIFI transceiver 162 is a low radiation transceiver with emitted energy of less and 100 milliwatt. In a preferred embodiment, the emitted energy is less than 10 milliwatt.

WIFI transceiver 162 can discover other compatible transceivers in the vicinity and establish a temporary two-way connection with other devices equipped with compatible transceivers.

[0037] Referring now to FIG. 2A, in one embodiment, emergency detection and notification system 10 comprises a processor 11 interconnected with switches 12, battery 13, communication center 15, BLUETOOTH transceiver 161, sensors 17, sensors interface 171, and memory 18.

[0038] Referring now to FIG. 2B, in one embodiment, emergency detection and notification system 10 comprises a processor 11 interconnected with switches 12, battery 13, communication center 15, WIFI transceiver 162, sensors 17, sensors interface 171, and memory 18.

[0039] Turning now to FIG. 3, the flowchart illustrates the operation of an emergency detection and notification system 10 using BLUETOOTH. In step 30 the emergency detection and notification system establishes a BLUETOOTH connection with a wireless communication device. The emergency detection and notification system is previously paired with the wireless communication device, and the PIN codes are previously entered (if needed). If a connection cannot be established, communication center 15 issues an audible alarm message. Audible alarm message can be a buzzer, a ring, or a voice message.

[0040] In step 31, sensors 17 collect sensor data from onboard sensors and remote wireless sensors and compare their outputs to user defined acceptable thresholds. The user defined acceptable thresholds are programmed by the user through a computer connected through a cable, an onboard keypad, a BLUETOOTH paired mobile phone, or a connected WIFI terminal.

[0041] In step 32, if sensor output is found outside the acceptable thresholds, an alarm condition is identified and the emergency detection and notification system 10 issues an audible request to the user through communication center 15 and waits for a user response for a predetermined period of time in step 33. For example, it may issue the following message:

[0042] “A chock was detected. Do you want to call for assistance? Yes or No?”

[0043] “A health condition was detected. Do you want to call for assistance? Yes or No?”

[0044] In an alternative embodiment, the emergency detection and notification system 10 issues a vibration or a visual indication to the user and waits for a response. In step 34, if a user response is not received within a predetermined period of time, it is assumed that the user is out of conscience.

[0045] In a preferred embodiment, a user response is a voice response. In another embodiment, the user response is a motion response such as pushing a button or waiving a hand.

[0046] The emergency detection and notification system 10 will command the connected mobile phone to call one or more emergency phone numbers stored in memory in step 35. The wireless communication device dials and establishes a cellular network communication with at least another communication device based on user parameters and user rules.
When a called line is picked up in step 36, the emergency detection and notification system 10 converts text messages, user messages and sensor output to speech in step 37 using text to speech conversion means such as a voice synthesizer.
For example, the emergency detection and notification system 10 can get GPS data from a GPS sensor, and convert it to speech: “the user position is Latitude is thirty eight degrees fifty minutes twenty two point zero eight three seven seven seconds north . . . ” corresponding to GPS reading of 38°53′22.08377″N . . . .
In another example, the emergency detection and notification system 10 says the name of the patient, the emergency condition, the state, and the sensor readings, “Mrs. Johnson has fallen. She is not responding to questions. The heart beat is one hundred . . . .”
The emergency detection and notification system 10 can also play some pre-recorded recordings.
The emergency detection and notification system 10 plays the function of a life monitor as it can detect if the user is out of conscience (for example is user got into an accident and is not responding, or if user got a heart attack and is not responding, or if the user had an epileptic seizure and is not responding, etc. . . . ), and can ensure that it automatically calls for help and provides assistance. Furthermore, the emergency detection and notification system 10 plays a health monitor function as it can monitor multiple health signs, and can inform the user and call for help should a health condition arise.
In step 38, the emergency detection and notification system 10 opens a full duplex between the user and the called party so that the called party can hear the user and can talk to him and help him.
In another embodiment, one channel is used for listening to the user.
On top of a voice message, the emergency detection and notification system 10 can also send text messages (SMS or email) to the called party containing sensor data. The voice and/or text messages may contain prerecord messages, data, data converted to voice through a synthesizer, or any combination of the above.
In another embodiment, the user responds to the message from the emergency detection and notification system 10 by issuing a voice response. The emergency detection and notification system 10 interprets the voice response and compares it to acceptable responses. The emergency detection and notification system 10 may do voice recognition. If the response is not understood or is not valid, the emergency detection and notification system 10 commands the connected phone to call one or more emergency phone numbers stored in memory.
If a response is understood or is valid, the emergency detection and notification system 10 performs actions according to pre-configured business rules.
In another embodiment, the user responds to the message from the emergency detection and notification system 10 by pressing one or more buttons. The emergency detection and notification system 10 interprets the buttons push and compares it to acceptable responses. If the response does not match with acceptable responses or is not valid, the emergency detection and notification system 10 commands the connected phone to call one or more emergency phone numbers stored in memory.
If a response is accepted, the emergency detection and notification system 10 performs actions according to pre-configured business rules.
In a preferred embodiment, the emergency detection and notification system 10 or the VOIP server generates electrical signals corresponding to sensor output or part of sensor output, and producing sounds on a remote terminal.

[0047] In a configuration step, the user defines what phone numbers to dial or SMS or what email addresses to email. The user also defines the rules and conditions under which those numbers/emails are dialed/emailed and what messages are sent. When those conditions occur, those phone numbers are emailed and those SMS/emails are sent.

[0048] Turning now to FIG. 4, the flowchart illustrates the operation of an emergency detection and notification system using VOIP.

[0049] In step 40 the emergency detection and notification system establishes a WIFI connection with a wireless communication device. The emergency detection and notification system is previously connected with the wireless communication device and the security keys are previously entered (if needed).
In a preferred embodiment, the emergency detection and notification system establishes a connection with a VOIP service. A VOIP service can be SKYPE service, OOVOO service, GOOGLE TALK service, or any other service capable of dialing a number and establishing a voice channel between a user using a wearable device and a dialed number.
In a preferred embodiment, the voice channel is a two way voice channel.
If a connection cannot be established, communication center 15 issues alarms.
In step 41, sensors 17 collect sensor data from onboard sensors and remote wireless sensors and compare their outputs to user defined acceptable thresholds. The user defined acceptable thresholds are programmed by the user through a computer connected through a cable, an onboard keypad, a BLUETOOTH paired mobile phone, or a connected WIFI terminal.
In step 42, if sensor output is found outside the acceptable thresholds, the emergency detection and notification system 10 issues an audible message to the user through communication center 15 and waits for a user response for a predetermined period of time.
If a user response is not received within a predetermined period of time, it is assumed that the user is out of conscience. The emergency detection and notification system 10 will command the VOIP service to call one or more emergency phone numbers stored in memory in step 45. The VOIP service dials and establishes a network communication with at least another communication device based on user parameters and user rules.
When a called line is picked up in step 46, the emergency detection and notification system 10 converts text messages and sensor output to speech in step 47.
The emergency detection and notification system 10 can also play some pre-recorded recordings.
In step 48, the emergency detection and notification system 10 opens a full duplex between the user and the called party so that the called party can hear the user, can talk to him and help him.
On top of a voice message, the emergency detection and notification system 10 can also send text messages (SMS or email) to the called party containing sensor data. The voice and/or text messages may contain prerecord messages, data, data converted to voice through a synthesizer, or any combination of the above.

[0050] Turning now to FIG. 5, the flowchart illustrates initiating the alarming function of the emergency detection and notification system.

In step 50, the emergency detection and notification system 10 tries to establish connection with a wireless communication device.

In a preferred embodiment, the connection is BLUETOOTH and the wireless communication device is a mobile phone.

In another embodiment, the connection is WIFI and the wireless communication device is a WIFI terminal.

[0051] The emergency detection and notification system 10 establishes a connection with a mobile phone or a VOIP service when it turns ON. The connection must be up at all times in order to guarantee that the emergency detection and notification system 10 is capable of calling a remote number should an alarm condition arise. In step 52, if a connection is not established, the emergency detection and notification system 10 goes to alarm mode in step 58.

[0052] In step 54, if the emergency detection and notification system 10 detects a connection failure such as a drop, a disconnect, or a failure to connect, it goes to alarm mode in step 58.

In step 56, if battery is low, the emergency detection and notification system 10 goes to alarm mode in step 58.

In step 58 alarm mode, the emergency detection and notification system 10 can issue vocal alarms as well as visual alarms and mechanical alarms.

An example of a vocal alarm is:

“Cannot connect to mobile phone—System cannot make calls”

“Cannot connect to WIFI—System cannot make calls”

“Battery is low—Please charge”

An example of visual alarm is LED or LED or OLED messaging.

An example of mechanical alarm is vibrator.

[0053] Turning now to FIG. 6, the flowchart illustrates pairing the emergency detection and notification system with a second device.

[0054] In step 60, the user sets the emergency detection and notification system 10 to discoverable mode. This can be done by pressing one or more buttons for a predetermined period of time, by issuing a voice command, or by programming the emergency detection and notification system using a programming cable.
In step 62, the user uses a second device equipped with BLUETOOTH, searches for compatible devices within proximity that are discoverable.
In step 64, the user can select an emergency detection and notification system 10 among the discovered devices for pairing.
The second device may request the user to enter a pairing PIN code which it will authenticate.
Once paired, the emergency detection and notification system 10 becomes non-discoverable. This provides security to the user as the terminal is not visible to other terminals.
Once paired, the emergency detection and notification system 10 can command the second wireless communication device to dial a number, to open voice lines, to relay a message, to play a recording, to issue speech, to receive speech, to hang up, etc.

[0055] In another preferred embodiment, the user connects the emergency detection and notification system 10 to a WIFI access point. The emergency detection and notification system 10 may send an authorization code to the WIFI access point for connection the very first time. After that, the emergency detection and notification system 10 can connect to the WIFI access point without entering an authorization code.

[0056] Once connected to a WIFI access point, the emergency detection and notification system 10 connects to a VOIP service such as SKYPE service, OOVOO service, GOOGLE TALK service, or any other service capable of dialing a number and establishing a voice channel between a user using a wearable device and a dialed number.
Once connected to a VOIP service, the emergency detection and notification system 10 can command the VOIP service to dial a number, to open voice lines, to relay a message, to play a recording, to issue speech, to convert text to speech, to convert a message to speech, to convert sensor output to speech, to receive speech, to hang up, to convert a text message to speech, etc.

[0057] Turning now to FIG. 7, the flowchart illustrates configuring the emergency detection and notification system wirelessly.

In step 70, the user goes to a user interface onboard an electronic device such as a mobile phone, a computer or an electronic device equipped with BLUETOOTH.

In step 72, a two-way wireless connection is established between the emergency detection and notification system 10 and the electronic device.

In step 74, the user enters configuration parameters and files in the user interface and commands the user interface to update the emergency detection and notification system 10.

In step 76, the configuration parameters are stored onboard the emergency detection and notification system 10.

[0058] Turning now to FIG. 8, the flowchart illustrates configuring the emergency detection and notification system through USB.

In step 80, the user connects the emergency detection and notification system 10 to an electronic device such as a mobile phone, a computer or an electronic device equipped with USB.

In step 82, the user enters configuration parameters and files in the user interface and commands the user interface to update the emergency detection and notification system 10.

The user interface allows the user to set configuration parameters or to change them. It may also display old configuration parameters.

[0059] Configuration parameters may include data thresholds such as acceptable temperature, acceptable blood pressure, acceptable heart rate, acceptable insulin level, acceptable pulse, operation hours, operation days, alert messages, recordings, client name, greetings, health conditions, blood type, medications, buzzer type, buzzer volume, buzzer duration, alarm type. The configuration parameters are stored onboard the emergency detection and notification system. The user interface program can be installed onboard the portable electronic device from the emergency detection and notification system 10, from a CD, or from other medium such as Internet.
In step 84, the configuration parameters are stored onboard the emergency detection and notification system 10.

[0060] Turning to FIG. 9, the flowchart illustrates updating the emergency detection and notification system 10.

[0061] In step 90, the emergency detection and notification system 10 is connected to a computer through a cable. This can be a USB, RS232 or any other cable means. In step 91, the user runs an application to update the emergency detection and notification system 10. The application can be a program running on the computer, a web service, a web plug-in, or any software running on a specialized device.
In step 92, the application collects update parameters, stack and application, and prepares update files. In a preferred embodiment, the application builds a DFU (device firmware upgrade) file. The application can sign the update files using a private key matching a public key stored on the emergency detection and notification system 10.
In step 93, the application tries to download the signed file to the emergency detection and notification system 10.
In step 94, a resident loader firmware onboard the emergency detection and notification system 10 checks if the private key of the signed file matches a public key stored onboard the system or device.
In step 95, if there is a match, the signed file is downloaded to the emergency detection and notification system 10 in step 96. When the new firmware executes, it may set the emergency detection and notification system 10 to discoverable to enable pairing with a new second device.
In step 97, the signed file is not downloaded.
It is noted that the loader firmware cannot be updated through the data port or through the cable. It can only be updated through access to PCB pins or PCB test points, such as SPI pins. This is so that the firmware onboard the emergency detection and notification system 10 cannot be tempered.

[0062] Numerous other modifications, variations, and adaptations may be made to the particular embodiment of the invention described above without departing from the scope of the invention, which is defined in the claims. Hence, while exemplary embodiments of the present invention have been set forth above, it is to be understood that the pioneer inventions disclosed herein may be constructed or used otherwise than as specifically described.