5G Service Function Chaining via NEF User Plane Capability Exposure

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current 3GPP standards do not allow third parties to request or utilize specific service function chaining for their applications beyond the (S)Gi interface, limiting the flexibility and functionality of service function chaining in 5G networks.

Innovation Solution

A new API is introduced in the Nnef northbound interface that enables Application Functions (AFs) to request and manage User Plane (UP) capabilities, allowing for service function chaining on a per application and per user session basis, facilitating the configuration and control of UP capabilities through the Network Exposure Function (NEF) and network entities.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If service function chaining is limited to the (S)Gi interface as per current 3GPP specifications, then the system maintains architectural simplicity and defined scope, but third parties cannot request specific service function chaining for their applications, reducing service flexibility and adaptability

Engineering Contradiction:
Improveservice provisioning flexibilityVSAvoidsystem architecture complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent introduces a Service Chain Selection Function (SCSF) as an intermediary component that mediates between Application Functions and the core network. The SCSF receives service function chaining requests from third-party applications, processes them according to network policies, and translates them into appropriate network configurations. This intermediary enables flexible third-party service requests without requiring direct modifications to the core network architecture, thus resolving the contradiction between adaptability and complexity.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Adaptability or versatility

If the N6-LAN interface is excluded from service function chaining scope as stated in TS 22.101, then the specification remains manageable and implementation is simplified, but User Plane capabilities cannot be accessed by third parties, limiting service customization options

Engineering Contradiction:
ImproveUser Plane capability accessVSAvoidspecification complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent segments the service function chaining capability into two distinct parts: control plane functions (handled by SCSF and existing network elements) and user plane functions (handled by UPF and N6-LAN elements). This segmentation allows third-party access to User Plane capabilities through the N6-LAN interface while keeping the control plane architecture intact and manageable. The separation enables independent optimization and configuration of each segment, resolving the contradiction between adaptability and specification complexity.

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS12621641B2Service function chaining exposure in 5G networks
Publication Date: 2026.05.05 TELEFONAKTIEBOLAGET LM ERICSSON (PUBL)
  • US12621641B2 patent drawing
  • US12621641B2 patent drawing
  • US12621641B2 patent drawing

AI summary

There is provided a computer-implemented method for enabling an Application Function (AF) to request User Plane capabilities of a Mobile Network Operator (MNO). The method comprises requesting, by the AF from a Network Exposure Function (NEF), one or more UP capability groups for a first application identifier (App-ID) and/or one or more UP capabilities for the first App-ID, providing, from the NEF to a network entity, information associated with the one or more UP capability groups for the first App-ID and/or one or more UP capabilities for the first App-ID, storing, at the network entity, the one or more UP capability groups for the first App-ID and/or one or more UP capabilities for the first App-ID; and providing an indication from the NEF to the AF to indicate that the request has been accepted.