Intermediary Server for LYNC and Third-Party Audio Video Integration
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing solutions for integrating Microsoft LYNC meetings with third-party audio-video solutions in mixed environments are inadequate, as they do not seamlessly integrate with non-LYNC conferencing systems, requiring plugin installations and limiting user experience, especially for participants connecting via non-Microsoft video equipment.
Innovation Solution
A system that allows non-LYNC endpoints to connect to LYNC conferences without plugins by using a call server with dial rules and multipoint control units, creating a cascaded link between LYNC and non-LYNC MCUs, enabling seamless integration and continuous video presence across both systems.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If a plugin is deployed to OUTLOOK to integrate with third-party audio-video solutions, then the audio-video integration is achieved, but the system complexity and deployment difficulty increase
Solution Approach 1:
The patent introduces an intermediary component that sits between OUTLOOK and the third-party audio-video system. This intermediary handles the integration logic and communication protocols, allowing OUTLOOK to work with third-party systems without requiring direct plugin installations. The intermediary translates and bridges the different systems, reducing the complexity burden on the core OUTLOOK application.
2Adaptability or versatility
If LYNC clients dial a third-party conference ID to join meetings, then non-LYNC video equipment can connect, but the Microsoft solution flow is broken and user experience deteriorates
Solution Approach 1:
The patent employs an intermediary that enables LYNC clients to maintain their native meeting flow while still connecting to third-party video equipment. The intermediary handles the protocol translation and connection routing, allowing LYNC clients to use their standard hyperlink joining method while the intermediary seamlessly bridges them to the third-party system in the background.
Solution Approach 2:
The system architecture segments the meeting connection process into distinct layers: the LYNC client layer, the intermediary layer, and the third-party audio-video layer. This segmentation allows each layer to operate independently with its own optimized protocols, enabling LYNC clients to use their native joining process while the intermediary handles the complexity of bridging to third-party systems.
3Adaptability or versatility
If Outlook's built-in LYNC meeting button is used, then Microsoft environment integration is achieved, but third-party audio-video solutions cannot be scheduled
Solution Approach 1:
The patent implements a universal scheduling interface that can handle both Microsoft LYNC meetings and third-party audio-video conferences through a common mechanism. The intermediary provides multi-functional capabilities, allowing the same OUTLOOK interface to schedule different types of meetings by routing them appropriately, thereby extending LYNC's meeting button functionality to support third-party systems without adding separate scheduling interfaces.
Data Source
AI summary
An intermediary server allows endpoints connected to two different types of conferencing systems to participate in an integrated conference without requiring plugins to be installed at each endpoint. A conference identifier provided by a first type of conferencing system can be used by endpoints of a second type of conferencing system by allowing the intermediary server to send the conference identifier to a server of the first type of conferencing system and receive a link that a server of the second type of conferencing system can use to connect to the first type of conferencing system.