Static IP Pool Route Aggregation for Site Router Scalability

Resolve Bottlenecks,
Find Innovative Solutions
Generate 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 burden on site routers due to numerous /32 (ipv4) or 64 (Ipv6) route advertisements for static IP address allocations.

Innovation Solution

Implementing a method 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 complete static IP pools instead of individual /32 (ipv4) or 64 (Ipv6) addresses to site routers.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If multiple PGWs/GGSNs are deployed serving the same APN with individual /32 or 64 route advertisements for static IP addresses, then static IP address allocation is supported, but the burden on site routers increases significantly

Engineering Contradiction:
Improvestatic IP address allocation capabilityVSAvoidsite router burden
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent consolidates multiple individual /32 or 64 route advertisements into a single aggregated route advertisement representing the entire static IP address pool. This merging approach maintains the capability to support static IP address allocation while significantly reducing the number of routing entries that site routers must maintain and process.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The dedicated PGW/GGSN is configured to handle multiple static IP address allocations from a unified pool, making it a universal endpoint for static IP routing. This multi-functional approach allows the router to serve multiple customers or services through a single routing advertisement rather than requiring separate advertisements for each individual address.

Inventive Principle:
Principle #6Universality (Multi-functionality)

2Measurement precision

If individual /32 (ipv4) or 64 (Ipv6) addresses are advertised to site routers for each static IP allocation, then precise routing is achieved, but scalability is reduced

Engineering Contradiction:
Improverouting precisionVSAvoidnetwork scalability
Core Design Contradiction:
Measurement precisionVSProductivity

Solution Approach 1:

The patent merges multiple precise individual address advertisements into a single aggregated advertisement that represents the entire static IP pool. This maintains routing precision at the pool level while enabling scalability by reducing the number of routing entries that need to be propagated and maintained across the network.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The patent transitions from advertising individual addresses (zero-dimensional granularity) to advertising an aggregated pool (higher-dimensional aggregation). This dimensional change allows the network to maintain precise routing capabilities while operating at a more scalable aggregation level, effectively trading address-level granularity for network-wide scalability.

Inventive Principle:
Principle #17Another dimension (Dimensionality change)

Data Source

PatentEP4597981A1System and method for optimizing route advertisements for static IP address allocation
Publication Date: 2025.08.06 MAVENIR SYST INC
  • EP4597981A1 patent drawingFigure 1
  • EP4597981A1 patent drawingFigure 2
  • EP4597981A1 patent drawingFigure 3

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.