IPsec Tunnel Management for WiFi Paging
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Maintaining idle IPsec tunnels over WiFi for mobile terminating VoIP calls in wireless communication networks wastes network resources by reducing bandwidth and processing capacity, as these tunnels are often kept active unnecessarily.
Innovation Solution
Implementing a system where a Non-Third-Generation-Partnership-Project Interworking Function (N3IWF) manages IPsec tunnels by tearing them down when idle and re-establishing them upon receiving a mobile terminating call, using location update information to page the user equipment (UE) device via WiFi or cellular connections as necessary.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If idle IPsec tunnels are maintained over WiFi for mobile terminating VoIP calls, then call delivery reliability is improved, but network resource efficiency deteriorates due to reduced bandwidth and processing capacity
Solution Approach 1:
The system dynamically manages IPsec tunnel states by transitioning from static maintenance to dynamic creation/deletion based on actual call needs. The N3IWF receives notifications about mobile terminating calls and creates IPsec tunnels only when necessary, rather than maintaining them continuously in idle state. This dynamic approach resolves the contradiction by adapting tunnel existence to actual service requirements.
Solution Approach 2:
The system changes the operational parameters of IPsec tunnels from persistent maintenance to on-demand creation. By modifying the tunnel lifecycle parameters (creation trigger, deletion trigger, maintenance interval) based on call event parameters, the system achieves both reliable call delivery and efficient resource utilization. The tunnel parameters are adjusted according to the presence or absence of active calls.
2Productivity
If IPsec tunnels are torn down when idle to conserve resources, then network resource efficiency is improved, but call delivery time increases due to tunnel re-establishment overhead
Solution Approach 1:
The system performs preliminary actions by pre-configuring tunnel creation parameters and maintaining tunnel state information in the N3IWF before actual calls arrive. When a mobile terminating call is notified, the N3IWF can rapidly recreate tunnels using pre-stored configuration data, reducing the effective re-establishment time. This preliminary preparation mitigates the time loss from tunnel teardown while maintaining resource efficiency.
3Reliability
If continuous tunnel maintenance is implemented, then call delivery reliability is improved, but energy consumption increases due to persistent network activity
Solution Approach 1:
The system implements periodic tunnel creation and deletion synchronized with call event periods rather than continuous maintenance. The N3IWF creates tunnels periodically when call events occur and deletes them when calls end, transforming continuous energy-consuming maintenance into periodic actions aligned with actual service delivery needs. This reduces overall energy consumption while maintaining reliability during active service periods.
Data Source
AI summary
A device may include a processor configured to detect that an Internet Protocol Security (IPsec) tunnel from a user equipment (UE) device connected via a WiFi connection has become idle, based on the IPsec tunnel meeting an idleness criterion, and instruct the UE device to tear down the IPsec tunnel, in response to detecting that the IPsec tunnel from the UE device connected via the WiFi connection meets the idleness criterion. The device may be further configured to receive a mobile terminating call for the UE device; establish a new IPsec tunnel to the UE device via the WiFi connection, in response to receiving the mobile terminating call for the UE device; and forward the received mobile terminating call to the UE device via the established new IPsec tunnel.