The National Telecommunications Information Administration (NTIA) is the executive branch's advisory agency on telecommunications issues. In the early 1980s, this agency proposed a plan to raise awareness of a single emergency telephone number to the general public. From that program, the National Emergency Number Association (NENA), a non-profit organization, was created. NENA has since become a leading organization to improving technology and developing guidelines for 9-1-1 (“911”) telephone calls (i.e., emergency telephone calls) to improve response by emergency rescue teams.
Telecommunications has been changing rapidly over the past several years, primarily since the development and growth of the mobile telephone industry and the Internet. New forms of telecommunications have been developing as well Tradition telecommunications were performed over the public switch telephone network (PSTN). A system to maintain location of subscribers of telecommunications companies operating on the PSTN was developed. Determining the location of subscribers of the telecommunication companies was relatively easy as the locations were known by the telecommunications companies or carriers due to installing the telephones, establishing billing, or otherwise. With the new forms of telecommunications, these telephones and devices (e.g., Internet Protocol (IP) telephones or voice over IP (VoIP) telephones) operate over the Internet and have subscriptions with non-traditional telecommunications carriers, such as Vonage®. When VoIP telephones are not purchased from the telecommunications carriers, but rather purchased from a retail store, there is no record of physical location where the VoIP telephone is being used. Not leaving location information for the VoIP telephone is a problem for 911 telephone calls as the location information cannot automatically be communicated to a 911 operator at a public-safety answering point.
In response to the problem of the VoIP telephones not having addresses associated with them for 911 telephone calls, via databases or otherwise, NENA has encouraged the telecommunications industry to develop a system to provide public-safety answering points (PSAPs) with location information for non-traditional telephone calls through the use of enhanced 911 (“E-911”). To accommodate the need to provide location information to public-safety answering points during E-911 telephone calls, a number of solutions have been developed by different telecommunications groups.
In operation, when a user places an E-911 telephone call using the VoIP telephone 106, a signal 120, including a telephone number associated with a VoIP telephone 106, is communicated to the call server 108. The call server 108, in response, communicates the signal 120 to the VoIP position center 118. In response, the VoIP position center 118 communicates a signal 122, including the telephone number, emergency service routing key (ESQK), which causes the call to be routed to a local selective router and emergency service query key (ESQK), which causes the correct location information to be queried for display at the public-safety answering point 114 to the call server 108. The call server 108, in turn, communicates the signal 122 to the emergency service gateway 110. Based on the emergency service routing key, the emergency service gateway 110 communicates the signal 122 to the appropriate selective router 112 in an area near the VoIP telephone 106. The selective router 112 determines which public-safety answering point 114 is physically located near the VoIP telephone 106 and communicates the telephone number and emergency service query key in a signal 124 to the public-safety answering point 114.
The public-safety answering point 114 communicates the emergency service query key in a signal 126 to the automated location identifier 116, which, in turn, communicates the emergency service query key to the VoIP positioning center 118. The VoIP positioning center 118 looks up the address associated with the VoIP telephone 116 in a database using the emergency service query key and communicates the location, which may include an address, apartment, office number, or other information associated with the VoIP telephone 106, in a signal 128 to the automated location identifier 116. The automated location identifier 116 communicates the location information to the public-safety answering point 114 for display to an operator who answers the telephone call from the user of the VoIP telephone 106. The operator is then able to determine the specific location of the VoIP telephone 106 and communicate that information to emergency services, such as firefighters and policemen, who respond to the E-911 telephone calls.
There are problems that exist with the configuration of system 100. First, the VoIP positioning center 118 is a database that is very expensive to create and maintain. Second, communications between the automated location identifier 116 and VoIP positioning center 118 require two dedicated trunks, one for communications from the automated location identifier 116 to the VoIP positioning center 118 and one from the VoIP positioning center 118 to the automated location identifier 116. It is understood that the operation for deploying and maintaining these trunks is expensive. Third, entering information into a database located at the VoIP positioning center 118 is complicated. For at least these reasons, there is a need for an improved system for maintaining location information associated with VoIP telephones.
To overcome the problems of existing network configurations for handling addressed based E-911 telephone calls from VoIP telephones, the principles of the present invention provide for a network configuration that is less expensive and easier to manage than current systems. The principles of the present invention use a database for storing location information associated with VoIP telephones. In one embodiment, the database used to store the location information is a calling name database. Alternatively, the database may be a third party database. To collect the location information, an interactive voice response system may be used in conjunction with a calling name database, which is generally used for caller identification (ID). Upon a public-safety answering point receiving an E-911 telephone call from a VoIP telephone, the location information may be requested by the public-safety answering point from the database.
One embodiment of a system configured in accordance with the principles of the present invention includes a system for providing location information to a public-safety answering point during an E-911 telephone call by a person using a voice over Internet Protocol (VoIP) telephone. The system may include a database configured to store location information associated with subscribers of a VoIP telephone service. A database access server may be in communication with the database. A media gateway and emergency service gateway may be in communication with an Internet protocol (IP) network A telephone switch may be in communication with the database access server, media gateway, and emergency service gateway. A selective router may be in communication with the telephone switch. A public-safety answering point may be in communication with the selective router. A call server may be in communication with a VoIP telephone and be configured to (i) receive a telephone call from a VoIP telephone, (ii) determine if the call is a non-emergency call or an E-911 call, and (iii) determine if the call is a non-emergency call, and, if so, then route the call to the media gateway, otherwise, route the call to the emergency service gateway to cause the VoIP telephone to be in communication with the public-safety answering point. In response to receiving the E-911 call, the public-safety answering point may further be configured to (i) request location information associated with the VoIP telephone from the database via the telephone switch and database access server, (ii) receive the location information associated with the VoIP telephone, and (iii) display the location information.
A method operating in accordance with the principles of the present invention may include receiving an E-911 telephone call from a VoIP telephone. Location information associated with the VoIP telephone stored in a database may be requested. The location information may be received in a signal formatted substantially the same as a signal format for communicating caller identification information. The location information may be displayed at a public-safety answering point. In one embodiment, the location information may be displayed on a video display (e.g., computer screen). Alternatively, the location information may be displayed on a telephone display.
In another embodiment, a system for providing location information to a public-safety answering point during an E-911 telephone call by a person using a voice over Internet Protocol (VoIP) telephone may be provided. The system may include a database access server in communication with an Internet protocol (IP) network and configured to (i) receive a request from a public-safety answering point in communication with the public switched telephone network (PSTN) to obtain location information of a user of a VoIP telephone, (ii) request location information of the VoIP telephone from a database, (iii) receive the location information from the database, and (iv) communicate the location information to the public-safety answering point.
A more complete understanding of the method and apparatus of the present invention may be obtained by reference to the following Detailed Description when taken in conjunction with the accompanying Drawings wherein:
A service control point 202, which is operated by a telecommunications carrier, includes a calling name service 204 and name database 206. The calling name service 204 may be a server that provides an interface with the name database 206, where the name database 206 stores names and telephone numbers that are typically used for type II caller ID purposes, as understood in the art.
As understood in the art, signaling system 7 (SS7) is a network architecture for performing out-of-band signaling in support of the call-establishment, billing, routing, and information-exchange functions of the public switched telephone network (PSTN). A signal transfer point (STP) 208, which is a switch that relays messages between network switches and databases, routes SS7 messages to the correct outgoing signaling links based on SS7 message address fields. A signal switching point (SSP) 210 is in communication with the PSTN 104 and STP 208. The SSP 210 is a telephone switch that interconnects SS7 links and performs call processing on telephone calls that originate, tandem, or terminate at the SSP 210. The SSP 210 generates SS7 messages to transfer call-related information to other SSPs or to query the SCP 202 for routing instructions.
The service control point 202 may be in communication with a third party name database 212. The third party name database 212 may store names and telephone numbers of subscribers of other service providers for performing caller ID functionality. This third party name database 212 is typically managed by a third party, which may be a service provider other than a telecommunications carrier.
As described in connection with
Connected to the PSTN is a class 5 switch 310 that is in communication with a selective router 312. The selective router 312, as previously described, may be one of many located in the United States and be located in a local region as the VoIP telephone 106. The public-safety answering point 118, which, too, may be in the local region of the VoIP telephone 106, may be in communication with the selective router 312. The database access provider 214 may be in communication with both the IP network 102 and PSTN 104 and communicate with the third party database 212. In one embodiment, the third party database 212 may include an interactive voice response system (IVR) 316 that is utilized to prompt a user with voice commands to enter location information (e.g., address) using a voice or keypad response.
In operation, a user may register location information associated with the VoIP telephone 106 by calling a registration telephone number. The telephone call may be communicated using IP data packets 318. The registration telephone number may be associated with the third party database 212 so that information submitted via the telephone call can be input and stored in the third party database 212. In one embodiment, the registration telephone number calls the database access provider 214 via the IP network 102. The interactive voice response system 316 may be accessed and the user may respond to one or more prompts to speak or type via a keypad the user's location information. For example, the user may be prompted to speak his or her street address, street name, city, or any other information that would be helpful in an emergency situation for rescuers to locate a victim. As shown, a user may register the VoIP telephone 106 by calling the third party database 212 via the L2 switch 302, call server 304, database access provider 214, and third party database 212. Alternatively, the call server may route the call via the media gateway 308 and class 5 switch 310 to the database access provider 214. It should be understood that rather than the database access provider 214 being the intermediary to the third party database 212, another intermediary, such as a server at a telecommunications carrier. It should further be understood that if a subscriber of the VoIP telephone 106 purchases the telephone directly from the telecommunications carrier, that the telecommunications carrier may populate the third party database 212 with the location information of the VoIP telephone, if provided by the subscriber.
While the subscriber of the VoIP telephone 106 may use an interactive voice response system 316 to register location information into the third party database 212, it should be understood that a website (not shown) may be established to allow the subscriber to enter the location information via a graphical user interface (GUI). The website may be operated by the database access provider 214 or another operator. Any other method for populating the third party database 212 with location information of the VoIP telephone 106 may be performed.
The IP data packets 402 may include a query key or other identifier that may be used by the public-safety answering point 118 to request location information of the VoIP telephone 106 from the third party database 212. The public-safety answering point 118, in response, may request the location information from the third party database 212 by communicating a signal 406 through the class 5 switch 310. The class 5 switch 310 may convert the signal 406 to data packets 408 to be communicated to the third-party database 212 via the database access provider 212. In response to the request, the third party database 212 may look-up the location information associated with the VoIP telephone 106 and communicate the location information back to the class 5 switch 310, which, in turn, converts the location information into a frequency shift keying signal, the same or similar to signal 404, or other signal compatible with the telecommunications equipment at the public-safety answering point 118 for communication to the public-safety answering point 118.
More specifically, the address parameter may be ASCII equivalent of the characters that represent the address associated with the calling access line. The character subfields may be coded in 8 bit ASCII (no parity) with one octet per character. No characters (e.g., spaces, commas, periods, etc.) are assumed and the relevant characters are sent. The first character of the address may be transmitted first and subsequent characters may be transmitted in order until the last character is transmitted. For example, the address “12345 John Rd” may be coded over 12 octets as 00110001, 00110010, 00110011, 00110100, 00110101, 01001010, 01001111, 01001000, 01001110, 00100000 (space), 01010010, and 01000100. If the street number plus the street name combined is more than 14 characters, then the characters after 14 characters are ignored by the system. If the street number plus the street name combined occupies 11 characters then one space may be put before the street name, one space before the street type, and another space before the street code. If the street number plus the street name combined occupies 12 characters, then one space may be put before the street name and another space may be put before the zip code. If the street number plus the street name combined occupies 13 characters, then one space may be put before the street name. To minimize the total length of the displayed address message on the public-safety answering point side, no more than one space is put before the street name, street type, or zip code. If the street number plus the street name combined occupies 14 characters, then no spaces are included. Additional description of the signaling structure 500 and communication thereof is described in co-pending patent application having Ser. No. 11/430,232 filed May 8, 2006, which is incorporated herein by reference in its entirety.
The previous detailed description of a small number of embodiments for implementing the invention is not intended to be limiting in scope. One of skill in this art will immediately envisage the methods and variations used to implement this invention in other areas than those described in detail. The following claims set forth a number of the embodiments of the invention disclosed with greater particularity.
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 |
6137877 | Robin et al. | Oct 2000 | A |
6240285 | Blum et al. | May 2001 | B1 |
6317049 | Toubia et al. | Nov 2001 | B1 |
6366772 | Arnson | Apr 2002 | B1 |
6415018 | Antonucci et al. | Jul 2002 | B1 |
6480578 | Allport | Nov 2002 | B1 |
6526125 | Lindsay et al. | Feb 2003 | B1 |
6591112 | Siccardo et al. | Jul 2003 | B1 |
6642844 | Montague | Nov 2003 | B2 |
6678357 | Stumer et al. | Jan 2004 | B2 |
6690932 | Barnier et al. | Feb 2004 | B1 |
6771163 | Linnett et al. | Aug 2004 | B2 |
6839022 | Benco et al. | Jan 2005 | B1 |
7026925 | Roche et al. | Apr 2006 | B2 |
7079627 | Crago et al. | Jul 2006 | B2 |
7095733 | Yarlagadda et al. | Aug 2006 | B1 |
7098787 | Miller | Aug 2006 | B2 |
7231218 | Diacakis et al. | Jun 2007 | B2 |
7269413 | Kraft | Sep 2007 | B2 |
7342917 | Mohan et al. | Mar 2008 | B2 |
7386103 | Chahal | Jun 2008 | B1 |
7418087 | Luneau et al. | Aug 2008 | B2 |
7496189 | Clarisse et al. | Feb 2009 | B2 |
7574194 | Yang et al. | Aug 2009 | B2 |
7679505 | Vallaire | Mar 2010 | B1 |
7706356 | Olshansky et al. | Apr 2010 | B1 |
7734019 | Terpstra | Jun 2010 | B1 |
7773975 | Snapp et al. | Aug 2010 | B2 |
7843903 | Bakke et al. | Nov 2010 | B2 |
7920679 | Naim et al. | Apr 2011 | B1 |
7991135 | Rauba et al. | Aug 2011 | B2 |
8014341 | Ray | Sep 2011 | B1 |
8102986 | McClintock et al. | Jan 2012 | B1 |
8295801 | Ray et al. | Oct 2012 | B2 |
8320871 | Ray et al. | Nov 2012 | B2 |
8364113 | Ray et al. | Jan 2013 | B2 |
8447267 | Ray et al. | May 2013 | B2 |
8615214 | Jain et al. | Dec 2013 | B2 |
8630609 | Ray et al. | Jan 2014 | B2 |
8712366 | Greene et al. | Apr 2014 | B2 |
8718595 | Ray et al. | May 2014 | B2 |
8891749 | Geldbach et al. | Nov 2014 | B2 |
8923803 | Ray et al. | Dec 2014 | B2 |
8964945 | Ray | Feb 2015 | B2 |
8976938 | Zerillo et al. | Mar 2015 | B2 |
8982871 | Ray et al. | Mar 2015 | B2 |
20010003843 | Scepanovic et al. | Jun 2001 | A1 |
20010004588 | Hong | Jun 2001 | A1 |
20010012379 | Amemiya et al. | Aug 2001 | A1 |
20020012323 | Petite et al. | Jan 2002 | A1 |
20020016189 | Sheynblat et al. | Feb 2002 | A1 |
20020054667 | Martinez | May 2002 | A1 |
20020136363 | Stumer et al. | Sep 2002 | A1 |
20030012344 | Agarwal et al. | Jan 2003 | A1 |
20030063714 | Stumer et al. | Apr 2003 | A1 |
20030109245 | McCalmont et al. | Jun 2003 | A1 |
20030133450 | Baum | Jul 2003 | A1 |
20030158668 | Anderson | Aug 2003 | A1 |
20040072583 | Weng | Apr 2004 | A1 |
20040077347 | Lauber et al. | Apr 2004 | A1 |
20040090950 | Lauber et al. | May 2004 | A1 |
20040176123 | Chin et al. | Sep 2004 | A1 |
20040257273 | Benco et al. | Dec 2004 | A1 |
20050002499 | Ordille et al. | Jan 2005 | A1 |
20050003797 | Baldwin | Jan 2005 | A1 |
20050070315 | Rai et al. | Mar 2005 | A1 |
20050101287 | Jin et al. | May 2005 | A1 |
20050111630 | Potorny et al. | May 2005 | A1 |
20050123102 | Beason et al. | Jun 2005 | A1 |
20050151642 | Tupler et al. | Jul 2005 | A1 |
20050159132 | Wright et al. | Jul 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 |
20050232225 | Pelaez et al. | Oct 2005 | A1 |
20050265326 | Laliberte | Dec 2005 | A1 |
20060009190 | Laliberte | Jan 2006 | A1 |
20060043164 | Dowling et al. | Mar 2006 | A1 |
20060052134 | Sato | Mar 2006 | A1 |
20060072547 | Florkey et al. | Apr 2006 | A1 |
20060133582 | McCulloch | Jun 2006 | A1 |
20060217136 | Bantukul et al. | Sep 2006 | A1 |
20060219542 | Savir | Oct 2006 | A1 |
20060234726 | Ashley et al. | Oct 2006 | A1 |
20060234727 | Ashley et al. | Oct 2006 | A1 |
20060293024 | Benco et al. | Dec 2006 | A1 |
20070003024 | Olivier et al. | Jan 2007 | A1 |
20070041368 | Lorello et al. | Feb 2007 | A1 |
20070064882 | Ger et al. | Mar 2007 | A1 |
20070121851 | Maropis et al. | May 2007 | A1 |
20070201391 | Belmonte et al. | Aug 2007 | A1 |
20070273519 | Ichikawa et al. | Nov 2007 | A1 |
20070280428 | McClelland | Dec 2007 | A1 |
20070287473 | Dupray | Dec 2007 | A1 |
20080018452 | McCarthy et al. | Jan 2008 | A1 |
20080026728 | Snapp et al. | Jan 2008 | A1 |
20080064363 | Salafia et al. | Mar 2008 | A1 |
20080064375 | Gottlieb | Mar 2008 | A1 |
20080070546 | Lee | Mar 2008 | A1 |
20080200143 | Qui et al. | Aug 2008 | A1 |
20080261557 | Sim | Oct 2008 | A1 |
20080273670 | Dickinson | Nov 2008 | A1 |
20080304630 | Nguyen et al. | Dec 2008 | A1 |
20090047924 | Ray et al. | Feb 2009 | A1 |
20090086932 | Ray | Apr 2009 | A1 |
20090097474 | Ray et al. | Apr 2009 | A1 |
20090144260 | Bennett et al. | Jun 2009 | A1 |
20090186596 | Kaltsukis | Jul 2009 | A1 |
20090197567 | Ogram | Aug 2009 | A1 |
20090214011 | Geldbach et al. | Aug 2009 | A1 |
20090227225 | Mitchell et al. | Sep 2009 | A1 |
20090305730 | Herz et al. | Dec 2009 | A1 |
20090310602 | Olshansky et al. | Dec 2009 | A1 |
20100002845 | Zerillo et al. | Jan 2010 | A1 |
20100002846 | Ray et al. | Jan 2010 | A1 |
20100003946 | Ray et al. | Jan 2010 | A1 |
20100003947 | Ray et al. | Jan 2010 | A1 |
20100003949 | Ray et al. | Jan 2010 | A1 |
20100003954 | Ray et al. | Jan 2010 | A1 |
20100003955 | Ray et al. | Jan 2010 | A1 |
20100003961 | Ray et al. | Jan 2010 | A1 |
20100098062 | Croak et al. | Apr 2010 | A1 |
20100107192 | Sennett et al. | Apr 2010 | A1 |
20100142386 | Snapp et al. | Jun 2010 | A1 |
20100215153 | Ray et al. | Aug 2010 | A1 |
20100291894 | Pipes | Nov 2010 | A1 |
20110014923 | Krco et al. | Jan 2011 | A1 |
20110096769 | Sim | Apr 2011 | A1 |
20120214437 | Ray et al. | Aug 2012 | A1 |
20120309340 | Ray | Dec 2012 | A1 |
20130012156 | Ray et al. | Jan 2013 | A1 |
20130059560 | Ray et al. | Mar 2013 | A1 |
20130102269 | Ray et al. | Apr 2013 | A1 |
20130217355 | Ray et al. | Aug 2013 | A1 |
20130237181 | Ray | Sep 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/pages/products/cid.htm, downloaded from the World Wide Web on Apr. 24, 2006 (2 pages). |
“AT & T Wireless Unleashes the First and Only Wireless Messaging Device”, PhysOrg.com, Sep. 30, 2004; available online at URL: <http://www.physorg.com/news1392.html> (12 pages). |
Non-Final Office Action date mailed Aug. 3, 2010 for U.S. Appl. No. 11/891,784. |
Response filed Nov. 2, 2010 for U.S. Appl. No. 11/891,784. |
Federal Standard 1037C: Telecommunications: Glossary of Telecommunication Terms, National Communication System. Technology and Standards Division. Washington, DC; General Services Administration, Information Technology Service, 1996. pp. vii, A-28, H-7, O. |
U.S. Appl. No. 12/391,503; Non Final Office Action dated Feb. 16, 2012; 9 pages. |
U.S. Appl. No. 12/391,503; Final Rejection dated May 24, 2012; 19 pages. |
U.S. Appl. No. 11/430,232; Notice of Allowance dated May 13, 2011; 12 pages. |
U.S. Appl. No. 11/430,232; Issue Notification dated Aug. 17, 2011; 1 page. |
U.S. Appl. No. 11/904,883; Non-Final Rejection dated Oct. 7, 2011; 19 pages. |
U.S. Appl. No. 11/904,883; Final Rejection dated Apr. 27, 2012; 16 pages. |
U.S. Appl. No. 12/257,424; Non-Final Rejection dated Jan. 31, 2012; 21 pages. |
U.S. Appl. No. 12/257,424; Final Rejection dated Jul. 14, 2011; 19 pages. |
U.S. Appl. No. 11/974,775; Notice of Allowance dated Apr. 27, 2012; 12 pages. |
U.S. Appl. No. 11/974,775; Non-Final Rejection dated Nov. 7, 2011; 19 pages. |
U.S. Appl. No. 11/974,775; Non-Final Rejection dated May 10, 2011; 24 pages. |
U.S. Appl. No. 12/168,668; Non-Final Rejection dated Feb. 6, 2012; 21 pages. |
U.S. Appl. No. 12/070,909; Final Rejection dated Jan. 10, 2012; 9 pages. |
U.S. Appl. No. 12/070,909; Non-Final Rejection dated Aug. 16, 2011; 13 pages. |
U.S. Appl. No. 12/257,574; Final Rejection dated Dec. 29, 2011; 18 pages. |
U.S. Appl. No. 12/257,574; Non-Final Rejection dated Jul. 6, 2011; 20 pages. |
U.S. Appl. No. 12/257,624; Final Rejection dated Jan. 31, 2012; 14 pages. |
U.S. Appl. No. 12/257,624; Non-Final Rejection dated Oct. 6, 2011; 19 pages. |
U.S. Appl. No. 12/257,641; Notice of Allowance dated Feb. 2, 2012; 12 pages. |
U.S. Appl. No. 12/257,641; Non-Final Rejection dated May 24, 2011; 17 pages. |
U.S. Appl. No. 12/257,928; Non-Final Rejection dated Jun. 8, 2011; 21 pages. |
U.S. Appl. No. 12/272,238; Pre-Brief Appeal Conference Decision dated Jan. 17, 2012; 2 pages. |
U.S. Appl. No. 12/272,238; Notice of Appeal and Pre-Brief Conference Request dated Dec. 28, 2011; 6 pages. |
U.S. Appl. No. 12/272,238; Final Rejection dated Sep. 29, 2011; 12 pages. |
U.S. Appl. No. 12/257,862; Final Rejection dated Nov. 30, 2011; 15 pages. |
U.S. Appl. No. 12/257,862; Non-Final Rejection dated May 24, 2011; 19 pages. |
U.S. Appl. No. 11/904,883; Non Final Rejection dated Apr. 19, 2013; 22 pages. |
U.S. Appl. No. 12/257,641; Notice of Allowance dated Aug. 2, 2012; 17 pages. |
U.S. Appl. No. 12/257,862; Non-Final Rejection dated Mar. 13, 2013; 30 pages. |
U.S. Appl. No. 13/460,507; Non-Final Rejection dated Apr. 26, 2013; 19 pages. |
U.S. Appl. No. 13/614,585; Issue Notification dated May 1, 2013; 1 page. |
U.S. Appl. No. 13/715,808; Non-Final Rejection dated Apr. 9, 2013; 36 pages. |
U.S. Appl. No. 11/891,784, Notice of Allowance dated Jul. 18, 2012; 27 pages. |
U.S. Appl. No. 11/974,775, Notice of Allowance dated Jun. 12, 2012; 15 pages. |
U.S. Appl. No. 12/257,424, Final Rejection dated Jun. 13, 2012; 41 pages. |
U.S. Appl. No. 12/257;641; Notice of Allowance dated Aug. 2, 2012; 17 pages. |
U.S. Appl. No. 12/272,238; Notice of Allowance dated Jun. 8, 2012; 21 pages. |
U.S. Appl. No. 12/257,424; Non-Final Rejection dated Jul. 8, 2013; 46 pages. |
U.S. Appl. No. 12/257,862; Non-Final Rejection dated Aug. 23, 2013; 29 pages. |
U.S. Appl. No. 13/715,808; Notice of Allowance dated Sep. 13, 2013; 27 pages. |
U.S. Appl. No. 13/847,388; Non-Final Office Action dated Jul. 17, 2013; 54 pages. |
U.S. Appl. No. 12/168,668; Final Rejection dated Jul. 11, 2012; 29 pages. |
U.S. Appl. No. 13/460,507; Non-Final Refection dated Aug. 16, 2012; 28 pages. |
U.S. Appl. No. 11/974,775; Corrected Notice of Allowability dated Aug. 31, 2012; 7 pages. |
U.S. Appl. No. 12/257,574; Notice of Allowance dated Sep. 14, 2012; 25 pages. |
U.S. Appl. No. 11/891,784; Issue Notification dated Sep. 26, 2012; 1 page. |
U.S. Appl. No. 11/974,775; Issue Notification dated Sep. 26, 2012; 1 page. |
U.S. Appl. No. 12/272,238; Issue Notification dated Oct. 3, 2012; 1 page. |
U.S. Appl. No. 11/904,883; Non Final Rejection dated Oct. 11, 2012; 26 pages. |
U.S. Appl. No. 12/257,574; Issue Notification dated Jan. 9, 2013; 1 page. |
U.S. Appl. No. 12/257,641; Issue Notification dated Nov. 7, 2012; 1 page. |
U.S. Appl. No. 13/150,725; Non-Final Rejection dated Nov. 26, 2012; 19 pages. |
U.S. Appl. No. 13/460,507; Final Rejection dated Dec. 20, 2014; 14 pages. |
U.S. Appl. No. 13/614,585; Notice of Allowance dated Dec. 11, 2012; 30 pages. |
U.S. Appl. No. 12/257,624; Non-Final Rejection dated Oct. 16, 2013; 38 pages. |
U.S. Appl. No. 12/391,503; Non Final Office Action dated Oct. 25, 2013; 23 pages. |
U.S. Appl. No. 12/257,928; Non-Final Rejection dated Nov. 20, 2013; 35 pages. |
U.S. Appl. No. 12/257,424; Final Rejection dated Nov. 21, 2013; 34 pages. |
U.S. Appl. No. 12/257,862; Notice of Allowance dated Dec. 6, 2013; 21 pages. |
U.S. Appl. No. 13/847,388; Non-Final Office Action dated Dec. 9, 2013; 34 pages. |
U.S. Appl. No. 13/460,507; Notice of Allowance dated Dec. 20, 2013; 20 pages. |
U.S. Appl. No. 13/715,808; Issue Notification dated Dec. 24, 2013; 1 page. |
U.S. Appl. No. 11/904,883; Non Final Rejection dated Feb. 5, 2014; 19 pages. |
U.S. Appl. No. 12/257,424; Non-Final Rejection dated Apr. 17, 2014; 39 pages. |
U.S. Appl. No. 12/257,862; Issue Notification dated Apr. 9, 2014; 1 page. |
U.S. Appl. No. 12/257,928; Notice of Allowance dated Mar. 6, 2014; 20 pages. |
U.S. Appl. No. 13/460,507; Issue Notification dated Apr. 16, 2014; 1 page. |
U.S. Appl. No. 13/612,558; Non-Final Rejection dated Apr. 11, 2014; 37 pages. |
U.S. Appl. No. 13/847,388; Final Rejection dated Apr. 7, 2014; 36 pages. |
U.S. Appl. No. 11/904,883; Non Final Rejection dated Jun. 10, 2014; 15 pages. |
U.S. Appl. No. 12/070,909; Notice of Allowance dated Jul. 23, 2014; 33 pages. |
U.S. Appl. No. 12/257,424; Notice of Allowance dated Aug. 11, 2014; 36 pages. |
U.S. Appl. No. 12/257,624; Final Office Action dated May 13, 2014; 28 pages. |
U.S. Appl. No. 12/257,928; Issue Notification dated Jun. 25, 2014; 1 page. |
U.S. Appl. No. 12/391,503; Final Rejection dated Jun. 5, 2014; 39 pages. |
U.S. Appl. No. 13/847,388; Non-Final Rejection dated Jul. 17, 2014; 39 pages. |
U.S. Appl. No. 13/848,649; Non-Final Rejection dated Jul. 17, 2014; 21 pages. |
U.S. Appl. No. 11/904,883; Notice of Allowance dated Oct. 8, 2014; 17 pages. |
U.S. Appl. No. 12/070,909; Issue Notification dated Oct. 29, 2014; 1 page. |
U.S. Appl. No. 12/168,668; Notice of Allowance dated Oct. 7, 2014; 31 pages. |
U.S. Appl. No. 13/612,558; Notice of Allowance dated Sep. 16, 2014; 16 pages. |
U.S. Appl. No. 11/904,883; Issue Notification dated Feb. 4, 2015; 1 page. |
U.S. Appl. No. 12/168,668; Issue Notification dated Feb. 18, 2015; 1 page. |
U.S. Appl. No. 12/257,424; Issue Notification dated Dec. 10, 2014; 1 page. |
U.S. Appl. No. 12/257,624; Notice of Allowance dated Jan. 5, 2015; 18 pages. |
U.S. Appl. No. 12/391,503; Non Final Office Action dated Jan. 22, 2015; 23 pages. |
U.S. Appl. No. 13/612,558; Issue Notification dated Feb. 25, 2015; 1 page. |
U.S. Appl. No. 13/848,649; Non-Final Rejection dated Dec. 29, 2014; 12 pages. |
Number | Date | Country | |
---|---|---|---|
20080144779 A1 | Jun 2008 | US |