Solutions for voice over internet protocol (VoIP) 911 location services

0001This application is a continuation of U.S. application Ser. No. 11/819,262, entitled “Solutions for Voice Over Internet Protocol (VoIP) 911 Location Services” filed on Jun. 26, 2007 now U.S. Pat. No. 7,912,446 to Zhu, et al.; which in turn is a continuation of U.S. application Ser. No. 10/836,330, entitled “Solutions for Voice Over Internet Protocol (VoIP) 911 Location Services” filed on May 3, 2004 to Zhu, et al., now U.S. Pat. No. 7,260,186; which 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 is a continuation-in-part of 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., now U.S. Pat. No. 6,940,950, the entirety of all four of which are explicitly incorporated herein by reference.

BACKGROUND OF THE INVENTION

00021. Field of the Invention

0003This 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.

00042. Background of Related Art

0005911 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.

0006Some Public Safety Access Points (PSAPs) are not enhanced, and thus do not receive the callback or location information from any phone, landline or mobile.

0007Voice 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.

0008Voice 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.

0009As 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.

0010There are at least three VoIP scenarios that require E911 service: <ul id="ul0001" list-style="none"><li id="ul0001-0001" num="0000"><ul id="ul0002" list-style="none"><li id="ul0002-0001" num="0011">1. The VoIP device is physically connected to a static data cable at a “home” address.</li><li id="ul0002-0002" num="0012">2. The VoIP device is physically connected to a data cable at a location different than its “home” address. For instance, a laptop computer device utilized away from home as a VoIP communication device would be a VoIP ‘visitor’ device as described by this scenario.</li><li id="ul0002-0003" num="0013">3. The VoIP device is wireless, physically disconnected from any data cable. In this situation, the VoIP device connects to the VoIP network via cellular or WiFi technology.</li></ul></li></ul>

0014A 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.

0015Conventional 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.

0016Not 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.

0017This problem has been partially resolved as described in <figref idref="DRAWINGS">FIG. 12</figref>, which shows a conventional architecture for providing 911 service to a VoIP device.

0018In particular, as shown in <figref idref="DRAWINGS">FIG. 12</figref>, a conventional architecture routes VoIP 911 calls to a designated PSAP. However, such architecture fails to provide “enhanced” service for VoIP devices.

0019In particular, Option <b>1</b> in <figref idref="DRAWINGS">FIG. 12</figref> shows an IP device <b>250</b> utilizing VoIP protocols for voice communications dials 9-1-1. The VoIP device <b>250</b> is serviced by a VoIP switch <b>220</b> in the VoIP service provider's network. The VoIP switch <b>220</b> communicates with a Message Servicing Center (MSC) <b>230</b>. Using a database that relates the devices callback number or IP address to the owner's address, the MSC <b>230</b> can determine which PSAP has jurisdiction for that address. The MSC <b>230</b> then communicates back to the VoIP switch <b>220</b> a 10-digit telephone number for that PSAP. The VoIP Switch <b>220</b> then converts the IP call to TDM and routes the call to the designated PSAP using the provided 10-digit number.

0020A 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.

0021There 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.

SUMMARY OF THE INVENTION

0022In 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.

0023In 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.

BRIEF DESCRIPTION OF THE DRAWINGS

0024Features 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:

0025<figref idref="DRAWINGS">FIG. 1</figref> shows a block diagram of the architecture of a Voice Over Internet Protocol (VoIP) solution, in accordance with the principles of the present invention.

0026<figref idref="DRAWINGS">FIG. 2</figref> shows an overview of a Voice Over IP (VoIP) location service and network context diagram, in accordance with the principles of the present invention.

0027<figref idref="DRAWINGS">FIG. 3</figref> shows an exemplary message flow diagram for an exemplary VoIP subscriber location provisioning and validation procedure, in accordance with the principles of the present invention.

0028<figref idref="DRAWINGS">FIG. 4</figref> shows a scenario of an unsuccessful procedure for validating and provisioning a subscriber's location, in accordance with the principles of the present invention.

0029<figref idref="DRAWINGS">FIG. 5</figref> shows an exemplary message flow diagram for a 911 location service with call routing via SIP loopback signaling, in accordance with the principles of the present invention.

0030<figref idref="DRAWINGS">FIG. 6</figref> shows an abnormal scenario of a 911 location service with call routing via SIP redirect signaling, in accordance with the principles of the present invention.

0031<figref idref="DRAWINGS">FIG. 7</figref> shows an exemplary message flow diagram for a 911 location service with call routing via SIP redirect signaling, in accordance with another aspect of the present invention.

0032<figref idref="DRAWINGS">FIG. 8</figref> shows an exemplary abnormal scenario of a 911 location service with call routing via SIP redirect signaling, in accordance with the principles of the present invention.

0033<figref idref="DRAWINGS">FIG. 9</figref> shows another exemplary abnormal scenario of a 911 location service with call routing via SIP redirect signaling, in accordance with the principles of the present invention.

0034<figref idref="DRAWINGS">FIG. 10</figref> shows 911 Location Service with Call Routing via SIP Loopback Signaling, in accordance with another aspect of the present invention.

0035<figref idref="DRAWINGS">FIG. 11</figref> shows an abnormal Scenario of 911 Location Service with Call Routing via SIP Redirect Signaling, in accordance with another aspect of the present invention.

0036<figref idref="DRAWINGS">FIG. 12</figref> shows a conventional architecture for providing 911 service to a VoIP device which does not support CBN or ALI data delivery.

DETAILED DESCRIPTION OF ILLUSTRATIVE EMBODIMENTS

0037The present invention provides solutions covering different 911 location service aspects in support of Session Initiation Protocol (SIP) based VoIP 911 location services.

0038In 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.

0039The 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.

0040In 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.

0041<figref idref="DRAWINGS">FIG. 1</figref> shows a block diagram of the architecture of the VoIP solution, in accordance with the principles of the present invention. There are two additional options illustrated, in addition to the conventional option shown in <figref idref="DRAWINGS">FIG. 12</figref>. <ul id="ul0003" list-style="none"><li id="ul0003-0001" num="0000"><ul id="ul0004" list-style="none"><li id="ul0004-0001" num="0042">1. Option <b>2</b>: providing enhanced 911 service from IP devices located at “home” or at “visitor” locations, physically connected to the VoIP network via cable.</li><li id="ul0004-0002" num="0043">2. Option <b>3</b>: providing enhanced 911 service from mobile IP devices.</li></ul></li></ul>

0044In particular, as shown in <figref idref="DRAWINGS">FIG. 1</figref>, VoIP gateways <b>100</b> are implemented locally, e.g., one within each local access and transport area (LATA). The local VoIP gateways <b>100</b> accept VoIP packetized data inbound, and convert it to standard wireline voice calls. Calls are routed to an IP address at the VoIP gateway <b>100</b>, which then egresses the call to a voice port at a selective router. Suitable VoIP gateways <b>100</b> are otherwise conventionally known and commercially available.

0045Dedicated voice trunks <b>107</b>-<b>109</b> are installed between each local VoIP gateway <b>100</b> and appropriate selective routers <b>150</b><i>a</i>-<b>150</b><i>c </i>(referred to collectively herein as selective routers <b>150</b>). Examples of common voice trunks include Centralized Automatic Message Accounting (CAMA) trunks <b>107</b>, Signaling System #7 (SS7) voice trunks <b>108</b>, and/or FG-D trunks <b>109</b> are installed between each local VoIP gateway <b>100</b> and a respective group of selective routers <b>150</b>.

0046The selective routers <b>150</b> are provisioned as desired and otherwise conventionally known.

0047An Automatic Location Identification (ALI) database <b>190</b> is included, and is provisioned with Emergency Services Location Keys (ESLKs) dedicated for VoIP use as desired and otherwise conventionally known.

0048Transport Control Protocol/Internet Protocol (TCP/IP) data circuits may be installed between various local VoIP gateways <b>100</b>. For instance, additional IP circuits may be established between the local VoIP gateway(s) of other carriers to handle additional VoIP traffic.

0049The message flow resulting from a VoIP call from a given IP device, e.g., IP device <b>352</b>, is now described with reference to <figref idref="DRAWINGS">FIG. 1</figref>.

0050As a descriptive example, assume a VoIP “E911” call is being placed by VoIP device <b>352</b> as shown by “Option <b>2</b>” from the left side of <figref idref="DRAWINGS">FIG. 1</figref>. The following describes message flow to route that call directly to the correct PSAP, including the provision of location information of the VoIP device <b>352</b> to the correct PSAP.

0051In step <b>1</b>, a caller using the VoIP device <b>352</b> dials “911” on their VoIP device <b>352</b>. In the given example, the VoIP device <b>352</b> provides location information with the E911 call.

0052In step <b>2</b>, the VoIP switch <b>120</b><i>b </i>servicing that particular VoIP device <b>352</b> receives the E911 call, and queries the VoIP location server (VLS) <b>130</b><i>b </i>for routing information. The query to the VLS <b>130</b><i>b </i>includes a callback number, and location information (if mobile).

0053In step <b>3</b>, the MSC <b>130</b><i>b </i>relates location to specific PSAPs. If the location is static, the phone number and location will already be established in the MSC database <b>130</b><i>b</i>. If the VoIP device <b>352</b> 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.

0054In step <b>4</b>, upon determination of the appropriate PSAP to receive the E911 call, the MSC <b>130</b><i>b </i>responds with an Emergency Service Location Key (ESLK), plus IP routing instructions to the VoIP switch <b>120</b><i>b</i>. 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 <figref idref="DRAWINGS">FIG. 1</figref>, only the selective routers <b>150</b> compatible with one local VoIP gateway <b>100</b> are shown, as are PSAPs <b>200</b>-<b>206</b> having dedicated E911 trunks associated with each of those selective routers <b>150</b>. The person of skill in the art will understand from <figref idref="DRAWINGS">FIG. 1</figref> that similar local Gateway's will be implemented throughout a large area, e.g., across state lines or even countries, each having associated selective routers, and each selective router having one or more dedicated trunk line to a given one or more PSAPs.

0055The ESLK provided by the VLS <b>130</b><i>b </i>to the VoIP switch <b>120</b><i>b </i>is unique to the particular PSAP servicing the location that the mobile VoIP device <b>352</b> is calling from. The IP routing instructions provided by the VLS <b>130</b><i>b </i>to the VoIP switch <b>120</b><i>b </i>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 <b>100</b> shown in <figref idref="DRAWINGS">FIG. 1</figref>, or it might instead be another local VoIP gateway associated with another local area (e.g., another LATA).

0056In step <b>5</b>, the VoIP switch <b>120</b><i>b </i>routes the VoIP E911 call to the designated VoIP gateway <b>100</b>. The routed VoIP E911 call includes the ESLK.

0057In step <b>6</b>, the VoIP gateway <b>100</b> recognizes the ESLK, and selects a corresponding voice egress trunk (e.g., CAMA, SS7 or FG-D) <b>107</b>-<b>109</b>. The VoIP gateway <b>100</b> converts the VoIP data to voice, and egresses the E911 call to the proper selective router <b>150</b><i>a</i>, <b>150</b><i>b </i>or <b>150</b><i>c </i>on the selected trunk <b>107</b>-<b>109</b>.

0058In step <b>7</b>, as in otherwise conventional techniques, upon reaching the selective router <b>150</b><i>a</i>, <b>150</b><i>b </i>or <b>150</b><i>c</i>, the existing E911 infrastructure delivers the E911 call to the proper PSAP <b>200</b>, <b>202</b>, <b>204</b> or <b>206</b> that is assigned to the location that the mobile VoIP device <b>352</b> is calling from. Thus, the relevant selective router <b>150</b><i>a</i>, <b>150</b><i>b </i>or <b>150</b><i>c </i>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 <b>200</b>, <b>202</b>, <b>204</b> or <b>206</b>.

0059In step <b>8</b>, as in otherwise conventional techniques, the PSAP <b>200</b>, <b>202</b>, <b>204</b> or <b>206</b> receives the E911 voice call, and using the ESLK, queries the ALI database <b>190</b> for the location of the caller, and for call-back information.

0060The ALI database <b>190</b> steers the ESLK to the appropriate MSC <b>130</b><i>b</i>, 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.

0061The sequence of events for Option <b>1</b> would be similar as for the above described Option <b>2</b>, except that the location information would already be stored at the VLS and would not necessarily need to forwarded by the device.

0062Sequence of events for Option <b>3</b> (mobile IP device) would be as follows:

0063In step <b>1</b>, a caller using the mobile VoIP device <b>355</b> dials “911”.

0064In step <b>2</b>, the VoIP switch <b>120</b><i>b </i>servicing that particular VoIP device <b>352</b> receives the E911 call, and queries the VoIP location server (VLS) <b>130</b><i>b </i>for routing information. The query to the VLS <b>130</b><i>b </i>includes a callback number, but no location information.

0065In step <b>3</b>, the MSC <b>130</b><i>b </i>initiates a GPOSREQ to the Position Determining Equipment (PDE) <b>400</b> 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 <b>2</b> 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.

0066The PDE <b>400</b>, using otherwise conventional techniques, responds with a gposreq response that contains the latitude and longitude of the mobile IP device. The VLS <b>130</b><i>b </i>relates location to a specific PSAP.

0067Subsequent steps in Option <b>3</b> are similar to those described with respect to Option <b>2</b>.

0068Implementation 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.

0069<figref idref="DRAWINGS">FIG. 2</figref> is another depiction of an exemplary Voice Over IP (VoIP) location service and network context diagram, in accordance with the principles of the present invention.

0070In particular, <figref idref="DRAWINGS">FIG. 2</figref> provides an overview of the disclosed VoIP 911 Location Service, in which a VoIP Location Server <b>400</b> can either inter-connect with an intermediate VoIP Switch <b>402</b>, or directly inter-connect with a customer VoIP switch <b>404</b>, via standard Session Initiation Protocol (SIP) protocol. Subscriber Location Provisioning/Validation protocol is preferably simply HTTP based protocol to be used to “push” subscriber's location information stored in the Customer VoIP Switch network.

0071In operation, with reference to <figref idref="DRAWINGS">FIG. 2</figref>, a caller dials 911 via VoIP telephone <b>352</b>, and the call goes to the customer's VoIP switch <b>404</b>. For mobile VoIP devices <b>353</b> (e.g. a laptop), location information is provided to the VoIP switch <b>404</b> via data provided by the user at log-in. The customer's VoIP switch <b>404</b> routes the VoIP call to an intermediate (e.g., 3rd party) VoIP routing switch <b>402</b>.

0072The intermediate VoIP switch <b>402</b> 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.

0073Based upon the location of the caller, the VoIP 911 location server <b>400</b> determines the correct public safety access point (PSAP) <b>200</b>-<b>206</b> to which the 911 call should be directed. The VoIP location server <b>400</b> 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 <b>400</b> stages the ESLK, CBN, and location information. <ul id="ul0005" list-style="none"><li id="ul0005-0001" num="0000"><ul id="ul0006" list-style="none"><li id="ul0006-0001" num="0074">1) The VoIP 911 Location Server provides IP routing information to the VoIP switch <b>402</b>.</li><li id="ul0006-0002" num="0075">2) The VoIP switch <b>402</b> routes the VoIP call via IP to the intended local VoIP gateway.</li><li id="ul0006-0003" num="0076">3) The VoIP gateway <b>100</b> interprets the ESLK, converts the VoIP call to CAMA or SS7 as required, and egresses the call to the correct selective router <b>150</b>.</li><li id="ul0006-0004" num="0077">4) The call progresses to the PSAP <b>200</b>-<b>206</b> per existing technology.</li><li id="ul0006-0005" num="0078">5) The PSAP <b>200</b>-<b>206</b> queries the ALI <b>190</b>. Existing steering instructions route the call to the VoIP Location Server ALI Link via PAM or E2</li><li id="ul0006-0006" num="0079">6) VoIP Location Server <b>400</b> responds with location information. <br /> Provisioning and Validation of VoIP Subscriber Location </li></ul></li></ul>

0080One 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 <b>404</b>. During this process, the subscriber's location information can be recorded in the customer VoIP switch <b>404</b>.

0081However, conventionally there is an issue regarding how the location information can be used by the VoIP Location Server <b>400</b>. 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 <b>307</b> of a local VoIP service provider can push the subscriber location information to the VoIP Location Server.

0082<figref idref="DRAWINGS">FIG. 3</figref> shows an exemplary message flow diagram for an exemplary VoIP subscriber location provisioning and validation procedure, in accordance with the principles of the present invention.

0083In particular, as shown in <figref idref="DRAWINGS">FIG. 3</figref>, a Sub_Location_Validation_Req message requesting address and/or longitude/latitude information about the caller, is transmitted from the CP office <b>307</b> to the VoIP location server <b>400</b>. The transmitted Sub_Location_Validation_Req message preferably includes the following information:

0084A flag indicating action: Add/Update or Delete

0085VoIP Provider's Name (preferably required)

0086Customer Name (preferably optional);

0087Customer VoIP telephone number (preferably required);

0088Street address of the IP device preferably includes: <ul id="ul0007" list-style="none"><li id="ul0007-0001" num="0000"><ul id="ul0008" list-style="none"><li id="ul0008-0001" num="0089">Street number (preferably required. Provisions should be made for street addresses that do not use a street number);</li><li id="ul0008-0002" num="0090">Street Name (preferably required);</li><li id="ul0008-0003" num="0091">Street Directional (preferably required if applicable);</li><li id="ul0008-0004" num="0092">Apartment # (preferably required if applicable);</li><li id="ul0008-0005" num="0093">Room # (preferably required if applicable);</li><li id="ul0008-0006" num="0094">Community Name (preferably required);</li><li id="ul0008-0007" num="0095">State (preferably required);</li><li id="ul0008-0008" num="0096">Zip code (preferably optional);</li><li id="ul0008-0009" num="0097">Position information in WGS84 format (preferably optional);</li><li id="ul0008-0010" num="0098">Position Source (preferably optional);</li><li id="ul0008-0011" num="0099">Terminal Type (preferably optional);</li><li id="ul0008-0012" num="0100">Terminal Capability (preferably optional)</li><li id="ul0008-0013" num="0101">Supplemental Field #<b>1</b> (preferably optional);</li><li id="ul0008-0014" num="0102">Supplemental Field #<b>2</b> (preferably optional);</li><li id="ul0008-0015" num="0103">Supplemental Field #<b>3</b> (preferably optional);</li><li id="ul0008-0016" num="0104">Supplemental Field #<b>4</b> (preferably optional);</li></ul></li></ul>

0105latitude/longitude (preferably optional)

0106Upon receiving the location information, the VoIP Location Server <b>400</b> validates the location information with a geographic location database to see that the address is valid. If it is, then the VoIP location server <b>400</b> converts the location information received to latitude/longitude type information and stores the same in its subscriber database <b>401</b>.

0107A Sub_Location_Validation_Res (or Sub_Location_Validation_Ack) message containing an indication of positive acknowledgement is passed from the VoIP location server <b>400</b> back to the CP Office <b>307</b>.

0108<figref idref="DRAWINGS">FIG. 4</figref> shows a scenario of an unsuccessful procedure for validating and provisioning a subscriber's location, in accordance with the principles of the present invention.

0109In particular, as shown in <figref idref="DRAWINGS">FIG. 4</figref>, a Sub_Location_Validation_Req( ) request message is passed from the customer VoIP switch <b>404</b> to the VoIP location server <b>400</b>. The transmitted Sub_Location_Validation_Req message may include the same information as explained with reference to <figref idref="DRAWINGS">FIG. 3</figref>.

0110Upon receiving the location information, the VoIP Location Server <b>400</b> 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 <b>400</b> may return one of the following exemplary errors: “Record not found”, or “Not in the service coverage”, or similar.

0000911 Location Service with Call Routing Via SIP Loopback Signaling

0111This 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 <b>400</b> decides which PSAP <b>200</b>-<b>206</b> 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 <b>402</b>, which in turn routes the call to the correct PSAP <b>200</b>-<b>206</b>. The VoIP 911 Location Server <b>400</b> stays in the call signaling path, until the call is terminated by either the caller or the appropriate PSAP <b>200</b>-<b>206</b>.

0112<figref idref="DRAWINGS">FIG. 5</figref> shows an exemplary message flow diagram for a 911 location service with call routing via SIP loopback signaling, in accordance with the principles of the present invention.

0113In particular, as shown in <figref idref="DRAWINGS">FIG. 5</figref>:

0114In step <b>1</b>, a SIP IP phone initiates an emergency call by sending an SIP INVITE message to the customer's VoIP switch <b>404</b>, with 911 as destination address and its own id.

0115In step <b>2</b>, the customer VoIP switch <b>404</b> of the service provider returns a SIP 100 TRYING message to the SIP VoIP phone <b>352</b>.

0116In step <b>3</b>, the customer VoIP switch <b>404</b> of the service provider sends a SIP INVITE message to the intermediate VoIP switch <b>402</b>, and routes the call to the intermediate VoIP switch <b>402</b> that connects with the VoIP Location Server <b>400</b>.

0117In step <b>4</b>, the intermediate VoIP switch <b>402</b> responds with a SIP 100 TRYING message.

0118In step <b>5</b>, the intermediate VoIP switch <b>402</b> forwards the received SIP INVITE message to the VoIP Location Server <b>400</b>.

0119In step <b>6</b>, a SIP 100 TRYING message is returned from the VoIP location server <b>400</b> to the intermediate VoIP switch <b>402</b>.

0120In step <b>7</b>, based on information received in the INVITE message, the VoIP Location Server <b>400</b> 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.

0121In step <b>8</b>, the VoIP Location Server <b>400</b> 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 <b>402</b>. The INVITE message may include “911” in the “To” field, and the assigned ESLK in the “From” field.

0122In step <b>9</b>, a SIP 100 TRYING message is returned from the VoIP location server <b>400</b> to the intermediate VoIP switch <b>402</b>.

0123In step <b>10</b>, the intermediate VoIP switch <b>402</b> reserves resources by using MGCP/MEGACO or TGCP at the TDM Gateway.

0124In step <b>11</b>, an ISUP IAM message is sent to the appropriate PSAP <b>200</b>-<b>206</b>.

0125In step <b>12</b>, an emergency call is established.

0126In step <b>13</b>, the appropriate PSAP <b>200</b>-<b>206</b> queries the location of the emergency caller by sending an ESPOSREQ with ESLK.

0127In step <b>14</b>, the VoIP Location Server <b>400</b> returns the caller's position to the appropriate PSAP <b>200</b>-<b>206</b> in an esposreq message.

0128In step <b>15</b>, after sometime, the emergency call is terminated by the caller, and a SIP BYE message is transmitted.

0129In step <b>16</b>, the customer's VoIP switch <b>404</b> returns a “200” message to the VoIP SIP phone <b>352</b>.

0130In step <b>17</b>, a SIP BYE message is sent to the intermediate VoIP switch <b>402</b>.

0131In step <b>18</b>, a “200” message is returned from the intermediate VoIP switch <b>402</b> to the customer VoIP switch <b>404</b>.

0132In step <b>19</b>, the intermediate VoIP switch <b>402</b> transmits a SIP BYE message to the VoIP Location Server <b>400</b>.

0133In step <b>20</b>, the VoIP Location Server <b>400</b> returns a SIP 200 message to the intermediate VoIP server <b>402</b>, and clears the call data and resources related to the call.

0134In step <b>21</b>, the VoIP Location Server <b>400</b> sends a SIP BYE message to the intermediate VoIP switch <b>402</b> to terminate the call leg to the Intermediate VoIP switch <b>402</b>.

0135In step <b>22</b>, the intermediate VoIP switch <b>402</b> returns a SIP 200 message to the VoIP location server <b>400</b>.

0136In step <b>23</b>, the intermediate VoIP switch <b>402</b> cleans up the resources at the TDM Gateway <b>100</b> using MGCP/MEGACO or TGCP.

0137In step <b>24</b>, an ISUP REL message is transmitted from the intermediate VoIP switch <b>402</b> to the appropriate PSAP <b>200</b>-<b>206</b>.

0138In step <b>25</b>, an ISUP RLC message is returned by the appropriate PSAP <b>200</b>-<b>206</b> to the intermediate VoIP switch <b>402</b>.

0000Examples of SIP Messages:

0000Incoming SIP INVITE Message:

0139INVITE tel: 911 SIP/2.0

0140Via: SIP/2.0/UDP pc33.atlanta.com;branch=z9hG4bK776asdhds

0141Max-Forwards: 10

0142To: EME <tel: 911>

0143From: Alice <tel: 5551234567>;tag=1928301774

0144Call-ID: a84b4c76e66710@pc33.atlanta.com

0145CSeq: 314159 INVITE

0146Contact: <tel: 5551234567>

0147Content-Type: application/sdp

0148Content-Length: nnn

0000Outgoing SIP INVITE Message:

0149INVITE tel: 911 SIP/2.0

0150Via: SIP/2.0/UDP VoIPMPC.VoIP.com;branch=zkljioyuwe235kljll

0151Via: SIP/2.0/UDP pc33.atlanta.com;branch=z9hG4bK776asdhds

0152Max-Forwards: 9

0153To: EME <tel: 911>

0154From: Alice <tel: 2061234567>;tag=1928301774

0155Call-ID: a84b4c76e66710@pc33.atlanta.com

0156CSeq: 314159 INVITE

0157Contact: <tel: 2061234567>

0158Contact: <tel: 2063456789>

0159Content-Type: application/sdp

0160Content-Length: nnn

0000Notes:

01611) Assigned ESLK is +1-206-1234567;

01622) Admin number is +1-206-3456789;

0000Outgoing ISUP IAM Message:

0163Called party number: 911

0164Calling party number: 2061234567 (ESLK)

0165Charge Number: 2061234567 (ESLK)

0166Generic digits parameter: n/a

0167Calling geodetic location: n/a

0168Originating Line Information (OLI): If included, use value 00 (POTS)

0169<figref idref="DRAWINGS">FIG. 6</figref> shows an abnormal scenario of a 911 location service with call routing via SIP redirect signaling, in accordance with the principles of the present invention.

0170In particular, as shown in <figref idref="DRAWINGS">FIG. 6</figref>:

0171In step <b>1</b>, a SIP IP phone <b>352</b> initiates an emergency call by sending an SIP INVITE message, with 911 as the destination address, and its own id.

0172In step <b>2</b>, the customer's VoIP switch <b>404</b> of the service provider returns a SIP 100 TRYING message.

0173In step <b>3</b>, the customer's VoIP switch <b>404</b> sends a SIP INVITE message and routes the call to the intermediate VoIP switch <b>402</b> that connects with the TCP Location Server <b>400</b>.

0174In step <b>4</b>, the intermediate VoIP switch <b>402</b> responds with a SIP 100 TRYING message.

0175In step <b>5</b>, the intermediate VoIP switch <b>402</b> forwards the SIP INVITE message to the VoIP Location Server <b>400</b>.

0176In step <b>6</b>, a SIP 100 TRYING message is returned.

0177In step <b>7</b>, based on information received in the INVITE message, the VoIP Location Server <b>400</b> 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.

0178However, in this scenario, the procedure fails, or there is not a match in the database of the VoIP Location Server <b>400</b> with respect to the retrieve location.

0179In step <b>8</b>, the VoIP Location Server <b>400</b> then uses the default PSAP <b>200</b>-<b>206</b> 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 <b>402</b>. The INVITE message preferably includes “911” in the “To” field, and the assigned ESLK in the “From” field.

0180In step <b>9</b>, a SIP 100 TRYING message is returned.

0181In step <b>10</b>, the intermediate VoIP switch <b>402</b> reserves resources by using MGCP/MEGACO or TGCP at the TDM Gateway <b>100</b>.

0182In step <b>11</b>, an ISUP IAM message is sent to the appropriate PSAP <b>200</b>-<b>206</b>.

0183In step <b>12</b>, an emergency call is established.

0184In step <b>13</b>, the appropriate PSAP <b>200</b>-<b>206</b> queries the location of the emergency caller by sending an ESPOSREQ with ESLK message(s).

0185In step <b>14</b>, the VoIP Location Server <b>400</b> returns the caller's position to the appropriate PSAP <b>200</b>-<b>206</b> in an ESPOSREQ message.

0186In step <b>15</b>, after sometime, the emergency call is terminated by the caller, and a SIP BYE message is sent.

0187In step <b>16</b>, the Customer VoIP switch <b>404</b> of the service provider returns a 200 message.

0188In step <b>17</b>, a SIP BYE message is transmitted to the Intermediate VoIP switch <b>402</b>.

0189In step <b>18</b>, a 200 message is returned.

0190In step <b>19</b>, the Intermediate VoIP switch <b>402</b> sends a SIP BYE message to the VoIP Location Server <b>400</b>.

0191In step <b>20</b>, the VoIP Location Server <b>400</b> returns a SIP 200 message, and clears the call data and resources related to the call.

0192In step <b>21</b>, the VoIP Location Server <b>400</b> sends a SIP BYE message to terminate the call leg to the Intermediate VoIP switch <b>402</b>.

0193In step <b>22</b>, a SIP 200 message is returned.

0194In step <b>23</b>, an intermediate VoIP switch cleans up the resources at the TDM Gateway <b>100</b> using MGCP/MEGACO or TGCP.

0195In step <b>24</b>, an ISUP REL message is sent.

0196In step <b>25</b>, an ISUP RLC message is returned.

0000911 Location Service with Call Routing Via SIP Redirect Signaling

0197This section provides a more efficient solution to routing a 911 call initiated by a VoIP terminal <b>352</b>. The basic concept is that the VoIP 911 Location Server <b>400</b> decides which PSAP <b>200</b>-<b>206</b> 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 <b>402</b>, which in turn routes the call to the correct PSAP <b>200</b>-<b>206</b>. The VoIP 911 Location Server <b>400</b> 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 <b>402</b>.

0198Note that, depending upon the implementation, the VoIP 911 Location Server <b>400</b> may need to send a SIP SUBSCRIBE message to the intermediate VoIP switch <b>402</b> as defined in IETF RFC3265. However, the intermediate VoIP switch <b>402</b> can also be implemented to always send a NOTIFY message to the 911 Location Server <b>400</b> once the 911 call is released, to simplify the signaling.

0199<figref idref="DRAWINGS">FIG. 7</figref> shows an exemplary message flow diagram for a 911 location service with call routing via SIP redirect signaling, in accordance with another aspect of the present invention.

0200In particular, as shown in <figref idref="DRAWINGS">FIG. 7</figref>:

0201In step <b>1</b>, a SIP IP phone <b>352</b> initiates an emergency call by sending an SIP INVITE message, with 911 as its destination address, and its own id.

0202In step <b>2</b>, the customer VoIP switch <b>404</b> of their service provider returns a SIP 100 TRYING message.

0203In step <b>3</b>, the customer VoIP switch <b>404</b> of the service provider sends a SIP INVITE message, and routes the call to the intermediate VoIP switch <b>402</b> that connects with the VoIP Location Server <b>400</b>.

0204In step <b>4</b>, the Intermediate VoIP switch <b>402</b> responds with a SIP 100 TRYING message.

0205In step <b>5</b>, the intermediate VoIP switch <b>402</b> forwards the SIP INVITE message to the VoIP Location Server <b>400</b>.

0206In step <b>6</b>, a SIP 100 TRYING message is returned.

0207In step <b>7</b>, the VoIP Location Server <b>400</b> 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 <b>402</b>.

0208In step <b>8</b>, a SIP ACK message is returned.

0209In step <b>9</b>, the intermediate VoIP switch <b>402</b> reserves resources by using MGCP/MEGACO or TGCP at the TDM Gateway <b>100</b>.

0210In step <b>10</b>, an ISUP IAM message is sent to the appropriate PSAP <b>200</b>-<b>206</b>.

0211In step <b>11</b>, an emergency call is established.

0212In step <b>12</b>, the appropriate PSAP <b>200</b>-<b>206</b> queries the location of the emergency caller by sending an ESPOSREQ with ESLK.

0213In step <b>13</b>, the VoIP Location Server <b>400</b> returns the caller's position to the appropriate PSAP <b>200</b>-<b>206</b> in an ESPOSREQ message.

0214In step <b>14</b>, after sometime, the emergency call is terminated by the caller, and a SIP BYE message is sent.

0215In step <b>15</b>, the customer VoIP switch <b>404</b> of the service provider returns a 200 message.

0216In step <b>16</b>, a SIP BYE message is sent to the intermediate VoIP switch <b>402</b>.

0217In step <b>17</b>, a 200 message is returned.

0218In step <b>18</b>, the Intermediate VoIP <b>402</b> sends a SIP NOTIFY message with an indication of call termination to the VoIP Location Server <b>400</b>.

0219In step <b>19</b>, the VoIP Location Server <b>400</b> returns a SIP 200 message, and clears the call data and resources related to the establishment of the call.

0220In step <b>20</b>, the intermediate VoIP switch <b>402</b> cleans up the resources at the TDM Gateway <b>100</b> using MGCP/MEGACO or TGCP.

0221In step <b>21</b>, an ISUP REL message is sent.

0222In step <b>22</b>, an ISUP RLC message is returned.

0000Examples of SIP Messages:

0000SIP INVITE Message:

0223INVITE sip:911@commpartners.com SIP/2.0

0224Via: SIP/2.0/UDP pc33.atlanta.com;branch=z9hG4bK776asdhds

0225Max-Forwards: 10

0226To: EME <sip:911@commpartners.com>

0227From: Alice <sip:5551234567@commpartners.com>;tag=1928301774

0228Call-ID: a84b4c76e66710@pc33.atlanta.com

0229CSeq: 314159 INVITE

0230Contact: <sip:5551234567@commpartners.com>

0231Content-Type: application/sdp

0232Content-Length: nnn

0000Outgoing SIP 300 Response with ESLK:

0233SIP/2.0 300 Multiple Choices

0234Via: SIP/2.0/UDP VoIPMPC.VoIP.com;branch=zkljioyuwe235kljll

0235Via: SIP/2.0/UDP pc33.atlanta.com;branch=z9hG4bK776asdhds

0236Max-Forwards: 9

0237To: EME <sip:911@commpartners.com>

0238From: Alice <sip:2061234567@commpartners.com>;tag=1928301774

0239Call-ID: a84b4c76e66710@pc33.atlanta.com

0240CSeq: 314159 INVITE

0241Contact: <sip:2061234567@commpartners.com>

0242Contact: <sip:2063456789@commpartners.com>

0243Content-Type: application/sdp

0244Content-Length: nnn

0000Notes:

02451) Assigned ESLK is +1-206-1234567;

02462) Admin number is +1-206-3456789;

0000ISUP IAM Message:

0247Called party number: 911

0248Calling party number: 2061234567 (ESLK)

0249Charge Number: 2061234567 (ESLK)

0250Generic digits parameter: n/a

0251Calling geodetic location: n/a

0252Originating Line Information (OLI): If included, use value 00 (POTS)

0253<figref idref="DRAWINGS">FIG. 8</figref> shows an exemplary abnormal scenario of a 911 location service with call routing via SIP redirect signaling, in accordance with the principles of the present invention.

0254In particular, as shown in <figref idref="DRAWINGS">FIG. 8</figref>:

0255In step <b>1</b>, a SIP IP phone <b>352</b> initiates an emergency call by sending an SIP INVITE message, with 911 as its destination address and its own id.

0256In step <b>2</b>, the customer VoIP switch <b>404</b> of the service provider returns a SIP 100 TRYING message.

0257In step <b>3</b>, the customer VoIP switch <b>404</b> of the service provider sends a SIP INVITE message, and routes the call to the intermediate VoIP switch <b>402</b> that connects with the TCP Location Server <b>400</b>.

0258In step <b>4</b>, the Intermediate VoIP switch <b>402</b> responds with a SIP 100 TRYING message.

0259In step <b>5</b>, the Intermediate VoIP switch <b>402</b> forwards the SIP INVITE message to the VoIP Location Server <b>400</b>.

0260In step <b>6</b>, a SIP 100 TRYING message is returned.

0261In step <b>7</b>, given the failure scenario of the present embodiment for purposes of explanation, the VoIP Location Server <b>400</b> 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 <b>402</b>.

0262In step <b>8</b>, a SIP ACK message is returned.

0263In step <b>9</b>, the intermediate VoIP switch <b>402</b> reserves resources by using MGCP/MEGACO or TGCP at the TDM Gateway <b>100</b>.

0264In step <b>10</b>, an ISUP IAM message is sent to the appropriate PSAP <b>200</b>-<b>206</b>.

0265In step <b>11</b>, an emergency call is established.

0266In step <b>12</b>, the appropriate PSAP <b>200</b>-<b>206</b> queries the location of the emergency caller by sending an ESPOSREQ with ESLK.

0267In step <b>13</b>, the VoIP Location Server <b>400</b> returns the caller's position to the appropriate PSAP <b>200</b>-<b>206</b> in an ESPOSREQ message.

0268In step <b>14</b>, after sometime, the emergency call is terminated by the caller, and a SIP BYE message is sent.

0269In step <b>15</b>, the customer VoIP switch <b>404</b> of their service provider returns a 200 message.

0270In step <b>16</b>, a SIP BYE message is sent to the Intermediate VoIP switch <b>402</b>.

0271In step <b>17</b>, a 200 message is returned.

0272In step <b>18</b>, the Intermediate VoIP switch <b>402</b> sends a SIP NOTIFY message with an indication of call termination to the VoIP Location Server <b>400</b>.

0273In step <b>19</b>, the VoIP Location Server <b>400</b> returns a SIP 200 message, and clears the call data and resources related to establishment of the call.

0274In step <b>20</b>, the Intermediate VoIP switch <b>402</b> cleans up the resources at the TDM Gateway <b>100</b> using MGCP/MEGACO or TGCP.

0275In step <b>21</b>, an ISUP REL message is sent.

0276In step <b>22</b>, an ISUP RLC message is returned.

0000Mid-Call Updated Location Services for VoIP Mobility

0277Mobility 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,

0278Similar 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.

0279In 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 <b>352</b> 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 <b>352</b> itself. This provides a rather generic protocol mechanism to enable updated location retrieval during an emergency call.

0280<figref idref="DRAWINGS">FIG. 9</figref> shows another exemplary abnormal scenario of a 911 location service with call routing via SIP redirect signaling, in accordance with the principles of the present invention.

0281In particular, as shown in <figref idref="DRAWINGS">FIG. 9</figref>:

0282In step <b>1</b>, an emergency call has been established between the VoIP terminal <b>352</b> and the appropriate PSAP <b>200</b>-<b>206</b>, using any one of the call routing methods, e.g., as described herein above.

0283In step <b>2</b>, the appropriate PSAP <b>200</b>-<b>206</b> queries the VoIP location server (VLS) <b>400</b> for an updated location of the emergency caller. As disclosed, the updated location information is obtained with the transmission of an ESPOSREQ with ESLK.

0284In step <b>3</b>, the VoIP Location Server <b>400</b> 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 <b>402</b>.

0285In step <b>4</b>, the intermediate VoIP switch <b>402</b> forwards the INFORMATION message to the customer VoIP switch <b>404</b>.

0286In step <b>5</b>, the customer VoIP switch <b>404</b> forwards the INFORMATION message to the VoIP terminal <b>352</b> that initiated the emergency call.

0287In step <b>6</b>, upon receiving the INFORMATION message, depending on the specific capability that the particular calling VoIP terminal <b>352</b> has (e.g. AGPS may be integrated with the VoIP terminal <b>352</b>), the VoIP terminal <b>352</b> 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 <b>404</b> provided by their service provider.

0288In step <b>7</b>, the customer VoIP switch <b>404</b> forwards the SIP 200 response message to the intermediate VoIP switch <b>402</b>.

0289In step <b>8</b>, the intermediate VoIP switch <b>402</b> forwards the SIP 200 response message to the customer VoIP switch <b>404</b>.

0290In step <b>9</b>, the VoIP Location Server <b>400</b> returns the caller's updated position to the relevant PSAP <b>200</b>-<b>206</b>, e.g., in an ESPOSREQ message.

0000911 Location Service with Call Routing Via Stateless SIP Proxy

0291This 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.

0292<figref idref="DRAWINGS">FIG. 10</figref> shows 911 Location Service with Call Routing via SIP Loopback Signaling, in accordance with another aspect of the present invention.

0293In particular, as shown in <figref idref="DRAWINGS">FIG. 10</figref>:

0294In step <b>1</b>, a SIP IP phone initiates an emergency call by sending an SIP INVITE message, with 911 as destination address and its own ID.

0295In step <b>2</b>, the Softswitch of the service provider sends a SIP INVITE message and route the call to TCP Location Server.

0296In step <b>3</b>, 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 <figref idref="DRAWINGS">FIG. 3</figref>. Then VoIP Location Server converts the caller's address to lat/lon (if lat/lon are not retrieved from the SW) and determines the ESZ of the caller, assigns an ESLK, formats a SIP INVITE message with assigned ESLK and a default admin number for the service provider, and then sends INVITE message back to the Intermediate softswitch. The INVITE message includes “911” in “To”, and the assigned ESLK in “From” (see details in next Page).

0297In step <b>4</b>, the Intermediate Softswitch responds with a SIP 100 TRYING.

0298In step <b>5</b>, the VoIP Location Server forwards SIP 100 TRYING to the Customer SIP S/W.

0299In step <b>6</b>, the Softswitch of service provider returns a SIP 100 TRYING.

0300In step <b>7</b>, the intermediate softswitch reserves resource by using MGCP/MEGACO or TGCP at the TDM Gateway.

0301In step <b>8</b>, an ISUP IAM is sent to the PSAP.

0302In step <b>9</b>, an emergency call is established.

0303In step <b>10</b>, the PSAP queries the location of the emergency caller by sending, for example, an ESP ESPOSREQ with ESLK.

0304In step <b>11</b>, the VoIP Location Server returns the caller's position to the PSAP in an esposreq message.

0305In step <b>12</b>, after sometime, the emergency call is terminated by the caller, a SIP BYE message is sent.

0306In step <b>13</b>, the customer SIP S/W forwards SIP BYE message to VoIP Location Server.

0307In step <b>14</b>, the customer SIP S/W returns a SIP 200 message.

0308In step <b>15</b>, the VoIP Location Server forwards the SIP BYE to the Intermediate S/W.

0309In step <b>16</b>, the intermediate S/W returns a SIP 200 message.

0310In step <b>17</b>, the VoIP Location Server forwards SIP 200 message back to Customer SIP S/W.

0311In step <b>18</b>, the intermediate SW cleans up the resource at TDM Gateway using MGCP/MEGACO or TGCP.

0312In step <b>19</b>, an ISUP REL message is sent.

0313In step <b>20</b>, an ISUP RLC message is returned.

0000Example of SIP Messages:

0000Incoming SIP INVITE Message:

0314INVITE tel: 911 SIP/2.0

0315Via: SIP/2.0/UDP pc33.atlanta.com;branch=z9hG4bK776asdhds

0316Max-Forwards: 10

0317To: EME <tel: 911>

0318From: Alice <tel: 5551234567>;tag=1928301774

0319Call-ID: a84b4c76e66710@pc33.atlanta.com

0320CSeq: 314159 INVITE

0321Contact: <tel: 5551234567>

0322Content-Type: application/sdp

0323Content-Length: nnn

0000Outgoing SIP INVITE Message:

0324INVITE tel: 911 SIP/2.0

0325Via: SIP/2.0/UDP VoIPMPC.VoIP.com;branch=zkljioyuwe235kljll

0326Via: SIP/2.0/UDP pc33.atlanta.com;branch=z9hG4bK776asdhds

0327Max-Forwards: 9

0328To: EME <tel: 911>

0329From: Alice <tel: 2061234567>; tag=1928301774

0330Call-ID: a84b4c76e66710@pc33.atlanta.com

0331CSeq: 314159 INVITE

0332Contact: <tel: 2061234567>

0333Contact: <tel: 2063456789>

0334Content-Type: application/sdp

0335Content-Length: nnn

0000Notes:

03361) Assigned ESLK is +1-206-1234567;

03372) Admin number is +1-206-3456789;

0000Outgoing ISUP IAM Message:

0338Called party number: 911

0339Calling party number: 2061234567 (ESLK)

0340Charge Number: 2061234567 (ESLK)

0341Generic digits parameter: n/a

0342Calling geodetic location: n/a

0343Originating Line Information (OLI): If included, use value 00 (POTS)

0344<figref idref="DRAWINGS">FIG. 11</figref> shows an abnormal Scenario of 911 Location Service with Call Routing via SIP Redirect Signaling, in accordance with another aspect of the present invention.

0345In particular, as shown in <figref idref="DRAWINGS">FIG. 11</figref>:

0346In step <b>1</b>, a SIP IP phone initiates an emergency call by sending an SIP INVITE message, with 911 as destination address and its own ID.

0347In step <b>2</b>, the Softswitch of the service provider sends a SIP INVITE message and route the call to TCP Location Server.

0348In step <b>3</b>, based on the information received in the INVITE message, VoIP Location Server tries to retrieve the subscriber's location provided by Customer SIP SAN during Subscriber Location Provision/Validation procedure as illustrated in <figref idref="DRAWINGS">FIG. 3</figref>, however, no location info is found. Then VoIP Location Server uses a default location and ESZ for the VoIP provider, assigns an ESLK, formats a SIP INVITE message with assigned ESLK and a default admin number for the service provider, and then sends INVITE message back to the Intermediate softswitch. The INVITE message includes “911” in “To”, and the assigned ESLK in “From” (see details in next Page).

0349In step <b>4</b>, the intermediate Softswitch responds with a SIP 100 TRYING.

0350In step <b>5</b>, the VoIP Location Server forwards SIP 100 TRYING to the Customer SIP S/W.

0351In step <b>6</b>, the Softswitch of service provider returns a SIP 100 TRYING.

0352In step <b>7</b>, the intermediate softswitch reserves resource by using MGCP/MEGACO or TGCP at the TDM Gateway.

0353In step <b>8</b>, an ISUP IAM is sent to the PSAP.

00009). Emergency Call is Established.

0354In step <b>10</b>, the PSAP queries the location of the emergency caller by sending, for example, an ESP ESPOSREQ with ESLK.

0355In step <b>11</b>, the VoIP Location Server returns the caller's position to the PSAP in an esposreq message.

0356In step <b>12</b>, after sometime, the emergency call is terminated by the caller, a SIP BYE message is sent.

0357In step <b>13</b>, the customer SIP S/W forwards SIP BYE message to VoIP Location Server.

0358In step <b>14</b>, the customer SIP S/W returns a SIP 200 message.

0359In step <b>15</b>, the VoIP Location Server forwards the SIP BYE to the Intermediate S/W.

0360In step <b>16</b>, an intermediate S/W returns a SIP 200 message.

0361In step <b>17</b>, the VoIP Location Server forwards SIP 200 message back to Customer SIP S/W.

0362In step <b>18</b>, the intermediate SW cleans up the resource at TDM Gateway using MGCP/MEGACO or TGCP.

0363In step <b>19</b>, an ISUP REL message is sent.

0364In step <b>20</b>, an ISUP RLC message is returned.

0365The 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 <b>352</b> travels.

0366The 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.

0367The 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.

0368Another 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).

0369Also, 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.

0370While 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.