When emergencies occur or other help is needed, people will reach out to emergency services, such as 911, for assistance. Traditionally, in order to request emergency services, a person places a telephone call to 911 or another emergency telephone number. As cellular and Internet-based phones rival traditional telephones connected to the Public Switched Telephone Network (PSTN) in popularity, emergency call centers are receiving calls from an increasing variety of sources. Because different sources for requesting emergency services may have different capabilities, there is a need for emergency call centers to be able to move beyond ordinary PSTN telephone capabilities. For example, text messaging, e-mail, and various other features have become more common on cellular telephones.
In order to provide an emergency call center, such as a 911 Public Safety Answering Point (PSAP), with complete information in the event a text message or other similar emergency communication is sent to the PSAP, a preformatted emergency text message may be generated on a wireless communications device and communicated via a communications network. An appropriate emergency call center may be determined on the communications network and the generated preformatted emergency text message may be communicated to the appropriate PSAP.
One embodiment of a method for generating an emergency text message includes, in response to receiving a request to communicate an emergency text message, accessing stored personal data for use in generating content of the emergency text message. A determination may be made as to whether current location coordinates are available. If available, the emergency text message may be populated with the accessed stored personal data and the current location coordinates. The populated emergency text message may be communicated over a communications network 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:
In one embodiment, the wireless communications device 104 communicates the emergency text message 106 over the wireless communications network 108 to emergency message router 110. The emergency message router 110 may be in communication with the communications network 108 and be configured to receive and distribute emergency text messages, such as emergency text message 106. Some data that the emergency message router 110 may use to route emergency text messages to the appropriate PSAP includes current user location information, such as a cell site ID code (CCID), also referred to as cell site coordinates, global positioning system (GPS) coordinates, or other available information in the emergency text message 106. Along with information stored in the emergency message router 110, as well as available on remote sources, the emergency message router 110 may then choose the most appropriate PSAP for message delivery. Given that there are many thousands of PSAPs, selection of the most appropriate or closest PSAP to the current location of the user who sent the emergency text message can be helpful to emergency personnel.
As not all wireless communications devices are configured to generate preformatted emergency data messages, a user may generate and communicate a freeform emergency data message (e.g., text message, e-mail, instant message, image message) to a network address, such as Internet domain name “911.911,” for routing to a PSAP local to the user. A freeform emergency data message is any data message that is addressed and communicated to a network address for routing to a PSAP local to the user
The PSAPs have a wide variety of capabilities depending upon the equipment and level of sophistication of the PSAP 112. For instance, some of the PSAPs 112 may have limited capabilities and be capable of receiving address information, call back number, and a person's name to which the calling phone number is registered. Other, more sophisticated PSAPs 112, may have the ability to receive GPS location coordinates, as well as other more detailed information. The emergency message router 110 may have knowledge of the capabilities of each of the PSAPs 112 and use this knowledge, in addition to distance or other location information, to determine the most appropriate PSAP for the message. Having an emergency message router 110 allows for a stored emergency network address, such as “911.911”, to be used as a generic address, rather than individual users 102 having to input a specific PSAP address each time their location changes. Without the emergency message router 110, an emergency text message 106 may be delivered to a PSAP which either does not have the capability of receiving text messages or may not be the closest PSAP to the user 102. Within the PSAP may be one or more terminals having a PSAP display screen 114 for displaying the emergency text message 106. Any known or related information to the user who sent the emergency text message 106 may also be displayed on the PSAP display screen 114 upon receipt.
A message text field 206 may also be pre-populated with a default message, such as, “need emergency/911 help.” In an alternative embodiment, the message text field may be entered manually and edited by the user. Alternatively, the message text field may be selected from a list of pre-defined emergency messages. A name field 208 may also be included for indicating the name of the person associated with a wireless communications device 200 that is communicating the emergency text message. In an alternative embodiment, the name field 208 may also be edited by the user replacing any default name in the field. A call back number field 210 may provide a PSAP with a number for contacting the user for more information regarding an emergency. The call back number 210 may not necessarily be a number directly associated with the wireless communication device 200, but rather may be a number associated with an emergency contact, such as a family member or friend. For example, some wireless communications devices 200 may have text capability, but not voice capability. Therefore, an attempt to call the wireless communication device may not work. Providing the call back number 210 belonging to a friend or family member may allow a person at the PSAP to obtain additional information that could prove helpful.
A current location field 212 may be populated by the user prior to communicating the emergency text message. Alternatively, the current location field 212 may be blank if the user chooses or does not have time to populate the current location field 212. While the current location field 212 may be useful in providing the PSAP with location information, it may not always be possible to have the current location field 212 updated or entered prior to sending the emergency text message. Because the current location field 212 may be blank, a permanent address field 214 may also be provided to send the PSAP. The permanent address may be the user's home or office, where additional information may likely be found. Even if the wireless communications device 200 is not located at the permanent address found in the permanent address field 212, having a permanent contact address may prove to be useful in the event an investigation or other information needs to be obtained at a later time.
GPS coordinate fields 216 may also be included to provide GPS coordinates to the PSAP if the wireless communications device 200 is GPS enabled. If the wireless communications device 200 is GPS enabled, latitude and longitude coordinates may be included in the emergency text message and communicated within the emergency text message to provide specific location information for locating the user with the wireless communications device 200. Frequently, GPS coordinate information will not be available because of location or environmental factors, such as being in a basement or a thickly walled building. Therefore, GPS coordinate information may not be available, even if the wireless communications device 200 is GPS enabled. Additionally, GPS coordinates may be requested from the communications network, as is described below in reference to
A memory 508 may also be located within the wireless communications device 501 for storing data being processed by the processor 502, as well as user data (not shown) for use in generating a preformatted emergency text message 509. The memory 508 may be RAM, FLASH, or any other memory configured to operate in the wireless communication device 501. In addition to data being processed and the user data, the memory 508 may also store menu information 510 used in displaying menus for guiding a user of the wireless communications device 501 through creation of an emergency text message. Templates 511 that define structure of text messages that are used to report different types of emergencies may also be stored in the memory 508. Depending on selections made by the user using the menus 510, a particular one of the templates 511 may be selected for use in generating an emergency text message. Having different emergency text message templates 511 allows different information to be included or not included depending on the particular type of emergency selected by the user via the menus 510. For example, a fire emergency away from a user's home may not include the user's home address as would a medical emergency occurring at the user's home.
A display 512 for viewing data from the wireless communications device 501 may also be provided. The display 512 may also allow for a user to view an emergency text message that has been generated, edit the message, read replies, and perform many other functions of a display 512.
A GPS device 514 may also be provided within the wireless communications device 501. The GPS device 514 may be an electronic component or some other hardware, either integrated into the wireless communications device or in communication with the wireless communications device 501, which provides GPS enablement to the wireless communications device 501. GPS enablement allows for the wireless communications device 501 to be able to generate current GPS coordinates, which may be used within the emergency text message.
In step 806, a determination is made as to whether GPS coordinate data is available. If the wireless communications device is GPS enabled and the GPS coordinates are available, then at step 808, an emergency text message is populated with the GPS coordinates. The emergency text message is also populated with the stored information. In step 809, the emergency text message is sent to emergency services, such as a PSAP via a network router configured to identify and route the emergency message to a PSAP local to the user.
If the GPS coordinate data was not available in step 806, in step 810 a request may be made for coordinates that may be available from the network. Triangulation or another commonly known method may be used by the network to determine GPS coordinate data. In step 812, a determination is made as to whether the current GPS coordinates are available within a predetermined time window. The predetermined time window may be anytime from a fraction of a second to multiple seconds and should provide sufficient time for coordinates to be made available from the network. If the current GPS coordinates are available within the predetermined time window from step 812, the emergency text message may be populated and then sent to emergency services complete with GPS coordinate data as described previously in steps 808 and 809. If the current GPS coordinates were not available within the predetermined time window, the emergency text message may be sent without GPS coordinate data in step 809. In step 814, a determination is made as to whether the GPS coordinate data was sent. If the GPS coordinate data was sent, the process ends. If the current GPS coordinates data were not sent, a second time window may be granted. In step 816, it may be determined whether GPS coordinates were available within the second time window. If the GPS coordinates data were available within the predetermined second time window, the emergency text message may be populated with the current GPS coordinates and sent to emergency services as described in steps 808 and 809. If the GPS coordinates were not available within the second time window, the process ends.
Although the principles of the present 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 skill 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 Provisional Patent Application Ser. No. 61/078,123, entitled: Emergency 911 Text Messaging Services, was 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 | Yarlgadda 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 |
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 |
Entry |
---|
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). |
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. 12/272,238. |
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. |
“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. |
Response filed Nov. 2, 2010 for U.S. Appl. No. 11/891,784. |
U.S. Appl. No. 12/070,775; Final Rejection dated May 14, 2012; 27 pages. |
U.S. Appl. No. 12/257,674; Non-Final Rejection dated Jul. 20, 2012; 21 pages. |
U.S. Appl. No. 12/257,640; Final Rejection dated May 2, 2012; 18 pages. |
U.S. Appl. No. 12/257,416; Final Rejection dated Jun. 13, 2012; 38 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/257,674; Notice of Allowance dated Jan. 25, 2012; 7 pages. |
U.S. Appl. No. 12/257,674; Final Rejection dated Oct. 3, 2011; 15 pages. |
U.S. Appl. No. 12/257,674 Non-Final Rejection dated Apr. 28, 2011; 14 pages. |
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; 14 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; 17 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,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; 11 pages. |
U.S. Appl. No. 12/257,416; Final Rejection dated Jul. 14, 2011; 17 pages. |
U.S. Appl. No. 12/070,775; Non-Final Rejection dated Jul. 25, 2011; 33 pages. |
U.S. Appl. No. 12/257,655; Final Rejection dated Sep. 16, 2011; 20 pages. |
U.S. Appl. No. 12/257,655; Amendment and Request for Continued Examination dated Dec. 16, 2011; 14 pages. |
U.S. Appl. No. 12/257,836 Non-Final 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/070,775; Issue Notification dated Jan. 9, 2013; 1 page. |
U.S. Appl. No. 12/070,775; Notice of Allowance dated Sep. 12, 2012; 24 pages. |
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,674; Final Rejection dated Nov. 5, 2012; 17 pages. |
U.S. Appl. No. 12/257,717; Non-Final Rejection dated Aug. 16, 2012; 42 pages. |
U.S. Appl. No. 12/257,725; Notice of Allowance dated Dec. 24, 2012; 24 pages. |
U.S. Appl. No. 12/257,836; Non-Final Rejection dated Sep. 12, 2012; 25 pages. |
U.S. Appl. No. 12/257,640; Final Rejection dated Apr. 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,674; Notice of Allowance dated Apr. 3, 2013; 15 pages. |
U.S. Appl. No. 12/257,717; Notice of Allowance dated Feb. 14, 2013; 35 pages. |
U.S. Appl. No. 12/257,725; Issue Notification dated Apr. 3, 2013; 1 page. |
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. |
Number | Date | Country | |
---|---|---|---|
20100003959 A1 | Jan 2010 | US |
Number | Date | Country | |
---|---|---|---|
61078123 | Jul 2008 | US |