Hierarchical DBA for PON SLA Compliance

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In converged optical networks, residential and business traffic sharing the same communication medium often leads to congestion, causing violations of service level agreements (SLAs) due to the inability to effectively manage and prioritize bandwidth allocation between different traffic classes.

Innovation Solution

Implementing a hierarchical dynamic bandwidth allocation (DBA) system that groups residential and business traffic separately, allowing independent scheduling within each group and prioritizing business services during congestion to ensure compliance with SLAs, while enabling oversubscription of residential services.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Device complexity

If residential and business traffic share the same communication medium without separate scheduling, then network simplicity is maintained, but SLA performance for business services deteriorates during congestion

Engineering Contradiction:
Improvenetwork scheduling complexityVSAvoidSLA performance compliance
Core Design Contradiction:
Device complexityVSReliability

Solution Approach 1:

The patent segments the shared communication medium into separate scheduling instances for residential and business traffic. The DBA server creates distinct scheduling cycles where business traffic receives dedicated bandwidth allocation and priority treatment, while residential traffic shares remaining capacity. This segmentation allows SLA-compliant performance for business services without requiring complete network isolation.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system implements dynamic bandwidth allocation where the DBA server continuously adjusts bandwidth parameters based on real-time traffic conditions and SLA requirements. During congestion events, the system dynamically reallocates bandwidth to prioritize business traffic, ensuring SLA compliance while maintaining overall network efficiency through adaptive scheduling.

Inventive Principle:
Principle #15Dynamics

2Reliability

If business traffic is prioritized over residential traffic during congestion, then SLA performance for business services is maintained, but residential service quality deteriorates

Engineering Contradiction:
Improvebusiness service SLA complianceVSAvoidresidential service availability
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent applies local quality by providing differentiated service characteristics to different traffic types within the same network infrastructure. Business traffic receives localized priority treatment with guaranteed bandwidth and low latency, while residential traffic receives best-effort service. This localized differentiation ensures SLA compliance for business without completely blocking residential access.

Inventive Principle:
Principle #3Local quality

Solution Approach 2:

The system implements partial prioritization where business traffic receives enhanced scheduling attention and bandwidth allocation during congestion events, while residential traffic retains partial access to remaining network capacity. This partial action approach ensures critical business SLA requirements are met while maintaining some level of residential service availability.

Inventive Principle:
Principle #16Partial or excessive action

3Reliability

If separate scheduling for residential and business traffic is implemented, then SLA performance is ensured, but scheduling complexity increases

Engineering Contradiction:
Improveservice level agreement complianceVSAvoidbandwidth allocation system complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent introduces a DBA (Dynamic Bandwidth Allocation) server as an intermediary component that manages the complexity of separate scheduling for residential and business traffic. This centralized intermediary handles the scheduling computations, bandwidth calculations, and coordination between different traffic types, reducing the complexity burden on individual network elements while ensuring SLA compliance.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The DBA server implements a universal scheduling framework that handles both residential and business traffic through a single integrated system. This multi-functional approach allows the same scheduling infrastructure to serve different service classes with different SLA requirements, reducing overall system complexity compared to separate independent scheduling systems.

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

4Productivity

If bandwidth is allocated to accommodate peak residential traffic demand, then residential service quality is maintained, but business service SLA performance deteriorates during peak periods

Engineering Contradiction:
Improveresidential service capacityVSAvoidbusiness service SLA compliance
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The patent implements preliminary action by pre-allocating guaranteed bandwidth reserves for business traffic based on SLA requirements before congestion occurs. The DBA server calculates and reserves minimum bandwidth levels for business services, ensuring that during peak residential demand periods, business SLA requirements are already secured and cannot be violated by transient residential traffic spikes.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS9083464B2Systems and methods for scheduling business and residential services in optical networks
Publication Date: 2015.07.14 ADTRAN INC
  • US9083464B2 patent drawing
  • US9083464B2 patent drawing
  • US9083464B2 patent drawing

AI summary

A passive optical network (PON) has an optical line termination (OLT) that terminates an optical fiber servicing a plurality of optical network units (ONUs). Each ONU has one or more traffic containers (TCONTs) addressable by the OLT. The PON dynamic bandwidth allocation (DBA) implements a scheduling hierarchy, including several scheduling layers, such that disjoint sets of TCONTs can be grouped together, then disjoint sets of groups can be grouped, and so on. In such hierarchy, the residential traffic can be grouped separately from the business traffic. Further, within either the residential or business group, traffic may be grouped to define scheduling layers (“sub-groups”) within the residential or business group. Scheduling in one group or sub-group is performed independently of the scheduling in other groups or sub-groups, subject to the available bandwidth for each group. The scheduling may be controlled to allow the residential services to be oversubscribed while still ensuring compliance of service level performance metrics for the business services.