Network Path Validation for Video Conferencing Reliability

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Video conferencing systems often face connectivity issues due to network failures or performance degradation, leading to costly disruptions, especially during important meetings where multiple participants cannot join due to undetected network conditions.

Innovation Solution

A management system that periodically tests connectivity with remote locations before a scheduled call, automatically alerts IT personnel or participants of issues, and optionally reschedules the call to use functioning endpoints, ensuring smooth videoconferencing by verifying and maintaining network paths through test calls and alternate routes.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If video conferencing systems wait until the scheduled call time to establish connectivity, then the system simplicity is maintained, but connectivity failures occur due to undetected network conditions

Engineering Contradiction:
Improveconnectivity reliabilityVSAvoidsystem complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The system performs preliminary connectivity validation by placing test calls to remote locations at scheduled intervals before the actual video conference call. This preliminary action detects network path failures in advance, allowing the system to identify connectivity issues before they impact the scheduled conference, thereby improving reliability without requiring complex real-time monitoring during the call

Inventive Principle:
Principle #10Preliminary action

2Reliability

If the system performs frequent connectivity validation tests before scheduled calls, then connectivity reliability is improved, but network resources and time are consumed

Engineering Contradiction:
Improveconnectivity reliabilityVSAvoidvalidation time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system performs connectivity validation at periodic intervals before scheduled calls rather than continuously or at every possible moment. The validation is scheduled to occur at specific times leading up to the conference call, balancing the need for reliable connectivity assessment with the constraint of limited time resources, ensuring validation happens frequently enough to detect issues but not so frequently as to waste time

Inventive Principle:
Principle #19Periodic action

3Productivity

If the system automatically alerts IT personnel and reschedules calls upon detecting connectivity issues, then service continuity is improved, but automation complexity increases

Engineering Contradiction:
Improveservice continuityVSAvoidautomation level
Core Design Contradiction:
ProductivityVSExtent of automation

Solution Approach 1:

The system automatically detects connectivity failures through preliminary validation calls, alerts IT personnel or participants without human intervention, and even autonomously reschedules conference calls to alternative times when endpoints are available. This self-service capability improves service continuity by handling failure responses automatically, reducing the need for manual intervention while managing automation complexity through rule-based decision-making

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS8149739B2Background call validation
Publication Date: 2012.04.03 ENGHOUSE INTERACTIVE
  • US8149739B2 patent drawing
  • US8149739B2 patent drawing
  • US8149739B2 patent drawing

AI summary

A management system may test network paths prior to scheduled calls. Testing network paths may include one endpoint placing a test call to an endpoint on the other end of the path. Various characteristics of the network path may be tested. If the network path fails and/or in some way does not meet the predefined characteristics for the call, an administrator may be notified and/or alternate network path may be detected and tested. The call may be rescheduled if a satisfactory network path is not found in time.