UE Capability Exchange Using Network Vendor-Specific Configuration

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional capability exchange methods in UE terminals lack sufficient granularity, leading to sub-optimal performance and interoperability issues due to reliance on coarse triggers like PLMN identifiers, which cannot distinguish between different infrastructure vendors within a single operator's network.

Innovation Solution

A UE terminal and network device exchange capability information, including specific network vendor information to enable dynamic and adaptive capability configuration updates, with the UE terminal updating its configuration based on network vendor information and selectively making changes persistent or temporary, and reporting detailed vendor information to the network.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Measurement precision

If capability exchange is triggered by PLMN identifier changes, then the procedure is simple to implement, but the granularity is insufficient and cannot distinguish between different infrastructure vendors

Engineering Contradiction:
Improvecapability configuration granularityVSAvoidcapability exchange procedure complexity
Core Design Contradiction:
Measurement precisionVSDevice complexity

Solution Approach 1:

The patent segments the capability exchange procedure into multiple stages: initial capability exchange based on PLMN identifier, and subsequent vendor-specific capability updates triggered by vendor information detection. This allows the system to maintain simple initial configuration while enabling detailed vendor-specific optimizations when needed, resolving the contradiction between simplicity and granularity.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent implements dynamic capability configuration that adapts based on detected vendor information. The UE terminal dynamically updates its capability configuration from a database when vendor-specific information is detected, allowing the system to transition from generic to optimized configuration based on operational context, thereby achieving fine-grained control without permanently increasing procedural complexity.

Inventive Principle:
Principle #15Dynamics

2Reliability

If vendor-specific capability configuration is implemented, then performance and interoperability are optimized, but the capability exchange procedure becomes more complex

Engineering Contradiction:
ImproveinteroperabilityVSAvoidcapability exchange procedure complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent pre-populates a database with vendor-specific capability configurations before actual network operation. When vendor information is detected during operation, the corresponding pre-configured capabilities are simply retrieved and applied. This preliminary preparation work, done offline, enables complex vendor-specific optimization without adding complexity to the real-time capability exchange procedure.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent implements a feedback mechanism where the UE terminal detects vendor information from network messages, compares it with stored vendor information, and automatically triggers capability updates when mismatches are found. This closed-loop feedback system ensures reliable vendor-specific configuration without requiring complex manual intervention or procedural changes.

Inventive Principle:
Principle #23Feedback

3Productivity

If capability configuration is dynamically updated based on vendor information, then performance is optimized, but message processing complexity increases

Engineering Contradiction:
Improvenetwork interaction efficiencyVSAvoidmessage processing complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The patent extracts vendor information from standard network messages (such as system information or RRC messages) without requiring new message types or protocols. By taking out and utilizing existing vendor identification fields in conventional messages, the system achieves vendor-specific optimization without increasing message processing complexity or requiring new communication protocols.

Inventive Principle:
Principle #2Taking out (Extraction)

Data Source

PatentUS20260052378A1User equipment terminal and method for dynamic capability exchange configuration
Publication Date: 2026.02.19 MEDIATEK INC
  • US20260052378A1 patent drawing
  • US20260052378A1 patent drawing
  • US20260052378A1 patent drawing

AI summary

A method for performing a capability exchange with a network device by a user equipment (UE) terminal includes receiving a message from the network device, wherein the message comprises network vendor information for identifying a manufacturer of the network device; updating a capability configuration of the UE terminal based on the message; transmitting an update notification message to the network device to trigger a capability exchange procedure; and during the capability exchange procedure, transmitting capability report information to the network device. The capability report information includes the updated capability configuration and at least a portion of UE terminal vendor information for identifying a chipset manufacturer of the UE terminal.