PREDICTIVE MEMORY CACHING

• US 20170315917A1
• Filed: 04/29/2016
• Published: 11/02/2017
• Est. Priority Date: 04/29/2016
• Status: Active Grant

• Current Assignee: NCR Corporation
• Original Assignee: NCR Corporation
• Inventors: Yamamoto, Leo, Chinnaveerappan, Lakshmanan, Wang, Eric
• Granted Patent: US 9,946,653 B2
• Time in Patent Office: Days
• CPC Class Codes: G06F 12/0862 with prefetch
• CPC Class Codes: G06F 12/0866 for peripheral storage systems, e.g. disk cache
• CPC Class Codes: G06F 2212/1021 Hit rate improvement
• CPC Class Codes: G06F 2212/6028 Prefetching based on hints or prefetch instructions
• CPC Class Codes: G06N 20/00 Machine learning
• CPC Class Codes: H04L 67/14 Session management for real-time applications in data packet communications networks H04L65/1066
• CPC Class Codes: H04L 67/5681 Pre-fetching or pre-delivering data based on network characteristics

Abstract

Metadata history is collected for operations performed by an application as directed by a user. In a subsequent interaction by the user with the application, interaction metadata for the interaction is matched to a pattern in the metadata history. An operation identified in the pattern is processed as a background process and results from processing the operation are pre-staged in cache of the device being operated by the user. When the user requests the operation during the subsequent interaction with the application, the pre-staged results from the cache are provided to the user.

Claims

1. A method, comprising:

collecting metadata for an interaction with an application;

matching the metadata with a pattern in metadata history for previous interactions with the application;

executing an operation identified in the pattern to obtain a result; and

prepopulating a cache with the result in advance of the interaction requesting that the operation be processed by the application.

2. The method of claim 1 further comprising, providing the result from the cache when the interaction requests the operation for processing by the application.

3. The method of claim 1, wherein collecting further includes collecting the metadata as session metadata for a network session between the application and a network application, wherein the network session is the interaction.

4. The method of claim 1, wherein collecting further includes collecting the metadata as session metadata for a session initiated when a user operating the device initiates the application on the device for execution, wherein the session is between the user and the application and contained on the device.

5. The method of claim 1, wherein matching further includes scoring weighted components of the metadata and comparing the scored and weighted components against scored and weighted patterns in the metadata history for matching to the pattern.

6. The method of claim 1, wherein matching further includes processing a machine learning algorithm for matching to the pattern.

7. The method of claim 6, wherein processing further dynamically adjusting a factor processed by the machine learning algorithm in performing matching based on one or more actions taken during the interaction for processing by the machine learning algorithm in subsequent interactions with the application.

8. The method of claim 1, wherein executing further includes executing the operation as a series of operations associated with a workflow.

9. The method of claim 8, wherein executing further includes processing at least one of the operations from the series by a different application from the application.

10. The method of claim 1, wherein executing further includes executing the operation as a background process on the device.

11. The method of claim 1, wherein prepopulating further includes streaming the results over a network connection as a background process to the cache, wherein the cache is part of the device.

12. A method, comprising:

maintaining a profile for first interactions with an application on a first device;

identifying a second interaction with the application occurring on a second device;

synchronizing the profile from the first device to the second device upon detection of initiation of the second interaction on the second device;

preprocessing an operation for the application on the second device based on the profile to obtain a result; and

prepopulating the result to a cache of the second device in advance of and in anticipation of the second interaction requesting the operation of the application during the second interaction.

13. The method of claim 12 further comprising, providing the result from the cache when the second interaction requests the result from the application.

14. The method of claim 13, wherein maintaining further includes maintaining the profile as patterns derived from a history of interactions performed by a user when interacting with the application.

15. The method of claim 14, wherein maintaining further includes embedding identifiers for operations available with the application within the patterns.

16. The method of claim 12, wherein synchronizing further includes synchronizing the profile from a server interfaced to the first device and pushing the profile from the server to the second device.

17. The method of claim 16, wherein preprocessing further includes presenting a confirmation request on a display of the second device requesting confirmation from a user interacting with the application on the second device before preprocessing at least a portion of the operation on the second device.

18. A device, comprising:

a hardware processor;

a cache memory;

a predictive caching service configured to;

i) execute on the hardware processor, ii) preprocess an operation for an application in advance of a request made by a user interacting with the application based on a behavioral profile of the user for prior operations taken by the user during prior interactions of the user with the application, iii) prepopulate the cache memory with a result obtained from preprocessing the operation in advance of a request made by the user for the application to process the operation, and iv) provide the result from the cache memory when the user makes the request for the application to process the operation.

19. The device of claim 18, wherein the predictive caching service is further configured, in iii), to:

preprocess at least one additional operation to resolve a variable value for a variable associated with a template for a confirmation request, replace the variable with the resolved variable value, and present the template as the confirmation request for confirmation by user before preprocessing the operation.

20. The device of claim 18, wherein the device is one of:

a phone, a wearable processing device, a tablet, a laptop, a desktop computer, a Self-Service Terminal, and a POS terminal.