UE Parameters Update Handling for Unsupported Data Set Types

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

In Third Generation Partnership Project (3GPP) Fifth Generation (5G) telecommunications systems, UEs receiving unsupported UE parameters update data set types via the UDM control plane procedure incorrectly handle unassigned code points, leading to the entire Payload container IE being ignored, resulting in loss of all information and failure to send acknowledgments.

Innovation Solution

A method is implemented to detect and handle UE Parameters Update (UPU) data set types supported by a UE, involving network nodes like the UDM and AMF to send supported UPU data set types and avoid sending unsupported types, ensuring proper handling and acknowledgment of UPU data.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If a Rel-17 network sends new UPU data set types to a pre-Rel-17 UE, then the network can provide updated parameters, but the pre-Rel-17 UE incorrectly handles unassigned code points causing the entire Payload container IE to be ignored and information loss

Engineering Contradiction:

Improvenetwork capability to support new UPU data set typesVSAvoidcorrect handling of UPU data by pre-Rel-17 UEs

Core Design Contradiction:

Adaptability or versatilityVSReliability

Solution Approach 1:

The patent segments the UPU data transmission by introducing version indicators and type flags that divide the data structure into recognizable parts. Pre-Rel-17 UEs can identify and process only the portions they understand (version 0 data), while ignoring unsupported segments, preventing complete message rejection.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The network performs preliminary actions by setting version indicators and type flags before transmitting UPU data. This allows UEs to pre-validate the data format and determine compatibility before full processing, enabling graceful handling of mixed-version scenarios.

Inventive Principle:

Principle #10Preliminary action

2Adaptability or versatility

If the network uses reserved code points for future UPU data set types, then forward compatibility is maintained, but current UEs incorrectly interpret these as syntactically incorrect and ignore the entire Payload container IE

Engineering Contradiction:

Improveforward compatibility for future UPU data set typesVSAvoidloss of all information in Payload container IE when unsupported types are detected

Core Design Contradiction:

Adaptability or versatilityVSLoss of information

Solution Approach 1:

The patent segments the UPU data structure into individually addressable data sets with unique identifiers. Each data set can be independently processed or ignored by UEs based on their capabilities, preventing the 'all-or-nothing' rejection behavior that occurs with reserved code points.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The patent changes the parameter structure by introducing version indicators and type flags that transform reserved code points from error-triggering values into valid, versioned data set identifiers. This allows UEs to distinguish between unsupported future types and valid current types.

Inventive Principle:

Principle #35Parameter changes

3Reliability

If pre-Rel-17 UEs follow the specification and ignore Payload container IE with unassigned code points, then protocol compliance is maintained, but all information including supported data sets is lost

Engineering Contradiction:

Improveprotocol compliance of pre-Rel-17 UEsVSAvoidloss of all information in Payload container IE

Core Design Contradiction:

ReliabilityVSLoss of information

Solution Approach 1:

The patent segments the Payload container IE into multiple independent UPU data sets, each with its own validity indicator. UEs can selectively process valid segments while ignoring invalid ones, maintaining protocol compliance without suffering complete information loss.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The network performs preliminary validation by setting version indicators and type flags that allow UEs to pre-identify valid data sets before processing. This enables UEs to maintain protocol compliance while selectively accepting supported data sets.

Inventive Principle:

Principle #10Preliminary action

Data Source

PatentUS12574721B2Handling UE parameters update data set types which may be unsupported in UE parameters update via UDM control plane procedure

Publication Date: 2026.03.10 TELEFONAKTIEBOLAGET LM ERICSSON (PUBL)

AI summary

Disclosed herein is a method performed by a network node and a network node for handling User Equipment, UE, Parameters Update, UPU, data set types which may not be supported by a UE, the method comprising one or more of: receiving an indication of UPU data set types supported by a UE; determining if a given UPU data set type is supported by the UE based on the indication; if the given UPU data set type is supported by the UE, sending a UPU message to the UE with the given UPU data set type; and if the given UPU data set type is not supported by the UE, not sending the UPU message to the UE with the given UPU data set type.