IFIT Flow Configuration via BGP to Cut Packet Overhead

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The deployment of bidirectional IFIT (in-situ Flow Information Telemetry) increases the size of service packets, requiring additional bandwidth and reducing forwarding efficiency due to the need for extended headers and increased forwarding table searches.

Innovation Solution

A method where a head node sends IFIT configuration information via a BGP update packet to a tail node, allowing the tail node to generate a service flow identification rule based on this information, enabling bidirectional IFIT without needing to include configuration information in each service packet.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If bidirectional IFIT is implemented by adding an extended field to service packets, then reverse IFIT information can be carried, but the service packet size increases and forwarding efficiency decreases

Engineering Contradiction:
Improvereverse IFIT information transmissionVSAvoidforwarding efficiency
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The head node performs preliminary action by sending IFIT configuration information to the tail node before the service packets need to be forwarded. This configuration information is transmitted in advance through a separate channel (BGP update packet), so that when service packets arrive, the tail node already has the necessary information to generate appropriate service flow identification rules, eliminating the need to append configuration data to each service packet.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent introduces an intermediary mechanism using BGP update packets to transfer IFIT configuration information between head and tail nodes. This intermediary channel separates the configuration information transmission from the service packet forwarding process, allowing the service packets to maintain their original size while still enabling bidirectional IFIT functionality through the configuration rules established by the intermediary communication.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If IFIT configuration information is added to each service packet, then bidirectional IFIT can be supported, but the bandwidth required increases

Engineering Contradiction:
Improvebidirectional IFIT capabilityVSAvoidbandwidth consumption
Core Design Contradiction:
ReliabilityVSQuantity of substance

Solution Approach 1:

The head node sends IFIT configuration information to the tail node in advance through BGP update packets before service packets need to be processed. This preliminary configuration allows the tail node to pre-generate service flow identification rules, so that when service packets traverse the network, no additional bandwidth is consumed for carrying configuration information within the service packets themselves.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

BGP update packets serve as an intermediary mechanism that decouples the configuration information transmission from the service packet data transmission. This intermediary approach allows the necessary IFIT configuration to be exchanged between nodes without increasing the bandwidth consumption of the actual service traffic, as the configuration is established separately before data forwarding occurs.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Reliability

If extended fields are inserted into service packets for bidirectional IFIT, then reverse IFIT information can be carried, but the number of forwarding table searches increases

Engineering Contradiction:
Improvereverse IFIT information carryingVSAvoidforwarding table search operations
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The tail node performs preliminary action by generating service flow identification rules in advance based on configuration information received from the head node. These pre-generated rules are stored in the forwarding table before service packets arrive, allowing the tail node to directly match and process service packets without performing additional forwarding table searches or complex processing during the actual data forwarding operation.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The BGP update packet acts as an intermediary that carries configuration information to the tail node, enabling the tail node to pre-compute and store service flow identification rules in its forwarding table. This intermediary configuration mechanism allows the tail node to use simple, pre-established lookup rules during service packet forwarding, significantly reducing the complexity and number of forwarding table searches compared to processing extended fields in every service packet.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentEP4697670A1In-situ flow telemetry information configuration method and apparatus, and network device and storage medium
Publication Date: 2026.02.18 NEW H3C TECH CO LTD
  • EP4697670A1 patent drawingFigure 1~2
  • EP4697670A1 patent drawingFigure 3~6
  • EP4697670A1 patent drawingFigure 7~11

AI summary

The examples of the present disclosure provide an IFIT information configuration method, apparatus, a network device and a storage medium, which relates to the field of communication technology. The method is applied to a tail node, the method includes: receiving a first BGP update packet from a head node, and the first BGP update packet includes IFIT configuration information; receiving a first service packet from the head node through a first path, the first service packet includes a first IFIT option, and the first IFIT option includes first indication information; if a value of the first indication information is a first value, generating a service flow identification rule based on the configuration information, and the service flow identification rule is to identify a service flow requiring IFIT, and the service flow is transmitted through a second path, and the second path is a forwarding path from the tail node to the head node, and the first path and the second path pass through a same intermediate node. The efficiency of service packet forwarding can be improved.