Distributed Correlation Engines for VoLTE QoS Monitoring
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In telecommunications networks, particularly in VoLTE environments, there is a challenge in correlating signaling call flows across different network interfaces due to the lack of a common identifier across all involved interfaces and protocols, limiting the possibilities for monitoring Quality of Service (QoS).
Innovation Solution
A system with passive monitoring probes and distributed correlation engines is implemented to capture and correlate data records from SIP, RTP, and H.248 portions of VoLTE calls, using distribution keys and routing labels to bind records into a single call record, enabling end-to-end correlation across different network interfaces.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Measurement precision
If distributed correlation engines are used to correlate signaling call flows across different network interfaces, then QoS monitoring capability is improved, but system complexity increases
Solution Approach 1:
The correlation engine is divided into multiple distributed correlation engines, each responsible for correlating data records from specific network interfaces or protocol types. This segmentation allows the system to handle complex multi-interface correlation tasks through distributed processing, improving QoS monitoring capability while managing system complexity through modular architecture
Solution Approach 2:
A standardized data record format acts as an intermediary between different network interfaces and protocols. The system uses uniform data structures with standardized fields to represent signaling call flows from SIP, RTP, and H.248 protocols, enabling correlated analysis across interfaces without requiring complex interface-specific processing logic
2Adaptability or versatility
If multiple network interfaces are monitored simultaneously, then monitoring coverage is improved, but resource requirements increase
Solution Approach 1:
The system employs a universal data record structure that can represent signaling call flows from multiple network interfaces and protocols (SIP, RTP, H.248) using the same format. This multi-functionality allows a single correlation engine implementation to handle diverse interface types, expanding monitoring coverage without proportionally increasing resource requirements
Solution Approach 2:
The system changes the parameter representation by using standardized fields in data records that can accommodate different interface types. By parameterizing the data structure to include interface-specific information in a unified format, the system efficiently monitors multiple interfaces while optimizing resource utilization through consistent data handling
Data Source
AI summary
A system for monitoring calls in a VoLTE network is provided. The monitored calls include SIP, RTP and H.248 portions. The system includes monitoring probes and first and second correlation engine components (CECs). The probe is configured to generate SIP, RTP and H.248 data records (DRs), send the SIP DRs to a second CEC based on a distribution key, generate and send a routing label to a first CEC and to send the H.248 and RTP DRs to the first CEC based on the first and second attributes, respectively. The first CEC is configured to correlate the received RTP and H.248 DRs and the routing label based on the second and first attributes, respectively, and send the correlated DRs to the second CEC based on a distribution key. The second CEC is configured to bind all of the generated DRs to a single call based on the distribution key.