Telephony Device Management for Virtual Meeting Integration

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Typical virtualized meeting software lacks the capability to manage telephony devices such as VOIP phones and voice conference devices, preventing seamless integration with virtual meeting platforms.

Innovation Solution

A device management system utilizing a connection edge server, MQTT protocol, and a device manager to configure and upgrade telephony devices to operate on a virtual meeting room platform, enabling them to connect and communicate effectively within the unified communications as a service (UCaaS) framework.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If telephony devices are integrated with virtual meeting platforms, then communication services are enhanced, but device complexity increases

Engineering Contradiction:
Improveintegration capabilityVSAvoidsystem complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent introduces a device manager as an intermediary component that mediates between telephony devices and the virtual meeting platform. The device manager handles device discovery, provisioning, and configuration tasks, allowing telephony devices to be integrated without requiring complex modifications to the devices themselves. This intermediary layer simplifies the integration process while maintaining adaptability.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The device manager is designed to work with multiple types of devices (telephony devices, video devices, etc.) and multiple communication protocols (MQTT, SIP, etc.). This universal approach allows the system to manage diverse devices through a single management platform, reducing overall system complexity while enhancing integration capability across different device types.

Inventive Principle:
Principle #6Universality (Multi-functionality)

2Adaptability or versatility

If device management capabilities are added to virtualized meeting software, then device integration is enabled, but software complexity increases

Engineering Contradiction:
Improvedevice management capabilityVSAvoidsoftware complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent segments the device management functionality into a separate device manager component that operates independently from the core virtualized meeting software. This segmentation allows device management capabilities to be added without significantly increasing the complexity of the meeting software itself. The device manager handles device-specific tasks while the meeting software focuses on meeting functionality.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The device manager serves as an intermediary layer between the virtualized meeting software and telephony devices. It translates between different protocols and interfaces, enabling device management without requiring the meeting software to directly handle device-specific complexities. This intermediary approach enables device management capability while isolating software complexity.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Ease of repair

If firmware upgrades are implemented remotely, then device maintenance is improved, but communication requirements increase

Engineering Contradiction:
Improveremote maintenance capabilityVSAvoidcommunication protocol requirement
Core Design Contradiction:
Ease of repairVSDevice complexity

Solution Approach 1:

The patent implements a self-service firmware upgrade mechanism where the device manager can remotely push firmware updates to telephony devices, and the devices automatically install them. This self-service approach improves ease of repair by eliminating the need for manual intervention, while the use of standardized MQTT protocols keeps communication requirements manageable rather than complex.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The system implements feedback mechanisms where devices report their status, firmware versions, and upgrade progress back to the device manager through MQTT communications. This feedback loop enables automated firmware management and remote maintenance while using simple, standardized communication protocols rather than complex custom protocols.

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS11777797B2Method and apparatus for device management
Publication Date: 2023.10.03 ZOOM COMMUNICATIONS INC
  • US11777797B2 patent drawing
  • US11777797B2 patent drawing
  • US11777797B2 patent drawing

AI summary

A telephony device includes a memory that stores firmware to operate the telephony device. The telephony device includes a network interface that transmits a first command to establish a connection with a telephony server. The telephony device includes a receiver that receives a second command from a device manager. The second command includes an instruction to upgrade the firmware of the telephony device. The telephony device includes a processor that upgrades the firmware of the telephony device based on the second command. The processor establishes a connection to a virtual meeting room platform based on the upgraded firmware.