Location based geo-reminders

Information

  • Patent Grant
  • 9467810
  • Patent Number
    9,467,810
  • Date Filed
    Tuesday, October 21, 2014
    10 years ago
  • Date Issued
    Tuesday, October 11, 2016
    8 years ago
Abstract
Location based geo-reminding system retrieves, from a location based geo-reminder physical server, a current location of wireless client devices within a given area. The method accesses, from the location based geo-reminder physical server, a physical location based geo-reminder database comprising an identity of a trigger identifier and a limits of trigger identifier. Transmission of a location based geo-reminder message is initiated if the current location of a particular wireless client device is within a limits of restriction distance from a location of the identity of the trigger.
Description
BACKGROUND OF THE INVENTION

1. Field of the Invention


This invention relates generally to wireless communications. More particularly, it relates to location based services (LBS) and short messaging system (SMS) messaging.


2. Background


Personal data assistants and smart phones are becoming increasingly popular. Part of the appeal of such devices is the ability to execute applications that do a myriad of functions. Once of those functions is a reminder reminder function that can be programmed through an appropriate application. Users can program an appropriate application to provide an reminder in advance of a given event. For instance, a user can program their device to provide an reminder of a doctor's visit the following day, to provide an reminder that a bill is due within a few days, to provide an reminder that it is time to go to a business meeting, to provide an reminder that a library book is due for return, to provide an reminder that dry cleaning is ready for pick-up, etc.


Although time based reminders are known within the art, there is a need for a method and apparatus that allows for tying an reminder to a current location of a wireless user. This would provide an reminder when a user is at a location to address such an reminder.


SUMMARY OF THE INVENTION

In accordance with the principles of the present invention, a method of location based geo-reminders retrieves, from a location based geo-reminder physical server, a current location of a particular wireless client device within a given area. The method accesses, from the location based geo-reminder physical server, a physical location based geo-reminder database comprising an identity of a trigger identifier and a limits of trigger identifier. Transmission of a location based geo-reminder message is initiated if the current location of the particular wireless client device is within a limits of restriction distance from a location of the identity of the trigger.


In accordance with another aspect of the invention, a location based geo-reminder server includes a location access module to retrieve, from the location based geo-reminder physical server, a current location of a particular wireless client device within a given area. A location based geo-reminder database access module accesses, from the location based geo-reminder physical server, a physical location based geo-reminder database comprising an identity of a trigger identifier and a limits of trigger identifier. A location based geo-reminder module initiates generation of a location based geo-reminder message if the current location of the particular wireless client device is within a limits of trigger distance from a location of the identity of the trigger identifier.





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:



FIG. 1 shows a location based geo-reminder system, in accordance with the principles of the present invention.



FIG. 2 shows an example entry in the location based geo-reminder database shown in FIG. 1, in accordance with the principles of the present invention.



FIG. 3 shows an example map graphic displaying pins for a wireless device and information associated with a reminder target, in accordance with the principles of the present invention.



FIG. 4 shows an example flow chart for a process of triggering a location based geo-reminder message, in accordance with the principles of the present invention.





DETAILED DESCRIPTION OF ILLUSTRATIVE EMBODIMENTS

Existing technology relies on use of time-based tasks in a personal digital assistant (PDA) or similar device. Location based geo-reminders, or “Geo-reminders”, in accordance with the principles of the present invention add a location component to a task to be done when a subscriber is in a specified area.


Location-based reminders do not exist. Rather, conventional devices require a user to rely on memory or a scheduled reminder, which may be triggered based on a given time or date. But the present inventors have appreciated that the user might not be in the vicinity of a relevant location at the time that the reminder is issued to execute a given task.


Carrier customers currently must depend on visual cues or calendar-based based methods (e.g., memory, Post-it Notes, or calendar reminders) to remember to complete a task such as picking up their cleaning, scheduling a dentist appointment, stopping for groceries, or returning a book to the library.


The present invention provides location based geo-reminders, i.e., “Geo-reminders”. Geo-reminders allow a user to set up reminders to send an SMS to their cell phone when they are in the vicinity of a pre-defined location. Preferably, the distance defined by ‘vicinity’ with respect to the present invention is configurable, either by a system administrator or customized by the user.


For example, when a user is within one mile of the public library on Third and Pine, between the hours of 8:00 a.m. and 7:00 p.m., Monday thru Saturday, he or she will be sent a reminder to return checked out books.


The present invention uses both a web-based and a handset based interface for provisioning reminders.


Preferably, the interface allows a user to search by address and drop a reminder “pin” on a displayable map. This reminder “pin” preferably has attributes such as vicinity radius, and reminder text to be provided to the user, e.g., by SMS, IM, or similar messaging technology.


The reminder pin also preferably includes criteria, such as time of day, and day, that control the sending of an SMS or other reminder message. When a reminder is submitted, the solution will flag the cell site equipment that is in the vicinity of the pin. Any time your phone interacts with the cell site equipment the system will send a SMS to your cell phone with the reminder.


For example, the reminder to be sent might relate to the next time the user is within one mile of the public library on Third and Pine, between the hours of 8:00 a.m. and 7:00 p.m., Monday thru Saturday, remind me to return the books I have checked out.


Alternatively, and importantly, the geo-reminder allows a sender to remind another user based on a location and time. For instance, a husband or other pre-authorized sender might access an appropriate web page, or send an appropriate message instruction to a service provider, to establish a geo-reminder in another user's device. As an example, the husband might send a geo-reminder to his wife that when they get within two blocks of the grocery store on her way home to send her a message reminder (e.g., SMS, IM, etc.) to pick up some milk.


Using the present invention, users no longer need to rely on their memories or scheduled reminders. Instead, reminders are triggered not only based on time (or timeless), but importantly based on location, e.g., when the user is in the proximity of a task they are to complete.


The invention has particular relevance and use with a cell phone or personal digital assistant (PDA).


For instance, FIG. 1 shows a location based geo-reminder system, in accordance with the principles of the present invention.


In particular, the location based geo-reminder (LBGR) system 101 disclosed herein, can include a LBGR server 100, a location based geo-reminder database 110, a home location register (HLR) 120, a communication network 130, various messaging servers 142-146, a gateway 150, and a cellular tower 160. The LBGR system 101 disclosed herein can further include various wireless clients (WCs), such as in particular a cellular telephone 180a, a smart phone 180b, a personal data assistant 180c, and a laptop computer 180d (collectively and individually described herein as wireless client(s) 180).


LBGR server 100 provides the backbone for location monitoring and message remindering functions disclosed herein. In particular LBGR server 100 can access location based geo-reminder database 110 for parameters with which to base WC 180 monitoring, as well as limitations that dictate when a location based geo-reminder message is to be issued in the event that a WC 180 is in proximity to a particular location and/or another WC 180.


LBGR server 100 can access a location service, such as HLR 120. Each time a WC 180 registers call-routing information in HLR 120, the LBGR 100 can use a pre-set proximity value retrieved from location based geo-reminder database 110 to create a proximity-list of WCs 180 that are within a pre-defined distance, as defined in location based geo-reminder database 110. This LBGR system 101 then preferably compares the registered call-routing information for WC 180a with the proximity-list. If the registered WC's 180 call-routing is in the proximity-list, the PBPA 100 system then sends an appropriate location based reminder message (e.g., SMS, IM, etc.) to WC 180a remindering them to that they are in a vicinity of a pre-designated location or WC 180.


When a geo-reminder message is submitted by LBGR server 100, the cell tower 160 that is in the vicinity of an identity of a trigger, e.g., library pin 320, is flagged. Any time a WC 180 interacts with the flagged cell tower 160 the LBGR server 100 can send a geo-reminder message, e.g., SMS, to a WC 180.


Communication network 130 can be any digital communication network that allows LBGR server 100 to send an appropriate location based geo-reminder message. Communication network 130 is preferably an open IP based communication network, such as the Internet. Alternately, communication network 130 can be a closed IP based communication network, relying on locally assigned IP addresses. Irrespectively of the type of communication network 130 used, LPBA server 100 can communicate with any of a variety of messaging servers, such as e-mail server 142, Short Message Service (SMS) server 144, Instant Message (IM) server 146, etc. through IP packet addressing, as is known within the art.


Gateway 150 provides gateway functions to allow communication network 130 to send and receive digital data packets to and from cellular network 160. Cellular network 160 transits an appropriate location based geo-reminder message from any of e-mail server 142, Short Message Service (SMS) server 144, Instant Message (IM) server 146, etc. to a pre-designated WC 180 over communication network 130.


For example purposes only, WC 180a is shown as having an entry in the location based geo-reminder database 110. However, any number of WCs 180 can have simultaneously entries in the restraining order database 110. WC 180a is shown as having an entry in the location based geo-reminder database 110 that corresponds to the radius distance 184. The radius distance 184 can be a distance measured in any unit of measurement that allows for triggering of a location based geo-reminder message when a WC 180 is in a vicinity of a pre-designated WC 180 or geographic location. Radius distance 184 from WC 180a produces a reminder zone 182 around WC 180a.


In the example shown, WC 180a will receive a geo-reminder message associated with the pre-designated library 170. If LBGR server 100 determines that a library 170 is within radius distance 184 from WC 180a, LPBA server 100 triggers transmission of an appropriate location based geo-reminder message. As shown in more detail in FIG. 2, the specific type of location based geo-reminder message can be specified as an entry in the location based geo-reminder database 110.


Radius distance 184 is described above as producing a reminder zone 182 that when breached, e.g., by library 170, triggers an appropriate location based geo-reminder message. However, in an alternate embodiment radius distance 184 can be a reminder zone that when breached by another WC 180 will cause trigger of an appropriate location based geo-reminder message. In this type of embodiment, if WC 180a is the subject of a reminder message when another WC 180 comes within a pre-determined distance from WC 180a, an appropriate location based geo-reminder message will be transmitted to pre-designated messaging system, as defined in a location based geo-reminder database entry 200, shown in detail in FIG. 2.


Location based geo-reminder database 110 preferably is a highly secure database that requires encrypted and password protected access. Subscribers can be provided remote access to the location based geo-reminder database 110 through a secure digital connection. A web page can be used to populate the entries within the location based geo-reminder database 110, as well as review and correct the entries within the location based geo-reminder database 110. Although location based geo-reminder database 110 is shown as being accessible through communication network 130, within the principles disclosed herein location based geo-reminder database 110 can be integrated with the LBGR server 100.


Although the LBGR system 101 disclosed herein relies on access to a HLR to monitor the location of WCs 180, any of a number of location services can be employed to determine the location of WCs 180. Global Positioning System (GPS) is becoming commonly integrated in WCs 180 and can be used to directly provide location information for a WC 180 to LBGR server 100. Alternately, within the principles disclosed herein, cellular triangulation, signal strength monitoring, etc. can be used to provide location information for WCs 180 to LBGR server 100.



FIG. 2 shows an example entry 200 in the location based geo-reminder database 110 shown in FIG. 1, in accordance with the principles of the present invention.


In particular, entry 200 can include a requestor field 210, a time limits field 220, an identity of trigger field 230, limits of reminder field 240, and type of reminder field 250.


The example requestor field 210 is shown as being “John Doe”. However, the requestor field 210 can include anyone that has access to location based geo-reminders database 110. The requestor filed's 210 value can be transmitted to a WC 180 to convey who initiated a geo-reminder message.


The example time limits field 220 is shown as being “Sep. 1, 2009-Sep. 30, 2009”. However, the time limits field 220 can include specific times of a day, specific days of the week, specific months of the year, and even years of enforcement, all in accordance within the principles disclosed herein. For example, a subscriber of a WC 180 may only desire to have reminders issued during work hours for work related reminders, during non-work hours for non-work related reminders, during weekends when running errands, during evening commute times, etc. Depending upon the desires of a subscriber of a WC 180, the time limits field 220 can specify any time period the subscriber desires a location based geo-reminder message to be issued.


The example identity of trigger field 230 is shown as being “Library at 3rd and Main, Smallville, Va.”. However, in accordance with the principles disclosed herein the identity of trigger field 230 can include other WCs 180, telephone numbers, specific longitude(s) and latitude(s), ranges of longitudes and latitudes, names of geographic places that can be cross-referenced to their geographic locations, etc. The other WCs 180 can be identified by a MIN, telephone number, a name that is associated with a MIN and/or telephone number, etc.


The limits of reminder field 240 is shown as being “100 yards”. However, in accordance with the principles disclosed herein the limits of reminder field 240 can be a zero value requiring direct contact with the identity of the value associated with the identity of trigger field 230, can be a measurement in miles, a city limits value, a state value, etc.


The type of reminder field 250 is shown as being “SMS XXX-XXX-XXXX ‘Return Moby Dick to Library’”. However, in accordance with the principles disclosed herein the type of reminder field 250 can designate e-mail and an e-mail address, can designate IM and an IM address, can designate any desired telephone number to call, etc. Preferably, if LBGR server 100 dials a telephone number to provide an reminder of a location based geo-reminder, a pre-recorded geo-reminder message is played. Likewise, if LBGR server 100 transmits a geo-reminder message, the WC 180 can further be provided with an option to obtain directions to the geographic location and/or WC 180 associated with the geo-reminder message.


Alternately, within the scope of the principles disclosed herein the type of reminder field 250 can designate a list of reminder messages to transmit. The LBGR server 100 can use the designated list of reminder messages to trigger transmission of a plurality of location based geo-reminder messages in response to a single location based geo-reminder trigger. The type of reminder filed 250 can even include a MIN to assist in reaching a WC 180 in the event an alternate designated fails to reach the WC 180.



FIG. 3 shows an example map graphic displaying pins for a wireless device and information associated with a reminder reminder target, in accordance with the principles of the present invention.


In particular, the example map graphic 300 includes a WC pin 310, a library pin 320, a radius distance graphic 330, and a library information overlay 340.


WC pin 310 preferably is a moving pin whose position is continuously updated on map graphic 300, and other map graphics not shown. Surrounding WC pin 310 is a radius distance graphic 330. Preferably radius distance graphic 330 is continuous updated on map graphic 300, and other map graphics not shown, to display a reminder zone. Multiple radius distance graphics 330 can be displayed for a single WC pin 310 to provide an indication to a user of a WC 180 that they have multiple location based geo-reminders pre-configured. The radius distance 184 value used to size the radius distance graphic 330 is retrieved from an entry in location based geo-reminders database 110.


Radius distance graphic 330 can be viewable only when a WC 180 comes within a pre-designated distance from a pre-designated target. Alternately, radius distance graphic 330 can be visible continuously during display of map graphic 300.


Library pin 320 provides a visual representation of a pre-configured reminder entry from the location based geo-reminders database 110. The library pin's 320 location is preferably shown relative to the current location of a WC 180, shown as WC pin 310.


Either by user selection, automatically initiated when a WC 180 comes within radius distance 184, or viewable at all times library pin 320 is viewable, library information overlay 340 provides information related to library pin 320. The information shown as populating library information overlay 340 can be sourced from any combination of information entered by a user of a WC 180 establishing a location based geo-reminder in accordance with the principles disclosed herein, a mapping database having metadata associated with specific addresses, an Internet mapping service that provides mapping services, such as Mapquest and Google Maps, etc.


Whichever information source provides the information needed to populate the library information overlay 320, preferably a user of a WC 180 can configure the specific type of information displayed in the library information overlay 340. For example, a particular user of a WC 180 may only desire a telephone number to be displayed in library information overlay 320. An additional field within the location based geo-reminder database entry 200 can store configuration information to control the type of information provided to a user of a WC 180 in library information overlay 320.



FIG. 4 shows an example flow chart for a process of triggering a location based geo-reminder message 400, in accordance with the principles of the present invention.


At step 410, a determination is made of which WC(s) 180 exist within in a particular area. LBGR server 100 can access a HLR 120 to retrieve a list of WCs 180 and their respective locations that have registered call-routing information in the HLR 120.


At step 420, a determination is made if any of the WCs 180 that were determined to be within a particular area in step 410 have an entry in the location based geo-reminder database 110. LBGR server 100 can use the list of WCs 180, e.g., MINs, that were determined to be within a particular area in step 310 as a database query issued to location based geo-reminder database 110. Any matched WCs 180 returned from the database query provides a list of WC(s) 180 that have pre-established location based geo-reminders and their respective restrictions.


At step 430, a decision is made if the WC(s) 180 that has pre-established location based geo-reminders are in a vicinity of a pre-configured geographic location or another WC 180. LBGR server 100 can compare the current geographic location of the WC(s) 180 that have pre-established location based geo-reminders to the geographic location of the identity of the trigger, as retrieved from location based geo-reminder database 110. The identity of the trigger can be another WC 180 or geographic coordinates that correspond to, e.g., school, playground, daycare center, library, video rental store, etc.


If the result of the decision from step 430 is that a WC 180 is within a pre-determined distance from a pre-designated geographic location or another WC 180, step 430 branches to step 440. Otherwise, step 430 branches back to step 410 to continuously monitor for a location based geo-reminder.


At step 440, an appropriate location based geo-reminder message (e.g., SMS, IM, etc.) is transmitted to whatever reminder destination that is specified by the type of reminder field 250 in the location based geo-reminder database entry 200. The LBGR 100 server initiates transmission of an appropriate location based geo-reminder message to the type of reminder 250 destination that is associated with the WC(s) 180 that was determined to within a pre-designated vicinity of a pre-designated geographic location or another WC 180.


Step 440 branches back to the beginning of the process of triggering a location based geo-reminder message 400 to allow for continuous monitoring of location based geo-reminders, in accordance with the principles disclosed herein.


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 location based geo-reminders, comprising: accessing, from a physical location based geo-reminder database, a trigger identifier identifying a user-defined time at which a location based geo-reminder message regarding a user-defined task is to be transmitted; andtriggering transmission at said user-defined time of said location based geo-reminder message regarding a user-defined task, to a particular wireless client device, when said particular wireless client device interacts with a cellular tower when said wireless client device is within a pre-defined limit of restriction to a location defined for said location based geo-reminder message;wherein said pre-defined limit of restriction is identified by a pre-defined radius distance.
  • 2. The method of location based geo-reminders according to claim 1, wherein said trigger identifier comprises: a mobile identification number (MIN).
  • 3. The method of location based geo-reminders according to claim 1, wherein said trigger identifier comprises: a mobile telephone number.
  • 4. The method of location based geo-reminders according to claim 1, wherein said location based geo-reminder message comprises: an email message.
  • 5. A location based geo-reminder server, comprising: a physical location based geo-reminder database comprising a trigger identifier identifying a user-defined time at which a location based geo-reminder message regarding a user-defined task is to be transmitted; anda location based geo-reminder module to trigger transmission at said user-defined time of said location based geo-reminder message regarding a user-defined task, to a particular wireless client device, when said particular wireless client device interacts with a cellular tower when said wireless client device is within a pre-defined limit of restriction to a location defined for said location based geo-reminder message;wherein said pre-defined limit of restriction is identified by a pre-defined radius distance.
  • 6. The location based geo-reminder server according to claim 5, wherein said trigger identifier comprises: a mobile identification number (MIN).
  • 7. The location based geo-reminder server according to claim 5, wherein said trigger identifier comprises: a mobile telephone number.
  • 8. The location based geo-reminder server according to claim 5, wherein said location based geo-reminder message comprises: an email message.
  • 9. A method of location based geo-reminders, comprising: accessing, from a physical location based geo-reminder database, a trigger identifier identifying a user-defined time at which a location based geo-reminder message regarding a user-defined task is to be transmitted; andtriggering transmission at said user-defined time of said location based geo-reminder message regarding a user-defined task, to a particular wireless client device, when said particular wireless client device interacts with a cellular tower when said wireless client device is within a pre-defined limit of restriction to a location defined for said location based geo-reminder message;wherein said pre-defined limit of restriction is identified by a pre-defined reminder zone.
  • 10. The method of location based geo-reminders according to claim 9, wherein said trigger identifier comprises: a mobile identification number (MIN).
  • 11. The method of location based geo-reminders according to claim 9, wherein said trigger identifier comprises: a mobile telephone number.
  • 12. The method of location based geo-reminders according to claim 9, wherein said location based geo-reminder message comprises: an email message.
Parent Case Info

The present invention is a continuation of Ser. No. 12/588/331, entitled “Location Based Geo-Reminders”, filed on Oct. 13, 2009; which claims priority from U.S. Provisional Application 61/136,917, filed Oct. 14, 2008, entitled “LOCATION BASED GEO-REMINDERS”, to GEHRKE et al., the entirety of both of which are expressly incorporated herein by reference.

US Referenced Citations (408)
Number Name Date Kind
4445118 Taylor Apr 1984 A
4928107 Kuroda May 1990 A
4972484 Theile Nov 1990 A
5126722 Kamis Jun 1992 A
5283570 DeLuca Feb 1994 A
5301354 Schwendeman Apr 1994 A
5311516 Kuznicki May 1994 A
5327529 Fults Jul 1994 A
5335246 Yokev Aug 1994 A
5351235 Lahtinen Sep 1994 A
5365451 Wang Nov 1994 A
5418537 Bird May 1995 A
5422813 Schuchman Jun 1995 A
5479408 Will Dec 1995 A
5485163 Singer Jan 1996 A
5504491 Chapman Apr 1996 A
5506886 Maine Apr 1996 A
5517199 DiMattei May 1996 A
5530655 Lokhoff Jun 1996 A
5530914 McPheters Jun 1996 A
5539395 Buss Jul 1996 A
5539829 Lokhoff Jul 1996 A
5546445 Dennison Aug 1996 A
5568153 Beliveau Oct 1996 A
5583774 Diesel Dec 1996 A
5594780 Wiedeman Jan 1997 A
5606618 Lokhoff Feb 1997 A
5611050 Theimer Mar 1997 A
5629693 Janky May 1997 A
5633630 Park May 1997 A
5636276 Brugger Jun 1997 A
5661652 Sprague Aug 1997 A
5661755 Van de Kerkhof Aug 1997 A
5689245 Noreen Nov 1997 A
5699053 Jonsson Dec 1997 A
5704029 Wright, Jr. Dec 1997 A
5721781 Deo Feb 1998 A
5731785 Lemelson Mar 1998 A
5765152 Erickson Jun 1998 A
5771353 Eggleston Jun 1998 A
5774670 Montulli Jun 1998 A
5809415 Rossmann Sep 1998 A
5812086 Bertiger Sep 1998 A
5812087 Krasner Sep 1998 A
5841396 Krasner Nov 1998 A
5857201 Wright, Jr. Jan 1999 A
5864667 Barkan Jan 1999 A
5874914 Krasner Feb 1999 A
5896369 Warsta Apr 1999 A
5898391 Jefferies Apr 1999 A
5922074 Richard Jul 1999 A
5930250 Klok Jul 1999 A
5945944 Krasner Aug 1999 A
5946629 Sawyer Aug 1999 A
5950137 Kim Sep 1999 A
5960362 Grob Sep 1999 A
5983099 Yao Nov 1999 A
5999124 Sheynblat Dec 1999 A
6032051 Hall Feb 2000 A
6052081 Krasner Apr 2000 A
6058338 Agashe May 2000 A
6061018 Sheynblat May 2000 A
6064336 Krasner May 2000 A
6067045 Castelloe May 2000 A
6081229 Soliman Jun 2000 A
6085320 Kaliski, Jr. Jul 2000 A
6091956 Hollenberg Jul 2000 A
6118403 Lang Sep 2000 A
6121923 King Sep 2000 A
6124810 Segal Sep 2000 A
6131067 Girerd Oct 2000 A
6133874 Krasner Oct 2000 A
6134483 Vayanos Oct 2000 A
6147598 Murphy Nov 2000 A
6150980 Krasner Nov 2000 A
6154172 Piccionelli Nov 2000 A
6169901 Boucher Jan 2001 B1
6169902 Kawamoto Jan 2001 B1
6178506 Quick, Jr. Jan 2001 B1
6185427 Krasner Feb 2001 B1
6188354 Soliman Feb 2001 B1
6188909 Alanara Feb 2001 B1
6189098 Kaliski, Jr. Feb 2001 B1
6195555 Dent Feb 2001 B1
6195557 Havinis Feb 2001 B1
6204798 Fleming Mar 2001 B1
6205330 Winbladh Mar 2001 B1
6208290 Krasner Mar 2001 B1
6215441 Moeglein Apr 2001 B1
6239742 Krasner May 2001 B1
6247135 Feague Jun 2001 B1
6249873 Richard Jun 2001 B1
6253203 O'Flaherty Jun 2001 B1
6260147 Quick, Jr. Jul 2001 B1
6275692 Skog Aug 2001 B1
6275849 Ludwig Aug 2001 B1
6297768 Allen, Jr. Oct 2001 B1
6307504 Sheynblat Oct 2001 B1
6308269 Proidl Oct 2001 B2
6313786 Sheynblat Nov 2001 B1
6321257 Kotola Nov 2001 B1
6324524 Lent Nov 2001 B1
6327473 Soliman Dec 2001 B1
6333919 Gaffney Dec 2001 B2
6360093 Ross Mar 2002 B1
6360102 Havinis Mar 2002 B1
6363254 Jones Mar 2002 B1
6367019 Ansell Apr 2002 B1
6370389 Isomursu Apr 2002 B1
6377209 Krasner Apr 2002 B1
6397074 Pihl May 2002 B1
6400314 Krasner Jun 2002 B1
6400958 Isomursu Jun 2002 B1
6411254 Moeglein Jun 2002 B1
6421002 Krasner Jul 2002 B2
6430504 Gilbert Aug 2002 B1
6433734 Krasner Aug 2002 B1
6442391 Johansson Aug 2002 B1
6449473 Raivisto Sep 2002 B1
6449476 Hutchison, IV Sep 2002 B1
6456852 Bar Sep 2002 B2
6463272 Wallace Oct 2002 B1
6477150 Maggenti Nov 2002 B1
6505049 Dorenbosch Jan 2003 B1
6510387 Fuchs Jan 2003 B2
6512922 Burg Jan 2003 B1
6512930 Sandegren Jan 2003 B2
6515623 Johnson Feb 2003 B2
6519466 Pande Feb 2003 B2
6522682 Kohli Feb 2003 B1
6525687 Roy Feb 2003 B2
6525688 Chou Feb 2003 B2
6529829 Turetzky Mar 2003 B2
6531982 White Mar 2003 B1
6538757 Sansone Mar 2003 B1
6539200 Schiff Mar 2003 B1
6539304 Chansarkar Mar 2003 B1
6542464 Takeda Apr 2003 B1
6542734 Abrol Apr 2003 B1
6542743 Soliman Apr 2003 B1
6549776 Joong Apr 2003 B1
6549844 Egberts Apr 2003 B1
6556832 Soliman Apr 2003 B1
6560461 Fomukong May 2003 B1
6560534 Abraham May 2003 B2
6567035 Elliott May 2003 B1
6570530 Gaal May 2003 B2
6574558 Kohli Jun 2003 B2
6580390 Hay Jun 2003 B1
6584552 Kuno Jun 2003 B1
6594500 Bender Jul 2003 B2
6597311 Sheynblat Jul 2003 B2
6603973 Foladare Aug 2003 B1
6606495 Korpi Aug 2003 B1
6606554 Edge Aug 2003 B2
6609004 Morse Aug 2003 B1
6611757 Brodie Aug 2003 B2
6618670 Chansarkar Sep 2003 B1
6621452 Knockeart Sep 2003 B2
6628233 Knockeart Sep 2003 B2
6633255 Krasner Oct 2003 B2
6640184 Rabe Oct 2003 B1
6650288 Pitt Nov 2003 B1
6661372 Girerd Dec 2003 B1
6665539 Sih Dec 2003 B2
6665541 Krasner Dec 2003 B1
6670905 Orr Dec 2003 B1
6671620 Garin Dec 2003 B1
6677894 Sheynblat Jan 2004 B2
6680694 Knockeart Jan 2004 B1
6680695 Turetzky Jan 2004 B2
6690940 Brown Feb 2004 B1
6691019 Seeley Feb 2004 B2
6694258 Johnson Feb 2004 B2
6694351 Shaffer Feb 2004 B1
6697629 Grilli Feb 2004 B1
6698195 Hellinger Mar 2004 B1
6701144 Kirbas Mar 2004 B2
6703971 Pande Mar 2004 B2
6703972 van Diggelen Mar 2004 B2
6704651 Van Diggelen Mar 2004 B2
6707421 Drury Mar 2004 B1
6714793 Carey Mar 2004 B1
6721871 Piispanen Apr 2004 B2
6724342 Bloebaum Apr 2004 B2
6725159 Krasner Apr 2004 B2
6731940 Nagendran May 2004 B1
6734821 Van Diggelen May 2004 B2
6738013 Orler May 2004 B2
6738800 Aquilon May 2004 B1
6741842 Goldberg May 2004 B2
6745038 Callaway, Jr. Jun 2004 B2
6747596 Orler Jun 2004 B2
6748195 Phillips Jun 2004 B1
6751464 Burg Jun 2004 B1
6756938 Zhao Jun 2004 B2
6757544 Rangarajan Jun 2004 B2
6772340 Peinado Aug 2004 B1
6775655 Peinado Aug 2004 B1
6775802 Gaal Aug 2004 B2
6778136 Gronemeyer Aug 2004 B2
6778885 Agashe Aug 2004 B2
6781963 Crockett Aug 2004 B2
6788249 Farmer Sep 2004 B1
6795699 McCraw Sep 2004 B1
6799050 Krasner Sep 2004 B1
6801124 Naitou Oct 2004 B2
6801159 Swope Oct 2004 B2
6804524 Vandermeijden Oct 2004 B1
6807534 Erickson Oct 2004 B1
6810323 Bullock Oct 2004 B1
6813499 McDonnell Nov 2004 B2
6813560 van Diggelen Nov 2004 B2
6816111 Krasner Nov 2004 B2
6816710 Krasner Nov 2004 B2
6816719 Heinonen Nov 2004 B1
6816734 Wong Nov 2004 B2
6820069 Kogan Nov 2004 B1
6829475 Lee Dec 2004 B1
6832373 O'Neill Dec 2004 B2
6833785 Brown Dec 2004 B2
6839020 Geier Jan 2005 B2
6839021 Sheynblat Jan 2005 B2
6842715 Gaal Jan 2005 B1
6853849 Tognazzini Feb 2005 B1
6853916 Fuchs Feb 2005 B2
6856282 Mauro Feb 2005 B2
6859722 Jones Feb 2005 B2
6861980 Rowitch Mar 2005 B1
6865171 Nilsson Mar 2005 B1
6865395 Riley Mar 2005 B2
6867734 Voor Mar 2005 B2
6873854 Crockett Mar 2005 B2
6885940 Brodie Apr 2005 B2
6888497 King May 2005 B2
6888932 Snip May 2005 B2
6895238 Newell May 2005 B2
6895249 Gaal May 2005 B2
6895324 Straub May 2005 B2
6898633 Lyndersay May 2005 B1
6900758 Mann May 2005 B1
6903684 Simic Jun 2005 B1
6904029 Fors Jun 2005 B2
6907224 Younis Jun 2005 B2
6907238 Leung Jun 2005 B2
6912395 Benes Jun 2005 B2
6915208 Garin Jul 2005 B2
6917331 Gronemeyer Jul 2005 B2
6930634 Peng Aug 2005 B2
6937187 Van Diggelen Aug 2005 B2
6937872 Krasner Aug 2005 B2
6941144 Stein Sep 2005 B2
6944540 King Sep 2005 B2
6947772 Minear Sep 2005 B2
6950058 Davis Sep 2005 B1
6956467 Mercado, Jr. Oct 2005 B1
6957073 Bye Oct 2005 B2
6961562 Ross Nov 2005 B2
6965754 King Nov 2005 B2
6965767 Maggenti Nov 2005 B2
6970917 Kushwaha Nov 2005 B1
6973166 Tsumpes Dec 2005 B1
6973320 Brown Dec 2005 B2
6975266 Abraham Dec 2005 B2
6978453 Rao Dec 2005 B2
6980816 Rohles Dec 2005 B2
6985105 Pitt Jan 2006 B1
6985747 Chithambaram Jan 2006 B2
6996720 DeMello Feb 2006 B1
6999782 Shaughnessy Feb 2006 B2
7024321 Deninger Apr 2006 B1
7024393 Peinado Apr 2006 B1
7047411 DeMello May 2006 B1
7064656 Belcher Jun 2006 B2
7065351 Carter Jun 2006 B2
7065507 Mohammed Jun 2006 B2
7079857 Maggenti Jul 2006 B2
7082365 Sheha et al. Jul 2006 B2
7103018 Hansen Sep 2006 B1
7103574 Peinado Sep 2006 B1
7106717 Rousseau et al. Sep 2006 B2
7113128 Pitt Sep 2006 B1
7123874 Brennan Oct 2006 B1
7130644 Kuwahra et al. Oct 2006 B2
7136838 Peinado Nov 2006 B1
7151946 Maggenti Dec 2006 B2
7177623 Baldwin Feb 2007 B2
7209757 Naghian Apr 2007 B2
7209969 Lahti Apr 2007 B2
7218940 Niemenmaa May 2007 B2
7221959 Lindquist May 2007 B2
7269428 Wallenius Sep 2007 B1
7301494 Waters Nov 2007 B2
7440779 Kim Oct 2008 B2
7444342 Hall Oct 2008 B1
7565132 Ben Ayed Jul 2009 B2
7577522 Rosenberg Aug 2009 B2
7583972 Clipsham Sep 2009 B2
7629926 Pitt Dec 2009 B2
7792989 Toebes Sep 2010 B2
7848765 Phillips Dec 2010 B2
7864047 Aninye Jan 2011 B2
7890122 Walsh Feb 2011 B2
8000726 Altman et al. Aug 2011 B2
RE42927 Want Nov 2011 E
8065079 Rogers Nov 2011 B2
8170580 Dingler May 2012 B2
8200291 Steinmetz Jun 2012 B2
8307029 Davis et al. Nov 2012 B2
8359048 Riley Jan 2013 B2
8373588 Kuhn Feb 2013 B2
8396490 Platt et al. Mar 2013 B2
8483652 Hall Jul 2013 B2
8489669 Johnson Jul 2013 B2
8525681 Gehrke Sep 2013 B2
8559980 Pujol Oct 2013 B2
8682300 Stopel Mar 2014 B2
8686852 Ben-Dayan Apr 2014 B2
20010011247 O'Flaherty Aug 2001 A1
20020002036 Uehara Jan 2002 A1
20020037735 Maggenti Mar 2002 A1
20020038182 Wong Mar 2002 A1
20020052214 Maggenti May 2002 A1
20020061760 Maggenti May 2002 A1
20020069529 Wieres Jun 2002 A1
20020085538 Leung Jul 2002 A1
20020102999 Maggenti Aug 2002 A1
20020112047 Kushwaha Aug 2002 A1
20020116123 Lampe Aug 2002 A1
20020135504 Singer Sep 2002 A1
20020173317 Nykanen Nov 2002 A1
20020198632 Breed Dec 2002 A1
20030009602 Jacobs Jan 2003 A1
20030037163 Kitada Feb 2003 A1
20030044654 Holt Mar 2003 A1
20030065788 Salomaki Apr 2003 A1
20030078064 Chan Apr 2003 A1
20030081557 Mettala May 2003 A1
20030101329 Lahti May 2003 A1
20030101341 Kettler May 2003 A1
20030103484 Oommen Jun 2003 A1
20030114157 Spitz Jun 2003 A1
20030118160 Holt Jun 2003 A1
20030119528 Pew Jun 2003 A1
20030134648 Reed Jul 2003 A1
20030153340 Crockett Aug 2003 A1
20030153341 Crockett Aug 2003 A1
20030153342 Crockett Aug 2003 A1
20030153343 Crockett Aug 2003 A1
20030161298 Bergman Aug 2003 A1
20030186709 Rhodes Oct 2003 A1
20030204640 Sahinoja Oct 2003 A1
20030223381 Schroderus Dec 2003 A1
20040002326 Maher Jan 2004 A1
20040044623 Wake Mar 2004 A1
20040064550 Sakata Apr 2004 A1
20040068724 Gardner Apr 2004 A1
20040070515 Burkley Apr 2004 A1
20040077359 Bernas Apr 2004 A1
20040078694 Lester Apr 2004 A1
20040090121 Simonds May 2004 A1
20040176107 Chadha Sep 2004 A1
20040203876 Drawert Oct 2004 A1
20040204806 Chen Oct 2004 A1
20040205151 Sprigg Oct 2004 A1
20040209594 Naboulsi Oct 2004 A1
20040229632 Flynn Nov 2004 A1
20050003797 Baldwin Jan 2005 A1
20050020242 Holland Jan 2005 A1
20050028034 Gantman Feb 2005 A1
20050039178 Marolia Feb 2005 A1
20050041578 Huotari Feb 2005 A1
20050074107 Renner Apr 2005 A1
20050075116 Laird Apr 2005 A1
20050086467 Asokan Apr 2005 A1
20050112030 Gaus May 2005 A1
20050148346 Maloney Jul 2005 A1
20050209995 Aksu Sep 2005 A1
20050238156 Turner Oct 2005 A1
20050255853 Ewert Nov 2005 A1
20050259675 Tuohino Nov 2005 A1
20060010200 Mousseau Jan 2006 A1
20060053225 Poikselka Mar 2006 A1
20060058045 Nilsen Mar 2006 A1
20060058948 Blass Mar 2006 A1
20060212558 Sahinoja Sep 2006 A1
20060212562 Kushwaha Sep 2006 A1
20060234639 Kushwaha Oct 2006 A1
20060234698 Fok Oct 2006 A1
20070026854 Nath Feb 2007 A1
20070030539 Nath Feb 2007 A1
20070159322 Garratt Campbell Jul 2007 A1
20070201623 Hines Aug 2007 A1
20080032703 Krumm Feb 2008 A1
20080081641 Smith Apr 2008 A1
20080132251 Altman Jun 2008 A1
20080227467 Barnes Sep 2008 A1
20080268769 Brown Oct 2008 A1
20090029675 Steinmetz Jan 2009 A1
20090323636 Dillon Dec 2009 A1
20100167691 Howarter Jul 2010 A1
20100214149 Kuhn Aug 2010 A1
20110102232 Orr May 2011 A1
20110109468 Hirschfeld May 2011 A1
20120268306 Coburn Oct 2012 A1
20130009760 Washlow Jan 2013 A1
20130281129 Laine Oct 2013 A1
20140099921 Weiss Apr 2014 A1
Non-Patent Literature Citations (3)
Entry
International Search Report received in PCT/US2011/001990 dated Apr. 24, 2012.
International Search Report Received in PCT/US11/01971 dated Feb. 28, 2013.
Search Report received in European Appl. No. 07751688.8 dated Oct. 22, 2012.
Related Publications (1)
Number Date Country
20150057029 A1 Feb 2015 US
Provisional Applications (1)
Number Date Country
61136917 Oct 2008 US
Continuations (1)
Number Date Country
Parent 12588331 Oct 2009 US
Child 14519279 US