Network Handover Fallback Using Reserved Uplink Resources

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

User devices in communication networks often fail to establish a communication link with target network nodes during handovers, leading to unsuccessful handovers and subsequent fallbacks to source nodes, which are lengthy and battery-consuming recovery procedures, particularly in lower level mobility scenarios where no fallback procedures are defined.

Innovation Solution

User devices are equipped with instructions to obtain an indication of a fallback message uplink resource, execute a handover command or conditional configuration, attempt a handover to a target node, and in case of failure, execute a fallback to the source node using the reserved uplink resource to transmit a fallback message.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If a handover is attempted from source node to target node, then the user device can potentially connect to a new network node, but the handover may fail and cause service interruption

Engineering Contradiction:
Improvehandover capabilityVSAvoidconnection reliability
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The source node reserves uplink resources and transmits fallback indication information to the user device before the handover is completed. This preliminary preparation ensures that if the handover fails, the user device can immediately execute fallback without needing to request new resources, thereby maintaining connection reliability while enabling handover capability.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system prepares fallback mechanisms in advance by reserving uplink resources at the source node and providing fallback indication information to the user device before handover failure occurs. This cushioning measure ensures that the user device has a ready-made recovery path, reducing service interruption time and improving connection reliability.

Inventive Principle:
Principle #11Beforehand cushioning (Prior cushioning)

2Reliability

If the user device performs a recovery procedure after failed handover, then the communication link can be re-established, but the procedure is lengthy and causes service interruption

Engineering Contradiction:
Improvecommunication link restorationVSAvoidservice interruption time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The source node reserves uplink resources and transmits fallback indication information to the user device before the handover is completed. This preliminary preparation ensures that if the handover fails, the user device can immediately execute fallback without needing to request new resources, thereby maintaining connection reliability while minimizing service interruption time.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system allows the user device to skip the lengthy resource request and allocation procedures by providing pre-reserved uplink resources. The user device can directly transmit fallback indication information using these reserved resources, rushing through the recovery process and minimizing service interruption time while ensuring communication link restoration.

Inventive Principle:
Principle #21Skipping (Rushing through)

3Adaptability or versatility

If the user device requests new radio resources after handover failure, then fallback can be enabled, but the procedure consumes additional time and battery power

Engineering Contradiction:
Improvefallback capabilityVSAvoidbattery consumption
Core Design Contradiction:
Adaptability or versatilityVSUse of energy by moving object

Solution Approach 1:

The source node reserves uplink resources and transmits fallback indication information to the user device before the handover is completed. This preliminary preparation ensures that if the handover fails, the user device can immediately execute fallback using pre-reserved resources without consuming additional battery power on resource request procedures.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system enables the user device to self-service the fallback process by providing pre-configured uplink resources and fallback indication information. The user device can autonomously execute fallback without needing to engage in additional resource request and allocation procedures, reducing battery consumption while maintaining fallback capability.

Inventive Principle:
Principle #25Self-service

4Productivity

If the source node releases configuration before handover completion, then resources can be reallocated, but the user device loses access to uplink resources needed for fallback

Engineering Contradiction:
Improveresource allocation efficiencyVSAvoidfallback availability
Core Design Contradiction:
ProductivityVSAdaptability or versatility

Solution Approach 1:

The source node reserves uplink resources and transmits fallback indication information to the user device before the handover is completed. This preliminary action ensures that resources are maintained when needed for fallback while allowing the system to plan resource release timing, balancing resource allocation efficiency with fallback availability.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS20260059418A1Handover in a communication network
Publication Date: 2026.02.26 NOKIA TECHNOLOGIES OY
  • US20260059418A1 patent drawing
  • US20260059418A1 patent drawing
  • US20260059418A1 patent drawing

AI summary

Inter-alia, methods and apparatuses are disclosed for a handover of a user device in a communication network.