Dynamic adaptations for network delays during complex event processing

• US 9,059,935 B2
• Filed: 11/22/2011
• Issued: 06/16/2015
• Est. Priority Date: 11/22/2011
• Status: Active Grant

• Current Assignee: SAP SE
• Original Assignee: SAP SE
• Inventors: Hudzia, Benoit, Dawson, Stephen, Hay, Alan
• Primary Examiner(s): LI, GUANG W
• Application Number:
  US13/302,799
• Publication Number:
  US 20130132560A1
• Time in Patent Office: 1,302 Days
• Field of Search: 709/224
• US Class Current: 1/1
• CPC Class Codes: H04L 41/064 involving time analysis
• CPC Class Codes: H04L 47/283 in response to processing delays, e.g. caused by jitter or round trip time [RTT]

Abstract

A message handler may receive a plurality of messages associated with a plurality of events, the events having a temporal relationship to one another. A header inspector may extract latency information from the plurality of messages, the latency information characterizing a transmission duration experienced by each message in traveling from the one or more source nodes through the network. A window manager may correct a disruption in the temporal relationship between at least two events of the plurality of events, the disruption including relative differences in the transmission duration experienced by the at least two events, including relating the at least two events to a time window for processing the at least two events. An event processor may process the at least two events relative to the time window.

Claims

1. A system including instructions recorded on a computer-readable medium and executable by at least one processor, the system comprising:

a message handler configured to cause the at least one processor to receive a plurality of messages associated with a plurality of events, the events having a temporal relationship to one another, the events including a first event and a second event, wherein the first event and the second event are associated with a time window to process the first event and the second event such that the first and second events are not processed when at least one of the first and second events are considered to have occurred outside the time window;

a header inspector configured to cause the at least one processor to extract latency information from the plurality of messages, the latency information characterizing a transmission duration experienced by each message in traveling from one or more source nodes through a network of nodes;

a window manager configured to cause the at least one processor to correct a disruption in the temporal relationship between the first event and the second event based on the extracted latency information for a first message corresponding to the first event and a second message corresponding to the second event, the disruption including relative differences in the transmission duration experienced by the first event and the second event, wherein disruption in the temporal relationship is corrected by extending the time window such that the first event and the second event fall within the time window; and

an event processor configured to cause the at least one processor to process the first and second events relative to the time window.

2. The system of claim 1, wherein the latency information extracted from each message includes an aggregation of average transmission times between each pair of nodes traversed by the message through the network of nodes, the average transmission times having been added incrementally to the aggregation at each traversed node.

3. The system of claim 1, wherein the latency information extracted from each message includes an aggregation of a total number of hops experienced by a respective message through the network of nodes, each hop of the total number of hops having been added incrementally at each traversed node.

4. The system of claim 1, comprising:

a transmission time calculator configured to maintain a transmission time table which characterizes average transmission times between a node hosting the system and other network nodes connected by a single hop.

5. The system of claim 1, comprising:

a header manager configured to update, within a header of each message received at the node hosting the system from a transmitting node one hop away therefrom, the latency information including the average transmission time between the hosting node and the transmitting node.

6. The system of claim 1, wherein the network of nodes includes a peer-to-peer network.

7. The system of claim 1, wherein the window manager is configured to detect the disruption including comparing the latency information of each message with expected latency information for the corresponding message.

8. The system of claim 7, comprising a table manager configured to maintain the expected latency information including a latency table characterizing recent latency information determined with respect to previous messages traversing the network of nodes from the corresponding source node.

9. The system of claim 1, wherein the window manager comprises a view generator configured to display at least one of the latency information and the relation of the first and second events to the time window.

10. The system of claim 1, wherein the window manager comprises a delay adjuster configured to correct the disruption including delaying processing of at least one of the first and second events within a queue, in order to relate the first and second events relative to the time window in an order corresponding to an actual order of occurrence thereof.

11. The system of claim 1, wherein the window manager comprises a size manager configured to correct the disruption including adjusting a relative size of the time window in order to relate the first and second events within the adjusted time window in a manner corresponding to an actual occurrence thereof within the time window.

12. A computer-implemented method for executing instructions stored on a computer readable storage medium, the method comprising:

receiving a plurality of messages associated with a plurality of events, the events having a temporal relationship to one another, the events including a first event and a second event, wherein the first event and the second event are associated with a time window to process the first event and the second event such that the first and second events are not processed when at least one of the first and second events are considered to have occurred outside the time window;

extracting latency information from the plurality of messages, the latency information characterizing a transmission duration experienced by each message in traveling from one or more source nodes through a network of nodes;

correcting a disruption in the temporal relationship between the first event and the second event based on the extracted latency information for a first message corresponding to the first event and a second message corresponding to the second event, the disruption including relative differences in the transmission duration experienced by the first event and the second event, wherein disruption in the temporal relationship is corrected by extending the time window such that the first event and the second event fall within the time window; and

processing the first and second events relative to the time window.

13. The method of claim 12, wherein the correcting the disruption includes detecting the disruption including comparing the latency information of each message with expected latency information for the corresponding message.

14. A computer program product, the computer program product being tangibly embodied on a non-transitory computer-readable storage medium and comprising instructions that, when executed, are configured to:

receive a plurality of messages associated with a plurality of events, the events having a temporal relationship to one another, the events including a first event and a second event, wherein the first event and the second event are associated with a time window to process the first event and the second event such that the first and second events are not processed when at least one of the first and second events are considered to have occurred outside the time window;

extract latency information from the plurality of messages, the latency information characterizing a transmission duration experienced by each message in traveling from the one or more source nodes through a network of nodes;

correct a disruption in the temporal relationship between the first event and the second event based on the extracted latency information for a first message corresponding to the first event and a second message corresponding to the second event, the disruption including relative differences in the transmission duration experienced by the first event and the second event, wherein disruption in the temporal relationship is corrected by extending the time window such that the first event and the second event fall within the time window; and

process the first and second events relative to the time window.

15. The computer program product of claim 14, wherein the latency information includes aggregated latency information having been added incrementally at each node traversed by each message through the network of nodes.

16. The computer program product of claim 14, wherein the disruption is corrected including comparing the latency information of each message with expected latency information for the corresponding message.

17. The computer program product of claim 14, wherein the instructions, when executed, are configured to correct the disruption including delaying processing of at least one of the first and second events within a queue, in order to relate the first event and the second event relative to the time window in an order corresponding to an actual order of occurrence thereof.

18. The computer program product of claim 14, wherein the instructions, when executed, are configured to extend the time window include instructions to adjust a size of the time window in order to relate the first and second events within the adjusted time window in a manner corresponding to an actual occurrence thereof within the time window.