VoIP Packet Loss Attribution via Call Detail Record Correlation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional network monitoring tools fail to effectively identify and pinpoint issues causing packet loss in voice over Internet Protocol (VoIP) traffic, making it difficult for system administrators to diagnose and resolve network problems affecting VoIP quality.
Innovation Solution
A system and method that records routing messages and call detail records to identify the best paths taken by VoIP packets, assigning dropped packets to nodes and links, and tracking changes in paths during calls to accurately attribute packet loss to specific network components, providing administrators with detailed reports to investigate potential issues.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Measurement precision
If conventional network monitoring tools are used, then general network traffic can be monitored, but they fail to identify specific issues causing packet loss in VoIP traffic
Solution Approach 1:
The patent segments network monitoring into general traffic monitoring and VoIP-specific monitoring. It separates VoIP traffic identification from general packet monitoring by using call detail records to identify VoIP flows, then specifically tracking routing messages and packet loss for those identified flows, enabling precise VoIP problem detection without being lost in general network traffic
Solution Approach 2:
The patent introduces call detail records as an intermediary between general network monitoring and VoIP-specific problem identification. These records serve as a mediator that provides call-specific information (calling party, called party, time stamps) to correlate with network routing messages and packet loss data, enabling precise attribution of packet loss to specific VoIP calls
2Loss of information
If call detail records are analyzed without routing message correlation, then packet loss statistics can be obtained, but the source of dropped packets cannot be pinpointed
Solution Approach 1:
The patent merges call detail records with routing messages by correlating them through time stamps and call identifiers. It combines the packet loss statistics from call detail records with the routing path information from routing messages to create a unified view that shows not only how many packets were lost but also which network nodes and links were involved, enabling administrators to pinpoint problem sources
Solution Approach 2:
The patent establishes a feedback loop where call detail records provide packet loss information that is fed back to correlate with routing message data. This feedback mechanism allows the system to continuously refine its understanding of network performance by matching observed packet loss with routing changes, providing actionable troubleshooting information
3Loss of information
If routing messages are recorded without call detail record correlation, then network path information can be tracked, but packet loss cannot be attributed to specific calls
Solution Approach 1:
The patent performs preliminary action by recording and storing routing messages with their time stamps before packet loss occurs. It pre-establishes the network path information and routing state at various points in time, so when packet loss is later detected in call detail records, the system can retrospectively correlate the loss with the routing messages that were recorded in advance, enabling accurate attribution
Data Source
AI summary
A system and method allocates dropped packets from a call detail record in a voice over Internet Protocol to links or nodes the call traversed, and to events that occurred during the call and prefixes corresponding to the phones used in the call, along with a report in decreasing order of the dropped packets for the nodes, links, events and prefixes, to allow a system administrator to help identify the source of the dropped packets.