NF Feature Negotiation via Repository-Based Default Subscriptions
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In the 3GPP 5G network, there is no mechanism for a Network Function (NF) producer to determine which optional features are supported by a Network Function (NF) consumer during default subscription creation, leading to notifications being sent with information elements that may not be supported by the consumer.
Innovation Solution
A method involving a service consumer invoking a management service to transmit a profile with default notification subscription information and feature support, and a service producer using a discovery service to determine supported features, allowing the NF producer to adjust notification content accordingly.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If the NF producer directly delivers notifications to the NF consumer without subscription creation message exchange, then the communication efficiency is improved, but the NF producer cannot know which optional features are supported by the NF consumer
Solution Approach 1:
The NF consumer performs preliminary action by including feature support information in the NF profile registration with the NRF before the NF producer discovers it. This allows the NF producer to obtain feature support information during the discovery phase without requiring additional subscription creation messages, thus maintaining communication efficiency while preventing information loss.
2Quantity of substance
If the NF producer sends notifications with all information elements, then the completeness of information is improved, but the NF consumer may receive information elements that are not supported
Solution Approach 1:
The system implements feedback mechanism where the NF consumer's supported features are registered with the NRF and discovered by the NF producer. The NF producer uses this feedback information to filter and customize notification content, including only those information elements that the NF consumer supports. This prevents harmful unsupported information elements from being sent while maintaining information completeness within supported scope.
3Measurement precision
If feature negotiation is performed through Subscription Creation Request and Response, then the feature support information is accurately exchanged, but the process complexity increases
Solution Approach 1:
The invention merges the feature negotiation function into the NF profile registration and discovery processes. Instead of separate subscription creation messages for feature negotiation, the feature support information is included in the NF profile registered with the NRF. The NF producer obtains this information during the standard discovery process, combining multiple functions into existing procedures and reducing overall process complexity while maintaining negotiation accuracy.
Data Source
AI summary
TS 29.500, usually the feature negotiation is done when the subscription is created by the NF consumer. P: For default notification subscriptions, the NF consumer registers the default subscriptions in NRF and NF producer discover and directly send the notification towards the callback URI without subscription creation procedure. S: NF to register the supported features in default subscription. The NF producer can get aware the supported feature of the NF consumer and adjust the notification accordingly. TS 29.510, API Version Control and feature negotiation between NF producer and NF consumer. In 5GC, a NF Producer may subscribe to another NF producer on behalf of the NF consumer with directly reporting. P: No way for the NF consumer to indicate the supported API version and features of the second NF producer which will directly report to the NF consumer. S: New header to allow the NF consumer to indicate the supported API version and features.