Policy-Based Message Aggregation Framework for Enterprise Integration

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The complexity and cost associated with integrating various message formats in business enterprises for computer-to-computer communication lead to inefficiencies, as existing solutions require custom software and are not scalable for diverse communication needs.

Innovation Solution

An extensible, policy-based message aggregation framework that batches multiple messages into a single output stream, allowing for efficient transmission based on business logic and reducing overhead costs by optimizing communication timing.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If custom software solutions are used to aggregate messages, then message aggregation functionality is achieved, but system complexity and cost increase

Engineering Contradiction:
Improvemessage aggregation efficiencyVSAvoidsoftware complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The patent implements a universal message aggregation framework that handles multiple message formats (XML, EDI, Flat File, SWIFT, HL7) through a single platform. The framework uses configurable aggregators that can process different message types without requiring custom software for each format, thereby achieving message aggregation efficiency while avoiding the complexity of multiple specialized solutions

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

Solution Approach 2:

The framework uses configurable parameters and policies to define aggregation behavior. Instead of hardcoding aggregation logic for different message types, the system allows parameter changes in aggregation policies to adapt to different message formats and business requirements. This parameter-driven approach reduces software complexity while maintaining high productivity across diverse messaging scenarios

Inventive Principle:
Principle #35Parameter changes

2Reliability

If messages are transmitted individually, then communication reliability is maintained, but transmission costs and overhead increase

Engineering Contradiction:
Improvecommunication reliabilityVSAvoidtransmission cost
Core Design Contradiction:
ReliabilityVSLoss of energy

Solution Approach 1:

The patent merges multiple individual messages into aggregated batches that are transmitted together as a single unit. The aggregation framework combines messages from multiple sources or of the same type into batches, reducing the number of separate transmission operations. This merging approach maintains communication reliability through consistent batch processing while significantly reducing transmission costs and overhead associated with individual message sends

Inventive Principle:
Principle #5Merging (Combining)

3Adaptability or versatility

If multiple message formats are supported, then adaptability to different partners is improved, but system complexity increases

Engineering Contradiction:
Improvemessage format compatibilityVSAvoidintegration complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The framework introduces configurable aggregators as intermediary components that mediate between different message formats and the transmission system. Each aggregator acts as a specialized handler for specific message types (XML, EDI, SWIFT, HL7), translating and preparing messages for aggregation without requiring the core system to understand all formats directly. This intermediary approach improves adaptability to various partners while managing complexity through modular, configurable components

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS7890955B2Policy based message aggregation framework
Publication Date: 2011.02.15 MICROSOFT TECHNOLOGY LICENSING LLC
  • US7890955B2 patent drawing
  • US7890955B2 patent drawing
  • US7890955B2 patent drawing

AI summary

Messages generated by an originating application are aggregated into batches based on a configuration policy. The configuration policy contains business logic used to aggregate messages into a batch. Once a batch is complete, it is formatted into a single stream output and sent to a destination application designed to receive the messages. Messages may also be aggregated into batches that are controlled by the originating application. The messages include an indicator set by the originating application to signal when a batch is complete. Once the batch is complete, it is formatted into a single stream output and sent to a destination application designed to receive the messages.