5G Terminal Capability Identifier Segmentation for Software Updates

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In the 5G NR system, existing communication capability reporting methods fail to update terminal communication capabilities when software changes occur, as the capability identifier remains unchanged despite changes in communication capabilities.

Innovation Solution

A method where a terminal determines and sends a capability identifier to a network device, allowing the network to associate and update communication capabilities based on multiple identifiers, enabling timely updates even when software is refreshed or upgraded.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Device complexity

If a single capability identifier is used to represent terminal communication capability, then the capability reporting is simplified and data volume is reduced, but the capability cannot be updated when software changes occur

Engineering Contradiction:
Improvecapability reporting complexityVSAvoidcapability update ability
Core Design Contradiction:
Device complexityVSAdaptability or versatility

Solution Approach 1:

The capability identifier is segmented into multiple independent parts: terminal identifier, capability version identifier, and capability type identifier. This segmentation allows the terminal to update specific capability information (through version or type identifiers) without changing the terminal identifier, enabling flexible capability updates while maintaining a structured reporting framework

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The capability identifier structure is made dynamic by introducing version identifiers and type identifiers that can change independently. When software is updated, the terminal can modify the version identifier or add new type identifiers to reflect changed capabilities, making the identifier system adaptable to software changes while maintaining backward compatibility

Inventive Principle:
Principle #15Dynamics

2Reliability

If capability identifier is based on IMEI components (TAC and SVN), then the identifier is stable and easy to obtain, but it cannot reflect communication capability changes after software refresh

Engineering Contradiction:
Improveidentifier stabilityVSAvoidcapability change information
Core Design Contradiction:
ReliabilityVSLoss of information

Solution Approach 1:

A capability version identifier is introduced as an intermediary between the stable terminal identifier (IMEI components) and the variable communication capabilities. This intermediary layer allows the system to maintain stable terminal identification while accurately reflecting capability changes through version information, preventing information loss about capability evolution

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The identifier system transitions from static IMEI components to a dynamic multi-parameter structure including terminal identifier, capability version identifier, and capability type identifier. This parameter expansion allows the system to maintain stability (through terminal identifier) while capturing capability changes (through version and type identifiers), resolving the information loss problem

Inventive Principle:
Principle #35Parameter changes

3Loss of information

If terminal reports detailed communication capability parameters, then the network has complete capability information, but the data volume and reporting overhead increase significantly

Engineering Contradiction:
Improvecapability information completenessVSAvoidreported data volume
Core Design Contradiction:
Loss of informationVSQuantity of substance

Solution Approach 1:

The patent extracts only the essential capability identification elements (terminal identifier, capability version identifier, and capability type identifier) from the complete set of communication capability parameters. This extraction provides the network with sufficient information to identify and manage terminal capabilities without requiring transmission of all detailed capability parameters, thereby reducing data volume while maintaining information completeness

Inventive Principle:
Principle #2Taking out (Extraction)

Data Source

PatentEP3761688B1Communication capability reporting
Publication Date: 2024.11.06 HUAWEI TECH CO LTD
  • EP3761688B1 patent drawingFigure 1
  • EP3761688B1 patent drawingFigure 2
  • EP3761688B1 patent drawingFigure 3A

AI summary

Embodiments of this application provide a communication capability reporting method, a device, and a system, so that a communications device can update its own communication capability in a timely manner when the communication capability of the communications device is associated with a capability identifier of the communications device. The method includes: determining, by a first communications device, a capability identifier of the first communications device, where the capability identifier of the first communications device is one of one or more capability identifiers corresponding to the first communications device; and sending, by the first communications device, the capability identifier of the first communications device to a second communications device, where the capability identifier of the first communications device is used to determine the communication capability of the first communications device.