Methods and systems for managing energy efficiency based on availability performance

Abstract

Methods and systems for managing energy efficiency based on availability performance are provided. Embodiments herein disclose a mechanism for determining Energy Efficiency (EE) of a cell in a gNodeB based on its availability performance, which includes determining a number of in-service active cells in the gNB and determining an average energy consumption per cell in the gNB. Embodiments herein disclose a mechanism for determining EE of a Radio Access Network (RAN) sub-network based on its availability performance, which includes determining a number of in-service active cells in the entire RAN sub-network and determining an average energy consumption per cell of the entire RAN sub-network.

Description

METHODS AND SYSTEMS FOR MANAGING ENERGY EFFICIENCY BASED ON AVAILABILITY PERFORMANCE

[0001] Embodiments disclosed herein relate to wireless communication networks, and more particularly to managing energy efficiency in wireless communication networks based on availability performance.

[0002] A typical Fifth Generation (5G) system comprises of 5G Access Network (AN), 5G Core Network (CN) and User Equipment (UE) (see TS 23.501). The 5G system is expected to be able to provide optimized support for a variety of different communication services, different traffic loads, and different end-user communities. For example, the communication services using network slicing may include Vehicle-to-everything (V2X)　services, 5G seamless Enhanced Mobile Broadband (eMBB), massive Internet of Things (IoT) connections, and so on.

[0003] The 5G system aims to enhance its capability to meet Key Performance Indicators (KPIs) that are required by emerging V2X applications. For these applications, the requirements (such as, but not limited to, data rate, reliability, latency, communication range and speed, and so on) are made more stringent.

[0004] As 5G seamless eMBB is one of the key technologies to enable network slicing, fixed mobile convergence (FMC) which includes wireless-to-the-everything (WTTx) and fibre-to-the-everything (FTTx), is expected to provide native support for network slicing. For optimization and resource efficiency, the 5G system will select the most appropriate 3rdGeneration Partnership Project (3GPP) or non-3GPP access technology for a communication service, potentially allowing multiple access technologies to be used simultaneously for one or more services active on a UE.

[0005] Support for massive Internet of Things (mIoT) brings many new requirements in addition to Mobile Broadband (MBB) enhancements. Communication services with massive IoT connections (such as, but not limited to, smart households, smart grid, smart agriculture, smart meters, and so on) will require the support of a large number and high density IoT devices to be efficient and cost effective.

[0006] Operators can use one or more network slice instances to provide these communication services, which require similar network characteristics, to different vertical industries. 3GPP TS 28.530 and 28.531 defines the management of network slices in 5G networks. 3GPP TS 28.530 and 28.531 also defined the concept of communication services, which are provided using one or more network slices. Network slicing is the key feature of the 5G networks and enables to build dedicated logical networks on a shared infrastructure. These dedicated networks would permit the implementation of tailor-made functionality and network operation specific to the needs of each slice customer, rather than a one-size-fits-all approach as witnessed in the current and previous mobile generations, which would not be economically viable. The slicing enables provisioning network resources at runtime for a specific purpose. The slices can be short-lived (for example, an exclusive slice providing eMBB service to the broadcast service provider to cover the football match in a particular stadium at a particular time). Some slices can be long-lived in nature (for example, a slice providing eMBB service to a hospital). A Network Slice Instance (NSI) may support multiple Communication Service Instances (CSI). Similarly, a CSI may utilize multiple NSIs. GST (Generic Slice Template) is used to provide a standardized list of attributes that can characterize a type of network slice.

[0007] Closed control loops are defined where there is no direct involvement of a human operator or other management entity in the control loop, the control loop is fully automated. The human operator or management entity is not directly controlling the details inside the process steps, but provides control outside the loop. For example, configuring goals for the control loop to make autonomous decisions within the boundaries of the set goal. Once the control loop is configured with the goal, the controlled entity is adjusted according to the set goals. In a closed control loop, the input to the control loop can be provided by a human operator or another management entity which includes the goal or policies. The output of the closed control loop may include the closed control loop status to a human operator or other management entity. Typically, the goal is set within certain parameter boundaries, the closed control loop can automatically monitor the network and ascertain if the defined goals are being breached. If the goal is breached the loop can re-configure the network to mitigate the breach.

[0008] Telecommunication networks energy efficiency (EE) KPIs are defined by various Standards Development Organizations (SDOs) and are of various natures. Generally, EE KPI is defined as the ratio between performance and energy consumption. The performance may be measured based on for example, data volume, latency, availability, number of active users, and so on. The EE KPIs can be applied to one of whole networks (i.e., end-to-end), sub-networks (e.g., radio access network), single network elements; or telecommunication sites (which contain network elements and site equipment).

[0009] In TS 28.310 (and TS 28.554), the existing EE KPIs (i.e., Next Generation - Radio Access Network (NG-RAN) Energy Efficiency (EE) and 5G Core (5GC) EE) only consider the aspect of data volume, latency and number of active IoT users; but not the other network performance aspects (such as, but not limited to, availability); i.e., there is no mechanism to evaluate and judge energy efficiency in network based on availability performance such as of cell in a gNB or of RAN subnetwork. For example, two gNBs may have similar EE evaluation results using the EE KPI which uses Data Volume (DV) as the performance indicator, but the user-experienced service quality of these two serving gNBs may vary largely because of availability of cell(s) or network(s). It is not feasible to consider availability based energy efficiency performance in selecting a gNB or RAN slice-subnet, while creating a slice as per customer requirements. Further, there is no method to determine how much average energy consumption per cell in a gNB or in a RAN subnetwork is there in a network.

[0010] To enhance the EE KPIs as more comprehensive in different network scenarios, it is needed to consider the availability performance aspect. Currently, there is no mechanism to evaluate and judge energy efficiency in the network based on availability performance such as of cell in a gNB or of RAN subnetwork as a whole.

[0011] Hence, there is a need in the art for solutions which will overcome the above mentioned drawback(s), among others.

[0012] The principal object of embodiments herein is to disclose a mechanism for determining Energy Efficiency (EE) of a cell in a gNodeB based on its availability performance, which includes determining a number of in-service active cells in the gNB and determining an average energy consumption per cell in the gNB.

[0013] Another object of embodiments herein is to disclose a mechanism for determining EE of a Radio Access Network (RAN) sub-network based on its availability performance, which includes determining a number of in-service active cells in the RAN sub-network and determining an average energy consumption per cell of the RAN sub-network.

[0014] Another object of embodiments herein is to disclose methods and systems for enabling a Management service (MnS) producer to manage energy efficiency in wireless communication networks, wherein availability based energy efficiency performance can be considered in selecting a gNB or RAN slice-subnet while creating a slice as per customer requirements.

[0015] Another object of embodiments herein is to disclose methods and systems for enabling a MnS consumer to perform EE optimization in its network if the availability based EE SLA is breached or is about to be breached.

[0016] These and other aspects of the embodiments herein will be better appreciated and understood when considered in conjunction with the following description and the accompanying drawings. It should be understood, however, that the following descriptions, while indicating at least one embodiment and numerous specific details thereof, are given by way of illustration and not of limitation. Many changes and modifications may be made within the scope of the embodiments herein without departing from the spirit thereof, and the embodiments herein include all such modifications.

[0017] Embodiments herein are illustrated in the accompanying drawings, throughout which like reference letters indicate corresponding parts in the various figures. The embodiments herein will be better understood from the following description with reference to the following illustratory drawings. Embodiments herein are illustrated by way of examples in the accompanying drawings, and in which:

[0018] FIG. 1 is a block diagram of a network management system, according to embodiments as disclosed herein;

[0019] FIG. 2 is a flowchart depicting the process of managing the energy efficiency in the wireless communication network, according to embodiments as disclosed herein;

[0020] FIGs. 3A and 3B depicts the process of using the determined KPIs of availability based Energy Efficiency per cell in a gNB or RAN subnetwork, for performing NSI allocation, according to embodiments as disclosed herein; and

[0021] FIGs. 4A and 4B depict the procedure for performing availability based energy efficiency KPI optimization, according to embodiments as disclosed herein.

[0022] The embodiments herein and the various features and advantageous details thereof are explained more fully with reference to the non-limiting embodiments that are illustrated in the accompanying drawings and detailed in the following description. Descriptions of well-known components and processing techniques are omitted so as to not unnecessarily obscure the embodiments herein. The examples used herein are intended merely to facilitate an understanding of ways in which the embodiments herein may be practiced and to further enable those of skill in the art to practice the embodiments herein. Accordingly, the examples should not be construed as limiting the scope of the embodiments herein.

[0023] For the purposes of interpreting this specification, the definitions (as defined herein) will apply and whenever appropriate the terms used in singular will also include the plural and vice versa. It is to be understood that the terminology used herein is for the purposes of describing particular embodiments only and is not intended to be limiting. The terms "comprising", "having" and "including" are to be construed as open-ended terms unless otherwise noted.

[0024] The words / phrases "exemplary", "example", "illustration", "in an instance", "and the like", "and so on", "etc.", "etcetera", "e.g.," , "i.e.," are merely used herein to mean "serving as an example, instance, or illustration." Any embodiment or implementation of the present subject matter described herein using the words / phrases "exemplary", "example", "illustration", "in an instance", "and the like", "and so on", "etc.", "etcetera", "e.g.," , "i.e.," is not necessarily to be construed as preferred or advantageous over other embodiments.

[0025] Embodiments herein may be described and illustrated in terms of blocks which carry out a described function or functions.　These blocks, which may be referred to herein as managers, units, modules, hardware components or the like, are physically implemented by analog and / or digital circuits such as logic gates, integrated circuits, microprocessors, microcontrollers, memory circuits, passive electronic components, active electronic components, optical components, hardwired circuits and the like, and may optionally be driven by a firmware. The circuits may, for example, be embodied in one or more semiconductor chips, or on substrate supports such as printed circuit boards and the like.　The circuits constituting a block may be implemented by dedicated hardware, or by a processor (e.g., one or more programmed microprocessors and associated circuitry), or by a combination of dedicated hardware to perform some functions of the block and a processor to perform other functions of the block.　Each block of the embodiments may be physically separated into two or more interacting and discrete blocks without departing from the scope of the disclosure.　Likewise, the blocks of the embodiments may be physically combined into more complex blocks without departing from the scope of the disclosure.

[0026] It should be noted that elements in the drawings are illustrated for the purposes of this description and ease of understanding and may not have necessarily been drawn to scale. For example, the flowcharts / sequence diagrams illustrate the method in terms of the steps required for understanding of aspects of the embodiments as disclosed herein. Furthermore, in terms of the construction of the device, one or more components of the device may have been represented in the drawings by conventional symbols, and the drawings may show only those specific details that are pertinent to understanding the present embodiments so as not to obscure the drawings with details that will be readily apparent to those of ordinary skill in the art having the benefit of the description herein. Furthermore, in terms of the system, one or more components / modules which comprise the system may have been represented in the drawings by conventional symbols, and the drawings may show only those specific details that are pertinent to understanding the present embodiments so as not to obscure the drawings with details that will be readily apparent to those of ordinary skill in the art having the benefit of the description herein.

[0027] The accompanying drawings are used to help easily understand various technical features and it should be understood that the embodiments presented herein are not limited by the accompanying drawings. As such, the present disclosure should be construed to extend to any modifications, equivalents, and substitutes in addition to those which are particularly set out in the accompanying drawings and the corresponding description. Usage of words such as first, second, third etc., to describe components / elements / steps is for the purposes of this description and should not be construed as sequential ordering / placement / occurrence unless specified otherwise.

[0028] Hereinafter, embodiments of the disclosure will be described in detail with reference to the accompanying drawings.

[0029] In describing the embodiments, descriptions related to technical contents well-known in the art and not associated directly with the disclosure will be omitted. Such an omission of unnecessary descriptions is intended to prevent obscuring of the main idea of the disclosure and more clearly transfer the main idea.

[0030] For the same reason, in the accompanying drawings, some elements may be exaggerated, omitted, or schematically illustrated. Further, the size of each element does not completely reflect the actual size. In the drawings, identical or corresponding elements are provided with identical reference numerals or different reference numerals.

[0031] The advantages and features of the disclosure and ways to achieve them will be apparent by making reference to embodiments as described below in detail in conjunction with the accompanying drawings. However, the disclosure is not limited to the embodiments set forth below, but may be implemented in various different forms. The following embodiments are provided only to completely disclose the disclosure and inform those skilled in the art of the scope of the disclosure, and the disclosure is defined only by the scope of the appended claims. Throughout the specification, the same or like reference numerals designate the same or like elements. Furthermore, in describing the disclosure, a detailed description of known functions or constitution incorporated herein will be omitted in the case that it is determined that the description may make the subject matter of the disclosure unnecessarily unclear. The terms which will be described below are terms defined in consideration of the functions in the disclosure, and may be different according to users, intentions of the operators, or customs. Therefore, the definitions of the terms should be made based on the contents throughout the specification.

[0032] Herein, it will be understood that each block of the flowchart illustrations, and combinations of blocks in the flowchart illustrations, may be performed based on computer program instructions. These computer program instructions may be loaded individually or collectively onto at least one processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which perform through any one of, or in any combination of, the at least one processor of the computer or other programmable data processing apparatus, create means for performing the functions specified in the flowchart block(s). These computer program instructions may also be stored in a non-transitory computer usable or computer-readable memory that may direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer usable or computer-readable memory produce an article of manufacture including instruction means that perform the function specified in the flowchart block(s). The computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable data processing apparatus to produce a computer executed process such that the instructions that perform on the computer or other programmable data processing apparatus provide steps for executing the functions specified in the flowchart block(s).

[0033] Further, each block may represent a module, segment, or portion of code, which includes one or more executable instructions for executing the specified logical function(s). It should also be noted that in some alternative implementations, the functions noted in the blocks may occur out of the order. For example, two blocks (or functions) shown in succession may in fact be performed substantially concurrently or the blocks may sometimes be performed in the reverse order, depending upon the functionality involved.

[0034] As used in embodiments of the disclosure, a "~unit / module" may refer to a software element or a hardware element, such as a field programmable gate array (FPGA) or an application specific integrated circuit (ASIC), which performs a predetermined function. However, the term including the word "~unit / module" does not always have a meaning limited to software or hardware. The "~unit / module" may be constructed either to be stored in an addressable storage medium or to execute one or more processors. Therefore, the "~unit / module" includes, for example, software elements, object-oriented software elements, components such as class elements and task elements, processes, functions, properties, procedures, sub-routines, segments of a program code, drivers, firmware, micro-codes, circuits, data, database, data structures, tables, arrays, and parameters. The components and functions provided by the "~unit / module" may be either combined into a smaller number of components and a "~unit / module," or divided into additional components and a "~unit / module." Moreover, the components and "~units / module" may be implemented to reproduce one or more central processing units (CPUs) within a device or a security multimedia card. Further, in the embodiments, the "unit / module" may include one or more processors.

[0035] The entirety of the one or more computer programs may be stored in a single memory device, or the one or more computer programs may be divided with different portions stored in different multiple memory devices.

[0036] Any of the functions or operations described herein can be processed by one processor or a combination of processors. The one processor or the combination of processors is circuitry performing processing and includes circuitry like an application processor (AP, e.g. a CPU), a communication processor (CP, e.g., a modem), a graphics processing unit (GPU), a neural processing unit (NPU) (e.g., an artificial intelligence (AI) chip), a Wi-Fi chip, a Bluetooth chip, a global positioning system (GPS) chip, a near field communication (NFC) chip, connectivity chips, a sensor controller, a touch controller, a finger-print sensor controller, a display driver integrated circuit (IC), an audio CODEC chip, a universal serial bus (USB) controller, a camera controller, an image processing IC, microprocessors, microcontrollers, digital　signal processors, FPGA, ASIC, a microprocessor unit (MPU), a system on chip (SoC), an IC, or the like. The one processor or the combination of processors executes instructions that can be stored in a memory, such as the　operating system, in order to control the overall operation of the device.　Also, the one processor or the combination of processors is also capable of executing other processes and programs　resident in the memory, such as processes for the disclosure.

[0037] It will be appreciated that various embodiments of the disclosure according to the claims and description in the specification can be realized in the form of hardware, software or a combination of hardware and software.

[0038] Any such software may be stored in non-transitory computer readable storage media. The non-transitory computer readable storage media store one or more computer programs (software modules), the one or more computer programs include computer-executable instructions that, when executed by one or more processors of an electronic device individually or collectively, cause the electronic device to perform a method of the disclosure. Additionally, or alternatively, such software may be a computer program [product] comprising instructions which, when executed by one or more processors of an electronic device individually or collectively, cause the electronic device to perform a method of the disclosure.

[0039] Any such software may be stored in the form of volatile or non-volatile storage such as, for example, a storage device like read only memory (ROM), whether erasable or rewritable or not, or in the form of memory such as, for example, random access memory (RAM), memory chips, device or integrated circuits or on an optically or magnetically readable medium such as, for example, a compact disk (CD), digital versatile disc (DVD), magnetic disk or magnetic tape or the like. It will be appreciated that the storage devices and storage media are various embodiments of non-transitory machine-readable storage that are suitable for storing a computer program or computer programs comprising instructions that, when executed, implement various embodiments of the disclosure. Accordingly, various embodiments of the present disclosure may provide a program comprising code for implementing apparatus or a method as claimed in any one of the claims of this specification and a non-transitory machine-readable storage storing such a program.

[0040] Hereinafter, the determination of priority between A and B in the present disclosure may refer to various actions such as selecting the one having a higher priority based on a predefined priority rule and performing an operation corresponding thereto, or omitting or dropping an operation corresponding to the one having a lower priority.

[0041] Hereinafter, "A or B" as described in the present disclosure may be understood as "A and / or B," which may include A, or B, or both A and B.

[0042] In addition, "at least one of A, B, and C" as described in the present disclosure may be understood to include A, or B, or C, or any combination of A, B, and C.

[0043] In addition, "at least one of A, B, or C" as described in the present disclosure may be understood to include A, or B, or C, or any combination of A, B, and C.

[0044] Furthermore, "A / B" as described in the present disclosure may be understood as "A and / or B," which may include A, or B, or both A and B.

[0045] Furthermore, "A, B" as described in the present disclosure may be understood as "A and / or B," which may include A, or B, or both A and B.

[0046] Furthermore, "A and B" as described in the present disclosure may be understood as "A and / or B," which may include A, or B, or both A and B.

[0047] Furthermore, "if condition A and condition B are satisfied," as described in the present disclosure, may not be limited to a case where both condition A and condition B are satisfied, but may be understood to include a case where either condition A or condition B is individually satisfied, both condition A and condition B are satisfied, or one or more additional conditions are satisfied in combination.

[0048] Furthermore, throughout this disclosure, ordinal terms such as "first," "second," "third," etc., (and similar qualifiers) are used merely to distinguish between different instances, occurrences, configurations, messages, stages, elements or aspects of elements, operations, or information as described herein. Unless the context clearly dictates otherwise, the use of such ordinal terms does not itself require that the elements, operations, or information distinguished by these terms be structurally different, numerically distinct, or substantively dissimilar. For example, a "first signal" and a "second signal" may refer to instances of the same signal transmitted at different times or containing the same core information despite minor variations, or they may refer to signals with different content or characteristics, depending on the specific context. Similarly, a "first value" and a "second value" may represent the same magnitude but measured or applied in different circumstances, or they may represent different magnitudes. The interpretation should be guided by the specific technical context, function, and relationship described in the relevant portion of the specification and claims.

[0049] Furthermore, the terms "first ~", "second ~", etc., as described in the present disclosure with respect to various elements (e.g., information, objects, operation, sequences, or the like), should not limit those elements. These terms may only be intended to distinguish one element from another, and may not be intended to indicate a specific order. For example, a first element could be termed a second element, and, similarly, a second element could be termed a first element.

[0050] Furthermore, even if "first ~" and "second ~" are described in the present disclosure, it may be understood that element(s) referred to by "first ~" and "second ~" may be the same or different. For example, in case of element(s) being information, first information and second information may both be the same information, and, in some cases, are separate and different information.

[0051] In addition, the terms "if ~" and "in case that ~" as used in the disclosure or claims may be interpreted to include the meanings of "when (or upon) ~," "in response to ~," "based on ~," or "according to ~," and may be used interchangeably with these expressions. In addition, expressions other than those exemplified herein may also be used, as long as they have substantially the same meaning and do not impair the technical features of the present disclosure. If a method step (e.g., transmit a signal) is performed according to the disclosure of the application in connection with one of the above terms (such as "in case that ~" or the like), it may be interpreted to include the meanings (disclosure) of a prior determination that a feature has a specific state "~" (e.g., a bit length is above X), and then perform the method step in response to said determination.

[0052] In addition, the term "not perform" as used in the present disclosure or claims may, in context, be understood to mean that the corresponding step is omitted or skipped. Such a term may be replaced with other terms having the same or substantially equivalent meaning.

[0053] In addition, "transmitting a message including A and B" as described in the present disclosure, may be understood as encompassing both (i) transmitting A and B in a single message, and (ii) transmitting A and B separately via multiple messages (e.g., transmitting a first message including A and a second message including B). This interpretation may also apply to messages that include two or more items (e.g., A, B, C), transmitted either together or separately.

[0054] In addition, "transmitting a message including A and transmitting a message including B" may also be interpreted as transmitting a message including A and B in a single message.

[0055] In the specific embodiments of the present disclosure described below, terms or components included in the disclosure may be expressed in singular or plural form depending on the specific embodiments presented. However, such singular or plural expressions are selected appropriately for convenience of description, and the present disclosure is not limited to a singular or plural number of components. A component expressed in the plural form may be implemented as a single component, and a component expressed in the singular form may be implemented as multiple components.

[0056] The drawings or flowcharts described below illustrate example methods that may be implemented according to the principles of the present disclosure, and various modifications may be made to the methods illustrated in the flowcharts of the present disclosure. For example, although illustrated as a series of steps, various steps in each drawing or flowchart may overlap, occur in parallel, occur in a different order, or be repeated. In other examples, any step may be omitted or replaced with another step.

[0057] The process of the flowchart may be performed by a device. One or more of the steps of the　flowchart can be implemented by one or more processors / computer programs executing　instructions to perform the noted functions.

[0058] The methods and apparatuses proposed in the embodiments of the present disclosure may be disclosed in connection with drawings disclosing flowcharts to illustrate example methods that may be implemented according to the principles of the present disclosure. Such flowcharts may contain different branches and / or sub-branches. It is understood that the principles of the present disclosure do not only contain the combination of all branches / sub-branches disclosed in the embodiment, but the present disclosure also contains at least one isolated branch / isolated sub-branch, in particular to a single branch / single sub-branch.

[0059] The methods and apparatuses proposed in the embodiments of the present disclosure are not limited to each embodiment individually, but may also be applied in combination of all or some of the embodiments proposed in the disclosure. Therefore, the embodiments of the present disclosure may be modified and applied without significantly departing from the scope of the present disclosure, as would be understood by those skilled in the art.

[0060] In this case, even if certain wordings are described differently across embodiments, they may be used interchangeably or in substitution or in combination if their underlying concepts are equivalent. For example, for the same or equivalent concept, even if one embodiment uses the expression "A" and another embodiment uses the expression "B", such expressions may be understood interchangeably, in substitution, or in combination.

[0061] The terms used in the following description to refer to access nodes, network entities, messages, interfaces between network entities, various types of identification information, and the like, are provided merely for the convenience of explanation by way of example. Therefore, the present disclosure is not limited to the terms described below, and other terms having equivalent technical meanings may also be used. Such terms may also be interchangeable with terms defined in any 3rd generation partnership project　(3GPP) technical specifications (TS) or similar technical specifications, e.g., from ETSI, where appropriate.

[0062] Hereinafter, a base station (BS) is an entity that allocates resources to terminals, and may be at least one of a gNodeB, an eNodeB, a NodeB, a wireless access unit, a BS controller, or a node on a network.

[0063] Furthermore, the base station of the present disclosure may include a split architecture comprising a central unit (CU) and a distributed unit (DU). In this structure, the CU is configured to process the higher layers of the control and user planes, while the DU is configured to process lower-layer radio resource functions. The embodiments of the present disclosure may be equally applicable to 5G base station architectures in which such CU and DU functional splits are implemented.

[0064] A terminal may include a UE, a mobile station (MS), a cellular phone, a smartphone, a computer, a tablet, a wearable device, an Internet of Things (IoT) device, or any other device / system capable of performing communication functions.

[0065] In the disclosure, a downlink (DL) refers to a radio link through which a BS transmits a signal to a terminal, and an uplink (UL) refers to a radio link through which a terminal transmits a signal to a BS.

[0066] Furthermore, hereinafter, 5th generation (5G) mobile communication technologies (e.g., 5G new radio (NR)), 6th generation (6G) mobile communication technologies may be described by way of example, but the embodiments of the present disclosure may also be applied to other communication systems having similar technical backgrounds or channel types. For example, newly evolved mobile communication systems developed after 5G and 6G may be included. Furthermore, based on determinations by those skilled in the art, the embodiments of the present disclosure may also be applied to other communication systems (e.g., Wi-Fi systems) through some modifications without significantly departing from the scope of the present disclosure

[0067] In the following description, the terms physical channel and signal may be used interchangeably with data or control signal. For example, the term physical downlink shared channel (PDSCH) refers to a physical channel through which data is transmitted, but the term PDSCH may also be used to refer to the data itself. That is, in the present disclosure, the expression "transmit a physical channel" may be interpreted as being equivalent to the expression "transmit data or a signal via a physical channel."

[0068] Hereinafter, in the context of the present disclosure, higher layer signaling may refer to signaling corresponding to at least one or any combination of the following: master information block (MIB), system information block (SIB) or SIB M (M = 1, 2, ...), radio resource control (RRC), or medium access control (MAC) control element (CE), or a non-access stratum (NAS) signaling message, or an application layer message. The RRC signaling message may be referred to as Layer 3 (L3) signaling.

[0069] In addition, Layer 1 (L1) signaling may refer to signaling corresponding to at least one or any combination of signaling techniques using the at least one or any combination of the following physical layer channels or signaling: physical downlink control channel (PDCCH), downlink control information (DCI), user equipment (UE)-specific DCI, group-common DCI, common DCI, scheduling DCI (e.g., DCI used for scheduling downlink or uplink data), non-scheduling DCI (e.g., DCI not used for scheduling downlink or uplink data) physical uplink control channel (PUCCH), or uplink control information (UCI). The L1 signaling message may be referred to as a physical layer signaling.

[0070] For example, the physical layer signaling (i.e., L1 signaling) may include downlink control information (DCI). In addition, the higher layer signaling may include a medium access control (MAC) control message, a radio resource control (RRC) signaling message, a non-access stratum (NAS) signaling message, or an application layer message. The RRC signaling message may be referred to as L3 signaling. It should be noted, however, that the higher layer signaling is not limited to the aforementioned examples.

[0071] Hereinafter, the expression that information is configured by the BS, as used in the present disclosure or claims, may, in context, be understood to mean that the terminal receives the corresponding information from the BS via a physical layer signaling or a higher layer signaling. Such an expression may be replaced with other terms having the same or substantially equivalent meaning.

[0072] Hereinafter, the operational principle of the present disclosure will be described in detail with reference to the accompanying drawings.

[0073] The embodiments herein achieve methods and systems for determining energy efficiency in wireless communication networks based on availability performance of a cell in a gNodeB(gNB), and / or of the Radio Access Network (RAN) subnetwork as a whole. Referring now to the drawings, and more particularly to FIGS. 1 through 4B, where similar reference characters denote corresponding features consistently throughout the figures, there are shown embodiments.

[0074] Energy efficiency (EE) Key Performance Indicator (KPI) is defined as a ratio between a network performance aspect and its corresponding energy consumption. The performance may be a data volume, latency, number of active users etc. Embodiments herein disclose EE KPIs in terms of cell and RAN availability performance aspect of a network. To achieve this, embodiments herein disclose two new Energy consumption (EC) KPIs per cell in a gNB and in a RAN subnetwork level respectively. Embodiments herein disclose two new measurements for number of in-service active cells at gNB and RAN subnetwork level. The EE KPIs can be used for managing energy efficiency in networks, wherein availability based energy efficiency performance can be considered in selecting a gNB or RAN slice-subnet while creating a slice. The KPI information can also be used to perform EE optimization in network if the availability based EE service level agreement (SLA) is breached or is about to be breached.

[0075] 3GPP TS 28.310 defines high-level mobile network data EE KPIs and solutions for assessment of mobile network EE. A number of different EE KPIs have been defined in 3GPP TS 28.554 in previous 3GPP releases. Most of the EE metrics (i.e. NG-RAN Energy Efficiency and 5GC Energy Efficiency) only consider the aspect of data volume, but not the other network performance aspect such as availability. For example, two gNBs may have similar EE evaluation results using the EE KPI which uses Data Volume (DV) as the performance indicator, but the user experienced service quality of these two serving gNBs may vary largely because of availability of cell or network. It is not feasible to consider availability based energy efficiency performance in selecting a gNB / RAN slice-subnet while creating a slice as per customer requirements. Further there is no method to determine how much average energy consumption per cell in a gNB / CU or in a RAN subnetwork is there in a network. To enhance the EE KPIs as more comprehensive in different network scenarios, it is needed to consider availability performance aspect. Currently there is no mechanism to evaluate and judge energy efficiency in network based on availability performance such as of cell in a gNB / CU or of RAN subnetwork as a whole.

[0076] Energy Efficiency (EE) in mobile communication networks is the ratio between performance and energy consumption (EC) of the entity under consideration. In the present disclosure, new Energy Efficiency (EE) KPIsin terms of celland RANavailability performance aspect of a network are defined. To achieve this further twonew Energy consumption (EC) KPIs of a celland RAN sub-network, and two new measurements for number of in-service active cells at gNB / CU and RAN subnetwork level are defined. The performance dimension of new Energy Efficiency KPIs, i.e. the numerator part of the formula of new EE KPIs, are evaluated from availability performance of a network as reflected by some existing KPIs in 3GPP TS 28.554[2].

[0077] Embodiments herein disclose a mechanism for determining EE of a cell in a gNB based on its availability performance, which includes determining a number of in-service active cells in a gNB and determining an average energy consumption per cell in the gNB. Embodiments herein disclose a Key Performance Indicator (KPI) to obtain EE of a cell in the gNB based on its availability performance. Embodiments herein disclose a performance measurement in the network to determine number of "In-Service" active cells in the gNB. Embodiments herein disclose a KPI to obtain average energy consumption per cell in the gNB.

[0078] Embodiments herein disclose a mechanism for determining EE of a RAN sub-network based on its availability performance, which includes determining a number of in-service active cells in the RAN sub-network level and determining an average energy consumption per cell at the RAN sub-network. Embodiments herein disclose a KPI to obtain Energy Efficiency of the RAN sub-network based on its availability performance. Embodiments herein disclose a performance measurement in the network to determine number of "In-Service" active cells in the RAN sub-network. Embodiments herein disclose a KPI to obtain average energy consumption per cell of the RAN sub-network.

[0079] Embodiments herein enable a Management service (MnS) producer to manage energy efficiency in wireless communication networks, wherein availability based energy efficiency performance can be considered in selecting a gNB or RAN slice-subnet while creating a slice as per customer requirements. Embodiments herein enable a MnS consumer to perform EE optimization in its network if the availability based EE SLA is breached or is about to be breached.

[0080] Embodiments herein disclose methods and systems for managing energy efficiency in wireless communication networks, wherein availability based energy efficiency performance can be considered in selecting a gNB or RAN slice-subnet while creating a slice as per customer requirements. Embodiments herein can perform EE optimization accordingly if the availability based EE SLA has been breached or is about to be breached in a network.

[0081] Energy Efficiency (EE) in mobile communication networks is the ratio between performance and energy consumption (EC) of the entity under consideration. Embodiments herein define new Energy Efficiency (EE) Key Performance Indicators (KPIs) in terms of cell and RAN sub-network availability performance aspect of a network. To achieve this, further two new Energy consumption (EC) KPIs of per cell in a gNB and in a RAN subnetwork level, and two new measurements for number of in-service active cells at gNB and RAN subnetwork level are defined. The performance dimension of new Energy Efficiency KPIs, i.e. the numerator of new EE KPIs, are evaluated from availability performance of a network as reflected by some existing KPIs in 3GPP TS 28.554.

[0082] Availability performance KPIs that currently exist are Cell Availability KPI, and Radio access network availability KPI.

[0083] Embodiments herein disclose two new number of In-Service active cells measurements, two new Energy consumption KPIs and two new Energy Efficiency KPIs. Embodiments herein define a performance measurement to determine number of "In-Service" active cells in a gNB. Embodiments herein define a performance measurement to determine number of "In-Service" active cells in a RAN sub-network. Embodiments herein define a new KPI to obtain average energy consumption per cell in a gNB. Embodiments herein define a new KPI to obtain the average energy consumption per cell of a RAN sub-network. Embodiments herein define a new KPI to obtain Energy Efficiency of a cell in a gNB based on its availability performance. Embodiments herein define a new KPI to obtain Energy Efficiency of an entire RAN sub-network based on its availability performance.

[0084] A Measurement definition template is defined in clause 3.3 of TS 32.404, and KPI definition template is defined in clause 5 of TS 28.554. In an embodiment, the proposed measurements and KPIs description as per the standard template include:

[0085] Measurements:

[0086] 1. Number of "In-Service" active cells in a gNB:

[0087] a) This measurement (Ncellinservice) provides the total number of active cells in a gNB which are having Service Status as In-Service. Each gNB-DU reports the Service Status of the Active cells to the gNB-CU. The Service Status is the state of the radio transmission over the air. If the Service Status value is "In-Service" it means the active cell is operational, and the cell is able to serve UEs. A gNB-DU reports the Service Status to a gNB-CU using the GNB-DU CONFIGURATION UPDATE message that includes the cell(s) that are In-Service (TS 38.401 clause 8.5, TS 38.473 clause 8.2.4.2).

[0088] b) DER

[0089] c) Reception of GNB-DU CONFIGURATION UPDATE message(s) by the gNB during a given time duration / period and counting (uniquely) the number of active cells whose Service Status is present as In-Service in this message(s).

[0090] d) Each measurement can be a single integer value.

[0091] e) Ncellinservice

[0092] f) GNBCUCPFunction, ManagedElement, ManagedFunction

[0093] g) Valid for packet switching

[0094] h) 5GS

[0095] 2. Number of "In-Service" active cells in a RAN sub-network:

[0096] a) This measurement (NcellinserviceRAN) provides the total number of active cells which are having Service Status as In-Service considering all constituting gNB of a RAN subnetwork level. Each gNB-DU reports the Service Status of the Active cells to its gNB-CU. The Service Status is the state of the radio transmission over the air. If the Service Status value is "In-Service" it means the active cell is operational, and the cell is able to serve UEs. A gNB-DU reports the Service Status to gNB-CU using the GNB-DU CONFIGURATION UPDATE message that includes the cell(s) that are In-Service (TS 38.401 clause 8.5, TS 38.473 clause 8.2.4.2).

[0097] b) DER

[0098] c) Reception of GNB-DU CONFIGURATION UPDATE message(s) by all constituting gNB in a RAN subnetwork during a given time duration / period and counting (uniquely) the number of active cells whose Service Status is present as In-Service in a gNB and then summing up all such counts of all constituting gNB of the RAN sub-network.

[0099] d) Each measurement is a single integer value.

[0100] e) NcellinserviceRAN

[0101] f) SubNetwork, ManagedElement

[0102] g) Valid for packet switching

[0103] h) 5GS

[0104] KPIs:

[0105] 1. Average energy consumption per cell in a gNB:

[0106] a) ECavgcellgNBCU

[0107] b) This KPI (ECavgcellgNBCU) describes the average energy consumption per cell in a gNB. ECavgcellgNBCUcan be obtained by considering energy consumption of gNB for a given time duration / period and dividing it by total number of cells (Ncellinservice) in a gNB that are operational in same time duration / period. Ncellinserviceis the total number of active cells in a gNB whose Service Status are In-Service. The unit of this KPI is kWh or Joule. The KPI type is MEAN.

[0108] c) The formula for ECavgcellgNBCUis as follows:

[0109]

[0110] where,

[0111] can be obtained as per clause 5.1.1.19.3 of TS 28.552 or as per clause 6.7.3.4.2 or clause 6.7.3.1 of TS 28.554.

[0112] is as defined in TS 28.552 or as per clause 8.2.4.2 of TS 38.473 or clause 8.5 of TS 38.401.

[0113] d) GNBCUCPFunction, ManagedElement, ManagedFunction

[0114] 2. Average energy consumption per cell of RAN sub-network:

[0115] a) ECavgcellRAN

[0116] b) This KPI (ECavgcellRAN) describes the average energy consumption per cell of a RAN sub-network. It is obtained by summing the energy consumption of all constituting gNB in a RAN subnetwork for a given time duration / period and dividing it by the total number of cells (NcellinserviceRAN) in a RAN sub-network that are operational in the same time duration / period. NcellinserviceRANis the total number of active cells of all constituting gNB in RAN sub-network whose Service Status are In-Service during the same time duration / period. The unit of this KPI is kWh or Joule. The KPI type is MEAN.

[0117] c) The formula for ECavgcellRANis as follows:

[0118]

[0119] where,

[0120] is NG-RAN EC as defined in clause 6.7.3.4.1 of TS 28.554.

[0121] is as defined in TS 28.552 or as per clause 8.2.4.2 of TS 38.473, or clause 8.5 of TS 38.401.

[0122] d) SubNetwork, ManagedElement

[0123] 3. Energy Efficiency of a cell in a gNB based on its availability performance:

[0124] a) EECellAvailAvg

[0125] b) This KPI (EECellAvailAvg) describes the energy efficiency of a cell in a gNB based on its average availability. It is obtained by considering Cell Availability (average availability time duration per cell in a gNB-CU) in the numerator and dividing it by the average energy consumption per cell in a gNB over the same observation period. The unit of this KPI is seconds per joule (Sec / J) or seconds per kWh (Sec / kWh). The KPI type is MEAN.

[0126] c) The formula for EECellAvailAvgis as follows:

[0127]

[0128] where,

[0129] is the Cell Availability KPI as defined in TS 28.554, clause 6.10.1.1.1

[0130] is the average energy consumption per cell in a gNB

[0131] d) GNBCUCPFunction, ManagedElement, ManagedFunction

[0132] 4. Energy Efficiency of a RAN sub-network based on its availability performance:

[0133] a) EERANAvailAvg

[0134] b) This KPI (EERANAvailAvg) describes the energy efficiency of a RAN subnetwork based on its average availability. It is obtained by considering Radio access network availability (average availability time duration per cell of an entire RAN subnetwork) in the numerator and dividing it by the average energy consumption per cell in the RAN sub-network over the same observation period. The unit of this KPI is seconds per joule (Sec / J) or seconds per kWh (Sec / kWh). The KPI type is MEAN.

[0135] c) The formula for EERANAvailAvgis as follows:

[0136]

[0137] where,

[0138] is the Radio access network availability KPI as defined in TS 28.554 clause 6.10.1.1.2.

[0139] is the average energy consumption per cell in a RAN sub-network.

[0140] d) SubNetwork, ManagedElement

[0141] A terminal or a base station may perform various communication procedures related to the control plane or the user plane by cooperating with one or more network entities based on wireless communication. For example, the terminal may communicate with a network management system (for example, a gNB, a gNB-CU, a MnS consumer, a MnS producer, etc.) via the base station, or the base station may perform at least one communication procedure by directly transmitting and receiving signals to / from, or relaying signals between, the network entities.

[0142] The structure of the above-described network entity will be described in more detail with reference to the drawings.

[0143] FIG. 1 is a block diagram of a network management system 100. The network management system 100 may include an entity (apparatus, device, or server, etc.) that performs one or more network functions (NFs) or a part of a network function constituting a core network (e.g., a 5th generation (5G) core (5GC)) in a communication system. In this case, multiple NFs may be implemented within a single network management system, or a single NF may be distributed and implemented across a plurality of network entities. In addition, when an NF is implemented within the network management system, the NF may be implemented in the form of software, and in such a case, a program for operating the NF may be stored in memory of the network management system 100.

[0144] A single NF may be implemented by one or more instances, which may be deployed on the same network management system or distributed across multiple network entities to operate. The instance may be a software unit that logically executes a specific network function, and may be implemented in a form that is decoupled from physical hardware resources. Further, one or more NFs may be implemented in the form of one network slice to operate to satisfy specifications required by a particular service.

[0145] The NF may include at least one of a gNodeB (gNB), a gNB-CU (Centralized Unit), a Management Service (MnS) consumer, a MnS producer, etc.

[0146] Referring to FIG. 1, the network management system 100 may include at least one network interface 101, at least one processor 102 (hereinafter, "processor"), and at least one memory 103 (hereinafter, "memory"). As described above, a NF may be implemented in the form of a physical device such as the network management system 100, or may be virtualized and executed in the form of an instance. When implemented as an instance, the NF need not necessarily include physical components as illustrated in FIG. 1. In such a case, the instance may be logically represented as comprising one or more logical functional elements.

[0147] According to at least one or a combination of methods corresponding to the embodiments described in the present disclosure, the network interface 101, the processor 102, and the memory 103 of the network management system 100 may operate. However, components of the network management system 100 are not limited to the example components illustrated in FIG. 1. In another embodiment, the network management system 100 may further include additional components in addition to the above-mentioned components, or some components may be omitted. Further, in an embodiment, the network interface 101, the processor 102, or the memory 103 may be integrated in the form of one component.

[0148] The network interface 101 is a collective term for a transmitter part of the network management system 100 and a receiver part of the network management system 100, and may be a communication circuit for transmitting or receiving a signal to or from a terminal, a base station (BS), or another network management system. Here, the communication circuit may include both a communication circuit for wireless communication and a communication circuit for a wired communication. For example, the network interface 101 may include a circuit, logic, hardware, etc., configured to exchange a control plane message or a user plane message with a terminal, a BS, or other core network entities through wireless communication or wired communication. The network interface 101 may operate using various protocols (e.g., non-access stratum (NAS) protocol). The network interface 101 may also be referred to, for convenience of description or depending on implementation, as communication circuitry, network interface circuitry, or a communication interface circuitry.

[0149] The processor 102 may control general operations of the network management system 100 according to embodiments of the disclosure. The processor 102 may be implemented by one or more integrated circuit (or circuitry) (IC) chips and may execute various data processing. The processor 102 may include at least one electric circuit, and may execute instructions (or a program, codes, data, etc.) stored in the memory 103, individually, collectively or in any combination thereof. Further, the processor 102 may include a single-core processor or multi-core processor, and may include a processor assembly including a plurality of processing circuits (circuitry) according to a specific implementation scheme. Further, it should be noted that, according to another embodiment, in a case where NF is implemented in the form of an instance, the network function may be not necessarily configured by physical hardware.

[0150] According to an embodiment, the processor 102 may be electrically, operatively, and / or communicatively coupled to the network interface 101 to control the network interface 101.

[0151] The processor 102 may include at least one processor (or processing circuitry), and the at least one processor may perform the following operations individually, collectively or in any combination thereof. In a specific embodiment, at least a part of the processor 102 may be included in one chip and the other part of the processor 102 may be included in another chip. Otherwise, at least one processor may be included in another component, for example, the network interface 101 or the memory 103.

[0152] The processor 102 may perform or control or cause an operation of the network management system 100 for executing at least one or a combination of methods according to embodiments of the disclosure. For example, the processor 102 may control operations of the network management system 100 for exchanging a control plane message or a user plane message with a terminal, a BS, or other core network entities through wireless or wired communication, using various protocols (e.g., NAS protocol). To this end, the processor 102 may execute a computer program, codes, or instructions stored in the memory 103, so as to control other components of the network management system 100 to enable execution of various operations.

[0153] The memory 103 corresponds to a hardware storage device capable of temporarily or permanently storing information and may include one or more storage media. For example, the memory 103 may include a memory assembly including one or more storage media. For example, the one or more storage media may include permanent memory, such as a hard drive, flash memory, or read-only memory (ROM), semipermanent memory, such as random access memory (RAM), cache memory, or a combination thereof.

[0154] The memory 103 may be electrically, operatively, and / or communicatively coupled to the processor 102 and may be accessed by the processor 102.

[0155] The memory 103 may store a computer program, codes, or instructions executable by the processor 102. According to an embodiment, a computer program, codes, or instructions executable by the processor 102 may be either stored in a single memory device or separated and stored in a distributed manner in two or more memory devices. By executing the instructions stored in the memory 103, the processor 102 may perform various functions according to an embodiment of the disclosure.

[0156] According to an embodiment of the disclosure, operations of the network management system 100 may be caused to be performed based on execution of instructions (or a computer program or codes) stored in the memory 103 by at least one processor (or processing circuitry) configured to execute the same individually, collectively, or in any combination thereof, based on processing circuitry that is not configured to execute instructions, and / or based on components of processing circuitry that is not configured to execute instructions.

[0157] The processor 102 can manage the energy efficiency in the wireless communication network comprising one or more gNodeBs (gNBs) and at least one radio access network (RAN) sub-network. The processor 102 can collect availability metrics and energy consumption metrics associated with cells of a gNB or RAN sub-network during an observation period. Based on the collected metrics, the processor 102 can determine availability-based energy efficiency key performance indicators for at least one of a cell; and a RAN sub-network.

[0158] The processor 102 can obtain the availability-based energy efficiency key performance indicator of a cell in the gNB by dividing a cell availability metric by the average energy consumption per cell in the gNB. The processor 102 can determine the average energy consumption per cell in the gNB by dividing energy consumption of gNB for the observation period by total number of In-Service cells in the gNB during the same observation period.

[0159] The processor 102 can obtain the availability-based energy efficiency key performance indicator of a RAN subnetwork by dividing Radio access network availability with the average energy consumption per cell in the RAN subnetwork. The processor 102 can determine the average energy consumption per cell in the RAN subnetwork by summing the energy consumption of all constituting gNBs in the RAN subnetwork for the observation period and dividing it by the total number of In-Service cells of all constituting gNBs in a RAN sub-network during the same observation period. The processor 102 can determine the total number of In-Service cells during the observation period in the gNB comprises identifying the total number of active cells in the gNB which are having Service Status as In-Service. The processor 102 can determine the total number of In-Service cells during the observation period in the RAN subnetwork as the total number of active cells in all constituting gNBs of the RAN subnetwork which are having Service Status as In-Service.

[0160] The processor 102 can store the availability-based energy efficiency key performance indicators in the memory 103.

[0161] Using the availability-based energy efficiency key performance indicators, the processor 102 can select a gNB or RAN slice-subnet for network slice allocation. The processor 102 can select the gNB having a highest availability-based energy efficiency key performance indicator of a cell as the gNB for network slice allocation. The processor 102 can select the RAN slice-subnet having a highest availability-based energy efficiency key performance indicator of the RAN subnetwork as the RAN sub-subnet for slice creation.

[0162] Based on the availability-based energy efficiency key performance indicators of a cell or RAN subnetwork, the processor 102 can performing energy efficiency optimization in the network. The energy efficiency optimization based on availability-based energy efficiency key performance indicators of the cell or the RAN subnetwork comprises at least one of, modifying radio or hardware related configurations of the gNB or creation of AssuranceClosedControlLoop (ACCL) MOI to assure the availability based energy efficiency goal in the network.

[0163] FIG. 2 is a flowchart depicting the process of managing the energy efficiency in the wireless communication network. In step 201, the network management system 100 collects availability metrics and energy consumption metrics associated with cells of a gNB or RAN sub-network during the observation period.

[0164] Based on the collected metrics, in step 202, the network management system 100 determines availability-based energy efficiency key performance indicators for at least one of a cell; or a RAN sub-network. The network management system 100 determines the availability-based energy efficiency key performance indicator of a cell in the gNB by dividing a cell availability metric by the average energy consumption per cell in the gNB. The network management system 100 determines the average energy consumption per cell in the gNB by dividing energy consumption of gNB for the observation period by total number of In-Service cells in the gNB during the same observation period. The network management system 100 determines the availability-based energy efficiency key performance indicator of a RAN subnetwork by dividing RAN availability with the average energy consumption per cell in the RAN subnetwork. The network management system 100 determines the average energy consumption per cell in the RAN subnetwork by summing the energy consumption of all constituting gNBs in the RAN subnetwork for the observation period and dividing it by the total number of In-Service cells of all constituting gNBs in a RAN sub-network during the same observation period. The network management system 100 determines the total number of In-Service cells during the observation period in the gNB comprises identifying the total number of active cells in the gNB which are having Service Status as In-Service. The network management system 100 determines the total number of In-Service cells during the observation period in the RAN subnetwork as the total number of active cells in all constituting gNBs of the RAN subnetwork which are having Service Status as In-Service.

[0165] In step 203, the network management system 100 stores the availability-based energy efficiency key performance indicators in the network management system 100.

[0166] Using the availability-based energy efficiency key performance indicators, in step 204, the network management system 100 selects a gNB or RAN slice-subnet for network slice allocation. The network management system 100 selects the gNB having a highest availability-based energy efficiency key performance indicator of a cell as the gNB for network slice allocation. The network management system 100 selects the RAN slice-subnet having a highest availability-based energy efficiency key performance indicator of the RAN subnetwork as the RAN slice-subnet for slice creation.

[0167] Based on the availability-based energy efficiency key performance indicators of the cell or the RAN subnetwork, in step 205, the network management system 100 performs energy efficiency optimization in the network. The energy efficiency optimization based on availability-based energy efficiency key performance indicators of the cell or the RAN subnetwork comprises at least one of, modifying RF (radio frequency) or hardware related configurations of gNB or creation of ACCL MOI to assure the availability based energy efficiency goal in the network. The various actions in method 200 may be performed in the order presented, in a different order or simultaneously. Further, in some embodiments, some actions listed in FIG. 2 may be omitted.

[0168] FIGs. 3A and 3B depicts the process of creation of a network slice as per NSI allocation procedure using the determined KPIs of Energy Efficiency per cell in a gNB or RAN subnetwork, based on their availability performance. As depicted in FIG. 3A, based on the availability based energy efficiency of cells, the MnS Consumer can select the best gNB or RAN slice-subnet as per EE KPI (availability based) and use the selected gNB or Ran slice subnet to create a customer requested network slice.

[0169] In step 301, a Performance Assurance (PA) MnS Consumer sends a createMOI request, as defined in 3GPP TS 28.532, for PerfMetricJob IOC to a PA MnS producer. The request will contain required new measurements and KPIs (as defined herein) as attributes of PerfMetricJob IOC. In step 302, the PA MnS producer responds back with a createMOI response. In step 303, the PA MnS producer collects the required performance metrics (i.e., measurements and KPIs) from the network. In step 304, the required metrics values are provided by the PA MnS producer to the PA MnS consumer. In step 305, the PA MnS stores these metrics for further usage and necessary actions. In step 306, the General provisioning MnS consumer sends a AllocateNsi request to the provisioning MnS producer. Using information of EE KPIs (as stored in step 305), in step 307, the provisioning MnS producer selects the gNB or RAN slice-subnet with the highest EE KPI to be used for network slice allocation. This ensures that the gNB or RAN slice-subnet with the highest availability based EE KPI will be used in slice creation as per the consumer's request. In step 308, the NSI allocation procedure is carried out for creation of the network slice (as defined in TS 28.531).

[0170] FIGs. 4A and 4B depict the procedure for performing energy efficiency optimization. In step 401, the network slice is provisioned as per the procedures defined in 3GPP TS 28.531 with the availability based EE SLA as provided in the service profile. In step 402, the MnS Consumer sends a createMOI request, as defined in 3GPP TS 28.532, for PerfMetricJob IOC to PA (Performance Assurance) MnS producer. The request will contain required new measurements and KPIs (as disclosed herein) as attributes of the PerfMetricJob IOC. In step 403, the PA MnS producer responds back with the createMOI response. In step 404, the PA MnS producer collects the required performance metrics values (i.e., measurements and KPIs) from the network. In step 405, the required metrics values are provided from the PA MnS producer to the MnS consumer. Based on the received performance metric values, in step 406, the MnS consumer decides to perform energy efficiency optimization. There may be two possibilities; wherein the SLA has been breached, and SLA may be breached, as depicted in FIGs. 4A and 4B respectively.

[0171] As depicted in FIG. 4A, if the MnS consumer sees that the SLA 'is' breached, in step 407, the MnS consumer sends a modifyMOIAttributes request to a generic provisioning MnS producer in order to update one or more attributes in for example, NRCellDU, NRSectorCarrier or NRFrequency IOCs. In step 408, the modifyMOIAttributes response is sent from the generic provisioning MnS producer to the MnS consumer.

[0172] As depicted in FIG. 4B, if the MnS consumer sees that the SLA 'may be' breached in near future, then in step 409, the MnS consumer sends a createMOI request for AssuranceClosedControlLoop IOC to ACCL (Assurance Closed Control Loop) producer requesting the initiation of a closed control loop as defined in TS 28.536. The assurance goal can be set to initial availability based EE SLA as provided in service profile in step 401. In step 410, the createMOI response is sent from the ACCL producer to the MnS consumer indicating the successful creation of the closed control loop. The created CCL will work to assure the availability based Energy efficiency goal as defined in TS 28.536.

[0173] Embodiments herein enable measurement and monitoring of the availability based Energy Efficiency KPI of a cell in a gNB and in an entire RAN sub-network. Embodiments herein enable measurement and monitoring of the average energy consumption per cell in a gNB and in an entire RAN sub-network. Embodiments herein can analyze availability based EE KPI for its optimization and for using it as information in selecting best possible gNB or RAN slice-subnet in network slice creation. Embodiments herein enable a consumer to decide which attributes (such as, but not limited to, attributes of NRCellDU, NRSectorCarrier, NRFrequency, and so on) are to be updated for increasing availability of the cell (if required). Embodiments herein can now know which all and how many cells are in "In-Service" status in a gNB and in entire RAN subnetwork level.

[0174] The KPI is defined from a network availability performance dimension perspective. Energy efficiency of cell is provided based on availability. For example, the following parameters are provided.

[0175] a) EECell,AvailAvgTimeCU

[0176] b) A KPI that shows the energy efficiency of a cell in a gNB based on availability performance. This KPI is obtained by dividing cell availability KPI by the average energy consumption per cell in a gNB over the same observation period. The unit of this KPI is sec / J.

[0177] c)

[0178] d) GNBCUCPFunction

[0179] e) The cell availability KPI is defined in clause 6.10.1.1.1. The average energy consumption per cell in a gNB is obtained by considering energy consumption of gNB (ECgNB) for a given time period and dividing it by total number of cells in a gNB that are operational in same time duration / period. ECgNBis defined in clause 6.7.3.4.2.

[0180] Most of the EE KPIs (i.e. NG-RAN EE KPI and 5GC EE KPI) only consider the aspect of data volume, but not other network performance aspects. For example, two RAN base stations can have similar EE evaluation results using the EE KPI based on DV, but the RAN UE throughput or cell availability of these two serving base stations can be very different.

[0181] To enhance the EE KPIs to be more comprehensive in different network scenarios, it is needed to also consider other KPIs for EE evaluation. In the present disclosure, measuring and monitoring the availability-based Energy Efficiency KPI of a cell in a gNB are provide. In the present disclosure, new KPIs to obtain Energy Efficiency of a cell in a gNB / CU based on its availability performance and to obtain average energy consumption per cell in a gNB / CU are provided.

[0182] Meanwhile, although specific embodiments of the present disclosure have been described in detail, various modifications may be made without departing from the scope of the present disclosure. Therefore, the scope of the present disclosure should not be limited to the described embodiments, but should be defined by the claims and equivalents thereof.

[0183] According to embodiments, a method for managing energy efficiency in a wireless communication network comprising one or more gNodeBs (gNBs) and at least one radio access network (RAN) sub-network is provided. The method being performed by a network management system comprises collecting availability metrics and energy consumption metrics associated with cells of a gNB or RAN sub-network during an observation period; determining, based on the collected metrics, availability-based energy efficiency key performance indicators for at least one of a cell; and a RAN sub-network; storing the availability-based energy efficiency key performance indicators in a memory of the network management system; selecting, using the availability-based energy efficiency key performance indicators, a gNB or RAN slice-subnet for network slice allocation; and performing energy efficiency optimization in the network based on the availability-based energy efficiency key performance indicators of a cell or RAN subnetwork.

[0184] For example, the availability-based energy efficiency key performance indicator of a cell in the gNB is obtained by dividing a cell availability metric by the average energy consumption per cell in the gNB.

[0185] For example, determining the average energy consumption per cell in the gNB comprises dividing energy consumption of the gNB for the observation period by total number of in-service cells in the gNB during the observation period.

[0186] For example, the availability-based energy efficiency key performance indicator of the RAN subnetwork is obtained by dividing RAN availability with the average energy consumption per cell in the RAN subnetwork.

[0187] For example, determining the average energy consumption per cell in the RAN subnetwork comprises summing the energy consumption of all constituting gNBs in the RAN subnetwork for the observation period and dividing it by the total number of in-service cells of all constituting gNBs in the RAN sub-network during the observation period.

[0188] For example, determining total number of in-service cells during the observation period in the gNB comprises identifying the total number of active cells in the gNB which are having Service Status as In-Service.

[0189] For example, determining the total number of in-service cells during the observation period in the RAN subnetwork comprises identifying the total number of active cells in all constituting gNBs of the RAN subnetwork which are having Service Status as In-Service.

[0190] For example, the gNB for slice creation is selected having a highest availability-based energy efficiency key performance indicator of a cell.

[0191] For example, the RAN slice-subnet for slice creation is selected having a highest availability-based energy efficiency key performance indicator of the RAN subnetwork.

[0192] For example, the energy efficiency optimization based on availability-based energy efficiency key performance indicators of the cell or the RAN subnetwork comprises at least one of, modifying Radio Frequency (RF) or hardware related configurations of gNB or creation of AssuranceClosedControlLoop (ACCL) MOI to assure the availability based Energy efficiency goal in the network.

[0193] According to embodiments, a network management system is provided. The network management system comprises a processor; a network interface; and a memory module. The processor is coupled with the network interface and the memory module, wherein the processor is configured to collect availability metrics and energy consumption metrics associated with cells of a gNodeB (gNB) or a Radio Access Network (RAN) sub-network during an observation period; determine, based on the collected metrics, availability-based energy efficiency key performance indicators for at least one of a cell; and a RAN sub-network; store the availability-based energy efficiency key performance indicators in a memory of the network management system; select, using the availability-based energy efficiency key performance indicators, a gNB or RAN slice-subnet for network slice allocation; and perform energy efficiency optimization in the network based on the availability-based energy efficiency key performance indicators of a cell or RAN subnetwork.

[0194] For example, the processor is configured to obtain availability-based energy efficiency key performance indicator of a cell in the gNB by dividing a cell availability metric by the average energy consumption per cell in the gNB.

[0195] For example, the processor is configured to determine the average energy consumption per cell in the gNB by dividing energy consumption of the gNB for the observation period by total number of in-service cells in the gNB during the observation period.

[0196] For example, the processor is configured to obtain the availability-based energy efficiency key performance indicator of the RAN subnetwork by dividing RAN availability with the average energy consumption per cell in the RAN subnetwork.

[0197] For example, the processor is configured to determine the average energy consumption per cell in the RAN subnetwork by summing the energy consumption of all constituting gNBs in the RAN subnetwork for the observation period and dividing it by the total number of in-service cells of all constituting gNBs in the RAN sub-network during the observation period.

[0198] For example, the processor is configured to determine the total number of in-service cells during the observation period in the gNB by identifying the total number of active cells in the gNB which are having Service Status as In-Service.

[0199] For example, the processor is configured to determine the total number of in-service cells during the observation period in the RAN subnetwork by identifying the total number of active cells in all constituting gNBs of the RAN subnetwork which are having Service Status as In-Service.

[0200] For example, the gNB for slice creation is selected having a highest availability-based energy efficiency key performance indicator of a cell.

[0201] For example, the RAN slice-subnet for slice creation is selected having a highest availability-based energy efficiency key performance indicator of the RAN subnetwork.

[0202] For example, the energy efficiency optimization based on availability-based energy efficiency key performance indicators of the cell or the RAN subnetwork comprises at least one of, modifying Radio Frequency (RF) or hardware related configurations of gNB or creation of AssuranceClosedControlLoop (ACCL) MOI to assure the availability based Energy efficiency goal in the network.

[0203] According to a method for managing energy efficiency in a wireless communication network is provided. The method comprises collecting availability metrics and energy consumption metrics associated with cells during an observation period; determining, based on the collected metrics, availability-based energy efficiency key performance indicators for a cell; performing energy efficiency optimization in the network based on the availability-based energy efficiency key performance indicators.

[0204] According to a network management system is provided. The method comprises at least one processor; a network interface; and memory storing instructions. The at least one processor is coupled with the network interface and the memory, wherein the at least one processor is configured to collect availability metrics and energy consumption metrics associated with cells during an observation period; determine, based on the collected metrics, availability-based energy efficiency key performance indicators for a cell; perform energy efficiency optimization in the network based on the availability-based energy efficiency key performance indicators.

[0205] According to embodiments, a method for managing energy efficiency in a wireless communication network is provided. The method comprises determining, based on metrics, availability-based energy efficiency key performance indicators for a cell in a next generation node base station (gNB); and performing energy efficiency optimization in the network based on the availability-based energy efficiency key performance indicators.

[0206] For example, the availability-based energy efficiency key performance indicator of the cell is obtained by dividing a cell availability metric by an average energy consumption per cell in the gNB.

[0207] For example, the average energy consumption per cell in the gNB is determined based on dividing energy consumption of the gNB for the observation period by total number of In-Service cells in the gNB during the observation period.

[0208] The embodiments disclosed herein can be implemented through at least one software program running on at least one hardware device and performing network management functions to control the network elements. The elements include blocks which can be at least one of a hardware device, or a combination of hardware device and software module.

[0209] The embodiments disclosed herein describe methods and systems for determining energy efficiency in wireless communication networks based on availability performance of a cell in a gNB, and / or of the RAN subnetwork as a whole. Therefore, it is understood that the scope of the protection is extended to such a program and in addition to a computer readable means having a message therein, such computer readable storage means contain program code means for implementation of one or more steps of the method, when the program runs on a server or mobile device or any suitable programmable device. The method is implemented in at least one embodiment through or together with a software program written in e.g., Very high speed integrated circuit Hardware Description Language (VHDL) another programming language, or implemented by one or more VHDL or several software modules being executed on at least one hardware device. The hardware device can be any kind of portable device that can be programmed. The device may also include means which could be e.g., hardware means like e.g., an ASIC, or a combination of hardware and software means, e.g., an ASIC and an FPGA, or at least one microprocessor and at least one memory with software modules located therein. The method embodiments described herein could be implemented partly in hardware and partly in software. Alternatively, the invention may be implemented on different hardware devices, e.g., using a plurality of CPUs.

[0210] The foregoing description of the specific embodiments will so fully reveal the general nature of the embodiments herein that others can, by applying current knowledge, readily modify and / or adapt for various applications such specific embodiments without departing from the generic concept, and, therefore, such adaptations and modifications should and are intended to be comprehended within the meaning and range of equivalents of the disclosed embodiments. It is to be understood that the phraseology or terminology employed herein is for the purpose of description and not of limitation. Therefore, while the embodiments herein have been described in terms of embodiments and examples, those skilled in the art will recognize that the embodiments and examples disclosed herein can be practiced with modification within the scope of the embodiments as described herein.

[0211] It should be appreciated that various embodiments of the present disclosure and the terms used therein are not intended to limit the technological features set forth herein to particular embodiments and include various changes, equivalents, or replacements for a corresponding embodiment. With regard to the description of the drawings, similar reference numerals may be used to refer to similar or related elements. It is to be understood that a singular form of a noun corresponding to an item may include one or more of the things unless the relevant context clearly indicates otherwise. As used herein, each of such phrases as "A or B," "at least one of A and B," "at least one of A or B," "A, B, or C," "at least one of A, B, and C," and "at least one of A, B, or C," may include any one of or all possible combinations of the items enumerated together in a corresponding one of the phrases. As used herein, such terms as "1st" and "2nd," or "first" and "second" may be used to simply distinguish a corresponding component from another, and does not limit the components in other aspect (e.g., importance or order). It is to be understood that if an element (e.g., a first element) is referred to, with or without the term "operatively" or "communicatively", as "coupled with," or "connected with" another element (e.g., a second element), the element may be coupled with the other element directly (e.g., wiredly), wirelessly, or via a third element.

[0212] Various embodiments as set forth herein may be implemented as software including one or more instructions that are stored in a storage medium that is readable by a machine. For example, a processor of the machine may invoke at least one of the one or more instructions stored in the storage medium, and execute it, with or without using one or more other components under the control of the processor. This allows the machine to be operated to perform at least one function according to the at least one instruction invoked. The one or more instructions may include a code generated by a compiler or a code executable by an interpreter. The machine-readable storage medium may be provided in the form of a non-transitory storage medium. Wherein, the "non-transitory" storage medium is a tangible device, and may not include a signal (e.g., an electromagnetic wave), but this term does not differentiate between a case in which data is semi-permanently stored in the storage medium and a case in which the data is temporarily stored in the storage medium.

Claims

1.A method for managing energy efficiency in a wireless communication network comprising:determining, based on metrics, availability-based energy efficiency key performance indicators for a cell in a next generation node base station (gNB); andperforming energy efficiency optimization in the network based on the availability-based energy efficiency key performance indicators.2.The method of claim 1, wherein the availability-based energy efficiency key performance indicator of the cell is obtained by dividing a cell availability metric by an average energy consumption per cell in the gNB.3.The method of claim 2, wherein the average energy consumption per cell in the gNB is determined based on dividing energy consumption of the gNB for the observation period by total number of in-service cells in the gNB during the observation period.4.The method of claim 1, wherein the availability-based energy efficiency key performance indicator of the RAN subnetwork is obtained by dividing radio access network (RAN) availability with the average energy consumption per cell in a RAN subnetwork.5.The method of claim 4, wherein the average energy consumption per cell in the RAN subnetwork is determined based on summing the energy consumption of all constituting gNBs in the RAN subnetwork for the observation period and dividing it by the total number of in-service cells of all constituting gNBs in the RAN sub-network during the observation period.6.The method of claim 3, wherein the total number of in-service cells during the observation period in the gNB is determined based on identifying the total number of active cells in the gNB which are having Service Status as In-Service.7.The method of claim 5, wherein the total number of in-service cells during the observation period in the RAN subnetwork is determined based on identifying the total number of active cells in all constituting gNBs of the RAN subnetwork which are having Service Status as In-Service.8.The method of claim 1, comprising:selecting, using the availability-based energy efficiency key performance indicators, a gNB for network slice allocation; andwherein the gNB for network slice allocation is selected having a highest availability-based energy efficiency key performance indicator of a cell.9.The method of claim 1, comprising:selecting, using the availability-based energy efficiency key performance indicators, a RAN slice-subnet for network slice allocation; andwherein the RAN slice-subnet for network slice allocation is selected having a highest availability-based energy efficiency key performance indicator of the RAN subnetwork.10.The method of claim 1, wherein the energy efficiency optimization based on availability-based energy efficiency key performance indicators of the cell or the RAN subnetwork comprises at least one of, modifying Radio Frequency (RF) or hardware related configurations of gNB or creation of AssuranceClosedControlLoop (ACCL) MOI to assure the availability based Energy efficiency goal in the network.11.A network management system comprising:at least one processor;a network interface; andmemory storing instructions,wherein the instructions, when executed by the at least one processor, cause the at least one processor to:determine, based on metrics, availability-based energy efficiency key performance indicators for a cell in a next generation node base station (gNB); andperform energy efficiency optimization in the network based on the availability-based energy efficiency key performance indicators.12.The network management system of claim 11, wherein the processor is configured to obtain availability-based energy efficiency key performance indicator of the cell by dividing a cell availability metric by the average energy consumption per cell in the gNB.13.The network management system of claim 12, wherein the average energy consumption per cell in the gNB is determined based on dividing energy consumption of the gNB for the observation period by total number of in-service cells in the gNB during the observation period.14.The network management system of claim 11, wherein the availability-based energy efficiency key performance indicator of the RAN subnetwork is obtained by dividing radio access network (RAN) availability with the average energy consumption per cell in a RAN subnetwork.15.The network management system of claim 14, wherein the average energy consumption per cell in the RAN subnetwork is determined based on summing the energy consumption of all constituting gNBs in the RAN subnetwork for the observation period and dividing it by the total number of in-service cells of all constituting gNBs in the RAN sub-network during the observation period.

Images