Client Cache Search for High Latency Networks

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional methods for mobile users to access data on multiple computing devices are inefficient due to high network latency and the need to re-input data across siloed applications, leading to slow response times and excessive network usage, especially in low-bandwidth environments.

Innovation Solution

A system that utilizes a client cache and server cache to perform searches, allowing for sub-second response times and minimizing network traffic by caching data locally and synchronizing only incremental changes, while maintaining access to data even in low or no-network coverage conditions.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If data is accessed remotely over a high latency network, then data availability is improved, but response time deteriorates

Engineering Contradiction:
Improvedata availabilityVSAvoidresponse time
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

The system performs preliminary actions by caching data locally on the mobile device before it is needed. The client cache stores copies of data from remote data sources, allowing the device to access data immediately without waiting for network responses. This preliminary caching action resolves the contradiction by preparing data in advance so that when access is needed, the response time is fast even though the data originates from remote sources.

Inventive Principle:
Principle #10Preliminary action

2Loss of time

If data is cached locally on the client device, then response time is improved, but network usage increases

Engineering Contradiction:
Improveresponse timeVSAvoidnetwork usage
Core Design Contradiction:
Loss of timeVSLoss of energy

Solution Approach 1:

The system applies local quality by implementing a tiered caching strategy where frequently accessed data is cached locally on the mobile device while less frequently accessed data remains on remote servers. The client cache prioritizes storing data that is likely to be accessed soon, allowing the device to respond quickly to common queries without excessive network usage. This selective local caching resolves the contradiction by optimizing which data is cached based on access patterns.

Inventive Principle:
Principle #3Local quality

Solution Approach 2:

The system uses partial action by caching only the necessary portion of data locally rather than all data. The client cache stores a subset of data from remote sources based on predicted access patterns and available device storage. This partial caching approach improves response time for frequently accessed data while avoiding excessive network usage and device storage consumption that would result from caching everything.

Inventive Principle:
Principle #16Partial or excessive action

3Adaptability or versatility

If multiple siloed applications are used to access different data sources, then data specialization is improved, but ease of operation deteriorates

Engineering Contradiction:
Improvedata specializationVSAvoiduser burden
Core Design Contradiction:
Adaptability or versatilityVSEase of operation

Solution Approach 1:

The system applies universality by creating a unified client application that can access multiple different data sources through a single interface. The mobile device's client application queries both local cache and remote data sources transparently, allowing users to access various types of data (contacts, messages, emails, etc.) without needing to switch between multiple specialized applications. This multi-functional approach resolves the contradiction by maintaining data specialization while eliminating the need for users to manually manage multiple applications.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Solution Approach 2:

The system merges multiple data access functions into a unified system. The client application combines access to local cache, multiple remote data sources, and synchronization capabilities into a single integrated interface. This merging allows users to interact with one application rather than multiple siloed applications, reducing the user burden of manually re-inputting data across different applications while maintaining access to specialized data sources.

Inventive Principle:
Principle #5Merging (Combining)

4Reliability

If network connection is maintained continuously, then data access reliability is improved, but energy consumption increases

Engineering Contradiction:
Improvedata access reliabilityVSAvoidenergy consumption
Core Design Contradiction:
ReliabilityVSUse of energy by moving object

Solution Approach 1:

The system uses periodic action by establishing network connections only when needed rather than maintaining continuous connections. The mobile device queries the remote data source periodically or on-demand based on whether data needs to be synchronized or accessed. This periodic connection approach maintains data access reliability by ensuring the device can retrieve updated data when connected, while significantly reducing energy consumption compared to maintaining persistent network connections throughout device operation.

Inventive Principle:
Principle #19Periodic action

Data Source

PatentUS9495474B2Method and system for multi-tiered search over a high latency network
Publication Date: 2016.11.15 SAP SE
  • US9495474B2 patent drawing
  • US9495474B2 patent drawing
  • US9495474B2 patent drawing

AI summary

A computer implemented method and system include executing a search against both a client cache associated with a client and data sources remotely coupled to the client over a network connection. Results from the search against the client cache are rendered on a client UI. The client cache and the client UI are updated with the results from the search against the data sources.