Getting Ready for Energy-Efficient Networking                 E. Stephan
Internet-Draft                                                    Orange
Intended status: Informational                                M. Palmero
Expires: 28 July 2025                                Cisco Systems, Inc.
                                                               B. Claise
                                                                   Q. Wu
                                                                  Huawei
                                                         L. M. Contreras
                                                              Telefonica
                                                         24 January 2025


               Use Cases for Energy Efficiency Management
                    draft-stephan-green-use-cases-00

Abstract

   This document groups use cases for Energy efficiency Management of
   network devices.

   Discussion Venues

   Source of this draft and an issue tracker can be found at
   https://github.com/emile22/draft-stephan-green-use-cases

About This Document

   This note is to be removed before publishing as an RFC.

   The latest revision of this draft can be found at
   https://emile22.github.io/draft-stephan-green-use-cases/draft-
   stephan-green-use-cases.html.  Status information for this document
   may be found at https://datatracker.ietf.org/doc/draft-stephan-green-
   use-cases/.

   Discussion of this document takes place on the Getting Ready for
   Energy-Efficient Networking Working Group mailing list
   (mailto:green@ietf.org), which is archived at
   https://mailarchive.ietf.org/arch/browse/green/.  Subscribe at
   https://www.ietf.org/mailman/listinfo/green/.

   Source for this draft and an issue tracker can be found at
   https://github.com/emile22/draft-stephan-green-use-cases.

Status of This Memo

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



Stephan, et al.           Expires 28 July 2025                  [Page 1]

Internet-Draft       Use Cases for Energy Efficiency        January 2025


   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 28 July 2025.

Copyright Notice

   Copyright (c) 2025 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents (https://trustee.ietf.org/
   license-info) in effect on the date of publication of this document.
   Please review these documents carefully, as they describe your rights
   and restrictions with respect to this document.  Code Components
   extracted from this document must include Revised BSD License text as
   described in Section 4.e of the Trust Legal Provisions and are
   provided without warranty as described in the Revised BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   3
   2.  Use Cases . . . . . . . . . . . . . . . . . . . . . . . . . .   3
     2.1.  Incremental Application of the GREEN Framework  . . . . .   3
     2.2.  Selective reduction of energy consumption in network parts
            proportional to traffic levels . . . . . . . . . . . . .   5
     2.3.  Reporting on Lifecycle Management . . . . . . . . . . . .   5
       2.3.1.  Carbon Reporting  . . . . . . . . . . . . . . . . . .   5
       2.3.2.  Energy Mix  . . . . . . . . . . . . . . . . . . . . .   5
     2.4.  Real-time Energy Metering of Virtualised or Cloud-native
            Network Functions  . . . . . . . . . . . . . . . . . . .   6
     2.5.  Indirect Energy Monitoring and control  . . . . . . . . .   6
     2.6.  Consideration of other domains for obtention of end-to-end
            metrics  . . . . . . . . . . . . . . . . . . . . . . . .   7
     2.7.  Dynamic adjustment of network element throughput according
            to traffic levels in wireless transport networks . . . .   7
     2.8.  Video streaming use case  . . . . . . . . . . . . . . . .   8
     2.9.  WLAN Network Energy Saving  . . . . . . . . . . . . . . .   9
     2.10. Fixed Network Energy Saving . . . . . . . . . . . . . . .  10
     2.11. Energy Efficiency Network Management  . . . . . . . . . .  11
   3.  Security Considerations . . . . . . . . . . . . . . . . . . .  11



Stephan, et al.           Expires 28 July 2025                  [Page 2]

Internet-Draft       Use Cases for Energy Efficiency        January 2025


   4.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  11
   5.  Acknowledgments . . . . . . . . . . . . . . . . . . . . . . .  12
   6.  Use Cases Living List . . . . . . . . . . . . . . . . . . . .  12
   7.  References  . . . . . . . . . . . . . . . . . . . . . . . . .  12
     7.1.  Normative References  . . . . . . . . . . . . . . . . . .  12
     7.2.  Informative References  . . . . . . . . . . . . . . . . .  12
   8.  Appendix  . . . . . . . . . . . . . . . . . . . . . . . . . .  13
     8.1.  Framework Discussed During the BoF  . . . . . . . . . . .  13
   9.  Informative References  . . . . . . . . . . . . . . . . . . .  15
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  16

1.  Introduction

   This document groups use cases collected from operators and from
   discussions since the GREEN WG preparations.

   It provides a set of use cases for Energy efficiency Management of
   network devices.  The scope is devices like switches, routers,
   servers and storage devices having an IP address providing a
   management interface.  It includes their built-in components that
   receive and provide electrical energy.

   In annex we recall the framework where the use cases can be put in
   situation.

2.  Use Cases

   This section describes a number of relevant use cases with the
   purpose of elicit requirements for Energy Efficiency Management.
   This is a work in progress and additional use cases will be
   documented in next versions of this document.  Use cases which are
   not tied enough to the current GREEN chater will be moved to the
   GREEN WG wiki pages or to other WGs or RGs.

2.1.  Incremental Application of the GREEN Framework

   This section describes an incremental example [legacy-path] of usage
   showing how a product, a service and a network can use the framework
   in different settings.

   This use case is the less trendy of all the use cases by far as its
   ambitious is limited to migration and coexistence, as usual.
   Nevertheless from a telco perspective, it is the centrality for 2
   main reasons:

   *  to start immediatly the move to energy efficiency using legacy
      devices;




Stephan, et al.           Expires 28 July 2025                  [Page 3]

Internet-Draft       Use Cases for Energy Efficiency        January 2025


   *  to account the gain of the move one started;

   Once upon a time there was an very old legacy router named Rusty
   equipped with outdated ethernet and ugly optical interfaces.  Despite
   his worn-out appearance, Rusty was determined to contribute to the
   energy efficiency effort.  He dreamed of finding a way to optimize
   his old circuits and help reduce the power consumption of the network
   he had faithfully served for so many years.  Though he was no longer
   in his prime, Rusty believed that even an old router like him could
   make a difference in a world striving for sustainability and help
   reduce the carbon footprint.  He is convince that he still had a part
   to play in making the digital world a greener place.

   Device moving gradually to GREEN energy efficiency support:

   *  step 1 "baseline" : establishing a reference point of typical
      energy usage, which is crucial for identifying inefficiencies and
      measuring improvements over time.  At this step the controler use
      only the (c) part of the framework.  It is collected from the
      datasheet.

   By establishing a baseline and using benchmarking, you can determine
   if your networking equipment is performing normally or if it is "off"
   from expected performance, guiding you in making necessary
   improvements.

   The initial measurement of your networking equipment's energy
   efficiency and performance, aka Baselining, needs to be in
   coordination with the vendor specifications and industry standards to
   understand what is considered normal or optimal performance. example:
   Baseline: Your switches operate at 5 Gbps per watt.  Benchmarking:
   Vendor specification is 8 Gbps per watt; industry standard is 10 Gbps
   per watt.  Action: Implement energy-saving measures and upgrades.
   Tracking: Measure again to see if efficiency improves towards 8-10
   Gbps per watt.

   *  step 2 "component": part of the device hw or sw migrated to
      support GREEN framework elements.

   *  step 3 "device controleur"

   *  step 4 "network level"

   (i) Avoid a power-on/power-off frequency to break component parts
   (aka laser, power parts, wire connectors ...)

   (ii) the gain must be measurable




Stephan, et al.           Expires 28 July 2025                  [Page 4]

Internet-Draft       Use Cases for Energy Efficiency        January 2025


   (iii) network-wide energy efficiency solutions must include legacy
   devices and green-wg ready devices

2.2.  Selective reduction of energy consumption in network parts
      proportional to traffic levels

   Traffic levels in a network follow patterns reflecting the behavior
   of consumers.  Those patterns show periodicity in the terms of the
   traffic delivered, that can range from daily (from 00:00 to 23:59) to
   seasonal (e.g., winter to summer), showing peaks and valleys that
   could be exploited to reduce the consumption of energy in the network
   proportionally, in case the underlying network elements incorporate
   such capabilities.  The reduction of energy consumption could be
   performed by leveraging on sleep modes in components up to more
   extreme actions such as switching off network components or modules.
   Such decisions are expected to no impact on the service delivered to
   customers, and could be accompanied by traffic relocation and / or
   concentration in the network.

2.3.  Reporting on Lifecycle Management

   Lifecycle information related to manufacturing energy costs,
   transport, recyclability, and end-of-life disposal impacts is part of
   what is called "embedded carbon."  This information is considered to
   be an estimated value, which might not be implemented today in the
   network devices.  It might be part of the vendor information, and to
   be collected from datasheets or databases.  In accordance with ISO
   14040/44, this information should be considered as part of the
   sustainable strategy related to energy efficiency.  Also, refer to
   the ecodesign framework [(EU) 2024/1781] published in June by the
   European Commission.

2.3.1.  Carbon Reporting

   To report on carbon equivalents for global reporting, it is important
   to correlate the location where the specific entity/network element
   is operating with the corresponding carbon factor.  Refer to the
   world emission factor from the International Energy Agency (IEA),
   electricity maps applications that reflect the carbon intensity of
   the electricity consumed, etc.

2.3.2.  Energy Mix

   Energy efficiency is not limited to reducing the energy consumption,
   it is common to include carbon free, solar energy, wind energy,
   cogeneration in the efficiency.





Stephan, et al.           Expires 28 July 2025                  [Page 5]

Internet-Draft       Use Cases for Energy Efficiency        January 2025


   The type of the sources of energy of the power is one criteria of
   efficiency.

   There are other dimensions that must visible: As many telecom
   locations include battery or additionnally several backups levels (as
   example battery, standby generator ...) there is a requirement to
   known exactly when a backup power is in used and which one is.

2.4.  Real-time Energy Metering of Virtualised or Cloud-native Network
      Functions

   Facilitating more precise and real-time estimations of energy
   consumed by virtualised or cloud-native network functions.

   Effective metering of virtualized network infrastructure is critical
   for the efficient management and operation of next-generation mobile
   networks [GREEN_NGNM].

2.5.  Indirect Energy Monitoring and control

   There are cases where Energy Management for some devices need to
   report on other entities.  There are two major reasons for this.

   o For monitoring energy consumption of a particular entity, it is not
   always sufficient to communicate only with that entity.  When the
   entity has no instrumentation for determining power, it might still
   be possible to obtain power values for the entity via communication
   with other entities in its power distribution tree.  A simple example
   of this would be the retrieval of power values from a power meter at
   the power line into the entity.  A Power Distribution Unit (PDU) and
   a Power over Ethernet (PoE) switch are common examples.  Both supply
   power to other entities at sockets or ports, respectively, and are
   often instrumented to measure power per socket or port.  Also it
   could be considered to obtain power values for the entity via
   communication with other entities outside of the power distribution
   tree, like for example external databases or even data sheets.

   o Similar considerations apply to controlling the power supply of an
   entity that often needs direct or indirect communications with
   another entity upstream in the power distribution tree.  Again, a PDU
   and a PoE switch are common examples, if they have the capability to
   switch power on or off at their sockets or ports, respectively.









Stephan, et al.           Expires 28 July 2025                  [Page 6]

Internet-Draft       Use Cases for Energy Efficiency        January 2025


2.6.  Consideration of other domains for obtention of end-to-end metrics

   The technologies under the scope of IETF provide the necessary
   connectivity to other technological domains.  For the obtention of
   metrics end-to-end it would be required to combine or compose the
   metrics per each of those domains.

   An exemplary case is the one of a network slice service.  The concept
   of network slice was initially defined by 3GPP [TS23.501], and it has
   been further extended to the concerns of IETF [RFC9543].

   In regards energy efficiency, 3GPP defines a number of energy-related
   key performance indicators (KPI) in [TS28.554], specifically Energy
   Efficiency (EE) and Energy Consumption (EC) KPIs.  There are KPIs
   particular for a slice supporting a specific kind of service (e.g.,
   Mobile Broadband or MBB), or generic ones, like Generic Network Slice
   EE or Network Slice EC.  Assuming these as the KPIs of interest, the
   motivation of this use case is the obtention of the equivalent KPIs
   at IETF level, that is, for the network slice service as defined in
   [RFC9543].

   Note that according to [TS28.554], the Generic Network Slice EE is
   the performance of the network slice divided by the Network Slice EC.
   Same approach can be followed at IETF level.  Note that for avoiding
   double counting the energy at IETF level in the calculation of the
   end-to-end metric, the 3GPP metric should only consider the
   efficiency and consumption of the 3GPP-related technologies.

2.7.  Dynamic adjustment of network element throughput according to
      traffic levels in wireless transport networks

   Radio base stations are typically connected to the backbone network
   by means of fiber or wireless transport (e.g., microwave)
   technologies.  In the specific case of wireless transport, automation
   frameworks have been defined [ONF-MW][RFC8432][mWT025] for their
   control and management.















Stephan, et al.           Expires 28 July 2025                  [Page 7]

Internet-Draft       Use Cases for Energy Efficiency        January 2025


   One of the parameters subject of automated control is the power of
   the radio links.  The relevance of that capability is that the power
   can be adjusted accordingly to the traffic observed.  Wireless
   transport networks are typically planned to support the maximum
   traffic capacity in their area of aggregation, that is, the traffic
   peak.  With that input, the number of radio links in the network
   element and the corresponding power per radio link (for supporting a
   given modulation and link length in the worst weather conditions) are
   configured.  This is done to avoid any kind of traffic loss in the
   worst operational situation.  However, such operational needs are
   sporadic, giving room for optimization during normal operational
   circumstances and/or low traffic periods.

   Power-related parameters are for instance defined in [RFC8561].
   Those power parameters can be dynamically configured to adjust the
   power to the observed traffic levels with some coarse granularity,
   but pursuing certain degrees of proportionality.

2.8.  Video streaming use case

   Video streaming is nowadays the major source of traffic observed in
   ISP networks, in a propotion of 70% or even higher.  Over-the-top
   distribution of streaming traffic is typically done by delivering a
   unicast flow per end user for the content of its interest.In
   consequence, during the hours of higher demand, the total traffic in
   the network is proportional to the concurrence of users consuming the
   video streaming service.  The amount of traffic is also dependent of
   the resolution of the encoded video (the higher the resolution, the
   higher the bit rate per video flow), which tends to be higher as long
   as the users devices support such higher resolutions.

   The consequence of both the growth in the number of flows to be
   supported simultaneously, and the higher bit rate per flow, is that
   the nework elements in the path between the source of the video and
   the user have to be dimensioned accordingly.  This implies the
   continuous upgrade of those network elements in terms of capacity,
   with the need of deploying high-capacity network elements and
   components.  Apart from the fact that this process is shortening the
   lifetime of network elements, the need of high capacity interfaces
   also increase the energy consumption (despite the effort of
   manufacturers in creating more efficient network element platforms).
   Note that nowadays there is no actual possibility of activating
   energy consumption proportionality (in regards the delivered traffic)
   to such network elements.

   As a mean of slowing down this cycle of continuos renewal, and reduce
   the need og higher bit rate interfaces / line cards, it seems
   convenient to explore mechanisms that could reduce the volume of



Stephan, et al.           Expires 28 July 2025                  [Page 8]

Internet-Draft       Use Cases for Energy Efficiency        January 2025


   traffic without impacting the user service expectations.  Variants of
   multicast or different service delivery strategies can help to
   improve the energy efficiency associated to the video streaming
   service.  It should be noted that another front for optimization is
   the one related to the deployment of cache servers in the network.

2.9.  WLAN Network Energy Saving

   In a WLAN network, The AP is usually powered by a PoE switch.  AP
   nodes are network devices with the largest number and consuming most
   of energy.  Therefore, the working status of the AP is the core of
   the energy saving solution.

   The working status of the AP can be break down into 3 modes as
   follows: PoE power-off mode: In this mode, the PoE switch shuts down
   the port and stops supplying power to the AP.  The AP does not
   consume power at all.  When the AP wakes up, the port provides power
   again.  In this mode, it usually takes a few minutes for the AP to
   recover.  Hibernation mode: Only low power consumption is used to
   protect key hardware such as the CPU, and other components are shut
   down.  Low power consumption mode: Compared with the hibernation
   mode, the low power consumption mode maintains a certain
   communication capability.  For example, the AP retains only the 2.4
   GHz band and disables other radio bands.

   In energy saving deployment, after the surrounding energy saving APs
   are shut down, the Working AP automatically adjusts their transmit
   power to increase the coverage of the entire area at specific energy
   saving period.  In such case, energy saving APs can freely choose to
   switch to any mode we described above.

      /---\
     |     +-----+
     | AP  |     |
      \---/      |      +------------+
                 |      |            |
                 |------+     PoE    |
      /---\      |      |   Switch   |
     |     |     |      +------------+
     | AP  +-----+
      \---/

                        Figure 1: PoE Power Off Mode








Stephan, et al.           Expires 28 July 2025                  [Page 9]

Internet-Draft       Use Cases for Energy Efficiency        January 2025


                    4                         4
    +----------+   \|/        +----------+   \|/
    |          |    |         |          |    |
    |   +----+ |    |         |   +----+ |    |
    |   |5GHz+-+----+         |   |5GHz+-+-X--+
    |   | RF | |    2         |   | RF | |    2
    |   +----+ |   \|/    \   |   +----+ |   \|/
    |   +----+ |    |   ---\  |   +----+ |    |
    |  2.4GHz| |    |       \ |  2.4GHz| |    |
    |   | RF +-+----+       / |   | RF +-+-X--+
    |   +----+ |    2   ---/  |   +----+ |    2
    |   +----+ |   \|/    /   |   +----+ |   \|/
    |  2.4GHz| |    |         |  2.4GHz| |    |
    |   | RF |-+----+         |   | RF +-+----+
    |   +----+ |              |   +----+ |
    +----------+              +----------+

                    Figure 2: Low Power Consumption Mode

        +--+  +--+    +--+
        |AP|--|AP|--- |AP|      ------------------------------
        +--+  +--+   \+--+      Grouping  Recommended
        /               \        Area     Energy Saving Period
     +--+     +--+      +--+    ------------------------------
     |AP|     |AP|      |AP|    XED01-1  01:00:00,06:30:00
     +--+     +--+      +--+
       |                 |      ------------------------------
        +--+          +--+
        |AP|  +--+   /|AP|      XED01-2  01:30:00,06:30:00
        +--+--|AP|--- +--+     --------------------------------
              +--+

               Figure 3: Wireless Resource Management on APs

2.10.  Fixed Network Energy Saving

   Traffic on the Tidal network has an obvious tidal period, including
   heavy-traffic periods and light-traffic periods: The time duration of
   heavy traffic load and light traffic load are clearly distinguished.
   The switching time between the heavy-traffic period and the light-
   traffic period is quite fixed and cyclic.  In a tidal network, some
   network devices can be shut down or sleep during low-traffic periods
   to save energy.  In the metro or backbone network, the routers
   support various different speed interfaces, e.g., the gigabit level
   to 10GE/50GE, or 100G to 400G.  Routers might choose to adjust speed
   of the interface or downgrade from high speed interface to low speed
   interface based on network traffic load changes to save the energy.
   In addition, the routers can adjust the number of working network



Stephan, et al.           Expires 28 July 2025                 [Page 10]

Internet-Draft       Use Cases for Energy Efficiency        January 2025


   processor cores and clock frequency of chipsets and the number of
   SerDes buses based on network traffic load changes to save the
   energy.

2.11.  Energy Efficiency Network Management

   Network level Energy Efficiency allows network operators not only see
   real time energy consumption in the network devices of large scale
   network, but also allow you see o which network devices enable energy
   saving, which devices not,which are legacy ones, o The total energy
   consumption changing trend over the time of the day, for all network
   devices, o Energy efficiency changing trend over the time of the day
   for the whole network.  With the better observability to energy
   consumption statistics data and energy efficiency statistics data,
   the network operators can know which part of the network need to be
   adjusted or optimized based on network status change.

3.  Security Considerations

   Resiliency is an implicit use case of energy efficiency management
   which comes with numerous security considerations :

   Controlling Power State and power supply of entities are considered
   highly sensitive actions, since they can significantly affect the
   operation of directly and indirectly connected devices.  Therefore,
   all control actions must be sufficiently protected through
   authentication, authorization, and integrity protection mechanisms.

   Entities that are not sufficiently secure to operate directly on the
   public Internet do exist and can be a significant cause of risk, for
   example, if the remote control functions can be exercised on those
   devices from anywhere on the Internet.

   The monitoring of energy-related quantities of an entity as addressed
   can be used to derive more information than just the received and
   provided energy; therefore, monitored data requires protection.  This
   protection includes authentication and authorization of entities
   requesting access to monitored data as well as confidentiality
   protection during transmission of monitored data.  Privacy of stored
   data in an entity must be taken into account.  Monitored data may be
   used as input to control, accounting, and other actions, so integrity
   of transmitted information and authentication of the origin may be
   needed.

4.  IANA Considerations

   This document has no IANA actions.




Stephan, et al.           Expires 28 July 2025                 [Page 11]

Internet-Draft       Use Cases for Energy Efficiency        January 2025


5.  Acknowledgments

   The contribution of Luis M.  Contreras to this document has been
   supported by the Smart Networks and Services Joint Undertaking (SNS
   JU) under the European Union's Horizon Europe research and innovation
   projects 6Green (Grant Agreement no. 101096925) and Exigence (Grant
   Agreement no. 101139120).

6.  Use Cases Living List

   Consider 5g vs network slicing: 3GPP spec describing energy
   efficiency KPIs. 3GPP TS 28.554.
   Reference:https://datatracker.ietf.org/doc/rfc9543/ Connectivity from
   radio side (trying to control the traffic/related work to CCAMP)
   Marisol to add one use case: drift from data specifications...
   (somehow link to the above) Energy Metric in E2E view

7.  References

7.1.  Normative References

   [IEC.61850-7-4] International Electrotechnical Commission,
   "Communication networks and systems for power utility automation --
   Part 7-4: Basic communication structure -- Compatible logical node
   classes and data object classes", March 2010.

   [IEC.62053-21] International Electrotechnical Commission,
   "Electricity metering equipment (a.c.) -- Particular requirements --
   Part 21: Static meters for active energy (classes 1 and 2)", January
   2003.

   [IEC.62053-22] International Electrotechnical Commission,
   "Electricity metering equipment (a.c.) -- Particular requirements --
   Part 22: Static meters for active energy (classes 0,2 S and 0,5 S)",
   January 2003.

   [ATIS-0600015.03.2013] ATIS, "ATIS-0600015.03.2013: Energy Efficiency
   for Telecommunication Equipment: Methodology for Measurement and
   Reporting for Router and Ethernet Switch Products", 2013.

7.2.  Informative References

   [IEC.60050] International Electrotechnical Commission, "Electropedia:
   The World's Online Electrotechnical Vocabulary", 2013,
   http://www.electropedia.org/iev/iev.nsf/welcome?openform
   (http://www.electropedia.org/iev/iev.nsf/welcome?openform).





Stephan, et al.           Expires 28 July 2025                 [Page 12]

Internet-Draft       Use Cases for Energy Efficiency        January 2025


8.  Appendix

   This appendix should be removed when the initial set of GREEN WG
   documents will be stable

8.1.  Framework Discussed During the BoF

   The framework is maintainded in this version of the draft.  It will
   be removed when the use cases descriptions will be mature.

   Discovery functions involve identifying energy-managed networks,
   devices, and their components, as well as discovering the inventory
   of power components capabilities, optimization control capabilities,
   and nominal condition use.  Monitoring functions encompass tracking
   power states, power attributes, energy consumption, network
   performance, and energy efficiency metrics.  Control functions
   include managing energy-saving and optimization functions and the
   power states of energy-managed devices and their components.

   The overall framework is shown in Figure 4.































Stephan, et al.           Expires 28 July 2025                 [Page 13]

Internet-Draft       Use Cases for Energy Efficiency        January 2025


         What needs to be standardized for Framework


  (3) Network Domain Level :

  (a)              (b)              (c)
  Inventory        Monitor       +- DataSheets/DataBase and/or via API
  Of identity      Energy        |  Metadata and other device/component
  and Capability   Efficiency    |  /network related information:
       ^               ^         |
       |               |         |  .Power/Energy related metrics
       |               |         |  .information
       |               |         |  .origin of Energy Mix
       |               |         |  .carbon aware based on location
       |               |         |
       |               |         |
       |               |         |
       |               |         v
  +--------------------------------------------------------------------+
  |                   *                                                |
  |     (2) controller   (collection, compute and aggregate?)          |
  |                                                                    |
  +--------------------------------------------------------------------+
               ^              ^                   ^ |
    (d)        |  (e)         |  (f)              | |(g)
    Inventory  |  Monitor     |  GREEN WG:        | |GREEN WG: Control
    Capability |  Traffic     |  Monitor power    | |(Energy saving
               |  & power     |  Proportion,      | |Functionality
               |  consumption |  Energy efficiency| |Localized mgmt/
               |              |  ratio, etc)      | |network wide mgmt)
               |              |                   | |
               |              |                   | |
               |              |                   | v
  +--------------------------------------------------------------------+
  |                                            *                       |
  |                  (1) Device/Component Level                        |
  |                                                                    |
  | +---------+  +-----------+  +----------------+  +----------------+ |
  | | (I)     |  | (II)      |  | (III)          |  | (IV)           | |
  | | Network |  | Device    |  | Legacy Network |  | 'Attached'(PoE | |
  | | Device  |  | Component |  | Device         |  | kind) Device   | |
  | |         |  |           |  |                |  |                | |
  | +---------+  +-----------+  +----------------+  +----------------+ |
  +--------------------------------------------------------------------+

  (*) Energy Efficiency Management Function is implemented inside the
  device or in a controller




Stephan, et al.           Expires 28 July 2025                 [Page 14]

Internet-Draft       Use Cases for Energy Efficiency        January 2025


               Figure 4: Framework discussed during the BoF

   The main elements in the framework are as follows:

   (a),(d) Discovery and Inventory

   (b),(c) GREEN Metrics

   (b),(f) Monitor energy efficiency

   (e) Monitor power consumption and traffic (IPPM WG throughput,
   traffic load, etc)

   (g) Control Energy Saving

9.  Informative References

   [GREEN_NGNM]
              "NGMN Alliance, GREEN FUTURE NETWORKS: METERING IN
              VIRTUALISED RAN INFRASTRUCTURE", n.d.,
              <https://www.ngmn.org/publications/metering-in-
              virtualised-ran-infrastructure.html>.

   [legacy-path]
              "Requirements for Energy Efficiency Management", 21 July
              2024, <https://datatracker.ietf.org/doc/draft-stephan-
              legacy-path-eco-design>.

   [mWT025]   "ETSI GR mWT 025, Wireless Backhaul Network and Services
              Automation: SDN SBI YANG models, V1.1.1.", 31 March 2021.

   [ONF-MW]   "ONF TR-532, Microwave Information Model, version 2.0.",
              31 January 2024.

   [RFC8432]  Ahlberg, J., Ed., Ye, M., Ed., Li, X., Contreras, LM., and
              CJ. Bernardos, "A Framework for Management and Control of
              Microwave and Millimeter Wave Interface Parameters",
              RFC 8432, DOI 10.17487/RFC8432, October 2018,
              <https://www.rfc-editor.org/rfc/rfc8432>.

   [RFC8561]  Ahlberg, J., Ye, M., Li, X., Spreafico, D., and M.
              Vaupotic, "A YANG Data Model for Microwave Radio Link",
              RFC 8561, DOI 10.17487/RFC8561, June 2019,
              <https://www.rfc-editor.org/rfc/rfc8561>.







Stephan, et al.           Expires 28 July 2025                 [Page 15]

Internet-Draft       Use Cases for Energy Efficiency        January 2025


   [RFC9543]  Farrel, A., Ed., Drake, J., Ed., Rokui, R., Homma, S.,
              Makhijani, K., Contreras, L., and J. Tantsura, "A
              Framework for Network Slices in Networks Built from IETF
              Technologies", RFC 9543, DOI 10.17487/RFC9543, March 2024,
              <https://www.rfc-editor.org/rfc/rfc9543>.

   [TS23.501] "3GPP TS 23.501, System architecture for the 5G System
              (5GS), 17.6.0.", 22 September 2022.

   [TS28.554] "3GPP TS 28.554, Management and orchestration; 5G end to
              end Key Performance Indicators (KPI), 17.15.0.", 25
              September 2024.

Authors' Addresses

   Emile Stephan
   Orange
   Email: emile.stephan@orange.com


   Marisol Palmero
   Cisco Systems, Inc.
   Email: mpalmero@cisco.com


   Benoit Claise
   Huawei
   Email: benoit.claise@huawei.com


   Qin Wu
   Huawei
   Email: bill.wu@huawei.com


   Luis M. Contreras
   Telefonica
   Email: luismiguel.contrerasmurillo@telefonica.com













Stephan, et al.           Expires 28 July 2025                 [Page 16]