Email Client Conference Bridge Synchronization
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current email and calendaring systems lack integration with conferencing systems, requiring multiple steps to schedule meetings and leading to synchronization issues when meetings are modified or deleted.
Innovation Solution
A method that allows an email client to communicate with a conference bridge to schedule meetings, using a plug-in or email message to send meeting requests and access codes, ensuring synchronization between systems.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If separate email and conferencing systems are used, then system independence and flexibility are maintained, but multiple scheduling steps and synchronization complexity increase
Solution Approach 1:
The patent introduces an intermediary component that acts as a bridge between the email system and conferencing system. This intermediary receives meeting requests from the email system, translates them into conferencing system protocols, and manages the synchronization automatically, thereby maintaining system independence while reducing synchronization complexity.
Solution Approach 2:
The patent creates a universal interface that can handle multiple communication protocols and formats between different systems. This universal layer allows the email system and conferencing system to interact through a standardized method, enabling both systems to maintain their independence while achieving seamless integration through the multi-functional interface.
2Adaptability or versatility
If manual scheduling in both systems is required, then system independence is maintained, but user time and operational complexity increase
Solution Approach 1:
The patent implements preliminary action by having the email system proactively send meeting requests to the conferencing system before the meeting occurs. The intermediary automatically processes these requests in advance, reserves resources, and confirms scheduling, eliminating the need for manual intervention and reducing the time users spend on scheduling.
Solution Approach 2:
The system enables self-service automation where the email system automatically manages conferencing scheduling without requiring user intervention. The intermediary handles the entire process autonomously - receiving requests, translating protocols, reserving resources, and updating both systems - allowing users to focus on their primary tasks while the system manages the coordination automatically.
3Adaptability or versatility
If separate scheduling processes are used, then system autonomy is preserved, but synchronization reliability decreases
Solution Approach 1:
The patent implements a feedback mechanism where the intermediary continuously monitors the state of both the email system and conferencing system. When changes occur in either system, the intermediary detects them and automatically propagates the changes to the other system, ensuring synchronization reliability while preserving system autonomy through bidirectional communication and confirmation.
Solution Approach 2:
The intermediary acts as a reliable mediator that manages the complexity of synchronization between autonomous systems. It implements error handling, confirmation protocols, and rollback mechanisms to ensure that changes are reliably propagated between systems, maintaining synchronization reliability without compromising the autonomy of either system.
Data Source
AI summary
A method for scheduling a meeting using an email client that is part of an email system includes receiving a request at the email client to schedule the meeting. The request may include an indication of the resources that are to be provided by a conferencing system for the meeting. The method also includes communicating the request to a conference bridge that is part of the conferencing system and receiving from the conference bridge an access code associated with the meeting. The method also includes appending the access code to a meeting invitation associated with the meeting and providing the meeting invitation to an email server that is part of the email system. The method also includes sending the meeting invitation to users invited to participate in the meeting.