APPARATUS, SYSTEM, AND METHOD FOR IMPROVED PERFORMANCE OF REAL TIME APPLICATIONS IN INTERMITTENT CONNECTION ENVIRONMENTS

• US 20110078233A1
• Filed: 09/30/2009
• Published: 03/31/2011
• Est. Priority Date: 09/30/2009
• Status: Abandoned Application

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Salazar, Fernando
• Application Number:
  US12/571,161
• Publication Number:
  US 20110078233A1
• Time in Patent Office: Days
• US Class Current: 709/203
• CPC Class Codes: H04L 51/04 Real-time or near real-time messaging, e.g. instant messaging [IM]
• CPC Class Codes: H04L 67/14 Session management for real-time applications in data packet communications networks H04L65/1066

Abstract

An apparatus, system, and method are disclosed for distributing events between application instances that are connected by intermittent connections. The application instances are provided with brokers that communicate with each other and their respective application instances according to an interface. The application instances provide events to the brokers, which forward them to the other brokers in the system. If a particular broker cannot be reached, the broker queues the events in a local data store, monitors the connection, and sends them once the connection is reestablished. The broker similarly receives events generated by the application instance associated with the remote broker that could not be communicated while the connection was inactive. As a result, users in the system are provided with a best possible and most complete state of the entire application that is available given the connection statuses in the system at a given time.

Claims

1. A computer implemented method for a broker to distribute events to application instances that are connected with the broker by an intermittent connection, the method comprising:

receiving events from a first application instance that is connected to the broker by a persistent connection;

locally queuing the events received from the first application instance;

checking a connectivity status of the intermittent connection between the broker and a second application instance; and

sending the locally queued events to the second application instance over the intermittent connection in response to the connection status between the broker and the second application instance being active.

2. The method of claim 1, further comprising receiving, over the intermittent connection and in response to the connection status between the broker and the second application instance being active, remotely queued events generated by the second application instance.

3. The method of claim 2, further comprising sending the remotely queued events to the first application instance.

4. The method of claim 1, further comprising distributing the events from the first application instance to a third application instance that is connected to the broker by an active intermittent connection.

5. The method of claim 1, wherein the locally queued events are sent to the second application instance through a remote broker that is persistently connected with the second application instance, and wherein the remotely queued events are received from the second application instance through the remote broker.

6. The method of claim 5, further comprising maintaining a distribution list of one or more remote brokers with which locally queued events and remotely queued events are exchanged.

7. The method of claim 5, wherein distributing events to the second application instance comprises sending the locally queued events to the remote broker, the remote broker distributing the locally queued events to the second application instance.

8. The method of claim 1, further comprising the broker providing an events interface to the first application instance, and wherein the received events are submitted by the first application instance to the broker according to the events interface.

9. The method of claim 8, further comprising sending the remotely queued events to the first application instance according to the events interface.

10. A broker to distribute events to application instances that are connected with the broker by an intermittent connection, the broker comprising:

an events module for receiving events from a first application instance that is connected to the broker by a persistent connection;

a queue module for locally queuing the events received from the first application instance;

a connections module for checking a connectivity status of the intermittent connection between the broker and a second application instance; and

a send module for sending the locally queued events to the second application instance over the intermittent connection in response to the connection status between the broker and the second application instance being active.

11. The broker of claim 10, further comprising a receipt module for receiving, over the intermittent connection and in response to the connection status between the broker and the second application instance being active, remotely queued events generated by the second application instance.

12. The broker of claim 10, further comprising an interface module that provides an events interface to the first application instance, and wherein the events module receives events from the first application instance that are submitted according to the events interface.

13. The broker of claim 10, further comprising a transfer module that sends the remotely queued events to the first application instance according to the events interface.

14. A system to distribute events to application instances that are connected with one or more brokers by intermittent connections, the system comprising:

a first broker connected to a first application instance by a first persistent connection, the first broker comprising;

an events module for receiving events from the first application instance;

a queue module for locally queuing the events received from the first application instance;

a connections module for checking a connectivity status of an intermittent connection between the first broker and a second broker;

a send module for sending the locally queued events to the second broker over the intermittent connection in response to the connection status between the first broker and the second broker being active;

a receipt module for receiving remotely queued events from the second broker over the intermittent connection in response to the connection status between the first broker and the second broker being active;

the intermittent connection connecting the first broker and the second broker; and

the second broker connected to a second application instance by a second persistent connection, the second broker comprising;

an events module for receiving events from the second application instance;

a queue module for locally queuing the events received from the second application instance;

a connections module for checking a connectivity status of an intermittent connection between the first broker and a second broker;

a send module for sending the locally queued events to the first broker over the intermittent connection in response to the connection status between the first broker and the second broker being active;

a receipt module for receiving remotely queued events from the first broker over the intermittent connection in response to the connection status between the first broker and the second broker being active.

15. The system of claim 14, further comprising one or more additional brokers that communicate with the first broker and the second broker over the intermittent connection.

16. The system of claim 15, wherein each broker in the system maintains a distribution list of other brokers with which events are exchanged.

17. The system of claim 14, further comprising a hub broker that is connected to one or more brokers, and wherein each broker receives remotely queued events from the other brokers through the hub broker, and wherein each broker sends locally queued events through the hub broker.

18. The system of claim 14, wherein each broker in the system further comprises a transfer module that sends the remotely queued events to the first application instance according to the events interface.

19. The system of claim 14, wherein each broker in the system further comprises a storage module for storing the events received from the first application instance in a data store that is locally attached to the broker.

20. A computer program product stored on a computer readable storage medium and comprising operations for a broker to distribute events generated by an application instance connected to the broker by a persistent connection with a remote broker connected to the broker by a mobile connection, the operations comprising:

the broker receiving events from the first application instance that is connected to the broker by the persistent connection;

the broker locally queuing those events received from the first application instance that have not been successfully transmitted to the remote broker over the mobile connection;

the broker checking a connectivity status of the mobile connection between the broker and a remote broker at predefined intervals;

the broker sending, to the remote broker, the locally queued events that have not been successfully transmitted previously over the mobile connection in response to the connection status between the broker and the remote broker being active; and

the broker receiving, from the remote broker, remotely queued events that the broker had not successfully received previously over the mobile connection in response to the connection status between the broker and the remote broker being active.