Service Orchestration Module
Service Orchestration executes technical activation and orchestration logic for network-facing service implementation. It translates designed service/resource intent into controlled execution on target network systems.
Business Scope
Service Orchestration covers:
- activation and change execution on network elements,
- orchestration of multi-step technical fulfillment flows,
- method abstraction across southbound interfaces (API, NETCONF/YANG, Ansible, CLI),
- runtime safeguards (throttling, security controls, retries/rollback),
- technical completion feedback to fulfillment/order layers.
Key Concepts
- Design vs Activation: design and resource assignment are decided before activation; orchestration executes prepared intent.
- Execution Plane: controlled runtime where network actions are performed with policy and safety checks.
- Closed-loop Operational Context: activation results are fed back to order/inventory; monitoring remains a separate assurance domain.
Integration Role
Service Orchestration is typically integrated with:
- Ordering: service-order and fulfillment triggers,
- Catalog: service and technical specification logic,
- Inventory: assigned resource and runtime state context,
- external network controllers/NMS/automation platforms.
TMF Concept Alignment (General)
Service Orchestration aligns with TMF fulfillment and activation domains, with implementation-specific extensions for automation methods and operational safeguards.