MP-TCP Mobility Management for 5G Network Scalability

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current GTP-tunnel based mobility management in 4G-LTE networks does not scale effectively for 5G networks with billions of emerging devices, requiring significant state maintenance and signaling overhead, and limits evolution and interworking with other radio access technologies.

Innovation Solution

Implementing a multipath transfer control protocol (MP-TCP) for mobility management, which establishes multiple subflows using different IP addresses as a mobile device moves between coverage areas, simplifying network architecture and reducing state maintenance by leveraging standard IP/Ethernet interfaces.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If GTP-tunnel based mobility management is implemented, then session continuity is maintained during device movement, but network device complexity and state maintenance requirements increase significantly

Engineering Contradiction:
Improvesession continuityVSAvoidnetwork equipment complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent extracts the mobility management functionality from the core network elements (PDN Gateway, Serving Gateway, MME) and relocates it to the User Equipment (UE) itself. The UE maintains its own IP address and TCP connections independently, while network elements provide only basic IP routing services. This extraction eliminates the need for complex GTP tunneling infrastructure and state maintenance in network equipment.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The UE performs self-service mobility management by maintaining its own IP address, TCP connections, and application layer sessions independently of network location changes. The device autonomously manages its own mobility state without requiring network elements to track or maintain session information, thereby simplifying network device complexity while preserving session continuity.

Inventive Principle:
Principle #25Self-service

2Reliability

If GTP-tunnel based mobility management is implemented, then seamless mobility is provided, but signaling overhead and state information requirements increase

Engineering Contradiction:
Improveseamless mobilityVSAvoidstate information overhead
Core Design Contradiction:
ReliabilityVSLoss of information

Solution Approach 1:

The patent extracts state information maintenance from network elements and places it in the UE. Network elements no longer store PDP contexts, bearer information, or GTP tunnel states. Instead, the UE maintains all necessary state information locally, dramatically reducing signaling overhead and state information requirements in the network while preserving seamless mobility through autonomous UE-side session management.

Inventive Principle:
Principle #2Taking out (Extraction)

3Adaptability or versatility

If GTP-tunnel based interface is used, then backward compatibility is maintained, but adaptability to other radio access technologies is limited

Engineering Contradiction:
Improveinterworking with other RATsVSAvoidinterface complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent implements a universal mobility management approach where the UE maintains standard IP addresses and TCP connections that are technology-agnostic. The same IP-based mobility mechanism works across different radio access technologies (LTE, 5G, WLAN, etc.) without requiring technology-specific GTP interfaces. This multi-functionality enables seamless interworking with other RATs while using standardized IP/Ethernet interfaces, reducing interface complexity.

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

4Reliability

If significant state information is maintained in network equipment, then session continuity is ensured, but scalability to billions of devices is limited

Engineering Contradiction:
Improvesession continuityVSAvoidnetwork scalability
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent extracts state information maintenance from network equipment and relocates it to the UE. Network elements store minimal or no session state information, while each UE independently maintains its own session state, IP address, and connection information. This distribution of state management enables the network to scale to billions of devices without proportionally increasing network equipment complexity or state storage requirements.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

Each UE performs self-service session management, independently maintaining its own mobility state and IP connections without requiring network elements to store or manage its session information. This self-service approach allows the network to support billions of devices with minimal state maintenance overhead in network equipment, dramatically improving network scalability while ensuring session continuity through autonomous UE-side management.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS9681481B2Mobility management of wireless networks based on multipath transfer control protocol
Publication Date: 2017.06.13 AT&T INTELLECTUAL PROPERTY I L P
  • US9681481B2 patent drawing
  • US9681481B2 patent drawing
  • US9681481B2 patent drawing

AI summary

Mobile management in a cellular network utilizes the multipath-transfer control protocol (MP-TCP). A mobile device establishes a first multipath-transfer control protocol (MP-TCP) subflow to a corresponding node using a first internet protocol (IP) address corresponding to the mobile device. At least a portion of the first IP address is uniquely associated with the first coverage area. The mobile device establishes a second MP-TCP subflow using a second IP address corresponding to the mobile device while the mobile device is in an overlapped coverage area including a first portion of the first coverage area and a second portion of a second coverage area. At least a portion of the second IP address is uniquely associated with the second coverage area. The mobile node turns off the first subflow when the mobile node determines it has left the first coverage area.