Static IP Route Aggregation Across Shared-APN PGW Networks
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing systems face challenges in efficiently managing static IP address allocation in wireless networks, particularly when multiple PGWs/GGSNs serve the same APN, leading to increased routing complexity and burden on site routers due to the need for numerous /32 (ipv4) or 64 (Ipv6) routes for static IP address allocations.
Innovation Solution
A method is introduced where a Mobility Management Entity (MME)/Serving GPRS Support Node (SGSN) selects a dedicated PDN Gateway (PGW)/Gateway GPRS Support Node (GGSN) based on the Access Point Name (APN) used for PDN establishment, allowing dedicated PGWs/GGSNs to advertise a complete pool of static IP addresses instead of individual /32 (ipv4) or 64 (Ipv6) routes, thereby optimizing routing.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If multiple PGWs/GGSNs are deployed serving the same APN with individual /32 or 64 routes for static IP allocation, then static IP address allocation is supported, but routing complexity and burden on site routers increases
Solution Approach 1:
The patent consolidates multiple individual /32 or 64 routes into a single aggregated route advertisement from the dedicated PGW/GGSN to the site router. Instead of each PGW/GGSN advertising separate routes for static IP addresses, the dedicated PGW/GGSN advertises a single route covering the entire pool of static IP addresses, thereby reducing routing complexity while maintaining support for static IP allocation.
2Measurement precision
If individual /32 (ipv4) or 64 (Ipv6) routes are advertised for each static IP address, then precise routing is achieved, but the number of routes and routing burden increases
Solution Approach 1:
The patent merges multiple individual route advertisements into a single aggregated route advertisement. The dedicated PGW/GGSN advertises one route covering the complete pool of static IP addresses instead of advertising separate routes for each individual address, thereby maintaining routing precision while dramatically reducing the quantity of routes.
3Productivity
If a dedicated PGW/GGSN is configured with a pool of static IP addresses, then routing efficiency is improved, but configuration complexity increases
Solution Approach 1:
The dedicated PGW/GGSN is configured with a universal pool of static IP addresses that serves multiple purposes: it handles static IP allocation for multiple UEs, advertises a single aggregated route to the site router, and maintains routing efficiency. This multi-functional configuration reduces overall system complexity despite the dedicated setup.
Data Source
AI summary
A method for PGWs/GGSNs to route a subnet or complete pool of static IP addresses/prefixes instead of /32 (ipv4) or 64 (Ipv6) towards a site router in an Evolved Packet System (EPS)/Packet System Network (PDN) with deployments where multiple PGWs/GGSNs are each deployed serving the same APN, and the selection of a PDN Gateway (PGW)/Gateway GPRS Support Node (GGSN) is performed by a Mobility Management Entity (MME)/Serving GPRS Support Node (SGSN) based on the Access Point Name (APN) used for PDN establishment.