Data Object State Persistence During Cross-Device Transformation

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Current systems lack the ability to interact with digital objects represented by graphical shapes through a graphical user interface, and they struggle to efficiently transform and persist all states of data objects during the transformation lifecycle, especially in lightweight browsers with limited processing capabilities.

Innovation Solution

A system and process that allows users to upload media objects via a browser to a backend server using drag-and-drop methods, interpreting various object types and maintaining intelligent routines to separate data elements, enabling the transformation and persistence of data objects across devices and platforms, including the creation and recreation of graphical shapes and collages.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If data objects are transformed across multiple applications and devices, then functionality and versatility are improved, but device complexity and data management complexity increase

Engineering Contradiction:

ImprovefunctionalityVSAvoidcomplexity

Core Design Contradiction:

Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The system segments the data object into multiple states (original state, intermediate states, and final transformed state) and maintains each state separately in the database. This allows the application to retrieve and work with specific states without managing the entire transformation complexity, thus improving versatility while controlling complexity through structured data organization.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The patent introduces a server as an intermediary between multiple applications and devices. The server maintains the data object states in a centralized database and manages the transformation lifecycle, acting as a mediator that handles the complexity of cross-device data synchronization and transformation, allowing applications to focus on their specific functionality.

Inventive Principle:

Principle #24Intermediary (Mediator)

2Loss of information

If all states of data objects are persisted during transformation lifecycle, then information completeness is improved, but storage requirements and system complexity increase

Engineering Contradiction:

Improveinformation completenessVSAvoidstorage requirements

Core Design Contradiction:

Loss of informationVSQuantity of substance

Solution Approach 1:

The patent extracts only the essential transformation information (transformation type, parameters, and state relationships) from the complete data object lifecycle and stores this metadata in the database, while the actual data objects are stored in their respective states. This extraction approach maintains information completeness by preserving the transformation lineage without storing redundant full copies of all intermediate data, thus reducing storage requirements.

Inventive Principle:

Principle #2Taking out (Extraction)

Solution Approach 2:

The system creates selective copies of data objects in different states rather than storing the entire transformation history in full detail. The database stores references and transformation metadata that allow reconstruction of the complete lifecycle without requiring excessive storage space, achieving information completeness through intelligent copying strategies.

Inventive Principle:

Principle #26Copying

3Ease of operation

If lightweight browsers with limited processing capabilities are used, then ease of operation and accessibility are improved, but processing capability and transformation efficiency worsen

Engineering Contradiction:

ImproveaccessibilityVSAvoidtransformation efficiency

Core Design Contradiction:

Ease of operationVSProductivity

Solution Approach 1:

The server acts as a powerful intermediary that performs the computationally intensive data transformation operations, while the lightweight browser only handles user interface interactions and displays results. This division of labor allows accessibility through lightweight clients while maintaining high transformation efficiency through the server's processing power.

Inventive Principle:

Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent replaces the mechanical processing system (local browser processing) with a network-based distributed system where the browser communicates transformation requests to the server. This substitution allows lightweight browsers to access powerful transformation capabilities remotely, maintaining ease of operation while improving transformation efficiency through server-side processing.

Inventive Principle:

Principle #28Mechanics substitution (Replace mechanical system)

Data Source

PatentUS11689602B2Object transformations and the persistence of all states during the transformation lifecycle

Publication Date: 2023.06.27 JADHAV AJAY

AI summary

A system for object transformations and persistence of all states during a transformation lifecycle includes a user interface for receiving or creating a data object, a first application capable of processing and transmitting attributes of a data object, a server capable of receiving, persisting or distributing these attributes, a second application capable of receiving and processing these attributes to create or recreate a data object, a user interface for displaying the created or recreated data object, wherein the first and second applications of the system may be the same, may reside on the same device or platform, or may reside on different devices or platforms.