Core Network MME Relocation via External SDN Controller

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current 3GPP specifications do not provide procedures for relocating mobility management and bearer management of mobile terminals between Mobility Management Entities (MMEs) initiated by external control nodes such as Software-Defined Network (SDN) controllers, Network Function Virtualization (NFV) controllers, or Operations Support Systems (OSS), despite the growing demand for core network virtualization.

Innovation Solution

A method and device for relocating mobility management and bearer management of mobile terminals between network nodes in a core network, involving a control node that issues a relocation command to perform the relocation of mobility management and bearer management contexts from a source MME to a target MME, using Non-Access Stratum (NAS) messages and Radio Resource Control (RRC) messages, allowing for seamless handover regardless of the mobile terminal's movement.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If mobility management and bearer management are relocated between MMEs based on UE movement (TAU procedure or S1-based handover), then mobility management continuity is maintained, but the system cannot respond to external control node initiatives for load balancing or virtualization management

Engineering Contradiction:
Improveadaptability to external control node initiativesVSAvoidcomplexity of relocation procedure
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent introduces an external control node as an intermediary that mediates the relocation process between MMEs. The control node receives relocation requests, selects appropriate target MMEs, and coordinates the handover procedure, enabling the system to respond to load balancing and virtualization management initiatives without complicating the core MME relocation logic

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The relocation procedure is segmented into distinct phases: control node receives relocation request, control node selects target MME, source MME initiates handover to target MME, and target MME completes relocation. This segmentation allows each component to perform its specific function independently, improving adaptability while managing complexity through modular design

Inventive Principle:
Principle #1Segmentation

2Productivity

If core network virtualization is implemented to increase flexibility and efficiency, then network resource utilization improves, but the lack of standardized relocation procedures prevents effective management of virtualized MMEs

Engineering Contradiction:
Improvenetwork resource utilizationVSAvoidmanagement capability of virtualized MMEs
Core Design Contradiction:
ProductivityVSAdaptability or versatility

Solution Approach 1:

The patent creates a universal relocation procedure that works for both physical and virtualized MMEs. The control node manages relocation requests regardless of whether the MMEs are physical or virtual instances, enabling effective management of virtualized networks while maintaining compatibility with traditional deployments

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

Solution Approach 2:

The control node performs preliminary actions by pre-configuring virtualized MME resources and establishing relocation policies before actual relocation is needed. This allows the system to quickly respond to load balancing requirements and virtualization management initiatives without ad-hoc configuration delays

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS10448297B2Network node, mobile terminal, base station and methods performed therein
Publication Date: 2019.10.15 NEC CORP
  • US10448297B2 patent drawing
  • US10448297B2 patent drawing
  • US10448297B2 patent drawing

AI summary

A first network node (121S) is configured to perform mobility management and bearer management of a plurality of mobile terminals (111) having attached to the core network (120). Further, the first network node (121S) is configured to perform a relocation procedure for relocating the mobility management and the bearer management of the plurality of mobile terminals (111) to a second network node (121T) in the core network (120) in accordance with a relocation command from a control node (142) coupled to the core network (120). This contributes, for example, to relocation of mobility management and bearer management of a plurality of mobile terminals between network nodes regardless of the movement of those mobile terminals.