US20080281937A1 - Routing instant messages using configurable, pluggable delivery managers - Google Patents

Routing instant messages using configurable, pluggable delivery managers Download PDF

Info

Publication number
US20080281937A1
US20080281937A1 US12/179,610 US17961008A US2008281937A1 US 20080281937 A1 US20080281937 A1 US 20080281937A1 US 17961008 A US17961008 A US 17961008A US 2008281937 A1 US2008281937 A1 US 2008281937A1
Authority
US
United States
Prior art keywords
delivery
manager
delivery manager
mechanisms
routing
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
Application number
US12/179,610
Inventor
Moshe M. E. Matsa
Julius Q. Quiaot
Christopher R. Vincent
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
International Business Machines Corp
Original Assignee
International Business Machines Corp
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by International Business Machines Corp filed Critical International Business Machines Corp
Priority to US12/179,610 priority Critical patent/US20080281937A1/en
Publication of US20080281937A1 publication Critical patent/US20080281937A1/en
Abandoned legal-status Critical Current

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L51/00User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
    • H04L51/04Real-time or near real-time messaging, e.g. instant messaging [IM]
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network arrangements or protocols for supporting network services or applications
    • H04L67/50Network services
    • H04L67/54Presence management, e.g. monitoring or registration for receipt of user log-on information, or the connection status of the users
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network arrangements or protocols for supporting network services or applications
    • H04L67/50Network services
    • H04L67/60Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources
    • H04L67/63Routing a service request depending on the request content or context
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/40Network security protocols
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L51/00User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
    • H04L51/21Monitoring or handling of messages
    • H04L51/214Monitoring or handling of messages using selective forwarding
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/30Definitions, standards or architectural aspects of layered protocol stacks
    • H04L69/32Architecture of open systems interconnection [OSI] 7-layer type protocol stacks, e.g. the interfaces between the data link level and the physical level
    • H04L69/322Intralayer communication protocols among peer entities or protocol data unit [PDU] definitions
    • H04L69/329Intralayer communication protocols among peer entities or protocol data unit [PDU] definitions in the application layer [OSI layer 7]

Definitions

  • This invention relates, in general, to instant messaging, and in particular, to providing a messaging environment in which configurable, pluggable delivery managers are used to route instant messages to intended recipients.
  • instant messaging In today's communication environments, instant messaging is common place. Users send messages to one or more intended recipients and expect that those messages will be delivered substantially instantly.
  • Various mechanisms are used for instant messaging, including one or more instant messaging protocols, such as the SameTime protocol offered by International Business Machines Corporation or Instant Messenger offered by AOL.
  • Other techniques are also used to send instant messages, such as pager gateways.
  • the system includes, for instance, a computer system to include instructions to execute a method.
  • the method includes, for instance, selecting a delivery manager from a plurality of available delivery managers, via a client application to route an instant message to an intended recipient of the instant message, wherein the delivery manager is pluggable; configuring the delivery manager at runtime via the client application, wherein the configuring includes selecting a configuration for the delivery manager from a plurality of configurations, using content of the instant message; querying, by the delivery manager, a user configuration database of the intended recipient to determine one or more available delivery mechanisms supported by the intended recipient; querying, by the delivery manager, a delivery mechanism database to determine the active delivery mechanisms of the client application available for routing the instant message; identifying, by the delivery manager, one or more delivery mechanisms that are common to a result of the querying of the user configuration database and the querying of the delivery mechanism database to yield one or more possible delivery mechanisms; selecting, by the delivery manager, from
  • a messaging environment in which delivery managers are plugged in, dynamically configured at runtime, and used to control the routing of instant messages from users to intended recipients.
  • the delivery managers determine and apply delivery policies, which are based on user configurations, currently available delivery mechanisms, and the configuration of the delivery managers.
  • an instant message delivery environment which integrates multiple protocols and notification services to provide a more robust, intelligent technique of synchronous communication.
  • FIG. 1 depicts one embodiment of a computing environment incorporating and using aspects of the present invention
  • FIG. 2 depicts one embodiment of the logic associated with routing an instant message using a configurable and pluggable delivery manager, in accordance with an aspect of the present invention
  • FIG. 3 depicts one example of an instant message, in accordance with an aspect of the present invention.
  • FIG. 4 depicts one embodiment of a delivery manager database, in accordance with an aspect of the present invention.
  • FIG. 5 depicts one example of a delivery manager configuration database, in accordance with an aspect of the present invention.
  • FIG. 6 depicts one embodiment of a user configuration database, in accordance with an aspect of the present invention.
  • FIG. 7 depicts one example of a delivery mechanism database, in accordance with an aspect of the present invention.
  • FIG. 8 depicts a particular routing example, which uses aspects of the present invention.
  • a messaging environment in which delivery managers (i.e., routing logic modules) are plugged in, dynamically configured at run-time, and used to control the routing of instant messages from users to intended recipients (e.g., other users).
  • the delivery managers determine and apply delivery policies, which are based on user configurations, currently available delivery mechanisms, and the configuration of the delivery managers, to route the messages.
  • a computing environment 100 includes, for instance, at least one computing unit 102 coupled to at least one computing unit 104 via a connection 106 .
  • Each computing unit includes, for example, a personal computer, a workstation, a laptop computer, or any other type of computer.
  • each unit is a personal computer based on the UNIX architecture.
  • the connection is a standard connection, such as any type of wire connection, token ring, or network connection, to name just a few examples.
  • the connection is a communications channel, which may include one or more servers.
  • Executing on at least one of the computing units are one or more client applications that wish to send instant messages to one or more intended recipients (such as, users on Computing Unit 2 or other computing units).
  • the client applications run in a messaging environment, which supports multiple diverse delivery managers that are responsible for routing the messages.
  • the delivery managers can be dynamically added and/or configured at runtime.
  • the user can select at runtime which delivery manager to use and how it is to be configured for a particular message.
  • the delivery manager then uses a delivery policy to control delivery of that message.
  • the delivery policy is constrained by recipient configuration, delivery manager configuration, and available delivery mechanisms, as described below.
  • One embodiment of the logic associated with routing an instant message from a user to an intended recipient is described with reference to FIG. 2 .
  • This logic is executed by, for instance, a client application of a computing environment.
  • an instant message 300 includes, for instance, a user name 302 indicating the intended recipient of the message; a message body 304 , including the message to be delivered to the intended recipient; and one or more optional properties 306 .
  • the properties include a variety of features, such as behavior (e.g., the priority of the message), an expiration date of when the message is to expire, and/or any other features, as desired.
  • a delivery manager responsible for routing the particular message, is selected, STEP 202 .
  • the client application presents a drop-down menu of a group of one or more available delivery managers, (e.g., available classes of delivery managers), and the user selects one of those managers.
  • the client application includes logic (e.g., a selection based on criteria, such as intended recipient, etc.) that selects a delivery manager from the group of available delivery managers.
  • the group of delivery managers is stored, for instance, within a database 400 ( FIG. 4 ), which is accessible by the client application. That is, the database includes a list of available delivery managers.
  • the delivery managers are pluggable and hot-swappable (e.g., can be added and/or changed at runtime). In particular, multiple implementations and functional variants of delivery managers may exist simultaneously and be dynamically added, removed or changed.
  • each message is assigned to its own delivery manager.
  • a delivery manager may service multiple messages.
  • a configuration for the delivery manager is selected from, for instance, a delivery manager configuration database, STEP 206 .
  • a delivery manager configuration database 500 includes a configuration table 501 for each delivery manager.
  • Configuration table 501 includes one or more delivery manager configurations 502 for its respective delivery manager. These configurations are used to dynamically configure the delivery manager, at runtime.
  • the delivery manager is initialized with the selected configuration data, STEP 208 ( FIG. 2 ). This dynamically configures the delivery manager, and the delivery manager is ready to begin message routing.
  • the delivery manager defines a routing policy to be used to route the message to the intended recipient, STEP 210 .
  • One component of defining the policy includes querying, by the delivery manager, a user configuration database to determine how the intended recipient would like to receive the message, STEP 212 .
  • a user configuration database 600 includes a delivery mechanism table 602 for each valid message recipient.
  • Each user's table includes configuration information 604 for one or more of the delivery mechanisms of the computing environment that are supported by that user. That is, each intended recipient is a logical user that has a presence at one or more logical locations, as defined by the table.
  • the configuration information includes an identification of each delivery mechanism supported by the user (e.g., Instant Messaging (IM) Protocol 2, Email, Pager), and mechanism-specific configurations.
  • the user name of the message is used as an index into the user configuration database to locate the table corresponding to that user.
  • the delivery manager accesses the table to determine how the intended recipient desires to receive the message.
  • the user name is John Smith
  • the mechanisms for John Smith include: Instant Messaging Protocol 2, Email and Pager.
  • the delivery manager in addition to querying the user configuration database to define a routing policy, the delivery manager also queries a Delivery Mechanism Database to determine the active delivery mechanisms of the computing environment, STEP 214 .
  • a Delivery Mechanism Database is depicted in FIG. 7 .
  • a Delivery Mechanism Database 700 includes one or more delivery mechanisms 702 currently capable of sending messages. This database is dynamically updated by, for instance, the client application to reflect the current operating environment.
  • the intersection of the delivery mechanisms of Delivery Mechanism Configuration Table 602 and the active delivery mechanisms of Delivery Mechanism Database 700 specifies the set of mechanisms available for routing the assigned instant message.
  • the set of mechanisms include Instant Messaging Protocol 2, Email and Pager. This set of mechanisms defines the routing policy to be used to route the message to the intended recipient.
  • the delivery manager implements the routing policy, as constrained, however, by its own configuration, STEP 216 ( FIG. 2 ).
  • This constrained routing policy is referred to herein as the delivery policy.
  • the routing policy yields a set of mechanisms, which includes Instant Messaging Protocol 2, Email and Pager, but the delivery manager configuration does not include Email (see FIG. 5 ), then the delivery manager is limited to using Instant Messaging Protocol 2 and Pager.
  • the delivery manager applies the delivery policy to send the message to the intended recipient.
  • the instant message is dispatched to one or more of the available delivery mechanisms of the delivery policy, serially or in parallel, as defined by the delivery policy.
  • the delivery manager dispatches the instant message to Instant Messaging Protocol 2, and if the recipient is not available, then it initiates an alphanumeric page, after prompting the sender. This is indicated by the selected configuration (Normal Priority) of the delivery manager (see FIG. 5 ).
  • a selected delivery manager 800 is configured with Configuration 802 .
  • the delivery manager queries a Delivery Mechanism Configuration table 804 for John Smith and a Delivery Mechanisms Database 806 to define the routing policy to be used to send the message to John Smith.
  • the routing policy includes Instant Messaging Protocol 2, Alphanumeric Pager, and Email.
  • the routing policy is constrained by configuration 802 . That is, the delivery manager cannot use a mechanism that is not available to the delivery manager.
  • the delivery manager defines a delivery policy, which is the routing policy constrained by configuration 802 .
  • the delivery policy includes Instant Messaging Protocol 2 ( 808 ) and Pager ( 810 ).
  • the delivery manager uses one or more of the mechanisms of the delivery policy to route the message to John Smith.
  • the manner in which these mechanisms are used is defined by configuration 802 .
  • the message is first sent by Instant Messaging Protocol 2, and then by pager, after prompting the sender.
  • the invention is not limited to such example.
  • additional and/or different delivery managers and/or delivery manager configurations are possible.
  • different recipients may have additional and/or different delivery mechanisms available to them.
  • additional and/or different message delivery mechanisms may be available.
  • the delivery environment integrates multiple protocols and notification services to assist in providing a more robust, intelligent technique of synchronous communication.
  • the environment provides robust message delivery by automatically leveraging and dynamically configuring many unreliable services simultaneously.
  • a user e.g., one logical user
  • the system assigns it to a delivery manager.
  • the delivery manager is an agent which assumes responsibility for routing the logical content of the message to the recipient.
  • Message recipients have corresponding profiles, which specify how they may be contacted via different delivery mechanisms or messaging services.
  • a delivery manager agent adheres to a delivery policy, which includes a message routing algorithm paired with an agent-specific configuration.
  • both the delivery managers and the delivery mechanisms are pluggable and hot-swappable, meaning that multiple implementations or functional variants may exist simultaneously and be dynamically added or removed.
  • Delivery mechanisms support a common set of instant messaging functionality, providing an abstraction over a wide variety of network protocols and notification services.
  • Delivery managers support a common message routing interface, with each variant implementing different delivery policies. Delivery policies may utilize any of the delivery mechanisms available at the time a message is dispatched. Delivery managers are selected on a per-message basis, according to user configurations, such as message priority.
  • one or more aspects of the present invention provide higher rates of successful message delivery, as compared to state of the art instant messaging solutions; incorporate delivery mechanisms not typically associated with instant messaging clients (e.g., pagers, e-mail); provide users with fine-grained, accurate control over message routing behavior, without requiring interaction on a per-message basis; and support new message delivery mechanisms (pluggable system components) that may be implemented and distributed apart from the core system, which allows incremental refinements and extensions.
  • the client-side delivery managers efficiently route messages by applying these constraints based on the current operating environment and individual message requirements.
  • the present invention can be included in an article of manufacture (e.g., one or more computer program products) having, for instance, computer usable media.
  • the media has embodied therein, for instance, computer readable program code means for providing and facilitating the capabilities of the present invention.
  • the article of manufacture can be included as a part of a computer system or sold separately.
  • At least one program storage device readable by a machine, tangibly embodying at least one program of instructions executable by the machine to perform the capabilities of the present invention can be provided.

Abstract

Configurable, pluggable delivery managers are responsible for routing instant messages to intended recipients. A delivery manager is selected for a particular message, and that delivery manager defines, at runtime, a delivery policy to be used to route the instant message to an intended recipient of the message. The delivery policy is based upon a configuration of the delivery manager, a user configuration of the intended recipient, and one or more available delivery mechanisms. The delivery manager routes the instant message using the delivery policy.

Description

    CROSS-REFERENCE TO RELATED APPLICATIONS
  • This application is a continuation of co-pending U.S. patent application Ser. No. 11/037,857, filed Jan. 18, 2005, entitled “Routing Instant Messages Using Configurable Pluggable Delivery Managers,” by Matsa et al., which is a divisional of co-pending U.S. patent application Ser. No. 09/866,410, filed May 25, 2001, entitled “Routing Instant Messages Using Configurable, Pluggable Delivery Managers,” the entirety of each being hereby incorporated herein by reference.
  • TECHNICAL FIELD
  • This invention relates, in general, to instant messaging, and in particular, to providing a messaging environment in which configurable, pluggable delivery managers are used to route instant messages to intended recipients.
  • BACKGROUND OF THE INVENTION
  • In today's communication environments, instant messaging is common place. Users send messages to one or more intended recipients and expect that those messages will be delivered substantially instantly. Various mechanisms are used for instant messaging, including one or more instant messaging protocols, such as the SameTime protocol offered by International Business Machines Corporation or Instant Messenger offered by AOL. Other techniques are also used to send instant messages, such as pager gateways.
  • Although instant messaging is a common practice, frequently there are situations in which the message does not reach the intended recipient. For example, the messaging protocol is down or the intended recipient does not have access to the protocol sending the message (e.g., no computer access).
  • Thus, there is still a need for a capability that enhances the success rate with which an instant message reaches the intended recipient. A further need exists for an environment that is capable of providing a configurable and flexible delivery policy to be used to route messages to intended recipients.
  • SUMMARY OF THE INVENTION
  • The shortcomings of the prior art are overcome and additional advantages are provided through the provision of a system of routing instant messages. The system includes, for instance, a computer system to include instructions to execute a method. The method includes, for instance, selecting a delivery manager from a plurality of available delivery managers, via a client application to route an instant message to an intended recipient of the instant message, wherein the delivery manager is pluggable; configuring the delivery manager at runtime via the client application, wherein the configuring includes selecting a configuration for the delivery manager from a plurality of configurations, using content of the instant message; querying, by the delivery manager, a user configuration database of the intended recipient to determine one or more available delivery mechanisms supported by the intended recipient; querying, by the delivery manager, a delivery mechanism database to determine the active delivery mechanisms of the client application available for routing the instant message; identifying, by the delivery manager, one or more delivery mechanisms that are common to a result of the querying of the user configuration database and the querying of the delivery mechanism database to yield one or more possible delivery mechanisms; selecting, by the delivery manager, from the one or more possible delivery mechanisms, at least one delivery mechanism supported by the delivery manager; and routing, by the delivery manager, the instant message to the intended recipient using the at least one delivery mechanism.
  • Method and computer program products corresponding to the above-summarized claim are also described and may be claimed herein.
  • Advantageously, a messaging environment is provided, in which delivery managers are plugged in, dynamically configured at runtime, and used to control the routing of instant messages from users to intended recipients. The delivery managers determine and apply delivery policies, which are based on user configurations, currently available delivery mechanisms, and the configuration of the delivery managers.
  • In an aspect of the present invention, an instant message delivery environment is provided, which integrates multiple protocols and notification services to provide a more robust, intelligent technique of synchronous communication.
  • Additional features and advantages are realized through the techniques of the present invention. Other embodiments and aspects of the invention are described in detail herein and are considered a part of the claimed invention.
  • BRIEF DESCRIPTION OF THE DRAWINGS
  • The subject matter which is regarded as the invention is particularly pointed out and distinctly claimed in the claims at the conclusion of the specification. The foregoing and other objects, features, and advantages of the invention are apparent from the following detailed description taken in conjunction with the accompanying drawings in which:
  • FIG. 1 depicts one embodiment of a computing environment incorporating and using aspects of the present invention;
  • FIG. 2 depicts one embodiment of the logic associated with routing an instant message using a configurable and pluggable delivery manager, in accordance with an aspect of the present invention;
  • FIG. 3 depicts one example of an instant message, in accordance with an aspect of the present invention;
  • FIG. 4 depicts one embodiment of a delivery manager database, in accordance with an aspect of the present invention;
  • FIG. 5 depicts one example of a delivery manager configuration database, in accordance with an aspect of the present invention;
  • FIG. 6 depicts one embodiment of a user configuration database, in accordance with an aspect of the present invention;
  • FIG. 7 depicts one example of a delivery mechanism database, in accordance with an aspect of the present invention; and
  • FIG. 8 depicts a particular routing example, which uses aspects of the present invention.
  • DETAILED DESCRIPTION OF THE INVENTION
  • In accordance with an aspect of the present invention, a messaging environment is provided, in which delivery managers (i.e., routing logic modules) are plugged in, dynamically configured at run-time, and used to control the routing of instant messages from users to intended recipients (e.g., other users). The delivery managers determine and apply delivery policies, which are based on user configurations, currently available delivery mechanisms, and the configuration of the delivery managers, to route the messages.
  • One embodiment of a computing environment incorporating and using aspects of the present invention is depicted in FIG. 1. As depicted in FIG. 1, a computing environment 100 includes, for instance, at least one computing unit 102 coupled to at least one computing unit 104 via a connection 106. Each computing unit includes, for example, a personal computer, a workstation, a laptop computer, or any other type of computer. As one example, each unit is a personal computer based on the UNIX architecture. Further, the connection is a standard connection, such as any type of wire connection, token ring, or network connection, to name just a few examples. Alternatively, the connection is a communications channel, which may include one or more servers.
  • Executing on at least one of the computing units (e.g., Computing Unit 1) are one or more client applications that wish to send instant messages to one or more intended recipients (such as, users on Computing Unit 2 or other computing units). The client applications run in a messaging environment, which supports multiple diverse delivery managers that are responsible for routing the messages.
  • In accordance with an aspect of the present invention, the delivery managers can be dynamically added and/or configured at runtime. Thus, the user can select at runtime which delivery manager to use and how it is to be configured for a particular message. The delivery manager then uses a delivery policy to control delivery of that message. The delivery policy is constrained by recipient configuration, delivery manager configuration, and available delivery mechanisms, as described below.
  • One embodiment of the logic associated with routing an instant message from a user to an intended recipient is described with reference to FIG. 2. This logic is executed by, for instance, a client application of a computing environment.
  • Referring to FIG. 2, initially, a user composes an instant message to be sent to the recipient, STEP 200. One example of such a message is depicted in FIG. 3. As shown, an instant message 300 includes, for instance, a user name 302 indicating the intended recipient of the message; a message body 304, including the message to be delivered to the intended recipient; and one or more optional properties 306. As one example, the properties include a variety of features, such as behavior (e.g., the priority of the message), an expiration date of when the message is to expire, and/or any other features, as desired.
  • Returning to FIG. 2, in addition to composing the message, a delivery manager, responsible for routing the particular message, is selected, STEP 202. For example, the client application presents a drop-down menu of a group of one or more available delivery managers, (e.g., available classes of delivery managers), and the user selects one of those managers. As a further example, the client application includes logic (e.g., a selection based on criteria, such as intended recipient, etc.) that selects a delivery manager from the group of available delivery managers.
  • The group of delivery managers is stored, for instance, within a database 400 (FIG. 4), which is accessible by the client application. That is, the database includes a list of available delivery managers. The delivery managers are pluggable and hot-swappable (e.g., can be added and/or changed at runtime). In particular, multiple implementations and functional variants of delivery managers may exist simultaneously and be dynamically added, removed or changed.
  • Referring again to FIG. 2, subsequent to selecting a particular class of delivery manager, an instance of the delivery manager is created and the message is assigned thereto, STEP 204. In the example presented herein, each message is assigned to its own delivery manager. However, in other embodiments, a delivery manager may service multiple messages.
  • Thereafter, a configuration for the delivery manager is selected from, for instance, a delivery manager configuration database, STEP 206. An example of one such database is depicted in FIG. 5. As shown, a delivery manager configuration database 500 includes a configuration table 501 for each delivery manager. Configuration table 501 includes one or more delivery manager configurations 502 for its respective delivery manager. These configurations are used to dynamically configure the delivery manager, at runtime.
  • In one embodiment, the particular configuration for the chosen delivery manager is selected based on the content of the message. For example, a value of one of the properties, such as priority, is used to determine which configuration is selected. That is, if Priority=Normal (see 306 of FIG. 3), then the configuration for Normal Priority (see FIG. 5) is selected. Similarly, if Priority=Urgent, then the configuration for Urgent Priority is selected.
  • Subsequent to selecting a configuration for the delivery manager, the delivery manager is initialized with the selected configuration data, STEP 208 (FIG. 2). This dynamically configures the delivery manager, and the delivery manager is ready to begin message routing.
  • As an initial step of the routing process, the delivery manager defines a routing policy to be used to route the message to the intended recipient, STEP 210. One component of defining the policy includes querying, by the delivery manager, a user configuration database to determine how the intended recipient would like to receive the message, STEP 212.
  • One example of a user configuration database is depicted in FIG. 6. A user configuration database 600 includes a delivery mechanism table 602 for each valid message recipient. Each user's table includes configuration information 604 for one or more of the delivery mechanisms of the computing environment that are supported by that user. That is, each intended recipient is a logical user that has a presence at one or more logical locations, as defined by the table.
  • The configuration information includes an identification of each delivery mechanism supported by the user (e.g., Instant Messaging (IM) Protocol 2, Email, Pager), and mechanism-specific configurations. The mechanism-specific configurations include data, such as recipient login names on specific servers (e.g., user=jsmith@im.net, etc.), public keys for encrypted messaging protocols, etc.
  • The user name of the message is used as an index into the user configuration database to locate the table corresponding to that user. The delivery manager accesses the table to determine how the intended recipient desires to receive the message. In the example depicted in FIG. 6, the user name is John Smith, and the mechanisms for John Smith include: Instant Messaging Protocol 2, Email and Pager.
  • Returning to FIG. 2, in addition to querying the user configuration database to define a routing policy, the delivery manager also queries a Delivery Mechanism Database to determine the active delivery mechanisms of the computing environment, STEP 214. One example of such a database is depicted in FIG. 7.
  • As shown in FIG. 7, a Delivery Mechanism Database 700 includes one or more delivery mechanisms 702 currently capable of sending messages. This database is dynamically updated by, for instance, the client application to reflect the current operating environment.
  • The intersection of the delivery mechanisms of Delivery Mechanism Configuration Table 602 and the active delivery mechanisms of Delivery Mechanism Database 700 specifies the set of mechanisms available for routing the assigned instant message. For instance, in the particular example depicted herein, the set of mechanisms include Instant Messaging Protocol 2, Email and Pager. This set of mechanisms defines the routing policy to be used to route the message to the intended recipient.
  • The delivery manager implements the routing policy, as constrained, however, by its own configuration, STEP 216 (FIG. 2). (This constrained routing policy is referred to herein as the delivery policy.) For example, if the routing policy yields a set of mechanisms, which includes Instant Messaging Protocol 2, Email and Pager, but the delivery manager configuration does not include Email (see FIG. 5), then the delivery manager is limited to using Instant Messaging Protocol 2 and Pager.
  • The delivery manager applies the delivery policy to send the message to the intended recipient. In particular, the instant message is dispatched to one or more of the available delivery mechanisms of the delivery policy, serially or in parallel, as defined by the delivery policy. In this example, the delivery manager dispatches the instant message to Instant Messaging Protocol 2, and if the recipient is not available, then it initiates an alphanumeric page, after prompting the sender. This is indicated by the selected configuration (Normal Priority) of the delivery manager (see FIG. 5).
  • An overview of the particular example described herein is illustrated in FIG. 8. As shown, a selected delivery manager 800 is configured with Configuration 802. The delivery manager queries a Delivery Mechanism Configuration table 804 for John Smith and a Delivery Mechanisms Database 806 to define the routing policy to be used to send the message to John Smith. In this example, the routing policy includes Instant Messaging Protocol 2, Alphanumeric Pager, and Email. The routing policy, however, is constrained by configuration 802. That is, the delivery manager cannot use a mechanism that is not available to the delivery manager. Thus, the delivery manager defines a delivery policy, which is the routing policy constrained by configuration 802. In this example, the delivery policy includes Instant Messaging Protocol 2 (808) and Pager (810).
  • The delivery manager then uses one or more of the mechanisms of the delivery policy to route the message to John Smith. The manner in which these mechanisms are used is defined by configuration 802. Thus, in this example, the message is first sent by Instant Messaging Protocol 2, and then by pager, after prompting the sender.
  • Although a particular example is described above, the invention is not limited to such example. For example, additional and/or different delivery managers and/or delivery manager configurations are possible. Further, different recipients may have additional and/or different delivery mechanisms available to them. Also, at various times, additional and/or different message delivery mechanisms may be available.
  • Described in detail above is a pluggable, agent-driven, constraint-based instant messaging delivery environment. The delivery environment integrates multiple protocols and notification services to assist in providing a more robust, intelligent technique of synchronous communication. The environment provides robust message delivery by automatically leveraging and dynamically configuring many unreliable services simultaneously. When a user (e.g., one logical user) composes a message and dispatches it to one or more intended recipients (e.g., one or more other logical users on the same or different computing units), the system assigns it to a delivery manager. The delivery manager is an agent which assumes responsibility for routing the logical content of the message to the recipient. Message recipients have corresponding profiles, which specify how they may be contacted via different delivery mechanisms or messaging services. A delivery manager agent adheres to a delivery policy, which includes a message routing algorithm paired with an agent-specific configuration.
  • In one aspect of the invention, both the delivery managers and the delivery mechanisms are pluggable and hot-swappable, meaning that multiple implementations or functional variants may exist simultaneously and be dynamically added or removed. Delivery mechanisms support a common set of instant messaging functionality, providing an abstraction over a wide variety of network protocols and notification services. Delivery managers support a common message routing interface, with each variant implementing different delivery policies. Delivery policies may utilize any of the delivery mechanisms available at the time a message is dispatched. Delivery managers are selected on a per-message basis, according to user configurations, such as message priority.
  • Advantageously, one or more aspects of the present invention provide higher rates of successful message delivery, as compared to state of the art instant messaging solutions; incorporate delivery mechanisms not typically associated with instant messaging clients (e.g., pagers, e-mail); provide users with fine-grained, accurate control over message routing behavior, without requiring interaction on a per-message basis; and support new message delivery mechanisms (pluggable system components) that may be implemented and distributed apart from the core system, which allows incremental refinements and extensions. The client-side delivery managers efficiently route messages by applying these constraints based on the current operating environment and individual message requirements.
  • The above-described computing environment and/or computing units are only offered as examples. The present invention can be incorporated and used with many types of computing units, computers, processors, nodes, systems, work stations, and/or environments without departing from the spirit of the present invention.
  • The present invention can be included in an article of manufacture (e.g., one or more computer program products) having, for instance, computer usable media. The media has embodied therein, for instance, computer readable program code means for providing and facilitating the capabilities of the present invention. The article of manufacture can be included as a part of a computer system or sold separately.
  • Additionally, at least one program storage device readable by a machine, tangibly embodying at least one program of instructions executable by the machine to perform the capabilities of the present invention can be provided.
  • The flow diagrams depicted herein are just examples. There may be many variations to these diagrams or the steps (or operations) described therein without departing from the spirit of the invention. For instance, the steps may be performed in a differing order, or steps may be added, deleted or modified. All of these variations are considered a part of the claimed invention.
  • Although preferred embodiments have been depicted and described in detail herein, it will be apparent to those skilled in the relevant art that various modifications, additions, substitutions and the like can be made without departing from the spirit of the invention and these are therefore considered to be within the scope of the invention as defined in the following claims.

Claims (14)

1. A system of routing instant messages, said system comprising:
a computer system to include instructions to execute a method, said method comprising:
selecting a delivery manager from a plurality of available delivery managers, via a client application to route an instant message to an intended recipient of the instant message, wherein said delivery manager is pluggable;
configuring said delivery manager at runtime via the client application, wherein said configuring comprises selecting a configuration for said delivery manager from a plurality of configurations using content of the instant message;
querying, by the delivery manager, a user configuration database of the intended recipient to determine one or more available delivery mechanisms supported by the intended recipient;
querying, by the delivery manager, a delivery mechanism database to determine the active delivery mechanisms of the client application available for routing the instant message;
identifying, by the delivery manager, one or more delivery mechanisms that are common to a result of the querying of the user configuration database and the querying of the delivery mechanism database to yield one or more possible delivery mechanisms;
selecting, by the delivery manager, from the one or more possible delivery mechanisms, at least one delivery mechanism supported by the delivery manager; and
routing, by the delivery manager, the instant message to the intended recipient using the at least one delivery mechanism.
2. The system of claim 1, wherein said at least one delivery mechanism supported by the delivery manager is included within the configuration of the delivery manager.
3. The system of claim 1, wherein said routing comprises dispatching, by the delivery manager, the instant message to one or more delivery mechanisms of the at least one delivery mechanism in accordance with a policy specified by said configuration of the delivery manager.
4. The system of claim 1, wherein at least one available delivery mechanism of said one or more available delivery mechanisms is pluggable.
5. The system of claim 1, wherein the delivery manager comprises a routing logic module.
6. The system of claim 1, further comprising creating an instance of the delivery manager based on the selected particular delivery managers.
7. The system of claim 1, wherein the selecting the configuration based on content comprises selecting the configuration based on priority of the instant message to be routed.
8. At least one program storage device readable by a machine, tangibly embodying at least one program of instructions executable by the machine to perform a method of routing instant messages, said method comprising:
selecting a delivery manager from a plurality of available delivery managers, via a client application to route an instant message to an intended recipient of the instant message, wherein said delivery manager is pluggable;
configuring said delivery manager at runtime via the client application, wherein the configuring comprises selecting a configuration for said delivery manager from a plurality of configurations using content of the instant message;
querying, by the delivery manager, a user configuration database of the intended recipient to determine one or more available delivery mechanisms supported by the intended recipient;
querying, by the delivery manager, a delivery mechanism database to determine the active delivery mechanisms of the client application available for routing the instant message;
identifying, by the delivery manager, one or more delivery mechanisms that are common to a result of the querying of the user configuration database and the querying of the delivery mechanism database to yield one or more possible delivery mechanisms;
selecting, by the delivery manager, from the one or more possible delivery mechanisms, at least one delivery mechanism supported by the delivery manager; and
routing, by the delivery manager, the instant message to the intended recipient using the at least one delivery mechanism.
9. The at least one program storage device of claim 8, wherein said at least one delivery mechanism supported by the delivery manager is included within the configuration of the delivery manager.
10. The at least one program storage device of claim 8, wherein said routing comprises dispatching, by the delivery manager, the instant message to one or more delivery mechanisms of the at least one delivery mechanism in accordance with a policy specified by said configuration of the delivery manager.
11. The at least one program storage device of claim 8, wherein at least one available delivery mechanism of said one or more available delivery mechanisms is pluggable.
12. The at least one program storage device of claim 8, wherein the delivery manager comprises a routing logic module.
13. The at least one program storage device of claim 8, further comprising creating an instance of the delivery manager based on the selected particular delivery managers.
14. The at least one program storage device of claim 8, wherein the selecting the configuration based on content comprises selecting the configuration based on priority of the instant message to be routed.
US12/179,610 2001-05-25 2008-07-25 Routing instant messages using configurable, pluggable delivery managers Abandoned US20080281937A1 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
US12/179,610 US20080281937A1 (en) 2001-05-25 2008-07-25 Routing instant messages using configurable, pluggable delivery managers

Applications Claiming Priority (3)

Application Number Priority Date Filing Date Title
US09/866,410 US20020178227A1 (en) 2001-05-25 2001-05-25 Routing instant messages using configurable, pluggable delivery managers
US11/037,857 US7412490B2 (en) 2001-05-25 2005-01-18 Routing instant messages using configurable, pluggable delivery managers
US12/179,610 US20080281937A1 (en) 2001-05-25 2008-07-25 Routing instant messages using configurable, pluggable delivery managers

Related Parent Applications (1)

Application Number Title Priority Date Filing Date
US11/037,857 Continuation US7412490B2 (en) 2001-05-25 2005-01-18 Routing instant messages using configurable, pluggable delivery managers

Publications (1)

Publication Number Publication Date
US20080281937A1 true US20080281937A1 (en) 2008-11-13

Family

ID=25347549

Family Applications (4)

Application Number Title Priority Date Filing Date
US09/866,410 Abandoned US20020178227A1 (en) 2001-05-25 2001-05-25 Routing instant messages using configurable, pluggable delivery managers
US10/193,632 Expired - Fee Related US7284034B2 (en) 2001-05-25 2002-07-11 Transparent combination of instant message protocols
US11/037,857 Expired - Fee Related US7412490B2 (en) 2001-05-25 2005-01-18 Routing instant messages using configurable, pluggable delivery managers
US12/179,610 Abandoned US20080281937A1 (en) 2001-05-25 2008-07-25 Routing instant messages using configurable, pluggable delivery managers

Family Applications Before (3)

Application Number Title Priority Date Filing Date
US09/866,410 Abandoned US20020178227A1 (en) 2001-05-25 2001-05-25 Routing instant messages using configurable, pluggable delivery managers
US10/193,632 Expired - Fee Related US7284034B2 (en) 2001-05-25 2002-07-11 Transparent combination of instant message protocols
US11/037,857 Expired - Fee Related US7412490B2 (en) 2001-05-25 2005-01-18 Routing instant messages using configurable, pluggable delivery managers

Country Status (2)

Country Link
US (4) US20020178227A1 (en)
JP (1) JP4384839B2 (en)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20120303734A1 (en) * 2011-09-13 2012-11-29 Whitmyer Jr Wesley W Electronic messaging system with configurable delivery that maintains recipient privacy

Families Citing this family (89)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6732101B1 (en) * 2000-06-15 2004-05-04 Zix Corporation Secure message forwarding system detecting user's preferences including security preferences
US8972717B2 (en) * 2000-06-15 2015-03-03 Zixcorp Systems, Inc. Automatic delivery selection for electronic content
US8086672B2 (en) * 2000-06-17 2011-12-27 Microsoft Corporation When-free messaging
US20040073617A1 (en) 2000-06-19 2004-04-15 Milliken Walter Clark Hash-based systems and methods for detecting and preventing transmission of unwanted e-mail
US7929562B2 (en) 2000-11-08 2011-04-19 Genesis Telecommunications Laboratories, Inc. Method and apparatus for optimizing response time to events in queue
US6822945B2 (en) 2000-11-08 2004-11-23 Genesys Telecommunications Laboratories, Inc. Method and apparatus for anticipating and planning communication-center resources based on evaluation of events waiting in a communication center master queue
US7299259B2 (en) * 2000-11-08 2007-11-20 Genesys Telecommunications Laboratories, Inc. Method and apparatus for intelligent routing of instant messaging presence protocol (IMPP) events among a group of customer service representatives
US8583745B2 (en) * 2000-11-16 2013-11-12 Opendesign, Inc. Application platform
US7809854B2 (en) * 2002-02-12 2010-10-05 Open Design, Inc. Logical routing system
US7269627B2 (en) * 2001-07-27 2007-09-11 Intel Corporation Routing messages using presence information
US6985961B1 (en) * 2001-12-04 2006-01-10 Nortel Networks Limited System for routing incoming message to various devices based on media capabilities and type of media session
US20060015942A1 (en) 2002-03-08 2006-01-19 Ciphertrust, Inc. Systems and methods for classification of messaging entities
US7693947B2 (en) * 2002-03-08 2010-04-06 Mcafee, Inc. Systems and methods for graphically displaying messaging traffic
US7458098B2 (en) * 2002-03-08 2008-11-25 Secure Computing Corporation Systems and methods for enhancing electronic communication security
US7694128B2 (en) * 2002-03-08 2010-04-06 Mcafee, Inc. Systems and methods for secure communication delivery
US8132250B2 (en) 2002-03-08 2012-03-06 Mcafee, Inc. Message profiling systems and methods
US8561167B2 (en) 2002-03-08 2013-10-15 Mcafee, Inc. Web reputation scoring
US7096498B2 (en) 2002-03-08 2006-08-22 Cipher Trust, Inc. Systems and methods for message threat management
US7903549B2 (en) 2002-03-08 2011-03-08 Secure Computing Corporation Content-based policy compliance systems and methods
US8578480B2 (en) 2002-03-08 2013-11-05 Mcafee, Inc. Systems and methods for identifying potentially malicious messages
US7870203B2 (en) * 2002-03-08 2011-01-11 Mcafee, Inc. Methods and systems for exposing messaging reputation to an end user
US7124438B2 (en) * 2002-03-08 2006-10-17 Ciphertrust, Inc. Systems and methods for anomaly detection in patterns of monitored communications
US7657616B1 (en) * 2002-06-10 2010-02-02 Quest Software, Inc. Automatic discovery of users associated with screen names
US7818565B2 (en) * 2002-06-10 2010-10-19 Quest Software, Inc. Systems and methods for implementing protocol enforcement rules
US7428590B2 (en) 2002-06-10 2008-09-23 Akonix Systems, Inc. Systems and methods for reflecting messages associated with a target protocol within a network
CA2488731A1 (en) * 2002-06-10 2003-12-18 Akonix Systems, Inc. Systems and methods for a protocol gateway
US7707401B2 (en) * 2002-06-10 2010-04-27 Quest Software, Inc. Systems and methods for a protocol gateway
US7774832B2 (en) * 2002-06-10 2010-08-10 Quest Software, Inc. Systems and methods for implementing protocol enforcement rules
US20080196099A1 (en) * 2002-06-10 2008-08-14 Akonix Systems, Inc. Systems and methods for detecting and blocking malicious content in instant messages
US7596599B1 (en) * 2002-07-31 2009-09-29 Facetime Communications, Inc. Management capabilities for real-time messaging networks
USRE46776E1 (en) 2002-08-27 2018-04-03 Genesys Telecommunications Laboratories, Inc. Method and apparatus for optimizing response time to events in queue
US7945846B2 (en) 2002-09-06 2011-05-17 Oracle International Corporation Application-specific personalization for data display
US7912899B2 (en) * 2002-09-06 2011-03-22 Oracle International Corporation Method for selectively sending a notification to an instant messaging device
US7941542B2 (en) 2002-09-06 2011-05-10 Oracle International Corporation Methods and apparatus for maintaining application execution over an intermittent network connection
US7412481B2 (en) 2002-09-16 2008-08-12 Oracle International Corporation Method and apparatus for distributed rule evaluation in a near real-time business intelligence system
US8255454B2 (en) 2002-09-06 2012-08-28 Oracle International Corporation Method and apparatus for a multiplexed active data window in a near real-time business intelligence system
US7899879B2 (en) 2002-09-06 2011-03-01 Oracle International Corporation Method and apparatus for a report cache in a near real-time business intelligence system
US8165993B2 (en) 2002-09-06 2012-04-24 Oracle International Corporation Business intelligence system with interface that provides for immediate user action
US7401158B2 (en) 2002-09-16 2008-07-15 Oracle International Corporation Apparatus and method for instant messaging collaboration
CN1525322A (en) * 2003-02-27 2004-09-01 Ħ��������˾ System and apparatus for dynamically downloading instant information protocol and method thereof
US7761516B2 (en) * 2003-03-06 2010-07-20 Siemens Enterprise Communications, Inc. System and method for e-mail presence confirmation
US7698367B2 (en) * 2003-03-06 2010-04-13 Siemens Communications, Inc. System and method for presence enabled e-mail delivery
US7693952B2 (en) * 2003-03-27 2010-04-06 Microsoft Corporation Availability and scalability in a messaging system in a manner transparent to the application
US7539728B2 (en) * 2003-08-07 2009-05-26 International Business Machines Corporation Time sensitive electronic mail
US20050055412A1 (en) * 2003-09-04 2005-03-10 International Business Machines Corporation Policy-based management of instant message windows
US20050055405A1 (en) * 2003-09-04 2005-03-10 International Business Machines Corporation Managing status information for instant messaging users
US20050125496A1 (en) * 2003-12-03 2005-06-09 International Business Machines Corporation Automatically initiating an instant messaging action when a subscriber's availability status changes
DE60313187T2 (en) * 2003-12-08 2007-12-20 Research In Motion Ltd., Waterloo Method and device for instant message service
US7430754B2 (en) * 2004-03-23 2008-09-30 Microsoft Corporation Method for dynamic application of rights management policy
EP2259492A1 (en) 2004-05-03 2010-12-08 Research In Motion Limited User interface for integrating applications on a mobile communication device
US20060031317A1 (en) * 2004-06-04 2006-02-09 Wanrong Lin System for synthesizing instant message and presence attributes from polled, queried and event information sources
US20060047770A1 (en) * 2004-09-02 2006-03-02 International Business Machines Corporation Direct information copy and transfer between real-time messaging applications
US8635690B2 (en) 2004-11-05 2014-01-21 Mcafee, Inc. Reputation based message processing
US7730143B1 (en) * 2004-12-01 2010-06-01 Aol Inc. Prohibiting mobile forwarding
US8156485B2 (en) * 2004-12-03 2012-04-10 Google Inc. Method and apparatus for creating a pluggable, prioritized configuration engine to be used for configuring a software during installation, update and new profile creation
US7475396B2 (en) * 2004-12-03 2009-01-06 International Business Machines Corporation Method and apparatus for defining, building and deploying pluggable and independently configurable install components
US7734695B2 (en) * 2005-03-08 2010-06-08 International Business Machines Corporation Personal and timed chat interface
US7937480B2 (en) 2005-06-02 2011-05-03 Mcafee, Inc. Aggregation of reputation data
US20060277262A1 (en) * 2005-06-06 2006-12-07 Boss Gregory J Session management enhancements for instant messaging applications
US20070005711A1 (en) * 2005-07-01 2007-01-04 Imiogic, Inc. System and method for building instant messaging applications
FR2888706A1 (en) * 2005-07-12 2007-01-19 France Telecom METHOD FOR INTERPERSONAL RELATIONSHIP
US8706817B2 (en) * 2005-07-21 2014-04-22 International Business Machines Corporation Sender managed message privacy
EP1946217A2 (en) 2005-11-03 2008-07-23 Akonix Systems, Inc. Systems and methods for remote rogue protocol enforcement
US20070184855A1 (en) 2006-02-03 2007-08-09 Research In Motion Limited Visual representation of contact location
US20070239830A1 (en) * 2006-04-05 2007-10-11 Barnes Thomas H Method and apparatus for instant message notification and forwarding
US8364122B2 (en) * 2006-12-21 2013-01-29 International Business Machines Corporation Delayed delivery messaging
US8763114B2 (en) 2007-01-24 2014-06-24 Mcafee, Inc. Detecting image spam
US7779156B2 (en) 2007-01-24 2010-08-17 Mcafee, Inc. Reputation based load balancing
US8214497B2 (en) 2007-01-24 2012-07-03 Mcafee, Inc. Multi-dimensional reputation scoring
US8179798B2 (en) 2007-01-24 2012-05-15 Mcafee, Inc. Reputation based connection throttling
US7949716B2 (en) * 2007-01-24 2011-05-24 Mcafee, Inc. Correlation and analysis of entity attributes
US7885641B2 (en) * 2007-06-18 2011-02-08 Research In Motion Limited Method and system for using subjects in instant messaging sessions on a mobile device
US20090100161A1 (en) * 2007-10-15 2009-04-16 International Business Machines Corporation System and method for managing communications
US8185930B2 (en) 2007-11-06 2012-05-22 Mcafee, Inc. Adjusting filter or classification control settings
US8045458B2 (en) 2007-11-08 2011-10-25 Mcafee, Inc. Prioritizing network traffic
US8214847B2 (en) * 2007-11-16 2012-07-03 Microsoft Corporation Distributed messaging system with configurable assurances
US8160975B2 (en) 2008-01-25 2012-04-17 Mcafee, Inc. Granular support vector machine with random granularity
US8589503B2 (en) 2008-04-04 2013-11-19 Mcafee, Inc. Prioritizing network traffic
US9508059B2 (en) 2008-04-25 2016-11-29 T-Mobile Usa, Inc. Messaging device having a graphical user interface for initiating communication to recipients
US8843565B2 (en) * 2008-06-06 2014-09-23 International Business Machines Corporation Categorizing electronic messaging communications
US8281020B2 (en) * 2008-09-30 2012-10-02 Avaya Inc. Smart load balancing for call center applications
US20100306321A1 (en) * 2009-05-29 2010-12-02 Microsoft Corporation Delivering messages using user-defined agents
US8032624B2 (en) * 2009-06-19 2011-10-04 Avaya Inc. Pluggable contact resolution
US8332758B2 (en) * 2009-11-25 2012-12-11 International Business Machines Corporation Plugin-based user interface contributions to manage policies in an IT environment
US8621638B2 (en) 2010-05-14 2013-12-31 Mcafee, Inc. Systems and methods for classification of messaging entities
US9088624B2 (en) 2011-05-31 2015-07-21 Nokia Technologies Oy Method and apparatus for routing notification messages
US10080135B2 (en) * 2015-03-30 2018-09-18 International Business Machines Corporation Handling instant message delivery media to end user
US10574788B2 (en) * 2016-08-23 2020-02-25 Ebay Inc. System for data transfer based on associated transfer paths
US20210176198A1 (en) * 2019-12-06 2021-06-10 Lenovo Enterprise Solutions (Singapore) Pte. Ltd. Dynamically determining recipients of electronic messages

Citations (21)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US4912457A (en) * 1988-12-21 1990-03-27 Ladd Electronics Detector and message annunciator device
US5408646A (en) * 1991-03-29 1995-04-18 International Business Machines Corp. Multipath torus switching apparatus
US5675507A (en) * 1995-04-28 1997-10-07 Bobo, Ii; Charles R. Message storage and delivery system
US5717741A (en) * 1992-08-26 1998-02-10 Bellsouth Corp. Method for handling telephonic messages
US5742668A (en) * 1994-09-19 1998-04-21 Bell Communications Research, Inc. Electronic massaging network
US5870549A (en) * 1995-04-28 1999-02-09 Bobo, Ii; Charles R. Systems and methods for storing, delivering, and managing messages
US5905777A (en) * 1996-09-27 1999-05-18 At&T Corp. E-mail paging system
US6012084A (en) * 1997-08-01 2000-01-04 International Business Machines Corporation Virtual network communication services utilizing internode message delivery task mechanisms
US6026404A (en) * 1997-02-03 2000-02-15 Oracle Corporation Method and system for executing and operation in a distributed environment
US6038296A (en) * 1997-10-07 2000-03-14 Lucent Technologies Inc. Internet/intranet user interface to a multimedia messaging system
US6075844A (en) * 1997-11-18 2000-06-13 At&T Corp. Messaging system with remote messaging recording device where the message is routed based on the spoken name of the recipient
US6147977A (en) * 1997-12-12 2000-11-14 Motorola, Inc. Method and apparatus for processing messages based on originator and recipient priorities
US6175859B1 (en) * 1998-10-28 2001-01-16 Avaya Technology Corp. Sender-defined time for reporting on the status of a sent message or of the message's recipient
US6260148B1 (en) * 1997-04-04 2001-07-10 Microsoft Corporation Methods and systems for message forwarding and property notifications using electronic subscriptions
US6301609B1 (en) * 1999-07-07 2001-10-09 Lucent Technologies Inc. Assignable associate priorities for user-definable instant messaging buddy groups
US20020087704A1 (en) * 2000-11-30 2002-07-04 Pascal Chesnais Systems and methods for routing messages to communications devices over a communications network
US6430604B1 (en) * 1999-08-03 2002-08-06 International Business Machines Corporation Technique for enabling messaging systems to use alternative message delivery mechanisms
US20020116477A1 (en) * 1999-12-08 2002-08-22 Parvathi Somashekar Technique for configuring network deliverable components
US6463462B1 (en) * 1999-02-02 2002-10-08 Dialogic Communications Corporation Automated system and method for delivery of messages and processing of message responses
US20020160757A1 (en) * 2001-04-26 2002-10-31 Moshe Shavit Selecting the delivery mechanism of an urgent message
US20030105821A1 (en) * 1999-01-11 2003-06-05 Niraj A. Shah Improved server and method for routing messages to achieve unified communications

Family Cites Families (19)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
AU580150B2 (en) * 1985-04-17 1989-01-05 Matsushita Electric Industrial Co., Ltd. Heat cooking apparatus
JPH05347621A (en) * 1992-06-12 1993-12-27 Matsushita Electric Ind Co Ltd Composite medium communication server equipment
JP3431185B2 (en) * 1992-07-24 2003-07-28 株式会社東芝 Communication device and communication method
US5408656A (en) * 1992-09-23 1995-04-18 International Business Machines Corporation Method and system for non-specific address data retrieval in a data storage subsystem which includes multiple datasets stored at specific addresses
JPH07250094A (en) * 1994-03-11 1995-09-26 Ricoh Co Ltd Delivery system for electronic mail
JPH08172440A (en) * 1994-12-16 1996-07-02 Canon Inc Data communication system and its data transfer method
JPH09134319A (en) * 1995-10-03 1997-05-20 Sony Electron Inc User interface for personal communication routing system and rule processing
JP3451512B2 (en) * 1996-01-12 2003-09-29 日本電信電話株式会社 Multimedia information delivery method and system
US5761286A (en) * 1996-03-19 1998-06-02 At&T Corp Method for enabling communications between calling an called multmedia terminals
JP3782867B2 (en) * 1997-06-25 2006-06-07 株式会社日立製作所 Information reception processing method and computer / telephony integration system
JP3755270B2 (en) * 1997-12-25 2006-03-15 カシオ計算機株式会社 Communications system
US6157945A (en) * 1998-07-01 2000-12-05 Ricoh Company, Ltd. Digital communication device and method including a routing function
JP2000172584A (en) * 1998-12-03 2000-06-23 Matsushita Electric Ind Co Ltd Device and method for transmitting and receiving electronic mail
JP3454740B2 (en) * 1999-02-26 2003-10-06 日本電信電話株式会社 Real-time information distribution system
US6691162B1 (en) * 1999-09-21 2004-02-10 America Online, Inc. Monitoring users of a computer network
US7844666B2 (en) * 2000-12-12 2010-11-30 Microsoft Corporation Controls and displays for acquiring preferences, inspecting behavior, and guiding the learning and decision policies of an adaptive communications prioritization and routing system
US6993564B2 (en) * 2000-12-22 2006-01-31 At&T Corp. Method of authorizing receipt of instant messages by a recipient user
US20020116461A1 (en) * 2001-02-05 2002-08-22 Athanassios Diacakis Presence and availability management system
US6771756B1 (en) * 2001-03-01 2004-08-03 International Business Machines Corporation System and method to facilitate team communication

Patent Citations (22)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US4912457A (en) * 1988-12-21 1990-03-27 Ladd Electronics Detector and message annunciator device
US5408646A (en) * 1991-03-29 1995-04-18 International Business Machines Corp. Multipath torus switching apparatus
US5717741A (en) * 1992-08-26 1998-02-10 Bellsouth Corp. Method for handling telephonic messages
US5742668A (en) * 1994-09-19 1998-04-21 Bell Communications Research, Inc. Electronic massaging network
US6350066B1 (en) * 1995-04-28 2002-02-26 Bobo, Ii Charles R. Systems and methods for storing, delivering, and managing messages
US5870549A (en) * 1995-04-28 1999-02-09 Bobo, Ii; Charles R. Systems and methods for storing, delivering, and managing messages
US5675507A (en) * 1995-04-28 1997-10-07 Bobo, Ii; Charles R. Message storage and delivery system
US5905777A (en) * 1996-09-27 1999-05-18 At&T Corp. E-mail paging system
US6026404A (en) * 1997-02-03 2000-02-15 Oracle Corporation Method and system for executing and operation in a distributed environment
US6260148B1 (en) * 1997-04-04 2001-07-10 Microsoft Corporation Methods and systems for message forwarding and property notifications using electronic subscriptions
US6012084A (en) * 1997-08-01 2000-01-04 International Business Machines Corporation Virtual network communication services utilizing internode message delivery task mechanisms
US6038296A (en) * 1997-10-07 2000-03-14 Lucent Technologies Inc. Internet/intranet user interface to a multimedia messaging system
US6075844A (en) * 1997-11-18 2000-06-13 At&T Corp. Messaging system with remote messaging recording device where the message is routed based on the spoken name of the recipient
US6147977A (en) * 1997-12-12 2000-11-14 Motorola, Inc. Method and apparatus for processing messages based on originator and recipient priorities
US6175859B1 (en) * 1998-10-28 2001-01-16 Avaya Technology Corp. Sender-defined time for reporting on the status of a sent message or of the message's recipient
US20030105821A1 (en) * 1999-01-11 2003-06-05 Niraj A. Shah Improved server and method for routing messages to achieve unified communications
US6463462B1 (en) * 1999-02-02 2002-10-08 Dialogic Communications Corporation Automated system and method for delivery of messages and processing of message responses
US6301609B1 (en) * 1999-07-07 2001-10-09 Lucent Technologies Inc. Assignable associate priorities for user-definable instant messaging buddy groups
US6430604B1 (en) * 1999-08-03 2002-08-06 International Business Machines Corporation Technique for enabling messaging systems to use alternative message delivery mechanisms
US20020116477A1 (en) * 1999-12-08 2002-08-22 Parvathi Somashekar Technique for configuring network deliverable components
US20020087704A1 (en) * 2000-11-30 2002-07-04 Pascal Chesnais Systems and methods for routing messages to communications devices over a communications network
US20020160757A1 (en) * 2001-04-26 2002-10-31 Moshe Shavit Selecting the delivery mechanism of an urgent message

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20120303734A1 (en) * 2011-09-13 2012-11-29 Whitmyer Jr Wesley W Electronic messaging system with configurable delivery that maintains recipient privacy
US9147082B2 (en) * 2011-09-13 2015-09-29 Whorlr Llc Electronic messaging system with configurable delivery that maintains recipient privacy

Also Published As

Publication number Publication date
US20050125499A1 (en) 2005-06-09
JP2003101588A (en) 2003-04-04
US20020178231A1 (en) 2002-11-28
US20020178227A1 (en) 2002-11-28
US7412490B2 (en) 2008-08-12
US7284034B2 (en) 2007-10-16
JP4384839B2 (en) 2009-12-16

Similar Documents

Publication Publication Date Title
US7412490B2 (en) Routing instant messages using configurable, pluggable delivery managers
US8051057B2 (en) Processing of network content and services for mobile or fixed devices
US7363345B2 (en) Electronic notification delivery mechanism selection based on recipient presence information and notification content
CA2707536C (en) Processing of network content and services for mobile or fixed devices
EP1021897B1 (en) Messaging application having a plurality of interfacing capabilities
US6604133B2 (en) Inter-enterprise messaging system using bridgehead servers
US6868544B2 (en) Method and system for general-purpose interactive notifications
US7725542B2 (en) Forwarding IM messages to E-mail
US9742717B2 (en) Internet e-mail bridge
US20050004992A1 (en) Server that obtains information from multiple sources, filters using client identities, and dispatches to both hardwired and wireless clients
CA2544717C (en) Storing, sending and receiving text message threads on a wireless communication device
WO2011131262A1 (en) Controlling message delivery in publish/subscribe messaging
US7826406B2 (en) Storing, sending and receiving text message threads on a wireless communication device
AU2002322897B2 (en) Method and apparatus for pushing e-mail to wireless communication devices
US20060086798A1 (en) Deferred email message system and service
US20030018721A1 (en) Unified messaging with separate media component storage
EP0869639A2 (en) Message tracking
EP1713220B1 (en) Method and apparatus for pushing e-mail to wireless communication devices
Marti Active messenger: Email filtering and mobile delivery
EP1540903B1 (en) Method and apparatus for pushing e-mail to wireless communication devices

Legal Events

Date Code Title Description
STCB Information on status: application discontinuation

Free format text: ABANDONED -- FAILURE TO PAY ISSUE FEE