Enhanced E911 network access for call centers

Information

  • Patent Grant
  • 8406728
  • Patent Number
    8,406,728
  • Date Filed
    Monday, April 2, 2012
    12 years ago
  • Date Issued
    Tuesday, March 26, 2013
    11 years ago
Abstract
An emergency call (e.g., a 911 call, an alarm company call) forwarded by a telematics call center is routed over the switched PSTN to a Voice Over Internet Protocol (VoIP) call server, where the switched call is converted to a session initiating protocol (SIP) packetized IP call for presentation to an emergency services gateway, which reconverts the call to TDM and connects to a selective router via dedicated circuits, gaining full access to the Enhanced 911 network. This provides a PSAP receiving a call from a telematics call center or other call center with all features available in an Enhanced 911 network, e.g., callback number of the 911 caller, and location of the 911 caller. Location of the caller is provided using a VoIP positioning center (VPC).
Description
BACKGROUND OF THE INVENTION

1. Field of the Invention


This invention relates generally to E9-1-1 emergency phone calls. More particularly, it relates to emergency E9-1-1 calls using Voice Over Internet Protocol (VoIP), originating from centralized call centers.


2. Background of the Related Art


911 is a phone number widely recognized as an emergency phone number that is used by emergency dispatch personnel, among other things, 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.


Many cars built today include a telematics system. The word “telematics”, in its broadest sense, relates to the combination of computers and wireless telecommunications technologies. More recently, the term “telematics” has evolved to refer to automobile systems that combine global positioning satellite (GPS) tracking and other wireless communications for automatic roadside assistance and remote diagnostics. General Motors Corp. first popularized automotive telematics with its OnStar™ system. Mercedes-Benz offers a similar system called TeleAid™. The use of the word “telematics” throughout the current specification is intended to refer to the later definition of more recent recognition, i.e., to mean automotive telematics.


Many new vehicles are equipped with wireless-based telematics units providing services controlled by voice commands. One successful telematics system is available from OnStar Corp. (www.onstar.com). According to OnStar, OnStar brings together emergency service providers, wireless telephone, and satellite technologies to help protect a driver, and keep them connected on the road.


As part of the telematics system, a telematics unit including a cellular circuit is located within the vehicle, and powered by the vehicle's battery. Telematics units were originally analog-only, but have migrated to analog/digital-ready, and finally to dual-mode analog/digital. Dual-mode analog/digital telematics units operate on both the analog and digital wireless networks.


With a suitable subscription to use of a telematics operations center such as OnStar, a driver or passenger in a vehicle including a telematics unit has access to a voice-activated calling feature in their vehicle, just in case their hand-held cell phone is lost, forgotten or has a low battery. They can pre-purchase OnStar Hands-Free Calling minutes to use on the road. Such packages are typically billed to a credit card they keep on file with OnStar. They can order minutes packages by pushing the phone or white-dot button at any time.


Conventional telematics units are also capable of providing location information to a requesting wireless network, using a Global Positioning Satellite (GPS) mounted in the vehicle, or using other location technology within the wireless network. When a vehicle occupant pushes a given button in the vehicle, essentially calling the telematics operations center, the telematics operations center identifies the vehicle's location. Moreover, if their air bag deploys, the location of the vehicle can be reported to the telematics operations center. So it's only when the button is pushed to contact the telematics operations center, or when the telematics operations center is responding to an emergency signal, that the telematics operations center is provided with a location of the vehicle.


Today, most telematics companies and more generally alarm companies monitor signals from customers' car, home or business. The monitoring is usually centralized in a single location for customer locations across the country (e.g., a station in Columbus, Ohio might monitor homes throughout the country for a given monitoring company. In more global companies, an alarm or other monitoring company might monitor alarm signals from homes in the United States from a centralized command center located in Bombay, India.


Thus, in today's global economy, when a customer places an emergency call such as a 911 call (or automated alarm system emergency call), the call may be routed very far away, and in some instances half-way across the world. The telematics operator must then transfer the 911 call 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 telematics center—not to the callback number and certainly not the location of the customer originally dialing 911.



FIG. 3 shows conventional relevant systems in an emergency 911 call made via a telematics call center.


In particular, as shown in FIG. 3, a telematics unit 101 within a car dials 911. The 911 call is serviced by a cell site of a service provider, which includes a given mobile servicing center (MSC) 102. The MSC 102 passes the 911 call on to its relevant telematics call center 104. The telematics call center 104 may be, e.g., an ONSTAR™ call center.


The operator at the telematics call center 104 that handles the 911 call of its own subscriber obtains the identity and location information of the 911 caller. Based on the current location of the 911 caller, the operator performs a query of a telematics PSAP database 106 to determine a unique 10-digit phone number of the proper local PSAP physically responsible for the location of the 911 caller.


The operator at the telematics call center 104 then forwards the 911 caller to the PSAP by dialing its 10-digit phone number via the public switched telephone network (PSTN) 110.


Unfortunately, calls that arrive at the PSAP in this manner do not include call-back number (Automatic Number Identification (ANI)) and location information (Automatic Location Identification (ALI)). Moreover, the PSTN telephone 302 at the PSAP 118 is typically not answered with the same priority as are calls that originate on its E911 network. In addition, these calls are typically not recorded or time-stamped by PSAP equipment as are calls that arrive via the E911 network.


Trials have been conducted in which a local exchange carrier (LEC) has permitted access to a selective router for the E911 network via the PSTN. In this trial, the LEC designated a specific 10-digit telephone number. A caller has their emergency call transferred to this 10-digit telephone number, which is then call-forwarded within the central office to the selective router, which then forwards the call to the correct PSAP based upon the digits dialed. However, this solution suffers the same significant drawbacks as that shown in FIG. 3, i.e., that callback number and location are not provided to the responsible PSAP.


Other conventional technology relies on the PSAP having separate, second set of phone equipment capable of receiving proprietary data from the telematics center 104. But this solution would be prohibitively costly to implement nationwide for each telematics center, not to mention take up valuable space inside a PSAP center. Thus, the costs and disruption caused by the need for new hardware has little congestion control, making this a rather undesirable solution.


There is the need for a simple and effective solution to providing easy and full access to the Enhanced 911 network of an emergency services provider (e.g., PSAP) from users of a centralized call center, e.g., telematics call center, alarm call center, etc.


SUMMARY OF THE INVENTION

An emergency call (e.g., a 911 call, an alarm company call) forwarded by a telematics or other call center is routed over the switched PSTN to a Voice Over Internet Protocol (VoIP) call server, where the switched call is converted to a session initiating protocol (SIP) packetized IP call for presentation to an emergency services gateway (ESGW), which converts the call back to TDM and routes the call to a local selective router, thus gaining full access to the Enhanced 911 network. This provides a PSAP receiving a call from a telematics call center or other call center with all features available in an Enhanced 911 network, e.g., callback number of the 911 call center, and location of the 911 call center. Identification of the call center and the call-back number of the call center is provided using existing ALI circuits between a VoIP positioning center (VPC) and the PSAP's ALI database. The call center operator may update the VPC database with the caller's actual location and phone number, which can in turn be transmitted to the PSAP via existing ALI links.


In accordance with the principles of the present invention, a method of providing a call center with access to an Enhanced 911 network supporting a public safety answering point (PSAP) comprises determining a unique PSAP having jurisdictional responsibility for a physical current location of a caller to the call center. The caller is forwarded via a switched telephone network to a VoIP call server. The switched telephone call is converted into a session initiating protocol (SIP) packetized phone call. A VoIP positioning center is queried from the VoIP call server for call routing instructions for the SIP packetized phone call. The SIP packetized phone call is forwarded based on the call routing instructions to an emergency services gateway (ESGW) for conversion back to TDM and subsequent routing to the correct selective router.





BRIEF DESCRIPTION OF THE DRAWINGS


FIG. 1 shows an exemplary E911 architecture including E911 network access provided to a telematics call center or other call center, in accordance with the principles of the present invention.



FIG. 2 shows an exemplary call flow tracing an emergency 911 call from a telematics subscriber source to the appropriate PSAP, in accordance with the principles of the present invention.



FIG. 3 shows conventional relevant systems in an emergency 911 call made via a telematics call center.





DETAILED DESCRIPTION OF ILLUSTRATIVE EMBODIMENTS

In accordance with the principles of the present invention, an emergency call (e.g., 911 call, alarm company call) forwarded by a telematics call center is routed over the switched PSTN to a Voice Over Internet Protocol (VoIP) call server, where the switched call is converted to a packetized IP call for presentation to an emergency services gateway, gaining access to the Enhanced 911 network. Location of the caller is provided using a VoIP positioning center (VPC).


Voice Over IP (VoIP) is a technology that has been developed as an alternative telephony technology to the conventional 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 system such as the telephone network, utilizes packetized data transmission techniques most notably implemented in the Internet.


Voice-Over-Internet Protocol (VoIP) emulates a phone call, but instead of using a circuit based 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 SS7 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 provisioned to be at a given geographic location, or queried from a home location register (HLR) in a mobile system.



FIG. 1 shows an exemplary E911 architecture including E911 network access provided to a telematics call center or other call center, in accordance with the principles of the present invention.


The present invention applies VoIP technology in lieu of the switched telephone connectivity of the PSTN to route calls to a media gateway/VoIP call server 112. The switched call is converted into a packetized call using Internet Protocol (IP), and is routed via the internet to the ESGW 114 closest to the appropriate selective router for the destination PSAP. The ESGW converts the packetized IP data back into traditional TDM, and routes the call to the intended selective router 116 via dedicated TDM trunks, where it enters the E911 network. A selective router is the node in an emergency services network that performs enhanced call routing for 911 calls.


An example will be used to further illustrate the inventive architecture. In this example, a telematics unit 101 within a car dials 911. The 911 call is serviced by a cell site of a service provider, which includes a given mobile servicing center (MSC) 102. The MSC 102 forwards the 911 call on to its relevant telematics call center 104 via the PSTN. The telematics call center 104 may be, e.g., an ONSTAR™ call center, and may be located anywhere in the country or anywhere in the world.


The operator at the telematics call center 104 that handles the 911 call of its own subscriber obtains the nature of the call, as well as the identity and location of the 911 caller. The identity and location of the 911 call from the subscriber is most often received by the call center 104 over the open phone line to their subscriber. Equipment to receive the exact location of the subscriber is expensive, but necessary only at the centralized telematics call center. The thousands of PSAPs in the country do not have the same equipment, as it would be prohibitively expensive.


Based on the current location of the 911 caller, the operator performs a query of a telematics PSAP database 106 to determine a local PSAP physically responsible for that location, as well as a unique 10-digit phone number to access the Enhanced 911 network of that PSAP.


The operator at the telematics call center 104 handling the 911 call forwards the emergency call to a given media gateway/VoIP call server 112 by dialing the designated 10-digit number for that PSAP


To determine the appropriate PSAP and ESGW, the VoIP call server 112 queries a VoIP positioning center (VPC) 130. The VPC includes SIP connectivity to the VoIP call server 112. The VoIP call server 112 may also process VoIP calls. Using the 10-digit phone number dialed by the call center operator 104, the VPC queries the database 134 to determine the corresponding PSAP. The VPC then assigns an Emergency Services Query Key (ESQK) to the call and relays this routing key back to the VoIP Call Server 112.


The VoIP call server 112 passes the 911 emergency call on to an emergency service gateway ESGW 114, which in turn passes the 911 emergency call on to the desired PSAP 118. An ESGW resides in a VoIP service provider's network, and is responsible for integrating the session initiating protocol (SIP) network with the emergency services network (TDM). An ESGW 114 network includes dedicated voice trunks to selective routers in the Enhanced 911 (E911) network for any/all PSAPs being served (ideally a national network). The ESGW 114 routes 911 calls to the appropriate selective router, based on the ESRN/ESQK it receives.


The selective router 116 is provisioned with emergency services query keys (ESQKs) with ALI steering. (The ESQK is a digit string that uniquely identifies an ongoing emergency services call and is used to correlate the emergency services call with the associated data messages. It may also identify an emergency services zone and may be used to route the call through the network. The ESQK is similar to an ESRK in wireless E911 networks.)


A subscriber location database (SLDB) 134 is also provisioned. Preferably the SLDB 134 is configured so that no modifications are required to the core conventional existing VoIP E9-1-1 network. The SLDB 134 is used to relate a Session Initiated Protocol (SIP) Universal Resource Identifier (URI) or a telephone number to a PSAP.


In the given embodiments the SLDB 134 includes a listing of a series of “subscribers”, in which each subscriber is really a specific PSAP with a designated 1-900-xxx-yyyy phone number. Note that the phone number does not need to be a 1-900 number as this is used as an example only. This is also a useful technique for billing the call center for this service.


In the disclosed embodiments, the address of this “subscriber” is the latitude/longitude (lat/lon) of a centroid of the jurisdiction of the relevant PSAP. Alternatively, in databases that use tables in lieu of GIS for routing determination, the address of the “subscriber” can be any valid address within the jurisdiction of the PSAP.



FIG. 2 shows an exemplary call flow tracing an emergency 911 call from a telematics subscriber source to the appropriate PSAP, in accordance with the principles of the present invention.


In particular, as shown in FIG. 2, a caller or automated calling device 101 contacts a local security monitoring company or roadside assistance operator or similar third party call center 104. As an example shown in step 1, a caller 101 dials 911, which is serviced through a wireless MSC 102 and passed on to the relevant telematics call center, e.g., an OnSTAR™ call center. In the given example, the wireless MSC 102 may be part of a wireless carrier's network, with the 911 call being forwarded to the relevant telematics call center 104. Alternatively, the MSC 102 may be part of a large wireless network used by the telematics company itself.


The 911 call may be placed using an SOS or similar single-press button located in a car for use in emergency situations, automatically in the event of an accident, etc. Alternatively, the phone user may simply dial 911 in a manual cell phone call from a mobile phone, either integrated into a vehicle or entirely separate from a vehicle.


In step 2, a wireless MSC 102 routes the incoming emergency call to a telematics call center 104 (e.g., an ONSTAR™ or TeleAid™ call center). In the given example this routing includes use of the PSTN 110, though this need not be the case in all applications.


The call taker at the call center 104 who receives the 911 call from the caller 101 determines that this is an emergency call that must be referred to the local 911 PSAP.


Thus, in step 3, the telematics call taker queries an existing telematics PSAP database 106 to determine the correct PSAP to which the call should be routed. Of course, to save time step 3 may be performed simultaneous with, or even prior to, the call taker's determination that the call from the mobile user 101 is an emergency call.


In step 4, a telematics dispatcher dials (could be the same person and/or equipment as the call taker) a NPA-xxx-yyyy number designated for the determined PSAP. For instance, the call taker at the call center 104 then dials 1-900-xxx-yyyy, a designated number for that PSAP 118, and prepares to conduct a conference call with the caller 101 and the PSAP 118.


The call is then routed, via the PSTN 110, to a designated VoIP call server 112. The VoIP call server 112 may be co-located with a media gateway, which serves to convert TDM to IP. The VoIP call server 112 routes the resulting IP calls much like a traditional telephone switch routes a TDM call.


The VoIP call server 112 receives the ANI (caller ID) of the call center. The VoIP media gateway 112 reformats the call from time division multiplex (TDM) or code division multiplexed (CDM) into session initiation protocol (SIP). The VoIP Call Server rearranges the dialed digits, putting the DID that was dialed in step iii (e.g., 1-900-xxx-yyyy) in the FROM field and putting the ANI of the call center into the Just-in-Time callback number (JIT CBN) field within the P-Asserted Identity in the SIP Invite. (Session initiated protocol (SIP) is an IP-based protocol defined in IETF RFCs 3261 and 2543, the entirety of which are expressly incorporated herein by reference. SIP is one of two dominant messaging protocols used by the VoIP industry.


Importantly, the VoIP Media Gateway/call server 112 converts the TDM or CDM protocol of the incoming switched network phone call to packet data using session initiation protocol (SIP), and vice versa, meaning that packetized VoIP information coming from a relevant PSAP is converted into a switched connection with the 911 caller, terminated at the VoIP call server 112.


In step 5, the VoIP call server 112 holds the call while querying the VPC 130. The Invite is received by the VPC 130 for call routing instructions.


The VPC 130 is an application that determines the appropriate PSAP, based on the location of the 911 caller 101, returns associated routing instructions to the VoIP network, and provides the call center's identity and the callback number to the PSAP through the automatic location identifier (ALI). (An ALI is a database that relates a specific telephone number to an address. This database accepts a PSAP query with a telephone number and responds with an address. In the case of an ESQK, the ALI database steers (redirects) the query to the appropriate VoIP positioning center and steers the response back to the querying PSAP).


A SIP Invite command may be used for the query from the Call Server 112 to the VPC 130. The disclosed SIP Invite command preferably includes the following parameters:

    • a) The “from” field
      • =the dialed digits from the call center (NPA-xxx-yyyy)
    • b) The “to” field
      • =911
    • c) The JIT CBN field
      • =callback number of the call center


In step 6, the VoIP positioning center 132 queries an ERDB (SLDB) 134 for call routing instructions based upon the dialed NPA-xxx-yyyy number. The ERDB 134 relates the dialed number to the address of that phone number (lat/lon of the PSAP jurisdictional centroid) and determines the appropriate PSAP to receive the call. Within the ERDB 134, each phone number corresponds to a different PSAP.


In step 7, the ERDB 134 responds to the VPC 130 with the identity of the appropriate PSAP to serve the caller 101. The VPC 130 assigns an ESQK and emergency services routing number (ESRN) to the call and stages an ALI record. The ESRN is a 10-digit number that specifies the selective router to be used to route a call. The ALI record contains the phone number of the call center 104, based upon the ANI that accompanied the call. If the call center 104 is capable of sending the ANI of the actual end user, then this can be staged in the VPC ALI record.


Further call processing is otherwise per the conventional NENA i2 VoIP standard:


For instance, in step 8, the VoIP positioning center 130 assigns an emergency services query key (ESQK) appropriate to that PSAP, and stages a record with the call center CBN and call center company ID.


The VoIP positioning center 130 responds to the VoIP call server 112 with the ESQK, emergency services routing number (ESRN), and last routing option (LRO). (The LRO is routing information sent by the VPC 130 that provides a “last chance” destination for a call, for example the contingency routing number (CRN) or a routing number associated with a national call center.


In step 9, the VoIP call server 112 uses the ESRN to route the call to the correct emergency services gateway (ESGW) 114.


The VoIP call server 112 uses the received ESRN to determine the appropriate ESGW 114 and routes the call appropriately to the correct emergency services gateway (ESGW) 114. The ESGW 114 uses the ESRN to determine the appropriate selective router 116. For simplicity and clarity of description, only one ESGW 114 and one selective router 116 are pictured in FIG. 2.


In step 10, the ESGW 114 performs media conversion by converting the SIP protocol (and vice versa in the opposite communication direction), and uses the ESRN to route the call to the correct selective router 116, along with the ESQK.


In step 11, the selective router 116 routes the ESQK to the PSAP 118.


In step 12, the PSAP 118 queries the automatic location identifier (ALI) database 120 using the ESQK.


In step 13, the ALI database 120 steers the query to the VoIP positioning center (VPC) 130, per previously provisioned steering tables. The VPC 130 responds with a staged record that includes the callback number (CBN) and call center company ID. In the preferred embodiments, no latitude/longitude (lat/lon) is sent in the ALI record, although such data could be forwarded if it is available.


In step 14, the ALI database 120 forwards the callback number (CBN) and call center ID to the requesting PSAP 118.


In accordance with the present invention, benefits are derived by routing 911 calls via the Enhanced E911 network. Moreover, PSAPs can utilize all available technologies available to them in an Enhanced E911 network such as CAD, selective transfer, etc. when responding to a call from a telematics or other call center.


The present invention makes possible the transfer of misrouted or defaulted VoIP calls from a VoIP default call center to the appropriate PSAP via the Enhanced E911 network. In conventional systems defaulted calls must be routed via the PSTN.


This invention saves taxpayers money by allowing PSAPs to discontinue designated PSTN lines. This invention also increases the speed with which emergency services (responders) can be dispatched and provides recorded documentation of conversations that are typically available on calls received via the E911 network, but not via the PSTN.


The present invention has particular relevance for use by any alarm monitoring company, telematics call center, or emergency call center that monitors incoming calls. The invention has significant benefit in the use by automotive roadside assistance call centers like OnStar™, TeleAid, etc.


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 of providing a telematics call center with access to an Enhanced 911 network supporting a public safety answering point (PSAP), comprising: receiving a switched phone call from a telematics call center, via a switched telephone network, at a VoIP call server;converting, at said VoIP call server, said switched telephone call into an Internet Protocol (IP) based packetized phone call;querying a VoIP positioning center for call routing information to route said SIP packetized phone call to a particular PSAP, said VoIP positioning center query comprising a telematics call center telephone number;receiving said call routing information from said VoIP positioning center; andestablishing, via said VoIP call server, a conference call with said IP based packetized phone call, said telematics call center, and said particular PSAP based on said call routing information.
  • 2. The method of providing a telematics call center with access to an Enhanced 911 network supporting a public safety answering point (PSAP) according to claim 1, further comprising: forwarding a Time Division Multiplexed (TDM) phone call via a dedicated trunk line to a selective router serving said particular PSAP.
  • 3. The method of providing a telematics call center with access to an Enhanced 911 network supporting a public safety answering point (PSAP) according to claim 1, wherein: said an Internet Protocol (IP) based packetized phone call is a session initiating protocol (SIP) packetized phone call.
  • 4. The method of providing a telematics call center with access to an Enhanced 911 network supporting a public safety answering point (PSAP) according to claim 1, wherein: said telematics call center is one of ONSTAR™, ATX, Cross Country, or ADT.
  • 5. The method of providing a telematics call center with access to an Enhanced 911 network supporting a public safety answering point (PSAP) according to claim 1, wherein: said telematics call center is an alarm monitoring center.
  • 6. The method of providing a telematics call center with access to an Enhanced 911 network supporting a public safety answering point (PSAP) according to claim 1, wherein: said switched telephone call is received at said VoIP call server via a public switched telephone network (PSTN).
  • 7. The method of providing a telematics call center with access to an Enhanced 911 network supporting a public safety answering point (PSAP) according to claim 1, further comprising: determining a unique PSAP having jurisdictional responsibility for a physical current location of a caller to said telematics call center.
  • 8. The method of providing a telematics call center with access to an Enhanced 911 network supporting a public safety answering point (PSAP) according to claim 1, further comprising: receiving from said VoIP positioning center said call routing information for said SIP packetized phone call.
  • 9. System for providing a telematics call center with access to an Enhanced 911 network supporting a public safety answering point (PSAP), comprising: a receiver, at a VoIP call server, to receive a switched phone call, via a switched telephone network, from said telematics call center;a converter, at said VoIP call server, to convert said switched telephone call into an Internet Protocol (IP) based packetized phone call; anda database querying module to query a VoIP positioning center for call routing information to route said SIP packetized phone call to a particular PSAP, said query comprising a telematics call center telephone number; anda routing information receiver to receive said call routing information from said VoIP positioning center;wherein a conference call is established with said IP based packetized phone call, said telematics call center, and said particular PSAP based on said call routing information.
  • 10. The system for providing a telematics call center with access to an Enhanced 911 network supporting a public safety answering point (PSAP) according to claim 9, further comprising: means for forwarding a Time Division Multiplexed (TDM) phone call to a selective router serving said particular PSAP.
  • 11. The system for providing a telematics call center with access to an Enhanced 911 network supporting a public safety answering point (PSAP) according to claim 9, wherein: said an Internet Protocol (IP) based packetized phone call is a session initiating protocol (SIP) packetized phone call.
  • 12. The system for providing a telematics call center with access to an Enhanced 911 network supporting a public safety answering point (PSAP) according to claim 9, wherein: said telematics call center is an ONSTAR™ call center.
  • 13. The system for providing a telematics call center with access to an Enhanced 911 network supporting a public safety answering point (PSAP) according to claim 9, wherein: said telematics call center is an alarm monitoring center.
  • 14. The system for providing a telematics call center with access to an Enhanced 911 network supporting a public safety answering point (PSAP) according to claim 9, wherein: said means for forwarding said caller via a switched telephone network forwards via a public switched telephone network (PSTN).
  • 15. The system for providing a telematics call center with access to an Enhanced 911 network supporting a public safety answering point (PSAP) according to claim 9, further comprising: an emergency services gateway to determine a unique PSAP having jurisdictional responsibility for a physical current location of said phone call to said telematics call center.
  • 16. The system for providing a telematics call center with access to an Enhanced 911 network supporting a public safety answering point (PSAP) according to claim 9, wherein: said VoIP call server forwards said SIP packetized phone call based on said call routing information to an emergency services gateway.
Parent Case Info

The present invention is a continuation of U.S. patent application Ser. No. 11/354,861, entitled “Enhanced E911 Network for Call Centers,” filed on Feb. 16, 2006, now U.S. Pat. No. 8,150,363, the entirety of which is incorporated herein by reference.

US Referenced Citations (682)
Number Name Date Kind
1103073 O'Connell Jul 1914 A
4445118 Kuroda Apr 1984 A
4494119 Wimbush Jan 1985 A
4625081 Lotio Nov 1986 A
4651156 Martinez Mar 1987 A
4706275 Kamil Nov 1987 A
4868570 Davis Sep 1989 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
5068891 Marshall Nov 1991 A
5070329 Jasinaki Dec 1991 A
5081667 Drori Jan 1992 A
5119104 Heller Jun 1992 A
5126722 Kamis Jun 1992 A
5144283 Arens Sep 1992 A
5161180 Chavous Nov 1992 A
5166972 Smith Nov 1992 A
5177478 Wagai Jan 1993 A
5193215 Olmer Mar 1993 A
5208756 Song May 1993 A
5214789 George May 1993 A
5218367 Sheffer Jun 1993 A
5223844 Mansell Jun 1993 A
5239570 Koster Aug 1993 A
5265630 Hartmann Nov 1993 A
5266944 Carroll Nov 1993 A
5283570 DeLuca Feb 1994 A
5289527 Tiedemann Feb 1994 A
5293642 Lo Mar 1994 A
5299132 Wortham Mar 1994 A
5301354 Schwendeman Apr 1994 A
5311516 Kuznicke May 1994 A
5325302 Izidon Jun 1994 A
5327529 Fults Jul 1994 A
5334974 Simms Aug 1994 A
5335246 Yokev Aug 1994 A
5343493 Karimulah Aug 1994 A
5347568 Moody Sep 1994 A
5351235 Lahtinen Sep 1994 A
5361212 Class Nov 1994 A
5363425 Mufti Nov 1994 A
5365451 Wang Nov 1994 A
5374936 Feng Dec 1994 A
5379451 Nakagoshi Jan 1995 A
5381338 Wysocki Jan 1995 A
5387993 Heller Feb 1995 A
5388147 Grimes Feb 1995 A
5390339 Bruckert Feb 1995 A
5394158 Chia Feb 1995 A
5396227 Carroll Mar 1995 A
5398190 Wortham Mar 1995 A
5406614 Hara Apr 1995 A
5418537 Bird May 1995 A
5422813 Schuchman Jun 1995 A
5423076 Westergren Jun 1995 A
5434789 Fraker Jul 1995 A
5454024 Lebowitz Sep 1995 A
5461390 Hosher Oct 1995 A
5470233 Fruchterman Nov 1995 A
5479408 Will Dec 1995 A
5479482 Grimes Dec 1995 A
5485161 Vaughn Jan 1996 A
5485163 Singer Jan 1996 A
5488563 Chazelle Jan 1996 A
5494091 Freeman Feb 1996 A
5497149 Fast Mar 1996 A
5504491 Chapman Apr 1996 A
5506886 Maine Apr 1996 A
5508931 Snider Apr 1996 A
5513243 Kage Apr 1996 A
5515287 Hakoyama May 1996 A
5517199 DiMattei May 1996 A
5519403 Bickley May 1996 A
5530655 Lokhoff Jun 1996 A
5530914 McPheters Jun 1996 A
5532690 Hertel Jul 1996 A
5535434 Siddoway Jul 1996 A
5539395 Buss Jul 1996 A
5539398 Hall Jul 1996 A
5539829 Lokhoff Jul 1996 A
5543776 L'Esperance Aug 1996 A
5546445 Dennison Aug 1996 A
5552772 Janky Sep 1996 A
5555286 Tendler Sep 1996 A
5568119 Schipper Oct 1996 A
5568153 Beliveau Oct 1996 A
5574648 Pilley Nov 1996 A
5579372 Astrom Nov 1996 A
5588009 Will Dec 1996 A
5592535 Klotz Jan 1997 A
5594780 Wiedeman Jan 1997 A
5604486 Lauro Feb 1997 A
5606313 Allen Feb 1997 A
5606618 Lokhoff Feb 1997 A
5606850 Nakamura Mar 1997 A
5610815 Gudat Mar 1997 A
5614890 Fox Mar 1997 A
5615116 Gudat Mar 1997 A
5621793 Bednarek Apr 1997 A
5628051 Salin May 1997 A
5629693 Janky May 1997 A
5633912 Tsoi May 1997 A
5636276 Brugger Jun 1997 A
5661652 Sprague Aug 1997 A
5661755 Van de Kerkhof Aug 1997 A
5682600 Salin Oct 1997 A
5689245 Noreen Nov 1997 A
5699053 Jonsson Dec 1997 A
5731785 Lemelson Mar 1998 A
5740534 Ayerst Apr 1998 A
5761618 Lynch Jun 1998 A
5765152 Erickson Jun 1998 A
5767795 Schaphorst Jun 1998 A
5768509 Gunluk Jun 1998 A
5771353 Eggleston Jun 1998 A
5774533 Patel Jun 1998 A
5774670 Montulli Jun 1998 A
5787357 Salin Jul 1998 A
5794142 Vanttila Aug 1998 A
5797094 Houde Aug 1998 A
5797096 Lupien Aug 1998 A
5802492 DeLorme Sep 1998 A
5806000 Vo Sep 1998 A
5809415 Rossmann Sep 1998 A
5812086 Bertiger Sep 1998 A
5812087 Krasner Sep 1998 A
5822700 Hult Oct 1998 A
5828740 Khuc Oct 1998 A
5841396 Krasner Nov 1998 A
5857201 Wright, Jr. Jan 1999 A
5864667 Barkam Jan 1999 A
5874914 Krasner Feb 1999 A
5896369 Warsta Apr 1999 A
5920821 Seazholtz Jul 1999 A
5922074 Richard Jul 1999 A
5930250 Klok Jul 1999 A
5953398 Hill Sep 1999 A
5960362 Grob Sep 1999 A
5974054 Couts Oct 1999 A
5978685 Laiho Nov 1999 A
5983099 Yao Nov 1999 A
5987323 Huotari Nov 1999 A
5998111 Abe Dec 1999 A
5999124 Sheynblat Dec 1999 A
6014602 Kithil Jan 2000 A
6032051 Hall Feb 2000 A
6035025 Hanson Mar 2000 A
6049710 Nilsson Apr 2000 A
6052081 Krasner Apr 2000 A
6058300 Hanson May 2000 A
6061018 Sheynblat May 2000 A
6061346 Nordman May 2000 A
6064336 Krasner May 2000 A
6064875 Morgan May 2000 A
6067045 Castelloe May 2000 A
6070067 Nguyen May 2000 A
6075982 Donovan Jun 2000 A
6081229 Soliman Jun 2000 A
6081508 West Jun 2000 A
6085320 Kaliski, Jr. Jul 2000 A
6101378 Barabash Aug 2000 A
6108533 Brohoff Aug 2000 A
6122503 Daly Sep 2000 A
6122520 Want Sep 2000 A
6124810 Segal Sep 2000 A
6131067 Girerd Oct 2000 A
6133874 Krasner Oct 2000 A
6134316 Kallioniemi Oct 2000 A
6134483 Vayanos Oct 2000 A
6148197 Bridges Nov 2000 A
6148198 Anderson Nov 2000 A
6149353 Nilsson Nov 2000 A
6150980 Krasner Nov 2000 A
6154172 Piccionelli Nov 2000 A
6169891 Gorham Jan 2001 B1
6169901 Boucher Jan 2001 B1
6169902 Kawamoto Jan 2001 B1
6173181 Losh Jan 2001 B1
6178505 Schneider Jan 2001 B1
6178506 Quick, Jr. Jan 2001 B1
6181935 Gossman Jan 2001 B1
6181939 Ahvenainen Jan 2001 B1
6188354 Soliman Feb 2001 B1
6188752 Lesley Feb 2001 B1
6188909 Alanara Feb 2001 B1
6189098 Kaliski, Jr. Feb 2001 B1
6195557 Havinis Feb 2001 B1
6198431 Gibson Mar 2001 B1
6199045 Giniger Mar 2001 B1
6199113 Alegre Mar 2001 B1
6205330 Winbladh Mar 2001 B1
6208290 Krasner Mar 2001 B1
6208854 Roberts Mar 2001 B1
6215441 Moeglein Apr 2001 B1
6219557 Havinis Apr 2001 B1
6223046 Hamill-Keays Apr 2001 B1
6226529 Bruno May 2001 B1
6239742 Krasner May 2001 B1
6247135 Feaugue Jun 2001 B1
6249680 Wax Jun 2001 B1
6249744 Morita Jun 2001 B1
6249873 Richard Jun 2001 B1
6253074 Carlsson Jun 2001 B1
6253203 O'Flaherty Jun 2001 B1
6260147 Quick, Jr. Jul 2001 B1
6266614 Alumbaugh Jul 2001 B1
6275692 Skog Aug 2001 B1
6275849 Ludwig Aug 2001 B1
6278701 Ayyagari Aug 2001 B1
6289373 Dezonno Sep 2001 B1
6297768 Allen, Jr. Oct 2001 B1
6307504 Sheynblat Oct 2001 B1
6308269 Proidl Oct 2001 B2
6313786 Sheynblat et al. Nov 2001 B1
6317594 Gossman et al. Nov 2001 B1
6321091 Holland Nov 2001 B1
6321092 Fitch Nov 2001 B1
6321257 Kotola Nov 2001 B1
6324542 Wright, Jr. et al. Nov 2001 B1
6327473 Soliman Dec 2001 B1
6327479 Mikkola Dec 2001 B1
6333919 Gaffney Dec 2001 B2
6360093 Ross Mar 2002 B1
6360102 Havinis Mar 2002 B1
6363254 Jones Mar 2002 B1
6367019 Ansell Apr 2002 B1
6370389 Isomursu Apr 2002 B1
6377209 Krasner Apr 2002 B1
6400314 Krasner Jun 2002 B1
6400958 Isomursu Jun 2002 B1
6411254 Moeglein Jun 2002 B1
6421002 Krasner Jul 2002 B2
6427001 Contractor Jul 2002 B1
6433734 Krasner Aug 2002 B1
6434381 Moore Aug 2002 B1
6442391 Johansson Aug 2002 B1
6449473 Raivisto Sep 2002 B1
6449476 Hutchison, IV Sep 2002 B1
6456852 Bar Sep 2002 B2
6463272 Wallace Oct 2002 B1
6477150 Maggenti Nov 2002 B1
6504491 Christians Jan 2003 B1
6505049 Dorenbosch Jan 2003 B1
6510387 Fuchs Jan 2003 B2
6512922 Burg Jan 2003 B1
6512930 Sandegren Jan 2003 B2
6515623 Johnson Feb 2003 B2
6519466 Pande Feb 2003 B2
6522682 Kohli Feb 2003 B1
6526026 Menon Feb 2003 B1
6529500 Pandharipande Mar 2003 B1
6529829 Turetzky Mar 2003 B2
6531982 White Mar 2003 B1
6538757 Sansone Mar 2003 B1
6539200 Schiff Mar 2003 B1
6539232 Hendrey et al. Mar 2003 B2
6539304 Chansarkar Mar 2003 B1
6542464 Takeda Apr 2003 B1
6542734 Abrol Apr 2003 B1
6542743 Soliman Apr 2003 B1
6549776 Joong Apr 2003 B1
6549844 Egberts Apr 2003 B1
6556832 Soliman Apr 2003 B1
6560461 Fomukong May 2003 B1
6560534 Abraham May 2003 B2
6564261 Gudjonsson May 2003 B1
6570530 Gaal May 2003 B2
6571095 Koodli May 2003 B1
6574558 Kohli Jun 2003 B2
6580390 Hay Jun 2003 B1
6584552 Kuno Jun 2003 B1
6587691 Granstam Jul 2003 B1
6594500 Bender Jul 2003 B2
6597311 Sheynblat Jul 2003 B2
6600927 Hamilton Jul 2003 B2
6603973 Foladare Aug 2003 B1
6606495 Korpi Aug 2003 B1
6606554 Edge Aug 2003 B2
6609004 Morse Aug 2003 B1
6611757 Brodie Aug 2003 B2
6618670 Chansarkar Sep 2003 B1
6621452 Knockeart Sep 2003 B2
6621810 Leung Sep 2003 B1
6628233 Knockeart Sep 2003 B2
6633255 Krasner Oct 2003 B2
6640184 Rabe Oct 2003 B1
6650288 Pitt Nov 2003 B1
6661372 Girerd Dec 2003 B1
6665539 Sih Dec 2003 B2
6665541 Krasner Dec 2003 B1
6671620 Garin Dec 2003 B1
6677894 Sheynblat Jan 2004 B2
6680694 Knockeart Jan 2004 B1
6687504 Raith Feb 2004 B1
6691019 Seeley Feb 2004 B2
6694258 Johnson Feb 2004 B2
6694351 Shaffer Feb 2004 B1
6697629 Grilli Feb 2004 B1
6698195 Hellinger Mar 2004 B1
6701144 Kirbas Mar 2004 B2
6703971 Pande Mar 2004 B2
6703972 Van Diggelen Mar 2004 B2
6704651 Van Diggelen Mar 2004 B2
6707421 Drury Mar 2004 B1
6714793 Carey Mar 2004 B1
6718174 Vayanos Apr 2004 B2
6720915 Sheynblat Apr 2004 B2
6721578 Minear Apr 2004 B2
6721871 Piispanen Apr 2004 B2
6724342 Bloebaum Apr 2004 B2
6725159 Krasner Apr 2004 B2
6728701 Stoica Apr 2004 B1
6731940 Nagendran May 2004 B1
6734821 Van Diggelen May 2004 B2
6738013 Orler May 2004 B2
6738800 Aquilon May 2004 B1
6741842 Goldberg May 2004 B2
6744856 Karnik Jun 2004 B2
6744858 Ryan Jun 2004 B1
6745038 Callaway, Jr. Jun 2004 B2
6747596 Orler Jun 2004 B2
6748195 Phillips Jun 2004 B1
6751464 Burg Jun 2004 B1
6756938 Zhao Jun 2004 B2
6757544 Rangarajan Jun 2004 B2
6771742 McCalmont Aug 2004 B2
6772340 Peinado Aug 2004 B1
6775267 Kung Aug 2004 B1
6775534 Lindgren Aug 2004 B2
6775655 Peinado Aug 2004 B1
6775802 Gaal Aug 2004 B2
6778136 Gronemeyer Aug 2004 B2
6778885 Agashe Aug 2004 B2
6781963 Crockett Aug 2004 B2
6788249 Farmer Sep 2004 B1
6795444 Vo Sep 2004 B1
6795699 McCraw Sep 2004 B1
6799049 Zellner Sep 2004 B1
6799050 Krasner Sep 2004 B1
6801159 Swope Oct 2004 B2
6804524 Vandermeijden Oct 2004 B1
6807534 Erickson Oct 2004 B1
6810323 Bullock Oct 2004 B1
6813264 Vassilovski Nov 2004 B2
6813560 Van Diggelen Nov 2004 B2
6816111 Krasner Nov 2004 B2
6816710 Krasner Nov 2004 B2
6816719 Heinonen Nov 2004 B1
6816734 Wong Nov 2004 B2
6820269 Baucke et al. Nov 2004 B2
6829475 Lee Dec 2004 B1
6832373 O'Neill Dec 2004 B2
6839020 Geier Jan 2005 B2
6839021 Sheynblat Jan 2005 B2
6839417 Weisman Jan 2005 B2
6842715 Gaal Jan 2005 B1
6847618 Laursen Jan 2005 B2
6847822 Dennison Jan 2005 B1
6853916 Fuchs Feb 2005 B2
6856282 Mauro Feb 2005 B2
6861980 Rowitch Mar 2005 B1
6865171 Nilsson Mar 2005 B1
6865395 Riley Mar 2005 B2
6867733 Sandhu Mar 2005 B2
6867734 Voor Mar 2005 B2
6873854 Crockett Mar 2005 B2
6876734 Summers Apr 2005 B1
6882850 McConnell et al. Apr 2005 B2
6885940 Brodie Apr 2005 B2
6888497 King May 2005 B2
6888932 Snip May 2005 B2
6895238 Newell May 2005 B2
6895249 Gaal May 2005 B2
6900758 Mann May 2005 B1
6903684 Simic Jun 2005 B1
6904029 Fors Jun 2005 B2
6907224 Younis Jun 2005 B2
6907238 Leung Jun 2005 B2
6912230 Salkini Jun 2005 B1
6912395 Benes Jun 2005 B2
6912545 Lundy Jun 2005 B1
6915208 Garin Jul 2005 B2
6917331 Gronemeyer Jul 2005 B2
6930634 Peng Aug 2005 B2
6937187 Van Diggelen Aug 2005 B2
6937872 Krasner Aug 2005 B2
6940826 Simard Sep 2005 B1
6940950 Dickinson Sep 2005 B2
6941144 Stein Sep 2005 B2
6944540 King Sep 2005 B2
6947772 Minear Sep 2005 B2
6950058 Davis Sep 2005 B1
6957068 Hutchison Oct 2005 B2
6957073 Bye Oct 2005 B2
6961562 Ross Nov 2005 B2
6963557 Knox Nov 2005 B2
6965754 King Nov 2005 B2
6965767 Maggenti Nov 2005 B2
6968044 Beason Nov 2005 B2
6970917 Kushwaha Nov 2005 B1
6973320 Brown Dec 2005 B2
6975266 Abraham Dec 2005 B2
6978453 Rao Dec 2005 B2
6980816 Rohler Dec 2005 B2
6985747 Chithambaram Jan 2006 B2
6993355 Pershan Jan 2006 B1
6996720 DeMello Feb 2006 B1
6999782 Shaughnessy Feb 2006 B2
7024321 Deninger Apr 2006 B1
7024393 Peinado Apr 2006 B1
7047411 DeMello May 2006 B1
7065351 Carter Jun 2006 B2
7065507 Mohammed Jun 2006 B2
7072667 Olrik Jul 2006 B2
7079857 Maggenti Jul 2006 B2
7103018 Hansen Sep 2006 B1
7103574 Peinado Sep 2006 B1
7106717 Rousseau Sep 2006 B2
7113128 Pitt Sep 2006 B1
7136466 Gao Nov 2006 B1
7136838 Peinado Nov 2006 B1
7151946 Maggenti Dec 2006 B2
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
7194249 Phillips Mar 2007 B2
7200380 Havlark Apr 2007 B2
7209758 Moll Apr 2007 B1
7209969 Lahti Apr 2007 B2
7218940 Niemenmaa May 2007 B2
7221959 Lindqvist May 2007 B2
7245900 Lamb Jul 2007 B1
7246187 Ezra Jul 2007 B1
7260186 Zhu Aug 2007 B2
7260384 Bales Aug 2007 B2
7269428 Wallenius Sep 2007 B1
7302582 Snapp Nov 2007 B2
7321773 Hines Jan 2008 B2
7330899 Wong Feb 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
7392240 Scriffignano Jun 2008 B2
7394896 Norton Jul 2008 B2
7412049 Koch Aug 2008 B1
7424293 Zhu Sep 2008 B2
7426380 Hines Sep 2008 B2
7428571 Ichimura Sep 2008 B2
7436785 McMullen Oct 2008 B1
7440442 Grabelsky Oct 2008 B2
7450951 Vimpari Nov 2008 B2
7453990 Welenson Nov 2008 B2
7495608 Chen Feb 2009 B1
7519353 Stevens Apr 2009 B2
7573982 Breen Aug 2009 B2
7602886 Beech Oct 2009 B1
7617287 Vella Nov 2009 B2
7623447 Faccin Nov 2009 B1
7702081 Klesper Apr 2010 B1
7747258 Farmer Jun 2010 B2
7764961 Zhu Jul 2010 B2
7783297 Ishii Aug 2010 B2
7787611 Kotelly Aug 2010 B1
7881233 Bieselin Feb 2011 B2
7937067 Maier May 2011 B2
8005683 Tessel Aug 2011 B2
8027658 Suryanarayana Sep 2011 B2
8060389 Johnson Nov 2011 B2
8150363 Dickinson et al. Apr 2012 B2
20010011247 O'Flaherty Aug 2001 A1
20010040886 Jimenez Nov 2001 A1
20020037735 Maggenti Mar 2002 A1
20020052214 Maggenti May 2002 A1
20020058515 Holler May 2002 A1
20020061760 Maggenti May 2002 A1
20020069529 Wieres Jun 2002 A1
20020077083 Zellner Jun 2002 A1
20020077084 Zellner Jun 2002 A1
20020077118 Zellner Jun 2002 A1
20020077897 Zellner Jun 2002 A1
20020085538 Leung Jul 2002 A1
20020086676 Hendrey Jul 2002 A1
20020102996 Jenkins Aug 2002 A1
20020102999 Maggenti Aug 2002 A1
20020111172 DeWolf Aug 2002 A1
20020112047 Kushwaha Aug 2002 A1
20020118650 Jagadeesan Aug 2002 A1
20020118796 Menard Aug 2002 A1
20020123327 Vataja Sep 2002 A1
20020126656 Park Sep 2002 A1
20020158777 Flick Oct 2002 A1
20020173317 Nykanen Nov 2002 A1
20020191595 Mar Dec 2002 A1
20030009277 Fan Jan 2003 A1
20030009602 Jacobs Jan 2003 A1
20030012148 Peters Jan 2003 A1
20030013449 Hose Jan 2003 A1
20030016804 Sheha Jan 2003 A1
20030026245 Ejzak Feb 2003 A1
20030037163 Kitada Feb 2003 A1
20030040272 Lelievre Feb 2003 A1
20030044654 Holt Mar 2003 A1
20030065788 Salomaki Apr 2003 A1
20030072318 Lam Apr 2003 A1
20030078064 Chan Apr 2003 A1
20030081557 Mettala May 2003 A1
20030086539 McCalmont May 2003 A1
20030096623 Kim May 2003 A1
20030101329 Lahti May 2003 A1
20030101341 Kettler May 2003 A1
20030103484 Oommen Jun 2003 A1
20030108176 Kung Jun 2003 A1
20030109245 McCalmont Jun 2003 A1
20030114157 Spitz Jun 2003 A1
20030118160 Holt Jun 2003 A1
20030119521 Tipnis Jun 2003 A1
20030119528 Pew Jun 2003 A1
20030137961 Tsirtsis Jul 2003 A1
20030148757 Meer Aug 2003 A1
20030153340 Crockett Aug 2003 A1
20030153341 Crockett Aug 2003 A1
20030153342 Crockett Aug 2003 A1
20030153343 Crockett Aug 2003 A1
20030161298 Bergman Aug 2003 A1
20030186709 Rhodes Oct 2003 A1
20030196105 Fineberg Oct 2003 A1
20030204640 Sahinoja Oct 2003 A1
20030223381 Schroderus Dec 2003 A1
20040002326 Maher Jan 2004 A1
20040032485 Stephens Feb 2004 A1
20040043775 Kennedy Mar 2004 A1
20040044623 Wake Mar 2004 A1
20040047461 Weisman et al. Mar 2004 A1
20040068724 Gardner Apr 2004 A1
20040076277 Kuusinen Apr 2004 A1
20040098497 Banet May 2004 A1
20040132465 Mattila Jul 2004 A1
20040150518 Phillips Aug 2004 A1
20040152493 Phillips Aug 2004 A1
20040176123 Chin Sep 2004 A1
20040181689 Kiyoto Sep 2004 A1
20040184584 McCalmont Sep 2004 A1
20040190497 Knox Sep 2004 A1
20040192271 Eisner Sep 2004 A1
20040198332 Lundsgaard Oct 2004 A1
20040198386 Dupray Oct 2004 A1
20040203575 Chin Oct 2004 A1
20040203732 Brusilovsky Oct 2004 A1
20040205151 Sprigg Oct 2004 A1
20040229632 Flynn Nov 2004 A1
20040242238 Wang Dec 2004 A1
20040247090 Nurmela Dec 2004 A1
20040258021 Kashimoto Dec 2004 A1
20040267445 De Luca Dec 2004 A1
20050003797 Baldwin Jan 2005 A1
20050021769 Kim Jan 2005 A1
20050028034 Gantman Feb 2005 A1
20050030977 Casey Feb 2005 A1
20050039178 Marolia Feb 2005 A1
20050041578 Huotari Feb 2005 A1
20050043037 Loppe Feb 2005 A1
20050048987 Glass Mar 2005 A1
20050063519 James Mar 2005 A1
20050071671 Karaoguz Mar 2005 A1
20050074107 Renner Apr 2005 A1
20050078612 Lang Apr 2005 A1
20050083911 Grabelsky Apr 2005 A1
20050085257 Laird Apr 2005 A1
20050086467 Asokan Apr 2005 A1
20050090236 Schwinke Apr 2005 A1
20050838911 Chuang Apr 2005
20050101335 Kelly May 2005 A1
20050107673 Ball May 2005 A1
20050111630 Potorny May 2005 A1
20050112030 Gaus May 2005 A1
20050119012 Merheb Jun 2005 A1
20050134504 Harwood Jun 2005 A1
20050136885 Kaltsukis Jun 2005 A1
20050149430 Williams Jul 2005 A1
20050174991 Keagy Aug 2005 A1
20050186937 Graham Aug 2005 A1
20050190892 Dawson Sep 2005 A1
20050192822 Hartenstein Sep 2005 A1
20050201358 Nelson Sep 2005 A1
20050201529 Nelson Sep 2005 A1
20050209995 Aksu Sep 2005 A1
20050213716 Zhu Sep 2005 A1
20050232252 Hoover Oct 2005 A1
20050238156 Turner Oct 2005 A1
20050255857 Kim Nov 2005 A1
20050259675 Tuohino Nov 2005 A1
20050261002 Cheng Nov 2005 A1
20050265318 Khartabil Dec 2005 A1
20050271029 Iffland Dec 2005 A1
20050282518 D'Evelyn 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
20060053225 Poikselka Mar 2006 A1
20060058049 McLaughlin Mar 2006 A1
20060058102 Nguyen et al. Mar 2006 A1
20060068753 Karpen Mar 2006 A1
20060069503 Suomela et al. Mar 2006 A1
20060072729 Lee et al. Apr 2006 A1
20060077911 Shaffer Apr 2006 A1
20060078094 Breen Apr 2006 A1
20060088152 Green Apr 2006 A1
20060104306 Adamczyk May 2006 A1
20060120517 Moon Jun 2006 A1
20060128395 Muhonen Jun 2006 A1
20060135132 Cai Jun 2006 A1
20060135177 Winterbottom Jun 2006 A1
20060188083 Breen Aug 2006 A1
20060193447 Schwartz Aug 2006 A1
20060212558 Sahinoja Sep 2006 A1
20060212562 Kushwaha Sep 2006 A1
20060222151 Goldman et al. Oct 2006 A1
20060233338 Venkata Oct 2006 A1
20060234639 Kushwaha Oct 2006 A1
20060234698 Fok Oct 2006 A1
20060250987 White Nov 2006 A1
20060258380 Liebowitz Nov 2006 A1
20060259365 Agarwal et al. Nov 2006 A1
20060281437 Cook Dec 2006 A1
20060293024 Benco Dec 2006 A1
20060293066 Edge Dec 2006 A1
20070003024 Olivier Jan 2007 A1
20070014282 Mitchell Jan 2007 A1
20070019614 Hoffmann Jan 2007 A1
20070021908 Jaugilas Jan 2007 A1
20070022011 Altberg et al. Jan 2007 A1
20070026854 Nath Feb 2007 A1
20070026871 Wager Feb 2007 A1
20070027997 Polk Feb 2007 A1
20070030539 Nath Feb 2007 A1
20070036139 Patel Feb 2007 A1
20070041513 Gende Feb 2007 A1
20070049288 Lamprecht Mar 2007 A1
20070060097 Edge Mar 2007 A1
20070081635 Croak Apr 2007 A1
20070115941 Patel May 2007 A1
20070121601 Kikinis May 2007 A1
20070149213 Lamba Jun 2007 A1
20070160036 Smith Jul 2007 A1
20070162228 Mitchell Jul 2007 A1
20070201623 Hines Aug 2007 A1
20070206568 Silver Sep 2007 A1
20070206613 Silver Sep 2007 A1
20070242660 Xu Oct 2007 A1
20070263610 Mitchell Nov 2007 A1
20070263611 Mitchell Nov 2007 A1
20070270164 Maier Nov 2007 A1
20070293205 Henderson Dec 2007 A1
20080032703 Krumm Feb 2008 A1
20080037715 Prozeniuk Feb 2008 A1
20080063153 Krivorot Mar 2008 A1
20080065775 Polk Mar 2008 A1
20080081646 Morin Apr 2008 A1
20081178595 Shahidi May 2008
20080160953 Mia Jul 2008 A1
20080214202 Toomey Sep 2008 A1
20090128404 Martino May 2009 A1
20100003954 Greene Jan 2010 A1
20100119049 Clark May 2010 A1
20100198933 Smith Aug 2010 A1
20110113060 Martini May 2011 A1
20110273568 Lagassey Nov 2011 A1
20120001750 Monroe Jan 2012 A1
20120189107 Dickinson Jul 2012 A1
Foreign Referenced Citations (8)
Number Date Country
PCTSE9801887 Oct 1998 WO
WO9922546 May 1999 WO
PCTGB0004499 Nov 2000 WO
WO0211407 Feb 2002 WO
PCTUS03028369 Oct 2003 WO
WO2004098213 Nov 2004 WO
PCTUS05022090 Jun 2005 WO
WO2005051033 Jun 2005 WO
Non-Patent Literature Citations (16)
Entry
Intrado Inc., Qwest Detailed SR/ALI to MPC/GMLC Interface Specification for TCP/IP Implementation of TIA/EIA/J-STD-036 E2 with Phase I Location Description Addition, Intrado Informed Response; Apr. 2004; Issue 1.11; pp. 1-57.
Nars Haran, U.S. Cellular, Packet Data—Roaming and LBS Overview, Nov. 2, 2007, pp. 1-15.
Andrew Yeow, BCE, LBS Roaming Summit, Sep. 19, 2006, pp. 1-8.
Mike McMullen, Sprint, LBS Roaming Summit, Sep. 19, 2006.
Bhalla et al, TELUS, Technology Strategy—LBS Roaming Summit, Sep. 19, 2006.
Alfredo Aguirre, Ilusacell, First and Only Carrier in Mexico with a 3G CDMA Network, 2007.
International Search Report in PCT/US2008/01441dated May 16, 2008.
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.
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.
European Search Report in Appl. No. EP06827172 dated Dec. 29, 2009.
International Search Report in PCT/US/2010/01938 dated Sep. 30, 2010.
Location Based Services V2 Roaming Support (non proprietary), 80-V8470-2NP A, dated Jan. 27, 2005, pp. 1-56.
Schulzrinne et al., Emergency Services for Internet Telephony Systems draft-schulzrinne-sipping-emergency-arch, IETF Standard Working Draft, Feb. 4, 2004, 1-22.
European Search Report in European appl. No. 06851433.0-2413 dated Aug. 8, 2008.
“Location Services (LCS); Functional Description; stage 2; ETSI TS 101 724,” ETSI Standards, Jun. 2004 (2004-2006), XPO14016068, sect. 4, section 5.6.6., fig 3, sect. 7.6.2, fig. 30.
Intrado MSAG Prep for E911 Program and Documentation. Intrado Inc., Longmont, Co. Sep. 14, 2006. Acesses: Nov. 8, 2011. Idaho PSAP Standards Committee. Idaho Emergency Communications Commission, http://idahodispatch.com/index.php?option+com—documan&task+doc—download&gid+3&itemid+7.
Related Publications (1)
Number Date Country
20120287826 A1 Nov 2012 US
Continuations (1)
Number Date Country
Parent 11354861 Feb 2006 US
Child 13437213 US