UPF PFCP Association Release Signaling Optimization

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

The existing UPF initiated PFCP Association Release procedure is inefficient and difficult to implement, particularly due to the challenges in managing Graceful Release Periods and handling zero usage reports, which can lead to lost usage reports and prolonged signaling processes.

Innovation Solution

A new process for UPF initiated PFCP association release is introduced, which includes exchanging support for an enhanced UP initiated PFCP association release mechanism during the PFCP Association Setup Procedure. This process involves sending PFCP Session Report Requests with indicators and non-zero usage reports, followed by a PFCP Association Update Request to initiate the association release, ensuring all non-zero usage reports are sent before deleting sessions.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If the existing UPF initiated PFCP Association Release procedure is used, then the association release can be initiated, but usage reports may be lost and signaling processes are prolonged

Engineering Contradiction:

Improveusage report deliveryVSAvoidsignaling process duration

Core Design Contradiction:

ReliabilityVSLoss of time

Solution Approach 1:

The patent applies preliminary action by requiring the UPF to send all usage reports for affected PFCP sessions to the CP function before initiating the association release procedure. This ensures that usage data is delivered before the association is torn down, preventing loss of usage reports while maintaining efficient signaling flow.

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The patent segments the association release process into distinct phases: first completing all usage report deliveries for affected sessions, then initiating the actual association release. This segmentation allows usage reports to be handled separately and ensures they are not lost during the release process.

Inventive Principle:

Principle #1Segmentation

2Ease of operation

If Graceful Release Period is implemented, then release timing can be controlled, but implementation complexity increases

Engineering Contradiction:

Improverelease timing controlVSAvoidprocedure implementation

Core Design Contradiction:

Ease of operationVSDevice complexity

Solution Approach 1:

The patent extracts the Graceful Release Period concept from the standard PFCP association release procedure and applies it specifically to UPF-initiated releases. By taking out this timing control mechanism and integrating it into the UPF's release initiation process, the patent provides release timing control without requiring complex modifications to the overall PFCP protocol architecture.

Inventive Principle:

Principle #2Taking out (Extraction)

3Productivity

If zero usage reports are handled in existing procedure, then all sessions are processed uniformly, but unnecessary signaling occurs

Engineering Contradiction:

Improvesignaling efficiencyVSAvoidsession handling flexibility

Core Design Contradiction:

ProductivityVSAdaptability or versatility

Solution Approach 1:

The patent applies partial action by requiring usage reports to be sent only for PFCP sessions that have non-zero usage, rather than uniformly for all sessions. This optimization reduces unnecessary signaling for sessions with no usage while maintaining complete usage reporting for sessions that have transmitted data, thus improving signaling efficiency without sacrificing versatility.

Inventive Principle:

Principle #16Partial or excessive action

Data Source

PatentUS12213207B2Enhanced up function requested PFCP association release

Publication Date: 2025.01.28 TELEFONAKTIEBOLAGET LM ERICSSON (PUBL)

AI summary

Embodiments of a method performed in a User Plane Entity (UPE) in a core network to perform a user plane initiated Packet Forwarding Control Protocol (PFCP) association release procedure are provided. In some embodiments, the method comprises, for each affected PFCP session, sending, to a Control Plane Entity (CPE), a PFCP session report request comprising an indicator that the PFCP session is being removed and one or more usage reports for the PFCP session, and deleting the PFCP session. The method further comprises sending, to the CPE, a PFCP association update request comprising information that indicates that the PFCP association update request is to initiate release of the PFCP association and an indicator that all non-zero usage reports for the affected PFCP session(s) have been reported. The method further comprises receiving, from the CPE, a PFCP association release request and sending, to the CPE, a PFCP association release response.