VoIP Session Detail Record Generation via RTCP Caching
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The generation of VoIP session detail records is cost-inefficient due to intensive computation requirements, especially for transcoding-free VoIP-to-VoIP calls, which necessitates a more efficient method to derive these records from RTP and RTCP packets.
Innovation Solution
Implementing local packet processors on distributed packet interface cards to cache and report the latest RTCP packets, with a centralized host processor generating session detail records by selecting the last RTCP report packet based on timestamps, thereby reducing computational demands and improving efficiency.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Measurement precision
If session detail records are generated by measuring received RTP packets, then complete session information can be obtained, but intensive computation is required making it cost-inefficient
Solution Approach 1:
The patent introduces RTCP packets as an intermediary to carry session detail information. Instead of measuring RTP packets directly, the system uses RTCP packets as a mediator that contains pre-computed session statistics and metrics, thereby reducing the computational burden while maintaining measurement precision.
Solution Approach 2:
The patent extracts session detail information from RTCP packets, which contain pre-computed metrics such as packet loss, jitter, and round trip time. This extraction approach avoids the need for intensive computation by directly utilizing the information already packaged in RTCP reports.
2Loss of information
If all RTCP packets are processed and stored centrally, then complete session data is available, but demand for communication bandwidth and message buffers increases
Solution Approach 1:
The patent applies preliminary action by having local packet processors cache and prepare RTCP report data before central collection. The latest RTCP report is identified and cached locally, so that only essential final data needs to be transmitted centrally, reducing bandwidth and buffer requirements while maintaining data completeness.
Solution Approach 2:
The patent segments the RTCP processing task between local packet processors and the central host processor. Local processors handle caching and preliminary identification of final RTCP reports, while the central processor performs final session detail record generation. This segmentation reduces the communication burden on the central system.
Data Source
AI summary
An apparatus including a plurality of packet processors each included in one of a plurality of voice-over-internet-protocol (VoIP) network interfaces. Each of the plurality of packet processors is configured to cache a latest version of realtime transport control protocol (RTCP) report data by discarding an older version of the RTCP report data. The RTCP report data includes at least one of RTCP sender report data and RTCP receiver report data. The apparatus also includes a packet data switching matrix configured to switch packet data between ones of the plurality of VoIP network interfaces. A central processor of the apparatus is configured to generate a final session detail record upon the termination of a VoIP-session by selecting RTCP session-concluding report data from a plurality of RTCP final report data each cached by a corresponding one of the plurality of packet processors.