Thin Client Disconnected Operation via Local Application Logic Caching

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Thin client applications face disruptions when disconnected from the network, leading to incomplete tasks and reduced productivity due to the unpredictability of network connections, which are critical for mission-critical applications like expense reporting and calendar management.

Innovation Solution

A system and method that allow a thin client to download a version of the application before disconnecting, enabling continued functionality during disconnection, with changes saved for integration upon reconnection, using a synchronization service to process and update data.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If a thin client application relies on continuous network connection to access remote application logic, then the application can leverage server-side processing power and security, but the application becomes inaccessible when network connection is disrupted

Engineering Contradiction:
Improveapplication availabilityVSAvoidoperational flexibility during network disruption
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The system pre-downloads application logic and data to the client before network disruption occurs. The client system stores a local copy of the application logic and relevant data, enabling continuous operation during network outages. This preliminary action ensures the application remains functional without requiring real-time network connectivity.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent creates a local copy of the application logic and data on the client system. This copy allows the thin client to execute application functions locally when network connection is unavailable. The local copy includes necessary application logic, data structures, and operational state, enabling the application to function independently of the remote server during disconnection events.

Inventive Principle:
Principle #26Copying

2Device complexity

If the application is designed as a thin client with minimal local processing capability, then hardware requirements and maintenance complexity are reduced, but the client cannot perform processing functions during network disconnection

Engineering Contradiction:
Improveclient hardware requirementsVSAvoidtask completion during network outage
Core Design Contradiction:
Device complexityVSProductivity

Solution Approach 1:

The system performs preliminary actions by downloading and caching application logic and data before network disruption. This enables the thin client to execute processing functions locally during outages without requiring permanent installation of heavy processing capabilities. The application logic is prepared in advance and stored locally for immediate execution.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent implements dynamic adaptation where the client can switch between server-mode operation (when connected) and local-mode operation (when disconnected). The application logic dynamically loads from or saves to the local storage based on network availability, allowing the thin client to maintain full functionality across varying network conditions without permanent hardware upgrades.

Inventive Principle:
Principle #15Dynamics

3Loss of information

If network-based applications require real-time connectivity for data access and processing, then data consistency and security are maintained, but task completion is delayed when connection is unavailable

Engineering Contradiction:
Improvedata consistencyVSAvoidtask completion delay
Core Design Contradiction:
Loss of informationVSLoss of time

Solution Approach 1:

The system pre-loads necessary data and application logic before network disruption occurs. During disconnection, the client continues processing using locally stored data and application logic, eliminating task completion delays. When connectivity restores, the system automatically synchronizes changes with the server, ensuring data consistency is maintained without waiting for real-time connection.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent enables continuous execution of application tasks by maintaining local copies of application logic and data. Processing actions continue uninterrupted during network outages, as the thin client can execute functions and manipulate data locally. This continuity ensures task completion is not delayed by network connectivity status.

Inventive Principle:
Principle #20Continuity of useful action

4Adaptability or versatility

If the application logic is stored locally on the client system, then the application can operate during network disconnection, but the client system requires more storage space and processing capability

Engineering Contradiction:
Improveoffline operation capabilityVSAvoidstorage space requirement
Core Design Contradiction:
Adaptability or versatilityVSQuantity of substance

Solution Approach 1:

The system performs preliminary actions by downloading only the necessary application logic and currently needed data before disconnection occurs. This selective pre-loading minimizes the storage space required on the client system while maintaining offline operation capability. The application logic is cached in advance, and only relevant data is stored locally based on current operational needs.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent implements partial caching of application logic and data on the client system. Instead of storing the complete application and all possible data, the system stores only the necessary portions for current operations. This partial action approach reduces storage space requirements while maintaining sufficient functionality for offline operation during network disconnection events.

Inventive Principle:
Principle #16Partial or excessive action

Data Source

PatentUS7685253B1System and method for disconnected operation of thin-client applications
Publication Date: 2010.03.23 ORACLE AMERICAN INC
  • US7685253B1 patent drawing
  • US7685253B1 patent drawing
  • US7685253B1 patent drawing

AI summary

System and method for disconnected operation of thin-client applications. In embodiments, a thin client on a client system may be used to access an application on a server via a network. Prior to the thin client disconnecting from the application, a version of the application including at least a portion of the application logic of the application may be downloaded to the client system to be accessed using the thin client during disconnected operation of the client system. After reconnection of the thin client to the application, changes made, if any, to application data on the client system may be integrated into the application data on the server.