Fixed Access & Broadband

Fixed access is the orchestration domain that touches the largest number of customer endpoints in any operator — millions of homes and businesses, each with a physical media (fibre, copper, coax, fixed wireless) and a CPE. The orchestration story is dominated by subscribers, sessions, and CPE lifecycle, not by service models, and it is the domain most coupled to physical fulfilment workflows (truck rolls, line handover, CPE shipping).

This section covers BNG/BRAS subscriber sessions, PON access (OLT/ONT/ONU), CPE management, IPAM coupling, and the dominant access controllers. The goal is to make the orchestration interface explicit at three places where this domain is uniquely fragile: subscriber session state, IP allocation, and the activation sequence between physical media and service.

Domain Anatomy: BNG, OLT, ONT, CPE

Fixed access is a multi-element domain — every customer connection involves at least three managed elements (CPE, ONT/modem, OLT/BNG) plus AAA and IPAM. Understanding what each element does dictates the orchestration responsibilities and where state has to live.

Access Technologies and Their Orchestration Implications

The access medium determines the elements involved and the activation flow. Most operators run several technologies in parallel — FTTH for new build, DSL/copper for legacy, DOCSIS for cable estates, fixed wireless for hard-to-reach areas — each with its own controller, EMS, or vendor stack.

The Subscriber Session Model

Unlike IP/MPLS — where the orchestrator configures relatively static services — fixed access is dominated by subscriber sessions that come and go. A customer's session is created when their CPE connects, authenticated against AAA, given an IP address by IPAM, granted policy by the BNG, and torn down on disconnect. The orchestrator does not manage individual sessions; it manages the subscriber profile that determines what sessions are allowed and how they are policed.

Service Abstractions in Fixed Access

Access Controllers and EMS

The access domain has fewer controller options than IP/MPLS or mobile core, partly because access is heavily vendor-locked at the OLT layer (the OLT vendor and ONT vendor must match for legacy GPON). The major access controllers all combine OLT/ONT control with subscriber management and increasingly with CPE management.

IPAM Coupling: The Hardest Integration

Every fixed-access subscriber needs IP. At Tier-1 scale, that is millions of IPv4 addresses (most behind CGNAT) and IPv6 prefixes. IPAM is the hardest integration in the access domain because it is the only one that has to be transactional, low-latency, and survive every BNG event without divergence between IPAM, BNG, and RADIUS state.

• IPv4 with CGNAT — public IPv4 pools shared via CGNAT; the orchestrator allocates the inside-IP, the BNG/CGNAT box does the public mapping at session time.
• IPv6 prefix delegation — each subscriber typically gets a /56 or /64 prefix, allocated by IPAM, delegated through the BNG via DHCPv6-PD or RADIUS attributes.
• Dual-stack — most operators run IPv4 + IPv6 simultaneously, each from its own pool, with their own address-family lifetime and renewal cadence.
• Static allocation — business customers and BGP-peered enterprises need static IPs; these must be reserved, never recycled, and tied to the customer record across CPE replacements.

CPE Management: TR-069 and TR-369 (USP)

The CPE is the only OSS-managed element inside the customer's home or office. Managing it requires a remote-management protocol that survives NAT, intermittent connectivity, and the customer's right to power-cycle their router on a whim.

Anti-Patterns in Fixed-Access Orchestration