Emergency alert for voice over internet protocol (VoIP)

Information

  • Patent Grant
  • 9390615
  • Patent Number
    9,390,615
  • Date Filed
    Friday, September 3, 2010
    14 years ago
  • Date Issued
    Tuesday, July 12, 2016
    8 years ago
Abstract
A voice over Internet Protocol (VoIP) positioning center (VPC) is implemented in configuration with support from a text-to-voice module, emergency routing database, and VoIP switching points (VSPs) to allow a public safety access point (PSAP) or other emergency center to effectively communicate the nature of an emergency alert notification and the area of notification to the VoIP positioning center (VPC). The inventive VPC in turn determines which phones (including wireless and/or VoIP phones) are currently in the area for notification, and reliably and quickly issues the required warning to all affected wireless and VoIP phones.
Description
BACKGROUND OF THE INVENTION

1. Field of the Invention


This invention relates generally to emergency services. More particularly, it relates to emergency alert (e.g., Emergency alert™ type services) and technology for land-based and/or wireless phones, including and particularly Voice Over Internet Protocol (VoIP) phones.


2. Background of Related Art


Many communities have, or are in the process of, implementing what is known as an emergency alert system. An emergency alert system allows an emergency center to rapidly notify by telephone residents and businesses within a given geographical area affected by any given emergency. The larger the emergency, the larger the affected community and telephones to be notified. Public safety access points (PSAPs) typically employ emergency alert in emergency situations where it is necessary to contact thousands of citizens to alert them of pending or potential dangers such as neighborhood evacuations, tornado warnings, etc.


Current emergency alert systems employ banks of telephone dialers to quickly work through a list of hundreds, and even thousands (or more) telephone numbers, playing an audio recording to each answered phone. Some systems will leave the emergency message on an answering machine if that is what answers the line. Other emergency alert systems will keep track of which telephone numbers in a list are not answered after a predetermined number of rings, and will attempt to redial those numbers a predetermined number of times in an attempt to make contact.


Conventional emergency alert systems are based on the location of land-based (or street address-associated) telephones. For other phones, such as wireless phones, or voice over Internet Protocol (VoIP) phones, the users must register their phone number in the emergency alert system at a given location.


As VoIP promises to become the predominant telecommunications technology in the world, heightened emphasis will be placed on the registration process of VoIP phones to associate those phone numbers with a given location.


The present inventor has appreciated that due to the mobile and otherwise nomadic capabilities of VoIP telephones, however, the challenge of routing 911 calls with adequate automatic location identification (ALI) data to PSAPs is made more difficult. The existing solution to this problem is standardized in the NENA i2 Migratory standard. This standard uses dynamic ALI updates based upon emergency services query keys (ESQKs), and ALI steering, to supply accurate ALI data to a given public safety access point (PSAP) attempting to conduct an emergency alert set of calls. Although this solution is effective in getting 911 calls TO a PSAP, it has inherent problems when the PSAP itself initiates calls to individual telephones in the so-called “emergency alert” scenario.


Most emergency alert solutions today rely upon telephone numbers in an ALI database that are linked with the address where the phone is located. After selecting a particular geographical area, emergency alert solutions determine from the ALI database which telephone numbers are located in that area, and then commence to dial each number one by one. Depending upon how large the region is, and how large the outdialing phone banks are, the notification time can take several minutes to several hours.


However, such conventional solutions have disadvantages with conventional emergency alert systems, mostly because typical wireless and VoIP phones within the affected emergency region may not be included in the emergency alert process. Either the wireless or VoIP phone is not registered with an accurate location (e.g., it may currently not be at the registered location), or they simply might not have a specific telephone number listed in the ALI database, much less a specific current location. And even if it is listed in the ALI database, because many wireless and VoIP phones are mobile, there is no assurance that any particular wireless or VoIP phone may or may not be within the region of concern at the time of the concern.


In a VoIP phone network, the entity that knows the location of a specific VoIP phone is the VoIP positioning center (VPC). In the case of a completely wireless phone (e.g., cellular, WiFI), there may not be any network entity that knows its location. Without assurance that a particular phone is within a given area of concern, or without knowledge of VoIP phone numbers that exist within the given PSAP's jurisdiction, the PSAP cannot reliably issue emergency warnings to these phones.


There is a need for a better emergency alert system capable of quickly and reliably alerting wireless and/or VoIP phones currently within a region affected by a given emergency message.


SUMMARY OF THE INVENTION

In accordance with the principles of the present invention, an apparatus and method to alert a plurality of phones currently located within a given geographical region comprises receiving text data as an emergency alert message passed to a voice over Internet Protocol (VoIP) positioning center (VPC). Information is received defining the given geographical region, passed to the VPC. The text data is converted into voice data. The voice data is routed to each of the large number of phones determined to be within the given geographical region.


A method and apparatus to alert a plurality of phones currently located within a given geographical region in accordance with another aspect of the invention comprises receiving as a first input an emergency alert message passed to a voice over Internet Protocol (VoIP) positioning center (VPC). A second input information is received defining the given geographical region, passed to the VPC. The received emergency alert message is converted into VoIP data. The VoIP data is routed to each of the plurality of phones determined to be within the given geographical region.





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 an exemplary emergency alert Voice Over Internet Protocol (VoIP) solution, in accordance with the principles of the present invention.



FIG. 2 shows an exemplary call flow for reverse E911service, in accordance with the principles of the present invention.





DETAILED DESCRIPTION OF ILLUSTRATIVE EMBODIMENTS

The present invention implements a voice over Internet Protocol (VoIP) positioning center (VPC) in configuration with support from a text-to-voice module, emergency routing database, and VoIP switching points (VSPs) to allow a public safety access point (PSAP) or other emergency center to effectively communicate the nature of an emergency alert notification and the area of notification to the VoIP positioning center (VPC). The inventive VPC in turn determines which phones (including wireless and/or VoIP phones) are currently in the area for notification, and reliably and quickly issues the required warning to all affected wireless and VoIP phones.



FIG. 1 shows an exemplary emergency alert Voice Over Internet Protocol (VoIP) solution, in accordance with the principles of the present invention.


In particular, as shown in FIG. 1, emergency alert infrastructure includes a VoIP positioning center (VPC) 100 in communication with a text-to-voice module 112 and emergency routing database 110. Emergency messages are passed from the VPC 100 to the text-to-voice module 112, which routes packetized audio messages to targeted IP devices 120 via appropriate VoIP switching points, or softswitch, (VSPs) 116, 118. The VSPs 116, 118 are a VoIP service provider's equivalent to a landline central office.


The ERDB 110 outputs a target list of phones to be contacted 114, based on geographical definitions provided by the VPC 100. Though the geographical definitions are provided by the VPC 100 in the disclosed embodiments, the geographical definitions may be provided by a separate entity, preferably in communication with and directed by the VPC 100, e.g., over the Internet 203.


The present invention also requires implementation of voice trunks, e.g., CAMA or SS7 voice trunks, provisioned between an emergency services gateway (ESGW) and a selective router.


Also required is an automatic location identification (ALI) database, provisioned per otherwise conventional procedures.


TCP/IP data circuits are provisioned between the VoIP positioning center (VPC) 100 and the ALI database(s).


The VoIP positioning center (VPC) 100 is the call routing “mastermind” that maintains an emergency routing database (ERDB) 110 of VoIP customer addresses. In conventional 911 use, the VPC 100 also determines which PSAP should receive a received emergency call received from a wireless VoIP phone. Location techniques vary, e.g., location determined via which cellular tower the wireless device is communicating over, etc. The specific location technique used to locate a wireless and/or VoIP device is not crucial to the invention, just that the VPC 100 maintain a current location of all VoIP devices within a relevant emergency region. In a conventional 911 direction, the VoIP softswitches 116, 118 rely upon the VPC 100 to determine which selective router should receive a given E911 call. The VPC 100 also communicates with the PSAP 102 to inform the PSAP 102 of the caller's phone number (i.e., callback number) and location defined by a street address (or, in the case of a wireless caller, the closest street address to their current location).


Generally speaking, the inventive call flow traces emergency alert with a PSAP 102 that has determined that an emergency alert is required. In this call flow, the PSAP 102 that has determined the need for an emergency alert accesses a suitable web site 104 that offers a map of the PSAP jurisdiction. The specific drawing technique is not particularly important, as any suitable conventional application useful for emergency alert application may be implemented.


Using such drawing techniques provided by the web site 104, as directed by the PSAP 102 that provides the boundary within which all wireless and/or VoIP phones need to be alerted.


Next, in one disclosed embodiment, the PSAP 102 provides typed text of the alert into a provisioning field offered by a suitable web site page 104. The exact text message is not important to the invention. The text message may be pre-programmed and automatically provided by the PSAP equipment 102, or may be input as text directly by a PSAP operator. In any event, the PSAP 102 submits the completed warning to the VPC 100.


Alternative technology includes having the PSAP 102 contact a network operator at the VPC 100 (or other location) in other manner, e.g., verbally, via e-mail, facsimile (FAX), video (e.g., NTSC, PAL or even over the Internet using a multimedia messaging service (MMS) or similar technology, to describe the emergency alert message and the target area to be alerted.


The VPC 100 overlays the boundary area provided by the PSAP 102 to be alerted with the target list of phones 114 determined by the ERDB and/or other database maintained by the VPC 100 to be currently in the region to be alerted. Based on this overlay, the target list of vulnerable phones 114 is determined.


If textual input was submitted by the PSAP 102, then the textual input is converted into a data stream of packets representing an audible message by the text-to-voice module 112. The text-to-voice module 112 creates data representing an audible recording of the emergency alert message to be sent.


Lastly, an appropriate VoIP outdialing functionality instantly sends the recorded message to all phones on the target list. Because the VoIP dialing is packet based and digital in nature, virtually all wireless and/or VoIP phones to be alerted can be ‘dialed’, or contacted via Internet Protocol techniques, virtually simultaneously as compared with conventional DTMF dialing banks.


In an alternative embodiment, the target list of phone numbers to be alerted 114, is forwarded back to the PSAP 102, and the PSAP 102 initiates outdialing using otherwise existing emergency alert technology from the PSAP 102.



FIG. 2 shows an exemplary call flow for emergency alert service, in accordance with the principles of the present invention.


As shown in call flow step 1 of FIG. 2, the PSAP 102 determines that emergency notification is required, and the geographical region to be alerted is identified.


In call flow step 2, the PSAP 102 (or other emergency alert initiator (EAI) accesses the web site 104 of a suitable emergency alert vendor (e.g., www.reverse911.com). Using tools preferably provided by the web site 104, the PSAP 102 provides required input.


In particular, required inputs from an emergency alert initiator (EAI) include:


(1) A geographic boundary outline of the region (or regions) to be alerted. The geographic boundary outline may be defined in an appropriate manner, e.g., defined by a geographic shape such as a polygon, or defined by a civic address element such as street address range, zip code, city, county.


(2) An emergency alert message (EAM). The particular input format of the emergency alert message is unimportant, text or voice. Rather, the emergency alert message is a textual message to be transmitted in audible voice form (e.g., converted text-to-voice) to all wireless and/or VoIP (and even wired) phones within that geographic boundary.


Optional inputs from an emergency alert initiator include:


(3) EXPIRATION (date/time) of the emergency alert message (optional); and


(4) RETRY attempts (optional).


Delivery of the emergency alert message is attempted (and re-attempted) according to defined criteria (i.e., either time constrained or frequency constrained or both).


The emergency alert application server preferably provides feedback to the emergency alert initiator as to the success (or failure) of the delivery of the emergency alert message.


In call flow step 3, the boundary information and message text travel via Internet Protocol (IP) to the VPC 100.


In call flow step 4, the VPC 100 routes the geographic boundary of the region(s) to be alerted with an emergency alert message, to the ERDB 110.


In call flow step 5, the VPC 100 routes the alert message text to the text-to-voice converter module 112.


In call flow step 6, the ERDB 110 overlays the geographic boundary provided by the PSAP 102, and selects all wireless and/or VoIP phone numbers currently located within that boundary. These selected wireless and/or VoIP (and even wired) phone numbers create the target list of phone numbers 114.


The emergency alert application server (EAAS) then determines the VoIP users within the database that should receive the emergency alert message (EAM). This list is referred to as containing emergency alert targets.


The EAAS then initiates VoIP signaling to the relevant users. This signaling prompts the users' VoIP devices to establish a voice-path media connection with a suitable service provider so that the emergency alert message can be delivered to each user.


In call flow step 7, the target list of phone numbers 114 is forwarded to a suitable outbound call controller (OCC) 117.


In call flow step 8, the voice message representing the textual message transmitted by the PSAP 102 is forwarded to the outbound call controller 117.


In call flow step 9, the outbound call controller 117 dials each number on the target list of phone numbers to be alerted 114, and appends the alert voice message. Using VoIP, this process typically takes just milliseconds (i.e., all alert phone calls are placed virtually simultaneously).


In call flow step 10, the appropriate VoIP softswitch 116, 118 routes the call to the designated phone 120, be it wireless, VoIP, or even wired.


In call flow step 11, almost simultaneously, thousands of VoIP phones 120 ring, and in the same virtual instant the recorded text-to-voice message is heard by thousands of affected people.


In call flow step 12, the called public responds to the alert message.


The present invention provides a simple technique for quickly and reliably identifying target phones to be alerted in an emergency alert type emergency. The invention expedites contact with the numerous identified target phones, and has the capability to reliably contact many thousands, if not millions of phones in the case of a large-scale emergency, in a short amount of time.


Due to the unique qualities of VoIP, the entire target list of phones to be alerted 114 can be dialed virtually simultaneously and instantly, instead of sequentially and limited to the number of voice trunks implemented by the PSAP or other emergency alert source, as in conventional emergency alert techniques.


Quite simply, the invention saves time, lives and money.


This invention has applicability to wireless telecommunication in general, including long distance carriers, Internet Service Providers (ISPs), and information content delivery services/providers. More particularly, it has applicability to virtually any public service access point (PSAP), their use of location services, and to E-9-1-1 services for Voice Over Internet Protocol (VoIP).


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. A method to alert a plurality of phones currently located within a given geographic region, comprising: receiving an emergency alert message passed to a voice over Internet Protocol (VoIP) positioning center (VPC) in communication with at least one automatic location identification (ALI) database;receiving, at said VPC, a given geographic region to be alerted;determining a target plurality of destination phones to be contacted based on a match of a digitally stored current location of each of a plurality of VoIP phones in said VPC, to said given geographic region;passing, from said VPC, said emergency alert message to those of said target plurality of destination phones determined to have a digitally stored current location that is within said given geographic region; andretrying an unsuccessful attempt to pass said emergency alert VoIP data to any given one of said target plurality of destination phones.
  • 2. The method to alert a plurality of phones currently located within a given geographic region according to claim 1, wherein: said VPC determines which phones are in said target plurality of destination phones to be alerted.
  • 3. The method to alert a plurality of phones currently located within a given geographic region according to claim 2, wherein: said VPC determines which phones are in said target plurality of destination phones to be alerted, using an emergency routing database (ERDB).
  • 4. The method to alert a plurality of phones currently located within a given geographic region according to claim 1, wherein: said plurality of destination phones are voice over Internet Protocol (VolP) phones.
  • 5. The method to alert a plurality of phones currently located within a given geographic region according to claim 1, wherein: said emergency alert message comprises text message data.
  • 6. The method to alert a plurality of phones currently located within a given geographic region according to claim 1, wherein: said text message data is passed to said VPC via an Internet.
  • 7. The method to alert a plurality of phones currently located within a given geographic region according to claim 1, wherein: said given geographic region is passed to said VPC via an Internet.
  • 8. A method to alert a plurality of phones currently located within a given geographic region, comprising: receiving an emergency alert message passed to a voice over Internet Protocol (VoIP) positioning center (VPC) in communication with at least one automatic location identification (ALI) database;receiving, at said VPC, a given geographic region to be alerted;determining a target plurality of destination phones to be contacted based on a match of a digitally stored current location of each of a plurality of VoIP phones in said VPC, to said given geographic region;converting said received emergency alert message into emergency alert VoIP data;passing, from said VPC, said emergency alert VoIP data to each of those of said target plurality of destination phones determined to have a digitally stored current location that is within said given geographic region; andretrying an unsuccessful attempt to pass said emergency alert VoIP data to any given one of said target plurality of destination phones.
  • 9. The method to alert a plurality of phones currently located within a given geographic region according to claim 8, further comprising: receiving an expiration time of said received emergency alert message.
Parent Case Info

The present application claims priority from U.S. Provisional Application No. 60/711,435, filed Aug. 25, 2005, entitled “Emergency alert For VoIP”, to Dickinson et al., the entirety of which is expressly incorporated herein by reference.

US Referenced Citations (288)
Number Name Date Kind
1103073 O'Connel Jul 1914 A
4445118 Taylor et al. Apr 1984 A
4494119 Wimbush Jan 1985 A
4651156 Martinez Mar 1987 A
4891638 Davis Jan 1990 A
4891650 Sheffer Jan 1990 A
4952928 Carroll Aug 1990 A
4972484 Theile Nov 1990 A
5014206 Scribner May 1991 A
5043736 Darnell Aug 1991 A
5055851 Sheffer Oct 1991 A
5068656 Sutherland Nov 1991 A
5166972 Smith Nov 1992 A
5712900 Maupin Jan 1998 A
5937344 Zicker Aug 1999 A
6108533 Brohoff Aug 2000 A
6275937 Hailpern Aug 2001 B1
6427001 Contractor Jul 2002 B1
6526026 Menon Feb 2003 B1
6529500 Pandharipande Mar 2003 B1
6529722 Heinrich Mar 2003 B1
6535743 Kennedy, III Mar 2003 B1
6539232 Hendrey et al. Mar 2003 B2
6556816 Gafrick Apr 2003 B1
6564261 Gudjonsson May 2003 B1
6675017 Zellner Jan 2004 B1
6694351 Shaffer Feb 2004 B1
6721396 Chin Apr 2004 B2
6731940 Nagendran May 2004 B1
6744858 Ryan Jun 2004 B1
6771639 Holden et al. Aug 2004 B1
6771742 McCalmont et al. Aug 2004 B2
6775267 Kung Aug 2004 B1
6775534 Lindgren Aug 2004 B2
6795444 Vo Sep 2004 B1
6813264 Vassilovski Nov 2004 B2
6816878 Zimmers Nov 2004 B1
6839417 Weisman Jan 2005 B2
6847618 Laursen Jan 2005 B2
6865266 Pershan Mar 2005 B1
6876734 Summers Apr 2005 B1
6882850 McConnell et al. Apr 2005 B2
6912230 Salkini Jun 2005 B1
6925504 Liskov Aug 2005 B1
6940826 Simard Sep 2005 B1
6940950 Dickinson et al. Sep 2005 B2
6968044 Beason Nov 2005 B2
6985747 Chithambaram Jan 2006 B2
6990081 Schaefer et al. Jan 2006 B2
6993355 Pershan Jan 2006 B1
7031724 Ross Apr 2006 B2
7130630 Enzmann Oct 2006 B1
7136466 Gao Nov 2006 B1
7171220 Belcea Jan 2007 B2
7174153 Ehlers Feb 2007 B2
7177397 McCalmont Feb 2007 B2
7177398 Meer Feb 2007 B2
7177399 Dawson Feb 2007 B2
7184418 Baba Feb 2007 B1
7200380 Havlark Apr 2007 B2
7245900 Lamb Jul 2007 B1
7260186 Zhu Aug 2007 B2
7260384 Bales et al. Aug 2007 B2
7269428 Wallenius Sep 2007 B1
7277938 Duimovich Oct 2007 B2
7321773 Hines Jan 2008 B2
7333480 Clarke Feb 2008 B1
7366157 Valentine Apr 2008 B1
7369508 Parantainen May 2008 B2
7369530 Keagy May 2008 B2
7382773 Schoeneberger Jun 2008 B2
7394896 Norton Jul 2008 B2
7412049 Koch Aug 2008 B1
7428571 Ichimura Sep 2008 B2
7436785 McMullen Oct 2008 B1
7440442 Grabelsky et al. Oct 2008 B2
7453990 Welenson Nov 2008 B2
7516198 Appala Apr 2009 B1
7519353 Stevens Apr 2009 B2
7526563 Ingimundarson Apr 2009 B2
7573982 Breen Aug 2009 B2
7602886 Beech Oct 2009 B1
7617287 Vella et al. Nov 2009 B2
7627331 Winterbottom Dec 2009 B2
7664233 Kirchmeier Feb 2010 B1
7684782 Ashley Mar 2010 B2
7702081 Klesper Apr 2010 B1
7751826 Gardner Jul 2010 B2
7783297 Ishii Aug 2010 B2
7787611 Kotelly Aug 2010 B1
7822391 Delker Oct 2010 B1
7822871 Stolorz Oct 2010 B2
7895263 Kirchmeier Feb 2011 B1
20010021646 Antonucci Sep 2001 A1
20010040886 Jimenez Nov 2001 A1
20020055924 Liming May 2002 A1
20020058515 Holler May 2002 A1
20020069079 Vega Jun 2002 A1
20020085538 Leung Jul 2002 A1
20020086659 Lauper Jul 2002 A1
20020086676 Hendry Jul 2002 A1
20020099802 Marsh Jul 2002 A1
20020113797 Potter Aug 2002 A1
20020118650 Jagadeesan Aug 2002 A1
20020118796 Menard Aug 2002 A1
20020126656 Park Sep 2002 A1
20020136364 Stumer Sep 2002 A1
20020141386 Minert Oct 2002 A1
20020154221 Ishimaru Oct 2002 A1
20020174073 Nordman Nov 2002 A1
20020191595 Mar Dec 2002 A1
20030012148 Peters Jan 2003 A1
20030026245 Ejzak Feb 2003 A1
20030044654 Holt Mar 2003 A1
20030063714 Stumer Apr 2003 A1
20030063730 Woodring Apr 2003 A1
20030069002 Hunter et al. Apr 2003 A1
20030081752 Trandal May 2003 A1
20030081754 Esparza May 2003 A1
20030086539 McCalmont May 2003 A1
20030096623 Kim May 2003 A1
20030108176 Kung Jun 2003 A1
20030109245 McCalmont Jun 2003 A1
20030118160 Holt Jun 2003 A1
20030135493 Phelan Jul 2003 A1
20030148757 Meer Aug 2003 A1
20030163483 Zingher Aug 2003 A1
20030186709 Rhodes Oct 2003 A1
20030187803 Pitt Oct 2003 A1
20030222901 Houck Dec 2003 A1
20040032485 Stephens Feb 2004 A1
20040043775 Kennedy Mar 2004 A1
20040047461 Weisman Mar 2004 A1
20040064500 Kolar et al. Apr 2004 A1
20040076277 Kuusinen Apr 2004 A1
20040078694 Lester Apr 2004 A1
20040093217 Yeh May 2004 A1
20040097243 Zellner May 2004 A1
20040107143 Niemi Jun 2004 A1
20040150518 Phillips et al. Aug 2004 A1
20040152493 Phillips et al. Aug 2004 A1
20040156394 Westman Aug 2004 A1
20040157175 Matsumoto Aug 2004 A1
20040176123 Chin Sep 2004 A1
20040180671 Spain Sep 2004 A1
20040181689 Kiyoto Sep 2004 A1
20040184584 McCalmont Sep 2004 A1
20040190497 Knox Sep 2004 A1
20040192271 Eisner Sep 2004 A1
20040198386 Dupray Oct 2004 A1
20040203568 Kirtland Oct 2004 A1
20040203575 Chin Oct 2004 A1
20040203732 Brusilovsky Oct 2004 A1
20040203919 Ross Oct 2004 A1
20040242191 Hossain Dec 2004 A1
20040258021 Kashimoto Dec 2004 A1
20040267445 De Luca Dec 2004 A1
20050003797 Baldwin Jan 2005 A1
20050021769 Kim Jan 2005 A1
20050030977 Casey et al. Feb 2005 A1
20050031095 Pietrowicz Feb 2005 A1
20050039135 Othmer Feb 2005 A1
20050047399 Lee et al. Mar 2005 A1
20050048987 Glass Mar 2005 A1
20050053209 D'Evelyn Mar 2005 A1
20050063519 James Mar 2005 A1
20050071251 Linden Mar 2005 A1
20050074107 Renner Apr 2005 A1
20050078612 Lang Apr 2005 A1
20050083911 Grabelsky Apr 2005 A1
20050085257 Laird Apr 2005 A1
20050101335 Kelly May 2005 A1
20050107673 Ball May 2005 A1
20050111630 Potorney May 2005 A1
20050135569 Dickinson Jun 2005 A1
20050136885 Kaltsukis Jun 2005 A1
20050144322 Miyajima Jun 2005 A1
20050169248 Truesdale Aug 2005 A1
20050174991 Keagy Aug 2005 A1
20050186937 Graham Aug 2005 A1
20050188078 Kotzin Aug 2005 A1
20050190892 Dawson Sep 2005 A1
20050192822 Hartenstein Sep 2005 A1
20050195954 Klein Sep 2005 A1
20050201358 Nelson Sep 2005 A1
20050201528 Meer Sep 2005 A1
20050201529 Nelson Sep 2005 A1
20050202799 Rollender Sep 2005 A1
20050213537 Ingimundarson et al. Sep 2005 A1
20050213716 Zhu Sep 2005 A1
20050215233 Perera Sep 2005 A1
20050216300 Appelman Sep 2005 A1
20050222908 Altberg Oct 2005 A1
20050232252 Hoover Oct 2005 A1
20050238156 Turner Oct 2005 A1
20050261002 Cheng Nov 2005 A1
20050265318 Khartabil Dec 2005 A1
20050271029 Iffland Dec 2005 A1
20050282518 D'Evelyn Dec 2005 A1
20050287979 Rollender Dec 2005 A1
20050289097 Trossen Dec 2005 A1
20060008065 Longman et al. Jan 2006 A1
20060010200 Mousseau Jan 2006 A1
20060023747 Koren et al. Feb 2006 A1
20060026288 Acharya Feb 2006 A1
20060044407 Barbeau Mar 2006 A1
20060058049 McLaughlin Mar 2006 A1
20060068753 Karpen Mar 2006 A1
20060069503 Suomela et al. Mar 2006 A1
20060073812 Punaganti Apr 2006 A1
20060077911 Shaffer Apr 2006 A1
20060078094 Breen Apr 2006 A1
20060079236 Del Pino Apr 2006 A1
20060088152 Green Apr 2006 A1
20060099935 Gallagher May 2006 A1
20060106774 Cohen May 2006 A1
20060120517 Moon Jun 2006 A1
20060125692 Wang Jun 2006 A1
20060128395 Muhonen Jun 2006 A1
20060135132 Cai Jun 2006 A1
20060135177 Winterbottom Jun 2006 A1
20060154665 Svensson Jul 2006 A1
20060184617 Nicholas Aug 2006 A1
20060189303 Rollender Aug 2006 A1
20060193447 Schwartz Aug 2006 A1
20060205383 Rollender Sep 2006 A1
20060206568 Verma Sep 2006 A1
20060206610 Ling Sep 2006 A1
20060222151 Goldman Oct 2006 A1
20060233317 Coster Oct 2006 A1
20060236258 Othmer Oct 2006 A1
20060239205 Warren Oct 2006 A1
20060250987 White Nov 2006 A1
20060281437 Cook Dec 2006 A1
20060293024 Benco et al. Dec 2006 A1
20070003024 Olivier Jan 2007 A1
20070019614 Hoffman Jan 2007 A1
20070021908 Jaugilas Jan 2007 A1
20070027997 Polk Feb 2007 A1
20070036139 Patel Feb 2007 A1
20070040895 Barbeau et al. Feb 2007 A1
20070041513 Gende Feb 2007 A1
20070060097 Edge Mar 2007 A1
20070081635 Croak Apr 2007 A1
20070104183 Bakke May 2007 A1
20070115941 Patel May 2007 A1
20070121601 Kikinis May 2007 A1
20070160036 Smith Jul 2007 A1
20070162228 Mitchell Jul 2007 A1
20070190968 Dickinson Aug 2007 A1
20070201623 Hines Aug 2007 A1
20070202844 Wilson Aug 2007 A1
20070206568 Silver Sep 2007 A1
20070206613 Silver Sep 2007 A1
20070218871 Bonner Sep 2007 A1
20070238448 Gallagher Oct 2007 A1
20070242660 Xu Oct 2007 A1
20070253429 James Nov 2007 A1
20070263610 Mitchell Nov 2007 A1
20070263611 Mitchell Nov 2007 A1
20070270164 Maier Nov 2007 A1
20070293205 Henderson Dec 2007 A1
20080037715 Prozeniuk Feb 2008 A1
20080045250 Hwang Feb 2008 A1
20080063153 Krivorot Mar 2008 A1
20080065775 Polk Mar 2008 A1
20080081646 Morin Apr 2008 A1
20080117859 Shahidi May 2008 A1
20080160953 Mia Jul 2008 A1
20080192731 Dickinson Aug 2008 A1
20080208671 Ehrlich Aug 2008 A1
20080214202 Toomey Sep 2008 A1
20080268809 Busin Oct 2008 A1
20080313000 Degeratu Dec 2008 A1
20090003535 Grabelsky Jan 2009 A1
20090128404 Martino May 2009 A1
20090198733 Gounares Aug 2009 A1
20090204471 Elenbaas et al. Aug 2009 A1
20090204600 Kalik Aug 2009 A1
20090237210 Ciesla Sep 2009 A1
20100003954 Greene Jan 2010 A1
20100010860 Bose Jan 2010 A1
20100119049 Clark May 2010 A1
20100198933 Smith Aug 2010 A1
20100233991 Crawford Sep 2010 A1
20100262668 Piett Oct 2010 A1
20110207429 Maier Aug 2011 A1
20120079600 Kellerman Mar 2012 A1
Foreign Referenced Citations (5)
Number Date Country
WO9921380 Apr 1999 WO
WO0145342 Jun 2001 WO
WO2004025941 Mar 2004 WO
WO2004021726 Mar 2004 WO
WO2005051033 Jun 2005 WO
Non-Patent Literature Citations (13)
Entry
http://en.wikipedia.org/wiki/imsi, Wikipedia Encyclopedia, International Mobile Subscriber Identity, pp. 1-4, printed on Sep. 4, 2008.
Harry Newton, Newton's Telecom Dictionary, Feb. 2000, Telecom Books, 16th edition, p. 427.
Le-Pond Chin, Jyh-Hong Wen, Ting-Way Liu, The Study of the Interconnection of GSM Mobile Communication System Over IP based Network, May 6, 2001, IEEE, Vehicular Technology Conference, vol. 3, pp. 2219-2223.
Winterbottom, et al., “GEOPRIV PIDF-Lo Usage Clarification, Considerations and Recommendations; draft-ietf-geopriv-pdif-lo-profile-00.txt,” Nortel, Jul. 2, 2005, pp. 1-31.
Berners-Lee, et al., “Uniform Resource Identifier (URI) Generic Standard, Internet Engineering Task Force,” Day Software, Jan. 1, 2005, pp. 1-61.
Zehua et al., “On Querying Geospatial and Georeferenced Metadata Resources in G-Portal,” IEEE Comp. SOC, May 31, 2003, pp. 245-255.
Peterson et al., “A Presence-based GEOPRIV Location Object Format; rfc4119,txt,” Neustar, Dec. 1, 2005, pp. 1-23.
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 received in PCT/US2012/00266 dated Aug. 3, 3012.
International Search Report received in PCT/US2011/001990 dated Apr. 24, 2012.
International Search Report received in PCT/US2012/067857 dated Feb. 20, 2013.
International Search Report received in PCT/US2012/67689 dated Feb. 22, 2013.
International Search Report received in PCT/US2012/066313 dated Feb. 4, 2013.
Related Publications (1)
Number Date Country
20110019664 A1 Jan 2011 US
Provisional Applications (1)
Number Date Country
60711435 Aug 2005 US
Continuations (1)
Number Date Country
Parent 11508283 Aug 2006 US
Child 12923142 US