OpenFlow Buffer Control for Flow-Specific Packet Caching

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The existing OpenFlow protocol lacks a dedicated buffer processing mechanism, which is necessary for efficient data packet forwarding in mobile networks, particularly in scenarios involving idle mode, network handovers, and resource limitations.

Innovation Solution

Implementing a flow granularity-based buffer processing mechanism in the OpenFlow protocol, where network elements receive buffer information from controllers to manage data packet storage and forwarding through buffer creation, modification, or deletion based on specific triggers and instructions.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If the existing OpenFlow protocol is used without buffer processing mechanism, then the protocol structure remains simple, but the data buffering capability is insufficient for mobile network scenarios

Engineering Contradiction:
Improvedata buffering capabilityVSAvoidprotocol structure
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent applies preliminary action by pre-configuring buffer processing mechanisms in the OpenFlow protocol before data transmission occurs. The controller pre-establishes buffer policies, flow tables, and resource allocation rules, so that when data packets arrive, the network elements can immediately execute buffering operations without complex runtime decision-making, thus improving reliability while maintaining protocol simplicity

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent introduces a controller as an intermediary between the network elements and the buffer management system. The controller mediates buffer resource allocation, flow table configuration, and policy enforcement, allowing network elements to execute buffering operations through standardized OpenFlow commands without requiring complex local decision logic, thereby enhancing buffering capability while keeping device complexity manageable

Inventive Principle:
Principle #24Intermediary (Mediator)

2Adaptability or versatility

If buffer resources are allocated without flow granularity, then resource management is simpler, but data flow-specific buffering requirements cannot be met

Engineering Contradiction:
Improveflow-specific bufferingVSAvoidbuffer management complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent applies segmentation by dividing buffer resources into flow-specific segments through flow tables. Each flow entry can have dedicated buffer resources allocated to it, allowing different buffering policies for different data flows. This enables fine-grained control over buffer allocation while maintaining systematic management through the flow table structure, thus achieving flow-specific adaptability without excessive complexity

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent uses parameter changes by dynamically adjusting buffer allocation parameters (such as buffer size, priority, and duration) based on flow characteristics and network conditions. The controller can modify flow table entries to change buffer parameters without reconfiguring the entire buffer management system, enabling flexible adaptation to different flow requirements while keeping the management mechanism relatively simple

Inventive Principle:
Principle #35Parameter changes

3Reliability

If dedicated buffer processing mechanism is added to OpenFlow protocol, then data buffering requirement is met, but the protocol complexity increases

Engineering Contradiction:
Improvebuffer processing capabilityVSAvoidprotocol structure
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent applies universality by designing a buffer processing mechanism that can handle multiple buffering scenarios (packet capture, packet modification, packet forwarding, packet dropping) through a unified set of OpenFlow commands and flow table structures. This multi-functional approach allows the protocol to meet diverse buffering requirements without requiring separate specialized mechanisms for each scenario, thus improving reliability while controlling protocol complexity

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

Solution Approach 2:

The patent incorporates feedback mechanisms where network elements report buffer status and flow information to the controller, which then adjusts buffer allocation and flow table configurations accordingly. This closed-loop control allows the system to adapt to changing network conditions and buffering requirements dynamically, improving reliability while maintaining protocol simplicity through automated feedback-driven adjustments

Inventive Principle:
Principle #23Feedback

Data Source

PatentEP3627784B1Cache control method, network element and controller
Publication Date: 2026.01.07 HUAWEI TECH CO LTD
  • EP3627784B1 patent drawingFigure 1~2
  • EP3627784B1 patent drawingFigure 3
  • EP3627784B1 patent drawingFigure 4A

AI summary

Embodiments of this application provide a buffer control method, a network element, and a controller. The method includes: receiving, by a network element, a flow table message from a controller, where the flow table message includes buffer information of a data packet matching a flow table; and further, processing, by the network element, a buffer of the data packet based on the buffer information, and sending a flow table response message to the controller. In the method in the embodiments of this application, the network element processes the buffer of the data packet based on the buffer information, so that the network element can save, based on a corresponding saving manner, at least one data packet matching the flow table to the buffer corresponding to the flow table. It can be learned that, a data flow granularity-based buffer processing manner can be supported in an OpenFlow protocol, and a data buffering requirement of a mobile network can be met.