Methods and system for using caches

• US 20060155819A1
• Filed: 05/27/2003
• Published: 07/13/2006
• Est. Priority Date: 05/29/2002
• Status: Abandoned Application

• Current Assignee: Flyingspark Ltd.
• Original Assignee: Flyingspark Ltd.
• Inventors: Grabinar, Paul Lionel, Wood, Simon David
• Application Number:
  US10/516,140
• Publication Number:
  US 20060155819A1
• Time in Patent Office: Days
• US Class Current: 709/213
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 67/04 specially adapted for terminals or networks with limited capabilities; specially adapted for terminal portability
• CPC Class Codes: H04L 67/06 specially adapted for file transfer, e.g. file transfer protocol [FTP]
• CPC Class Codes: H04L 67/289 Intermediate processing functionally located close to the data consumer application, e.g. in same machine, in same home or in same sub-network
• CPC Class Codes: H04L 67/568 Storing data temporarily at an intermediate stage, e.g. caching
• CPC Class Codes: H04L 67/5682 Policies or rules for updating, deleting or replacing the stored data
• CPC Class Codes: H04L 69/329 in the application layer [OSI layer 7]

Abstract

A method of communicating data objects includes the steps of assembling at least one business object by a request server (225) from data held in a data store (230) in a remote information system (240) and storing a corresponding business object in a cache (210) in a local information processing device (235). A business object update message updates data held in the data store (230) or the cache (210). Furthermore, the cache stores at least one business object comprising a plurality of data objects as one retrievable entity. In this manner, business logic may be removed from an application and a cache, thereby making them easier to implement and increase the portability between the cache (210) and different data stores (130). Additionally, an improved cache management communications protocol removes the need for an application to recover from network problems, making the application easier to write.

Claims

1. A method of communicating data objects across a data communication network between a cache (210) in a local information processing device (235) and a request server (225), operably coupled to a data store (130), in a remote information system (240), the method characterised by the steps of:

assembling at least one business object by said request server (225) from data held in said data store (130);

storing a corresponding at least one business object in said cache (210); and

communicating at least one business object update message between said cache (210) and said request server (225) to update data held in said data store (130) or said cache (210), wherein said at least one business object update message substantially comprises only one or more change to said data.

2. The method of communicating data objects across a data communication network according to claim 1, wherein said step of communicating includes communicating a single business object update message containing substantially all changes to said at least one business object thereby maintaining data integrity between said cache (210) and said data store (230).

3. The method of communicating data objects across a data communication network according to claim 1 or claim 2, wherein said cache (210) is operably coupled to an application (105), the method further characterised by the step of:

requesting, by said application (105), a data update relating to said at least one business object in said request server (225);

attaching an update request to said at least one business object update message by said cache (210).

4. The method of communicating data objects across a data communication network according to claim 3, the method further characterised by the step of:

receiving said update request attached to said at least one business object update message by said request server (225); and

updating said data store (230) with said update.

5. The method of communicating data objects across a data communication network according to claim 4, the method further characterised by the step of:

informing said cache (210) by said request server (225) when said update of said data store has been completed; and

updating said cache (210) with said update request in response to said step of informing.

6. The method of communicating data objects across a data communication network according to claim 3, the method further characterised by said cache (210) performing the following steps:

reading properties from the requested cached object;

applying any updates from an attached update request to the properties;

applying any further updates from an attached child update request to the properties; and

returning the updated object to the application (105).

40. A storage medium storing processor-implementable instructions for controlling a processor to carry out the method of claim 1 or the method of claim 34.

7. A cache (210) for use in a local information processing device (235), said cache characterised in that said cache stores at least one business object comprising a plurality of data objects as one retrievable entity.

8. The cache (210) according to claim 7, wherein said at least one business object includes one or more of the following:

one or more lists of objects, objects and/or object properties.

9. The cache (210) according to claim 8, wherein said cache is further characterised by said at least one business object comprising the following three types of entity:

one or more lists of objects, objects, and object properties, where the three types of entity are interrelated only by data contained within the entities themselves.

10. The cache (210) according to any of preceding claims 7 to 9, wherein said cache (210) is operably coupled to an application (105) such that said cache stores data locally to the application, said cache (210) further characterised by storing at least one new data object or at least one modification to an existing data object from said application (105).

11. The cache (210) according to claim 10, wherein said cache is further characterised by storing a request from said application (105) to update one or more data objects, as an update request attached to said one or more data objects.

12. The cache (210) according to claim 10, wherein said cache is further characterised by storing a new request to update a data object, which at that time is being used to update the data store (130), as a child request of an original update request.

13. The cache (210) according to claim 12, wherein said cache is further characterised by a merging function to merge at least one additional new update request on a data object containing the original update request, provided said at least one original update request is not at that time being used to update data on said data store (130).

14. The cache (210) according to claim 7, wherein said cache is further characterised by:

means for reading the properties from the cached object;

means for applying, operably coupled to said means for reading, any updates from an attached update request to the properties and any further updates from an attached child update request to the properties; and

means for transmitting the updated object to the application.

15. A request server (225) operably coupled to a data store (130), wherein said request server (225) includes a logic function (228) to assemble business objects from data in held in said data store (130).

16. The request server (225) according to claim 15, wherein said logic function (228) is specific to said data store (130).

17. The request server (225) according to claim 15 or claim 16, wherein said logic function (228) is specific to data contained in said data store (130).

18. A cache management communications protocol running on a transport protocol within a data communication network, such that the cache management communications protocol,controls a flow of data between a request server and a cache, the cache management communication protocol supporting one or more of the following data transmission features:

(i) A data block size adjusted dependent upon a performance of said data communication network;

(ii) A data block re-transmit timer dependent upon a performance of the communication network; and

/or

(iii) Objects passed between said request server and said cache at opposite ends of said cache management communications protocol using, for example, self-defining data definition such as XML notation.

19. The cache management communications protocol according to claim 18, wherein the performance of said data communication network includes one or more of the following:

(i) The available bandwidth of the network,

(ii) The loading on a communication channel,

(iii) A size of a data block transmitted, or

(iv) An amount of processing to be performed in a remote information system (240) containing said request server (225) to retrieve requested data.

20. The cache management communications protocol according to claim 18 or claim 19, wherein a re-transmit timer is adaptively adjusted, in response to on one or more time-out counters based on prevailing communication network conditions.

21. The cache management communications protocol according to claim 18 or claim 19, wherein a data block size is adaptively adjusted, in response to on one or more counters based on prevailing communication network conditions.

22. The cache management communications protocol according to claim 21, wherein a first transmitted data block is constrained to support a relatively small number of messages, in order to improve a response time for receiving data from a remote information system (240).

23. The cache management communications protocol according to claim 22, wherein said first transmitted data block size is adjusted depending on one or more of the following:

(i) A type of data request,

(ii) A preference set by a user, and

(iii) A task that a user is currently performing.

24. The cache management communications protocol according to claim 18, wherein, in response to determining that said communication network is reliable, wherein as a result of sending large data blocks:

(i) Data overhead in the transmission is substantially minimised,

(ii) A more rapid transmission is provided, and/or

(iii) A more efficient use of the communication network (155) is achieved.

25. A request server (225) adapted to operate using the cache management communications protocol according to claim 18.

26. A local information processing device (235) adapted to operate using the cache management communications protocol according to claim 18.

27. A remote information system (240) adapted to operate using the cache management communications protocol according to claim 18.

28. A communication network (200) comprising a local information processing device (235) and/or a remote information system (240) that operate(s) a transport protocol such that said local information processing device (235) and/or said remote information system (240) includes a processor to perform one or more of the following data processing functions to enable data to be transmitted using said transport protocol:

wrap a data block in one packet or, if said data block is larger than a largest data packet the transport protocol supports, in multiple packets;

route data packets from a source to a destination;

if a data block was passed in more than one packet, re-assemble said data block from its constituent packets; and

detect and delete data blocks duplicated in a communication network;

the communication network (200) characterised by;

one or both of said local information processing device (235) and said remote information system (240) estimate a likely transmission time for each data packet based on a recent communication network bit rate, and forwards said estimate to a respective user, for example a cache (210) or a request server (225).

29. The communication network (200) according to claim 28, further characterised by said local information processing device (235) and/or said remote information system (240) being configured to inform said respective user (210, 235), when transmission of a data packet commences.

30. The communication network (200) according to claim 28 or claim 29, further characterised by said processor of said local information processing device (235) and/or said remote information system (240) being configured to:

detect at least one data packet lost from at least one multi-packet data block; and

re-transmit said at least one lost data packet without involvement of said user (210, 235)

31. A request server (225) adapted to operate in the data communication network according to claim 28 or claim 29.

32. A local information processing device (235) adapted to operate in the data communication network according to claim 28 or claim 29.

33. A remote information system (240) adapted to operate in the data communication network according to claim 28 or claim 29.

34. A method (300) for a local information processing device having a cache to retrieve at least one data object from a remote information system (240) across a data network, the method comprising the step of:

requesting, for example from an application (105) operably coupled to said cache (210), a data list from said cache (210);

the method characterised by the steps of;

determining, by said cache (210), that a subset or all of said objects are contained within said cache (210); and

returning said subset number or all of said objects to said application (105) directly (340, 345) from the cache (210).

35. The method (300) for retrieving at least one data object from a remote information system (240) according to claim 34, the method further characterised by the step of:

forwarding any remaining object request, where the data object(s) is not contained within said cache, to said remote information system to retrieve said remaining data object(s).

36. The method (300) for retrieving at least one data object from a remote information system (240) according to claim 35 further characterised by the steps of:

receiving (350) said remaining object(s) from said remote information system; and

transmitting (355) said remaining object(s) to said application.

37. The method (300) for retrieving at least one data object from a remote information system (240) according to claim 34 or claim 35, wherein said step of determining includes the following steps of:

requesting, by said cache, from the remote information system (240), identifiers of substantially all objects contained in said data list requested by said application (105); and

receiving said identifiers at said cache (210), in order to make said determination.

38. The method (300) for retrieving at least one data object from a remote information system (240) according to claim 34 or claim 35, the method further characterised by the steps of:

forwarding said data list to said application (105) from said cache (210); and

transmitting, a number of individual requests (325, 330 and 335) from said application (105) to said cache (210) wherein said number of requests relate to a number of objects received in said data list, such that said step of determining is performed in response to said application requesting said number of objects.

39. The method (300) for retrieving at least one data object from a remote information system (240) according to claim 34, the method further characterised by the step of:

specifying, by said application (105), a maximum number of data object requests to be concatenated into a single cache data block to be sent to said remote information system.

41. A local information processing device (235) adapted to perform any of the method steps of claim 34.

42. A cache (210) adapted to facilitate the performance of the method of the steps of claim 34.