Idle Endpoint Network Probes for VoIP Monitoring

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing methods for testing packet switching networks, such as those used for VoIP communication, face issues with network probe degradation due to excessive traffic generation and failure to detect problems during idle periods, as they rely on active endpoints or generate traffic only between specific domains.

Innovation Solution

A method where idle user endpoint devices are designated as probes, communicate with a server to identify other probes across subnetworks, and transmit test packets using RTCP or other techniques to monitor network conditions, ensuring continuous testing without degrading network performance.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If all idle IP endpoints generate calls throughout the network to verify communications, then network monitoring coverage is improved, but network performance degrades due to excessive traffic generation

Engineering Contradiction:
Improvenetwork monitoring coverageVSAvoidnetwork performance
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The network is segmented into multiple domains, and the monitoring function is segmented so that only one probe per domain is active at a time. This divides the monitoring task across multiple smaller units (domains) rather than having all endpoints generate traffic simultaneously, reducing overall network traffic while maintaining comprehensive coverage.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

Instead of having all idle endpoints generate monitoring traffic (excessive action), the system activates only one probe per domain (partial action). This selective activation provides sufficient monitoring coverage without generating excessive traffic that would degrade network performance.

Inventive Principle:
Principle #16Partial or excessive action

2Reliability

If an IP endpoint is designated as a network probe, then monitoring capability is improved, but the probe stops generating traffic when engaged in actual calls

Engineering Contradiction:
Improvemonitoring capabilityVSAvoidtraffic generation
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The system automatically detects when a probe becomes engaged in an actual call and self-adjusts by selecting a different idle endpoint within the same domain to become the new probe. This self-service mechanism ensures continuous monitoring capability and continuous traffic generation without manual intervention.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The system implements feedback by monitoring the operational state of probes. When a probe becomes engaged in a call, this state change is detected, and the system responds by selecting a new probe from idle endpoints, ensuring that monitoring and traffic generation functions are always performed by active probes.

Inventive Principle:
Principle #23Feedback

3Reliability

If RTCP packets are used for network monitoring, then monitoring function is improved, but monitoring fails during idle periods when no traffic is sent

Engineering Contradiction:
Improvemonitoring functionVSAvoiddetection delay
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system performs preliminary action by having idle endpoints proactively generate test calls to other domains before actual network problems occur. This advance monitoring activity ensures that network issues are detected during idle periods rather than waiting for actual traffic to reveal problems.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system ensures continuity of useful action by maintaining constant monitoring activity through probes that continuously generate traffic. Even when the overall network is idle, probes remain active and continue to send test traffic, eliminating gaps in monitoring coverage.

Inventive Principle:
Principle #20Continuity of useful action

Data Source

PatentUS7352705B1Method and apparatus for determining endpoints for use as testing devices
Publication Date: 2008.04.01 AVAYA INC
  • US7352705B1 patent drawing
  • US7352705B1 patent drawing
  • US7352705B1 patent drawing

AI summary

A method and apparatus for testing a digital network having a plurality of subnetworks by determining by one of a plurality of user endpoint devices assigned to one of the plurality of subnetworks upon the one of the plurality of user endpoint devices being idle that the one of the plurality of user endpoint devices should perform the functions of a testing user endpoint device for the one of the plurality of subnetworks; identifying the one of plurality of user endpoint devices to a server or a distributed system of servers as a testing user endpoint device; obtaining the identifies of other testing user endpoint devices in other ones of the plurality of subnetworks from the server; and testing the network by transmission of test packets to other ones of the testing user endpoint devices in the other ones of the plurality of subnetworks.