UE Parameters Update Compatibility Signaling for Unsupported Data Set Types
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing 3GPP Fifth Generation (5G) telecommunications systems face issues with unsupported User Equipment (UE) parameters update data set types during the UDM control plane procedure, leading to loss of information and failure to send acknowledgments, as pre-Release-17 UEs consider new code points as reserved, causing the entire Payload container IE to be ignored.
Innovation Solution
A method for the network to detect and send only supported UE parameters update data set types by receiving an indication of supported UPU data set types from the UE, using Nudm_SDM_Notification and Nudm_SDM_Info messages, and storing this information for subsequent procedures.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If the network sends new UPU data set type code points to pre-Release-17 UEs, then the network can provide updated parameters, but the UE ignores the entire Payload container IE and loses all information
Solution Approach 1:
The patent segments the UPU data transmission by introducing individual support indication bits for each UPU data set type (routing indicator update data, default configured NSSAI update data, and future extensions). This allows the network to send only the data set types that the UE supports, preventing the UE from ignoring the entire Payload container while still providing updated parameters where compatible.
Solution Approach 2:
The patent performs preliminary action by having the UE indicate its supported UPU data set types before the network sends the actual update data. The UE sends a support indication message containing bits that specify which data set types it can handle, allowing the network to prepare and send only compatible data, thereby preventing information loss.
2Adaptability or versatility
If pre-Release-17 UEs receive unsupported code points, then the network attempts to provide new functionality, but the UE discards the entire Payload container IE
Solution Approach 1:
The patent implements feedback by having the UE send a support indication message back to the network before receiving UPU data. This feedback contains information about which data set types the UE supports, allowing the network to adjust its transmission strategy and maintain reliable parameter updates by sending only compatible data.
Solution Approach 2:
The patent performs preliminary action by establishing compatibility information exchange before the actual data transfer. The UE's support indication is received and processed in advance, enabling the network to configure the Payload container with only supported data set types, thus ensuring reliable delivery.
3Productivity
If the network sends UPU data without checking UE support, then the procedure is simple and fast, but the UE ignores the Payload container and no acknowledgment is sent
Solution Approach 1:
The patent performs preliminary action by exchanging support indication information before the actual parameter update data is sent. This preliminary step, while adding some signaling overhead, prevents the complete loss of update data by ensuring compatibility, thereby maintaining the effectiveness of the parameter update procedure.
Solution Approach 2:
The patent introduces an intermediary support indication mechanism that mediates between the network's desire to send updated parameters and the UE's capability to process them. This intermediary step provides compatibility information that enables successful data transfer without complete information loss.
Data Source
Figure 1
Figure 2
Figure 3
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 (506, 606, 726a, 826a) 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 (508, 608) 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.