NEF Third-Party Service Exposure for Secure Network Integration
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing network architectures lack efficient methods for managing third-party services, such as AI and perception services, which are provided by external entities, leading to security risks and limited network service richness.
Innovation Solution
Implementing a third-party service management method through Network Exposure Function (NEF) and Network Repository Function (NRF) elements to manage and register/cancel third-party services, ensuring authorization and secure service exposure.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If third-party services are integrated into the network architecture, then network service richness is improved, but security risks increase
Solution Approach 1:
The patent introduces the NEF element as an intermediary between third-party service providers and the core network. The NEF receives service exposure requests from third parties, performs authorization verification, and selectively exposes non-sensitive network capabilities while filtering out security risks. This mediator approach allows the network to benefit from third-party services while maintaining security control.
Solution Approach 2:
The patent segments the service management functionality by introducing dedicated network elements (NEF and NRF) that handle third-party service management separately from the core network operations. This segmentation isolates potential security risks to specific components while allowing the rest of the network to continue operating securely. The NRF maintains a separate service registry for third-party services, further compartmentalizing the architecture.
2Adaptability or versatility
If existing network architecture is used without third-party service management mechanisms, then system complexity is low, but ability to manage third-party services is insufficient
Solution Approach 1:
The NEF element performs multiple functions: it acts as an authorization gateway for third-party services, manages service exposure policies, verifies service requests, and coordinates with the NRF for service registration. By consolidating these diverse functions into a single multi-functional element, the patent adds third-party service management capability without proportionally increasing overall system complexity.
Solution Approach 2:
The NRF automatically manages the service registry by receiving service information from the NEF and maintaining updated records of available third-party services. This self-service mechanism reduces the need for manual configuration and complex management procedures, allowing the system to scale with third-party services without linearly increasing operational complexity.
Data Source
AI summary
A third-party service management method includes: receiving a first management request for managing a third-party service sent by an application function (AF) element, in which, the first management request indicates the third-party service that is provided by a third-party application; managing the third-party service based on the first management request; and sending a management result to the AF element.