Browse Prior Art Database

A means for preventing the need to retype a message to instant messaging peers

IP.com Disclosure Number: IPCOM000125713D
Original Publication Date: 2005-Jun-14
Included in the Prior Art Database: 2005-Jun-14
Document File: 2 page(s) / 57K

Publishing Venue

IBM

Abstract

The popularity of instant messaging means that instant messaging technology has become an increasingly ubiquitous means for interaction between co-workers and friends. There are many occasions when a user has many chat sessions open at a time (and is therefore servicing a session with many peers). In particular, this means that the user has to maintain (using written text) a dialogue with each user. Often if the user is about to go away or disconnect, they say a few words rather than letting their instant messaging status work by itself ("Active", "Offline", "Away" ). This becomes cumbersome when a user has many sessions to service and generally a user either retypes in each session, copy and pastes from one to the other or simply disconnects. There are drawbacks to either case, the main one being time and hassle to navigate through a number of sessions.

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 means for preventing the need to retype a message to instant messaging peers

The popularity of instant messaging means that instant messaging technology has become an increasingly ubiquitous means for interaction between co-workers and friends. There are many occasions when a user has many chat sessions open at a time (and is therefore servicing a session with many peers). In particular, this means that the user has to maintain (using written text) a dialogue with each user. Often if the user is about to go away or disconnect, they say a few words rather than letting their instant messaging status work by itself ("Active", "Offline", "Away" ). This becomes cumbersome when a user has many sessions to service and generally a user either retypes in each session, copy and pastes from one to the other or simply disconnects. There are drawbacks to either case, the main one being time and hassle to navigate through a number of sessions.

The proposed solution comprises the following components:

Profiles mapping commonly used words and phrases to online changes of

state. For example, the word "reboot" would map to "active -> offline". This is used to associate a change of online state with free text entered into a session.

Profiles mapping the change-of-state profile in (1) to peer user IDs and


2.

message text. For example, mapping offline state and the word "reboot" (as in 1) to the user ID "user A@myserver.com" and text "i'll be back in just a second, i have to reboot my machine".

A session and state monitor component. When the user's state changes

(e.g. from "active" to "away"), the monitor component examines the last text typed in the last focused chat session before the change. The state monitor is responsible for tracking the currently focused session to keep track of where the user last typed text prior to the state change and also the number of current sessions open (and hence whom they are being conducted with).

A profile builder component that is responsible for maintaining the profiles


4.

created in 1 and 2 with input taken from the state monitor in 3 (state, peer user ID and the free text typed into the session). This component is responsible for distilling the free text down into its composite keywords and augmenting the profiles and is invoked by the state monitor in 3 when a state change occurs. Note that the component can prompt the user as to whether they wish to store the free text in the profiles in (2) -- after all there may not be much point storing multiple variations on the same theme. In a simplistic embodiment only the first entry for a given keyword for a given user is used.

An matching engine invoked by the state monitor component in 3 when the

user state changes. This maps the state change to keywords to try and ascertain the reason in text for the state change from the last text entered in a session....