Mute Request Management in Electronic Conferences
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing electronic conferencing systems lack efficient management of mute and unmute requests, leading to embarrassing or unwanted situations due to lack of information about the status and reasons for muting, and inadequate control over who can initiate these requests.
Innovation Solution
A conferencing system that allows participants to send mute and unmute requests with explanations, provides notifications on user devices about mute statuses, and implements rules to control who can submit these requests, ensuring informed decisions and preventing unintended changes in mute status.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If the system allows any participant to send mute requests freely, then the ease of operation is improved, but the reliability deteriorates due to unintended changes in mute status
Solution Approach 1:
The system applies preliminary anti-action by requiring confirmation before executing a mute request. When a participant sends a mute request, the system sends a notification to the targeted participant asking for confirmation. Only upon confirmation does the mute status actually change. This prevents unintended changes while maintaining ease of operation, as the initial request can still be sent easily but requires a simple confirmation step to execute.
2Reliability
If the system provides detailed information about mute status and reasons, then the reliability is improved, but the device complexity increases
Solution Approach 1:
The system segments information presentation by separating mute status indicators from detailed explanation displays. The interface shows concise mute status information (who is muted, by whom) prominently, while detailed explanations are displayed separately or on demand. This segmentation allows the system to provide comprehensive information for reliable decision-making without overwhelming the interface with complexity.
Solution Approach 2:
The system introduces an intermediary notification mechanism that mediates between the complex internal state management and the user interface. Notifications serve as an intermediary layer that presents processed, relevant information to participants without exposing the underlying complexity of mute status management, reason tracking, and participant authorization verification.
3Loss of information
If the system sends notifications to all participants about mute requests, then the loss of information is reduced, but the productivity decreases due to excessive notifications
Solution Approach 1:
The system applies local quality by sending notifications selectively rather than universally. Notifications are sent based on local conditions: only to the targeted participant whose mute status is changing, and only when the change is significant (e.g., when a new mute request is received or when a participant responds to a pending request). This reduces information loss for affected participants while minimizing productivity impact by avoiding unnecessary notifications to all participants.
Data Source
AI summary
In certain embodiments, a method includes receiving, from a first participant of a plurality of participants in an electronic-conference session, a mute request. The mute request comprises information indicating a request to mute communication from a second participant of the plurality of participants in the electronic-conference session, information identifying the first participant as a mute requester, and information identifying the second participant as a mutee. The method includes muting, in response to the mute request, communication from the second participant. The method includes sending, to one or more user devices, the information identifying the first participant as the mute requester and the information identifying the second participant as the mutee.