RedCap-Aware Neighbor Cell Handover for Service Continuity

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

The 3GPP standards lack mechanisms to support seamless handovers for RedCap devices between LTE and 5G networks, particularly when target cells do not support RedCap capabilities, leading to fragmented implementations and disrupted service continuity.

Innovation Solution

Implement RedCap-aware Automatic Neighbor Relationship (ANR) mechanisms to identify and avoid handovers to non-RedCap cells, and provide intelligent UE recovery strategies, including retry limits and reselection to LTE networks when handovers fail.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If RedCap devices are migrated to 5G networks, then device capability and performance are improved, but service continuity is disrupted when target cells do not support RedCap capabilities

Engineering Contradiction:

Improvedevice capabilityVSAvoidservice continuity

Core Design Contradiction:

Adaptability or versatilityVSReliability

Solution Approach 1:

The network node performs preliminary actions by determining RedCap support capability of neighbor cells before handover execution, and generates handover prohibition information to prevent handovers to non-RedCap cells, thereby avoiding service disruption before it occurs

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The system implements feedback mechanisms where the network node sends handover prohibition information to the RedCap device based on target cell capability assessment, and the device provides feedback on handover execution status, enabling dynamic adjustment of handover decisions

Inventive Principle:

Principle #23Feedback

2Ease of operation

If handover mechanisms are implemented without RedCap awareness, then network mobility is enabled, but fragmented design and implementation occur across different vendors

Engineering Contradiction:

Improvenetwork mobilityVSAvoidimplementation fragmentation

Core Design Contradiction:

Ease of operationVSDevice complexity

Solution Approach 1:

The patent creates a universal handover mechanism that works across different vendor implementations by standardizing the handover prohibition information exchange between network nodes and RedCap devices, making the solution multi-vendor compatible while maintaining simplicity

Inventive Principle:

Principle #6Universality (Multi-functionality)

Solution Approach 2:

The system changes the handover decision parameters by introducing RedCap support capability as a determining factor, transforming the handover mechanism from a generic mobility function to a RedCap-aware selective handover function that prevents fragmentation

Inventive Principle:

Principle #35Parameter changes

3Area of stationary object

If handovers to non-RedCap cells are allowed, then network coverage is expanded, but service continuity is compromised

Engineering Contradiction:

Improvenetwork coverageVSAvoidservice continuity

Core Design Contradiction:

Area of stationary objectVSReliability

Solution Approach 1:

The network node acts as an intermediary between the RedCap device and non-RedCap cells by generating and transmitting handover prohibition information, preventing direct handover to incompatible cells while maintaining network coverage through alternative RedCap-capable cell selections

Inventive Principle:

Principle #24Intermediary (Mediator)

Data Source

PatentUS12587919B2Systems and methods to facilitate service continuity for wireless communication system handovers

Publication Date: 2026.03.24 AT&T INTELLECTUAL PROPERTY I L P

AI summary

Aspects of the subject disclosure may include, for example, determining, for a network node, one or more neighbor network nodes relative to the network node; determining, for each of the one or more neighbor network nodes, whether support is provided for a particular type of end-user device; and generating, for the network node, a neighbor cell relation table, wherein the neighbor cell relation table includes the one or more neighbor network nodes, and wherein the neighbor cell relation table further includes for at least one of the neighbor network nodes an indication that support is provided for the particular type of end-user device. Other embodiments are disclosed.