Consequential location derived information

Information

  • Patent Grant
  • 8290505
  • Patent Number
    8,290,505
  • Date Filed
    Tuesday, August 29, 2006
    18 years ago
  • Date Issued
    Tuesday, October 16, 2012
    12 years ago
Abstract
The number of messages required in networks where location services are deployed may be reduced, by providing updated location information regarding particular subscribers, or even all subscribers, to subscribed or otherwise logged applications or services upon obtaining and providing location information for a different application or service. Consequential watch services in accordance with the principles of the present invention provide location information to one or more services OTHER than or in ADDITION to the service currently requesting location information, based on subscription to a suitable service.
Description

This application claims priority from U.S. Appl. No. 60/367,708, entitled “Location Derived Presence Information,” filed Mar. 28, 2002, to Hines et al.; U.S. Appl. No. 60/367,709, entitled “Consequential Location Services,” filed Mar. 28, 2002, to Hines et al.; U.S. application Ser. No. 10/395,217, entitled “Location Derived Presence Information,” filed Mar. 25, 2003, to Hines, et al.; and is a continuation application of U.S. application Ser. No. 10/400,639, now U.S. Pat. No. 7,120,450, entitled “Consequential Location Derived Information,” filed Mar. 28, 2003 the entirety of all four of which are explicitly incorporated herein by reference.


BACKGROUND OF THE INVENTION

1. Field of the Invention


This invention relates generally to wireless communication carriers. More particularly, it relates to location-based services for the wireless industry.


2. Background of Related Art


Location information regarding subscribers is increasingly becoming available in a wireless network. This is particularly true in systems that comply with E-9-1-1 requirements. Location information relates to absolute coordinates of a wireless device.


Both Location and Presence services are message intensive on telecom networks. Message reduction in general is desirable, both to allow increased capacity in a wireless network, as well as to improve reliability of the system by reducing the number of messages.



FIG. 4 shows a conventional LoCation Services (LCS) request.


In particular, as shown in FIG. 4, a location server 106 requests location information regarding a particular mobile subscriber (MS) from a core network node, e.g., from a Mobile Switch Center (MSC) 110. Requested information regarding a particular wireless device (MS) may include, e.g., attach, detach, and location area update. The location server 106 may also request information regarding the wireless device such as attach, detach and/or location area update from a Packet Date Node (e.g., SGSN, GGSN, or PDSN), or help the device calculate x/y direction.


Typically, location information regarding a particular wireless device is requested of a home location register (HLR).


As shown in step 1 of FIG. 4, a locations services client sends a message to a location server.


In step 2, a location server 106 sends a Provide Subscriber Info message to a Home Location Register 108, requesting subscriber information regarding a particular subscriber.


In step 3, the carrier's Home Location Register (HLR) 108 provides the subscriber information for the requested subscriber back to the location server 106.


In step 4, location information regarding the requested subscriber is requested to either an MSC or Packet Data node 110. The MSC or Packet Data Node preferably provides precise location information using, e.g., a global positioning satellite (GPS), triangulation techniques, or other relevant locating technology, or helps the device calculate X/Y direction.


In step 5, the location request is forwarded to the Radio Access Network (RAN) 112 if needed.


In step 6, precise, updated location information regarding the requested subscriber is sent to the location server (LS) 106.


In step 7, an ultimate response to the original location request is sent to the LCS client 104 that initially requested the location information.


Others have proposed watching or monitoring locations of subscribers in a wireless network by “polling”. The conventional polling technique utilizes a system within the wireless network to request updated location information relating to all provisioned subscribers. The polling is performed periodically, e.g., every N minutes.


However, polling is disadvantageous in that it is very resource intensive making it a costly solution for the business use cases it supports.


SUMMARY OF THE INVENTION

In accordance with the principles of the present invention, a method and apparatus provides presence and location information regarding a wireless device. Applications register with the system they are interested in presence and/or location information consequentially. A request for presence or location information is received by a potentially unrelated application, either through a direct request or as a polled request. The information is retrieved through standard practices and replied to the caller. As a consequence of the original presence or location request, the resultant information is also returned to the register applications. This greatly reduces the load placed on the wireless network since the registered applications received updated information without directly requesting the information.





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 generally a location request.



FIG. 2 shows an exemplary message flow of a LoCation Services (LCS) request, including a consequential watch application or service, in accordance with the principles of the present invention.



FIG. 3 shows an exemplary consequential watch table, in accordance with the principles of the present invention.



FIG. 4 shows a conventional LoCation Services (LCS) request.





DETAILED DESCRIPTION OF ILLUSTRATIVE EMBODIMENTS

The present invention reduces the number of messages required in networks where location-based services are deployed.


Consequential Watch services in accordance with the principles of the present invention provides location information to one or more services OTHER than or in ADDITION to the service currently requesting location information, based on subscription to a suitable service, referred to herein as a consequential watch application. Of course, a suitable service may have any name other than consequential watch yet perform the same or similar function(s) as does the described consequential watch.


In the disclosed embodiments, a consequential watch service notifies one or more OTHER applications other than the particular application responsible for a latest location request, whenever location information for a particular subscriber is updated. A consequential watch application allows the avoidance of polling of subscribers for latest location information, and instead replaces polling as in conventional wireless systems with a monitoring and reporting service that reports to relevant applications that have previously requested monitoring service for the particular subscriber(s), even though those applications were not currently responsible for an update to the relevant subscriber's location information.


Thus, the disclosed consequential watch application notifies other applications or services, e.g., upon a request for update of a mobile subscriber's position, state, preferences or feature set, as a consequence of another service requesting location information (thus updating the location database at, e.g., a Location Server (LS)). Note that the other applications or services are not necessarily notified only when the particular subscriber changes location: but rather as a consequence of a different application or service requesting updated location information regarding that particular subscriber.


The present invention solves fundamental disadvantages of conventional wireless systems regarding location reporting. For instance, conventional wireless networks including a location-based service update location information on a scheduled, regular basis, i.e., using polling. However, polling of every single mobile subscriber in a mobile network is extremely resource intensive.


For example, if a mobile network has 10,000,000 subscribers, and a mere 5% of those 10,000,000 subscribers, or 500,000 actually use a location service requiring location tracking of their handset, the entire network would be subjected to location tracking. With 5-minute updating of each wireless device in the network this translates into a need to support 1,667 transactions per second. This puts a strain on the wireless network, and consumes valuable data bandwidth in the communications.


In accordance with a consequential watch system in accordance with the principles of the present invention, various applications or services will, from time to time, request an update of the location of a particular subscriber anyway. A consequential watch application reduces this redundancy by allowing entities in communication with the wireless network to subscribe to a consequential watch service wherein when a particular user's location information is updated in the Location Server (LS), then applications or services requesting location information upon update of that particular subscriber will also receive relevant, updated location information regarding the same wireless user.


The subscriber to the consequential watch service may be inside or outside the carrier's network.


For example, presume a wireless subscriber with a phone number, e.g., (206) 390-9150 is subscribed to, e.g., Starbucks Promotions, Yahoo! Messaging, & The Battle in Seattle (a multi-player mobile game), and that wireless subscriber (206) 390-9150 dials #777 to ask for the nearest Bank of America ATM, the location data update made for #777 will be pushed to the other three applications as a consequence of the #777 request and the functionality of the consequential watch.



FIG. 1 shows generally a location request to a core network node containing pertinent location information, resulting not only in a return of location information, but also in the spawning of presence information.


In particular, as shown in FIG. 1, a location server 204 requests location information regarding a particular mobile subscriber (MS) from a core network node 205, e.g., from a Mobile Switch Center (MSC). Requested information regarding a particular wireless device (MS) may include, e.g., attach, detach, and location area update. The location server 204 may also request information regarding the wireless device such as attach, detach and/or location area update from a Packet Date Node (e.g., SGSN, GGSN, or PDSN). The location server 204 may alternatively (or additionally) obtain location information directly from an appropriately equipped wireless device (e.g., a wireless device including a global positioning satellite (GPS) receiver.


Typically, location information regarding a particular wireless device is requested of a home location register (HLR). In accordance with the principles of the present invention, the home location register can also serve as a basis for presence services. Exemplary presence services may include, e.g., the state and/or status of a subscriber.


Importantly, in accordance with the present invention, information relating to an initial location request spawns or triggers the provision of additional location request information messages to subscribers to a consequential watch application or service.



FIG. 2 shows an exemplary message flow of a LoCation Services (LCS) request between a location service client 204, a location server 206, a home location register (HLR) 208, a core network node such as an MSC or packet data node 210, and a radio access node (RAN) 212, including a consequential watch application or service located, e.g., in the location server 206, in accordance with the principles of the present invention. While the consequential watch application is located herein in association with a location server 206, the consequential watch application may be located in any suitable element sufficient to cause the provision of multiple location information messages in response to a single request.


In the exemplary embodiment, the messaging cycle is initiated (shown in step 1) by a location services client 204, that transmits a location request message to a location services server 206 in the relevant carrier's network.


In step 2, a location server 206 sends a Provide Subscriber Info message to a Home Location Register 208 (or other node containing subscriber identity information) regarding a particular subscriber. The Provide Subscriber Info message can request location information and/or subscriber state. In this use case, location information regarding a particular subscriber is requested, and within the same message, presence information such as subscriber state may also be requested. Requested presence information can include, e.g., idle, bust, not reachable, etc.


In step 3, the network node containing the location information (e.g., the carrier's Home Location Register (HLR) 208) provides the requested subscriber information for the requested subscriber back to the location server 206.


In step 4, the location services server 206 requests information regarding the relevant wireless user by message to either an MSC or Packet Data node 210. The MSC or Packet Data Node preferably provides precise location information using, e.g., a global positioning satellite (GPS), triangulation techniques, or other relevant locating technology. Alternatively, precise location information may be obtained from an appropriately equipped wireless device (e.g., a wireless device including a GPS receiver).


In step 5, the MSC or packet data node 210 requests updated location information of the wireless network, i.e., sending a request for current location information from a relevant node or application of the wireless network (e.g., from the Radio Access Network (RAN) 212).


The MSC, packet data node 110, Radio Access Network 212, etc. may determine a current location of the relevant wireless device using any suitable location technology, e.g., using a global positioning satellite (GPS) system, using triangulation, using angle of arrival, etc.


As part of the determination of a current location of the wireless device, as shown in Step 5, the location request may be forwarded to the relevant Radio Access Network 212. This would be necessary for certain locating technologies, e.g., for triangulation, angle of arrival, etc.) If a global positioning satellite system is utilized, the location request may be forwarded to a suitable GPS application in the wireless network that receives GPS location information regarding a relevant wireless device.


In step 6, a response to the update location information request including precise, updated location information regarding the requested subscriber is transmitted to the location services server (LS) 206. (The updated location information may also be forwarded to the HLR (not shown in FIG. 2) to update the current location of the relevant wireless device).


In step 7, an ultimate response to the original location request is sent to the LCS client 204 that initially requested the location information. This location information ideally includes current location information freshly obtained from the MSC 210 or other network node, but may instead be cached location information stored in the HLR 208 if the location information is not returned within a sufficient time window (e.g., causing a timeout). This would be the end of an otherwise conventional location request. However, the invention importantly continues on. In some applications, if desired, the process may end in the event of a timeout. However, the consequential provision of location information to subscribed other applications or services may be provided even in the event of a timeout waiting for new location information.


Step 8 particularly shows the advantages of a consequential location application or service, in accordance with the principles of the present invention.


In particular, in accordance with important principles of the present invention, although location information has already been provided to a requesting application or service, the same location information is also provided to one or more additional applications or services that have previously requested such information in the event of somebody else requesting information regarding the particular subscriber.


This ‘freebie’ location information is an important aspect of the present invention. For instance, an entirely separate application or service may register with a particular carrier for a consequential location service, perhaps by paying suitable fees, for the right to receive location information for those wireless devices that otherwise have location information retrieved. This avoids the need for the location server 206 to separately handle additional requests from each separate application desiring location information regarding the same subscriber(s).



FIG. 3 shows an exemplary consequential watch table 305, in accordance with the principles of the present invention.


In particular, FIG. 3 shows just one possible table associating unique subscriber identities (e.g., phone numbers) with one or more applications or services that desire to be provided with location information whenever the location information is already being provided to a different application or service.



FIG. 3 shows just two entries 301, 303 associating unique subscriber identities with applications or services subscribed to consequential watch services. Thus, application or services subscribing to a consequential watch service receives location information, avoiding the need for multiple messages otherwise required to update the same application with location information.


Applications or services may also be provided location updates by default, whenever location information regarding anyone in a particular subscriber group, or fitting particular aspects of subscribers, is provided.


As an example of consequential watch services, presume that Application 2 and Application 3 subscribe to a consequential watch service of a particular wireless carrier, as shown in FIG. 3. According to this example, the consequential watch is set up such that anytime the location of a particular subscriber (e.g., Subscriber (111) 111-5555) is updated in the location server (LS), Application 2 would be notified of the updated location by the relevant consequential watch application in addition to the initial requestor of the location information. Also according to this example, the consequential watch is further set up such that anytime the location of subscriber (555) 555-1212 is requested and provided by a location server, the same updated location information will also be provided to Application 2 and Application 3 without any further intervention or requests necessary by either Application 2 or Application 3.


Steps 8 and 9 show this latest example where location information, provided in response to a location request from one application, is also provided to Application 2 (Step 8) and also to Application 3 (Step 9).


The present invention provides benefits such as reducing core network messaging traffic, thus providing better system performance.


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 information regarding a wireless device, comprising: receiving, at a network node, a current request for location information regarding a wireless device;retrieving, from said network node, said location information regarding said wireless device; andin response to said current request for location information regarding said wireless device, triggering, by said network node, transmission of said location information regarding said wireless device to both a requesting application device and a non-requesting application device said location information is obtained in response to a network trigger generated in response to said wireless device moving from a first cell-site to a second cell site;wherein said non-requesting application device previously requested location information regarding said wireless device prior to said current request for location information.
  • 2. The method of providing location information regarding a wireless device according to claim 1, wherein: said location information is current location information.
  • 3. The method of providing location information regarding a wireless device according to claim 1, wherein: said location information is provided to at least two different applications separate from said wireless device associated with said requesting application device.
  • 4. The method of providing location information regarding a wireless device according to claim 1, wherein: said location information is maintained in a home location register.
  • 5. The method of providing location information regarding a wireless device according to claim 1, further comprising: requesting current location information regarding said wireless device from a core network node.
  • 6. The method of providing location information regarding a wireless device according to claim 5, wherein said core network node comprises: a mobile switch center.
  • 7. The method of providing location information regarding a wireless device according to claim 1, further comprising: obtaining last known location information regarding said wireless device to return as said location information.
  • 8. The method of providing location information regarding a wireless device according to claim 1, wherein: said location information is obtained from cached memory.
  • 9. The method of providing location information regarding a wireless device according to claim 1, wherein: said location information is obtained from a radio access network.
  • 10. The method of providing location information regarding a wireless device according to claim 1, wherein: said location information is obtained from a global positioning satellite (GPS) system.
  • 11. Apparatus for providing information regarding a wireless device, comprising: means for receiving, at a network node, a current request for location information regarding a wireless device;means for retrieving, from said network node, said location information regarding said wireless device said means for retrieving obtains said location information in response to a network trigger generated in response to said wireless device moving from a first cell-site to a second cell-site; andmeans for triggering, by said network node, transmission of said location information regarding said wireless device to both a requesting application device and a non-requesting application device, said transmission being triggered in response to said current request for location information regarding said wireless device;wherein said non-requesting application device previously requested location information regarding said wireless device prior to said current request for location information.
  • 12. The apparatus for providing location information regarding in a wireless device according to claim 11, wherein: said means for providing location information provides said location information to at least two different applications separate from said wireless device associated with said requesting application device.
  • 13. The apparatus for providing location information regarding in a wireless device according to claim 11, wherein: said location information is maintained in a home location register.
  • 14. The apparatus for providing location information regarding in a wireless device according to claim 11, further comprising: means for requesting current location information regarding said wireless device from a core network node.
  • 15. The apparatus for providing location information regarding in a wireless device according to claim 11, wherein said core network node comprises: a mobile switch center.
  • 16. The apparatus for providing location information regarding in a wireless device according to claim 11, further comprising: means for obtaining last known location information regarding said wireless device to return as said location information.
  • 17. The apparatus for providing location information regarding in a wireless device according to claim 11, wherein: said means for providing location information obtains said location information from cached memory.
  • 18. The apparatus for providing location information regarding in a wireless device according to claim 11, wherein: said means for providing location information obtains said location information from a radio access network.
  • 19. The apparatus for providing location information regarding in a wireless device according to claim 11, wherein: said means for providing location information obtains said location information from a global positioning satellite (GPS) system.
  • 20. The apparatus for providing location information regarding in a wireless device according to claim 11, wherein: said location information is current location information.
US Referenced Citations (219)
Number Name Date Kind
1103073 O'Connel Jul 1914 A
4445118 Taylor Apr 1984 A
4494119 Wimbush Jan 1985 A
4651156 Martinez Mar 1987 A
4868570 Davis Sep 1989 A
4891638 Davis Jan 1990 A
4891650 Sheffer Jan 1990 A
4952928 Carroll Aug 1990 A
4972484 Theile Nov 1990 A
5014206 Scribner May 1991 A
5043736 Darnell Aug 1991 A
5055851 Sheffer Oct 1991 A
5068656 Sutherland Nov 1991 A
5166972 Smith Nov 1992 A
5432841 Rimer Jul 1995 A
5835907 Newman Nov 1998 A
6032051 Hall et al. Feb 2000 A
6067045 Castelloe May 2000 A
6104931 Havinis et al. Aug 2000 A
6108533 Brohoff Aug 2000 A
6134316 Kallioniemi Oct 2000 A
6138003 Kingdon et al. Oct 2000 A
6181939 Ahvenainen Jan 2001 B1
6185427 Krasner Feb 2001 B1
6253074 Carlsson Jun 2001 B1
6278701 Ayyagari Aug 2001 B1
6321092 Fitch et al. Nov 2001 B1
6330454 Verdonk Dec 2001 B1
6360102 Havinis Mar 2002 B1
6377810 Geiger et al. Apr 2002 B1
6397208 Lee May 2002 B1
6427001 Contractor Jul 2002 B1
6526026 Menon Feb 2003 B1
6529500 Pandharipande Mar 2003 B1
6539232 Hendrey et al. Mar 2003 B2
6553236 Dunko Apr 2003 B1
6564261 Gudjonsson May 2003 B1
6580390 Hay Jun 2003 B1
6587691 Granstam et al. Jul 2003 B1
6600927 Hamilton Jul 2003 B2
6618593 Drutman Sep 2003 B1
6621810 Leung Sep 2003 B1
6687504 Raith Feb 2004 B1
6694351 Shaffer Feb 2004 B1
6731940 Nagendran May 2004 B1
6744858 Ryan Jun 2004 B1
6757545 Nowak et al. Jun 2004 B2
6771971 Smith Aug 2004 B2
6775255 Roy Aug 2004 B1
6775267 Kung Aug 2004 B1
6775534 Lindgren Aug 2004 B2
6795444 Vo Sep 2004 B1
6813264 Vassilovski Nov 2004 B2
6839417 Weisman Jan 2005 B2
6847618 Laursen Jan 2005 B2
6876734 Summers Apr 2005 B1
6882850 McConnell et al. Apr 2005 B2
6885874 Grube Apr 2005 B2
6912230 Salkini Jun 2005 B1
6940826 Simard Sep 2005 B1
6940950 Dickinson et al. Sep 2005 B2
6957068 Hutchinson Oct 2005 B2
6968044 Beason Nov 2005 B2
6985747 Chithambaram Jan 2006 B2
6993355 Pershan Jan 2006 B1
7072667 Olrik Jul 2006 B2
7106717 Rousseau et al. Sep 2006 B2
7110773 Wallace et al. Sep 2006 B1
7113128 Pitt Sep 2006 B1
7136466 Gao Nov 2006 B1
7174153 Ehlers Feb 2007 B2
7177397 McCalmont Feb 2007 B2
7177398 Meer Feb 2007 B2
7177399 Dawson Feb 2007 B2
7200380 Havlark Apr 2007 B2
7245900 Lamb Jul 2007 B1
7246187 Ezra Jul 2007 B1
7260186 Zhu Aug 2007 B2
7260384 Bales et al. Aug 2007 B2
7269428 Wallenius Sep 2007 B1
7302582 Snapp Nov 2007 B2
7321773 Hines Jan 2008 B2
7330899 Wong Feb 2008 B2
7333480 Clarke Feb 2008 B1
7369508 Parantainen May 2008 B2
7369530 Keagy May 2008 B2
7382773 Schoeneberger Jun 2008 B2
7392240 Scriffignano Jun 2008 B2
7394896 Norton Jul 2008 B2
7403939 Virdy Jul 2008 B1
7412049 Koch Aug 2008 B1
7424293 Zhu Sep 2008 B2
7426380 Hines Sep 2008 B2
7428571 Ichimura Sep 2008 B2
7436785 McMullen Oct 2008 B1
7440442 Grabelsky et al. Oct 2008 B2
7453990 Welenson Nov 2008 B2
7495608 Chen Feb 2009 B1
7573982 Breen Aug 2009 B2
7602886 Beech Oct 2009 B1
7623447 Faccin Nov 2009 B1
7711094 Olshansky May 2010 B1
7747258 Farmer Jun 2010 B2
7764961 Zhu Jul 2010 B2
7783297 Ishii Aug 2010 B2
7787611 Kotelly Aug 2010 B1
7895263 Kirchmeier Feb 2011 B1
20010040886 Jimenez Nov 2001 A1
20020077083 Zellner Jun 2002 A1
20020077084 Zellner Jun 2002 A1
20020077118 Zellner Jun 2002 A1
20020077897 Zellner Jun 2002 A1
20020085538 Leung Jul 2002 A1
20020086676 Hendry Jul 2002 A1
20020098832 Fleischer et al. Jul 2002 A1
20020102996 Jenkins Aug 2002 A1
20020118650 Jagadeesan Aug 2002 A1
20020123327 Vataja Sep 2002 A1
20020126656 Park Sep 2002 A1
20020138650 Yamamoto et al. Sep 2002 A1
20020158777 Flick Oct 2002 A1
20020173317 Nykanen Nov 2002 A1
20020191595 Mar Dec 2002 A1
20030009277 Fan Jan 2003 A1
20030012148 Peters Jan 2003 A1
20030026245 Ejzak Feb 2003 A1
20030044654 Holt Mar 2003 A1
20030086539 McCalmont May 2003 A1
20030108176 Kung Jun 2003 A1
20030109245 McCalmont Jun 2003 A1
20030118160 Holt Jun 2003 A1
20030119528 Pew Jun 2003 A1
20030186709 Rhodes Oct 2003 A1
20040032485 Stephens Feb 2004 A1
20040043775 Kennedy Mar 2004 A1
20040047461 Weisman et al. Mar 2004 A1
20040076277 Kuusinen Apr 2004 A1
20040181689 Kiyoto Sep 2004 A1
20040184584 McCalmont Sep 2004 A1
20040185875 Diacakis Sep 2004 A1
20040190497 Know Sep 2004 A1
20040192271 Eisner Sep 2004 A1
20040198386 Dupray Oct 2004 A1
20040267445 De Luca Dec 2004 A1
20050031095 Pietrowics Feb 2005 A1
20050043037 Ioppe Feb 2005 A1
20050053209 D'Evelyn Mar 2005 A1
20050063519 James Mar 2005 A1
20050074107 Renner Apr 2005 A1
20050078612 Lang Apr 2005 A1
20050083911 Grabelsky Apr 2005 A1
20050101335 Kelly May 2005 A1
20050107673 Ball May 2005 A1
20050119012 Merheb Jun 2005 A1
20050125376 Curtis Jun 2005 A1
20050135569 Dickinson Jun 2005 A1
20050136885 Kaltsukis Jun 2005 A1
20050169248 Truesdale Aug 2005 A1
20050174991 Keagy Aug 2005 A1
20050192822 Hartenstein Sep 2005 A1
20050201529 Nelson Sep 2005 A1
20050213716 Zhu Sep 2005 A1
20050232252 Hoover Oct 2005 A1
20050238156 Turner Oct 2005 A1
20050255857 Kim Nov 2005 A1
20050265318 Khartabil Dec 2005 A1
20050271029 Iffland Dec 2005 A1
20050282518 D'Evelyn Dec 2005 A1
20050287979 Rollender Dec 2005 A1
20050289097 Trossen Dec 2005 A1
20060008065 Longman et al. Jan 2006 A1
20060010200 Mousseau Jan 2006 A1
20060023747 Koren et al. Feb 2006 A1
20060026288 Acharya Feb 2006 A1
20060068753 Karpen Mar 2006 A1
20060077911 Shaffer Apr 2006 A1
20060078094 Breen Apr 2006 A1
20060088152 Green Apr 2006 A1
20060120517 Moon Jun 2006 A1
20060128395 Muhonen Jun 2006 A1
20060135177 Winterbottom Jun 2006 A1
20060188083 Breen Aug 2006 A1
20060193447 Schwartz Aug 2006 A1
20060239205 Warren Oct 2006 A1
20060250987 White Nov 2006 A1
20060258380 Liebowitz Nov 2006 A1
20060281437 Cook Dec 2006 A1
20060293024 Benco Dec 2006 A1
20060293066 Edge Dec 2006 A1
20070003024 Olivier Jan 2007 A1
20070019614 Hoffmann Jan 2007 A1
20070022011 Altberg Jan 2007 A1
20070026871 Wager Feb 2007 A1
20070027997 Polk Feb 2007 A1
20070036139 Patel Feb 2007 A1
20070041513 Gende Feb 2007 A1
20070049288 Lamprecht Mar 2007 A1
20070060097 Edge Mar 2007 A1
20070081635 Croak Apr 2007 A1
20070115941 Patel May 2007 A1
20070121601 Kikinis May 2007 A1
20070149213 Lamba Jun 2007 A1
20070160036 Smith Jul 2007 A1
20070162228 Mitchell Jul 2007 A1
20070201623 Hines Aug 2007 A1
20070206568 Silver Sep 2007 A1
20070206613 Silver Sep 2007 A1
20070242660 Xu Oct 2007 A1
20070263610 Mitchell Nov 2007 A1
20070270164 Maier Nov 2007 A1
20080037715 Prozeniuk Feb 2008 A1
20080045250 Hwang Feb 2008 A1
20080063153 Krivorot Mar 2008 A1
20080065775 Polk Mar 2008 A1
20080117859 Shahidi May 2008 A1
20080186164 Emigh Aug 2008 A1
20080214202 Toomey Sep 2008 A1
20080249967 Flinn Oct 2008 A1
20100119049 Clark May 2010 A1
Foreign Referenced Citations (3)
Number Date Country
WO0145342 Jun 2001 WO
WO2004025941 Mar 2004 WO
WO2005051033 Jun 2005 WO
Related Publications (1)
Number Date Country
20080057975 A1 Mar 2008 US