Mobility Management Element for Private Network Handover

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In communication systems with type A private networks, ensuring service continuity when a terminal device moves out of coverage from one private network to another, particularly due to overlapping network coverage with public networks, is a challenge.

Innovation Solution

A communication method involving a mobility management network element that receives and sends cell and network identifiers to facilitate the transfer of downlink routing information between user plane entities in different private networks or public networks, enabling seamless handover and service continuity.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If the terminal device moves out of coverage of the first private network, then the terminal device can access the second private network, but service continuity cannot be ensured due to lack of downlink routing information transfer

Engineering Contradiction:
Improvenetwork access capabilityVSAvoidservice continuity
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The mobility management network element proactively obtains downlink routing information from the first user plane entity before the terminal device actually hands over to the second private network. This preliminary acquisition of routing information enables the system to prepare the necessary data for seamless service continuation, resolving the contradiction by acting in advance rather than reactively after coverage loss.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The mobility management network element serves as an intermediary that coordinates between the first and second private networks. It receives the first cell identifier and network identifier, obtains routing information from the first user plane entity, and sends this information to the second user plane entity, thereby mediating the data transfer process and ensuring service continuity during the handover.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If downlink routing information is transferred between user plane entities, then service continuity is maintained, but network complexity increases due to additional information processing

Engineering Contradiction:
Improveservice continuityVSAvoidnetwork processing complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The mobility management network element performs multiple functions: it manages terminal device registration, obtains cell identifiers, acquires downlink routing information, and facilitates handover coordination. By consolidating these diverse functions into a single network element, the patent reduces overall network complexity while maintaining service continuity capability.

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

Solution Approach 2:

The mobility management network element autonomously obtains downlink routing information from the first user plane entity and independently sends it to the second user plane entity without requiring manual intervention or complex external coordination. This self-service mechanism simplifies the network architecture by enabling automatic routing information transfer during handover processes.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS11956691B2Communication method, device, and system
Publication Date: 2024.04.09 HUAWEI TECH CO LTD
  • US11956691B2 patent drawing
  • US11956691B2 patent drawing
  • US11956691B2 patent drawing

AI summary

One example method includes receiving, by a first mobility management network element, a first cell identifier and a network identifier from a first network element, where the network identifier includes an identifier of a first private network and an identifier of a second private network. The first mobility management network element can then obtain information about a second network element based on the first cell identifier and the network identifier, where the first network element serves a terminal device in the first private network, and where the second network element serves the terminal device in the second private network. The first mobility management network element can then send the first cell identifier and the network identifier to the second network element indicated by the information about the second network element, where the first cell identifier and the network identifier are used to obtain downlink routing information.