Handling NES cell status change in wireless networks

Abstract

Embodiments of the present disclosure disclose a gNodeB (gNB) (104) and a method for handling Network Energy Saving (NES) cell status change in wireless networks. The gNB (104) is configured to detect a change in a current status of at least one NES feature of at least one NES cell (102). The current status of the at least one NES feature of the at least one NES cell (102) indicates an activation status of the at least one NES feature of the at least one NES cell (102). Further, the gNB (104) is configured to transmit information related to the change in the current status of the at least one NES feature, to a plurality of neighboring entities (110) of the at least one NES cell (102). The plurality of neighboring entities (110) of the at least one NES cell (102) performs one or more actions based on the current status of the at least one NES feature of the at least one NES cell (102).

Description

[0001] TITLE

[0002] HANDLING NES CELL STATUS CHANGE IN WIRELESS NETWORKS

[0003] CROSS-REFERENCE TO RELATED APPLICATION (S)

[0004]

[0001] This application claims priority to Indian non provisional application No. 202441070831, filed on September 19, 2024 the entire contents of which is incorporated herein by reference.

[0005] FIELD

[0006]

[0002] The present disclosure relates to handling Network Energy Saving (NES) cell status change in wireless networks.

[0007] BACKGROUND

[0008]

[0003] Network energy efficiency is a performance requirement in wireless networks. Consequently, Third Generation Partnership Project (3 GPP) standards are designed to enable low energy consumption, not only in user terminals, but also in network equipments. New features for energy savings (also termed as Network Energy Saving (NES) features) are introduced. For example, much longer durations and higher ratio of discontinuous transmission (DTX) is supported in New Radio (NR) compared to the 3GPP Long Term Evolution (LTE) standard. Also, the feature of transmitting System Information Blocks (SIBs) only on-demand is supported. Network energy saving is of great importance for environmental sustainability, to reduce environmental impact (greenhouse gas emissions), and for operational cost savings. Cells associated with the NES features (also termed as NES cells) stay in dormant state or sleep state to save energy. The NES cells stay in dormant state until a wake-up signal is received. The NES cells transmit SIBs to User Equipments (UEs) on receiving the wake-up signal.

[0004] SIBs are broadcast messages from a base station or a gNodeB (gNB) to the UEs that contain information relevant when evaluating whether a UE is allowed to access a cell and defines the scheduling of other system information. The SIB is a downlink broadcast information block transmitted periodically by the gNB. The SIB is very critical information for the UE to connect to the gNB. The UE needs SIB for cell camping when it is powered on, and for cell selection and cell reselection when the UE is in Radio Resource Control (RRC) IDLE / inactive mode. The SIB provides all necessary details like system frame number, system bandwidth, Public Land Mobile Network (PLMN), cell selection and re-selection thresholds, and the like, to access the network. 3 GPP Release 19 has a work item for Network Energy Savings with an objective to provide on-demand SIB1 (OD-SIB1) transmission to UEs by enabling NES cells to selectively broadcast SIB1 based on specific trigger via uplink wake-up signals using existing channels.

[0009]

[0005] A concept of a non-anchor NES cell without periodic SIB1 is introduced in 3GPP, where the UE is in coverage of an anchor cell and one or multiple non-anchor NES cell(s). An anchor cell is a cell where a UE is capable of receiving Synchronization Signal Block (SSB), system information and paging. A non- anchor NES cell without periodic SSB and SIB1 transmission is a cell where a UE receives neither SSB nor SIBl. The anchor cell periodically transmits at least its own SIBl to the UE. The non-anchor NES Cell transmits SIBl in response to a wake-up signal received from the UE.

[0010]

[0006] The information disclosed in this background section is only for enhancement of understanding of the general background of the disclosure and should not be taken as an acknowledgement or any form of suggestion that this information forms the prior art already known to a person skilled in the art.

[0011] SUMMARY

[0012]

[0007] In an embodiment, the present disclosure discloses a gNodeB (gNB). The gNB is configured to detect a change in a current status of at least one Network Energy Saving (NES) feature of at least one NES cell. The current status of the at least one NES feature indicates an activation status of the at least one NES feature of the at least one NES cell. Further, the gNB is configured to transmit information related to the change in the current status of the at least one NES feature, to a plurality of neighboring entities of the at least NES cell. The plurality of neighboring entities of the at least one NES cell performs one or more actions based on the current status of the at least one NES feature of the at least one NES cell.

[0013]

[0008] In an embodiment, the present disclosure discloses a method. The method comprises detecting, by a first entity associated with a gNodeB (gNB), a change in a current status of at least one Network Energy Saving (NES) feature of at least one NES cell. The current status of the at least one NES feature indicates an activation status of at least one NES feature of the at least one NES cell. Further, the method comprises transmitting, by the first entity, information related to the change in the current status of the at least one NES feature, to a plurality of neighboring entities of the at least one NES cell, via a second entity associated with the gNB. The plurality of neighboring entities of the at least one NES cell performs one or more actions based on the current status of the at least one NES feature of the at least one NES cell.

[0014]

[0009] In an embodiment, the present disclosure discloses a non-transitory computer readable medium including instructions for performing operations. The operations comprise detecting a change in a current status of at least one Network Energy Saving (NES) feature of at least one NES cell. The current status of the at least one NES feature indicates an activation status of the at least one NES feature of the at least one NES cell. Further, the method comprises transmitting information related to the change in the current status of the at least one NES feature of the at least one NES cell, to a plurality of neighboring entities of the at least one NES cell. The plurality of neighboring entities of the at least one NES cell performs one or more actions based on the current status of the at least one NES feature of the at least one NES cell. BRIEF DESCRIPTION OF THE DRAWINGS

[0015]

[0010] Features, aspects, and advantages of embodiments of the disclosure will be described below with reference to the accompanying drawings, in which like reference numerals denote like elements, and wherein:

[0016] [Oil] Figure 1A illustrates a current On Demand-System Information Block 1 (OD-SIB1) mechanism;

[0017]

[0012] Figure IB illustrates an exemplary environment for handling Network Energy Saving (NES) cell status change in wireless networks, in accordance with some embodiments of the present disclosure;

[0018]

[0013] Figure 2 illustrates a detailed diagram of a first entity associated with a gNodeB (gNB), in accordance with some embodiments of the present disclosure;

[0019]

[0014] Figure 3 illustrates an exemplary signaling diagram for handling NES cell status change in the wireless networks, in accordance with some embodiments of the present disclosure;

[0020]

[0015] Figure 4 shows an exemplary flow chart illustrating method steps for handling NES cell status change in the wireless networks, in accordance with some embodiments of the present disclosure; and

[0021]

[0016] Figure 5 shows a diagram of example components of the first entity for handling NES cell status change in the wireless networks, in accordance with embodiments of the present disclosure.

[0022] DETAILED DESCRIPTION

[0017] The following detailed description of example embodiments refers to the accompanying drawings. The foregoing disclosure provides illustration and description, but is not intended to be exhaustive or to limit the implementations to the precise form disclosed. Modifications and variations are possible in light of the above disclosure or may be acquired from practice of the implementations. Further, one or more features or components of one embodiment may be incorporated into or combined with another embodiment (or one or more features of another embodiment). Additionally, the flowchart and description of operations provided below relate to one of the various embodiments. It should be noted that it is possible to make other embodiments that do not exactly match the flowchart and its description. It is understood that in other embodiments one or more operations may be omitted, one or more operations may be added, one or more operations may be performed simultaneously (at least in part).

[0023]

[0018] It will be apparent that systems and / or methods described herein may be implemented in different forms of hardware, software, or a combination of hardware and software. The actual specialized control hardware or software code used to implement these systems and / or methods is not limiting of the implementations. Thus, the operation and behavior of the systems and / or methods are described herein without reference to specific software code. It is understood that software and hardware may be designed to implement the systems and / or methods based on the description herein.

[0024]

[0019] Even though particular combinations of features are recited in the claims and / or disclosed in the specification, these combinations are not intended to limit the disclosure of implementations. In fact, many of these features may be combined in ways not specifically recited in the claims and / or disclosed in the specification. Although each dependent claim listed below may directly depend on only one claim, the disclosure of implementations includes each dependent claim in combination with every other claim in the claim set.

[0020] No element, act, or instruction used herein should be construed as critical or essential unless explicitly described as such. Also, as used herein, the articles “a” and “an” are intended to include one or more items and may be used interchangeably with “one or more.” Also, as used herein, the terms “has,” “have,” “having,” “include,” “including,” or the like are intended to be open-ended terms. Further, the phrase “based on” is intended to mean “based, at least in part, on” unless explicitly stated otherwise. Furthermore, expressions such as “at least one of [A] and [B],” “[A] and / or [B],” or “at least one of [A] or [B]” are to be understood as including only A, only B, or both A and B.

[0025]

[0021] The foregoing disclosure provides illustration and description but is not intended to be exhaustive or to limit the implementations to the precise form disclosed. Modifications and variations are possible in light of the above disclosure or may be acquired from practice of the implementations.

[0026]

[0022] Third Generation Partnership Project (3 GPP) standards introduced new features for energy savings (also termed as Network Energy Saving (NES) features). For example, the NES features such as discontinuous transmission (DTX), on- demand System Information Block 1 (SIB1) transmission are supported. Cells associated with the NES features (also termed as NES cells) stay in dormant state or sleep state to save energy. The NES cells stay in dormant state until a wake-up signal is received. For instance, the wake-up signal may be received from User Equipments (UEs). The NES cells transmit SIB 1 to the UEs on receiving the wakeup signal.

[0027]

[0023] SIB1 is a broadcast message from a gNodeB (gNB) to the UEs that contain information relevant when evaluating whether a UE is allowed to access a cell and define the scheduling of other system information. The UE needs SIB 1 for camping on a cell , or for cell selection and cell re-selection when the UE is in Radio Resource Control (RRC) IDLE / inactive mode.

[0024] 3GPP Release 18 introduces the concept of “NES” Cell which includes On Demand SSB which is a Secondary Cell (SCell) in a Carrier Aggregation (CA) scenario, and On Demand SIB 1 where NES cells do not need to transmit SIB 1 when there is no UE data transmission in the cell, thereby allowing the cell to be in energy-saving mode.

[0028]

[0025] 3GPP Release 19 has a work item for NES with an objective to provide on- demand SIB1 (OD-SIB1) transmission to UEs in idle / inactive mode. This is studied by RANI, RAN2, and RAN3. The OD-SIB1 is provided by enabling NES cells to selectively broadcast SIB1 based on specific trigger via uplink wake-up signals using existing channels. For example, the trigger may be received from the UE.

[0029]

[0026] The objectives of 3GPP Release 19 related to NES is reproduced below:

[0030] 1. Specify procedures and signaling method(s) to support on-demand SSB SCell operation for UEs in connected mode configured with CA,for both intra-Zinter- band CA. [RAN1 / 2 / 3 / 4]

[0031] • Specify triggering method(s) (select from UE uplink wake-up-signal using an existing signal / channel, cell on / off indication via backhaul, Scell activation / deactivation signaling)

[0032] • Notel: On-demand SSB transmission can be used by UE for at least SCell time / frequency synchronization, L1 / L3 measurements and SCell activation, and is supported for FR1 and FR2 in non-shared spectrum.

[0033]

[0027] A concept of a non-anchor NES cell without periodic SIB1 is introduced in 3GPP, where the UE is in coverage of one or more anchor cells and one or multiple non-anchor NES cell(s). Figure 1A illustrates a current OD-SIB1 mechanism. An anchor cell, a NES cell, and a UE are illustrated in Figure 1 A. The anchor cell is a cell where the UE is capable of receiving Synchronization Signal Block (SSB), SIB1, and paging information. The anchor cell is also termed as “Cell A” in RAN1#116. The NES cell (also termed as a non-anchor NES cell) without periodic SSB and SIB1 transmission is a cell where the UE does not receive SSB and / or SIB1. The anchor cell periodically transmits its own SIB1 to the UE. The nonanchor NES Cell transmits SIB1 and / or SSB in response to an Uplink (UL) Wake- Up Signal (WUS) received from the UE.

[0034]

[0028] Generally, served cell information exchanged during Xn setup procedure and Fl setup procedure includes SCell information. The purpose of the Xn Setup procedure is to exchange application level configuration data needed for multiple gNBs or New Generation (NG)-Radio Access Network (RAN) nodes to interoperate correctly over Xn-C interface. The Fl setup procedure allows exchanging application-level data needed for gNB -Distributed Unit (DU) and gNB- Central Unit (CU) associated with a gNB to interoperate correctly over Fl interface.

[0035]

[0029] An activation and a deactivation of NES features of Release 19 (e.g.: OD- SIB1 and OD-SSB) needs to be notified to neighboring NG-RAN nodes and their respective gNB-DUs for the following reasons. When the NES features are active on a given SCell (also referred as NES SCell), the NES SCell cannot be used by the neighboring NG-RAN nodes for features like Dual Connectivity (DC), multiple Transmission and Reception Points (mTRP), interference mitigation, mobility load balancing, and the like. Further, performance monitoring and internal bookkeeping on the network side (at the neighboring RAN nodes) needs to factor in NES feature activation duration.

[0036]

[0030] Due to impact on the neighboring NG-RAN nodes, it is clear that activation and deactivation of the OD-SIB1 and the OD-SSB needs to be notified to the neighboring NG-RAN nodes . The NES features like OD-SIB1 and OD-SSB are dynamic in nature and are turned on and off by the gNB based on various factors such as a current usage, historical data, and the like. However, the activation and deactivation of the NES features of the NES cell configured in the gNB are not notified to the neighboring RAN nodes. This causes impact on neighboring RAN nodes and their respective gNB-DUs, as the information shared during the Xn setup procedure (between the NG-RAN nodes) and the Fl setup procedure (during cell setup) are temporarily invalid due to dynamic changes in the activation of the NES features.

[0037]

[0031] The present disclosure provides an apparatus and a method for handling NES cell status change in wireless networks. In the present disclosure, a first entity (gNB-DU) associated with a gNB detects a change in a current status of a NES cell. The first entity detects whether NES features of the NES cell are activated or deactivated. The first entity transmits information related to the change in the current status of the NES cell to neighboring entities of the NES cell. The neighboring entities include neighboring DU of the same gNB or neighboring gNBs and their respective DUs. Hence, the present disclosure enables dynamically notifying the neighboring entities of the change in the current status of the NES cell. The neighboring entities can take actions based on the current status of the NES cell. For instance, the neighboring entities perform configuration or deconfiguration of network functions such as handover, configures UEs to perform measurements of the NES cell or exclude the NES cell while performing the measurements, monitor performance of the NES cell based on a duration of activation of the NES features. Hence, the accuracy of performance monitoring Key Performance Indicators (KPIs) is improved. Further, the present disclosure enables increased efficiency of mobility performance, by enabling the neighboring entities to take actions based on the current status of the NES cell. Also, overhead is reduced in the network as neighboring NG-RAN nodes of the NES cell are notified on time.

[0038]

[0032] A disaggregated gNodeB (gNB) architecture is briefly described. In Fifth Generation (5G) networks, a base station or a gNB is split into three distinct components i.e., a Centralized Unit (CU) (also referred as the gNB-CU in the description), a Distributed Unit (DU) (also referred as the gNB-DU in the description), and a Remote Radio Unit (RU). The gNB-CU serves as central intelligence, adeptly handling complex and centralized network functions. These functions include, but are not limited to, proficient radio resource management, effective network control, and seamless coordination with the 5GC. The gNB-DU is responsible for managing data plane processing, encompassing vital tasks such as data transmission and reception with a User Equipment (UE). The gNB-DU interfaces seamlessly with the gNB-CU over Fl interface. Further, a control -plane gNB-CU-CP is connected to the gNB-DU through Fl-C interface. A user plane gNB-CU-UP is connected to the gNB-DU through Fl-U interface. The gNB-CU- CP is connected to gNB-CU-CP(s) over El interface. The RU deals with physical layer functions, housing antennas and radio transceivers that facilitate the actual transmission and reception of radio signals. The description of the present disclosure is explained considering Fifth Generation (5G) networks only. However, the present disclosure is applicable to any type of networks such as Fourth Generation (4G) networks, 6G networks, and the like.

[0039]

[0033] Figure IB illustrates an exemplary environment 100 for handling NES cell status change in wireless networks, in accordance with embodiments of the present disclosure. The exemplary environment 100 illustrates at least one Network Energy Saving (NES) cell 102, a gNodeB (gNB) 104, and a plurality of neighboring entities 110. The at least one NES cell 102 is associated with the gNB 104. The at least one NES cell 102 is a cell that stays in dormant state until a wake-up signal is received from User Equipments (UEs). The at least one NES cell 102 supports NES features such as On-Demand System Information Block 1 (OD SIB1) transmission, OD Synchronization Signal Block (SSB) transmission, and the like. The NES cell 102 transmits OD SIB 1 / SSB to the UEs on receiving the wake-up signal. In an embodiment, a single NES cell or multiple NES cells may be configured in the gNB 104. Figure IB illustrates only one NES cell 102 for simplicity purposes. The gNB 104 is associated with a first entity 106 and a second entity 108. In an embodiment, the first entity 106 may be a gNB-DU 106. The gNB-DU 106 may be associated with a serving cell camped on by a UE (not illustrated in Figures), and is responsible for managing data plane processing, data transmission and reception with the UE. The UE represents end-user devices that access services and applications through a wireless network. The UE is configured to connect to the first entity 106 and the second entity 108 over the wireless network. Examples of the UE include, but not limited to, any device used by a user to communicate over the wireless network, such as, but not limited to, mobile phones, smartphones, laptops, wearables, Internet of Things (loTs), and the like.

[0040]

[0034] In an embodiment, the second entity 108 may be a gNB-CU 108. The gNB- CU 108 serves as central intelligence handling complex and centralized network functions. The gNB-CU 108 manages multiple DUs in the wireless networks. Figure IB illustrates only one DU i.e., the gNB-DU 106 for explaining the present disclosure. However, the gNB-CU 108 can be associated with more than one DU, and this should not be considered as limiting. Similarly, the wireless network may include more than one CU, and thus should not be considered as limiting.

[0041]

[0035] In the present disclosure, the gNB 104 is configured to handle NES cell status change in the wireless networks. Herein, the first entity 106 associated with the gNB 104 detects a change in a current status of at least one NES feature of the at least one NES cell 102. The current status of the at least one NES feature of the at least one NES cell 102 indicates an activation status of the at least one NES feature of the at least one NES cell 102. For example, consider that the at least one NES feature was not activated in the at least one NES cell 102. Upon activating of the at least one NES features, there is a change in the current status of the at least one NES feature of the at least one NES cell 102. Then, the first entity 106 may transmit information related to the change in the current status of the at least one NES feature of the at least one NES cell 102, to a plurality of neighboring entities 110 of the at least one NES cell 102, via the second entity 108. The first entity 106 may transmit the information to the second entity 108 over Fl interface.

[0042]

[0036] The plurality of neighboring entities 110 may include a neighboring gNB- DU of the same gNB 104 or a neighboring gNB and their respective DUs. Figure IB illustrates gNBs neighboring to the gNB 104 as the plurality of neighboring entities 110. However, this should not be considered as limiting, and the plurality of neighboring entities 110 may also include neighboring gNB-DU of the same gNB 104. The information related to the change in the current status of the at least one NES feature of the at least one NES cell 102 is transmitted to each of the plurality of neighboring entities 110 of the at least one NES cell 102, via respective gNB-CU over Fl interface or Xn interface. For instance, the change in the current status of the at least one NES feature of the at least one NES cell 102 is transmitted to the neighboring gNB-DU of the same gNB 104 over Fl interface. The change in the current status of the at least one NES feature of the at least one NES cell 102 is transmitted to the neighboring gNBs (i.e., neighboring gNB CUs) over Xn interface. The neighboring gNB CUs may transmit the change in the current status of the at least one NES feature of the at least one NES cell 102 to respective DUs over Fl interface. The plurality of neighboring entities 110 of the at least one NES cell 102 performs one or more actions based on the current status of the at least one NES feature of the at least one NES cell 102. The one or more actions performed by the plurality of neighboring entities 110 are explained in detail in later part of the present description.

[0043]

[0037] Figure 2 illustrates a detailed diagram of the first entity 106, in accordance with some embodiments of the present disclosure. The first entity 106 may include Input / Output (VO) interface 202, a memory 204, and a Central Processing Unit (also referred as “CPU” or “a processor 206”). In some embodiments, the memory 204 may be communicatively coupled to the processor 206. The memory 204 stores instructions executable by the processor 206. The processor 206 may comprise at least one data processor for executing program components for executing user or system -generated requests. The memory 204 may be communicatively coupled to the processor 206. The memory 204 stores instructions, executable by the processor 206, which, on execution, may cause the processor 206 to handle the NES cell status change in the wireless networks. The VO interface 202 is coupled with the processor 206 through which an input signal or / and an output signal is communicated. For example, the first entity 106 transmits the information related to the change in the status of the at least one NES feature of the at least one NES cell 102 to the second entity 108, via the EO interface 202. In an embodiment, the first entity 106 may be implemented in a variety of computing systems, such as a server, a network server, a cloud-based server, and the like.

[0044]

[0038] In an embodiment, the memory 204 may include data 208. In one implementation, the data 208 may include, for example, detection data 210, transmission data 212, and other data 214.

[0045]

[0039] In an embodiment, the processor 206 is configured to detect a change in a current status of the at least one NES feature of the at least one NES cell 102. The current status of the at least one NES feature of the at least one NES cell 102 indicates an activation status of the at least one NES feature of the at least one NES cell 102. The activation status indicates one of an activation and a deactivation of the at least one NES feature. The at least one NES feature may include, but not limited to, OD SIB1 transmission and OD SSB transmission. In an embodiment, the at least one NES cell 102 may be configured in the gNB 104. The gNB 104 may be configured to activate the at least one NES feature of the at least one NES cell 102. The gNB 104 may decide to configure the at least one NES feature based on one or more factors. In an embodiment, the one or more factors may include a current usage, historical data, and the like. In an example, the gNB 104 may analyze from the historical data that network usage is low at night times. Hence, the gNB 104 may decide to activate the at least one NES feature for a pre-determined time (for example, between 12AM to 5 AM) in the night. In such a case, the current status of the at least one NES feature of the at least one NES cell 102 may change from a first status indicating a deactivation of the at least one NES feature to a second status indicating an activation of the at least one NES feature. The processor 206 may detect such a change in the current status of the at least one NES feature of the at least one NES cell 102. Referring to the above-stated example, the gNB 104 may deactivate the at least one NES feature at 5AM. In such a case, the current status of the at least one NES feature of the at least one NES cell 102 may change from a first status indicating an activation of the at least one NES feature to a second status indicating a deactivation of the at least one NES feature. The processor 206 may detect such a change in the current status of the at least one NES feature of the at least one NES cell 102.

[0046]

[0040] Referring to Figure 3A, as shown in block 1, at least one NES cell 102 is configured in the gNB 104. As shown in block 2, in one embodiment, the gNB-CU 108 decides to activate the at least one NES feature based on the one or more factors. In another embodiment, the gNB-DU 106 decides to activate the at least one NES feature based on the one or more factors In yet another embodiment, any other network entity decides to activate the at least one NES feature based on the one or more factors. The activation of the at least one NES feature deactivates the at least one NES cell 102, as the at least one NES cell 102 is in an energy saving mode. At step 3, the gNB-CU 108 transmits configuration update indicating activation of the at least one NES feature along with cell Identity (ID) of the NES cell 102. At step 4, the gNB-DU 106 configures the at least one NES cell 102 with the configuration update or activates the at least one NES feature at the at least one NES cell 102. Referring back to Figure 2, the change in the current status of the at least one NES feature of the at least one NES cell 102 may be stored as the detection data 210 in the memory 204. The present disclosure proposes detecting or monitoring a change in the activation status of the at least one NES feature of the at least one NES cell 102 so that timely actions can be taken at the neighboring NG-RAN nodes / neighboring DUs based on the activation status of the at least one NES feature of the at least one NES cell 102.

[0047]

[0041] In an embodiment, the processor 206 may be configured to transmit information related to the change in the current status of the at least one NES feature of the at least one NES cell 102 to a plurality of neighboring entities 110 of the at least one NES cell 102. In an embodiment, the processor 206 transmits the information related to the change in the current status of the at least one NES feature of the at least one NES cell 102 to the plurality of neighboring entities 110 via the second entity 108 (i.e., the gNB-CU 108). Herein, the processor 206 transmits the information related to the change in the current status of the at least one NES feature of the at least one NES cell 102 to second entity 108, over Fl interface. The second entity 108 transmits the information related to the change in the current status of the at least one NES feature of the at least one NES cell 102 to the plurality of neighboring entities 110 over Fl / Xn interface. For instance, the second entity 108 transmits the information related to the change in the current status of the at least one NES feature of the at least one NES cell 102 to a neighboring gNB-DU of the same gNB 104 over Fl interface. The second entity 108 transmits the information related to the change in the current status of the at least one NES feature of the at least one NES cell 102 to neighboring gNBs or NG-RAN nodes over Xn interface. Referring again to Figure 3, the processor 206 in the gNB-DU 106 transmits the configuration update indicating the change in the current status of the at least one NES feature of the at least one NES cell 102 to the gNB-CU 108, as shown in step 5. The gNB-CU 108 notifies the plurality of neighboring entities 110 by transmitting the configuration update indicating the change in the current status of the at least one NES feature of the at least one NES cell 102, as shown in block 6 and step 7. Referring back to Figure 2, data related to transmission of the change in the current status of the at least one NES feature of the at least one NES cell 102 is stored as the transmission data 212 in the memory 204.

[0048]

[0042] The plurality of neighboring entities 110 of the at least one NES cell 102 performs one or more actions based on the current status of the at least one NES feature of the at least one NES cell 102. The present disclosure improves network performance by enabling the plurality of neighboring entities 110 to take actions based on the current status of the at least one NES feature of the at least one NES cell 102. Also, overhead is reduced in the network as neighboring NG-RAN nodes of the at least one NES cell 102 are notified on time. The one or more actions performed by the plurality of neighboring entities 110 is explained in detail hereafter in the present description.

[0043] In an embodiment, the plurality of neighboring entities 110 perform configuration or deconfiguration of one or more network functions based on the current status of the at least one NES feature of the at least one NES cell 102. The one or more network functions may comprise at least one of, but not limited to, handover, Carrier Aggregation (CA), Dual Connectivity (DC), and Multiple Transmit / Receive Point (mTRP) operation. The handover may include Lower-layer Triggered Mobility (LTM) handover, Conditional Handover (CHO), Dual Active Protocol Stack (DAPS) Handover, and the like. The plurality of neighboring entities 110 may preclude or include the at least one NES cell 102 for performing the configuration or deconfiguration of the one or more network functions, based on the cun ent status of the at least one NES feature of the at least one NES cell 102. In an embodiment, some of the above-stated network functions are UE-specific features and due to unavailability (temporary) of the at least one NES cell 102, the at least one NES cell 102 is not considered for the UE. For example, the NES cell 102 is not considered when selecting a target cell for handover.

[0049]

[0044] In an embodiment, the one or more actions performed by the plurality of neighboring entities 110 may comprise updating a state of the at least one of NES cell 102 in a Neighbor Relation Table (NRT) associated with each of the plurality of neighboring entities 110. A state of the at least one NES cell 102 may be updated as an inactive state in the NRT, when the current status of the at least one NES feature of the at least one NES cell 102 indicates an activation of the at least one NES feature for a time exceeding a pre-defined timer value. Once the current status of the at least one NES feature of the at least one NES cell 102 is received, instead of deleting NRT entry, the NRT entry is marked as dormant when an activation duration of the at least one NES feature exceeds a pre-defined timer value for neighbor cell deletion in the NRT. The pre-defined timer value is a timer value in use by Automatic Neighbor Relation (ANR) mechanism for neighbor deletion. The NRT entry is marked as dormant as the at least one NES cell 102 is unavailable when the at least one NES feature is activated. The state of the at least one NES cell 102 is updated as an active state, when the current status of the at least one NES feature of the at least one NES cell 102 indicates a deactivation of the at least one NES feature as the at least NES cell 102 is available when the at least one NES feature is activated.

[0050]

[0045] In an embodiment, the one or more actions performed by the plurality of neighboring entities 110 may comprise configuring the UEs to perform measurements of the at least one NES cell 102 at the plurality of neighboring entities 110, based on the current status of the at least one NES feature of the at least one NES cell 102. When the at least one NES feature is activated, the at least one NES cell 102 may be optionally de-configured from measurements at the plurality of neighboring entities 110 or performing the measurements may be stopped at the at least one NES cell 102. This is to avoid unnecessary overhead and measurements, as the at least one NES cell 102 is unavailable when the at least one NES feature is activated. The at least one NES cell 102 may be de-configured from the measurements based on a time duration of non-availability of the at least one NES cell 102. For instance, the at least one NES cell 102 may be de-configured from the measurements when the time duration of non-availability of the at least one NES cell 102 is high. The UEs may be re-configured to perform the measurements of the at least one NES cell 102, when the at least one NES feature is deactivated.

[0051]

[0046] In an embodiment, the one or more actions performed by the plurality of neighboring entities 110 may comprise monitoring performance of the at least one NES cell 102. In an embodiment, the processor 206 may be configured to determine a time duration of non-availability of the at least one NES cell 102. The processor 206 may determine the time duration of non-availability based on the change in the current status of the at least one NES feature of the at least one NES cell 102 from a first status indicating a deactivation of the at least one NES feature to a second status indicating an activation of the at least one NES feature. In other words, the time duration of non-availability is a time from a deactivation of the at least one NES feature to an activation of the at least one NES feature. In an embodiment, the processor 206 may determine the time duration based on UEs request and activation of the at least one NES feature. In an embodiment, the processor 206 may firstly transmit the time duration to the second entity 108 over Fl interface. The second entity 108 may then transmit the time duration of non-availability of the at least one NES cell 102 to the plurality of neighboring entities 110 over Xn interface. The plurality of neighboring entities 110 monitors performance of the at least one NES cell 102 based on the time duration. For instance, the plurality of neighboring entities 110 may monitor Handover (HO) related performance statistics based on the time duration. The time duration of NES feature activation is factored in computation of KPIs / performance counters related to mobility. This improves performance monitoring accuracy. The other network and cell performance KPIs may also be monitored in a similar manner when the time duration of NES cells availability is a factor in their computations. In an embodiment, the second entity 108 may utilize the time duration of non-availability of the at least one NES cell 102 as an assistance information for performance monitoring KPI computations.

[0052]

[0047] Referring again to Figure 3, the plurality of neighboring entities 110 perform the one or more actions, as shown in block 8, when the at least one NES feature is activated. The one or more actions may include excluding the at least one NES cell 102 while performing the configuration or deconfiguration of the one or more network functions, updating the state of the at least one NES cell 102 as an inactive state in the NRT, configuring the UEs to stop measurements of the at least one NES cell 102, and factor NES activation duration for Performance Monitoring (PM) computation. Consider a UL WUS is received from a UE as shown in block 9. The at least one NES cell 102 may transmit the OD-SIB1 / OD-SSB upon reception of the UL WUS from the UE. In other words, the at least one NES cell 102 is activated. There is a change in the current status of the at least one NES feature of the at least one NES cell 102. As shown in steps 10-12, the information related to the change in the current status of the at least one NES feature of the at least one NES cell 102 is transmitted to the plurality of neighboring entities 110. As shown in block 13, the plurality of neighboring entities 110 revert the one or more actions when the at least one NES feature is deactivated. The reverted one or more actions may comprise including / considering the at least one NES cell 102 while performing the configuration or deconfiguration of the one or more network functions, updating the state of the at least one NES cell 102 as an active state in the NRT, configuring the UEs to perform measurements of the at least one NES cell 102, and factor NES activation duration for PM computation. As shown in block 14, the first entity 106 determines the time duration of non-availability of the at least one NES cell 102. The time duration is transmitted to the second entity 108 over the Fl interface, as shown on step 15. As shown in step 16, the second entity 108 utilizes the time duration of non-availability of the at least one NES cell 102 as an assistance information for performance monitoring KPI computations. The second entity 108 transmits the time duration of non-availability of the NES cell 102 to the plurality of neighboring entities 110, as shown in step 17. The plurality of neighboring entities 1 10 monitors the performance of the at least one NES cell 102 based on the time duration, as shown in block 18.

[0053]

[0048] The other data 214 may store data, including temporary data and temporary files, for performing the various functions of the first entity 106. The other data 214 may be stored in the memory 204.

[0054]

[0049] Figure 4 shows an exemplary flow chart illustrating method steps for handling NES cell status change in the wireless networks, in accordance with some embodiments of the present disclosure. As illustrated in Figure 4, the method 400 may comprise one or more steps. The method 400 may be described in the general context of computer executable instructions. Generally, computer executable instructions can include routines, programs, objects, components, data structures, procedures, modules, and functions, which perform particular functions or implement particular abstract data types.

[0050] The order in which the method 400 is described is not intended to be construed as a limitation, and any number of the described method blocks can be combined in any order to implement the method. Additionally, individual blocks may be deleted from the methods without departing from the scope of the subject matter described herein. Furthermore, the method can be implemented in any suitable hardware, software, firmware, or combination thereof.

[0055]

[0051] At step 402, the first entity 106 detects a change in a current status of the at least one NES feature of the at least one NES cell 102. The current status of the at least one NES feature of the at least one NES cell 102 indicates an activation status of at least one NES feature of the at least one NES cell 102. The activation status indicates one of an activation and a deactivation of the at least one NES feature. The at least one NES feature may include, but not limited to, OD SIB1 transmission and OD SSB transmission.

[0056]

[0052] At step 404, the first entity 106 transmits information related to the change in the current status of the at least one NES feature of the at least one NES cell 102 to a plurality of neighboring entities 110 of the at least one NES cell 102. In an embodiment, the first entity 106 transmits the information related to the change in the current status of the at least one NES feature of the at least one NES cell 102 to the plurality of neighboring entities 110 via the second entity 108. Herein, the first entity 106 transmits the information related to the change in the current status of the at least one NES feature of the at least one NES cell 102 to second entity 108, over Fl interface. The second entity 108 transmits the information related to the change in the current status of the at least one NES feature of the at least one NES cell 102 to the plurality of neighboring entities 110 over Fl / Xn interface. The plurality of neighboring entities 110 of the at least one NES cell 102 performs one or more actions based on the current status of the at least one NES feature of the at least one NES cell 102.

[0053] In an embodiment, the plurality of neighboring entities 110 perform configuration or deconfiguration of one or more network functions based on the current status of the at least one NES feature of the at least one NES cell 102. The one or more network functions may comprise at least one of, but not limited to, handover, Carrier Aggregation (CA), Dual Connectivity (DC), and Multiple Transmit / Receive Point (mTRP) operation. The plurality of neighboring entities 110 may preclude or include the at least one NES cell 102 for performing the configuration or deconfiguration of the one or more network functions, based on the current status of the at least one NES feature of the at least one NES cell 102. In an embodiment, the one or more actions performed by the plurality of neighboring entities 110 may comprise updating a state of the at least one NES cell 102 in the NRT associated with each of the plurality of neighboring entities 110. A state of the at least one NES cell 102 may be updated as an inactive state in the NRT, when the current status of the at least one NES feature of the at least one NES cell 102 indicates an activation of the at least one NES feature for a time exceeding a pre-defined timer value. The state of the at least one NES cell 102 is updated as an active state, when the current status of the at least one NES cell 102 indicates a deactivation of the at least one NES feature as the at least one NES cell 102 is available when the at least one NES feature is activated.

[0057]

[0054] In an embodiment, the one or more actions performed by the plurality of neighboring entities 110 may comprise configuring the UEs to perform measurements of the at least one NES cell 102 at the plurality of neighboring entities 110, based on the current status of the at least one NES feature of the at least one NES cell 102. When the at least one NES feature is activated, the at least one NES cell 102 may be optionally de-configured from measurements at the plurality of neighboring entities 110 or performing the measurements may be stopped at the at least one NES cell 102. The UEs may be re-configured to perform the measurements of the at least one NES cell 102, when the at least one NES feature is deactivated. In an embodiment, the one or more actions performed by the plurality of neighboring entities 110 may comprise monitoring performance of the at least one NES cell 102. The first entity 106 may determine a time duration of non-availability of the at least one NES cell 102, based on the change in the current status of the at least one NES feature of the at least one NES cell 102 from a first status indicating a deactivation of the at least one NES feature to a second status indicating an activation of the at least one NES feature. In an embodiment, the first entity 106 may firstly transmit the time duration to the second entity 108 over Fl interface. The second entity 108 may then transmit the time duration of nonavailability of the at least one NES cell 102 to the plurality of neighboring entities 110 over Xn interface. The plurality of neighboring entities 110 monitors performance of the at least one NES cell 102 based on the time duration. In an embodiment, the second entity 108 may utilize the time duration of non-availability of the at least one NES cell 102 as an assistance information for performance monitoring KPI computations.

[0058]

[0055] FIGURE 5 illustrates an embodiment of a first entity 500. As shown in FIGURE 5, the first entity 500 comprises a processor 502, a memory 504, a storage component 506, an input component 508, an output component 510, a communication interface 512, and a bus 514. The first entity 500 may be used to realize the first entity 106 of Figure 2. Hence, the first entity 500 may be used for handling NES cell status change in wireless networks, in accordance with embodiments of the present disclosure.

[0059]

[0056] The processor 502, as used herein, means any type of computational circuit that may comprise hardware elements and software elements. The processor 502 may be embodied as a multi-core processor, a single core processor, or a combination of one or more multi -core processors and / or one or more single core processors, a distributed processing system, or the like. The processor 502 may be a Central Processing Unit (CPU), a graphics processing unit (GPU), an accelerated processing unit (APU), an application-specific integrated circuit (ASIC), or another type of processing component. The processor 502 may be used to realize the processor 206 described in Figure 2.

[0057] The memory 504 includes a non-transitory computer readable medium. Memory 504 includes a random-access memory (RAM), a read only memory (ROM), and / or another type of dynamic or static storage device (e.g., a flash memory, a magnetic memory, and / or an optical memory) that stores information and / or instructions for use by processor 502. The memory 504 comprises machine- readable instructions which are executable by the processor 502. These machine- readable instructions when executed by the processor 502 cause the processor 502 to perform one or more method steps of an embodiment described above. The memory 504 may be used to realize the memory 204 described in Figure 2. The memory 504 is communicatively coupled to the processor 502. The memory 504 stores instructions, executable by the one or more processors 502, which, on execution, may cause the processor 502 to handle NES cell status change in wireless networks, in accordance with embodiments of the present disclosure.

[0060]

[0058] The storage component 506 stores information and / or software related to the operation and use of the first entity 500. For example, the storage component 506 may include a hard disk (e.g., a magnetic disk, an optical disk, a magneto-optic disk, and / or a solid-state disk), a compact disc (CD), a digital versatile disc (DVD), a floppy disk, a cartridge, a magnetic tape, and / or another type of non-transitory computer-readable medium, along with a corresponding drive.

[0061]

[0059] The input component 508 is configured to receive information, such as user input. For example, the input component 508 may include, but not be limited to, a touch screen display, a keyboard, a keypad, a mouse, a button, a switch, and / or a microphone. Additionally, or alternatively, the input component 508 may include a sensor for sensing information (e.g., a global positioning system (GPS), an accelerometer, a gyroscope, and / or an actuator).

[0062]

[0060] The output component 510 is configured to provide output information from the first entity 500. For example, the output component 510 may be, but not limited to, a display, a speaker, instructions to an external device, and / or one or more lightemitting diodes (LEDs).

[0063]

[0061] The communication interface 512 is an interface that provides a communication connection to other devices, such as external devices and internal devices. The connection by the communication interface 512 can be a wired connection, a wireless connection, or a combination of wired and wireless connections, and can be a direct connection or an indirect connection via a communication network that exists between the first entity 106 and other devices. In other words, the standard of the communication interface 512 is not limited. The first entity 106 may communicate with the second entity 108, over a communication network 609.

[0064]

[0062] The bus 514 acts as an interconnect between the processor 502, the memory 504, the storage component 506, the input component 508, the output component 510, and the communication interface 512 of the first entity 500. The bus 514 may include a wired interconnection or a wireless interconnection.

[0065]

[0063] The number and arrangement of components shown in FIGURE 6 are provided as an example. In practice, the first entity 500 may include additional components, fewer components, different components, or differently arranged components than those shown in FIGURE 6. Additionally, or alternatively, a set of components (e.g., one or more components) of the first entity 500 may perform one or more functions described as being performed by another set of components of the first entity 500.

[0066]

[0064] In an embodiment [1], the present disclosure discloses a gNB 104. The gNB 104 is configured to detect a change in a current status of at least one NES feature of at least one NES cell 102. The current status of the at least one NES feature of the at least one NES cell 102 indicates an activation status of the at least one NES feature of the at least one NES cell 102. The gNB 104 transmits information related to the change in the current status of the at least one NES feature of the at least one NES cell 102, to the plurality of neighboring entities 110 of the at least one NES cell 102. The plurality of neighboring entities 110 of the at least one NES cell 102 performs one or more actions based on the current status of the at least one NES feature of the at least one NES cell 102.

[0067]

[0065] In an embodiment [2], the gNB 104, described in the embodiment [1], the activation status indicates one of an activation and a deactivation of the at least one NES feature of the at least one NES cell 102.

[0068]

[0066] In an embodiment [3], the gNB 104, described in the embodiments [1] or

[0069] [2], the performing of the one or more actions comprises performing configuration or deconfiguration of one or more network functions based on the current status of at least one NES feature of the at least one the NES cell 102.

[0070]

[0067] In an embodiment [4], the gNB 104, described in the embodiments [1] or

[0071] [3], the one or more network functions comprises at least one of, handover, Carrier Aggregation (CA), Dual Connectivity (DC), and Multiple Transmit / Receive Point (mTRP) operation.

[0072]

[0068] In an embodiment [5], the gNB 104, described in the embodiments [1] or [2], the performing of the one or more actions comprises updating a state of the at least one NES cell 102 in aNRT associated with each of the plurality of neighboring entities 110 as an inactive state, when the current status of the at least one NES feature of the at least one NES cell 102 indicates an activation of the at least one NES feature for a time exceeding a pre-defined timer value. The performing of the one or more actions comprises updating the state of the at least one NES cell 102 as an active state, when the current status of the at least one NES cell 102 indicates a deactivation of the at least one NES feature.

[0069] In an embodiment [6], the gNB 104, described in the embodiments [1] or [2], the performing of the one or more actions comprises configuring UEs to perform measurements of the at least one NES cell 102 at the plurality of neighboring entities 110, based on the current status of the at least one NES feature of the at least one NES cell 102.

[0073]

[0070] In an embodiment [7], the gNB 104, described in the embodiments [1] or [2] or [3] or [5] or [6], configured to determine a time duration of non-availability of the at least one NES cell 102 based on the change in the current status of the at least one NES feature of the at least one NES cell 102 from a first status indicating a deactivation of the at least one NES feature to a second status indicating an activation of the at least one NES feature. The gNB 104 is configured to transmit the time duration to the plurality of neighboring entities 110. The plurality of neighboring entities 110 monitors performance of the at least one NES cell 102 based on the time duration.

[0074]

[0071] In an embodiment [8], the gNB 104, described in the embodiment [1], comprises a first entity 106 and a second entity 108. The first entity 106 transmits information related to the change in the current status of the at least one NES feature of the at least one NES cell 102, to a plurality of neighboring entities 110 of the at least one NES cell 102, via the second entity 108.

[0075]

[0072] In an embodiment [9], the gNB 104, described in the embodiments [1] or [8], the first entity 106 is a gNB-DU, the second entity 108 is a gNB- CU, the plurality of neighboring entities 110 is one of, a neighboring gNB-DU of the same gNB 104 or a neighboring gNB. The information related to the change in the current status of the at least one NES feature of the at least one NES cell 102 is transmitted to each of the plurality of neighboring entities 110 of the at least one NES cell 102, via respective gNB-CU over Fl interface or Xn interface.

[0073] In an embodiment

[0010] , the present disclosure discloses a method comprising detecting, by a first entity 106 associated with a gNB 104, a change in a current status of at least one NES feature of at least one NES cell 102. The current status of the at least one NES feature of the at least one NES cell 102 indicates an activation status of at least one NES feature of the at least one NES cell 102. The method further comprises transmitting, by the first entity 106, information related to the change in the current status of the at least one NES feature of the at least one NES cell 102, to the plurality of neighboring entities 110 of the at least one NES cell 102. The plurality of neighboring entities 110 of the at least one NES cell 102 performs one or more actions based on the current status of at least one NES feature of the at least one the NES cell 102.

[0076]

[0074] In an embodiment

[0011] , the method, described in the embodiment

[0010] , the activation status indicates one of an activation and a deactivation of the at least one NES feature of the at least one NES cell 102.

[0077]

[0075] In an embodiment

[0012] , the method, described in the embodiments

[0010] or

[0078]

[0011] , the performing of the one or more actions comprises performing configuration or deconfiguration of one or more network functions based on the current status of the at least one NES feature of the at least one NES cell 102.

[0079]

[0076] In an embodiment

[0013] , the method, described in the embodiments

[0010] or

[0080]

[0012] , the one or more network functions comprises at least one of, handover, Carrier Aggregation (CA), Dual Connectivity (DC), and Multiple Transmit / Receive Point (mTRP) operation.

[0081]

[0077] In an embodiment

[0014] , the method, described in the embodiments

[0010] or

[0011] , the performing of the one or more actions comprises updating a state of the at least one NES cell 102 in aNRT associated with each of the plurality of neighboring entities 110 as an inactive state, when the current status of the at least one NES feature of the at least one NES cell 102 indicates an activation of the at least one NES feature for a time exceeding a pre-defined timer value. The performing of the one or more actions comprises updating the state of the at least one NES cell 102 as an active state, when the current status of the at least one NES feature of the at least one NES cell 102 indicates a deactivation of the at least one NES feature.

[0082]

[0078] In an embodiment

[0015] , the method, described in the embodiments

[0010] or

[0012] , the performing of the one or more actions comprises configuring UEs to perform measurements of the at least one NES cell 102 at the plurality of neighboring entities 110, based on the current status of the at least one NES feature of the at least one NES cell 102.

[0083]

[0079] In an embodiment

[0016] , the method, described in the embodiments

[0010] or

[0012] or

[0013] or

[0015] or

[0016] , comprises determining a time duration of nonavailability of the at least one NES cell 102 based on the change in the current status of the at least one NES feature of the at least one NES cell 102 from a first status indicating a deactivation of the at least one NES feature to a second status indicating an activation of the at least one NES feature. The method comprises transmitting the time duration to the plurality of neighboring entities 110. The plurality of neighboring entities 110 monitors performance of the at least one NES cell 102 based on the time duration.

[0084]

[0080] In an embodiment

[0017] , the method, described in the embodiment

[0010] , the first entity 106 is a gNB-DU, the second entity 108 is a gNB- CU, the plurality of neighboring entities 110 is one of, a neighboring gNB-DU of the same gNB 104 or a neighboring gNB. The information related to the change in the current status of the at least one NES feature of the at least one NES cell 102 is transmitted to each of the plurality of neighboring entities 110 of the at least one NES cell 102, via respective gNB-CU over Fl interface or Xn interface.

[0081] In an embodiment

[0018] , the present disclosure discloses a non-transitory computer readable medium including instructions for performing operations comprising detecting a change in a current status of at least one NES feature of at least one NES cell 102. The current status of the at least one NES feature of the at least one NES cell 102 indicates an activation status of at least one NES feature of the at least one NES cell 102. The method further comprises transmitting information related to the change in the current status of the at least one NES feature of the at least one NES cell 102, to the plurality of neighboring entities 110 of the at least one NES cell 102. The plurality of neighboring entities 110 of the at least one NES cell 102 performs one or more actions based on the current status of the at least one NES feature of the at least one NES cell 102.

Claims

We claim:

1. A gNodeB (gNB) (104) configured to: detect a change in a current status of at least one NES feature of at least one Network Energy Saving (NES) cell (102), wherein the current status of the at least one NES feature indicates an activation status of the at least one NES feature of the at least one NES cell (102); and transmit information related to the change in the current status of the at least one NES feature of the at least one NES cell (102), to a plurality of neighboring entities (110) of the at least one NES cell (102), wherein the plurality of neighboring entities (110) of the at least one NES cell (102) performs one or more actions based on the current status of the at least one NES cell (102).

2. The gNB (104) as claimed in claim 1, wherein the activation status indicates one of an activation and a deactivation of the at least one NES feature of the at least one NES cell (102).

3. The gNB (104) as claimed in claim 1, wherein performing the one or more actions comprising: performing configuration or reconfiguration of one or more network functions based on the current status of the at least one NES feature of the at least one NES cell (102).

4. The gNB (104) as claimed in claim 3, wherein the one or more network functions comprises at least one of, handover, Carrier Aggregation (CA), Dual Connectivity (DC), and Multiple Transmit / Receive Point (mTRP) operation.

5. The gNB (104) as claimed in claim 1, wherein performing the one or more actions comprising:updating a state of the at least one NES cell (102) in a Neighbor Relation Table (NRT) associated with each of the plurality of neighboring entities (110) as an inactive state, when the current status of the at least one NES feature of the at least one NES cell (102) indicates an activation of the at least one NES feature for a time exceeding a pre-defined timer value ; and updating the state of the at least one NES cell (102) as an active state, when the current status of the at least one NES feature of the at least one NES cell (102) indicates a deactivation of the at least one NES feature.

6. The gNB (104) as claimed in claim 1, wherein performing the one or more actions comprising: configuring UEs to perform measurements of the at least one NES cell (102) at the plurality of neighboring entities (110), based on the current status of the at least one NES feature of the at least one NES cell (102).

7. The gNB (104) as claimed in claim 1, further configured to: determine a time duration of non-availability of the at least one NES feature of the at least one NES cell (102) based on the change in the current status of the at least one NES feature of the at least one NES cell (102) from a first status indicating a deactivation of the at least one NES feature to a second status indicating an activation of the at least one NES feature; transmit the time duration to the plurality of neighboring entities (110), wherein the plurality of neighboring entities (110) monitors performance of the at least one NES cell (102) based on the time duration.

8. The gNB (104) as claimed in claim 1, comprises a first entity (106) and a second entity (108), wherein the first entity (106) transmits information related to the change in the current status of the at least one NES feature of the at least one NES cell (102), to a plurality of neighboring entities (110) of the at least one NES cell (102), via the second entity (108).

9. The gNB (104) as claimed in claim 8, wherein the first entity (106) is a gNB- Distributed Unit (DU), the second entity (108) is a gNB-Central Unit (CU), the plurality of neighboring entities (110) is one of, a neighboring gNB-DU of the same gNB (104) or a neighboring gNB, and the information related to the change in the current status of the at least one NES feature of the at least one NES cell (102) is transmitted to each of the plurality of neighboring entities (110) of the at least one NES cell (102), via Fl interface to a serving gNB-CU and to the respective neighboring gNB-CU over Xn interface.

10. A method comprising: detecting, by a first entity (106) associated with a gNodeB (gNB) (104), a change in a current status of at least one NES feature of at least one Network Energy Saving (NES) cell (102), wherein the current status of the at least one NES feature of the at least one NES cell (102) indicates an activation status of the at least one NES feature of the at least one NES cell (102); and transmitting, by the first entity (106), information related to the change in the current status of the at least one NES feature of the at least one NES cell (102), to a plurality of neighboring entities (110) of the at least one NES cell (102), wherein the plurality of neighboring entities (110) of the at least one NES cell (102) performs one or more actions based on the current status of the at least one NES feature of the at least one NES cell (102).

11. The method as claimed in claim 10, wherein the activation status indicates one of an activation and a deactivation of the at least one NES feature of the at least one NES cell (102).

12. The method as claimed in claim 10, wherein performing the one or more actions comprising:performing configuration or reconfiguration of one or more network functions based on the current status of the least one NES feature of the at least one NES cell (102).

13. The method as claimed in claim 12, wherein the one or more network functions comprises at least one of, handover, Carrier Aggregation (CA), Dual Connectivity (DC), and Multiple Transmit / Receive Point (mTRP) operation.

14. The method as claimed in claim 10, wherein performing the one or more actions comprising: updating a state of the at least one NES cell (102) in a Neighbor Relation Table (NRT) associated with each of the plurality of neighboring entities (110) as an inactive state, when the current status of the at least one NES feature of the at least one NES cell (102) indicates an activation of the at least one NES feature for a time exceeding a pre-defined timer value; and updating the state of the at least one NES cell (102) as an active state, when the current status of the at least one NES feature of the at least one NES cell (102) indicates a deactivation of the one or more NES features.

15. The method as claimed in claim 10, wherein performing the one or more actions comprising: configuring UEs to perform measurements of the at least one NES cell (102) at the plurality of neighboring entities (110), based on the current status of the at least one NES feature of the at least one NES cell (102).

16. The method as claimed in claim 10, further comprising: determining a time duration of non-availability of the at least one NES feature of the at least one NES cell (102) based on the change in the current status of the at least one NES feature of the at least one NES cell (102) froma first status indicating a deactivation of the at least one NES feature to a second status indicating an activation of the at least one NES feature; transmitting the time duration to the plurality of neighboring entities (110), via the second entity (108), wherein the plurality of neighboring entities (110) monitors performance of the at least one NES cell (102) based on the time duration.

17. The method as claimed in claim 10, wherein the first entity (106) is a gNB- Distributed Unit (DU), the second entity (108) is a gNB-Central Unit (CU), the plurality of neighboring entities (110) is one of, a neighboring gNB-DU of the same gNB (104) or a neighboring gNB, and the information related to the change in the current status of the NES cell (102) is transmitted to each of the plurality of neighboring entities (110) of the NES cell (102), via the Fl interface to a serving gNB-CU and to the respective neighboring gNB-CU over Xn interface.

18. A non-transitory computer readable medium including instructions for performing operations comprising: detecting, by a first entity (106) associated with a gNodeB (gNB) (104), a change in a current status of at least one Network Energy Saving (NES) feature of at least one NES cell (102), wherein the current status of the at least one NES feature indicates an activation status of the at least one NES feature of the at least one NES cell (102); and transmitting, by the first entity (106), information related to the change in the current status of the at least one feature of the at least one NES cell (102), to a plurality of neighboring entities (110) of the at least one NES cell (102), via a second entity (108) associated with the gNB (104), wherein the plurality of neighboring entities (110) of the at least one NES cell (102) performs one or more actions based on the current status of the at least one NES cell (102).

Images