Video Conferencing Load Balancing via Protocol Connector

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional load balancing methods for video conferencing systems are inadequate as they do not effectively handle different client applications and internal security measures, such as firewalls, which restrict redirects to unfamiliar servers, leading to functional limitations and security issues.

Innovation Solution

A video conferencing system that dynamically selects an appropriate load balancing technique based on client application profiles, using a protocol connector module to retrieve profiles and perform load balancing capabilities, and logs performance metrics to optimize server usage and adapt to real-time changes, ensuring geographic distribution and local clustering of load across multiple servers.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If conventional load balancing methods (DNS round robin or proxying) are used for all client applications, then load distribution is achieved, but functionality is lost for client applications that do not support redirects or are blocked by firewalls

Engineering Contradiction:
Improveload distribution efficiencyVSAvoidcompatibility with different client applications
Core Design Contradiction:
ProductivityVSAdaptability or versatility

Solution Approach 1:

The system dynamically selects load balancing techniques based on real-time client application capabilities and network conditions. Instead of using a static load balancing method for all clients, the system adapts the approach (DNS round robin, proxying, or direct connection) according to each client's support for redirects and firewall constraints, thereby maintaining both load distribution efficiency and broad client compatibility

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The system changes the load balancing parameter (technique selection) based on client application characteristics. By detecting whether a client supports redirects and understanding firewall constraints, the system switches between different load balancing parameters (DNS-based, proxy-based, or direct server connection) to optimize both productivity and adaptability for each specific client type

Inventive Principle:
Principle #35Parameter changes

2Productivity

If redirects are implemented for load balancing, then server distribution is improved, but security measures (firewalls) block redirects to unfamiliar servers

Engineering Contradiction:
Improveserver utilization balanceVSAvoidfirewall blocking
Core Design Contradiction:
ProductivityVSObject-affected harmful factors

Solution Approach 1:

The system introduces an intermediary approach by using proxy servers as intermediate nodes between clients and target servers. When firewalls block direct redirects to unfamiliar servers, the proxy server acts as a trusted intermediary that clients can connect to, which then forwards requests to the appropriate backend servers. This maintains server utilization balance while bypassing firewall restrictions

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

Instead of redirecting clients directly to target servers (which gets blocked by firewalls), the system inverts the approach by having clients connect to a known proxy server first, which then performs the redirection to target servers. This reverses the redirect path to work around firewall blocking while achieving the same load distribution goal

Inventive Principle:
Principle #13The other way round (Inversion)

Data Source

PatentUS9525849B2Provision of video conferencing with load balancing
Publication Date: 2016.12.20 VERIZON PATENT & LICENSING INC
  • US9525849B2 patent drawing
  • US9525849B2 patent drawing
  • US9525849B2 patent drawing

AI summary

Embodiments are described for provision of video conferencing with load balancing. In some embodiments, a protocol connector module receives a media processing request from a client application for the video conference endpoint device and a client application identifier, a profile for the client application is retrieved using the client application identifier, at least one load balancing capability is determined for the client application using the identifier, a load balancing technique is selectively performed based on the at least one load balancing capability, and performance of the client application is logged with the load balancing technique in the profile.