Component Summary Interface for File Interaction Tracking

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current software applications do not allow users to selectively view only the components of interest from a large file without first accessing all components, limiting user experience and efficiency.

Innovation Solution

A system that maintains a record of user interactions with file components, evaluates these interactions to identify significant components, and presents a summary of these components in a user interface, allowing users to focus on the most relevant content.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Loss of information

If all components are distributed to users in a file, then users can access complete content, but users must view all components including those not of interest, increasing time consumption and reducing efficiency

Engineering Contradiction:
Improveimportant contentVSAvoidtime to view components
Core Design Contradiction:
Loss of informationVSLoss of time

Solution Approach 1:

The system performs preliminary analysis of user interactions with file components before the user needs to view them. By maintaining records of actions taken by users on components and evaluating these records to identify important components in advance, the system prepares a filtered summary that excludes irrelevant components, allowing users to immediately access only the content they need without viewing unnecessary components first

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system extracts and isolates only the important components from the complete file based on evaluated user interaction records. By taking out the identified important components and presenting them in a dedicated summary view, the system separates relevant content from irrelevant content, allowing users to access important information without being burdened by components not of interest

Inventive Principle:
Principle #2Taking out (Extraction)

2Productivity

If a summary of components is provided, then users can quickly identify important content, but the system must analyze and process user interaction records, increasing system complexity

Engineering Contradiction:
Improveuser efficiencyVSAvoidsystem complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The system uses a universal record evaluation mechanism that handles multiple types of user interactions (viewing, editing, sharing, commenting) through a single unified process. The same evaluation logic identifies important components across different file types and interaction patterns, reducing the need for separate analysis systems for each scenario and managing complexity through generalization

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

Solution Approach 2:

The system automatically maintains and evaluates user interaction records without requiring manual input or intervention. The record of actions taken by users is automatically captured and processed to identify important components, allowing the system to self-manage the complexity of analysis and summary generation without additional user burden or manual configuration

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS11392630B2Presenting a summary of components in a file
Publication Date: 2022.07.19 MICROSOFT TECHNOLOGY LICENSING LLC
  • US11392630B2 patent drawing
  • US11392630B2 patent drawing
  • US11392630B2 patent drawing

AI summary

Systems, methods, and software are disclosed herein to provide users with a summary of components in a file. A record is maintained of actions taken by users on a plurality of components in a file. The record is evaluated to identify one or more components of the plurality of components based on the actions taken by the users on the plurality of components in the file. In response to identifying the one or more components in the file, a summary of the plurality of components in the file is presented in a user interface comprising the one or more identified components of the plurality of components.