CodingBox Documentation

Fibre network topologies and architectures

Two transceivers and a fibre make a link; a network is what you do with hundreds of them. The way links are arranged — point-to-point, ring, tree, mesh, star — decides how many fibres a route needs, what happens when a cable is cut, which optics each end carries and how the plant is documented. This page walks through the topologies used in data centres, campuses, access networks and transport, the structured-cabling hierarchy that standards prescribe, FTTx architectures, fibre-count planning and protection schemes — with the optics implied by each.

Fibre network topologies: point-to-point, protected ring, PON tree, WDM on one pair

Basic topologies

TopologyStructureFibres per linkProtectionTypical opticsWhere
Point-to-point, duplexA ↔ B on two fibres2none (or a second diverse pair)SR/LR/ER, DAC/AOCeverywhere
Point-to-point, single-fibre BiDione fibre, two wavelengths1noneBiDi pairs (1310/1490, 1270/1330)fibre-scarce routes, FTTx
Point-to-point WDMN channels on one pair via mux/demux2 for N servicesper systemCWDM/DWDM modules (CWDM, DWDM)metro, campus interconnect
Star / hub-and-spokeevery site to a central node2 per spokedual-homing to two hubsLR/ER by distancecampus, enterprise WAN
Ringnodes in a loop, traffic both ways2 (single ring) or 4 (dual)inherent: second pathLR/ER, DWDM with OADMsmetro, carrier access, utilities
Tree (PON)one OLT fibre split 1:32–1:128 to ONUs1 feeder, 1 per subscriberType B/C protection optionalPON optics classes (How PON works)FTTH
Meshmany-to-manymanyreroutingROADM/coherentcore transport
Leaf–spine (folded Clos)every leaf to every spine2 per linkmultipath by designSR4/DR4/AOC (Roles & topologies)data centre
Bus / linear add-dropnodes along one route2noneOADMpipelines, railways

Structured cabling hierarchy (TIA-568 / ISO 11801)

ElementRoleFibre choiceNotes
Entrance facilitywhere carrier cables enter; transition outdoor → indooras carrieroutdoor cable may run ≤ 15 m indoors unless rated (NEC 770)
Equipment room / main cross-connect (MC)core switches, ODFOS2all backbones terminate here
Backbone (vertical / campus)MC ↔ intermediate (IC) ↔ horizontal cross-connects (HC)OS2 (OM4 for short intra-building)≤ 2 000 m campus SMF; 12–48 fibres per closet typical
Telecommunications room (TR/HC)floor distributionaccess switches
Horizontal cablingTR → work area outlet, ≤ 90 mcopper mostly; fibre in centralized cabling (≤ 300 m OM3/OM4)fibre-to-the-desk rare but exists
Data centre (TIA-942)MDA → IDA → HDA → EDA (ZDA optional)OM4/OS2 trunks with MPOToR, EoR, MoR patterns below

Data-centre cabling patterns

PatternCablingOptics
Top-of-rack (ToR)servers to a switch in the same rack over DAC; switch uplinks to spines over structured fibreDAC ≤ 3 m; SR4/DR4/AOC uplinks
End-of-row / middle-of-row (EoR/MoR)servers cabled across the row to a switch at the end/middleAOC or SR optics 10–30 m; more fibre, fewer switches
Structured MPO trunks + cassettes12/24-fibre trunks between MDA and HDA/EDA, LC breakout in cassettesany duplex optic; polarity method A/B/C (Breakout & MPO)
Direct point-to-point MPOtrunk straight between QSFP ports (SR4/DR4)parallel optics; fewer connectors
Rail-optimised (AI)each GPU NIC to a different leafAOC/DR4 mostly (Cabling an AI cluster)

FTTx architectures

ArchitectureFibre reachesLast segmentActive equipmentOptics
FTTH — PONthe home1 fibre from splitterOLT + ONUGPON/XGS-PON classes; splitters 1:32–1:64
FTTH — P2P Ethernet (AON)the homededicated fibre per homeEthernet switch + CPE1G/10G BiDi single-fibre
FTTBthe buildingcopper (Ethernet/VDSL/G.fast) insidebuilding switch/DSLAM1G/10G LR uplink
FTTC / FTTNcabinet / nodeVDSL over copperstreet DSLAM1G/10G LR, CWDM
FTTAthe antennafibre to the RRURRU/AAU10/25G fronthaul optics (Fronthaul)
FTTx with WDM-PON / TWDMthe home1 fibre, wavelength per user/groupNG-PON2tunable ONU optics

Split architecture in PON: centralized (one 1:64 splitter at the cabinet — flexible, one splice point) vs cascaded/distributed (1:4 then 1:16 along the street — less feeder fibre, more closures, ~0.5 dB extra) (ODN classes).

Fibre-count planning

RuleReasoning
2 fibres per duplex service, 1 per BiDi/PON subscriberbaseline
Add 50–100 % spare on backbone routescivil works cost dwarfs fibre cost; pulling later costs more
Never fewer than 12 fibres in any outdoor cable; 24–48 between buildings; 96–288 on metro trunks; 864+ on ducts feeding data centresgranularity of splicing and ribbon counts
Plan WDM instead of fibres where duct space is the constraint8–96 services on one pair
Separate fibres (or cables) for protection pathsa second pair in the same cable does not survive a dig-up
Reserve fibres for monitoring (RFTS) and future PON splitters
Dark fibre lease vs wavelength/Ethernet servicedark fibre: you choose optics, you manage the plant; managed wavelength: provider's optics rules

Protection and diversity

SchemeHowSwitch timeFibre cost
Unprotectedone path
1+1traffic sent on two diverse paths, receiver picks< 50 ms
1:1 / 1:Nstandby path activated on failure50 ms–seconds2× or shared
Ring (ERPS G.8032, MPLS-TP, OTN, SNCP)reroute the other way around the ring< 50 msring fibres
Mesh restorationcontrol plane finds a new pathsecondsshared spare capacity
PON Type B / Credundant OLT port / trunk / full duplicationseconds+1 feeder fibre
Dual-homing (LAG/MLAG/ECMP to two nodes)L2/L3 multipathsub-second2× access links (Forwarding basics)

Diversity means physically separate routes: different ducts, different building entries, different street sides. Two cables in one trench share the excavator.

Latency

MediumDelayNote
Standard fibre≈ 4.9 µs/km (n ≈ 1.47)100 km ≈ 0.5 ms one way
Hollow-core fibre≈ 3.3 µs/kmtrading, HPC (Fibre types)
Copper / microwave / free space≈ 3.3 µs/kmmicrowave beats fibre on straight paths
Add per hopswitches 1–10 µs, routers 10–100 µs, FEC/DSP in 400G+ optics 100–300 ns, coherent DSP µsequipment, not glass

Documentation of a topology

Every fibre network needs: a route map (GIS), cable and fibre numbering, splice diagrams per closure, ODF port maps, cross-connect records, test results per fibre and a change log — kept current (Maintenance & restoration, Installation & routes).

In CodingBox

Topology decides the optics list: BiDi pairs for single-fibre spokes, PON classes for trees, CWDM/DWDM channels for shared pairs, parallel SR4/DR4 for MPO trunks. CodingBox verifies each delivered module against that list — wavelength, channel, PMD, power class — before it goes to the site (Check transceiver, Code database).

Keeping the topology knowable — identifier schemes, labels, splice schedules, GIS and records: Documentation & labelling; the boxes at the nodes of these topologies — transponders, ROADMs, OLTs, protection switches, media converters: Transport & access equipment.