Local Message Builder for Enterprise Software Protocol Compatibility

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Enterprise software applications face challenges in communicating across incompatible systems without relying on costly and complex exchange systems, which are typically required for message protocol compatibility.

Innovation Solution

A local system configured to build and send messages according to a specific message protocol, using stored configuration data that includes technical and logical addressing information, authentication data, and interface mappings, enabling point-to-point connectivity without the need for an exchange system.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If an exchange system is used to facilitate communication between incompatible enterprise software applications, then message protocol compatibility is achieved, but system complexity and cost increase

Engineering Contradiction:
Improvemessage protocol compatibilityVSAvoidsystem complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent extracts the message building functionality from the centralized exchange system and implements it locally at each enterprise software application. Each application independently builds messages using stored configuration data, eliminating the need for a complex exchange system while maintaining protocol compatibility.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

Each enterprise software application serves itself by locally storing and using configuration data to build messages according to the required protocol. The system is self-sufficient and does not require external exchange system infrastructure to achieve message compatibility.

Inventive Principle:
Principle #25Self-service

2Adaptability or versatility

If an exchange system is deployed to enable communication between enterprise software applications, then interoperability is improved, but implementation cost increases

Engineering Contradiction:
ImproveinteroperabilityVSAvoidimplementation cost
Core Design Contradiction:
Adaptability or versatilityVSEase of manufacture

Solution Approach 1:

The patent removes the expensive exchange system infrastructure and extracts only the essential message building capability, which is implemented locally using lightweight configuration data storage and processing.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The patent uses simple, inexpensive configuration data structures that can be easily stored and processed locally, replacing the need for expensive, complex exchange system infrastructure while achieving the same interoperability goal.

Inventive Principle:
Principle #27Cheap short-living objects (Disposable)

3Stability of the object's composition

If message building is centralized in an exchange system, then protocol standardization is achieved, but system simplicity is reduced

Engineering Contradiction:
Improveprotocol standardizationVSAvoidsystem simplicity
Core Design Contradiction:
Stability of the object's compositionVSDevice complexity

Solution Approach 1:

The patent segments the message building process from the centralized exchange system and distributes it to individual enterprise software applications. Each application independently builds messages using local configuration data, maintaining protocol standardization while simplifying the overall system architecture.

Inventive Principle:
Principle #1Segmentation

Data Source

PatentEP2669802B1Facilitating communication between enterprise software applications
Publication Date: 2019.07.03 SAP SE
  • EP2669802B1 patent drawingFigure 1
  • EP2669802B1 patent drawingFigure 2
  • EP2669802B1 patent drawingFigure 3

AI summary

Methods, systems, and apparatus, including computer programs encoded on a computer storage medium, for facilitating communication between enterprise software applications. Some enterprise software systems communicate using a message protocol designed for use with an exchange system. Those systems require the exchange system to communicate using that message protocol. To communicate with systems using that message protocol, a local system can build a message formatted in accordance with the message protocol, even without an exchange system. The local system stores configuration data and uses the configuration data to build the message.