Patent Application
20140286197
1. Field of the Invention
This invention relates generally to Voice Over Internet Protocol (VoIP) and long distance carriers, Internet Service Providers (ISPs), and information content delivery services/providers and long distance carriers. More particularly, it relates to 911 location services for the telecommunication industry.
2. Background of Related Art
911 is a phone number widely recognized as an emergency phone number that is used by emergency dispatch personnel, among other things, to determine a location of a caller. Enhanced 911 (E911) is defined by the transmission of callback number and location information. E911 may be implemented for landline and/or mobile devices.
Some Public Safety Access Points (PSAPs) are not enhanced, and thus do not receive the callback or location information from any phone, landline or mobile.
Voice Over IP (VoIP) is a technology that has been developed as an alternative telephony technology to the conventional telephony service (e.g. PSTN). VoIP takes advantage of high speed Internet data switched networks, and is able to provide low cost telephony services to end users. VoIP technology emulates a phone call, but instead of using a circuit based system such as the telephone network, utilizes packetized data transmission techniques most notably implemented in the Internet.
Voice Over IP is not a single technology, but rather four distinctive applications targeted at distinct market segments in either static, portable, or mobile environments. A first application is the use of VoIP technology with cable and digital subscriber line (DSL), often deployed in static configurations in which the end user stays at a fixed location and uses the standard North American Numbering Plan. Examples of this type service include residential line replacement using cable or DSL connections. Another frequent application is an enterprise use of VoIP technology, usually deployed in static configurations with occasional portability, allowing the end user to easily move his telephony connection anywhere within the enterprise campus. A third application is the use of VoIP with an Internet Service Provider (ISP), usually provided as a highly portable telephony configuration which allows the end user to establish a telecommunications connection wherever they can obtain an internet-based connection to their ISP provider. A last application is the use of VoIP with a Wireless Fidelity (WiFi) network. This is a mobile telephony configuration that allows the end user to take a home-based telephony connection and roam within an interconnected WiFi network, much like cellular technologies allow today.
As VoIP service providers begin to offer VoIP packet based telephony service to the general public as a replacement to conventional switched telephone networks, one key service related issue has been identified in the need to support the ability to determine a caller's location when they dial “911” using a VoIP device. The FCC in the United States has mandated E911 for wireless devices, but not (yet) for VoIP. The VoIP industry, with NENA encouragement, is currently making efforts to voluntarily comply. Moreover, such 911 services become even more important as additional mobility options become available for VoIP terminals, e.g., mobile VoIP phones.
There are at least three VoIP scenarios that require E911 service:
A VoIP gateway is a gateway that bridges a VoIP network (i.e., a packet switched voice service) with a conventional public switched telephone network (PSTN) (i.e., a circuit switched voice service). A major advantage enjoyed by users of a VoIP network is often referred to as “long distance bypassing”. To accomplish a suitable VoIP network, a VoIP provider establishes VoIP gateways throughout a region or country of interest. Each VoIP gateway is connected to a local PSTN. This allows VoIP customers to make long distance calls via the VoIP network, which then route the call to a desired destination using the local circuit at the local gateway.
Conventional VoIP voice gateways are typically located in only a few places across the country. Thus, any 911 call originating in a city such as Miami, for example, may initially be routed to the public safety answer point (PSAP) in, e.g., Minneapolis if the VoIP gateway happens to be located in Minneapolis. Moreover, the call will not be “enhanced”. That is, it will not provide any location or callback information to the dispatcher.
Not all PSAPs support direct-dial administrative lines, many administrative lines are not answered 24 hours-a-day or during periods of heavy call volume, and administrative lines do not support the ability to automatically identify the location of a party dialing 911. Rather, the location of the caller is typically conveyed verbally or through alternative data entry methods that are not supported by all PSAPs. Furthermore, today's VoIP solutions for portable environments terminate calls to an administrative telephone lines at a Public Safety Answering Point (PSAP)—not directly to emergency operators. Thus, unlike 911 calls originating from a wireline or a mobile phones, 911 calls made from a device utilizing VoIP may be routed to an administrative line and are sometimes answered by a front desk receptionist or administrator instead of an actual emergency operator, wasting valuable seconds in the case of an emergency. In addition, existing solutions for 911 calls made on a VoIP network are frequently unable to determine the geographic location of the VoIP caller dialing 911. For example, if an individual is using a virtual private network to tunnel into a corporate server and make a VoIP call through that server, a 911 call will provide no location information unless manually entered before the call.
This problem has been partially resolved as described in
In particular, as shown in
In particular, Option 1 in
A primary challenge results from the fact that the E911 network is not directly accessible via the Public Switched Telephone Network (PSTN); Rather, all enhanced 911 calls must be routed via dedicated local voice trunks to a selective router that in turn routes the call to the PSAP. Calls that do arrive at the PSAP arrive without callback number or location information. Provision of location information to the PSAP via the PSTN also circumvents specific PSAP hardware (e.g., CAD, GIS) designed to facilitate dispatching of responders and tracking the location of the mobile caller.
There is a need for an architecture and methodology to allow VoIP users all features relating to E911 services enjoyed by non-VoIP users, e.g., call back phone number and location information provided to a public safety answer point (PSAP), and to do so both accurately and as quickly as possible. In emergency call situations, often seconds can mean the difference between life and death.
In accordance with the principles of the present invention, a method apparatus for providing mid-call updating of a location of a VoIP terminal, comprises allowing a VoIP call to be established with said VoIP terminal. The updated location information relevant to movement of the VoIP terminal since the call was established is requested. Updated location information relevant to movement of the VoIP terminal since the call was established is transmitted.
In accordance with another aspect of the present invention, a method and apparatus for validating a location of a VoIP terminal, comprises receiving subscriber location information pushed to a VoIP location server using HTTP based protocol. The received subscriber location information is compared against a geographic location database to confirm that an address contained within the subscriber location information is valid.
Features and advantages of the present invention will become apparent to those skilled in the art from the following description with reference to the drawings, in which:
The present invention provides solutions covering different 911 location service aspects in support of Session Initiation Protocol (SIP) based VoIP 911 location services.
In accordance with the principles of the present invention, 911 calls made from a VoIP device are routed directly to an emergency operator, saving valuable seconds in the event of an emergency situation. Moreover, the disclosed embodiments provide accurate location information to emergency operators, as well as a call-back number in the event that the VoIP 911 caller is disconnected. The present invention allows static, portable, and mobile VoIP calls to be routed to PSAPs while automatically providing the location and identity of the caller. A robust solution for emergency services such as is disclosed herein helps to guarantee the future success and growth of VoIP technology.
The present invention provides an E-9-1-1 voice-over-IP (VoIP) solution, wherein a 911 call from a VoIP device is routed directly to the correct Public Safety Answer Point (PSAP) via dedicated trunks, and associated together with correct location information and call-back number.
In accordance with the present invention, local VoIP gateways are incorporated, and a centralized routing intelligence is implemented, to provide access to the existing E911 infrastructure.
In particular, as shown in
Dedicated voice trunks 107-109 are installed between each local VoIP gateway 100 and appropriate selective routers 150a-150c (referred to collectively herein as selective routers 150). Examples of common voice trunks include Centralized Automatic Message Accounting (CAMA) trunks 107, Signaling System #7 (SS7) voice trunks 108, and/or FG-D trunks 109 are installed between each local VoIP gateway 100 and a respective group of selective routers 150.
The selective routers 150 are provisioned as desired and otherwise conventionally known.
An Automatic Location Identification (ALI) database 190 is included, and is provisioned with Emergency Services Location Keys (ESLKs) dedicated for VoIP use as desired and otherwise conventionally known.
Transport Control Protocol/Internet Protocol (TCP/IP) data circuits may be installed between various local VoIP gateways 100. For instance, additional IP circuits may be established between the local VoIP gateway(s) of other carriers to handle additional VoIP traffic.
The message flow resulting from a VoIP call from a given IP device, e.g., IP device 352, is now described with reference to
As a descriptive example, assume a VoIP “E911” call is being placed by VoIP device 352 as shown by “Option 2” from the left side of
In step 1, a caller using the VoIP device 352 dials “911” on their VoIP device 352. In the given example, the VoIP device 352 provides location information with the E911 call.
In step 2, the VoIP switch 120b servicing that particular VoIP device 352 receives the E911 call, and queries the VoIP location server (VLS) 130b for routing information. The query to the VLS 130b includes a callback number, and location information (if mobile).
In step 3, the MSC 130b relates location to specific PSAPs. If the location is static, the phone number and location will already be established in the MSC database 130b. If the VoIP device 352 is mobile, the caller provides location information at the time of log-on. This caller information will then accompany the E911 call. In certain scenarios such as even in static situations, the location information may accompany the E911 call.
In step 4, upon determination of the appropriate PSAP to receive the E911 call, the MSC 130b responds with an Emergency Service Location Key (ESLK), plus IP routing instructions to the VoIP switch 120b. The utilized ESLK is a 10-digit number compatible with the selective router that serves that particular PSAP. ESLKs uniquely identify a specific PSAP. In
The ESLK provided by the VLS 130b to the VoIP switch 120b is unique to the particular PSAP servicing the location that the mobile VoIP device 352 is calling from. The IP routing instructions provided by the VLS 130b to the VoIP switch 120b identify the IP address of the correct local VoIP gateway in the local access and transport area (LATA) where the compatible selective router exists. For example, it might be the local VoIP gateway 100 shown in
In step 5, the VoIP switch 120b routes the VoIP E911 call to the designated VoIP gateway 100. The routed VoIP E911 call includes the ESLK.
In step 6, the VoIP gateway 100 recognizes the ESLK, and selects a corresponding voice egress trunk (e.g., CAMA, SS7 or FG-D) 107-109. The VoIP gateway 100 converts the VoIP data to voice, and egresses the E911 call to the proper selective router 150a, 150b or 150c on the selected trunk 107-109.
In step 7, as in otherwise conventional techniques, upon reaching the selective router 150a, 150b or 150c, the existing E911 infrastructure delivers the E911 call to the proper PSAP 200, 202, 204 or 206 that is assigned to the location that the mobile VoIP device 352 is calling from. Thus, the relevant selective router 150a, 150b or 150c previously provisioned to recognize the ESLK in the ANI field of the CAMA or SS7 voice E911 call, will route the E911 call to the appropriate PSAP 200, 202, 204 or 206.
In step 8, as in otherwise conventional techniques, the PSAP 200, 202, 204 or 206 receives the E911 voice call, and using the ESLK, queries the ALI database 190 for the location of the caller, and for call-back information.
The ALI database 190 steers the ESLK to the appropriate MSC 130b, which in turn responds to the ALI query with the correct location and call-back information. The disclosed ALI query employs otherwise conventional PAM or E2+ protocols.
The sequence of events for Option 1 would be similar as for the above described Option 2, except that the location information would already be stored at the VLS and would not necessarily need to forwarded by the device.
Sequence of events for Option 3 (mobile IP device) would be as follows:
In step 1, a caller using the mobile VoIP device 355 dials “911”.
In step 2, the VoIP switch 120b servicing that particular VoIP device 352 receives the E911 call, and queries the VoIP location server (VLS) 130b for routing information. The query to the VLS 130b includes a callback number, but no location information.
In step 3, the MSC 130b initiates a GPOSREQ to the Position Determining Equipment (PDE) 400 serving the VoIP service provider that provides mobile coverage for the IP device. A PDE is a position determining device that determines a position, e.g., a latitude and longitude in the wireless Phase 2 world. VoIP devices may utilize various wireless communication technologies, including WiFi, 3G, and cellular technology, thus positioning equipment used for cellular devices may be utilized for VoIP devices, given the present invention.
The PDE 400, using otherwise conventional techniques, responds with a gposreq response that contains the latitude and longitude of the mobile IP device. The VLS 130b relates location to a specific PSAP.
Subsequent steps in Option 3 are similar to those described with respect to Option 2.
Implementation of E911 for VoIP callers as disclosed herein facilitates the migration of an individual PSAP to a pure VoIP environment, minimizing additional engineering as VoIP systems become more prevalent and revolutionize the telecom industry.
In particular,
In operation, with reference to
The intermediate VoIP switch 402 sends Call Back Number (CBN) information via SIP protocol. Note that the subscriber's location information is provisioned and validated during the subscriber's registration phase.
Based upon the location of the caller, the VoIP 911 location server 400 determines the correct public safety access point (PSAP) 200-206 to which the 911 call should be directed. The VoIP location server 400 also assigns an Emergency Service Location Key (ESLK), which importantly associates a specific PSAP to a location of a VoIP device from which the 911 call originates. The VoIP location server 400 stages the ESLK, CBN, and location information.
One of the key issues of a VoIP 911 location service is related to how a subscriber's location information can be retrieved. In the current VoIP industry standard, a VoIP subscriber is required to register in the customer VoIP switch 404. During this process, the subscriber's location information can be recorded in the customer VoIP switch 404.
However, conventionally there is an issue regarding how the location information can be used by the VoIP Location Server 400. In addition, the location information (street address etc.) may be incorrect (e.g. typo etc.) because of the need for entry of the location during registration, so validation is desirable. Aspects of the present invention as illustrated herein provide a solution for these issues. A simple HTTP based protocol is defined as such that the CP Office 307 of a local VoIP service provider can push the subscriber location information to the VoIP Location Server.
In particular, as shown in
Upon receiving the location information, the VoIP Location Server 400 validates the location information with a geographic location database to see that the address is valid. If it is, then the VoIP location server 400 converts the location information received to latitude/longitude type information and stores the same in its subscriber database 401.
A Sub_Location_Validation_Res (or Sub_Location_Validation_Ack) message containing an indication of positive acknowledgement is passed from the VoIP location server 400 back to the CP Office 307.
In particular, as shown in
Upon receiving the location information, the VoIP Location Server 400 validates the location information with a geographic location database to see if the received address is valid. If there is not a match, or if the location provided is not in the 911 service coverage (e.g. not in the country), the VoIP Location Server 400 may return one of the following exemplary errors: “Record not found”, or “Not in the service coverage”, or similar.
911 Location Service with Call Routing Via SIP Loopback Signaling
This section provides a solution to properly route a 911 call initiated by a VoIP terminal. The basic concept is that the VoIP 911 Location Server 400 decides which PSAP 200-206 should be responsible for the 911 call based on the caller's location, and provides the routing information as an ESLK inside a SIP INVITE message back to the intermediate VoIP switch 402, which in turn routes the call to the correct PSAP 200-206. The VoIP 911 Location Server 400 stays in the call signaling path, until the call is terminated by either the caller or the appropriate PSAP 200-206.
In particular, as shown in
In step 1, a SIP IP phone initiates an emergency call by sending an SIP INVITE message to the customer's VoIP switch 404, with 911 as destination address and its own id.
In step 2, the customer VoIP switch 404 of the service provider returns a SIP 100 TRYING message to the SIP VoIP phone 352.
In step 3, the customer VoIP switch 404 of the service provider sends a SIP INVITE message to the intermediate VoIP switch 402, and routes the call to the intermediate VoIP switch 402 that connects with the VoIP Location Server 400.
In step 4, the intermediate VoIP switch 402 responds with a SIP 100 TRYING message.
In step 5, the intermediate VoIP switch 402 forwards the received SIP INVITE message to the VoIP Location Server 400.
In step 6, a SIP 100 TRYING message is returned from the VoIP location server 400 to the intermediate VoIP switch 402.
In step 7, based on information received in the INVITE message, the VoIP Location Server 400 optionally initiates a Subscriber Location Retrieval Procedure via, for example, standard remote database procedure call (such as LDAP or RPC or the like), or via the procedure described earlier, to retrieve the subscriber's location based on the registration information that the subscriber provided during the SIP Registration procedure.
In step 8, the VoIP Location Server 400 converts the caller's address to latitude/longitude (if latitude/longitude are not retrieved from the switch) and determines the ESZ of the caller, assigns an ESLK, formats a SIP INVITE message with an assigned ESLK and a default admin number for the service provider, and then sends an INVITE message back to the Intermediate VoIP softswitch 402. The INVITE message may include “911” in the “To” field, and the assigned ESLK in the “From” field.
In step 9, a SIP 100 TRYING message is returned from the VoIP location server 400 to the intermediate VoIP switch 402.
In step 10, the intermediate VoIP switch 402 reserves resources by using MGCP/MEGACO or TGCP at the TDM Gateway.
In step 11, an ISUP IAM message is sent to the appropriate PSAP 200-206.
In step 12, an emergency call is established.
In step 13, the appropriate PSAP 200-206 queries the location of the emergency caller by sending an ESPOSREQ with ESLK.
In step 14, the VoIP Location Server 400 returns the caller's position to the appropriate PSAP 200-206 in an esposreq message.
In step 15, after sometime, the emergency call is terminated by the caller, and a SIP BYE message is transmitted.
In step 16, the customer's VoIP switch 404 returns a “200” message to the VoIP SIP phone 352.
In step 17, a SIP BYE message is sent to the intermediate VoIP switch 402.
In step 18, a “200” message is returned from the intermediate VoIP switch 402 to the customer VoIP switch 404.
In step 19, the intermediate VoIP switch 402 transmits a SIP BYE message to the VoIP Location Server 400.
In step 20, the VoIP Location Server 400 returns a SIP 200 message to the intermediate VoIP server 402, and clears the call data and resources related to the call.
In step 21, the VoIP Location Server 400 sends a SIP BYE message to the intermediate VoIP switch 402 to terminate the call leg to the Intermediate VoIP switch 402.
In step 22, the intermediate VoIP switch 402 returns a SIP 200 message to the VoIP location server 400.
In step 23, the intermediate VoIP switch 402 cleans up the resources at the TDM Gateway 100 using MGCP/MEGACO or TGCP.
In step 24, an ISUP REL message is transmitted from the intermediate VoIP switch 402 to the appropriate PSAP 200-206.
In step 25, an ISUP RLC message is returned by the appropriate PSAP 200-206 to the intermediate VoIP switch 402.
Incoming SIP INVITE message:
In particular, as shown in
In step 1, a SIP IP phone 352 initiates an emergency call by sending an SIP INVITE message, with 911 as the destination address, and its own id.
In step 2, the customer's VoIP switch 404 of the service provider returns a SIP 100 TRYING message.
In step 3, the customer's VoIP switch 404 sends a SIP INVITE message and routes the call to the intermediate VoIP switch 402 that connects with the TCP Location Server 400.
In step 4, the intermediate VoIP switch 402 responds with a SIP 100 TRYING message.
In step 5, the intermediate VoIP switch 402 forwards the SIP INVITE message to the VoIP Location Server 400.
In step 6, a SIP 100 TRYING message is returned.
In step 7, based on information received in the INVITE message, the VoIP Location Server 400 optionally initiates a Subscriber Location Retrieval Procedure via, for example, standard remote database procedure call (e.g., LDAP or RPC or the like, or via the procedure described earlier to retrieve the subscriber's location based on the registration information that the subscriber provided during the SIP Registration procedure.
However, in this scenario, the procedure fails, or there is not a match in the database of the VoIP Location Server 400 with respect to the retrieve location.
In step 8, the VoIP Location Server 400 then uses the default PSAP 200-206 per agreement with the service provider, assigns an ESLK, formats a SIP INVITE message with assigned ESLK and a default admin number for the service provider, and then sends an INVITE message back to the Intermediate VoIP switch 402. The INVITE message preferably includes “911” in the “To” field, and the assigned ESLK in the “From” field.
In step 9, a SIP 100 TRYING message is returned.
In step 10, the intermediate VoIP switch 402 reserves resources by using MGCP/MEGACO or TGCP at the TDM Gateway 100.
In step 11, an ISUP IAM message is sent to the appropriate PSAP 200-206.
In step 12, an emergency call is established.
In step 13, the appropriate PSAP 200-206 queries the location of the emergency caller by sending an ESPOSREQ with ESLK message(s).
In step 14, the VoIP Location Server 400 returns the caller's position to the appropriate PSAP 200-206 in an ESPOSREQ message.
In step 15, after sometime, the emergency call is terminated by the caller, and a SIP BYE message is sent.
In step 16, the Customer VoIP switch 404 of the service provider returns a 200 message.
In step 17, a SIP BYE message is transmitted to the Intermediate VoIP switch 402.
In step 18, a 200 message is returned.
In step 19, the Intermediate VoIP switch 402 sends a SIP BYE message to the VoIP Location Server 400.
In step 20, the VoIP Location Server 400 returns a SIP 200 message, and clears the call data and resources related to the call.
In step 21, the VoIP Location Server 400 sends a SIP BYE message to terminate the call leg to the Intermediate VoIP switch 402.
In step 22, a SIP 200 message is returned.
In step 23, an intermediate VoIP switch cleans up the resources at the TDM Gateway 100 using MGCP/MEGACO or TGCP.
In step 24, an ISUP REL message is sent.
In step 25, an ISUP RLC message is returned.
911 Location Service with Call Routing Via SIP Redirect Signaling
This section provides a more efficient solution to routing a 911 call initiated by a VoIP terminal 352. The basic concept is that the VoIP 911 Location Server 400 decides which PSAP 200-206 should be responsible for the 911 call based on the caller's location, and provides the routing information as an ESLK inside a SIP 300 response message back to the intermediate VoIP switch 402, which in turn routes the call to the correct PSAP 200-206. The VoIP 911 Location Server 400 will no longer stay in the call signaling path, and will be notified of the call termination event by a SIP NOTIFY message initiated by the Intermediate VoIP switch 402.
Note that, depending upon the implementation, the VoIP 911 Location Server 400 may need to send a SIP SUBSCRIBE message to the intermediate VoIP switch 402 as defined in IETF RFC3265. However, the intermediate VoIP switch 402 can also be implemented to always send a NOTIFY message to the 911 Location Server 400 once the 911 call is released, to simplify the signaling.
In particular, as shown in
In step 1, a SIP IP phone 352 initiates an emergency call by sending an SIP INVITE message, with 911,as its destination address, and its own id.
In step 2, the customer VoIP switch 404 of their service provider returns a SIP 100 TRYING message.
In step 3, the customer VoIP switch 404 of the service provider sends a SIP INVITE message, and routes the call to the intermediate VoIP switch 402 that connects with the VoIP Location Server 400.
In step 4, the Intermediate VoIP switch 402 responds with a SIP 100 TRYING message.
In step 5, the intermediate VoIP switch 402 forwards the SIP INVITE message to the VoIP Location Server 400.
In step 6, a SIP 100 TRYING message is returned.
In step 7, the VoIP Location Server 400 then converts the caller's address to latitude/longitude (if latitude/longitude are not retrieved from the switch) and determines the ESZ of the caller, assigns an ESLK, formats a SIP 300 message with assigned ESLK and a default admin number for the service provider, and then sends the message back to the Intermediate VoIP switch 402.
In step 8, a SIP ACK message is returned.
In step 9, the intermediate VoIP switch 402 reserves resources by using MGCP/MEGACO or TGCP at the TDM Gateway 100.
In step 10, an ISUP IAM message is sent to the appropriate PSAP 200-206.
In step 11, an emergency call is established.
In step 12, the appropriate PSAP 200-206 queries the location of the emergency caller by sending an ESPOSREQ with ESLK.
In step 13, the VoIP Location Server 400 returns the caller's position to the appropriate PSAP 200-206 in an ESPOSREQ message.
In step 14, after sometime, the emergency call is terminated by the caller, and a SIP BYE message is sent.
In step 15, the customer VoIP switch 404 of the service provider returns a 200 message.
In step 16, a SIP BYE message is sent to the intermediate VoIP switch 402.
In step 17, a 200 message is returned.
In step 18, the Intermediate VoIP 402 sends a SIP NOTIFY message with an indication of call termination to the VoIP Location Server 400.
In step 19, the VoIP Location Server 400 returns a SIP 200 message, and clears the call data and resources related to the establishment of the call.
In step 20, the intermediate VoIP switch 402 cleans up the resources at the TDM Gateway 100 using MGCP/MEGACO or TGCP.
In step 21, an ISUP REL message is sent.
In step 22, an ISUP RLC message is returned.
SIP INVITE message:
In particular, as shown in
In step 1, a SIP IP phone 352 initiates an emergency call by sending an SIP INVITE message, with 911 as its destination address and its own id.
In step 2, the customer VoIP switch 404 of the service provider returns a SIP 100 TRYING message.
In step 3, the customer VoIP switch 404 of the service provider sends a SIP INVITE message, and routes the call to the intermediate VoIP switch 402 that connects with the TCP Location Server 400.
In step 4, the Intermediate VoIP switch 402 responds with a SIP 100 TRYING message.
In step 5, the Intermediate VoIP switch 402 forwards the SIP INVITE message to the VoIP Location Server 400.
In step 6, a SIP 100 TRYING message is returned.
In step 7, given the failure scenario of the present embodiment for purposes of explanation, the VoIP Location Server 400 is not able to find the caller's address based on the calling party number, so it then assigns a default ESLK, formats a SIP 300 message with assigned ESLK and a default admin number for the service provider, and then sends the message back to the Intermediate VoIP switch 402.
In step 8, a SIP ACK message is returned.
In step 9, the intermediate VoIP switch 402 reserves resources by using MGCP/MEGACO or TGCP at the TDM Gateway 100.
In step 10, an ISUP IAM message is sent to the appropriate PSAP 200-206.
In step 11, an emergency call, is established.
In step 12, the appropriate PSAP 200-206 queries the location of the emergency caller by sending an ESPOSREQ with ESLK.
In step 13, the VoIP Location Server 400 returns the caller's position to the appropriate PSAP 200-206 in an ESPOSREQ message.
In step 14, after sometime, the emergency call is terminated by the caller, and a SIP BYE message is sent.
In step 15, the customer VoIP switch 404 of their service provider returns a 200 message.
In step 16, a SIP BYE message is sent to the Intermediate VoIP switch 402.
In step 17, a 200 message is returned.
In step 18, the Intermediate VoIP switch 402 sends a SIP NOTIFY message with an indication of, call termination to the VoIP Location Server 400.
In step 19, the VoIP Location Server 400 returns a SIP 200 message, and clears the call data and resources related to establishment of the call.
In step 20, the Intermediate VoIP switch 402 cleans up the resources at the TDM Gateway 100 using MGCP/MEGACO or TGCP.
In step 21, an ISUP REL message is sent.
In step 22, an ISUP RLC message is returned.
Mobility related to VoIP 911 location services is becoming increasingly important, particularly as more and more SIP based IP phones (VoIP phones) become convenient for carrying, and also as 802.11 based WiFi wireless data services provide better coverage,
Similar to 911 location services for wireless mobile telephony industry, it is proposed that PSAPs have the additional capability to request updated location information in the middle of the emergency call. The present invention envisions a solution to support a mid-call updated location request.
In accordance with the principles of the present invention, mid-call updated location requests can use standard SIP INFORMATION methodology (RFC 2976) to communicate with the VoIP terminal 352 that initiated a 911 call, to retrieve updated location information. Note that mid-call location updates as disclosed herein may be (and are in the disclosed embodiments) independent from actual positioning implemented or integrated in the VoIP terminal 352 itself. This provides a rather generic protocol mechanism to enable updated location retrieval during an emergency call.
In particular, as shown in
In step 1, an emergency call has been established between the VoIP terminal 352 and the appropriate PSAP 200-206, using any one of the call routing methods, e.g., as described herein above.
In step 2, the appropriate PSAP 200-206 queries the VoIP location server (VLS) 400 for an updated location of the emergency caller. As disclosed, the updated location information is obtained with the transmission of an ESPOSREQ with ESLK.
In step 3, the VoIP Location Server 400 checks its database, finds the record of the emergency call based on ESLK, and sends a SIP INFORMATION message indicating that updated location information is required to be transmitted to the intermediate VoIP switch 402.
In step 4, the intermediate VoIP switch 402 forwards the INFORMATION message to the customer VoIP switch 404.
In step 5, the customer VoIP switch 404 forwards the INFORMATION message to the VoIP terminal 352 that initiated the emergency call.
In step 6, upon receiving the INFORMATION message, depending on the specific capability that the particular calling VoIP terminal 352 has (e.g. AGPS may be integrated with the VoIP terminal 352), the VoIP terminal 352 performs appropriate procedures to generate the current location information. The VoIP terminal then sends updated location information, e.g., in a SIP 200 response message to the customer VoIP switch 404 provided by their service provider.
In step 7, the customer VoIP switch 404 forwards the SIP 200 response message to the intermediate VoIP switch 402.
In step 8, the intermediate VoIP switch 402 forwards the SIP 200 response message to the customer VoIP switch 404.
In step 9, the VoIP Location Server 400 returns the caller's updated position to the relevant PSAP 200-206, e.g., in an ESPOSREQ message.
911 Location Service with Call Routing Via Stateless SIP Proxy
This section provides a solution to route 911 call initiated by VoIP terminal. The basic concept is that the VoIP 911 Location Server decides which PSAP should be responsible for the 911 call based on the caller's location, and forwards the SIP call signaling message with the routing information as an ESLK to the intermediate switch, which in turn routes the call to the correct PSAP. The VoIP 911 Location Server stays in the call signaling path, until the call is terminated by either the caller or PSAP.
In particular, as shown in
In step 1, a SIP IP phone initiates an emergency call by sending an SIP INVITE message, with 911 as destination address and its own ID.
In step 2, the Softswitch of the service provider sends a SIP INVITE message and route the call to TCP Location Server.
In step 3, based on the information received in the INVITE message, VoIP Location Server retrieves the subscriber's location provided by Customer SIP S/W during Subscriber Location Provision/Validation procedure as illustrated in
In step 4, the Intermediate Softswitch responds with a SIP 100 TRYING.
In step 5, the VoIP Location Server forwards SIP 100 TRYING to the Customer SIP S/W.
In step 6, the Softswitch of service provider returns a SIP 100 TRYING.
In step 7, the intermediate softswitch reserves resource by using MGCP/MEGACO or TGCP at the TDM Gateway.
In step 8, an ISUP IAM is sent to the PSAP.
In step 9, an emergency call is established.
In step 10, the PSAP queries the location of the emergency caller by sending, for example, an ESP ESPOSREQ with ESLK.
In step 11, the VoIP Location Server returns the caller's position to the PSAP in an esposreq message.
In step 12, after sometime, the emergency call is terminated by the caller, a SIP BYE message is sent.
In step 13, the customer SIP S/W forwards SIP BYE message to VoIP Location Server.
In step 14, the customer SIP S/W returns a SIP 200 message.
In step 15, the VoIP Location Server forwards the SIP BYE to the Intermediate S/W.
In step 16, the intermediate S/W returns a SIP 200 message.
In step 17, the VoIP Location Server forwards SIP 200 message back to Customer SIP S/W.
In step 18, the intermediate SW cleans up the resource at TDM Gateway using MGCP/MEGACO or TGCP.
In step 19, an ISUP REL message is sent.
In step 20, an ISUP RLC message is returned.
Incoming SIP INVITE message:
In particular, as shown in
In step 1, a SIP IP phone initiates an emergency call by sending an SIP INVITE message, with 911 as destination address and its own ID.
In step 2, the Softswitch of the service provider sends a SIP INVITE message and route the call to TCP Location Server.
In step 3, based on the information received in the INVITE message, VoIP Location Server tries to retrieve the subscriber's location provided by Customer SIP S/W during Subscriber Location Provision/Validation procedure as illustrated in
In step 4, the intermediate Softswitch responds with a SIP 100 TRYING.
In step 5, the VoIP Location Server forwards SIP 100 TRYING to the Customer SIP S/W.
In step 6, the Softswitch of service provider returns a SIP 100 TRYING.
In step 7, the intermediate softswitch reserves resource by using MGCP/MEGACO or TGCP at the TDM Gateway.
In step 8, an ISUP IAM is sent to the PSAP.
9). Emergency call is established.
In step 10, the PSAP queries the location of the emergency caller by sending, for example, an ESP ESPOSREQ with ESLK.
In step 11, the VoIP Location Server returns the caller's position to the PSAP in an esposreq message.
In step 12, after sometime, the emergency call is terminated by the caller, a SIP BYE message is sent.
In step 13, the customer SIP S/W forwards SIP BYE message to VoIP Location Server.
In step 14, the customer SIP S/W returns a SIP 200 message.
In step 15, the VoIP Location Server forwards the SIP BYE to the Intermediate S/W.
In step 16, an intermediate S/W returns a SIP 200 message.
In step 17, the VoIP Location Server forwards SIP 200 message back to Customer SIP S/W.
In step 18, the intermediate SW cleans up the resource at TDM Gateway using MGCP/MEGACO or TGCP.
In step 19, an ISUP REL message is sent.
In step 20, an ISUP RLC message is returned.
The present invention enables automatic fallbacks to a location system by automatically performing a message tunneling feature to ensure that communication between the location service system and the target mobile is secure and uninterrupted as the mobile VoIP device 352 travels.
The disclosed embodiments may also comprise a VoIP E9-1-1 ALI Service—a capability which allows any fixed, portable, or mobile VoIP directory number to be correlated with current geographic coordinates and nearest street address as provided by a standard Automatic Line Identification (ALI) database.
The disclosed embodiments may further comprise a VoIP E9-1-1 ESLK Service—a Emergency Services Location Key (ESLK) capability which handles call routing management, ensuring that the originating location of the call will determine the subsequent routing of the emergency call to the closest PSAP.
Another feature of the disclosed embodiments is that they may include a VoIP E9-1-1 ALI Link Service—a capability which allows any VoIP Service Provider to interconnect to any existing PSAP connection currently supporting basic wireless E9-1-1 services (currently estimated to be greater than 65% of all existing PSAPs).
Also, a VoIP E9-1-1 VPC service may be implemented, wherein a Positioning Center supporting VoIP calls which will interact with a wide variety of VoIP switching infrastructure to pass the current known location information.
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.
This application claims priority from U.S. Provisional Appl. No. 60/555,305, entitled “Solutions For VoIP 911 Location Services” filed on Mar. 23, 2004 to Zhu, et al., and from U.S. application Ser. No. 10/739,292, entitled “Enhanced E911 Location Information Using Voice Over Internet Protocol (VoIP)” filed on Dec. 19, 2003 to Dickinson, et al., the entirety of both of which are explicitly incorporated herein by reference.
| Number | Date | Country | |
|---|---|---|---|
| 60555305 | Mar 2004 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 13775670 | Feb 2013 | US |
| Child | 14297216 | US | |
| Parent | 13064203 | Mar 2011 | US |
| Child | 13775670 | US | |
| Parent | 11819262 | Jun 2007 | US |
| Child | 13064203 | US | |
| Parent | 10836330 | May 2004 | US |
| Child | 11819262 | US | |
| Parent | 10739292 | Dec 2003 | US |
| Child | 10836330 | US |
