NF Service Discovery Correlation in Subscriber Call Flow Tracing
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing call tracing tools cannot stitch network function (NF) service discovery procedures into call flows due to the absence of subscriber-specific parameters, leading to incomplete call flow analysis and delayed issue resolution.
Innovation Solution
A technique to determine a best match NF service discovery procedure by correlating subscriber-specific identifiers with NF service discovery procedures using hostnames, parameters, or values, enabling the stitching of an end-to-end call flow trace.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Device complexity
If NF service discovery procedures are excluded from call flow stitching due to absence of subscriber-specific parameters, then tracing tool complexity is reduced, but call flow analysis completeness deteriorates
Solution Approach 1:
The patent introduces hostname correlation as an intermediary mechanism to bridge NF service discovery procedures and subscriber-specific call flows. By using hostnames as a common reference point that appears in both types of procedures, the system can indirectly associate service discovery procedures with specific subscribers without requiring subscriber-specific parameters within those procedures themselves.
Solution Approach 2:
The patent makes hostnames serve multiple functions: they act as identifiers in subscriber-specific call flow procedures and simultaneously as correlation keys for NF service discovery procedures. This universal use of hostnames across different procedure types enables unified call flow analysis without modifying the original procedures.
2Productivity
If manual data mining of stored network traffic is required to obtain NF service discovery procedures, then automated tracing is simplified, but issue resolution time increases
Solution Approach 1:
The patent performs preliminary correlation between hostnames in call flow procedures and hostnames in NF service discovery procedures during the tracing process itself. This preliminary action eliminates the need for subsequent manual data mining of stored network traffic, as all necessary correlations are already established when the trace data is initially captured and processed.
3Reliability
If subscriber-specific parameters are used for stitching call flows, then call flow traceability by IMSI or MSISDN is enabled, but NF service discovery procedures cannot be included due to parameter absence
Solution Approach 1:
The patent uses hostnames as an intermediary that allows NF service discovery procedures to be associated with subscriber-specific call flows indirectly. This intermediary approach maintains the integrity of subscriber-specific traceability while enabling the inclusion of procedures that originally lacked subscriber-specific parameters.
Solution Approach 2:
The patent transitions from a single-dimension approach (direct subscriber-specific parameters) to a two-dimension approach by introducing hostname correlation as an additional dimension. This allows procedures to be associated with subscribers through a secondary correlation path, expanding the versatility of which procedures can be included in stitched call flows.
Data Source
AI summary
Described herein are computing device(s) configured to identify first hostnames, parameters, or values for each call leg included in a call flow trace associated with a subscriber-specific identifier. The computing device(s) may also be configured to identify second hostnames, parameters, or values from network function (NF) service discovery procedures based on the first hostnames, parameters, or values and determine a best match NF service discovery procedure for the call flow trace based on correlation(s) between the first hostnames, parameters, or values and the second hostnames, parameters, or values.