Collaboration Activity Summaries via Event Segmentation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In highly collaborative environments, users face cognitive overload due to the high volume and rate of collaboration activity events, with legacy systems failing to present meaningful summaries or interrelate actions among users, leading to incomprehensible displays.

Innovation Solution

The system generates candidate summary pages by grouping interaction events and scoring them to determine a comprehensible summary page, reducing the need for repeated database probing and improving human-machine interfaces.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Speed

If collaboration activity events are presented on the fly as they occur, then the system provides real-time collaboration information, but the user experiences cognitive overload due to high volume and rate of events

Engineering Contradiction:
Improvereal-time information deliveryVSAvoiduser comprehension
Core Design Contradiction:
SpeedVSEase of operation

Solution Approach 1:

The system segments the continuous stream of collaboration events into discrete, manageable time intervals (e.g., hourly, daily summaries). This segmentation transforms the overwhelming continuous flow into digestible chunks that users can process without cognitive overload, while still maintaining near-real-time awareness through frequent interval updates.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system implements periodic summarization where collaboration events are aggregated and presented at regular intervals rather than continuously. This periodic action allows the system to maintain real-time data collection while presenting information in controlled, manageable bursts that prevent user information overload.

Inventive Principle:
Principle #19Periodic action

2Loss of information

If all collaboration events are displayed to the user, then complete information is provided, but the user cannot comprehend the volume of events

Engineering Contradiction:
Improveinformation completenessVSAvoidinformation presentation complexity
Core Design Contradiction:
Loss of informationVSDevice complexity

Solution Approach 1:

The system extracts and highlights only the most significant collaboration events from the complete event stream, separating critical information from routine noise. This extraction maintains information completeness for system records while presenting a simplified, comprehension-friendly view to users by taking out only the essential events for display.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The system applies local quality by providing different levels of detail for different types of events or for different users based on their roles and preferences. Critical events receive detailed presentation while routine events are summarized, creating a non-uniform information presentation that optimizes comprehension while maintaining overall information completeness.

Inventive Principle:
Principle #3Local quality

3Quantity of substance

If legacy systems present individual events in sequence, then all events are recorded, but the events are not interrelated or summarized meaningfully

Engineering Contradiction:
Improveevent data volumeVSAvoidmeaningful context
Core Design Contradiction:
Quantity of substanceVSLoss of information

Solution Approach 1:

The system merges related collaboration events into consolidated summary entries that capture the essence of multiple individual events. For example, multiple edits to the same document by different users are merged into a single summary statement about collaborative document work, preserving the quantity of event data while creating meaningful contextual relationships between events.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The system introduces an intermediary summarization layer that processes individual events and generates meaningful contextual relationships. This intermediary layer analyzes event patterns, identifies relationships between events, and creates synthesized summaries that convey the underlying story and context, transforming raw event data into meaningful information.

Inventive Principle:
Principle #24Intermediary (Mediator)

4Reliability

If the system processes and presents all collaboration events, then comprehensive monitoring is achieved, but computational resources and network bandwidth are consumed

Engineering Contradiction:
Improvecollaboration monitoring accuracyVSAvoidcomputational resource consumption
Core Design Contradiction:
ReliabilityVSUse of energy by moving object

Solution Approach 1:

The system implements partial action by processing all events for system-wide monitoring purposes while presenting only a subset of summarized events to individual users. This allows comprehensive monitoring accuracy to be maintained in the backend while reducing frontend computational and network resource consumption by transmitting only essential summarized information.

Inventive Principle:
Principle #16Partial or excessive action

Solution Approach 2:

The system performs preliminary summarization and filtering of collaboration events before transmission to users. By pre-processing events into condensed summaries on the server side, the system maintains comprehensive monitoring capabilities while significantly reducing the computational and network resources required for event delivery and presentation to end users.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS12056163B2Collaboration activity summaries
Publication Date: 2024.08.06 BOX INC
  • US12056163B2 patent drawing
  • US12056163B2 patent drawing
  • US12056163B2 patent drawing

AI summary

System and methods for summarizing collaboration activity events into a plurality of pages that are then scored with respect to user-specific relevance that is based on a set of comprehensibility characteristic parameters. The collaboration activity events are summarized into groups of activities based on certain common attributes that are deemed to have quantitatively measurable relevance to the user. The groups of activities are assembled into a plurality of personalized candidate pages. The candidate summary pages are then scored using a function that includes parameters that serve to quantify how interesting or readable the particular user would find the particular candidate summary page. One or more of the higher scoring candidate summary pages are selected for presentation to the user.