Service Request Processing with Data Normalization

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The complexity of acquiring data from diverse and dynamic data repositories, coupled with the lack of standardization and scalability, hampers efficient data extraction and processing, particularly in cloud computing models like Data-as-a-Service (DaaS), leading to challenges in real-time data access and handling large volumes of data.

Innovation Solution

A system with a processing arrangement and an administrator module that identifies attributes of service requests, normalizes data from multiple data sources, and provides it in a format suitable for execution, enabling scalable and concurrent data extraction and processing without requiring extensive human intervention or altering sub-routines for each data source.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If specialized query language is used to access data repositories, then data extraction capability is improved, but system complexity and development time increase

Engineering Contradiction:
Improvedata extraction capabilityVSAvoidsystem complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent introduces an intermediary layer (processing arrangement with administrator module) between the service request and the diverse data repositories. This intermediary automatically translates service requests into repository-specific queries and normalizes the returned data, eliminating the need for specialized query languages at the application level while maintaining extraction capability.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The system segments the data access functionality into independent, standardized components. The processing arrangement handles translation and normalization as separate functions, allowing the core application logic to remain simple while complex data extraction tasks are handled by dedicated modules.

Inventive Principle:
Principle #1Segmentation

2Manufacturing precision

If sub-routines are tailored for each data repository, then data acquisition quality is improved, but development time and human intervention increase

Engineering Contradiction:
Improvedata acquisition qualityVSAvoiddevelopment time
Core Design Contradiction:
Manufacturing precisionVSLoss of time

Solution Approach 1:

The processing arrangement is designed as a universal component that can handle multiple types of data repositories through automatic translation and normalization. A single processing arrangement can serve diverse data sources without requiring custom sub-routines for each repository, maintaining data acquisition quality through standardized processes.

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

3Stability of the object's composition

If data repositories are centralized, then data structure control is improved, but scalability and elasticity decrease

Engineering Contradiction:
Improvedata structure controlVSAvoidscalability
Core Design Contradiction:
Stability of the object's compositionVSAdaptability or versatility

Solution Approach 1:

The processing arrangement acts as an intermediary that enables centralized control of data structure through normalization while allowing distributed data repositories to maintain their independence. The normalization process ensures consistent data structure control without requiring physical centralization of the repositories.

Inventive Principle:
Principle #24Intermediary (Mediator)

4Speed

If real-time data processing is implemented, then service response time is improved, but computational complexity increases

Engineering Contradiction:
Improveservice response timeVSAvoidcomputational complexity
Core Design Contradiction:
SpeedVSDevice complexity

Solution Approach 1:

The system performs preliminary actions by pre-establishing translation rules and normalization schemas for different data repositories. When service requests arrive in real-time, the processing arrangement can quickly translate and normalize data without complex computational overhead, improving response time while managing complexity through advance preparation.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS11954111B2System and method for executing service request
Publication Date: 2024.04.09 INNOPLEXUS AG
  • US11954111B2 patent drawing
  • US11954111B2 patent drawing

AI summary

Disclosed is system for executing service request. The system comprises a processing arrangement and data sources. The processing arrangement receives the service request and is configured to extract data from the data sources based on the service request. The data sources respond in response to a characteristic framework of the service request. The system further comprises an administrator module to permute the service request received by the processing arrangement in accordance with the characteristic framework employed by the data sources. The administrator module is configured to identify at least one attribute of the service request, obtain data corresponding to the at least one attribute of the service request from the data sources, normalize the obtained data and provide the normalized data to execute the service request, via the processing arrangement.