Internet-Draft UNCO April 2025
Li & Li Expires 26 October 2025 [Page]
Workgroup:
Neotec Working Group
Internet-Draft:
draft-li-unco-framework-00
Published:
Intended Status:
Standards Track
Expires:
Authors:
X. Li
China Telecom
C. Li
China Telecom

Unified Network and Cloud Orchestration Framework

Abstract

This draft introduces the Unified Network and Cloud Orchestration Framework (UNCO), a framework designed to enable real-time joint orchestration of network and computing resources in 5G and future-generation networks. UNCO framework addresses inefficiencies in current resource scheduling mechanisms, resolves objective conflicts across domains, and provides unified policy and security management. It is applicable in emerging scenarios such as ultra-reliable low-latency communications (URLLC), mobile edge computing (MEC), and network slicing, where service quality and operational efficiency are paramount.

Status of This Memo

This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79.

Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet-Drafts is at https://datatracker.ietf.org/drafts/current/.

Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress."

This Internet-Draft will expire on 26 October 2025.

▲

Table of Contents

1. Introduction

As 5G and next-generation networks evolve to support latency-sensitive, compute-intensive, and highly dynamic applications, traditional siloed orchestration mechanisms are no longer sufficient. The integration of network and computing resources is essential to enable real-time, adaptive service provisioning. Current industry efforts such as ETSI NFV [NFV033], 3GPP MEC, and IETF service chaining [RFC8969] have made progress in specific domains, but a holistic orchestration framework that bridges network and computing domains with unified security and policy governance remains lacking.

In addition, Telecom Clouds introduce new operational complexities that differ significantly from public cloud deployments. Unlike public clouds, which rely on third-party network providers, Telecom Clouds operate under a single administrative domain where both network and cloud infrastructure are tightly coupled and managed by the same operator. This integration opens up opportunities for real-time coordination between cloud service scaling events and network policy adjustments. However, most existing network management systems lack visibility into dynamic cloud states, which can lead to inefficient load balancing, suboptimal routing, and SLA violations for critical services like AI/ML pipelines, video streaming, and 5G slice traffic.

To address these limitations, the UNCO framework introduces a telemetry-driven mechanism whereby cloud-side resource and service status can be abstracted and delivered to network controllers in near real-time. This mechanism enables the dynamic adjustment of network policies such as UCMP and load balancing, based on ongoing changes in cloud resource availability or service deployment state. Unlike existing IETF efforts (e.g., TEAS [draft-ietf-teas-ietf-network-slice-framework], OPSAWG [draft-ietf-opsawg-service-assurance-architecture], CATS [draft-ietf-cats-framework]), which offer valuable foundations for traffic engineering and service-aware routing, UNCO builds upon and extends them by incorporating real-time cloud-derived metrics directly into the orchestration logic. This approach ensures SLA-compliant, fine-grained orchestration of both network and compute infrastructure in multi-cloud and Telecom Cloud environments.

The Unified Network and Cloud Orchestration framework (UNCO) addresses these gaps by enabling:

UNCO introduces a layered architectural model with well-defined functional modules and interfaces to facilitate standardization and interoperability among diverse vendor ecosystems.

2. Conventions used in this document

The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in [RFC2119] [RFC8174].

3. Terminology

The following terms are used in this draft:

4. Problem Overview

4.1 Real-Time and Dynamic Resource Scheduling

Modern applications, such as immersive reality, smart manufacturing, and vehicular communication systems, demand rapid provisioning and adjustment of both compute and network resources. Traditional orchestrators often pre-allocate resources statically or based on historical models, which are ill-suited to handle:

These limitations lead to under-utilization of expensive infrastructure and inconsistent quality of experience (QoE).

4.2 Contradictions Among Different Objectives

Multiple stakeholders often have conflicting optimization goals. For instance:

A successful orchestration strategy must balance these trade-offs dynamically, based on service priorities and system state.

4.3 Lack of Joint Effectiveness Evaluation

Scheduling strategies are often evaluated independently in the context of either network performance (e.g., throughput, delay) or computing performance (e.g., CPU usage, task completion time). However, next-gen services require holistic metrics that combine:

Such unified metrics are crucial for validating orchestration policies.

4.4 Security and Strategy Fragmentation

Network policy (e.g., firewalls, ACLs, segmentation) and cloud security policy (e.g., IAM, security groups) are traditionally managed in isolation. This results in:

UNCO proposes a security-unified model to enforce coherent policies across cloud and network domains.

5. Overview of the UNCO framework

This section provides an overview of the UNCO framework and an introduction to its key components. The high-level framework overview of UNCO is shown in Figure 1.

UNCO is composed of three primary modules:

  1. NS-OSS (Network Service Orchestration and Scheduling System): The central decision-making and coordination entity responsible for managing service deployment, orchestrating cross-domain resources, and enforcing global policies.

  2. Cloud Manager: A cloud-native resource controller that abstracts heterogeneous computing resources (VMs, containers, GPUs, NPUs, etc.) across edge and central cloud domains. It acts as the compute-plane orchestrator, reporting availability and enforcing workload deployment.

  3. Network Controller: A domain-specific SDN or legacy-compatible controller that governs routing, QoS, and telemetry. It operates on the data plane and acts as a programmable policy agent for traffic forwarding, service chaining, and SLA-aware path selection.

These components are deployed in a logically centralized but physically distributed manner to support scalability and fault tolerance. They interact via well-defined interfaces and protocols to deliver seamless joint orchestration.

UNCO is designed to operate across hybrid infrastructures:

                   +----------------+
                   |  Application   |
                   +----------------+
                        |     |
                      IN1.1  IN1.2
                        |     |
                   +----------------+ --IN2.1--  +----------------+
                   |     NS-OSS     | --IN2.2--  | Cloud Manager  |
                   +----------------+            +----------------+
                        |       |                        |
                      IN3.1   IN3.2                      |
                        |       |                        |
                  +-------------------+                  |
                  |Network Controller |                  |
                  +-------------------+                  |
                           |                             |
              +------------------------+       +---------------------+
              |      Public Cloud      |-------| Cloud(VM/containers,|
              |        (WAN)           |       |  GPUs/NPUs,etc.)    |
              +------------------------+       +---------------------+
  Figure 1 The overall  framework of UNCO

Each module can scale independently, supporting multi-tenancy, high availability, and flexible deployment topologies. NS-OSS typically includes a policy engine, resource graph model, service catalog, and intent resolution logic. It may integrate with external OSS/BSS systems for commercial service integration.

5.1. NS-OSS

The NS-OSS (Network Service Orchestration and Scheduling System) serves as the brain of the UNCO framework. It is designed to perform centralized decision-making while maintaining awareness of service requirements, real-time resource availability, and policy enforcement across domains. NS-OSS is capable of translating high-level application intents into concrete actions such as workload placement, bandwidth allocation, and route optimization.

It plays a vital role in translating service-level requirements into programmable tasks, ensuring optimal resource usage while maintaining SLA commitments. The NS-OSS also maintains a global topology and performance view of both computing and networking infrastructure, enabling end-to-end orchestration decisions. Moreover, it ensures feedback-driven loop closure, adapting orchestration actions based on monitored outcomes. Through coordination with both the Cloud Manager and the Network Controller, the NS-OSS can adjust deployments in response to failures, demand surges, or SLA violations.

The NS-OSS is a logically centralized orchestrator with the following extended capabilities:

5.2. Cloud Manager

The Cloud Manager is responsible for abstracting and managing the compute, storage, and specialized acceleration resources (e.g., GPU, TPU, NPU) across different cloud domains, including edge, regional, and centralized clouds. It serves as the execution agent for deployment decisions initiated by the NS-OSS and provides real-time feedback on resource utilization and availability.

Beyond resource abstraction, the Cloud Manager enables policy-compliant service instantiation, performance monitoring, and failure detection at the compute layer. It supports diverse virtualization and containerization technologies, offering a unified interface for NS-OSS to interact with heterogeneous platforms such as Kubernetes, OpenStack, or bare-metal clusters. In the UNCO framework, the Cloud Manager plays a critical role in edge computing scenarios, ensuring proximity-based service placement and maintaining low-latency, high-reliability requirements. Furthermore, it facilitates fine-grained scaling decisions that match service-level intents, contributing directly to elastic, resilient orchestration.

The Cloud Manager serves as the bridge between orchestration logic and actual compute substrates. Its extended functionalities include:

5.3. Network Controller

The Network Controller in UNCO serves as a programmable interface between orchestration logic and the physical or virtual network infrastructure. It is responsible for interpreting policies and traffic engineering directives from NS-OSS and translating them into actionable configurations on network devices or SDN agents.

As the network-facing component, the controller collects real-time metrics from the underlying transport and access networks, including traffic utilization, link health, congestion indicators, and routing anomalies. These insights feed back into NS-OSS to enable adaptive reconfiguration in response to network dynamics. The controller also supports integration with emerging technologies such as P4 programmable data planes and segment routing protocols, allowing fine-grained per-flow steering based on SLA metadata or service tags.

By interfacing with the Cloud Manager, the Network Controller becomes cloud-aware, enabling traffic paths to be optimized based on the location, health, and demand patterns of compute resources. This makes the UNCO framework especially suitable for distributed AI, AR/VR, and latency-sensitive applications. Additionally, it supports inter-domain coordination for multi-cloud and multi-vendor environments, ensuring robust, scalable service delivery across complex topologies.

The Network Controller performs programmable data-plane management and service-aware traffic engineering:

6. Standard Interfaces and Functional Requirements

6.1. Standard Interfaces

The UNCO framework defines standard interfaces between its components to support unified orchestration and closed-loop control across cloud and network domains. The interfaces are categorized as follows:

1) IN1: Application - NS-OSS Interface

This interface enables applications to interact with the orchestration system for service deployment and resource feedback.

2) Cloud Manager - NS-OSS Interface

This interface enables the Cloud Manager to provide real-time cloud resource status to NS-OSS.

3) IN3: NS-OSS - Network Controller Interface

This interface allows the NS-OSS to dynamically program the network according to real-time cloud and service conditions.

6.2. Functional Requirements

To ensure UNCO can support a wide range of networked applications across edge, cloud, and transport environments, it defines a set of functional requirements that guide its architectural design and interface behaviors. These requirements emphasize responsiveness, reliability, and compatibility across multi-vendor, multi-domain infrastructures. The following functions are essential to enable joint orchestration of computing and networking resources while preserving service quality, optimizing resource utilization, and maintaining policy consistency.

Here are some functional requirements:

7. Conclusion

Cloud computing has become a foundational component in the infrastructure of modern telecom operators. With the increasing deployment of cloud-based AI services and edge-native applications, it is essential to support integrated orchestration of cloud and network resources as well as end-to-end security management. UNCO addresses this need by providing mechanisms to incorporate cloud-related information into network control and policy decision-making, enabling dynamic, SLA-driven service management.

However, the lack of standardized interfaces and models for exchanging cloud telemetry across the network domain remains a key obstacle. Cross-domain collaboration is often hindered by proprietary APIs, inconsistent abstractions, and limited interoperability. These limitations result in delayed network adjustments and fragmented service delivery.

UNCO addresses these challenges by proposing a unified framework and standardized interfaces that bring real-time cloud awareness into network orchestration. Its ability to coordinate compute and network resources holistically enables more resilient, efficient, and SLA-compliant service delivery across public clouds, private datacenters, and edge platforms.

As UNCO continues to evolve, its ability to bridge these gaps through telemetry integration, policy abstraction, and multi-domain orchestration will be critical. Potential application scenarios include:

These emerging services demand orchestration frameworks like UNCO that go beyond siloed resource management and offer unified, programmable, and standards-aligned operational control.

UNCO presents a comprehensive framework for integrating computing and networking orchestration in modern networks. By addressing dynamic scheduling, multi-objective trade-offs, cross-domain policy harmonization, and end-to-end security, UNCO provides a strong foundation for enabling future-ready services.

8. IANA Considerations

TBD

9. Acknowledgement

TBD

10. Normative References

[draft-ietf-cats-framework]
"Computing-Aware Traffic Steering Framework".
[draft-ietf-opsawg-service-assurance-architecture]
"draft-ietf-opsawg-service-assurance-architecture – Service Assurance Architecture".
[draft-ietf-teas-ietf-network-slice-framework]
"draft-ietf-teas-ietf-network-slice-framework – IETF Network Slice Framework", .
[NFV033]
"ETSI GS NFV-IFA 033-2020", .
[RFC2119]
"".
[RFC8174]
"Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words".
[RFC8969]
"A Framework for Automating Service and Network Management with YANG".

Authors' Addresses

Xueting Li
China Telecom
Beiqijia Town, Changping District
Beijing
Beijing, 102209
China
Cong Li
China Telecom
Beiqijia Town, Changping District
Beijing
Beijing, 102209
China