Activation Integration: What ROM Actually Talks To
Activation Integration: What ROM Actually Talks To
Sections 3.6–3.10 walked through five complete order lifecycle examples — Broadband B2C, Fixed B2B, Mobile 4G B2C, SD-WAN B2B, and Mobile 5G B2B — from CPQ to ROM activation. But the activation step was deliberately abstract: "ROM sends GPON activation commands to the OLT via NETCONF adapter." Which OLT? Whose adapter? What protocol, exactly? This section lifts the lid on the activation layer across six technology domains, naming the specific vendor systems, products, and protocols that ROM talks to at the bottom of the stack.
The Activation Layer: Where ROM Meets the Network
ROM uses activation adapters (also called southbound plugins, drivers, or mediators) to translate RFS resource order items into vendor-specific protocol calls. Each adapter speaks one protocol to one management system type. The adapter pattern decouples ROM's order logic from the specifics of each network element management system — ROM doesn't need to know NETCONF from RADIUS; the adapter handles that translation.
ROM Activation Adapter Roles
| Adapter Type | What It Abstracts | Protocol(s) | Example Targets |
|---|---|---|---|
| OLT / EMS Adapter | Optical access equipment management | NETCONF, SNMP, TL1 | Nokia AMS, Huawei iMaster NCE, Calix AXOS |
| BNG / RADIUS Adapter | Broadband subscriber session management | NETCONF, RADIUS CoA | Cisco ASR 9000, Nokia 7750 SR, Juniper MX |
| ACS Adapter | CPE remote management | TR-069, TR-369 (USP) | Axiros, CommScope ACS, Incognito DMS |
| UDM / HSS Adapter | Mobile subscriber data management | Diameter, HTTP/2 SBI | Ericsson CCDM, Nokia UDM, Ericsson HSS-FE |
| PCRF / PCF Adapter | Mobile policy and charging control | Diameter Gx, HTTP/2 SBI | Ericsson PCRF/PCF, Nokia PCRF/PCF |
| SIM OTA Adapter | SIM personalisation and eSIM provisioning | OTA SMS-PP, GSMA SGP.22 | G+D OTA, Thales SM-DP+ |
| NSO / SDN Adapter | Network-wide service provisioning (L2/L3VPN, PE config) | NETCONF, RESTCONF | Cisco NSO, Nokia NSP, Ciena MCP |
| MANO Adapter | VNF/CNF lifecycle management | ETSI SOL005 | ONAP, OSM, Ericsson Orchestrator |
| Cloud API Adapter | Public cloud infrastructure | REST SDKs | AWS, Azure, GCP |
| Satellite NMS Adapter | Satellite terminal and beam management | SNMP, Proprietary REST | Hughes NMS, iDirect NMS, ViaSat Platform |
Six Technology Domain Examples
Each tab below shows a realistic activation scenario for a different technology domain. Every example includes: the customer scenario, the RFS-to-activation-target mapping table, the ROM adapter activation sequence, and cross-reference notes linking to deeper content elsewhere in the platform. The six domains cover residential and business variants of fixed access, both 4G and 5G mobile, satellite connectivity, and multi-domain cloud services.
Fixed/Broadband: RFS → Activation Target Mapping
| RFS Item | Activation Target | Protocol |
|---|---|---|
| RFS:GPON-Bearer | Nokia AMS (or Huawei iMaster NCE) | NETCONF |
| RFS:VLAN-Service | Same EMS or access switch | NETCONF |
| RFS:IP-Profile | Infoblox IPAM + Cisco ISE / FreeRADIUS | REST + RADIUS CoA |
| RFS:QoS-Profile | Cisco ASR 9000 BNG (or Nokia 7750 SR BNG) | NETCONF or RADIUS CoA |
| RFS:TR069-Config | Axiros ACS (or CommScope ACS) | TR-069 REST API |
| RFS:Cloud-Controller | CloudWiFi platform (Plume, Calix Cloud) | REST |
ROM Adapter Activation Sequence — Fixed/Broadband
OLT Port Activation
ROM → Nokia AMS (NETCONF)ROM's OLT/EMS adapter opens a NETCONF session to Nokia AMS, creates a GPON service profile on OLT-EAST-07 (Line Card 3, Port 12), and configures the ONT registration. AMS confirms bearer UP.
BNG Session & QoS
ROM → Cisco ASR 9000 BNG (RADIUS CoA)ROM's BNG adapter sends a RADIUS Change-of-Authorization (CoA) to the Cisco ASR 9000 BNG, binding Jane's session (VLAN 1042, IP 10.42.17.22) to QoS policy BW-200-50-RES. The BNG installs the policy in hardware.
ACS Profile Push
ROM → Axiros ACS (REST)ROM's ACS adapter calls the Axiros REST API to create a device management profile for CPE serial HWT2340098. When the CPE first powers on, it will perform a TR-069 Inform to Axiros and receive its full configuration (SSID, WPA3 key, firmware).
Cloud WiFi Registration
ROM → Plume CloudWiFi (REST)ROM's Cloud API adapter registers the CPE with the Plume CloudWiFi platform via REST, linking device CW-89012 to Jane's account and enabling the WiFi management app features.
Cross-Domain Activation Summary
The table below consolidates all six domain examples into a single comparison, showing the key activation targets and protocols for each technology domain.
Cross-Domain Activation Summary
| Technology Domain | Example Product | Key CFS | Key RFS Items | Primary Activation Targets | Protocols |
|---|---|---|---|---|---|
| Fixed / Broadband | SuperFibre 200 Home | CFS:Internet-Access | GPON-Bearer, VLAN, IP-Profile, QoS, TR069, Cloud-Controller | Nokia AMS, Cisco ASR BNG, Axiros ACS, Plume CloudWiFi | NETCONF, RADIUS CoA, TR-069, REST |
| Fixed B2B | Business Ethernet 1Gbps | CFS:Ethernet-Line | PE-Interface, MPLS-VPN, QoS-SLA, CE-Router, Access-Circuit, Monitoring | Cisco NSO, Nokia SAM/NSP, ZTP Server, NMS/APM | NETCONF, RESTCONF, SNMP, ZTP |
| Mobile / 4G | 4G Freedom 30GB | CFS:Mobile-Access | HSS-Subscriber, PCRF-Policy, SIM-OTA, HLR-IN, Voicemail, NP | Ericsson HSS-FE, Ericsson PCRF, G+D OTA, HLR/IN, Voicemail | Diameter (S6a/Gx), MAP/SS7, OTA SMS-PP, REST |
| Mobile / 5G | 5G Unlimited Plus | CFS:Mobile-Access | UDM-Subscriber, QoS-Policy, SIM-Activation, Network-Slice, NP | Ericsson CCDM, Ericsson PCF, Thales SM-DP+, NP Clearinghouse | HTTP/2 SBI, SGP.22, NP API |
| Satellite (GEO) | SatConnect Business 50 | CFS:Satellite-Access | Terminal-Reg, Beam-Assignment, Gateway-Config, QoS-Plan | Hughes NMS, Hughes NCS, Gateway Controller | Proprietary REST, SNMP, NMS API |
| Cloud MSP | Cloud Edge Connect | CFS:Managed-Cloud-Edge | PE-VRF, VNF-Instance, VNF-Config, Cloud-Infra, Direct-Connect, Overlay | Cisco NSO, ONAP NFVO, AWS API | NETCONF, SOL005, REST SDK |
Southbound Protocol Reference
Quick-reference table for the southbound protocols encountered in this section. Each protocol has a different maturity level and standardisation body — understanding this heterogeneity is key to realistic activation architecture.
Southbound Protocol Reference
| Protocol | Standard Body | Primary Use Case | Maturity |
|---|---|---|---|
| NETCONF | IETF (RFC 6241) | Network element configuration (routers, switches, OLTs) | Mature — widely adopted |
| YANG | IETF (RFC 7950) | Data modelling language for NETCONF/RESTCONF payloads | Mature — industry standard |
| RADIUS CoA | IETF (RFC 5176) | Dynamic session policy changes on BNGs | Mature — broadband standard |
| TR-069 (CWMP) | Broadband Forum | CPE remote management and auto-configuration | Mature — deployed at scale, being superseded |
| TR-369 (USP) | Broadband Forum | Next-gen CPE management (MQTT/WebSocket transport) | Emerging — new CPE deployments |
| HTTP/2 SBI | 3GPP (TS 29.5xx) | 5G Core network function service-based interfaces | Mature for 5G SA — replacing Diameter |
| Diameter | 3GPP / IETF | 4G/LTE subscriber and policy signalling (HSS, PCRF) | Mature — legacy for 5G, still dominant in 4G |
| MAP / SS7 | 3GPP / ITU-T | HLR/IN supplementary voice services, legacy number portability | Legacy — being replaced by IMS/Diameter, but still in production for CS voice |
| ZTP (DHCP+TFTP) | IETF / Vendor | Zero Touch Provisioning for managed CE routers and CPE | Mature — widely supported by Cisco, Juniper, Nokia CE platforms |
| TWAMP | IETF (RFC 5357) | Two-Way Active Measurement Protocol for SLA monitoring (latency, jitter, loss) | Mature — standard for IP SLA measurement |
| GSMA SGP.22 | GSMA | eSIM profile provisioning (SM-DP+ to eUICC) | Mature — standard for eSIM |
| ETSI SOL005 | ETSI NFV ISG | VNF/CNF lifecycle management (NFVO northbound) | Mature — MANO standard |
| Cloud REST SDKs | AWS / Azure / GCP | Public cloud infrastructure provisioning | Mature — vendor-specific |
| SNMP | IETF (RFC 3411-3418) | Legacy device monitoring and basic configuration | Legacy — being replaced by NETCONF |
Section 3.11 Key Takeaways
- ROM talks to management systems (EMS, NMS, ACS, UDM, NFVO), not directly to hardware — the activation adapter pattern provides the abstraction layer
- Fixed/Broadband activation involves three distinct system types and protocols: EMS (NETCONF), BNG (RADIUS CoA), and ACS (TR-069 REST)
- Mobile/4G activation targets HSS + PCRF + HLR/IN over Diameter (S6a, Gx) and MAP/SS7 — still the majority of global mobile activations. Mobile/5G shifts to UDM + PCF over HTTP/2 SBI with eSIM via GSMA SGP.22
- Fixed B2B activation is fundamentally different from residential: it involves PE-to-PE MPLS transport (via NSO), managed CPE provisioning (via ZTP), and SLA monitoring from Day 1 — with multi-site orders generating multiple parallel resource orders
- Satellite has no standardised southbound interface — each vendor (Hughes, iDirect, ViaSat, Starlink) requires a proprietary adapter, unlike the convergence seen in terrestrial networks
- Cloud MSP is the most complex domain: ROM orchestrates across NSO + MANO + cloud APIs in phased activation, and SOM owns the cross-system saga for compensation
- The southbound protocol landscape is heterogeneous by design — NETCONF, RADIUS, TR-069, HTTP/2 SBI, SOL005, and cloud SDKs all coexist in a single operator's activation stack
- Catalog-driven engine routing (Module 9 Section 9.4) selects the correct adapter at runtime based on RFS technology indicators — ROM doesn't hardcode which adapter to use
- This section gives the conceptual map of what ROM talks to; Module 9 provides the engineering depth of how the routing and integration actually works