Objects Comparison Manager for Data Variation Detection

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

When users modify data stored on a system, saving the entire copy can consume significant resources, especially for large datasets, as only small portions of the data may have changed, leading to unnecessary processor and memory usage.

Innovation Solution

The Objects Comparison Manager (OCM) compares modified and saved objects to determine the specific changes and saves only those variations to disk storage, rather than the entire object, using default and user-defined comparison logic based on object schemas and functions to efficiently manage user-defined objects.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If the entire copy of data is saved to disk storage, then data integrity is ensured, but processor cycles and memory are unnecessarily consumed

Engineering Contradiction:
Improvedata integrityVSAvoidprocessor efficiency
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent segments the data saving process by comparing the modified object against the saved object to identify and save only the specific portions that have changed, rather than saving the entire object. This segmentation allows the system to maintain data integrity for changed portions while avoiding unnecessary processing of unchanged data.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent extracts only the varied portions between the modified object and the saved object using comparison logic. By taking out and saving only these specific changed portions rather than the entire object, the system reduces processor cycles and memory consumption while ensuring integrity of the modified data.

Inventive Principle:
Principle #2Taking out (Extraction)

2Reliability

If the entire copy of large data is saved, then all changes are captured, but significant computing resources are wasted on unchanged data

Engineering Contradiction:
Improvechange capture completenessVSAvoidcomputing resource consumption
Core Design Contradiction:
ReliabilityVSLoss of energy

Solution Approach 1:

The patent applies partial action by saving only the necessary changed portions of the object rather than the entire object. The comparison logic identifies which specific portions have changed, and only those portions are saved, avoiding the excessive action of processing and saving all data including unchanged portions.

Inventive Principle:
Principle #16Partial or excessive action

Solution Approach 2:

The patent changes the parameter of what is being saved from the entire object to only the varied portions. By using comparison logic to identify changes, the system transforms the saving operation from a full-object operation to a selective portion operation, reducing computing resource consumption.

Inventive Principle:
Principle #35Parameter changes

3Ease of manufacture

If default comparison logic is used for all objects, then implementation is simple, but user-defined comparison requirements cannot be met

Engineering Contradiction:
Improveimplementation simplicityVSAvoidcomparison logic flexibility
Core Design Contradiction:
Ease of manufactureVSAdaptability or versatility

Solution Approach 1:

The patent creates a universal comparison manager that can handle both default comparison logic and user-defined comparison logic. The system is designed to be multi-functional, supporting built-in comparison methods for common scenarios while also allowing users to provide custom comparison logic for specialized requirements, thus achieving both simplicity and flexibility.

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

Solution Approach 2:

The comparison manager acts as an intermediary between the saving operation and the comparison logic. It can invoke either default comparison logic or user-provided comparison logic as needed, mediating between the simple implementation of default logic and the adaptability of user-defined logic.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS10558639B2Objects comparison manager
Publication Date: 2020.02.11 SAP SE
  • US10558639B2 patent drawing
  • US10558639B2 patent drawing
  • US10558639B2 patent drawing

AI summary

Disclosed herein are system, method, and computer program product embodiments for objects comparison manager. An embodiment operates by receiving a request to compare two versions of an object, including a saved version of the object and a modified version of the object. A user-defined schema for the object is determined. The two versions of the object are compared based on the user-defined schema. As a result of the comparison, a variation between the modified version and the saved version of the object is determined. The variation between the two versions of the object is saved.