Cross-Organization Calendar Comparison via Trusted Intermediary
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current calendar comparison systems face difficulties in scheduling meetings between users from different organizations due to incompatible company policies and security restrictions, leading to manual and inefficient communication processes, especially when trying to share calendar information and comply with legal requirements for texting.
Innovation Solution
A software application that enables users from multiple organizations to share and compare calendars, automatically determine available times for meetings, and manage messaging permissions through a trusted third-party server system, allowing seamless communication across different calendaring systems and compliance with legal texting regulations.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If manual calendar comparison methods are used, then users can share calendar information, but the process requires significant time and communication effort
Solution Approach 1:
The system automatically compares calendars and determines available times without requiring manual intervention. The automated calendar comparison feature retrieves calendar data from multiple sources, processes it server-side, and returns available time slots, eliminating the need for users to manually exchange and compare calendar information.
Solution Approach 2:
The patent replaces manual mechanical processes (emails, phone calls, manual calendar checking) with an automated electronic system. The server-based calendar comparison mechanism uses electronic data retrieval and processing to automatically determine availability, substituting the manual communication loop with an automated information processing system.
2Adaptability or versatility
If users share calendar information directly, then scheduling becomes possible, but company policies and security restrictions prevent information sharing
Solution Approach 1:
The system introduces a trusted third-party server as an intermediary between users from different organizations. Instead of users directly sharing calendar data (which would violate security policies), the server acts as a mediator that securely retrieves calendar information from authorized sources, compares it according to policy rules, and returns processed results without requiring direct data exposure between organizations.
Solution Approach 2:
The calendar comparison system is designed to work universally across different organizational environments. It can access calendars from multiple sources (Exchange, Outlook, Google Calendar, iCloud) and accommodate various company policies and security restrictions, making it adaptable to diverse organizational structures while maintaining policy compliance.
3Ease of operation
If text messaging is used for scheduling, then communication is convenient, but legal requirements for texting compliance create difficulties
Solution Approach 1:
The server acts as an intermediary that manages text messaging compliance. Instead of users directly handling text message compliance requirements, the system retrieves contact information and messaging permissions from authorized sources, determines appropriate communication methods according to legal requirements, and manages the messaging process while ensuring compliance with texting regulations.
Data Source
AI summary
A system includes a memory and at least one processor to receive a communication having a communication type comprising one of email, phone, and text messaging from a sender comprising one of a first user having a first client computing device and a second user having a second client computing device, determine whether the first user having the first client computing device and the second user having the second client computing device have granted permission to communicate using the communication type and forward the communication having the communication type to a recipient comprising one of the first user having the first client computing device and the second user having the second client computing device.


