Browse Prior Art Database

A Mechanism to Map Instant Messaging States to Arbitrary Programmable Entity States

IP.com Disclosure Number: IPCOM000031853D
Original Publication Date: 2004-Oct-14
Included in the Prior Art Database: 2004-Oct-14
Document File: 2 page(s) / 90K

Publishing Venue

IBM

Abstract

A Mechanism to Map Instant Messaging States to Arbitrary Programmable Entity States

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

Page 1 of 2

A Mechanism to Map Instant Messaging States to Arbitrary Programmable Entity States

Main Idea

In today's work environment, instant messaging (IM) clients tend to be some of the most used software. People use IM to collaborate/communicate as well as indicate their current status of work. When they are online, they are often open to requests while when they are very busy they are not open to requests. Similarly, they can indicate that they are in a meeting or working on a particular item using custom states. IM today reflects the availability of a user to the world.

When a user of IM goes to a meeting or is busy, she desires to perform a set of co-related functions. For example, she might change her IM state to 'do not disturb'. When she takes this action, she typically wants to perform some other set of actions on other entities like cell phone (setting it to Reject mode and changing the greeting for voice message), office phone (muting it and changing the greeting for voice message) , automatic logging onto databases and their servers (for the purposes of meeting) etc. Today, the user on performing one action has to perform other set of actions manually -- this is tedious and time-consuming.

What we are proposing is a generic framework where a change in state of IM client can be mapped to several states of different chosen entities.

What is a Programmable Entity: A programmable entity for the purpose of this invention is defined as any hardware/device/software that can be controlled via programmable code. An entity has a set of states that it can be in. The set of states are not predefined and are defined by the entity. An entity can be programmed to move from one state to another.

Examples of entities: cell phone with states = {On, Busy, DoNotDisturb , Off } email client with states = { InOffice, OutofO...