<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE rfc SYSTEM "rfc2629-xhtml.ent">
<?rfc toc="yes"?>
<?rfc tocompact="yes"?>
<?rfc tocdepth="3"?>
<?rfc tocindent="yes"?>
<?rfc symrefs="yes"?>
<?rfc sortrefs="yes"?>
<?rfc comments="yes"?>
<?rfc inline="yes"?>
<?rfc compact="yes"?>
<?rfc subcompact="no"?>

<rfc xmlns:xi="http://www.w3.org/2001/XInclude" category="std" ipr="trust200902" submissionType="IETF" docName="draft-chen-green-ran-transport-coord-energy-saving-00">

  <front>
      <title abbrev="coordinated-energy-saving-between-ran-and-transport-network">
Coordinated Energy Saving between RAN and Transport Network
      </title>

    <!-- AUTHORS -->
    <author fullname="Xinyu Chen"
            initials="X."
            surname="Chen">
      <organization abbrev="CMCC">
        China Mobile
      </organization>
      <address>
        <postal>
          <street>No.32 Xuanwumen west street</street>
          <city>Beijing</city>
          <code>100053</code>
          <country>China</country>
        </postal>
        <phone></phone>
        <email>chenxinyuyjy@chinamobile.com</email>
        <uri></uri>
      </address>
    </author>
	
    <author fullname="Jin Zhou"
            initials="J."
            surname="Zhou">
      <organization abbrev="ZTE">
        ZTE Corporation
      </organization>
      <address>
        <email>zhou.jin6@zte.com.cn</email>
        <uri></uri>
      </address>
    </author>

    <area>Operations and Management</area>

    <workgroup>GREEN</workgroup>

    <!--abstract-->
    <abstract>
      <t>
	  This document provides an coordinated energy saving mechanism between RAN and transport network. 
      </t>
    </abstract>

  </front>

  <middle>

    <!--1 introduction-->
    <section anchor="sec:introduction" title="Introduction">
		<t>
           This document addresses the usecases of RAN and transport network identified in 
		   <xref target="I-D.ietf-green-use-cases"/> through an coordinated energy saving mechanism.
        </t>	
		<t>
           As described in Section 2.7 of <xref target="I-D.ietf-green-use-cases"/>, radio base stations are typically 
		   connected to the backbone network by means of fiber technologies. The capability of radio link can be adjusted
		   accordingly to the traffic observed. Some of the power-related parameters are dynamically configured to adjust 
		   the power to the observed traffic levels with some coarse granularity to avoid the underutilized of energy.
           In addition, as described in <xref target="I-D.chen-green-transport-energy-saving"/> describes the energy saving 
		   in transport network.
        </t>
		<t>
           However, under current energy-saving methods, energy saving of RAN and TN are done separately 
		   and without coordination. This leads to RAN adjusting its wireless link according to its own traffic conditions, 
		   but the transport network is unaware of this and still reserves resources based on the maximum traffic, 
		   especially the internal forwarding resources, optical module resources, and TDM slot resources, resulting 
		   in resource waste.
        </t>
		<t>
		   Therefore, it is necessary to study an energy-saving coordination mechanism between the RAN and the transport 
		network.
		</t>
		
	
    </section>
	<!--end of introduction-->
    
    <!--2 coordination-->
    <section anchor="sec:coordination" title="Coordination">
	<t>
        This section describes the detailed coordination mechanisms that may exist between the Radio Access Network (RAN) and 
		the Transport Network (TN).
	</t>
<figure anchor="fig-arch" align="center">
      <name>Energy Saving Coordination between RAN and Transport Network</name>
      <artwork type="ascii-art" align="center"><![CDATA[
	  
+--------------------------------------------------------------------------------+
|                                                                                |
|                       +------------------+                                     |
|                       |  RAN Controller  <----------------------------------------------------+
|                       +--------+---------+                                     |              |
|                                |                                               |              |
|      +------------+------------+------------+------------+------------+        |              |
|      |            |            |            |            |            |        |              | 
|  +---+---+    +---+---+    +---+---+    +---+---+    +---+---+    +---+---+    |              |
|  | RAN1  |    | RAN2  |    | RAN3  |    |  RAN4 |    |  RAN5 |    |  RAN6 |    |              |
|  +---^---+    +---^---+    +---^---+    +---^---+    +---^---+    +---^---+    |              |
|      |            |            |            |            |            |        |              | 
|      |            |            |            |            |            |        |              |   
+------+------------+------------+------------+------------+------------+--------+              |
       |            |            |            |            |            |                       |
+--------------------------------------------------------------------------------+              |
|      |            |            |            |            |            |        |              |
|      |       +----v----+       |            |       +----v----+       |        |              |
|      +-------> Access  <-------+            +-------> Access  <-------+        |              |
|              | Node 1  |                            | Node 2  |                |              |
|              +----+----+                            +----+----+                |              |
|                   |                                      |                     |              |
|                   |                                      |                     |              |
|                   +-----------------+--------------------+                     |              |
|                   |                 |                    |                     |              |
|                   |        +--------+-------+            |                     |              |
|                   |        |   Aggregation  |            |                     |              |
|                   |        |       Node     |            |                     |              |
|                   |        +--------+-------+            |                     |              |
|                   |                 |                    |                     |              |
|                   +-----------------+--------------------+                     |              | 
|                                     |                                          |              |
|                          +----------+-------+                                  |              |
|                          |   TN Controller  <-------------------------------------------------+ 
|                          +------------------+                                  |
|                                                                                |
+--------------------------------------------------------------------------------+
        ]]></artwork>
    </figure>
	
	<t>
	As show in Figure 1, the upper part represents the Radio Access Network(RAN), which consists of six RAN access nodes,
	labeled RAN1 through RAN6. These nodes provide radio coverage and user-plane termination for mobile terminals. All six 
	RAN nodes are under the control of a single RAN controller, which is responsible for radio resource management, 
	traffic scheduling, and RAN-side energy-saving decisions.
	</t>
	<t>
	The lower part represents the Transport Network (TN), which provides the connectivity between the RAN nodes and the core 
	network. This part comprises three transport nodes arranged into a two-tier hierarchy, two access nodes, referred to as 
	Access Node 1 and Access Node 2, and one aggregation node. Access Node 1 and Access Node 2 are directly interact with 
	the RAN nodes, while the Aggregation Node provides aggregated streams toward the core network. All transport nodes in 
	the TN are under the control of TN controller (e.g. for path computation and resource allocation), which is responsible 
	for TN side energy-saving decisions such as port sleep, switching board sleep, and TDM timeslot deactivation, etc.
	</t>
	<t>The energy-saving coordination between the RAN and the TN may include:</t>
	   <list style="bullets">
		     <li>
             Energy-related information advertisement: energy consumption prediction, link power status;
			 </li>
			<li>
             Energy-saving intent decomposition or policy: translating an operator-level energy-saving goal into 
			 concrete actions for both the RAN and the TN;
			 </li>
			 <li>
             Action alignment: aligning wake-up latencies and co-sleep windows to avoid one domain sleeping 
			 while the other related resources remains active;
			 </li>
			 <li>
             Traffic/load coordination: jointly migrating services and rerouting backhaul paths before shutting 
			 down a transport link;
			 </li>
		 </list>
	<t>This coordination can be realized through four approaches: </t>
		   <list style="bullets">
		     <li>
                 Controller-to-Controller (C2C) coordination is best suited for policy-level and long-horizon tasks such as 
				 intent decomposition, global state aggregation, and joint energy-budget management, where minutes-to-hours decision 
				 cycles are acceptable. This approach may exist between peer controllers or orchestrators across RAN and TN for 
				 unified energy saving.
			 </li>
			<li>
                 Node-to-Node (N2N) coordination is best suited for data-plane and short-horizon tasks such as real-time action 
				 synchronization, link adaptation, and rapid wake-up upon unexpected traffic bursts, where controller 
				 involvement would introduce latency. 
			 </li>
			 <li>
            	 Hybrid coordination combining both C2C and N2N is also possible.
			 </li>
			
		 </list>
    </section>		
	<!--end of coordination-->
	


    <section anchor="sec:extension" title="Extension">
    <t>
       Depending on the specific coordination approach, different extensions may be required. For C2C coordination, 
	   the interaction typically relies on CPIs and may necessitate extensions to existing YANG data models and intent 
	   objects within the IETF GREEN framework or network management agent coordinations. For N2N coordination, 
	   nodes may leverage existing protocols, such as LLDP, IPv6, or some OAM protocol, without introducing 
	   new protocols.
    </t>
    <t>
       This part requires further study within the GREEN framework and its YANG modules.
    </t>
    </section>
	
  </middle>

  <back>

    <references title="Informative References">
	  <?rfc include='reference.I-D.ietf-green-terminology'?>
	  <?rfc include='reference.I-D.ietf-green-use-cases'?>
	  <?rfc include='reference.I-D.belmq-green-framework'?>
	  <?rfc include='reference.I-D.chen-green-transport-energy-saving'?>
    </references>
	
  </back>

</rfc>
