Telecommunications devices have advanced in a wide variety of ways. As telecommunications networks have improved and expanded functionality, telecommunications devices have followed. For example, wireless devices were developed to enable users to communicate text messages using short message service (SMS), instance messages (IM), and e-mails. Other technological functionality has also been developed for wireless communications devices.
Emergency situations can arise in a variety of ways at unpredictable times. Emergencies may come in the form of weather, crime, illness, natural disasters, man-made disasters, car accidents, and so forth. In an emergency situation, public safety answering points (PSAPs) have been established throughout the United States to answer emergency calls placed to “911.” Emergency operators at the PSAPs have been trained to answer emergency calls and provide emergency response by the most suitable emergency response team (e.g., firemen, police, ambulance, etc.) that the emergency situation warrants. Emergency calls, however, are not always possible depending upon the situation. Poor wireless network coverage, need to remain silent so as to avoid being discovered, being in a noisy environment, and having a low battery are a limited set of illustrative reasons as to why emergency voice calls are not always possible.
To overcome the problems of requesting emergency personnel support in situations where an emergency voice call is not possible or desirable, the principles of the present invention provide for emergency messaging to be provided to users of mobile devices and wireless communications devices. To simplify and expedite emergency messaging for users of a wireless communications devices, an emergency message button may be available on the wireless communications device so that, in response to selection of the emergency message button, an emergency message is generated and sent to a public safety answering point over a communications network. The emergency message button may be a hard-button or soft-button.
One embodiment of a wireless communications device according to the principles of the present invention includes a housing, a user interface configured to enable a user to type text messages for communication over a communications network, an emergency message button selectable by a user, and a processing unit in communication with the user interface and emergency message button. The processing unit may be configured to generate and send an emergency message to a public safety answering point in response to a user selecting the emergency message button.
One embodiment of a method for enabling a user to send an emergency message from a wireless communications device includes providing an emergency message button on the wireless communications device, and, in response to a user selecting the emergency message button, causing an emergency message to be generated and sent to a public safety answering point.
Illustrative embodiments of the present invention are described in detail below with reference to the attached drawing figures, which are incorporated by reference herein and wherein:
With regard to
In the event of an emergency, the user 102 may utilize the wireless communications device 104 to communicate an emergency message 112 over the network 108 to the PSAP 106. The emergency message 112 traditionally has been a telephone call, but in accordance with the principles of the present invention, the emergency message 112 may be a (i) text message using short message service (SMS), (ii) prerecorded message stored on the wireless communications device 104, (iii) instant message, or any other text or non-text message that may be initiated by the user 102 selecting an emergency message button 114 on the wireless communications device 104, as further described herein.
With regard to
In one embodiment, rather than a user simply having to activate the emergency message button 208 to initiate an emergency message, the wireless communications device 200a may be configured to have the user activate the emergency message button 208 and talk button 207, or any other button, substantially simultaneously to initiate the emergency message. By having the user press both buttons 208 and 207, the ability for the user to inadvertently send an emergency text message to a PSAP is minimal. In an alternative embodiment, both buttons can be activated at different times, such as pressing the emergency message button 208 first and then the talk button 207 to confirm desire to send the emergency message.
One or more illumination devices 209a-209n (collectively 209) may be positioned on the wireless communications device 200a. In one embodiment, one or more of the illumination devices 209 are LEDs. Another illumination device is the electronic display 206. One of the illumination devices 209a may be positioned to illuminate the emergency message button in response to an emergency message being communicated. Other illumination devices 209 may be illuminated, strobed or otherwise used to indicate successfully communicating an emergency message.
With regard to
With regard to
With regard to
With regard to
With regard to
With regard to
A generate emergency message module 404 may be configured to generate (i) a text message for use in sending to a PSAP, (ii) prerecorded voice message, or (iii) speech synthesized voice message. If an emergency text message is generated, the emergency text message may include information about the user and geographical location of the user, including “send to” address, name, home address, telephone number, geographic coordinates (e.g., global positioning system (GPS) coordinates), and other information that can be fit into a text message. If the emergency message is a prerecorded voice message, then the emergency message may be stored in memory of the wireless communications device and played to an operator at a PSAP. The prerecorded voice message may be recorded by the user to provide the PSAP operator with any information that could be helpful to police in the event of an emergency, such as the name of a known stalker. If the emergency message is a speech synthesized message, then the wireless communications device may store data in memory for use in generating an emergency message by a speech synthesizer executed by the wireless communications device that converts the stored data into synthesized speech for audio presentation to an operator at a PSAP. Both the pre-recorded and speech synthesized messages may have information, such as GPS coordinates, added at the time of a call to a PSAP by the wireless communications device in response to the user activating the emergency message button.
A send emergency message module 406 may be configured to send the generated emergency message to a PSAP. If the emergency message is a prerecorded message or a speech synthesized message, then the send emergency message module 406 may automatically call 911 or send a text message to an address (e.g., “emergency.org”) for routing to a local PSAP. It should be understood that non-preformatted messages as understood in the art, may be sent by a user to a network address for routing to a PSAP.
A configure illumination/audio device(s) in emergency mode module 408 may be configured to set at least one component into an emergency mode, such as by reducing or eliminating illumination of an electronic display and other illumination devices (e.g., LEDs) of a wireless communications device and significantly lower volume of the wireless communications device (e.g., reduce by 60 dB) of audio device(s) of the wireless communications device. By reducing or turning off illumination and audio devices (i.e., setting the wireless communications device in an emergency mode), a user who requests an emergency message to be sent to a PSAP may be protected in the event that the user is hiding from an intruder who might otherwise discover the user's presence should the wireless device be illuminated or produce an audible sound. In the event that the user desires to turn sound and illumination device(s) back on, the configure illumination/audio device(s) in emergency mode module 408 may turn on the illumination and audio device(s) on in response to the user selecting a button, such as the user-on button or otherwise.
A generate acknowledgement notification signal module 410 may be configured to notify the user that an emergency message has been sent to a PSAP by generating an acknowledgement indicator or acknowledgement notification signal, such as a visual signal. The acknowledgement indicator may be a low-level light by illuminating an LED to light the emergency message button, for example. In an alternative embodiment, the acknowledgement notification signal may be white text or graphics displayed a black background on an electronic display of the wireless communications device, where the white text or graphics indicates that the emergency message was communicated to the PSAP (e.g., “emergency message sent”). In one embodiment, if a successful receipt is received from the PSAP, in addition to notifying the user that the emergency message was communicated, a receipt acknowledgement notification signal may cause an illumination device, such as an LED or electronic display, to change colors, flash a different number of times than the acknowledgement notification signal, or any other indicator to notify the user that the PSAP received the message and help is being sent.
An abbreviated emergency startup sequence module 412 may be configured to start-up or turn on the wireless communications device in an abbreviated manner if an emergency message is requested to be sent while the wireless communications device is turned off. The wireless communications device may execute the abbreviated emergency start-up sequence module 412 to turn on a limited number of components, such as a processing unit, I/O unit, memory, wireless transmission devices, and other devices without turning on an electronic display or other illumination devices to limit the amount of power consumed by the wireless communications device and to quickly generate and communicate an emergency message.
A standard power-up sequence module 414 may be configured to power-up the wireless communications device in a standard or normal manner. The standard power-up sequence module 414 performs a routine power-up, including turning-on the electronic display.
With regard to
With regard to
With regard to
With regard to
With regard to
Although the emergency message button has been described for use on a wireless communications device, it should be understood that the principles of the present invention could be applied to other wireless devices, such a voice over Internet protocol (VoIP) telephones, portable game consoles (e.g., Nintendo DS), or fixed game consoles, such as x-box, where network connectivity exists. Still yet, the principles of the present invention could be applied to wired communications devices, such as telephones. Furthermore, the term button is representative of any device, such as a switch, knob, wheel, or otherwise, that can be utilized to interact with the wireless communications device.
Although the principles of the present invention have primarily been described with regard to wireless communications devices, it should be understood that wired communications devices, including wired/wireless computers, may be adapted to include emergency messaging, as described herein. One or more buttons or other initiation devices may be provided on the wired communications devices to generate and communicate an emergency data message to a network location for routing to a PSAP local to the user. In adapting the wired communications devices, software may be included in the devices to generate and communicate an emergency data message (e.g., text message or email) using a communications protocol that is capable of being communicated over the communications network (e.g., public switched telephone network, cable network, Internet), as understood in the art. Information specific to the user, location of the user, or otherwise may be included in the emergency data message. For example, name, address, number of people in residence, photograph, medical conditions, or any other information may be pre-established for retrieval and inclusion in the emergency data message, thereby providing information to an operator at a PSAP to provide emergency personnel, such as police, firemen, or medical personnel.
The previous detailed description is of a small number of embodiments for implementing the invention and is not intended to be limiting in scope. One of skills in this art will immediately envisage the methods and variations used to implement this invention in other areas than those described in detail. The following claims set forth a number of the embodiments of the invention disclosed with greater particularity.
This application claims priority to co-pending Provisional Patent Application Ser. No. 61/078,123 filed on Jul. 3, 2008; the entire teachings of which are incorporated herein by reference.
Number | Name | Date | Kind |
---|---|---|---|
5339351 | Hoskinson et al. | Aug 1994 | A |
5379337 | Castillo et al. | Jan 1995 | A |
5497149 | Fast | Mar 1996 | A |
5555286 | Tendler | Sep 1996 | A |
5646987 | Gerber et al. | Jul 1997 | A |
5710803 | Kowal et al. | Jan 1998 | A |
5936622 | Halverson et al. | Aug 1999 | A |
5941930 | Morimoto et al. | Aug 1999 | A |
6240285 | Blum et al. | May 2001 | B1 |
6317049 | Toubia et al. | Nov 2001 | B1 |
6366772 | Arnson | Apr 2002 | B1 |
6377169 | Yanagisawa | Apr 2002 | B1 |
6405033 | Kennedy et al. | Jun 2002 | B1 |
6415018 | Antonucci et al. | Jul 2002 | B1 |
6424908 | Urban et al. | Jul 2002 | B2 |
6456695 | Lee | Sep 2002 | B2 |
6480578 | Allport | Nov 2002 | B1 |
6526125 | Lindsay et al. | Feb 2003 | B1 |
6631184 | Weiner | Oct 2003 | B1 |
6636732 | Boling et al. | Oct 2003 | B1 |
6690932 | Barnier et al. | Feb 2004 | B1 |
7026925 | Roche et al. | Apr 2006 | B2 |
7079627 | Crago et al. | Jul 2006 | B2 |
7095733 | Yarlagadda et al. | Aug 2006 | B1 |
7231218 | Diacakis et al. | Jun 2007 | B2 |
7269413 | Kraft | Sep 2007 | B2 |
7391784 | Renkel | Jun 2008 | B1 |
7418087 | Luneau et al. | Aug 2008 | B2 |
7444238 | Opitz | Oct 2008 | B1 |
7496189 | Clarisse et al. | Feb 2009 | B2 |
7679505 | Vallaire | Mar 2010 | B1 |
7706356 | Olshansky et al. | Apr 2010 | B1 |
7734019 | Terpstra | Jun 2010 | B1 |
8364117 | Hawkins | Jan 2013 | B2 |
8428548 | Ray et al. | Apr 2013 | B2 |
8472916 | Coppage et al. | Jun 2013 | B2 |
8489062 | Ray et al. | Jul 2013 | B2 |
20010003843 | Scepanovic et al. | Jun 2001 | A1 |
20010004588 | Hong | Jun 2001 | A1 |
20010012379 | Amemiya et al. | Aug 2001 | A1 |
20020016189 | Sheynblat et al. | Feb 2002 | A1 |
20020068584 | Gage et al. | Jun 2002 | A1 |
20020136363 | Stumer et al. | Sep 2002 | A1 |
20030063714 | Stumer et al. | Apr 2003 | A1 |
20030109245 | McCalmont et al. | Jun 2003 | A1 |
20030122779 | Martin et al. | Jul 2003 | A1 |
20030133450 | Baum | Jul 2003 | A1 |
20030162554 | Kim | Aug 2003 | A1 |
20040029610 | Ihira et al. | Feb 2004 | A1 |
20040056770 | Metcalf | Mar 2004 | A1 |
20040063439 | Glazko et al. | Apr 2004 | A1 |
20040072583 | Weng | Apr 2004 | A1 |
20040113836 | Rickerson, Jr. | Jun 2004 | A1 |
20040157564 | Murakami et al. | Aug 2004 | A1 |
20040176123 | Chin et al. | Sep 2004 | A1 |
20040185871 | Somani et al. | Sep 2004 | A1 |
20040198329 | Vasa | Oct 2004 | A1 |
20040258216 | Reid | Dec 2004 | A1 |
20050003797 | Baldwin | Jan 2005 | A1 |
20050048947 | Holland et al. | Mar 2005 | A1 |
20050070315 | Rai et al. | Mar 2005 | A1 |
20050085257 | Laird et al. | Apr 2005 | A1 |
20050097380 | Kim | May 2005 | A1 |
20050101287 | Jin et al. | May 2005 | A1 |
20050111630 | Potorny et al. | May 2005 | A1 |
20050169248 | Truesdale et al. | Aug 2005 | A1 |
20050197096 | Yang et al. | Sep 2005 | A1 |
20050201358 | Nelson et al. | Sep 2005 | A1 |
20050209781 | Anderson | Sep 2005 | A1 |
20050239477 | Kim et al. | Oct 2005 | A1 |
20050265326 | Laliberte | Dec 2005 | A1 |
20050277405 | Noguchi | Dec 2005 | A1 |
20060009243 | Dahan et al. | Jan 2006 | A1 |
20060052134 | Sato | Mar 2006 | A1 |
20060056620 | Shingal et al. | Mar 2006 | A1 |
20060133582 | McCulloch | Jun 2006 | A1 |
20060145841 | Daurensan et al. | Jul 2006 | A1 |
20060152373 | King | Jul 2006 | A1 |
20060166685 | Adkins | Jul 2006 | A1 |
20060217105 | Kumar et al. | Sep 2006 | A1 |
20060217136 | Bantukul et al. | Sep 2006 | A1 |
20060219542 | Savir | Oct 2006 | A1 |
20060222151 | Goldman et al. | Oct 2006 | A1 |
20060227122 | Proctor | Oct 2006 | A1 |
20060229100 | Born | Oct 2006 | A1 |
20060238384 | Hess et al. | Oct 2006 | A1 |
20060276168 | Fuller et al. | Dec 2006 | A1 |
20060293024 | Benco et al. | Dec 2006 | A1 |
20070001902 | Kuo et al. | Jan 2007 | A1 |
20070003024 | Olivier et al. | Jan 2007 | A1 |
20070082652 | Hartigan et al. | Apr 2007 | A1 |
20070201391 | Belmonte et al. | Aug 2007 | A1 |
20070201645 | Gass et al. | Aug 2007 | A1 |
20070273519 | Ichikawa et al. | Nov 2007 | A1 |
20070280428 | McClelland | Dec 2007 | A1 |
20070287473 | Dupray | Dec 2007 | A1 |
20080001734 | Stilp et al. | Jan 2008 | A1 |
20080013696 | Motley et al. | Jan 2008 | A1 |
20080057944 | Miriyala et al. | Mar 2008 | A1 |
20080057987 | Landschaft et al. | Mar 2008 | A1 |
20080070553 | Yamakawa et al. | Mar 2008 | A1 |
20080122929 | Chukwu | May 2008 | A1 |
20080220715 | Sinha et al. | Sep 2008 | A1 |
20080227427 | Kadavallur et al. | Sep 2008 | A1 |
20080254810 | Fok et al. | Oct 2008 | A1 |
20080273670 | Dickinson | Nov 2008 | A1 |
20080275950 | Jordan | Nov 2008 | A1 |
20080287748 | Sapounas et al. | Nov 2008 | A1 |
20080310850 | Pederson et al. | Dec 2008 | A1 |
20090047924 | Ray et al. | Feb 2009 | A1 |
20090064039 | Lee et al. | Mar 2009 | A1 |
20090121930 | Bennett et al. | May 2009 | A1 |
20090131072 | Razdan et al. | May 2009 | A1 |
20090144157 | Saracino et al. | Jun 2009 | A1 |
20090149153 | Lee | Jun 2009 | A1 |
20090186596 | Kaltsukis | Jul 2009 | A1 |
20090197567 | Ogram | Aug 2009 | A1 |
20090215428 | Noldus et al. | Aug 2009 | A1 |
20090227225 | Mitchell et al. | Sep 2009 | A1 |
20090233573 | Gray | Sep 2009 | A1 |
20090310602 | Olshansky et al. | Dec 2009 | A1 |
20100098062 | Croak et al. | Apr 2010 | A1 |
20100291894 | Pipes | Nov 2010 | A1 |
20130115909 | Hawkins | May 2013 | A1 |
Entry |
---|
Response filed Nov. 2, 2010 for U.S. Appl. No. 11/891,784. |
Dale N. Hatfield, “A Report on Technical and Operational Issues Impacting the Provision of Wireless Enhanced 911 Services,” Federal Communications Commission, printed from the World Wide Web on May 8, 2006 (54 pages). |
ANSI, “TIA Standard Telecommunications Telephone Terminal Equipment Caller Identity and Visual Message Waiting Indicator Equipment Performance Requirements,” TIA-777-A, Revision of TIA/EIA-777, May 1, 2003 (77 pages). |
Micro Engineering Labs, Inc., “Caller ID”, Retrieved from the Internet at URL: <http://www.melabs.com/resources/callerid.htm> on Apr. 24, 2006; Copyright 2006 by microEngineering Labs, Inc (as of date of retrieval, article last updated Apr. 16, 2006) (3 pages). |
Dave Ryan & Asher Hazanchuk, “On-Hook & Off-Hook Caller ID Using DSP,” Circuit Cellular INK # 83, Jun. 1997 (12 pages). |
Ittiam Systems, “Caller Identification (CLI or Caller ID),” Retrieved from the Internet on Apr. 24, 2006 at URL <http://www.ittiam.com/pages/products/cid.htm, downloaded from the World Wide Web on Apr. 24, 2006 (2 pages). |
“AT & T Wireless Unleashes the First and Only Wireless Messaging Device”, PhysOrg.com, Sep. 30, 2004; available online at URL: <http://www.physorg.com/news1392.html> (12 pages). |
Non-Final Office Action date mailed Aug. 3, 2010 for U.S. Appl. No. 11/891,784. |
Non-Final Rejection mailed Jan. 19, 2011 for U.S. Appl. No. 11/430,232. |
Non-Final Rejection mailed Mar. 17, 2011 for U.S. Appl. No. 11/640,714. |
RCE filed on Apr. 4, 2011 for U.S. Appl. No. 11/891,784. |
Final Rejection mailed Jan. 3, 2011 for U.S. Appl. No. 11/891,784. |
Non-Final Rejection mailed Mar. 4, 2011 for U.S. Appl. No. 12/257,424. |
“NENA Recommended Generic Standards for E9-1-1 PSAP Equipment” NENA Technical Reference. NENA-04-001 Issue 2, Mar. 2001. |
Non-Final Rejection mailed Mar. 28, 2011 for U.S. Appl. No. 11/430,232. |
Non-Final Rejection mailed Apr. 1, 2011 for U.S. Appl. No. 12/257,655. |
Non-Final Rejection mailed Mar. 3, 2011 for U.S. Appl. No. 12/257,416. |
Non-Final Rejection mailed Mar. 17, 2011 for U.S. Appl. No. 12/257,640. |
U.S. Appl. No. 12/257,717; Final Rejection dated Jan. 23, 2012; 16 pages. |
U.S. Appl. No. 12/257,717; Non-Final Rejection dated Sep. 13, 2011; 19 pages. |
U.S. Appl. No. 12/257,725; Final Rejection dated Jan. 17, 2012; 17 pages. |
U.S. Appl. No, 12/257,725; Non-Final Rejection dated Jul. 19, 2011; 26 pages. |
U.S. Appl. No. 12/257,640; Non-Final Rejection dated Jan. 4, 2012; 19 pages. |
U.S. Appl. No. 12/257,640; Final Rejection dated Aug. 17, 2011; 17 paces. |
U.S. Appl. No. 12/257,655; Final Rejection dated Sep. 16, 2011; 22 pages. |
U.S. Appl. No. 12/257,655; Amendment and Reguest for Continued Examination dated Dec. 16, 2011; 18 pages. |
U.S. Appl. No. 12/070,775; Non-Final Rejection dated Jul. 25, 2011; 33 pages. |
U.S. Appl. No. 12/257,836 Non-Finai Rejection dated Nov. 29, 2011; 13 pages. |
U.S. Appl. No. 12/257,836; Non-Final Rejection dated Jun. 8, 2011; 15 pages. |
U.S. Appl. No. 12/257,687; Non-Final Rejection dated Apr. 9, 2012; 16 pages. |
U.S. Appl. No, 12/257,687; Non-Final Rejection dated May 10, 2011; 14 pages. |
U.S. Appl. No. 12/257,687; Final Rejection dated Sep. 29, 2011: 12 pages. |
U.S. Appl. No. 12/257,736; Non-Final Rejection dated Apr. 28, 2011; 15 pages. |
U.S. Appl. No. 12/257,736; Final Rejection dated Nov. 23, 2011; 18 pages. |
U.S. Appl. No. 12/257,736; Amendment and Request for Continued Examination dated Feb. 22, 2012; 12 pages. |
U.S. Appl. No. 12/257,416; Final Rejection dated Jul. 14, 2011; 17 Pages. |
U.S. Appl. No. 12/257,416; Non-Final Rejection dated Feb. 3, 2012; 24 pages. |
U.S. Appl. No. 12/070,775; Final Rejection dated May 14, 2012; 27 pages. |
U.S. Appl. No. 12/257,416; Final Rejection dated Jun. 13, 2012; 38 pages. |
U.S. Appl. No. 12/257,640; Final Rejection dated May 2, 2012; 18 pages. |
U.S. Appl. No. 12/257,655; Non-Final Rejection dated Jul. 17, 2012; 26 pages. |
U.S. Appl. No. 12/257,836; Final Rejection dated May 14, 2012; 26 pages. |
U.S. Appl. No. 12/070,775; Notice of Allowance dated Sep. 12, 2012; 24 pages. |
U.S. Appl. No. 12/257,687; Final Rejection dated Aug. 31, 2012; 19 pages. |
U.S. Appl. No. 121257,717; Non-Final Rejection dated Aug. 16, 2012; 42 pages. |
U.S. Appl. No. 12/257,836; Non-Final Rejection dated Sep. 12, 2012; 25 pages. |
U.S. Appl. No. 12/070,775; Issue Notification dated Jan. 9, 2013; 1 page. |
U.S. Appl. No. 12/257,640; Non-Final Rejection dated Dec. 5, 2012; 23 pages. |
U.S. Appl. No. 12/257,655; Final Rejection dated Jan. 2, 2013; 18 pages. |
U.S. Appl. No. 12/257,687; Notice of Allowance dated Feb. 20, 2013; 20 pages. |
U.S. Appl. No. 12/257,687; Notice of Panel Decision on Pre-Appeal Brief Review dated Dec. 14, 2012; 2 pages. |
U.S. Appl. No. 12/257,717; Notice of Allowance dated Feb. 14, 2013: 35 pages. |
U.S. Appl. No. 12/257,725; Notice of Allowance dated Dec. 24, 2012; 24 pages. |
U.S. Appl. No. 12/257,836; Notice of Allowance dated Mar. 12, 2013; 31 pages. |
U.S. Appl. No. 13/712,669; Non-Final Rejection dated Mar. 27, 2013; 34 pages. |
U.S. Appl. No. 12/257,725; Issue Notification dated Apr. 3, 2013; 1 page. |
U.S. Appl. No. 12/257,640; Final Rejection dated Arp. 15, 2013; 21 pages. |
U.S. Appl. No. 12/257,655; Notice of Allowance dated Apr. 16, 2013; 15 pages. |
U.S. Appl. No. 12/257,416; Non Final Office Action dated May 22, 2013; 40 pages. |
U.S. Appl. No. 12/257,687; Issue Notification dated Jun. 5, 2013; 1 page. |
U.S. Appl. No. 12/257,836; Issue Notification dated Jun. 26, 2013; 1 page. |
Number | Date | Country | |
---|---|---|---|
20100003951 A1 | Jan 2010 | US |
Number | Date | Country | |
---|---|---|---|
61078123 | Jul 2008 | US |