File Modification Status Request for Collaboration

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In large-scale collaboration events over networks, such as video conferences, existing methods require frequent and inefficient communication of entire files, leading to high bandwidth and resource usage, especially when multiple users are updating shared files frequently.

Innovation Solution

Implementing conditioned requests that allow clients to request file modifications only when changes occur, using a 'when' condition rather than an 'if' condition, enabling the server to notify clients of changes without continuous polling, and communicating only the modifications rather than the entire file.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If the entire file is communicated between computers every time it is updated, then the file update is complete and accurate, but the bandwidth and network resources are excessively consumed

Engineering Contradiction:
Improvefile update completenessVSAvoidbandwidth consumption
Core Design Contradiction:
ReliabilityVSLoss of energy

Solution Approach 1:

The patent extracts only the modified portions of the file (file modifications) from the entire file and transmits only these changes between computers. This is achieved by identifying specific modified regions in the source file and transmitting only these regions, thereby reducing bandwidth consumption while maintaining file update completeness.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The patent segments the file into modified and unmodified portions, transmitting only the modified segments between computers. By dividing the file structure and identifying specific modified regions, the system reduces the amount of data transmitted while ensuring complete and accurate file updates at the destination.

Inventive Principle:
Principle #1Segmentation

2Speed

If continuous polling is used to check for file modifications, then the client receives updates promptly, but the network latency and resource consumption increase

Engineering Contradiction:
Improveupdate notification speedVSAvoidnetwork latency
Core Design Contradiction:
SpeedVSLoss of time

Solution Approach 1:

The patent establishes a file modification status request mechanism in advance, where the client requests modification status information from the server. The server then proactively notifies the client when modifications occur, eliminating the need for continuous polling and reducing network latency while maintaining prompt update notification.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent implements a feedback mechanism where the server monitors file modifications and automatically notifies clients when changes occur. This feedback loop ensures clients receive updates promptly without requiring continuous polling, thereby reducing network latency and resource consumption.

Inventive Principle:
Principle #23Feedback

3Reliability

If the entire file is transmitted to ensure accurate updates, then the file synchronization is reliable, but the communication overhead and network resources are excessively used

Engineering Contradiction:
Improvefile synchronization accuracyVSAvoidcommunication overhead
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent extracts and transmits only the modified portions of the file rather than the entire file. By identifying and transmitting only the specific modified regions, the system maintains reliable file synchronization while significantly reducing communication overhead and network resource usage.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The patent segments the file transmission into modified and unmodified portions, sending only the necessary modified segments between computers. This segmentation approach ensures accurate file synchronization while minimizing communication overhead and network resource consumption.

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS9436700B2Methods and program products for communicating file modifications during a collaboration event
Publication Date: 2016.09.06 IOCOM UK LTD
  • US9436700B2 patent drawing
  • US9436700B2 patent drawing
  • US9436700B2 patent drawing

AI summary

One example method for communicating a file modification during a collaboration event includes steps of a first computer communicating a file modification status request to a second computer, the status request including at least a file identifier and a file property. The second computer uses the file identifier from the request to identify a current property of a corresponding file. The second computer compares the current file property to the file property from the status request and communicates a response to the first computer when the current property does not match the property from the status request.