Mobile device tracking using mobile agent location breadcrumbs

Information

  • Patent Grant
  • 7860517
  • Patent Number
    7,860,517
  • Date Filed
    Friday, December 22, 2006
    18 years ago
  • Date Issued
    Tuesday, December 28, 2010
    14 years ago
Abstract
A method, a computer readable medium and a system for using a mobile agent to track a mobile device using a plurality of location breadcrumbs in an environment where network access may be unreliable, comprising, registering with a tracking server by a tracking client to receive a location of the mobile agent, receiving a location breadcrumb by the tracking server from the mobile agent, and reporting the location of the mobile agent by the tracking server to the tracking client.
Description
BACKGROUND

An advanced object-oriented computing concept is mobile agent technology. The computer science definition of a mobile agent is a composition of computer software and data which is able to migrate from one computer to another autonomously and continue its execution on the destination computer. The embodiment of a mobile agent refers to a process that can transport its state from one environment to another, with its data intact, and still be able to perform appropriately in the new environment. When a mobile agent decides to move, it saves its own state, transports this saved state to next host, and resumes execution from the saved state.


Location Based Services (LBS) is a growing technology commonly used by mobile network service providers to send information to subscribers that is customized for their location. Paramount to LBS is ability to locate subscribers, and this generally requires input from the mobile device. The predominant location technologies include the Global Positioning System (GPS) and cellular radiolocation. An advancing technology that is gaining momentum is the use of radiolocation in Wireless Fidelity (Wi-Fi) networks.


GPS is a fully functional satellite navigation system that broadcasts precise radio timing signals to ground based GPS receivers. GPS technology allows a receiver to accurately determine its latitude, longitude and altitude, in any weather, day or night, anywhere on Earth. Advanced GPS techniques can enhance the accuracy of location detection to within one centimeter.


In general, radiolocation is the process of locating something through the use of radio waves by analyzing the angle and period of radio signals traveling between a radio receiver and transmitter. In cellular network, the signal strength, the time of arrival, and the angle of arrival of radio waves traveling between a mobile device and a fixed location base station (also referred to a “cell site”) can be used to approximate the location of a mobile device. When multiple cell sites are in communication with the device, triangulation, trilateration or multilateration (also known as “hyperbolic positioning”) techniques can be locating the device.


Radiolocation can location of devices operating Interoperability for Microwave technique is less effective used to increase the accuracy of also be used to determine the in a Wi-Fi or WiMAX (Worldwide Access) network. However, this in Wi-Fi networks because the location of wireless access points (WAPs) are not necessarily known or fixed. As urban communities add public wireless networks to their infrastructure and record the location of their WAPs, the techniques of radiolocation can be readily applied to Wi-Fi and WiMAX devices.


“Breadcrumbs” (or breadcrumb trails) are a simple navigation technique used to keep track of a subject's path as it traverses from one location to another. The technique takes its name from the bread crumb trail left by Hansel and Gretel in the popular Brothers Grimm fairy tale, “Hansel and Gretel”.





BRIEF DESCRIPTION OF THE DRAWINGS


FIG. 1 illustrates a process for deploying a mobile agent to a mobile device according to one or more embodiments;



FIG. 2 illustrates a client registration with a tracking server to receive a periodic location update for a mobile agent in accordance with one or more embodiments;



FIG. 3 illustrates a client on-demand request to receive a mobile agent location from a tracking server in accordance with one or more embodiments;



FIG. 4 illustrates a tracking server reporting a location of a predictable mobile agent to a tracking client based on location breadcrumb analysis in accordance with one or more embodiments;



FIG. 5 illustrates a tracking server reporting a location of an unpredictable mobile agent to a tracking client based on location breadcrumb analysis in accordance with one or more embodiments; and



FIG. 6 illustrates a tracking server reporting a location of an unpredictable mobile agent to a tracking client based on historical location breadcrumb analysis in accordance with one or more embodiments.





DETAILED DESCRIPTION
Mobile Agent Deployment

Mobile agent deployment to a mobile device can precede mobile agent location tracking. To form a basis for articulating one or more embodiments, a process for deploying a mobile agent is presented.


Referring to FIG. 1, in accordance with one or more embodiments, system 100 creates a mobile agent 120. Mobile agent 120 is deployed to mobile device 130 via a connection through network 110. Mobile agent 120 is capable of working with the LBS and communication capabilities available on mobile device 130, and mobile device 130 is capable of receiving, establishing and executing mobile agent 120. Mobile agent 120 is configured with a prioritized list of well known tracking servers to which it will report, one of which may include system 100. In addition, mobile agent 120 is configured with a maximum reporting interval that may be any unit of time suitable for the application and for the supporting infrastructure. Finally, mobile agent 120 is given a preferred location itinerary (or route) that can be made available to host device 130.


Additional network configuration methods for deploying mobile agents may be utilized. These methods may include, but are not limited to, deployment via wireless area network (WLAN) connection, deployment via satellite connection, deployment via data connection over a cellular network, or deployment via other computer readable media such as disk drives, optical drives and pluggable memory devices.


One or more embodiments describe methods for using a mobile agent to track a mobile device using a plurality of location breadcrumbs in an environment where network access may be unreliable, comprising, registering with a tracking server by a tracking client to receive a location of the mobile agent, receiving a location breadcrumb by the tracking server from the mobile agent, and reporting the location of the mobile agent by the tracking server to the tracking client.


In one or more embodiments, a computer readable medium comprises instructions for: registering with a tracking server by a tracking client to receive a location of a mobile agent; receiving a location breadcrumbs by the tracking server from the mobile agent, wherein the location breadcrumb comprises a location of the mobile agent, a time the location was valid, and an itinerary of the mobile agent; predicting the location of the mobile agent using at least one of, a database of one or more location breadcrumbs, and a database of historical accuracy; and reporting the location of the mobile agent by the tracking server to the tracking client.


One or more embodiments include a system for using a mobile agent to track a mobile device using a plurality of location breadcrumbs in an environment where network access may be unreliable, comprising: a memory that stores a tracking client registration and at least one of, a database of one or more mobile agent location breadcrumbs, and a database of historical accuracy; a first processor communicably coupled to the memory, wherein the processor responds to the tracking client registration, receives a mobile agent location breadcrumb, predicts the location of the mobile agent to the tracking client, and reports the location of the mobile agent to the tracking client; and a second processor communicably coupled to the first processor, wherein the processor reports the location breadcrumb to the first processor.


Client Location Requests


Referring to FIG. 2, in accordance with one or more embodiments, client system 200 registers with mobile agent tracking server 220 to receive location breadcrumbs. Registration data 210 provided by client 200 includes a network address of the client, an identity of a subject mobile agent and a reporting interval.


Referring to FIG. 3, in accordance with one or more embodiments, client system 300 requests an on-demand location update from mobile agent tracking server 320. Client 300 provides an identity 310 of a subject mobile agent. Server 320 responds with location update 330.


Location Breadcrumb Tracking


Referring to FIG. 4, in accordance with one or more embodiments, tracking server 420 maintains a breadcrumb database 425 of reported mobile agent breadcrumbs that include time and itinerary. At the expiry of its reporting interval, mobile agent 400 uses a LBS mechanism of its host device to obtain location breadcrumb 410. Mobile agent 400 reports location breadcrumb 410 to tracking server 420 via an available host device network connection. Location breadcrumb 410 identifies an actual location (illustrated as (1, 4)) at time C, and it also identifies an itinerary for its next location (illustrated as (2, 6)) at time D. Tracking server 420 updates its breadcrumb database 425 with location breadcrumb 410.


Approaching time D, tracking client 440 requests the location of mobile agent 400 from tracking server 420. However, mobile agent 400 has not recently reported its position due to a lack of network availability. Using its breadcrumb database 425, tracking server 420 estimates that mobile agent 400 should be near location (2, 6) at time D. Since previous reports by mobile agent 400 matched its itinerary, and since it is not quite time D, tracking server 420 places an 85% degree of certainty on this estimate (an unscientific number chosen to reify this example). Tracking server 420 responds to client 440 by reporting a last known location and estimated location 430 of mobile agent 400.


Referring to FIG. 5, in accordance with one or more embodiments, tracking server 520 maintains a breadcrumb database 525 of reported mobile agent breadcrumbs that include time and itinerary. At the expiry of its reporting interval, mobile agent 500 uses a LBS mechanism of its host device to obtain location breadcrumb 510. Mobile agent 500 reports location breadcrumb 510 to tracking server 520 via an available host device network connection. Location breadcrumb 510 identifies an actual location (illustrated as (1, 5)) at time C, and it also identifies an itinerary for its next location (illustrated as (2, 6)) at time D. Tracking server 520 updates its breadcrumb database 525 with location breadcrumb 510. Tracking server 520 observes that mobile agent 500's actual location at time C differs from a previous itinerary which indicated mobile agent 500 would be at position (1,4) at time C, not at position (1,5).


Approaching time D, tracking client 540 requests the location of mobile agent 500 from tracking server 520. However, mobile agent 500 has not recently reported its position due to a lack of network availability. Using its breadcrumb database 525, tracking server 520 estimates that mobile agent 500 should be near location (2, 6) at time D. Since previous reports by mobile agent 500 have differed from the itinerary, and since it is not quite time D, tracking server 520 places a 70% degree of certainty on this estimate (an unscientific number chosen to reify this example). Tracking server 520 responds to client 540 by reporting the last known location and estimated location 530 of mobile agent 500.


Referring to FIG. 6, in accordance with one or more embodiments, tracking server 620 maintains a breadcrumb database 625 of reported mobile agent breadcrumbs that include time, itinerary, and historical data. Historical data is represented in FIG. 6 by a simple number that describes tracking accuracy against a plurality of previous itineraries for a given location; however, mobile agent history may be represented by a more sophisticated collection of data. At the expiry of its reporting interval, mobile agent 600 uses a LBS mechanism of its host device to obtain location breadcrumb 610. Mobile agent 600 reports location breadcrumb 610 to tracking server 620 via an available host device network connection. Location breadcrumb 610 identifies an actual location (illustrated as (1, 5)) at time C. Tracking server 620 updates its breadcrumb database 625 with location breadcrumb 610.


Approaching time D, tracking client 640 requests the location of mobile agent 600 from tracking server 620. However, mobile agent 600 has not recently reported its position due to a lack of network availability. Using its breadcrumb database 625 (with history data), tracking server 620 estimates that mobile agent 600 should be near location (2, 6) at time D. Since the accuracy of previous reports by mobile agent 600 have historically differed from the itinerary for this location, tracking server 620 places a 50% degree of certainty on this estimate (an unscientific number chosen to reify this example). Tracking server 620 responds to client 640 by reporting the last known location and estimated location 630 of mobile agent 600.


CONCLUSION

Systems, methods, devices and computer readable media have been shown and/or described in the above embodiments for using a mobile agent to track a mobile device using a plurality of location breadcrumbs in an environment where network access may be unreliable. Although the above descriptions set forth particular embodiments, it will be understood that this is not intended to be limiting. For example, one or more embodiments are not limited to the communication technologies presented herein, and future LBS technologies should not be precluded. Furthermore, the simplified data forms used to represent location, itinerary and history in these embodiments should not be assumed to represent limitations of the location breadcrumbs described by one or more embodiments. Lastly, one or more embodiments are intended to cover capabilities and concepts whether they are via a loosely coupled set of components or converged into one or more integrated components, devices, circuits, and/or software programs.

Claims
  • 1. A non-transitory computer readable medium having stored thereon, computer-executable instructions that, responsive to execution by a computing device, cause the computing device to perform operations comprising: receiving, from a tracking client, a registration to receive a location of a mobile agent;receiving a location breadcrumb from the mobile agent;storing, in a database, historical accuracy data that includes tracking accuracy of previous location breadcrumbs of the mobile agent and associated itineraries of the mobile agent; andreporting the location of the mobile agent to the tracking client.
  • 2. The non-transitory computer readable medium of claim 1, wherein receiving the registration includes receiving a network address of the tracking client, an identity of the mobile agent, and a reporting interval.
  • 3. The non-transitory computer readable medium of claim 2, wherein the computer-executable instructions, responsive to execution by the computing device, cause the computing device to perform operations further comprising: reporting the location of the mobile agent to the tracking client by at least one of: an expiry of the reporting interval; oron demand.
  • 4. The non-transitory computer readable medium of claim 3, wherein the computer-executable instructions, responsive to execution by the computing device, cause the computing device to perform operations further comprising associating a degree of certainty with the location reported to the tracking client.
  • 5. The non-transitory computer readable medium of claim 1, wherein receiving the location breadcrumb includes receiving an actual location of the mobile agent, a time the actual location was valid, and an itinerary of the mobile agent.
  • 6. The non-transitory computer readable medium of claim 5, wherein the computer-executable instructions, responsive to execution by the computing device, cause the computing device to perform operations further comprising storing, in the database, location breadcrumbs reported by one or more mobile agents.
  • 7. The non-transitory computer readable medium of claim 6, wherein the computer-executable instructions, responsive to execution by the computing device, cause the computing device to perform operations further comprising inspecting the database to predict the location of the mobile agent.
  • 8. The non-transitory computer readable medium of claim 6, wherein storing the historical accuracy data comprises storing historical accuracy data that correlates the actual location of the mobile agent with the itinerary of the mobile agent.
  • 9. The non-transitory computer readable medium of claim 8, wherein the computer-executable instructions, responsive to execution by the computing device, cause the computing device to perform operations further comprising inspecting the database to predict the location of the mobile agent.
  • 10. A non-transitory computer readable medium having stored thereon, computer-executable instructions that, responsive to execution by a computing device, cause the computing device to perform operations comprising: receiving a registration from a tracking client to receive a location of a mobile agent;receiving a location breadcrumb from the mobile agent, wherein the location breadcrumb comprises the location of the mobile agent, a time the location was valid, and an itinerary of the mobile agent;predicting the location of the mobile agent using at least one of: a database of one or more location breadcrumbs; ora database of historical accuracy;associating a degree of certainty with a predicted location of the mobile agent by using at least one of: the database of one or more location breadcrumbs to account for differences between previous location breadcrumbs of the mobile agent and the itinerary of the mobile agent; orthe database of historical accuracy to account for levels of accuracy between the itinerary of the mobile agent and previous location breadcrumbs of the mobile agent; andreporting the location of the mobile agent to the tracking client.
  • 11. The non-transitory computer readable medium of claim 10, wherein the computer-executable instructions, responsive to execution by the computing device, cause the computing device to perform operations further comprising: retaining registration data for the tracking client, wherein the registration data comprises a network address, an identity of the mobile agent, and a reporting interval.
  • 12. The non-transitory computer readable medium of claim 11, wherein the computer-executable instructions, responsive to execution by the computing device, cause the computing device to perform operations further comprising: causing establishment of a network connection to the tracking client;reporting, using the network connection, the location of the mobile agent to the tracking client by at least one of: an expiry of the reporting interval; oron demand.
  • 13. The non-transitory computer readable medium of claim 10, wherein the computer-executable instructions, responsive to execution by the computing device, cause the computing device to perform operations further comprising: receiving the location breadcrumb from the mobile agent via a network connection.
  • 14. The non-transitory computer readable medium of claim 10, wherein the computer-executable instructions, responsive to execution by the computing device, cause the computing device to perform operations further comprising: storing the location breadcrumb received from the mobile agent in the database of one or more location breadcrumbs.
  • 15. The non-transitory computer readable medium of claim 14, wherein the computer-executable instructions, responsive to execution by the computing device, cause the computing device to perform operations further comprising: analyzing the database of one or more location breadcrumbs to predict the location of the mobile agent.
  • 16. The non-transitory computer readable medium of claim 10, wherein the computer-executable instructions, responsive to execution by the computing device, cause the computing device to perform operations further comprising: correlating an actual location of the mobile agent with the itinerary of the mobile agent in the database of historical accuracy.
  • 17. The non-transitory computer readable medium of claim 16, wherein the computer-executable instructions, responsive to execution by the computing device, cause the computing device to perform operations further comprising: analyzing the database of historical accuracy to predict the location of the mobile agent.
  • 18. A system, comprising: a non-transitory computer-readable memory configured to store a registration of a tracking client and at least one of: a database of one or more location breadcrumbs associated with at least one mobile agent; ora database of historical accuracy;a processor configured to be communicably coupled to the memory, wherein the processor is configured to: respond to the tracking client registration;receive a location breadcrumb;predict a location of the at least one mobile agent to the tracking client;associate a degree of certainty with a predicted location of the at least one mobile agent by using at least one of: the database of one or more location breadcrumbs to account for differences between previous location breadcrumbs of the at least one mobile agent and an itinerary of the at least one mobile agent; orthe database of historical accuracy to account for levels of accuracy between the itinerary of the at least one mobile agent and previous location breadcrumbs of the at least one mobile agent; andreport the location of the at least one mobile agent to the tracking client.
  • 19. The system of claim 18, wherein the processor is configured to access the memory to query at least one of: the database of one or more location breadcrumbs; orthe database of historical accuracy.
  • 20. The system of claim 18, wherein the processor is configured to: cause establishment of a network connection to the tracking client.
US Referenced Citations (207)
Number Name Date Kind
4714995 Materna et al. Dec 1987 A
5465111 Fukushima et al. Nov 1995 A
5495533 Linehan et al. Feb 1996 A
5524253 Pham et al. Jun 1996 A
5604800 Johnson et al. Feb 1997 A
5675711 Kephart et al. Oct 1997 A
5721912 Stepczyk et al. Feb 1998 A
5778395 Whiting et al. Jul 1998 A
5812997 Morimoto et al. Sep 1998 A
5859911 Angelo et al. Jan 1999 A
5930798 Lawler et al. Jul 1999 A
5982891 Ginter et al. Nov 1999 A
6038500 Weiss Mar 2000 A
6055562 Devarakonda et al. Apr 2000 A
6065040 Mima et al. May 2000 A
6088689 Kohn et al. Jul 2000 A
6113650 Sakai Sep 2000 A
6134580 Tahara et al. Oct 2000 A
6134660 Boneh et al. Oct 2000 A
6154777 Ebrahim Nov 2000 A
6172986 Watanuki et al. Jan 2001 B1
6199195 Goodwin et al. Mar 2001 B1
6202060 Tran Mar 2001 B1
6209124 Vermeire et al. Mar 2001 B1
6230309 Turner et al. May 2001 B1
6233601 Walsh May 2001 B1
6256773 Bowman-Amuah Jul 2001 B1
6272478 Obata et al. Aug 2001 B1
6282563 Yamamoto et al. Aug 2001 B1
6282697 Fables et al. Aug 2001 B1
6304556 Haas Oct 2001 B1
6330677 Madoukh Dec 2001 B1
6343265 Glebov et al. Jan 2002 B1
6349343 Foody et al. Feb 2002 B1
6389462 Cohen et al. May 2002 B1
6438744 Toutonghi et al. Aug 2002 B2
6442537 Karch Aug 2002 B1
6452910 Vij et al. Sep 2002 B1
6477372 Otting et al. Nov 2002 B1
6496871 Jagannathan et al. Dec 2002 B1
6600430 Minagawa et al. Jul 2003 B2
6600975 Moriguchi et al. Jul 2003 B2
6611516 Pirkola et al. Aug 2003 B1
6629032 Akiyama Sep 2003 B2
6629128 Glass Sep 2003 B1
6662642 Breed et al. Dec 2003 B2
6671680 Iwamoto et al. Dec 2003 B1
6687761 Collins et al. Feb 2004 B1
6701381 Hearne et al. Mar 2004 B2
6714844 Dauner et al. Mar 2004 B1
6738975 Yee et al. May 2004 B1
6744352 Lesesky et al. Jun 2004 B2
6744358 Bollinger Jun 2004 B1
6744820 Khairallah et al. Jun 2004 B1
6768417 Kuragaki et al. Jul 2004 B2
6816452 Maehata Nov 2004 B1
6831375 Currie et al. Dec 2004 B1
6851108 Syme Feb 2005 B1
6862443 Witte Mar 2005 B2
6876845 Tabata et al. Apr 2005 B1
6879570 Choi Apr 2005 B1
6895391 Kausik May 2005 B1
6901588 Krapf et al. May 2005 B1
6904593 Fong et al. Jun 2005 B1
6931455 Glass Aug 2005 B1
6931623 Vermeire et al. Aug 2005 B2
6947965 Glass Sep 2005 B2
6951021 Bodwell et al. Sep 2005 B1
6957439 Lewallen Oct 2005 B1
6963582 Xu Nov 2005 B1
6981150 Little et al. Dec 2005 B2
6985929 Wilson et al. Jan 2006 B1
6993774 Glass Jan 2006 B1
7010689 Matyas, Jr. et al. Mar 2006 B1
7043522 Olson et al. May 2006 B2
7047518 Little et al. May 2006 B2
7055153 Beck et al. May 2006 B2
7058645 Seto et al. Jun 2006 B2
7062708 Mani et al. Jun 2006 B2
7069551 Fong et al. Jun 2006 B2
7127259 Ueda et al. Oct 2006 B2
7127724 Lewallen Oct 2006 B2
7146614 Nikols et al. Dec 2006 B1
7146618 Mein et al. Dec 2006 B1
7172113 Olenick et al. Feb 2007 B2
7174533 Boucher Feb 2007 B2
7197742 Arita et al. Mar 2007 B2
7210132 Rivard et al. Apr 2007 B2
7213227 Kompalli et al. May 2007 B2
7225425 Kompalli et al. May 2007 B2
7228141 Sethi Jun 2007 B2
7231403 Howitt et al. Jun 2007 B1
7237225 Kompalli et al. Jun 2007 B2
7293261 Anderson et al. Nov 2007 B1
7376959 Warshavsky et al. May 2008 B2
7475107 Maconi et al. Jan 2009 B2
7477897 Bye Jan 2009 B2
7496637 Han et al. Feb 2009 B2
7499990 Tai et al. Mar 2009 B1
7502615 Wilhoite et al. Mar 2009 B2
7506309 Schaefer Mar 2009 B2
7519455 Weiss et al. Apr 2009 B2
7566002 Love et al. Jul 2009 B2
7643447 Watanuki et al. Jan 2010 B2
7660777 Hauser Feb 2010 B1
7660780 Patoskie Feb 2010 B1
7664721 Hauser Feb 2010 B1
7698243 Hauser Apr 2010 B1
7702602 Hauser Apr 2010 B1
7702603 Hauser Apr 2010 B1
7702604 Hauser Apr 2010 B1
7774789 Wheeler Aug 2010 B1
7810140 Lipari et al. Oct 2010 B1
7823169 Wheeler Oct 2010 B1
20010029526 Yokoyama et al. Oct 2001 A1
20010051515 Rygaard Dec 2001 A1
20010056425 Richard Dec 2001 A1
20020032783 Tuatini Mar 2002 A1
20020035429 Banas Mar 2002 A1
20020091680 Hatzis et al. Jul 2002 A1
20020115445 Myllymaki Aug 2002 A1
20020116454 Dyla et al. Aug 2002 A1
20020159479 Watanuki et al. Oct 2002 A1
20020174222 Cox Nov 2002 A1
20020196771 Vij et al. Dec 2002 A1
20030009539 Hattori Jan 2003 A1
20030018950 Sparks et al. Jan 2003 A1
20030023573 Chan et al. Jan 2003 A1
20030033437 Fischer et al. Feb 2003 A1
20030046377 Daum et al. Mar 2003 A1
20030046432 Coleman et al. Mar 2003 A1
20030051172 Lordermann et al. Mar 2003 A1
20030055898 Yeager et al. Mar 2003 A1
20030070071 Riedel et al. Apr 2003 A1
20030101441 Harrison, et al. May 2003 A1
20030177170 Glass Sep 2003 A1
20030191797 Gurevich et al. Oct 2003 A1
20030191969 Katsikas Oct 2003 A1
20030225789 Bussler et al. Dec 2003 A1
20030225935 Rivard et al. Dec 2003 A1
20040003243 Fehr et al. Jan 2004 A1
20040015539 Alegria et al. Jan 2004 A1
20040037315 Delautre et al. Feb 2004 A1
20040044985 Kompalli et al. Mar 2004 A1
20040044986 Kompalli et al. Mar 2004 A1
20040044987 Kompalli et al. Mar 2004 A1
20040064503 Karakashian et al. Apr 2004 A1
20040078423 Satyavolu et al. Apr 2004 A1
20040078687 Partamian et al. Apr 2004 A1
20040082350 Chen et al. Apr 2004 A1
20040088369 Yeager et al. May 2004 A1
20040111730 Apte Jun 2004 A1
20040133656 Butterworth et al. Jul 2004 A1
20040148073 Hawig et al. Jul 2004 A1
20040172614 Gallagher Sep 2004 A1
20040194072 Venter Sep 2004 A1
20040203731 Chen et al. Oct 2004 A1
20040220952 Cheenath Nov 2004 A1
20040221292 Chiang et al. Nov 2004 A1
20050004727 Remboski et al. Jan 2005 A1
20050030202 Tsuboi Feb 2005 A1
20050090279 Witkowski et al. Apr 2005 A9
20050114832 Manu May 2005 A1
20050141706 Regli et al. Jun 2005 A1
20050144218 Heintz Jun 2005 A1
20050163549 Shima et al. Jul 2005 A1
20050172123 Carpentier et al. Aug 2005 A1
20050246302 Lorenz et al. Nov 2005 A1
20050256614 Habermas Nov 2005 A1
20050256876 Eidson Nov 2005 A1
20050262155 Kress et al. Nov 2005 A1
20050281363 Qi et al. Dec 2005 A1
20060005177 Atkin et al. Jan 2006 A1
20060031850 Falter et al. Feb 2006 A1
20060040640 Thompson et al. Feb 2006 A1
20060041337 Augsburger et al. Feb 2006 A1
20060048145 Celli et al. Mar 2006 A1
20060080646 Aman Apr 2006 A1
20060090103 Armstrong et al. Apr 2006 A1
20060111089 Winter et al. May 2006 A1
20060112183 Corson et al. May 2006 A1
20060121916 Aborn Jun 2006 A1
20060123396 Fox et al. Jun 2006 A1
20060143600 Cottrell et al. Jun 2006 A1
20060149746 Bansod et al. Jul 2006 A1
20060167981 Bansod et al. Jul 2006 A1
20060173857 Jackson Aug 2006 A1
20060190931 Scott et al. Aug 2006 A1
20060200494 Sparks Sep 2006 A1
20060206864 Shenfield et al. Sep 2006 A1
20060220900 Ceskutti et al. Oct 2006 A1
20060221901 Yaqub et al. Oct 2006 A1
20060245406 Shim Nov 2006 A1
20060256006 Nylen Nov 2006 A1
20060256008 Rosenberg Nov 2006 A1
20060272002 Wightman et al. Nov 2006 A1
20070004432 Hwang et al. Jan 2007 A1
20070015495 Winter et al. Jan 2007 A1
20070026871 Wager Feb 2007 A1
20070103292 Burkley et al. May 2007 A1
20070112773 Joyce May 2007 A1
20070223432 Badarinath Sep 2007 A1
20070243880 Gits et al. Oct 2007 A1
20080077667 Hwang et al. Mar 2008 A1
20100161543 Hauser Jun 2010 A1
20100223210 Patoskie Sep 2010 A1
20100235459 Wheeler Sep 2010 A1
Foreign Referenced Citations (1)
Number Date Country
2005190103 Jul 2005 JP