UE Radio Capability Identifier for 5G Network Storage Optimization

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The existing 3GPP systems face challenges in efficiently managing and transferring UE radio capabilities, particularly due to the large size of UE capability information messages caused by increasing carrier aggregation band combinations, leading to increased LTE call setup times and storage burdens in the core network.

Innovation Solution

The introduction of a UE Radio Capability Identifier (URCI) that comprises a Device Manufacturer ID, Model ID, and Capability ID, allowing for secure and efficient transfer of UE capabilities, reducing storage needs, and enabling flexible capability reporting based on operating profiles, while preventing rogue devices from overriding genuine capabilities.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Speed

If UE capabilities are stored per UE in the core network, then the network can quickly retrieve capabilities during connection setup, but the storage burden increases significantly with millions of subscribers

Engineering Contradiction:
Improvecapability retrieval speedVSAvoidstorage burden
Core Design Contradiction:
SpeedVSQuantity of substance

Solution Approach 1:

The patent creates a copy of UE capabilities from the first UE that provides them, and stores this copied capability information in the core network for reuse with subsequent UEs of the same model, eliminating the need to store individual capability data for every UE

Inventive Principle:
Principle #26Copying

Solution Approach 2:

The patent makes UE capability information universal by storing it once per UE model rather than per individual UE, allowing the same capability data to serve multiple UEs of the same model, thus reducing overall storage requirements while maintaining quick retrieval capability

Inventive Principle:
Principle #6Universality (Multi-functionality)

2Loss of information

If UE capability information messages include all carrier aggregation band combinations, then complete capability information is provided, but the message size increases leading to increased LTE call setup times

Engineering Contradiction:
Improvecapability information completenessVSAvoidLTE call setup time
Core Design Contradiction:
Loss of informationVSLoss of time

Solution Approach 1:

The patent extracts only the essential UE capability information needed for network configuration from the complete capability set, separating critical capabilities from optional or redundant ones, thereby reducing message size while maintaining sufficient information for successful call setup

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The patent applies partial action by transmitting a subset of UE capabilities that are most relevant for initial network setup and connection establishment, rather than transmitting the complete capability information set, thus reducing transmission time while maintaining adequate functionality

Inventive Principle:
Principle #16Partial or excessive action

3Device complexity

If a fixed UE identifier like TAC part of IMEI is used, then capability storage is simplified, but flexibility is lost when UEs need to advertise different capabilities according to PLMN or operating conditions

Engineering Contradiction:
Improvecapability storage simplicityVSAvoidcapability advertising flexibility
Core Design Contradiction:
Device complexityVSAdaptability or versatility

Solution Approach 1:

The patent implements a dynamic UE identifier system that can adapt based on the PLMN and operating conditions, allowing the identifier to change or expand according to the specific network context, thus maintaining both simplicity and flexibility

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The patent segments the UE identifier into multiple components, with the base identifier remaining fixed for simple storage, and additional context-specific identifiers or parameters added when needed for different PLMNs or operating conditions, maintaining flexibility without overwhelming complexity

Inventive Principle:
Principle #1Segmentation

4Quantity of substance

If the network retrieves UE capabilities from the first UE and uses it for all UEs of that model, then storage is reduced, but the risk of rogue UEs overriding genuine capabilities increases

Engineering Contradiction:
Improvestorage requirementsVSAvoidcapability authenticity
Core Design Contradiction:
Quantity of substanceVSReliability

Solution Approach 1:

The patent implements a feedback mechanism where the network verifies UE capability information against stored reference data and validates subsequent UEs against the established capability profile, creating a closed-loop system that detects and prevents rogue UE attempts to override genuine capabilities

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The patent performs preliminary validation and authentication of the first UE's capability information before storing it as the reference profile, and establishes verification procedures in advance that prevent rogue UEs from successfully overriding genuine capabilities, addressing the security issue before it can manifest

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS11671822B2UE capabilities provisioning and retrieval in cellular networks
Publication Date: 2023.06.06 APPLE INC
  • US11671822B2 patent drawing
  • US11671822B2 patent drawing
  • US11671822B2 patent drawing

AI summary

An apparatus of a user equipment (UE) comprises one or more baseband processors to encode a unique UE identifier to be transmitted to an Access and Mobility Function (AMF) of a Fifth Generation (5G) network, wherein the unique identifier identifies UE capabilities to be stored in a UE capabilities database. An apparatus of Access and Mobility Function (AMF) of a Fifth Generation (5G) network comprises one or more processors to receive a user equipment (UE) Capabilities update from a remote server to update a UE capability database that stores UE capability information corresponding to one or more UEs identified with a unique identifier, and to process the UE Capabilities update via one or more Application Programming Interfaces (APIs).