An OLT — Optical Line Terminal — is the central-office equipment at the head of a Passive Optical Network (PON). It lives in the carrier's server room or a campus central cabinet. On one side it faces the upstream core router or metro network; on the other it reaches dozens to over a hundred ONUs through optical splitters. Put simply, the OLT is the "main gate" of the PON: it pours upper-layer IP services over the OLT fiber to subscribers, then collects the subscribers' upstream traffic and sends it back to the core.
An OLT is the central-office end of a PON — it bridges the core network and every user behind a splitter.
Upstream it hands aggregated PON traffic to a BRAS or core router (usually 10GE); downstream it drives GPON/EPON/XGSPON ports that fan out through splitters to ONUs.
In practice the OLT does four jobs: authenticate ONUs, assign bandwidth (DBA), run remote OAM, and enforce QoS and multicast.
The difference between OLT and ONU comes down to location and layer. The OLT device sits in the equipment room or central cabinet — the "central office" end. The ONU sits at the user's side — in the corridor, the home gateway, or the enterprise comms closet.
The OLT manages every ONU under its PON ports: it pushes configuration to each ONU, authenticates it, and grants upstream timeslots. The ONU only serves its one or few users, gathering data from PCs, phones, IPTV, and cameras and feeding it into the fiber. The OLT is the manager; the ONU is the managed. This master-slave relationship has not changed from GPON to XGSPON. In real deployments, an OLT vendor (such as Rayin) follows exactly this "one-feed-many" central-office model — a single cabinet unit stands in for dozens of user-side ONUs.
On the uplink side, the OLT sends the traffic aggregated from the PON side back to the core. The interfaces are typically GE (gigabit) or 10GE (10-gigabit) electrical ports, or SFP / SFP+ optics, facing a BRAS or core router.
Size the bandwidth backwards. A GPON PON port runs 2.5G down / 1.25G up (per ITU-T G.984), shared by 128 ONUs. If you fill two downstream PON ports (as on Rayin's L102P, an 8 port GPON OLT), the uplink needs at least 10GE — otherwise downstream floods happily while upstream cannot get back, and users feel "fast download, stuck upload." XGSPON pushes upstream all the way to 10G, so its uplink must be 10-gigabit from the start.
Do not hang the uplink on a single link. Run link aggregation (LACP) or dual uplinks on the core link; if one port dies, the whole user segment goes dark.
Note: Bandwidth is sized from the user side inward. A 1:128 GPON split can easily exceed 1 Gbps of aggregate upstream, so a 1GE uplink becomes the bottleneck long before the PON ports do.
The downlink side is the OLT's real job. A PON port runs GPON / EPON / XGSPON; once the OLT fiber enters the ODN it splits one-to-many through splitters. Common split ratios are 1:64 and 1:128 — a 1:128 means one PON port's light reaches 128 ONUs.
Optical power budget is a hard constraint. GPON Class B+ budgets about 28 dB; a 1:128 split alone eats roughly 21 dB (about 3 dB per split stage, compounding logarithmically), leaving little margin for fiber and connectors. A 1:128 split is workable within 20 km on a clean link; past 20 km or with many inline flanges, the light never reaches the ONU and it will not register. So for long runs, do not force 1:128 — step back to 1:64 for stability.
Another trap: downstream is broadcast, upstream is time-division. GPON downstream is broadcast (every ONU receives it and filters by LLID); upstream is TDMA (ONUs transmit in the timeslots the OLT grants — they cannot grab the bus themselves, or frames collide). The OLT schedules these timeslots centrally.
Warning: An ONU that transmits out of its assigned slot collides and the OLT drops the frame. The whole upstream schedule is the OLT's job — that is why rogue or mis-ranged ONUs must be blocked at registration.
Pull the threads together and the OLT does four things in a PON:
Subscriber authentication and registration. It checks each ONU's LOID / SN and runs Ranging to lock the delay, turning away unauthorized terminals at the door. The protocol is OMCI / OAM.
Dynamic Bandwidth Allocation (DBA). Upstream bandwidth is granted by timeslot on demand — whoever has traffic gets it, idle ones are reclaimed — so ONUs do not fight for upstream and port utilization stays high.
OAM operations. Remote OLT configuration — VLAN, rate limits, optical-power alarms, and batch firmware upgrades — no need to pull fiber on site, which cuts operating cost.
QoS and multicast. It sets priority and rate limits per service; IPTV rides multicast as a single copy so downstream bandwidth is not duplicated, protecting voice and video experience.
Tip: DBA is what makes a shared 1.25G upstream feel fair. Without it, a few chatty ONUs would starve the rest — the OLT rebalances the slice every few milliseconds.
Do not get distracted by flashy specs — pin these down first: PON port count (how many ONUs it can drive), PON type (is GPON enough or do you need XGSPON), uplink bandwidth (start at 10-gigabit), split-ratio support (1:64 or 1:128), and operations capability (can it do remote OAM and DBA).
| Dimension | OLT (central office) | ONU (user side) |
|---|---|---|
| Placement | Equipment room / central cabinet | Corridor / home / enterprise closet |
| Role | Manager of the whole PON | Managed, serves a single user |
| Uplink to | BRAS / core router | OLT (via splitter) |
| Downlink to | Splitter → many ONUs | PC / phone / IPTV / camera |
| Key ability | Auth, DBA, OAM, QoS | Optical-electrical conversion, user access |
| Count relation | One drives dozens to hundreds of ONUs | Massive, distributed to users |
| Standard | Downstream | Upstream | Spec | Common split |
|---|---|---|---|---|
| GPON | 2.5G | 1.25G | ITU-T G.984 | 1:64 / 1:128 |
| XGSPON | 10G | 10G | ITU-T G.987 | 1:64 / 1:128 |
| EPON | 1.25G | 1.25G | IEEE 802.3ah | 1:32 / 1:64 |
Note that EPON is symmetric 1.25G up and down, while GPON has a stronger downstream but only 1.25G upstream; to fill the upstream too you need XGSPON. Match the uplink count as well: if you fill 8 GPON ports downstream (8×2.5G), you need at least two 10GE uplinks to avoid a jam.
Note: This is a different layer from the switch uplink question — an OLT network centers on optical splitters and TDMA, while a switch moves frames inside one LAN. Both, though, live or die by how you size the uplink.
What is the real difference between OLT and ONU?
Location and role. The OLT is the central-office manager that controls every ONU under its PON ports; the ONU is the user-side device that serves one subscriber and feeds data into the fiber. The master-slave model holds from GPON through XGSPON.
How many ONUs can one GPON port drive?
Up to 128 on a 1:128 split, sharing 2.5G down / 1.25G up. Keep it within 20 km on a clean link — beyond that, or with many flanges, the optical budget runs out and ONUs will not register. Step down to 1:64 for longer or lossier runs.
Why does the OLT uplink need to be 10-gigabit?
Because bandwidth is sized from the users inward. 128 ONUs sharing a PON port can easily exceed 1 Gbps of aggregate upstream, and filling several PON ports multiplies that. A 1GE uplink becomes the bottleneck long before the PON ports do, so 10GE is the sensible floor.
What four jobs does the OLT actually do?
Authenticate and register ONUs (OMCI/OAM), allocate upstream bandwidth dynamically (DBA), run remote OAM (VLAN, alarms, batch upgrade), and enforce QoS and multicast so voice and video stay smooth.
An OLT is the central-office brain of a PON — the manager that sits between the core network and every subscriber behind a splitter. It authenticates ONUs, balances upstream with DBA, runs remote OAM, and protects voice and video with QoS and multicast. Size it from the user side inward: count the PON ports, pick the PON type, and never let the uplink be the weak link. When you spec an OLT network, the four jobs above — not the sticker specs — are what decide whether your subscribers get fast download and a responsive upload. For a compact central-office unit, Rayin's OLT lineup shows the "one-feed-many" model in practice.
Customer Manager at Shenzhen Rayin Technology Co., Ltd.
