Test Data Request Routing Across Domains With API Mediation

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Current systems lack a holistic application programming interface (API) that allows any line of business (LOB) to request data for software testing across multiple domains, leading to complexity, configuration challenges, and limited inner sourcing opportunities due to domain-specific knowledge requirements and API changes over time.

Innovation Solution

A computing system that routes test data requests through appropriate function application program interfaces (FAPIs) using an inventory database and request router, enabling automatic data acquisition and storage without requiring domain knowledge, and maintaining an inventory of non-stale data to reduce redundant processing and resource usage.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If a holistic API is implemented to allow any LOB to request data from any data domain, then data accessibility and versatility are improved, but device complexity and configuration difficulty increase significantly

Engineering Contradiction:

Improvedata accessibilityVSAvoidAPI complexity

Core Design Contradiction:

Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent introduces an intermediary system comprising an inventory database and request router that mediates between LOBs and data domains. This intermediary layer handles the complexity of data routing, transformation, and orchestration, allowing LOBs to access data from any domain through a simplified interface without directly managing the underlying complexity of multiple data sources and transformations.

Inventive Principle:

Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent creates a universal data access framework that enables a single API interface to serve multiple LOBs and access multiple data domains. This universal system performs multiple functions including data retrieval, transformation, routing, and inventory management through a unified architecture, eliminating the need for separate domain-specific APIs and reducing overall system complexity.

Inventive Principle:

Principle #6Universality (Multi-functionality)

2Reliability

If domain knowledge is embedded in the API to add intelligence and orchestration, then data acquisition accuracy is improved, but ease of operation deteriorates due to knowledge requirements

Engineering Contradiction:

Improvedata acquisition accuracyVSAvoidoperational simplicity

Core Design Contradiction:

ReliabilityVSEase of operation

Solution Approach 1:

The patent implements a self-service system where the request router and inventory database automatically determine the appropriate data sources, transformations, and routing paths without requiring user domain knowledge. The system autonomously orchestrates data acquisition by matching requests with available data inventories and executing appropriate transformations, eliminating the need for users to possess specialized domain expertise while maintaining high data acquisition accuracy.

Inventive Principle:

Principle #25Self-service

3Adaptability or versatility

If the API is configured to handle multiple LOBs and data domains, then versatility is improved, but ease of manufacture and configuration deteriorate

Engineering Contradiction:

Improvemulti-LOB supportVSAvoidconfiguration ease

Core Design Contradiction:

Adaptability or versatilityVSEase of manufacture

Solution Approach 1:

The patent implements preliminary action by pre-configuring an inventory database that catalogs available data from multiple domains and pre-establishing transformation rules and routing logic. This upfront configuration creates a reusable framework that can serve multiple LOBs without requiring complex per-LOB configuration, as the system is pre-adapted to handle various data domains and transformation requirements through standardized inventory entries and routing templates.

Inventive Principle:

Principle #10Preliminary action

4Reliability

If manual domain expertise is required for data acquisition, then data accuracy is improved, but productivity deteriorates due to manual intervention

Engineering Contradiction:

Improvedata accuracyVSAvoiddata acquisition speed

Core Design Contradiction:

ReliabilityVSProductivity

Solution Approach 1:

The patent replaces the manual mechanical process of domain expert intervention with an automated computational system comprising request routers, inventory databases, and transformation engines. This automated system maintains data accuracy by applying predefined transformation rules and validation logic while dramatically increasing productivity through automated data acquisition, elimination of manual review steps, and parallel processing of multiple requests simultaneously.

Inventive Principle:

Principle #28Mechanics substitution (Replace mechanical system)

Data Source

PatentUS12567030B1Test data acquisition framework

Publication Date: 2026.03.03 THE TRAVELERS INDEMNITY

AI summary

A method, a computing system, and a non-transitory computer-readable storage medium are provided for satisfying a request for test data. A computing system receives a request for test data. Responsive to determining that information related to the test data does not exist in an inventory database, a number of operations are performed. According to the operations, when at least one function application program interface exists for satisfying the request, the computing system routes the request to one or more appropriate processors executing one or more appropriate function application program interfaces. The one or more appropriate processors execute the at least one function application program interface to satisfy the request. The computing system notifies an originator of the request that the request for the test data is successfully completed.