Multi-tier Network Flow Management Architecture

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Large-scale data centers and provider networks face complexity in managing network packet transformations due to diverse customer needs, requiring flexible and scalable solutions for packet processing, address manipulation, and traffic management across numerous virtual and physical machines.

Innovation Solution

A scalable, fault-tolerant network flow management service is implemented, utilizing a distributed system with multiple tiers of nodes for packet transformation, state tracking, and rewriting decisions, which classifies packets, applies transformation directives, and manages metadata to efficiently handle various packet processing requirements, including stateful anycast, multicast, and load balancing.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If ad-hoc solutions are used for packet transformation requirements, then flexibility in handling diverse customer needs is improved, but scalability to large provider networks is worsened

Engineering Contradiction:
Improveflexibility in packet transformationVSAvoidscalability to large networks
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent segments the packet transformation function into distinct network elements: service function chains (SFCs) that define transformation sequences, and network virtualization layer (NVL) components that execute them. This segmentation allows flexible configuration of transformation rules through SFC descriptors while maintaining scalability by distributing execution across multiple NVL nodes, preventing any single point from becoming a bottleneck in large provider networks.

Inventive Principle:
Principle #1Segmentation

2Adaptability or versatility

If multiple network transformations are implemented, then customer-specific packet processing requirements are improved, but network management complexity is worsened

Engineering Contradiction:
Improvepacket processing requirementsVSAvoidnetwork management
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent implements a universal service function chain framework that can handle multiple types of network transformations (address manipulation, packet routing, load balancing, etc.) through a single standardized mechanism. The SFC descriptor language provides a unified way to define diverse transformation requirements, while the NVL executes different transformation types using common infrastructure components, reducing network management complexity despite supporting multiple customer-specific processing requirements.

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

3Reliability

If stateful packet processing is implemented, then application performance is improved, but processing overhead is worsened

Engineering Contradiction:
Improveapplication performanceVSAvoidprocessing overhead
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent applies preliminary action by pre-configuring service function chains with their transformation rules and state management parameters before packets arrive. The NVL nodes preload SFC descriptors and establish processing pipelines in advance, allowing packets to flow through pre-established stateful processing paths. This reduces per-packet processing overhead while maintaining the benefits of stateful application performance monitoring and consistent packet handling.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS9998955B1Multi-tier stateful network flow management architecture
Publication Date: 2018.06.12 AMAZON TECH INC
  • US9998955B1 patent drawing
  • US9998955B1 patent drawing
  • US9998955B1 patent drawing

AI summary

A packet transformation node of a multi-tier flow management system receives a packet of a particular network flow. The packet transformation node produces a modified version of the packet with changes to one or more header elements based on a rewrite entry generated at a rewriting decisions tier of the system, and transmits the modified version to a destination. A rewriting decisions node of the system generates rewrite entries corresponding to various packet processing requirements, based at least partly on state information regarding various flows for which rewriting entries have already been generated.