Tracking PDP Context for Mobile Node Reachability
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current DNS protocols face challenges in coordinating mobility and network access for multiple end users, particularly in conserving IP addresses and radio bearer resources, especially for mobile nodes that are attached but not necessarily connected at the IP layer.
Innovation Solution
The proposed solution involves a communication system where a Gateway GPRS Support Node (GGSN) acts as a dynamic DNS server, allocating and updating IP addresses for mobile nodes, and establishing a tracking PDP context without assigning an IP address, allowing for network-initiated data calls and conserving resources.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If a mobile node is attached to the network at the IP layer to ensure constant reachability, then network accessibility is improved, but IP addresses and radio bearer resources are consumed continuously
Solution Approach 1:
The patent segments the traditional IP layer attachment into two distinct layers: the application layer maintains a persistent tracking PDP context with the network, while the IP layer connection is established only temporarily when data transmission is actually needed. This segmentation allows the mobile node to be reachable at the application layer without continuously consuming IP addresses and radio bearer resources at the IP layer.
Solution Approach 2:
The tracking PDP context is established in advance at the application layer before any actual data communication occurs. This preliminary action ensures the mobile node is pre-registered and reachable in the network, but without triggering the consumption of expensive IP addresses and radio bearer resources until truly necessary.
2Adaptability or versatility
If DNS protocols are used to coordinate mobility for multiple end users, then network management capability is improved, but system complexity increases
Solution Approach 1:
The patent extracts the mobility coordination function from the complex DNS protocol framework and implements it through a simplified tracking PDP context mechanism at the application layer. This extraction removes the burden of DNS protocol coordination while maintaining the essential mobility management capability, thereby reducing system complexity.
Solution Approach 2:
The tracking PDP context acts as an intermediary mechanism that simplifies mobility coordination. Instead of relying on complex DNS protocols to track and manage mobile nodes, the tracking PDP context provides a direct, streamlined method for the network to maintain awareness of mobile node availability and initiate data calls when needed.
3Quantity of substance
If a tracking PDP context is established without an IP address, then resource conservation is improved, but network-initiated data call capability must be carefully managed
Solution Approach 1:
The patent implements a dynamic approach where the tracking PDP context exists in a suspended state without an IP address, and only transitions to an active IP-connected state when a network-initiated data call is actually required. This dynamic state transition allows resource conservation during idle periods while maintaining the capability to establish full IP connectivity on demand.
Solution Approach 2:
The system automatically manages the tracking PDP context and IP address allocation based on actual communication needs. When the network needs to initiate a data call to a mobile node, the system self-servicefully establishes the IP connection through the existing tracking context, eliminating the need for manual configuration or complex management overhead.
Data Source
AI summary
A method is provided in one example embodiment and includes communicating an access request message associated with a mobile node, receiving an access accept message that includes domain name data associated with the mobile node, and communicating a packet data protocol (PDP) context accept message for a tracking PDP context associated with the mobile node without associating an internet protocol (IP) address to the mobile node. The tracking PDP context identifies that the mobile node is available to receive network data. In more particular embodiments, the access request message includes an International Mobile Subscriber Identity (IMSI) associated with the mobile node, and the domain name data includes a fully qualified domain name. In still other embodiments, the tracking PDP includes a protocol configuration option (PCO) indicating that an IP address is not required for the mobile node.