System and method for exchanging data

• US 20040221057A1
• Filed: 03/22/2004
• Published: 11/04/2004
• Est. Priority Date: 02/01/2000
• Status: Active Grant

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Paul B. Darcy, Steven A. Deluca
• Inventors: Darcy, Paul B., DeLuca, Steven A.
• Granted Patent: US 7,225,265 B2
• Time in Patent Office: Days
• US Class Current: 709/233
• CPC Class Codes: H04L 47/10 Flow control; Congestion control
• CPC Class Codes: H04L 47/27 Evaluation or update of window size, e.g. using information derived from acknowledged [ACK] packets

Abstract

A system and method are provided for exchanging data at irregular intervals between a sender and a receiver. The sender transmits to the receiver reports containing subject data along with information regarding the next interval at which subject data will be transmitted to the receiver. The receiver may create an expectation window corresponding to the interval information. In a network environment, the level of non-management traffic is monitored, and an average interval value for exchanging management data is selected as a function of the level of non-management traffic. Then, interval values are randomly generated based on the selected average interval value, and the management data is transmitted from the sender to the receiver at irregular intervals corresponding to the interval values.

Claims

1. (Canceled)

2. (Canceled)

3. (Canceled)

4. (Canceled)

5. (Canceled)

6. (Canceled)

7. (Canceled)

8. (Canceled)

9. (Canceled)

10. (Canceled)

11. (Canceled)

12. (Canceled)

13. (Canceled)

14. (Canceled)

15. (Canceled)

16. (Canceled)

17. (Canceled)

18. (Canceled)

19. (Canceled)

20. (Canceled)

21. (Canceled)

22. (Canceled)

23. (Canceled)

24. (Canceled)

25. (Canceled)

26. (Canceled)

27. (Canceled)

28. (Canceled)

29. (Canceled)

30. A method for exchanging data between a sender and a receiver, said method comprising:

generating a first schedule at the sender for sending data to the receiver;

generating a second schedule at the receiver for receiving data from the sender, the second schedule being generated as a function of the first schedule to cause a predetermined probability of failure; and

upon detecting a failure, generating an event at the receiver.

31. The method of claim 30, wherein data from the sender not being received at the receiver a predetermined number of times constitutes a failure.

32. The method of claim 30, wherein said step of generating a second schedule includes establishing at least one expectation window for receiving data from the sender.

33. A computer-readable medium having computer-executable instructions for performing the steps recited in claim 30.

34. (Canceled)

35. (Canceled)

36. (Canceled)