WO2025199691A1

WO2025199691A1 - Power limited event duration prediction and energy usage modification

Info

Publication number: WO2025199691A1
Application number: PCT/CN2024/083605
Authority: WO
Inventors: Hajer BRAHAM; Borislava GAJIC; Sivaramakrishnan Swaminathan; Srilakshmi SRINIVASARAJU; Shu Qiang SUN
Original assignee: Nokia Shanghai Bell Co Ltd; Nokia Solutions and Networks Oy; Nokia Technologies Oy
Current assignee: Nokia Shanghai Bell Co Ltd; Nokia Solutions and Networks Oy; Nokia Technologies Oy
Priority date: 2024-03-25
Filing date: 2024-03-25
Publication date: 2025-10-02
Anticipated expiration: 2026-09-25

Abstract

Various example embodiments of this disclosure generally relate to the field of communication, and in particular (but not exclusively), apparatuses, methods, and computer readable storage media related to power limited event duration prediction and energy usage modification. For instance, a first apparatus may transmit, to a second apparatus, a request for an energy usage modification (e. g., energy service optimization, such as an energy saving service), based on a power limited event (e. g., power cut or power outage) of a network device. The first apparatus may receive, from the second apparatus, a report of the energy usage modification. The report may indicate at least one of the following: (i) a predicted duration of the power limited event for the network device and an importance level of the power limited event, or (ii) at least one action of the network device to prolong a service duration of at least one backup battery.

Description

POWER LIMITED EVENT DURATION PREDICTION AND ENERGY USAGE MODIFICATION

TECHNICAL FIELD

Various example embodiments described in this disclosure generally relate to the field of communication, and in particular (but not exclusively) , to apparatuses, methods, and a computer readable storage media related to power limited event (e.g., power cut or power outage) duration prediction and energy usage modification (e.g., energy service optimization, such as an energy saving service) .

BACKGROUND

A communication network can be seen as a facility that enables communications between two or more communication devices, or provides communication devices access to a data network. A mobile or wireless communication network is one example of a communication network. A communication device may be provided with a service by an application server.

Such communication networks operate in accordance with standards, such as those promulgated by 3GPP (Third Generation Partnership Project) or ETSI (European Telecommunications Standards Institute) . Examples of such standards include the so-called 5G (5th Generation) standards promulgated by 3GPP.

SUMMARY

Various example embodiments described in this disclosure provide certain advantages, for example in the form of one or more improvements that are either explicitly described herein or otherwise apparent to a person skilled in the relevant art (s) in view of this disclosure. Hence, at least some of these example embodiments aim to provide (or otherwise contribute to) at least part of the aforementioned advantages and improvements.

Some example embodiments of this disclosure provide apparatuses, methods, and a computer readable storage medium related to power limited event (e.g. power cut or power outage) duration prediction and energy usage modification (e.g., energy service optimization, such as an energy saving service) . For example, one or more solutions provided by some example embodiments of this disclosure can predict the backup battery period of service, optimize the energy usage modification (e.g., energy service optimization, such as an energy saving service) , and/or enable (or otherwise facilitate) the optimization of the backup battery lifespan.

Some example embodiments of this disclosure will be described with respect to certain aspects. These aspects are not intended to indicate key or essential features of the various example embodiments of this disclosure, nor are they intended to be used to limit the scope of thereof. Other features, aspects, and elements will be apparent to a person skilled in the art in view of this disclosure. For example, it should be appreciated that further aspects may be provided by the combination of any two or more of the various aspects described below.

In a first aspect, there is provided a first apparatus. The first apparatus may comprise at least one processor and at least one memory storing instructions that, when executed by the at least one processor, cause the first apparatus at least to: transmit, to a second apparatus, a request for an energy usage modification (e.g., energy service optimization, such as an energy saving service) associated with at least one backup battery or uninterruptible power supply (UPS) of a network device based on a power limited event (e.g., power cut or power outage) of the network device; and receive, from the second apparatus, a report of the energy usage modification (e.g., energy service optimization, such as an energy saving service) , wherein the report indicates at least one of the following: (i) a predicted duration of the power limited event (e.g., power cut or power outage) for the network device and an importance level of the power limited event (e.g., power cut or power outage) , or (ii) at least one action of the network device to prolong a service duration of the at least one backup battery.

In a second aspect, there is provided a second apparatus. The second apparatus may comprise at least one processor and at least one memory storing instructions that, when executed by the at least one processor, cause the second apparatus at least to: receive, from a first apparatus, a request for an energy usage modification (e.g., energy service optimization, such as an energy saving service) associated with at least one backup battery or UPS of a network device based on a power limited event (e.g., power cut or power outage) of the network device; based on receiving the request, collect input data for performing the energy usage modification (e.g., energy service optimization, such as an energy saving service) ; derive output data of the energy usage modification (e.g., energy service optimization, such as an energy saving service) based on the collected input data, wherein the output data comprises at least one of the following: (i) a predicted duration of the power limited event (e.g., power cut or power outage) for the network device and an importance level of the power limited event (e.g., power cut or power outage) , or (ii) at least one action of the network device to prolong a service duration of the at least one backup battery; and transmit, to the first apparatus, a report of the energy usage modification (e.g., energy service optimization, such as an energy saving service) comprising the output data.

In a third aspect, there is provided a method. The method may comprise: transmitting, at a first apparatus to a second apparatus, a request for an energy usage modification (e.g., energy service optimization, such as an energy saving service) associated with at least one backup battery or UPS of a network device based on a power limited event (e.g., power cut or power outage) of the network device is cut; and receiving, from the second apparatus, a report of the energy usage modification (e.g., energy service optimization, such as an energy saving service) , wherein the report indicates at least one of: (i) a predicted duration of a power limited event (e.g., power cut or power outage) for the network device and an importance level of the power limited event (e.g., power cut or power outage) , or (ii) at least one action of the network device to prolong a service duration of the at least one backup battery.

In a fourth aspect, there is provided a method. The method may comprise: receiving, at a second apparatus from a first apparatus, a request for an energy usage modification (e.g., energy service optimization, such as an energy saving service) associated with at least one backup battery or UPS of a network device based on a power limited event (e.g., power cut or power outage) of the network device; based on receiving the request, collecting input data for performing the energy usage modification (e.g., energy service optimization, such as an energy saving service) ; deriving output data of the energy usage modification (e.g., energy service optimization, such as an energy saving service) based on the collected input data, wherein the output data comprises at least one of the following: (i) a predicted duration of a power limited event (e.g., power cut or power outage) for the network device and an importance level of the power limited event, or (ii) at least one action of the network device to prolong a service duration of the at least one backup battery; and transmitting, to the first apparatus, a report of the energy usage modification (e.g., energy service optimization, such as an energy saving service) comprising the output data.

In a fifth aspect, there is provided a first apparatus. The first apparatus may comprise: means for transmitting, at the first apparatus to a second apparatus, a request for an energy usage modification (e.g., energy service optimization, such as an energy saving service) associated with at least one backup battery or UPS of a network device based on a power limited event (e.g., power cut or power outage) of the network device; and means for receiving, from the second apparatus, a report of the energy usage modification (e.g., energy service optimization, such as an energy saving service) , wherein the report indicates at least one of the following: (i) a predicted duration of a power limited event (e.g., power cut or power outage) for the network device and an importance level of the power limited event (e.g., power cut or power outage) , or (ii) at least one action of the network device to prolong a service duration of the at least one backup battery.

In a sixth aspect, there is provided a second apparatus. The second apparatus may comprise: means for receiving, at the second apparatus from a first apparatus, a request for an energy usage modification (e.g., energy service optimization, such as an energy saving service) associated with at least one backup battery or UPS of a network device based on a power limited event (e.g., power cut or power outage) of the network device; means for collecting input data for performing the energy usage modification (e.g., energy service optimization, such as an energy saving service) based on receiving the request; means for deriving output data of the energy usage modification (e.g., energy service optimization, such as an energy saving service) based on the collected input data, wherein the output data comprises at least one of the following: (i) a predicted duration of a power limited event (e.g., power cut or power outage) for the network device and an importance level of the power limited event (e.g., power cut or power outage) , or (ii) at least one action of the network device to prolong a service duration of the at least one backup battery; and means for transmitting, to the first apparatus, a report of the energy usage modification (e.g., energy service optimization, such as an energy saving service) comprising the output data.

In a seventh aspect, there is provided a non-transitory computer readable medium comprising program instructions for causing an apparatus to perform at least the method according to the third or fourth aspects.

In an eighth aspect, there is provided a computer program comprising instructions, which, when executed by an apparatus, cause the apparatus at least to: transmit, to a second apparatus, a request for an energy usage modification (e.g., energy service optimization, such as an energy saving service) associated with at least one backup battery or UPS of a network device based on a power limited event (e.g., power cut or power outage) of the network device is cut; and receive, from the second apparatus, a report of the energy usage modification (e.g., energy service optimization, such as an energy saving service) , wherein the report indicates at least one of the following: (i) a predicted duration of a power limited event (e.g., power cut or power outage) for the network device and an importance level of the power limited event (e.g., power cut or power outage) , or (ii) at least one action of the network device to prolong a service duration of the at least one backup battery.

In a ninth aspect, there is provided a computer program comprising instructions, which, when executed by an apparatus, cause the apparatus at least to: receive, from a first apparatus, a request for an energy usage modification (e.g., energy service optimization, such as an energy saving service) associated with at least one backup battery or UPS of a network device based on a power limited event (e.g., power cut or power outage) of the network device; based on receiving the request, collect input data for performing the energy usage modification (e.g., energy service optimization, such as an energy saving service) ; derive output data of the energy usage modification (e.g., energy service optimization, such as an energy saving service) based on the collected input data, wherein the output data comprises at least one of the following: (i) a predicted duration of a power limited event (e.g., power cut or power outage) for the network device and an importance level of the power limited event (e.g., power cut or power outage) , or (ii) at least one action of the network device to prolong a service duration of the at least one backup battery; and transmit, to the first apparatus, a report of the energy usage modification (e.g., energy service optimization, such as an energy saving service) comprising the output data.

In a tenth aspect, there is provided a first apparatus. The first apparatus may comprise transmitting circuitry configured to transmit, to a second apparatus, a request for an energy usage modification (e.g., energy service optimization, such as an energy saving service) associated with at least one backup battery or UPS of a network device based on a power limited event (e.g., power cut or power outage) of the network device; and receiving circuitry configured to receive, from the second apparatus, a report of the energy usage modification (e.g., energy service optimization, such as an energy saving service) , wherein the report indicates at least one of the following: (i) a predicted duration of a power limited event (e.g., power cut or power outage) for the network device and an importance level of the power limited event (e.g., power cut or power outage) , or (ii) at least one action of the network device to prolong a service duration of the at least one backup battery.

In an eleventh aspect, there is provided a second apparatus. The second apparatus may comprise receiving circuitry configured to receive, from a first apparatus, a request for an energy usage modification (e.g., energy service optimization, such as an energy saving service) associated with at least one backup battery or UPS of a network device based on a power limited event (e.g., power cut or power outage) of the network device; collecting circuitry configured to, based on receiving the request, collect input data for performing the energy usage modification (e.g., energy service optimization, such as an energy saving service) ; deriving circuitry configured to derive output data of the energy usage modification (e.g., energy service optimization, such as an energy saving service) based on the collected input data, wherein the output data comprises at least one of the following: (i) a predicted duration of a power limited event (e.g., power cut or power outage) for the network device and an importance level of the power limited event (e.g. power cut or power outage) , or (ii) at least one action of the network device to prolong a service duration of the at least one backup battery; and transmitting circuitry configured to transmit, to the first apparatus, a report of the energy usage modification (e.g., energy service optimization, such as an energy saving service) comprising the output data.

Various other aspects and further example embodiments are also described in the following detailed description and in the claims.

According to some aspects, there is provided the subject matter of the independent claims. Some further aspects are defined in the dependent claims. Examples that do not fall under the scope of the claims are to be interpreted as examples useful for understanding this disclosure.

As previously mentioned, it is to be understood that the summary section is not intended to identify key or essential features of the various example embodiments of this disclosure, nor is it intended to be used to limit the scope thereof. Other features, aspects, and elements of this disclosure will become apparent in view of the following.

BRIEF DESCRIPTION OF THE DRAWINGS

Some example embodiments will now be described, by way of illustrative and non-limiting example only, with reference to the accompanying drawings, in which:

FIG. 1A illustrates an example network environment in which some example embodiments of this disclosure may be implemented;

FIG. 1B illustrates an example gNB and backup batteries related to some example embodiments of this disclosure;

FIG. 2 illustrates an example signaling process of power limited event (e.g., power cut or power outage) duration prediction and energy usage modification (e.g., energy service optimization, such as an energy saving service) in accordance with some example embodiments of this disclosure;

FIG. 3 illustrates another example signaling process of power limited event (e.g., power cut or power outage) duration prediction and energy usage modification (e.g., energy service optimization, such as an energy saving service) in accordance with some example embodiments of this disclosure;

FIG. 4 illustrates an example backup battery assisted energy usage modification (e.g., energy optimization, such as an energy saving) usage in accordance with some example embodiments of this disclosure;

FIG. 5 illustrates an example flowchart of a process of power limited event (e.g., power cut/outage) duration prediction and energy usage modification (e.g., energy service optimization, such as an energy saving service) in accordance with some example embodiments of this disclosure;

FIG. 6 illustrates another example flowchart of a process of power limited event (e.g., power cut or power outage) duration prediction and energy usage modification (e.g., energy service optimization, such as an energy saving service) in accordance with some example embodiments of this disclosure;

FIG. 7 illustrates an example simplified block diagram of a device configured to implement some example embodiments of this disclosure; and

FIG. 8 illustrates an example block diagram of an example computer readable medium in accordance with some example embodiments of this disclosure.

Throughout the drawings, the same or similar reference numerals represent the same or similar element.

DETAILED DESCRIPTION

Various example embodiments of this disclosure will now be further described. It is to be understood that these example embodiments are described only for the purpose of illustration and are intended to aid those skilled in the art to understand and implement various examples of this disclosure, without suggesting any specific limitation as to the scope thereof. Example embodiments described herein may be implemented in various manners other than the ones described below.

The terminology used herein is generally provided the purpose of describing certain example embodiments only and is not intended to be limiting. In the following description and claims, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art (s) to which this disclosure pertains, unless otherwise defined.

References in this disclosure to “one embodiment, ” “an embodiment, ” “an example embodiment, ” “some example embodiments, ” “certain example embodiments, ” “various example embodiments, ” and the like indicate that the referenced embodiment (s) described may include particular feature (s) , structure (s) , or characteristic (s) , but it is not necessary that every embodiment or example embodiment include the particular feature (s) , structure (s) , or characteristic (s) . Moreover, such phrases are not necessarily referring to the same embodiment or example embodiment. Further, when particular feature (s) , structure (s) , or characteristic (s) are described in connection with an embodiment or an example embodiment, it is submitted that it is within the knowledge of one skilled in the art to combine such feature (s) , structure (s) , or characteristic (s) in connection with other embodiments or example embodiments whether or not such combination (s) are explicitly described.

It may be understood that although the terms “first” and “second, ” etc. may be used herein to describe various elements, these elements are not intended to be limited by these terms. These terms are only used to distinguish one element from another. For example, a first element could be termed a second element, and similarly, a second element could be termed a first element, without departing from the scope of the various example embodiments.

The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the various example embodiments of this disclosure. As used herein, the singular forms “a” , “an” and “the” are intended to include the plural forms as well, unless the context indicates otherwise. It will be further understood that the terms “comprises” , “comprising” , “has” , “having” , “includes” and/or “including” , when used herein, specify the presence of stated features, elements, and/or components etc., but do not preclude the presence or addition of one or more other features, elements, components and/or combinations thereof.

As used herein, “at least one of the following: <a list of two or more elements>” and “at least one of <a list of two or more elements>” and similar wording, where the list of two or more elements are joined by “and” or “or” , mean at least any one of the elements, or at least any two or more of the elements, or at least all the elements.

As used herein, the expression “and/or” also includes any and all combinations of the listed terms, including at least any one of the elements, or at least any two or more of the elements, or at least all of the elements.

As used herein, the term “or” refers to a non-exclusive “or” unless otherwise indicated (e.g., use of “or else” or “or in the alternative” ) .

As used herein, unless stated explicitly, performing a respective feature, step, or functionality “in response to A” does not indicate that the respective feature, step, or functionality is performed immediately after “A” occurs as one or more unstated and intervening features, steps, or functionalities may be performed (at least in part) between an occurrence of the respective feature, step, or function and “A” . Analogously, performing a respective feature, step, or functionality “based on A” does not indicate that the respective feature, step, or functionality is performed solely based on “A” as the respective feature, step, or functionality may be further based on one or more unstated features, steps, or functionalities in addition to “A” .

As used herein, the term “circuitry” may refer to one or more or all of the following example embodiments:

(a) hardware-only circuit implementations (such as implementations in only analog and/or digital circuitry) and

(b) combinations of hardware circuits and software, such as (as applicable) :

(i) a combination of analog and/or digital hardware circuit (s) with software/firmware and

(ii) any portions of hardware processor (s) with software (including digital signal processor (s) ) , software, and memory (ies) that work together to cause an apparatus, such as a mobile phone or server, to perform various functions) and

(c) hardware circuit (s) and or processor (s) , such as a microprocessor (s) or a portion of a microprocessor (s) that requires software (e.g., firmware) for operation, but the software may not be present when it is not utilized for operation.

This definition of circuitry applies to all uses of this term herein. As a further example, as used herein, the term circuitry also covers an implementation of merely a hardware circuit or processor (or multiple processors) or portion of a hardware circuit or processor and its (or their) accompanying software and/or firmware. The term circuitry also covers, for example and if applicable to the particular claim element, a baseband integrated circuit or processor integrated circuit for a mobile device or a similar integrated circuit in server, a cellular network device, or other computing or network device.

As used herein, the term “communication network” refers to a network following any suitable communication standards, such as long term evolution (LTE) , LTE-advanced (LTE-A) , wideband code division multiple access (WCDMA) , high-speed packet access (HSPA) , narrow band Internet of things (NB-IoT) and so on. Furthermore, the communications between a terminal device and a network device in the communication network may be performed according to any suitable generation communication protocols, including, but not limited to, the third generation (3G) , the fourth generation (4G) , 4.5G, the fifth generation (5G) , the sixth generation (6G) communication protocols and/or beyond. The various example embodiments of this disclosure may be applied in various communication systems. Given the rapid development in communications, there will of course also be future type communication technologies and systems with which this disclosure may be embodied. It should not be seen as limiting the scope of this disclosure to only the aforementioned communication technologies and systems.

As used herein, the term “network device” refers to a node in a communication network via which a terminal device accesses the network and receives services therefrom. The network device may refer to a base station (BS) or an access point (AP) , for example, a node B (NodeB or NB) , an evolved NodeB (eNodeB or eNB) , a NR NB (also referred to as a gNB) , a remote radio unit (RRU) , a radio header (RH) , a remote radio head (RRH) , a relay, a low power node such as a femto, a pico, and so forth, depending on the applied terminology and technology.

The term “terminal device” refers to any end device that may be configured to perform wireless communication. By way of example embodiment, a terminal device may also be referred to as a communication device, user equipment (UE) , a subscriber station (SS) , a portable subscriber station, a mobile station (MS) , or an access terminal (AT) . The terminal device may include, but not limited to, a mobile phone, a cellular phone, a smart phone, voice over IP (VoIP) phones, wireless local loop phones, a tablet, a wearable terminal device, a personal digital assistant (PDA) , portable computers, desktop computer, image capture terminal devices such as digital cameras, gaming terminal devices, music storage and playback appliances, vehicle-mounted wireless terminal devices, wireless endpoints, mobile stations, laptop-embedded equipment (LEE) , laptop-mounted equipment (LME) , USB dongles, smart devices, wireless customer-premises equipment (CPE) , an Internet of things (loT) device, a watch or other wearable, a head-mounted display (HMD) , a vehicle, a drone, a medical device and applications (e.g., remote surgery) , an industrial device and applications (e.g., a robot and/or other wireless devices operating in an industrial and/or an automated processing chain contexts) , a consumer electronics device, a device operating on commercial, a relay node, an integrated access and backhaul (IAB) node, and/or industrial wireless networks, and the like. As used herein, the terms “terminal device” , “communication device” , “terminal” , “user equipment” and “UE” may be used interchangeably.

As used herein, the terms “resource” , “transmission resource” , “resource block” , “physical resource block” (PRB) , “uplink (UL) resource” or “downlink (DL) resource” may refer to any resource for performing a communication, for example, a communication between a terminal device and a network device, such as a resource in time domain, a resource in frequency domain, a resource in space domain, a resource in code domain, a resource in a combination of more than one domain or any other resource enabling (or otherwise facilitating) a communication, and the like. As used herein, a resource in time domain (such as, a subframe) may be used as an example of a transmission resource for describing some example embodiments of this disclosure. It is noted that various example embodiments of this disclosure are equally applicable to other resources in other domains.

In the context of on-going Release 18, a study on new aspects of energy efficiency (EE) for the fifth generation (5G) Phase 2 are discussed. In this on-going study phase, there is an issue related to radio access network (RAN) energy saving when using backup batteries. The usage of backup battery is triggered when a RAN node {e.g., a generalized node B (gNB) } faces a power outage or power cut (e.g., of the main power supply) , to prolong the service. However, the period of service time supported by backup batteries may not align with demand.

As alluded to above, the period of service time supported by backup batteries may not align with demand. In such case, other actions may be utilized by the management system to prolong the service time. Some requirements are defined. With the requirement energy saving backup battery-1 (REQ-ES_BB-1) , for example, the 3rd generation partnership project (3GPP) management system should be able to monitor the state of charge and discharge of backup batteries of gNBs. Based on this information, it should be able to know the UPS battery capacity at any time. For REQ-ES_BB-2, the 3GPP management system should be able to monitor the state of the main power supply of gNBs.

These requirements are related to the capability of a 3GPP management system to monitor the backup battery charge/discharge level and state. For example, from V18.0.0 TR28.913, Clause 4 of ETSI ES 202 336-11 [18] lists information that can be monitored and controlled via the interface between the battery system and the remote management application: State of Charge (SoC) for each integrated battery system (IBS) .

Further, annex A (respectively annex B) of ETSI ES 202 336-11 [18] provides a list of mandatory (respectively non-mandatory) monitoring/supervision information, amongst which the following two attributes can be extracted: (i) operating mode; (ii) estimated remaining battery autonomy (time) . With regard to the former, an operating mode may represent the working status of backup batteries. The enumerated value of an operating mode could be: charge, discharge, float charge, sleep, and safe. The change of operating mode is a monitored event and can be sent out from the on-site battery system to a remote management application. With regard to the latter, an estimated remaining battery autonomy (time) may include information, which may be consulted from a remote management application, to know the remaining battery autonomy time.

Clause C. 1 of ETSI ES 202 336-11 [18] provides a structure of an XML document, which can be used to control and monitor battery systems from a remote management application. Where (i.e., in which standards development organizations (SDO) ) and when the aforementioned information and data models are to be specified is for further study.

In section 4.9.3, to fulfil the requirement REQ-ES_BB-1 from clause 4.9.1.2, potential solution #1 should be complemented with an information model (Stage 2) specifying the backup battery information (based on ETSI ES 202 336-11 [18] ) that can be monitored for the NG-RAN in the 3GPP management system, and data model (s) (Stage 3) , in YAML and/or in YANG.

Backup batteries may be used to enable (or otherwise facilitate) uninterrupted service in the situation of a power limited event (e.g., power cut or power outage) of RAN power supply for a RAN node (e.g., a gNB) . However, backup batteries have a limited lifespan due to cost and deployment constraints. Such limited lifespan decreases with the use of the batteries. This may lead to challenges in supporting the RAN services for the entire duration of the power limited event (e.g., power cut or power outage) . Indeed, the time supported by backup batteries may not satisfy demand when the RAN site has faced, is facing, and/or is expected to face a power limited event (e.g., power cut or power outage) and thus some actions may be utilized to optimize the backup battery period of service.

To optimize the service duration that the backup battery can support, many factors (which have an impact (e.g., direct impact) on the backup battery power consumption) can be considered. Such factors may, for example, include loads and other optimizations (e.g., RAN energy saving) features. With regard to loads, the number of active UEs and the traffic these UEs are generating may increase/decrease the amount of energy consumed by a gNB. Efficient balancing of load and management of user mobility may save energy for a gNB that has faced, is facing, and/or is expected to face a power limited event (e.g., power cut or power outage) . With regard to other optimization (e.g., RAN energy saving) features, the execution of one or more actions based on use of backup battery power may modify (e.g., optimize, such as save) energy utilization for the gNB that has faced, is facing, and/or is expected to face a power limited event (e.g., power cut or power outage) . A degradation of quality of service (QoS) should also be considered and/or expected when utilizing one or more actions.

It is to be noted that the duration of the power limited event (e.g., power cut or power outage) should also be factored when optimizing the duration of backup battery supporting the service. Unfortunately, such information is not known by the management system. In addition, the duration of the power limited event (e.g., power cut or power outage) may be used as an indicator to define an importance level of the power limited event (e.g., power cut or power outage) and prioritize actions to optimize the backup battery support duration.

Currently, there are no means to classify the importance level of a power limited event (e.g., power cut or power outage) nor predict the power limited event (e.g., power cut or power outage) duration. In addition, based on the power limited event (e.g., power cut or power outage) duration and importance level, there are no means to indicate to a gNB which action (e.g., an optimal or best action) to take to prolong the service period supported by the backup battery and for how long the backup battery support period is extended.

Therefore, some example embodiments of this disclosure relate to adding more requirements for optimizing the backup battery usage during a power limited event (e.g., power cut or power outage) . Some example embodiments of this disclosure propose solution (s) that enable (or otherwise facilitate) optimization of the backup battery lifespan, such that the duration of the support for RAN service is optimized (e.g., maximized) . In some example embodiments, a backup battery energy saving (BB-ES) management service (MnS) is introduced. The backup battery energy saving (BB-ES) MnS consumer (e.g., a gNB) that has faced, is facing, and/or is expected to face a power limited event (e.g., power cut or power outage) (or network operator’s management system) may be enabled (or otherwise facilitated) to request analytics and prediction of the power limited event (e.g., power cut or power outage) period, an estimation of the importance level of the power limited event (e.g., power cut or power outage) , and/or analytics on prolonging backup battery support duration.

According to some example embodiments of this disclosure, a first apparatus may transmit, to a second apparatus, a request for an energy usage modification (e.g., energy service optimization, such as an energy saving service) associated with at least one backup battery or UPS of a network device based on a power limited event (e.g., power cut or power outage) of the network device. The first apparatus may receive, from the second apparatus, a report of the energy usage modification (e.g., energy service optimization, such as an energy saving service) . The report indicates at least one of the following: (i) a predicted duration of a power limited event (e.g., power cut or power outage) for the network device and an importance level of the power limited event (e.g., power cut or power outage) , or (ii) at least one action of the network device to prolong a service duration of the at least one backup battery.

It is understood that the above procedure steps may work together, in a flow of operations as described in the next section, partly together or independently of each other. By implementing one or more of the example embodiments of this disclosure, the backup battery period of service can be predicted, the energy usage modification (e.g., energy service optimization, such as an energy saving service) can be optimized, and/or the optimization of the backup battery lifespan can be enabled (or otherwise facilitated) .

For non-limiting and illustrative purposes, various example embodiments of this disclosure pertaining to power limited event (e.g., power cut or power outage) duration prediction and energy usage modification (e.g., energy service optimization, such as an energy saving service) optimization are described below with reference to FIG. 1A –FIG. 8. However, it is to be noted that these example embodiments are merely provided to enable (or otherwise facilitate) those skilled in the art to understand this disclosure and implement the various example embodiments described herein, and not intended to limit the scope of this disclosure in any way.

Reference is made to FIG. 1A, which illustrates an example network environment 100A in which some example embodiments of this disclosure may be implemented. The network environment 100, which may be a part of a communication network, includes a first apparatus 102 and a second apparatus 104.

As illustrated in FIG. 1A, the first apparatus 102 and the second apparatus 104 can communicate with each other. In some example embodiments, the first apparatus 102 may be an MnS consumer, and the second apparatus 104 may be an MnS producer. In some example embodiments, if the MnS consumer has faced, is facing, and/or is expected to face a power limited event (e.g., power cut or power outage) , it may request an energy usage modification (e.g., energy service optimization, such as an energy saving service) . The MnS producer may collect information from related components upon receiving the request, and derive an output. The MnS producer may send the output to the MnS consumer.

FIG. 1B illustrates an example gNB and backup batteries 100B related to some example embodiments of this disclosure. The main power supply 106 may provide energy for the gNB 108 for most situations (e.g., use cases) . However, when the main power supply 106 doesn’ t work due, for example, to a power limited event (e.g., power cut or power outage) , the 3GPP management system 110 can utilize the backup batteries 112 continue to provide energy to the gNB 108. The 3GPP management system may, in some example embodiments, also utilize the backup batteries 112 to provide energy to the gNB 108 in other situations, such as a power limited event (e.g., where the main power supply 106 is inadequate for a particular use case) , or where the main power supply 106 does work but would benefit from additional power for a particular use case due to a power limited event.

Reference is made to FIG. 2, which illustrates an example signaling process 200 of power limited event (e.g., power cut or power outage) duration prediction and energy usage modification (e.g., energy service optimization, such as an energy saving service) in accordance with some example embodiments of this disclosure. FIG. 2 will be described with reference to FIG. 1A.

As shown in FIG. 2, the first apparatus 102 transmits (202) a request 206 for an energy usage modification (e.g., energy service optimization, such as an energy saving service) to the second apparatus 104. The energy usage modification (e.g., energy service optimization, such as an energy saving service) may be associated with at least one backup battery or UPS of a network device, if main power of the network device has experienced, is experiencing, and/or will experience a power limited event (e.g., power cut or power outage) . The second apparatus 104 receives (204) the request 206 from the first apparatus 102.

The second apparatus 104 collects (208) input data for performing the energy usage modification (e.g., energy service optimization, such as an energy saving service) based on receiving the request 206. The input data for performing such prediction may, for example, comprise history information of power limited events (e.g., power cuts or power outages) within a given area, and/or a power supplier, etc. The input information will be described in detail later.

In some example embodiments, the second apparatus 104 may take different parameters and measurements from the network as input. For example, the backup battery charge/discharge status for gNBs whose main power supply has gone down (may also include a type of the backup battery) or are otherwise experiencing a power limited event; performance measurements (e.g., traffic/energy consumption counters) ; configuration management parameters {e.g., parameters related to the gNB that has faced, is facing, and/or is expected to face a power limited event (e.g., power cut or power outage) , and all neighboring gNBs, enabled energy usage modification (e.g., optimization, such as saving) features, etc. } ; fault management (e.g., power outage alarm, power recovery alarm, service offline due to power outage alarm) ; and analytics provided by management data analytics service (MDAS) (e.g., energy saving analytics, traffic prediction analytics) .

The second apparatus 104 derives (210) output data of the energy usage modification (e.g., energy service optimization, such as an energy saving service) based on the collected input data. In some example embodiments, the output data may comprise (i) a predicted duration of a power limited event (e.g., power cut or power outage) for the network device and an importance level of the power limited event (e.g., power cut or power outage) . In some example embodiments, the output data may comprise (ii) at least one action of the network device to prolong a service duration of the at least one backup battery. In some example embodiments, the output data may comprise both items (i) and (ii) .

In some example embodiments, the output data may comprise analytics and prediction of the power limited event (e.g., power cut or power outage) period. Such a prediction may, for example, be derived in terms of statistics on the frequency of power limited events (e.g., power cuts or power outages) a gNB has faced, is facing, or is expected to face and respective period (s) associated therewith. The prediction of the period (s) of the power limited event (e.g., power cut or power outage) may be requested for a specific geographic area, and/or a specific network node (e.g., gNB, the power supplier, etc. ) .

In some example embodiments, the output data may comprise an estimation of the importance level of the power limited event (e.g., power cut or power outage) . Such an estimation may depend on a predicted duration of the power limited event (e.g., power cut or power outage) , the backup battery charge/discharge state, and/or a gNB type (e.g., macro/micro) , etc. In some example embodiments, a numerical range from 1-3 may, for example, be implemented as level of importance, where 3 may represent a power limited event with a higher importance and 1 may represent power limited event with a lower importance. In other example embodiments, a level of importance of 1 may represent a power limited event with a lower importance and 3 may represent a power limited event with a higher importance. In some example embodiments, other forms of importance than those listed herein may be implemented.

In some example embodiments, the output data may comprise analytics on prolonging the duration of backup battery support. The output of this analytics may, for example, comprise (or otherwise indicate) potential actions to reduce the energy consumption and thus prolong the duration of the backup batteries support.

In some embodiments, a confidence level may be associated to the prediction of the duration of the power limited event (e.g., power cut or power outage) (e.g., which is provided as part of BB-ES MnS producer’s response or the second apparatus 104) . This confidence level may be used by the BB-ES MnS consumer or the first apparatus 102 as an indication to adjust its requests for action (s) for backup battery service duration extension.

In some example embodiments, the output data may comprise (or otherwise indicate) a table comprising a suggested or recommended action. The suggested or recommended action may, for example, be supported to optimize energy consumption and thus to prolong the duration of the backup battery. If an action is related to load balancing management, then the action may target to offload traffic for the gNB that has faced, is facing, and/or is expected to face a power limited event (e.g., power cut or power outage) towards one or more of its neighboring gNBs. If an action is related to one or more energy usage modification (e.g., energy optimization, such as energy saving) features, then the action may propose the activation and/or deactivation of one or more energy usage modification (e.g., energy optimization, such as energy saving) features (e.g., cell switch and thus balance the energy consumption requirements and the QoS requirements during the duration of the power limited event) .

In some example embodiments, to predict the duration of the power limited event, importance level, and provide one or more recommended actions to prolong the duration of backup battery support, different approaches can be employed (e.g., including the use of machine learning) .

The second apparatus 104 transmits (214) a report 216 of the energy usage modification (e.g., energy service optimization, such as an energy saving service) comprising the output data to the first apparatus 102. The first apparatus 102 receives (212) the report 216 from the second apparatus 104.

In some example embodiments, the output data may comprise (or otherwise indicate) a table comprising the backup battery support period if the recommended action (s) is/are taken by the BB-ES MnS consumer. In some example embodiments, the report 216 may detail each recommended action in the following aspects. If the action is related to offloading traffic, then the report details may comprise (or otherwise indicate) a set of recommended candidate cells {e.g., neighboring backup battery cell (s) and/or gNB (s) } for taking over the traffic, and a timing (e.g., time (s) ) to enter and terminate the load offloading state. If the action is related to activating one or more energy usage modification (e.g., energy optimization, such as energy saving) features, then report details may comprise (or otherwise indicate) a set of recommended NR Cell (ES-Cell) to enter a modified energy usage state (e.g., energy optimized state, such as an energy saving state) , one or more recommended candidate cells with precedence (e.g., priority) for taking over the traffic of the ES-Cell, a timing (e.g., time (s) ) to enter and terminate the modified energy usage state (e.g., energy optimized state, such as an energy saving state) , and/or the load threshold (s) to enter and terminate the modified energy usage state (e.g., energy optimized state, such as an energy saving state) for the respective ES-Cell (s) .

By implementing one or more example embodiments of the method 200, the backup battery period of service can be predicted, the energy usage modification (e.g., energy service optimization, such as an energy saving service) can be optimized, and/or optimization of the backup battery lifespan can be enabled (or otherwise facilitated) .

Reference is made to FIG. 3, which illustrates another example signaling process 300 of power limited event (e.g., power cut or power outage) duration prediction and energy usage modification (e.g., energy service optimization, such as an energy saving service) in accordance with some example embodiments of this disclosure. FIG. 3 illustrates the procedures utilized for deriving analytics and predictions of the power limited event (e.g., power cut or power outage) in the network and exposing such information to the authorized consumer (e.g., gNB management system) . Various example embodiments provide a separate management service for backup battery energy saving. A same or similar solution could also be extended to new MDA analytics. In such case, a new analytics use-case can be proposed to cover the different prediction and analytics described at step 342, and the workflow would be similar, requesting MDA analytics and notifying when the MDA report is ready. In FIG. 3, the BB-ES MnS consumer 302 may correspond to the first apparatus 102 in FIG. 1A. The BB-ES MnS producer 304 may correspond to the second apparatus 104 in FIG. 1A.

At 320, the BB-ES MnS consumer 302 may transmit a request for energy usage modification (e.g., energy service optimization, such as a backup battery energy saving service request) to the BB-ES MnS producer 304. For example, the authorized consumer, e.g. gNB (or network operator’s management system) , may request information on the power limited event (e.g., power cut or power outage) it has faced, is facing, and/or is expected to face. In such a request, the BB-ES MnS consumer 302 may indicate at least one of the following: a load situation and a traffic of the related gNB; a current backup battery charge/discharge level; or an expected output (e.g., only period prediction and importance level of the power limited event (e.g., power cut or power outage) , or one or more recommended actions and a prolonged backup period support period) . The request may, in some example embodiments, include (e.g., only include) the identity (ID) of the node (e.g., BB-ES MnS consumer 302) that has faced, is facing and/or is expected to face the power limited event (e.g., power cut or power outage) , and then the BB-ES MnS producer 304 may collect all related information associated therewith.

At 322, the BB-ES MnS producer 304 (producer of the power limited event optimization analytics, e.g. NSP OAM system, or MDAF) may derive which input data is relevant to perform the requested analytics or prediction.

At 324 (from step 326 to step 340) , the BB-ES MnS producer 304 may subscribe to relevant data, such as provisioning MnS producer (PM) 306, fault supervision MnS producer (FM) 308, performance assurance MnS producer 310, analytics function 312, life cycle management (LCM) and connection management (CM) , based on the derived info at 322. The BB-ES MnS producer 304 may receive corresponding inputs.

For example, the PM 306 may include the energy consumption and traffic load metrics collected for different network functions (NFs) . The BB-ES MnS Producer 304 may rely on analytics and predictions already available in the network (e.g., UE communication analytics, or other analytics provided by MDAF on traffic load trends and energy saving related analytics) . The FM 308 may include information about when the battery system starts to provide power (e.g., information extracted from the received alarm (s) about a timing (e.g., occurrence timing) of at least one power limited event, such as power cut or power outage) .

At 342, the MnS producer 304 may derive prediction and analytics on the power limited event (e.g., power cut or power outage) . The MnS producer 304 may derive the following outputs (1) to (3) to the be reported to the MnS consumer. The output (1) may be power limited event duration prediction with a confidence interval related to this prediction. A classification of the importance level of power limited event (e.g., power cut or power outage) might also be derived. Such information may be derived based on the history (e.g., history information) of the FM data (e.g. power outage alarm, power recovery alarm, service offline due to power outage alarm) .

The output (2) may comprise (or otherwise indicate) a table of potential action that includes the different features that can be supported by the gNB that has faced, is facing, and/or is expected to face a power limited event (e.g., power cut or power outage) and the prolonged backup battery support duration related therewith. The following table illustrates an example of action table produced by the BB-ES MnS producer 304. In some example embodiments, the table may include the backup battery support period estimated where each action or multiple actions proposed by the BB-ES MnS producer 304 are to be decided by the BB-ES MnS consumer 302. For example, Table 1 shows an example table of potential actions.

Table 1

The output (3) may comprise (otherwise indicate) recommended actions and configuration parameters for the gNB that has faced, is facing, and/or is expected to face a power limited event (e.g., power cut or power outage) and neighbouring gNBs. At 344, the BB-ES Mns producer 304 may report the prediction and analytics output to the BB-ES MnS consumer 302.

With some example embodiments of this disclosure, several aspects of relevant specification (s) may be changed. By way of non-limiting and illustrative example, three example embodiments are herein provided. In the following example embodiments, some new parts or changed parts for the cited specification are reflected in bold.

Example Embodiment A1: Example embodiment to SA5 TS 28.541 with Rel18 active WID: EE5GPLUS_Ph2.

4.3.58 DESManagementFunction

4.3.58.1 Definition

This IOC represents the management capabilities of Distributed SON Energy Saving (ES) functions (see clause 6.2.3.0 in TS 28.310 [71] ) . This is provided for Energy Saving purposes.

NOTE: in the case where multiple DESManagementFunction MOIs exist at different levels of the containment tree, the DESManagementFunction MOI at the lower level overrides the DESManagementFunction MOIs at higher level (s) of the same containment tree.

This IOC includes an attribute isESusedForPowerCut to indicate if the Energy Saving function is used during a power cut situation in order to prolong the backup battery support duration or not. When the isESusedForPowerCut is ON, the time period during which the energy saving state is allowed, is indicated by the attribute esPowerCutTimePeriod.

4.3.58.2 Attributes

The DESManagementFunction IOC includes attributes inherited from Top IOC (defined in TS 28.622 [30] ) and the following attributes:

4.3.58.3 Attribute constraints

4.3.63 CESManagementFunction

4.3.63.1 Definition

This IOC represents the management capabilities of Centralized SON Energy Saving (ES) functions. (see clause 6.2.2 of TS 28.310 [71] ) This is provided for Energy Saving purposes.

NOTE: in the case where multiple CESManagementFunction MOIs exist at different levels of the containment tree, the CESManagementFunction MOI at the lower level overrides the CESManagementFunction MOIs at higher level (s) of the same containment tree.

4.3.63.2 Attributes

The CESManagementFunction IOC includes attributes inherited from Top IOC (defined in TS 28.622 [30] ) and the following attributes:

4.3.63.3 Attribute constraints

4.3.63.4 Notification

The common notifications defined in clause 4.5 are valid for this IOC, without exceptions or additions.

4.4 Attribute definitions

4.4.1 Attribute properties

Example Embodiment A2: MDA requirements TS 28.104

7 Use cases and requirements for MDA capabilities and services

7.1 General

The following clauses describe the use cases and requirements for MDA capabilities and MDA MnSs. The MDA capabilities are grouped under specific categories.

7.2 MDA capabilities

7.2.4 MDA assisted Energy Saving

7.2.4. xx Energy saving during power outage analysis

A RAN node, experiencing a power outage, including power outage related to the main power supply, might trigger the usage of the backup battery, to prolong the service duration. However, the service duration supported by backup batteries may not meet the duration of the power outage. Therefore, the RAN node is to reduce its consumed energy to prolong the service duration supported by the backup battery. Reducing the energy consumption of the RAN node might be realized in (1) soft-manner by offloading partially the traffic to neighboring cells or in (2) hard-manner by triggering an energy saving feature, such as a cell switch-off. To achieve this, an MDA can be used to assist the MDAS consumer, e.g. RAN node, to make energy saving decisions to prolong the support duration of the backup battery.

7.2.4. xx. 3 Requirements

Table 7.2.4. xx. 3-1

Example Embodiment A3: MDA capability definition

8.4 Data definitions per MDA capability

8.4.4 MDA assisted energy saving

8.4.4. xx Energy saving analysis during power outage/cut

8.4.4. xx. 1 MDA type

The MDA type for energy saving during power outage analysis is: MDAAssistedEnergySavingPowerOutage. EnergySavingAnalysisPowerOutage.

8.4.4. xx. 2 Enabling data

The enabling data for this MDA type are provided in table 8.4.4. xx. 2-1.

Table 8.4.4. xx. 2-1: Enabling data for energy saving during power outage analysis

8.4.4.1.3 Analytics output

The specific information elements of the analytics output for energy saving during power outage analysis, in addition to the common information elements of the analytics outputs are provided in table 8.4.4. xx. 3-1.

Table 8.4.4. xx. 3-1: Analytics output for energy saving analysis

8.5. x ESRecommendationPowerOutage <<dataType>>

8.5. x. 1 Definition

This data type specifies the RAN energy saving recommendation and backup battery support duration prolongation.

8.5. x. 2 Information elements

Table 8.5. x. 2-1

FIG. 4 illustrates an example backup battery assisted energy saving usage 400 in accordance with some example embodiments of this disclosure. In FIG. 4, an example of backup battery assisted energy saving usage is shown. In some example embodiments, the analytics may be used to assist the BB-ES MnS consumer (e.g., management system of gNB that has faced, is facing, and/or is expected to face a power limited event (e.g., power cut, or power outage) to adapt its decision depending on the backup battery charge levels, and thereby prolong the backup battery support period while maintaining the QoS or connectivity (e.g., as much as possible) . In some example embodiments, gNB offloading actions may be taken when the backup battery charge level reaches 80%to prolong the backup battery support period to 5 hours (as shown in line 410) , and energy usage modification (e.g., energy optimization, such as energy saving) actions can be activated when backup battery charge level reaches 50%to further prolong the support period up to 6 hours (as shown in line 406) .

Reference is made to FIG. 5, which illustrates an example flowchart of a process 500 of power limited event duration prediction and energy usage modification (e.g., energy service optimization, such as an energy saving service) in accordance with some example embodiments of this disclosure. FIG. 5 will be described with reference to FIG. 1A.

At 502, the first apparatus 102 transmits a request for an energy usage modification (e.g., energy service optimization, such as an energy saving service) to the second apparatus 104. The energy usage modification (e.g., energy service optimization, such as an energy saving service) is associated with at least one backup battery or UPS of a network device based on a power limited event (e.g., power cut, or power outage) that the network device has experienced, is experiencing, and/or is expected to experience.

At 504, the first apparatus 102 receives a report of the energy usage modification (e.g., energy service optimization, such as an energy saving service) from the second apparatus 104. The report indicates at least one of the following: (i) a predicted duration of a power limited event (e.g., power cut or power outage) for the network device and an importance level of the power limited event (e.g., power cut or power outage) , or (ii) at least one action of the network device to prolong a service duration of the at least one backup battery.

In some example embodiments, the request may indicate at least one of the following: an ID of the network device, a load situation of the network device, traffic of the network device, at least one charge level for charging the at least one backup battery, at least one discharge level for discharging the at least one backup battery, or an expected output of the energy usage modification (e.g., energy service optimization, such as an energy saving service) .

In some example embodiments, the report may further indicate a confidence interval associated with the predicted duration of the power limited event (e.g., power cut or power outage) . In some example embodiments, the importance level may be determined based on at least one of the following: the predicted duration of the power limited event (e.g., power cut or power outage) , at least one charge/discharge state of the at least one backup battery, a type of the network device, or history information of at least one fault management of the network device.

In some example embodiments, the at least one action may comprise at least one of the following: a first action, and the first action comprises offloading, at least partially, traffic of the network device to at least one neighboring network device; or a second action, and the second action comprises activating an energy usage modification (e.g., energy optimization, such as energy saving) feature.

In some example embodiments, the report may indicate the first action and at least one of the following: at least one candidate cell for offloading the traffic of the network device; timing (e.g., time (s) ) to enter an offloading state; timing (e.g., time (s) ) to terminate the offloading state; a load threshold to enter the offloading state; or a load threshold to terminate the offloading state.

In some example embodiments, the report may indicate the second action and at least one of the following: a cell of the network device to enter a modified energy usage state (e.g., energy optimized state, such as an energy saving state) ; at least one candidate cell with precedence (e.g., priority) for offloading the traffic of the cell of the network device; timing (e.g., time (s) ) to enter the modified energy usage state (e.g., energy optimized state, such as an energy saving state) ; timing (e.g., time (s) ) to terminate the modified energy usage state (e.g., energy optimized state, such as an energy saving state) ; a load threshold to enter the modified energy usage state (e.g., energy optimized state, such as an energy saving state) for a cell of the network device; or a load threshold to terminate the modified energy usage state (e.g., energy optimized state, such as an energy saving state) for the cell.

In some example embodiments, the predicted duration and the at least one action may be indicated using an action table, and the action table may further comprise (or otherwise indicate) : a plurality of combinations of actions to prolong the service duration and a plurality of estimated periods of backup battery service respective to the plurality of combinations of the actions.

In some example embodiments, the report may further indicate a plurality of configuration parameters for performing the at least one action for at least one of the network device or at least one neighboring network device.

Reference is made to FIG. 6, which illustrates an example flowchart of a process 600 of power limited event duration prediction and energy usage modification (e.g., energy service optimization, such as an energy saving service) in accordance with some example embodiments of this disclosure. FIG. 6 will be described with reference to FIG. 1A.

At 602, the second apparatus 104 receives a request for an energy usage modification (e.g., energy service optimization, such as an energy saving service) from a first apparatus 102. The energy usage modification (e.g., energy service optimization, such as an energy saving service) is associated with at least one backup battery or uninterruptible power supply (UPS) of a network device based on a power limited event (e.g., power cut or power outage) that the network device has experienced, is experiencing, and/or will experience. At 604, the second apparatus 104 collects input data for performing the energy usage modification (e.g., energy service optimization, such as an energy saving service) based on receiving the request.

At 606, the second apparatus 104 derives output data of the energy usage modification (e.g., energy service optimization, such as an energy saving service) based on the collected input data. The output data may comprise (or otherwise indicate) at least one of the following: (i) a predicted duration of a power limited event (e.g., power cut, or power outage) for the network device and an importance level of the power limited event (e.g., power cut or power outage) , or (ii) at least one action of the network device to prolong a service duration of the at least one backup battery. At 608, the second apparatus 104 transmits a report of the energy usage modification (e.g., energy service optimization, such as an energy saving service) comprising the output data to the first apparatus 102.

In some example embodiments, the report may indicate the second action and at least one of the following: a cell of the network device to enter a modified energy usage state (e.g., energy optimized state, such as an energy saving state) ; at least one candidate cell with precedence (e.g., priority) for offloading the traffic of the cell of the network device; timing (e.g., time (s) ) to enter the modified energy usage state (e.g., energy optimized state, such as an energy saving state) ; timing (e.g., time (s) ) to terminate the modified energy usage (e.g., energy optimized state, such as an energy saving state) ; a load threshold to enter the modified energy usage state (e.g., energy optimized state, such as an energy saving state) for a cell of the network device; or a load threshold to terminate the modified energy usage state (e.g., energy optimized state, such as an energy saving state) for the cell.

In some example embodiments, the predicted duration and the at least one action may be indicated using an action table, and the action table may further comprise: a plurality of combinations of actions to prolong the service duration and a plurality of estimated periods of backup battery service respective to the plurality of combinations of the actions.

In some example embodiments, the input data comprises at least one of the following: at least one geographic area associated with the energy usage modification (e.g., energy service optimization, such as an energy saving service) ; at least one network node associated with the energy usage modification (e.g., energy service optimization, such as an energy saving service) ; at least one power supplier associated with the energy usage modification (e.g., energy service optimization, such as an energy saving service) ; history information of at least one power limited event (e.g., power cut or power outage) associated with the energy usage modification (e.g., energy service optimization, such as an energy saving service) ; at least one status of the backup battery charge or discharge for the network device; at least one type of the at least one backup battery; at least one performance measurement of the network device; at least one configuration management parameter of at least one of the network device or at least one neighboring network device; at least one fault management of the network device; or analytics provided by an MDAS.

By implementing one or more of example embodiments of the methods 500 and 600, the backup battery period of service can be predicted, the energy usage modification (e.g., energy service optimization, such as an energy saving service) can be optimized, and/or optimization of the backup battery lifespan can be enabled (or otherwise facilitated) .

In some example embodiments, a first apparatus capable of performing the method 500 (for example, the first apparatus 102) may comprise means for performing the respective steps of the method 500. The means may be implemented in any suitable form. For example, the means may be implemented in a circuitry or software module.

In some example embodiments, the first apparatus may comprise means for transmitting, at the first apparatus to a second apparatus, a request for an energy usage modification (e.g., energy service optimization, such as an energy saving service) associated with at least one backup battery or UPS of a network device based on a power limited event (e.g., power cut or power outage) of the network device; and means for receiving, from the second apparatus, a report of the energy usage modification (e.g., energy service optimization, such as an energy saving service) , wherein the report indicates at least one of the following: (i) a predicted duration of a power limited event (e.g., power cut or power outage) for the network device and an importance level of the power limited event (e.g., power cut or power outage) , or (ii) at least one action of the network device to prolong a service duration of the at least one backup battery.

In some example embodiments, the report may indicate the second action and at least one of the following: a cell of the network device to enter a modified energy usage state (e.g., energy optimized state, such as an energy saving state) ; at least one candidate cell with precedence (e.g., priority) for offloading the traffic of the cell of the network device; time to enter the modified energy usage state (e.g., energy optimized state, such as an energy saving state) ; timing (e.g., time (s) ) to terminate the modified energy usage state (e.g., energy optimized state, such as an energy saving state) ; a load threshold to enter the modified energy usage state (e.g., energy optimized state, such as an energy saving state) for a cell of the network device; or a load threshold to terminate the modified energy usage state (e.g., energy optimized state, such as an energy saving state) for the cell.

In some example embodiments, the first apparatus may further comprise means for performing other steps in some example embodiments of the method 500. In some example embodiments, the means comprises at least one processor and at least one memory including computer program code, the at least one memory and computer program code configured to, with the at least one processor, cause the performance of the first apparatus.

In some example embodiments, a second apparatus capable of performing the method 600 (for example, the second apparatus 104) may comprise means for performing the respective steps of the method 600. The means may be implemented in any suitable form. For example, the means may be implemented in a circuitry or software module.

In some example embodiments, the second apparatus may comprise means for receiving, at the second apparatus from a first apparatus, a request for an energy usage modification (e.g., energy service optimization, such as an energy saving service) associated with at least one backup battery or UPS of a network device based on a power limited event (e.g., power cut or power outage) of the network device; means for collecting input data for performing the energy usage modification (e.g., energy service optimization, such as an energy saving service) based on receiving the request; means for deriving output data of the energy usage modification (e.g., energy service optimization, such as an energy saving service) based on the collected input data, wherein the output data comprises at least one of the following: (i) a predicted duration of a power limited event (e.g., power cut or power outage) for the network device and an importance level of the power limited event (e.g., power cut or power outage) , or (ii) at least one action of the network device to prolong a service duration of the at least one backup battery; and means for transmitting, to the first apparatus, a report of the energy usage modification (e.g., energy service optimization, such as an energy saving service) comprising the output data.

In some example embodiments, the report may indicate the second action and at least one of the following: a cell of the network device to enter a modified energy usage state (e.g., energy optimized state, such as an energy saving state) ; at least one candidate cell with precedence (e.g., priority) for offloading the traffic of the cell of the network device; timing (e.g., time (s) ) to enter the modified energy usage state (e.g., energy optimized state, such as an energy saving state) ; timing (e.g., time (s) ) to terminate the modified energy usage state (e.g., energy optimized state, such as an energy saving state; a load threshold to enter the modified energy usage state (e.g., energy optimized state, such as an energy saving state) for a cell of the network device; or a load threshold to terminate the modified energy usage state (e.g., energy optimized state, such as an energy saving state) for the cell.

In some example embodiments, the input data may comprise at least one of the following: at least one geographic area associated with the energy usage modification (e.g., energy service optimization, such as an energy saving service) ; at least one network node associated with the energy usage modification (e.g., energy service optimization, such as an energy saving service) ; at least one power supplier associated with the energy usage modification (e.g., energy service optimization, such as an energy saving service) ; history information of at least one power limited event (e.g., power cut or power outage) associated with the energy usage modification (e.g., energy service optimization, such as an energy saving service) ; at least one status of the backup battery charge or discharge for the network device; at least one type of the at least one backup battery; at least one performance measurement of the network device; at least one configuration management parameter of at least one of the network device or at least one neighboring network device; at least one fault management of the network device; or analytics provided by an MDAS.

In some example embodiments, the second apparatus may further comprise means for performing other steps in some example embodiments of the method 600. In some example embodiments, the means comprises at least one processor and at least one memory including computer program code, the at least one memory and computer program code configured to, with the at least one processor, cause the performance of the second apparatus.

Reference is made to FIG. 7, which illustrates an example simplified block diagram of a device 700 that is configured to implement at least some example embodiments of this disclosure. The device 700 may implement the communication device, for example the first apparatus as shown in FIG. 1A. As shown, the device 700 includes one or more processors 710, one or more memories 720 may couple to the processor 710, and one or more communication modules 740 may couple to the processor 710.

The communication module 740 is for bidirectional communications. The communication module 740 has at least one antenna to enable (or otherwise facilitate) communication. The communication interface may represent any interface that is utilized for communication with other network elements. F example, the communication interface may be wireless or wireline to other network elements, and/or software based interface for communication.

The processor 710 may be of any type configured to the local technical network and may include one or more of the following: general purpose computers, special purpose computers, microprocessors, digital signal processors (DSPs) and processors based on multicore processor architecture, as non-limiting and illustrative examples. The device 700 may have multiple processors 710, such as an application specific integrated circuit chip that is slaved in time to a clock which synchronizes the main processor.

The memory 720 may include one or more non-volatile memories and one or more volatile memories. Examples of the non-volatile memories include, but are not limited to, a read only memory (ROM) 724, an electrically programmable read only memory (EPROM) , a flash memory, a hard disk, a compact disc (CD) , a digital video disk (DVD) , and other magnetic storage and/or optical storage. Examples of the volatile memories include, but are not limited to, a random access memory (RAM) 722 and other volatile memories that are not configured to last in the power-down duration.

A computer program 730 includes computer executable instructions that are executed by the associated processor 710. The program 730 may be stored in the ROM 724. The processor 710 may perform any suitable actions and processing by loading the program 730 into the RAM 722.

The various example embodiments of this disclosure may be implemented by means of the program so that the device 700 may perform any process (or portion thereof) of the disclosure as discussed with reference to FIG. 2 to FIG. 6. The various example embodiments of this disclosure may also be implemented by hardware or by a combination of software and hardware.

In some example embodiments, the program 730 may be tangibly comprised in a computer readable medium, which may be included in the device 700 (such as in the memory 720) or other storage devices that are accessible by the device 700. The device 700 may load the program 730 from the computer readable medium to the RAM 722 for execution. The computer readable medium may include any types of tangible non-volatile storage, such as ROM, EPROM, a flash memory, a hard disk, CD, DVD, and the like. FIG. 8 shows an example of the computer readable medium 800 in form of CD or DVD. The computer readable medium has the program 730 stored thereon.

Generally, various example embodiments of this disclosure may be implemented in hardware or special purpose circuits, software, logic or any combination thereof. Some aspects may be implemented in hardware, while other aspects may be implemented in firmware or software which may be executed by a controller, microprocessor or other computing device. While various aspects of the example embodiments described herein are illustrated and described as block diagrams, flowcharts, or using some other pictorial representations, it is to be understood that the block, apparatus, system, technique or method described herein may be implemented in, by way of non-limiting and illustrative example, hardware, software, firmware, special purpose circuits or logic, general purpose hardware or controller or other computing devices, or some combination thereof.

This disclosure also provides at least one computer program product tangibly stored on a non-transitory computer readable storage medium. The computer program product includes computer-executable instructions, such as those included in program modules, being executed in a device on a target real or virtual processor, to carry out the methods 500 or 600 as described above with reference to FIG. 5 or FIG. 6. Generally, program modules include routines, programs, libraries, objects, classes, components, data structures, or the like that perform particular tasks or implement particular data types. The functionality of the program modules may be combined or split between program modules as desired in various embodiments. Machine-executable instructions for program modules may be executed within a local or distributed device. In a distributed device, program modules may be located in both local and remote storage media.

Program code for carrying out methods of this disclosure may be written in any combination of one or more programming languages. These program codes may be provided to a processor or controller of a general purpose computer, special purpose computer, or other programmable data processing apparatus, such that the program codes, when executed by the processor or controller, cause the functions/operations specified in the flowcharts and/or block diagrams to be implemented. The program code may execute entirely on a machine, partly on the machine, as a stand-alone software package, partly on the machine and partly on a remote machine or entirely on the remote machine or server.

In the context of this disclosure, the computer program code or related data may be carried by any suitable carrier to enable (or otherwise facilitate) the device, apparatus or processor to perform various processes and operations as described herein. Examples of the carrier include a signal, computer readable medium, and the like.

The computer readable medium may be a computer readable signal medium or a computer readable storage medium. A computer readable medium may include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination of the foregoing. More specific examples of the computer readable storage medium would include an electrical connection having one or more wires, a portable computer diskette, a hard disk, a random access memory (RAM) , a read-only memory (ROM) , an erasable programmable read-only memory (EPROM or Flash memory) , an optical fiber, a portable compact disc read-only memory (CD-ROM) , an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. The term “non-transitory, ” as used herein, is a limitation of the medium itself (i.e., tangible, not a signal) as opposed to a limitation on data storage persistency (e.g., RAM vs. ROM) .

Further, while operations are depicted in a particular order, this should not be understood as requiring that such operations be performed in the particular order shown or in sequential order, or that all illustrated operations be performed, to achieve particular result (s) . In certain circumstances, multitasking and parallel processing may be advantageous. Likewise, while several specific implementation details are contained in the above discussions, these should not be construed as limitations on the scope of this disclosure, but rather as descriptions of features that may be specific to particular example embodiments. Certain features that are described in the context of separate example embodiments may also be implemented in combination in a single example embodiment. Conversely, various features that are described in the context of a single example embodiment may also be implemented in multiple example embodiments separately or in any suitable sub-combination.

Although this disclosure has been described in terminology specific to structural features and/or methodological acts, it is to be understood that this disclosure is not necessarily limited to the specific features or acts described above. Rather, the specific features and acts described above are disclosed as non-limiting and illustrative forms of implementing subject matter described herein.

Claims

A first apparatus comprising:

at least one processor; and

at least one memory storing instructions that, when executed by the at least one processor, cause the first apparatus at least to:

transmit, to a second apparatus, a request for an energy usage modification associated with at least one backup battery or uninterruptible power supply (UPS) of a network device based on a power limited event of the network device; and

receive, from the second apparatus, a report of the energy usage modification, wherein the report indicates at least one of the following: (i) a predicted duration of the power limited event for the network device and an importance level of the power limited event, or (ii) at least one action of the network device to prolong a service duration of the at least one backup battery.
The first apparatus of claim 1, wherein the request indicates at least one of the following:

an identity (ID) of the network device;

a load situation of the network device;

traffic of the network device;

at least one charge level for charging the at least one backup battery;

at least one discharge level for discharging the at least one backup battery; or

an expected output of the energy usage modification.
The first apparatus of claim 1 or 2, wherein the report further indicates a confidence interval associated with the predicted duration of the power limited event.
The first apparatus of claim 3, wherein the importance level is determined based on at least one of the following:

the predicted duration of the power limited event;

at least one charge/discharge state of the at least one backup battery;

a type of the network device; or

history information of at least one fault management of the network device.
The first apparatus of any of claims 1-4, wherein the at least one action comprises at least one of the following:

a first action, wherein the first action comprises offloading, at least partially, traffic of the network device to at least one neighboring network device; or

a second action, wherein the second action comprises activating an energy usage modification feature.
The first apparatus of claim 5, wherein the report indicates the first action and at least one of the following:

at least one candidate cell for offloading the traffic of the network device;

timing to enter an offloading state;

timing to terminate the offloading state;

a load threshold to enter the offloading state; or

a load threshold to terminate the offloading state.
The first apparatus of claim 5 or 6, wherein the report indicates the second action and at least one of the following:

a cell of the network device to enter a modified energy usage state;

at least one candidate cell with precedence for offloading the traffic of the cell of the network device;

timing to enter the modified energy usage state;

timing to terminate the modified energy usage state;

a load threshold to enter the modified energy usage state for a cell of the network device; or

a load threshold to terminate the modified energy usage state for the cell.
The first apparatus of any of claims 1-7, wherein the predicted duration and the at least one action are indicated using an action table, and the action table further comprises:

a plurality of combinations of actions to prolong the service duration and a plurality of estimated periods of backup battery service respective to the plurality of combinations of the actions.
The first apparatus of any of claims 1-8, wherein the report further indicates:

a plurality of configuration parameters for performing the at least one action for at least one of the network device or at least one neighboring network device.
A second apparatus comprising:

at least one processor; and

at least one memory storing instructions that, when executed by the at least one processor, cause the second apparatus at least to:

receive, from a first apparatus, a request for an energy usage modification associated with at least one backup battery or uninterruptible power supply (UPS) of a network device based on a power limited event of the network device;

based on receiving the request, collect input data for performing the energy usage modification;

derive output data of the energy usage modification based on the collected input data, wherein the output data comprises at least one of the following: (i) a predicted duration of the power limited event for the network device and an importance level of the power limited event, or (ii) at least one action of the network device to prolong a service duration of the at least one backup battery; and

transmit, to the first apparatus, a report of the energy usage modification comprising the output data.
The second apparatus of claim 10, wherein the request indicates at least one of the following:

an identity (ID) of the network device;

a load situation of the network device;

traffic of the network device;

at least one charge level for charging the at least one backup battery;

at least one discharge level for discharging the at least one backup battery; or

an expected output of the energy usage modification.
The second apparatus of claim 10 or 11, wherein the output data further comprises a confidence interval associated with the predicted duration of the power limited event.
The second apparatus of claim 12, wherein the importance level is determined based on at least one of the following:

the predicted duration of the power limited event;

at least one charge/discharge state of the at least one backup battery;

a type of the network device; or

history information of at least one fault management of the network device.
The second apparatus of any of claims 10-13, wherein the at least one action comprises at least one of the following:

a first action, wherein the first action comprises offloading, at least partially, traffic of the network device to at least one neighboring network device; or

a second action, wherein the second action comprises activating an energy usage modification feature.
The second apparatus of claim 14, wherein the report indicates the first action and at least one of the following:

at least one candidate cell for offloading the traffic of the network device;

timing to enter an offloading state;

timing to terminate the offloading state;

a load threshold to enter the offloading state; or

a load threshold to terminate the offloading state.
The second apparatus of claim 14 or 15, wherein the report indicates the second action and at least one of the following:

a cell of the network device to enter a modified energy usage state;

at least one candidate cell with precedence for offloading the traffic of the cell of the network device;

timing to enter the modified energy usage state;

timing to terminate the modified energy usage state;

a load threshold to enter the modified energy usage state for a cell of the network device; or

a load threshold to terminate the modified energy usage state for the cell.
The second apparatus of any of claims 10-16, wherein the predicted duration and the at least one action are indicated using an action table, and the action table further comprises:

a plurality of combinations of actions to prolong the service duration and a plurality of estimated periods of backup battery service respective to the plurality of combinations of the actions.
The second apparatus of claim 17, the action table further comprises:

a plurality of configuration parameters for performing the at least one action for at least one of the network device or at least one neighboring network device.
The second apparatus of any of claims 10-18, wherein the input data comprises at least one of the following:

at least one geographic area associated with the energy usage modification;

at least one network node associated with the energy usage modification;

at least one power supplier associated with the energy usage modification;

history information of at least one power limited event associated with the energy usage modification;

at least one status of the backup battery charge or discharge for the network device;

at least one type of the at least one backup battery;

at least one performance measurement of the network device;

at least one configuration management parameter of at least one of the network device or at least one neighboring network device;

at least one fault management of the network device; or

analytics provided by a management data analytics service (MDAS) .
A method comprising:

transmitting, to a second apparatus, a request for an energy usage modification associated with at least one backup battery or uninterruptible power supply (UPS) of a network device based on a power limited event of the network device; and

receiving, from the second apparatus, a report of the energy usage modification, wherein the report indicates at least one of the following: (i) a predicted duration of the power limited event for the network device and an importance level of the power limited event, or (ii) at least one action of the network device to prolong a service duration of the at least one backup battery.
A method comprising:

receiving, from a first apparatus, a request for an energy usage modification associated with at least one backup battery or uninterruptible power supply (UPS) of a network device based on a power limited event of the network device;

based on receiving the request, collecting input data for performing the energy usage modification;

deriving output data of the energy usage modification based on the collected input data, wherein the output data comprises at least one of the following: (i) a predicted duration of the power limited event for the network device and an importance level of the power limited event, or (ii) at least one action of the network device to prolong a service duration of the at least one backup battery; and

transmitting, to the first apparatus, a report of the energy usage modification comprising the output data.
A first apparatus comprising:

means for transmitting, to a second apparatus, a request for an energy usage modification associated with at least one backup battery or uninterruptible power supply (UPS) of a network device based on a power limited event of the network device; and

means for receiving, from the second apparatus, a report of the energy usage modification, wherein the report indicates at least one of the following: (i) a predicted duration of the power limited event for the network device and an importance level of the power limited event, or (ii) at least one action of the network device to prolong a service duration of the at least one backup battery.
A second apparatus comprising:

means for receiving, from a first apparatus, a request for an energy usage modification associated with at least one backup battery or uninterruptible power supply (UPS) of a network device based on a power limited event of the network device;

means for collecting input data for performing the energy usage modification based on receiving the request;

means for deriving output data of the energy usage modification based on the collected input data, wherein the output data comprises at least one of the following: (i) a predicted duration of the power limited event for the network device and an importance level of the power limited event, or (ii) at least one action of the network device to prolong a service duration of the at least one backup battery; and

means for transmitting, to the first apparatus, a report of the energy usage modification comprising the output data.
A non-transitory computer readable medium comprising program instructions for causing an apparatus to perform at least a method of claim 20 or 21.