Metadata Tree Sub-Tree Traversal for Web UI Updates

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current solutions for customizing and updating web applications require significant manual effort due to the complexity of feature sets and frequent data changes, making static rendering insufficient for performance and user experience.

Innovation Solution

A method that involves rendering a user interface by traversing a metadata tree, calculating a minimum sub-metadata tree for updated nodes and their dependencies, and re-rendering only that sub-tree, allowing for efficient updates without re-rendering the entire interface.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of manufacture

If static rendering is used for web applications with complicated feature sets, then implementation is simpler, but performance and user experience requirements are not satisfied

Engineering Contradiction:
Improveimplementation simplicityVSAvoidperformance
Core Design Contradiction:
Ease of manufactureVSProductivity

Solution Approach 1:

The patent segments the user interface rendering process by introducing a metadata tree structure that divides the interface into hierarchical nodes. This allows the system to render only the necessary portions of the interface based on metadata changes, rather than re-rendering the entire static page. The segmentation enables dynamic updates while maintaining overall system simplicity.

Inventive Principle:
Principle #1Segmentation

2Adaptability or versatility

If manual customization is performed for different customer requirements, then user experience is tailored, but significant manual effort is required

Engineering Contradiction:
Improvecustomization capabilityVSAvoidmanual effort
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

The patent implements self-service customization through a metadata-driven architecture. Instead of requiring manual customization for each customer, the system automatically adapts the user interface by processing metadata that defines different feature sets and configurations. The metadata tree structure enables the system to self-configure based on customer requirements without manual intervention.

Inventive Principle:
Principle #25Self-service

3Reliability

If frequent web page updates are performed, then data currency is maintained, but significant manual effort is required for each update

Engineering Contradiction:
Improvedata currencyVSAvoidupdate effort
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent applies preliminary action by pre-defining the metadata tree structure that represents the user interface hierarchy before updates are needed. When data changes occur, the system only needs to update the affected metadata nodes rather than manually updating the entire web page. This preliminary structuring enables efficient, automated updates while maintaining data currency.

Inventive Principle:
Principle #10Preliminary action

4Stability of the object's composition

If the entire user interface is re-rendered for each update, then consistency is maintained, but performance efficiency decreases

Engineering Contradiction:
Improveinterface consistencyVSAvoidupdate efficiency
Core Design Contradiction:
Stability of the object's compositionVSProductivity

Solution Approach 1:

The patent extracts and processes only the minimum sub-metadata tree that contains changed nodes and their dependent nodes, rather than re-rendering the entire metadata tree. This extraction approach maintains interface consistency for updated portions while avoiding the performance cost of re-rendering unchanged portions, thereby improving update efficiency.

Inventive Principle:
Principle #2Taking out (Extraction)

5Productivity

If a metadata tree structure is implemented for dynamic rendering, then update efficiency is improved, but system complexity increases

Engineering Contradiction:
Improveupdate efficiencyVSAvoidsystem complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The patent implements a universal metadata tree structure that serves multiple functions: defining the user interface hierarchy, tracking changes, determining dependencies, and guiding selective re-rendering. This multi-functional approach consolidates what could be multiple separate systems into a single unified metadata-driven framework, managing complexity while maintaining update efficiency.

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

Data Source

PatentUS10558736B2Metadata driven user interface layout control for web applications
Publication Date: 2020.02.11 SAP SE
  • US10558736B2 patent drawing
  • US10558736B2 patent drawing
  • US10558736B2 patent drawing

AI summary

Methods and apparatus, including computer program products, are provided for rendering and re-rendering a user interface of a web application based on definition of and traversal of a minimum sub-metadata tree. Related apparatus, systems, methods, and articles are also described.