Cloud Content Management Local Queuing for Intermittent Connectivity

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing content management systems face limitations in providing seamless user interactions, especially when connectivity between the user device and the server is intermittent, leading to delays in content upload, sharing, and management functionalities.

Innovation Solution

Implementing a system where user devices can display and interact with content as if it has already been uploaded to the server, using a processing module to queue requests and assign local identifiers, which are later replaced with global identifiers once network connectivity is established, allowing for immediate user interaction and seamless functionality regardless of network status.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If the system waits for server confirmation before displaying content, then data consistency is maintained, but user interaction speed and responsiveness deteriorate

Engineering Contradiction:
Improvedata consistencyVSAvoiduser interaction delay
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system performs preliminary actions by displaying content locally immediately upon user request without waiting for server confirmation. The client application shows the content in the user interface right away, then separately transmits the request to the server in the background. This resolves the contradiction by prioritizing user interaction speed while maintaining eventual data consistency through the subsequent server synchronization.

Inventive Principle:
Principle #10Preliminary action

2Loss of time

If the system operates fully locally without server connection, then user interaction speed improves, but data consistency and content management reliability deteriorate

Engineering Contradiction:
Improvecontent upload timeVSAvoidcontent management consistency
Core Design Contradiction:
Loss of timeVSReliability

Solution Approach 1:

The system maintains continuity of useful action by enabling uninterrupted local content management operations. The client application allows users to upload, share, and manage content locally without being blocked by network connectivity status. Background synchronization processes continue to update the server when connectivity is available, ensuring eventual consistency while maintaining continuous local functionality.

Inventive Principle:
Principle #20Continuity of useful action

3Measurement precision

If the system requires high network connectivity for server interaction, then data accuracy is maintained, but system adaptability to intermittent connectivity deteriorates

Engineering Contradiction:
Improvecontent synchronization accuracyVSAvoidconnectivity condition adaptability
Core Design Contradiction:
Measurement precisionVSAdaptability or versatility

Solution Approach 1:

The system dynamically adapts its operation mode based on network connectivity conditions. When connectivity is good, it performs synchronous operations with the server to maintain high data accuracy. When connectivity is poor or intermittent, it switches to asynchronous local operations, allowing content management to continue with reduced but acceptable synchronization accuracy. This dynamic behavior resolves the contradiction by adjusting the balance between accuracy and adaptability based on real-time conditions.

Inventive Principle:
Principle #15Dynamics

Data Source

PatentUS10067652B2Providing access to a cloud based content management system on a mobile device
Publication Date: 2018.09.04 DROPBOX INC
  • US10067652B2 patent drawing
  • US10067652B2 patent drawing
  • US10067652B2 patent drawing

AI summary

A user device has a processing module and a UI module. The processing module may have a permanent connection to the UI module, and an intermittent connection to a content management system over a data network. User requested actions are executed within the UI module. For each such action, a parallel request is sent to the content management system when network connectivity allows. Results of the user requested actions are presented within the UI module as if they had been implemented on the content management system. The user may thus interact with content as if all user requested actions have occurred substantially simultaneously with the request. When network connectivity allows, confirmation is received in the processing module from the content management system that the actions have been implemented, and the state of the user requested actions in the UI module is matched with that on the content management system.