Bandwidth Registration for MP2MP Services

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current technologies face challenges in efficiently managing bandwidth for multipoint-to-multipoint (MP2MP) services in provider networks, particularly in defining and enforcing Service Level Agreements (SLAs) due to ambiguity in bandwidth allocation and wastage of excess bandwidth.

Innovation Solution

The technique involves using registration protocols like GARP and MRP to advertise maximum bandwidth values for each port direction, ensuring that no port delivers more bandwidth than it can receive, and implementing a connectivity priority to manage bandwidth allocation and enforcement, thereby preventing wastage and ensuring SLA compliance.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Measurement precision

If maximum bandwidth values are advertised for each port direction in MP2MP services, then bandwidth allocation precision is improved, but device complexity increases due to registration protocol processing

Engineering Contradiction:
Improvebandwidth allocation precisionVSAvoiddevice complexity
Core Design Contradiction:
Measurement precisionVSDevice complexity

Solution Approach 1:

The patent segments bandwidth management into port-direction-specific registrations, where each port independently advertises its bandwidth capabilities. This allows precise tracking of bandwidth allocation per port while distributing the processing complexity across multiple port-level entities rather than requiring centralized complex processing.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent implements preliminary bandwidth registration and advertisement before actual data transmission begins. By pre-advertising maximum bandwidth values for each port direction using registration protocols, the system establishes bandwidth allocations in advance, avoiding the need for complex real-time negotiation during data flow.

Inventive Principle:
Principle #10Preliminary action

2Device complexity

If bandwidth is allocated without considering actual port reception capabilities, then device complexity is reduced, but bandwidth wastage increases due to excess transmission

Engineering Contradiction:
Improvedevice complexityVSAvoidbandwidth wastage
Core Design Contradiction:
Device complexityVSLoss of energy

Solution Approach 1:

The patent implements a feedback mechanism where each port advertises its maximum bandwidth reception capability through registration protocols, and this information is propagated throughout the network. This feedback loop ensures that bandwidth allocation decisions are based on actual port capabilities, preventing excessive bandwidth allocation and transmission wastage.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The patent dynamically adjusts bandwidth allocation parameters based on advertised port capabilities. By changing the bandwidth parameter from a fixed or estimated value to a dynamically advertised value reflecting actual port reception capability, the system optimizes bandwidth utilization and reduces wastage.

Inventive Principle:
Principle #35Parameter changes

3Reliability

If Service Level Agreements are strictly enforced with precise bandwidth limits, then reliability is improved, but ease of operation deteriorates due to complex configuration

Engineering Contradiction:
ImproveSLA complianceVSAvoidconfiguration simplicity
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

The patent enables self-service bandwidth management where network devices automatically advertise their capabilities and enforce SLAs without requiring manual configuration. The registration protocols allow devices to autonomously register their bandwidth parameters, and the system automatically enforces allocations, eliminating complex manual setup while maintaining reliable SLA compliance.

Inventive Principle:
Principle #25Self-service

4Ease of operation

If excess bandwidth is transmitted without policing, then ease of operation is improved, but loss of substance increases due to unnecessary bandwidth consumption

Engineering Contradiction:
Improveoperational simplicityVSAvoidbandwidth consumption
Core Design Contradiction:
Ease of operationVSLoss of substance

Solution Approach 1:

The patent applies preliminary bandwidth policing by rate limiters based on pre-advertised maximum bandwidth values. Before excess bandwidth can be transmitted and wasted, the system has already established rate limits at each port based on advertised capabilities, automatically preventing unnecessary bandwidth consumption without requiring complex operational intervention.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS7515535B2Technique for efficiently managing bandwidth for multipoint-to-multipoint services in a provider network
Publication Date: 2009.04.07 CISCO TECHNOLOGY INC
  • US7515535B2 patent drawing
  • US7515535B2 patent drawing
  • US7515535B2 patent drawing

AI summary

A technique efficiently manages bandwidth (BW) for multipoint-to-multipoint (MP2MP) services in a provider network of a computer network. According to the novel technique, each bridge having a user-network interface (UNI) port of an MP2MP service generates a registration for the service that carries maximum BW values for each port direction (e.g., for each {service, priority, color} triple), e.g., as defined by a Service Level Agreement (SLA). The registrations are advertised among neighboring bridges throughout the network toward other UNI ports of the MP2MP service. As each bridge receives registrations from each neighboring bridge (or from the UNI port), the bridge advertises registered BW values pertaining to a particular direction on a particular one of its ports that correspond to the sum of the BW values for that direction received on all of the other ports of the bridge, up to a maximum BW value (e.g., configured or physical) for the particular port. The actual BW required for allocation on an active port for each direction is the lower of either the registered value advertised from the port in a particular direction or the registered value received at the port in the opposite direction.