Persistent Node Framework for Graphical Context Retention

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current computer graphics technologies lack persistence and self-persistence, making it difficult to retain context and user interactions on graphical rendering surfaces, especially in cloud computing environments, where collaborative applications require seamless and interactive rendering of diverse graphical shapes and objects.

Innovation Solution

A hierarchical, persistent, and relational node framework that allows for representing scenarios on any graphical rendering surface, tracking user interactions, applying transforms to un-rendered data, and persisting modifications in memory or databases, both locally and in cloud infrastructure, enabling true persistence and interaction across different types of objects.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If stateless information is used in browser graphics rendering, then rendering capability is provided, but persistence and context retention are lost

Engineering Contradiction:
ImprovepersistenceVSAvoidcontext retention
Core Design Contradiction:
ReliabilityVSLoss of information

Solution Approach 1:

The patent implements preliminary action by establishing persistent storage mechanisms before graphical rendering occurs. The system pre-configures storage layers (database, file system, cloud infrastructure) to capture and retain graphical data, user interactions, and contextual information before the actual rendering takes place, ensuring that this information is preserved and available for subsequent operations.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent applies copying by creating multiple representations of graphical data across different storage mediums. The system generates copies of graphical objects, user interactions, and contextual metadata and stores them in various locations (local database, cloud infrastructure, file system), allowing the original rendering to be reproduced or restored from these copies, thereby maintaining persistence and context retention.

Inventive Principle:
Principle #26Copying

2Adaptability or versatility

If graphical rendering is performed on any computing device, then versatility is improved, but complexity of tracking interactions and persisting data increases

Engineering Contradiction:
Improverendering surface compatibilityVSAvoidinteraction tracking complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent implements universality by designing a multi-functional node framework that can operate across different computing devices and graphical rendering surfaces. The system uses universal data structures and protocols that work consistently whether the rendering occurs on web browsers, mobile devices, or desktop applications, allowing the same interaction tracking and persistence mechanisms to function across all platforms without requiring device-specific implementations.

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

Solution Approach 2:

The patent applies the intermediary principle by introducing a centralized node framework that acts as a mediator between the graphical rendering surface and the persistence layer. This intermediary layer handles the complexity of tracking user interactions and managing data persistence, abstracting these complex operations from the rendering surface itself and providing a simplified interface for interaction tracking regardless of the underlying platform.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Productivity

If transforms are applied to un-rendered data in memory, then rendering efficiency is improved, but data management complexity increases

Engineering Contradiction:
Improverendering efficiencyVSAvoiddata management complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The patent applies segmentation by dividing the data management system into separate functional layers: un-rendered data storage, transformation processing, and rendering output. The node framework segments data into distinct nodes that can be independently managed, transformed, and rendered. This segmentation allows transforms to be applied efficiently to un-rendered data in memory without creating a monolithic data management system, as each node can be processed independently through the transformation layer.

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS10382287B2Persistent node framework
Publication Date: 2019.08.13 JADHAV AJAY
  • US10382287B2 patent drawing
  • US10382287B2 patent drawing
  • US10382287B2 patent drawing

AI summary

A node framework capable of rendering any aspect of a computer model with persistence onto a graphical rendering surface of a computing device is disclosed. Initially, a plurality of nodes are received, where each of the plurality of nodes is associated with a payload, at one of the plurality of nodes is a persistent node, and another of the plurality of nodes has a predefined relationship with the persistent node. Next, the payload associated with each of the plurality of nodes extracted. Finally, display of information based on the extracted payload associated with each of the plurality of nodes is enabled.