Webpage Fragment Synchronization Across Trusted Devices

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Users face difficulties in continuing fragmented webpage tasks across multiple devices due to the need for re-authorization, extra steps for saving task context, and resource consumption when working with whole applications instead of task-specific fragments.

Innovation Solution

A computer-implemented method for synchronously sharing webpage fragments across trusted devices, allowing users to share and continue working on specific task components without re-authentication, enabling seamless transitions between devices and preserving work context.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If users access webpage tasks from multiple devices through traditional methods, then they can continue working on different devices, but they must re-authenticate and re-save task context

Engineering Contradiction:

Improveease of continuing tasks across devicesVSAvoidtime for re-authentication and re-saving context

Core Design Contradiction:

Ease of operationVSLoss of time

Solution Approach 1:

The patent segments the webpage into task-specific fragments that can be independently shared across devices. Instead of sharing entire webpages or applications, only the relevant task portions are extracted and transmitted to other devices, enabling seamless continuation without re-authentication.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The system performs preliminary actions by pre-authenticating users and pre-saving task context on the server before device switching occurs. When a user switches devices, the authenticated session and task state are already prepared and waiting, eliminating the need for re-authentication and manual context saving.

Inventive Principle:

Principle #10Preliminary action

2Loss of information

If users work with whole applications across devices, then they can maintain complete context, but resource consumption increases

Engineering Contradiction:

Improvetask context preservationVSAvoidresource consumption

Core Design Contradiction:

Loss of informationVSUse of energy by moving object

Solution Approach 1:

The patent extracts only the necessary task-specific fragments from complete webpages and applications. These fragments contain only the essential task context needed for continuation, excluding unnecessary application resources. This extraction approach preserves task information while significantly reducing the resources that need to be transferred and processed across devices.

Inventive Principle:

Principle #2Taking out (Extraction)

3Use of energy by moving object

If users share task fragments across devices, then resource consumption is reduced, but system complexity increases

Engineering Contradiction:

Improveresource consumptionVSAvoidsystem complexity for fragment management

Core Design Contradiction:

Use of energy by moving objectVSDevice complexity

Solution Approach 1:

The patent introduces a server as an intermediary that manages the complexity of fragment segmentation, authentication, and synchronization. The server handles the intricate tasks of identifying task fragments, managing user sessions, and coordinating between devices, while client devices receive simplified instructions. This centralizes complexity in the server infrastructure rather than burdening individual devices.

Inventive Principle:

Principle #24Intermediary (Mediator)

Data Source

PatentUS11622021B2Synchronous shared webpage fragment across trusted devices

Publication Date: 2023.04.04 INTERNATIONAL BUSINESS MACHINE CORPORATION

AI summary

A web application is initiated with a server device. A share component of the web application is received. A connection with a receiver device is initiated. The share component is pushed to the receiver device. An updated share component is received from the receiver device. The updated share component is a modified version of the share component. The updated share component is pushed to the server device.