MP-DCCP Proxy for Multipath DCCP Across NAT and Firewalls
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing DCCP services lack multipath support, leading to overstraining of communication paths and inability to establish connections, and firewalls and NAT units often only support UDP and TCP, limiting the use of DCCP despite its advantages for latency-sensitive applications.
Innovation Solution
A packet conversion device, specifically a MP-DCCP Proxy, converts non-MP-DCCP data traffic to MP-DCCP traffic and vice versa, enabling multipath transmission by using a first single or multipath interface and a packet conversion module to handle protocol conversions.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If DCCP services are implemented without multipath support, then existing systems can operate with simple single-path DCCP, but communication paths become overstrained and connections cannot be established
Solution Approach 1:
The patent introduces a proxy server as an intermediary component that bridges single-path DCCP clients and multipath-capable networks. The proxy receives single-path DCCP packets, converts them to multipath DCCP packets for distribution across multiple paths, and vice versa for incoming traffic. This mediator enables existing DCCP services to benefit from multipath transmission without requiring changes to the original DCCP implementations, resolving the contradiction between maintaining compatibility and achieving reliable multipath communication.
2Adaptability or versatility
If firewalls and NAT units only support UDP and TCP, then existing network infrastructure can be used, but DCCP cannot be properly routed through these devices
Solution Approach 1:
The proxy server acts as an intermediary that translates DCCP traffic into UDP/TCP formats for traversal through firewalls and NAT units. The proxy converts incoming UDP/TCP packets into DCCP packets for the destination, and reverse conversion for outgoing traffic. This enables DCCP to leverage existing UDP/TCP-based network infrastructure while maintaining DCCP's latency-sensitive application benefits, resolving the contradiction between infrastructure compatibility and protocol-specific transmission capability.
3Productivity
If single-path DCCP is used, then existing DCCP implementations can operate, but bandwidth and reliability are limited compared to multipath transmission
Solution Approach 1:
The proxy server centralizes the multipath scheduling function by receiving traffic from single-path DCCP clients and distributing it across multiple paths using an integrated multipath scheduler. This eliminates the need for complex multipath scheduler implementations in each endpoint device, allowing bandwidth aggregation through multipath transmission while maintaining simplicity at the client side. The proxy handles the complexity of path selection, load balancing, and congestion control centrally.
4Reliability
If MP-DCCP is implemented end-to-end, then multipath transmission is achieved, but existing DCCP services cannot communicate without modification
Solution Approach 1:
The proxy server serves as a translation layer that enables multipath DCCP communication without requiring modifications to existing DCCP implementations. Single-path DCCP clients communicate with the proxy using standard DCCP, while the proxy handles multipath conversion to multipath DCCP for transmission across multiple paths. This intermediary approach allows gradual deployment where only the proxy needs multipath support, while existing DCCP services remain unchanged, significantly reducing implementation complexity.
Data Source
AI summary
A packet conversion device includes: a first single path interface arranged for data packet transmission over one communication path or a first multipath interface arranged for data packet transmission over at least two communication paths, wherein the data traffic transmitted over the first single path interface or the first multipath interface is non-Multipath-Datagram Congestion Control Protocol (non-MP-DCCP) data traffic; a second multipath interface arranged for data packet transmission over at least two communication paths, wherein the data traffic transmitted over the second multipath interface is MP-DCCP data traffic; and a packet conversion module arranged to convert non-MP-DCCP data traffic to MP-DCCP data traffic according to a protocol conversion and/or to convert MP-DCCP data traffic to non-MP-DCCP data traffic according to a further protocol conversion for further transmission.


