Thin-Client Display Synchronization for Real-Time PDF Markup

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Collaborative document editing on PDF documents is challenging for thin client computing devices due to the need for substantial processing and storage capabilities to handle native markup objects, which many devices lack.

Innovation Solution

Utilizing cross-compatible markup objects, such as JSON objects, that are more consumable by thin client devices, enabling real-time collaboration by subscribing to events, extracting modifications, and transmitting these objects across thin client applications.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If native markup objects are used for collaborative document editing, then markup functionality and collaboration capability are improved, but processing load and storage requirements increase significantly for thin client devices

Engineering Contradiction:

Improvecollaborative document editing capabilityVSAvoidprocessing load on thin client

Core Design Contradiction:

Adaptability or versatilityVSUse of energy by moving object

Solution Approach 1:

The patent extracts the heavy processing and storage requirements from thin client devices by implementing a server-based architecture. The server handles native markup object processing, event subscription, and collaboration logic, while thin clients only need to display rendered documents and transmit basic user interactions. This extraction allows thin clients to gain collaborative editing capability without bearing the processing burden.

Inventive Principle:

Principle #2Taking out (Extraction)

Solution Approach 2:

The patent introduces a server as an intermediary between thin clients and the document markup system. The server mediates all collaborative operations by receiving events from thin clients, processing native markup objects, and distributing updated rendered documents back to clients. This intermediary approach enables full collaboration functionality while shielding thin clients from processing complexity.

Inventive Principle:

Principle #24Intermediary (Mediator)

2Adaptability or versatility

If native markup objects are used for collaborative document editing, then markup functionality is improved, but device complexity and storage requirements increase for thin client devices

Engineering Contradiction:

Improvemarkup handling capabilityVSAvoidlocal installation requirements

Core Design Contradiction:

Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent extracts complex markup processing libraries and rendering engines from thin client devices and relocates them to the server. Thin clients only require basic web browser capabilities to display rendered documents and send/receive JSON events. This extraction eliminates the need for heavy local installations while maintaining full markup handling capability through server-side processing.

Inventive Principle:

Principle #2Taking out (Extraction)

Solution Approach 2:

The patent makes the server universal by implementing it as a multi-functional platform that handles document storage, markup processing, event management, and document rendering for all thin clients. This centralized universal server eliminates the need for each thin client to independently install and maintain complex markup processing software, reducing device complexity while maintaining capability.

Inventive Principle:

Principle #6Universality (Multi-functionality)

3Productivity

If real-time collaboration is implemented across thin client devices, then collaboration speed and responsiveness are improved, but network bandwidth and data transmission requirements increase

Engineering Contradiction:

Improvecollaboration speedVSAvoiddata transmission volume

Core Design Contradiction:

ProductivityVSQuantity of substance

Solution Approach 1:

The patent applies local quality by transmitting different types of data in different formats optimized for their specific purposes. Full rendered documents are transmitted only when necessary (e.g., initial load, major changes), while real-time collaboration events are transmitted as lightweight JSON objects containing only essential modification information. This differentiated data transmission approach enables real-time collaboration responsiveness while minimizing overall network bandwidth consumption.

Inventive Principle:

Principle #3Local quality

Solution Approach 2:

The patent implements periodic action through event-driven architecture where data transmission occurs only when specific events are triggered (e.g., user action, document change). Instead of continuous polling or periodic full document transmission, the system transmits updates asynchronously in response to actual collaboration events. This event-triggered periodic transmission maintains real-time collaboration speed while significantly reducing unnecessary data transmission volume.

Inventive Principle:

Principle #19Periodic action

Data Source

PatentUS12432270B2Systems and methods for synchronizing graphical displays across thin client devices

Publication Date: 2025.09.30 BLUEBEAM INC

AI summary

Systems and methods are disclosed for synchronizing a document markup modification across a plurality of devices. One method comprises subscribing to one or more events occurring in a first document markup application, the first document markup application being a first thin client application, and receiving a notification indicating a modification to a document markup in the first document markup application. A cross-compatible markup object associated with the modified document markup may be extracted and transmitted to a second document markup application, the second document markup application being a second thin client application.