WO2005062778A2 - ENHANCED E911 LOCATION INFORMATION USING VOICE OVER INTERNET PROTOCOL (VoIP) - Google Patents

ENHANCED E911 LOCATION INFORMATION USING VOICE OVER INTERNET PROTOCOL (VoIP) Download PDF

Info

Publication number
WO2005062778A2
WO2005062778A2 PCT/US2004/042370 US2004042370W WO2005062778A2 WO 2005062778 A2 WO2005062778 A2 WO 2005062778A2 US 2004042370 W US2004042370 W US 2004042370W WO 2005062778 A2 WO2005062778 A2 WO 2005062778A2
Authority
WO
WIPO (PCT)
Prior art keywords
voip
call
esrk
psap
voip device
Prior art date
Application number
PCT/US2004/042370
Other languages
French (fr)
Other versions
WO2005062778A3 (en
Inventor
Richard Dickinson
Roger Marshall
Steven P. Helme
Original Assignee
Telecommunication Systems Inc.
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Family has litigation
First worldwide family litigation filed litigation Critical https://patents.darts-ip.com/?family=34677561&utm_source=google_patent&utm_medium=platform_link&utm_campaign=public_patent_search&patent=WO2005062778(A2) "Global patent litigation dataset” by Darts-ip is licensed under a Creative Commons Attribution 4.0 International License.
Application filed by Telecommunication Systems Inc. filed Critical Telecommunication Systems Inc.
Priority to EP04814540A priority Critical patent/EP1709789A4/en
Publication of WO2005062778A2 publication Critical patent/WO2005062778A2/en
Publication of WO2005062778A3 publication Critical patent/WO2005062778A3/en

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M11/00—Telephonic communication systems specially adapted for combination with other electrical systems
    • H04M11/04—Telephonic communication systems specially adapted for combination with other electrical systems with alarm systems, e.g. fire, police or burglar alarm systems
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/66—Arrangements for connecting between networks having differing types of switching systems, e.g. gateways
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M2242/00—Special services or facilities
    • H04M2242/04—Special services or facilities for emergency applications
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M3/00—Automatic or semi-automatic exchanges
    • H04M3/42—Systems providing special services or facilities to subscribers
    • H04M3/50—Centralised arrangements for answering calls; Centralised arrangements for recording messages for absent or busy subscribers ; Centralised arrangements for recording messages
    • H04M3/51—Centralised call answering arrangements requiring operator intervention, e.g. call or contact centers for telemarketing
    • H04M3/5116—Centralised call answering arrangements requiring operator intervention, e.g. call or contact centers for telemarketing for emergency applications
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/50—Connection management for emergency connections

Definitions

  • This invention relates generally to VoIP communication carriers. More particularly, it relates to location-based services for the provision of E-9-1-1 emergency services by the VoIP industry.
  • Enhanced 911 is defined by the transmission of callback number and location information.
  • E911 may be implemented for landline and/or wireless 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 wireless.
  • PSAPs Public Safety Access Points
  • VoIP Voice-Over-Internet Protocol
  • VoIP Voice-Over-Internet Protocol
  • VoIP Voice-Over-Internet Protocol
  • the VoIP device is physically connected to a static data cable at a "home" address. 2.
  • the VoIP device is physically connected to a data cable at a location different than its "home" address. For instance, a laptop computer device utilized away from home as a VoIP communication device would be a VoIP 'visitor' device as described by this scenario. 3.
  • the VoIP device is wireleless, physically disconnected from any data cable. In this situation, the VoIP device connects to the VoIP network via cellular or WiFi technology.
  • Conventional VoIP voice gateways are typically located in only a few places across the country. Thus, any 911 call originating in a city such as Miami, for example, may initially be routed to the public safety answer point (PSAP) in, e.g., Minneapolis if the VoIP gateway happens to be located in Minneapolis.
  • PSAP public safety answer point
  • a conventional architecture routes VoIP 911 calls to a designated PSAP.
  • VoIP 911 calls to a designated PSAP.
  • VoIP switch 220 in the VoIP carrier's network.
  • the VoIP switch 220 communicates with a Message Servicing Center (MSC) 230.
  • MSC Message Servicing Center
  • the MSC 230 can determine which PSAP has jurisdiction for that address. The MSC 230 then communicates back to the VoIP switch 220 a 10-digit telephone number for that PSAP. The VoIP Switch 220 then converts the IP call to TDM and routes the call via the PSTN to the designated PSAP using the provided 10-digit number.
  • a primary challenge results from the fact that the E911 network is not accessible via the Public Switched Telephone Network (PSTN); all enhanced 911 calls must be routed via dedicated local voice trunks to a selective router that in turn routes the call to the PSAP. Calls routed via the PSTN arrive at the PSAP without callback number or location information.
  • PSTN Public Switched Telephone Network
  • Provision of location information to the PSAP via the PSTN also circumvents specific PSAP hardware (e.g., CAD, GIS) designed to facilitate dispatching of responders and tracking the location of the wireless caller.
  • PSAP hardware e.g., CAD, GIS
  • VoIP users all features relating to E911 services enjoyed by non- VoIP users, e.g., call back phone number and location information provided to a public safety answer point (PSAP).
  • PSAP public safety answer point
  • a method and apparatus for routing an ESRK to public safety answer point (PSAP) relating to a call from a VoIP device comprises provisioning a first local voice-over-Internet Protocol (VoIP) gateway.
  • VoIP voice-over-Internet Protocol
  • a first dedicated trunk line is established between the provisioned first local VoIP gateway and a first selective router associated with a first PSAP.
  • An ESRK is importantly associating a specific PSAP to a location of a VoIP device from which the E911 call originates.
  • the E911 call and ESRK are routed to specific PSAPs responsible for receiving E911 calls from the location from which the E911 call originates on the VoIP device.
  • Fig. 1 shows a block diagram of the architecture of the VoIP solution, in accordance with the principles of the present invention.
  • Fig. 2 shows a conventional architecture for providing 911 service to a VoIP device.
  • DETAILED DESCRIPTION OF ILLUSTRATIVE EMBODIMENTS The present invention provides an E-9-1-1 voice-over-IP (VoIP) solution, wherein a 911 call from a VoIP device is routed directly to the correct Public Safety Answer Point (PSAP) via dedicated trunks, together with correct location information and call-back number.
  • PSAP Public Safety Answer Point
  • Fig. 1 shows a block diagram of the architecture of the VoIP solution, in accordance with the principles of the present invention.
  • Option 2 proposed technology for providing enhanced 911 service from IP devices located at "home” or at “visitor” locations, physically connected to the VoIP network, via cable.
  • Option 3 proposed technology for providing enhanced 911 service from wireless IP devices.
  • VoIP gateways 100 are implemented locally, e.g., one within each local access and transport area (LATA).
  • the local VoIP gateways 100 accept VoIP packetized data inbound, and convert it to standard wireline voice calls. Calls are routed to an IP address at the VoIP gateway, which then egresses the call to a voice port at a selective router. Suitable VoIP gateways are otherwise conventionally known and commercially available. Dedicated voice trunks 107-109 are installed between each local VoIP gateway 100 and appropriate selective routers 150a-150c
  • selective routers 150 examples include Centralized Automatic Message Accounting (CAMA) trunks 107, Signaling System #7 (SS7) voice trunks 108, and/or FG-D trunks 109 are installed between each local VoIP gateway 100 and a respective group of selective routers 150.
  • the selective routers 150 are provisioned as desired and otherwise conventionally known.
  • An Automatic Location Identification (ALI) database 190 is included, and is provisioned with Emergency Service Routing Keys
  • ESRKs Transport Control Protocol/Internet Protocol
  • TCP/IP Transport Control Protocol/Internet Protocol
  • VoIP device 352 to the correct PSAP.
  • a caller using the VoIP device 352 dials "911" on their VoIP device 352.
  • the VoIP device 352 provides location information with the E911 call.
  • the VoIP switch 120b servicing that particular VoIP device 352 receives the E911 call, and queries the wireless carrier MSC 130b for routing information.
  • the query to the MSC 130b includes a callback number, and location information (if mobile).
  • the MSC 130b relates location to specific PSAPs.
  • the location is static, the phone number and location will already be established in the MSC database 130b,. If the VoIP device 352 is mobile, the caller provides location information at the time of log-on. This caller information will then accompany the E911 call. In certain scenarios such as even in static situations, the location information may accompany the E911 call.
  • the , MSC 130b upon determination of the appropriate PSAP to receive the E911 call, the , MSC 130b responds with an Emergency Service Routing Key (ESRK), plus IP routing instructions to the VoIP switch 120b.
  • ESRK is a 10-digit number compatible with the selective router that serves that particular PSAP. ESRKs uniquely identify a specific PSAP.
  • ESRK is a 10-digit number compatible with the selective router that serves that particular PSAP. ESRKs uniquely identify a specific PSAP.
  • FIG. 1 only the selective routers 150 compatible with one local VoIP gateway 100 are shown, as are PSAPs 200-206 having dedicated E911 trunks associated with each of those selective routers 150.
  • PSAPs 200-206 having dedicated E911 trunks associated with each of those selective routers 150.
  • the person of skill in the art will understand from Fig. 1 that similar local Gateway's will be implemented throughout a large area, e.g., across state lines or even countries, each having associated selective routers, and each selective router having one or more dedicated trunk line to a given one or more PSAPs.
  • the ESRK provided by the MSC 130b to the VoIP switch 120b is unique to the particular PSAP servicing the location that the wireless VoIP device 352 is calling from.
  • the IP routing instructions provided by the MSC 130b to the VoIP switch 120b identify the IP address of the correct local VoIP gateway in the local access and transport area (LATA) where the compatible selective router exists. For example, it might be the local VoIP gateway 100 shown in Fig. 1 , or it might instead be another local VoIP gateway associated with another local area (e.g., another LATA).
  • the VoIP switch 120b routes the VoIP E911 call to the designated VoIP gateway 100.
  • the routed VoIP E911 call includes the ESRK.
  • the VoIP gateway 100 recognizes the ESRK, and selects a corresponding voice egress trunk (e.g., CAMA, SS7 or FG-D) 107-109.
  • the VoIP gateway 100 converts the VoIP data to voice, and egresses the E911 call to the proper selective router 150a, 150b or 150c on the selected trunk 107-109.
  • the existing E911 infrastructure delivers the E911 call to the proper PSAP 200, 202, 204 or
  • the relevant selective router 150a, 150b or 150c previously provisioned to recognize the ESRK in the AN I field of the
  • PSAP 200, 202, 204 or 206 receives the E911 voice call, and using the
  • ESRK queries the ALI database 190 for the location of the caller, and for call-back information.
  • the ALI database 190 steers the ESRK to the appropriate
  • step 2 the VoIP switch 120b servicing that particular VoIP device 352 receives the E911 call, and queries the wireless carrier MSC
  • the query to the MSC 130b includes a callback number, but no location information.
  • the MSC 130b initiates a GPOSREQ to the Position Determining Equipment (PDE) 400 serving the wireless carrier that provides the wireless coverage for the IP device.
  • PDE Position Determining Equipment
  • a PDE is a position determining device that determines a position, e.g., a latitude and longitude in the wireless Phase 2 world.
  • Many wireless VoIP devices utilize cellular technology, thus positioning equipment used for cellular devices may be utilized for VoIP devices, given the present invention.
  • the PDE 400 using otherwise conventional techniques, responds with a gposreq response that contains the latitude and longitude of the wireless IP device.
  • the MPC 130b relates location to a specific PSAP.

Abstract

An E-9-1-1 voice-over-IP (VoIP) solution is provided wherein a 911 call from a wireless VoIP device is routed directly to the correct Public Safety Answer Point (PSAP) via dedicated trunks, together with correct location information and call-back number. VoIP gateways are implemented locally, at least one per LATA, and accept VoIP packetized data inbound, and convert it to standard wireline voice calls. Calls are routed to an IP address at the VoIP gateway, which then egresses the call to a voice port at a selective router. Dedicated voice trunks (CAMA, SS7, FG-D) are installed between each local VoIP gateway and appropriate selective routers. An Automatic Location Identification (ALI) database is provisioned with ESRKs dedicated for VoIP use. TCP/IP circuits may be established between some or all of the various local VoIP gateways.

Description

ENHANCED E911 LOCATION INFORMATION USING VOICE OVER INTERNET PROTOCOL (VoIP)
BACKGROUND OF THE INVENTION 1. Field of the Invention This invention relates generally to VoIP communication carriers. More particularly, it relates to location-based services for the provision of E-9-1-1 emergency services by the VoIP industry.
2. Background of 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.
E911 may be implemented for landline and/or wireless 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 wireless. Voice-Over-Internet Protocol (VoIP) is a technology that 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. As people adopt voice-over-IP (VoIP) technology for routine communications, the inventor herein recognizes that there is a growing need to be able to access E911 services including provision of location information from a VoIP device. The existing E911 infrastructure is built upon copper wire line voice technology and is not compatible with VoIP. There are at least three VoIP scenarios that require E911 service: 1. The VoIP device is physically connected to a static data cable at a "home" address. 2. The VoIP device is physically connected to a data cable at a location different than its "home" address. For instance, a laptop computer device utilized away from home as a VoIP communication device would be a VoIP 'visitor' device as described by this scenario. 3. The VoIP device is wireleless, physically disconnected from any data cable. In this situation, the VoIP device connects to the VoIP network via cellular or WiFi technology. Conventional VoIP voice gateways are typically located in only a few places across the country. Thus, any 911 call originating in a city such as Miami, for example, may initially be routed to the public safety answer point (PSAP) in, e.g., Minneapolis if the VoIP gateway happens to be located in Minneapolis. Moreover, the call will not be "enhanced". That is, it will not provide any location or callback information to the dispatcher. This problem has been partially resolved as described in Fig. 2. As shown in Fig. 2, a conventional architecture routes VoIP 911 calls to a designated PSAP. However, such architecture fails to provide "enhanced" service for VoIP devices. In particular, as shown in Option 1 , an IP device 250 utilizing VoIP protocols for voice communications dials 9-1-1. The VoIP device 250 is serviced by a VoIP switch 220 in the VoIP carrier's network. The VoIP switch 220 communicates with a Message Servicing Center (MSC) 230. Using a database that relates the devices callback number or IP address to the owner's address, the MSC 230 can determine which PSAP has jurisdiction for that address. The MSC 230 then communicates back to the VoIP switch 220 a 10-digit telephone number for that PSAP. The VoIP Switch 220 then converts the IP call to TDM and routes the call via the PSTN to the designated PSAP using the provided 10-digit number. A primary challenge results from the fact that the E911 network is not accessible via the Public Switched Telephone Network (PSTN); all enhanced 911 calls must be routed via dedicated local voice trunks to a selective router that in turn routes the call to the PSAP. Calls routed via the PSTN arrive at the PSAP without callback number or location information. Provision of location information to the PSAP via the PSTN also circumvents specific PSAP hardware (e.g., CAD, GIS) designed to facilitate dispatching of responders and tracking the location of the wireless caller. There is a need for an architecture and methodology to allow VoIP users all features relating to E911 services enjoyed by non- VoIP users, e.g., call back phone number and location information provided to a public safety answer point (PSAP).
SUMMARY OF THE INVENTION In accordance with the principles of the present invention, a method and apparatus for routing an ESRK to public safety answer point (PSAP) relating to a call from a VoIP device comprises provisioning a first local voice-over-Internet Protocol (VoIP) gateway. A first dedicated trunk line is established between the provisioned first local VoIP gateway and a first selective router associated with a first PSAP. An ESRK is importantly associating a specific PSAP to a location of a VoIP device from which the E911 call originates. The E911 call and ESRK are routed to specific PSAPs responsible for receiving E911 calls from the location from which the E911 call originates on the VoIP device.
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, in which: Fig. 1 shows a block diagram of the architecture of the VoIP solution, in accordance with the principles of the present invention. Fig. 2 shows a conventional architecture for providing 911 service to a VoIP device. DETAILED DESCRIPTION OF ILLUSTRATIVE EMBODIMENTS The present invention provides an E-9-1-1 voice-over-IP (VoIP) solution, wherein a 911 call from a VoIP device is routed directly to the correct Public Safety Answer Point (PSAP) via dedicated trunks, together with correct location information and call-back number. In accordance with the present invention, local VoIP gateways are incorporated, and a centralized routing intelligence is implemented, to provide access to the existing E911 infrastructure. Fig. 1 shows a block diagram of the architecture of the VoIP solution, in accordance with the principles of the present invention. There are two additional options illustrated, in addition to the conventional option shown in Fig. 2. 1. Option 2: proposed technology for providing enhanced 911 service from IP devices located at "home" or at "visitor" locations, physically connected to the VoIP network, via cable. 2. Option 3: proposed technology for providing enhanced 911 service from wireless IP devices. In particular, as shown in Fig. 1 , VoIP gateways 100 are implemented locally, e.g., one within each local access and transport area (LATA). The local VoIP gateways 100 accept VoIP packetized data inbound, and convert it to standard wireline voice calls. Calls are routed to an IP address at the VoIP gateway, which then egresses the call to a voice port at a selective router. Suitable VoIP gateways are otherwise conventionally known and commercially available. Dedicated voice trunks 107-109 are installed between each local VoIP gateway 100 and appropriate selective routers 150a-150c
(referred to collectively herein as selective routers 150). Examples of common voice trunks include Centralized Automatic Message Accounting (CAMA) trunks 107, Signaling System #7 (SS7) voice trunks 108, and/or FG-D trunks 109 are installed between each local VoIP gateway 100 and a respective group of selective routers 150. The selective routers 150 are provisioned as desired and otherwise conventionally known. An Automatic Location Identification (ALI) database 190 is included, and is provisioned with Emergency Service Routing Keys
(ESRKs) dedicated for VoIP use as desired and otherwise conventionally known. Transport Control Protocol/Internet Protocol (TCP/IP) data circuits may be installed between various local VoIP gateways 100. For instance, additional IP circuits may be established between the local VoIP gateway(s) of other carriers to handle additional VoIP traffic. The message flow resulting from a VoIP call from a given IP device, e.g., IP device 352, is now described with reference to Fig. 1. As a descriptive example, assume a VoIP "E911" call is being placed by VoIP device 352 as shown by "Option 2" from the left side of Fig. 1. The following describes message flow to route that call directly to the correct PSAP, including the provision of location information of the
VoIP device 352 to the correct PSAP. In step 1 , a caller using the VoIP device 352 dials "911" on their VoIP device 352. In the given example, the VoIP device 352 provides location information with the E911 call. In step 2, the VoIP switch 120b servicing that particular VoIP device 352 receives the E911 call, and queries the wireless carrier MSC 130b for routing information. The query to the MSC 130b includes a callback number, and location information (if mobile). In step 3, the MSC 130b relates location to specific PSAPs.
If the location is static, the phone number and location will already be established in the MSC database 130b,. If the VoIP device 352 is mobile, the caller provides location information at the time of log-on. This caller information will then accompany the E911 call. In certain scenarios such as even in static situations, the location information may accompany the E911 call. In step 4, upon determination of the appropriate PSAP to receive the E911 call, the , MSC 130b responds with an Emergency Service Routing Key (ESRK), plus IP routing instructions to the VoIP switch 120b. The utilized ESRK is a 10-digit number compatible with the selective router that serves that particular PSAP. ESRKs uniquely identify a specific PSAP. In Fig. 1, only the selective routers 150 compatible with one local VoIP gateway 100 are shown, as are PSAPs 200-206 having dedicated E911 trunks associated with each of those selective routers 150. The person of skill in the art will understand from Fig. 1 that similar local Gateway's will be implemented throughout a large area, e.g., across state lines or even countries, each having associated selective routers, and each selective router having one or more dedicated trunk line to a given one or more PSAPs. The ESRK provided by the MSC 130b to the VoIP switch 120b is unique to the particular PSAP servicing the location that the wireless VoIP device 352 is calling from. The IP routing instructions provided by the MSC 130b to the VoIP switch 120b identify the IP address of the correct local VoIP gateway in the local access and transport area (LATA) where the compatible selective router exists. For example, it might be the local VoIP gateway 100 shown in Fig. 1 , or it might instead be another local VoIP gateway associated with another local area (e.g., another LATA). In step 5, the VoIP switch 120b routes the VoIP E911 call to the designated VoIP gateway 100. The routed VoIP E911 call includes the ESRK. In step 6, the VoIP gateway 100 recognizes the ESRK, and selects a corresponding voice egress trunk (e.g., CAMA, SS7 or FG-D) 107-109. The VoIP gateway 100 converts the VoIP data to voice, and egresses the E911 call to the proper selective router 150a, 150b or 150c on the selected trunk 107-109. In step 7, as in otherwise conventional techniques, upon reaching the selective router 150a, 150b or 150c, the existing E911 infrastructure delivers the E911 call to the proper PSAP 200, 202, 204 or
206 that is assigned to the location that the wireless VoIP device 352 is calling from. Thus, the relevant selective router 150a, 150b or 150c previously provisioned to recognize the ESRK in the AN I field of the
CAMA or SS7 voice E911 call, will route the E911 call to the appropriate PSAP 200, 202, 204 or 206. In step 8, as in otherwise conventional techniques, the
PSAP 200, 202, 204 or 206 receives the E911 voice call, and using the
ESRK, queries the ALI database 190 for the location of the caller, and for call-back information. The ALI database 190 steers the ESRK to the appropriate
MSC 130b, which in turn responds to the ALI query with the correct location and call-back information. The disclosed ALI query employs otherwise conventional PAM or E2+ protocols. The sequence of events for Option 1 would be similar as for the above described Option 2, except that the location information would already be stored at the MPC and would not necessarily need to forwarded by the device. Sequence of events for Option 3 (wireless IP device) would be as follows: In step 1 , a caller using the wireless VoIP device 355 dials
"911". In step 2, the VoIP switch 120b servicing that particular VoIP device 352 receives the E911 call, and queries the wireless carrier MSC
130b for routing information. The query to the MSC 130b includes a callback number, but no location information. In step 3, the MSC 130b initiates a GPOSREQ to the Position Determining Equipment (PDE) 400 serving the wireless carrier that provides the wireless coverage for the IP device. A PDE is a position determining device that determines a position, e.g., a latitude and longitude in the wireless Phase 2 world. Many wireless VoIP devices utilize cellular technology, thus positioning equipment used for cellular devices may be utilized for VoIP devices, given the present invention. The PDE 400, using otherwise conventional techniques, responds with a gposreq response that contains the latitude and longitude of the wireless IP device. The MPC 130b relates location to a specific PSAP. Subsequent steps in Option 3 are similar to those described with respect to Option 2. Implementation of E911 for VoIP callers as disclosed herein facilitates the migration of an individual PSAP to a pure VoIP environment, minimizing additional engineering as VoIP systems become more prevalent and revolutionize the telecom industry. 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

What is claimed is: 1. A method of routing an ESRK to public safety answer point (PSAP) relating to a call from a VoIP device, comprising: provisioning a first local voice-over-Internet Protocol (VoIP) gateway; establishing a first dedicated trunk line between said provisioned first local VoIP gateway and a first selective router associated with a first PSAP; use of an ESRK associating a specific PSAP to a location of said VoIP device from which said E911 call originates; and routing said E911 call and ESRK to specific PSAPs responsible for receiving E911 calls from said location from which said E911 call originates on said VoIP device.
2. The method of routing an ESRK to public safety answer point (PSAP) relating to a call from a VoIP device according to claim 1 , further comprising: establishing a TCP/IP communication channel between said first local VoIP gateway and said second local VoIP gateway.
3. The method of routing an ESRK to public safety answer point (PSAP) relating to a call from a VoIP device according to claim 1, further comprising: receiving a VoIP E911 call from a VoIP device; querying a Message Servicing Center (MSC) from a VoIP switch servicing said VoIP device for ESRK information; and receiving in response an ESRK.
4. The method of routing an ESRK to public safety answer point (PSAP) relating to a call from a VoIP device according to claim 3, further comprising: querying from said MSC an Automatic Location Identification (ALI) database for said ESRK information relating to an E911 call from a VoIP device.
5. The method of routing an ESRK to public safety answer point (PSAP) relating to a call from a VoIP device according to claim 1, wherein: said VoIP device is a wireless device that uses a PDE to determine it's location.
6. Apparatus for routing an ESRK to public safety answer point (PSAP) relating to a call from a VoIP device, comprising: means for provisioning a first local voice-over-Internet Protocol (VoIP) gateway; means for establishing a first dedicated trunk line between said provisioned first local VoIP gateway and a first selective router associated with a first PSAP; means for using an ESRK associating a specific PSAP to a location of said VoIP device from which said E911 call originates; and means for routing said E911 call and ESRK to specific PSAPs responsible for receiving E911 calls from said location from which said E911 call originates on said VoIP device.
7. The apparatus for routing an ESRK to public safety answer point (PSAP) relating to a call from a VoIP device according to claim 6, further comprising: means for establishing a TCP/IP communication channel between said first local VoIP gateway and said second local VoIP gateway.
8. The apparatus for routing an ESRK to public safety answer point (PSAP) relating to a call from a VoIP device according to claim 6, further comprising: means for receiving a VoIP E911 call from a VoIP device; means for querying a Message Servicing Center (MSC) from a VoIP switch servicing said VoIP device for ESRK information; and means for receiving in response an ESRK.
9. The apparatus for routing an ESRK to public safety answer point (PSAP) relating to a call from a VoIP device according to claim 8, further comprising: means for querying from said MSC an Automatic Location Identification (ALI) database for said ESRK information relating to an E911 call from a VoIP device.
10. The apparatus for routing an ESRK to public safety answer point (PSAP) relating to a call from a VoIP device according to claim 6, wherein: said VoIP device is a wireless device that uses a PDE to determine it's location.
PCT/US2004/042370 2003-12-19 2004-12-20 ENHANCED E911 LOCATION INFORMATION USING VOICE OVER INTERNET PROTOCOL (VoIP) WO2005062778A2 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
EP04814540A EP1709789A4 (en) 2003-12-19 2004-12-20 ENHANCED E911 LOCATION INFORMATION USING VOICE OVER INTERNET PROTOCOL (VoIP)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US10/739,292 2003-12-19
US10/739,292 US6940950B2 (en) 2003-12-19 2003-12-19 Enhanced E911 location information using voice over internet protocol (VoIP)

Publications (2)

Publication Number Publication Date
WO2005062778A2 true WO2005062778A2 (en) 2005-07-14
WO2005062778A3 WO2005062778A3 (en) 2005-09-15

Family

ID=34677561

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2004/042370 WO2005062778A2 (en) 2003-12-19 2004-12-20 ENHANCED E911 LOCATION INFORMATION USING VOICE OVER INTERNET PROTOCOL (VoIP)

Country Status (3)

Country Link
US (1) US6940950B2 (en)
EP (1) EP1709789A4 (en)
WO (1) WO2005062778A2 (en)

Families Citing this family (173)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9286294B2 (en) 1992-12-09 2016-03-15 Comcast Ip Holdings I, Llc Video and digital multimedia aggregator content suggestion engine
US7168084B1 (en) 1992-12-09 2007-01-23 Sedna Patent Services, Llc Method and apparatus for targeting virtual objects
EP1266321A4 (en) 2000-02-25 2003-05-21 Telecomm Systems Inc Prepaid short messaging
US7110773B1 (en) 2000-04-11 2006-09-19 Telecommunication Systems, Inc. Mobile activity status tracker
US7522911B2 (en) * 2000-04-11 2009-04-21 Telecommunication Systems, Inc. Wireless chat automatic status tracking
US8041817B2 (en) 2000-06-30 2011-10-18 At&T Intellectual Property I, Lp Anonymous location service for wireless networks
US7796998B1 (en) * 2000-08-01 2010-09-14 At&T Intellectual Property, I, L.P. Method and system for delivery of a calling party's location
US7245925B2 (en) 2000-12-19 2007-07-17 At&T Intellectual Property, Inc. System and method for using location information to execute an action
US7110749B2 (en) 2000-12-19 2006-09-19 Bellsouth Intellectual Property Corporation Identity blocking service from a wireless service provider
US7116977B1 (en) 2000-12-19 2006-10-03 Bellsouth Intellectual Property Corporation System and method for using location information to execute an action
US7130630B1 (en) 2000-12-19 2006-10-31 Bellsouth Intellectual Property Corporation Location query service for wireless networks
US7224978B2 (en) 2000-12-19 2007-05-29 Bellsouth Intellectual Property Corporation Location blocking service from a wireless service provider
US7085555B2 (en) 2000-12-19 2006-08-01 Bellsouth Intellectual Property Corporation Location blocking service from a web advertiser
US7428411B2 (en) 2000-12-19 2008-09-23 At&T Delaware Intellectual Property, Inc. Location-based security rules
US7181225B1 (en) 2000-12-19 2007-02-20 Bellsouth Intellectual Property Corporation System and method for surveying wireless device users by location
US7793326B2 (en) 2001-08-03 2010-09-07 Comcast Ip Holdings I, Llc Video and digital multimedia aggregator
US7908628B2 (en) 2001-08-03 2011-03-15 Comcast Ip Holdings I, Llc Video and digital multimedia aggregator content coding and formatting
US6658260B2 (en) 2001-09-05 2003-12-02 Telecommunication Systems, Inc. Inter-carrier short messaging service providing phone number only experience
US8477758B2 (en) 2001-12-21 2013-07-02 At&T Intellectual Property I, L.P. Voice over network (VoN)/voice over internet protocol (VoIP) architect having hotline and optional tie line
US7391761B1 (en) 2001-12-21 2008-06-24 At&T Delaware Intellectual Property, Inc. System and method for voice over internet protocol using a standard telephone system
US7801289B2 (en) * 2001-12-21 2010-09-21 At&T Intellectual Property I, L.P. Voice-over network (VoN)/voice-over internet protocol (VoIP) architect using advance intelligent network alternatives
US7321773B2 (en) * 2002-03-28 2008-01-22 Telecommunication Systems, Inc. Area watcher for wireless network
US8918073B2 (en) 2002-03-28 2014-12-23 Telecommunication Systems, Inc. Wireless telecommunications location based services scheme selection
US8027697B2 (en) 2007-09-28 2011-09-27 Telecommunication Systems, Inc. Public safety access point (PSAP) selection for E911 wireless callers in a GSM type system
US7426380B2 (en) * 2002-03-28 2008-09-16 Telecommunication Systems, Inc. Location derived presence information
US9154906B2 (en) 2002-03-28 2015-10-06 Telecommunication Systems, Inc. Area watcher for wireless network
US8290505B2 (en) 2006-08-29 2012-10-16 Telecommunications Systems, Inc. Consequential location derived information
US7526076B2 (en) * 2002-03-29 2009-04-28 At&T Intellectual Property I, L.P. Audio delivery of caller identification information
US7729687B2 (en) * 2002-04-01 2010-06-01 At&T Intellectual Property I, L.P. Audio delivery of callerid information to a wireless communications device
US20030191046A1 (en) * 2002-04-09 2003-10-09 Pawlak Krzysztof Cosmetic and perfume products with amber
US6931117B2 (en) * 2002-06-21 2005-08-16 Bellsouth Intellectual Property Corporation Caller control of internet call waiting
US7317714B2 (en) * 2002-06-21 2008-01-08 At&T Deleware Intellectual Property, Inc. Internet call waiting messaging
US7027842B2 (en) * 2002-09-24 2006-04-11 Bellsouth Intellectual Property Corporation Apparatus and method for providing hands-free operation of a device
US7899500B2 (en) * 2002-09-24 2011-03-01 At&T Intellectual Property I, L. P. Apparatus and method for providing hands-free operation of a device
US20070238455A1 (en) * 2006-04-07 2007-10-11 Yinjun Zhu Mobile based area event handling when currently visited network doe not cover area
US8666397B2 (en) 2002-12-13 2014-03-04 Telecommunication Systems, Inc. Area event handling when current network does not cover target area
US7715538B2 (en) * 2003-04-29 2010-05-11 At&T Intellectual Property I, L.P. Privacy screening services
US7899473B2 (en) * 2003-07-21 2011-03-01 Telecommunications Systems, Inc. Wireless network location-based reference information
US7027564B2 (en) * 2003-09-22 2006-04-11 Foundry Networks, Inc. System, method and apparatus for supporting E911 emergency services in a data communications network
US7424293B2 (en) 2003-12-02 2008-09-09 Telecommunication Systems, Inc. User plane location based service using message tunneling to support roaming
US7260186B2 (en) 2004-03-23 2007-08-21 Telecommunication Systems, Inc. Solutions for voice over internet protocol (VoIP) 911 location services
US20070298765A1 (en) * 2006-06-27 2007-12-27 Richard Dickinson Public services access point (PSAP) designation of preferred emergency call routing method via internet or public switched telephone network (PSTN)
US20080090546A1 (en) 2006-10-17 2008-04-17 Richard Dickinson Enhanced E911 network access for a call center using session initiation protocol (SIP) messaging
US20080126535A1 (en) 2006-11-28 2008-05-29 Yinjun Zhu User plane location services over session initiation protocol (SIP)
US7903791B2 (en) 2005-06-13 2011-03-08 Telecommunication Systems, Inc. Enhanced E911 location information using voice over internet protocol (VoIP)
US7483519B2 (en) 2003-12-23 2009-01-27 At&T Intellectual Property I, L.P. Caller controlled systems to suppress system to de-activate 911 indicator
US7068760B2 (en) * 2004-01-30 2006-06-27 Bellsouth Intellectual Property Corporation Systems and methods for providing location signals/indicators when 911 dialed
US7620156B2 (en) 2006-06-06 2009-11-17 At&T Intellectual Property I, L.P. Systems and methods for providing location signals/indicators when 911 dialed
US7177399B2 (en) * 2004-02-27 2007-02-13 Nortel Network Limited Determining the geographical location from which an emergency call originates in a packet-based communications network
US7783013B2 (en) * 2004-04-30 2010-08-24 At&T Intellectual Property I, L.P. Method and system for routing emergency communications
US20060115057A1 (en) * 2004-04-30 2006-06-01 Donald Laliberte Method and system for control of a voice/data communications device using a radio frequency component
US7586902B2 (en) 2004-05-10 2009-09-08 At&T Intellectual Property I, L.P. Methods, apparatus and computer program products for associating local telephone numbers with emergency phone calls in a packet switched telephone system
US7580405B2 (en) * 2004-05-27 2009-08-25 At&T Intellectual Property I, L. P. Method and system for routing emergency data communications
US7764944B2 (en) * 2004-06-24 2010-07-27 Alcatel-Lucent Usa Inc. Method of providing a unique call back number for wireless 9-1-1 calls
US7257387B2 (en) * 2004-06-30 2007-08-14 At&T Intellectual Property, Inc. Method and system for emergency control of a voice/data communications device
US7626950B2 (en) * 2004-08-18 2009-12-01 At&T Intellectual Property, I,L.P. SIP-based session control among a plurality of multimedia devices
US7630328B2 (en) * 2004-08-18 2009-12-08 At&T Intellectual Property, I,L.P. SIP-based session control
US20060029195A1 (en) * 2004-08-18 2006-02-09 Karen Mullis Methods, apparatus and computer program products for message notification in a voice over internet protocol communication system
US7940746B2 (en) 2004-08-24 2011-05-10 Comcast Cable Holdings, Llc Method and system for locating a voice over internet protocol (VoIP) device connected to a network
US7937485B2 (en) * 2004-08-31 2011-05-03 At&T Intellectual Property I, L.P. Streaming gateway
US7894406B2 (en) * 2004-09-30 2011-02-22 Alcatel-Lucent Usa Inc. System for routing remote VoIP emergency calls
US7079627B2 (en) * 2004-10-13 2006-07-18 Bce Inc. Emergency call handling in a voice-over-packet environment
US20070041513A1 (en) * 2005-02-08 2007-02-22 Gende Michael F Emergency call identification, location and routing method and system
US7917396B1 (en) * 2005-02-15 2011-03-29 Embarq Holdings Company, Llc Method and system for processing communications orders
US7756253B2 (en) * 2005-02-22 2010-07-13 At&T Intellectual Property Ii, Lp Methods and systems for providing foreign call back number compatibility for VoIP E9-1-1 calls
US7353034B2 (en) 2005-04-04 2008-04-01 X One, Inc. Location sharing and tracking using mobile phones or other wireless devices
US7961717B2 (en) * 2005-05-12 2011-06-14 Iposi, Inc. System and methods for IP and VoIP device location determination
US8103242B2 (en) * 2005-05-26 2012-01-24 Telecommunication Systems, Inc. E911 call blocking for non-initialized wireless telephones
US8116722B2 (en) * 2005-05-26 2012-02-14 Telecommunication Systems, Inc. E911 call blocking for non-initialized wireless telephones
US8175570B2 (en) * 2005-05-26 2012-05-08 Telecommunication Systems, Inc. E911 call blocking for non-initialized wireless telephones
US8660573B2 (en) 2005-07-19 2014-02-25 Telecommunications Systems, Inc. Location service requests throttling
US10178522B2 (en) * 2005-08-02 2019-01-08 Qualcomm Incorporated VoIP emergency call support
US8515386B2 (en) 2005-08-05 2013-08-20 Dennis J. Hasenfang Emergency services for voice over IP telephony (E-VoIP)
US7933580B2 (en) * 2005-08-05 2011-04-26 Hasenfang Dennis J Emergency services for voice over IP telephony (E-VoIP)
US7548158B2 (en) 2005-08-08 2009-06-16 Telecommunication Systems, Inc. First responder wireless emergency alerting with automatic callback and location triggering
US7933385B2 (en) * 2005-08-26 2011-04-26 Telecommunication Systems, Inc. Emergency alert for voice over internet protocol (VoIP)
US20070123271A1 (en) * 2005-08-26 2007-05-31 Richard Dickinson Cellular phone tracking scope
US9282451B2 (en) 2005-09-26 2016-03-08 Telecommunication Systems, Inc. Automatic location identification (ALI) service requests steering, connection sharing and protocol translation
DE102005045859A1 (en) * 2005-09-26 2007-04-05 Siemens Ag Establishing communications link via distributed network to reserved destination device involves checking if initiated link defined by reserved subscriber number should be carried out when link is initialized at network element
US8467320B2 (en) 2005-10-06 2013-06-18 Telecommunication Systems, Inc. Voice over internet protocol (VoIP) multi-user conferencing
US7907551B2 (en) * 2005-10-06 2011-03-15 Telecommunication Systems, Inc. Voice over internet protocol (VoIP) location based 911 conferencing
US7626951B2 (en) * 2005-10-06 2009-12-01 Telecommunication Systems, Inc. Voice Over Internet Protocol (VoIP) location based conferencing
US8600009B1 (en) * 2005-10-19 2013-12-03 At&T Intellectual Property Ii, L.P. Method and apparatus for mapping media access control addresses to service addresses
US8824454B2 (en) * 2005-10-24 2014-09-02 West Corporation Peering network for parameter-based routing of special number calls
US7843903B2 (en) * 2005-11-04 2010-11-30 Broadsoft M6, Llc Methods, systems, and computer program products for emergency 911 (E911) registration assistance for subscribers using portable internet protocol (IP) communications devices
WO2007061790A2 (en) 2005-11-18 2007-05-31 Telecommunication Systems, Inc. Voice over internet protocol (voip) mobility detection
US20070123208A1 (en) * 2005-11-28 2007-05-31 Puneet Batta System and method for prioritizing emergency communications in a wireless network
US8599879B1 (en) 2005-11-30 2013-12-03 At&T Intellectual Property Ii, L.P. External application gateway
US8280341B2 (en) * 2005-12-16 2012-10-02 Verizon Business Global Llc GPS-assisted architecture for VoIP 9-1-1
US9100237B2 (en) * 2005-12-22 2015-08-04 At&T Intellectual Property I, L.P. VoIP 911 address locator service
US20070153986A1 (en) * 2006-01-03 2007-07-05 Sony Ericsson Mobile Communications Ab Method and Apparatus for Routing Emergency Calls in a VoIP System
US20070153982A1 (en) * 2006-01-03 2007-07-05 Sony Ericsson Mobile Communications Ab Method and Apparatus for Routing Emergency Calls in a VoIP System
US20070153984A1 (en) * 2006-01-03 2007-07-05 Sony Ericsson Mobile Communications Ab Method and Apparatus for Routing Emergency Calls in a VoIP System
US8289958B1 (en) 2006-01-05 2012-10-16 Sprint Spectrum L.P. Using a clearinghouse to determine caller location for VoIP calls
US20070189492A1 (en) * 2006-01-20 2007-08-16 George Heinrichs Peering network for parameter-based routing of special number calls
US8150363B2 (en) 2006-02-16 2012-04-03 Telecommunication Systems, Inc. Enhanced E911 network access for call centers
US8059789B2 (en) * 2006-02-24 2011-11-15 Telecommunication Systems, Inc. Automatic location identification (ALI) emergency services pseudo key (ESPK)
US8532266B2 (en) 2006-05-04 2013-09-10 Telecommunication Systems, Inc. Efficient usage of emergency services keys
US8208605B2 (en) 2006-05-04 2012-06-26 Telecommunication Systems, Inc. Extended efficient usage of emergency services keys
US11089441B2 (en) 2006-05-16 2021-08-10 RedSky Technologies, Inc. Method and system for locating a network device in an emergency situation including public location information with device verification
US10856127B2 (en) 2006-05-16 2020-12-01 RedSky Technologies, Inc. Method and system for an emergency location information service (E-LIS) for water-based network devices
US10588004B2 (en) 2006-05-16 2020-03-10 RedSky Technologies, Inc. Method and system for locating a network device in an emergency situation
US8442482B2 (en) 2006-05-16 2013-05-14 RedSky Technologies, Inc. Method and system for an emergency location information service (E-LIS)
US7937067B2 (en) * 2006-05-16 2011-05-03 Red Sky Technologies, Inc. System and method for an emergency location information service (E-LIS)
US10511950B2 (en) 2006-05-16 2019-12-17 RedSky Technologies, Inc. Method and system for an emergency location information service (E-LIS) for Internet of Things (IoT) devices
US9094816B2 (en) 2006-05-16 2015-07-28 RedSky Technologies, Inc. Method and system for an emergency location information service (E-LIS) from unmanned aerial vehicles (UAV)
US8918075B2 (en) 2006-05-16 2014-12-23 RedSky Technologies, Inc. Method and system for an emergency location information service (E-LIS) from wearable devices
US8755767B2 (en) 2006-05-16 2014-06-17 RedSky Technologies, Inc. Method and system for an emergency location information service (E-LIS)
US10912056B2 (en) 2006-05-16 2021-02-02 RedSky Technologies, Inc. Method and system for locating a network device in an emergency situation including public location information
US11412364B2 (en) 2006-05-16 2022-08-09 Everbridge, Inc. Method and system for locating a network device connected to a proxy network device in an emergency situation
US9635534B2 (en) 2006-05-16 2017-04-25 RedSky Technologies, Inc. Method and system for an emergency location information service (E-LIS) from automated vehicles
US11463860B2 (en) 2006-05-16 2022-10-04 Everbridge, Inc. Method and system for an emergency location information service (E-LIS) for proxy network devices
US7773584B2 (en) * 2006-06-13 2010-08-10 At&T Intellectual Property I, L.P. Method and apparatus for processing session initiation protocol messages associated with a voice over IP terminal
US9252981B2 (en) * 2006-06-13 2016-02-02 At&T Intellectual Property I, L.P. Method and apparatus for processing a communication request from a roaming voice over IP terminal
US7391231B2 (en) * 2006-06-19 2008-06-24 International Business Machines Corporation Switch selectable terminator for differential and pseudo-differential signaling
US8077701B2 (en) * 2006-07-20 2011-12-13 At&T Intellectual Property I, Lp Systems, methods, and apparatus to prioritize communications in IP multimedia subsystem networks
US8064875B2 (en) * 2006-08-04 2011-11-22 At&T Intellectual Property I, L.P. Methods and apparatus to update geographic location information associated with internet protocol devices for E-911 emergency services
JP2008047219A (en) * 2006-08-16 2008-02-28 Toshiba Corp Nand-type flash memory
US20080267172A1 (en) * 2006-09-26 2008-10-30 Hines John G Location object proxy broker
US9408046B2 (en) 2006-10-03 2016-08-02 Telecommunication Systems, Inc. 911 data messaging
US9160572B2 (en) * 2006-10-17 2015-10-13 Telecommunication Systems, Inc. Automated location determination to support VoIP E911 using self-surveying techniques for ad hoc wireless network
US8531995B2 (en) 2006-11-01 2013-09-10 At&T Intellectual Property I, L.P. Systems and methods for location management and emergency support for a voice over internet protocol device
US7966013B2 (en) 2006-11-03 2011-06-21 Telecommunication Systems, Inc. Roaming gateway enabling location based services (LBS) roaming for user plane in CDMA networks without requiring use of a mobile positioning center (MPC)
US8818344B2 (en) 2006-11-14 2014-08-26 Microsoft Corporation Secured communication via location awareness
US8731146B2 (en) 2007-01-04 2014-05-20 At&T Intellectual Property I, L.P. Call re-directed based on voice command
US8363640B2 (en) * 2007-01-31 2013-01-29 At&T Intellectual Property I, L.P. Methods and apparatus for handling a communication session for an unregistered internet protocol multimedia subsystem (IMS) device
WO2008097500A1 (en) * 2007-02-06 2008-08-14 Telecommunication Systems, Inc. Voice over internet protocol (voip) location based commercial prospect conferencing
US8050386B2 (en) 2007-02-12 2011-11-01 Telecommunication Systems, Inc. Mobile automatic location identification (ALI) for first responders
US8620257B2 (en) * 2007-02-20 2013-12-31 At&T Intellectual Property I, L.P. Systems and methods for location management and emergency support for a voice over internet protocol device
US8520805B2 (en) * 2007-05-02 2013-08-27 Telecommunication Systems, Inc. Video E911
US20080307445A1 (en) * 2007-06-05 2008-12-11 Sukesh Garg Method and apparatus for providing a unified system for interaction with cellular and internet protocol devices
US8504614B2 (en) * 2007-06-28 2013-08-06 Verizon Patent And Licensing Inc. Systems and methods for verification of IP device location
US8149996B2 (en) * 2007-07-05 2012-04-03 West Corporation Providing routing information to an answering point of an emergency services network
WO2009038726A1 (en) 2007-09-17 2009-03-26 Telecommunication Systems, Inc. Emergency 911 data messaging
US20090077077A1 (en) * 2007-09-18 2009-03-19 Gerhard Geldenbott Optimal selection of MSAG address for valid civic/postal address
US9130963B2 (en) 2011-04-06 2015-09-08 Telecommunication Systems, Inc. Ancillary data support in session initiation protocol (SIP) messaging
US7929530B2 (en) 2007-11-30 2011-04-19 Telecommunication Systems, Inc. Ancillary data support in session initiation protocol (SIP) messaging
US8280342B1 (en) 2008-02-11 2012-10-02 Sprint Communications Company L.P. Emergency services using path optimization
US8254529B2 (en) * 2008-02-20 2012-08-28 Oldham Eamonn John Method and apparatus for emergency services number alerting in an internet protocol network
US8576991B2 (en) 2008-03-19 2013-11-05 Telecommunication Systems, Inc. End-to-end logic tracing of complex call flows in a distributed call system
US7903587B2 (en) 2008-05-30 2011-03-08 Telecommunication Systems, Inc. Wireless emergency services protocols translator between ansi-41 and VoIP emergency services protocols
US8068587B2 (en) * 2008-08-22 2011-11-29 Telecommunication Systems, Inc. Nationwide table routing of voice over internet protocol (VOIP) emergency calls
US8195121B2 (en) * 2008-09-15 2012-06-05 T-Mobile Usa, Inc. Method and system for establishing messaging communication with a service provider, such as a PSAP (public safety answering point)
US8954028B2 (en) 2008-09-25 2015-02-10 Telecommunication Systems, Inc. Geo-redundant and high reliability commercial mobile alert system (CMAS)
US8239483B2 (en) * 2009-03-16 2012-08-07 Andrew, Llc System and method for generic application of location determination for network attached devices
US9301191B2 (en) 2013-09-20 2016-03-29 Telecommunication Systems, Inc. Quality of service to over the top applications used with VPN
US8867485B2 (en) 2009-05-05 2014-10-21 Telecommunication Systems, Inc. Multiple location retrieval function (LRF) network having location continuity
US8406730B1 (en) 2010-06-10 2013-03-26 Sprint Communications Company L.P. Possession confidence metric for a wireless communication device
US8542611B1 (en) 2010-09-20 2013-09-24 Sprint Communications Company L.P. Wireless communication system for routing emergency calls from a VoIP network
CA2825289A1 (en) 2010-12-13 2012-06-21 Telecommunication Systems, Inc. Location services gateway server
US8942743B2 (en) 2010-12-17 2015-01-27 Telecommunication Systems, Inc. iALERT enhanced alert manager
US8688087B2 (en) 2010-12-17 2014-04-01 Telecommunication Systems, Inc. N-dimensional affinity confluencer
WO2012141762A1 (en) 2011-02-25 2012-10-18 Telecommunication Systems, Inc. Mobile internet protocol (ip) location
US9137383B2 (en) 2011-06-17 2015-09-15 Airbus Ds Communications, Inc. Systems, apparatus, and methods for collaborative and distributed emergency multimedia data management
US9479344B2 (en) 2011-09-16 2016-10-25 Telecommunication Systems, Inc. Anonymous voice conversation
US9544271B2 (en) 2011-09-16 2017-01-10 Telecommunication Systems, Inc. Anonymous messaging conversation
WO2013048551A1 (en) 2011-09-30 2013-04-04 Telecommunication Systems, Inc. Unique global identifier for minimizing prank 911 calls
US8929854B2 (en) 2011-10-27 2015-01-06 Telecommunication Systems, Inc. Emergency text messaging
US9313637B2 (en) 2011-12-05 2016-04-12 Telecommunication Systems, Inc. Wireless emergency caller profile data delivery over a legacy interface
US9264537B2 (en) 2011-12-05 2016-02-16 Telecommunication Systems, Inc. Special emergency call treatment based on the caller
US8984591B2 (en) 2011-12-16 2015-03-17 Telecommunications Systems, Inc. Authentication via motion of wireless device movement
US9384339B2 (en) 2012-01-13 2016-07-05 Telecommunication Systems, Inc. Authenticating cloud computing enabling secure services
US9544260B2 (en) 2012-03-26 2017-01-10 Telecommunication Systems, Inc. Rapid assignment dynamic ownership queue
US9307372B2 (en) 2012-03-26 2016-04-05 Telecommunication Systems, Inc. No responders online
US9338153B2 (en) 2012-04-11 2016-05-10 Telecommunication Systems, Inc. Secure distribution of non-privileged authentication credentials
US9313638B2 (en) 2012-08-15 2016-04-12 Telecommunication Systems, Inc. Device independent caller data access for emergency calls
US9208346B2 (en) 2012-09-05 2015-12-08 Telecommunication Systems, Inc. Persona-notitia intellection codifier
US9456301B2 (en) 2012-12-11 2016-09-27 Telecommunication Systems, Inc. Efficient prisoner tracking
US8983047B2 (en) 2013-03-20 2015-03-17 Telecommunication Systems, Inc. Index of suspicion determination for communications request
US9408034B2 (en) 2013-09-09 2016-08-02 Telecommunication Systems, Inc. Extended area event for network based proximity discovery
US9516104B2 (en) 2013-09-11 2016-12-06 Telecommunication Systems, Inc. Intelligent load balancer enhanced routing
US9479897B2 (en) 2013-10-03 2016-10-25 Telecommunication Systems, Inc. SUPL-WiFi access point controller location based services for WiFi enabled mobile devices
US9408047B2 (en) 2013-10-10 2016-08-02 Telecommunication Systems, Inc. Read acknowledgement interoperability for text messaging and IP messaging

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6650901B1 (en) * 2000-02-29 2003-11-18 3Com Corporation System and method for providing user-configured telephone service in a data network telephony system
US6678357B2 (en) * 2001-09-26 2004-01-13 Siemens Information And Communication Networks, Inc. Internet protocol (IP) emergency connections (ITEC) telephony
US6771742B2 (en) * 2001-11-05 2004-08-03 Intrado Inc. Geographic routing of emergency service call center emergency calls

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
None

Also Published As

Publication number Publication date
EP1709789A2 (en) 2006-10-11
US6940950B2 (en) 2005-09-06
US20050135569A1 (en) 2005-06-23
EP1709789A4 (en) 2010-04-28
WO2005062778A3 (en) 2005-09-15

Similar Documents

Publication Publication Date Title
US6940950B2 (en) Enhanced E911 location information using voice over internet protocol (VoIP)
US9467836B2 (en) Enhanced E911 location information using voice over internet protocol (VoIP)
US9544429B2 (en) Solutions for voice over internet protocol (VoIP) 911 location services
US8369825B2 (en) Enhanced E911 network access for a call center using session initiation protocol (SIP) messaging
US9420444B2 (en) Enhanced E911 network access for call centers
US20150029941A1 (en) Public Services Access Point (PSAP) Designation of Preferred Emergency Call Routing Method Via Internet or Public Switched Telephone Network (PSTN)
US20070041513A1 (en) Emergency call identification, location and routing method and system
US20070003024A1 (en) Network emergency call taking system and method
US20050123102A1 (en) Telephone emergency response system and method
US8149997B2 (en) Protocol converting 9-1-1 emergency messaging center
US8160539B1 (en) Location provisioning for 911 calls received at a telecommunications relay service

Legal Events

Date Code Title Description
AK Designated states

Kind code of ref document: A2

Designated state(s): AE AG AL AM AT AU AZ BA BB BG BR BW BY BZ CA CH CN CO CR CU CZ DE DK DM DZ EC EE EG ES FI GB GD GE GH GM HR HU ID IL IN IS JP KE KG KP KR KZ LC LK LR LS LT LU LV MA MD MG MK MN MW MX MZ NA NI NO NZ OM PG PH PL PT RO RU SC SD SE SG SK SL SY TJ TM TN TR TT TZ UA UG US UZ VC VN YU ZA ZM ZW

AL Designated countries for regional patents

Kind code of ref document: A2

Designated state(s): BW GH GM KE LS MW MZ NA SD SL SZ TZ UG ZM ZW AM AZ BY KG KZ MD RU TJ TM AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HU IE IS IT LT LU MC NL PL PT RO SE SI SK TR BF BJ CF CG CI CM GA GN GQ GW ML MR NE SN TD TG

121 Ep: the epo has been informed by wipo that ep was designated in this application
DPEN Request for preliminary examination filed prior to expiration of 19th month from priority date (pct application filed from 20040101)
NENP Non-entry into the national phase

Ref country code: DE

WWW Wipo information: withdrawn in national office

Ref document number: DE

REEP Request for entry into the european phase

Ref document number: 2004814540

Country of ref document: EP

WWE Wipo information: entry into national phase

Ref document number: 2004814540

Country of ref document: EP

WWP Wipo information: published in national office

Ref document number: 2004814540

Country of ref document: EP