IPv6 Interface ID Filter for MPTCP Traffic Separation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current 3GPP specifications limit multipath TCP (MPTCP) implementation by allowing only a single IPv6 prefix within a PDN connection, restricting dual connectivity and traffic separation across different bearers, which hinders efficient use of dual LTE connections for improved throughput and link robustness.
Innovation Solution
Assigning a unique Interface Identifier (IID) to dedicated bearers and making the P-GW aware of this IID for traffic separation, allowing MPTCP to operate over two different cell layers with separate IP addresses, enabling full operator control and backward compatibility.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If a single IPv6 prefix is used within a PDN connection, then compliance with current 3GPP specifications is maintained, but multipath TCP functionality and traffic separation across different bearers are restricted
Solution Approach 1:
The invention segments the IPv6 address space by introducing multiple prefixes within a single PDN connection, allowing different prefixes to be assigned to different bearers. This enables traffic separation and multipath TCP functionality while maintaining compliance with 3GPP specifications through the use of a single PDN connection framework.
Solution Approach 2:
The invention adds a new dimension to IP address management by introducing the prefix level hierarchy within a PDN connection. Instead of only using interface identifiers within a single prefix, the solution operates at the prefix dimension, allowing multiple prefixes to coexist under one PDN connection, thereby enabling multipath TCP without increasing overall system complexity.
2Productivity
If multiple IP addresses are assigned within a single PDN connection, then traffic separation and MPTCP support are improved, but filter evaluation complexity and P-GW processing load increase
Solution Approach 1:
The invention applies local quality by associating specific packet filters with specific prefixes rather than evaluating all filters against all IP addresses. Each bearer's traffic is filtered based on its designated prefix, reducing the evaluation complexity from O(n*m) to O(n), where n is the number of filters and m is the number of prefixes.
Solution Approach 2:
The solution implements preliminary action by pre-associating packet filters with specific prefixes during bearer setup. This pre-linking mechanism ensures that when multiple IP addresses are active, the P-GW only needs to evaluate filters associated with the relevant prefix, significantly reducing real-time processing complexity.
3Reliability
If dual connectivity is implemented with separate IP addresses, then throughput and link robustness are enhanced, but backward compatibility and operator control are compromised
Solution Approach 1:
The invention achieves universality by designing a solution that simultaneously supports both legacy single-prefix PDN connections and new multi-prefix PDN connections. The P-GW and UE can operate in either mode depending on capability indicators, ensuring backward compatibility while enabling advanced multipath TCP functionality where supported.
Solution Approach 2:
The solution uses parameter changes by introducing capability indicators and optional parameters in existing 3GPP message flows (e.g., Bearer Resource Command, Bearer Resource Modification Request). These parameter changes allow the network to negotiate and activate multi-prefix functionality without breaking existing single-prefix deployments, maintaining backward compatibility while enabling enhanced reliability.
Data Source
Figure 1~2
Figure 3~4
Figure 5
AI summary
It is provided a method, comprising monitoring if a second data path is established for a flow, wherein a first internet protocol address is configured for the flow via a first data path between an apparatus performing the method and a packet data network; assigning, if the second data path is established, a second internet protocol address different from the first internet protocol address for the flow via the second data path, wherein at least a part of the first data path belongs to a radio access technology; at least a part of the second data path belongs to the radio access technology; and the part of the first data path is different from the part of the second data path.