OLAP Engine Dynamic Result Set Structure Memory References

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional OLAP systems face inefficiencies due to repeated data copying and transformation across software layers, which occupy computer memory and dominate query execution time.

Innovation Solution

An OLAP engine system that receives a dynamic result set structure from an application layer, enhances raw data from a database based on this structure, and passes references to memory locations for data elements, eliminating the need for data copying and transformation between layers.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If data is copied and transformed between software layers in conventional OLAP systems, then each layer can process data in its proprietary format, but memory occupation increases and query execution time increases

Engineering Contradiction:
Improvelayer compatibilityVSAvoidquery execution time
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

The patent uses references (pointers) to copy data locations rather than copying actual data. When data needs to be accessed across layers, instead of physically copying the data between layers, the system creates reference pointers that point to the original data location. This allows multiple layers to access the same data without duplicating it in memory, thereby maintaining layer compatibility while significantly reducing memory occupation and query execution time.

Inventive Principle:
Principle #26Copying

Solution Approach 2:

The patent introduces a data reference mechanism as an intermediary between software layers. This reference system acts as a mediator that allows different layers with proprietary formats to access and share data without direct copying. The reference mechanism translates between different layer requirements while pointing to the underlying data, enabling adaptability across layers without the performance penalty of repeated data transformation and copying.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Adaptability or versatility

If data is copied and transformed between software layers in conventional OLAP systems, then each layer can process data in its proprietary format, but memory occupation increases

Engineering Contradiction:
Improvelayer compatibilityVSAvoidmemory occupation
Core Design Contradiction:
Adaptability or versatilityVSQuantity of substance

Solution Approach 1:

The patent uses references (pointers) to copy data locations rather than copying actual data. When data needs to be accessed across layers, instead of physically copying the data between layers, the system creates reference pointers that point to the original data location. This allows multiple layers to access the same data without duplicating it in memory, thereby maintaining layer compatibility while significantly reducing memory occupation and query execution time.

Inventive Principle:
Principle #26Copying

3Adaptability or versatility

If data is repeatedly transformed across layers, then proprietary formats are supported, but processing speed decreases

Engineering Contradiction:
Improveformat flexibilityVSAvoidprocessing speed
Core Design Contradiction:
Adaptability or versatilityVSProductivity

Solution Approach 1:

The patent uses references (pointers) to copy data locations rather than copying actual data. When data needs to be accessed across layers, instead of physically copying the data between layers, the system creates reference pointers that point to the original data location. This allows multiple layers to access the same data without duplicating it in memory, thereby maintaining layer compatibility while significantly reducing memory occupation and query execution time.

Inventive Principle:
Principle #26Copying

Solution Approach 2:

The patent performs data enhancement and transformation only once at the source layer before data is accessed by other layers. By preprocessing and enhancing the data in its original location, the system eliminates the need for repeated transformations when other layers access the data through references. This preliminary action maintains format flexibility while dramatically improving processing speed by avoiding redundant transformation operations.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS9031900B2System and methods for integrating software layers for OLAP
Publication Date: 2015.05.12 SAP SE
  • US9031900B2 patent drawing
  • US9031900B2 patent drawing
  • US9031900B2 patent drawing

AI summary

In accordance with aspects of the disclosure, a system and methods may be provided for integrating software layers in OLAP including receiving, at an OLAP engine, a dynamic result set structure passed from an application layer via one or more other software layers. The dynamic result set structure may include a description of entities for a target layer. The system and methods may include enhancing raw data, at the OLAP engine, acquired from a database associated with a source layer based on the description of entities for the dynamic result set structure and passing one or more references to one or more memory locations for data elements in the dynamic result set structure from the OLAP engine to the application layer via the one or more other software layers for acquiring each data element associated with each corresponding reference in the dynamic result set structure.