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

Routing instant messages using configurable, pluggable delivery managers Download PDF

Info

Publication number
US20020178227A1
US20020178227A1 US09866410 US86641001A US2002178227A1 US 20020178227 A1 US20020178227 A1 US 20020178227A1 US 09866410 US09866410 US 09866410 US 86641001 A US86641001 A US 86641001A US 2002178227 A1 US2002178227 A1 US 2002178227A1
Authority
US
Grant status
Application
Patent type
Prior art keywords
delivery
manager
policy
mechanisms
pluggable
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
US09866410
Inventor
Moshe Matsa
Julius Quiaot
Christopher 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

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network-specific arrangements or communication protocols supporting networked applications
    • H04L67/32Network-specific arrangements or communication protocols supporting networked applications for scheduling or organising the servicing of application requests, e.g. requests for application data transmissions involving the analysis and optimisation of the required network resources
    • H04L67/327Network-specific arrangements or communication protocols supporting networked applications for scheduling or organising the servicing of application requests, e.g. requests for application data transmissions involving the analysis and optimisation of the required network resources whereby the routing of a service request to a node providing the service depends on the content or context of the request, e.g. profile, connectivity status, payload or application type
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L29/00Arrangements, apparatus, circuits or systems, not covered by a single one of groups H04L1/00 - H04L27/00 contains provisionally no documents
    • H04L29/02Communication control; Communication processing contains provisionally no documents
    • H04L29/06Communication control; Communication processing contains provisionally no documents characterised by a protocol
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00Arrangements for maintenance or administration or management of packet switching networks
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L51/00Arrangements for user-to-user messaging in packet-switching networks, e.g. e-mail or instant messages
    • 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-specific arrangements or communication protocols supporting networked applications
    • H04L67/24Presence management
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L51/00Arrangements for user-to-user messaging in packet-switching networks, e.g. e-mail or instant messages
    • H04L51/14Arrangements for user-to-user messaging in packet-switching networks, e.g. e-mail or instant messages with selective forwarding
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00Application independent communication protocol aspects or techniques in packet data networks
    • H04L69/30Definitions, standards or architectural aspects of layered protocol stacks
    • H04L69/32High level architectural aspects of 7-layer open systems interconnection [OSI] type protocol stacks
    • H04L69/322Aspects of intra-layer communication protocols among peer entities or protocol data unit [PDU] definitions
    • H04L69/329Aspects of intra-layer communication protocols among peer entities or protocol data unit [PDU] definitions in the application layer, i.e. layer seven

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

    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. [0001]
  • 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. [0002]
  • 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). [0003]
  • 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. [0004]
  • SUMMARY OF THE INVENTION
  • The shortcomings of the prior art are overcome and additional advantages are provided through the provision of a method of routing instant messages. The method includes, for instance, defining, at runtime by a pluggable delivery manager, a delivery policy to be used to route an instant message to an intended recipient of the instant message, wherein the delivery policy is based upon a configuration of the pluggable delivery manager, a user configuration of the intended recipient, and one or more available delivery mechanisms; and routing the instant message to the intended recipient using the delivery policy. [0005]
  • In a further aspect of the present invention, a method of routing instant messages is provided. The method includes, for instance, selecting a delivery manager to route an instant message to an intended recipient of the instant message, the delivery manager being pluggable; configuring, at runtime, the delivery manager, wherein the configuring comprises selecting a configuration for the delivery manager from a set of one or more configurations, the selecting using content of the instant message to make the selection; querying, by the delivery manager, a user configuration of the intended recipient to determine one or more delivery mechanisms supported by the intended recipient; determining, by the delivery manager, one or more available delivery mechanisms; identifying, by the delivery manager, one or more delivery mechanisms that are common to a result of the querying and the determining to yield one or more possible delivery mechanisms; selecting, from the one or more possible delivery mechanisms, at least one delivery mechanism supported by the delivery manager; and routing the instant message to the intended recipient using the at least one delivery mechanism. [0006]
  • System and computer program products corresponding to the above-summarized methods are also described and claimed herein. [0007]
  • 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. [0008]
  • 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. [0009]
  • 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.[0010]
  • 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: [0011]
  • FIG. 1 depicts one embodiment of a computing environment incorporating and using aspects of the present invention; [0012]
  • 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; [0013]
  • FIG. 3 depicts one example of an instant message, in accordance with an aspect of the present invention; [0014]
  • FIG. 4 depicts one embodiment of a delivery manager database, in accordance with an aspect of the present invention; [0015]
  • FIG. 5 depicts one example of a delivery manager configuration database, in accordance with an aspect of the present invention; [0016]
  • FIG. 6 depicts one embodiment of a user configuration database, in accordance with an aspect of the present invention; [0017]
  • FIG. 7 depicts one example of a delivery mechanism database, in accordance with an aspect of the present invention; and [0018]
  • FIG. 8 depicts a particular routing example, which uses aspects of the present invention.[0019]
  • BEST MODE FOR CARRYING OUT 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. [0020]
  • 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 [0021] 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 [0022] 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. [0023]
  • 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. [0024]
  • Referring to FIG. 2, initially, a user composes an instant message to be sent to the recipient, STEP [0025] 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 [0026] 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 [0027] 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 [0028] 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 [0029] 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 [0030] 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 [0031] 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 [0032] 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 [0033] 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 [0034] 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 [0035] 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 [0036] 214. One example of such a database is depicted in FIG. 7.
  • As shown in FIG. 7, a Delivery Mechanism Database [0037] 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 [0038] 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 [0039] 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 [0040] 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 [0041] 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 [0042] 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. [0043]
  • 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. [0044]
  • 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. [0045]
  • 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. [0046]
  • 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. [0047]
  • 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. [0048]
  • 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. [0049]
  • 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. [0050]
  • 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. [0051]

Claims (47)

    What is claimed is:
  1. 1. A method of routing instant messages, said method comprising:
    defining, at runtime by a pluggable delivery manager, a delivery policy to be used to route an instant message to an intended recipient of the instant message, wherein the delivery policy is based upon a configuration of the pluggable delivery manager, a user configuration of the intended recipient, and one or more available delivery mechanisms; and
    routing said instant message to the intended recipient using said delivery policy.
  2. 2. The method of claim 1, wherein said defining of the delivery policy comprises:
    defining a routing policy based on said user configuration and said one or more available delivery mechanisms, wherein said routing policy includes one or more possible delivery mechanisms; and
    selecting from the routing policy at least one delivery mechanism to be included in the delivery policy, said selecting being based upon the configuration of the pluggable delivery manager.
  3. 3. The method of claim 1, wherein said defining of the delivery policy comprises:
    determining, from the user configuration, one or more delivery mechanisms supported by said intended recipient;
    determining which of said one or more delivery mechanisms supported by said intended recipient are included in the one or more available delivery mechanisms to yield one or more possible delivery mechanisms; and
    determining which of the one or more possible delivery mechanisms are supported by the pluggable delivery manager, as indicated in the configuration of the pluggable delivery manager, a result of which defines the delivery policy.
  4. 4. The method of claim 3, wherein said routing comprises dispatching the instant message to at least one delivery mechanism of the delivery policy, as indicated by the delivery policy.
  5. 5. The method of claim 1, wherein said routing comprises dispatching the instant message to at least one delivery mechanism of the delivery policy, as indicated by the delivery policy.
  6. 6. The method of claim 1, further comprising selecting the pluggable delivery manager from a plurality of delivery managers.
  7. 7. The method of claim 1, further comprising configuring said pluggable delivery manager.
  8. 8. The method of claim 7, wherein said configuring comprises selecting a configuration for said pluggable delivery manager from a set of one or more configurations, wherein said selecting uses content of the instant message to make the selection.
  9. 9. The method of claim 7, wherein said configuring comprises configuring said pluggable delivery manager at runtime.
  10. 10. The method of claim 1, wherein the intended recipient is indicated by the instant message.
  11. 11. The method of claim 1, wherein at least one available delivery mechanism of said one or more available delivery mechanisms is pluggable.
  12. 12. A method of routing instant messages, said method comprising:
    selecting a delivery manager to route an instant message to an intended recipient of the instant message, said delivery manager being pluggable;
    configuring, at runtime, said delivery manager, wherein the configuring comprises selecting a configuration for said delivery manager from a set of one or more configurations, said selecting using content of the instant message to make the selection;
    querying, by the delivery manager, a user configuration of the intended recipient to determine one or more delivery mechanisms supported by the intended recipient;
    determining, by the delivery manager, one or more available delivery mechanisms;
    identifying, by the delivery manager, one or more delivery mechanisms that are common to a result of the querying and the determining to yield one or more possible delivery mechanisms;
    selecting, from the one or more possible delivery mechanisms, at least one delivery mechanism supported by the delivery manager; and
    routing the instant message to the intended recipient using the at least one delivery mechanism.
  13. 13. The method of claim 12, wherein said at least one delivery mechanism supported by the delivery manager is included within the configuration of the delivery manager.
  14. 14. The method of claim 12, 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.
  15. 15. The method of claim 12, wherein at least one available delivery mechanism of said one or more available delivery mechanisms is pluggable.
  16. 16. A system of routing instant messages, said system comprising:
    means for defining, at runtime by a pluggable delivery manager, a delivery policy to be used to route an instant message to an intended recipient of the instant message, wherein the delivery policy is based upon a configuration of the pluggable delivery manager, a user configuration of the intended recipient, and one or more available delivery mechanisms; and
    means for routing said instant message to the intended recipient using said delivery policy.
  17. 17. The system of claim 16, wherein said means for defining the delivery policy comprises:
    means for defining a routing policy based on said user configuration and said one or more available delivery mechanisms, wherein said routing policy includes one or more possible delivery mechanisms; and
    means for selecting from the routing policy at least one delivery mechanism to be included in the delivery policy, the selecting being based upon the configuration of the pluggable delivery manager.
  18. 18. The system of claim 16, wherein said means for defining the delivery policy comprises:
    means for determining, from the user configuration, one or more delivery mechanisms supported by said intended recipient;
    means for determining which of said one or more delivery mechanisms supported by said intended recipient are included in the one or more available delivery mechanisms to yield one or more possible delivery mechanisms; and
    means for determining which of the one or more possible delivery mechanisms are supported by the pluggable delivery manager, as indicated in the configuration of the pluggable delivery manager, a result of which defines the delivery policy.
  19. 19. The system of claim 18, wherein said means for routing comprises means for dispatching the instant message to at least one delivery mechanism of the delivery policy, as indicated by the delivery policy.
  20. 20. The system of claim 16, wherein said means for routing comprises means for dispatching the instant message to at least one delivery mechanism of the delivery policy, as indicated by the delivery policy.
  21. 21. The system of claim 16, further comprising means for selecting the pluggable delivery manager from a plurality of delivery managers.
  22. 22. The system of claim 16, further comprising means for configuring said pluggable delivery manager.
  23. 23. The system of claim 22, wherein said means for configuring comprises means for selecting a configuration for said pluggable delivery manager from a set of one or more configurations, wherein the selecting uses content of the instant message to make the selection.
  24. 24. The system of claim 22, wherein said means for configuring comprises means for configuring said pluggable delivery manager at runtime.
  25. 25. The system of claim 16, wherein the intended recipient is indicated by the instant message.
  26. 26. The system of claim 16, wherein at least one available delivery mechanism of said one or more available delivery mechanisms is pluggable.
  27. 27. A system of routing instant messages, said system comprising:
    means for selecting a delivery manager to route an instant message to an intended recipient of the instant message, said delivery manager being pluggable;
    means for configuring, at runtime, said delivery manager, wherein said means for configuring comprises means for selecting a configuration for said delivery manager from a set of one or more configurations, the selecting using content of the instant message to make the selection;
    means for querying, by the delivery manager, a user configuration of the intended recipient to determine one or more delivery mechanisms supported by the intended recipient;
    means for determining, by the delivery manager, one or more available delivery mechanisms;
    means for identifying, by the delivery manager, one or more delivery mechanisms that are common to a result of the querying and the determining to yield one or more possible delivery mechanisms;
    means for selecting, from the one or more possible delivery mechanisms, at least one delivery mechanism supported by the delivery manager; and
    means for routing the instant message to the intended recipient using the at least one delivery mechanism.
  28. 28. The system of claim 27, wherein said at least one delivery mechanism supported by the delivery manager is included within the configuration of the delivery manager.
  29. 29. The system of claim 27, wherein said means for routing comprises means for 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.
  30. 30. The system of claim 27, wherein at least one available delivery mechanism of said one or more available delivery mechanisms is pluggable.
  31. 31. A system of routing instant messages, said system comprising:
    a delivery policy defined, at runtime by a pluggable delivery manager, to be used to route an instant message to an intended recipient of the instant message, wherein the delivery policy is based upon a configuration of the pluggable delivery manager, a user configuration of the intended recipient, and one or more available delivery mechanisms; and
    said pluggable delivery manager to route said instant message to the intended recipient using said delivery policy.
  32. 32. A system of routing instant messages, said system comprising:
    a delivery manager to route an instant message to an intended recipient of the instant message, wherein said delivery manager is pluggable, and configured, at runtime, by selecting, using content of the instant message, a configuration for said delivery manager from a set of one or more configurations;
    said delivery manager being adapted to:
    query a user configuration of the intended recipient to determine one or more delivery mechanisms supported by the intended recipient;
    determine one or more available delivery mechanisms;
    identify one or more delivery mechanisms that are common to a result of the query and the determination to yield one or more possible delivery mechanisms;
    select, from the one or more possible delivery mechanisms, at least one delivery mechanism supported by the delivery manager; and
    route the instant message to the intended recipient using the at least one delivery mechanism.
  33. 33. 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:
    defining, at runtime by a pluggable delivery manager, a delivery policy to be used to route an instant message to an intended recipient of the instant message, wherein the delivery policy is based upon a configuration of the pluggable delivery manager, a user configuration of the intended recipient, and one or more available delivery mechanisms; and
    routing said instant message to the intended recipient using said delivery policy.
  34. 34. The at least one program storage device of claim 33, wherein said defining of the delivery policy comprises:
    defining a routing policy based on said user configuration and said one or more available delivery mechanisms, wherein said routing policy includes one or more possible delivery mechanisms; and
    selecting from the routing policy at least one delivery mechanism to be included in the delivery policy, said selecting being based upon the configuration of the pluggable delivery manager.
  35. 35. The at least one program storage device of claim 33, wherein said defining of the delivery policy comprises:
    determining, from the user configuration, one or more delivery mechanisms supported by said intended recipient;
    determining which of said one or more delivery mechanisms supported by said intended recipient are included in the one or more available delivery mechanisms to yield one or more possible delivery mechanisms; and
    determining which of the one or more possible delivery mechanisms are supported by the pluggable delivery manager, as indicated in the configuration of the pluggable delivery manager, a result of which defines the delivery policy.
  36. 36. The at least one program storage device of claim 35, wherein said routing comprises dispatching the instant message to at least one delivery mechanism of the delivery policy, as indicated by the delivery policy.
  37. 37. The at least one program storage device of claim 33, wherein said routing comprises dispatching the instant message to at least one delivery mechanism of the delivery policy, as indicated by the delivery policy.
  38. 38. The at least one program storage device of claim 33, wherein said method further comprises selecting the pluggable delivery manager from a plurality of delivery managers.
  39. 39. The at least one program storage device of claim 33, wherein said method further comprises configuring said pluggable delivery manager.
  40. 40. The at least one program storage device of claim 39, wherein said configuring comprises selecting a configuration for said pluggable delivery manager from a set of one or more configurations, wherein said selecting uses content of the instant message to make the selection.
  41. 41. The at least one program storage device of claim 39, wherein said configuring comprises configuring said pluggable delivery manager at runtime.
  42. 42. The at least one program storage device of claim 33, wherein the intended recipient is indicated by the instant message.
  43. 43. The at least one program storage device of claim 33, wherein at least one available delivery mechanism of said one or more available delivery mechanisms is pluggable.
  44. 44. 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 to route an instant message to an intended recipient of the instant message, said delivery manager being pluggable;
    configuring, at runtime, said delivery manager, wherein the configuring comprises selecting a configuration for said delivery manager from a set of one or more configurations, said selecting using content of the instant message to make the selection;
    querying, by the delivery manager, a user configuration of the intended recipient to determine one or more delivery mechanisms supported by the intended recipient;
    determining, by the delivery manager, one or more available delivery mechanisms;
    identifying, by the delivery manager, one or more delivery mechanisms that are common to a result of the querying and the determining to yield one or more possible delivery mechanisms;
    selecting, from the one or more possible delivery mechanisms, at least one delivery mechanism supported by the delivery manager; and
    routing the instant message to the intended recipient using the at least one delivery mechanism.
  45. 45. The at least one program storage device of claim 44, wherein said at least one delivery mechanism supported by the delivery manager is included within the configuration of the delivery manager.
  46. 46. The at least one program storage device of claim 44, 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.
  47. 47. The at least one program storage device of claim 44, wherein at least one available delivery mechanism of said one or more available delivery mechanisms is pluggable.
US09866410 2001-05-25 2001-05-25 Routing instant messages using configurable, pluggable delivery managers Abandoned US20020178227A1 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
US09866410 US20020178227A1 (en) 2001-05-25 2001-05-25 Routing instant messages using configurable, pluggable delivery managers

Applications Claiming Priority (5)

Application Number Priority Date Filing Date Title
US09866410 US20020178227A1 (en) 2001-05-25 2001-05-25 Routing instant messages using configurable, pluggable delivery managers
JP2002147211A JP4384839B2 (en) 2001-05-25 2002-05-22 Configurable, routing of instant messages using embeddable delivery manager
US10193632 US7284034B2 (en) 2001-05-25 2002-07-11 Transparent combination of instant message protocols
US11037857 US7412490B2 (en) 2001-05-25 2005-01-18 Routing instant messages using configurable, pluggable delivery managers
US12179610 US20080281937A1 (en) 2001-05-25 2008-07-25 Routing instant messages using configurable, pluggable delivery managers

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US10193632 Continuation-In-Part US7284034B2 (en) 2001-05-25 2002-07-11 Transparent combination of instant message protocols

Publications (1)

Publication Number Publication Date
US20020178227A1 true true US20020178227A1 (en) 2002-11-28

Family

ID=25347549

Family Applications (4)

Application Number Title Priority Date Filing Date
US09866410 Abandoned US20020178227A1 (en) 2001-05-25 2001-05-25 Routing instant messages using configurable, pluggable delivery managers
US10193632 Active 2023-07-25 US7284034B2 (en) 2001-05-25 2002-07-11 Transparent combination of instant message protocols
US11037857 Active 2023-02-03 US7412490B2 (en) 2001-05-25 2005-01-18 Routing instant messages using configurable, pluggable delivery managers
US12179610 Abandoned US20080281937A1 (en) 2001-05-25 2008-07-25 Routing instant messages using configurable, pluggable delivery managers

Family Applications After (3)

Application Number Title Priority Date Filing Date
US10193632 Active 2023-07-25 US7284034B2 (en) 2001-05-25 2002-07-11 Transparent combination of instant message protocols
US11037857 Active 2023-02-03 US7412490B2 (en) 2001-05-25 2005-01-18 Routing instant messages using configurable, pluggable delivery managers
US12179610 Abandoned US20080281937A1 (en) 2001-05-25 2008-07-25 Routing instant messages using configurable, pluggable delivery managers

Country Status (2)

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

Cited By (48)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20030023691A1 (en) * 2001-07-27 2003-01-30 Knauerhase Robert C. Routing messages using presence information
US20030172166A1 (en) * 2002-03-08 2003-09-11 Paul Judge Systems and methods for enhancing electronic communication security
US20030225924A1 (en) * 2002-02-12 2003-12-04 Edward Jung Logical routing system
US20040103318A1 (en) * 2002-06-10 2004-05-27 Akonix Systems, Inc. Systems and methods for implementing protocol enforcement rules
US20040109518A1 (en) * 2002-06-10 2004-06-10 Akonix Systems, Inc. Systems and methods for a protocol gateway
US20050055405A1 (en) * 2003-09-04 2005-03-10 International Business Machines Corporation Managing status information for instant messaging users
US20050055412A1 (en) * 2003-09-04 2005-03-10 International Business Machines Corporation Policy-based management of instant message windows
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
US20060123409A1 (en) * 2004-12-03 2006-06-08 International Business Machines Corporation Method and apparatus for creating a pluggable, prioritized configuration engine to be used for configuring a software during installation, update and new profile creation
US20060123410A1 (en) * 2004-12-03 2006-06-08 International Business Machines Corporation Method and apparatus for defining, building and deploying pluggable and independently configurable install components
US20060267802A1 (en) * 2002-03-08 2006-11-30 Ciphertrust, Inc. Systems and Methods for Graphically Displaying Messaging Traffic
US20070027992A1 (en) * 2002-03-08 2007-02-01 Ciphertrust, Inc. Methods and Systems for Exposing Messaging Reputation to an End User
US20070124577A1 (en) * 2002-06-10 2007-05-31 Akonix Systems and methods for implementing protocol enforcement rules
US20070195753A1 (en) * 2002-03-08 2007-08-23 Ciphertrust, Inc. Systems and Methods For Anomaly Detection in Patterns of Monitored Communications
US20070300286A1 (en) * 2002-03-08 2007-12-27 Secure Computing Corporation Systems and methods for message threat management
US20080177691A1 (en) * 2007-01-24 2008-07-24 Secure Computing Corporation Correlation and Analysis of Entity Attributes
US20080196099A1 (en) * 2002-06-10 2008-08-14 Akonix Systems, Inc. Systems and methods for detecting and blocking malicious content in instant messages
US20080281933A1 (en) * 2005-06-06 2008-11-13 Gregory Jensen Boss Session Management Enhancements for Instant Messaging Applications
US20090077260A1 (en) * 2000-11-16 2009-03-19 Rob Bearman Application platform
US7657616B1 (en) * 2002-06-10 2010-02-02 Quest Software, Inc. Automatic discovery of users associated with screen names
US7664822B2 (en) 2002-06-10 2010-02-16 Quest Software, Inc. Systems and methods for authentication of target protocol screen names
US7694128B2 (en) * 2002-03-08 2010-04-06 Mcafee, Inc. Systems and methods for secure communication delivery
US7756981B2 (en) 2005-11-03 2010-07-13 Quest Software, Inc. Systems and methods for remote rogue protocol enforcement
US20100192025A1 (en) * 2003-03-27 2010-07-29 Microsoft Corporation Availability and scalability in a messaging system in a manner transparent to the application
US7779156B2 (en) 2007-01-24 2010-08-17 Mcafee, Inc. Reputation based load balancing
EP2223280A1 (en) * 2007-11-16 2010-09-01 Microsoft Corporation Distributed messaging system with configurable assurances
US7882265B2 (en) 2002-06-10 2011-02-01 Quest Software, Inc. Systems and methods for managing messages in an enterprise network
US7903549B2 (en) 2002-03-08 2011-03-08 Secure Computing Corporation Content-based policy compliance systems and methods
US7937480B2 (en) 2005-06-02 2011-05-03 Mcafee, Inc. Aggregation of reputation data
US8045458B2 (en) 2007-11-08 2011-10-25 Mcafee, Inc. Prioritizing network traffic
US8132250B2 (en) 2002-03-08 2012-03-06 Mcafee, Inc. Message profiling systems and methods
US8160975B2 (en) 2008-01-25 2012-04-17 Mcafee, Inc. Granular support vector machine with random granularity
US8179798B2 (en) 2007-01-24 2012-05-15 Mcafee, Inc. Reputation based connection throttling
US8185930B2 (en) 2007-11-06 2012-05-22 Mcafee, Inc. Adjusting filter or classification control settings
US8204945B2 (en) 2000-06-19 2012-06-19 Stragent, Llc Hash-based systems and methods for detecting and preventing transmission of unwanted e-mail
US8214497B2 (en) 2007-01-24 2012-07-03 Mcafee, Inc. Multi-dimensional reputation scoring
US8549611B2 (en) 2002-03-08 2013-10-01 Mcafee, Inc. Systems and methods for classification of messaging entities
US8561167B2 (en) 2002-03-08 2013-10-15 Mcafee, Inc. Web reputation scoring
US8578480B2 (en) 2002-03-08 2013-11-05 Mcafee, Inc. Systems and methods for identifying potentially malicious messages
US8589503B2 (en) 2008-04-04 2013-11-19 Mcafee, Inc. Prioritizing network traffic
US8621638B2 (en) 2010-05-14 2013-12-31 Mcafee, Inc. Systems and methods for classification of messaging entities
US8635690B2 (en) 2004-11-05 2014-01-21 Mcafee, Inc. Reputation based message processing
US8763114B2 (en) 2007-01-24 2014-06-24 Mcafee, Inc. Detecting image spam
USRE46174E1 (en) * 2001-01-18 2016-10-04 Genesys Telecommunications Laboratories, Inc. Method and apparatus for intelligent routing of instant messaging presence protocol (IMPP) events among a group of customer service representatives
US20160295402A1 (en) * 2015-03-30 2016-10-06 International Business Machines Corporation Handling instant message delivery media to end user
US9648168B2 (en) 2002-08-27 2017-05-09 Genesys Telecommunications Laboratories, Inc. Method and apparatus for optimizing response time to events in queue
USRE46776E1 (en) 2002-08-27 2018-04-03 Genesys Telecommunications Laboratories, Inc. Method and apparatus for optimizing response time to events in queue
USRE46852E1 (en) 2002-08-27 2018-05-15 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

Families Citing this family (39)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8086672B2 (en) * 2000-06-17 2011-12-27 Microsoft Corporation When-free messaging
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
US7596599B1 (en) * 2002-07-31 2009-09-29 Facetime Communications, Inc. Management capabilities for real-time messaging networks
US7945846B2 (en) 2002-09-06 2011-05-17 Oracle International Corporation Application-specific personalization for data display
US8165993B2 (en) 2002-09-06 2012-04-24 Oracle International Corporation Business intelligence system with interface that provides for immediate user action
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
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
US7401158B2 (en) 2002-09-16 2008-07-15 Oracle International Corporation Apparatus and method for instant messaging collaboration
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
CN1525322A (en) * 2003-02-27 2004-09-01 摩托罗拉公司 System and apparatus for dynamically downloading instant information protocol and method thereof
US7698367B2 (en) * 2003-03-06 2010-04-13 Siemens Communications, Inc. System and method for presence enabled e-mail delivery
US7761516B2 (en) * 2003-03-06 2010-07-20 Siemens Enterprise Communications, Inc. System and method for e-mail presence confirmation
US7539728B2 (en) * 2003-08-07 2009-05-26 International Business Machines Corporation Time sensitive electronic mail
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
ES2285030T3 (en) 2003-12-08 2007-11-16 Research In Motion Limited Method and device for instant messaging.
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
US7730143B1 (en) * 2004-12-01 2010-06-01 Aol Inc. Prohibiting mobile forwarding
US7734695B2 (en) * 2005-03-08 2010-06-08 International Business Machines Corporation Personal and timed chat interface
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 linking Interpersonal
US8706817B2 (en) * 2005-07-21 2014-04-22 International Business Machines Corporation Sender managed message privacy
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
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
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
US9088624B2 (en) 2011-05-31 2015-07-21 Nokia Technologies Oy Method and apparatus for routing notification messages
US9147082B2 (en) * 2011-09-13 2015-09-29 Whorlr Llc Electronic messaging system with configurable delivery that maintains recipient privacy

Citations (21)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US4675507A (en) * 1985-04-17 1987-06-23 Matsushita Electric Industrial Co., Ltd. Heat cooking apparatus having a flat flexible heater
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
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 (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
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
US5675507A (en) * 1995-04-28 1997-10-07 Bobo, Ii; Charles R. Message storage and delivery system
JPH09134319A (en) * 1995-10-03 1997-05-20 Sony Electron Inc User interface and rule processing for personal communication routing 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
EP1368740A1 (en) * 2001-02-05 2003-12-10 Personity Inc. A method and device for displaying contact information in a 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
US4675507A (en) * 1985-04-17 1987-06-23 Matsushita Electric Industrial Co., Ltd. Heat cooking apparatus having a flat flexible heater
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
US5870549A (en) * 1995-04-28 1999-02-09 Bobo, Ii; Charles R. Systems and methods for storing, delivering, and managing messages
US6350066B1 (en) * 1995-04-28 2002-02-26 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
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 (81)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8204945B2 (en) 2000-06-19 2012-06-19 Stragent, Llc Hash-based systems and methods for detecting and preventing transmission of unwanted e-mail
US8272060B2 (en) 2000-06-19 2012-09-18 Stragent, Llc Hash-based systems and methods for detecting and preventing transmission of polymorphic network worms and viruses
US8583745B2 (en) 2000-11-16 2013-11-12 Opendesign, Inc. Application platform
US20090077260A1 (en) * 2000-11-16 2009-03-19 Rob Bearman Application platform
USRE46174E1 (en) * 2001-01-18 2016-10-04 Genesys Telecommunications Laboratories, Inc. Method and apparatus for intelligent routing of instant messaging presence protocol (IMPP) events among a group of customer service representatives
US8819273B2 (en) 2001-02-12 2014-08-26 Opendesign, Inc. Logical routing system
US20110029688A1 (en) * 2001-02-12 2011-02-03 Open Design, Inc. Logical routing system
US20070299927A1 (en) * 2001-07-27 2007-12-27 Intel Corporation Routing messages using presence information
US7269627B2 (en) * 2001-07-27 2007-09-11 Intel Corporation Routing messages using presence information
US20030023691A1 (en) * 2001-07-27 2003-01-30 Knauerhase Robert C. 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
US7809854B2 (en) * 2002-02-12 2010-10-05 Open Design, Inc. Logical routing system
US20030225924A1 (en) * 2002-02-12 2003-12-04 Edward Jung Logical routing system
US7779466B2 (en) 2002-03-08 2010-08-17 Mcafee, Inc. Systems and methods for anomaly detection in patterns of monitored communications
US20070195753A1 (en) * 2002-03-08 2007-08-23 Ciphertrust, Inc. Systems and Methods For Anomaly Detection in Patterns of Monitored Communications
US20070027992A1 (en) * 2002-03-08 2007-02-01 Ciphertrust, Inc. Methods and Systems for Exposing Messaging Reputation to an End User
US8549611B2 (en) 2002-03-08 2013-10-01 Mcafee, Inc. Systems and methods for classification of messaging entities
US20070300286A1 (en) * 2002-03-08 2007-12-27 Secure Computing Corporation Systems and methods for message threat management
US8132250B2 (en) 2002-03-08 2012-03-06 Mcafee, Inc. Message profiling systems and methods
US8069481B2 (en) 2002-03-08 2011-11-29 Mcafee, Inc. Systems and methods for message threat management
US8042149B2 (en) 2002-03-08 2011-10-18 Mcafee, Inc. Systems and methods for message threat management
US8561167B2 (en) 2002-03-08 2013-10-15 Mcafee, Inc. Web reputation scoring
US20060267802A1 (en) * 2002-03-08 2006-11-30 Ciphertrust, Inc. Systems and Methods for Graphically Displaying Messaging Traffic
US7903549B2 (en) 2002-03-08 2011-03-08 Secure Computing Corporation Content-based policy compliance systems and methods
US7693947B2 (en) 2002-03-08 2010-04-06 Mcafee, Inc. Systems and methods for graphically displaying messaging traffic
US7694128B2 (en) * 2002-03-08 2010-04-06 Mcafee, Inc. Systems and methods for secure communication delivery
US8578480B2 (en) 2002-03-08 2013-11-05 Mcafee, Inc. Systems and methods for identifying potentially malicious messages
US20030172166A1 (en) * 2002-03-08 2003-09-11 Paul Judge Systems and methods for enhancing electronic communication security
US7870203B2 (en) 2002-03-08 2011-01-11 Mcafee, Inc. Methods and systems for exposing messaging reputation to an end user
US8042181B2 (en) 2002-03-08 2011-10-18 Mcafee, Inc. Systems and methods for message threat management
US8631495B2 (en) 2002-03-08 2014-01-14 Mcafee, Inc. Systems and methods for message threat management
US7657616B1 (en) * 2002-06-10 2010-02-02 Quest Software, Inc. Automatic discovery of users associated with screen names
US20080196099A1 (en) * 2002-06-10 2008-08-14 Akonix Systems, Inc. Systems and methods for detecting and blocking malicious content in instant messages
US20040109518A1 (en) * 2002-06-10 2004-06-10 Akonix Systems, 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
US7818565B2 (en) 2002-06-10 2010-10-19 Quest Software, Inc. Systems and methods for implementing protocol enforcement rules
US7707401B2 (en) 2002-06-10 2010-04-27 Quest Software, Inc. Systems and methods for a protocol gateway
US7882265B2 (en) 2002-06-10 2011-02-01 Quest Software, Inc. Systems and methods for managing messages in an enterprise network
US20040103318A1 (en) * 2002-06-10 2004-05-27 Akonix Systems, Inc. Systems and methods for implementing protocol enforcement rules
US7664822B2 (en) 2002-06-10 2010-02-16 Quest Software, Inc. Systems and methods for authentication of target protocol screen names
US8195833B2 (en) 2002-06-10 2012-06-05 Quest Software, Inc. Systems and methods for managing messages in an enterprise network
US20070124577A1 (en) * 2002-06-10 2007-05-31 Akonix Systems and methods for implementing protocol enforcement rules
USRE46853E1 (en) 2002-08-27 2018-05-15 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
US9648168B2 (en) 2002-08-27 2017-05-09 Genesys Telecommunications Laboratories, Inc. Method and apparatus for optimizing response time to events in queue
USRE46852E1 (en) 2002-08-27 2018-05-15 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
USRE46776E1 (en) 2002-08-27 2018-04-03 Genesys Telecommunications Laboratories, Inc. Method and apparatus for optimizing response time to events in queue
US20100192025A1 (en) * 2003-03-27 2010-07-29 Microsoft Corporation Availability and scalability in a messaging system in a manner transparent to the application
US8135794B2 (en) * 2003-03-27 2012-03-13 Microsoft Corporation Availability and scalability in a messaging system in a manner transparent to the application
US20050055405A1 (en) * 2003-09-04 2005-03-10 International Business Machines Corporation Managing status information for instant messaging users
US20050055412A1 (en) * 2003-09-04 2005-03-10 International Business Machines Corporation Policy-based management of instant message windows
US20100250692A1 (en) * 2003-09-04 2010-09-30 International Business Machines Corporation Managing Status Information for Instant Messaging Users
US8635690B2 (en) 2004-11-05 2014-01-21 Mcafee, Inc. Reputation based message processing
US20060123410A1 (en) * 2004-12-03 2006-06-08 International Business Machines Corporation Method and apparatus for defining, building and deploying pluggable and independently configurable install components
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
US20060123409A1 (en) * 2004-12-03 2006-06-08 International Business Machines Corporation Method and apparatus for creating a pluggable, prioritized configuration engine to be used for configuring a software during installation, update and new profile creation
US7937480B2 (en) 2005-06-02 2011-05-03 Mcafee, Inc. Aggregation of reputation data
US20080281933A1 (en) * 2005-06-06 2008-11-13 Gregory Jensen Boss Session Management Enhancements for Instant Messaging Applications
US8380792B2 (en) 2005-06-06 2013-02-19 International Business Machines Corporation Session management enhancements for instant messaging applications
US7756981B2 (en) 2005-11-03 2010-07-13 Quest Software, Inc. Systems and methods for remote rogue protocol enforcement
US8578051B2 (en) 2007-01-24 2013-11-05 Mcafee, Inc. Reputation based load balancing
US8179798B2 (en) 2007-01-24 2012-05-15 Mcafee, Inc. Reputation based connection throttling
US8214497B2 (en) 2007-01-24 2012-07-03 Mcafee, Inc. Multi-dimensional reputation scoring
US9009321B2 (en) 2007-01-24 2015-04-14 Mcafee, Inc. Multi-dimensional reputation scoring
US7949716B2 (en) 2007-01-24 2011-05-24 Mcafee, Inc. Correlation and analysis of entity attributes
US20080177691A1 (en) * 2007-01-24 2008-07-24 Secure Computing Corporation Correlation and Analysis of Entity Attributes
US8763114B2 (en) 2007-01-24 2014-06-24 Mcafee, Inc. Detecting image spam
US9544272B2 (en) 2007-01-24 2017-01-10 Intel Corporation Detecting image spam
US7779156B2 (en) 2007-01-24 2010-08-17 Mcafee, Inc. Reputation based load balancing
US8762537B2 (en) 2007-01-24 2014-06-24 Mcafee, Inc. Multi-dimensional reputation scoring
US8621559B2 (en) 2007-11-06 2013-12-31 Mcafee, Inc. Adjusting filter or classification control settings
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
EP2223280A4 (en) * 2007-11-16 2012-08-08 Microsoft Corp Distributed messaging system with configurable assurances
EP2223280A1 (en) * 2007-11-16 2010-09-01 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
US8606910B2 (en) 2008-04-04 2013-12-10 Mcafee, Inc. Prioritizing network traffic
US8589503B2 (en) 2008-04-04 2013-11-19 Mcafee, Inc. Prioritizing network traffic
US8621638B2 (en) 2010-05-14 2013-12-31 Mcafee, Inc. Systems and methods for classification of messaging entities
US20160294737A1 (en) * 2015-03-30 2016-10-06 International Business Machines Corporation Handling instant message delivery media to end user
US20160295402A1 (en) * 2015-03-30 2016-10-06 International Business Machines Corporation Handling instant message delivery media to end user

Also Published As

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

Similar Documents

Publication Publication Date Title
US6018762A (en) Rules-based synchronization of mailboxes in a data network
US6631363B1 (en) Rules-based notification system
US7096255B2 (en) System and method for providing a roster list of temporary contacts having expiration periods designated by a user in an instant messaging environment
US7085812B1 (en) System and method for selective application of email delivery options
US7272662B2 (en) Systems and methods for routing messages to communications devices over a communications network
US7685265B1 (en) Topic-based notification service
US6360252B1 (en) Managing the transfer of e-mail attachments to rendering devices other than an original e-mail recipient
US6112227A (en) Filter-in method for reducing junk e-mail
US6360272B1 (en) Method and apparatus for maintaining a unified view of multiple mailboxes
US20040172454A1 (en) Reconfiguring an electronic message to effect an enhanced notification
US20110029616A1 (en) Unified auto-reply to an email coming from unified messaging service
US20050267896A1 (en) Performing an operation on a message received from a publish/subscribe service
US20040154022A1 (en) System and method for filtering instant messages by context
US20030074482A1 (en) Composable messaging protocol
US7039671B2 (en) Dynamically routing messages between software application programs using named routing nodes and named message queues
US20040039779A1 (en) System and method for managing information and collaborating
US7254614B2 (en) Web services push gateway
US20090037541A1 (en) System and method for automatically responding to a message sent to a user at an email server
US20040054733A1 (en) E-mail management system and method
US20060116138A1 (en) Value added services creation (vasc) platform
US20020083035A1 (en) System and method for wireless delivery of text data
US6643687B1 (en) Email system delivers email message to a proxy email address that corresponds to a sender and recipient pairing
US20030131050A1 (en) Method for user-specified error correction in an instant messaging system
US20070239866A1 (en) Managing Rich Presence Collections
US20060155812A1 (en) Management of network devices via email

Legal Events

Date Code Title Description
AS Assignment

Owner name: INTERNATIONAL BUSINESS MACHINES CORPORATION, NEW Y

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:MATSA, MOSHE M. E.;QUIAOT, JULIUS Q.;VINCENT, CHRISTOPHER R.;REEL/FRAME:011893/0439

Effective date: 20010521