Skip to main content
BSS/OSS Academy
🌐
Section 9.8

Fixed Access & Broadband

Last updated 12 Oct 2026

01

At a glance

Fixed access reaches more customer endpoints than any other domain, each with a physical line and a CPE. Every connection involves at least three managed elements plus AAA and IPAM, configured in the right order. The access technology decides which elements and controllers are involved, and the OLT vendor largely decides the controller.

02

The picture

COM — Commercial Order ManagementProduct Order → CFS decompositionProduct OrderTMF622SOM — Service Order ManagementCFS→RFS decomposition, dependency sequencing, orchestration planCFS:Internet-AccessData bearerCFS:WiFi-MgmtCloud WiFiCFS:CPE-MgmtRouter configROM — Resource Order Management7 Resource Order Items dispatched to activation adaptersResource Order (7 ROIs)TMF652Activation AdaptersProtocol-specific southbound adaptersNETCONFOLT adapterNETCONF/CLIBNG adapterRESTIPAM adapterRADIUSDHCP/RADIUSTR-069ACS adapterRESTCloud WiFiBroadband Network ElementsOLT/EMSGPON accessBNGSubscriber sessionIPAMAddress mgmtDHCP/RADIUSAuth & IPACSCPE mgmtCloud WiFiWiFi platformTMF641 Service OrderTMF652 Resource OrderExecution: OLT + CPE ship in parallel → VLAN → IP/QoS → TR-069 → Cloud WiFi

Broadband B2C activation — SOM orchestrates through ROM to provision OLT, BNG, DHCP/RADIUS, IPAM, ACS, and Cloud WiFi

A broadband order: SOM decomposes the CFS items, ROM dispatches resource orders, and protocol-specific adapters configure the OLT, BNG, DHCP/RADIUS, IPAM, ACS and Wi-Fi management.
03

How it works

The elements

ElementRoleTypical integration
BNG / BRASSubscriber session termination at the IP edge: IPoE/PPPoE, RADIUS, QoSNETCONF/YANG (modern); RADIUS/Diameter for sessions; SNMP/CLI (legacy)
OLTPON aggregation: manages ONTs, line cards, PON portsNETCONF/YANG (modern); proprietary EMS (legacy)
ONT / ONUCustomer-side PON termination; handoff to the home networkOMCI on the PON; TR-069 / TR-369 for management
CPE / residential gatewayRouter and Wi-Fi; the customer’s view of "broadband"TR-069 / TR-369 via an ACS
AAA / RADIUSAuthentication, authorisation, accountingRADIUS/Diameter from the BNG; provisioning API from OSS
IPAMAddress and prefix allocation; CGNAT pools; IPv6 prefix delegationREST to OSS; coupled to BNG and RADIUS

The activation chain

1
Media
Field operations

Fibre or copper installed to the premises. Often a field visit.

2
OLT
Access controller

Line card and PON port configured for the subscriber.

3
ONT
Access controller

Registered and activated on the PON.

4
BNG and AAA
ROM adapters

Subscriber profile created on the BNG and in AAA.

5
IPAM
IPAM

Pool or static allocation for the subscriber.

6
CPE
ACS

Configured through the ACS.

Get one step out of order and the customer sees no service. Activating the ONT before the upstream path exists is the classic failure. If the catalog does not encode these dependencies, operations works around them by hand for years.

Access technologies

TechnologyActive elementsNotes
GPON / XGS-PON (FTTH)OLT, ONT, BNGDominant new-build technology; modern OLTs are NETCONF/YANG-managed
25G/50G PON, NG-PON2Higher-speed OLT/ONT pairsSame orchestration surface; emerging in business FTTH and 5G x-haul
VDSL / FTTCDSLAM, BNG, copper distribution pointOften pre-NETCONF kit; declining as copper is decommissioned
DOCSIS (cable)CMTS, cable modemDistinct ecosystem; provisioning differs from PON
Fixed wireless accessgNB / eNB, 5GC / EPC, indoor CPESold as fixed; the radio side is orchestrated through the mobile core (9.5)
Wholesale accessWholesaler’s OLT or DSLAM; retail BNGRetail catalog coordinated with the wholesaler’s order workflow

What the domain exposes upward

AbstractionWhat it representsHides
Residential broadbandInternet access with a bandwidth tier, managed CPEBNG profile, RADIUS attributes, OLT line config, IPAM lease, CPE config
Business Ethernet / leased lineSymmetric uncontended service over fibre with SLAOLT business profile, BNG VRF, IP block, monitoring
Triple playInternet, IPTV multicast and VoIPMulticast groups, IGMP snooping, VoIP CPE provisioning, QoS
Wholesale broadbandRetail product on a wholesaler-delivered circuitWholesaler order coordination, port mapping, handoff type
04

Who owns what

EntitySystem of RecordSystem of EngagementSystem of ReferenceNotes
Physical access plant (fibre, splitters, PON trees)Resource InventoryField operations—Passive; only as good as the last field update.
OLT port and ONT assignmentResource InventoryAccess controller / EMSROMThe access controller holds live state; inventory should reconcile from it.
Broadband service instance (CFS)Service InventorySOMCOMTMF641 order state to COM; TMF652 to ROM for each element.
Wholesale access circuitWholesale providerRetail order managementResource InventoryThe retailer holds a reference and the order state; the wholesaler owns the line.
05

In practice

Access has fewer controller options than IP/MPLS or the mobile core, because legacy GPON ONTs are vendor-matched to the OLT. The main controllers, such as Nokia Altiplano, Calix SMx, Adtran Mosaic and Huawei iManager / NCE, each combine OLT and ONT control with subscriber management, and increasingly CPE management. In practice the controller follows the OLT vendor.

Multi-vendor access is therefore multi-controller orchestration. Interoperability between vendors is technically possible but rarely deployed in production because of the operational risk.

Legacy reality
Most operators run several access technologies at once: FTTH for new build, copper for legacy, DOCSIS on cable estates, fixed wireless for hard-to-reach areas. Each has its own controller or EMS. Customers on copper were connected long before current models existed, and many will migrate to fibre with incomplete line records.
06

The trade-off

What it solves

Encoding the activation chain and its dependencies in the catalog lets one broadband order configure every element in the right order, across access technologies.

What it does not solve

  • The physical work: installs, field visits and line handovers still set the pace.
  • Vendor lock at the OLT layer, which makes each footprint its own controller.
  • Incomplete line records for customers connected before current models.

What it adds

  • Dependencies across six or more elements must be modelled and kept in step with technology changes.
  • Several controllers, one per OLT vendor and technology, behind one SOM.
  • Wholesale access adds an external party’s order states and waiting times.

Architecture decision

How should a second OLT vendor be brought into orchestration?

  • Its own controller, integrated beside the first

    Choose when the new footprint is large and the vendor’s controller is mature; SOM routes by technology and vendor.

  • Under the existing controller’s multi-vendor support

    Choose when the existing controller has proven support for that vendor’s OLTs in production today.

  • Through ROM adapters to the vendor EMS

    Choose when the footprint is small or temporary and a full controller is not justified.

Breaks if one controller is assumed to hide vendor differences it does not. ONT, profile and fault handling then diverge per vendor inside workflows.

07

Takeaways

Key Takeaways

  • Every fixed-access connection involves CPE, ONT or modem, OLT or BNG, plus AAA and IPAM.
  • Media → OLT → ONT → BNG/AAA → IPAM → CPE must run in order; the catalog must encode it.
  • Access technology decides the elements and controllers; most operators run several at once.
  • Multi-vendor access is multi-controller, because the controller follows the OLT vendor.

Check yourself

  • New FTTH customers report "connected light but no internet" on day one. Where do you look first?Show answer

    The activation order and its later steps: BNG subscriber profile, AAA entry, IPAM allocation and CPE configuration. A registered ONT shows the line is up; the service needs the upstream steps too.

  • An operator buys a second OLT vendor and expects its existing access controller to manage it. What do you check?Show answer

    Whether that controller manages the new vendor’s OLTs and ONTs in production. Because ONTs are vendor-matched, the usual result is a second controller, so SOM must route by vendor.