Wireless emergency services protocols translator between ANSI-41 and VoIP emergency services protocols

Information

  • Patent Grant
  • 9001719
  • Patent Number
    9,001,719
  • Date Filed
    Monday, February 4, 2013
    11 years ago
  • Date Issued
    Tuesday, April 7, 2015
    9 years ago
Abstract
A protocol converter or translator between ANSI-41 ORREQs and VoIP V2 messaging. The protocol converter may alternatively (or also) provide conversion between GMS MAP and VoIP V2 messaging. Interaction of VSPs with a Mobile Positioning Center (MPC) or a Gateway Mobile Location Center (GMLC) is permitted, as is interaction of wireless carriers with a Voice Positioning Center (VPC). In this way existing GMLCs or MPCs may be used to service VoIP 9-1-1 calls. Moreover, operators of Voice Positioning Centers (VPCs) who implement wireless offerings can re-use their existing VPCs to service wireless 9-1-1 calls.
Description
BACKGROUND OF THE INVENTION

1. Field of the Invention


This invention relates generally to wireless telecommunications. More particularly, it relates to wireless telecommunication protocol conversion to Voice Over Internet Protocol (VoIP) protocol and vice versa. Specifically, ANSI-41 J-STD-036 E3 interface to VoIP NENA 08-001 V2 interface and vice versa. As well as, GSM J-STD-036 Lg/Lg+ interface to VoIP NENA 08-001 V2 interface and vice versa.


2. Background of the Related Art


Voice Over Internet Protocol (VoIP) is a technology that has been developed as an alternative packet-based telephony technology to the conventional switched telephony service (e.g. PSTN). VoIP takes advantage of high speed Internet data networks, and is able to provide low cost telephony services to end users. VoIP technology emulates a phone call, but instead of using a circuit based switched system such as the telephone network, utilizes packetized data transmission techniques most notably implemented in the Internet.


VoIP phone calls are routed to a VoIP voice gateway, from which they are passed on to their destination VoIP device. Conventional VoIP voice gateways (i.e., soft switches) are typically located in only a few places across the country. A soft switch is a programmable network switch that can process the signaling for all types of packet protocols. Also known as a ‘media gateway controller,’ ‘call agent,’ or ‘call server,’ such devices are used by carriers that support converged communications services by integrating signaling system No. 7 (SS7) type switched telephone signaling with packet networks. Softswitches can support, e.g., IP, DSL, ATM and frame relay.


Because VoIP is Internet Protocol (IP) based, call related information such as CallerID type services may not be available or accurate. A location of a given VoIP device may be statically provisioned to be at a given geographic location, or queried from a home location register (HLR) in a mobile system.


911 is a phone number widely recognized as an emergency phone number that is routed to emergency dispatch personnel and used to determine a location of a caller. Enhanced 911 (E911) is defined by the transmission of callback number and location information to the relevant public safety answering point (PSAP). A PSAP is the endpoint of an emergency services call. PSAPs are responsible for answering emergency services calls. E911 may be implemented for landline and/or mobile devices. Some Public Safety Access Points (PSAPs) are not enhanced, and thus do not receive the callback or location information from any phone, landline or mobile.


The problem is not necessarily solved with the use of a centralized emergency call center. In such case, when a VoIP customer places an emergency call such as an E911 call, the call may be routed to an emergency call center that is very far away, and in some instances half-way across the world to reach the centralized emergency call center. The VoIP E911 call must then be transferred to the relevant 911 center (public safety access point (PSAP)). However, this transfer must take place over the Public Switched Telephone Network (PSTN) because such transfer cannot conventionally be gained to the PSAP's existing Enhanced 911 (E911) dedicated network where location and callback number of the originating 911 caller are provided. Moreover, note that even the call related information (e.g., CallerID) provided with the call would relate to the identity and location of the centralized call center—not to the callback number and certainly not the location of the customer originally dialing 911.


An ANSI-41 J-STD-036 E3 (“E3”) interface is a time division multiplex (TDM) format that operates at 34.368 Mbps, and supports both Physical Layer Conversion Protocol (PLCP) and direct cell mapping.


A voice over Internet Protocol (VoIP) NENA 08-001 V2 (“V2”) interface is used to request emergency call routing information when the call server/routing proxy/redirect server is a separate element from a VoIP voice over Internet Protocol (VoIP) positioning center (VPC).


Session Internet Protocol (SIP) to ISDN User Part (ISUP) conversion, and ISUP to SIP conversion is somewhat common in the market. But currently, an E3 interface interfaces only with a mobile positioning center (MPC). Similarly, an Lg/Lg+ interface interfaces only with Gateway Mobile Location Centers (GMLCs), and V2 interfaces only with VoIP Positioning Centers (VPCs).


SUMMARY OF THE INVENTION

In accordance with the principles of the present invention, a method and apparatus to translate emergency services protocol call setup information from VoIP V2 to ANSI-41 ORREQ comprises receiving VoIP V2 signaling from a Voice Service Provider (VSP). A call back number (CBN) is inserted into both a mobile directory number (MDN) field and an emergency service routing digits (ESRD) field of an ANSI-41 ORREQ. An emergency service routing key (ESRK) and, if needed, digits are inserted to determine a selective router and/or trunk, into up to 20 digits of a VoIP V2 message. Use of the digits received in the VoIP V2 message permit setup of an emergency services call over Session Initiation Protocol (SIP) using a wireless ESRK.


Apparatus and a method to translate emergency services protocol call setup information from VoIP V2 to GSM MAP SLR in accordance with another aspect of the invention comprises receiving VoIP V2 signaling from a Voice Service Provider (VSP). A call back number (CBN) is inserted into both an International Mobile Subscriber Identity (IMSI) field and an na-ESRD field of a GSM MAP SLR. An emergency service routing key (ESRK) is inserted and, if needed, digits are inserted to determine a selective router and/or trunk, into up to 20 digits of a VoIP V2 message. Use of the digits received in the VoIP V2 message permit setup of an emergency services call over Session Initiation Protocol (SIP) using a wireless ESRK.


Apparatus and a method to translate emergency services protocol call setup information from ANSI-41 ORREQ to VoIP V2 in accordance with yet another aspect of the invention comprises receiving an ANSI-41 ORREQ containing a call back number (CBN) and emergency service routing digits (ESRD) from a mobile servicing center (MSC). The CBN is converted to a VoIP V2 request. The VoIP V2 request is sent to a voice positioning center (VPC). The VoIP V2 request including an emergency service query key (ESQK) and an emergency service routing number (ESRN) inserted therein in a plurality of designated fields, is returned by a voice positioning center (VPC). Use of the ORREQ permits setup of an emergency services call over ISDN User Part (ISUP) or Multi-Frequency (MF) signaling.


Apparatus and a method to translate emergency services protocol call setup information from GSM MAP SLR to VoIP V2 in accordance with still another aspect of the invention comprises receiving a GSM MAP SLR containing a call back number (CBN) and emergency service routing digits (ESRD) from a mobile servicing center (MSC). The CBN and ESRD are converted to a VoIP V2 request. The VoIP V2 request is sent to a voice positioning center (VPC). The VoIP V2 request including an emergency service query key (ESQK) and an emergency service routing number (ESRN) is returned by a voice positioning center (VPC). The VoIP V2 request is converted to an SLR with an na-ESRK with the ESQK and a last 7-digits of the ESRN. Use of the SLR permits setup of an emergency services call over ISDN User Part (ISUP) or Multi-Frequency (MF) signaling.





BRIEF DESCRIPTION OF THE DRAWINGS

Features and advantages of the present invention will become apparent to those skilled in the art from the following description with reference to the drawings:



FIG. 1 shows conversion of Voice Over Internet Protocol (VoIP) emergency call set up to wireless emergency call set up, with VoIP V2 converted to ANSI-41 ORREQs, in accordance with the principles of the present invention.



FIG. 2 shows conversion of Voice Over Internet Protocol (VoIP) emergency call set up to wireless emergency call set up, with VoIP V2 converted to GSM MAP SLRs, in accordance with the principles of the present invention.



FIG. 3 shows conversion of wireless emergency call set up to Voice Over Internet Protocol (VoIP) emergency call set up, with ANSI-41 ORREQs being converted to VoIP V2, in accordance with the principles of the present invention.



FIG. 4 shows conversion of wireless emergency call set up to Voice Over Internet Protocol (VoIP) emergency call set up, with GSM MAP SLRs converted to VoIP V2s, in accordance with the principles of the present invention.





DETAILED DESCRIPTION OF ILLUSTRATIVE EMBODIMENTS

The present inventors have appreciated that wireless carriers may soon desire the ability to use current, IS41-based wireless telecommunications protocols to request Voice Over Internet Protocol (VoIP) call routing information. They also have appreciated that VoIP Service Providers may soon desire the ability to use current VoIP protocols to request IS41-based wireless call routing information. But IS41 and Voice Over Internet Protocol (VoIP) are disparate protocols, and thus Signaling System No. 7 (SS7) nodes (IS41-based) cannot signal to Voice Positioning Centers (VPCs). Similarly, VoIP nodes cannot signal to Mobile Positioning Centers (MPCs) or Gateway Mobile Location Centers (GMLCs).


The present invention provides a protocol converter (or alternatively referred to as a translator) between ANSI-41 ORREQs and VoIP V2 messaging. The invention also provides protocol conversion (or alternatively translation) between GMS MAP and VoIP V2 messaging.



FIG. 1 shows conversion of Voice Over Internet Protocol (VoIP) emergency call set up to wireless emergency call set up, with VoIP V2 converted to ANSI-41 ORREQs, in accordance with the principles of the present invention.


In particular, as shown in FIG. 1, emergency services protocols are translated from those of a voice service provider (VSP) 510 to those of a mobile positioning center (MPC) 520, by a VoIP V2 to ANSI-41 ORREQ Wireless Emergency Services Protocol Converter 610.


The VoIP V2 to ANSI-41 ORREQ Wireless Emergency Services Protocol Converter 610 functions as follows:


In step 101 of FIG. 1, the voice service provider (VSD) 510 signals VoIP V2 to the VoIP V2 to ANSI-41 ORREQ Wireless Emergency Services Protocol Converter 610.


In step 102, the VoIP V2 to ANSI-41 ORREQ Wireless Emergency Services Protocol Converter 610 puts the call back number (CBN) into an ANSI-41 ORREQ, with the call back number (CBN) preferably in both the mobile directory number (MDN) field and the emergency services routing digits (ESRD) field of the ORREQ.


In step 103, the mobile positioning center (MPC) 520 treats the mobile directory number (MDN) as the emergency services routing digits (ESRD), and the ESRD determines an ESRK (and possibly digits to select the selective router or the trunk group) based on the subscribers provisioned address, similar to how wireless calls route based on the location of a cell tower.


In step 104, the VoIP V2 to ANSI-41 ORREQ Wireless Emergency Services Protocol Converter 610 puts the ESRK and, if needed, the digits to determine the selective router and/or trunk, into a VoIP V2 message containing up to 20 digits in a preferred embodiment.


In step 105, the voice service provider (VSP) 510 uses the digits received in the VoIP V2 message to set up the call over Session Initiation Protocol (SIP) using a wireless emergency services routing key (ESRK).



FIG. 2 shows conversion of Voice Over Internet Protocol (VoIP) emergency call set up to wireless emergency call set up, with VoIP V2 converted to GSM MAP SLRs, in accordance with the principles of the present invention.


In particular, as shown in FIG. 2, emergency services protocols are translated from those of a voice service provider (VSP) 510 to those of a Gateway Mobile Location Center (GMLC) 530, by a VoIP V2 to GSM MAP SLR Wireless Emergency Services Protocol Converter 620.


The VoIP V2 to GSM MAP SLR Wireless Emergency Services Protocol Converter 620 functions as follows:


In step 201 shown in FIG. 2, the Voice Service Provider (VSP) 510 signals VoIP V2 to the VoIP V2 to GSM MAP SLR Wireless Emergency Services Protocol Converter 620.


In step 202, the VoIP V2 to GSM MAP SLR Wireless Emergency Services Protocol Converter 620 puts the call back number (CBN) into a GSM MAP SLR with the call back number (CBN) preferably inserted into both the International Mobile Subscriber Identity (IMSI) field and the na-ESRD field, and it sets the na-ESRK flag.


In step 203, the Gateway Mobile Location Center (GMLC) 530 treats the call back number (CBN) as ESRD, and the ESRD determines an ESRK (and possibly digits to select the selective router or the trunk group) based on the subscribers provisioned address, similar to how wireless calls route based on the location of a cell tower. The return SLR contains 17 digits: the 10 digit ESRK and up to 7 digits to determine the trunk group.


In accordance with the embodiment, it is also possible that the second 7 digits be used to represent a 10 digit number with the same NPA as the ESRK. It is preferable that the SLR na-ESRK may only contain 18 digits.


In step 204, the VoIP V2 to GSM MAP SLR Wireless Emergency Services Protocol Converter 620 puts the ESRK and, if needed, the digits to determine the selective router and/or trunk, into a VoIP V2 message containing up to 20 digits.


In step 205, the Voice Service Provider (VSP) 510 uses the digits received over VoIP V2 to set up the call over Session Initiation Protocol (SIP) using a wireless ESRK.



FIG. 3 shows conversion of wireless emergency call set up to Voice Over Internet Protocol (VoIP) emergency call set up, with ANSI-41 ORREQs being converted to VoIP V2, in accordance with the principles of the present invention.


In particular, as shown in FIG. 3, emergency services protocols are translated back from those of a mobile servicing center (MSC) 540 to those of a Voice Positioning Center (VPC) 550, by an ANSI-41 ORREQ to VoIP V2 Wireless Emergency Services Protocol Converter 630.


The ANSI-41 ORREQ to VoIP V2 Wireless Emergency Services Protocol Converter 630 functions as follows:


In step 301 of FIG. 3, for ANSI-41 signaling, the ORREQ sent by the Mobile Servicing Center (MSC) 540 preferably contains the call back number (CBN) and the Emergency Services Routing Digits (ESRD).


In step 302, the ANSI-41 ORREQ to VoIP V2 Wireless Emergency Services Protocol Converter 630 receives the ORREQ request with the call back number (CBN) and Emergency Services Routing Digits (ESRD), converts it to a VoIP V2 request, and sends the VoIP V2 request to the Voice Positioning Center (VPC) 550.


In step 303, the Voice Positioning Center (VPC) 550 is configured to return an Emergency Service Query Key (ESQK) and Emergency Service Routing Number (ESRN).


In step 304, the ANSI-41 ORREQ to VoIP V2 Wireless Emergency Services Protocol Converter 630 receives the VoIP V2 request and converts it to an ORREQ with the Emergency Service Routing Number (ESRN) and Emergency Service Query Key (ESQK) into designated fields. Exemplary designated fields used for insertion of the combination of the ESRN and ESQK may be any combination of the DialedDigits field, the Mobile Directory Number (MDN) field, the BillingDigits field, and/or the GenericDigits field.


In step 305, the Mobile Servicing Center (MSC) 540 receives the ORREQ and sets up the call appropriately over ISDN User Part (ISUP) or Multi-Frequency (MF) signaling.



FIG. 4 shows conversion of wireless emergency call set up to Voice Over Internet Protocol (VoIP) emergency call set up, with GSM MAP SLRs converted to VoIP V2s, in accordance with the principles of the present invention.


In particular, as shown in FIG. 4, emergency services protocols are translated back from those of a mobile servicing center (MSC) 540 to those of a Voice Positioning Center (VPC) 550, by a GSM MAP SLRs to VoIP V2 Wireless Emergency Services Protocol Converter 640.


The GSM MAP SLRs to VoIP V2 Wireless Emergency Services Protocol Converter 640 functions as follows:


In step 401 of FIG. 4, for GSM MAP signaling, the GSM MAP SLR sent by the Mobile Servicing Center (MSC) 540 preferably contains the call back number (CBN) and the Emergency Services Routing Digits (ESRD).


In step 402, the GSM MAP SLRs to VoIP V2 Wireless Emergency Services Protocol Converter 640 receives an SLR request with the call back number (CBN) and Emergency Services Routing Digits (ESRD), converts it to a VoIP V2 request, and sends the VoIP V2 request to the Voice Positioning Center (VPC) 550.


In step 403, the Voice Positioning Center (VPC) 550 is configured to return an Emergency Service Query Key (ESQK) and Emergency Service Routing Number (ESRN).


In step 404, the GSM MAP SLRs to VoIP V2 Wireless Emergency Services Protocol Converter 640 receives a VoIP V2 request and converts it to an SLR with the na-ESRK with the Emergency Service Query Key (ESQK) and the last 7-digits of the Emergency Service Routing Number (ESRN).


Note that the na-ERSK field contains a maximum of 18 digits. In the preferred embodiment, the numbering plan area (NPA) of the Emergency Service Routing Number (ESRN) is preferably always the same as the numbering plan area (NPA) of the Emergency Service Query Key (ESQK).


In step 405, the Mobile Servicing Center (MSC) 540 receives the SLR and sets up the call appropriately over ISUP or Multi-Frequency (MF) signaling.


Benefits of the invention include that operators of Gateway Mobile Location Centers (GMLCs) or Mobile Positioning Centers (MPCs) who implement VoIP offerings can re-use their existing GMLC or MPC to service VoIP 9-1-1 calls. Moreover, operators of Voice Positioning Centers (VPCs) who implement wireless offerings can re-use their existing VPCs to service wireless 9-1-1 calls.


The invention allows interaction of VSPs with a Mobile Positioning Center (MPC) or Gateway Mobile Location Center (GMLC), and/or interaction of wireless carriers with a Voice Positioning Center (VPC). Those that will find particular use of the invention include wireless carriers, VoIP service providers, and especially those who already own an MPC, GMLC, or VPC and want to provide both wireless and VoIP telecommunications.


While the invention has been described with reference to the exemplary embodiments thereof, those skilled in the art will be able to make various modifications to the described embodiments of the invention without departing from the true spirit and scope of the invention.

Claims
  • 1. Apparatus to translate emergency services protocol call setup information from ANSI-41 ORREQ to VoIP, comprising: a receiver to receive, from a mobile switching (MSC), an ANSI-41 ORREQ containing at least one of a call back number (CBN) and emergency service routing digits (ESRD);a converter to convert said at least one of a CBN and an ESRD to a VoIP request;a transmitter to send, to a VoIP positioning center (VPC), said VoIP request; anda VoIP receiver to receive, from said VoIP positioning center (VPC), said VoIP request including at least one of an emergency service query key (ESQK) and an emergency service routing number (ESRN), said VoIP request having said at least one of an ESQK and an ESRN inserted in at least one of a designated field;whereby said ORREQ permits setup of an emergency services call with at least one of an ISDN User Part (ISUP) and Multi-Frequency (MF) signaling.
  • 2. Apparatus to translate emergency services protocol call setup information from ANSI-41 ORREQ to VoIP according to claim 1, wherein said at least one of a designated field comprises: a DialedDigits field;a Mobile Directory Number (MDN) field;a BillingDigits field; anda GenericDigits field.
  • 3. A method to translate emergency services protocol call setup information from ANSI-41 ORREQ to VoIP, comprising: receiving, from a mobile switching center (MSC), an ANSI-41 ORREQ containing at least one of a call back number (CBN) and emergency service routing digits (ESRD);converting said at least one of a CBN and an ESRD to a VoIP request;sending, to a VoIP positioning center (VPC), said VoIP request; andreceiving, from a VoIP positioning center (VPC), said VoIP request including at least one of an emergency service query key (ESQK) and an emergency service routing number (ESRN) inserted therein in at least one of a designated field;whereby said ORREQ permits setup of an emergency services call over at least one of ISDN User Part (ISUP) and Multi-Frequency (MF) signaling.
  • 4. The method to translate emergency services protocol call setup information from ANSI-41 ORREQ to VoIP according to claim 3, wherein said at least one of a designated field comprises: a DialedDigits field;a Mobile Directory Number (MDN) field;a BillingDigits field; anda GenericDigits field.
Parent Case Info

This application is a divisional of U.S. application Ser. No. 12/929,953 entitled “WIRELESS EMERGENCY SERVICES PROTOCOLS TRANSLATOR BETWEEN ANSI-41 AND VoIP EMERGENCY SERVICES PROTOCOLS”, to Poremba et al., filed Feb. 28, 2011; which claims priority from U.S. application Ser. No. 12/453,870 entitled “WIRELESS EMERGENCY SERVICES PROTOCOLS TRANSLATOR BETWEEN ANSI-41 AND VoIP EMERGENCY SERVICES PROTOCOLS”, to Poremba et al., filed May 26, 2009; which claims priority from U.S. Provisional Application No. 61/129,008 entitled “WIRELESS EMERGENCY SERVICES PROTOCOLS TRANSLATED BACK AND FORTH TO VoIP EMERGENCY SERVICES PROTOCOLS”, to Poremba et al., filed May 30, 2008, the entirety of all of which are explicitly incorporated herein by reference.

US Referenced Citations (224)
Number Name Date Kind
5712900 Maupin Jan 1998 A
5937344 Zicker Aug 1999 A
6002936 Roel-Ng Dec 1999 A
6134316 Kallioniemi Oct 2000 A
6181939 Ahvenainen Jan 2001 B1
6253074 Carlsson Jun 2001 B1
6275937 Hailpern Aug 2001 B1
6304635 Iwami Oct 2001 B1
6321092 Fitch Nov 2001 B1
6330313 Hunt Dec 2001 B1
6360102 Havinis Mar 2002 B1
6427001 Contractor Jul 2002 B1
6429808 King Aug 2002 B1
6526026 Menon Feb 2003 B1
6529500 Pandharipande Mar 2003 B1
6539232 Hendrey Mar 2003 B2
6587691 Granstam Jul 2003 B1
6687504 Raith Feb 2004 B1
6694351 Shaffer Feb 2004 B1
6744858 Ryan Jun 2004 B1
6757545 Nowak Jun 2004 B2
6775267 Kung Aug 2004 B1
6775534 Lindgren Aug 2004 B2
6795444 Vo et al. Sep 2004 B1
6813501 Kinnunen Nov 2004 B2
6847618 Laursen Jan 2005 B2
6876734 Summers Apr 2005 B1
6882850 McConnell Apr 2005 B2
6898274 Galt May 2005 B1
6940826 Simard Sep 2005 B1
6693748 Chithambaran Nov 2005 B1
6968044 Beason Nov 2005 B2
6985747 Chithambaram Jan 2006 B2
7031724 Ross Apr 2006 B2
7106717 Rousseau Sep 2006 B2
7136466 Gao Nov 2006 B1
7174153 Ehlers Feb 2007 B2
7177397 McCalmont Feb 2007 B2
7177398 Meer Feb 2007 B2
7177399 Dawson Feb 2007 B2
7200380 Havlark Apr 2007 B2
7245900 Lamb Jul 2007 B1
7245910 Osmo Jul 2007 B2
7246187 Ezra Jul 2007 B1
7260186 Zhu Aug 2007 B2
7269428 Wallenius Sep 2007 B1
7321773 Hines Jan 2008 B2
7330899 Wong Feb 2008 B2
7369530 Keagy May 2008 B2
7382773 Schoeneberger Jun 2008 B2
7394896 Norton Jul 2008 B2
7428571 Ichimura Sep 2008 B2
7436769 Loader Oct 2008 B2
7436785 McMullen Oct 2008 B1
7440442 Grabelsky Oct 2008 B2
7450951 Vimpari Nov 2008 B2
7453990 Welenson Nov 2008 B2
7522182 Bang Apr 2009 B2
7573982 Breen Aug 2009 B2
7602886 Beech Oct 2009 B1
7623447 Faccin Nov 2009 B1
7626951 Croy Dec 2009 B2
7627331 Winterbottom Dec 2009 B2
7764961 Zhu Jul 2010 B2
7787611 Kotelly Aug 2010 B1
7881233 Bieselin Feb 2011 B2
7937066 Kaltsukis May 2011 B2
7937067 Maier May 2011 B2
20020055924 Liming May 2002 A1
20020085538 Leung Jul 2002 A1
20020086676 Hendrey Jul 2002 A1
20020099802 Marsh Jul 2002 A1
20020102996 Jenkins Aug 2002 A1
20020118650 Jagadeesan Aug 2002 A1
20020123354 Nowak Sep 2002 A1
20020126656 Park Sep 2002 A1
20020147023 Sawada Oct 2002 A1
20020154221 Ishimaru Oct 2002 A1
20020164998 Younis Nov 2002 A1
20020173317 Nykanen Nov 2002 A1
20020188680 McCormack Dec 2002 A1
20030012148 Peters Jan 2003 A1
20030026245 Ejzak Feb 2003 A1
20030044654 Holt Mar 2003 A1
20030081752 Trandal May 2003 A1
20030086539 McCalmont May 2003 A1
20030108176 Kung Jun 2003 A1
20030109245 McCalmont Jun 2003 A1
20030115261 Mohammed Jun 2003 A1
20030118160 Holt et al. Jun 2003 A1
20030119521 Tipnis Jun 2003 A1
20030119528 Pew Jun 2003 A1
20030125021 Tell Jul 2003 A1
20030125493 Harris Jul 2003 A1
20030186709 Rhodes Oct 2003 A1
20030201931 Durst Oct 2003 A1
20030222901 Houck Dec 2003 A1
20040032485 Stephens Feb 2004 A1
20040041729 Rowitch Mar 2004 A1
20040043775 Kennedy Mar 2004 A1
20040064500 Kolar et al. Apr 2004 A1
20040076277 Kuusinen Apr 2004 A1
20040078694 Lester Apr 2004 A1
20040107143 Niemi Jun 2004 A1
20040132465 Mattila Jul 2004 A1
20040157175 Matsumoto Aug 2004 A1
20040176123 Chin Sep 2004 A1
20040181689 Kiyoto Sep 2004 A1
20040190497 Knox Sep 2004 A1
20040198386 Dupray Oct 2004 A1
20040203919 Ross Oct 2004 A1
20040204847 Yanai Oct 2004 A1
20040225878 Costa-Requena Nov 2004 A1
20050039135 Othmer Feb 2005 A1
20050053209 D'Evelyn Mar 2005 A1
20050063519 James Mar 2005 A1
20050074107 Renner Apr 2005 A1
20050078612 Lang Apr 2005 A1
20050083911 Grabelsky Apr 2005 A1
20050083923 Kimata Apr 2005 A1
20050101335 Kelly May 2005 A1
20050107673 Ball May 2005 A1
20050135569 Dickinson Jun 2005 A1
20050136885 Kaltsukis Jun 2005 A1
20050148351 Reding Jul 2005 A1
20050148353 Hicks Jul 2005 A1
20050169248 Truesdale Aug 2005 A1
20050174991 Keagy Aug 2005 A1
20050181805 Gallagher Aug 2005 A1
20050186948 Gallagher Aug 2005 A1
20050188078 Kotzin Aug 2005 A1
20050195954 Klein Sep 2005 A1
20050201529 Nelson Sep 2005 A1
20050213537 Ingimundarson et al. Sep 2005 A1
20050238156 Turner Oct 2005 A1
20050239458 Hurtta Oct 2005 A1
20050265318 Khartabil Dec 2005 A1
20050271051 Holloway Dec 2005 A1
20050272424 Gallagher Dec 2005 A1
20050272449 Gallagher Dec 2005 A1
20050282518 D'Evelyn Dec 2005 A1
20050287979 Rollender Dec 2005 A1
20050289097 Trossen Dec 2005 A1
20060008065 Longman Jan 2006 A1
20060010200 Mousseau Jan 2006 A1
20060023747 Koren Feb 2006 A1
20060026288 Acharya Feb 2006 A1
20060068753 Karpen Mar 2006 A1
20060072729 Lee Apr 2006 A1
20060073812 Punaganti Apr 2006 A1
20060077911 Shaffer Apr 2006 A1
20060079236 Del Pino Apr 2006 A1
20060088152 Green Apr 2006 A1
20060104306 Adamczyk May 2006 A1
20060120517 Moon Jun 2006 A1
20060135177 Winterbottom Jun 2006 A1
20060154665 Svensson Jul 2006 A1
20060184617 Nicholas Aug 2006 A1
20060188083 Breen Aug 2006 A1
20060189303 Rollender Aug 2006 A1
20060205383 Rollender Sep 2006 A1
20060236258 Othmer Oct 2006 A1
20060239205 Warren Oct 2006 A1
20060250987 White Nov 2006 A1
20060258380 Liebowitz Nov 2006 A1
20060281437 Cook Dec 2006 A1
20060293024 Benco Dec 2006 A1
20060293066 Edge Dec 2006 A1
20070003024 Olivier Jan 2007 A1
20070008885 Bonner Jan 2007 A1
20070022011 Altberg Jan 2007 A1
20070027997 Polk Feb 2007 A1
20070036139 Patel Feb 2007 A1
20070041513 Gende Feb 2007 A1
20070041516 Dickinson Feb 2007 A1
20070049288 Lamprecht Mar 2007 A1
20070060097 Edge Mar 2007 A1
20070070980 Phelps Mar 2007 A1
20070072553 Barbera Mar 2007 A1
20070081635 Croak Apr 2007 A1
20070121601 Kikinis May 2007 A1
20070160036 Smith Jul 2007 A1
20070162228 Mitchell Jul 2007 A1
20070182631 Berlinsky Aug 2007 A1
20070201623 Hines Aug 2007 A1
20070202844 Wilson Aug 2007 A1
20070206568 Silver et al. Sep 2007 A1
20070206580 Silver et al. Sep 2007 A1
20070206613 Silver Sep 2007 A1
20070206735 Silver et al. Sep 2007 A1
20070238448 Gallagher Oct 2007 A1
20070242660 Xu Oct 2007 A1
20070263610 Mitchell Nov 2007 A1
20080032703 Krumm Feb 2008 A1
20080037715 Prozeniuk Feb 2008 A1
20080058003 Rydnell et al. Mar 2008 A1
20080063153 Krivorot Mar 2008 A1
20080065775 Polk Mar 2008 A1
20080080691 Dolan Apr 2008 A1
20080117859 Shahidi et al. May 2008 A1
20080186164 Emigh Aug 2008 A1
20080228926 Shiratzky Sep 2008 A1
20080235511 O'Brien Sep 2008 A1
20080253535 Sherry Oct 2008 A1
20080267172 Hines Oct 2008 A1
20080273670 Dickinson Nov 2008 A1
20090094270 Alirez Apr 2009 A1
20090129396 Bakker May 2009 A1
20090215466 Ahl et al. Aug 2009 A1
20090224931 Dietz Sep 2009 A1
20090237210 Ciesla Sep 2009 A1
20090284348 Pfeffer Nov 2009 A1
20090298488 Snapp Dec 2009 A1
20100003954 Greene Jan 2010 A1
20100029244 Moodbidri Feb 2010 A1
20100062788 Nagorniak Mar 2010 A1
20100069034 Dickinson Mar 2010 A1
20100125892 Tanizawa May 2010 A1
20100142386 Snapp Jun 2010 A1
20100272242 Croy Oct 2010 A1
20110113060 Martini May 2011 A1
20110131414 Cheng Jun 2011 A1
20110149953 Helgeson Jun 2011 A1
20110165861 Wilson Jul 2011 A1
Foreign Referenced Citations (2)
Number Date Country
WO0145342 Jun 2001 WO
WO2004025941 Mar 2004 WO
Non-Patent Literature Citations (7)
Entry
Yilin Ahao, Efficient and reliable date transmission for cellular and GPS based mayday systems, Nov. 1997, IEEE, IEEE Conference on Intelligent Transportation System, 1997. ITSC 97, 555-559.
International Search Report in PCT/US/2010/01938 dated Sep. 30, 2010.
International Search Report in PCT/US/2009/002752 dated Jul. 6, 2009.
International Search Report received in PCT/US2012/000422 dated Dec. 10, 2012.
International Search Report received in PCT/US2012/00208 dated Jul. 6, 2012.
International Search Report received in PCT/US2011/001990 dated Apr. 24, 2012.
Intrado MSAG Prep for E911 Program Documentation. Intrado Inc., Longmont, CO. Sep. 14, 2006. Accessed: Nov. 8, 2011. Idaho Standards Committee. Idaho Emergency Communications Commission.
Related Publications (1)
Number Date Country
20130148555 A1 Jun 2013 US
Provisional Applications (1)
Number Date Country
61129008 May 2008 US
Divisions (1)
Number Date Country
Parent 12929953 Feb 2011 US
Child 13758680 US
Continuations (1)
Number Date Country
Parent 12453870 May 2009 US
Child 12929953 US