Distributed Object Tree for Asynchronous Data Access

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Traditional data access interfaces require significant customization and redevelopment efforts when porting functionality to different user interfaces, leading to increased costs and complexity due to the need for specific knowledge of the user interface and manual integration of objects into data trees.

Innovation Solution

A system that generates a distributed object tree asynchronously, allowing data access mechanisms to interact with publisher modules rather than specific user interfaces, enabling automatic representation and update of the tree in the user interface without requiring developers to write custom integration code, and supporting portability across different MVC frameworks.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If data access interfaces are customized for a particular user interface, then data access functionality is achieved, but implementation effort and costs increase significantly

Engineering Contradiction:
Improvedata access functionalityVSAvoidimplementation effort
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent creates a universal data access interface that can work with multiple different user interfaces through a standardized object tree structure. Instead of customizing data access for each specific UI, the system uses a generic interface that interacts with publisher modules, allowing the same data access mechanism to serve multiple UI types (Windows forms, web, mobile, etc.).

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

Solution Approach 2:

The patent introduces an intermediary object tree structure that sits between the data access interface and the user interface. This object tree acts as a mediator that translates between the generic data access operations and the specific UI requirements, eliminating the need for direct customization between data access and each UI type.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If data access mechanisms are tied to a specific user interface, then integration is achieved, but portability to different interfaces becomes difficult

Engineering Contradiction:
ImproveintegrationVSAvoidportability
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The data access interface is designed to be universal and interface-agnostic by interacting with publisher modules through a standardized object tree. This allows the same data access mechanism to be ported to different user interfaces (Windows forms, web, mobile) without requiring redevelopment, as it doesn't depend on any specific UI framework.

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

Solution Approach 2:

The patent segments the system into distinct layers: the data access interface layer, the object tree layer, and the user interface layer. This segmentation allows the data access mechanism to be independent and portable, while each UI layer can be developed and modified separately without affecting the core data access functionality.

Inventive Principle:
Principle #1Segmentation

3Reliability

If developers manually create and insert objects into the tree, then tree representation is achieved, but time and effort costs increase

Engineering Contradiction:
Improvetree representationVSAvoiddevelopment time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent implements self-service automation where the object tree is automatically generated and populated by the system based on data access requests. Instead of requiring developers to manually create and insert each object, the system automatically builds the tree structure and populates it with relevant data objects, significantly reducing development time and effort.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The system performs preliminary actions by pre-defining the object tree structure and relationships in advance. When a data access request is made, the tree is automatically assembled from pre-configured components, eliminating the need for manual object creation and insertion during development or runtime.

Inventive Principle:
Principle #10Preliminary action

4Reliability

If the entire backend data access is rebuilt when porting to a different user interface, then functionality is maintained, but redevelopment effort increases

Engineering Contradiction:
ImprovefunctionalityVSAvoidredevelopment effort
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The backend data access is designed as a universal interface that doesn't depend on any specific user interface framework. By using a standardized object tree structure and publisher module interaction model, the same backend data access code can serve multiple different UI types (Windows forms, web, mobile) without requiring rebuilding or significant modification.

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

Data Source

PatentUS7783651B2Base tree node infrastructure
Publication Date: 2010.08.24 SAP SE
  • US7783651B2 patent drawing
  • US7783651B2 patent drawing
  • US7783651B2 patent drawing

AI summary

Methods and apparatuses enable generation of a tree structure that integrates the objects of the tree with access interfaces. A tree worker receives an indication of a base node object of a tree, and a list of children related to the base node object. In response to receiving the indication of the base node object and the list of children, the tree worker can generate a tree structure having the object and its related (children) objects.