Bridge Server Cross-Domain UCC Protocol Translation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Communications systems face limitations when trying to facilitate seamless interactions across incompatible Unified Communications and Collaboration (UCC) platforms, requiring a solution to enable cross-domain communication with a single user identifier.

Innovation Solution

A cross-domain system utilizing a bridge server and media gateway to manage notifications and media handling, allowing a single user identifier to be registered across multiple platforms, enabling communication sessions across incompatible platforms by converting protocols and signaling messages.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If a single user identifier is registered across multiple incompatible UCC platforms, then cross-platform communication capability is improved, but system complexity increases due to protocol conversion requirements

Engineering Contradiction:
Improvecross-platform communication capabilityVSAvoidsystem complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent introduces a gateway server as an intermediary component that mediates between incompatible UCC platforms. The gateway server receives signaling messages from one platform, converts them to the appropriate protocol format, and forwards them to the target platform. This intermediary approach enables cross-platform communication without requiring changes to the existing UCC platforms, thereby improving adaptability while managing system complexity through a dedicated conversion component.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Adaptability or versatility

If protocol conversion is implemented to enable cross-platform communication, then compatibility across UCC platforms is improved, but processing time increases due to message transformation operations

Engineering Contradiction:
Improveplatform compatibilityVSAvoidprocessing time
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

The gateway server performs protocol conversion in advance by maintaining translation rules and mapping relationships between different UCC protocols. When a signaling message arrives, the gateway already has the necessary conversion logic prepared, allowing it to rapidly transform messages without extensive real-time processing. This preliminary preparation of conversion rules reduces the actual processing time during message transformation operations.

Inventive Principle:
Principle #10Preliminary action

3Adaptability or versatility

If existing UCC servers are modified to support cross-domain communication, then integration capability is improved, but system stability deteriorates due to changes in proven systems

Engineering Contradiction:
Improveintegration capabilityVSAvoidsystem stability
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The patent segments the cross-platform communication functionality into a separate gateway server component, distinct from the existing UCC platforms. This segmentation allows the gateway to handle all protocol conversion and cross-domain communication tasks independently, while the original UCC servers continue to operate unchanged. By isolating the integration logic in a dedicated gateway, the system maintains the stability of proven UCC servers while achieving enhanced integration capability through the separate gateway component.

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS10091025B2System and method for enabling use of a single user identifier across incompatible networks for UCC functionality
Publication Date: 2018.10.02 DAMAKA INC
  • US10091025B2 patent drawing
  • US10091025B2 patent drawing
  • US10091025B2 patent drawing

AI summary

A method and system for supporting a cross-domain communication session between communication platforms using a bridge server are provided. In one example, the method includes registering the bridge server with multiple platforms using a user identifier. A request is received from one of the platforms to establish a communication session with a user corresponding to the user identifier. A communication leg is created for each of the platforms. The leg from which the request was received is an incoming leg and the other legs are outgoing legs. The request is sent over the outgoing legs. An acceptance is received from one of the outgoing legs. A cancel message is sent over the outgoing legs from which the acceptance was not received. The acceptance is sent over the incoming leg. The incoming leg and the outgoing leg from which the acceptance was received are bridged to establish the session.