Attribute Management for Remote Data Sources

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing data-processing systems require manual effort and access to underlying data sources to configure and apply data-processing attributes, which can be time-consuming and impractical, especially when data sources are remote or inaccessible due to security or logistical constraints.

Innovation Solution

A processor-based attribute management application that allows users to define and manage data-processing attributes by creating models of remote data sources, matching these models to exported data, and applying attributes without direct access to the data source, using user interfaces and data services to execute functions on the exported data.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Manufacturing precision

If manual programming is used to configure data-processing attributes, then the attributes can be accurately applied to data sources, but the process becomes time-consuming and expensive

Engineering Contradiction:
Improveaccuracy of data-processing attribute applicationVSAvoidtime required for configuration
Core Design Contradiction:
Manufacturing precisionVSLoss of time

Solution Approach 1:

The system performs preliminary actions by automatically generating data-processing attribute configurations based on user specifications before actual data processing occurs. The attribute management application pre-configures the processing logic, transformation rules, and parameter settings, eliminating the need for time-consuming manual programming while ensuring accurate application to the data source.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system enables self-service by allowing users to directly specify data-processing attributes through the application interface without requiring programmer intervention. The attribute management application automatically translates user requirements into executable configurations, making the system self-sufficient and eliminating the manual programming step entirely.

Inventive Principle:
Principle #25Self-service

2Manufacturing precision

If programmers are given access to remote or inaccessible data sources, then they can accurately code the desired functionality, but security and logistical constraints prevent such access

Engineering Contradiction:
Improveaccuracy of functionality codingVSAvoidaccessibility to data source
Core Design Contradiction:
Manufacturing precisionVSEase of operation

Solution Approach 1:

The attribute management application serves as an intermediary between the user and the remote data source. It receives user specifications for data-processing attributes, automatically generates the appropriate configurations, and applies them to the data source without requiring the user or programmer to directly access the data source. This mediator approach maintains security constraints while enabling accurate functionality implementation.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The system creates a virtual representation or model of the data source and its data-processing attributes. Instead of requiring direct access to the actual remote data source, the application works with copied metadata and attribute definitions that replicate the essential structure and behavior, allowing accurate configuration without physical access to the source system.

Inventive Principle:
Principle #26Copying

Data Source

PatentUS11669503B2Building and managing data-processing attributes for modeled data sources
Publication Date: 2023.06.06 EQUIFAX INC
  • US11669503B2 patent drawing
  • US11669503B2 patent drawing
  • US11669503B2 patent drawing

AI summary

In some aspects, a model of a remote data source is defined. The model includes an entity representing a data segment from the remote data source. The entity has properties, which represent fields of a data structure in the remote data source and have data type descriptors indicating data types used by the fields. The model also includes an attribute specifying a function, which uses the properties as inputs. The entity is matched to exported data from the remote data source, and the exported data is used as input data to the attribute's function.