Message Hub Protocol Adaptation for Messaging System Compatibility

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Hub-based messaging systems face challenges in compatibility and downtime during software upgrades due to differing protocol versions between sender and receiver systems, leading to inoperable messaging systems and loss of messages.

Innovation Solution

Implementing a downwards compatible messaging system where message hubs can route messages using the lower or equal protocol version, allowing flexible upgrades without requiring simultaneous system-wide updates, and enabling processing of stored messages post-upgrade.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If a hub-based messaging system uses a single protocol version across all components, then system compatibility is maintained, but system flexibility and upgrade capability are reduced

Engineering Contradiction:
Improveupgrade capabilityVSAvoidsystem compatibility
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The message hub dynamically adjusts the protocol version used for communication based on the capabilities of the communicating party. The hub maintains multiple protocol version capabilities and selects the appropriate version dynamically, allowing the system to adapt to different upgrade states of sender and receiver systems while maintaining compatibility.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The system changes the protocol version parameter based on the communication context. The message hub stores multiple protocol version capabilities and selects the appropriate version for each communication instance, enabling flexible upgrades while maintaining backward compatibility with older system versions.

Inventive Principle:
Principle #35Parameter changes

2Reliability

If the messaging system requires simultaneous system-wide updates, then protocol compatibility is ensured, but system downtime increases

Engineering Contradiction:
Improveprotocol compatibilityVSAvoidsystem downtime
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The messaging system is segmented into independent components (sender system, message hub, receiver system) that can be upgraded independently. The message hub acts as an intermediary that can handle multiple protocol versions, allowing individual components to be upgraded without requiring simultaneous system-wide updates, thus minimizing downtime.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The message hub serves as an intermediary between sender and receiver systems, maintaining multiple protocol version capabilities. This intermediary role allows the hub to translate between different protocol versions, enabling independent upgrades of sender and receiver systems without requiring simultaneous updates, thereby reducing system downtime.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Adaptability or versatility

If message hubs support multiple protocol versions, then upgrade flexibility increases, but system complexity increases

Engineering Contradiction:
Improveupgrade flexibilityVSAvoidsystem complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The message hub is designed with multi-functionality to handle multiple protocol versions. By consolidating the capability to understand and process multiple protocol versions within a single hub component, the system achieves upgrade flexibility without proportionally increasing overall system complexity. The hub acts as a universal intermediary that can adapt to different protocol versions.

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

Data Source

PatentUS7573901B2Hub-based messaging system
Publication Date: 2009.08.11 SAP SE
  • US7573901B2 patent drawing
  • US7573901B2 patent drawing
  • US7573901B2 patent drawing

AI summary

A messaging system may include a sender backend system, a receiver backend system, and one or more intermediate hubs. The backend systems and message hubs may have messaging software with different protocol versions. The messaging system is downward compatible such that messages routed from the sender backend system through intermediate message hubs are received by the receiver backend system with a protocol version compatible with that of the receiver backend system.