Session Border Controller UCE Routing via ENUM

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

The transmission and processing of multiple user capability exchange (UCE) messages across different IMS subnetworks in SIP-based communication systems waste resources and increase latency, as they require multiple messages to be sent and received between various network devices, leading to inefficient network performance.

Innovation Solution

Implementing a system where a single User Equipment (UE) can transmit a single UCE message to a specific IMS subnetwork, identified by a Session Border Controller (SBC) using an ENUM data structure, which then processes a single response, reducing the number of messages transmitted and received across the network.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If multiple UCE messages are transmitted across different IMS subnetworks, then capability information can be exchanged with all subnetworks, but network resources are wasted and latency increases

Engineering Contradiction:

Improvecapability exchange completenessVSAvoidnetwork resource consumption

Core Design Contradiction:

ReliabilityVSLoss of energy

Solution Approach 1:

The system segments the capability exchange process by identifying which IMS subnetworks are relevant to the specific session type. The SBC divides the broadcast UCE messages into targeted messages, sending capability exchange requests only to subnetworks that handle the specific service type (voice, video, messaging, etc.), thereby avoiding unnecessary transmissions to irrelevant subnetworks.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

Instead of transmitting UCE messages to all IMS subnetworks (excessive action), the system applies partial action by selectively transmitting messages only to the subset of subnetworks that are relevant to the session. This partial transmission approach reduces network resource consumption while maintaining complete capability exchange for the required service type.

Inventive Principle:

Principle #16Partial or excessive action

2Reliability

If multiple UCE messages are transmitted across different IMS subnetworks, then capability information can be exchanged with all subnetworks, but latency increases due to multiple message transmissions

Engineering Contradiction:

Improvecapability exchange completenessVSAvoidmessage transmission latency

Core Design Contradiction:

ReliabilityVSLoss of time

Solution Approach 1:

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The system skips unnecessary message transmissions to irrelevant IMS subnetworks. By using the ENUM data structure to identify and skip non-relevant subnetworks, the system rushes through the capability exchange process efficiently, reducing overall latency while ensuring complete exchange with relevant subnetworks.

Inventive Principle:

Principle #21Skipping (Rushing through)

3Loss of energy

If a single UCE message is transmitted to a specific IMS subnetwork, then network resources are conserved, but the message must be correctly routed to the appropriate subnetwork

Engineering Contradiction:

Improvenetwork resource consumptionVSAvoidrouting complexity

Core Design Contradiction:

Loss of energyVSDevice complexity

Solution Approach 1:

The SBC acts as an intermediary between the UCE message source and the target IMS subnetwork. It uses the ENUM data structure as a lookup table to translate service type identifiers into specific subnetwork addresses, thereby simplifying the routing complexity while enabling precise message delivery to the correct subnetwork.

Inventive Principle:

Principle #24Intermediary (Mediator)

Solution Approach 2:

The ENUM data structure is pre-populated with mappings between service type identifiers and IMS subnetwork addresses. This preliminary action allows the SBC to quickly resolve the correct subnetwork destination without complex real-time routing decisions, reducing routing complexity while maintaining efficient single-message transmission.

Inventive Principle:

Principle #10Preliminary action

Data Source

PatentUS11444987B2Systems and methods for user capability exchange across networks

Publication Date: 2022.09.13 VERIZON PATENT & LICENSING INC

AI summary

A session border manager (SBM) may receive a session initiation protocol (SIP) request for a session or a service involving a first user equipment (UE) that is subscribed to a first network and a second UE, that is subscribed to a second network, wherein the SIP request indicates a service type of the session or the service. The SBM may determine, based on the service type, a subnetwork of the second network that is to facilitate the session or the service, wherein the subnetwork is one subnetwork, of a plurality of subnetworks, of the second network that is designated to manage communications that are associated with the service type. The SBM may transmit the SIP request to the subnetwork to cause the subnetwork to initiate the session or the service with the second UE. The SBM may receive, from the subnetwork, a response to the SIP request.