Enhanced E911 location information using voice over internet protocol (VoIP)

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

The present application claims priority from U.S. patent application Ser. No. 10/739,292, entitled “ENHANCED E911 LOCATION INFORMATION USING VOICE OVER INTERNET PROTOCOL (VoIP),” filed on Dec. 19, 2003, the entirety of which is explicitly incorporated herein by reference.


BACKGROUND OF THE INVENTION

1. Field of the Invention


This invention relates generally to VoIP communication carriers. More particularly, it relates to location-based services for the provision of E-9-1-1 emergency services by the VoIP industry.


2. Background of Related Art


911 is a phone number widely recognized as an emergency phone number that is used by emergency dispatch personnel, among other things, to determine a location of a caller. Enhanced 911 (E911) is defined by the transmission of callback number and location information. E911 may be implemented for landline and/or wireless devices.


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


Voice-Over-Internet Protocol (VoIP) is a technology that emulates a phone call, but instead of using a circuit based system such as the telephone network, utilizes packetized data transmission techniques most notably implemented in the Internet.


As people adopt voice-over-IP (VoIP) technology for routine communications, the inventor herein recognizes that there is a growing need to be able to access E911 services including provision of location information from a VoIP device. The existing E911 infrastructure is built upon copper wire line voice technology and is not compatible with VoIP.


There are at least three VoIP scenarios that require E911 service:

    • 1. The VoIP device is physically connected to a static data cable at a “home” address.
    • 2. The VoIP device is physically connected to a data cable at a location different than its “home” address. For instance, a laptop computer device utilized away from home as a VoIP communication device would be a VoIP ‘visitor’ device as described by this scenario.
    • 3. The VoIP device is wireleless, physically disconnected from any data cable. In this situation, the VoIP device connects to the VoIP network via cellular or WiFi technology.


Conventional VoIP voice gateways are typically located in only a few places across the country. Thus, any 911 call originating in a city such as Miami, for example, may initially be routed to the public safety answer point (PSAP) in, e.g., Minneapolis if the VoIP gateway happens to be located in Minneapolis. Moreover, the call will not be “enhanced”. That is, it will not provide any location or callback information to the dispatcher. This problem has been partially resolved as described in FIG. 2.


As shown in FIG. 2, a conventional architecture routes VoIP 911 calls to a designated PSAP. However, such architecture fails to provide “enhanced” service for VoIP devices.


In particular, as shown in Option 1, an IP device 250 utilizing VoIP protocols for voice communications dials 9-1-1. The VoIP device 250 is serviced by a VoIP switch 220 in the VoIP carrier's network. The VoIP switch 220 communicates with a Message Servicing Center (MSC) 230. Using a database that relates the devices callback number or IP address to the owner's address, the MSC 230 can determine which PSAP has jurisdiction for that address. The MSC 230 then communicates back to the VoIP switch 220 a 10-digit telephone number for that PSAP. The VoIP Switch 220 then converts the IP call to TDM and routes the call via the PSTN to the designated PSAP using the provided 10-digit number.


A primary challenge results from the fact that the E911 network is not accessible via the Public Switched Telephone Network (PSTN); all enhanced 911 calls must be routed via dedicated local voice trunks to a selective router that in turn routes the call to the PSAP. Calls routed via the PSTN arrive at the PSAP without callback number or location information. Provision of location information to the PSAP via the PSTN also circumvents specific PSAP hardware (e.g., CAD, GIS) designed to facilitate dispatching of responders and tracking the location of the wireless caller.


There is a need for an architecture and methodology to allow VoIP users all features relating to E911 services enjoyed by non-VoIP users, e.g., call back phone number and location information provided to a public safety answer point (PSAP).


SUMMARY OF THE INVENTION

In accordance with the principles of the present invention, a method and apparatus for routing an ESRK to public safety answer point (PSAP) relating to a call from a VoIP device comprises provisioning a first local voice-over-Internet Protocol (VoIP) gateway. A first dedicated trunk line is established between the provisioned first local VoIP gateway and a first selective router associated with a first PSAP. An ESRK is importantly associating a specific PSAP to a location of a VoIP device from which the E911 call originates. The E911 call and ESRK are routed to specific PSAPs responsible for receiving E911 calls from the location from which the E911 call originates on the VoIP device.





BRIEF DESCRIPTION OF THE DRAWINGS

Features and advantages of the present invention will become apparent to those skilled in the art from the following description with reference to the drawings, in which:



FIG. 1 shows a block diagram of the architecture of the VoIP solution, in accordance with the principles of the present invention.



FIG. 2 shows a conventional architecture for providing 911 service to a VoIP device.





DETAILED DESCRIPTION OF ILLUSTRATIVE EMBODIMENTS

The present invention provides an E-9-1-1 voice-over-IP (VoIP) solution, wherein a 911 call from a VoIP device is routed directly to the correct Public Safety Answer Point (PSAP) via dedicated trunks, together with correct location information and call-back number.


In accordance with the present invention, local VoIP gateways are incorporated, and a centralized routing intelligence is implemented, to provide access to the existing E911 infrastructure.



FIG. 1 shows a block diagram of the architecture of the VoIP solution, in accordance with the principles of the present invention. There are two additional options illustrated, in addition to the conventional option shown in FIG. 2.

    • 1. Option 2: proposed technology for providing enhanced 911 service from IP devices located at “home” or at “visitor” locations, physically connected to the VoIP network via cable.
    • 2. Option 3: proposed technology for providing enhanced 911 service from wireless IP devices.


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


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


The selective routers 150 are provisioned as desired and otherwise conventionally known.


An Automatic Location Identification (ALI) database 190 is included, and is provisioned with Emergency Service Routing Keys (ESRKs) dedicated for VoIP use as desired and otherwise conventionally known.


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


The message flow resulting from a VoIP call from a given IP device, e.g., IP device 352, is now described with reference to FIG. 1.


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


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


In step 2, the VoIP switch 120b servicing that particular VoIP device 352 receives the E911 call, and queries the wireless carrier MSC 130b for routing information. The query to the MSC 130b includes a callback number, and location information (if mobile).


In step 3, the MSC 130b relates location to specific PSAPs. If the location is static, the phone number and location will already be established in the MSC database 130b. If the VoIP device 352 is mobile, the caller provides location information at the time of log-on. This caller information will then accompany the E911 call. In certain scenarios such as even in static situations, the location information may accompany the E911 call.


In step 4, upon determination of the appropriate PSAP to receive the E911 call, the MSC 130b responds with an Emergency Service Routing Key (ESRK), plus IP routing instructions to the VoIP switch 120b. The utilized ESRK is a 10-digit number compatible with the selective router that serves that particular PSAP. ESRKs uniquely identify a specific PSAP. In FIG. 1, only the selective routers 150 compatible with one local VoIP gateway 100 are shown, as are PSAPs 200-206 having dedicated E911 trunks associated with each of those selective routers 150. The person of skill in the art will understand from FIG. 1 that similar local Gateway's will be implemented throughout a large area, e.g., across state lines or even countries, each having associated selective routers, and each selective router having one or more dedicated trunk line to a given one or more PSAPs.


The ESRK provided by the MSC 130b to the VoIP switch 120b is unique to the particular PSAP servicing the location that the wireless VoIP device 352 is calling from. The IP routing instructions provided by the MSC 130b to the VoIP switch 120b identify the IP address of the correct local VoIP gateway in the local access and transport area (LATA) where the compatible selective router exists. For example, it might be the local VoIP gateway 100 shown in FIG. 1, or it might instead be another local VoIP gateway associated with another local area (e.g., another LATA).


In step 5, the VoIP switch 120b routes the VoIP E911 call to the designated VoIP gateway 100. The routed VoIP E911 call includes the ESRK.


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


In step 7, as in otherwise conventional techniques, upon reaching the selective router 150a, 150b or 150c, the existing E911 infrastructure delivers the E911 call to the proper PSAP 200, 202, 204 or 206 that is assigned to the location that the wireless VoIP device 352 is calling from. Thus, the relevant selective router 150a, 150b or 150c previously provisioned to recognize the ESRK in the 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 ESRK, queries the ALI database 190 for the location of the caller, and for call-back information.


The ALI database 190 steers the ESRK to the appropriate MSC 130b, which in turn responds to the ALI query with the correct location and call-back information. The disclosed ALI query employs otherwise conventional PAM or E2+ protocols.


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


Sequence of events for Option 3 (wireless IP device) would be as follows:


In step 1, a caller using the wireless VoIP device 355 dials “911”.


In step 2, the VoIP switch 120b servicing that particular VoIP device 352 receives the E911 call, and queries the wireless carrier MSC 130b for routing information. The query to the MSC 130b includes a callback number, but no location information.


In step 3, the MSC 130b initiates a GPOSREQ to the Position Determining Equipment (PDE) 400 serving the wireless carrier that provides the wireless coverage for the IP device. A PDE is a position determining device that determines a position, e.g., a latitude and longitude in the wireless Phase 2 world. Many wireless VoIP devices utilize cellular technology, thus positioning equipment used for cellular devices may be utilized for VoIP devices, given the present invention.


The PDE 400, using otherwise conventional techniques, responds with a gposreq response that contains the latitude and longitude of the wireless IP device. The MPC 130b relates location to a specific PSAP.


Subsequent steps in Option 3 are similar to those described with respect to Option 2.


Implementation of E911 for VoIP callers as disclosed herein facilitates the migration of an individual PSAP to a pure VoIP environment, minimizing additional engineering as VoIP systems become more prevalent and revolutionize the telecom industry.


While the invention has been described with reference to the exemplary embodiments thereof, those skilled in the art will be able to make various modifications to the described embodiments of the invention without departing from the true spirit and scope of the invention.

Claims
  • 1. A method of providing location information to a public safety answer point (PSAP) relating to a call from a VoIP device, comprising: provisioning a local voice-over-Internet Protocol (VoIP) gateway to convert a VoIP E911 call to a circuit switched 911 voice call;establishing a plurality of dedicated trunk lines between said provisioned local VoIP gateway and a plurality of selective routers associated with a plurality of specific PSAPs to communicate said converted VoIP E911 call-to-circuit switched 911 voice call with a specific PSAP;selecting, based on a received Emergency Services Routing Key (ESRK), a particular dedicated trunk line from said plurality of dedicated trunk lines; androuting, from said provisioned local VoIP gateway to said selected particular dedicated trunk line, said converted VoIP E911 call to circuit switched 911 voice call to said specific PSAP responsible for receiving a given E911 call from a location from which said given E911 call originates on said VoIP device.
  • 2. The method of providing location information to a public safety answer point (PSAP) relating to a call from a VoIP device according to claim 1, wherein: said identifier is an emergency services key.
  • 3. The method of providing location information to a public safety answer point (PSAP) relating to a call from a VoIP device according to claim 1, further comprising: querying a positioning center for routing information.
  • 4. The method of providing location information to a public safety answer point (PSAP) relating to a call from a VoIP device according to claim 3, wherein said routing information comprises: an emergency services key.
  • 5. The method of providing location information to a public safety answer point (PSAP) relating to a call from a VoIP device according to claim 3, further comprising: sending said routing information to said VoIP gateway from said positioning center.
  • 6. The method of providing location information to a public safety answer point (PSAP) relating to a call from a VoIP device according to claim 5, further comprising: after a query from said PSAP, sending payload data including a callback number and said location information to an automatic location identifier (ALI) database from said positioning center.
  • 7. The method of providing location information to a public safety answer point (PSAP) relating to a call from a VoIP device according to claim 1, further comprising: responding to a query from said VoIP gateway with an emergency services key.
  • 8. The method of providing location information to a public safety answer point (PSAP) relating to a call from a VoIP device according to claim 1, further comprising: responding to a query from said PSAP with said location information and a callback number.
  • 9. The method of providing location information to a public safety answer point (PSAP) relating to a call from a VoIP device according to claim 8, wherein: said Emergency Services Routing Key (ESRK) is a 10-digit number compatible with the selective router that serves said specific PSAP.
  • 10. The method of providing location information to a public safety answer point (PSAP) relating to a call from a VoIP device according to claim 1, wherein: said routing information is internet protocol (IP) routing instructions identifying an IP address of a correct local VoIP gateway serving said specific PSAP.
  • 11. The method of providing location information to a public safety answer point (PSAP) relating to a call from a VoIP device according to claim 1, further comprising: querying an Automatic Location Identification (ALI) database for said location of said caller, and for callback information.
  • 12. The method of providing location information to a public safety answer point (PSAP) relating to a call from a VoIP device according to claim 11, wherein: said querying is performed from said specific PSAP.
  • 13. The method of providing location information to a public safety answer point (PSAP) relating to a call from a VoIP device according to claim 11, wherein: said querying of said ALI database uses an emergency services key.
  • 14. The method of providing location information to a public safety answer point (PSAP) relating to a call from a VoIP device according to claim 13, further comprising: steering said emergency services key to said positioning center; andresponding to said ALI query with location and callback information of said caller.
  • 15. The method of providing location information to a public safety answer point (PSAP) relating to a call from a VoIP device according to claim 1, further comprising: initiating a Geo-Position Request (GPOSREQ) to position determining equipment.
  • 16. Apparatus for providing location information to a public safety answer point (PSAP) relating to a call from a VoIP device, comprising: means for provisioning a local voice-over-Internet Protocol (VoIP) gateway to convert a VoIP E911 call to a circuit switched 911 voice call;means for establishing a plurality of dedicated trunk lines between said provisioned local VoIP gateway and a plurality of selective routers associated with a plurality of specific PSAPs to communicate said converted VoIP E911 call-to-circuit switched 911 voice call with a specific PSAP;means for selecting, based on a received Emergency Services Routing Key (ESRK), a particular dedicated trunk line from said plurality of dedicated trunk lines; andmeans for routing, from said provisioned local VoIP gateway to said selected particular dedicated trunk line, said converted VoIP E911 call to circuit switched 911 voice call to said specific PSAP responsible for receiving a given E911 call from a location from which said given E911 call originates on said VoIP device.
  • 17. The apparatus for providing location information to a public safety answer point (PSAP) relating to a call from a VoIP device according to claim 16, wherein: said identifier is an emergency services key.
  • 18. The apparatus for providing location information to a public safety answer point (PSAP) relating to a call from a VoIP device according to claim 16, further comprising: means for querying a positioning center for routing information.
  • 19. The apparatus for providing location information to a public safety answer point (PSAP) relating to a call from a VoIP device according to claim 18, wherein said routing information comprises: an emergency services key.
  • 20. The apparatus for providing location information to a public safety answer point (PSAP) relating to a call from a VoIP device according to claim 18, further comprising: means for sending said routing information to said VoIP gateway from said positioning center.
  • 21. The apparatus for providing location information to a public safety answer point (PSAP) relating to a call from a VoIP device according to claim 20, further comprising: means for sending, after a query from said PSAP, payload payload data including a callback number and said location information, to an automatic location identifier (ALI) database from said positioning center.
  • 22. The apparatus for providing location information to a public safety answer point (PSAP) relating to a call from a VoIP device according to claim 16, further comprising: means for responding to a query from said VoIP gateway with an emergency services key.
  • 23. The apparatus for providing location information to a public safety answer point (PSAP) relating to a call from a VoIP device according to claim 16, further comprising: means for responding to a query from said PSAP with said location information and a callback number.
  • 24. The apparatus for providing location information to a public safety answer point (PSAP) relating to a call from a VoIP device according to claim 23, wherein: said Emergency Services Routing Key (ESRK) is a 10-digit number compatible with the selective router that serves said specific PSAP.
  • 25. The apparatus for providing location information to a public safety answer point (PSAP) relating to a call from a VoIP device according to claim 16, wherein: said routing information is internet protocol (IP) routing instructions identifying an IP address of a correct local VoIP gateway serving said specific PSAP.
  • 26. The apparatus for providing location information to a public safety answer point (PSAP) relating to a call from a VoIP device according to claim 16, further comprising: means for querying an Automatic Location Identification (ALI) database for said location of said caller, and for callback information.
  • 27. The apparatus for providing location information to a public safety answer point (PSAP) relating to a call from a VoIP device according to claim 26, wherein: said querying is performed from said specific PSAP.
  • 28. The apparatus for providing location information to a public safety answer point (PSAP) relating to a call from a VoIP device according to claim 26, wherein: said querying of said ALI database uses an emergency services key.
  • 29. The apparatus for providing location information to a public safety answer point (PSAP) relating to a call from a VoIP device according to claim 28, further comprising: means for steering said emergency services key to said positioning center; andmeans for responding to said ALI query with location and callback information of said caller.
  • 30. The apparatus for providing location information to a public safety answer point (PSAP) relating to a call from a VoIP device according to claim 16, further comprising: means for initiating a Geo-Position Request (GPOSREQ) to position determining equipment.
US Referenced Citations (259)
Number Name Date Kind
1103073 O'Connell Jul 1914 A
4494119 Wimbush Jan 1985 A
4625081 Lotito Nov 1986 A
4651156 Martinez Mar 1987 A
4706275 Kamil Nov 1987 A
4891638 Davis Jan 1990 A
4891650 Sheffer Jan 1990 A
4910767 Brugliera et al. Mar 1990 A
4952928 Carroll et al. Aug 1990 A
5014206 Scribner et al. May 1991 A
5043736 Darnell et al. Aug 1991 A
5055851 Sheffer Oct 1991 A
5068656 Sutherland Nov 1991 A
5068891 Marshall Nov 1991 A
5070329 Jasinaki Dec 1991 A
5081667 Drori et al. Jan 1992 A
5119104 Heller Jun 1992 A
5144283 Arens et al. Sep 1992 A
5161180 Chavous Nov 1992 A
5177478 Wagai et al. Jan 1993 A
5193215 Olmer Mar 1993 A
5208756 Song May 1993 A
5214789 George May 1993 A
5218367 Sheffer et al. Jun 1993 A
5223844 Mansell et al. Jun 1993 A
5224150 Neustein Jun 1993 A
5239570 Koster et al. Aug 1993 A
5265630 Hartmann Nov 1993 A
5266944 Carroll et al. Nov 1993 A
5289527 Teidemann, Jr. Feb 1994 A
5293642 Lo Mar 1994 A
5299132 Wortham Mar 1994 A
5325302 Izidon et al. Jun 1994 A
5334974 Simms et al. Aug 1994 A
5343493 Karimullah Aug 1994 A
5347568 Moody et al. Sep 1994 A
5351235 Lahtinen Sep 1994 A
5361212 Class et al. Nov 1994 A
5363425 Mufti et al. Nov 1994 A
5374936 Feng Dec 1994 A
5379451 Nakagoshi et al. Jan 1995 A
5381338 Wysocki et al. Jan 1995 A
5387993 Heller et al. Feb 1995 A
5388147 Grimes Feb 1995 A
5394158 Chia Feb 1995 A
5396227 Carroll et al. Mar 1995 A
5398190 Wortham Mar 1995 A
5406614 Hara Apr 1995 A
5418537 Bird May 1995 A
5423076 Westergren et al. Jun 1995 A
5432841 Rimer Jul 1995 A
5434789 Fraker et al. Jul 1995 A
5454024 Lebowitz Sep 1995 A
5461390 Hoshen Oct 1995 A
5470233 Fruchterman et al. Nov 1995 A
5479408 Will Dec 1995 A
5479482 Grimes Dec 1995 A
5485161 Vaughn Jan 1996 A
5488563 Chazelle et al. Jan 1996 A
5494091 Freeman et al. Feb 1996 A
5497149 Fast Mar 1996 A
5508931 Snider Apr 1996 A
5513243 Kage Apr 1996 A
5515287 Hakoyama et al. May 1996 A
5519403 Bickley et al. May 1996 A
5532690 Hertel Jul 1996 A
5535434 Siddoway et al. Jul 1996 A
5539398 Hall et al. Jul 1996 A
5543776 L'Esperance et al. Aug 1996 A
5552772 Janky et al. Sep 1996 A
5555286 Tendler Sep 1996 A
5568119 Schipper et al. Oct 1996 A
5579372 Astrom Nov 1996 A
5588009 Will Dec 1996 A
5592535 Klotz Jan 1997 A
5604486 Lauro et al. Feb 1997 A
5606313 Allen et al. Feb 1997 A
5606850 Nakamura Mar 1997 A
5610815 Gudat et al. Mar 1997 A
5614890 Fox Mar 1997 A
5615116 Gudat et al. Mar 1997 A
5621793 Bednarek et al. Apr 1997 A
5628051 Salin May 1997 A
5633912 Tsoi May 1997 A
5682600 Salin Oct 1997 A
5740534 Averst et al. Apr 1998 A
5767795 Schaphorst Jun 1998 A
5768509 Gunluk Jun 1998 A
5774533 Patel Jun 1998 A
5787357 Salin Jul 1998 A
5794142 Vanttila et al. Aug 1998 A
5797094 Houde et al. Aug 1998 A
5797096 Lupien et al. Aug 1998 A
5802492 Delorme et al. Sep 1998 A
5806000 Vo et al. Sep 1998 A
5822700 Hult et al. Oct 1998 A
5920821 Seaholtz et al. Jul 1999 A
5930701 Skog Jul 1999 A
5943399 Bannister et al. Aug 1999 A
5946629 Sawyer et al. Aug 1999 A
5946630 Willars et al. Aug 1999 A
5950130 Coursey Sep 1999 A
5953398 Hill Sep 1999 A
5974054 Couts et al. Oct 1999 A
5978685 Laiho Nov 1999 A
5987323 Huotari Nov 1999 A
5998111 Abe Dec 1999 A
6035025 Hanson Mar 2000 A
6049710 Nilsson Apr 2000 A
6058300 Hanson May 2000 A
6061346 Nordman May 2000 A
6064875 Morgan May 2000 A
6070067 Nguyen et al. May 2000 A
6075982 Donovan et al. Jun 2000 A
6101378 Barabash et al. Aug 2000 A
6104931 Havinis et al. Aug 2000 A
6122503 Daly Sep 2000 A
6122520 Want et al. Sep 2000 A
6131028 Whitington Oct 2000 A
6148197 Bridges et al. Nov 2000 A
6148198 Anderson et al. Nov 2000 A
6149353 Nilsson Nov 2000 A
6169891 Gorham et al. Jan 2001 B1
6173181 Losh Jan 2001 B1
6178505 Schneider et al. Jan 2001 B1
6181935 Gossman et al. Jan 2001 B1
6188752 Lesley Feb 2001 B1
6198431 Gibson Mar 2001 B1
6199113 Alegre et al. Mar 2001 B1
6205330 Winbladh Mar 2001 B1
6208854 Roberts et al. Mar 2001 B1
6219557 Havinis Apr 2001 B1
6223046 Hamill-Keays et al. Apr 2001 B1
6226529 Bruno et al. May 2001 B1
6249680 Wax et al. Jun 2001 B1
6249744 Morita Jun 2001 B1
6266614 Alumbaugh Jul 2001 B1
6289373 Dezonno Sep 2001 B1
6317594 Gossman et al. Nov 2001 B1
6321091 Holland Nov 2001 B1
6327479 Mikkola Dec 2001 B1
6427001 Contractor Jul 2002 B1
6456852 Bar et al. Sep 2002 B2
6529500 Pandharipande Mar 2003 B1
6529722 Heinrich Mar 2003 B1
6560456 Lohtia et al. May 2003 B1
6584307 Antonucci et al. Jun 2003 B1
6650901 Schuster et al. Nov 2003 B1
6678357 Stumer et al. Jan 2004 B2
6728545 Belcea Apr 2004 B1
6744856 Karnik et al. Jun 2004 B2
6744858 Ryan et al. Jun 2004 B1
6771742 McCalmont et al. Aug 2004 B2
6775534 Lindgren Aug 2004 B2
6779049 Altman et al. Aug 2004 B2
6799049 Zellner et al. Sep 2004 B1
6813264 Vassilovski Nov 2004 B2
6816580 Timmins Nov 2004 B2
6937597 Rosenberg Aug 2005 B1
6940950 Dickinson et al. Sep 2005 B2
6963557 Knox Nov 2005 B2
6968044 Beason Nov 2005 B2
7020480 Coskun Mar 2006 B2
7092385 Gallant Aug 2006 B2
7136466 Gao Nov 2006 B1
7171220 Belcea Jan 2007 B2
7177397 McCalmont Feb 2007 B2
7177399 Dawson Feb 2007 B2
7194249 Phillips Mar 2007 B2
7245900 Lamb Jul 2007 B1
7260186 Zhu Aug 2007 B2
7260384 Bales et al. Aug 2007 B2
7330899 Wong Feb 2008 B2
7333480 Clarke Feb 2008 B1
7366157 Valentine et al. Apr 2008 B1
7369530 Keagy May 2008 B2
7412049 Koch Aug 2008 B1
7440442 Grabelsky et al. Oct 2008 B2
7522581 Acharya Apr 2009 B2
7573982 Breen Aug 2009 B2
7617287 Vella Nov 2009 B2
7702081 Klesper Apr 2010 B1
20010021646 Antonucci Sep 2001 A1
20010049274 Degraeve Dec 2001 A1
20020118796 Menard Aug 2002 A1
20020126656 Park Sep 2002 A1
20020156732 Odijk Oct 2002 A1
20030026245 Ejzak Feb 2003 A1
20030069002 Hunter et al. Apr 2003 A1
20030072318 Lam et al. Apr 2003 A1
20030086539 McCalmont May 2003 A1
20030096623 Kim May 2003 A1
20030100320 Ranjan May 2003 A1
20030109245 McCalmont Jun 2003 A1
20030125042 Olrik Jul 2003 A1
20030147537 Jing et al. Aug 2003 A1
20030186709 Rhodes Oct 2003 A1
20030196105 Fineberg Oct 2003 A1
20040043775 Kennedy Mar 2004 A1
20040092250 Valloppillil May 2004 A1
20040098497 Banet et al. May 2004 A1
20040132465 Mattila et al. Jul 2004 A1
20040146040 Phan-Anh Jul 2004 A1
20040150518 Phillips et al. Aug 2004 A1
20040152493 Phillips et al. Aug 2004 A1
20040176123 Chin Sep 2004 A1
20040180671 Spain Sep 2004 A1
20040184584 McCalmont Sep 2004 A1
20040190497 Knox Sep 2004 A1
20040203568 Kirtland Oct 2004 A1
20040203575 Chin Oct 2004 A1
20040203922 Hines et al. Oct 2004 A1
20040229632 Flynn et al. Nov 2004 A1
20040235493 Ekerborn Nov 2004 A1
20040242238 Wang et al. Dec 2004 A1
20040247090 Nurmela Dec 2004 A1
20050003797 Baldwin Jan 2005 A1
20050048987 Glass Mar 2005 A1
20050053209 D'Evelyn Mar 2005 A1
20050083911 Grabelsky Apr 2005 A1
20050085257 Laird Apr 2005 A1
20050107673 Ball May 2005 A1
20050135569 Dickinson Jun 2005 A1
20050169248 Truesdale Aug 2005 A1
20050190892 Dawson Sep 2005 A1
20050201528 Meer Sep 2005 A1
20050201529 Nelson Sep 2005 A1
20050213716 Zhu et al. Sep 2005 A1
20050261002 Cheng Nov 2005 A1
20050282518 D'Evelyn et al. Dec 2005 A1
20050287979 Rollender Dec 2005 A1
20060025154 Alapuranen et al. Feb 2006 A1
20060058049 McLaughlin Mar 2006 A1
20060069503 Suomela et al. Mar 2006 A1
20060109960 D'Evelyn et al. May 2006 A1
20060120517 Moon Jun 2006 A1
20060125692 Wang Jun 2006 A1
20060135132 Cai Jun 2006 A1
20060188083 Breen Aug 2006 A1
20060193447 Schwartz Aug 2006 A1
20060239205 Warren Oct 2006 A1
20060293024 Benco Dec 2006 A1
20070019614 Hoffmann Jan 2007 A1
20070021908 Jaugilas et al. Jan 2007 A1
20070036139 Patel Feb 2007 A1
20070041513 Gende Feb 2007 A1
20070115941 Patel May 2007 A1
20070117574 Watanabe May 2007 A1
20070117577 Harris May 2007 A1
20070121601 Kikinis May 2007 A1
20070160036 Smith Jul 2007 A1
20070253429 James Nov 2007 A1
20070263610 Mitchell Nov 2007 A1
20070293205 Henderson Dec 2007 A1
20080081646 Morin Apr 2008 A1
20090003535 Grabelsky Jan 2009 A1
20090221263 Titus Sep 2009 A1
20100003954 Greene Jan 2010 A1
20100076767 Vieri Mar 2010 A1
Foreign Referenced Citations (2)
Number Date Country
WO 9921380 Apr 1999 WO
WO9921380 Apr 1999 WO
Related Publications (1)
Number Date Country
20060280164 A1 Dec 2006 US