US 8,489,062 B2Grant
System and method for sending an emergency message selected from among multiple emergency message types from a wireless communications device
Issue Date:2013-07-16
•18 Claims
•9 Drawing Sheets
Abstract
A wireless communications device and method for communicating an emergency message to a public safety answering point (PSAP) may include storing (i) data representative of a plurality of emergency messages being of different message types and (ii) a network address associated with each emergency message. In response to a user selecting one of the emergency messages, the selected emergency message and associated network address may be established as defaults for communication of the default emergency message to a PSAP over the communications network. In response to the user requesting to send an emergency message, the default emergency message may be generated by using the default network address to communicate the emergency message and communicated over the communications network to the default network address for routing the default emergency message to a PSAP local to the user.
Metadata
Assignee
- CenturyLink Intellectual Property LLC
Inventors
- Amar Nath Ray
- Carl M. Coppage
- Lynn T. Greene
Application Information
Application Number:US 12/257,836
Filing Date:2008-10-24
Priority Date:2008-07-03
Art Unit:2642
Classifications
IPC:
H04M11/04
Patent Drawings (9 sheets)
Description
Cross Reference to Related Applications
[0001] This Application claims priority to Provisional Patent Application Ser. No. 61/078,123 filed on Jul. 3, 2008; the entire teachings of which are incorporated herein by reference.
Background of the Invention
[0002] 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.
[0003] 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.
Summary
[0004] To enable users of wireless communications devices to easily and expeditiously communicate an emergency message during an emergency situation, the principles of the present invention provide for a wireless communications device to enable a user to communicate an emergency message to a PSAP. Multiple emergency messages of different message types may be stored on the wireless communications device for the user to select one to use as a default emergency communications message. The different types of emergency messages may include a text message, email message, recorded voice message, or data used to perform a text-to-speech synthesis.
[0005] A wireless communications device and method for communicating an emergency message to a public safety answering point (PSAP) may include storing (i) data representative of a plurality of emergency messages being of different message types and (ii) a network address associated with each emergency message. In response to a user selecting one of the emergency messages, the selected emergency message and associated network address may be established as defaults for communication of the default emergency message to a PSAP over the communications network. In response to the user requesting to send an emergency message, the default emergency message may be generated by using the default network address to communicate the emergency message and communicated over the communications network to the default network address for routing the default emergency message to a PSAP local to the user.
Brief Description of the Drawings
[0006] 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:
[0007] FIG. 1 is an illustrative network environment configured to enable a user to communicate emergency messages to a public safety answering point;
[0008] FIGS. 2A-2D are illustrations of illustrative wireless communications devices configured with emergency message buttons for initiating and communicating an emergency message to a public safety answering point;
[0009] FIG. 3A is a block diagram of an illustrative wireless communications device configured with an emergency message button for generating and communicating an emergency message;
[0010] FIG. 3B is a block diagram of an illustrative circuit within the wireless communications device of FIG. 3A for powering-up the wireless communications device using both standard and emergency power-up sequences;
[0011] FIG. 4 is a block diagram of illustrative modules that can be executed on the wireless communications device of FIG. 3A ;
[0012] FIGS. 5A-5C are signal diagrams showing illustrative emergency request signals with different activation sequences for initiating an emergency message to be communicated to a public safety answering point;
[0013] FIG. 6 is a graph of illustrative force signals associated with regular keys and an emergency key for use in initiating an emergency message;
[0014] FIG. 7 is a flow diagram of an illustrative process for identifying a user request to generate and send an emergency message;
[0015] FIG. 8 is a flow diagram of an illustrative process for identifying a user request to generate and communicate an emergency message to a public safety answering point;
[0016] FIG. 9 is a flow diagram of an illustrative process for a wireless communications device in performing a power-up sequence based on the type of power-up sequence requested by a user;
[0017] FIG. 10 is a timing diagram of illustrative timings for both standard and abbreviated power-up sequences;
[0018] FIG. 11 is a signal diagram of illustrative power usage for both standard and abbreviated power-up sequences;
[0019] FIG. 12 is a flow diagram of an illustrative process for powering-up a wireless communications device;
[0020] FIG. 13 is a flow diagram of a more detailed illustrative process for powering-up a wireless communications device;
[0021] FIG. 14 is a screen shot of an illustrative menu for a user to select an emergency message type as a default for sending an emergency message to a PSAP local to the user when requested; and
[0022] FIG. 15 is a flow chart of an illustrative process for a establishing an emergency message and network address as defaults and communicating the default emergency message to the associated network address for routing of the default emergency message to a PSAP local to the user.
Detailed Description of the Drawings
[0023] With regard to FIG. 1 , a user 102 of a wireless communications device 104 may have a need for communicating with a public safety answering point (PSAP) 106 in an emergency situation. The wireless communications device 104 may be a mobile telephone, personal digital assistant (PDA), wireless electronic game, multi-mode telephone, or other electronic devices capable of communicating emergency data messages (EDMs) to public safety answering points (PSAPs). The wireless communications device 104 may communicate with the PSAP 106 over a communications network 108. The communications network 108 may include one or more communications networks, including mobile communications networks, the Internet, public switched telephone network (PSTN), or other communications network over which the wireless communications device 104 may communicate with the PSAP 106. The wireless communications device 104 may communicate over a wireless communications path 110a with the network 108 and the PSAP 106 may communicate with the network 108 over a communications path 110b, which may be wireless or wired.
[0024] 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, (iv) email 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 farther described herein. 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, email, 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.
[0025] With regard to FIG. 2A , a wireless communications device 200a includes a housing 202 and user interface 204. The user interface is shown as a keypad, but as understood in the art, the user interface may alternatively be a touch screen or combination thereof. The wireless communications device 200a further includes an electronic display 206 on which information, such as telephone numbers being called or received, are displayed. In addition, an emergency message button 208 may be disposed on the housing in a convenient place for a user to activate an emergency message. In being disposed on the housing, the emergency message button 208 actually passes through or is mounted to the housing 202 and is positioned in a location at which the user may access the emergency message button 208 without having to open any portion of the housing 202. In an alternative embodiment, the emergency message button 208 may be covered by a portion of the housing or other structure (e.g., repositionable flap or cover (not shown)) that can be removed or displaced to enable a user to access the emergency message button 208. As shown, the emergency message button 208 is a hard-button or key that operates in the same or similar manner as buttons or keys of the user interface 204. For example, the emergency message button 208 may be depressible for a user to initiate an emergency message. Alternatively, the emergency message button 208 may be an electronic touch sensor that identifies that a user has contacted the emergency message button 208.
[0026] 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.
[0027] 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.
[0028] With regard to FIG. 2B , the emergency message button 208 is shown to be recessed within the housing 202 so as to minimize the chance of a user inadvertently pressing the emergency message button 208. In being recessed, the housing 208 may have a protrusion (not shown) around the emergency message button 208 or the emergency message button 208 may be recessed with respect to a surface of the housing 202.
[0029] With regard to FIG. 2C , a wireless communications device 200b is shown to be configured with a user interface 212 that includes a multi-purpose button 214 that may be utilized to (i) end a telephone call, (ii) turn on the wireless communications device 200b, (iii) turn off the wireless communications device 200b, and (iv) request an emergency message to be communicated to a PSAP. The wireless communications device 200b may be configured to distinguish between a user's actions of the multi-purpose button 214 so as to avoid communicating an emergency message inadvertently. It should be understood that alternative buttons other than an on/off power button may be utilized.
[0030] With regard to FIG. 2D , a wireless communications device 200c may be configured to display a soft-button 216 on an electronic display 218 that may be selectable by a user to initiate and communicate an emergency message. If electronic display 218 is a touch screen (i.e., an electronic display that senses a user touching a portion of the electronic display), then the user may activate the soft-button 216 by pressing his or her finger to the electronic display 218 at a region defined by the soft-button 216. Alternatively, the user may select a hard-button 220 associated with the soft-button 216 to initiate an emergency message from the wireless communications device 200c.
[0031] With regard to FIG. 3A , a wireless communications device 300 may include a processing unit 302 that executes software 304. The software may include conventional communications functionality as well as functionality for generating and communicating an emergency message to a public safety answering point. The processing unit 302 may be in communication with a memory 306 that is configured to store data and software, and input/output (I/O) unit 308 that includes wireless communications devices, as understood in the art. The memory may store pre-established emergency messages, such as text messages, voice recorded messages, email messages, and the like, and network addresses associated with each type of message for routing of the emergency message to a PSAP local to the user and with communications capabilities that allow for receipt and processing of the emergency message.
[0032] The processing unit 302 may further be in communication with an electronic display 310, user interface 312, and emergency message button 314, which may be considered part of the user interface 312. The electronic display 310 may be configured to display information to a user using the wireless communications device 300. The user interface 312 may enable a user to place telephone calls and/or send text messages via a keypad or otherwise. The emergency message button 314 may be a hard-key that a user may press to initiate an emergency message to be generated and communicated by the software 304. Alternatively, the emergency message button 314 may be a soft-button generated by the processing unit 312 and displayed on the electronic display 310, and enable a user to request an emergency message to be generated and communicated by selection thereof In one embodiment, the wireless communications device 300 includes GPS circuitry 315, may be utilized to generate geographic coordinates for the processing unit 302 to include in an emergency message, such as an emergency text message, if available.
[0033] With regard to FIG. 3B , an illustrative circuit 313 is shown to include the emergency message button 314, battery 316, and on/off button 318. Two switches 320 and 322 are configured to switch and generate turn-on signals 324 and 326, respectively, when a user activates the emergency message button 314 or on/off button 318. As shown, the turn-on signal 324 is toggled three times, thereby representing a user selecting the emergency message button 314 three times within a second, which may be a pre-established activation sequence to cause the wireless communications device to activate an emergency power-up sequence. In an alternative embodiment, the emergency message button 314 and on/off button 318 may be the same hard-buttons. In such a configuration, the processing unit 302 may determine whether the user intended to turn on the wireless communications device using a standard power-up sequence or an emergency power-up sequence by determining whether the user activated the on/off button using a pre-established activation sequence.
[0034] With regard to FIG. 4 , modules 400, which may be software modules of software 304 of FIG. 3A , may be configured to identify a request from a user to generate and communicate an emergency message. Alternatively, one or more of the modules 400 may be hardware modules. An identify emergency message request module 402 may be configured to identify when a user requests an emergency message to be communicated to a public safety answering point. In identifying the emergency message request, the identify emergency message request module 402 may monitor a hard-button or soft-button, depending on the configuration of the wireless communication device in which the modules 400 are being executed. The identify emergency message request module 402 may monitor an emergency message key (e.g., emergency message key 208 of FIG. 2A ), to identify a particular sequence that a user presses the emergency message key, as further described with regard to FIG. 5 .
[0035] 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, (iii) speech synthesized voice message, (iv) email message, or otherwise. 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” network 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. If the emergency message is an email message, then the email message may include a network address to which the email is to be sent for routing to a local PSAP, information about the user, geographic information, if available, and message descriptive of an existing situation about which the user has known about (e.g., medical condition, doctor name, contact information, etc.). The emergency 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.
[0036] 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 for a network node at the network address to route to a local PSAP. If the emergency message is a text message, then the emergency text message may be sent to a network address configured to receive and route emergency text messages to local PSAPs. In one embodiment, the pre-established emergency message may be presented to the user prior to sending to the network address to enable the user to add, remove, or change information in the pre-established emergency message.
[0037] 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.
[0038] 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.
[0039] 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. In addition, the abbreviated emergency start-up sequence module 412 may automatically cause an emergency message, such as a text message, to be generated and communicated to a PSAP. Furthermore, once the emergency message is communicated to the PSAP, the abbreviated emergency start-up sequence module 412 may illuminate an illumination device, such as an LED, to notify the user that the emergency message was sent.
[0040] 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.
[0041] A select default emergency message module 416 may be configured to enable a user to select a default emergency message via a menu system or other graphical user interface elements. The user may select from multiple different forms of emergency messages, including text messaging, speech synthesis, recorded audio message, email, and instant message. Each of the types of messages may have a different network address associated therewith as different types of communications (e.g., voice message, text message, email message) are communicated to different network addresses for routing or distributing to a local PSAP that is capable of receiving those types of communications. In one embodiment, the user is able to edit a pre-established emergency message to include information associated with the user, such as home address, alternative telephone number, or other information personal to the user.
[0042] With regard to FIGS. 5A-5C , three illustrative user request signals 502, 504, and 506, respectively, are displayed. The user request signal 502 includes three pulses 508a-508c (collectively 508) that occur within a time period T1. In one embodiment, the wireless communication device may be configured to identify that an emergency request is made if a user selects an emergency message button three times to produce the three pulses 508 within a given time period, such as one second. By using a sequence, such as three presses of a button within a second, false emergency message requests may be minimized to avoid emergency messages being sent when a user has the wireless communication device in his or her pocket, handbag, or otherwise. As shown in FIG. 5B , an emergency request signal 504 is shown to be activated for T2 seconds. In one embodiment, the wireless communications device may use a pre-established or predetermined sequence for a user to press an emergency message button for two seconds or longer for an emergency request to be generated and sent to a PSAP. In yet another embodiment, as shown in FIG. 5C , the emergency message signal 506 is shown to include three pulses 510a-510c, where the first two pulses have the same duration of T3 and the last pulse 510c has a duration of T4 (i.e., short-short-long). Having a predetermined sequence that is irregular may further minimize inadvertent emergency message requests.
[0043] With regard to FIG. 6 , two force signals 602 and 604 are shown, where force signal 602 represents an amount of force that a regular key of a user interface requires to activate the regular key (e.g., alphanumeric key) and force signal 604 represents the amount of force required for a user to activate an emergency key. In one embodiment, an emergency key threshold force (FEK) is at least two times the amount of regular key threshold force (FRK). By using an emergency key that requires a user to apply more force than a regular key to reach a threshold force to activate the emergency key, the user is less likely to inadvertently request an emergency message to be communicated to a PSAP and activate the emergency message key by an intentional act. It should be understood that alternative embodiments may have an emergency key that requires the same or less force than a regular key for activation.
[0044] With regard to FIG. 7 , an illustrative process 700 for generating and communicating an emergency message to a PSAP is provided. The process 700 starts with step 702. At step 704, a determination as to whether a user has selected an emergency message button is performed. If the user has selected an emergency message button, then at step 706, an emergency message is generated. The emergency message may be a preestablished text message, audio message, or speech synthesized message. Each of the emergency messages may contain the telephone number of the wireless communications device, home address, current GPS coordinates, and/or other information associated with the user. At step 708, the emergency message may be sent or otherwise communicated to the PSAP. In sending the emergency message to the PSAP, the wireless communications device may communicate the emergency message using a wireless communications protocol for a particular type of message, as understood in the art. For example, if the emergency message is a text message, then the wireless communications device may use SMS. If, alternatively, the message is a prerecorded voice message, then the wireless communications device may communicate over a voice communications channel, as understood in the art. The process ends at step 710. If, at step 704, a determination is made that the user has not selected an emergency message button, then the process ends at step 710.
[0045] With regard to FIG. 8 , a process 800 may be used to respond to a user request for generating and communicating an emergency message in both power-on and power-off states of a wireless communications device. The process 800 starts at step 802, where an emergency message request is identified. In identifying an emergency message request, a determination is made as to whether an emergency message button has been selected a pre-determined sequence (e.g., three selections within one second). In identifying that the emergency message request has been made, at step 804, a determination as to whether power of the wireless communications device is currently on may be made by hardware, software, or firmware. If so, then at step 806, an emergency message is generated and sent at step 808. Alternatively, if the power of the wireless communication device is not currently on, then an abbreviated power-up sequence may be performed at step 810 prior to generating and sending an emergency message at steps 806 and 808, respectively. The abbreviated power-up sequence may limit electronic devices within the wireless communications device to turn on so as to accelerate generation and communication of the emergency message. If the communications device is configured to send an emergency message in response to activation of an emergency message button, then the wireless communications device may be configured to turn off with sufficient battery life, such as five percent, to send at least one emergency message or be configured with an emergency battery to be maintained in the event that an emergency message is requested to be sent after battery life of a primary battery has been exhausted.
[0046] With regard to FIG. 9 , an illustrative process 900 provides for a wireless communications device with an emergency message button. At step 902, an emergency message button is provided on a wireless communications device. The emergency message button may be a hard-button or a soft-button. At step 904, an emergency message is caused to be generated and sent to a PSAP in response to a user selecting the emergency message button. In sending the message to a PSAP, if the emergency message is an emergency text message, the emergency text message may be communicated to a central site (e.g., “emergency.gov”) to route the emergency text message to a local PSAP. If the emergency message is a prerecorded or speech synthesized message, a call to “911” may be placed in response to the emergency message button being activated by a user automatically (i.e., single button call).
[0047] With regard to FIG. 10 , a timing diagram shows illustrative graphs 1000 with timing signals 1002 and 1004, which represent standard and abbreviated emergency power-up sequence timing signals, respectively, for powering-up a wireless communications device. As shown, the standard power-up sequence timing signal 1002 lasts for a time TSTD and abbreviated power-up sequence timing signal 1004 last for a time TABBR, which is shorter than the length of time than it takes to power-up the wireless communications device using the standard power-up sequence. It should be understood that the relative times between the signals 1002 and 1004 are illustrative and that the differential between the power-up times may be higher or lower.
[0048] With regard to FIG. 11 , a signal diagram shows an illustrative graph 1100 with power signals 1102 and 1104, which represent standard and abbreviated emergency power-up sequence, respectively, for powering-up a wireless communications device. As shown, the standard power-up power signal 1102 illustrates that the standard power-up sequence uses more power than the abbreviated emergency power-up sequence. Maximum power of the standard power-up sequence is PSTD, and maximum power of the abbreviated power-up sequence is PABBR, which is lower than the maximum power of the standard power-up sequence. At time T1, the standard power-up sequence is complete and the wireless communications device is powered in a power-on state. At time T2, the abbreviated emergency power-up sequence is completed, which is shorter in time than the standard power-up sequence. Shown on the abbreviated power-up signal 1104 is a power surge 1106 at the time that an emergency message is sent as power is used to drive wireless communications electronics.
[0049] With regard to FIG. 12 , an illustrative process 1200 may be utilized to power-up a wireless communications device. The process 1200 starts at step 1202. At step 1204, a power-up request is received. At step 1206, a determination may be made as to whether the power-up request is a standard power-up request or an emergency power-up request. The determination may be made based on a signal line over which the power-up request is received by a processing unit or a power-up signal that is received. For example, a power-up signal may match a pre-established power-up sequence (e.g., three activations of an emergency message button within one second). If the power-up request is a standard power-up request, then at step 1208, the wireless communications device is powered-up using a standard power-up sequence, where a standard power-up sequence turns on the wireless communications device as currently understood in the art. If the request is determined to be an emergency power-up request at step 1206, then the wireless communications device is powered up using an abbreviated power-up sequence at step 1210. The abbreviated power-up sequence may power up fewer electronics or power-up the wireless communications device faster by not executing all standard power-up sequence software routines. The process ends at step 1212.
[0050] With regard to FIG. 13 , a more detailed process 1300 for performing an emergency power-up sequence is provided. The process 1300 starts at step 1302, where an emergency message request is received. At step 1304, emergency electronics are powered-up. In one embodiment, the emergency electronics may exclude powering up unnecessary electronics, such as an audible device or electronic display) that are not utilized for generating and communicating an emergency message so as to conserve power or minimize chance of a person in an emergency being detected. At step 1306, the wireless communications device registers with a communications network and registration confirmation is received at step 1308.
[0051] At step 1310, an emergency message is generated. In one embodiment, the emergency message is an emergency text message. Alternatively, the emergency message may be a voice synthesized message. At step 1312, a determination is made as to whether geographic coordinates are available. If so, then at step 1314, geographic coordinates are added to the emergency message. The geographic coordinates may be GPS coordinates if the wireless communications device is configured with a GPS device. Alternatively, the geographic coordinates may be generated by the wireless communications device requesting geographic coordinates from the communications network. If the geographic coordinates are not available at step 1312, then the message is communicated to a PSAP without the geographic coordinates at step 1316.
[0052] With regard to FIG. 14 , an illustrative graphical user interface 1400 displayed on a wireless communications device may be generated by a software module, such as the select default emergency message module 416 (FIG. 4 ), to enable a user to select one as a default emergency message. A user of the wireless communications device may communicate the default emergency message in response to the user activating an emergency message button, either hard-button or soft-button. As shown, a variety of emergency message types may be available for selection as a default emergency message, including a (1) pre-established emergency text message, (2) pre-established speech synthesis message, (3) record message, (4) email message, (5) instant message, and (6) image message. Depending on the model of the wireless communications device, not all of the emergency message default options shown may be available. For example, if the wireless communications device does not have speech synthesis capabilities, then the (2) pre-established speech synthesis message option may not be available. In addition, if the wireless communications device does not have email capabilities, then the (4) email message option would not be available.
[0053] An example of an emergency text message may be as follows, “Name>Bob Jones; Tel. No. 214 405-1234; Addr.>555 Victory Ave Dallas 75206; Msg.>Emergency Send Help.” It should be understood that the emergency message may be more detailed and include additional information. Still yet, other information related to the user may be included to further assist an operator at the PSAP and emergency personnel.
[0054] The user may select the option most appropriate for him or her depending on the area in which he or she lives and the pre-established messages stored in memory of the wireless communications device. If the user lives in a rural area, then it is unlikely that any local PSAPs are configured to receive emergency data messages, such as text messages, email messages, instant messages, or image messages, so the user should select either the pre-established speech synthesis message, if the wireless communications device is configured with a speech synthesizer or record a message. If a text-to-speech synthesizer is available on a network, such as the PSTN, then it may be desirable for the user to select the (1) pre-established text message option to communicate to the text-to-speech synthesizer for playing a local PSAP. As an alternative to the user selecting a default, a service provider or manufacturer may provide a user with the default already established based on PSAP communications capabilities in an area in which the user resides.
[0055] Each of the available selectable emergency messages has its pros and cons. For example, a text message is good because a text message can be communicated without an operator having to answer a call and it is a short message that can be communicated very quickly. Given that some PSAPs routinely have delays in answering voice calls, an emergency message that is performed via a voice channel, such as the (2) pre-established speech synthesis message and (3) voice recorded message, may not be the most efficient for the user if in an emergency that requires an immediate response. The (4) email message may also be good because an email may be communicated quickly. However, depending on the location of the user and the capabilities of local PSAPs, that data message option may be limited in value. The (6) image message is good because a photograph or video of the user may be sent to the PSAP for distribution to emergency personnel, thereby shortening response time. However, sending a photo or video is not as fast as a text message and local PSAPs would need to be configured to handle such data. Users may consult their service provider or PSAP to determine communications capabilities.
[0056] With regard to FIG. 15 , a illustrative process 1500 may be utilized to enable a user of a wireless communications device to select a default emergency message and communicate the default emergency message. At step 1502, multiple emergency messages of different message types and a network address associated with each respective emergency message may be stored. At step 1504, a default emergency message and network address may be established by a user selecting an emergency message type to use as a default. Each of the multiple emergency messages may be of a different type (e.g., text, recorded speech, email). At step 1506, the default emergency message may be generated with the network address in a “To” field. In one embodiment, the default emergency message is generated in response to a user selecting an emergency message button. In generating the default emergency message, the default emergency message may be populated with user-related information that may be stored in memory of the wireless communications device. The user-related information may include the user's home address, alternative telephone number, and so on. In addition, if geographic coordinates, such as GPS coordinates, are available when the emergency message is generated, then the geographic coordinates may be included in the emergency message. If, for example, the emergency message is a text or email message, then the geographic coordinates may be inserted therein. If the emergency message is a voice synthesized message, then the geographic coordinates may be spoken by a voice synthesizer while communicating with an operator at a PSAP.
[0057] At step 1508, the default emergency message is communicated over a wireless communications network to the default network address for routing to a PSAP local to the user. The default network address is a network address of a server or router on the communications network configured to identify a PSAP local to the user and configured to receive the type of emergency message being communicated. If the emergency message is a text message, then the network address may be an Internet Protocol domain name, such as “911.911,” which is associated with a server for routing to a local PSAP that has the communications capability to receive emergency text messages. Alternatively, if the emergency message is a recorded speech message or speech synthesized message, then the network address may be “911,” as is conventionally utilized by callers.
[0058] 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.
[0059] 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 preestablished 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.
[0060] 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.
Claims
The invention claimed is:
1. A wireless communications device for communicating an emergency message to a public safety answering point (PSAP), said wireless communications device comprising:
a memory storing (i) data representative of a plurality of emergency messages being of different message types and (ii) a network address associated with each respective emergency message;
an input/output (I/O) unit configured to wirelessly communicate with a communications network;
a processing unit in communication with said memory and I/O unit;
an electronic display in communication with said processing unit;
at least one illumination device in communication with said processing unit;
an abbreviated startup sequence module in communication with said memory, I/O unit, and processing unit; and
a user interface in communication with said processing unit, and configured to cause said processing unit to:
in response to a user selecting one of the emergency messages:
reduce illumination of the electronic display and the at least one illumination device; and
establish the selected emergency message and associated network address as defaults for communication of the default emergency message to the PSAP over the communications network; and
in response to the user requesting to send an emergency message:
generate the default emergency message by using the default network address as an address to which to communicate the emergency message;
communicate the default emergency message via said I/O unit over the communications network to the default network address for routing the default emergency message to a PSAP local to the user,
wherein when the user requests to send the emergency message while the wireless communication device is turned off, the abbreviated startup sequence module turns on the memory, I/O unit, and processing unit, so as to generate the default emergency message and communicate the default emergency message via said I/O unit over the communications network to the default network, without turning on full functionalities of the wireless communication device;
illuminate one or more of the at least one illumination device on the wireless communication device to notify the user that the emergency message was sent; and
display at least one of a white text against a black background or a white graphic against a black background on the electronic display to notify the user that the emergency message was sent.
2. The wireless communications device according to claim 1, wherein the data representative of the emergency message includes at least two of text message data, prerecorded speech data, email message data, instant message data, and data for speech synthesis communication.
3. The wireless communications device according to claim 2, wherein said user interface includes at least one preference selection to enable the user to select which of the at least two emergency messages to generate and communicate in response to the user requesting to send an emergency message.
4. The wireless communications device according to claim 1, wherein said user interface includes an emergency message button that, when activated to indicate a user request, causes said processing unit to generate and communicate the default emergency message using a communications protocol available to be used to communicate a type of message of which the default emergency message is classified.
5. The wireless communications device according to claim 4, wherein the communications protocol is short message service and the default emergency message is a text message.
6. The wireless communications device according to claim 4, wherein the emergency message button is a hard-button.
7. The wireless communications device according to claim 1, wherein said processing unit is further configured to speech synthesize data of the default emergency message to notify an operator at the PSAP of an emergency situation.
8. The wireless communications device according to claim 1, wherein said processing unit is further configured to include geographic coordinates of a current location of the wireless communications device in the default emergency message.
9. The wireless communications device according to claim 8, wherein said processing unit is further configured to communicate the default emergency message without the geographic coordinates if not available when the default emergency message is generated and, when available, generate and communicate another default emergency message with the geographic coordinates.
10. A method for communicating an emergency message from a wireless communications device to a public safety answering point (PSAP), wherein said wireless communications device comprises a memory, an input/output (I/O) unit, a processing unit, an electronic display, at least one illumination device, and an abbreviated startup sequence module in communication with said memory, I/O unit, and processing unit, said method comprising:
storing, in the memory, (i) data representative of a plurality of emergency messages being of different message types and (ii) a network address associated with each emergency message;
in response to a user selecting one of the emergency messages:
reducing, by the processing unit, illumination of the electronic display and the at least one illumination device; and
establishing, by the processing unit, the selected emergency message and associated network address as defaults for communication of the default emergency message to the PSAP over the communications network; and
in response to the user requesting to send an emergency message:
generating, by the processing unit, the default emergency message by using the default network address as an address to which to communicate the emergency message;
communicating, by the processing unit, the default emergency message via said I/O unit over the communications network to the default network address for routing the default emergency message to a PSAP local to the user,
wherein when the user requests to send the emergency message while the wireless communication device is turned off, the abbreviated startup sequence module turns on the memory, I/O unit, and processing unit, so as to generate the default emergency message and communicate the default emergency message via said I/O unit over the communications network to the default network, without turning on full functionalities of the wireless communication device; and
illuminating one or more of the at least one illumination device on the wireless communication device to notify the user that the emergency message was sent; and
displaying at least one of a white text against a black background or a white graphic against a black background on the electronic display to notify the user that the emergency message was sent.
11. The method according to claim 10, wherein storing the data representative of the emergency message includes storing at least two of text message data, prerecorded speech data, email message data, instant message data, and data for speech synthesis communication.
12. The method according to claim 11, further comprising providing a user interface that includes at least one preference selection to enable the user to select which of the at least two emergency messages to generate and communicate in response to the user requesting to send an emergency message.
13. The method according to claim 12, wherein providing a user interface includes providing an emergency message button that, when activated to indicate a user request, causes generating and communicating the default emergency message using a communications protocol available to be used to communicate a type of message of which the default emergency message is classified.
14. The method according to claim 13, wherein communicating the communications protocol includes using short message service to communicate the default emergency message as a text message.
15. The method according to claim 13, wherein providing the emergency message button includes providing a hard-button.
16. The method according to claim 10, further comprising speech synthesizing data of the default emergency message to notify an operator at the PSAP of an emergency situation.
17. The method according to claim 10, further comprising including geographic coordinates of a current location of the wireless communications device in the default emergency message.
18. The method according to claim 17, further comprising communicating the default emergency message without the geographic coordinates if not available when the default emergency message is generated and, when available, generating and communicating another default emergency message with the geographic coordinates.
Patent Citations (124)
| Patent | Date | Inventor | Cited By |
|---|---|---|---|
| US5339351(A) | 1994-08-01 | Hoskinson et al. | Applicant |
| US5379337(A) | 1995-01-01 | Castillo et al. | Examiner |
| US5497149(A) | 1996-03-01 | Fast | Examiner |
| US5555286(A) | 1996-09-01 | Tendler | Applicant |
| US5646987(A) | 1997-07-01 | Gerber et al. | Examiner |
| US5710803(A) | 1998-01-01 | Kowal et al. | Applicant |
| US5936622(A) | 1999-08-01 | Halverson et al. | Applicant |
| US5941930(A) | 1999-08-01 | Morimoto et al. | Applicant |
| US6240285(B1) | 2001-05-01 | Blum et al. | Examiner |
| US6317049(B1) | 2001-11-01 | Toubia et al. | Applicant |
| US6366772(B1) | 2002-04-01 | Arnson | Applicant |
| US6377169(B1) | 2002-04-01 | Yanagisawa | Applicant |
| US6405033(B1) | 2002-06-01 | Kennedy et al. | Applicant |
| US6415018(B1) | 2002-07-01 | Antonucci et al. | Examiner |
| US6424908(B2) | 2002-07-01 | Urban et al. | Applicant |
| US6456695(B2) | 2002-09-01 | Lee | Applicant |
| US6480578(B1) | 2002-11-01 | Allport | Applicant |
| US6526125(B1) | 2003-02-01 | Lindsay et al. | Applicant |
| US6631184(B1) | 2003-10-01 | Weiner | Applicant |
| US6636732(B1) | 2003-10-01 | Boling et al. | Applicant |
| US6690932(B1) | 2004-02-01 | Barnier et al. | Examiner |
| US7026925(B2) | 2006-04-01 | Roche et al. | Examiner |
| US7079627(B2) | 2006-07-01 | Crago et al. | Applicant |
| US7095733(B1) | 2006-08-01 | Yarlagadda et al. | Applicant |
| US7231218(B2) | 2007-06-01 | Diacakis et al. | Applicant |
| US7269413(B2) | 2007-09-01 | Kraft | Applicant |
| US7391784(B1) | 2008-06-01 | Renkel | Applicant |
| US7418087(B2) | 2008-08-01 | Luneau et al. | Applicant |
| US7444238(B1) | 2008-10-01 | Opitz | Applicant |
| US7496189(B2) | 2009-02-01 | Clarisse et al. | Applicant |
| US7679505(B1) | 2010-03-01 | Vallaire | Examiner |
| US7706356(B1) | 2010-04-01 | Olshansky et al. | Applicant |
| US7734019(B1) | 2010-06-01 | Terpstra | Applicant |
| US8364117(B2) | 2013-01-01 | Hawkins | Applicant |
| US8428548(B2) | 2013-04-01 | Ray et al. | Applicant |
| US8472916(B2) | 2013-06-01 | Coppage et al. | Applicant |
| US2001/0003843(A1) | 2001-06-01 | Scepanovic et al. | Examiner |
| US2001/0004588(A1) | 2001-06-01 | Hong | Applicant |
| US2001/0012379(A1) | 2001-08-01 | Amemiya et al. | Applicant |
| US2002/0016189(A1) | 2002-02-01 | Sheynblat et al. | Applicant |
| US2002/0068584(A1) | 2002-06-01 | Gage et al. | Applicant |
| US2002/0136363(A1) | 2002-09-01 | Stumer et al. | Applicant |
| US2003/0063714(A1) | 2003-04-01 | Stumer et al. | Applicant |
| US2003/0109245(A1) | 2003-06-01 | McCalmont et al. | Examiner |
| US2003/0122779(A1) | 2003-07-01 | Martin et al. | Applicant |
| US2003/0133450(A1) | 2003-07-01 | Baum | Applicant |
| US2003/0158668(A1) | 2003-08-01 | Anderson | Examiner |
| US2003/0162554(A1) | 2003-08-01 | Kim | Applicant |
| US2004/0029610(A1) | 2004-02-01 | Ihira et al. | Applicant |
| US2004/0056770(A1) | 2004-03-01 | Metcalf | Examiner |
| US2004/0063439(A1) | 2004-04-01 | Glazko et al. | Applicant |
| US2004/0072583(A1) | 2004-04-01 | Weng | Applicant |
| US2004/0113836(A1) | 2004-06-01 | Rickerson, Jr. | Applicant |
| US2004/0157564(A1) | 2004-08-01 | Murakami et al. | Applicant |
| US2004/0176123(A1) | 2004-09-01 | Chin et al. | Applicant |
| US2004/0185871(A1) | 2004-09-01 | Somani et al. | Applicant |
| US2004/0198329(A1) | 2004-10-01 | Vasa | Applicant |
| US2004/0258216(A1) | 2004-12-01 | Reid | Applicant |
| US2005/0003797(A1) | 2005-01-01 | Baldwin | Applicant |
| US2005/0048947(A1) | 2005-03-01 | Holland et al. | Applicant |
| US2005/0070315(A1) | 2005-03-01 | Rai et al. | Applicant |
| US2005/0085257(A1) | 2005-04-01 | Laird et al. | Applicant |
| US2005/0097380(A1) | 2005-05-01 | Kim | Examiner |
| US2005/0101287(A1) | 2005-05-01 | Jin et al. | Applicant |
| US2005/0111630(A1) | 2005-05-01 | Potorny et al. | Examiner |
| US2005/0169248(A1) | 2005-08-01 | Truesdale et al. | Applicant |
| US2005/0197096(A1) | 2005-09-01 | Yang et al. | Examiner |
| US2005/0201358(A1) | 2005-09-01 | Nelson et al. | Examiner |
| US2005/0209781(A1) | 2005-09-01 | Anderson | Applicant |
| US2005/0239477(A1) | 2005-10-01 | Kim et al. | Examiner |
| US2005/0265326(A1) | 2005-12-01 | Laliberte | Examiner |
| US2005/0277405(A1) | 2005-12-01 | Noguchi | Applicant |
| US2006/0009243(A1) | 2006-01-01 | Dahan et al. | Applicant |
| US2006/0052134(A1) | 2006-03-01 | Sato | Applicant |
| US2006/0056620(A1) | 2006-03-01 | Shingal et al. | Applicant |
| US2006/0133582(A1) | 2006-06-01 | McCulloch | Examiner |
| US2006/0145841(A1) | 2006-07-01 | Daurensan et al. | Applicant |
| US2006/0152373(A1) | 2006-07-01 | King | Examiner |
| US2006/0166685(A1) | 2006-07-01 | Adkins | Applicant |
| US2006/0217105(A1) | 2006-09-01 | Kumar et al. | Applicant |
| US2006/0217136(A1) | 2006-09-01 | Bantukul et al. | Applicant |
| US2006/0219542(A1) | 2006-10-01 | Savir | Applicant |
| US2006/0222151(A1) | 2006-10-01 | Goldman et al. | Examiner |
| US2006/0227122(A1) | 2006-10-01 | Proctor | Applicant |
| US2006/0229100(A1) | 2006-10-01 | Born | Examiner |
| US2006/0238384(A1) | 2006-10-01 | Hess et al. | Applicant |
| US2006/0276168(A1) | 2006-12-01 | Fuller et al. | Applicant |
| US2006/0293024(A1) | 2006-12-01 | Benco et al. | Applicant |
| US2007/0001902(A1) | 2007-01-01 | Kuo et al. | Applicant |
| US2007/0003024(A1) | 2007-01-01 | Olivier et al. | Examiner |
| US2007/0082652(A1) | 2007-04-01 | Hartigan et al. | Applicant |
| US2007/0201391(A1) | 2007-08-01 | Belmonte et al. | Examiner |
| US2007/0201645(A1) | 2007-08-01 | Gass et al. | Applicant |
| US2007/0273519(A1) | 2007-11-01 | Ichikawa et al. | Applicant |
| US2007/0280428(A1) | 2007-12-01 | McClelland | Applicant |
| US2007/0287473(A1) | 2007-12-01 | Dupray | Examiner |
| US2008/0001734(A1) | 2008-01-01 | Stilp et al. | Applicant |
| US2008/0013696(A1) | 2008-01-01 | Motley et al. | Examiner |
| US2008/0057944(A1) | 2008-03-01 | Miriyala et al. | Examiner |
| US2008/0057987(A1) | 2008-03-01 | Landschaft et al. | Applicant |
| US2008/0070553(A1) | 2008-03-01 | Yamakawa et al. | Applicant |
| US2008/0122929(A1) | 2008-05-01 | Chukwu | Applicant |
| US2008/0220715(A1) | 2008-09-01 | Sinha et al. | Examiner |
| US2008/0227427(A1) | 2008-09-01 | Kadavallur et al. | Applicant |
| US2008/0254810(A1) | 2008-10-01 | Fok et al. | Applicant |
| US2008/0273670(A1) | 2008-11-01 | Dickinson | Examiner |
| US2008/0275950(A1) | 2008-11-01 | Jordan | Applicant |
| US2008/0287748(A1) | 2008-11-01 | Sapounas et al. | Applicant |
| US2008/0310850(A1) | 2008-12-01 | Pederson et al. | Applicant |
| US2009/0047924(A1) | 2009-02-01 | Ray et al. | Examiner |
| US2009/0064039(A1) | 2009-03-01 | Lee et al. | Applicant |
| US2009/0121930(A1) | 2009-05-01 | Bennett et al. | Applicant |
| US2009/0131072(A1) | 2009-05-01 | Razdan et al. | Applicant |
| US2009/0144157(A1) | 2009-06-01 | Saracino et al. | Applicant |
| US2009/0149153(A1) | 2009-06-01 | Lee | Applicant |
| US2009/0186596(A1) | 2009-07-01 | Kaltsukis | Examiner |
| US2009/0197567(A1) | 2009-08-01 | Ogram | Applicant |
| US2009/0215428(A1) | 2009-08-01 | Noldus et al. | Applicant |
| US2009/0227225(A1) | 2009-09-01 | Mitchell et al. | Applicant |
| US2009/0233573(A1) | 2009-09-01 | Gray | Applicant |
| US2009/0310602(A1) | 2009-12-01 | Olshansky et al. | Applicant |
| US2010/0098062(A1) | 2010-04-01 | Croak et al. | Applicant |
| US2010/0291894(A1) | 2010-11-01 | Pipes | Applicant |
| US2013/0115909(A1) | 2013-05-01 | Hawkins | Applicant |
Non-Patent Literature (60)
- 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).Applicant
- 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).Applicant
- 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).Applicant
- Dave Ryan & Asher Hazanchuk, “On-Hook & Off-Hook Caller ID Using DSP,” Circuit Cellular INK #83, Jun. 1997 (12 pages).Applicant
- 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).Applicant
- “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).Applicant
- Non-Final Rejection mailed Jan. 19, 2011 for U.S. Appl. No. 11/430,232.Applicant
- Non-Final Rejection mailed Mar. 17, 2011 for U.S. Appl. No. 11/640,714.Applicant
- RCE filed Apr. 4, 2011 for U.S. Appl. No. 11/640,714.Applicant
- Final Rejection mailed Jan. 3, 2011 for U.S. Appl. No. 11/891,784.Applicant
- Non-Final Rejection mailed Mar. 4, 2011 for U.S. Appl. No. 12/257,424.Applicant
- “NENA Recommended Generic Standards for E9-1-1 PSAP Equipment” NENA Technical Reference, NENA-0-001 Issue 2, Mar. 2001.Applicant
- Non-Final Rejection mailed Mar. 28, 2011 for U.S. Appl. No. 12/272,238.Applicant
- Non-Final Rejection mailed Apr. 1, 2011 for U.S. Appl. No. 12/257,655.Applicant
- Non-Final Rejection mailed Mar. 3, 2011 for U.S. Appl. No. 12/257,416.Applicant
- Non-Final Rejection mailed Mar. 17, 2011 for U.S. Appl. No. 12/257,640.Applicant
- Non-Final Office Action date mailed Aug. 3, 2010 for U.S. Appl. No. 11/891,784.Applicant
- Response filed Nov. 2, 2010 for U.S. Appl. No. 11/891,784.Applicant
- U.S. Appl. No. 12/257,674; Notice of Allowance dated Jan. 25, 2012; 7 pages.Applicant
- U.S. Appl. No. 12/257,674; Final Rejection dated Oct. 3, 2011; 15 pages.Applicant
- U.S. Appl. No. 12/257,674; Non-Final Rejection dated Apr. 28, 2011; 14 pages.Applicant
- U.S. Appl. No. 12/257,717; Final Rejection dated Jan. 23, 2012; 16 pages.Applicant
- U.S. Appl. No. 12/257,717; Non-Final Rejection dated Sep. 13, 2011; 14 pages.Applicant
- U.S. Appl. No. 12/257,736; Non-Final Rejection dated Apr. 28, 2011; 15 pages.Applicant
- U.S. Appl. No. 12/257,736; Final Rejection dated Nov. 23, 2011; 17 pages.Applicant
- U.S. Appl. No. 12/257,736; Amendment and Request for Continued Examination dated Feb. 22, 2012; 12 pages.Applicant
- U.S. Appl. No. 12/257,725; Final Rejection dated Jan. 17, 2012; 17 pages.Applicant
- U.S. Appl. No. 12/257,725; Non-Final Rejection dated Jul. 19, 2011; 26 pages.Applicant
- U.S. Appl. No. 12/257,640; Non-Final Rejection dated Jan. 4, 2012; 19 pages.Applicant
- U.S. Appl. No. 12/257,640; Final Rejection dated Aug. 17, 2011; 11 pages.Applicant
- U.S. Appl. No. 12/257,416; Final Rejection dated Jul. 14, 2011; 17 pages.Applicant
- U.S. Appl. No. 12/070,775; Non-Final Rejection dated Jul. 25, 2011; 33 pages.Applicant
- U.S. Appl. No. 12/257,655; Final Rejection dated Sep. 16, 2011; 20 pages.Applicant
- U.S. Appl. No. 12/257,655; Amendment and Request for Continued Examination dated Dec. 16, 2011; 14 pages.Applicant
- U.S. Appl. No. 12/257,687; Non-Final Rejection dated Apr. 9, 2012; 16 pages.Applicant
- U.S. Appl. No. 12/257,687; Non-Final Rejection dated May 10, 2011; 14 pages.Applicant
- U.S. Appl. No. 12/257,687; Final Rejection dated Sep. 29, 2011; 12 pages.Applicant
- U.S. Appl. No. 12/070,775; Final Rejection dated May 14, 2012; 27 pages.Applicant
- U.S. Appl. No. 12/257,674; Non-Final Rejection dated Jul. 20, 2012; 21 pages.Applicant
- U.S. Appl. No. 12/257,640; Final Rejection dated May 2, 2012; 18 pages.Applicant
- U.S. Appl. No. 12/257,416; Final Rejection dated Jun. 13, 2012; 38 pages.Applicant
- U.S. Appl. No. 12/257,655; Non-Final Rejection dated Jul. 17, 2012; 26 pages.Applicant
- U.S. Appl. No. 12/070,775; Issue Notification dated Jan. 9, 2013; 1 page.Applicant
- U.S. Appl. No. 12/257,640; Non-Final Rejection dated Dec. 5, 2012; 23 pages.Applicant
- U.S. Appl. No. 12/257,655; Final Rejection daed Jan. 2, 2013; 18 pages.Applicant
- U.S. Appl. No. 12/257,687; Notice of Allowance dated Feb. 20, 2013; 20 pages.Applicant
- U.S. Appl. No. 12/257,687; Notice of Panel Decision on Pre-Appeal Brief Review dated Dec. 14, 2012; 2 pages.Applicant
- U.S. Appl. No. 12/257,717; Notice of Allowance dated Feb. 14, 2013; 35 pages.Applicant
- U.S. Appl. No. 12/257,725; Notice of Allowance dated Dec. 24, 2012; 24 pages.Applicant
- U.S. Appl. No. 12/070,775; Notice of Allowance dated Sep. 12, 2012; 24 pages.Applicant
- U.S. Appl. No. 12/257,674; Final Rejection dated Nov. 5, 2012; 17 pages.Applicant
- U.S. Appl. No. 12/257,687; Final Rejection dated Aug. 31, 2012; 19 pages.Applicant
- U.S. Appl. No. 12/257,717; Non-Final Rejection dated Aug. 16, 2012; 42 pages.Applicant
- U.S. Appl. No. 12/257,416; Non Final Office Action dated May 22, 2013; 40 pages.Applicant
- U.S. Appl. No. 12/257,640; Final Rejection dated Apr. 15, 2013; 21 pages.Applicant
- U.S. Appl. No. 12/257,655; Notice of Allowance dated Apr. 16, 2013; 15 pages.Applicant
- U.S. Appl. No. 12/257,674; Notice of Allowance dated Apr. 3, 2013; 15 pages.Applicant
- U.S. Appl. No. 12/257,725; Issue Notification dated Apr. 3, 2013; 1 page.Applicant
- U.S. Appl. No. 13/712,669; Non-Final Rejection dated Mar. 27, 2013; 34 pages.Applicant
- U.S. Appl. No. 12/257,687; Issue Notification dated Jun. 5, 2013; 1 page.Applicant