US20060277262A1 - Session management enhancements for instant messaging applications - Google Patents
Session management enhancements for instant messaging applications Download PDFInfo
- Publication number
- US20060277262A1 US20060277262A1 US11/146,989 US14698905A US2006277262A1 US 20060277262 A1 US20060277262 A1 US 20060277262A1 US 14698905 A US14698905 A US 14698905A US 2006277262 A1 US2006277262 A1 US 2006277262A1
- Authority
- US
- United States
- Prior art keywords
- message
- remote user
- computer
- messaging sessions
- session
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Abandoned
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/10—Network architectures or network communication protocols for network security for controlling access to devices or network resources
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
- G06Q10/10—Office automation; Time management
- G06Q10/107—Computer-aided management of electronic mailing [e-mailing]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L51/00—User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
- H04L51/04—Real-time or near real-time messaging, e.g. instant messaging [IM]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L51/00—User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
- H04L51/21—Monitoring or handling of messages
- H04L51/212—Monitoring or handling of messages using filtering or selective blocking
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/14—Session management
Definitions
- the present invention is a process for using electrical computers or digital processing systems to transfer data via one or more communications media.
- the present invention comprises an improved demand-based messaging system that enables a message recipient to manage messaging sessions.
- Demand-based messaging is a communication service that allows people to exchange message data, such as text, over a network or other communications media, in real time.
- message data such as text
- a network or other communications media Probably the most common medium for exchange is the Internet, but as wireless phone networks continue to expand, their popularity for text messaging is also expanding.
- Instant messaging is perhaps the most widely known and used embodiment of demand-based messaging.
- Instant messaging services also are being rapidly deployed and integrated into enterprise infrastructure.
- International Business Machines, Inc. (IBM), for example, has deployed LOTUS SAMETIME instant messaging applications for employees world-wide.
- Other examples of IM applications that are popular today include MSN Messenger and Yahoo/AOL Instant Messenger.
- Web-based interfaces are also gaining popularity, as illustrated in U.S. Pat. No. 6,651,086 issued to Manber et al., which describes how a user can join conversations about topics that are presented as web content.
- IM users typically use a networked computer and an IM client program to exchange messages with one another in conversational style.
- An IM client provides an interface for users to compose, send, receive, and read messages.
- an IM client usually includes at least two windows: a window for composing and sending messages, and a window for displaying messages as users take turns sending and receiving them.
- IM sessions (colloquially referred to as “chats”) are often lengthy, with multiple participants each taking many turns “speaking” in the chat window. It is common for one user to have multiple IM chats running simultaneously, usually in separate windows.
- the invention comprises an improved demand-based messaging system that enables a user to effectively manage multiple messaging sessions.
- the messaging system comprises a messaging program operable on a plurality of electrical computers or data processing machines connected by one or more communications media.
- the messaging program comprises a conventional message composer program, a conventional message transport program, a conventional message reader program, and an inventive, user-configurable, policy-driven session management program.
- FIG. 1 represents an exemplary network of hardware devices
- FIG. 2 is a schematic of a memory having the components of the present invention stored therein;
- FIG. 3 provides a functional overview of the messaging program of the present invention, as it interacts with a first user sending a message to a second user over a network of hardware devices;
- FIG. 4 illustrates a hypothetical interface to the messaging program of the present invention
- FIG. 5 is an exemplary interface, in which controls for the present invention are integrated into a conventional interface for selecting options
- FIG. 6 is a flowchart of the present invention as it implements a queuing policy
- FIG. 7 illustrates an alternative embodiment of the hypothetical interface to the messaging program of the present invention.
- the principles of the present invention are applicable to a variety of computer hardware and software configurations.
- computer hardware or “hardware,” as used herein, refers to any machine or apparatus that is capable of accepting, performing logic operations on, storing, or displaying data, and includes without limitation processors and memory; the term “computer software” or “software,” refers to any set of instructions operable to cause computer hardware to perform an operation.
- a computer program may, and often is, comprised of a plurality of smaller programming units, including without limitation subroutines, modules, functions, methods, and procedures.
- the functions of the present invention may be distributed among a plurality of computers and computer programs.
- the invention is described best, though, as a single computer program that configures and enables one or more general-purpose computers to implement the novel aspects of the invention.
- the inventive computer program will be referred to as the “messaging program.”
- a “network” comprises any number of hardware devices coupled to and in communication with each other through a communications medium, such as the Internet.
- a “communications medium” includes without limitation any physical, optical, electromagnetic, or other medium through which hardware or software can transmit data.
- exemplary network 100 has only a limited number of nodes, including workstation computer 105 , workstation computer 110 , server computer 115 , and persistent storage 120 .
- Network connection 125 comprises all hardware, software, and communications media necessary to enable communication between network nodes 105 - 120 . Unless otherwise indicated in context below, all network nodes use publicly available protocols or messaging services to communicate with each other through network connection 125 .
- Messaging program 200 and its components, composer 205 , session manager 210 , and reader 215 typically are stored in a memory, represented schematically as memory 220 in FIG. 2 .
- a single memory may encompass and be distributed across a plurality of media and network nodes.
- FIG. 2 is included merely as a descriptive expedient and does not necessarily reflect any particular physical embodiment of memory 220 .
- memory 220 may include additional data and programs.
- memory 220 may include message transfer program (MTP) 230 and session queue 240 , with which messaging program 200 interacts.
- MTP message transfer program
- FIG. 3 provides a functional overview of messaging program 200 , as it interacts with a first user sending a message to a second user over a computer network.
- a message recipient (the second user in the example of FIG. 3 ) is referred to as the “local user.”
- a user that initiates a message is referred to as the “remote user.”
- Messaging program 200 is loaded into the memory of both users' computers.
- Composer 205 accepts message data from the remote user ( 305 ), and then, upon the remote user's request, MTP 230 locates the local user's computer on the network and transfers the message data to the local user's computer ( 310 ).
- Session manager 210 on the local user's computer then examines the local user's current activity and the local user's activity policy ( 315 ).
- the local user's activity comprises the number of messaging sessions in which the local user is presently “active,” while the local user's activity policy indicates the threshold of activity at which session manager 210 should intervene to control the flow of messages or message notices to reader 215 .
- the term “active” in this context is inherently subjective, and session manager 210 can be configured to recognize active sessions based upon context or a user's preference. Thus, while there are many ways to define an “active” session, a specific definition is not material to the inventive features of messaging program 200 . Referring again to FIG.
- session manager 210 notifies reader 215 of incoming message data ( 320 ), and reader 215 displays the incoming message data to the local user ( 325 ).
- MTP 230 transfers the message data to a messaging server (such as server computer 115 ), and MTP 230 on the local user's computer retrieves the message data from the messaging server.
- session manager 210 is driven by a user-configurable activity policy that reflects a local user's preferences for accepting new message data while actively engaged in other messaging sessions.
- an activity policy is a flexible concept in which many variations of the policies described in detail here are possible.
- session manager 210 implements high-level functions in the following configurable policies: a “courtesy” policy, a “blocking” policy, a “queuing” policy, and an “inactive session” policy. The functions of each policy are described in more detail in the following discussion.
- FIG. 4 illustrates a hypothetical interface to session manager 210 in which the courtesy policy has been applied, where the parenthetical number next to each user's identify indicates the number of sessions that the user has active.
- the hypothetical interface of FIG. 4 is representative of both a local user's and a remote user's interface, depending upon context.
- the blocking policy configures session manager 210 to block new message data if the number of active sessions exceeds an “activity limit,” or if the request is from a remote user identified in a “block list.”
- the activity limit represents the maximum number of sessions that can be active at any given time, while the block list identifies specific remote users whose requests should be denied at any given time. Both the activity limit and the block list are user-configurable parameters.
- the local user may configure these parameters through a graphical interface, in which case session manager 210 stores the parameters in a configuration file, or the local user may edit the configuration file directly.
- FIG. 5 is an exemplary interface, in which controls for the parameters described herein are integrated into a conventional interface for selecting options.
- any new message data from the remote user (identified as “jdoe@us.ibm.com” in this example) would be blocked until at least one of the local user's current sessions ends or becomes inactive.
- Session manager 210 optionally notifies the remote user that the request was blocked based upon the local user's number of active sessions.
- the queuing policy extends the blocking policy so that session manager 210 stores new message data in session queue 240 , rather than blocking the new message data, if the number of active sessions exceeds the activity limit.
- FIG. 6 is a flowchart of session manager 210 as it implements a queuing policy.
- the maximum size of session queue 240 and thus the number of new messages that session manager 210 can store therein, is a user-configurable parameter, referred to herein as the “queue limit.”
- session manager 210 first determines the number of active sessions ( 610 ). If the number of active sessions does not exceed the activity limit, then messaging program 200 proceeds in a conventional manner and notifies reader 215 that new message data has been received ( 620 ).
- session manager 210 determines if the new message data would exceed the queue limit ( 625 ). If the new message data does not exceed the queue limit, session manager 210 stores the new message data ( 630 ) in session queue 240 and increments a queued message counter ( 640 ), but does not notify reader 215 . But if the new message data does exceed the queue limit, then session manager 210 blocks the message data ( 650 ) and, optionally, notifies the remote user ( 660 ) that the message data has been blocked because of activity limits. When an active session ends or becomes inactive, session manager 210 decreases the queued session counter and notifies reader 215 that the new message data is ready to be retrieved from session queue 240 . Reader 215 then removes the new message data from session queue 240 and processes the new message data in a conventional manner that is familiar to those skilled in the art.
- Interfaces to messaging program 200 may be modified to display queue status data, such as the queued message counter and a given user's position within a queue.
- FIG. 7 illustrates an exemplary modified interface for a user identified as jdoe@us.ibm.com.
- queue status data is displayed for some subset of users selected by jdoe@us.ibm.com, and the meaning of the parenthetical numbers depends upon context. For example, if jdoe@us.ibm.com is a remote user and sends message data to local user rh@us.ibm.com, then the parenthetical information on display of FIG.
- the inactive session policy allows a user to configure an “inactive” session parameter that defines an inactive session in terms of a period of time in which no messages are exchanged with a given remote user.
- a user also can configure an inactive session policy so that messaging program 200 takes user-selected action when a session is identified as inactive, such as archiving the session messages and closing the session interface.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Business, Economics & Management (AREA)
- Signal Processing (AREA)
- Human Resources & Organizations (AREA)
- Entrepreneurship & Innovation (AREA)
- Computer Hardware Design (AREA)
- Strategic Management (AREA)
- Operations Research (AREA)
- Quality & Reliability (AREA)
- Computer Security & Cryptography (AREA)
- Computing Systems (AREA)
- Economics (AREA)
- Marketing (AREA)
- General Engineering & Computer Science (AREA)
- Data Mining & Analysis (AREA)
- Tourism & Hospitality (AREA)
- Physics & Mathematics (AREA)
- General Business, Economics & Management (AREA)
- General Physics & Mathematics (AREA)
- Theoretical Computer Science (AREA)
- Computer And Data Communications (AREA)
Abstract
Description
- The present invention is a process for using electrical computers or digital processing systems to transfer data via one or more communications media. In particular, the present invention comprises an improved demand-based messaging system that enables a message recipient to manage messaging sessions.
- Demand-based messaging is a communication service that allows people to exchange message data, such as text, over a network or other communications media, in real time. Probably the most common medium for exchange is the Internet, but as wireless phone networks continue to expand, their popularity for text messaging is also expanding. U.S. Pat. No. 6,301,609 issued to Aravamudun et al., and U.S. Patent Publications Nos. 2002/0035605 and 2004/0254998, for example, illustrate the move toward an exchange medium that unifies traditional and wireless communications. Instant messaging (IM) is perhaps the most widely known and used embodiment of demand-based messaging. Today, most network and online service providers offer some form of IM service. According to some estimates, the top three instant messaging service providers serve over forty million users. Instant messaging services also are being rapidly deployed and integrated into enterprise infrastructure. International Business Machines, Inc. (IBM), for example, has deployed LOTUS SAMETIME instant messaging applications for employees world-wide. Other examples of IM applications that are popular today include MSN Messenger and Yahoo/AOL Instant Messenger. Web-based interfaces are also gaining popularity, as illustrated in U.S. Pat. No. 6,651,086 issued to Manber et al., which describes how a user can join conversations about topics that are presented as web content.
- IM users typically use a networked computer and an IM client program to exchange messages with one another in conversational style. An IM client provides an interface for users to compose, send, receive, and read messages. In a graphical display, an IM client usually includes at least two windows: a window for composing and sending messages, and a window for displaying messages as users take turns sending and receiving them. IM sessions (colloquially referred to as “chats”) are often lengthy, with multiple participants each taking many turns “speaking” in the chat window. It is common for one user to have multiple IM chats running simultaneously, usually in separate windows.
- Demand-based messaging services, including instant messaging services, no doubt owe much of their success to the convenience and efficiency with which communications can be exchanged. Unfortunately, the popularity of such messaging services directly affects the convenience and efficiency with which users can exchange communications, even making such communications disruptive at times. For example, it is not uncommon for users to have important instant messaging sessions active with one or more users, while other users continue to interrupt the flow of communications with unrelated messages.
- Current messaging applications provide minimal configuration and control to a user, often including only rudimentary means for blocking individual users from initiating a messaging session. With such limited means for managing the exchange of communications, any given messaging user is available to some sub-set of other users. Thus, existing messaging applications remain too cumbersome to manage communications effectively and there remains a need to advance the state of the art of demand-based messaging to overcome these shortcomings.
- The invention comprises an improved demand-based messaging system that enables a user to effectively manage multiple messaging sessions.
- The messaging system comprises a messaging program operable on a plurality of electrical computers or data processing machines connected by one or more communications media. The messaging program comprises a conventional message composer program, a conventional message transport program, a conventional message reader program, and an inventive, user-configurable, policy-driven session management program.
- The novel features believed characteristic of the invention are set forth in the appended claims. The invention itself, however, as well as a preferred mode of use, further objectives and advantages thereof, will be understood best by reference to the following detailed description of an illustrative embodiment when read in conjunction with the accompanying drawings, wherein:
-
FIG. 1 represents an exemplary network of hardware devices; -
FIG. 2 is a schematic of a memory having the components of the present invention stored therein; -
FIG. 3 provides a functional overview of the messaging program of the present invention, as it interacts with a first user sending a message to a second user over a network of hardware devices; -
FIG. 4 illustrates a hypothetical interface to the messaging program of the present invention; -
FIG. 5 is an exemplary interface, in which controls for the present invention are integrated into a conventional interface for selecting options; -
FIG. 6 is a flowchart of the present invention as it implements a queuing policy; and -
FIG. 7 illustrates an alternative embodiment of the hypothetical interface to the messaging program of the present invention. - The principles of the present invention are applicable to a variety of computer hardware and software configurations. The term “computer hardware” or “hardware,” as used herein, refers to any machine or apparatus that is capable of accepting, performing logic operations on, storing, or displaying data, and includes without limitation processors and memory; the term “computer software” or “software,” refers to any set of instructions operable to cause computer hardware to perform an operation. A “computer,” as that term is used herein, includes without limitation any useful combination of hardware and software, and a “computer program” or “program” includes without limitation any software operable to cause computer hardware to accept, perform logic operations on, store, or display data. A computer program may, and often is, comprised of a plurality of smaller programming units, including without limitation subroutines, modules, functions, methods, and procedures. Thus, the functions of the present invention may be distributed among a plurality of computers and computer programs. The invention is described best, though, as a single computer program that configures and enables one or more general-purpose computers to implement the novel aspects of the invention. For illustrative purposes, the inventive computer program will be referred to as the “messaging program.”
- Additionally, the messaging program is described below with reference to an exemplary network of hardware devices, as depicted in
FIG. 1 , through which the messaging program can transfer data from one user to another. A “network” comprises any number of hardware devices coupled to and in communication with each other through a communications medium, such as the Internet. A “communications medium” includes without limitation any physical, optical, electromagnetic, or other medium through which hardware or software can transmit data. For descriptive purposes,exemplary network 100 has only a limited number of nodes, includingworkstation computer 105,workstation computer 110,server computer 115, andpersistent storage 120.Network connection 125 comprises all hardware, software, and communications media necessary to enable communication between network nodes 105-120. Unless otherwise indicated in context below, all network nodes use publicly available protocols or messaging services to communicate with each other throughnetwork connection 125. -
Messaging program 200 and its components,composer 205,session manager 210, andreader 215 typically are stored in a memory, represented schematically asmemory 220 inFIG. 2 . The term “memory,” as used herein, includes without limitation any volatile or persistent medium, such as an electrical circuit, magnetic disk, or optical disk, in which a computer can store data or software for any duration. A single memory may encompass and be distributed across a plurality of media and network nodes. Thus,FIG. 2 is included merely as a descriptive expedient and does not necessarily reflect any particular physical embodiment ofmemory 220. As depicted inFIG. 2 , though,memory 220 may include additional data and programs. Of particular import tomessaging program 200,memory 220 may include message transfer program (MTP) 230 andsession queue 240, with whichmessaging program 200 interacts. -
FIG. 3 provides a functional overview ofmessaging program 200, as it interacts with a first user sending a message to a second user over a computer network. Inasmuch as the following discussion largely addresses the features ofmessaging program 200 from a recipient's perspective, a message recipient (the second user in the example ofFIG. 3 ) is referred to as the “local user.” A user that initiates a message is referred to as the “remote user.”Messaging program 200 is loaded into the memory of both users' computers.Composer 205 accepts message data from the remote user (305), and then, upon the remote user's request,MTP 230 locates the local user's computer on the network and transfers the message data to the local user's computer (310).Session manager 210 on the local user's computer then examines the local user's current activity and the local user's activity policy (315). In general, the local user's activity comprises the number of messaging sessions in which the local user is presently “active,” while the local user's activity policy indicates the threshold of activity at whichsession manager 210 should intervene to control the flow of messages or message notices toreader 215. The term “active” in this context is inherently subjective, andsession manager 210 can be configured to recognize active sessions based upon context or a user's preference. Thus, while there are many ways to define an “active” session, a specific definition is not material to the inventive features ofmessaging program 200. Referring again toFIG. 3 for illustration, if the local user's activity policy permits,session manager 210 notifiesreader 215 of incoming message data (320), andreader 215 displays the incoming message data to the local user (325). Alternatively,MTP 230 transfers the message data to a messaging server (such as server computer 115), andMTP 230 on the local user's computer retrieves the message data from the messaging server. Those skilled in the art will appreciate that many similar functional variations are possible and not all are described here. - As briefly described above,
session manager 210 is driven by a user-configurable activity policy that reflects a local user's preferences for accepting new message data while actively engaged in other messaging sessions. Thus, an activity policy is a flexible concept in which many variations of the policies described in detail here are possible. In the preferred embodiment, though,session manager 210 implements high-level functions in the following configurable policies: a “courtesy” policy, a “blocking” policy, a “queuing” policy, and an “inactive session” policy. The functions of each policy are described in more detail in the following discussion. - If the courtesy policy is applied,
session manager 210 broadcasts the number of sessions that the local user has active at any given time, so that other instances ofmessaging program 200 running on remote computers can display this number to remote users. Thus, the courtesy policy causessession manager 210 to provide information to remote users, but relies upon the remote users to exercise their own personal judgment regarding the propriety of requesting a session with someone that already has multiple active sessions.FIG. 4 illustrates a hypothetical interface tosession manager 210 in which the courtesy policy has been applied, where the parenthetical number next to each user's identify indicates the number of sessions that the user has active. The hypothetical interface ofFIG. 4 is representative of both a local user's and a remote user's interface, depending upon context. - The blocking policy configures
session manager 210 to block new message data if the number of active sessions exceeds an “activity limit,” or if the request is from a remote user identified in a “block list.” The activity limit represents the maximum number of sessions that can be active at any given time, while the block list identifies specific remote users whose requests should be denied at any given time. Both the activity limit and the block list are user-configurable parameters. The local user may configure these parameters through a graphical interface, in whichcase session manager 210 stores the parameters in a configuration file, or the local user may edit the configuration file directly.FIG. 5 is an exemplary interface, in which controls for the parameters described herein are integrated into a conventional interface for selecting options. Many other techniques for configuring and storing parameters are well-known in the art, and the particular technique applied is not material to the inventive features ofmessaging program 200. Referring again toFIG. 4 for illustration, if the user identified as “rh@us.ibm.com” is the local user and has set the activity limit to 10 active sessions, any new message data from the remote user (identified as “jdoe@us.ibm.com” in this example) would be blocked until at least one of the local user's current sessions ends or becomes inactive.Session manager 210 optionally notifies the remote user that the request was blocked based upon the local user's number of active sessions. - The queuing policy extends the blocking policy so that
session manager 210 stores new message data insession queue 240, rather than blocking the new message data, if the number of active sessions exceeds the activity limit.FIG. 6 is a flowchart ofsession manager 210 as it implements a queuing policy. The maximum size ofsession queue 240, and thus the number of new messages thatsession manager 210 can store therein, is a user-configurable parameter, referred to herein as the “queue limit.” Thus, with the queuing policy applied,session manager 210 first determines the number of active sessions (610). If the number of active sessions does not exceed the activity limit, then messagingprogram 200 proceeds in a conventional manner and notifiesreader 215 that new message data has been received (620). If the number of active sessions has reached the activity limit, thensession manager 210 determines if the new message data would exceed the queue limit (625). If the new message data does not exceed the queue limit,session manager 210 stores the new message data (630) insession queue 240 and increments a queued message counter (640), but does not notifyreader 215. But if the new message data does exceed the queue limit, thensession manager 210 blocks the message data (650) and, optionally, notifies the remote user (660) that the message data has been blocked because of activity limits. When an active session ends or becomes inactive,session manager 210 decreases the queued session counter and notifiesreader 215 that the new message data is ready to be retrieved fromsession queue 240.Reader 215 then removes the new message data fromsession queue 240 and processes the new message data in a conventional manner that is familiar to those skilled in the art. - Interfaces to
messaging program 200, such as the interface illustrated inFIG. 4 , may be modified to display queue status data, such as the queued message counter and a given user's position within a queue.FIG. 7 illustrates an exemplary modified interface for a user identified as jdoe@us.ibm.com. InFIG. 7 , queue status data is displayed for some subset of users selected by jdoe@us.ibm.com, and the meaning of the parenthetical numbers depends upon context. For example, if jdoe@us.ibm.com is a remote user and sends message data to local user rh@us.ibm.com, then the parenthetical information on display ofFIG. 7 would indicate that local user rh@us.ibm.com has 10 active sessions and that jdoe@us.ibm.com's request is the third in the local user's queue. If jdoe@us.ibm.com has not sent any messages to rh@us.ibm.com, then the parenthetical information next to rh@us.ibm.com indicates that rh@us.ibm.com has 10 active sessions and a total of three messages in the queue. In yet another context, the parenthetical information next to jdoe@us.ibm.com indicates that jdoe@us.ibm.com has two active sessions and no messages waiting in the queue. Additionally, if either user places a mouse cursor over the number, or takes some other appropriate triggering action,messaging program 200 would display the identities of the active users, the queued users, or both. - The inactive session policy allows a user to configure an “inactive” session parameter that defines an inactive session in terms of a period of time in which no messages are exchanged with a given remote user. A user also can configure an inactive session policy so that
messaging program 200 takes user-selected action when a session is identified as inactive, such as archiving the session messages and closing the session interface. - A preferred form of the invention has been shown in the drawings and described above, but variations in the preferred form will be apparent to those skilled in the art. The preceding description is for illustration purposes only, and the invention should not be construed as limited to the specific form shown and described. The scope of the invention should be limited only by the language of the following claims.
Claims (20)
Priority Applications (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US11/146,989 US20060277262A1 (en) | 2005-06-06 | 2005-06-06 | Session management enhancements for instant messaging applications |
US12/177,284 US8380792B2 (en) | 2005-06-06 | 2008-07-22 | Session management enhancements for instant messaging applications |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US11/146,989 US20060277262A1 (en) | 2005-06-06 | 2005-06-06 | Session management enhancements for instant messaging applications |
Related Child Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US12/177,284 Continuation US8380792B2 (en) | 2005-06-06 | 2008-07-22 | Session management enhancements for instant messaging applications |
Publications (1)
Publication Number | Publication Date |
---|---|
US20060277262A1 true US20060277262A1 (en) | 2006-12-07 |
Family
ID=37495406
Family Applications (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US11/146,989 Abandoned US20060277262A1 (en) | 2005-06-06 | 2005-06-06 | Session management enhancements for instant messaging applications |
US12/177,284 Active 2027-02-18 US8380792B2 (en) | 2005-06-06 | 2008-07-22 | Session management enhancements for instant messaging applications |
Family Applications After (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US12/177,284 Active 2027-02-18 US8380792B2 (en) | 2005-06-06 | 2008-07-22 | Session management enhancements for instant messaging applications |
Country Status (1)
Country | Link |
---|---|
US (2) | US20060277262A1 (en) |
Cited By (10)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20070005763A1 (en) * | 2005-07-01 | 2007-01-04 | Cisco Technology, Inc. | Method and system for using load information in an instant messaging system |
US20070171821A1 (en) * | 2006-01-25 | 2007-07-26 | Konica Minolta Business Technologies, Inc. | Data communication apparatus, data communication method and data communication processing program |
US20080195710A1 (en) * | 2007-02-12 | 2008-08-14 | International Business Machines Corporation | System, method and program for managing e-mail |
US20090094368A1 (en) * | 2007-10-08 | 2009-04-09 | Steven Francis Best | Instant messaging general queue depth management |
US20100041420A1 (en) * | 2006-10-13 | 2010-02-18 | Roebke Matthias | Method for exchanging messages in a mobile radio network |
CN103188137A (en) * | 2011-12-30 | 2013-07-03 | 阿里巴巴集团控股有限公司 | Message emerging method based on fatigue control, server and instant messaging client-side |
CN103326924A (en) * | 2012-03-21 | 2013-09-25 | 阿里巴巴集团控股有限公司 | Emerging message task control method, server and instant messaging client |
WO2018103555A1 (en) * | 2016-12-07 | 2018-06-14 | 阿里巴巴集团控股有限公司 | Group message notification method, client, electronic device and server |
US20190245819A1 (en) * | 2016-03-03 | 2019-08-08 | Genband Us Llc | System and method for blocking notification messages during screen sharing |
US20190387031A1 (en) * | 2018-06-18 | 2019-12-19 | Verizon Patent And Licensing Inc. | Systems and methods for generating a shortcut associated with a rich communication services messaging session |
Families Citing this family (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP5037117B2 (en) * | 2006-03-15 | 2012-09-26 | 株式会社リコー | Program and display control method |
US9083557B2 (en) * | 2010-06-18 | 2015-07-14 | International Business Machines Corporation | User initiated rule-based restrictions on messaging applications |
Citations (20)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20030002441A1 (en) * | 2001-06-27 | 2003-01-02 | International Business Machines Corporation | Reduction of server overload |
US20030142654A1 (en) * | 2002-01-29 | 2003-07-31 | Agere Systems Inc. | Method and device for providing a communication session |
US20040103318A1 (en) * | 2002-06-10 | 2004-05-27 | Akonix Systems, Inc. | Systems and methods for implementing protocol enforcement rules |
US20040111479A1 (en) * | 2002-06-25 | 2004-06-10 | Borden Walter W. | System and method for online monitoring of and interaction with chat and instant messaging participants |
US20040199594A1 (en) * | 2001-06-21 | 2004-10-07 | Radatti Peter V. | Apparatus, methods and articles of manufacture for intercepting, examining and controlling code, data and files and their transfer |
US20050080848A1 (en) * | 2003-09-25 | 2005-04-14 | Sun Microsystems, Inc. | Method and system for busy presence state detection in an instant messaging system |
US20050091253A1 (en) * | 2003-10-22 | 2005-04-28 | International Business Machines Corporation | Attaching and displaying annotations to changing data views |
US20050149620A1 (en) * | 2004-01-07 | 2005-07-07 | International Business Machines Corporation | Instant messaging windowing for topic threads |
US20060059235A1 (en) * | 2004-09-15 | 2006-03-16 | International Business Machines Corporation | System and method for multi-threaded discussion within a single instant messenger pane |
US20060062203A1 (en) * | 2004-09-21 | 2006-03-23 | Cisco Technology, Inc. | Method and apparatus for handling SCTP multi-homed connections |
US20060075029A1 (en) * | 2004-09-15 | 2006-04-06 | International Business Machines Corporation | System and method for client based instant messenger queue limit |
US20060168048A1 (en) * | 2005-01-21 | 2006-07-27 | International Business Machines Corporation | Selectively blocking instant messages according to a do not instant message list |
US20060168065A1 (en) * | 2004-12-08 | 2006-07-27 | John Martin | Electronic message response and remediation system and method |
US20060212519A1 (en) * | 2005-03-15 | 2006-09-21 | International Business Machines Corporation | Rfid wireless control of instant messaging |
US20060235932A1 (en) * | 2005-04-18 | 2006-10-19 | International Business Machines Corporation | Chat server mute capability |
US20060253895A1 (en) * | 2005-03-29 | 2006-11-09 | Michael Brandofino | Video communication call authorization |
US7356567B2 (en) * | 2004-12-30 | 2008-04-08 | Aol Llc, A Delaware Limited Liability Company | Managing instant messaging sessions on multiple devices |
US20080184366A1 (en) * | 2004-11-05 | 2008-07-31 | Secure Computing Corporation | Reputation based message processing |
US7412491B2 (en) * | 2003-04-30 | 2008-08-12 | International Business Machines Corporation | Method and apparatus for enhancing instant messaging systems |
US7454709B1 (en) * | 1997-02-24 | 2008-11-18 | Aol Llc, A Delaware Limited Liability Company | User definable on-line co-user lists |
Family Cites Families (11)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6301609B1 (en) | 1999-07-07 | 2001-10-09 | Lucent Technologies Inc. | Assignable associate priorities for user-definable instant messaging buddy groups |
US20020035605A1 (en) | 2000-01-26 | 2002-03-21 | Mcdowell Mark | Use of presence and location information concerning wireless subscribers for instant messaging and mobile commerce |
US6651086B1 (en) | 2000-02-22 | 2003-11-18 | Yahoo! Inc. | Systems and methods for matching participants to a conversation |
US6760580B2 (en) | 2000-03-06 | 2004-07-06 | America Online, Incorporated | Facilitating instant messaging outside of user-defined buddy group in a wireless and non-wireless environment |
US6731308B1 (en) * | 2000-03-09 | 2004-05-04 | Sun Microsystems, Inc. | Mechanism for reciprocal awareness of intent to initiate and end interaction among remote users |
US8086672B2 (en) | 2000-06-17 | 2011-12-27 | Microsoft Corporation | When-free messaging |
US20020178227A1 (en) | 2001-05-25 | 2002-11-28 | International Business Machines Corporation | Routing instant messages using configurable, pluggable delivery managers |
US7321969B2 (en) | 2002-04-26 | 2008-01-22 | Entrust Limited | Secure instant messaging system using instant messaging group policy certificates |
US7281215B1 (en) * | 2002-04-30 | 2007-10-09 | Aol Llc | IM conversation counter and indicator |
US7769811B2 (en) * | 2003-03-03 | 2010-08-03 | Aol Llc | Instant messaging sound control |
US7433920B2 (en) * | 2003-10-10 | 2008-10-07 | Microsoft Corporation | Contact sidebar tile |
-
2005
- 2005-06-06 US US11/146,989 patent/US20060277262A1/en not_active Abandoned
-
2008
- 2008-07-22 US US12/177,284 patent/US8380792B2/en active Active
Patent Citations (23)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7454709B1 (en) * | 1997-02-24 | 2008-11-18 | Aol Llc, A Delaware Limited Liability Company | User definable on-line co-user lists |
US20040199594A1 (en) * | 2001-06-21 | 2004-10-07 | Radatti Peter V. | Apparatus, methods and articles of manufacture for intercepting, examining and controlling code, data and files and their transfer |
US20030002441A1 (en) * | 2001-06-27 | 2003-01-02 | International Business Machines Corporation | Reduction of server overload |
US20030142654A1 (en) * | 2002-01-29 | 2003-07-31 | Agere Systems Inc. | Method and device for providing a communication session |
US20040103318A1 (en) * | 2002-06-10 | 2004-05-27 | Akonix Systems, Inc. | Systems and methods for implementing protocol enforcement rules |
US20040111479A1 (en) * | 2002-06-25 | 2004-06-10 | Borden Walter W. | System and method for online monitoring of and interaction with chat and instant messaging participants |
US20080250336A1 (en) * | 2003-04-30 | 2008-10-09 | International Business Machines Corporation | Method and Apparatus for Enhancing Instant Messaging Systems |
US7412491B2 (en) * | 2003-04-30 | 2008-08-12 | International Business Machines Corporation | Method and apparatus for enhancing instant messaging systems |
US20050080848A1 (en) * | 2003-09-25 | 2005-04-14 | Sun Microsystems, Inc. | Method and system for busy presence state detection in an instant messaging system |
US20050091253A1 (en) * | 2003-10-22 | 2005-04-28 | International Business Machines Corporation | Attaching and displaying annotations to changing data views |
US20080183832A1 (en) * | 2004-01-07 | 2008-07-31 | International Business Machines Corporation | Instant Messaging Windowing for Topic Threads |
US20050149620A1 (en) * | 2004-01-07 | 2005-07-07 | International Business Machines Corporation | Instant messaging windowing for topic threads |
US20060075029A1 (en) * | 2004-09-15 | 2006-04-06 | International Business Machines Corporation | System and method for client based instant messenger queue limit |
US20060059235A1 (en) * | 2004-09-15 | 2006-03-16 | International Business Machines Corporation | System and method for multi-threaded discussion within a single instant messenger pane |
US20060062203A1 (en) * | 2004-09-21 | 2006-03-23 | Cisco Technology, Inc. | Method and apparatus for handling SCTP multi-homed connections |
US20080184366A1 (en) * | 2004-11-05 | 2008-07-31 | Secure Computing Corporation | Reputation based message processing |
US20060168065A1 (en) * | 2004-12-08 | 2006-07-27 | John Martin | Electronic message response and remediation system and method |
US7356567B2 (en) * | 2004-12-30 | 2008-04-08 | Aol Llc, A Delaware Limited Liability Company | Managing instant messaging sessions on multiple devices |
US20080189374A1 (en) * | 2004-12-30 | 2008-08-07 | Aol Llc | Managing instant messaging sessions on multiple devices |
US20060168048A1 (en) * | 2005-01-21 | 2006-07-27 | International Business Machines Corporation | Selectively blocking instant messages according to a do not instant message list |
US20060212519A1 (en) * | 2005-03-15 | 2006-09-21 | International Business Machines Corporation | Rfid wireless control of instant messaging |
US20060253895A1 (en) * | 2005-03-29 | 2006-11-09 | Michael Brandofino | Video communication call authorization |
US20060235932A1 (en) * | 2005-04-18 | 2006-10-19 | International Business Machines Corporation | Chat server mute capability |
Cited By (21)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20070005763A1 (en) * | 2005-07-01 | 2007-01-04 | Cisco Technology, Inc. | Method and system for using load information in an instant messaging system |
US20070171821A1 (en) * | 2006-01-25 | 2007-07-26 | Konica Minolta Business Technologies, Inc. | Data communication apparatus, data communication method and data communication processing program |
US8654633B2 (en) * | 2006-01-25 | 2014-02-18 | Konica Minolta Business Technologies, Inc | Data communication apparatus, data communication method and data communication processing program |
US8649809B2 (en) * | 2006-10-13 | 2014-02-11 | T-Mobile International Ag | Method for exchanging messages in a mobile radio network |
US20100041420A1 (en) * | 2006-10-13 | 2010-02-18 | Roebke Matthias | Method for exchanging messages in a mobile radio network |
US20080195710A1 (en) * | 2007-02-12 | 2008-08-14 | International Business Machines Corporation | System, method and program for managing e-mail |
WO2008098904A2 (en) | 2007-02-12 | 2008-08-21 | International Business Machines Corporation | System, method and program for managing e-mail |
US8055718B2 (en) | 2007-02-12 | 2011-11-08 | International Business Machines Corporation | Management of carbon copy and reply to all functions of an email |
US20090094368A1 (en) * | 2007-10-08 | 2009-04-09 | Steven Francis Best | Instant messaging general queue depth management |
US20160234137A1 (en) * | 2011-12-30 | 2016-08-11 | Alibaba Group Holding Limited | Fatigue control-based message float-out method, system and instant messaging client |
US20130173708A1 (en) * | 2011-12-30 | 2013-07-04 | Alibaba Group Holding Limited | Fatigue control-based message float-out method, system and instant messaging client |
WO2013101576A1 (en) * | 2011-12-30 | 2013-07-04 | Alibaba Group Holding Limited | Fatigue control-based message float-out method, system and instant messaging client |
JP2015501047A (en) * | 2011-12-30 | 2015-01-08 | アリババ・グループ・ホールディング・リミテッドAlibaba Group Holding Limited | Fatigue control based message floatout method, system and instant messaging client |
US9350688B2 (en) * | 2011-12-30 | 2016-05-24 | Alibaba Group Holding Limited | Fatigue control-based message float-out method, system and instant messaging client |
CN103188137A (en) * | 2011-12-30 | 2013-07-03 | 阿里巴巴集团控股有限公司 | Message emerging method based on fatigue control, server and instant messaging client-side |
TWI612464B (en) * | 2011-12-30 | 2018-01-21 | Alibaba Group Holding Ltd | Message floating method based on fatigue control, server and instant messaging client |
CN103326924A (en) * | 2012-03-21 | 2013-09-25 | 阿里巴巴集团控股有限公司 | Emerging message task control method, server and instant messaging client |
US20190245819A1 (en) * | 2016-03-03 | 2019-08-08 | Genband Us Llc | System and method for blocking notification messages during screen sharing |
WO2018103555A1 (en) * | 2016-12-07 | 2018-06-14 | 阿里巴巴集团控股有限公司 | Group message notification method, client, electronic device and server |
US20190387031A1 (en) * | 2018-06-18 | 2019-12-19 | Verizon Patent And Licensing Inc. | Systems and methods for generating a shortcut associated with a rich communication services messaging session |
US11310289B2 (en) * | 2018-06-18 | 2022-04-19 | Verizon Patent And Licensing Inc. | Systems and methods for generating a shortcut associated with a rich communication services messaging session |
Also Published As
Publication number | Publication date |
---|---|
US8380792B2 (en) | 2013-02-19 |
US20080281933A1 (en) | 2008-11-13 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US8380792B2 (en) | Session management enhancements for instant messaging applications | |
US8001184B2 (en) | System and method for managing an instant messaging conversation | |
US7844673B2 (en) | Filtering features for multiple minimized instant message chats | |
US10630617B2 (en) | Maintaining message privacy on an exposed display device | |
US7596596B2 (en) | Chat marking and synchronization | |
US7568007B2 (en) | System and method for supporting instant messaging in disconnected modes | |
US7949107B2 (en) | Method, system, and computer program product for providing privacy measures in instant messaging systems | |
US9563876B2 (en) | Control options for instant message display and notification | |
US7284034B2 (en) | Transparent combination of instant message protocols | |
EP3402137B1 (en) | Methods and apparatuses for cross platforms conversations through a bot framework | |
US7680895B2 (en) | Integrated conversations having both email and chat messages | |
US10554594B2 (en) | Method and system for automatic switching between chat windows | |
US9628426B2 (en) | Instant messaging system | |
US8015497B2 (en) | Folding text in side conversations | |
US7814159B2 (en) | Time line display of chat conversations | |
US20070198474A1 (en) | Contact list search with autocomplete | |
US20070143417A1 (en) | Instant messaging confirmation and receipt | |
US20060212583A1 (en) | Distributing messaging session logs to users entering an already ongoing messaging session | |
US8082305B2 (en) | Saving un-viewed instant messages | |
US20050198589A1 (en) | Focus stealing prevention | |
US20070094342A1 (en) | Detachable control window for instant messaging chats | |
US8583741B2 (en) | Integrated email and chat archiving with fine grained user control for chat archiving | |
JP4560844B2 (en) | Selective attendance management method for instant messaging service in telecommunication networks such as the Internet | |
US20070022160A1 (en) | Method of managing privileged conversations in an instant conversation system | |
EP2112794A1 (en) | Method and apparatuses for pushing e-mail to wireless communication devices |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: INTERNATIONAL BUSINESS MACHINES CORPORATION, NEW Y Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:BOSS, GREGORY JENSEN;HAMILTON, II, RICK ALLEN;PANDYA, AROOPRATAN D.;AND OTHERS;REEL/FRAME:016410/0925;SIGNING DATES FROM 20050523 TO 20050602 |
|
STCB | Information on status: application discontinuation |
Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION |
|
AS | Assignment |
Owner name: KYNDRYL, INC., NEW YORK Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:INTERNATIONAL BUSINESS MACHINES CORPORATION;REEL/FRAME:058213/0912 Effective date: 20211118 |