UDM Node Managing Redundant PDU Session Pairing

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The existing 5G core network struggles to support high-speed, ultra-wide band services due to difficulty in accommodating low latency and high reliability requirements, particularly in scenarios like autonomous driving and factory automation, where conventional LTE networks fall short with latency exceeding 1 ms.

Innovation Solution

A method is introduced to manage redundant protocol data unit (PDU) sessions through a unified data management node, which receives and transmits redundancy sequence numbers and PDU session IDs between session management function nodes to ensure disjoint user plane paths for redundant PDU sessions, facilitating dual connectivity and improved network reliability.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If redundant PDU sessions are managed by multiple SMF nodes independently, then each SMF can allocate redundancy sequence numbers autonomously, but the SMF nodes cannot identify the pairing relationship between redundant PDU sessions

Engineering Contradiction:
Improveautonomous RSN allocationVSAvoidpairing relationship information
Core Design Contradiction:
Ease of operationVSLoss of information

Solution Approach 1:

The UDM node serves as an intermediary between multiple SMF nodes, centralizing the storage and management of PDU session pairing relationships. When an SMF node creates a redundant PDU session, it registers the pairing relationship with the UDM node. This intermediary approach allows SMF nodes to autonomously allocate RSNs while the UDM node maintains the global view of pairings, resolving the contradiction between autonomous operation and information availability.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Device complexity

If the core network uses conventional LTE architecture, then the network structure is simple and well-established, but it cannot accommodate low latency and high reliability requirements for ultra-wide band services

Engineering Contradiction:
Improvenetwork architecture simplicityVSAvoidservice reliability and latency
Core Design Contradiction:
Device complexityVSReliability

Solution Approach 1:

The patent segments the session management function into multiple independent SMF nodes, each capable of autonomously managing PDU sessions. This segmentation allows the network to handle multiple services with different reliability and latency requirements simultaneously. The UDM node provides centralized coordination for redundant sessions, enabling the network to meet ultra-reliable low-latency communication requirements while maintaining architectural simplicity through functional separation.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces new parameters including redundancy sequence numbers (RSN) and PDU session pair IDs to enable identification and management of redundant PDU sessions. These parameter changes allow the network to differentiate between primary and redundant sessions, track their pairing relationships, and manage them appropriately, thereby achieving high reliability and low latency for ultra-wide band services while building upon the existing LTE architecture.

Inventive Principle:
Principle #35Parameter changes

Data Source

PatentUS11503483B2Method and apparatus for supporting redundant PDU sessions
Publication Date: 2022.11.15 LG ELECTRONICS INC
  • US11503483B2 patent drawing
  • US11503483B2 patent drawing
  • US11503483B2 patent drawing

AI summary

One disclosure of the present specification provides a method for supporting redundant protocol data unit (PDU) sessions. The method may be performed by a unified data management (UDM) node and comprise: receiving, from a first session management function (SMF) node, a first message including a first redundancy sequence number (RSN) which is allocated by the first SMF node for managing a first PDU session and an identifier of the first PDU session; transmitting, to a second SMF node for managing a second PDU session, a second message including the first RSN and a PDU session pair ID, which is identical to the identifier of the first PDU session; and receiving, from the second SMF node, a third message including a second RSN which is allocated by the second SMF node and an identifier of the second PDU session. The second PDU session may be duplication of the first PDU session.