WebDAV Client Byte-Range Data Access Method

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional WebDAV GET request methods are inefficient when dealing with large data files, as they often result in unnecessary compute load on servers and high bandwidth usage by downloading entire files instead of exact byte-ranges, especially in scenarios with random access patterns and large data storage across multiple systems.

Innovation Solution

The Explicit Access method, where a WebDAV client bypasses caching and sends exact byte-range requests to the server, receiving and delivering only the requested data without caching it, thereby avoiding unnecessary data transfer and compute load.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If conventional WebDAV GET request methods are used to access data from a server, then the client can retrieve data from remote storage, but the client downloads entire files instead of exact byte-ranges, resulting in high bandwidth usage and unnecessary compute load on the server

Engineering Contradiction:
Improvedata access efficiencyVSAvoidbandwidth usage
Core Design Contradiction:
ProductivityVSLoss of energy

Solution Approach 1:

The patent segments the data file into discrete byte-range portions, allowing the client to request only the specific segments needed rather than downloading the entire file. This is achieved through HTTP Range requests that specify exact byte-range parameters, enabling precise data retrieval and reducing network bandwidth consumption.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent extracts and retrieves only the specific byte-range portions of data that are actually needed from the server, rather than transferring the complete file. This extraction approach removes unnecessary data transfer, reducing bandwidth usage and server compute load while maintaining data access functionality.

Inventive Principle:
Principle #2Taking out (Extraction)

2Productivity

If conventional WebDAV GET request methods are used to access data from a server, then the client can retrieve data from remote storage, but the client downloads entire files instead of exact byte-ranges, resulting in unnecessary compute load on the server

Engineering Contradiction:
Improvedata access efficiencyVSAvoidserver compute load
Core Design Contradiction:
ProductivityVSPower

Solution Approach 1:

The patent segments the data file into discrete byte-range portions, allowing the client to request only the specific segments needed rather than downloading the entire file. This is achieved through HTTP Range requests that specify exact byte-range parameters, enabling precise data retrieval and reducing network bandwidth consumption.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent extracts and retrieves only the specific byte-range portions of data that are actually needed from the server, rather than transferring the complete file. This extraction approach removes unnecessary data transfer, reducing bandwidth usage and server compute load while maintaining data access functionality.

Inventive Principle:
Principle #2Taking out (Extraction)

3Speed

If the client caches data locally to avoid redundant requests, then future requests can be fulfilled faster, but the client consumes more bandwidth and storage by caching entire files instead of exact byte-ranges

Engineering Contradiction:
Improvedata retrieval speedVSAvoidbandwidth usage
Core Design Contradiction:
SpeedVSLoss of energy

Solution Approach 1:

The patent segments the data file into discrete byte-range portions, allowing the client to request only the specific segments needed rather than downloading the entire file. This is achieved through HTTP Range requests that specify exact byte-range parameters, enabling precise data retrieval and reducing network bandwidth consumption.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent implements local caching with quality differentiation, where the client caches only the specific byte-range portions that are actually needed rather than caching entire files. This selective caching approach optimizes local storage usage and reduces bandwidth consumption while maintaining fast retrieval for previously accessed data segments.

Inventive Principle:
Principle #3Local quality

4Speed

If the client caches data locally to avoid redundant requests, then future requests can be fulfilled faster, but the client consumes more storage by caching entire files instead of exact byte-ranges

Engineering Contradiction:
Improvedata retrieval speedVSAvoidstorage consumption
Core Design Contradiction:
SpeedVSVolume of stationary object

Solution Approach 1:

The patent segments the data file into discrete byte-range portions, allowing the client to request only the specific segments needed rather than downloading the entire file. This is achieved through HTTP Range requests that specify exact byte-range parameters, enabling precise data retrieval and reducing network bandwidth consumption.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent implements local caching with quality differentiation, where the client caches only the specific byte-range portions that are actually needed rather than caching entire files. This selective caching approach optimizes local storage usage and reduces bandwidth consumption while maintaining fast retrieval for previously accessed data segments.

Inventive Principle:
Principle #3Local quality

Data Source

PatentUS9178931B2Method and system for accessing data by a client from a server
Publication Date: 2015.11.03 CUBIC DIGITAL INTELLIGENCE INC
  • US9178931B2 patent drawing
  • US9178931B2 patent drawing
  • US9178931B2 patent drawing

AI summary

A system and a method for accessing data by a client computer system from a server computer system, the client computer system including one or more processors configured to execute computer program modules, are described. The method includes receiving, by the client computer system from an application program, a read request to read at least a portion of a data file; sending, by the client computer system to the server computer system, a request for exact data corresponding to the at least the portion of the data file requested by the application program in the read request; receiving, by the client computer system from the server computer system, a response to the request including the exact data requested by the client computer system; and providing, by the client computer system to the application program, the exact data in response to the read request.