UE PDU Session Establishment via Rejection Handling

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In 5G wireless networks, user equipment (UE) faces challenges in establishing packet data unit (PDU) sessions due to unknown PDU session types, leading to repeated rejections and inefficiencies in route selection policies.

Innovation Solution

The UE method involves transmitting a first message requesting communication based on a specific session type and attributes, receiving a rejection message indicating an unknown session type, and subsequently transmitting a new message requesting communication based on a different session type and attributes, ensuring the combinations are not identical.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If the UE continues to attempt PDU session establishment with the same RSD after rejection, then the UE maintains persistence in establishing communication, but the likelihood of repeated rejections increases and system resources are wasted

Engineering Contradiction:
ImprovePDU session establishment success rateVSAvoidTime spent on repeated rejection attempts
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The UE performs preliminary action by storing the rejected PDU session type and session attributes combination in a 'not to be used' list before making further establishment attempts. This prevents the UE from retrying the same rejected combination, thereby avoiding repeated rejections and saving time and resources while maintaining persistence through alternative session types.

Inventive Principle:
Principle #10Preliminary action

2Productivity

If the UE removes rejected session type combinations from use, then the UE avoids repeated rejections and improves establishment efficiency, but the complexity of session management increases

Engineering Contradiction:
ImprovePDU session establishment efficiencyVSAvoidSession management complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The UE maintains a pre-configured 'not to be used' list that stores rejected PDU session type and session attributes combinations. By having this list prepared in advance and consulting it before each establishment attempt, the UE efficiently avoids repeated rejections without adding significant runtime complexity to the session management process.

Inventive Principle:
Principle #10Preliminary action

3Adaptability or versatility

If the UE explores alternative session types and attributes after rejection, then the UE increases chances of successful establishment, but the session selection process becomes more complex

Engineering Contradiction:
ImproveSession type flexibilityVSAvoidRoute selection policy complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The UE segments the session selection process by dividing all possible PDU session type and session attributes combinations into two categories: those to be tried and those marked 'not to be used' based on previous rejections. This segmentation allows the UE to systematically explore alternative session types while following a structured approach, reducing the perceived complexity through organized management of session options.

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS20250142657A1URSP evaluation for unknown PDU session type
Publication Date: 2025.05.01 NOKIA TECHNOLOGIES OY
  • US20250142657A1 patent drawing
  • US20250142657A1 patent drawing
  • US20250142657A1 patent drawing

AI summary

A UE transmits a first message including a request to establish communication based on a first communication session type and a first set of one or more session attributes associated with the first message. The UE receives a second message including an indication that the request to establish communication using the first communication session type is rejected. After receiving the second message, the UE removes from use, a retransmission of the first communication session type and the first set of one or more session attributes for establishing communication, and transmits a third message including a request for communication based on a second communication session type and a second set of one or more session attributes, associated with the third message. A combination of the first communication session type and the first set, is not identical to a second combination including the second communication session type and the second set.