Disconnectible Applications for Offline Client Execution

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional networked applications require constant connectivity to a server, making them unreliable and inefficient when network conditions are poor, as they often wait for server responses, leading to resource wastage and limited flexibility in data processing.

Innovation Solution

The development of disconnectible applications that can execute autonomously on a client without constant server connectivity, using a runtime environment for asynchronous communication and local data storage, allowing for dynamic data access and message handling, enabling operation even in poor network conditions.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If conventional networked applications require constant connectivity to a server, then the applications can access real-time data and services, but the applications become unreliable and inefficient when network conditions are poor

Engineering Contradiction:
Improveapplication reliabilityVSAvoidadaptability to network conditions
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The system pre-loads applications, data, and services onto the client device before network connectivity is needed. The runtime environment stores application code and data locally, enabling the client to execute applications autonomously without constant server connectivity. This preliminary action ensures reliability during poor network conditions while maintaining adaptability when connectivity is available.

Inventive Principle:
Principle #10Preliminary action

2Productivity

If applications wait for server responses before proceeding, then data accuracy is maintained, but resource wastage occurs and productivity decreases

Engineering Contradiction:
Improveapplication processing efficiencyVSAvoidresource wastage
Core Design Contradiction:
ProductivityVSLoss of energy

Solution Approach 1:

Data and services are pre-loaded and cached on the client device before being needed. The runtime environment maintains local copies of data that can be accessed immediately without waiting for server responses. This eliminates resource wastage from repeated network requests while maintaining data accuracy through synchronization when connectivity is available.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The runtime environment enables continuous local execution of applications without interruption for server communication. Processes can proceed continuously using locally cached data and services, eliminating the stop-start pattern caused by waiting for server responses. This maintains productivity while reducing energy consumption from repeated network transactions.

Inventive Principle:
Principle #20Continuity of useful action

3Ease of operation

If servers devote resources to responses for remote clients, then client applications can function, but server resources are wasted on unimportant responses

Engineering Contradiction:
Improveclient application functionalityVSAvoidserver resource utilization
Core Design Contradiction:
Ease of operationVSProductivity

Solution Approach 1:

The system extracts critical functionality from the server and relocates it to the client through pre-loading. Applications, data, and services are stored locally on the client device, eliminating the need for continuous server processing. This extraction maintains client application functionality while freeing server resources for more important tasks.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The client device becomes self-sufficient by storing and executing applications autonomously. The runtime environment on the client handles data access, processing, and communication without requiring continuous server intervention. This self-service capability maintains ease of operation for clients while dramatically improving server resource utilization for critical operations.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS7685258B2Disconnectible applications
Publication Date: 2010.03.23 ORACLE INT CORP
  • US7685258B2 patent drawing
  • US7685258B2 patent drawing
  • US7685258B2 patent drawing

AI summary

Embodiments provide mechanisms and methods for providing disconnectible applications capable of executing at least semi-autonomously, i.e., without needing constant contact with a server, on a client substantially independent of server connectivity. The ability of a disconnectible application to execute on a client substantially independent of server connectivity can enable enhanced flexibility in organizing applications to build data processing systems.