Content Integration Framework for Streaming Data

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current data integration systems for streaming data lack flexibility and standardization, requiring developers to implement complex logic for content acquisition and transformation, leading to high development costs and maintenance challenges, especially in financial services where rapid data integration is critical for competitive advantage.

Innovation Solution

A system and method for integrating streaming and static data using a Content Integration Framework that provides flexible transformation, standards-based interfaces, and domain-specific implementations of the JMS messaging paradigm, enabling rapid acquisition, transformation, and distribution of data, as well as load balancing and scalability.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of manufacture

If developers implement complex logic for content acquisition and transformation in current streaming data integration systems, then data integration functionality is achieved, but development costs and maintenance complexity increase significantly

Engineering Contradiction:
Improveease of data integrationVSAvoiddevelopment complexity
Core Design Contradiction:
Ease of manufactureVSDevice complexity

Solution Approach 1:

The patent introduces an integration server as an intermediary component between data sources and client applications. This server implements content acquisition, transformation, and distribution logic centrally, eliminating the need for developers to implement complex integration logic in their applications. The server acts as a mediator that handles all data integration complexities while providing simple standardized interfaces to clients.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent extracts integration logic from client applications and concentrates it in a dedicated integration server. By taking out the complex content acquisition and transformation logic from distributed client code and centralizing it in the server, the system reduces development complexity for individual applications while maintaining comprehensive data integration capabilities.

Inventive Principle:
Principle #2Taking out (Extraction)

2Ease of operation

If proprietary APIs are used to simplify developer tasks in streaming data integration, then implementation ease improves, but system maintainability and platform compatibility deteriorate

Engineering Contradiction:
Improveease of implementationVSAvoidplatform compatibility
Core Design Contradiction:
Ease of operationVSAdaptability or versatility

Solution Approach 1:

The patent implements a universal integration server that can work with multiple data sources and client applications across different platforms. The server provides standardized interfaces and protocols that are platform-independent, allowing the same integration logic to serve multiple purposes and platforms without requiring proprietary API implementations for each case.

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

Solution Approach 2:

The patent uses configurable parameters and metadata to adapt the integration behavior to different data sources and clients without changing the core system architecture. By parameterizing the integration logic rather than hardcoding proprietary APIs, the system maintains ease of implementation while achieving broad platform compatibility and adaptability.

Inventive Principle:
Principle #35Parameter changes

3Adaptability or versatility

If logic is placed on the client side in current integration systems, then flexibility is maintained, but development costs and long-term risks increase

Engineering Contradiction:
Improvesystem flexibilityVSAvoidlong-term stability
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The integration server serves as a stable intermediary that maintains system flexibility through configurable parameters while providing long-term reliability through centralized, maintained logic. The server absorbs the complexity and risk of integration logic maintenance, allowing client applications to remain simple and stable over time while still adapting to different data sources through server-side configuration.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS8281026B2System and method for integration of streaming and static data
Publication Date: 2012.10.02 METAFLUENT LLC
  • US8281026B2 patent drawing
  • US8281026B2 patent drawing
  • US8281026B2 patent drawing

AI summary

The invention relates to integration of streaming data. The invention provides a means for integrating both high-throughput streaming and static content originating from multiple types and/or instances of data sources into discrete units of data. The invention provides integration of a wide variety of disparate streaming and static data sources as well as deployment of content in multiple protocols, either static or streaming or both. In the preferred embodiment, the invention provides a method and system for the insertion of domain-specific implementations of the JMS (Java Message System) messaging paradigm into a server-based JMS provider infrastructure. A Content Integration Framework provides access to Content Instances. The Content Integration Framework is used by Distribution Adapters that expose content from Content Instances cached in the system using a variety of protocols.