Wireless communications devices, such as cellular phones, pagers, PDAs, and many other similar devices are prolific in modern society. One commonality among most of the devices is the use of batteries to power the devices. Batteries, by their very nature, discharge with use and at some point the battery does not contain sufficient charge to power the device. Currently, there are ways to determine battery life remaining for a device. Additionally, the devices often include a display showing the amount of time or a percentage of the charge of the battery remaining.
Users often ignore warnings indicating that there is low power remaining until a device ceases to work. If the user has no alternative way to power the device until the battery gets replaced or recharged, the device becomes useless. In the event of an emergency or otherwise, the device will not allow even a brief communication until the battery is replaced or another power source is provided.
In order to provide an emergency power supply to a wireless communications device, a secondary battery may be provided for operating emergency functions of a wireless communications device. In the case where only a single battery is present, a voltage threshold may be deterrmned and utilized to implement a battery cut off, thereby providing reserve backup power for use in emergency situations or upon being overridden by a user.
One embodiment includes a wireless communications device including electronics configured to provide communications over a communications network, a primary battery configured to power the electronics during a power-on mode, and a secondary battery configured to power the electronics in response to an emergency signal being received while the electronics are in a power-off mode.
Another embodiment of a method for establishing a voltage threshold at which to turn off electronics of a wireless communications device includes determining a power threshold level at which a device is to be shut off when a battery of the device reaches or drops below the power threshold level. The determined power threshold level may be offset. The amount of power remaining for the battery in the communications device may be measured. The wireless communications device may be shut off based on the offset power threshold level.
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:
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.
There are different configurations of PSAPs 104, where different PSAPs have different capabilities. Some PSAPs 104 ate compatible with E911 Phase I, while others are compatible with E911 Phase II, as is commonly known in the art. For less advanced PSAPs 104, only basic information, such as the telephone number of the caller and a name registered may be communicated. More advanced PSAPs 104 include much greater detail, where some are capable of determining coordinates and physical addresses of mobile phone users.
An emergency text messaging switch 208 may be provided for initiating an emergency message from the wireless communications device 102. The emergency text messaging switch 208 may be a hard-button, such as a traditional key on a keypad, or may be a soft-button, such as found on a device with a touch screen. When the emergency text messaging switch 208 is depressed or otherwise activated, an emergency text message may be generated and communicated to a PSAP. A more detailed description of the generation and communication is described below in greater detail.
Memory 202 may also be located within the wireless communications device 102 for storing data being processed by the processor 206. The memory 202 may be removable, such as flash memory, or fixedly attached within the wireless communications device 102, such as SDRAM, or any other memory configured to store data within the wireless communications device 102. Within the memory 210 may be an offset 212 representing an amount of power that a user or other entity decides is an appropriate margin above a traditional battery power level shutoff 214. The offset 212 may be an adder (e.g., 3%), a multiplier (e.g., 1.5), or any other value used to modify or adjust an existing voltage, current or battery power level shutoff 214. In an alternative embodiment, a set power level, not specifically tied to the battery power level shutoff 214, may also be used for the offset 212. The battery power level shutoff 214 may be configured to represent the power level at which the power remaining in a battery is not sufficient to power the wireless communications device 102. The battery power level shutoff 214 may be determined based on continuously monitoring the power level or may be determined in advance and preprogrammed into the wireless communications device 102. Once the battery power level shutoff 214 has been set, calculations using the offset 212 and the battery power level shutoff 214 may be made to determine when to power off the wireless communications device 102 in order to reserve enough power in the battery for at least one emergency communication to be communicated. The offset 212 and battery power level shutoff 214 is described below in greater detail in
An input/output (I/O) unit 215 may be provided for communicating emergency messages as well as providing for the traditional functionalities of the wireless communication device 102, as commonly known in the art. The I/O unit 215 may additionally include a transceiver (not shown) for transmitting an emergency message to a PSAP or remote location and for receiving and sending communications as commonly performed by a wireless communications device 102.
A primary battery 216 may be included to provide power to the wireless communications device 102. In one embodiment, only one battery, the primary battery 216, may be present. If only the primary battery 216 is present, the wireless communications device 102 may be configured to power down according to calculations using the offset and battery power level shutoff in order to reserve power in the event the wireless communications device 102 is needed for one or more emergency messages to be communicated.
In another embodiment, an optional secondary battery 218 may be present to provide power to the wireless communications device 102 during emergency situations in case the primary battery 216 is out of charge. The presence of the optional secondary battery 218 may obviate the use of the offset 212 as described previously. If an optional secondary battery 218 is present, the battery power level shutoff 210 may be the correctional point (i.e., without offset) at which the wireless communications device 102 is configured to shut down. In one embodiment, the secondary battery 218 may be used upon depletion of the primary battery 216 and in response to a request for communicating an emergency message. Alternatively, the secondary battery 218 may be used in any number of other circumstances in which the primary battery 216 is not able to provide power and the device is needed.
A maintaining emergency functions module 236 may be configured to provide an emergency reserve of battery power for the wireless communications device 102. Either independently or by using the battery status module 232, as well as the battery threshold module 234, the maintaining emergency functions module 236 may determine how much charge is necessary to provide the wireless communications device 102 with enough power to communicate at least one emergency communications message. Using the determined charge information, the maintaining emergency functions module 236 may attempt to reserve enough battery power for communicating at least one emergency message to a PSAP when the wireless device is configured with a single battery.
Depending upon the status or mode of the device at the time an emergency message request is made, the wireless communications device may operate differently. There are at least two modes for the wireless communications device 102, a power-on mode and a power-off mode. In the power-on mode, the wireless communications device is currently on, and in the power-off mode, the wireless communications device is currently off. While in the power-on mode, when it is determined that the power level has crossed a set power threshold, the maintaining emergency functions module 236 may be configured to automatically place the wireless communications device in power-off mode. Accordingly, the power-off mode may occur either manually, such as when a user chooses to turn off the device, or automatically, such as when the maintaining emergency functions module 236 places the device in power-off mode. In one embodiment, the maintaining emergency functions module 236 may be configured to allow a user to override the power reserve and use the remaining battery life for actions other than emergency communications.
A generate emergency message module 238 may also be present within the wireless communications device 102 for generating and enabling the commurucation of an emergency message from the wireless communications device. The generate emergency message module 238 may be initiated by a “hard-key” or “hard-button” configured to initiate an emergency message or other emergency signal by the wireless communications device 102. The hard-key may be a dedicated button configured to initiate the emergency communication, or may be a key with multiple functions, where one of the functions initiates the emergency communication. For example, an On/Off button may be configured to (i) power on or off the device, (ii) initiate the generate emergency message module 238 if pressed in a unique pattern or some other variation. In one embodiment, a soft-key, such as an icon on a touch screen enabled device, may also be configured to cause the generate emergency message 238 to generate an emergency message 238 to generate an emergency message.
It should be understood that different wireless communications devices may have different power requirements. If there is a backup battery present within the wireless communications device 102, rather than using an offset as in the single battery configuration, the battery may be configured to shutoff at the power threshold level V at step 254. Because of the presence of a backup battery, the entire charge remaining in a primary battery may be used for normal functions of the wireless communications device 102. In the event an emergency communications message becomes necessary to be communicated, the backup battery may be used to power the wireless communications device 102.
The primary battery 262 may be connected to an on/off button 266, with the on/off button 266 being responsible for sending an on/off signal 270 through a switch 268 to a processor 272, to power on and off the wireless communications device. When turned on, the primary battery 262 may be used to power normal operating functions of the wireless communications device.
In an alternative embodiment, the on/off button 266 may also function as an emergency communication hard key. In the event that the on/off button 266 also functions as the emergency communication hard key, a distinctive pattern or predefined sequence for depressing the on/off button 266 may be used to distinguish between a desire to power on or off the device or to send an emergency communications message. Other hard keys (not shown) on the wireless communications device may similarly perform multiple functions and may be used in place of the on/off button 266 as an emergency communication hard key.
The secondary battery 264 may be connected to an emergency communication hard key 274. The emergency communication hard key 274 may be a button with the sole function of initiating an emergency communication 278 or may be a multi-purpose button, as described previously. In one embodiment, when the emergency communication hard key 274 is activated, the secondary battery 264 may power the wireless communications device, in whole or in part, and send the emergency communication 278 through a switch and on to the processor 272. In another embodiment, the secondary battery 264 is limited to powering the wireless communications device when the wireless communications device is in the power-off mode. In other words, the primary battery 262 would continue to power the wireless communications device and would be responsible for sending the emergency communication if signaled to do so while the device is in the power-on mode.
In one embodiment, the emergency communication hard key 274 may be illuminated by a light source that illuminates the emergency communication hard key 274 with less light than other hard-keys. If keys on a wireless communications device are ordinarily lit by an LED and powered by the primary battery, when the wireless communications device is powered off, none of the keys would ordinarily be lit. In one embodiment, the emergency communication hard key 274 may be lit separately, whether powered on or powered off with an LED light that releases less light than the other keys. Alternatively, illumination may be provided with the same or more light than normally provided for other keys. It is important to note that although not depicted in the figure, the illumination of the emergency communication hard key 274 may be provided by either the primary or the secondary battery.
If the power threshold level setting 308 is currently at 15%, the wireless communications device may be configured to power down the device with 15% of the battery level remaining. By definition, the power threshold level is the point at which there would no longer be enough available battery power to power the wireless communications device, including communicating an emergency message. A multiplier 310, such as 1.5, as described previously, may be selected for the offsetted power threshold level. Alternatively, an adder 312, such as 3% may be added to the power threshold level 308 for determining the offsetted power threshold level. Although described as using the power threshold level, a voltage threshold level or current threshold level may equivalently be utilized to manage battery shutoff and offset levels.
In step 404, a voltage threshold of a battery of the wireless communications device may be established that, when measured, causes the electronics to turn off so as to ensure that the wireless communications device has sufficient power to perform at least one powered-down emergency communication if activated by a user. Using information obtained in step 402, the voltage threshold of the battery may be established in step 404. The voltage threshold may also allow for any number of powered-down emergency communications. The number may be established by default or by a user of the device.
In step 406, a turn-off voltage threshold parameter may be set in the wireless communications device based on the established voltage threshold that causes the wireless communications device to turn off at a certain battery voltage level to ensure sufficient battery power remains to perform at least one powered-down emergency communication. The established voltage threshold may be set as a parameter within the communications device, with the ability to adjust or eliminate the turn-off voltage threshold parameter made possible by the wireless communications device.
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 rmmediately 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 | Yarlagadda et al. | Aug 2006 | B1 |
7231218 | Diacakis et al. | Jun 2007 | B2 |
7269413 | Kraft | Sep 2007 | B2 |
7391784 | Renkel | Jun 2008 | B1 |
7418087 | Luneau et al. | Aug 2008 | B2 |
7444238 | Opitz | Oct 2008 | B1 |
7496189 | Clarisse et al. | Feb 2009 | B2 |
7679505 | Vallaire | Mar 2010 | B1 |
7706356 | Olshansky et al. | Apr 2010 | B1 |
7734019 | Terpstra | Jun 2010 | B1 |
8364117 | Hawkins | Jan 2013 | B2 |
8428548 | Ray et al. | Apr 2013 | B2 |
8472916 | Coppage et al. | Jun 2013 | B2 |
8489062 | Ray et al. | Jul 2013 | B2 |
20010003843 | Scepanovic et al. | Jun 2001 | A1 |
20010004588 | Hong | Jun 2001 | A1 |
20010012379 | Amemiya et al. | Aug 2001 | A1 |
20020016189 | Sheynblat et al. | Feb 2002 | A1 |
20020068584 | Gage et al. | Jun 2002 | A1 |
20020136363 | Stumer et al. | Sep 2002 | A1 |
20030063714 | Stumer et al. | Apr 2003 | A1 |
20030109245 | McCalmont et al. | Jun 2003 | A1 |
20030122779 | Martin et al. | Jul 2003 | A1 |
20030133450 | Baum | Jul 2003 | A1 |
20030162554 | Kim | Aug 2003 | A1 |
20040029610 | Ihira et al. | Feb 2004 | A1 |
20040056770 | Metcalf, Jr. | 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 P S et al. | Sep 2006 | A1 |
20060217136 | Bantukul et al. | Sep 2006 | A1 |
20060219542 | Savir | Oct 2006 | A1 |
20060222151 | Goldman et al. | Oct 2006 | A1 |
20060227122 | Proctor | Oct 2006 | A1 |
20060229100 | Born | Oct 2006 | A1 |
20060238384 | Hess et al. | Oct 2006 | A1 |
20060276168 | Fuller et al. | Dec 2006 | A1 |
20060293024 | Benco et al. | Dec 2006 | A1 |
20070001902 | Kuo et al. | Jan 2007 | A1 |
20070003024 | Olivier et al. | Jan 2007 | A1 |
20070082652 | Hartigan et al. | Apr 2007 | A1 |
20070201391 | Belmonte et al. | Aug 2007 | A1 |
20070201645 | Gass et al. | Aug 2007 | A1 |
20070273519 | Ichikawa et al. | Nov 2007 | A1 |
20070280428 | McClelland | Dec 2007 | A1 |
20070287473 | Dupray | Dec 2007 | A1 |
20080001734 | Stilp et al. | Jan 2008 | A1 |
20080013696 | Motley et al. | Jan 2008 | A1 |
20080057944 | Miriyala et al. | Mar 2008 | A1 |
20080057987 | Landschaft et al. | Mar 2008 | A1 |
20080070553 | Yamakawa et al. | Mar 2008 | A1 |
20080122929 | Chukwu | May 2008 | A1 |
20080220715 | Sinha et al. | Sep 2008 | A1 |
20080227427 | Kadavallur et al. | Sep 2008 | A1 |
20080254810 | Fok et al. | Oct 2008 | A1 |
20080273670 | Dickinson | Nov 2008 | A1 |
20080275950 | Jordan | Nov 2008 | A1 |
20080287748 | Sapounas et al. | Nov 2008 | A1 |
20080310850 | Pederson et al. | Dec 2008 | A1 |
20090047924 | Ray et al. | Feb 2009 | A1 |
20090064039 | Lee et al. | Mar 2009 | A1 |
20090121930 | Bennett et al. | May 2009 | A1 |
20090131072 | Razdan et al. | May 2009 | A1 |
20090144157 | Saracino et al. | Jun 2009 | A1 |
20090149153 | Lee | Jun 2009 | A1 |
20090186596 | Kaltsukis | Jul 2009 | A1 |
20090197567 | Ogram | Aug 2009 | A1 |
20090215428 | Noldus et al. | Aug 2009 | A1 |
20090227225 | Mitchell et al. | Sep 2009 | A1 |
20090233573 | Gray | Sep 2009 | A1 |
20090310602 | Olshansky et al. | Dec 2009 | A1 |
20100098062 | Croak et al. | Apr 2010 | A1 |
20100291894 | Pipes | Nov 2010 | A1 |
20130115909 | Hawkins | May 2013 | A1 |
Entry |
---|
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/pp./products/cid.htm, downloaded from the World Wide Web on Apr. 24, 2006 (2 pages). |
“AT & T Wireless Unleashes the First and Only Wireless Messaging Device”, PhysOrg.com, Sep. 30, 2004; available online at URL: <http://www.physorg.com/news1392.html> (12 pages). |
Non-Final Office Action date mailed Aug. 3, 2010 for U.S. Appl. No. 11/891,784. |
Response filed Nov. 2, 2010 for U.S. Appl. No. 11/891,784. |
Non-Final Rejection mailed Jan. 19, 2011 for U.S. Appl. No. 11/430,232. |
Non-Final Rejection mailed Mar. 17, 2011 for U.S. Appl. No. 11/640,714. |
RCE filed on Apr. 4, 2011 for U.S. Appl. No. 11/891,784. |
Final Rejection mailed Jan. 3, 2011 for U.S. Appl. No. 11/891,784. |
Non-Final Rejection mailed Mar. 4, 2011 for U.S. Appl. No. 12/257,424. |
“NENA Recommended Generic Standards for E9-1-1 PSAP Equipment” NENA Technical Reference. NENA-04-001 Issue 2, Mar. 2001. |
Non-Final Rejection mailed Mar. 28, 2011 for U.S. Appl. No. 12/272,238. |
Non-Final Rejection mailed Mar. 17, 2011 for U.S. Appl. No. 12/257,640. |
Non-Final Rejection mailed Mar. 3, 2011 for U.S. Appl. No. 12/257,416. |
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/070,775; Non-Final Rejection dated Jul. 25, 2011; 33 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/257,687; Non-Final Rejection dated Apr. 9, 2012; 16 pages. |
U.S. Appl. No. 12/257,687; Non-Final Rejection dated May 10, 2011; 14 pages. |
U.S. Appl. No. 12/257,687; Final Rejection dated Sep. 29, 2011; 12 pages. |
U.S. Appl. No. 12/257,416; Final Rejection dated Jul. 14, 2011; 17 pages. |
U.S. Appl. No. 12/070,775; Notice of Allowance dated Sep. 12, 2012; 24 pages. |
U.S. Appl. No. 12/257,674; Final Rejection dated Nov. 5, 2012; 17 pages. |
U.S. Appl. No. 12/257,687; Final Rejection dated Aug. 31, 2012; 19 pages. |
U.S. Appl. No. 12/257.717; Non-Final Rejection dated Aug. 16, 2012; 42 pages. |
U.S. Appl. No. 12/257,836; Non-Final Rejection dated Sep. 12, 2012; 25 pages. |
U.S. Appl. No. 12/070,775; 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,836; Final Rejection dated May 14, 2012; 26 pages. |
U.S. Appl. No. 12/070,775; Issue Notification dated Jan. 9, 2013; 1 page. |
U.S. Appl. No. 12/257,640; Non-Final Rejection dated Dec. 5, 2012; 23 pages. |
U.S. Appl. No. 12/257,725; Notice of Allowance dated Dec. 24, 2012; 24 pages. |
U.S. Appl. No. 12/257,687; Notice of Allowance dated Feb. 20, 2013; 20 pages. |
U.S. Appl. No. 12/257,687; Notice of Panel Decision on Pre-Appeal Brief Review dated Dec. 14, 2012; 2 pages. |
U.S. Appl. No. 12/257,717; Notice of Allowance dated Feb. 14, 2013; 35 pages. |
U.S. Appl. No. 12/257,836; Issue Notification dated Jun. 26, 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. |
U.S. Appl. No. 12/257,674; Notice of Allowance dated Apr. 3, 2013; 15 pages. |
U.S. Appl. No. 12/257,725; Issue Notification dated Apr. 3, 2013; 1 page. |
U.S. Appl. No. 12/957,640; Final Rejection dated Apr. 15, 2013 ; 21 pages. |
U.S. Appl. No. 12/257,416; Non Final Office Action dated May 22, 2013; 40 pages. |
U.S. Appl. No. 12/257,687; Issue Notification dated Jun. 5, 2013; 1 page. |
Number | Date | Country | |
---|---|---|---|
20100003950 A1 | Jan 2010 | US |
Number | Date | Country | |
---|---|---|---|
61078123 | Jul 2008 | US |