IGP Routing Message Compression for Lower Flooding Overhead

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The inefficiency and resource strain in networks implementing Interior Gateway Protocols (IGPs) due to excessive data flooding, which affects bandwidth, throughput, and latency, is exacerbated by data transmission limits in existing IGPs like IS-IS and OSPFv2/v3.

Innovation Solution

Implementing a compression scheme within network elements (NEs) using either stateless or stateful compression, where a central entity or designated NE generates dictionaries to map frequently occurring bit strings to codewords, reducing data volume before transmission across the network.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If data is transmitted using existing IGP protocols (IS-IS, OSPFv2/v3), then routing information can be exchanged among network elements, but network bandwidth is consumed excessively and throughput is reduced due to data flooding

Engineering Contradiction:
Improverouting information exchangeVSAvoidbandwidth consumption
Core Design Contradiction:
ReliabilityVSLoss of energy

Solution Approach 1:

The patent applies parameter changes by modifying the data representation format in IGP messages. Specifically, it changes the encoding of IP prefixes from traditional formats to a compressed format using variable-length field encoding and prefix aggregation techniques. This allows the same routing information to be transmitted with reduced bit length, directly addressing the bandwidth consumption issue while maintaining protocol functionality.

Inventive Principle:
Principle #35Parameter changes

2Reliability

If routing information is flooded throughout the network to ensure all network elements have complete topology data, then link-state routing can be maintained, but network latency increases due to the volume of data transmission

Engineering Contradiction:
Improvelink-state routing maintenanceVSAvoidnetwork latency
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent reduces latency by changing the transmission parameters of routing data. It implements variable-length field encoding where common prefix patterns are represented more compactly, and uses prefix aggregation to combine multiple routing entries into fewer, more concise representations. These parameter changes reduce the total data volume that must be transmitted and processed during IGP updates, thereby reducing network latency while maintaining complete topology information.

Inventive Principle:
Principle #35Parameter changes

3Productivity

If compression schemes are implemented to reduce data volume, then bandwidth efficiency improves and throughput increases, but device complexity increases due to compression and decompression operations

Engineering Contradiction:
Improvenetwork throughputVSAvoidcompression operation complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The patent applies preliminary action by pre-defining compression rules and encoding schemes that are incorporated into the IGP protocol specification itself. The compression methodology is built into the protocol framework, with predefined patterns for prefix aggregation and variable-length encoding that network elements can implement without complex runtime decision-making. This reduces the operational complexity at each device while achieving significant compression ratios.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentEP3900192B1Compressed data transmissions in networks implementing interior gateway protocol
Publication Date: 2025.08.06 HUAWEI TECH CO LTD
  • EP3900192B1 patent drawingFigure 1
  • EP3900192B1 patent drawingFigure 2
  • EP3900192B1 patent drawingFigure 3

AI summary

A method is performed by a network element (NE) in a network implementing an Interior Gateway Protocol (IGP). The method comprises generating a message comprising a header and data, wherein the header comprises a length of the data prior to compressing the data, a length of the data after compressing the data, and a compression identifier, compressing the data based on a compression scheme identified by the compression identifier to obtain compressed data, and forwarding a compressed message comprising the header and the compressed data to other NEs in the network.