Kernel Event Triggers for Unified Content Collaboration

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Collaborative workflows across different content item types and systems face challenges due to disjointed workflows, leading to the use of parallel processes for content manipulation and communication, which are retained from traditional desktop file management paradigms and legacy applications.

Innovation Solution

Implementing kernel event triggers on client devices networked with a content management system to detect kernel-level file events, retrieve and perform instructions, and manage access rights, collaboration data, and presentation of content items, thereby integrating content management and communication within a unified workflow.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If kernel event triggers are implemented to integrate content management and communication, then collaborative workflow efficiency is improved, but system complexity increases

Engineering Contradiction:
Improvecollaborative workflow efficiencyVSAvoidsystem complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The patent merges content management and communication workflows into a unified system by implementing kernel event triggers that automatically initiate communication actions (such as sending notifications or starting video conferences) when specific file events occur. This integration eliminates the need for separate parallel workflows, improving collaborative efficiency while managing complexity through automated event-driven architecture.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The system performs preliminary actions by pre-configuring event triggers and associated instructions in advance. When a kernel-level file event occurs (such as a document being edited or saved), the predetermined instructions are automatically executed, enabling seamless integration of communication and content management without requiring real-time complex decision-making, thus improving workflow efficiency.

Inventive Principle:
Principle #10Preliminary action

2Speed

If kernel level event detection is implemented, then real-time collaboration capability is improved, but processing overhead increases

Engineering Contradiction:
Improvereal-time collaboration capabilityVSAvoidprocessing overhead
Core Design Contradiction:
SpeedVSUse of energy by moving object

Solution Approach 1:

The patent extracts and monitors only specific kernel-level file events that are relevant to collaboration (such as create, modify, delete operations on shared documents) rather than monitoring all system events. This selective event detection enables real-time collaboration capabilities while minimizing processing overhead by focusing computational resources only on meaningful collaboration-triggering events.

Inventive Principle:
Principle #2Taking out (Extraction)

3Reliability

If access control and rights management are enforced, then security is improved, but ease of operation deteriorates

Engineering Contradiction:
ImprovesecurityVSAvoidease of operation
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

The system implements self-service access control by automatically enforcing rights management policies based on pre-configured rules and event triggers. When users perform file operations, the system automatically checks and enforces access permissions without requiring manual security approvals or complex user interventions. This maintains high security while preserving ease of operation, as users can work freely within their authorized boundaries without constant security management overhead.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS11467891B2Kernel event triggers for content item security
Publication Date: 2022.10.11 DROPBOX INC
  • US11467891B2 patent drawing
  • US11467891B2 patent drawing
  • US11467891B2 patent drawing

AI summary

The present technology pertains to responding to a kernel level file event for a content item and presenting a file event window associated with the content item. A client device can detect the kernel level file event for the content item. This can be accomplished using a kernel extension on a client device that is networked with a content management system. The client device can then retrieve data associated with the content item, including an instruction for the content item. The client device can then perform the instruction. This instruction can be to retrieve collaboration data from the content management system and present the collaboration data in a file event window.