On a single passive optical network, data, voice, and video all share the same fiber — and without isolation, a broadcast storm in one service takes the others down with it. The fix is two layers: VLANs separate the services, and QoS puts the critical ones first, with both meeting at the OLT uplink to actually take effect. In a GPON network the upstream is a TDMA-shared 1.25 Gbps, so a single ONU flooding the link can starve a neighbor's voice timeslot unless the OLT enforces priority. This guide walks through how to carve VLANs per service, map DSCP and IEEE 802.1p priorities, and set DBA so voice stays clean through the evening peak.
Separate every service with its own VLAN; keep voice on a dedicated VLAN so a camera loop or ARP storm never cuts the phones.
VLAN separates, QoS decides who goes first — you need both, and they must converge on the OLT uplink.
Reserve fixed DBA bandwidth for voice; full-dynamic DBA lets a saturated monitor ONU steal the voice timeslot.
The simplest plan is "one VLAN per service": data on one VLAN, voice on another, video surveillance on a third. The ONU user-side port is set to Access and tags frames as they arrive; the OLT uplink is a Trunk that carries all three VLAN tags upstream.
When users multiply, you can go finer — "one VLAN per user per service" (for example voice VLAN 100, data VLAN 200 plus room number). The fine cut shrinks each broadcast domain so one subscriber's problem stays local; the cost is more VLAN bookkeeping, so first confirm the OLT's VLAN spec (commonly up to 4K).
Warning: Never mix voice and video in the same VLAN. If a surveillance camera gets dragged down by an ARP storm or a loop, the phones on that VLAN go down with it. Isolation is the cheapest fault-containment you have.
VLAN solves "separated," not "who goes first." Beyond PTP, ordinary multi-service priority rides on IEEE 802.1p and DSCP:
| Service | VLAN | IEEE 802.1p | DSCP | Queue policy |
|---|---|---|---|---|
| Voice (VoIP) | Dedicated VLAN | 6 | 46 (EF) | Strict priority |
| Video (monitor / IPTV) | Dedicated VLAN | 4–5 | 26 / 34 (AF) | Weighted round-robin |
| Data (internet) | Dedicated VLAN | 0 | 0 (BE) | Best effort |
| Management / protocol | Dedicated VLAN | 3 | 24 (CS3) | Reserved bandwidth |
Voice gets the highest priority — DSCP 46 (EF), IEEE 802.1p 6, into a strict-priority queue with the least jitter. Video rides weighted round-robin at DSCP 26 or 34 (AF). Data is best-effort at DSCP 0, and management gets a small reserved slice at DSCP 24 (CS3).
Tip: On the GPON OLT uplink, trust DSCP, map IEEE 802.1p ↔ DSCP, and enable queue scheduling. A GPON upstream is TDMA — all ONUs time-share 1.25 Gbps — so without priority mapping, one ONU's burst upload eats a neighbor's voice timeslot.
GPON upstream relies on DBA (Dynamic Bandwidth Allocation) to hand out timeslots to each ONU. If DBA is fully dynamic — first come, first served — a saturated monitor ONU at peak eats the voice ONU's slot. The right move is to reserve fixed guaranteed bandwidth for voice in the DBA (Type fixed bandwidth) and let the rest run best-effort dynamic. Voice timeslots stay stable; video and data use what's left.
Note: In one 500-home community we separated voice, monitor, and internet (per-building) VLANs, ran a 2×10G GPON OLT uplink with voice at DSCP 46 strict and monitor on AF weighted round-robin. After adding fixed DBA voice bandwidth, the evening peak showed zero voice glitches and no dropped monitor frames — before that, voice occasionally broke up at peak.
Plan VLANs — one VLAN per service; go per-user-per-service when scale demands.
Tag at the edge — ONU user side Access, OLT uplink Trunk passthrough.
Set priority — voice highest, video mid-high, data default, management separate.
On the OLT uplink — trust DSCP, map IEEE 802.1p ↔ DSCP, enable queue scheduling.
DBA — reserve fixed bandwidth for voice, dynamic for the rest.
Check Trunk ports across devices — confirm priority tags ride through, not stripped.
Do VLAN and QoS have to be done together? VLAN separates services; QoS decides who goes first. They do not conflict but must pair. VLAN alone leaves voice crowded out by video at peak; QoS alone leaves a broadcast storm taking everything down. They only become complete where they meet at the OLT uplink.
Why must voice have its own VLAN and highest priority? Voice is the most sensitive to latency and jitter — drop a few packets and it breaks up. A dedicated VLAN contains faults, DSCP 46 strict priority protects the timeslot, and fixed DBA bandwidth locks it in. Three layers of insurance.
How does GPON's shared upstream affect multi-service? The upstream is TDMA — all ONUs time-share 1.25 Gbps. One ONU uploading at full speed can crowd out a neighbor's voice timeslot. The OLT's queue scheduling plus fixed DBA bandwidth lock the voice timeslot in place.
Can't DBA just be fully dynamic? No. Fully dynamic means first come, first served, so a saturated monitor ONU steals voice's slot at peak. You must reserve fixed guaranteed bandwidth for voice and leave the rest dynamic. That fixed reservation is the key step in protecting voice on PON.
What happens if the OLT uplink doesn't map priority? The VLAN isolation is wasted — the downstream switch schedules on the wrong priority and video crowds out voice. The OLT uplink must trust DSCP and map IEEE 802.1p ↔ DSCP, or the whole scheme falls apart.
Multi-service PON comes down to two lines: VLANs separate data, voice, and video, and QoS on the OLT uplink puts voice first, video mid-high, data default — with DBA reserving a fixed voice timeslot. Miss any one link and the phones buckle first at peak.
About the author: Sara — Sara is a Customer Manager at Rayin with over 10 years of experience in the communications field. She specializes in technical product selection and writes guides and tutorials that help procurement engineers and system integrators solve problems more efficiently. In her free time, she enjoys badminton and swimming.
About Rayin: Shenzhen Rayin Technology Co., Ltd. — Company Profile
