DBA (Dynamic Bandwidth Allocation)

DBA stands for Dynamic Bandwidth Allocation. It's the upstream scheduling mechanism in GPON and XGS-PON networks, implemented in the TC (Transmission Convergence) layer at the OLT, by which the OLT continuously assigns upstream time slots to ONTs based on real-time traffic demand. DBA is what allows a single PON port's shared upstream capacity (1.244 Gbps for GPON, 10 Gbps for XGS-PON) to efficiently serve up to 32 or 64 ONTs without manual per-subscriber bandwidth engineering.

DBA operates because PON upstream is time-division multiplexed: each ONT can transmit only during time slots assigned to it by the OLT, with all ONTs sharing the same upstream wavelength back to the OLT. Without DBA, time slots would have to be statically allocated, wasting upstream capacity when ONTs are idle. With DBA, the OLT monitors each ONT's transmission buffer state and reallocates upstream time slots dynamically to ONTs with traffic to send.

ITU-T G.984.3 defines two DBA modes for GPON, both supported by ITU-T G.9807.1 for XGS-PON:

- **Status Reporting DBA (SR-DBA, Type 2 and Type 3 T-CONTs)**: ONTs explicitly report their upstream buffer occupancy to the OLT via dedicated reporting messages (DBRu fields in upstream PLOAM). The OLT uses these reports to allocate the next round of time slots. Type 2 T-CONTs are non-assured (best-effort) traffic; Type 3 T-CONTs combine assured (committed) and non-assured bandwidth. - **Traffic Monitoring DBA (NSR-DBA, Type 4 T-CONTs)**: The OLT infers each ONT's upstream demand by monitoring idle frames in the ONT's transmissions, without requiring explicit buffer reports. Lower overhead than SR-DBA but less precise; used for best-effort traffic only.

T-CONT (Transmission Container) classes define the bandwidth service profile per ONT logical port:

- **T-CONT Type 1**: Fixed bandwidth. The ONT is granted a constant assigned bit rate (e.g., 100 Mbps reserved), independent of demand. Used for guaranteed-bandwidth services like business VoIP. - **T-CONT Type 2**: Assured bandwidth. Guaranteed allocation up to a committed rate, with the OLT confirming the grant via DBA. Used for video and managed services. - **T-CONT Type 3**: Assured + non-assured. Committed bandwidth plus burst capacity into the unassured pool. Used for residential service tiers with peak/burst expectations. - **T-CONT Type 4**: Best-effort. No committed rate; granted bandwidth only when capacity is available. Used for low-priority background traffic. - **T-CONT Type 5**: Combined. Mixes fixed, assured, and non-assured allocations in a single container. Used for sophisticated multi-service ONTs.

DBA polling cycles run at approximately 0.125–1 ms intervals on modern OLTs, with end-to-end upstream latency (ONT buffer-to-OLT) of 1–5 ms for residential service. Sub-millisecond latency is achievable with optimized DBA configurations but is rarely required for residential traffic.

DBA vs static allocation: Static allocation pre-assigns a fixed share of upstream capacity to each ONT regardless of demand, wasting capacity when ONTs are idle. DBA dynamically reassigns idle ONTs' time slots to active ONTs, achieving 70–90% upstream utilization in real-world residential GPON networks compared to 20–40% utilization for naive static allocation. DBA is the architectural innovation that makes shared-PON economics work — without it, GPON's per-subscriber bandwidth would be 1/32 of upstream capacity (~39 Mbps for GPON) instead of the multi-hundred-Mbps burst rates subscribers experience.

DBA configuration directly affects subscriber-perceived performance and SLA compliance. Misconfigured T-CONT classes — e.g., assigning a business VoIP service to Type 4 best-effort instead of Type 1 fixed — produce intermittent service degradation that is difficult to diagnose without OLT log analysis. MapItRight tracks T-CONT class assignment per subscriber service profile, automatically validating that committed-rate services are mapped to assured T-CONT classes and flagging misalignment between billing-system service tiers and ONT-provisioned T-CONT configurations.