DCN-Based Capability Management for Video Conferencing Reconnection

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Existing video and audio conferencing systems face challenges in efficiently setting up and reestablishing conference calls due to the time-consuming process of determining connection rules through gatekeepers, which can lead to disruptions if connection devices disconnect during calls.

Innovation Solution

A management system that queries and monitors connection devices for their capabilities, using Deducible Capability Numbering (DCN) to automatically establish and reestablish connections, allowing for dynamic routing and reconnection without relying on gatekeepers, by assigning scores based on device capabilities and implementing rules for optimal connection selection.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If gatekeepers use database inquiries and preprogrammed rules to determine connection routing, then connection reliability is improved, but setup time and operational complexity increase

Engineering Contradiction:

Improveconnection reliabilityVSAvoidsetup time

Core Design Contradiction:

ReliabilityVSLoss of time

Solution Approach 1:

The system performs preliminary actions by having connection devices automatically send capability information to the management system before calls are established. The management system pre-processes this information into structured data, so when a call needs to be routed, the routing decision can be made quickly based on pre-analyzed capability data rather than querying databases during the setup phase.

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

Connection devices automatically provide their own capability information to the management system without requiring manual configuration or gatekeeper intervention. The devices self-register their capabilities, and the management system automatically maintains the capability database, eliminating the need for time-consuming manual rule setup and database inquiries.

Inventive Principle:

Principle #25Self-service

2Measurement precision

If gatekeepers rely on databases to store caller type and ability information, then routing accuracy is improved, but device complexity and operational difficulty increase

Engineering Contradiction:

Improverouting accuracyVSAvoidsystem complexity

Core Design Contradiction:

Measurement precisionVSDevice complexity

Solution Approach 1:

Inventive Principle:

Principle #25Self-service

Solution Approach 2:

The system changes the parameter representation by using a standardized capability information format with specific parameters (video resolution, audio codecs, network protocols) that can be systematically processed. This structured parameter approach enables automated routing decisions based on precise capability matching without requiring complex database schemas or manual rule configuration.

Inventive Principle:

Principle #35Parameter changes

3Ease of operation

If the system manually configures calling rules through gatekeepers, then connection control is improved, but productivity and call reestablishment speed decrease

Engineering Contradiction:

Improveconnection controlVSAvoidcall reestablishment speed

Core Design Contradiction:

Ease of operationVSProductivity

Solution Approach 1:

The management system automatically monitors capability changes and handles call reestablishment without requiring manual gatekeeper intervention. When a connection device's capabilities change or a call needs reestablishment, the system autonomously queries the updated capabilities, reevaluates routing options, and executes reconnection, dramatically improving reestablishment speed while maintaining controlled routing through automated decision-making.

Inventive Principle:

Principle #25Self-service

Solution Approach 2:

The system implements continuous feedback by monitoring capability information from connection devices in real-time. When capabilities change or connections fail, the management system receives feedback about the current state, automatically reevaluates routing decisions based on updated information, and adjusts connections accordingly, enabling both controlled operation and rapid response to changes.

Inventive Principle:

Principle #23Feedback

4Reliability

If the system monitors capability changes continuously, then call reliability is improved, but energy consumption and processing load increase

Engineering Contradiction:

Improvecall reliabilityVSAvoidprocessing load

Core Design Contradiction:

ReliabilityVSUse of energy by moving object

Solution Approach 1:

Instead of continuous monitoring, the system uses periodic capability queries where the management system requests capability information at scheduled intervals or triggered by specific events. This periodic approach maintains reliable knowledge of device capabilities while significantly reducing the processing load and energy consumption compared to continuous real-time monitoring, as the system only actively queries when needed rather than constantly tracking all devices.

Inventive Principle:

Principle #19Periodic action

Data Source

PatentUS7864714B2Capability management for automatic dialing of video and audio point to point/multipoint or cascaded multipoint calls

Publication Date: 2011.01.04 ENGHOUSE INTERACTIVE

AI summary

In various embodiments, a management system may query connection devices for their capabilities and store the information in a data structure. In some embodiments, the data structure may be in a form of a Deducible Capability Numbering (DCN) number. In some embodiments, the DCN number may describe the capabilities of a connection device using a series of representative numbers. After connecting the connection devices, the management system may continue monitoring capabilities of the connection devices and line failures. The management system may reconnect connection devices based on their capabilities if a line failure occurs.