Skip to main content
BSS/OSS Academy
Domain Examples/Fixed Wireless Access (FWA) — B2B

Fixed Wireless Access (FWA) — B2B

End-to-end flow for a B2B 5G Fixed Wireless Access service: ACME Ltd orders 500 Mbps business internet with a 99.9 % SLA, a static public /30 and a managed CE for its Oslo site. Follows the order from COM and order management through SOM decomposition, what SOM passes to ROM, ROM’s inventory reservation and allocation, activation of the 5G core, transport and PE by their controllers, the site install, end-to-end verification and assurance — and shows why the per-customer VLAN and VRF sit at the core-to-PE handoff, not on the radio backhaul.

Architecture Overview

B2B Fixed Wireless Access delivers business internet over 5G radio instead of fibre. An outdoor CPE with an eSIM attaches to the serving sector; the 5G core authenticates it, sets its speed and QoS, and anchors its static address; the traffic leaves the mobile domain at the UPF and is handed to a PE, on a per-customer VLAN, into the customer’s VRF. The systems above the network decide and orchestrate; the controllers configure; the RAN is shared with every mobile user of the cell — which is why capacity, not configuration, is the hard part. Values are ACME Ltd’s illustrative order.

BSS — COM & Order Managementwhat is sold, and the order for itSOM — Service Order Managementdecomposes and orchestrates the service — never touches a deviceInventoryservice + resource: what exists, its stateROMallocates and orchestrates resourcesNetwork activation — NMS / EMS / controllersconfigure the network — execute, do not chooseCOM: the commercial product and its characteristics. No VLAN, VRF, PE port or radio parameter.Product & offer500 Mbps · SLA · static IPCaptures customer, site, product, SLA, CPE, static IP, installation and requested date, and validates them.Order managementcapture · validateDecomposes B2B Internet Access into the services and resources that deliver it.Service decompositionCFS → FWA · transport · PE · CEPasses requirements, and any instances already selected, to ROM; tracks the result. Configures nothing.Service orchestrationrequirements → ROM · trackRecords the service instance once activation is confirmed.Service inventoryservice instancesCPE, SIM, sector capacity, circuits, interfaces, VLANs, VRFs, IP subnets, PEs, CEs — and their state.Resource inv.available · stateCommits the chosen instances to the order before any configuration, so no other order can take them.Reserve / allocateAVAILABLE → RESERVEDAllocates resources against inventory, creates a resource order per domain, tracks activation and returns status to SOM.Resource orchestrationresource orders · statusCPE management platform: device identity, profile, firmware.CPE mgmtTR-069 / TR-369Core provisioning: the subscription, the static address on the DNN, 5QI / AMBR. The RAN enforces what the core sets.5G coreUDM · PCF · DNNTransport / SDN controller: the circuit, VLAN and QinQ from the UPF site to the PE.TransportSDN · circuit · VLANPE controller or EMS: sub-interface, VRF, addressing, routing, QoS and security policy.PE / IPsub-if · VRF · routeMonitors the SLA, radio quality and sector load, and reconciles the live network with inventory.AssuranceSLA · reconcileCustomer site (B2B)5G RANBackhaul (shared)5G coreIP/MPLS edge — PEInternet / corporate5G NR · n78ACME LtdOslo site · LANManaged CE router at the site, behind the FWA CPE: WAN 203.0.113.2/30, routes the customer LAN. Optional — many FWA sites use the CPE as the router.CEmanaged(optional)CPE-12345 — outdoor 5G FWA unit with eSIM, aligned on sector OSL-042-S03; managed over TR-069 / TR-369.FWA CPECPE-12345gNB — 5G NR, sector OSL-042-S03 serves the site. Shared with every mobile and FWA user of the cell.gNBsector OSL-042-S03RAN backhaul — shared; carries the traffic inside GTP-U tunnels to the core. Nothing per customer is configured here.BackhaulGTP-U tunnelsnothing per customer5G core — UPF anchors the session on DNN acme.fwa with the static /30; SMF, PCF and UDM hold the subscription and the 500 Mbps policy.UPFSMF · PCF · UDMDNN acme.fwastatic IP · 500 MbpsThe per-customer handoff: VLAN 3105 carried on transport circuit CIR-88421 (QinQ) from the UPF site to PE-OSL-01.VLAN 3105CIR-88421PE-OSL-01 — sub-interface xe-0/0/12.3105 in VRF ACME-FWA, 203.0.113.1/30, static route, QoS, anti-spoofing.PE-OSL-01xe-0/0/12.3105VRFACME-FWA203.0.113.0/30Internetor corporate VPN
InventoryCECPE-12345eSIMSector capacityCIR-88421VLAN 3105PE xe-0/0/12VRF ACME-FWA203.0.113.0/30

Press Simulate an activation to watch ACME Ltd’s order for 500 Mbps B2B fixed wireless travel from the product to a verified, live service: the systems light up as they act, a pulse follows each message, and the inventory strip follows each resource from AVAILABLE through RESERVED to IN SERVICE. Tick Simulate a failed activation to see the PE reject the configuration and ROM roll back.

Customer site — CPE & CE

The outdoor 5G CPE (CPE-12345, eSIM) is mounted and aligned on the serving sector; it is managed over TR-069 / TR-369. A managed CE, where ordered, sits behind it at the site and routes the customer LAN — WAN 203.0.113.2/30. Many FWA sites have no CE: the CPE is the router.

5G RAN — gNB sector

Sector OSL-042-S03 on n78 serves the site, shared with every mobile and FWA user of the cell. Usually nothing per customer is configured on the gNB: it enforces the QoS the core signals. What is managed per customer is capacity — the sector’s FWA budget.

Backhaul & 5G core

Backhaul is shared and carries the traffic in GTP-U tunnels — nothing per customer. The core (UDM, PCF, SMF, UPF) holds the subscription, DNN acme.fwa with the static /30, and 5QI / AMBR for 500 Mbps. The same core as mobile handsets.

Transport handoff & PE

Where the per-customer resources live: VLAN 3105 on circuit CIR-88421 (QinQ) from the UPF site to PE-OSL-01, sub-interface xe-0/0/12.3105 in VRF ACME-FWA, 203.0.113.1/30, static routing, QoS and anti-spoofing. A dedicated VLAN and VRF are design choices, not requirements of FWA.

Internet / corporate network

From the VRF, traffic breaks out to the Internet — or, where the design uses it, into the customer’s corporate VPN. Assurance measures the SLA end to end, PE to CE.