Multi-Domain Orchestration
Network Integration & Service Orchestration
How OSS orchestrates fulfilment across IP/MPLS, mobile core, transport, and access domains. Establishes the strict layering between COM/SOM, cross-domain orchestration, and ROM/domain controllers, and works through the integration patterns, protocols, and worked examples that turn an RFS into configured network state.
Sections
OSS Functional Layering & Cross-Domain Orchestration
A strict functional layering of the OSS runtime path β CRM/CPQ, COM/SOM, cross-domain service orchestration, ROM / domain execution β and why each layer is a distinct product category. Clarifies where Itential, Ericsson Order Care, Hansen Order Management, Cisco NSO, Nokia E2E SO, Ericsson SOA, Blue Planet MDSO, and Oracle Unified Orchestrator actually sit.
Domain Integration: The Universal Pattern
The integration pattern shared by every OSS-to-network conversation: service intent β resource intent β domain commands β network state. Establishes the abstraction contract domain controllers must hold, the protocols that carry each layer (NETCONF/YANG, gNMI, 3GPP SBI, RADIUS, TR-069/USP, legacy SNMP/TL1/SOAP), data-model alignment (SID β YANG β proprietary), and the rollback shapes that exist by domain class. Anti-patterns: scripting the EMS, imperative payloads, assumed cross-domain ACID.
IP / MPLS / Transport Domain
IP/MPLS, transport, and optical as a single orchestration domain. Covers PE/P/RR topology, transponders/ROADM, the service abstractions exposed (L3VPN, L2VPN/EVPN, IP transit, optical Ξ», SR transport, transport slicing), the standardised IETF YANG service models (L3SM/L3NM/L2NM/L1CSM), the controller layer (Cisco NSO, Nokia NSP, Juniper Paragon, Blue Planet, ONAP SDN-C), live topology awareness via BGP-LS and PCEP/SR-PCE, and the legacy SDH/SONET integration gap. Anti-patterns: per-VRF Jinja-templated NSO, hard-coded SR paths in the catalog, vendor-flavoured service models leaking into XDO.
Mobile Core Integration (4G / 5G)
Mobile core as a single orchestration domain. 3GPP refresher (4G EPC: HSS/MME/S-PGW/PCRF; 5GC: AMF/SMF/UPF/UDM/PCF/NSSF/NRF). What the orchestrator actually configures (subscriber/profile, DNN/APN, QoS, slice templates, policy). Network slicing as the first-class XDO use case (3GPP 28-series, GSMA GST/NEST). MANO architecture (NFVO/VNFM/VIM) and Day-0/1/2 lifecycle. NFVI generations (OpenStack vs Kubernetes). Vendor stacks (Nokia OC, Ericsson SOA, Mavenir, ONAP). Anti-patterns: treating 5GC NFs as routers, SOM hard-coding infrastructure, slice = list of NF configs.
Fixed Access & Broadband
Fixed access as an orchestration domain dominated by subscribers, sessions, and CPE. Covers BNG/BRAS subscriber session model (IPoE/PPPoE, RADIUS), PON access (OLT/ONT/ONU), CPE management (TR-069 and TR-369/USP), IPAM coupling (CGNAT, IPv6 prefix delegation), access controllers (Nokia Altiplano, Calix SMx, Adtran Mosaic, Huawei iManager/NCE), and the activation chain from media to service. Anti-patterns: ONT activated before upstream service path, session events treated as orchestration events, IPAM as an afterthought.
Cross-Domain Composition: Worked Examples
Four worked examples that compose across the domains established earlier: Enterprise SD-WAN (MPLS L3VPN + CPE + IPAM + optional 5G backup), 5G enterprise URLLC slice (RAN + transport + core SLA composition), FTTH residential broadband (OLT + BNG + IPAM + CPE + workforce), and Enterprise Ethernet (L2VPN/EVPN + NID + activation testing TMF634). Each example shows the dependency graph, execution sequence, rollback scope, and assurance feedback path. Cross-cutting lessons: IPAM first, capacity-as-reservation, saga rollback (not transaction), activation testing as a gate, assurance armed at activation, workforce as a first-class actor.