Flexible NF Instance Identification in 5G Core Networks
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current identification methods in 5G core networks and other communication networks are inflexible, limiting the ability to integrate different types of services across heterogeneous environments and operator domains.
Innovation Solution
The introduction of a flexible framework for identifying Network Functions (NFs) using a combination of a string and a type for the NFInstanceID, which can support multiple identity types such as UUID and SPIFFE, allowing for enhanced service identification and integration.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If a single fixed identification method (e.g., UUID only) is used for Network Functions, then the identification system is simple and consistent, but the system lacks flexibility to integrate different types of services across heterogeneous environments and operator domains
Solution Approach 1:
The NFInstanceId is designed to support multiple identity types (UUID, SPIFFE, and custom types) within a single identification framework. The type field indicates which identification scheme is being used, allowing the system to universally handle different service types and heterogeneous environments through one unified mechanism rather than requiring separate identification systems for each type.
Solution Approach 2:
The NFInstanceId is segmented into two distinct parts: a type indicator and a value component. This segmentation allows the system to separately manage the identification scheme selection (type) and the actual identification data (value), providing flexibility in choosing different identification methods while maintaining a consistent overall structure.
2Adaptability or versatility
If traditional identification methods are used, then the current system operates reliably with established protocols, but the ability to support future network functions and services is limited
Solution Approach 1:
The identification framework is made dynamic by allowing the type field to indicate different identification schemes (UUID, SPIFFE, custom types). This enables the system to adapt to future network functions and services by introducing new identification types as needed, while existing types continue to operate reliably based on established protocols.
Solution Approach 2:
The system changes the parameter of identification type from a fixed single value to a selectable category. By modifying the type field to accept different values (UUID, SPIFFE, custom), the system can transition between different identification methodologies while maintaining the same overall NFInstanceId structure, ensuring both future adaptability and current reliability.
3Adaptability or versatility
If multiple identity types are supported in NFInstanceID, then service identification and integration across diverse environments is enhanced, but the complexity of managing different identity types increases
Solution Approach 1:
The type field acts as an intermediary that mediates between different identity types and the rest of the system. By indicating which identification scheme is being used, the type field allows various identity types (UUID, SPIFFE, custom) to coexist without requiring the entire system to be aware of or handle each specific type's complexities, thus enhancing service identification while managing complexity.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
According to an example aspect of the present invention, there is provided a method comprising receiving, by a network repository function, a request from a network function, wherein the request comprises a string associated with an instance identity of the network function, determining, by the network repository function, a type of the instance identity of the network function from a set of instance identity types, determining, by the network repository function, the instance identity of the network function based on the string associated with the instance identity of the network function and the type of the instance identity of the network function and transmitting, by the network repository function, a response to the network function, wherein the response depends on whether the instance identity of the network function was found in a list of network function instances registered at the network repository function.