Container File Transfer via Selective Component Transmission

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Transferring large files over networks is time-consuming and power-intensive, especially for mobile devices, and increases security and data corruption risks due to bandwidth restrictions and the need to transmit duplicate data.

Innovation Solution

A method and system that minimizes data transfer by transmitting metadata first, allowing the server to determine which components of a container file are needed, and only sending those components, using techniques like caching and hash values to identify duplicate data, thereby reducing the amount of data transmitted and cached.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If the entire container file is transmitted over the network, then the server receives complete data, but transmission time and power consumption increase significantly

Engineering Contradiction:
Improvedata completenessVSAvoidtransmission time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The container file is divided into multiple component files, and the system transmits only the necessary components rather than the entire file. This segmentation allows selective transmission of data based on what the server actually needs, reducing overall transmission time while maintaining data completeness for required elements.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system extracts and transmits only the specific component files that the server needs from the container file, rather than transmitting the complete container. This extraction approach eliminates unnecessary data transmission, directly reducing transmission time while ensuring the server receives all required components.

Inventive Principle:
Principle #2Taking out (Extraction)

2Reliability

If the entire container file is transmitted over the network, then all data is available at the server, but power consumption increases significantly

Engineering Contradiction:
Improvedata availabilityVSAvoidpower consumption
Core Design Contradiction:
ReliabilityVSUse of energy by moving object

Solution Approach 1:

The container file structure enables segmentation of data into discrete components, allowing the system to transmit only the necessary subset. This reduces the total data volume transmitted over the network, directly lowering power consumption while ensuring all required components are available at the server.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system performs partial transmission by sending only the specific components needed by the server rather than the complete container file. This partial action approach reduces power consumption by minimizing network transmission activity while still achieving the goal of making necessary data available at the server.

Inventive Principle:
Principle #16Partial or excessive action

3Reliability

If duplicate data is transmitted over the network, then all required data is ensured to be sent, but network bandwidth is wasted and transmission efficiency decreases

Engineering Contradiction:
Improvedata delivery assuranceVSAvoidtransmission efficiency
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The container file structure segments data into identifiable components with unique characteristics. This segmentation enables the system to recognize and eliminate duplicate components before transmission, ensuring each unique component is sent only once. This maintains data delivery assurance while significantly improving transmission efficiency by eliminating redundant data transfer.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system uses hash values as a parameter to identify and compare component files. By changing the representation of data from raw content to hash-based identifiers, the system can efficiently detect duplicates and avoid transmitting redundant components, thereby improving transmission efficiency while maintaining complete data delivery.

Inventive Principle:
Principle #35Parameter changes

4Reliability

If large files are transmitted over the network, then complete data is transferred, but security risks and data corruption risks increase

Engineering Contradiction:
Improvedata transfer completenessVSAvoidsecurity and data corruption risks
Core Design Contradiction:
ReliabilityVSObject-affected harmful factors

Solution Approach 1:

The container file is segmented into smaller component files for transmission. This segmentation reduces the size of individual data transfers, thereby reducing the attack surface and risk of data corruption during transmission. Each smaller component can be independently verified and retransmitted if needed, improving security and reliability.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system transmits only the partial set of components that the server actually needs rather than the complete container file. This partial transmission approach reduces the total data exposure to security risks and data corruption, while still achieving complete delivery of necessary data through selective component transfer.

Inventive Principle:
Principle #16Partial or excessive action

Data Source

PatentEP3375168B1Transferring a container file over a network
Publication Date: 2021.03.10 MICROSOFT TECHNOLOGY LICENSING LLC
  • EP3375168B1 patent drawingFigure 1
  • EP3375168B1 patent drawingFigure 2
  • EP3375168B1 patent drawingFigure 3

AI summary

Systems, components, devices, and methods for transferring files are provided. An example file is a container file comprising a plurality of component files. A non-limiting example method is a method for transferring a container file over a network to a remote device. The method includes the step of accessing a container file, the container file comprising a plurality of components. The method also includes the step of transmitting metadata information for the plurality of components to the remote device. The method further includes the step of determining components from the plurality of components to transmit to the remote device. The method additionally includes the step of transmitting component data items for the determined components to the remote device.