WLCP Tunneling for PDN Connection Management
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current technologies are unable to efficiently manage multiple Packet Data Network (PDN) connections over Trusted WLAN Access Networks, particularly due to address overlapping issues and limitations in existing tunneling solutions, which restrict the ability to provide multiple concurrent services and impose functional restrictions on user equipment.
Innovation Solution
A below-Layer 3 (L3) tunneling protocol, known as the Wireless LAN Control Protocol (WLCP), is introduced to establish and control tunnels for PDN connections, using identifiers such as MN ID, APN, and MAC addresses to differentiate and manage multiple PDN connections, allowing for efficient traffic separation and management.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If existing tunneling solutions are used for PDN connections over WLAN, then protocol compatibility is maintained, but multiple concurrent PDN connections cannot be established due to address overlapping issues
Solution Approach 1:
The patent segments the tunnel identification into two separate identifiers: a first identifier for uplink traffic (UE to network) and a second identifier for downlink traffic (network to UE). This segmentation allows the network to distinguish between multiple PDN connections even when IP addresses overlap, enabling multiple concurrent connections without requiring complex modifications to the UE.
Solution Approach 2:
The patent introduces a new control protocol as an intermediary layer between the UE and the existing tunneling protocol. This intermediary protocol handles the establishment, modification, and release of tunnels, and manages the assignment of first and second identifiers. By placing this intelligence in the network infrastructure rather than the UE, the solution maintains backward compatibility while enabling multiple PDN connections.
2Reliability
If a single identifier is used for tunnel identification in both uplink and downlink, then protocol simplicity is maintained, but address overlapping issues prevent proper traffic differentiation
Solution Approach 1:
The patent divides the tunnel identification function into two separate identifiers: a first identifier embedded in uplink packets (UE to network) and a second identifier embedded in downlink packets (network to UE). This segmentation enables reliable traffic differentiation even when IP addresses overlap between different PDN connections, as the tunnel identifiers provide an additional layer of distinction that the network can use to properly route traffic.
3Productivity
If multiple PDN connections are established with overlapping IP addresses, then service concurrency is improved, but traffic routing becomes ambiguous
Solution Approach 1:
The patent segments the routing identification into two parts: IP addresses for network layer routing and separate first/second identifiers for tunnel-level identification. This allows multiple PDN connections with overlapping IP addresses to coexist, as the network uses the tunnel identifiers (first identifier in uplink, second identifier in downlink) to unambiguously route traffic to the correct PDN connection despite IP address overlaps.
Solution Approach 2:
The patent introduces a control protocol as an intermediary that manages the assignment and coordination of first and second identifiers. This intermediary layer resolves the routing ambiguity by ensuring that each PDN connection has uniquely identifiable tunnel markers, allowing concurrent services with overlapping IP addresses to be properly distinguished and routed.
Data Source
AI summary
Establishing and controlling a tunnel for carrying a PDN connection between a first node and a second node. The first node sends a request to set up a tunnel, the request including a first identifier. The first node then receives a second identifier for use in identifying the tunnel when receiving data sent from the second node to the first node. Data packets are sent from the first node, the data packets including the first and/or second identifiers for identifying the tunnel from the first node to the second node. Data packets are received from the second node, the data packets including the second identifier from the second node to the first node.