Edge-Core NEF Slice Architecture for Local Low-Latency Services
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing wireless communication networks lack effective integration and efficient deployment of Network Exposure Functions (NEFs) to provide local and low-latency services to user equipment, leading to suboptimal performance in delivering data services.
Innovation Solution
The implementation of a Network Exposure Function (NEF) slice that includes an edge NEF element coupled to a core NEF element, selected based on the geographic location of user equipment, allowing for efficient integration with wireless network slices and providing local, low-latency services through an Access and Mobility Management Function (AMF) and Session Management Function (SMF) selection of NEF addresses, with User Plane Function (UPF) facilitating API exchanges.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Device complexity
If NEFs are centrally deployed in network data centers, then network management is simplified, but service latency increases and local service delivery is suboptimal
Solution Approach 1:
The NEF is segmented into two distinct components: a centralized core NEF and distributed edge NEFs. The core NEF handles overall management and coordination, while edge NEFs are deployed at network edges closer to user equipment to provide low-latency local services. This segmentation resolves the contradiction by distributing functionality to reduce latency while maintaining centralized oversight for manageable complexity.
Solution Approach 2:
The architecture transitions from a single-dimensional centralized deployment to a multi-dimensional hierarchical structure. The core NEF operates at the network core level while edge NEFs operate at the network edge level, creating vertical dimensionality. This allows the system to simultaneously achieve centralized management benefits and distributed low-latency service delivery by operating at different network dimensions.
2Loss of time
If NEFs are distributed at network edges, then service latency is reduced, but network integration complexity increases
Solution Approach 1:
The core NEF serves as an intermediary between edge NEFs and other network elements. It manages the complexity of integrating multiple distributed edge NEFs by providing a centralized coordination point that handles interconnections, resource allocation, and cross-edge communication. This intermediary approach allows edge NEFs to be distributed for low latency while the core NEF absorbs the integration complexity.
Solution Approach 2:
The core NEF is designed with multi-functional capabilities to handle diverse tasks: managing multiple edge NEFs, coordinating with AMF/SMF/UPF, providing fallback services, and handling inter-edge communication. This universality consolidates multiple functions into a single centralized entity, reducing the overall integration complexity despite the distributed edge architecture.
3Device complexity
If a single NEF serves all UEs, then network element count is minimized, but service localization and performance optimization are limited
Solution Approach 1:
The system implements local quality by deploying edge NEFs with specific functional characteristics optimized for local service delivery. Each edge NEF is positioned geographically close to specific user equipment and can be configured with location-aware service capabilities. This allows the network to provide localized services with optimized performance for specific regions while maintaining an overall manageable architecture through the core NEF.
Data Source
AI summary
A wireless communication network serves a Network Exposure Function (NEF) slice to User Equipment (UE). An Access and Mobility Management Function (AMF) selects a NEF slice for the UE. A Session Management Function (SMF) selects a NEF address for the NEF slice for the UE. A User Plane Function (UPF) exchanges Application Programming Interface (API) calls and responses between the UE and a NEF based on the NEF address. The NEF exchanges the API messages with the UE over the UPF. The NEF slice may comprise an edge NEF slice that is selected based on the geographic location of the UE and that features a local NEF element that is coupled to a core NEF element.