UE-Level PFCP Session Handling for SGW Multi-PDN Buffering
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current specifications require separate PFCP sessions and buffers for each Packet Data Network (PDN) at the Serving Gateway (SGW), leading to inefficient management, incorrect distribution of downlink data, and complex signaling procedures due to PDN-level handling.
Innovation Solution
Implementing a UE-level PFCP session at the SGW, using a single PFCP session and Buffering Action Rule (BAR) for all PDNs, allowing centralized management and simplified signaling procedures.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If separate PFCP sessions are created for each PDN at SGW, then PDN-specific data handling is enabled, but device complexity and signaling complexity increase
Solution Approach 1:
The patent merges multiple PDN-specific PFCP sessions into a single UE-level PFCP session at the SGW. Instead of maintaining separate sessions for each PDN, the SGW establishes one session per UE and uses Packet Detection Rules (PDRs) to differentiate and handle data from different PDNs within that single session, thereby reducing session management complexity while preserving PDN-specific handling capabilities
Solution Approach 2:
The single UE-level PFCP session at the SGW is designed to serve multiple PDNs simultaneously. The session structure incorporates universal elements (PDRs, FARs, BARs) that can be dynamically applied to different PDN data flows, allowing the same session infrastructure to handle diverse PDN requirements without requiring separate sessions for each PDN
2Adaptability or versatility
If separate buffers are allocated for each PDN at SGW, then PDN-specific buffering control is achieved, but loss of substance and management overhead increase
Solution Approach 1:
The patent combines multiple PDN-specific buffers into a single UE-level buffer at the SGW. This single buffer is shared across all PDNs associated with the UE, and the SGW uses Packet Detection Rules to identify which PDN a downlink packet belongs to, ensuring accurate routing and distribution of data from the shared buffer to the appropriate PDN, thereby eliminating buffer management overhead while maintaining PDN-specific control
Solution Approach 2:
The Packet Detection Rule (PDR) acts as an intermediary mechanism between the single UE-level buffer and multiple PDNs. The PDR inspects incoming packets, identifies the source PDN, and directs packets to the appropriate destination, enabling the single buffer to serve multiple PDNs with accurate distribution without requiring separate buffers for each PDN
3Ease of operation
If PDN-level PFCP session handling is used, then detailed PDN control is possible, but signaling complexity and procedure complexity increase
Solution Approach 1:
The patent merges multiple PDN-level PFCP session management operations into a single UE-level session management process. Control plane messages (PFCP Session Establishment, Modification, Release) are exchanged once at the UE level, and the changes are applied uniformly across all PDNs associated with that UE, eliminating the need for repeated signaling for each PDN while maintaining the ability to control individual PDNs when needed
Data Source
AI summary
A method, system and computer readable medium for providing support for CUPS PFCP Session at UE Level for Serving Gateway are presented. In one embodiment, a method includes providing a Packet Forwarding Control Protocol (PFCP) session at a User Equipment (UE) level for a Serving Gateway (SGW); anchoring, by the SGW, the UE session; handling, by the SGW, buffering of Idle UE and UE Active-to-Idle transitions; using, by the SGW, a same PFCP session for all Packet Data Networks (PDNs); and using, by the SGW, a same Buffering Action Rule (BAR) for all PDNs.