MGW Control Plane Device Selection via DNS Query

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The conventional eMBMS network architecture is inefficient due to cumbersome logic in end-to-end control plane message exchanges between the BMSC and eNB, requiring complex manual provisioning of downstream control elements, which is operationally intensive and not scalable, especially in large core networking domains, leading to poor customer satisfaction and revenue loss.

Innovation Solution

The introduction of a dynamic control plane node selection method using a Domain Name System (DNS) query/response exchange, where the Multimedia Broadcast Multicast Service Gateway (MGW) intelligently selects downstream control plane devices based on session exchange procedural triggers, eliminating the need for pre-provisioning and simplifying the network architecture by dynamically allocating control plane entities such as MMEs and SGSNs.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If conventional eMBMS session exchange procedures are used with manual provisioning of downstream control elements, then basic connectivity can be established, but the network architecture becomes operationally intensive and not scalable

Engineering Contradiction:
Improvebasic connectivityVSAvoidnetwork architecture complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The MGW autonomously selects downstream control plane devices (MMEs, SGSNs) based on service area information from DNS queries, eliminating the need for manual provisioning and complex pre-configuration of downstream control elements. The system serves itself by dynamically discovering and selecting appropriate control plane entities.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

A DNS system is introduced as an intermediary between the MGW and downstream control plane devices. The DNS receives queries from the MGW containing service area information and returns corresponding control plane device identifiers, simplifying the interaction and eliminating complex direct provisioning between MGW and multiple control elements.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If manual provisioning of downstream control elements is implemented, then control plane connectivity can be established, but operational overhead increases significantly

Engineering Contradiction:
Improvecontrol plane connectivityVSAvoidoperational overhead
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The MGW automatically performs DNS queries to discover downstream control plane devices without requiring manual provisioning operations. The system eliminates time-consuming manual configuration tasks by enabling autonomous device selection through standardized DNS query/response exchanges.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The DNS system pre-loads and stores mappings between service area information and control plane device identifiers. When the MGW needs to select a control plane device, it simply queries the pre-prepared DNS records, avoiding the need for complex real-time provisioning decisions and manual interventions.

Inventive Principle:
Principle #10Preliminary action

3Reliability

If complex mapping of BMSC with downstream control elements is performed, then complete network connectivity can be achieved, but scalability to large core networking domains is limited

Engineering Contradiction:
Improvenetwork connectivityVSAvoidnetwork scalability
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The DNS acts as a scalable intermediary that decouples the BMSC/MGW from direct knowledge of downstream control elements. This abstraction layer allows the network to scale to large core networking domains by simply adding DNS records rather than reconfiguring complex mappings across multiple network elements.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The DNS system provides a universal mechanism for service area to control plane device mapping that works across all types of downstream control elements (MMEs, SGSNs, etc.). This single universal approach replaces multiple specialized provisioning mechanisms, enabling scalable deployment across diverse network configurations.

Inventive Principle:
Principle #6Universality (Multi-functionality)

4Reliability

If pre-provisioning of downstream control plane devices is done, then control plane establishment can proceed, but message exchange efficiency deteriorates due to message length and node name identifiers

Engineering Contradiction:
Improvecontrol plane establishmentVSAvoidmessage exchange efficiency
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The invention extracts and separates the service area identification function from the control plane device selection function. By using DNS to translate service area information into control plane device identifiers, the system eliminates the need for lengthy node name identifiers in control plane messages, reducing message length and improving exchange efficiency.

Inventive Principle:
Principle #2Taking out (Extraction)

Data Source

PatentUS10805217B2Control plane device selection for broadcast session exchange
Publication Date: 2020.10.13 AT&T INTELLECTUAL PROPERTY I L P
  • US10805217B2 patent drawing
  • US10805217B2 patent drawing
  • US10805217B2 patent drawing

AI summary

Control plane devices are selected by a Multimedia Broadcast Multicast Service Gateway (MGW) based on session exchange procedural triggers received from a Broadcast Multicast Service Center (BMSC). In one aspect, the MGW can employ a serving area-based Domain Name System (DNS) query/response exchange for control plane device selection that simplifies the overall complex broadcast core network architecture and design. Additionally or optionally, the MGW can employ other factors, such as, but not limited to, round trip time (RTT), load information, active/inactive link status, etc. to select the control plane devices that are to be utilized for establishing the end-to-end control plane message exchanges.