Aggregated NF Service Registration for Alternate Callback Routing
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In 5G telecommunications networks, using a single service name in binding information for alternate routing can prevent discovery of network functions (NFs) when some of their services are available, leading to network latency and inefficiencies.
Innovation Solution
Implementing a network function (NF) that registers an aggregated service name representing multiple service types with the NRF, allowing it to maintain a registered status as long as any service remains available, and communicate this aggregated service name for binding information, enabling alternate routing even when individual services become unavailable.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Device complexity
If a single service name is used in binding information for alternate routing, then the routing information is simple and easy to manage, but the discovery of network functions is prevented when some services are unavailable
Solution Approach 1:
The patent segments the service name into multiple individual service names, each representing a specific service type provided by the network function. Instead of using a single aggregated service name, the system now uses multiple distinct service names (e.g., service name 1, service name 2, service name 3) in the binding information. This segmentation allows the consumer NF to discover the producer NF through any available service, resolving the contradiction by maintaining discovery reliability while keeping each individual service name simple and manageable.
2Reliability
If multiple service names are used in binding information, then the discovery reliability is improved, but the complexity of routing information increases
Solution Approach 1:
The patent applies universality by making the binding information multi-functional - it can serve multiple service types simultaneously. The producer NF registers multiple service names (service name 1, service name 2, service name 3) that all point to the same NF instance, allowing the binding information to universally represent different service types. This reduces the need for separate routing information for each service, as a single binding entry with multiple service names can handle all service types, thereby improving reliability without proportionally increasing complexity.
3Loss of information
If a single service name is used, then the binding information is concise, but network latency increases when services become unavailable
Solution Approach 1:
The patent applies preliminary action by pre-registering multiple service names with the NRF before any service unavailability occurs. The producer NF proactively registers service name 1, service name 2, and service name 3 in advance, so that when a service becomes unavailable, the consumer NF can immediately use an alternative service name for discovery without experiencing latency. This preliminary preparation of multiple discovery paths eliminates the time penalty that would otherwise occur when services fail.
4Duration of action of stationary object
If aggregated service name is used, then the registered status is maintained longer, but the precision of service identification is reduced
Solution Approach 1:
The patent applies local quality by making each service name specific to its particular service type while maintaining the overall NF profile. Instead of using one generic aggregated service name that lasts longer, the system uses multiple specific service names (service name 1 for service type 1, service name 2 for service type 2, etc.). Each service name maintains high identification precision for its specific service, and the NF can maintain registration status through any available service, thus achieving both local precision and extended duration through the combination of multiple specific identifiers.
Data Source
AI summary
A method for service aggregation for alternate routing of callback messages includes registering, by an NF and with an NRF, an NF profile of the NF including an aggregated service name representing a plurality of different service types provided by the NF. The method further includes receiving, by the NF, requests from consumer NFs relating to the different service types. The method further includes obtaining, by the NF, and in response to the requests from the consumer NFs, resource information from a producer NF, re-using the resource information to respond to the requests, and communicating the aggregated service name to the producer NF as binding information. The method further includes maintaining, by the NF, a registered status of the aggregated service name with the NRF as long as any of the service types remain available at the NF.