Virtual Object Mediator for API Data Synchronization

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Maintaining synchronization between local and source data objects is challenging due to differences in naming standards, property formats, and available functionalities when interacting with a source data object via an API.

Innovation Solution

A method and system that utilize a virtual object to associate and translate properties and functions between the local and source objects, allowing users to interact with the source object through a customized interface while ensuring data integrity and security, by using a translation engine and object property builder to map virtual object properties to source object properties and execute corresponding functions.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If a local data object is created based on interaction with a source data object via API, then the local object can be used within the application, but maintaining synchronization with the source object becomes difficult due to different naming standards, property formats, and functionality limitations

Engineering Contradiction:

Improveease of interaction with source objectVSAvoiddata synchronization

Core Design Contradiction:

Ease of operationVSReliability

Solution Approach 1:

The patent introduces a virtual object as an intermediary layer between the local application and the source data object. This virtual object receives operations on local properties and translates them into corresponding operations on the source object's properties, maintaining synchronization without requiring direct interaction between the local and source objects. The virtual object acts as a mediator that handles the complexity of property mapping and translation.

Inventive Principle:

Principle #24Intermediary (Mediator)

2Reliability

If the local data object directly mirrors the source data object's properties, then data integrity is maintained, but the interface becomes complex and exposes unnecessary functionality

Engineering Contradiction:

Improvedata integrityVSAvoidinterface complexity

Core Design Contradiction:

ReliabilityVSDevice complexity

Solution Approach 1:

The patent extracts only the necessary properties and functionality from the source data object into the virtual object's interface. Instead of exposing all source object properties, the virtual object selectively presents a simplified interface with only the properties and operations that the local application needs, while maintaining data integrity through translation to the source object's actual properties.

Inventive Principle:

Principle #2Taking out (Extraction)

Solution Approach 2:

The patent applies different property formats and naming conventions at different levels: the virtual object uses local naming standards suitable for the application, while the source object maintains its original format. The translation layer handles the conversion between these different 'local qualities' of property representation.

Inventive Principle:

Principle #3Local quality

3Adaptability or versatility

If all properties and functionality of the source data object are exposed in the local data object, then complete functionality is available, but security risks increase and unnecessary functionality is exposed

Engineering Contradiction:

Improvefunctionality availabilityVSAvoidsecurity risks

Core Design Contradiction:

Adaptability or versatilityVSObject-affected harmful factors

Solution Approach 1:

The virtual object serves as a security intermediary that controls and filters access to the source data object. It exposes only the functionality that should be available to the local application while blocking access to sensitive or unnecessary operations. The translation layer validates and controls all interactions, reducing security risks.

Inventive Principle:

Principle #24Intermediary (Mediator)

4Ease of operation

If the local data object uses different naming standards and property formats than the source object, then the interface is optimized for the application, but synchronization and translation become difficult

Engineering Contradiction:

Improveinterface optimizationVSAvoidtranslation complexity

Core Design Contradiction:

Ease of operationVSDevice complexity

Solution Approach 1:

The virtual object acts as a translation intermediary that handles the conversion between local naming standards and source object property formats. The system defines a set of functions that perform the actual translation and mapping between different property representations, managing the complexity of format conversion.

Inventive Principle:

Principle #24Intermediary (Mediator)

Data Source

PatentUS10678608B2Interacting with a source object via a virtual object

Publication Date: 2020.06.09 RED HAT ISRAEL

AI summary

An example method of interacting with a source object via a virtual object, the method includes associating a first set of properties of a virtual object with a second set of properties of a source object that is defined in a program. The method also includes defining a set of functions corresponding to the associated first and second sets of properties and receiving a first request to instantiate the virtual object. The source object is instantiated in response to the first request. The method further includes receiving a second request to perform an operation using the first set of properties of the virtual object and executing the set of functions in response to the second request. The method also includes updating the second set of properties of the source object in accordance with a result of the executed set of functions.