Multi-Domain SCP Routing Using Producer NF Lookup Headers
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In 5G telecommunications networks with multiple SCP domains, each SCP in the path from a consumer NF to a producer NF performs a reverse lookup to determine producer NF identification information, leading to processing delays and resource wastage due to repeated lookups.
Innovation Solution
A method and system for optimized multi-domain SCP routing that involves a first SCP performing a reverse lookup to determine producer NF identification information, modifying the SBI request to include this information, and routing it to a second SCP, using custom headers to avoid duplicate lookups by subsequent SCPs.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Measurement precision
If each SCP in the path performs a reverse lookup to determine producer NF identification information, then routing accuracy is improved, but processing time and resource consumption increase
Solution Approach 1:
The first SCP performs the reverse lookup in advance to obtain producer NF identification information (NF instance ID and service instance ID) before forwarding the request to subsequent SCPs. This preliminary action eliminates the need for repeated lookups by intermediate SCPs, reducing overall processing time while maintaining routing accuracy through the use of custom headers that carry the pre-obtained identification information
Solution Approach 2:
Custom headers are introduced as intermediaries to carry producer NF identification information between SCPs. Instead of each SCP independently performing lookups, the identification information is transmitted through these custom headers, allowing intermediate SCPs to forward requests without repeating the reverse lookup operation
2Measurement precision
If each SCP in the path performs a reverse lookup to determine producer NF identification information, then routing accuracy is improved, but network resource consumption increases
Solution Approach 1:
The first SCP performs the reverse lookup in advance to obtain producer NF identification information before forwarding the request to subsequent SCPs. This preliminary action eliminates the need for repeated lookups by intermediate SCPs, reducing overall processing time while maintaining routing accuracy through the use of custom headers that carry the pre-obtained identification information
Solution Approach 2:
Custom headers are introduced as intermediaries to carry producer NF identification information between SCPs. Instead of each SCP independently performing lookups, the identification information is transmitted through these custom headers, allowing intermediate SCPs to forward requests without repeating the reverse lookup operation
3Productivity
If producer NF identification information is included in custom headers, then lookup efficiency is improved, but message complexity increases
Solution Approach 1:
The custom headers serve multiple functions: they carry producer NF identification information for efficient routing, maintain backward compatibility with existing SCP implementations, and enable optimized multi-domain routing without requiring fundamental changes to the SBI request structure. This multi-functionality justifies the added complexity by providing significant performance benefits
Data Source
AI summary
A method for optimized multi-domain service communication proxy (SCP) routing includes receiving, at a first SCP, a service based interface (SBI) request for requesting service provided by a producer NF. The method further includes performing, by the first SCP, a reverse lookup to determine producer NF identification information. The method further includes modifying the SBI request to include the producer NF identification information. The method further includes determining an SCP domain of the producer NF. The method further includes routing the SBI request to a second SCP in a path for reaching the SCP domain of the producer NF.


