Document Collaboration System Asynchronous Workflow Handoff

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Ensuring seamless document sharing and collaboration across diverse hardware and software platforms in remote computing environments is challenging due to inconsistencies in user requests processing and system updates, particularly with the need for timely and failure-resilient workflows.

Innovation Solution

A document management and collaboration system utilizing synchronous-to-asynchronous handoff in processing requests, where operations are executed synchronously for minimal delay and computationally intensive tasks are offloaded to asynchronous workflows, ensuring consistent user views and system integrity through APIs and workflow services.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If synchronous processing is used for all operations, then system consistency is maintained, but user-perceived delays increase

Engineering Contradiction:
Improvesystem consistencyVSAvoiduser-perceived delays
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent segments processing operations into synchronous and asynchronous categories. Critical operations that require immediate system consistency (like document metadata updates) are processed synchronously, while non-critical operations (like full document content synchronization) are processed asynchronously. This segmentation allows the system to maintain consistency where needed while minimizing user-perceived delays for less critical operations.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent implements dynamic processing mode selection where the system adapts its processing approach based on operation type and system state. The document management system dynamically determines whether to use synchronous or asynchronous processing for each operation, allowing flexibility in balancing consistency and responsiveness based on specific operational requirements.

Inventive Principle:
Principle #15Dynamics

2Loss of time

If asynchronous processing is used for all operations, then user-perceived delays are minimized, but system consistency deteriorates

Engineering Contradiction:
Improveuser-perceived delaysVSAvoidsystem consistency
Core Design Contradiction:
Loss of timeVSReliability

Solution Approach 1:

The patent segments processing operations into synchronous and asynchronous categories. Critical operations that require immediate system consistency (like document metadata updates) are processed synchronously, while non-critical operations (like full document content synchronization) are processed asynchronously. This segmentation allows the system to maintain consistency where needed while minimizing user-perceived delays for less critical operations.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent implements feedback mechanisms where the system monitors operation completion and system state, then adjusts processing modes accordingly. Asynchronous operations include feedback loops that notify the system when processing is complete, allowing the system to maintain consistency by tracking the state of asynchronous operations and ensuring proper commit sequences.

Inventive Principle:
Principle #23Feedback

3Reliability

If computationally intensive tasks are processed synchronously, then system consistency is maintained, but processing speed decreases

Engineering Contradiction:
Improvesystem consistencyVSAvoidprocessing speed
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent extracts computationally intensive tasks (such as full document content synchronization, complex formatting operations, and large file transfers) from the synchronous processing path and places them in the asynchronous processing queue. This extraction allows the main synchronous thread to complete critical operations quickly while intensive tasks execute independently in the background, maintaining system consistency without sacrificing processing speed.

Inventive Principle:
Principle #2Taking out (Extraction)

4Adaptability or versatility

If diverse hardware and software platforms are supported, then system versatility is improved, but processing inconsistencies increase

Engineering Contradiction:
Improveplatform compatibilityVSAvoidprocessing consistency
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The patent implements a universal asynchronous processing framework that standardizes how operations are handled across diverse platforms. The workflow service and task queue system provide platform-agnostic interfaces for submitting and tracking asynchronous operations, ensuring consistent behavior whether the underlying hardware or software platform differs. This universality allows the system to support multiple platforms while maintaining processing consistency through standardized asynchronous handling.

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

Data Source

PatentEP3614276B1Document management and collaboration system
Publication Date: 2023.01.04 AMAZON TECH INC
  • EP3614276B1 patent drawingFigure 1
  • EP3614276B1 patent drawingFigure 2
  • EP3614276B1 patent drawingFigure 3

AI summary

A method and apparatus for document collaboration and management are disclosed. In the method and apparatus, a document may be incorporated in a document directory maintained by a document collaboration and management service. A portable representation underlay based on the document may be generated using one or more asynchronous workflows and the portable representation underlay may be provided in response to a user request.