Dynamically managing data conveyance between computing devices

• US 20040243617A1
• Filed: 05/30/2003
• Published: 12/02/2004
• Est. Priority Date: 05/30/2003
• Status: Active Grant

• Current Assignee: SAP SE
• Original Assignee: SAP AG (SAP SE)
• Inventors: Bayyapu, Pavan
• Granted Patent: US 7,516,135 B2
• Time in Patent Office: Days
• US Class Current: 707/102
• CPC Class Codes: H04L 67/62 Establishing a time schedule for servicing the requests
• CPC Class Codes: H04L 69/329 in the application layer [OSI layer 7]
• CPC Class Codes: Y10S 707/99943 Generating database or data structure, e.g. via user interface

Abstract

Dynamically managing data conveyance between computing devices may be achieved by a data distribution device establishing a data pull service in response to a subscription request from a data acquisition device, the data pull service having a first refresh interval, determining whether new data is available, if new data is available, determining whether the data is responsive to the subscription request, if the data is responsive to the subscription request, determining an interval for the responsive new data becoming available, and determining a second refresh interval for the data pull service based on the determined interval.

Claims

1. A method performed at a data distribution device, the method comprising:

establishing a data pull service in response to a subscription request from a data acquisition device, the data pull service having a first refresh interval;

determining whether new data is available;

if new data is available, determining whether the data is responsive to the subscription request;

if the data is responsive to the subscription request, determining an interval for the responsive new data becoming available; and

determining a second refresh interval for the data pull service based on the determined interval.

2. The method of claim 1, further comprising:

determining whether a message requesting new data has been received; and

if the message has been received, sending a message comprising the second refresh interval.

3. The method of claim 1, further comprising:

receiving a message comprising a subscription request;

determining an attribute of data responsive to the subscription request; and

selecting, based on a current state of the data distribution device and the attribute of the responsive data, between the data pull service and a data push service for providing the responsive data.

4. The method of claim 3, further comprising:

if the selected service comprises the data pull service, determining the first refresh interval; and

sending a message comprising the first refresh interval.

5. The method of claim 1, further comprising:

determining whether the new data is responsive to a subscription request for a data push service; and

if the data is responsive to a subscription request for a data push service, sending a message comprising the data.

6. The method of claim 1, further comprising:

tracking an amount of time for responsive new data becoming available; and

sending a message comprising a disconnect notification if a predefined period of time has expired.

7. The method of claim 1, wherein determining a second refresh interval comprises analyzing intervals at which responsive new data is becoming available.

8. The method of claim 1, further comprising:

determining whether a message indicating that the service should be stopped has been received; and

if a stoppage message has been received, releasing resources for the service.

9. The method of claim 1, further comprising:

sending a message comprising an acknowledge request; and

determining whether a response to the acknowledge request has been received.

10. The method of claim 9, further comprising deciding to use a data pull service if a response to the acknowledge request has not been received.

11. A system comprising:

a data distribution device comprising;

a communication network interface operable to receive a subscription request from a data acquisition device; and

a processor operable to;

establish a data pull service in response to the subscription request, the data pull service having a first refresh interval;

determine whether new data is available,

if new data is available, determine whether the data is responsive to the subscription request,

if the data is responsive to the subscription request, determine an interval for the responsive new data becoming available, and

determine a second refresh interval for the data pull service based on the determined interval.

12. The system of claim 11, wherein:

the communication network interface is further operable to receive a message requesting new data; and

the processor is further operable to;

determine whether the message has been received, and

if the message has been received, generate a message comprising the second refresh interval.

13. The system of claim 11, wherein:

the communication network interface is further operable to receiving a message comprising a subscription request; and

the processor is further operable to;

determine an attribute of data responsive to the subscription request, and

select, based on a current state of the data distribution device and the attribute of the responsive data, between the data pull service and a data push service for providing the responsive data.

14. The system of claim 13, wherein the processor is further operable to:

if the selected service comprises the data pull service, determine the first refresh interval; and

generate a message comprising the first refresh interval.

15. The system of claim 11, wherein the processor is further operable to:

determine whether the new data is responsive to a subscription request for a data push service; and

if the data is responsive to a subscription request for a data push service, generate a message comprising the data.

16. The system of claim 11, wherein the processor is further operable to:

track an amount of time for responsive new data becoming available; and

generate a message comprising a disconnect notification if a predefined period of time has expired.

17. The system of claim 11, wherein the processor is operable to analyze intervals at which responsive new data is becoming available to determine the second refresh interval.

18. The system of claim 11, wherein the data distribution device comprises a server.

19. The system of claim 11, wherein the processor is further operable to:

generate a message comprising an acknowledge request; and

determine whether a response to the acknowledge request has been received.

20. The system of claim 19, wherein the processor is further operable to decide to use a data pull service if a response to the acknowledge request has not been received.

21. An article comprising a machine-readable medium storing instructions operable to cause one or more machines to perform operations comprising:

establishing a data pull service at a data distribution device in response to a subscription request from a data acquisition device, the data pull service having a first refresh interval;

determining whether new data is available;

if new data is available, determining whether the data is responsive to the subscription request;

if the data is responsive to the subscription request, determining an interval for the responsive new data becoming available; and

determining a second refresh interval for the data pull service based on the determined interval.

22. The article of claim 21, wherein the instructions are further operable to cause one or more machines to perform operations comprising:

determining whether a message requesting new data has been received; and

if the message has been received, generating a message comprising the second refresh interval.

23. The article of claim 21, wherein the instructions are further operable to cause one or more machines to perform operations comprising:

determining whether a message comprising a subscription request has been received;

determining an attribute of data responsive to the subscription request; and

selecting, based on a current state of the data distribution device and the attribute of the responsive data, between the data pull service and a data push service for providing the responsive data.

24. The article of claim 23, wherein the instructions are further operable to cause one or more machines to perform operations comprising:

if the selected service comprises the data pull service, determining the first refresh interval; and

generating a message comprising the first refresh interval.

25. The article of claim 21, wherein the instructions are further operable to cause one or more machines to perform operations comprising:

determining whether the new data is responsive to a subscription request for a data push service; and

if the data is responsive to a subscription request for a data push service, generating a message comprising the data.

26. The article of claim 21, wherein the instructions are further operable to cause one or more machines to perform operations comprising:

tracking an amount of time for responsive new data becoming available; and

generating a message comprising a disconnect notification if a predefined period of time has expired.

27. The article of claim 21, wherein the instructions are operable to cause one or more machines to analyze the intervals at which responsive new data is becoming available to determine the second refresh interval.

28. The article of claim 21, wherein the instructions are further operable to cause one or more machines to perform operations comprising:

generating a message comprising an acknowledge request; and

determining whether a response to the acknowledge request has been received.

29. The article of claim 28, wherein the instructions are further operable to cause one or more machines to perform operations comprising deciding to use a data pull service if a response to the acknowledge request has not been received.

30. A method preformed at a data acquisition device, the method comprising:

determining whether a first refresh interval has expired for a data pull service;

if the first refresh interval has expired, sending a message requesting new data;

determining whether a message comprising new data has been received;

if a message comprising new data has been received, updating existing data;

determining whether a message comprising a second refresh interval has been received; and

if a message comprising a second refresh interval has been received, updating the first refresh interval with the second refresh interval.

31. The method of claim 30, further comprising:

determining whether data is desired by a process; and

if data is desired, sending a message comprising a subscription request.

32. The method of claim 31, further comprising:

determining whether a message regarding a selected service has been received; and

if a message regarding a selected service has been received, determining whether the selected service comprises the data pull service or a data push service.

33. The method of claim 32, further comprising:

if the selected service comprises a data push service, establishing a persistent connection;

determining whether a message comprising new data has been received; and

if a message comprising new data has been received, updating existing data for the service.

34. The method of claim 30, further comprising:

determining whether the service is still desired; and

if the service is not still desired, sending a message indicating that the service should be stopped.

35. The method of claim 30, further comprising:

determining whether a message comprising a disconnect notification has been received; and

if a disconnect notification has been received, determining whether disconnection is acceptable.

36. The method of claim 30, further comprising:

determining whether an acknowledge request has been received; and

if an acknowledge request has been received, sending a response.

37. A system comprising:

a data acquisition device comprising;

a processor operable to;

determine whether a first refresh interval has expired for a data pull service,

if the first refresh interval has expired, generate a message requesting new data,

determine whether a message comprising new data has been received,

if a message comprising new data has been received, updating existing data,

determine whether a message comprising a second refresh interval has been received, and

if a message comprising a second refresh interval has been received, 14 updating the first refresh interval with the second refresh interval.

38. The system of claim 37, wherein the processor is further operable to:

determine whether data is desired by a process; and

if data is desired, generate a message comprising a subscription request.

39. The system of claim 38, wherein the processor is further operable to:

determine whether a message regarding a selected service has been received; and

if a message regarding a selected service has been received, determine whether the selected service comprises the data pull service or a data push service.

40. The system of claim 39, wherein the processor is further operable to:

if the selected service comprises a data push service, establish a persistent connection;

determine whether a message comprising new data has been received; and

if a message comprising new data has been received, update existing data for the service.

41. The system of claim 37, wherein the remote device comprises a personal computer executing a Web-based browser.

42. An article comprising a machine-readable medium storing instructions operable to cause one or more machines to perform operations comprising:

determining at a data acquisition device whether a first refresh interval has expired for a data pull service;

if the first refresh interval has expired, generating a message requesting new data;

determining whether a message comprising new data has been received;

if a message comprising new data has been received, updating existing data;

determining whether a message comprising a second refresh interval has been received; and

if a message comprising a second refresh interval has been received, updating the first refresh interval with the second refresh interval.

43. The article of claim 42, wherein the instructions are further operable to cause one or more machines to perform operations comprising:

determining whether data is desired by a process; and

if data is desired, generating a message comprising a subscription request.

44. The article of claim 43, wherein the instructions are further operable to cause one or more machines to perform operations comprising:

determining whether a message regarding a selected service has been received; and

if a message regarding a selected service has been received, determining whether the selected service comprises the data pull service or a data push service.

45. The article of claim 44, wherein the instructions are further operable to cause one or more machines to perform operations comprising:

if the selected service comprises a data push service, establishing a persistent connection;

determining whether a message comprising new data has been received; and

if a message comprising new data has been received, updating existing data for the service.

46. A system comprising:

a data acquisition device operable to;

determine whether data is desired by a process,

if data is desired, send a message comprising a subscription request,

determine whether an acknowledge request has been received,

if an acknowledge request has been received, send a response,

determine whether a message regarding a selected service has been received,

if a message regarding a selected service has been received, determine whether the selected service is a data pull service or a data push service, the data pull service having a first refresh interval,

if the service is a data pull service;

determine whether the first refresh interval has expired;

if the first refresh interval has expired, send a message requesting new data;

determine whether a message comprising new data and a second refresh interval has been received; and

if a message comprising new data and a second refresh interval has been received, update existing data and the first refresh interval,

if the selected service is a data push service;

establish a persistent connection;

determine whether a message comprising new data has been received; and

if a message comprising new data has been received, update existing data,

determine whether the selected service is still desired,

if the service is not still desired, send a message indicating that the service should be stopped,

determine whether a message comprising a disconnect notification has been received, and

if a disconnect notification has been received, determine whether disconnection is acceptable; and

a data distribution device operable to;

determine whether the message comprising the subscription request has been received,

if a subscription request has been received;

determine an attribute of data responsive to the subscription request;

send a message comprising an acknowledge request;

determine whether a response to the acknowledge request has been received; and

select, based on a current state of the data distribution device, the attribute of the responsive data, and the response to the acknowledge request, if any, between the data pull service and the data push service for providing the responsive data,

if the selected service is a data pull service;

determine the first refresh interval;

send the message regarding the selected service, the message comprising the refresh interval;

determine whether new data is available;

if new data is available, determine whether the data is responsive to the subscription request;

if the data is responsive, store the data;

determine the second refresh interval for the data pull service based on intervals at which responsive new data is becoming available;

receive the message requesting new data; and

if the message requesting new data has been received, send the message comprising the new data and the second refresh interval,

if the selected service is a data push service;

send the message regarding the selected service;

determine whether new data is available;

if new data is available, determine whether the data is responsive to the subscription request; and

if the data is responsive to the subscription request, send a message comprising the data,

track an amount of time for responsive new data becoming available,

send the message comprising a disconnect notification if a predefined period of time has expired,

determine whether the service stoppage message has been received, and

release resources for the service if the service stoppage message has been received.