ULCL Network Function Selective Uplink Routing

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The 5G network specified by 3GPP faces inefficiencies in signaling load and User Plane (UP) performance due to the need for per PDU session configuration of Traffic Management (TM) functionality, leading to increased processing load, latency, and energy consumption, especially in use cases like Edge Computing where similar traffic rules apply to multiple sessions.

Innovation Solution

A service-based Uplink Classifier (ULCL) is introduced, which is not PDU session aware and can be configured based on parameters like App-IDs, subnetworks, and locations, allowing for selective routing of uplink data traffic through service-based interfaces, enabling efficient handling of traffic management actions for groups of PDU sessions.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If per PDU session configuration of Traffic Management functionality is implemented, then traffic routing control is achieved, but signaling load and processing complexity increase

Engineering Contradiction:
Improvetraffic routing controlVSAvoidsignaling load
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent segments the Traffic Management functionality by introducing a service-based ULCL that operates independently from PDU session configuration. The ULCL is configured once with filter criteria and automatically applies to multiple PDU sessions, dividing the configuration task from the session management task. This reduces signaling load while maintaining routing control.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The ULCL is configured in advance with filtering criteria (App-IDs, subnetworks, locations) before PDU sessions are established. This preliminary configuration allows the ULCL to automatically route traffic for multiple sessions without requiring per-session configuration, reducing signaling overhead and processing complexity.

Inventive Principle:
Principle #10Preliminary action

2Reliability

If per PDU session configuration of Traffic Management functionality is implemented, then traffic routing control is achieved, but processing load and latency increase

Engineering Contradiction:
Improvetraffic routing controlVSAvoidprocessing load
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent separates the routing decision logic from PDU session configuration by introducing a service-based ULCL entity. The ULCL maintains its own configuration with filter criteria and independently makes routing decisions for multiple PDU sessions, reducing the processing load on the PDU session configuration process and eliminating redundant operations.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The ULCL configuration serves as a template that is automatically applied to multiple PDU sessions. Instead of creating separate configuration instances for each session, the system copies the ULCL's filter criteria and routing rules to applicable sessions, significantly reducing processing load and configuration time.

Inventive Principle:
Principle #26Copying

3Reliability

If per PDU session configuration of Traffic Management functionality is implemented, then traffic routing control is achieved, but energy consumption increases

Engineering Contradiction:
Improvetraffic routing controlVSAvoidenergy consumption
Core Design Contradiction:
ReliabilityVSUse of energy by moving object

Solution Approach 1:

The patent segments the configuration management by introducing a service-based ULCL that operates independently from PDU session configuration. This segmentation eliminates redundant configuration operations across multiple sessions, reducing the computational energy required for processing and configuration management.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The ULCL is configured once in advance with comprehensive filter criteria that cover multiple PDU sessions. This preliminary configuration avoids repeated configuration operations for each session, significantly reducing the energy consumption associated with processing and configuration management.

Inventive Principle:
Principle #10Preliminary action

4Productivity

If service-based ULCL with filter criteria is introduced, then routing efficiency is improved, but device complexity increases

Engineering Contradiction:
Improverouting efficiencyVSAvoidconfiguration complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The service-based ULCL is designed as a universal entity that handles multiple functions: it filters traffic based on App-IDs, subnetworks, and locations, and automatically applies routing rules to multiple PDU sessions. This multi-functionality consolidates what would otherwise require multiple separate configuration mechanisms, improving routing efficiency without proportionally increasing complexity.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Solution Approach 2:

The ULCL acts as an intermediary between the configuration system and PDU sessions. It receives filter criteria and routing rules, processes them against incoming traffic, and makes routing decisions without requiring direct configuration of each PDU session. This intermediary role simplifies the overall system architecture while improving routing efficiency.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS11979927B2Registering and configuring a network function for selectively routing uplink data traffic
Publication Date: 2024.05.07 TELEFONAKTIEBOLAGET LM ERICSSON (PUBL)
  • US11979927B2 patent drawing
  • US11979927B2 patent drawing
  • US11979927B2 patent drawing

AI summary

An aspect provides a method by user plane function (UPF) in a core network (CN) of a communication network for registering the UPF at a network repository function (NRF) of the CN. The UPF is to selectively route uplink data traffic in one or more data sessions from a user equipment (UE) to one of a plurality of session anchor network functions (NFs). The method by the UPF comprises sending (1701) a registration request to the NRF. The registration request comprises registration information comprising an indication of a type of filter supported by the UPF to selectively route uplink data traffic from a UE to a particular session anchor NF. The type of filter relates to an application identity; and an indication of a value for the indicated type of filter.