Communication App Synchronization via Meeting Event Mediation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing communication applications on information handling systems lack effective synchronization across multiple systems, leading to suboptimal user experiences during meetings and collaborations.
Innovation Solution
Implementing a local and central communication management module to register and monitor communication applications, enabling synchronization of status updates and predefined actions based on meeting events across information handling systems.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If communication applications run independently on multiple information handling systems, then each application maintains its own state and operations, but synchronization and coordination between applications across systems deteriorate
Solution Approach 1:
The patent introduces a communication management module as an intermediary component that mediates between multiple communication applications across different information handling systems. This module receives notifications from applications, determines appropriate actions, and coordinates execution across systems, thereby achieving synchronization without direct complex inter-application communication.
Solution Approach 2:
The communication management functionality is segmented into distributed communication management modules on each information handling system. Each module independently manages local applications while coordinating with remote modules through standardized notifications and actions, dividing the complex synchronization problem into manageable local decision-making units.
2Adaptability or versatility
If multiple communication applications operate simultaneously on the same information handling system, then users can access diverse communication tools, but state synchronization and action coordination between applications deteriorate
Solution Approach 1:
The communication management module implements a universal notification and action framework that works across multiple different communication applications. Standardized notification types (e.g., meeting start, meeting end) and actions (e.g., update status, pause application) enable diverse applications to participate in a common synchronization mechanism without requiring application-specific coordination logic.
Solution Approach 2:
The system implements feedback loops where communication applications notify the management module of their state changes (such as meeting events), and the management module responds by executing actions that affect application states. This closed-loop feedback ensures that state information is continuously synchronized across applications without loss.
3Ease of operation
If manual coordination of communication application states is implemented, then users have full control over application behavior, but user workload and response time deteriorate
Solution Approach 1:
The communication management module implements self-service automation by automatically receiving notifications from communication applications, determining appropriate actions based on predefined logic, and executing those actions without requiring user intervention. The system serves itself by autonomously coordinating application states and managing synchronization tasks.
Solution Approach 2:
The system performs preliminary configuration of communication management modules and notification-action mappings in advance. This preliminary setup enables the automated coordination mechanism to function immediately when communication applications are deployed, eliminating the need for manual real-time coordination while maintaining full control over application behavior.
Data Source
AI summary
Synchronizing communication applications, including registering a first instance of a first communication application of a first IHS with a first local communication management computing module of the first IHS; registering a first instance of a second communication application of the first IHS with the first local communication management module; monitoring a status of each of the first instance of the first communication application and the first instance of the second communication application, including: receiving a notification indicating a meeting event associated with the first instance of the first communication application; in response to receiving the notification: accessing a database that indicates, for each communication application, computer-implemented actions that are responsive to the notification of the meeting event; identifying a particular computer-implemented action; performing the particular computer-implemented action at the first instance of the second communication application including updating a state of the first instance of the second communication application.