Network Exposure Function for External Service Bridging
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current 5G systems have limited capabilities for exposing network resources and services from external network entities, leading to inflexible parameter provisioning, inefficient communication, long latency, and restricted service exposure.
Innovation Solution
The proposed solution involves network entities that facilitate the registration and bridging of services between external network entities and the 5G network, using a registration service to create a clone of the external service and a transfer service to manage service traffic.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If external network entities provide services to the 5G network, then network capability and service quality are improved, but service exposure is restricted and communication efficiency deteriorates
Solution Approach 1:
The patent introduces a Network Exposure Function (NEF) as an intermediary between external network entities and the 5G core network. The NEF receives service requests from external entities, translates them into appropriate internal protocols, and manages service exposure through standardized interfaces. This mediator enables flexible service exposure while maintaining efficient internal communication by handling protocol conversion and authentication centrally.
Solution Approach 2:
The NEF is designed as a universal function that handles multiple types of service exposures including event exposure, parameter provisioning, trigger invocation, and analytics data exposure. By consolidating these diverse service exposure functions into a single multi-functional entity, the system achieves both adaptability for different service types and efficiency through centralized management.
2Adaptability or versatility
If parameter provisioning is implemented for external entities, then service customization is improved, but flexibility deteriorates due to pre-configuration requirements
Solution Approach 1:
The patent implements dynamic parameter provisioning where the NEF can modify service parameters in real-time based on network conditions and service requirements. Instead of static pre-configuration, the system allows parameters to be updated dynamically through service requests, enabling both customization and flexibility. The NEF manages parameter lifecycles including creation, modification, and deletion without requiring system reconfiguration.
3Adaptability or versatility
If service traffic is bridged between external entities and network entities, then service integration is improved, but latency increases
Solution Approach 1:
The patent implements service registration and subscription mechanisms where external entities and network entities pre-establish service relationships before actual service delivery. The NEF maintains subscription information and service context in advance, so when service requests occur, the bridging can proceed directly without setup delays. This preliminary action reduces latency while maintaining integration capability.
4Adaptability or versatility
If network capabilities are exposed externally, then service quality is improved, but system complexity increases
Solution Approach 1:
The patent extracts the complexity of capability exposure management from individual network functions and consolidates it into the dedicated NEF. The NEF handles authentication, authorization, protocol translation, and service management externally, allowing core network entities to maintain simple, standardized interfaces. This extraction reduces system architecture complexity while enabling comprehensive capability exposure.
Data Source
AI summary
The present disclosure relates to external services provided to a network. One example method includes: obtaining a clone service invocation request from an other network entity, wherein the clone service invocation request includes clone service invocation information of a clone of a service provided by an external network entity, and providing a service invocation request to the external network entity, wherein the service invocation request includes service invocation information.