Event-Based Collaboration Framework for Desktop Sharing

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Traditional collaboration methods, such as sending pixels and documents, result in significant network traffic and latency issues, limiting user experience and being ineffective for non-collaboration aware applications.

Innovation Solution

Implementing event-based collaboration using frameworks that intercept and transmit input events from a presenter's computer to participants' systems, allowing seamless interaction with applications unaware of the collaboration session, including document sharing and control handoff.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If traditional pixel-based collaboration is used to share desktops, then all participants can view the presenter's desktop, but network traffic increases significantly and latency issues occur

Engineering Contradiction:
Improvecollaboration reliabilityVSAvoidnetwork traffic
Core Design Contradiction:
ReliabilityVSLoss of energy

Solution Approach 1:

The patent extracts only the essential collaboration data (input events such as keyboard strokes, mouse movements, and application commands) from the complete desktop pixel stream. Instead of transmitting all pixels, the system sends only the discrete event data that represents user actions, dramatically reducing network traffic while maintaining collaboration reliability.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The patent segments the continuous desktop video stream into discrete input events. By breaking down the collaboration data transmission into individual events (key presses, mouse clicks, window changes), the system can transmit only necessary information at specific moments, reducing overall network bandwidth consumption compared to continuous pixel streaming.

Inventive Principle:
Principle #1Segmentation

2Reliability

If traditional pixel-based collaboration is used to share desktops, then all participants can view the presenter's desktop, but network latency increases resulting in poor user experience

Engineering Contradiction:
Improvecollaboration reliabilityVSAvoidnetwork latency
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent extracts only the essential collaboration data (input events such as keyboard strokes, mouse movements, and application commands) from the complete desktop pixel stream. Instead of transmitting all pixels, the system sends only the discrete event data that represents user actions, dramatically reducing network traffic while maintaining collaboration reliability.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The system uses periodic event capture and transmission, where input events are captured at discrete moments when user actions occur rather than continuously streaming pixels. This event-driven periodic transmission reduces latency by sending data only when changes occur, rather than maintaining a continuous high-bandwidth connection.

Inventive Principle:
Principle #19Periodic action

3Adaptability or versatility

If custom collaboration-aware applications are used, then collaboration functionality is achieved, but application complexity and compatibility requirements increase

Engineering Contradiction:
Improvecollaboration functionalityVSAvoidapplication complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent introduces an intermediary collaboration framework that sits between the application and the network transmission layer. This framework captures input events at the operating system level and handles the collaboration logic, allowing standard applications to participate in collaboration without needing to be modified or made collaboration-aware themselves.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The collaboration framework is designed to be universal and application-agnostic, working with any application that runs on the operating system. By capturing events at the OS level rather than within individual applications, the system provides collaboration functionality across diverse applications without requiring each application to implement collaboration features.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Data Source

PatentUS7908325B1System and method for event-based collaboration
Publication Date: 2011.03.15 ORACLE AMERICAN INC
  • US7908325B1 patent drawing
  • US7908325B1 patent drawing
  • US7908325B1 patent drawing

AI summary

A first collaboration framework on a first computer system may intercept, via an operating system event handling mechanism on the first computer system, local input events for a first application executing on the first computer system. The first collaboration framework may also send messages including the intercepted input events to other collaboration frameworks executing on other respective computer systems. In response to receiving a message including an intercepted input event, each of the other collaboration frameworks may deliver the input event, via an operating system event handling mechanism to another application. A collaboration framework may deliver an input event intercepted on another computer system to a local application as if the input event were input locally. Delivered input events may cause applications on other computer systems to perform the same one or more actions as performed by the application for which the input event was originally intended.