Unified NEF Interface for 5G Infrequent Data

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

5G telecommunications networks face challenges in supporting infrequent small data communication between low-powered user equipment and application functions, particularly in roaming scenarios and across multiple network slices with different deployment models, leading to difficulties in maintaining consistent data delivery paths.

Innovation Solution

A unified interface is established via a network exposure function (NEF) that switches between non-IP and IP data delivery paths, using N33/T8, N6 point-to-point tunnel, and N6 interfaces, allowing seamless communication regardless of the data delivery path or plane, with the NEF functioning as a PDU session anchor and monitoring packet traffic.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If multiple different data delivery paths and interfaces are used to support various deployment models, then adaptability to different network configurations is improved, but device complexity and difficulty of operation increase

Engineering Contradiction:

Improveadaptability to different deployment modelsVSAvoidinterface complexity

Core Design Contradiction:

Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The Network Exposure Function (NEF) serves as an intermediary between the Application Function (AF) and the 5G core network. It provides a unified T8/N33 interface that abstracts the complexity of multiple data delivery paths (NIDD via control plane, NIDD via user plane with UPF, and IP data delivery). The AF interacts only with the NEF through this single interface, while the NEF handles the complexity of selecting and managing appropriate data delivery paths based on network configuration and deployment model.

Inventive Principle:

Principle #24Intermediary (Mediator)

Solution Approach 2:

The NEF implements a universal T8/N33 interface that can handle multiple types of data delivery paths and deployment models through a single unified interface. This interface supports both mobile originated (MO) and mobile terminated (MT) messages regardless of the underlying data delivery path, making the AF interface agnostic to the specific network configuration or deployment model being used.

Inventive Principle:

Principle #6Universality (Multi-functionality)

2Ease of operation

If a unified interface is implemented to simplify communication, then ease of operation is improved, but adaptability to different network configurations may be reduced

Engineering Contradiction:

Improveinterface usabilityVSAvoidsupport for multiple deployment models

Core Design Contradiction:

Ease of operationVSAdaptability or versatility

Solution Approach 1:

The NEF acts as a mediator that maintains a simple unified T8/N33 interface for the AF while simultaneously supporting multiple deployment models and data delivery paths. The NEF's internal logic adapts to different network configurations (roaming scenarios, network slices, home vs. visited network capabilities) without requiring the AF to change its interface or know about these configurations.

Inventive Principle:

Principle #24Intermediary (Mediator)

Solution Approach 2:

The system segments the complexity management function into the NEF, separating the simple unified interface layer (T8/N33) from the complex path selection and management layer. This segmentation allows the AF to use a simple interface while the NEF handles the adaptation to different deployment models, network slices, and data delivery path selections in the background.

Inventive Principle:

Principle #1Segmentation

3Adaptability or versatility

If multiple data delivery planes are supported, then adaptability to different network scenarios is improved, but difficulty of detecting and measuring increases

Engineering Contradiction:

Improvesupport for roaming and network slicesVSAvoidpath selection complexity

Core Design Contradiction:

Adaptability or versatilityVSDifficulty of detecting and measuring

Solution Approach 1:

The NEF implements feedback mechanisms to monitor the status and capabilities of different data delivery paths. It receives PDU session event change notifications from the SMF and uses this feedback to determine the appropriate data delivery path. The NEF can detect changes in network configuration, roaming status, and slice capabilities, and automatically adjusts the data delivery path selection based on this feedback without requiring complex manual configuration or measurement.

Inventive Principle:

Principle #23Feedback

Data Source

PatentEP4256825B1Methods systems, and computer readable media for providing a unified interface configured to support infrequent data communications via a network exposure function

Publication Date: 2024.12.04 ORACLE INT CORP

Figure 1
Figure 2
Figure 3

AI summary

Methods, systems, and computer readable media for providing a unified interface that is configured to support communication between a user equipment (UE) and application function (AF) via a network exposure function (NEF) are disclosed. One method includes receiving, by a NEF and from a session management function (SMF), a protocol data unit (PDU) session event change notification message associated with a UE, establishing, by the NEF, a data delivery path between the UE and an application function (AF) via one of a plurality of data delivery planes that traverse the NEF in response to the PDU session event change notification message and processing, by the NEF, messages communicated between the UE and the AF over any of the plurality of data delivery planes using a single unified interface supported by the NEF.