Conference Image Sharing via a Companion Device Interface
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional conferencing software faces challenges when participants attempt to share content from a secondary device, leading to increased resource utilization, confusing multiple device connections, and potential performance degradation.
Innovation Solution
A system that allows a conference participant to connect two devices to a conference while being shown as joined only once, enabling content sharing from a secondary device through a companion user interface.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If a conference participant joins a conference using multiple devices (primary device and secondary device) to enable content sharing from the secondary device, then content sharing capability is improved, but resource utilization increases and system complexity increases
Solution Approach 1:
The system separates the conference participation function into two distinct roles: primary device for audio/video communication and secondary device for content sharing. This segmentation allows each device to perform its specific function without requiring full conference participation capabilities, reducing overall system complexity while maintaining versatility.
Solution Approach 2:
The secondary device is integrated into the conference ecosystem with a universal interface that allows it to share content (images, videos, files) with the conference group. The device serves multiple purposes including content sharing, receiving conference notifications, and facilitating interaction, achieving multi-functionality without requiring full conference client functionality.
2Adaptability or versatility
If a conference participant joins a conference using multiple devices (primary device and secondary device) to enable content sharing from the secondary device, then content sharing capability is improved, but resource utilization increases
Solution Approach 1:
The system extracts the content sharing functionality from the full conference client and implements it as a separate, lightweight secondary device integration. This extraction allows the secondary device to share content without requiring the full resource-intensive conference client stack, including audio/video processing, screen sharing, and complex communication protocols.
Solution Approach 2:
The secondary device uses a simplified copy of the conference client functionality, implementing only the essential content sharing features. Instead of running a complete conference client on the secondary device, the system creates a lightweight replica that handles content upload and basic interaction, significantly reducing resource utilization while maintaining content sharing capability.
3Adaptability or versatility
If conventional conferencing software allows multiple device connections per participant, then content sharing flexibility is improved, but conference performance degrades due to duplicate connections and stream management overhead
Solution Approach 1:
The system introduces an intermediary mechanism where the primary device acts as a bridge between the secondary device and the conference server. The secondary device communicates content to be shared to the primary device, which then uploads it to the conference server. This intermediary approach avoids creating duplicate conference connections, reducing stream management overhead while maintaining content sharing flexibility.
Solution Approach 2:
Instead of allowing the secondary device to directly connect to the conference server as a full participant (which would create duplicate connections and degrade performance), the system inverts the approach: the secondary device connects only to the primary device, and the primary device handles all server communications. This inversion eliminates duplicate connections while preserving content sharing flexibility.
Data Source
AI summary
An indication of images is received at a first device connected to a conference. A first image is transmitted to a conferencing server based on a request to share the first image of the images in the conference. The first image is displayed in a companion tile associated with the first device. A request is received to share a second image of the images in the conference. The first image is replaced in the companion tile with the second image.


