NRF Slice-Level Load Prioritization for 5G NF Discovery
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In 5G telecommunications networks, the Network Function Repository Function (NRF) lacks network slice level load information of producer NFs, leading to incorrect prioritization of NF profiles in discovery responses, which can result in network slice overload and improper load balancing.
Innovation Solution
The System Control Plane (SCP) receives and reads network slice level load information from producer NFs via Service-Based Interface (SBI) messages, and communicates this information to the NRF using custom headers or information elements in NF update or heart-beat request messages, enabling the NRF to prioritize NF profiles based on slice level load.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Measurement precision
If the NRF prioritizes NF profiles based on NF instance level load attributes only, then the prioritization process is simple, but the NRF cannot accurately reflect network slice level loading conditions
Solution Approach 1:
The patent segments load information into two distinct levels: NF instance level load attributes and network slice level load attributes. This segmentation allows the NRF to maintain separate tracking of overall NF load and specific network slice load, enabling precise measurement of slice-level loading conditions without conflating them with general NF load status.
Solution Approach 2:
The patent adds a new dimension to load information by introducing network slice level load attributes alongside the existing NF instance level attributes. This dimensional expansion transforms the NRF's view from a single-level load perspective to a multi-dimensional load perspective, enabling accurate prioritization that considers both overall NF capacity and specific slice utilization.
2Reliability
If the NRF collects and processes network slice level load information from all producer NFs, then accurate prioritization is achieved, but the information management complexity and storage requirements increase
Solution Approach 1:
The patent makes the NRF multi-functional by enabling it to handle both NF instance level load information and network slice level load information through the same NF profile data structure. This universality allows the NRF to perform both traditional NF prioritization and new slice-level prioritization without requiring separate information management systems, thereby reducing overall complexity.
Solution Approach 2:
The patent implements preliminary action by having producer NFs proactively report their network slice level load attributes to the NRF during NF registration and updates. This advance reporting ensures the NRF has current slice load information available before making prioritization decisions, eliminating the need for complex real-time querying mechanisms.
3Reliability
If the NRF uses only NF instance level load attributes for prioritization, then the processing is straightforward, but network slice overload cannot be detected
Solution Approach 1:
The patent implements feedback mechanisms where producer NFs continuously report their network slice level load attributes to the NRF. This feedback loop ensures the NRF always has current information about slice-level loading conditions, enabling it to detect slice overload situations and adjust prioritization accordingly, preventing information loss about critical slice status.
4Reliability
If network slice level load information is not communicated to the NRF, then the current system architecture is maintained, but incorrect NF profile prioritization occurs leading to potential network outages
Solution Approach 1:
The patent enables producer NFs to self-report their network slice level load attributes to the NRF as part of their normal NF registration and update procedures. This self-service approach eliminates the need for complex centralized collection mechanisms, maintaining system operational simplicity while ensuring the NRF receives accurate slice load information for reliable prioritization.
Data Source
AI summary
A method for communicating and using producer network function (NF) network slice level load information includes receiving, by a service communication proxy (SCP) and from a producer NF, a service-based interface (SBI) message including producer NF network slice level load information. The method further includes reading, by the SCP and from the SBI message, the producer NF network slice level load information. The method further includes communicating, by the SCP and to an NF repository function (NRF), the producer NF network slice level load information. The method further includes storing, by the NRF, the producer NF network slice level load information. The method further includes using, by the NRF, the producer NF network slice level load information to generate a response message to be sent to a consumer NF or the SCP.