Browse Prior Art Database

Machine State Agent

IP.com Disclosure Number: IPCOM000012082D
Original Publication Date: 2003-Apr-07
Included in the Prior Art Database: 2003-Apr-07
Document File: 2 page(s) / 6K

Publishing Venue

IBM

Abstract

Machine State Agent automatically selects a default state based on a user's operating system-related activity and/or their lifestyle.

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

Page 1 of 2

Machine State Agent

Background:

Some operating systems include an application that allows users to select an operating system state. For example, on one operating system, possible states include: logoff, shutdown, restart, stand by, and hibernate. Although these applications are usually GUI based, they can be command-line/text based.

Problem:

In general, the default state selection is set to the last selection the user executed or always the same selection. For example:
a) The user invokes the machine state application and selects shutdown.
b) The default selection is now shutdown.
c) The next time the user invokes the machine state application, shutdown is the default selection.

The above default selection mechanism does not take the user's operating system-related activity or their lifestyle into account. For example, in general,:
a) Users do not shutdown their operating systems during the middle of a work day.
b) Users do not restart their operating systems at the end of a work day.

Solution:

Enhance the machine state application to account for a user's operating system-related activity and/or their lifestyle.

For example:
a) A user's operating system-related activity may include installation, configuration, or deletion of software or hardware that requires the operating system to restart.
b) A user's lifestyle may be defined as a table which contains the actual machine states for the last sixty days, or a table which references a defined schedule, such as the user's calendar. The machine state agent will look at the table with the history of actual machine states to predict when states will occur in the future. For example, the table may only have three days of data. Each day the user starts the machine at 8AM and issues a shutdown at 5PM. The agent will define the start of the work day as 8AM and the end of the work day as 5PM. After a few weeks of data have been collected, the agent may discover new usage patterns. For example, everyday a shutdown occurs at 5PM, except for Mondays. For the last three Mondays, the user issues a shutdown at 2:30PM. The agent will define the end of the work day as 2:30PM for Mondays o...