Gateway Node Data Channel Negotiation for Legacy PBX Calls
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Legacy Private Branch Exchange (PBX) systems lack the functionality to support enhanced calling features, such as peer-to-peer application media types, which are not supported in typical SIP Session Description Protocol (SDP), limiting flexibility and compatibility with modern data channels in wireless communications networks.
Innovation Solution
A gateway node, such as a Data Channel Server Gateway (DCS GW), is introduced to negotiate and establish data channels between User Equipments (UEs) associated with a PBX, enabling enhanced call sessions by supporting IMS data channel specifications and interacting with PBXs through REST interfaces and WebSocket event notifications.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If legacy PBX systems are used, then compatibility with existing infrastructure is maintained, but support for enhanced calling features and data channels is limited
Solution Approach 1:
A gateway node is introduced as an intermediary component between legacy PBX systems and modern data channel requirements. The gateway translates and adapts signaling protocols, enabling enhanced calling features while maintaining compatibility with existing PBX infrastructure without requiring complex modifications to the legacy systems themselves
Solution Approach 2:
The system is segmented into distinct functional components: the legacy PBX system remains unchanged while a separate gateway node handles data channel negotiation and establishment. This segmentation allows enhanced features to be added without increasing the complexity of the core PBX system
2Adaptability or versatility
If data channels are established between UEs, then real-time data exchange capability is improved, but compatibility with legacy PBX systems deteriorates
Solution Approach 1:
The gateway node acts as a mediator that translates data channel establishment requests into legacy PBX-compatible signaling. It negotiates data channel parameters between modern UEs and the legacy PBX system, ensuring compatibility while enabling real-time data exchange capabilities that would otherwise be incompatible with legacy systems
3Adaptability or versatility
If PBX systems are upgraded to support modern features, then functionality is improved, but infrastructure cost and complexity increase
Solution Approach 1:
Rather than upgrading the entire PBX infrastructure, a lightweight gateway node is deployed as an intermediary. This gateway provides modern data channel capabilities while the legacy PBX system continues to operate unchanged, avoiding the cost and complexity of comprehensive infrastructure upgrades
Solution Approach 2:
The gateway node implements a simplified version of modern data channel functionality that interfaces with legacy PBX systems. Instead of replacing the entire system with a complex modern PBX, the gateway copies only the necessary data channel negotiation and management functions, reducing overall system complexity
Data Source
AI summary
A method performed by a gateway node for enhancing a call session between a first User Equipment, UE, and a second UE in a communications network is provided. The second UE is associated to a Private Branch Exchange, PBX, node. When a call session has been established between the first UE and the second UE via the PBX node and via an Internet Protocol Multimedia Subsystem, IMS, network, the gateway node receives, from any one out of the first UE and the second UE, a request for establishing a data channel to enhance the call session. The gateway node negotiates one or more parameters to be used in the requested data channel between the first UE and the second UE. The gateway node establishes the data channel according to the negotiation, to enhance the call session between the first UE and the second UE.