Browse Prior Art Database

Method for Entropy Base Revitalization Calendar Event Scheduling

IP.com Disclosure Number: IPCOM000111732D
Original Publication Date: 1994-Mar-01
Included in the Prior Art Database: 2005-Mar-26
Document File: 2 page(s) / 79K

Publishing Venue

IBM

Related People

Williams, ML: AUTHOR

Abstract

Recent advancements in Personal Digital Assistants (PDAs), notebooks, laptops, etc., have provided users with methods for transporting their electronic office. Recent products provide methods by which the software can notify the user as to the battery power level. These products, typically, provide a local warning that the battery strength is diminishing. However, such conditions do not directly inform the user of recharging times or intervals required for recharging. More specifically, no reminder is generated for recharging. There are a series of problems for which an event or activity implies a known expenditure of energy or resource for which will subsequently need to be replenished.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 52% of the total text.

Method for Entropy Base Revitalization Calendar Event Scheduling

      Recent advancements in Personal Digital Assistants (PDAs),
notebooks, laptops, etc., have provided users with methods for
transporting their electronic office.  Recent products provide
methods by which the software can notify the user as to the battery
power level.  These products, typically, provide a local warning that
the battery strength is diminishing.  However, such conditions do not
directly inform the user of recharging times or intervals required
for recharging.  More specifically, no reminder is generated for
recharging.  There are a series of problems for which an event or
activity implies a known expenditure of energy or resource for which
will subsequently need to be replenished.

      Example: Consider an enterprise that shares electronic
notebooks.  Users coordinate their use of a notebook via an
electronic calendar.  One user has scheduled the resource; however,
no indication is given to the energy level of the battery.
Subsequent users may get an electronic notebook with the battery at
an unacceptable level.  Subsequent users may wrongly assume the
battery is low and spend time checking/charging the battery.  Users
desire a method by which such conditions are reported on a calendar,
but, more importantly, schedule times based on the events for which
the resource is needed.

      This article employs a method by which an electronic identifier
is sent to the calendar service when a resource condition reaches a
specified power level in relation to another calendar event.  For
example, a notebook battery reaches a level for which it will be too
low for the needs of the next event.  This identifier may be queued
with other requests when the resource component is in disconnect
mode.  Upon the calendar service receiving the identifier, the
calendar will schedule an event for which the resource can be
recharged before its next allocation.  For example, a battery level
...