Removing Application Identifiers in 5G User Plane Entities

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The existing methods for removing an application identifier in a 5G network are complex and require significant signaling, leading to misalignment of data between policy control, session management, and user plane functions, impacting ongoing sessions.

Innovation Solution

A method and system where the user plane entity determines the need to stop tracking data packet flows identified by an application identifier, removes associated detection filters, and requests the session control entity to remove packet detection rules, ensuring consistency across policy and charging control entities by updating relevant rules.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If the existing method for removing an application identifier is used, then the application identifier can be removed, but the signaling complexity increases and data misalignment occurs between policy control, session management, and user plane functions

Engineering Contradiction:
Improvedata consistencyVSAvoidsignaling complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The session management function acts as an intermediary between the policy control function and the user plane function. When an application identifier needs to be removed, the session management function receives the request from the policy control function, coordinates the removal across all relevant packet detection rules, and ensures all entities are synchronized. This intermediary role prevents data misalignment and reduces signaling complexity by centralizing the coordination logic.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The system performs preliminary validation and coordination before actually removing the application identifier. The session management function first identifies all packet detection rules associated with the application identifier, prepares the removal sequence, and ensures all necessary entities are ready. This preliminary action prevents partial removals and data inconsistency, ensuring reliable data consistency across the network.

Inventive Principle:
Principle #10Preliminary action

2Ease of operation

If the application identifier is removed using the existing method, then the removal can be completed, but the impact on ongoing sessions increases

Engineering Contradiction:
Improveoperational flexibilityVSAvoidsession stability
Core Design Contradiction:
Ease of operationVSReliability

Solution Approach 1:

The removal process is segmented into multiple phases: identification of affected packet detection rules, validation of ongoing sessions, staged removal of rules, and verification of consistency. By segmenting the removal process, the system can maintain ongoing sessions that are not affected while selectively removing only the necessary packet detection rules, thereby reducing impact on session stability while maintaining operational flexibility.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system performs a partial removal action by selectively removing only the packet detection rules associated with the specific application identifier while leaving other rules intact. This partial action approach ensures that ongoing sessions using other application identifiers continue unaffected, maintaining session stability while achieving the operational flexibility needed to remove the specific application identifier.

Inventive Principle:
Principle #16Partial or excessive action

Data Source

PatentUS11849351B2Removal of application identifier
Publication Date: 2023.12.19 TELEFONAKTIEBOLAGET LM ERICSSON (PUBL)
  • US11849351B2 patent drawing
  • US11849351B2 patent drawing
  • US11849351B2 patent drawing

AI summary

A method for operating a user plane entity configured to handle a user plane of data packet sessions exchanged in a cellular network, each data packet session comprising data packet flows of a plurality of applications, the data packet flows of each application being identified by an application identifier, the method includes: determining that a tracking of data packet flows identified by an application identifier should be stopped, determining one or more application detection filters configured to detect data packet flows identified by the application identifier, removing the one or more application detection filters and the application identifier from the user plane entity, and requesting a session control entity configured to control the data packet sessions to remove packet detection rules usable to detect the data packet flows identified by the application identifier, wherein the request includes the application identifier.