US20070121798A1 - Public service answering point (PSAP) proxy - Google Patents
Public service answering point (PSAP) proxy Download PDFInfo
- Publication number
- US20070121798A1 US20070121798A1 US11/472,308 US47230806A US2007121798A1 US 20070121798 A1 US20070121798 A1 US 20070121798A1 US 47230806 A US47230806 A US 47230806A US 2007121798 A1 US2007121798 A1 US 2007121798A1
- Authority
- US
- United States
- Prior art keywords
- psap
- voip
- call
- internet protocol
- access point
- 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
Links
- 238000000034 method Methods 0.000 claims description 10
- 206010047289 Ventricular extrasystoles Diseases 0.000 abstract description 7
- 238000005129 volume perturbation calorimetry Methods 0.000 abstract description 7
- 108010007100 Pulmonary Surfactant-Associated Protein A Proteins 0.000 abstract 11
- 102100027773 Pulmonary surfactant-associated protein A2 Human genes 0.000 abstract 11
- 239000004165 Methyl ester of fatty acids Substances 0.000 description 15
- 238000005516 engineering process Methods 0.000 description 15
- 235000015854 Heliotropium curassavicum Nutrition 0.000 description 7
- 244000301682 Heliotropium curassavicum Species 0.000 description 7
- 239000000969 carrier Substances 0.000 description 3
- 230000001413 cellular effect Effects 0.000 description 3
- 230000000977 initiatory effect Effects 0.000 description 3
- 230000008569 process Effects 0.000 description 3
- 230000005540 biological transmission Effects 0.000 description 2
- 230000004044 response Effects 0.000 description 2
- RYGMFSIKBFXOCR-UHFFFAOYSA-N Copper Chemical compound [Cu] RYGMFSIKBFXOCR-UHFFFAOYSA-N 0.000 description 1
- 239000008186 active pharmaceutical agent Substances 0.000 description 1
- 238000011956 best available technology Methods 0.000 description 1
- 238000006243 chemical reaction Methods 0.000 description 1
- 230000002860 competitive effect Effects 0.000 description 1
- 230000002349 favourable effect Effects 0.000 description 1
- 230000003993 interaction Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000002085 persistent effect Effects 0.000 description 1
- 230000011664 signaling Effects 0.000 description 1
- 230000003068 static effect Effects 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
- H04L65/1066—Session management
- H04L65/1069—Session establishment or de-establishment
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
- H04L65/1066—Session management
- H04L65/1101—Session protocols
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
- H04L65/1066—Session management
- H04L65/1101—Session protocols
- H04L65/1104—Session initiation protocol [SIP]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
- H04L65/40—Support for services or applications
- H04L65/401—Support for services or applications wherein the services involve a main real-time session and one or more additional parallel real-time or time sensitive sessions, e.g. white board sharing or spawning of a subconference
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M7/00—Arrangements for interconnection between switching centres
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M2242/00—Special services or facilities
- H04M2242/04—Special services or facilities for emergency applications
Definitions
- This invention relates generally to telecommunication. More particularly, it relates to location based services for the provision of E-9-1-1 emergency services using Voice Over Internet Protocol (VoIP) protocols and architectures.
- VoIP Voice Over Internet Protocol
- E911 is a phone number widely recognized in North America as an emergency phone number that is used to contact emergency dispatch personnel.
- Enhanced 911 (E911) is defined by the transmission of callback number and location information.
- E911 may be implemented for landline, cellular and/or VoIP.
- a Public Service Answering Point is a dispatch office that receives 9-1-1 calls from the public.
- a PSAP may be a local, fire or police department, an ambulance service or a regional office covering all services.
- a 9-1-1 (“911”) service becomes E-9-1-1 (“E911”) when automatic number identification and automatic location information related to the call is provided to the 911 operator.
- VoIP Voice-Over-Internet Protocol
- IP Internet Protocol
- PSTN Public Switched Telephone Network
- PSAPs Public Safety Access Points
- the existing E911 infrastructure is built upon copper wire line voice technology and is not fully compatible with VoIP. Given VoIP technology, there are at least three VoIP scenarios that require E911 service:
- VoIP 911 call-routing relies on a VoIP Positioning Center (VPC) to receive VoIP 911 calls, determine the location of the VoIP caller (through prior location provisioning, or passing location with call signaling), determine the correct PSAP for that location and determine how that PSAP can receive VoIP calls (e.g. over PSTN, over Selective Router, or over VoIP). Additionally, the VPC is responsible for interaction with the PSAP's ALI, handling the various ALI protocols.
- ALI is a database that relates a specific telephone number to an address. This database accepts a PSAP query with a telephone number and responds with an address.
- ESQK Emergency Services Query Key
- the ALI database steers the query to the appropriate VPC and steers the response back to the PSAP.
- An ESQK is a digit string that uniquely identifies an ongoing emergency services call and is used to correlate the emergency services call with the associated data messages. It may also identify an emergency services zone and may be used to route the call through the network. Similar to an Emergency Services Routing Key (ESRK) in wireless E9-1-1 networks.)
- ESRK Emergency Services Routing Key
- a VoIP Positioning Center is acting as a “Swiss Army Knife” of VoIP Emergency Service.
- URI Uniform Resource Identifier
- SIP Session Initiation Protocol
- URI Uniform Resource Identifier
- SIP is the IP-based protocol defined in IETF RFCs 3261 and 2543. SIP is one of two dominant protocols used by the VoIP industry.
- URI is the addressing technology for identifying resources on the Internet or a private intranet. URIs were originally defined as two types: Uniform Resource Locators (URLs) which are addresses with network location, and Uniform Resource Names (URNs) which are persistent names that are address independent. Today, a URI is defined by its purpose rather than the URL vs. URN classification.)
- FIG. 3 shows basic conventional VoIP elements required to interconnect a VoIP emergency E911 caller to a relevant public safety access point (PSAP).
- PSAP public safety access point
- VoIP telephone devices 102 a , 102 b , 102 c are connected to respective VoIP Service Provider (VSP) soft switches 104 a , 104 b , 104 c (collectively referred to as 104 ) using an Internet Protocol (IP) connection, most commonly over the Internet.
- VoIP service provider's soft switch 104 in turn communicates with a respective VoIP Positioning Center (VPC) 106 a , 106 b , 106 c (collectively referred to as 106 ) using an appropriate IP connection.
- VPC VoIP Positioning Center
- Each VSP requires use of their own VPC, as depicted in FIG. 3 .
- FIG. 4 shows in more detail conventional VoIP elements required by a VPC to interconnect a VoIP emergency E911 caller to a relevant public safety access point (PSAP).
- PSAP public safety access point
- each VPC 106 comprises its own respective route determination module 404 , call delivery module 406 , and provisioning list 408 .
- a respective location information server (LIS) 108 services each of the VPCs 106 .
- the LIS 108 is responsible for storing and providing access to the subscriber location information needed for E9-1-1 call processing (as defined by the NENA VoIP Location Working Group).
- a conventional VoIP Positioning Center (VPC) 106 is a system that attempts to determine the appropriate or correct PSAP 114 that a VoIP emergency E911 call should be routed to based on the VoIP subscriber's position.
- the conventional VPC 106 also returns associated routing instructions to the VoIP network.
- the conventional VPC 106 additionally provides the caller's location and the callback number to the relevant PSAP through the automatic location identifier (ALI) (The ALI is a database that accepts a PSAP query, and using that relates a specific telephone number to a street address. In the case of an Emergency Services Query Key (ESQK), the ALI database steers the query to the appropriate VPC and steers the response back to the PSAP.
- ALI is typically owned by a LEC or a PSAP.
- each VSP route the emergency 9-1-1 call, without location object added, to their VPC 106 .
- the VPC must determine the correct PSAP 114 (collectively represented by PSAP 114 a , 114 b and 114 c ) and route to it using the appropriate technology.
- the VPC 106 passes the 9-1-1 call to the PSAP 114 a using an INVITE telephone number message, via a media gateway 110 that translates between the IP protocol of the INVITE message and a telephone line interface, and interfaces with the public switched telephone network (PSTN) 112 .
- PSTN public switched telephone network
- the VPC 106 passes the 9-1-1 call to the PSAP 114 b using an INVITE S/R message, via an ESGW 120 and selective router 122 .
- the selective router 122 is connected to the relevant PSAP 114 b via direct trunks.
- the VPC 106 passes the 9-1-1 call to the PSAP 114 c using an INVITE PSAP message, via IP, to the PSAP 114 c.
- the ALI 126 must be inter-connected with each VPC 106 (a,b,c). Furthermore, each VPC is burdened with supporting all the various ALI protocols: ve2, e2, PAM, legacy NENA, etc.
- each VoIP service provider requires its own VPC 106 comprising multiple elements (route determination module 404 , call delivery module 406 , and provisioning list 408 ).
- Conventional VPCs used by any given VoIP service provider are required to handle many aspects of routing an emergency VoIP E911 call to the relevant PSAP and providing ALI information to the PSAP, creating an expensive and highly complex architecture all in one place.
- the complexity is compounded by the fact that many (if not most) PSAPs are not capable of being accessed by an emergency VoIP E911 call via Internet Protocol (IP).
- IP Internet Protocol
- each VoIP service provider of which there are many, must implement their own VPC, causing wasteful inefficiencies in the system architecture as appreciated by the present inventors.
- VPC voice positioning center
- a voice over Internet Protocol (VoIP) emergency call is delivered to a public safety access point (PSAP) by determining a route of a VoIP emergency call.
- An INVITE message including a location object relating to a caller of said VoIP emergency call is passed over a connection utilizing Session Initiation Protocol (SIP).
- SIP Session Initiation Protocol
- a provisioning is looked up of the PSAP for accessing the PSAP with the VoIP emergency call.
- the INVITE message is delivered to the PSAP using an appropriate interface designated by the looked up access technology provisioned.
- PSAP Proxy a new VoIP element called a “PSAP Proxy” is introduced.
- the PSAP Proxy's role in VoIP E-9-1-1 is to represent the PSAP as a VoIP entity to the VoIP Service Provider.
- the PSAP Proxy represents ALI delivery over IP to the IP capable PSAP and a common protocol platform for access to traditional ALI databases.
- the PSAP Proxy makes it appear as if each PSAP is VoIP enabled.
- the PSAP Proxy takes over the burden from the VPC of delivering the call to the PSAP via whatever technology is required to route calls to the PSAP (e.g. PSTN, dedicated trunks, VoIP).
- the PSAP Proxy makes it appear as if each PSAP is ve2 enabled (ve2 is the current NENA VoIP standard ALI interface).
- the PSAP Proxy takes over the burden from the VPC of delivering ALI information to the PSAP via whatever technology or protocol the PSAP's ALI requires.
- FIG. 1 shows the implementation of a PSAP proxy in an IP network, in accordance with the principles of the present invention.
- FIG. 2 shows in more detail the implementation of a PSAP proxy in an IP network as shown in FIG. 1 .
- FIG. 3 shows basic conventional VoIP elements required to interconnect a VoIP emergency E911 caller to a relevant public safety access point (PSAP).
- PSAP public safety access point
- FIG. 4 shows in more detail conventional VoIP elements required to interconnect a VoIP emergency E911 caller to a relevant public safety access point (PSAP).
- PSAP public safety access point
- the present invention implements VoIP functions of call delivery and content delivery (e.g, ALI) in a separate network entity referred to herein as a “PSAP Proxy”.
- a PSAP Proxy is a unit that handles delivery of a VoIP call to a correct PSAP.
- a PSAP Proxy also provides VoIP call ALI information to the PSAP.
- the PSAP Proxy is separately IP addressable by multiple different VPCs, potentially from multiple VoIP service providers, providing greater network simplicity and efficiency than is provided by conventional network architectures.
- VoIP Voice Over Internet Protocol
- the VoIP Service Provider's Soft Switch sends the VoIP call to a VPC for addition of a Location Object (LO).
- LO Location Object
- the VPC selects the correct PSAP Proxy and passes the E911 emergency call, with location object, over an Internet Protocol connection to the correct PSAP Proxy.
- the PSAP proxy accepting an IP input from the VPC, handles delivery of the emergency VoIP call to the PSAP using the best available technology to interconnect with the PSAP.
- the PSAP Proxy in accordance with the present invention makes all PSAPs appear IP capable to the VoIP service providers, and provides a SIP URI for all PSAPs.
- the PSAP Proxy communicates with any other components or entities required to process the call (e.g., Selective Router, PSTN, PSAP).
- PSAP requests ALI information from the PSAP Proxy
- PSAP Proxy will handle protocol conversions between the existing ALI protocols (ve2, e2, e2+, PAM, legacy NENA, etc.) to NENA ve2 or NENA e2 used to communicate with a VPC.
- the PSAP Proxy technique as disclosed and taught herein provides VoIP service providers and VoIP positioning centers with the ability to deliver calls and automatic location identifier (ALI) information to PSAPs with the PSAP Proxy.
- ALI automatic location identifier
- a PSAP proxy in accordance with the principles of the present invention allows local exchange carriers (LECs) and Competitive Local Exchange Carriers (CLECs) the ability to collect inbound calls for routing via their public switched telephone network (PSTN) and emergency service network to the PSAPs.
- LECs local exchange carriers
- CLECs Competitive Local Exchange Carriers
- FIG. 1 shows implementation of a PSAP proxy 100 in an IP network, in accordance with the principles of the present invention.
- a network comprises multiple VoIP users 102 a , 102 b , 102 c , 102 d (collectively referred to herein as 102 ), serviced by a respective plurality of VoIP soft switches 104 a , 104 b , 104 c , 104 d (collectively referred to herein as 104 ).
- VPC VoIP positioning center
- the invention implements the call delivery module 502 and provisioning list 504 remote from the VPC 106 in what is referred to herein as a “PSAP Proxy”.
- the VPCs 106 communicate with the PSAP Proxy 100 via an IP interface connected to a plurality of VPC modules. In this way, call delivery and PSAP provisioning lookup functions can be consolidated into a common location for use by a plurality of VoIP service providers.
- the PSAP Proxy can be located within a VoIP service providers network, or because it is remote from the route determination module 508 of the VPC 106 , the PSAP Proxy can be implemented as a commercial service provided by a third party to multiple VoIP service providers.
- the VoIP positioning center (VPC) 106 selects the correct PSAP Proxy, based on a simple lookup of location object information with its designated PSAP. The VPC 106 then transmits the VoIP E911 call, with location object (LO) added, to the correct PSAP Proxy. Only one PSAP Proxy 100 is shown in FIGS. 1 and 2 , but it will be understood by those of ordinary skill in the art that multiple PSAP Proxies may be implemented, either co-located or separately located.
- the PSAP Proxy 100 makes all PSAPs 114 appear IP capable to VoIP service providers (VSPs), and provides a Session Initiation Protocol (SIP) Uniform Resource Identifier (URI) for all PSAPs 114 .
- VoIP Voice over IP
- SIP Session Initiation Protocol
- URI Uniform Resource Identifier
- the PSAP Proxy 100 communicates with any other components or entities required to process the call (e.g., ESGW, Selective Router, PSTN, PSAP).
- ESGW ESGW
- Selective Router PSTN
- PSAP PSAP
- FIG. 2 shows in more detail the implementation of a PSAP proxy 100 in an IP network as shown in FIG. 1 .
- a VoIP user 102 is connected to the VoIP service provider's soft switch 104 , which in turn communicates with a VoIP positioning center (VPC) 106 .
- a location information server (LIS) 108 services the VPC 106 .
- the LIS 108 is responsible for storing and providing access to the subscriber location information needed for E9-1-1 call processing (as defined by the NENA VoIP Location Working Group).
- the VoIP Service Provider's soft switch 104 sends the 9-1-1 call to the voice positioning center (VPC) 106 for addition of a location object (LO).
- VPC voice positioning center
- the PSAP Proxy 100 delivers the emergency 9-1-1 call, with location object added, to a correct PSAP 114 (collectively represented by PSAP 114 a , 114 b and 114 c ).
- the PSAP Proxy 100 passes the 9-1-1 call with location object added to the PSAP 114 a using an INVITE telephone number message, via a media gateway 110 that translates between the IP protocol of the INVITE message and a telephone line interface, and interfaces with the public switched telephone network (PSTN) 112 .
- PSTN public switched telephone network
- the PSAP Proxy 100 serves as a web service automatic location identifier (ALI).
- the PSAP proxy 100 passes the 9-1-1 call with location object added to the PSAP 114 b using an INVITE S/R message, via a ESGW 120 and selective router 122 .
- the selective router 122 is connected to the relevant PSAP 114 b via direct trunks.
- the PSAP proxy 100 passes the 9-1-1 call with location object added to the PSAP 114 c using an INVITE PSAP [LO] message, via IP, to the PSAP proxy 114 c .
- a web service for additional content delivery may be included such that the PSAP 114 c may access the web service.
- ALI data may be passed over the connection i3 between the PSAP proxy 100 and the PSAP 114 c.
- the location object preferably contains at a minimum one or more of the following: precise position (e.g., latitude/longitude), street address, or profile.
- the profile may comprise, e.g., a pre-defined location such as “home” or “work”, which in turn corresponds to a street address or lat/lon.
- the PSAP proxy 100 then converts the INVITE message to the appropriate technology and protocol and sends to the PSAP along with the pertinent information (including, in some cases, the location object for IP-enabled PSAPs).
- Entry 401 gives an example associating a given PSAP, this one identified with a SIP/URI such as 911@kirkland.wa.gov, with a call access type of i1 (PSTN).
- PSAPs can be identified in other unique ways, such as by an assigned number as exemplified in entry 403 .
- the PSAP might be provisioned with an i2 type of call access (i.e., selective router/direct trunk).
- entries 403 - 404 are PSAPs that are provisioned with i3 type call access, which are Internet Protocol (IP) interfaces that are VoIP enabled.
- IP Internet Protocol
- the interface between the VPC 106 and the PSAP Proxy 100 is an Internet Protocol (IP) connection such as the Internet.
- IP Internet Protocol
- any open API may be implemented.
- the PSAP Proxy communicates with any other components or entities required to process the call (e.g., ALI, Selective Router, PSTN, PSAP, VPC).
- ALI ALI
- Selective Router PSTN
- PSAP VPC
- Advantages of the present invention include that it can be used to simplify the introduction or adoption of future technologies system-wide or on a PSAP by PSAP basis, by incorporating additional logic/capability in the PSAP Proxy rather than requiring changes by individual PSAPs, local exchange carriers (LECs), or VoIP service providers (VSPs).
- LEC local exchange carriers
- VSPs VoIP service providers
- the LEC is the wireline carrier for local calls.
- the present invention moves call delivery outside the VoIP positioning center (VPC), simplifying the VPC and increasing flexibility of the system.
Abstract
Description
- 1. Field of the Invention
- This invention relates generally to telecommunication. More particularly, it relates to location based services for the provision of E-9-1-1 emergency services using Voice Over Internet Protocol (VoIP) protocols and architectures.
- 2. Background of the Related Art
- 911 is a phone number widely recognized in North America as an emergency phone number that is used to contact emergency dispatch personnel. Enhanced 911 (E911) is defined by the transmission of callback number and location information. E911 may be implemented for landline, cellular and/or VoIP.
- A Public Service Answering Point (PSAP) is a dispatch office that receives 9-1-1 calls from the public. A PSAP may be a local, fire or police department, an ambulance service or a regional office covering all services. A 9-1-1 (“911”) service becomes E-9-1-1 (“E911”) when automatic number identification and automatic location information related to the call is provided to the 911 operator.
- Voice-Over-Internet Protocol (VoIP) is a technology that emulates a traditional phone call, but instead of using a circuit based system such as the telephone network, it utilizes packetized data transmission techniques most notably implemented in the Internet. 911 calls made using VoIP technology must reach the correct PSAP, but there currently is no uniform interface to the various PSAPs for call delivery because the technology for connecting calls varies. For instance, some PSAPs are Internet Protocol (IP) capable. Some PSAPs are accessed via ordinary Public Switched Telephone Network (PSTN) telephone lines. Some PSAPs are accessed through selective routing such as direct trunks. There is no uniformity among the thousands of different PSAPs.
- Moreover, some Public Safety Access Points (PSAPs) are not enhanced, and thus do not receive the callback or location information at all from any phone; landline, cellular or VoIP.
- The existing E911 infrastructure is built upon copper wire line voice technology and is not fully compatible with VoIP. Given VoIP technology, there are at least three VoIP scenarios that require E911 service:
-
- 1. A VoIP UA that is physically connected to a static data cable at a “home” address. For instance, an Analog Telephone Adapter (ATA) that is connected to the “home” data cable and uses traditional telephone devices.
- 2. A VoIP UA that 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 software telephone would be a VoIP ‘visitor’ device as described by this scenario.
- 3. A VoIP UA that is wireleless, physically disconnected from any data cable. In this situation, the VoIP UA connects to the VoIP service provider via either a wide-are wireless technology (e.g., cellular, PCS, WiMAX) or via a local-area wireless technology (e.g., Wireless Fidelity (WiFi), UWB, etc.) using a laptop computer or handheld device.
- In the current state of technology, VoIP 911 call-routing relies on a VoIP Positioning Center (VPC) to receive VoIP 911 calls, determine the location of the VoIP caller (through prior location provisioning, or passing location with call signaling), determine the correct PSAP for that location and determine how that PSAP can receive VoIP calls (e.g. over PSTN, over Selective Router, or over VoIP). Additionally, the VPC is responsible for interaction with the PSAP's ALI, handling the various ALI protocols. (ALI is a database that relates a specific telephone number to an address. This database accepts a PSAP query with a telephone number and responds with an address. In the case of an Emergency Services Query Key (ESQK), the ALI database steers the query to the appropriate VPC and steers the response back to the PSAP. An ESQK is a digit string that uniquely identifies an ongoing emergency services call and is used to correlate the emergency services call with the associated data messages. It may also identify an emergency services zone and may be used to route the call through the network. Similar to an Emergency Services Routing Key (ESRK) in wireless E9-1-1 networks.) A VoIP Positioning Center is acting as a “Swiss Army Knife” of VoIP Emergency Service.
- Moreover, there is complexity in public access to Public Safety Answering Points due to lack of a Session Initiation Protocol (SIP) Uniform Resource Identifier (URI) for all PSAPs. (SIP is the IP-based protocol defined in IETF RFCs 3261 and 2543. SIP is one of two dominant protocols used by the VoIP industry. URI is the addressing technology for identifying resources on the Internet or a private intranet. URIs were originally defined as two types: Uniform Resource Locators (URLs) which are addresses with network location, and Uniform Resource Names (URNs) which are persistent names that are address independent. Today, a URI is defined by its purpose rather than the URL vs. URN classification.) Some PSAPs are accessed only by conventional telephone line, others only by direct telephone trunk lines. Not all PSAPs are accessible via the Internet.
-
FIG. 3 shows basic conventional VoIP elements required to interconnect a VoIP emergency E911 caller to a relevant public safety access point (PSAP). - In particular, as shown in
FIG. 3 ,VoIP telephone devices soft switches FIG. 3 . -
FIG. 4 shows in more detail conventional VoIP elements required by a VPC to interconnect a VoIP emergency E911 caller to a relevant public safety access point (PSAP). - In particular, as shown in
FIG. 4 , each VPC 106 comprises its own respectiveroute determination module 404, calldelivery module 406, and provisioning list 408. - A respective location information server (LIS) 108 services each of the VPCs 106. The
LIS 108 is responsible for storing and providing access to the subscriber location information needed for E9-1-1 call processing (as defined by the NENA VoIP Location Working Group). - A conventional VoIP Positioning Center (VPC) 106 is a system that attempts to determine the appropriate or
correct PSAP 114 that a VoIP emergency E911 call should be routed to based on the VoIP subscriber's position. The conventional VPC 106 also returns associated routing instructions to the VoIP network. The conventional VPC 106 additionally provides the caller's location and the callback number to the relevant PSAP through the automatic location identifier (ALI) (The ALI is a database that accepts a PSAP query, and using that relates a specific telephone number to a street address. In the case of an Emergency Services Query Key (ESQK), the ALI database steers the query to the appropriate VPC and steers the response back to the PSAP. An ALI is typically owned by a LEC or a PSAP.) - Further as shown in
FIG. 4 , each VSP route the emergency 9-1-1 call, without location object added, to their VPC 106. The VPC must determine the correct PSAP 114 (collectively represented byPSAP - In a first scenario, the VPC 106 passes the 9-1-1 call to the PSAP 114 a using an INVITE telephone number message, via a
media gateway 110 that translates between the IP protocol of the INVITE message and a telephone line interface, and interfaces with the public switched telephone network (PSTN) 112. - In a second scenario, the VPC 106 passes the 9-1-1 call to the PSAP 114 b using an INVITE S/R message, via an ESGW 120 and
selective router 122. In this scenario, theselective router 122 is connected to therelevant PSAP 114 b via direct trunks. - In a third scenario, the VPC 106 passes the 9-1-1 call to the
PSAP 114 c using an INVITE PSAP message, via IP, to thePSAP 114 c. - In the second and third scenario, the
ALI 126 must be inter-connected with each VPC 106 (a,b,c). Furthermore, each VPC is burdened with supporting all the various ALI protocols: ve2, e2, PAM, legacy NENA, etc. - Thus, each VoIP service provider requires its own VPC 106 comprising multiple elements (
route determination module 404, calldelivery module 406, and provisioning list 408). Conventional VPCs used by any given VoIP service provider are required to handle many aspects of routing an emergency VoIP E911 call to the relevant PSAP and providing ALI information to the PSAP, creating an expensive and highly complex architecture all in one place. The complexity is compounded by the fact that many (if not most) PSAPs are not capable of being accessed by an emergency VoIP E911 call via Internet Protocol (IP). Moreover, each VoIP service provider, of which there are many, must implement their own VPC, causing wasteful inefficiencies in the system architecture as appreciated by the present inventors. This makes the conventional VPC difficult to manage since it accomplishes not only route determination using theroute determination module 404, but also delivery of calls using acall delivery module 406, and additionally serves to maintain a provisioning list 408 (i.e., interface type) for accessing each PSAP. This in turn causes great complexity in public access to PSAPs, depending upon various entities in the VoIP world to know the capabilities of each particular PSAP throughout the region, state, or even country. - There is a need for an architecture and methodology that both simplifies the complexity of a voice positioning center (VPC), and which also increases system efficiencies.
- In accordance with the principles of the present invention, a voice over Internet Protocol (VoIP) emergency call is delivered to a public safety access point (PSAP) by determining a route of a VoIP emergency call. An INVITE message including a location object relating to a caller of said VoIP emergency call is passed over a connection utilizing Session Initiation Protocol (SIP). Upon receipt of the passed INVITE message, a provisioning is looked up of the PSAP for accessing the PSAP with the VoIP emergency call. The INVITE message is delivered to the PSAP using an appropriate interface designated by the looked up access technology provisioned.
- In accordance with the principles of the invention, a new VoIP element called a “PSAP Proxy” is introduced. The PSAP Proxy's role in VoIP E-9-1-1 is to represent the PSAP as a VoIP entity to the VoIP Service Provider. For the PSAP the PSAP Proxy represents ALI delivery over IP to the IP capable PSAP and a common protocol platform for access to traditional ALI databases.
- From the VoIP networks' perspective, the PSAP Proxy makes it appear as if each PSAP is VoIP enabled. The PSAP Proxy takes over the burden from the VPC of delivering the call to the PSAP via whatever technology is required to route calls to the PSAP (e.g. PSTN, dedicated trunks, VoIP).
- From the VPC ALI networks' perspective, the PSAP Proxy makes it appear as if each PSAP is ve2 enabled (ve2 is the current NENA VoIP standard ALI interface). The PSAP Proxy takes over the burden from the VPC of delivering ALI information to the PSAP via whatever technology or protocol the PSAP's ALI requires.
-
FIG. 1 shows the implementation of a PSAP proxy in an IP network, in accordance with the principles of the present invention. -
FIG. 2 shows in more detail the implementation of a PSAP proxy in an IP network as shown inFIG. 1 . -
FIG. 3 shows basic conventional VoIP elements required to interconnect a VoIP emergency E911 caller to a relevant public safety access point (PSAP). -
FIG. 4 shows in more detail conventional VoIP elements required to interconnect a VoIP emergency E911 caller to a relevant public safety access point (PSAP). - The present invention implements VoIP functions of call delivery and content delivery (e.g, ALI) in a separate network entity referred to herein as a “PSAP Proxy”. A PSAP Proxy is a unit that handles delivery of a VoIP call to a correct PSAP. A PSAP Proxy also provides VoIP call ALI information to the PSAP. The PSAP Proxy is separately IP addressable by multiple different VPCs, potentially from multiple VoIP service providers, providing greater network simplicity and efficiency than is provided by conventional network architectures.
- When a Voice Over Internet Protocol (VoIP) caller dials 9-1-1, the VoIP Service Provider's Soft Switch sends the VoIP call to a VPC for addition of a Location Object (LO). Then, based on the position of the caller determined by the location object, the VPC selects the correct PSAP Proxy and passes the E911 emergency call, with location object, over an Internet Protocol connection to the correct PSAP Proxy. The PSAP proxy, accepting an IP input from the VPC, handles delivery of the emergency VoIP call to the PSAP using the best available technology to interconnect with the PSAP. In this way, the PSAP Proxy in accordance with the present invention makes all PSAPs appear IP capable to the VoIP service providers, and provides a SIP URI for all PSAPs. The PSAP Proxy communicates with any other components or entities required to process the call (e.g., Selective Router, PSTN, PSAP). When the PSAP requests ALI information from the PSAP Proxy the PSAP Proxy will handle protocol conversions between the existing ALI protocols (ve2, e2, e2+, PAM, legacy NENA, etc.) to NENA ve2 or NENA e2 used to communicate with a VPC.
- The PSAP Proxy technique as disclosed and taught herein provides VoIP service providers and VoIP positioning centers with the ability to deliver calls and automatic location identifier (ALI) information to PSAPs with the PSAP Proxy.
- Moreover, a PSAP proxy in accordance with the principles of the present invention allows local exchange carriers (LECs) and Competitive Local Exchange Carriers (CLECs) the ability to collect inbound calls for routing via their public switched telephone network (PSTN) and emergency service network to the PSAPs.
-
FIG. 1 shows implementation of aPSAP proxy 100 in an IP network, in accordance with the principles of the present invention. - In particular, as shown in
FIG. 1 , a network comprisesmultiple VoIP users soft switches - Importantly, in accordance with the present invention, the conventional VoIP positioning center (VPC) is divided into a smaller, more efficient, less
complex VPC - Also importantly, the invention implements the
call delivery module 502 andprovisioning list 504 remote from the VPC 106 in what is referred to herein as a “PSAP Proxy”. The VPCs 106 communicate with thePSAP Proxy 100 via an IP interface connected to a plurality of VPC modules. In this way, call delivery and PSAP provisioning lookup functions can be consolidated into a common location for use by a plurality of VoIP service providers. - The PSAP Proxy can be located within a VoIP service providers network, or because it is remote from the route determination module 508 of the VPC 106, the PSAP Proxy can be implemented as a commercial service provided by a third party to multiple VoIP service providers.
- The VoIP positioning center (VPC) 106 selects the correct PSAP Proxy, based on a simple lookup of location object information with its designated PSAP. The VPC 106 then transmits the VoIP E911 call, with location object (LO) added, to the correct PSAP Proxy. Only one
PSAP Proxy 100 is shown inFIGS. 1 and 2 , but it will be understood by those of ordinary skill in the art that multiple PSAP Proxies may be implemented, either co-located or separately located. - The
PSAP Proxy 100 makes all PSAPs 114 appear IP capable to VoIP service providers (VSPs), and provides a Session Initiation Protocol (SIP) Uniform Resource Identifier (URI) for allPSAPs 114. - The
PSAP Proxy 100 communicates with any other components or entities required to process the call (e.g., ESGW, Selective Router, PSTN, PSAP). -
FIG. 2 shows in more detail the implementation of aPSAP proxy 100 in an IP network as shown inFIG. 1 . - In particular, as shown in
FIG. 2 , aVoIP user 102 is connected to the VoIP service provider's soft switch 104, which in turn communicates with a VoIP positioning center (VPC) 106. A location information server (LIS) 108 services the VPC 106. TheLIS 108 is responsible for storing and providing access to the subscriber location information needed for E9-1-1 call processing (as defined by the NENA VoIP Location Working Group). - As shown in
FIG. 2 , when theVoIP user 102 dials 9-1-1, the VoIP Service Provider's soft switch 104 sends the 9-1-1 call to the voice positioning center (VPC) 106 for addition of a location object (LO). - Further as shown in
FIG. 2 , thePSAP Proxy 100 delivers the emergency 9-1-1 call, with location object added, to a correct PSAP 114 (collectively represented byPSAP - In a first scenario, the
PSAP Proxy 100 passes the 9-1-1 call with location object added to thePSAP 114 a using an INVITE telephone number message, via amedia gateway 110 that translates between the IP protocol of the INVITE message and a telephone line interface, and interfaces with the public switched telephone network (PSTN) 112. In such case, thePSAP Proxy 100 serves as a web service automatic location identifier (ALI). - In a second scenario, the
PSAP proxy 100 passes the 9-1-1 call with location object added to thePSAP 114 b using an INVITE S/R message, via aESGW 120 andselective router 122. In this scenario, theselective router 122 is connected to therelevant PSAP 114 b via direct trunks. - In a third scenario, the
PSAP proxy 100 passes the 9-1-1 call with location object added to thePSAP 114 c using an INVITE PSAP [LO] message, via IP, to thePSAP proxy 114 c. In such case, a web service for additional content delivery may be included such that thePSAP 114 c may access the web service. Also, ALI data may be passed over the connection i3 between thePSAP proxy 100 and thePSAP 114 c. - In all cases shown in
FIG. 2 the location object preferably contains at a minimum one or more of the following: precise position (e.g., latitude/longitude), street address, or profile. The profile may comprise, e.g., a pre-defined location such as “home” or “work”, which in turn corresponds to a street address or lat/lon. - The
PSAP proxy 100 then converts the INVITE message to the appropriate technology and protocol and sends to the PSAP along with the pertinent information (including, in some cases, the location object for IP-enabled PSAPs). - Currently there are three types of call access to a PSAP by an incoming emergency E911 VoIP call. Each
PSAP 114 may have more than one type of call access: i1 type, i2 type, and/or i3 type. - i1 type call access for a PSAP is a common PSTN telephone line interface. i2 type call access for a PSAP relates to the use of a selective router/direct telephone trunk line. i3 type call access for a PSAP relates to a VoIP enabled PSAP.
- Entry 401 gives an example associating a given PSAP, this one identified with a SIP/URI such as 911@kirkland.wa.gov, with a call access type of i1 (PSTN). Of course, PSAPs can be identified in other unique ways, such as by an assigned number as exemplified in entry 403. Moreover, as exemplified in entry 402, the PSAP might be provisioned with an i2 type of call access (i.e., selective router/direct trunk). Exemplified in entries 403-404 are PSAPs that are provisioned with i3 type call access, which are Internet Protocol (IP) interfaces that are VoIP enabled.
- Most preferably, the interface between the VPC 106 and the
PSAP Proxy 100 is an Internet Protocol (IP) connection such as the Internet. However, any open API may be implemented. - The PSAP Proxy communicates with any other components or entities required to process the call (e.g., ALI, Selective Router, PSTN, PSAP, VPC).
- Advantages of the present invention include that it can be used to simplify the introduction or adoption of future technologies system-wide or on a PSAP by PSAP basis, by incorporating additional logic/capability in the PSAP Proxy rather than requiring changes by individual PSAPs, local exchange carriers (LECs), or VoIP service providers (VSPs). (The LEC is the wireline carrier for local calls.) The present invention moves call delivery outside the VoIP positioning center (VPC), simplifying the VPC and increasing flexibility of the system.
- 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.
- An early and favorable action of the merits is earnestly solicited.
Claims (13)
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US11/472,308 US20070121798A1 (en) | 2005-10-20 | 2006-06-22 | Public service answering point (PSAP) proxy |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US72832605P | 2005-10-20 | 2005-10-20 | |
US11/472,308 US20070121798A1 (en) | 2005-10-20 | 2006-06-22 | Public service answering point (PSAP) proxy |
Publications (1)
Publication Number | Publication Date |
---|---|
US20070121798A1 true US20070121798A1 (en) | 2007-05-31 |
Family
ID=38087496
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US11/472,308 Abandoned US20070121798A1 (en) | 2005-10-20 | 2006-06-22 | Public service answering point (PSAP) proxy |
Country Status (1)
Country | Link |
---|---|
US (1) | US20070121798A1 (en) |
Cited By (11)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20070242660A1 (en) * | 2006-04-14 | 2007-10-18 | Xiaode Xu | Determining a physical location of a VoIP endpoint device utilized to originate an emergency call |
US20080152092A1 (en) * | 2006-12-20 | 2008-06-26 | Rudolf Barton | Emergency call localization for ip-based telephony |
US20080166989A1 (en) * | 2007-01-05 | 2008-07-10 | Eniko Sokondar | System and Method for Conditionally Attempting an Emergency Call Setup |
US20110149953A1 (en) * | 2009-12-23 | 2011-06-23 | William Helgeson | Tracking results of a v2 query in voice over internet (VoIP) emergency call systems |
WO2014018387A2 (en) * | 2012-07-23 | 2014-01-30 | Telecommunication Systems, Inc. | Sip initiated legacy call to an ng911 esinet |
JP2014017822A (en) * | 2007-08-20 | 2014-01-30 | Nec Corp | Method for handling ip based emergency services in wimax |
US20150111527A1 (en) * | 2011-11-14 | 2015-04-23 | Avaya Inc. | Determination by psaps of caller location based on the wifi hot spots detected and reported by the caller's device(s) |
CN107800788A (en) * | 2017-10-23 | 2018-03-13 | 中国人民解放军信息工程大学 | A kind of calling party's area positioning method based on WMG |
CN108234498A (en) * | 2018-01-04 | 2018-06-29 | 广州市申迪计算机系统有限公司 | A kind of communication call source tracing method and system |
US20180352094A1 (en) * | 2017-06-06 | 2018-12-06 | Bandwidth.Com, Inc. | TECHNIQUES FOR MIGRATING LEGACY 911 SYSTEMS to NG-911 SYSTEMS |
US20190215676A1 (en) * | 2017-04-06 | 2019-07-11 | Microsoft Technology Licensing, Llc | Proximity detection of mobile devices for voip calling |
Citations (98)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US4445118A (en) * | 1981-05-22 | 1984-04-24 | The United States Of America As Represented By The Administrator Of The National Aeronautics And Space Administration | Navigation system and method |
US4494119A (en) * | 1983-08-04 | 1985-01-15 | 122923 Canada Limited | Distress radiolocation method and system |
US4651156A (en) * | 1982-02-08 | 1987-03-17 | Mcgraw-Edison Co. | Integrated radio location and communication system |
US4891650A (en) * | 1988-05-16 | 1990-01-02 | Trackmobile Inc. | Vehicle location system |
US4891638A (en) * | 1987-10-30 | 1990-01-02 | Motorola, Inc. | Nationwide display pager with location readout |
US5014206A (en) * | 1988-08-22 | 1991-05-07 | Facilitech International Incorporated | Tracking system |
US6032051A (en) * | 1997-12-01 | 2000-02-29 | Telefonaktiebolaget L/M Ericsson | Wireless mobile comunication devices for group use |
US6360102B1 (en) * | 1998-09-10 | 2002-03-19 | Ericsson Inc. | System and method for defining a subscriber location privacy profile |
US6397208B1 (en) * | 1999-01-19 | 2002-05-28 | Microsoft Corporation | System and method for locating real estate in the context of points-of-interest |
US20020077118A1 (en) * | 2000-12-19 | 2002-06-20 | Zellner Samuel N. | Location blocking service from a wireless service provider |
US20020077083A1 (en) * | 2000-12-19 | 2002-06-20 | Zellner Samuel N. | Identity blocking service from a wireless service provider |
US20020077897A1 (en) * | 2000-12-19 | 2002-06-20 | Zellner Samuel N. | Identity blocking service from a web advertiser |
US20020077084A1 (en) * | 2000-12-19 | 2002-06-20 | Zellner Samuel N. | Location blocking service from a web advertiser |
US20030012148A1 (en) * | 2001-07-10 | 2003-01-16 | Michael Peters | Software based single agent multipoint conference capability |
US20030026245A1 (en) * | 2001-07-31 | 2003-02-06 | Ejzak Richard Paul | Communication system including an interworking mobile switching center for call termination |
US6526026B1 (en) * | 1997-12-10 | 2003-02-25 | Intel Corporation | Digit transmission over wireless communication link |
US6529500B1 (en) * | 1999-08-26 | 2003-03-04 | Verizon Laboratories Inc. | Unified messaging notification |
US20030044654A1 (en) * | 2001-08-31 | 2003-03-06 | Holt Laurence E. | Extending external telephone calls as conference calls with other communicatively proximate wireless devices |
US6539232B2 (en) * | 2000-06-10 | 2003-03-25 | Telcontar | Method and system for connecting mobile users based on degree of separation |
US20030086539A1 (en) * | 2001-11-05 | 2003-05-08 | Mccalmont Patti L | Geographic routing of emergency service call center emergency calls |
US6564261B1 (en) * | 1999-05-10 | 2003-05-13 | Telefonaktiebolaget Lm Ericsson (Publ) | Distributed system to intelligently establish sessions between anonymous users over various networks |
US20030108176A1 (en) * | 1999-12-30 | 2003-06-12 | Fen-Chung Kung | Personal ip follow-me service |
US6687504B1 (en) * | 2000-07-28 | 2004-02-03 | Telefonaktiebolaget L. M. Ericsson | Method and apparatus for releasing location information of a mobile communications device |
US6694351B1 (en) * | 2000-06-30 | 2004-02-17 | Cisco Technology, Inc. | Call optimization in meet-me conference calls |
US20040032485A1 (en) * | 2001-07-31 | 2004-02-19 | Stephens James H. | System and method for communication device configuration, scheduling and access control |
US20040043775A1 (en) * | 2002-08-29 | 2004-03-04 | Kennedy Joseph P. | Tasking and reporting method and implementation for wireless appliance location systems |
US20040047461A1 (en) * | 2002-09-10 | 2004-03-11 | Weisman Jordan Kent | Method and apparatus for improved conference call management |
US20040076277A1 (en) * | 2002-07-04 | 2004-04-22 | Nokia Corporation | Managing a packet switched conference call |
US6731940B1 (en) * | 2000-04-28 | 2004-05-04 | Trafficmaster Usa, Inc. | Methods of using wireless geolocation to customize content and delivery of information to wireless communication devices |
US20050003797A1 (en) * | 2003-07-02 | 2005-01-06 | Baldwin Johnny E. | Localized cellular awareness and tracking of emergencies |
US6847618B2 (en) * | 2001-06-29 | 2005-01-25 | Ip Unity | Method and system for distributed conference bridge processing |
US20050020242A1 (en) * | 1999-07-29 | 2005-01-27 | Bryan Holland | Locator system |
US20050030977A1 (en) * | 2003-01-31 | 2005-02-10 | Qwest Communications International Inc. | Alert gateway, systems and methods |
US20050043037A1 (en) * | 2001-07-16 | 2005-02-24 | Ioppe Igor V. | System for providing alert-based services to mobile stations in a wireless communications network |
US20050053209A1 (en) * | 2003-09-06 | 2005-03-10 | D'evelyn Linda Kaye | Method and system for availing participants in a special number call event and others of information contained in a plurality of data stores |
US20050063519A1 (en) * | 2003-09-22 | 2005-03-24 | Foundry Networks, Inc. | System, method and apparatus for supporting E911 emergency services in a data communications network |
US6876734B1 (en) * | 2000-02-29 | 2005-04-05 | Emeeting.Net, Inc. | Internet-enabled conferencing system and method accommodating PSTN and IP traffic |
US20050074107A1 (en) * | 2003-10-01 | 2005-04-07 | Renner W. Karl | Conference calls via an intelligent call waiting interface |
US20050078612A1 (en) * | 2001-10-30 | 2005-04-14 | Lang Alexander C | Method and apparatus for providing extended call setup and control features using a short message service |
US6882850B2 (en) * | 2001-12-03 | 2005-04-19 | Sprint Spectrum L.P. | Method and system for zone-based capacity control |
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 |
US20050083891A1 (en) * | 2003-10-21 | 2005-04-21 | Chia-En Chuang | Method and apparatus for updating frame number |
US20050101335A1 (en) * | 2003-11-06 | 2005-05-12 | International Business Machines Corporation | System, method and program product for scheduling meetings |
US20050107673A1 (en) * | 2003-11-13 | 2005-05-19 | General Motors Corporation | System and method for maintaining and providing personal information in real time |
US6898633B1 (en) * | 2000-10-04 | 2005-05-24 | Microsoft Corporation | Selecting a server to service client requests |
US20050213716A1 (en) * | 2004-03-23 | 2005-09-29 | Yinjun Zhu | Solutions for voice over internet protocol (VoIP) 911 location services |
US6985747B2 (en) * | 2003-02-05 | 2006-01-10 | Autodesk, Inc. | Use of triggers and a location hypercube to enable push-based location applications |
US20060008065A1 (en) * | 2004-07-08 | 2006-01-12 | Timothy Longman | Method for setting up a conference call |
US20060010200A1 (en) * | 2004-05-20 | 2006-01-12 | Research In Motion Limited | Handling an audio conference related to a text-based message |
US6993355B1 (en) * | 2002-02-22 | 2006-01-31 | Verizon Services Corp. | Methods and apparatus for connecting family members |
US20060023747A1 (en) * | 2004-07-27 | 2006-02-02 | Eitan Koren | Method and apparatus for session layer framing to enable interoperability between packet-switched systems |
US20060026288A1 (en) * | 2004-07-30 | 2006-02-02 | Arup Acharya | Method and apparatus for integrating wearable devices within a SIP infrastructure |
US20060068753A1 (en) * | 2004-09-22 | 2006-03-30 | Jim Karpen | Emergency call handling system |
US20060072729A1 (en) * | 2002-12-20 | 2006-04-06 | Yong Lee | Internet conference call bridge management system |
US20060078094A1 (en) * | 2004-10-12 | 2006-04-13 | Bellsouth Intellectual Property Corporation | Methods and systems for managing a call session |
US20060077911A1 (en) * | 2000-05-17 | 2006-04-13 | Shmuel Shaffer | Call optimization in ad-hoc conference calls |
US20060079330A1 (en) * | 2004-10-13 | 2006-04-13 | Motorola, Inc. | Method and apparatus utilizing dynamic visual characters to address communications |
US20060088152A1 (en) * | 2004-10-21 | 2006-04-27 | Lightbridge, Inc. | Conference-call initiation |
US20070003024A1 (en) * | 2005-06-22 | 2007-01-04 | Cml Emergency Services Inc. | Network emergency call taking system and method |
US20070014282A1 (en) * | 2005-07-18 | 2007-01-18 | Don Mitchell | Integrated services user part (ISUP) /session initiation protocol (SIP) gateway for unlicensed mobile access (UMA) emergency services call flow |
US20070022011A1 (en) * | 2003-10-06 | 2007-01-25 | Utbk, Inc. | Methods and apparatuses to determine prices of communication leads |
US20070019614A1 (en) * | 2003-09-09 | 2007-01-25 | Klaus Hoffmann | Method for providing a user interaction dialogue (uid) prior to connection acceptance by the called user |
US20070027997A1 (en) * | 2005-07-29 | 2007-02-01 | Cisco Technology, Inc. | Technique for translating location information |
US20070026847A1 (en) * | 2005-08-01 | 2007-02-01 | Polk James M | Technique for displaying information ancillary to a location of an entity in a communication network |
US7174153B2 (en) * | 2003-12-23 | 2007-02-06 | Gregory A Ehlers | System and method for providing information to an operator of an emergency response vehicle |
US7177398B2 (en) * | 2004-03-13 | 2007-02-13 | Intrado Inc. | Bi-directional messaging for an emergency services network |
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 |
US20070036139A1 (en) * | 2005-08-09 | 2007-02-15 | Ashish Patel | System and method for authenticating internetwork resource requests |
US20070041513A1 (en) * | 2005-02-08 | 2007-02-22 | Gende Michael F | Emergency call identification, location and routing method and system |
US20070049288A1 (en) * | 2005-08-24 | 2007-03-01 | Lamprecht Leslie J | Creating optimum temporal location trigger for multiple requests |
US20070060097A1 (en) * | 2005-08-02 | 2007-03-15 | Edge Stephen W | VOIP emergency call support |
US7194249B2 (en) * | 2003-01-31 | 2007-03-20 | Qwest Communications International Inc. | Methods, systems and apparatus for providing urgent public information |
US7200380B2 (en) * | 2002-03-28 | 2007-04-03 | Telecommunication Systems, Inc. | Wireless telecommunications location based services scheme selection |
US20070081635A1 (en) * | 2005-09-29 | 2007-04-12 | Marian Croak | Method and apparatus for providing enhanced 911 for nomadic users |
US20070115941A1 (en) * | 2005-10-24 | 2007-05-24 | Ashish Patel | Peering Network for Parameter-Based Routing of Special Number Calls |
US20070121601A1 (en) * | 1998-09-24 | 2007-05-31 | Genesys Telecommunications Laboratories, Inc | Integrating SIP Control Messaging into Existing Communication Center Routing Infrastructure |
US7321773B2 (en) * | 2002-03-28 | 2008-01-22 | Telecommunication Systems, Inc. | Area watcher for wireless network |
US7330899B2 (en) * | 2003-06-05 | 2008-02-12 | Oracle International Corporation | Apparatus and method for developing applications with telephony functionality |
US20080037715A1 (en) * | 2006-06-29 | 2008-02-14 | Nortel Networks Ltd. | Adaption of emergency calls to the emergency services network based on caller location |
US7333480B1 (en) * | 2004-09-20 | 2008-02-19 | Nortel Networks Limited | Localization of call routing for TDM sets in an IP network |
US20080059304A1 (en) * | 2006-08-16 | 2008-03-06 | Kimsey Robert S | Method of active advertising and promotion in an online environment |
US20080063153A1 (en) * | 2006-08-21 | 2008-03-13 | Connexon Telecom Inc. | System and method for delivering callback numbers for emergency calls in a voip system |
US20080065775A1 (en) * | 2006-09-13 | 2008-03-13 | Cisco Technology, Inc. | Location data-URL mechanism |
US7369530B2 (en) * | 2004-01-30 | 2008-05-06 | Scott Keagy | Apparatus and method for interfacing packet-based phone services with emergency call centers |
US7369508B2 (en) * | 2001-10-17 | 2008-05-06 | Spyder Navigations L.L.C. | Informing network about amount of data to be transferred |
US20080117859A1 (en) * | 2006-11-21 | 2008-05-22 | Reza Shahidi | Dynamic operational mode management for a wireless terminal |
US7433673B1 (en) * | 2004-12-17 | 2008-10-07 | Sprint Spectrum L.P. | Method and system for providing location information for a wireless local area network (WLAN) |
US7711094B1 (en) * | 2005-11-16 | 2010-05-04 | Verizon Data Services Llc | E911 location server |
US20100119049A1 (en) * | 2006-12-22 | 2010-05-13 | Bce Inc. | Method and system for configuring information regarding processing of calls involving a party |
US20110013541A1 (en) * | 2005-10-06 | 2011-01-20 | Jon Croy | Voice over internet protocol (VoIP) location based 911 conferencing |
US7889718B2 (en) * | 2006-05-10 | 2011-02-15 | Microsoft Corporation | Determining physical location of network devices |
US7890122B2 (en) * | 2000-02-04 | 2011-02-15 | At&T Intellectual Property I, L.P. | Location privacy manager for a wireless communication device and method thereof |
US8060056B1 (en) * | 2006-12-04 | 2011-11-15 | Sprint Communications Company L.P. | Emergency call service termination |
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 |
US20120001750A1 (en) * | 2006-07-13 | 2012-01-05 | Henry Schein, Inc. | Central facility that communicates with portable container via mobile device |
US20130065550A1 (en) * | 2005-02-22 | 2013-03-14 | Sprint Spectrum L.P. | Method and System for Routing a Voice-Over-Packet Emergency Services Call to an Appropriate Public Safety Answering Point (PSAP) |
US20130072308A1 (en) * | 2011-09-15 | 2013-03-21 | Qonqr, Llc | Location-Based Multiplayer Game System and Method |
US20130079152A1 (en) * | 2007-08-17 | 2013-03-28 | At&T Intellectual Property I, L.P. | Location-based mobile gaming application and method for implementing the same using a scalable tiered geocast protocol |
-
2006
- 2006-06-22 US US11/472,308 patent/US20070121798A1/en not_active Abandoned
Patent Citations (104)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US4445118A (en) * | 1981-05-22 | 1984-04-24 | The United States Of America As Represented By The Administrator Of The National Aeronautics And Space Administration | Navigation system and method |
US4651156A (en) * | 1982-02-08 | 1987-03-17 | Mcgraw-Edison Co. | Integrated radio location and communication system |
US4494119A (en) * | 1983-08-04 | 1985-01-15 | 122923 Canada Limited | Distress radiolocation method and system |
US4891638A (en) * | 1987-10-30 | 1990-01-02 | Motorola, Inc. | Nationwide display pager with location readout |
US4891650A (en) * | 1988-05-16 | 1990-01-02 | Trackmobile Inc. | Vehicle location system |
US5014206A (en) * | 1988-08-22 | 1991-05-07 | Facilitech International Incorporated | Tracking system |
US6032051A (en) * | 1997-12-01 | 2000-02-29 | Telefonaktiebolaget L/M Ericsson | Wireless mobile comunication devices for group use |
US6526026B1 (en) * | 1997-12-10 | 2003-02-25 | Intel Corporation | Digit transmission over wireless communication link |
US6360102B1 (en) * | 1998-09-10 | 2002-03-19 | Ericsson Inc. | System and method for defining a subscriber location privacy profile |
US20070121601A1 (en) * | 1998-09-24 | 2007-05-31 | Genesys Telecommunications Laboratories, Inc | Integrating SIP Control Messaging into Existing Communication Center Routing Infrastructure |
US6397208B1 (en) * | 1999-01-19 | 2002-05-28 | Microsoft Corporation | System and method for locating real estate in the context of points-of-interest |
US6564261B1 (en) * | 1999-05-10 | 2003-05-13 | Telefonaktiebolaget Lm Ericsson (Publ) | Distributed system to intelligently establish sessions between anonymous users over various networks |
US20050020242A1 (en) * | 1999-07-29 | 2005-01-27 | Bryan Holland | Locator system |
US6529500B1 (en) * | 1999-08-26 | 2003-03-04 | Verizon Laboratories Inc. | Unified messaging notification |
US20030108176A1 (en) * | 1999-12-30 | 2003-06-12 | Fen-Chung Kung | Personal ip follow-me service |
US7890122B2 (en) * | 2000-02-04 | 2011-02-15 | At&T Intellectual Property I, L.P. | Location privacy manager for a wireless communication device and method thereof |
US6876734B1 (en) * | 2000-02-29 | 2005-04-05 | Emeeting.Net, Inc. | Internet-enabled conferencing system and method accommodating PSTN and IP traffic |
US6731940B1 (en) * | 2000-04-28 | 2004-05-04 | Trafficmaster Usa, Inc. | Methods of using wireless geolocation to customize content and delivery of information to wireless communication devices |
US20060077911A1 (en) * | 2000-05-17 | 2006-04-13 | Shmuel Shaffer | Call optimization in ad-hoc conference calls |
US6539232B2 (en) * | 2000-06-10 | 2003-03-25 | Telcontar | Method and system for connecting mobile users based on degree of separation |
US6694351B1 (en) * | 2000-06-30 | 2004-02-17 | Cisco Technology, Inc. | Call optimization in meet-me conference calls |
US6687504B1 (en) * | 2000-07-28 | 2004-02-03 | Telefonaktiebolaget L. M. Ericsson | Method and apparatus for releasing location information of a mobile communications device |
US6898633B1 (en) * | 2000-10-04 | 2005-05-24 | Microsoft Corporation | Selecting a server to service client requests |
US20020077083A1 (en) * | 2000-12-19 | 2002-06-20 | Zellner Samuel N. | Identity blocking service from a wireless service provider |
US20020077118A1 (en) * | 2000-12-19 | 2002-06-20 | Zellner Samuel N. | Location blocking service from a wireless service provider |
US20020077897A1 (en) * | 2000-12-19 | 2002-06-20 | Zellner Samuel N. | Identity blocking service from a web advertiser |
US20020077084A1 (en) * | 2000-12-19 | 2002-06-20 | Zellner Samuel N. | Location blocking service from a web advertiser |
US6847618B2 (en) * | 2001-06-29 | 2005-01-25 | Ip Unity | Method and system for distributed conference bridge processing |
US20030012148A1 (en) * | 2001-07-10 | 2003-01-16 | Michael Peters | Software based single agent multipoint conference capability |
US20050043037A1 (en) * | 2001-07-16 | 2005-02-24 | Ioppe Igor V. | System for providing alert-based services to mobile stations in a wireless communications network |
US20030026245A1 (en) * | 2001-07-31 | 2003-02-06 | Ejzak Richard Paul | Communication system including an interworking mobile switching center for call termination |
US20040032485A1 (en) * | 2001-07-31 | 2004-02-19 | Stephens James H. | System and method for communication device configuration, scheduling and access control |
US20030044654A1 (en) * | 2001-08-31 | 2003-03-06 | Holt Laurence E. | Extending external telephone calls as conference calls with other communicatively proximate wireless devices |
US7369508B2 (en) * | 2001-10-17 | 2008-05-06 | Spyder Navigations L.L.C. | Informing network about amount of data to be transferred |
US20050078612A1 (en) * | 2001-10-30 | 2005-04-14 | Lang Alexander C | Method and apparatus for providing extended call setup and control features using a short message service |
US7177397B2 (en) * | 2001-11-05 | 2007-02-13 | Intrado Inc. | Geographic routing of emergency service call center emergency calls |
US20030086539A1 (en) * | 2001-11-05 | 2003-05-08 | Mccalmont Patti L | Geographic routing of emergency service call center emergency calls |
US6882850B2 (en) * | 2001-12-03 | 2005-04-19 | Sprint Spectrum L.P. | Method and system for zone-based capacity control |
US6993355B1 (en) * | 2002-02-22 | 2006-01-31 | Verizon Services Corp. | Methods and apparatus for connecting family members |
US7321773B2 (en) * | 2002-03-28 | 2008-01-22 | Telecommunication Systems, Inc. | Area watcher for wireless network |
US7200380B2 (en) * | 2002-03-28 | 2007-04-03 | Telecommunication Systems, Inc. | Wireless telecommunications location based services scheme selection |
US20040076277A1 (en) * | 2002-07-04 | 2004-04-22 | Nokia Corporation | Managing a packet switched conference call |
US20040043775A1 (en) * | 2002-08-29 | 2004-03-04 | Kennedy Joseph P. | Tasking and reporting method and implementation for wireless appliance location systems |
US6839417B2 (en) * | 2002-09-10 | 2005-01-04 | Myriad Entertainment, Inc. | Method and apparatus for improved conference call management |
US20040047461A1 (en) * | 2002-09-10 | 2004-03-11 | Weisman Jordan Kent | Method and apparatus for improved conference call management |
US20060072729A1 (en) * | 2002-12-20 | 2006-04-06 | Yong Lee | Internet conference call bridge management system |
US20050030977A1 (en) * | 2003-01-31 | 2005-02-10 | Qwest Communications International Inc. | Alert gateway, systems and methods |
US7194249B2 (en) * | 2003-01-31 | 2007-03-20 | Qwest Communications International Inc. | Methods, systems and apparatus for providing urgent public information |
US6985747B2 (en) * | 2003-02-05 | 2006-01-10 | Autodesk, Inc. | Use of triggers and a location hypercube to enable push-based location applications |
US7330899B2 (en) * | 2003-06-05 | 2008-02-12 | Oracle International Corporation | Apparatus and method for developing applications with telephony functionality |
US20050003797A1 (en) * | 2003-07-02 | 2005-01-06 | Baldwin Johnny E. | Localized cellular awareness and tracking of emergencies |
US20050053209A1 (en) * | 2003-09-06 | 2005-03-10 | D'evelyn Linda Kaye | Method and system for availing participants in a special number call event and others of information contained in a plurality of data stores |
US20070019614A1 (en) * | 2003-09-09 | 2007-01-25 | Klaus Hoffmann | Method for providing a user interaction dialogue (uid) prior to connection acceptance by the called user |
US20050063519A1 (en) * | 2003-09-22 | 2005-03-24 | Foundry Networks, Inc. | System, method and apparatus for supporting E911 emergency services in a data communications network |
US20050074107A1 (en) * | 2003-10-01 | 2005-04-07 | Renner W. Karl | Conference calls via an intelligent call waiting interface |
US20070022011A1 (en) * | 2003-10-06 | 2007-01-25 | Utbk, Inc. | Methods and apparatuses to determine prices of communication leads |
US20050083891A1 (en) * | 2003-10-21 | 2005-04-21 | Chia-En Chuang | Method and apparatus for updating frame number |
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 |
US20050101335A1 (en) * | 2003-11-06 | 2005-05-12 | International Business Machines Corporation | System, method and program product for scheduling meetings |
US20050107673A1 (en) * | 2003-11-13 | 2005-05-19 | General Motors Corporation | System and method for maintaining and providing personal information in real time |
US7912446B2 (en) * | 2003-12-19 | 2011-03-22 | Telecommunication Systems, Inc. | Solutions for voice over internet protocol (VoIP) 911 location services |
US7174153B2 (en) * | 2003-12-23 | 2007-02-06 | Gregory A Ehlers | System and method for providing information to an operator of an emergency response vehicle |
US7369530B2 (en) * | 2004-01-30 | 2008-05-06 | Scott Keagy | Apparatus and method for interfacing packet-based phone services with emergency call centers |
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 |
US7177398B2 (en) * | 2004-03-13 | 2007-02-13 | Intrado Inc. | Bi-directional messaging for an emergency services network |
US7260186B2 (en) * | 2004-03-23 | 2007-08-21 | Telecommunication Systems, Inc. | Solutions for voice over internet protocol (VoIP) 911 location services |
US20050213716A1 (en) * | 2004-03-23 | 2005-09-29 | Yinjun Zhu | Solutions for voice over internet protocol (VoIP) 911 location services |
US20060010200A1 (en) * | 2004-05-20 | 2006-01-12 | Research In Motion Limited | Handling an audio conference related to a text-based message |
US20060008065A1 (en) * | 2004-07-08 | 2006-01-12 | Timothy Longman | Method for setting up a conference call |
US20060023747A1 (en) * | 2004-07-27 | 2006-02-02 | Eitan Koren | Method and apparatus for session layer framing to enable interoperability between packet-switched systems |
US20060026288A1 (en) * | 2004-07-30 | 2006-02-02 | Arup Acharya | Method and apparatus for integrating wearable devices within a SIP infrastructure |
US7333480B1 (en) * | 2004-09-20 | 2008-02-19 | Nortel Networks Limited | Localization of call routing for TDM sets in an IP network |
US20060068753A1 (en) * | 2004-09-22 | 2006-03-30 | Jim Karpen | Emergency call handling system |
US20060078094A1 (en) * | 2004-10-12 | 2006-04-13 | Bellsouth Intellectual Property Corporation | Methods and systems for managing a call session |
US20060079330A1 (en) * | 2004-10-13 | 2006-04-13 | Motorola, Inc. | Method and apparatus utilizing dynamic visual characters to address communications |
US20060088152A1 (en) * | 2004-10-21 | 2006-04-27 | Lightbridge, Inc. | Conference-call initiation |
US7433673B1 (en) * | 2004-12-17 | 2008-10-07 | Sprint Spectrum L.P. | Method and system for providing location information for a wireless local area network (WLAN) |
US20070041513A1 (en) * | 2005-02-08 | 2007-02-22 | Gende Michael F | Emergency call identification, location and routing method and system |
US20130065550A1 (en) * | 2005-02-22 | 2013-03-14 | Sprint Spectrum L.P. | Method and System for Routing a Voice-Over-Packet Emergency Services Call to an Appropriate Public Safety Answering Point (PSAP) |
US20070003024A1 (en) * | 2005-06-22 | 2007-01-04 | Cml Emergency Services Inc. | Network emergency call taking system and method |
US20070014282A1 (en) * | 2005-07-18 | 2007-01-18 | Don Mitchell | Integrated services user part (ISUP) /session initiation protocol (SIP) gateway for unlicensed mobile access (UMA) emergency services call flow |
US8090341B2 (en) * | 2005-07-18 | 2012-01-03 | Telecommunication Systems, Inc. | Integrated services user part (ISUP) /session initiation protocol (SIP) gateway for unlicensed mobile access (UMA) emergency services call flow |
US20070027997A1 (en) * | 2005-07-29 | 2007-02-01 | Cisco Technology, Inc. | Technique for translating location information |
US20070026847A1 (en) * | 2005-08-01 | 2007-02-01 | Polk James M | Technique for displaying information ancillary to a location of an entity in a communication network |
US20070060097A1 (en) * | 2005-08-02 | 2007-03-15 | Edge Stephen W | VOIP emergency call support |
US20070036139A1 (en) * | 2005-08-09 | 2007-02-15 | Ashish Patel | System and method for authenticating internetwork resource requests |
US20070049288A1 (en) * | 2005-08-24 | 2007-03-01 | Lamprecht Leslie J | Creating optimum temporal location trigger for multiple requests |
US20070081635A1 (en) * | 2005-09-29 | 2007-04-12 | Marian Croak | Method and apparatus for providing enhanced 911 for nomadic users |
US7907551B2 (en) * | 2005-10-06 | 2011-03-15 | Telecommunication Systems, Inc. | Voice over internet protocol (VoIP) location based 911 conferencing |
US20110013541A1 (en) * | 2005-10-06 | 2011-01-20 | Jon Croy | Voice over internet protocol (VoIP) location based 911 conferencing |
US20070115941A1 (en) * | 2005-10-24 | 2007-05-24 | Ashish Patel | Peering Network for Parameter-Based Routing of Special Number Calls |
US7711094B1 (en) * | 2005-11-16 | 2010-05-04 | Verizon Data Services Llc | E911 location server |
US7889718B2 (en) * | 2006-05-10 | 2011-02-15 | Microsoft Corporation | Determining physical location of network devices |
US20080037715A1 (en) * | 2006-06-29 | 2008-02-14 | Nortel Networks Ltd. | Adaption of emergency calls to the emergency services network based on caller location |
US20120001750A1 (en) * | 2006-07-13 | 2012-01-05 | Henry Schein, Inc. | Central facility that communicates with portable container via mobile device |
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 |
US20080059304A1 (en) * | 2006-08-16 | 2008-03-06 | Kimsey Robert S | Method of active advertising and promotion in an online environment |
US20080063153A1 (en) * | 2006-08-21 | 2008-03-13 | Connexon Telecom Inc. | System and method for delivering callback numbers for emergency calls in a voip system |
US20080065775A1 (en) * | 2006-09-13 | 2008-03-13 | Cisco Technology, Inc. | Location data-URL mechanism |
US20080117859A1 (en) * | 2006-11-21 | 2008-05-22 | Reza Shahidi | Dynamic operational mode management for a wireless terminal |
US8060056B1 (en) * | 2006-12-04 | 2011-11-15 | Sprint Communications Company L.P. | Emergency call service termination |
US20100119049A1 (en) * | 2006-12-22 | 2010-05-13 | Bce Inc. | Method and system for configuring information regarding processing of calls involving a party |
US20130079152A1 (en) * | 2007-08-17 | 2013-03-28 | At&T Intellectual Property I, L.P. | Location-based mobile gaming application and method for implementing the same using a scalable tiered geocast protocol |
US20130072308A1 (en) * | 2011-09-15 | 2013-03-21 | Qonqr, Llc | Location-Based Multiplayer Game System and Method |
Cited By (22)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US8358645B2 (en) * | 2006-04-14 | 2013-01-22 | Cisco Technology, Inc. | Determining a physical location of a VoIP endpoint device utilized to originate an emergency call |
US20070242660A1 (en) * | 2006-04-14 | 2007-10-18 | Xiaode Xu | Determining a physical location of a VoIP endpoint device utilized to originate an emergency call |
US20080152092A1 (en) * | 2006-12-20 | 2008-06-26 | Rudolf Barton | Emergency call localization for ip-based telephony |
US8576990B2 (en) * | 2006-12-20 | 2013-11-05 | International Business Machines Corporation | Emergency call localization for IP-based telephony |
US20080166989A1 (en) * | 2007-01-05 | 2008-07-10 | Eniko Sokondar | System and Method for Conditionally Attempting an Emergency Call Setup |
US8041331B2 (en) * | 2007-01-05 | 2011-10-18 | Research In Motion Limited | System and method for conditionally attempting an emergency call setup |
US8315591B2 (en) | 2007-01-05 | 2012-11-20 | Research In Motion Limited | System and method for conditionally attempting an emergency call setup |
US9019867B2 (en) | 2007-08-20 | 2015-04-28 | Nec Corporation | IP based emergency services solution in WiMAX |
JP2014017822A (en) * | 2007-08-20 | 2014-01-30 | Nec Corp | Method for handling ip based emergency services in wimax |
US20110149953A1 (en) * | 2009-12-23 | 2011-06-23 | William Helgeson | Tracking results of a v2 query in voice over internet (VoIP) emergency call systems |
US9648479B2 (en) * | 2011-11-14 | 2017-05-09 | Avaya Inc. | Determination by PSAPs of caller location based on the WiFi hot spots detected and reported by the caller's device(s) |
US20150111527A1 (en) * | 2011-11-14 | 2015-04-23 | Avaya Inc. | Determination by psaps of caller location based on the wifi hot spots detected and reported by the caller's device(s) |
WO2014018387A3 (en) * | 2012-07-23 | 2014-06-19 | Telecommunication Systems, Inc. | Sip initiated legacy call to an ng911 esinet |
WO2014018387A2 (en) * | 2012-07-23 | 2014-01-30 | Telecommunication Systems, Inc. | Sip initiated legacy call to an ng911 esinet |
US20190215676A1 (en) * | 2017-04-06 | 2019-07-11 | Microsoft Technology Licensing, Llc | Proximity detection of mobile devices for voip calling |
US10433148B2 (en) * | 2017-04-06 | 2019-10-01 | Microsoft Technology Licensing, Llc | Proximity detection of mobile devices for VoIP calling |
US10602340B2 (en) * | 2017-04-06 | 2020-03-24 | Microsoft Technology Licensing, Llc | Proximity detection of mobile devices for VOIP calling |
US10791449B2 (en) * | 2017-04-06 | 2020-09-29 | Microsoft Technology Licensing, Llc | Proximity detection of mobile devices for VoIP calling |
US20180352094A1 (en) * | 2017-06-06 | 2018-12-06 | Bandwidth.Com, Inc. | TECHNIQUES FOR MIGRATING LEGACY 911 SYSTEMS to NG-911 SYSTEMS |
US10367947B2 (en) * | 2017-06-06 | 2019-07-30 | Bandwith.com, Inc. | Techniques for migrating legacy 911 systems to NG-911 systems |
CN107800788A (en) * | 2017-10-23 | 2018-03-13 | 中国人民解放军信息工程大学 | A kind of calling party's area positioning method based on WMG |
CN108234498A (en) * | 2018-01-04 | 2018-06-29 | 广州市申迪计算机系统有限公司 | A kind of communication call source tracing method and system |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US7907551B2 (en) | Voice over internet protocol (VoIP) location based 911 conferencing | |
US20070121798A1 (en) | Public service answering point (PSAP) proxy | |
US9544429B2 (en) | Solutions for voice over internet protocol (VoIP) 911 location services | |
US9426304B2 (en) | Answering or releasing emergency calls from a map display for an emergency services platform | |
US8520805B2 (en) | Video E911 | |
US8903355B2 (en) | Answering or releasing emergency calls from a map display for an emergency services platform | |
US8774370B2 (en) | System and method for delivering callback numbers for emergency calls in a VOIP system | |
US7330464B2 (en) | Location identification for IP telephony to support emergency services | |
US8682286B2 (en) | Enhanced E911 network access for a call center using session initiation protocol (SIP) messaging | |
US8265068B2 (en) | Mapping of IP phones for E911 | |
US7940746B2 (en) | Method and system for locating a voice over internet protocol (VoIP) device connected to a network | |
RU2412552C2 (en) | Temporary enum gateway | |
JP4922952B2 (en) | System and method for providing 911 service to a mobile internet telephone caller | |
US20160183312A1 (en) | Enhanced E911 Network Access for Call Centers | |
US20070003024A1 (en) | Network emergency call taking system and method | |
US7889718B2 (en) | Determining physical location of network devices | |
US20120189002A1 (en) | Protocol Converting 9-1-1 Emergency Messaging Center | |
WO2007044454A2 (en) | Voice over internet protocol (voip) location based 911 conferencing | |
CA2598200A1 (en) | System and method for delivering callback numbers for emergency calls in a voip system |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: TELECOMMUNICATION SYSTEMS, INC., MARYLAND Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:CROY, JON;HINES, JOHN GORDON;JOHNSON, DARRIN;REEL/FRAME:018025/0484 Effective date: 20060620 |
|
AS | Assignment |
Owner name: SILICON VALLEY BANK, AGENT, MASSACHUSETTS Free format text: SECURITY AGREEMENT;ASSIGNORS:TELECOMMUNICATION SYSTEMS, INC.;LONGHORN ACQUISITION, LLC;SOLVERN INNOVATIONS, INC.;AND OTHERS;REEL/FRAME:023870/0484 Effective date: 20091231 Owner name: SILICON VALLEY BANK, AGENT,MASSACHUSETTS Free format text: SECURITY AGREEMENT;ASSIGNORS:TELECOMMUNICATION SYSTEMS, INC.;LONGHORN ACQUISITION, LLC;SOLVERN INNOVATIONS, INC.;AND OTHERS;REEL/FRAME:023870/0484 Effective date: 20091231 |
|
STCB | Information on status: application discontinuation |
Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION |
|
AS | Assignment |
Owner name: SOLVEM INNOVATIONS, INC., MARYLAND Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:SILICON VALLEY BANK;REEL/FRAME:037994/0113 Effective date: 20160223 Owner name: NETWORKS IN MOTION, INC., WISCONSIN Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:SILICON VALLEY BANK;REEL/FRAME:037994/0113 Effective date: 20160223 Owner name: TELECOMMUNICATION SYSTEMS, INC., MARYLAND Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:SILICON VALLEY BANK;REEL/FRAME:037994/0113 Effective date: 20160223 Owner name: LONGHORN ACQUISITION, LLC, MARYLAND Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:SILICON VALLEY BANK;REEL/FRAME:037994/0113 Effective date: 20160223 Owner name: QUASAR ACQUISITION, LLC, GEORGIA Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:SILICON VALLEY BANK;REEL/FRAME:037994/0113 Effective date: 20160223 |