Browse Prior Art Database

Instant messages usage for communication between end users and program applications

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

Publishing Venue

IBM

Abstract

Proposed is the use of Instant Messages as a tool for notification and bi-directional communication between applications and end-users .

This text was extracted from a PDF file.
At least one non-text object (such as an image or picture) has been suppressed.
This is the abbreviated version, containing approximately 53% of the total text.

Page 1 of 3

Instant messages usage for communication between end users and program applications

Proposed is the use of Instant Messages as a tool for notification and bi-directional communication between applications and end-users .

    This idea was implemented for Sametime* within Infoprint Manager*. The existing pop-up notification mechanism for Infoprint (for Windows** clients) is based on a notification agent, listening on port 25 (SMTP), that is very problematic in respect of security. Sametime has never been used for bi-directional communication for printing management.

Infoprint server, upon some events ( end-of-print, paper-jam, etc.), is programmed to send notification to the end-user using a notification method (mail, pop-up notification, etc) selected by the end-user. The idea disclosed herein is based on a new notification method: Instant Messages. It is implemented for Sametime in the environment of Infoprint.

    There are two modules installed in Infoprint server: Sametime-exit and Sametime-agent. Sametime-exit serves as connection module between the target server and Sametime. It forwards the notifications targeted to the end-user, who is already login and authenticated in Sametime.

    The bi-directional communication is implemented by means of extended Sametime-agent. The communication between the end-user and Infoprint server is based on the established secure communication channel between user's Sametime client and Sametime-agent in Infoprint. The Sametime-agent validates the correctness of the user request and executes it on behalf of the user. Message spooling is implemented in case Same Time user's Client is not reachable.

The existing pop-up notification in Windows is based on SMTP protocol that is very problematic in respect of security and very often it is disabled by end-users.

    Sametime as a communication method is a standard within the IBM community. Sametime is the only possible alternative for pop-up notification for printing in the existing Linux*** clients. The idea for this kind of notification is much more general, however, and it can be implemented for any Instant Messaging (MSN****, for example). It serves as an OS-independent end-user management tool for any application.

Page 2 of 3

Print Request Initiation

Linux

  Lpr or Applications ( Mozilla, OpenOffice)

 CUPS Infoprint Back-end

Notification Profile

pdpr

Delivery-method sametime

SameTime ID

WINDOWS

kalderon@il.ibm.com

    Applications (MS Browser, MS Office)

Message LifeTime 10h

Printers drivers

Port monitor pdpr

SameTime Notification - SERVER STRUCTURE

User's Print Request

INFOPRINT SERVER

Message Spool

 Same Time Standard exit

SameTime Spooler

SameTime Agent

SAMETIME SERVER

ST Notification

The implementation was done for Sametime for Infoprint Manager. In...