Single APN for Multiple PDN Connections
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current wireless communication systems require separate access point names (APNs) and binding cache entries for each packet data network (PDN) connection, leading to resource-intensive deployments and increased costs due to the need for multiple APNs and binding cache entries.
Innovation Solution
A method that uses a single APN for multiple PDN connections, allocating unique IP addresses based on a binding generated from the communications device's identifier, APN identifier, and an additional parameter such as a counter value, nonce, or system time, allowing for efficient IP address allocation and reduced resource utilization.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If separate APNs and binding cache entries are created for each PDN connection, then each connection can be properly managed and routed, but resource utilization increases and deployment costs increase
Solution Approach 1:
The patent merges multiple PDN connections under a single APN identifier, allowing multiple bindings to share one APN. This combines what were previously separate resources (APNs and binding cache entries) into a shared structure, reducing the total quantity of binding cache entries needed while maintaining proper connection management through unique binding identifiers.
Solution Approach 2:
The single APN is designed to serve multiple PDN connections simultaneously, making it a universal resource that performs multiple functions. Instead of requiring dedicated APNs for each connection, the universal APN handles multiple connections through differentiated binding cache entries that include additional parameters to distinguish between connections.
2Ease of operation
If separate APNs are used for each PDN connection, then routing is simplified, but the number of access points and deployment complexity increases
Solution Approach 1:
The patent combines multiple routing functions into a single APN configuration. Instead of requiring separate APN configurations for each PDN connection, the merged approach uses one APN with multiple bindings, each containing routing information for different PDNs, thereby reducing access point configuration complexity while maintaining routing simplicity.
Solution Approach 2:
The patent adds an additional dimension to the binding cache entry structure by including parameters beyond just the APN identifier. This dimensional expansion allows the system to differentiate between multiple PDN connections within a single APN context, enabling complex routing logic to be handled through enhanced data structures rather than multiple APN instances.
3Reliability
If multiple binding cache entries are created for multiple PDN connections, then each connection is properly tracked, but resource consumption and deployment costs increase
Solution Approach 1:
The patent merges multiple connection tracking functions into a single binding cache entry structure that serves multiple PDN connections. By combining what were previously separate tracking resources into one shared structure with differentiated parameters, the system reduces overall resource consumption while maintaining reliable tracking of each individual connection through unique binding identifiers.
Solution Approach 2:
The binding cache entry is designed as a universal structure that can track multiple PDN connections simultaneously. Instead of requiring dedicated tracking resources for each connection, the universal binding cache entry handles multiple connections through additional parameters, reducing resource consumption while ensuring each connection is properly tracked and managed.
Data Source
AI summary
A system and method for name binding for multiple packet data network access is provided. A method for communications device operation includes attaching to a first packet data network through an access network, thereby creating an access point name, triggering a connection to a second packet data network through the access network, and receiving an acknowledgement to the trigger. The triggering occurs over the access point name, and the acknowledgement comprises an address for the communications device. The address is allocated by a gateway for the second packet data network, and the address is allocated based on a binding generated from an identifier of the communications device, an identifier of the access point name, and a parameter.