Source Core Node Handover Cancellation for Timely Resource Release

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The ambiguity in resource management for user data control during handover between 5G and 4G networks, specifically in the management of GTP-U headers, leads to inefficient resource utilization and potential network congestion due to unresolved resources after handover cancellation.

Innovation Solution

A method for a source core network node that includes receiving messages to manage resource release in the 5G and EPS networks, ensuring proper handling of user data resources through a series of coordinated messages between radio access networks and core network nodes.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If handover cancellation procedure is implemented between 5GS and EPS, then service continuity is maintained, but resource management becomes ambiguous leading to inefficient resource utilization

Engineering Contradiction:
Improveservice continuityVSAvoidresource utilization efficiency
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The source core network node performs preliminary actions by sending a release request message to release resources in the target core network node before the handover cancellation is fully processed. This ensures that resources are proactively released in advance, preventing resource waste while maintaining service continuity during the handover cancellation procedure.

Inventive Principle:
Principle #10Preliminary action

2Reliability

If resources are secured in core network device for handover, then user data control is enabled, but resources are not released when handover is canceled causing network congestion

Engineering Contradiction:
Improveuser data controlVSAvoidnetwork congestion
Core Design Contradiction:
ReliabilityVSObject-generated harmful factors

Solution Approach 1:

The system implements feedback mechanisms where the source core network node receives notification about handover cancellation and responds by sending a release request message to the target core network node. This feedback loop ensures that resources are properly released when handover is canceled, preventing network congestion while maintaining user data control during active handover.

Inventive Principle:
Principle #23Feedback

3Adaptability or versatility

If GTP-U header management is performed differently in 5GS and EPS, then system-specific requirements are met, but interoperability during handover becomes complex

Engineering Contradiction:
Improvesystem-specific controlVSAvoidhandover procedure complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The source core network node acts as an intermediary that coordinates between 5GS and EPS systems during handover cancellation. It manages the complexity by sending appropriate release request messages to the target core network node, handling the differences in GTP-U header management between systems while simplifying the overall interoperability process.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS12526116B2Method for source core network node, source core network node, and non-transitory computer-readable medium
Publication Date: 2026.01.13 NEC CORP
  • US12526116B2 patent drawing
  • US12526116B2 patent drawing
  • US12526116B2 patent drawing

AI summary

An object is to appropriately manage a resource for user data control. A method for a source core network node according to one aspect of the present disclosure, includes: receiving, from a source RAN associated with a 5GS, a first message for canceling handover of a terminal from the 5GS to an EPS; transmitting a second message to a target core network node associated with the EPS when receiving the first message; receiving a third message from the target core network node when transmitting the second message; transmitting a fourth message to the source RAN when receiving the third message; and transmitting a fifth message for releasing a resource being secured in a core network device when transmitting the fourth message.