Centralized Application Message Processing Framework

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing application integration technologies are not optimally suited for organizations with numerous orchestrations and resource limitations, leading to costly and complex communication challenges between disparate applications, requiring frequent redesign and recompilation to accommodate changing requirements.

Innovation Solution

A centralized application message processing framework with hops (entry, intermediate, and exit) that process and route messages between applications, allowing designated services to be invoked and metrics to be cataloged, reducing the need for individual application updates and conserving resources.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If code redesign is used to enable communication between applications, then communication capability is improved, but development cost and complexity increase significantly as the number of applications grows

Engineering Contradiction:
Improvecommunication capabilityVSAvoidintegration complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent introduces an application message processing framework that acts as an intermediary between disparate applications. This framework provides standardized message routing, transformation, and processing capabilities, eliminating the need for direct code redesign between each application pair. The framework mediates communication by handling message format conversion, routing decisions, and protocol adaptation centrally, thereby reducing overall integration complexity while maintaining communication capability.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The application message processing framework is designed as a universal system that can handle multiple types of applications and message formats simultaneously. It provides multi-functional capabilities including message routing, transformation, validation, and error handling that can serve any number of applications through a single standardized interface, rather than requiring application-specific integration code for each communication scenario.

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

2Adaptability or versatility

If individual application code is redesigned to accommodate changing requirements, then adaptability to new requirements is improved, but resource consumption and maintenance burden increase exponentially

Engineering Contradiction:
Improverequirements adaptabilityVSAvoidresource consumption
Core Design Contradiction:
Adaptability or versatilityVSLoss of energy

Solution Approach 1:

The patent extracts the integration and message processing logic from individual application codebases and places it into a separate, dedicated message processing framework. This extraction allows application code to remain stable and unchanged while the framework handles all adaptation to new requirements. When requirements change, only the framework needs to be updated, not the individual applications, thereby reducing resource consumption and maintenance burden.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The message processing framework is designed with dynamic configuration capabilities, allowing routing rules, message formats, and processing logic to be modified without recompiling application code. The framework can dynamically adapt to changing requirements through configuration changes, hot reloading, or runtime updates, enabling requirements adaptability while preserving application stability and reducing resource-intensive recompilation cycles.

Inventive Principle:
Principle #15Dynamics

3Stability of the object's composition

If centralized system integration is implemented to consolidate multiple applications, then system coherence is improved, but initial setup complexity and storage requirements increase

Engineering Contradiction:
Improvesystem coherenceVSAvoidintegration architecture
Core Design Contradiction:
Stability of the object's compositionVSDevice complexity

Solution Approach 1:

The patent segments the integration architecture into distinct, modular components including message producers, message consumers, message routes, and message processors. Each component has a specific, well-defined responsibility, allowing the centralized system to achieve coherence through standardized interfaces while maintaining low individual component complexity. This segmentation enables independent development, testing, and deployment of each segment, reducing overall architecture complexity.

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS10037235B2Integrating applications
Publication Date: 2018.07.31 WALMART APOLLO LLC
  • US10037235B2 patent drawing
  • US10037235B2 patent drawing
  • US10037235B2 patent drawing

AI summary

The present disclosure extends to methods, systems, and computer program products for integrating applications. In general, aspects of the invention can be used to reduce complexities associated with integrating applications and conserve computer system resources. Designed message processing functionality as well as updates and changes can be maintained through a centralized application message processing framework and then used by a plurality of applications. The centralized application message processing framework significantly reduces, and potentially eliminates, the need to incorporate message processing functionality individually into each of the plurality of applications. This in turn reduces the burden and complexity of maintaining message processing functionality for the plurality of applications.