Collaboration Event Framework Automates Participant Joining

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Current collaboration event scheduling systems face inefficiencies due to manual participant joining processes, unclear resource requirements, and potential network bottlenecks, leading to productivity losses and increased costs from delayed meetings and resource shortages.

Innovation Solution

A collaboration event scheduling framework that integrates with calendaring systems to automatically schedule and initiate events using participant preferences, verifies identities, and analyzes resource requirements to ensure sufficient network resources are available, allowing for efficient and timely event invocation.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If manual processes are used for participants to join collaboration events (looking up calendar invites, dialing in, entering URLs), then participants can join events, but joining delays increase and productivity is lost

Engineering Contradiction:

Improveparticipant joining efficiencyVSAvoidparticipant joining delay

Core Design Contradiction:

ProductivityVSLoss of time

Solution Approach 1:

The system performs preliminary actions by automatically dialing participants' phones or sending instant messages before the collaboration event starts. This pre-initiation of contact eliminates the need for participants to manually look up information and join, directly reducing joining delays and improving productivity.

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The collaboration event framework acts as an intermediary between the scheduling system and participants. It automatically manages the joining process by contacting participants through preferred methods (phone, instant message) and coordinating their entry into the event, eliminating manual lookup and joining steps.

Inventive Principle:

Principle #24Intermediary (Mediator)

2Reliability

If participants wait for grace time before events start to allow everyone to join, then all participants can be present, but the event is delayed and productivity is lost

Engineering Contradiction:

Improveparticipant attendance completenessVSAvoidevent start delay

Core Design Contradiction:

ReliabilityVSLoss of time

Solution Approach 1:

The system contacts participants in advance of the event start time, allowing them to join as they become available rather than requiring everyone to be present simultaneously. This eliminates the need for grace time waiting while ensuring reliable attendance as participants join at their convenience.

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The event start time becomes dynamic rather than fixed. The framework monitors participant joining status and automatically initiates the event when appropriate conditions are met, rather than waiting for a predetermined grace period. This adaptive approach maintains reliability while reducing delays.

Inventive Principle:

Principle #15Dynamics

3Ease of operation

If calendar invites contain all collaboration details (phone numbers, passcodes, URLs), then participants have all information needed, but participants must access calendar applications which they may not have access to when mobile

Engineering Contradiction:

Improveaccess to collaboration detailsVSAvoidmobility flexibility

Core Design Contradiction:

Ease of operationVSAdaptability or versatility

Solution Approach 1:

The collaboration event framework serves as an intermediary that delivers collaboration details through multiple channels (phone calls, instant messages) rather than requiring participants to access calendar applications. This maintains ease of operation while enabling mobility flexibility by allowing participants to receive information on mobile devices.

Inventive Principle:

Principle #24Intermediary (Mediator)

Solution Approach 2:

The system provides universal access to collaboration details through multiple communication methods (telephone, instant message, email) rather than relying solely on calendar applications. This multi-functionality ensures participants can access information regardless of their device or location, enhancing both ease of operation and mobility adaptability.

Inventive Principle:

Principle #6Universality (Multi-functionality)

4Device complexity

If system administrators cannot see scheduled collaboration events, then system complexity is reduced, but resource requirements cannot be determined and network bottlenecks may occur

Engineering Contradiction:

Improvescheduling system complexityVSAvoidnetwork resource adequacy

Core Design Contradiction:

Device complexityVSReliability

Solution Approach 1:

The system extracts and separates the resource monitoring function from the participant-facing scheduling interface. Administrators can view scheduled events and resource requirements through a dedicated management interface without adding complexity to the participant experience. This extraction enables reliable resource planning while maintaining system simplicity for end users.

Inventive Principle:

Principle #2Taking out (Extraction)

Data Source

PatentUS8463632B2Management and automatic invocation of scheduled collaboration events

Publication Date: 2013.06.11 ORACLE INT CORP

AI summary

A collaboration event framework can be used to schedule and automatically invoke a collaboration event. An event coordinator may schedule a collaboration event, and the framework will automatically initiate contact with event participants using participant contact preferences. Participants can be asked to enter an identifier to verify the participant's identity. An event coordinator may be presented with a display that indicates the status of participants of the collaboration event. A system administrator may review all scheduled collaboration events to determine resource shortages.