5G Core Default Notification Routing via SCP Binding Indications
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In the context of 5G Core Network Function (NF) communication, there is a challenge in efficiently delivering notifications to default notification subscriptions due to the lack of standardized callback Uniform Resource Identifiers (URIs) and inadequate mechanisms for selecting or reselecting target NF consumers when failures occur, especially in indirect communication with delegated discovery.
Innovation Solution
Incorporating a predetermined service path and parameters like N1 message class and N2 information class in notification requests, and utilizing binding indications associated with NF consumers, enables the Service Communication Proxy (SCP) to properly handle and reselect target NF consumers for delivering notifications to default subscriptions.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If indirect communication with delegated discovery is used, then service framework flexibility is improved, but notification delivery reliability deteriorates due to lack of standardized callback URIs and inadequate reselection mechanisms
Solution Approach 1:
The patent applies preliminary action by pre-registering binding indications (NF instance ID, NF set ID, service name) for default notification subscriptions before actual notification delivery. When the SCP receives a notification request, it can immediately use these pre-stored binding indications to select or reselect target NF consumers without needing to perform complex discovery procedures at notification time, thus ensuring reliable delivery while maintaining framework flexibility
Solution Approach 2:
The Service Communication Proxy (SCP) acts as an intermediary between NF producers and NF consumers. The SCP stores binding indications received from NF consumers during registration, and uses these bindings to route notification requests from NF producers to appropriate NF consumers. This intermediary mechanism enables reliable notification delivery in indirect communication scenarios without requiring standardized callback URIs from NF consumers
2Reliability
If binding indications are stored and used for target selection, then notification delivery reliability is improved, but device complexity increases due to additional storage and selection mechanisms
Solution Approach 1:
The patent changes the parameter representation from complex callback URIs to simplified binding indication parameters (NF instance ID, NF set ID, service name). These simplified parameters are easier to store, compare, and use for selection. The SCP maintains a registry of NF consumers with these binding indications, enabling reliable target selection through simple parameter matching rather than complex URI parsing and validation
Solution Approach 2:
The SCP creates and maintains copies of binding indication information received during NF consumer registration. Instead of requiring NF consumers to provide complete callback URI information, the SCP stores simplified copies of the essential binding parameters (NF instance ID, NF set ID, service name) that can be readily used for notification routing and reselection operations
Data Source
Figure 1A~2
Figure 3~4
Figure 5~6
AI summary
The present disclosure provides a method (200) in a Network Function, NF, producer. The method (200) includes transmitting (210), 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.