HTTP Request Transmission with Overlapping CDN Byte-Range Validation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The MPHTTP technology, which divides an original HTTP request into multiple requests to utilize both Wi-Fi and cellular networks for higher bandwidth, often results in inconsistent data when pulling from different CDN servers, leading to invalid data splicing and disrupted service.

Innovation Solution

The method involves allocating overlapping byte ranges to different CDN servers to ensure data consistency by downloading and comparing data from these servers before splicing, adjusting ranges if necessary to maintain consistency, and using network-specific requests to optimize performance.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If an original HTTP request is divided into multiple HTTP requests to pull data from different CDN servers, then aggregated bandwidth is increased and download speed is improved, but data consistency cannot be guaranteed and spliced data becomes invalid

Engineering Contradiction:
Improvedownload speedVSAvoiddata consistency
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The patent segments the original HTTP request into multiple byte range requests distributed across different CDN servers to increase download speed. Each segment is independently fetched parallelly, achieving aggregated bandwidth utilization while maintaining the ability to reconstruct the complete data through splicing.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent implements a feedback mechanism where the system monitors data consistency between parallel requests in real-time. When inconsistency is detected, the system automatically triggers re-fetching of specific byte ranges from alternative CDN servers, ensuring data reliability without sacrificing overall download performance.

Inventive Principle:
Principle #23Feedback

2Adaptability or versatility

If data is pulled from different CDN servers through cross-network access, then network utilization is optimized and bandwidth aggregation is achieved, but access reliability decreases and download may fail

Engineering Contradiction:
Improvenetwork utilizationVSAvoidaccess reliability
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The patent dynamically changes network parameters by selecting appropriate CDN servers based on network conditions, server response characteristics, and byte range requirements. This adaptability allows the system to optimize for both speed and reliability by routing requests through the most reliable available paths.

Inventive Principle:
Principle #35Parameter changes

Solution Approach 2:

The patent prepares backup CDN server options and alternative byte range allocations in advance. When a primary CDN server fails or responds poorly, the system has pre-configured fallback options ready, ensuring continuous operation without significant interruption to the download process.

Inventive Principle:
Principle #11Beforehand cushioning (Prior cushioning)

3Productivity

If byte ranges are allocated to multiple CDN servers for parallel data retrieval, then download efficiency is improved, but data validation and consistency checking become more complex

Engineering Contradiction:
Improvedownload efficiencyVSAvoiddata validation complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The patent introduces an intermediary validation layer that coordinates between multiple CDN server requests. This mediator component standardizes the validation process by implementing uniform byte range checking and data splicing logic, reducing the overall system complexity despite the increased number of parallel operations.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent uses copying mechanisms where complete data blocks are fetched from multiple CDN servers as redundant copies. These copies are then validated against each other through simple comparison operations, making the validation process more straightforward than complex verification of partial data segments.

Inventive Principle:
Principle #26Copying

Data Source

PatentEP4047942B1HTTP request transmission method and device
Publication Date: 2025.07.30 HUAWEI TECH CO LTD
  • EP4047942B1 patent drawingFigure 1~2
  • EP4047942B1 patent drawingFigure 3
  • EP4047942B1 patent drawingFigure 4

AI summary

This application discloses an HTTP request transmission method and a device. The HTTP request transmission method and the device relate to the field of electronic devices, and resolve a problem that data finally obtained through splicing is invalid because dividing an original HTTP request into a plurality of HTTP requests to pull data from different CDN servers may cause inconsistency of the pulled data. When an electronic device needs to download data from a plurality of CDN servers, an overlapping range may be designed for byte ranges allocated to the different CDN servers. This means that the electronic device downloads data in the overlapping range from all the different CDN servers. Therefore, this part of data is used to check consistency of the data pulled from the different CDN servers. When determining that the data pulled from the different CDN servers is consistent, the electronic device may splice the data to obtain finally required data.