5G Core Network Node Notifications via SCP Target Reselection
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In the context of 5G Core network functions, existing methods for delivering notifications to default notification subscriptions in Network Function (NF) producers are inefficient due to the lack of standardized callback Uniform Resource Identifiers (URIs) and inadequate mechanisms for selecting or reselecting target NF consumers, especially in scenarios involving indirect communication with delegated discovery.
Innovation Solution
The proposed solution involves transmitting a notification request with a predetermined service path and optional parameters like N1 message class and N2 information class to a Service Communication Proxy (SCP), enabling the SCP to select or reselect a target NF consumer based on these parameters, and acquiring a callback URI from the NF profile of the target consumer.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If indirect communication with delegated discovery is used, then service flexibility and scalability are improved, but the mechanism for selecting or reselecting target NF consumers becomes inadequate and inefficient
Solution Approach 1:
The Service Communication Proxy (SCP) acts as an intermediary between the NF producer and target NF consumer. The SCP receives notification requests from the NF producer, performs discovery to identify suitable target NF consumers based on binding indications, and delivers notifications accordingly. This intermediary mechanism resolves the contradiction by providing automated target selection capabilities that maintain service flexibility while eliminating the inadequacy of manual or direct selection methods.
2Device complexity
If standardized callback URIs are not established, then system complexity is reduced, but notification delivery efficiency and reliability deteriorate
Solution Approach 1:
The patent introduces binding indication parameters (such as NF instance ID, NF set ID, service instance ID) that can be dynamically included in notification requests. These parameters enable the SCP to efficiently identify and select target NF consumers without requiring standardized callback URIs. By changing the approach from URI-based identification to parameter-based identification, the system maintains low complexity while achieving high notification delivery efficiency and reliability.
3Ease of operation
If binding indication is not used, then notification delivery simplicity is maintained, but the ability to handle failure and load balancing is insufficient
Solution Approach 1:
The binding indication is prepared in advance by the NF producer and included in the notification request before delivery. This preliminary action provides the SCP with all necessary information (NF instance ID, NF set ID, service instance ID) to perform intelligent target selection and reselection. By preparing the binding indication beforehand, the system maintains simple notification delivery procedures while enabling robust failure handling and load balancing capabilities through automated target reselection.
Data Source
AI summary
The present disclosure provides a method in a Network Function, NF, producer. The method includes transmitting, to a Service Communication Proxy, SCP, a notification request for delivering a notification. The notification request contains a Uniform Resource Identifier, URI, having a predetermined service path indicating that the notification request is associated with a default notification subscription.