Stale User Context Detection in 5G gNodeB

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Stale user contexts in 5G NR base station systems (gNodeB) lead to resource wastage, interference, and service impact due to desynchronization and incomplete procedures, lacking sufficient mechanisms for detection and removal before PDU session establishment.

Innovation Solution

Implementing a method for stale user context detection and removal at the gNB-CU and gNB-DU using configurable timers, periodic Channel State Information reports, and a new audit mechanism between gNB-CU and gNB-DU for active user context synchronization, involving changes to F1AP and E1AP protocol specifications for non-UE-associated signaling.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If UE contexts are maintained in gNB-CU and gNB-DU for active users, then service quality and QoS are improved, but stale UE contexts accumulate causing resource wastage and system complexity

Engineering Contradiction:
Improveservice qualityVSAvoidnumber of UE contexts
Core Design Contradiction:
ReliabilityVSQuantity of substance

Solution Approach 1:

The patent applies preliminary action by implementing proactive detection mechanisms (timers, measurement reports, audit procedures) that identify stale UE contexts before they cause significant resource consumption. The system performs periodic checks and synchronization audits to detect and remove stale contexts early, preventing the accumulation that would otherwise occur during normal operation.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent implements feedback mechanisms through periodic measurement reports from UEs, timer-based status checks, and audit procedures between gNB-CU and gNB-DU. These feedback loops continuously monitor UE context validity and trigger removal actions when staleness is detected, creating a closed-loop system that adapts to changing network conditions.

Inventive Principle:
Principle #23Feedback

2Reliability

If stale UE contexts are not removed, then active users are not affected, but resource wastage and interference increase

Engineering Contradiction:
Improveservice continuityVSAvoidresource wastage
Core Design Contradiction:
ReliabilityVSLoss of energy

Solution Approach 1:

The patent extracts and removes stale UE contexts from the active user context database through targeted deletion procedures. By identifying stale contexts using timers, measurement reports, and audit mechanisms, the system selectively removes only the problematic entries while preserving active user contexts, thereby eliminating resource wastage without disrupting ongoing services.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The patent changes the state of UE contexts from active to removed by modifying their status parameters. Through timer expiration, measurement report failures, and audit procedure results, the system determines when a context should be transitioned from active state to removed state, enabling resource reallocation while maintaining service continuity for legitimate users.

Inventive Principle:
Principle #35Parameter changes

3Device complexity

If gNB-CU and gNB-DU operate independently, then system complexity is reduced, but desynchronization creates stale contexts

Engineering Contradiction:
Improvesystem architectureVSAvoidcontext synchronization
Core Design Contradiction:
Device complexityVSReliability

Solution Approach 1:

The patent implements feedback mechanisms through periodic audit procedures where gNB-CU and gNB-DU exchange UE context status information. This feedback loop enables the independently operating units to detect and resolve desynchronization issues, ensuring consistency across the distributed architecture without requiring tight coupling.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The patent applies periodic action through timer-based status checks and scheduled audit procedures that run at configured intervals. These periodic operations allow gNB-CU and gNB-DU to synchronize their UE context databases at regular intervals, preventing desynchronization while maintaining architectural independence and avoiding continuous complex coordination.

Inventive Principle:
Principle #19Periodic action

4Productivity

If new admission control thresholds are set low, then more users can be served, but stale contexts fill available capacity

Engineering Contradiction:
Improveuser capacityVSAvoidstale user contexts
Core Design Contradiction:
ProductivityVSQuantity of substance

Solution Approach 1:

The patent applies preliminary action by detecting and removing stale UE contexts before they consume admission control capacity. Through proactive timer-based detection, measurement report monitoring, and periodic audits, the system identifies and removes stale contexts early, ensuring that admission control thresholds reflect only truly active users and maximizing available capacity for new users.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS20230396991A1METHODS FOR EFFECTIVE MANAGEMENT AND MAINTENANCE OF ACTIVE USER EQUIPMENT CONTEXT IN THE 5G gNodeB
Publication Date: 2023.12.07 MAVENIR US INC
  • US20230396991A1 patent drawing
  • US20230396991A1 patent drawing
  • US20230396991A1 patent drawing

AI summary

A method for stale user context detection and removal is implemented at one of Open Radio Access Network (O-RAN) Centralized Unit (gNB-CU) or Distributed Unit (gNB-DU). In a first variant which utilizes the gNB-CU, the gNB runs a configurable periodic timer for initiating the stale UE detection procedure, i.e., the gNB configures, for every UE context stored in its database, a special Event A1 with the low a1-Threshold=−120 dBm, reportInterval=512 ms, and reportAmount=2. In a second variant which utilizes the gNB-CU, stale UE detection mechanism can be based on a periodic Event A1 configured during initial User admission procedure, i.e., the gNB configures a special Event A1 with the low a1-Threshold=−120 dBm, reportInterval=1 minute, and reportAmount=infinity. In a further variant, stale UE contexts can be identified at the gNB-DU based on periodic Channel State Information (CSI) reports.