BGCF Session Setup Control for Messaging Interoperability
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing multimedia communication systems face challenges in managing network resources efficiently, as they need to coexist with pre-UP 1.0 devices and protocols, such as closed group chat and MSRP file transfer, while allowing advanced Rich Communication Services (RCS) features like open group chat and HTTP file transfer, without compromising security and resource allocation.
Innovation Solution
Implementing a system with a Breakout Gateway Control Function (BGCF) that filters and routes SIP messages to establish RCS messaging sessions based on device capabilities, blocking MSRP file transfers and CGC setups to prioritize UP 1.0 features and manage network resources effectively.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If the system allows both pre-UP 1.0 devices (using MSRP file transfer and closed group chat) and UP 1.0 devices (using HTTP file transfer and open group chat) to coexist, then device compatibility is improved, but network resource management and security are worsened
Solution Approach 1:
The system segments SIP message handling into distinct routing paths based on device capability. The BGCF divides traffic into UP 1.0 compliant sessions (using HTTP file transfer and open group chat) and pre-UP 1.0 sessions (using MSRP and closed group chat), allowing each segment to be managed with appropriate resource allocation and security policies
Solution Approach 2:
The Breakout Gateway Control Function (BGCF) acts as an intermediary between mobile originating devices and mobile terminating devices. It receives SIP messages, determines device capabilities, and routes messages appropriately - allowing UP 1.0 features while blocking legacy MSRP file transfers, thus enabling compatibility without compromising resource management
2Reliability
If the system blocks legacy MSRP file transfer and closed group chat protocols, then network security and resource allocation are improved, but compatibility with pre-UP 1.0 devices is worsened
Solution Approach 1:
The system applies different quality controls to different message types. UP 1.0 compliant messages (open group chat, HTTP file transfer) receive full routing and resource allocation, while pre-UP 1.0 messages (closed group chat, MSRP file transfer) are blocked at the BGCF, creating localized quality enforcement without universal blocking
Solution Approach 2:
The system performs preliminary capability determination before message routing. The BGCF evaluates device capabilities in advance and makes routing decisions based on UP 1.0 compliance, preventing legacy protocol messages from consuming network resources while allowing advanced features to proceed
3Productivity
If the system routes all SIP messages to establish sessions, then messaging functionality is improved, but network resource consumption and security risks are worsened
Solution Approach 1:
The system applies partial action by selectively routing only UP 1.0 compliant SIP messages while blocking legacy protocol messages. The BGCF performs capability determination and routes messages accordingly, avoiding the excessive action of routing all messages regardless of compliance, thus optimizing resource consumption while maintaining functionality
Data Source
AI summary
A device includes a processor and a memory. The processor effectuates operations including receiving a service capability for a mobile originating (MO) device. The processor further effectuates operations including receiving a service capability for a mobile terminating (MT) device. The processor further effectuates operations including receiving session initiation protocol (SIP) messages from the MO device at a Breakout Gateway Control Function (BGCF). The processor further effectuates operations including determining whether the received SIP messages are associated with setting up an outgoing open group chat (OGC) or an outgoing Message Session Relay Protocol (MSRP) file transfer. The processor further effectuates operations including blocking the SIP messages in response to the determination that the SIP messages are associated with setting up a MSRP file transfer.