Distributed Token Generator for Network Bandwidth Coordination

Solution Overview

Problem

Existing systems for managing bandwidth allocation in computer device clusters face challenges such as high data movement on internal networks, single points of failure, and data inconsistency due to centralized data transfer and packet throttling approaches.

Innovation Solution

A distributed queue system with a token generator module, where each host device is responsible for sending its own data, using tokens to manage bandwidth allocation dynamically and adapt to changing conditions, avoiding a single point of failure and ensuring fair access to bandwidth.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Device complexity

If a centralized master device is used to manage bandwidth allocation, then bandwidth policy enforcement is simplified, but internal network data movement volume increases and single point of failure risk increases

Engineering Contradiction:

Improvebandwidth policy enforcement complexityVSAvoidinternal network data movement volume

Core Design Contradiction:

Device complexityVSLoss of energy

Solution Approach 1:

The system divides the centralized bandwidth management function into distributed token generator modules located at each host device. Each host device independently generates and manages its own bandwidth tokens locally, eliminating the need for centralized master device coordination and reducing internal network data movement to only essential synchronization signals.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

Each host device is equipped with its own token generator module that autonomously manages bandwidth allocation for that device. The system enables self-service bandwidth management where each host device independently generates, stores, and consumes bandwidth tokens without requiring centralized control, thereby reducing dependency on a single master device.

Inventive Principle:

Principle #25Self-service

2Device complexity

If a centralized master device is used to manage bandwidth allocation, then bandwidth policy enforcement is simplified, but system reliability decreases due to single point of failure

Engineering Contradiction:

Improvebandwidth policy enforcement complexityVSAvoidsystem reliability

Core Design Contradiction:

Device complexityVSReliability

Solution Approach 1:

The system divides the centralized bandwidth management function into distributed token generator modules located at each host device. Each host device independently generates and manages its own bandwidth tokens locally, eliminating the need for centralized master device coordination and reducing internal network data movement to only essential synchronization signals.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

Each host device is equipped with its own token generator module that autonomously manages bandwidth allocation for that device. The system enables self-service bandwidth management where each host device independently generates, stores, and consumes bandwidth tokens without requiring centralized control, thereby reducing dependency on a single master device.

Inventive Principle:

Principle #25Self-service

3Productivity

If packet throttling is applied at router level, then bandwidth enforcement is achieved, but data consistency is compromised due to packet splitting

Engineering Contradiction:

Improvebandwidth enforcement efficiencyVSAvoiddata consistency

Core Design Contradiction:

ProductivityVSLoss of information

Solution Approach 1:

The system performs preliminary action by generating and distributing bandwidth tokens before data transmission occurs. Each host device receives tokens in advance that authorize specific data transfers, ensuring that bandwidth limits are respected before packets are sent. This prevents packet-level throttling issues and ensures data consistency is maintained throughout the transmission process.

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The patent introduces bandwidth tokens as an intermediary mechanism between bandwidth policy enforcement and actual data transmission. Instead of directly throttling packets at the router level, the system uses tokens as an intermediate authorization mechanism that host devices present when requesting bandwidth, thereby avoiding packet splitting and data inconsistency problems.

Inventive Principle:

Principle #24Intermediary (Mediator)

Data Source

PatentUS10587526B2Federated scheme for coordinating throttled network data transfer in a multi-host scenario

Publication Date: 2020.03.10 WALMART APOLLO LLC

AI summary

Embodiments relate to systems and methods that facilitate coordination amongst host devices that share network resources in order to use available bandwidth effectively. Embodiments can ensure the host devices themselves take responsibility for sending their data via shared network bandwidth, keeping access to bandwidth fair to all the host devices. Embodiments also include adapting to a continuously changing network bandwidth allocation policy for the shared network resource. In one embodiment, this includes using tokens (e.g., small chunk messages) to represent a grant to a host device to send a specified number of bytes over the network. Using a token generator module and a distributed queue, embodiments provide a unique and adaptive way to manage data transmissions among host devices within available resources.