<?xml version="1.0" encoding="utf-8"?>
<!-- 
     draft-rfcxml-general-template-standard-00
  
     This template includes examples of the most commonly used features of RFCXML with comments 
     explaining how to customise them. This template can be quickly turned into an I-D by editing 
     the examples provided. Look for [REPLACE], [REPLACE/DELETE], [CHECK] and edit accordingly.
     Note - 'DELETE' means delete the element or attribute, not just the contents.
     
     Documentation is at https://authors.ietf.org/en/templates-and-schemas
-->
<?xml-model href="rfc7991bis.rnc"?>  <!-- Required for schema validation and schema-aware editing -->
<!-- <?xml-stylesheet type="text/xsl" href="rfc2629.xslt" ?> -->
<!-- This third-party XSLT can be enabled for direct transformations in XML processors, including most browsers -->


<!DOCTYPE rfc [
  <!ENTITY nbsp    "&#160;">
  <!ENTITY zwsp   "&#8203;">
  <!ENTITY nbhy   "&#8209;">
  <!ENTITY wj     "&#8288;">
]>
<!-- If further character entities are required then they should be added to the DOCTYPE above.
     Use of an external entity file is not recommended. -->

<rfc
  xmlns:xi="http://www.w3.org/2001/XInclude"
  category="info"
  docName="draft-hu-neotec-usecases-notc-00"
  ipr="trust200902"
  obsoletes=""
  updates=""
  submissionType="IETF"
  xml:lang="en"
  version="3">
<!-- [REPLACE] 
       * docName with name of your draft
     [CHECK] 
       * category should be one of std, bcp, info, exp, historic
       * ipr should be one of trust200902, noModificationTrust200902, noDerivativesTrust200902, pre5378Trust200902
       * updates can be an RFC number as NNNN
       * obsoletes can be an RFC number as NNNN 
-->

  <front>
    <title abbrev="draft-hu-neotec-usecases-notc-00">Use cases in network operations in telco cloud
    </title>
    <!--  [REPLACE/DELETE] abbrev. The abbreviated title is required if the full title is longer than 39 characters -->

    <seriesInfo name="Internet-Draft" value="draft-hu-neotec-usecases-notc-00"/>
   
    <author fullname="Jiayuan Hu" initials="Jiayuan" role="editor" surname="Hu">
      <organization>China Telecom</organization>
      <address>
        <postal>
          <street>109, West Zhongshan Road, Tianhe District</street>
          <city>Guangzhou</city>
          <region>Guangdong</region>
          <code>510000</code>
          <country>CN</country>
        </postal>
        <email>hujy5@chinatelecom.cn</email>
      </address>
    </author>

    <author fullname="Fan Zhang" initials="F" role="editor" surname="Zhang">
      <organization>China Telecom</organization>
      <address>
        <postal>
          <street>109, West Zhongshan Road, Tianhe District</street>
          <city>Guangzhou</city>
          <region>Guangdong</region>
          <code>510000</code>
          <country>CN</country>
        </postal>
        <email>zhangf52@chinatelecom.cn</email>
      </address>
    </author>

    <author fullname="Yongqing Zhu" initials="Y" role="editor" surname="Zhu">
      <organization>China Telecom</organization>
      <address>
        <postal>
          <street>109, West Zhongshan Road, Tianhe District</street>
          <city>Guangzhou</city>
          <region>Guangdong</region>
          <code>510000</code>
          <country>CN</country>
        </postal>
        <email>zhuyq8@chinatelecom.cn</email>
      </address>
    </author>

    <author fullname="Chongfeng Xie" initials="C" surname="Xie">
      <organization>China Telecom</organization>

      <address>
        <postal>
          <street>Beiqijia Town, Changping District</street>

          <city>Beijing</city>

          <code>102209</code>

          <country>CN</country>
        </postal>

        <email>xiechf@chinatelecom.cn</email>
      </address>
    </author>

    <date year="2025"/>
    <!-- On draft subbmission:
         * If only the current year is specified, the current day and month will be used.
         * If the month and year are both specified and are the current ones, the current day will
           be used
         * If the year is not the current one, it is necessary to specify at least a month and day="1" will be used.
    -->

    <area>Routing</area>
    <workgroup>NeoTec</workgroup>
    <!-- "Internet Engineering Task Force" is fine for individual submissions.  If this element is 
          not present, the default is "Network Working Group", which is used by the RFC Editor as 
          a nod to the history of the RFC Series. -->

    <keyword>RFC</keyword>
    <!-- [REPLACE/DELETE]. Multiple allowed.  Keywords are incorporated into HTML output files for 
         use by search engines. -->

    <abstract>
      <t>This document presents two network operations in telco cloud orchestration use case for AI-based video recognition
        in smart city management and dynamic high-bandwidth transport. Key innovations include dynamic resource scheduling
        across heterogeneous computing (GPU/NPU) and network domains, centralized training with distributed
        inference, and low-latency data transmission compliant with data sovereignty requirements. Additionally,
        the use case demonstrates elastic bandwidth provisioning and failover mechanisms to ensure reliability.
        The framework highlights the need for standardized interfaces between cloud and network controllers to
        optimize performance, resource utilization, and QoS in telecom cloud environments.
</t>
    </abstract>
 
  </front>

  <middle>
    
    <section>
      <name>Introduction</name>
      <t>
        This document presents two network operations in telco cloud scheduling use case including AI-based video
        recognition in smart city management and dynamic high-bandwidth transport.
        The AI-based video use case addresses critical urban governance challenges including illegal street vending,
        unauthorized parking, garbage disposal, and waste classification through intelligent video analysis.
      </t>
      <t>
        dynamic high-bandwidth transport is an innovative network solution to address the challenges of
        large-scale, cross-regional data migration for high-performance computing (HPC), AI training, scientific
        research, and enterprise applications. It provides on-demand, elastic, and secure high-bandwidth connectivity
        tailored for temporary or periodic bulk data transfers, significantly reducing costs and improving
        efficiency compared to traditional methods like physical hard disk shipping or fixed-bandwidth dedicated lines.
        It enables instant setup and teardown of connections, allowing users to request bandwidth (1G-100G)
        only when needed (e.g., for scheduled nighttime transfers). Supports multi-dimensional billing (bandwidth,
        duration, distance, traffic volume, or usage frequency). Moreover, dynamic high-bandwidth transport can
        dynamically adjust bandwidth (e.g., from 30M to 10G in seconds) to match data transfer demands and implements
        network slicing (FlexE/IPv6+), SRv6 tunneling, and encryption to ensure data isolation and integrity.
      </t>
      <t>
        One of the example of dynamic high-bandwidth transport is LHAASO cosmic ray observatory, it transfers 11PB
        data from Sichuan to Beijing for processing per year. Reduced a 1.6TB transfer over 2,000 km to 40
        minutes (vs. days via hard disks). In AI/ML training area, dynamic high-bandwidth transport supports
        large-scale dataset migration to GPU clusters for distributed training. Moreover, PB-scale video rendering
        can be uploaded to cloud-based post-production studios in hours (e.g., 2TB/day via 10Gbps) in media production
        scenario.
      </t>
    </section>
      
    <section title="Conventions Used in This Document">
      <section>
        <name>Requirements Language</name>
        <t>The key words "MUST", "MUST NOT", "REQUIRED", "SHALL",
          "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT
          RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be
          interpreted as described in BCP 14 <xref target="RFC2119"/>
          <xref target="RFC8174"/> when, and only when, they appear in
          all capitals, as shown here.</t>
      </section>

      <section title="Abbreviations">
        <t> LHAASO: Large High Altitude Air Shower Observatory</t>
        <t> UCMP: Unequal-Cost Multi-Path routing</t>
      </section>
    </section>
      <!-- [CHECK] The 'Requirements Language' section is optional -->

    <section>
      <name>Problem Statement</name>
      <t>
        Telecom Clouds integrate compute, storage, and networking resources to deliver low-latency,
        high-bandwidth services such as 5G, AI/ML workloads, and real-time media processing. Unlike
        public clouds that depend on third-party networks, Telecom Clouds are operated under a single
        administrative domain, enabling tight coupling between cloud infrastructure and network operations.
        However, existing network management systems lack real-time visibility into dynamic cloud resource
        states, resulting in suboptimal performance, inefficient resource utilization, and SLA violations.
        Key challenges include:
      </t>
      <t>
        1. Network controllers remain unaware of cloud-side scaling events (e.g., VM/container orchestration,
        GPU resource allocation), preventing dynamic adjustments to load balancing, UCMP routing, or QoS policies.
      </t>
      <t>
        2. While cloud platforms (e.g., AWS CloudWatch, Azure Monitor) expose resource metrics, no standardized
        APIs or data models exist for network controllers to ingest and act on this telemetry in real time.
      </t>
      <t>
        3. AI/ML pipelines, 5G network slicing, and inter-cloud traffic exhibit highly variable patterns.
        Without real-time coordination between cloud resource availability and network state, traffic
        engineering becomes reactive, leading to congestion, unbalanced resource usage, and degraded QoE.
      </t>
      <t>
        4. standardized interface for informing routing decisions like UCMP weight adjustments, flow
   steering, or bandwidth allocation.<xref target="draft-li-unco-framework"/>
      </t>
      <t>
        5. Traditional network orchestrators often pre-allocate resources statically or based on historical
        models, but modern applications demand rapid provisioning and adjustment of both compute and network
        resources. Real-Time and dynamic resource scheduling ability is needed.<xref target="draft-li-unco-framework"/>
      </t>
      <t>
        To solving the problem is critical to achieving true cloud-network convergence, where dynamic cloud
        workloads and network resources are orchestrated as a unified system.
      </t>
    </section>

    <section>
      <name>Use Cases</name>
      <section>
        <name>Example 1: AI-based Video Recognition for City Management</name>
        <t>
          This use cases leverages cloud-network-computing integration to enable
          intelligent urban governance through real-time video analytics. Key Applications include
        </t>
        <t>
          1. Illegal Street Vending Detection: Identifies static objects (e.g., tables, chairs) left in restricted
          zones for prolonged periods, indicating unauthorized vending activities.
        </t>
        <t>
          2. Unauthorized Parking Monitoring: Detects vehicles parked in no-parking areas by analyzing predefined
          zones in video feeds.
        </t>
        <t>
          3. Litter and Waste Management: Flags scattered waste (bottles, paper, bags) on streets and
          overflowing/uncovered trash bins.
        </t>
        <t>
          4. Public Space Compliance: Monitors violations like disorderly wiring and shopfront obstructions.
        </t>
        <t>
          For the cameras used in urban management, the main network structure is shown in the following figure:
        </t>
        <figure>
          <name>The framework of AI-based video recognition for city management</name>
        <artwork align="center"><![CDATA[
                         +---------------------+
                         |     Street Cameras  |
                         +---------------------+
                             /             \
                            /               \
            (Cellular Access)           (WiFi Access)
                          /                 \
                    +--------+         +-------------+
                    |  eNB   |         |  WiFi AP   |
                    +--------+         +-------------+
                          |                   |
                          |                   |
            +----------------------+    +----------------------+
            |        UPF           |    |    Access PE Router  |
            +----------------------+    +----------------------+
                    |                             |
                    |                             |
                    |                             |
                   +-------------------------------+
                   |        Provider Transport     |
                   |            Network (TE)       |
                   +-------------------------------+
                                  |
                                  |
                                  v
                    +---------------------------+
                    |  Edge PE Router (per site)|
                    +---------------------------+
                                  |
                                  |
                                  v
                        +--------------------+
                        |  Edge Cloud Gateway|
                        |  + AI Model Module |
                        +--------------------+
	   ]]></artwork>
        </figure>
        <t>
          In the cloud-network convergence architecture, AI cameras transmit data  via cellular networks
          (e.g., through eNBs/gNBs and User Plane Functions (UPFs)) or WiFi Access Points.For cellular access,
          data is forwarded via GTP-U tunnels from eNBs to UPFs, which are often co-located with Edge Cloud sites.
          Data traverses the provider's transport network between the access point (PE router) and the Edge Cloud
          PE router. The Edge PE router connects to the Edge Cloud Gateway or compute node hosting the
          AI workload (e.g., real-time inference modules). A Cloud Manager evaluates end-to-end paths
          (bandwidth, latency, topology) between cameras and Edge Cloud sites to select optimal deployment
          locations for AI models.Network controllers dynamically adjust UCMP (Unequal Cost Multipath) load-balancing
          algorithms to meet performance constraints (e.g., XX Gbps bandwidth, YY ms delay) for
          inter-site data exchange. <xref target="draft-dunbar-neotec-ac-te-applicability"/>
        </t>
        <t>
          This architecture ensures low-latency, high-throughput data transmission for real-time AI processing
          while enabling dynamic resource allocation based on network-aware metrics. The solution leverages edge
          computing infrastructure to deploy AI inference models closer to data sources, enabling real-time
          processing of high-resolution video streams with millisecond-level response times. Key technical
          components include:
        </t>
        <t>
        1.Centralized training at the group data center with distributed edge inference
        </t>
        <t>
        2.Dynamic resource orchestration across heterogeneous computing facilities (GPU/NPU-enabled edge nodes)
        </t>
        <t>
        3.Cloud-aware network optimization ensuring low-latency data transmission
        </t>
        <t>
        4.Data sovereignty compliance through localized processing
        </t>
      </section>
      <section>
        <name>Example 2: dynamic high-bandwidth transport</name>
        <t>
          The dynamic high-bandwidth transport is an innovative network solution designed to address the challenges
          of large-scale, high-efficiency data migration for scenarios such as scientific computing, AI
          training, and cross-regional data transfers. Typical Use Cases like East-to-West Data Storage: Low-cost
          cold/backup data transfers to western data centers. Scientific Computing: Supports projects like the LHAASO
          cosmic ray observatory (11PB/year data) with high-speed links to supercomputing centers. AI/Media
          Production: Accelerates raw footage (e.g., 2TB/day) or AI model training data transfers.
        </t>
        <t>
          The network architecture of thedynamic high-bandwidth transport line service comprises three layers: the
          service enabling layer, the service core layer, and the business carrying layer. It can provide
          services for various data transmission businesses such as gene sequencing, scientific computing,
          cloud-to-cloud storage, film and television production, artificial intelligence, and more. The service
          enabling layer, through user-oriented unified APIs, SDKs, or service platforms, invokes network
          capabilities and allocates network resources on demand based on the business requirements transmitted
          by various applications, generating a combination of network capabilities and business capabilities.
          The service provides users with network capabilities such as elastic bandwidth, security
          isolation, flexible networking, deterministic resource assurance, and flexible billing based on usage,
          according to the business requests transmitted by the service enabling layer. The business carrying layer,
          as the physical carrier providing data transportation, builds on-demand, deterministic, secure, and
          reliable network channels between communicating parties, including network functional entities such as
          access terminals, super business gateways, and routers. The specific network architecture is shown
          in Figure 2.
        </t>
        <figure>
          <name>The framework of dynamic high-bandwidth transport</name>
        <artwork align="center"><![CDATA[
                        +---------------------+
                        |     Applications    |
                        +---------------------+
                                  ^
                                  |
                     API/service-oriented interfaces
                                  |
                                  v
            +--------------------------------------------+
            |  service enabling layer                    |
            |   +---------------------+   +----------+   |
            |   | resources on demand |   | security |   |
            |   +---------------------+   +----------+   |
            +--------------------------------------------+
                                  ^
                                  |
     combination of network capabilities and business capabilities
                                  |
                                  v
            +--------------------------------------------+
            |  service core layer                       |
            | +-------------------+ +-----------------+  |
            | | elastic bandwidth | |flexible billing |  |
            | +-------------------+ +-----------------+  |
            | +----------------------------------+       |
            | | deterministic resource assurance |       |
            | +----------------------------------+       |
            +--------------------------------------------+
                   |                             ^
                   |                             |
           control signal        business information collection
                   |                             |
                   v                             |
      +--------------------------------------------------------+
      |  business carrying layer                               |
      |  +---------------------+ +---------------------------+ |
      |  | data transportation | | reliable network channels | |
      |  +---------------------+ +---------------------------+ |
      |  +-------------------------+                           |
      |  | super business gateways |                           |
      |  +-------------------------+                           |
      +--------------------------------------------------------+
	   ]]></artwork>
        </figure>
        <t>
          Overall, dynamic high-bandwidth transport can significantly reducing costs and improving efficiency compared
          to traditional methods like physical hard disk shipping or fixed-bandwidth dedicated lines. Here's an
          overview of its key aspects:
        </t>
        <t>
          1. Task-Based On-Demand Service: Supports instant setup and teardown of connections (1G-100G bandwidth)
          for temporary or scheduled data transfers (e.g., nighttime off-peak usage).
        </t>
        <t>
          2. Elastic Bandwidth: Allows dynamic adjustment of bandwidth (e.g., from 100M to 10G) to meet burst
          demands while maintaining cost efficiency.
        </t>
        <t>
          3.High-Bandwidth and Low-Latency: Optimizes protocols (e.g., TCP/UDP), leverages wide-area RDMA for
          lossless transmission, and uses load balancing (e.g., SRv6 UCMP) to maximize throughput.
        </t>
        <t>
          4. Security and Reliability: Ensures end-to-end isolation via FlexE slicing and VPNs, with built-in
          encryption (IPSec) and route authentication (RPKI).
        </t>
        <t>
          5. Cross-Domain Coordination: Enables multi-domain/operator collaboration through centralized or
          distributed control planes for seamless resource scheduling.
        </t>
      </section>
    </section>

    <section>
      <name>Requirements</name>
        <t>
          To enable seamless cloud-network integration across edge, core, and transport environments,
          cloud-network integration framework establishes a set of functional requirements that drive its
          architecture and interface design. These requirements prioritize:
        </t>
        <t>
          1. To achieve dynamic resource scheduling, the system MUST support real-time elastic scaling of
          computing resources (e.g., GPU containers) and network bandwidth based on AI workload fluctuations.
        </t>
        <t>
          2. Upon detecting GPU node failures or BGP route oscillations, the system SHOULD automatically
          migrate services to back up nodes and activate OTN protection rings within 60 seconds.
        </t>
        <t>
          These requirements emphasize responsiveness, reliability, and compatibility in multi-domain environments
          ensures cloud-native applications (e.g., AI/ML, XR) achieve deterministic performance while
          maintaining operational efficiency in cloud-network fused environments.
        </t>
    </section>
    
    <section anchor="IANA">
    <!-- All drafts are required to have an IANA considerations section. See RFC 8126 for a guide.-->
      <name>IANA Considerations</name>
      <t>TBC</t>
    </section>
    
    <section anchor="Security">
      <!-- All drafts are required to have a security considerations section. See RFC 3552 for a guide. -->
      <name>Security Considerations</name>
      <t>TBC</t>
    </section>
    
    <!-- NOTE: The Acknowledgements and Contributors sections are at the end of this template -->
  </middle>

  <back>
    <references>
      <name>References</name>
      <references>
        <name>Normative References</name>
        
        <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.2119.xml"/>
        <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8174.xml"/>

        <reference anchor="draft-li-unco-framework">
        <front>
          <title>Unified Network and Cloud Orchestration Framework</title>

          <author>
            <organization/>
          </author>

          <date/>
        </front>
      </reference>

        <reference anchor="draft-dunbar-neotec-ac-te-applicability">
        <front>
          <title>Applying Attachmet Circuit and Traffic Engineering YANG Data Model to Edge AI Use Case</title>

          <author>
            <organization/>
          </author>

          <date/>
        </front>
      </reference>
        <!-- The recommended and simplest way to include a well known reference -->
        
      </references>
    </references>
    
    <section anchor="Contributors" numbered="false">
      <!-- [REPLACE/DELETE] a Contributors section is optional -->
      <name>Contributors</name>
      <t>Thanks to all of the contributors.</t>
      <!-- [CHECK] it is optional to add a <contact> record for some or all contributors -->
    </section>
    
 </back>
</rfc>
