Multi-Host Multipath QUIC Transport with Nested Encapsulation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current data exchange protocols lack deep control over multiple network paths, making it difficult to maintain connectivity to relocating edge servers and intermittent device-to-device peers, and do not support seamless proxying of secure end-to-end transport layer connections.

Innovation Solution

Implementing a multi-hop, multipath QUIC (Quick UDP Internet Connections) protocol that enables secure transport by encapsulating inner QUIC packetized data within outer QUIC packetized data, allowing for flexible path selection and maintenance of connections through proxies, and using new frame types like PACKET and SWITCH to manage multiplexing and proxying without overhead.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If traditional transport protocols are used, then connection establishment is simple, but deep control over multiple network paths is lost

Engineering Contradiction:
Improvecontrol over network pathsVSAvoidprotocol complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent implements nested QUIC connections where an outer QUIC connection encapsulates inner QUIC connections. The outer connection provides the control plane for path management while inner connections carry data flows. This nesting structure enables deep control over multiple network paths while maintaining QUIC protocol efficiency and security throughout the hierarchy.

Inventive Principle:
Principle #7Nested doll (Nesting)

Solution Approach 2:

The patent segments the transport protocol into distinct outer and inner QUIC connections with separate flow identifiers. Each inner connection represents an independent data path that can be controlled and managed separately through the outer connection's control mechanisms, enabling granular path control without overwhelming complexity.

Inventive Principle:
Principle #1Segmentation

2Reliability

If direct end-to-end connections are used, then security is maintained, but connectivity during server relocation is lost

Engineering Contradiction:
Improveconnectivity during migrationVSAvoidconnection management complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent introduces an outer QUIC connection as an intermediary that bridges the client and destination endpoint while supporting server relocation. The outer connection acts as a control plane that can dynamically adjust path routing when servers migrate, maintaining connectivity without breaking the secure transport layer. This intermediary structure enables reliable connectivity during migration while managing complexity through protocol encapsulation.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Adaptability or versatility

If multiple separate connections are established for multipath communication, then path diversity is achieved, but overhead increases

Engineering Contradiction:
Improvemultipath capabilityVSAvoidprotocol overhead
Core Design Contradiction:
Adaptability or versatilityVSLoss of energy

Solution Approach 1:

The patent merges multiple data paths into a single outer QUIC connection that encapsulates multiple inner QUIC connections. This consolidation reduces protocol overhead by sharing the outer connection's control plane, security context, and connection state across multiple inner data-bearing connections, achieving multipath capability without the overhead of fully separate connection management for each path.

Inventive Principle:
Principle #5Merging (Combining)

Data Source

PatentUS11985062B2Methods and apparatuses for enabling multi-host multipath secure transport with QUIC
Publication Date: 2024.05.14 INTERDIGITAL PATENT HOLDINGS INC
  • US11985062B2 patent drawing
  • US11985062B2 patent drawing
  • US11985062B2 patent drawing

AI summary

Methods and apparatuses for enabling multi-host multipath secure transport with Quick User Datagram Protocol (UDP) Connections (QUIC) are described herein. A method performed by a client endpoint may involve sending, to a network node, a request to establish a QUIC connection with a destination endpoint, the request to establish the QUIC connection including a flow identifier (ID). The method may involve receiving, from the network node, a response including an indication that the request to establish the QUIC connection with the destination endpoint is accepted. The method may involve encapsulating inner QUIC packetized data within outer QUIC packetized data, the inner QUIC packetized data including the flow ID. The method may involve sending, to the network node, the outer QUIC packetized data for forwarding toward the destination endpoint based on the flow ID.