US20130315384A1 - Handling emergency service calls originating from internet telephony - Google Patents

Handling emergency service calls originating from internet telephony Download PDF

Info

Publication number
US20130315384A1
US20130315384A1 US13/955,136 US201313955136A US2013315384A1 US 20130315384 A1 US20130315384 A1 US 20130315384A1 US 201313955136 A US201313955136 A US 201313955136A US 2013315384 A1 US2013315384 A1 US 2013315384A1
Authority
US
United States
Prior art keywords
routing device
psap
call
server
location
Prior art date
Legal status (The legal status 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 status listed.)
Abandoned
Application number
US13/955,136
Inventor
Mark W. Coster
John R. Anderson
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Verizon Business Global LLC
Original Assignee
Verizon Business Global LLC
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
Priority to US11/106,603 priority Critical patent/US7496182B2/en
Priority to US12/344,819 priority patent/US8559601B2/en
Application filed by Verizon Business Global LLC filed Critical Verizon Business Global LLC
Priority to US13/955,136 priority patent/US20130315384A1/en
Publication of US20130315384A1 publication Critical patent/US20130315384A1/en
Application status is Abandoned legal-status Critical

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L29/00Arrangements, apparatus, circuits or systems, not covered by a single one of groups H04L1/00 - H04L27/00
    • H04L29/02Communication control; Communication processing
    • H04L29/06Communication control; Communication processing characterised by a protocol
    • H04L29/06176Arrangements for real-time multimedia communications
    • H04L29/06387Services or applications
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04MTELEPHONIC COMMUNICATION
    • H04M3/00Automatic or semi-automatic exchanges
    • H04M3/42Systems providing special services or facilities to subscribers
    • H04M3/50Centralised arrangements for answering calls; Centralised arrangements for recording messages for absent or busy subscribers ; Centralised arrangements for recording messages
    • H04M3/51Centralised call answering arrangements requiring operator intervention, e.g. call or contact centers for telemarketing
    • H04M3/5116Centralised call answering arrangements requiring operator intervention, e.g. call or contact centers for telemarketing for emergency applications
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04MTELEPHONIC COMMUNICATION
    • H04M7/00Interconnection arrangements between switching centres
    • H04M7/006Networks other than PSTN/ISDN providing telephone service, e.g. Voice over Internet Protocol (VoIP), including next generation networks with a packet-switched transport layer
    • H04M7/0075Details of addressing, directories or routing tables
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04MTELEPHONIC COMMUNICATION
    • H04M2242/00Special services or facilities
    • H04M2242/04Special services or facilities for emergency applications
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04MTELEPHONIC COMMUNICATION
    • H04M2242/00Special services or facilities
    • H04M2242/30Determination of the location of a subscriber

Abstract

A method and system for interfacing internet protocol-enabled emergency calls to a public 9-1-1 system are described. The method can include routing an emergency call originating from internet protocol telephony to a data network via a routing device which may include an identifier. The method can include transferring the routed emergency call to a predetermined public service answering point based on the identifier.

Description

    CROSS-REFERENCE TO RELATED APPLICATION
  • This application is a continuation of prior co-pending U.S. patent application Ser. No. 11/106,603, filed Apr. 15, 2005, entitled “Handling Emergency Service Calls Originating From Internet Telephony”, the entire disclosure of which is hereby incorporated by reference herein.
  • FIELD OF THE INVENTION
  • Implementations relate generally to data based forms of telecommunications technology and, more particularly, to interfacing Internet protocol (IP)-enabled telephony emergency service calls to 9-1-1 emergency communications systems.
  • BACKGROUND OF THE INVENTION
  • Emergency 9-1-1 service has been designated in the U.S. as the emergency system for public use for emergency reporting to and/or requesting emergency assistance from public safety entities, typically for dispatch of emergency service providers (ESPs) (e.g., law enforcement, firefighters, emergency medical service (EMS)) to the scene of the emergency. An integral functional feature of existing 9-1-1 networks is that a call placed to 9-1-1 from anywhere within a calling region can be quickly directed to the appropriate ESP that can get to the site of the emergency the quickest, if necessary, in lieu of the need to directly dial the ten digit telephone number of the ESP. Current 9-1-1 emergency service capabilities range from traditional or basic 9-1-1 emergency service to enhanced or E911 emergency service.
  • Current 9-1-1 service has specific processing features that are designed to improve its functionality (e.g., ease of use, uniformity, etc.), and to reflect that time is of the essence in handling an emergency call. An enabling process for such features is the capability to determine, from call signal information (i.e., automatically), the geographic location of the calling party. The geographic source of the call has to be sufficiently precise so that the call can be immediately routed from anywhere within the calling region in which it is placed, to a predetermined public safety answering point (PSAP) in a given jurisdiction (e.g., municipality, county, etc.), where it is first “answered” by an operator or “call taker.” The call is then transferred or communicated from the PSAP to a predetermined ESP(s) for disposition based upon, for example, proximity to the site of the emergency.
  • Current processing features of the 9-1-1 infrastructure have developed around the use of traditional wireline technology that uses circuit-switched telephony (e.g., public switched telephone networks (PSTNs)), which is characterized by nominal subscribers using landlines at fixed geographic locations. Such features have evolved to provide access to the existing 9-1-1 networks for 9-1-1 calls originating from wireless telecommunications technology. For wireline placed 9-1-1 calls, the geographic location of the caller for purposes of PSAP routing can be determined automatically from the exchange portion of the calling party's telephone number (i.e., the first three digits), or from the calling party's entire telephone number (i.e., from caller identification (“ID”)). For cellular placed 9-1-1 calls, the geographic location of the caller for purposes of PSAP routing can be determined automatically from location information regarding the operative cell tower, or from global positioning system (GPS) data.
  • Internet telephony, such as voice over IP (VoIP) phone service, is reportedly poised to become the predominant technology used in the telecommunications industry. Thus, emergency calls will increasingly be placed from VoIP devices. Current VoIP offerings, however, fail to adequately provide suitable 9-1-1 network service, in part, due to the technological challenges in automatically determining the source of the 9-1-1 call, i.e., the specific geographical location of the VoIP device.
  • A VoIP placed call can originate from a VoIP user device and enter the Internet as a signal that is geographically nondescriptive. The call can be routed through the Internet to a PSTN that is geographically remote from the VoIP user device. Additionally, because VoIP user devices can be readily relocated and used at any available suitable network connection, the VoIP subscriber's fixed physical address that can be associated with the subscriber's phone number is not always going to be the originating location of the call. Thus, the “nomadic” use of VoIP telephony can operate to obscure the source of the VoIP placed call.
  • Proposed methods to provide 9-1-1 network access to VoIP users include diverting the VoIP-placed 9-1-1 call to the PSTN based on the VoIP subscriber's fixed address location. However, such processing can only be accomplished when the VoIP device is used at the subscriber's address location, and the VoIP subscriber has successfully registered the correct address information with the VoIP service provider, etc. Otherwise, the 9-1-1 call is simply dropped, or the 9-1-1 service disabled when used at an alternative or remote location. Thus, proposed methods to interface IP-enabled telecommunications to conventional 9-1-1 service are largely unavailable to VoIP device users. Accordingly, local service access VoIP systems do not process 9-1-1 calls in the manner that landline and cellular phones do, and thus such calls are not handled with the exceptional level of care and priority afforded to wired and cellular telephone calls to 9-1-1.
  • The effectiveness of the 9-1-1 emergency reporting system relates to public expectations regarding its convenience and uniformity. Thus, it is desirable to standardize 9-1-1 call processing, from the perspective of the caller, regardless of the telecommunications technology used to place the call to 9-1-1. Moreover, it is likely that government regulations and/or industry-adopted standards will soon require VoIP-enabled calls to 9-1-1 to have the “look and feel” of conventional 9-1-1 calls.
  • SUMMARY OF THE INVENTION
  • According to one aspect, a method for interfacing internet protocol-enabled emergency calls to a public 9-1-1 system includes routing an emergency call originating from internet protocol telephony to a data network via a routing device having a routing device identifier; and transmitting the routed emergency call to a public service answering point (PSAP), based on the routing device identifier.
  • According to another aspect, a network device includes a routing device to receive incoming data including an emergency call from an IP telephony user device via a first data network; and route the received data including the emergency call along with routing device location information to a second data network.
  • According to a further aspect, a method for providing 9-1-1 services to an internet telephony user includes: receiving a dialed 9-1-1 call on a data network from an IP user device configured to be selectively used from a fixed location connection and from a plurality of remote connections, wherein the 9-1-1 call includes profile information; determining from the profile information that the dialed 9-1-1 call originated from one of the remote connections; identifying an end-user routing device used to route the dialed 9-1-1 call; designating an assigned PSAP based on the identified end-user routing device; redirecting the routed 9-1-1 call to a public switched telephone network (PSTN); and forwarding the redirected 9-1-1 call to the assigned PSAP.
  • BRIEF DESCRIPTION OF THE DRAWINGS
  • The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate an implementation of the invention and, together with the description, explain the invention. In the drawings,
  • FIG. 1 is an exemplary schematic diagram illustrating an exemplary system in which methods and systems consistent with the principles of the invention can be implemented;
  • FIG. 2 is an exemplary schematic diagram illustrating an exemplary system in which methods and systems consistent with the principles of the invention can be implemented; and
  • FIG. 3 is an exemplary flow diagram illustrating a method for connecting internet telephony user devices to 9-1-1 services consistent with the principles of the invention.
  • DETAILED DESCRIPTION
  • The following detailed description of implementations consistent with the present invention refers to the accompanying drawings. The same reference numbers in different drawings may identify the same or similar elements. Also, the following detailed description does not limit the invention. Instead, the scope of the invention is defined by the appended claims and equivalents.
  • Overview
  • Systems and methods consistent with the principles of the invention can facilitate 9-1-1 services adoption and implementation for emergency calls from users of internet protocol (IP) telephony. According to one implementation, location information regarding a routing device through which an IP-enabled emergency call is routed can be used to identify the appropriate public service answering point (PSAP) for receiving the emergency call, which can then be forwarded to an emergency service provider (ESP) in the vicinity of the caller.
  • “Emergency call,” as the term is used herein, is to be broadly interpreted to include any suitable transmission of a signal message to an emergency number. Emergency calls can include, for example, analog, digital, and wireless transmissions that are subject to any known signal processing. An emergency call can include voice, text, image, video, page signaling, etc., in any format. An emergency call can originate from any known method for initiating a call such as manual dialing, voice command, activating a dedicated switch, etc. “Emergency number,” as the term is used herein, is to be broadly interpreted to include, for example, the numeric string, 9-1-1. However, systems consistent with principles of the invention can operate to any suitable universalized dialing sequence or code associated with any known or existing “9-1-1 service,” as well as any contemplated IP based “9-1-1 network,” which terms are to be broadly interpreted to include any location-sensitive emergency response service.
  • Exemplary System
  • FIG. 1 is an exemplary illustration of a system 100 in which methods and systems consistent with the principles of the invention can be implemented. As shown, system 100 may include a phone device 102 that operatively connects to a data network 106 through an analog telephone adapter (ATA) 104, and a routing device 108 that may be associated with data network 106. System 100 may also include a data network 110 that operatively connects to data network 106, a server 112 that may be associated with data network 110, and a database 114 that may be accessible to the server 112. System 100 may include a public service answering point (PSAP) 116 that operatively connects to data network 110 and multiple emergency service providers (ESPs) 118.
  • Phone device 102 can be any suitable user device for enabling voice communication via a data network, e.g., a voice over IP (VoIP) device, voice over Internet (VOI) phone, etc. In one implementation consistent with principles of the invention, phone device 102 can include a conventional analog telephone connected to data network 106 via a digital gateway, for example, ATA 104, or any device capable of initiating, transmitting, and receiving voice and data communications to a data network, such as VoIP gateways. It should be understood that the single instance of phone device 102 shown in FIG. 1, is provided for simplicity. In practice, methods and systems consistent with the principles of the invention can include any number and type of phone devices.
  • In one implementation consistent with principles of the invention, phone device 102 can include self-contained or stand alone broadband phones or software-based VoIP telephony interfaces (e.g., for running on laptops, personal digital assistants (PDAs), or personal computers) for which ATA 104 need not be used. For example, phone device 102 can include a hardwired VoIP telephone having an Ethernet port or a built-in modem, a session initiated protocol (SIP) telephone device, an H.323 telephone device, and a wireless VoIP phone having a built-in wireless fidelity (WiFi) transceiver or a built-in WiFi and global system for mobile communications (GSM) transceiver (e.g., 802.11(x)-based).
  • Data networks 106 and 110 can include a computer network of any type suitable for receiving, storing, processing, and/or transmitting data (e.g., discrete packets or units) among nodes or network elements in communication, having any suitable topology (e.g., bus, star, ring, etc.), protocol (e.g., IP, Ethernet, token-ring network, etc.), and architecture (e.g., peer-to-peer, client/server, etc.). For example, data networks 106 and 110 can include a local area network (LAN), a wide area network (WAN), a metropolitan area network (MAN), a campus-area network (CAN), a government area network (GAN), a home-area network (HAN), an intranet, the Internet, an Internet service provider's network, a VoIP service provider's network, and/or a combination of networks.
  • Routing device 108 associated with data network 106 can include any network element or device suitable for routing or forwarding data packets along. For example, routing device 108 can include a router, a modem of any type, a switching device, an interface device, a gateway, customer premises equipment (CPE) network devices, VoIP service provider devices, and/or incumbent local exchange carrier (ILEC) devices (e.g., network routers located at a central office). Consistent with principles of the invention, routing device 108 can include, for example, an edge router, a first hop router, a broadband interface, a VoIP gateway, a CPE routing device, and/or an end-user routing device. In one implementation consistent with the principles of the invention, routing device 108 can include a memory or a storage medium of any type, for example, flash random access memory (RAM). In another implementation consistent with the principles of the invention, routing device 108 can include a processing unit or processor of any type, for example, for receiving and responding to queries from server 112.
  • Server 112 associated with data network 110 can include any suitable network device for managing resources on data network 110. For example, server 112 can include a network server having any combination of hardware and software (e.g., a SIP proxy server and/or SIP redirect server) suitable for receiving a VoIP call from phone device 102, examining the call request, and routing the call to an appropriate destination. Details regarding the specific functionality of server 112 are set forth in additional detail below.
  • Database 114 associated with server 112 can include a suitable network element for maintaining information organized, for example, in fields, records, and/or files. Database 114 can include maintained profile information for each routing device 108 associated with server 112. Consistent with principles of the invention, the profile information can include a routing device identifier, routing device identification information, address location information, routing device location information, an IP address, a media access control (MAC) address, and/or corresponding PSAP information associated with the routing device 108. The routing device identifier and routing device identification information can include any unique designation assigned to routing device 108 under any suitable identification scheme. Address and routing device location information can include specific physical location information for routing device 108, including geographic location or position information in any suitable format for routing device 108. PSAP information can include contact or routing information for designated or assigned primary, secondary, or alternative PSAP corresponding to routing device 108.
  • Consistent with principles of the invention, PSAP 116 can include any suitable system or process for receiving emergency calls, e.g., 9-1-1 calls, for handling or dispositioning. For example, PSAP 116 can be a public entity having personnel (e.g., operators or call takers) and/or equipment for initially answering or fielding incoming 9-1-1 calls. For example, PSAP 116 can include conventional facilities capable of receiving conventional 9-1-1 calls from circuit-switched telephony, as well as IP based or systems capable of supporting emergency voice, text, and/or image messaging from the Internet. PSAP 116 can be located in the vicinity of the source of the emergency call, and in the vicinity of ESPs 118, to which the call can be forwarded. Although only one PSAP 116 is shown, depending on the area of service or jurisdiction (typically a municipality or county), system 100 can include additional PSAPs.
  • Consistent with principles of the invention, ESPs 118 can include any suitable emergency response entity or agency, which can be dispatched in the vicinity of the 9-1-1 caller, i.e., the emergency scene or the site of the emergency. For example, ESPs 118 can include authorities such as law enforcement, firefighting, and/or EMS personnel in the locale, who can be dispatched to the emergency scene, if necessary.
  • FIG. 2 illustrates another exemplary system 200 in which methods and systems consistent with the principles of the invention can be implemented. As shown, system 200 can include user phone device 102; data network 106; ATA 104; routing device 108; data network 110; server 112; database 114; PSAP 116; and ESPs 118, substantially as described above. Additionally, system 200 can include a gateway 202 operatively connected to data network 110 and a public switched telephone network (PSTN) 204 to which PSAP 116 connects.
  • Consistent with principles of the invention, gateway 202 can include any suitable node or network device for transmitting data from network to network. For example, gateway 202 can include any interface and combination of hardware and/or software capable of translating IP-based call information onto a public circuit-switched network, e.g., PSTN 204.
  • Consistent with principles of the invention, PSTN 204 can include any suitable telephone system, for example, using traditional telecommunications technology. For example, PSTN 204 can be any circuit-switched telephony network, such as a public-circuit-switched network.
  • Exemplary Processing
  • FIG. 3 is a flowchart of exemplary processing for supporting IP-enabled telephony emergency service calls to 9-1-1 emergency communications systems according to an implementation consistent with principles of the invention. Initially, a routing device 108 may be provided with routing device profile information (operation 302) that may be specific to routing device 108. The profile information may include an identifier, geographic location information that identifies the physical location of routing device 108, and the like. For example, a user of routing device 108 (e.g., a modem, other CPE, ILEC equipment, an edge router, a first hop router, etc.) and/or a network administrator may provide a profile information upon installation or performing other configuring operations. In one exemplary implementation, profile information can be stored in routing device 108. A storage medium in routing device 108 can register profile information for routing device 108 as entered, for example, in response to a prompt as part of setup or arranging of routing device 108. The profile information can be provided to server 112, for example, and stored in database 114, when entered in routing device 108 and/or when an emergency call is routed through routing device 108.
  • According to another exemplary implementation, providing routing device 108 with a routing device identifier may include collecting and storing (e.g., in database 114) at least a specific physical address associated with the routing device identifier. The database can include PSAP information corresponding to a particular routing device identifier, for example, that designates specific primary, secondary, and/or alternative PSAPs to the routing device identifier.
  • Following profile establishment, a 9-1-1 call dialed or originating from phone device 102 (and transmitted through ATA 104, if necessary) is received as a signal transmission or packet data on data network 106. The call signal can be transmitted to and routed through routing device 108 associated with data network 106 to data network 110. The stored profile information can be attached to or provided in an appropriate field or header of the call signal, thereby associating routing device 108 with the emergency call.
  • The call signal received via data network 110 can be transmitted to and processed by server 112 associated with data network 110, and identified as a 9-1-1 call (operation 304). As described above, server 112 can include VoIP proxy and redirect servers suitable for processing and routing received calls over the Internet. In one implementation, server 112 can include both a SIP proxy server and a SIP redirect server capable of receiving an IP call from phone device 102, managing the setup, processing, and tear down of the call, examining call data, determining appropriate treatment for the call, and routing the call to an appropriate destination.
  • Consistent with principles of the invention, one or more routing devices (not shown) may be in the transmission path in systems 100 and 200, on either or both sides of routing device 108. Such additional routing device(s) may or may not have an associated routing identifier or profile information. Server 112 can discriminately determine which of such routing devices to use in identifying the appropriate PSAP 116, for example, from information in the header of the call transmission. Under a hierarchal identification scheme, for example, a routing identifier associated with routing device 108 at a nearest point of call origination can be determined from header information in a designated field(s) (e.g., remark or text identifier) that is propagated or retained in the call transmission along the transmission path to server 112. The hierarchal identification scheme can be implemented, for example, by server 112 and/or a network administrator (not shown).
  • According to one exemplary implementation, server 112 can determine whether the 9-1-1 call originated from a fixed location associated with phone device 102 (e.g., the subscriber's home address), or from a location other than the fixed location (i.e., a remote location) based on the profile information (operation 306). If it is determined that phone device 102 is a nomadic device, the method can proceed to operation 310 set forth in detail below. However, if it is determined that phone device 102 is a fixed location device, it can be determined whether automatic number identification (ANI) and/or automatic location information (ALI) can be resolved from the subscriber's telephone number associated with phone device 102 (operation 308).
  • If phone device 102 is a nomadic device, and if ANI and/or ALI for phone device 102 are otherwise not resolvable, server 112 can determine or acquire an identity of routing device 108, such as a customer premise routing device, through which the 9-1-1 call was routed (operation 310). The profile information can be identified by server 112 and matched to or cross referenced against profile information maintained in database 114. According to one exemplary implementation, if server 112 cannot identify or retrieve profile information associated with the received call signal and/or stored in database 114, server 112 can transmit a query to routing device 108. Routing device 108 can provide profile information in response to the query from server 112. Server 112 can then use the received profile information to identify routing device 108.
  • Based on the identification of routing device 108, server 112 can access associated database 114 for PSAP 116 information (e.g., routing, contact information, and the like) for the identified routing device 108 (operation 312). The PSAP information including the appropriate PSAP 116 can be predetermined based on the geographic location of the identified routing device 108 as compared or pre-validated against, for example, a master street address guide (MSAG). The MSAG can include a listing of all streets and house number ranges within a specific 9-1-1 service area. The streets and address ranges are assigned selective routing codes, or emergency service numbers (ESNs), to enable proper routing of 9-1-1 calls. Accordingly, the MSAG is a summary database of valid address ranges, with the corresponding ESN for each range. Each assigned ESN is a unique number assigned to combinations of PSAP and ESPs.
  • Database 114 can include emergency service numbers ESNs for ESPs 118 associated with the designated PSAP 116, which can then be provided together with the emergency call upon selective forwarding of the IP-enabled 9-1-1 call to PSAP 116 (operation 314). The geographic location information for routing device 108 and/or ESN information can be provided to and/or displayed for a 9-1-1 PSAP 116 calltaker. Once terminated at PSAP 116, interactive querying of the caller by the calltaker can be performed to identify a specific geographic location of the emergency scene and a type of emergency. Concurrently, an appropriate ESP(s) 118 associated with the location of the identified routing device 108 in a vicinity of the emergency scene can be identified and contacted for dispatch, if necessary.
  • In one implementation consistent with principles of the invention, as shown in FIG. 2, following geographic location and corresponding PSAP/ESP identification, a call to the identified PSAP 116 can first be redirected to PSTN 204 through existing 9-1-1 call flow methods and procedures, for example, using an IP/PSTN gateway (e.g., gateway 202). In one implementation, the call can be initiated via a dedicated 9-1-1 trunk line associated with PSAP 116 by dialing a discrete ten digit number associated with PSAP 116. Upon receipt of such a call, the call can be selectively routed on the appropriate trunk line to PSAP 116.
  • In yet another implementation consistent with principles of the invention, systems 100 and 200 can detect or recognize a newly installed network device (e.g., a broadband interface (not shown)) along the transmission path, for example, using a suitable algorithm. Upon detecting the network device, server 112 may generate and transmit a query to phone device 102 (e.g., using a voice response unit (VRU), interactive voice response (IVR) system, etc.) regarding the physical location of the network device. The query may provide the location of routing device 108, and request or prompt a response from the installer of the network device and/or a user of phone device 102 concerning the location of the network device relative to routing device 108, whether the location will be fixed, etc. As a synchronization or updating process or “handshake” function, a routing device identifier or profile information may be established for the network device, and stored in database 114, based on the response received by server 112. The handshake or validation function or operation may be implemented, for example, by server 112 and/or a network administrator.
  • CONCLUSION
  • Implementations consistent with the principles of the invention enable provision of 9-1-1 service functionality to all manner of Internet telephony users.
  • The foregoing description of exemplary embodiments of the present invention provides illustration and description, but is not intended to be exhaustive or to limit the invention to the precise form disclosed. Modifications and variations are possible in light of the above teachings or may be acquired from practice of the invention.
  • Moreover, while series of operations have been described with regard to FIG. 3, the order of the operations can be varied in other implementations consistent with the principles of the invention. Moreover, non-dependent operations can be implemented in parallel.
  • It will also be apparent to one of ordinary skill in the art that aspects of the invention, as described above, can be implemented in many different forms of software, firmware, and hardware. The actual software code or specialized control hardware used to implement aspects consistent with the principles of the invention is not limiting of the present invention. Thus, the operation and behavior of the aspects of the invention were described without reference to the specific software code—it being understood that one of ordinary skill in the art would be able to design software and control hardware to implement the aspects based on the description herein.
  • No element, act, or instruction used in the description of the present application should be construed as critical or essential to the invention unless explicitly described as such. Also, as used herein, the article “a” is intended to include one or more items. Where only one item is intended, the term “one” or similar language is used. Further, the phrase “based on” is intended to mean “based, at least in part, on” unless explicitly stated otherwise.

Claims (21)

1-21. (canceled)
22. A method comprising:
identifying, by a server, a call signal received via a routing device as an emergency call;
determining, by the server and based on information included in the call signal, whether the emergency call originated from a registered location;
determining, by the server, when the emergency call originated from the registered location, whether at least one of an automatic number identification (ANI) or automatic location information (ALI) is identifiable from the call signal;
when the emergency call did not originate from the registered location or neither the at least one of the ANI or the ALI is identifiable, retrieving, from a database associated with the server, location information associated with the routing device;
identifying, by the server, a public service answering point (PSAP) based on the retrieved location information or the at least one of the ANI or the ALI; and
transmitting, by the server, the call signal to the PSAP.
23. The method of claim 22, further comprising:
attaching information identifying the PSAP to the call signal.
24. The method of claim 22, further comprising:
selecting a public switched telephone network (PSTN) from a plurality of PSTNs based on the identified PSAP.
25. The method of claim 24, where transmitting the call includes:
transferring the call signal to the selected PSTN.
26. The method of claim 22, further comprising:
querying the routing device for an identity of the routing device.
27. The method of claim 26, further comprising:
determining, based on a response to the querying, a physical location of the routing device identified in the location information; and
where identifying the PSAP includes:
identifying the PSAP based on the physical location of the routing device.
28. The method of claim 27, where the identifying the PSAP further includes:
correlating the physical location of the routing device to stored PSAP information for a plurality of PSAPs, and
identifying the PSAP based on correlating the physical location of the routing device to the stored PSAP information.
29. The method of claim 27, where the identifying the PSAP further includes:
selecting the PSAP from a plurality of PSAPs based on the physical location of the routing device.
30. The method of claim 22, further comprising:
determining, from a plurality of routing devices routing the call signal to the server, that the routing device is a nearest one of the plurality of routing devices to a point of origination for the call signal.
31. The method of claim 27, further comprising:
determining, based on the physical location of the routing device, an emergency service number of emergency service personnel associated with the physical location of the routing device; and
where transmitting the call signal includes:
providing information identifying the emergency service number to the PSAP.
32. A method comprising:
receiving, by a server via a routing device, an emergency call from Internet protocol (IP) telephony selectively used at a registered location and locations other than the registered location;
determining, by the server and from profile information associated with the routing device, whether the emergency call originated from the registered location or at one of the locations other than the registered location;
determining, by the server and when the emergency call originated from the registered location, whether at least one of an automatic number identification (ANI) or automatic location information (ALI) is identifiable from information in the emergency call;
identifying, by the server and when the emergency call originated from the one of the locations other than the registered location or when neither the at least one of the ANI or the ALI is identifiable, a physical location for the routing device;
designating, by the server, an assigned public safety answering point (PSAP) based on the identified physical location of the routing device or the at least one of the ANI or the ALI; and
forwarding, by the server, the emergency call to a public switched telephone network (PSTN) based on the assigned PSAP.
33. The method of claim 32, further comprising:
retrieving the physical location of the routing device from a database associated with the server.
34. The method of claim 33, further comprising:
storing information for the assigned PSAP in the database; and
correlating the assigned PSAP to a geographic location that includes the physical location of the routing device.
35. The method of claim 32, further comprising:
modifying the emergency call to include information identifying the assigned PSAP.
36. The method of claim 32, further comprising:
modifying the emergency call to include information identifying the physical location of the routing device.
37. The method of claim 32, where identifying the physical location of the routing device comprises:
transmitting a query from the server to the routing device;
receiving, based on transmitting the query, information identifying the routing device; and
using the information identifying the routing device to identify the physical location of the routing device.
38. The method of claim 32, further comprising:
determining, based on the physical location of the routing device, an emergency service number of emergency service personnel associated with the physical location of the routing device; and
providing information identifying the emergency service number to the PSAP.
39. A system comprising:
a server to:
store, in a memory, information identifying a physical location of a routing device via which an Internet protocol (IP)-enabled call is received;
correlate, based on the physical location of the routing device, a public safety answering point (PSAP), associated with an emergency communication system, to the routing device;
determine whether the IP-enabled call originated from a fixed location;
determine, when the emergency call originated from the fixed location, whether the IP-enabled call includes at least one of an automatic number identification (ANI) or automatic location information (ALI);
attach, when the emergency call did not originate from the fixed location or the IP-enabled call does not include the at least one of the ANI or the ALI, information identifying the PSAP to the IP-enabled call; and
forward the IP-enabled call based on the information identifying the PSAP.
40. The system of claim 39, where, when forwarding the IP-enabled call, the server is to:
re-direct the IP-enabled call to a public switched telephone network (PSTN).
41. The system of claim 39, where the server is further to:
determine, based on the physical location of the routing device, an emergency service number of emergency service personnel associated with the physical location of the routing device; and
where, when forwarding the IP-enabled call, the server is to:
provide information identifying the emergency service number to the PSAP.
US13/955,136 2005-04-15 2013-07-31 Handling emergency service calls originating from internet telephony Abandoned US20130315384A1 (en)

Priority Applications (3)

Application Number Priority Date Filing Date Title
US11/106,603 US7496182B2 (en) 2005-04-15 2005-04-15 Handling emergency service calls originating from internet telephony
US12/344,819 US8559601B2 (en) 2005-04-15 2008-12-29 Handling emergency service calls originating from internet telephony
US13/955,136 US20130315384A1 (en) 2005-04-15 2013-07-31 Handling emergency service calls originating from internet telephony

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
US13/955,136 US20130315384A1 (en) 2005-04-15 2013-07-31 Handling emergency service calls originating from internet telephony

Related Parent Applications (1)

Application Number Title Priority Date Filing Date
US12/344,819 Division US8559601B2 (en) 2005-04-15 2008-12-29 Handling emergency service calls originating from internet telephony

Publications (1)

Publication Number Publication Date
US20130315384A1 true US20130315384A1 (en) 2013-11-28

Family

ID=37108461

Family Applications (3)

Application Number Title Priority Date Filing Date
US11/106,603 Active 2027-03-02 US7496182B2 (en) 2005-04-15 2005-04-15 Handling emergency service calls originating from internet telephony
US12/344,819 Active 2027-07-16 US8559601B2 (en) 2005-04-15 2008-12-29 Handling emergency service calls originating from internet telephony
US13/955,136 Abandoned US20130315384A1 (en) 2005-04-15 2013-07-31 Handling emergency service calls originating from internet telephony

Family Applications Before (2)

Application Number Title Priority Date Filing Date
US11/106,603 Active 2027-03-02 US7496182B2 (en) 2005-04-15 2005-04-15 Handling emergency service calls originating from internet telephony
US12/344,819 Active 2027-07-16 US8559601B2 (en) 2005-04-15 2008-12-29 Handling emergency service calls originating from internet telephony

Country Status (1)

Country Link
US (3) US7496182B2 (en)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20130303196A1 (en) * 2005-07-18 2013-11-14 Telecommunication Systems, Inc. Integrated Services User Part (ISUP)/ Session Initiation Protocol (SIP) Gateway for Unlicensed Mobile Access (UMA) Emergency Services Call Flow
US20140139614A1 (en) * 2010-03-26 2014-05-22 Insors Integrated Communications Methods, systems and program products for managing resource distribution among a plurality of server applications
US9860722B1 (en) * 2014-01-30 2018-01-02 Sprint Communications Company L.P. Converting location information into public safety answering point (PSAP) signaling

Families Citing this family (44)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7894807B1 (en) * 2005-03-30 2011-02-22 Openwave Systems Inc. System and method for routing a wireless connection in a hybrid network
US7496182B2 (en) * 2005-04-15 2009-02-24 Verizon Business Global Llc Handling emergency service calls originating from internet telephony
US8116720B2 (en) * 2005-05-06 2012-02-14 Alcatel Lucent Method and apparatus for emergency call routing using an end node
US7933385B2 (en) 2005-08-26 2011-04-26 Telecommunication Systems, Inc. Emergency alert for voice over internet protocol (VoIP)
US8824454B2 (en) * 2005-10-24 2014-09-02 West Corporation Peering network for parameter-based routing of special number calls
US20070140457A1 (en) * 2005-12-19 2007-06-21 Sbc Knowledge Ventures Lp Method and apparatus for selectively routing callers to service call centers
US20070153986A1 (en) * 2006-01-03 2007-07-05 Sony Ericsson Mobile Communications Ab Method and Apparatus for Routing Emergency Calls in a VoIP System
US20070189492A1 (en) * 2006-01-20 2007-08-16 George Heinrichs Peering network for parameter-based routing of special number calls
US8457109B2 (en) * 2006-01-31 2013-06-04 United States Cellular Corporation Access based internet protocol multimedia service authorization
EP1850532B1 (en) * 2006-04-29 2012-03-28 Alcatel Lucent Method of providing a guest terminal with emergency access over a WLAN
US7889718B2 (en) * 2006-05-10 2011-02-15 Microsoft Corporation Determining physical location of network devices
US8442481B2 (en) 2006-05-16 2013-05-14 RedSky Technologies, Inc. Emergency location information gateway for public safety answering points (PSAPs) and method of use
US8463284B2 (en) 2006-07-17 2013-06-11 Telecommunication Systems, Inc. Short messaging system (SMS) proxy communications to enable location based services in wireless devices
KR20080012080A (en) * 2006-08-02 2008-02-11 주식회사유비컴테크놀로지 Peripheral devices integrated ubiquitous multifunction personal computer
US20080147546A1 (en) * 2006-09-19 2008-06-19 Walter Weichselbaumer Wireless device electronic wallet transaction validation
US8099105B2 (en) 2006-09-19 2012-01-17 Telecommunication Systems, Inc. Device based trigger for location push event
US9408046B2 (en) 2006-10-03 2016-08-02 Telecommunication Systems, Inc. 911 data messaging
CA3032707A1 (en) 2006-11-02 2008-05-08 Voip-Pal.Com, Inc. Producing routing messages for voice over ip communications
US8422507B2 (en) 2006-11-29 2013-04-16 Digifonica (International) Limited Intercepting voice over IP communications and other data communications
US8010079B2 (en) * 2006-12-28 2011-08-30 Trueposition, Inc. Emergency wireless location system including a wireless transceiver
US7848733B2 (en) * 2006-12-28 2010-12-07 Trueposition, Inc. Emergency wireless location system including a location determining receiver
CA2681984C (en) * 2007-03-26 2019-04-02 Digifonica (International) Limited Emergency assistance calling for voice over ip communications systems
US8830987B2 (en) * 2007-06-07 2014-09-09 Solacom Technologies Inc. IP-based call answering point selection and routing
US8149996B2 (en) * 2007-07-05 2012-04-03 West Corporation Providing routing information to an answering point of an emergency services network
US20090103687A1 (en) * 2007-10-17 2009-04-23 Vixxi Solutions, Inc. Geographic referenced telephone switching
US20100166154A1 (en) * 2007-10-17 2010-07-01 Vixxi Solutions, Inc. System and method for flexible forwarding of emergency call information
US9369294B2 (en) * 2007-12-14 2016-06-14 Telecommunication Systems, Inc. Reverse 911 using multicast session internet protocol (SIP) conferencing of voice over internet protocol (VoIP) users
WO2009078966A1 (en) * 2007-12-14 2009-06-25 Telecommunication Systems, Inc. Wireless application protocol (wap) application location based services (lbs)
EP2106097A1 (en) * 2008-03-27 2009-09-30 Alcatel Lucent Method and device for providing peer-to-peer emergency service
US7987218B2 (en) * 2008-05-05 2011-07-26 West Corporation Method and system for establishing a spatial street address data set
US20090290688A1 (en) * 2008-05-22 2009-11-26 Vixxi Solutions, Inc. System and method for selectively connecting denied calls
WO2010055410A1 (en) * 2008-11-17 2010-05-20 Nokia Corporation Method for srvcc emergency call support
US8396445B2 (en) * 2009-03-12 2013-03-12 At&T Intellectual Property I, L.P. Method to implement E911 services in IMS (IP Multimedia Subsystem)
US20100261448A1 (en) * 2009-04-09 2010-10-14 Vixxi Solutions, Inc. System and method for emergency text messaging
US8675566B2 (en) 2009-09-17 2014-03-18 Digifonica (International) Limited Uninterrupted transmission of internet protocol transmissions during endpoint changes
US20110206036A1 (en) * 2010-02-25 2011-08-25 West Corporation System and method for method for providing an indication of certainty of location of origin of an internet protocol emergency call
US20120006610A1 (en) 2010-07-09 2012-01-12 Erik Wallace Telematics enhanced mobile device safety interlock
US8688174B2 (en) 2012-03-13 2014-04-01 Telecommunication Systems, Inc. Integrated, detachable ear bud device for a wireless phone
US10298521B2 (en) * 2012-07-06 2019-05-21 Michael Oliszewski Systems and methods for connecting legacy products via an analog telephone adapter (ATA)
US8526576B1 (en) * 2012-11-02 2013-09-03 Connexon Telecom, Inc. Systems and methods for exchanging call routing policies for voice over IP calls
WO2015026247A1 (en) 2013-08-23 2015-02-26 Motorola Solutions, Inc. Method of and system for controlling communications between a personal communications device and a public safety network in an emergency
US9531564B2 (en) * 2014-01-15 2016-12-27 Cisco Technology, Inc. Single hop overlay architecture for line rate performance in campus networks
US9621735B2 (en) 2014-06-25 2017-04-11 Textnow, Inc. Mobile electronic communications combining voice-over-IP and mobile network services
US9843916B2 (en) 2015-05-22 2017-12-12 Nebulys Technologies, Inc. Systems and methods for automatic emergency contact routing

Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20030156577A1 (en) * 2002-02-19 2003-08-21 Mitel Knowledge Corporation Solution to enhanced emergency services (e.g. 911) for IP telephony systems
US6799049B1 (en) * 2000-12-19 2004-09-28 Bellsouth Intellectual Property Corporation System and method for tracking movement of a wireless device
US20040190497A1 (en) * 2003-03-29 2004-09-30 Mark Clinton Knox System and method for routing telephone calls involving internet protocol network
US20050083911A1 (en) * 2003-10-21 2005-04-21 3Com Corporation, A Corporation Of The State Of Delaware IP-based enhanced emergency services using intelligent client devices
US20060120517A1 (en) * 2004-03-05 2006-06-08 Avaya Technology Corp. Advanced port-based E911 strategy for IP telephony
US20060188073A1 (en) * 2003-08-27 2006-08-24 Wright Ronald Paul Methods, systems and computer program products for providing a E911 network
US7843934B2 (en) * 2002-01-08 2010-11-30 Verizon Services Corp. Methods and apparatus for providing emergency telephone service to IP-based telephone users

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO1999003257A1 (en) * 1997-07-09 1999-01-21 Sbc Technology Resources, Inc. Local routing system and method
US20050169248A1 (en) * 2004-02-04 2005-08-04 Nortel Networks Limited Method and apparatus for providing in-band location information in an emergency response network
US7352847B2 (en) * 2004-08-17 2008-04-01 Lucent Technologies Inc. Optimized routing of VoIP emergency calls
US7496182B2 (en) * 2005-04-15 2009-02-24 Verizon Business Global Llc Handling emergency service calls originating from internet telephony

Patent Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6799049B1 (en) * 2000-12-19 2004-09-28 Bellsouth Intellectual Property Corporation System and method for tracking movement of a wireless device
US7843934B2 (en) * 2002-01-08 2010-11-30 Verizon Services Corp. Methods and apparatus for providing emergency telephone service to IP-based telephone users
US20030156577A1 (en) * 2002-02-19 2003-08-21 Mitel Knowledge Corporation Solution to enhanced emergency services (e.g. 911) for IP telephony systems
US20040190497A1 (en) * 2003-03-29 2004-09-30 Mark Clinton Knox System and method for routing telephone calls involving internet protocol network
US20060188073A1 (en) * 2003-08-27 2006-08-24 Wright Ronald Paul Methods, systems and computer program products for providing a E911 network
US20050083911A1 (en) * 2003-10-21 2005-04-21 3Com Corporation, A Corporation Of The State Of Delaware IP-based enhanced emergency services using intelligent client devices
US20060120517A1 (en) * 2004-03-05 2006-06-08 Avaya Technology Corp. Advanced port-based E911 strategy for IP telephony

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20130303196A1 (en) * 2005-07-18 2013-11-14 Telecommunication Systems, Inc. Integrated Services User Part (ISUP)/ Session Initiation Protocol (SIP) Gateway for Unlicensed Mobile Access (UMA) Emergency Services Call Flow
US8954029B2 (en) * 2005-07-18 2015-02-10 Telecommunication Systems, Inc. Integrated services user part (ISUP)/ session initiation protocol (SIP) gateway for unlicensed mobile access (UMA) emergency services call flow
US20140139614A1 (en) * 2010-03-26 2014-05-22 Insors Integrated Communications Methods, systems and program products for managing resource distribution among a plurality of server applications
US9571793B2 (en) * 2010-03-26 2017-02-14 Iocom Uk Limited Methods, systems and program products for managing resource distribution among a plurality of server applications
US9860722B1 (en) * 2014-01-30 2018-01-02 Sprint Communications Company L.P. Converting location information into public safety answering point (PSAP) signaling

Also Published As

Publication number Publication date
US7496182B2 (en) 2009-02-24
US20090141870A1 (en) 2009-06-04
US20060233317A1 (en) 2006-10-19
US8559601B2 (en) 2013-10-15

Similar Documents

Publication Publication Date Title
US8718595B2 (en) Emergency data message router database
US7130385B1 (en) Advanced port-based E911 strategy for IP telephony
US7054611B2 (en) System and method for providing mobile caller information to a special number service station
US8886154B2 (en) Systems and methods for providing emergency callback procedures
US9197450B2 (en) SS7 MAP/Lg+ to sip based call signaling conversion gateway for wireless VoIP
TWI359607B (en) Peering network for parameter-based routing of spe
JP4253587B2 (en) Routing emergency calls based on the geographical location of the originating telephone office
US8903355B2 (en) Answering or releasing emergency calls from a map display for an emergency services platform
US7843903B2 (en) Methods, systems, and computer program products for emergency 911 (E911) registration assistance for subscribers using portable internet protocol (IP) communications devices
US8036342B2 (en) Methods and systems for providing foreign call back number compatibility for VoIP E9-1-1 calls
US20050169248A1 (en) Method and apparatus for providing in-band location information in an emergency response network
US20080107243A1 (en) Method And Apparatus For Handling Emergency Calls
US7653186B2 (en) System and method for event communication correlation
US7440442B2 (en) IP-based enhanced emergency services using intelligent client devices
JP2009522928A (en) Method and apparatus for routing emergency calls in a VOIP system
JP2009522926A (en) Method and apparatus for routing emergency calls in a VOIP system
US20070036139A1 (en) System and method for authenticating internetwork resource requests
US7907551B2 (en) Voice over internet protocol (VoIP) location based 911 conferencing
CA2487656C (en) Emergency call handling in a voice-over-packet environment
EP1643740A1 (en) System and method for enabling callback for VoIP emergency calls
US20090047924A1 (en) System and method for providing location information to a public safety answering point during an emergency 911 call from a WiFi handset
US7433673B1 (en) Method and system for providing location information for a wireless local area network (WLAN)
US8064875B2 (en) Methods and apparatus to update geographic location information associated with internet protocol devices for E-911 emergency services
US20050201529A1 (en) Method and apparatus for increasing the reliability of an emergency call communication network
US20060109960A1 (en) System and method for unilateral verification of caller location information

Legal Events

Date Code Title Description
STCB Information on status: application discontinuation

Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION