RTP Header Extension Tagging for VoIP Source Classification
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current solutions for VoIP communication sessions using RTP media streams fail to differentiate and manage RTP streams based on their source, leading to inadequate customer satisfaction, as participants are unable to distinguish between uninteresting content like music and important alerts, such as a conference host joining the call.
Innovation Solution
A system and method that identify and classify RTP data streams by inserting source-specific tags into RTP header extensions, allowing for policy-driven management of playback settings, enabling differentiation between various RTP sources and adjusting playback accordingly.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If present solutions treat all RTP streams substantially the same with default action, then system complexity is reduced, but the ability to differentiate and manage RTP streams based on source is lost
Solution Approach 1:
The patent segments RTP streams by inserting source identification tags into RTP header extensions. This allows the system to divide and categorize different RTP streams (music server, conference host, participant) with distinct tags, enabling differentiated playback control without requiring complex system architecture changes.
Solution Approach 2:
The patent introduces an intermediary tagging mechanism that inserts source identification information into RTP packets. This intermediary tag system acts as a mediator between the RTP stream source and the playback control system, enabling source-based differentiation without direct complex interaction between all system components.
2Loss of time
If participants listen to music while waiting on hold, then time is filled during waiting period, but important alerts such as conference host joining may be missed
Solution Approach 1:
The patent applies local quality by assigning different playback characteristics to different RTP sources. Music server RTP streams receive one playback treatment (e.g., lower volume, different audio output) while conference host RTP streams receive another treatment (e.g., higher volume, alert notifications), allowing participants to utilize waiting time with music while still perceiving important alerts.
Solution Approach 2:
The patent changes playback parameters (volume, audio output device, alert notification) based on the source identification tag in the RTP stream. This allows the system to dynamically adjust playback parameters for different sources, enabling music playback during waiting while ensuring important alerts are communicated effectively.
3Ease of operation
If music is played through speakerphone during waiting, then participants can listen without holding phone, but music may be annoying to nearby people
Solution Approach 1:
The patent changes the audio output parameter based on the RTP source tag. When music server RTP is detected, the system can direct audio to a specific output device (e.g., earpiece rather than speakerphone) or adjust volume levels, allowing hands-free operation while reducing annoyance to nearby people through parameter adjustment.
Data Source
AI summary
System and method to transmit an identification of a real-time transport protocol (RTP) data stream, the method including: identifying an identification of an RTP data stream; inserting the identification of the RTP data stream into an RTP header extension; and transmitting, by use of a network interface, an RTP packet comprising the RTP header extension. The method may further include: consulting a policy for profile tag settings, wherein the step of inserting the identification is dependent upon the policy.