5G SA Core Network UPF Selection via SMF Capability Query

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In 5G core networks, selecting a User Plane Function (UPF) capable of handling IPv4 requests is challenging, leading to failed connections when an UPF that only handles IPv6 traffic is selected, resulting in inefficient resource utilization and increased resource wastage due to failed attempts.

Innovation Solution

Implementing a centralized SMF status database that allows the Network Function Repository (NRF) to query and select a UPF capable of handling IPv4 requests, ensuring accurate and efficient handling of IPv4 traffic by verifying the capabilities of SMFs before establishing connections.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Speed

If a UPF is selected without verifying IPv4 capability, then connection establishment is faster, but connection failure rate increases due to incompatible UPF selection

Engineering Contradiction:
Improveconnection establishment speedVSAvoidconnection success rate
Core Design Contradiction:
SpeedVSReliability

Solution Approach 1:

The patent applies preliminary action by having the NRF query the SMF status database before UPF selection to obtain capability information in advance. This allows the system to pre-verify IPv4 capability compatibility, ensuring that only compatible UPFs are selected, thereby preventing connection failures before they occur while maintaining efficient connection establishment.

Inventive Principle:
Principle #10Preliminary action

2Productivity

If UPF capability verification is implemented, then resource utilization efficiency improves, but system complexity increases due to additional database queries and verification steps

Engineering Contradiction:
Improveresource utilization efficiencyVSAvoidsystem complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The patent introduces an intermediary approach by utilizing the existing SMF status database that already contains capability information. The NRF queries this pre-existing database rather than implementing complex real-time verification mechanisms, thereby obtaining necessary capability information with minimal additional system complexity while improving resource utilization efficiency.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Reliability

If IPv4 capability verification is performed before UPF selection, then failed connection attempts are reduced, but query time increases due to additional database lookups

Engineering Contradiction:
Improveconnection success rateVSAvoidquery time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent applies preliminary action by having capability information pre-stored in the SMF status database. The NRF performs quick lookups in this pre-prepared database rather than conducting time-consuming real-time verification, thereby minimizing query time while ensuring reliable UPF selection with verified IPv4 capability.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS20240205664A1Redirection of traffic instance identification in a 5g sa core network
Publication Date: 2024.06.20 T MOBILE US INC
  • US20240205664A1 patent drawing
  • US20240205664A1 patent drawing
  • US20240205664A1 patent drawing

AI summary

System and methods for efficient user plane function (UPF) selection are described. A mobile device (UE) may transmit a connection request to a 5G core network. The connection request can include an indication that the type of data to be serviced is IPv4-type traffic. The access management function (AMF) receives the request from a base station (e.g., gNodeB) and queries a network function repository function (NRF) for an identification of a session management function (SMF). The selected SMF queries a session management function datastore. If the SMF selected by the NRF is capable of IPV4 traffic, the identification of the SMF is returned to the AMF. If the SMF is not capable of IPV4 traffic, the identification of a capable SMF using the information received in the SMF status datastore is returned to the AMF through a 308 code. The mobile device is thereafter connected to the capable UPF.