Dynamic Protocol Conversion for SIP-SOAP Interoperability

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Current communication systems lack efficient methods for dynamic and multi-way conversion and coordination between Session Initiation Protocol (SIP) and Simple Object Access Protocol (SOAP) messages, limiting the ability to create converged applications that can adapt to changing requirements and support simultaneous management of multiple SIP-SOAP convergent applications.

Innovation Solution

A system and method that utilize a Protocol Conversion and Coordination Language (PCCL) to dynamically convert and coordinate SIP and SOAP messages, including a message receiver, session correlator, condition matcher, action executor, and message sender, which specify conversion rules to map messages to sessions and execute actions, enabling seamless communication between SIP and SOAP protocols.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If existing SIP to SOAP gateway solutions are used, then unidirectional message conversion is achieved, but multi-way dynamic coordination and adaptability to changing requirements are lost

Engineering Contradiction:

Improvedynamic adaptability to changing requirementsVSAvoidsystem complexity for multi-way coordination

Core Design Contradiction:

Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The system employs dynamic rule sets that can be modified at runtime to adapt to changing conversion requirements. The session correlator dynamically creates and manages session contexts, and the rule engine dynamically selects and applies appropriate conversion rules based on current message types and session states, enabling the system to adapt without reconfiguration.

Inventive Principle:

Principle #15Dynamics

Solution Approach 2:

The conversion system is segmented into independent functional modules: message receiver, session correlator, rule engine, action executor, and message sender. Each module handles specific aspects of the conversion process, allowing independent modification and management of conversion rules for different protocol pairs (SIP-SOAP, SOAP-SIP, H.323-SIP) without affecting the entire system.

Inventive Principle:

Principle #1Segmentation

2Adaptability or versatility

If multiple protocol conversion rules are maintained, then support for multiple convergent applications is achieved, but management complexity and resource consumption increase

Engineering Contradiction:

Improvesupport for multiple convergent applicationsVSAvoidcomplexity of managing conversion rules

Core Design Contradiction:

Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The system implements a universal session correlator that manages multiple protocol sessions simultaneously using a unified rule set framework. The same core infrastructure handles SIP-SOAP, SOAP-SIP, and H.323-SIP conversions, with protocol-specific details encapsulated in separate rule sets that are loaded and managed uniformly by the session correlator.

Inventive Principle:

Principle #6Universality (Multi-functionality)

Solution Approach 2:

The session correlator acts as an intermediary layer between the message receiver and the rule engine, normalizing incoming messages from different protocols into a unified internal representation. This intermediary layer abstracts the complexity of multiple protocol rules, allowing the system to manage diverse protocol conversions through a single coordinated interface.

Inventive Principle:

Principle #24Intermediary (Mediator)

3Reliability

If dynamic rule sets are implemented, then controlled coordination between multiple message types is achieved, but processing overhead and conversion time increase

Engineering Contradiction:

Improvecontrolled coordination accuracyVSAvoidmessage conversion time

Core Design Contradiction:

ReliabilityVSLoss of time

Solution Approach 1:

Conversion rules are pre-compiled and validated before runtime execution. The session correlator pre-establishes session contexts and pre-loads applicable rule sets when sessions are created, so that during actual message conversion, the system only needs to match messages against preprocessed rules rather than interpreting raw conversion logic in real-time.

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The system replaces complex mechanical rule interpretation with automated pattern matching algorithms. The rule engine uses structured pattern templates to quickly match incoming messages against predefined conversion patterns, substituting manual rule analysis with efficient algorithmic matching that reduces processing time while maintaining coordination accuracy.

Inventive Principle:

Principle #28Mechanics substitution (Replace mechanical system)

Data Source

PatentUS8850069B2Systems and methods for dynamically adaptive multi-way message conversion

Publication Date: 2014.09.30 TELEFONAKTIEBOLAGET LM ERICSSON (PUBL)

AI summary

Multilateral, dynamic and coordinated message conversion between different messages composed using different protocols, e.g., Session Initiation Protocol (SIP) and Simple Object Access Protocol (SOAP) are described. For each message pattern or set of messages between coordinated peers, a conversion session is established. Incoming messages are correlated to their respective conversion sessions so that a common set of conversion rules can be used to convert messages within a particular session.