User equipment triggered activation of network energy saving secondary cell

Abstract

Disclosed is an apparatus implemented at a gNodeB (gNB). The apparatus is configured to receive a request from a User Equipment (UE) to activate one or more Network Energy Saving (NES) Secondary Cells (SCells). The apparatus is configured to identify at least one NES SCell based on at least one of the received request, a location of the UE, and a preferred list of NES SCells. The apparatus is configured to prepare a configuration of the identified at least one NES SCell. The apparatus is further configured to initiate the identified at least one NES SCell to transmit one or more on-demand Synchronization Signal Blocks (on-demand SSBs) to the UE. The apparatus is configured to receive measurement reports for the transmitted one or more on-demand SSBs of the identified at least one NES SCell and activate the identified at least one NES SCell for UE.

Description

USER EQUIPMENT TRIGGERED ACTIVATION OF NETWORK ENERGY SAVING SECONDARY CELLCROSS REFERENCE TO RELATED APPLICATION(S)

[0001] This application claims priority based on India Patent Application No. 202411068293 filed September 10, 2024, the entire disclosure of which is incorporated by reference herein.FIELD

[0002] The present disclosure relates to a User Equipment (UE) triggered activation of a Network Energy Saving (NES) Secondary Cell (SCell).BACKGROUND

[0003] 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.

[0004] In general, System Information Blocks (SIBs) are structured messages used in wireless communication systems, particularly in cellular networks, to broadcast essential information to a User Equipment (UE). The SIBs are transmitted by a base station (e.g., gNodeB (gNB) in 5th Generation (5G), eNodeB (eNB) in 4th Generation (4G) Long-Term Evolution (LTE)) within a network, to allow the UE to access critical information about the network. The SIBs are organized into different types (e.g., SIB1, SIB2, SIB3, etc.), each conveying specific details required by the UE to access the network, such as cell selection / reselection parameters, security information, andnetwork configuration. In addition, on-demand SIB1 (OD-SIB1) is a mechanism introduced in 5GNew Radio (NR) networks, where a critical SIB1 message is transmitted by a Network EnergySavings (NES) cell based on a network trigger or a request from the UE, rather than being continuously broadcast. The SIB1 contains essential system information, including cell identity, system bandwidth, and other parameters required for initial network access.

[0005] In the Rel-19 NES work item (RP -234065), support for OD-SIB1 for UEs in an idle / inactive mode has been studied. The key aspects of such a study include signaling and procedures to enable the OD-SIB1 transmission for UEs in idle / inactive mode. For instance, the triggering method by Uplink Wake-Up Signal (UL-WUS) uses an existing signal / channel.

[0006] An On-Demand SSB (OD-SSB) transmission can be used by the UE for at least SCell time / frequency synchronization, L1 / L3 measurements, and SCell activation. The OD-SSB is supported for Frequency Range 1 (FR1) and FR2 in the non-shared spectrum.SUMMARY

[0007] This summary is provided to introduce a selection of concepts, in a simplified format, that are further described in the detailed description of the disclosure. This summary is neither intended to identify key or essential inventive concepts of the disclosure nor is it intended to determine the scope of the disclosure.

[0008] Disclosed herein is an apparatus implemented at a gNodeB (gNB). The apparatus is configured to receive a request from a User Equipment (UE) to activate one or more Network Energy Saving (NES) Secondary Cells (SCells). The apparatus is configured to identify at least one NES SCell based on at least one of the received request, a location of the UE, and a preferredlist of NES SCells. The apparatus is configured to prepare a configuration of the identified at least one NES SCell for the UE. The apparatus is also configured to transmit a Radio Resource Control (RRC) reconfiguration message indicating the configuration of the identified at least one NES SCell to the UE. The apparatus is further configured to initiate the identified at least one NES SCell to transmit one or more on-demand Synchronization Signal Blocks (on-demand SSBs) to the UE. The apparatus is further configured to receive measurement reports for the transmitted one or more on-demand SSBs of the identified at least one NES SCell. The apparatus is further configured to activate the identified at least one NES SCell for UE.

[0009] Also disclosed herein is a method. The method comprises receiving, by a gNodeB (gNB), a request from a User Equipment (UE) to activate one or more Network Energy Saving (NES) Secondary Cells (SCells). The method further comprises identifying, by the gNB, at least one NES SCell based on at least one of the received request from a UE, a location of the UE, and a preferred list of NES SCells. The method further comprises preparing, by the gNB, a configuration of the identified at least one NES SCell for the UE. The method further comprises transmitting, by the gNB, a Radio Resource Control (RRC) reconfiguration message indicating the configuration of the identified at least one NES SCell to the UE. The method further comprises initiating, by the gNB, the identified at least one NES SCell to transmit one or more on-demand Synchronization Signal Blocks (on-demand SSBs) to the UE. The method further comprises receiving, by the gNB, measurement reports for the transmitted one or more on-demand SSBs of the identified at least one NES SCell. The method also comprises activating, by the gNB, the identified at least one NESSCell for the UE.

[0010] Also disclosed herein is a system comprising a gNodeB (gNB) in communication with a User Equipment (UE). The gNB is configured to receive a request from the UE to activate one or more Network Energy Saving (NES) Secondary Cells (SCells). The gNB is further configured to identify at least one NES SCell based on at least one of the received request, a location of the UE, and a preferred list of NES SCells. The gNB is further configured to prepare a configuration of the identified at least one NES SCell for the UE. The gNB is also configured to transmit a Radio Resource Control (RRC) reconfiguration message indicating the configuration of the identified at least one NES SCell to the UE. The gNB is further configured to initiate the identified at least one NES SCell to transmit one or more on-demand Synchronization Signal Blocks (on-demand SSBs) to the UE. The gNB is further configured to receive measurement reports for the transmitted on- demand SSBs of the identified at least one NES SCell. The gNB is further configured to activate the identified at least one NES SCell for the UE.

[0011] Also disclosed herein is a non-transitory computer-readable medium storing instructions. The instructions comprise one or more instructions that are executed by a gNodeB (gNB). The gNB comprises one or more processors. The instructions cause the one or more processors to receive a request from a User Equipment (UE) to activate one or more Network Energy Saving (NES) Secondary Cells (SCells). The instructions also cause the one or more processors to identify at least one NES SCell based on at least one of the received request, a location of the UE, and a preferred list of NES SCells. The instructions also cause the one or more processors to prepare a configuration of the identified at least one NES SCell for the UE. The instructions further cause the one or more processors to transmit a Radio Resource Control (RRC) reconfiguration message indicating the configuration of the identified at least one NES SCell to the UE. The instructionsfurther cause the one or more processors to initialize the identified at least one NES SCell to transmit one or more on-demand Synchronization Signal Blocks (on-demand SSBs) to the UE. The instructions further cause the one or more processors to receive measurement reports for the transmitted one or more on-demand SSBs of the identified at least one NES SCell. The instructions further cause the one or more processors to activate the identified at least one NES SCell for the UE.

[0012] The disclosed apparatus, method, system, and non-transitory computer-readable medium enable the UE to trigger activation of the NES SCell(s).

[0013] To further clarify the advantages and features of the present disclosure, a more particular description of the disclosure will be rendered by reference to specific embodiments thereof, which is illustrated in the appended drawing. It is appreciated that these drawings depict only typical embodiments of the disclosure and are therefore not to be considered limiting its scope. The disclosure will be described and explained with additional specificity and detail with the accompanying drawings.BRIEF DESCRIPTION OF THE DRAWINGS

[0014] 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:FIG. l is a diagram illustrating example scenarios for Network Energy Saving (NES), according to one or more conventional techniques;FIG. 2 illustrates a block diagram of a communication system depicting a configuration of a gNodeB (gNB) and a User Equipment (UE), in accordance with an embodiment of the present disclosure;FIG. 3 illustrates a signaling diagram depicting an exchange of signals between the UE, a PCell gNB, and a NES SCell gNB for a NES Secondary cell (SCell) activation, in accordance with an embodiment of the present disclosure;FIG. 4 illustrates a signaling diagram depicting an exchange of signals between the UE, the PCell gNB, and the NES SCell gNB for the NES SCell activation, in accordance with another embodiment of the present disclosure;FIGS. 5A-5B illustrate a flowchart depicting a method for the NES SCell activation, in accordance with an embodiment of the present disclosure; andFIG. 6 is a diagram of example components of a wireless communication device, in accordance with an embodiment of the present disclosure.DETAILED DESCRIPTION

[0015] The following detailed description of example embodiments refers to the accompanying drawings. The present disclosure provides illustrations and descriptions, 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 present disclosure or may be acquired from the 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 at least one of the embodiments in the present disclosure. It should be noted that it is possible tomake 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).

[0016] 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 should not limit their 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.

[0017] Even though particular combinations of features are recited in the claims and / or disclosed in the specification, the particular 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. Even if a dependent claim directly depends on only one claim, the present disclosure may indicate that the dependent claim is dependent on other claims in the claim set.

[0018] 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” (in other words, nouns not mentioned in the plural) 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 “basedon” 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.

[0019] FIG. 1 is a diagram illustrating example scenarios for Network Energy Saving (NES), according to one or more conventional techniques. In general, the addition and activation of a Secondary Cell (SCell) include the following steps:• Step 1 : A User Equipment (UE) is connected to a Primary Cell (PCell) and is in Radio Resource Control (RRC) Connected mode. The PCell may also be referred to as an anchor cell.• Step 2: The PCell configures (adds) one or more SCells to the UE based on Synchronization Signal Block (SSB)-based measurement reports of the SCells from the UE. Quality of measurements enables the PCell to select suitable SCells that are good candidates for Carrier Aggregation (CA). When a bit rate requirement of the UE’s DL / UL transmission increases, then the PCell activates one or more previously configured SCells.• Step 3: For SCell activation, the UE is required to measure SSB from the SCells for an Automatic Gain Control (AGC), time / frequency synchronization, and more (ref. Clause 8.3 of TS 38.133).

[0020] Further, in release 18, the 3rd Generation Partnership Project (3GPP) introduces NES cells which are SCells in the CA, configured to maximize energy savings. Specifically, the NES cells are not required to transmit periodic Synchronization Signal Blocks (SSBs) when there is no UE data transmission in the cell. This enables the cell to be in energy-saving mode.

[0021] With reference to NES cells, various scenarios are defined in the RANI NES work item: (Ref R1 -2403506) as illustrated in FIG. 1.

[0022] Specifically, FIG. 1 illustrates a scenario 1 which corresponds to a time duration before a UE is configured with SCell. In such a scenario, when the UE needs to be configured with an SCell, a PCell can trigger on-demand SSB (also referred to as “OD-SSB”) for the SCell. This enables the UE to perform the required measurement for the SCell. A scenario 2 corresponds to a time duration when the SCell is configured to the UE, but the UE is yet to receive the SCell activation command (e g., as defined in TS 38.321). Thus, in such a scenario, the UE needs the SCell activation command before adding it to the SCell. Further, a scenario 3 A corresponds to a time duration, after the UE has received the SCell activation command. In such a scenario, for a NES SCell, SSB transmission is needed to support the SCell addition. Moreover, a scenario 3B corresponds to a time duration when an activation of the SCell is successfully completed.

[0023] Furthermore, across New Radio (NR) releases, the 3 GPP introduced several enhancements for SCell activation for faster SCell activation and Network (NW) energy savings. Such enhancements include:• NR Rel-15 SSB-less SCell for Intra-band contiguous CA: In this enhancement, a SCell can be configured without the SSB when the SCell is configured along with an intra-band contiguous serving cell.• NR Rel-17 Fast SCell activation: In this enhancement, Advanced Tracking Reference Signal (A-TRS) is introduced to reduce the SCell activation delay for known SCells. This is applicable for known cells without any limitation on collocation and SCell can be intra-band or inter-band FR1 / FR2.• NR Rel-18 SSB-less SCell for inter-band collocated CA in FR1 : As part of this enhancement, when certain conditions are met, a SCell can be configured without the SSB if there is another inter-band active serving cell in FR1.

[0024] However, none of the conventional techniques discloses UE-triggered activation of NES SCell(s). The present disclosure provides a solution to enable the UE to request SCell activation in a scenario, for example, when the UE’s data rate Key Performance Indicator (KPI) is below a satisfactory level.

[0025] FIG. 2 illustrates a block diagram of a communication system 200 (also referred to as the system 200) depicting a configuration of a gNodeB (gNB) 210 and a UE 220, in accordance with an embodiment of the present disclosure. The gNB 210 may be configured to communicate with the UE 220, as depicted in FIG. 2. The configurations as disclosed in FIG. 2 may be understood as parts of the configuration of the gNB 210 and the UE 220. Hereinafter, it is understood that terms including “unit” or “module” at the end may refer to the unit for processing at least one function or operation and may be implemented in hardware, software, or a combination of hardware and software.

[0026] In an embodiment, the communication system 200 may correspond to a 5th Generation (5G) New Radio (NR) communication environment. The gNB 210 may be referred to as a 5G base station that provides connectivity to the UE 220 and manages radio resources. In an embodiment, the UE 220 may be a mobile telephone, a smartphone, a tablet, a personal computer, a Personal Digital Assistant (PDA), a data terminal, etc.

[0027] It is appreciated that although the gNB 210 and the UE 220 are depicted in FIG. 2, the communication system 200 may include additional gNBs and UEs as well. Further, the detailsexplained in the present disclosure for the gNB 210, and the UE 220 are equally applicable for the additional gNBs and UEs as well.

[0028] Referring to FIG. 2, the gNB 210 may include an apparatus 201 comprising one or more processor(s) 202 (also, referred to as the processor 202), a storage unit (e.g., a memory 204), and a communication unit 206 (e.g., communicator or communication interface). The communication unit 206 may perform functions such as transmitting and receiving signals. The memory 204 may include executable instructions that, when executed by the processor 202, cause the apparatus 201 to perform the steps as described with reference to FIGS. 3, 4, and 5A.

[0029] As an example, the processor 202 may be a single processing unit or a number of units, all of which could include multiple computing units. The processor 202 may be implemented as one or more microprocessors, microcomputers, microcontrollers, digital signal processors, central processing units, state machines, logic circuitries, and / or any devices that manipulate signals based on operational instructions. Among other capabilities, the processor 202 is configured to fetch and execute computer-readable instructions and data stored in the memory 204. The processor 202 may include one or a plurality of processors. At this time, one or a plurality of processors 202 may be a general-purpose processor, such as a Central Processing Unit (CPU), an Application Processor (AP), or the like, and an Al-dedicated processor such as a Neural Processing Unit (NPU). The processor 202 may control the processing of input data in accordance with a predefined operating rule or Artificial Intelligence (Al) model stored in the non-volatile memory and the volatile memory, i.e., the memory 204. The predefined operating rule or artificial intelligence model is provided through training or learning.

[0030] The memory 204 may include any non-transitory computer-readable medium known in the art including, for example, volatile memory, such as Static Random-Access Memory (SRAM) and Dynamic Random-Access Memory (DRAM), and / or non-volatile memory, such as Read-Only Memory (ROM), erasable programmable ROM, flash memories, hard disks, optical disks, and magnetic tapes.

[0031] The communication unit 206 may include communication devices / components such as antennas, transmitters, receivers, communication interfaces, etc.

[0032] In some embodiments, the apparatus 201 may be implemented as dedicated hardware units. In some embodiments, the apparatus 201 may be implemented in the form of virtualized software units in hardware or cloud environments,

[0033] Further, the UE 220 may also include one or more processor(s) 212 (also, referred to as the processor 212), a storage unit (e.g., a memory 214), and a communication unit 216 (e.g., communicator or communication interface). The functionalities and features of the processor 212, the communication unit 216, and the memory 214 may be similar to those of the processor 202, the communication unit 206, and the memory 204, respectively of the gNB 210. Therefore, a detailed explanation of the same is omitted herein for the sake of brevity of the present disclosure.

[0034] FIG. 3 illustrates a signaling diagram 300 depicting an exchange of signals between the UE 220 and a PCell gNB 301 and a NES SCell gNB 303 for a NES Secondary cell (SCell) activation, in accordance with an embodiment of the present disclosure. In one embodiment, the PCell gNB 301 and / or the NES SCell gNB 303 may correspond to the gNB 210. The PCell may act as a main cell or an anchor cell that the UE 220 connects to for initial access and critical signaling. The PCell gNB 301 may be configured to provide a primary communication link to theUE 220. In one embodiment, the PCell gNB 301 may manage both control plane and user plane data. Further, the NES SCell gNB 303 may be configured to provide additional carriers to increase data throughout and a capacity for the UE 220. The NES SCell gNB 303 may be configured to enhance the overall performance and bandwidth available to the UE 220 via the CA. The signaling diagram 300 corresponds to a scenario when there is no always-on SSB mode activated in the NES SCell gNB 303. In particular, the SSB transmission by the NES SCell gNB 303 is stopped for energy saving.

[0035] Initially, the UE 220 maybe in a Radio Resource Control (RRC) connected state with the gNB 210 and connected with the PCell gNB 301.

[0036] At step 302, the UE 220 may monitor Quality of Service (QoS) / Key Performance Indicators (KPIs) (collectively referred to as the KPIs) related to data rate available to the UE 220. Examples of such KPIs may include, but are not limited to, a Guaranteed Bit Rate (GBR), an Allocation and Retention Priority (ARP), a Maximum Bit Rate (MBR), and an Adaptive MBR (AMBR), etc. The GBR may refer to a guaranteed minimum bit rate that is allocated to a specific service or an application of the UE 220 during the duration of the transmission. The GBR may ensure a consistent level of service, particularly for applications that are sensitive to delays and require a certain bandwidth for operation. Examples of such services may include, but are not limited to, Voice over Internet Protocol (VoIP), video streaming, etc. The ARP indicates a priority level of different services in terms of resource allocation and retention in the communication network. The MBR may be defined as a maximum data rate that can be allocated to a specific service or user in normal conditions. The MBR may set a threshold to ensure that no single user and / or service consumes an excessive amount of bandwidth or network resources. The AMBRmay be defined as a dynamic value that represents the maximum bit rate that can be allocated to a specific user or device for its complete data flow. The AMBR may be dependent on network conditions, user behavior, and policy configuration. The KPIs as explained above are exemplary and the UE 220 may monitor any additional KPI that is required to achieve a desired performance. The UE 220 may monitor the one or more KPIs on an application level either after every predefined duration or upon detection of an event. Examples of such events may include, but are not limited to, a packet drop event, a packet delay event, a packet re-transmission event, and the like. In one embodiment, the UE 220 may be configured to compare the one or more monitored KPIs with corresponding one or more threshold values to determine whether the one or more KPIs are unsatisfactory. In one non-limiting example, the one or more threshold values corresponding to the one or more KPIs may be defined by stakeholders including, but not limited to, telecom operators, standardization bodies (for example, the 3 GPP), regulatory authorities, or the network equipment vendors. In some embodiments, the one or more thresholds corresponding to the one or more KPIs may be preconfigured at the UE 220. Moreover, at step 302, the UE 220 may decide to indicate to the gNB 210 if the one or more KPIs are unsatisfactory.

[0037] At step 304, the UE 220 may read the System Information Block (i.e., SIB1) associated with the PCell gNB 301 to identify whether there are NES SCells associated with the gNB 210. In one embodiment, the SIB1 is transmitted by the PCell gNB 301, to allow the UE 220 to access critical information about the network and / or the gNB 210. The SIB1 may include specific information corresponding to the PCell gNB 301. Such information may include, but is not limited to, cell selection / reselection parameters, security information, network configuration, and SCell(s) configuration. In one non-limiting embodiment, the SIB1 of the PCell gNB 301 may include a listof deactivated SCells (gNB NES SCells) associated with the PCell gNB 301. Moreover, the UE 220 may access historical information stored within the UE 220 to determine a preferred list of SCells based on the SZB1 associated with the PCell gNB 301. The historical information may include information about previously configured SCells for a given Pcell and one or more corresponding performance indicators. Particularly, the UE 220 may select one or more SCells included in the SIB1 of the PCell gNB 301 based on the previous CA configuration in the PCell gNB 301. In one embodiment, the UE 220 may be configured to store the previous CA configurations (with one or more gNB NES SCells) in a current or a previously connected mode session.

[0038] At step 306, the UE 220 may transmit an RRC UE assistance information message to the PCell gNB 301. The RRC UE assistance information message may include UE assistance information to enable the gNB 210 to configure the one or more NES SCells for the UE. For instance, the UE assistance information may include an indication of QoS / KPIs corresponding to the data rate being unsatisfactory, a preferred list of SCells, and so forth. In one embodiment, the UE 220 may utilize L1 / L2 signaling to request the network and / or the PCell gNB 301 to improve the data rate. In particular, the UE 220 may request the network and / or the gNB 210 to activate the CA to improve the performance of the data transmission.

[0039] The UE assistance information may be categorized into different types based on the application of the information. Examples of such applications may include power-saving applications, overheating mitigation, measurement, and others. The various parameters / information included in the UE assistance information may be dependent on such categorization. In one embodiment of the present disclosure, the UE assistance information maybe modified to include a new cause named “unsatisfactory bitrate requesting SCell activation”. The unsatisfactory bitrate requesting SCell activation cause may indicate to the PCell gNB 301 that the UE 220 is requesting SCell activation.

[0040] At step 308, in response to the received UE assistance information, the PCell gNB 301 may configure UE’s preferred SCell(s) (for example, the NES SCell gNB 303) for the UE 220. In one embodiment, the PCell gNB 301 may utilize the preferred list of SCells included in the UE assistance information to configure the NES SCell gNB 303 for the UE 220. In another embodiment, the PCell gNB 301 may identify a location of the UE 220 in the PCell gNB 301. The PCell gNB 301 may then configure the NES SCell gNB 303 for the UE 220 based on the identified location of the UE 220. The PCell gNB 301 may utilize the location of the UE 220 in the PCell to configure the NES SCell gNB 303, in case the UE assistance information does not include the preferred list of SCells. In one or more embodiments, the PCell gNB 301 may be configured to implement one or more AI-ML-based techniques to determine the one or more UE’s preferred SCells. In some embodiments, the AI-ML-based techniques may predict the one or more UE’s preferred SCells based on a predicted or a reported UE’s location in the PCell gNB 301. The AI- ML-based techniques may enable the PCell gNB 301 to prioritize and / or select one or more NES SCells for configuration / addition for the UE 220.

[0041] At step 310, the PCell gNB 301 may transmit an RRC reconfiguration message to the UE 220. The RRC reconfiguration message may include CA information, SCell configuration, and SCell measurement. In one embodiment, the CA information may include, but is not limited to, details related to frequency bands or carriers associated with the PCell gNB 301 and the NES SCell gNB 303. The SCell configuration may indicate the configuration of the NES SCell gNB 303 forthe UE. The SCell measurements may include information such as, but not limited to, signal strength (for example, Reference Signal Received Power (RSRP), signal quality (for example,Reference Signal Received Quality (RSRQ), latency information, and so forth.

[0042] At step 312, the PCell gNB 301 may trigger OD-SSB for the configured SCells (for example, the NES SCell gNB 303). In one embodiment, the gNB 210 may trigger the OD-SSB for the configured SCell using backhaul signaling between the PCell gNB 301 and NES SCell gNB 303. In one non-limiting embodiment, the gNB 210 may trigger the OD-SBB during an inter- Distributed Unit (DU) CA. The OD-SSB (also referred to as the SSB) may act as an essential component to enable synchronization between the UE 220 and the NES SCell gNB 303. The OD- SSB may include several sub-components such as, Synchronization Signals (SS), Physical Broadcast Channel (PBCH), frequency and time domain allocation, repetition, carrier frequency, configuration parameters, and so forth. The SS may include two important components namely, a Primary Synchronization Signal (PSS) and a Secondary Synchronization Signal (SSS). The PSS may enable the UE 220 to acquire the time alignment with the network and determine frame timings. The SSS may enable the UE 220 to identify a cell Identifier (ID) and additional timing information associated with the corresponding SCell (for example, the NES SCell gNB 303). The PBCH may include information cell and system configuration information that may be required by the UE 220 for initial access to the network. Similarly, other sub-components of the SSB may enable the UE 220 to connect with the network via the corresponding SCell (the NES SCell gNB 303) effectively and efficiently.

[0043] At step 314, the NES SCell gNB 303 may initiate transmission of the OD-SSB based on the UE’s request. In particular, at step 316, the NES SCell gNB 303 may transmit SCell OD-SSB broadcast transmission to the UE 220.

[0044] In response to the received OD-SSB from the NES SCell gNB 303, at step 318, the UE 220 may transmit a measurement report for the NES SCell gNB 303 to the PCell gNB 301. Specifically, at step 318, the UE 220 may be configured to perform measurements on the received OD-SSB and send the measurement reports to the PCell gNB 301. In one non-limiting embodiment, the UE 220 may perform measurements such as, RSRP, RSRQ, synchronization timing, cell identity detection, frequency estimation, beam management, and so forth. The UE 220 measures the RSRP of the OD-SSB, to indicate the average received power level of the OD-SSB over a specific bandwidth. The RSRP may indicate the signal strength of the NES SCell gNB 303 for the UE 220. The RSRQ may indicate a quality of reference signals from the NES SCell gNB 303 to help the UE 220 assist the quality of the connection with the NES SCell gNB 303. Further, the frequency estimation may correspond to performing frequency error measurements based on the OD-SSB. The channel estimation corresponds to identifying channel conditions associated with the NES SCell gNB 303. Moreover, the beam management corresponds to identifying a quality and a direction of the beams corresponding to the OD-SSB. The UE 220 may prepare a measurement report based on one or more above-mentioned measurements and transmit the measurement report to the PCell gNB 301.

[0045] Based on the received measurement report from the UE 220, at step 320, the PCell gNB 301 may activate the NES SCell gNB 303 for the UE 220. The PCell gNB 301 may analyze the received measurement report to identify that the UE 220 can effectively connect and communicate with the NES SCell gNB 303. In one embodiment, the PCell gNB 301 may be configured tocompare the received one or more measurements in the measurement report with corresponding preconfigured threshold values to determine whether the configured SCell (the NES SCell gNB 303) meets SCell activation criteria. Based on said comparison and identification, the PCell gNB 301 activates the NES SCell gNB 303 for the UE 220. The PCell gNB 301 activates the NES SCell gNB 303 to improve the one or more KPIs associated with the UE 220.

[0046] In one embodiment, when there is a plurality of NES SCells associated with the gNB 210 is configured for the UE 220. The UE 220 may receive OD-SSB from each of the plurality of NES SCells. Also, the UE 220 may transmit a measurement report corresponding to each of the plurality of NES SCells to the PCell gNB 301. Based on the received measurement reports, the PCell gNB 301 may determine a valid list of NES SCells for the UE 220. The PCell gNB 301 may also configure the one or more NES SCells from the determined valid list of NES SCells for the UE 220 based on the received measurement reports. Moreover, in case the one or more NES SCells have overlapping coverage with the PCell gNB 301, the PCell gNB 301 may easily identify at least one NES SCell for the UE 220. However, in case there is no overlapping between the coverage area of the PCell gNB 301 and the one or more NES SCells, the PCell gNB 301 may utilize other assistance information to configure the one or more NES SCells for the UE 220. The other assistance information may include, but is not limited to, neighboring cell information, other cells reported in the received measurement reports, a location of the UE 220 in the PCell gNB 301, etc. Alternatively, the PCell gNB 301 may configure each of the identified one or more NES Scells in the valid list of NES SCell s for the UE 220.

[0047] The PCell gNB 301 may also transmit an activation confirmation indicating that the NESSCell gNB 303 has been activated to transmit OD-SSB for the UE 220.

[0048] In one embodiment, the gNB 210 may have a disaggregated architecture including multiple logical entities. For instance, the gNB 210 may include one or more gNB-Distributed Units (gNB- DUs), and a gNB-Centralized Unit (gNB-CU). The gNB-CU may be further split into a CU Control Plane (CP) part, also referred to as gNB-CU-CP, and a CU User Plane (UP) part, also referred to as gNB-CU-UP. In one embodiment, the PCell gNB 301 or the NES SCell gNB 303 may correspond to the gNB -DU.

[0049] FIG. 4 illustrates a signaling diagram 400 depicting an exchange of signals between the UE 220, the PCell gNB 301, and NES SCell gNB 303 for the NES SCell activation, in accordance with another embodiment of the present disclosure. The illustrated embodiment of FIG. 4 corresponds to a scenario when the NES SCells are in always-on SSB transmission mode with a relatively high periodicity. As explained above, the gNB 210 may correspond to the PCell gNB 301 and / or the NES SCell gNB 303. In one embodiment, the NES-specific periodicity (also referred to as SSB periodicity information) may correspond to a time duration after which the NES SCell (i.e., the NES SCell gNB 303) may transmitthe periodic SSB broadcast. The SSB periodicity information of the NES SCell gNB 303 may be transmitted to the UE 220 via the SIB 1 of the PCell gNB 301. In one embodiment, the Uplink Wake Up Signal (UL WUS) confirmation information may include the NES-specific periodicity.

[0050] At step 402, the UE 220 may monitor one or more KPIs associated with the data rate to indicate to the gNB 210 if the KPIs are unsatisfactory. The step 402 is similar to the step 302, as explained in reference to FIG. 3.

[0051] At step 404, the UE 220 may transmit an RRC message to the PCell gNB 301. The RRC message may include the UE assistance information and an indication that the one or more KPIsassociated with data rate (bit rate) are unsatisfactory. Specifically, at step 404, the UE 220 requests the gNB 210 to configure the one or more NES SCells for the UE 220.

[0052] In response to the received RRC message from the UE 220, at step 406, the PCell gNB 301 configures one or more NES SCells (including the NES SCell gNB 303) for the UE 220.

[0053] Next, at step 408, the PCell gNB 301 transmits the RRC reconfiguration message to the UE 220. The RRC reconfiguration message includes the CA configuration, SCell configuration, and SCell measurement configuration, as discussed above. In one or more embodiments, the RRC reconfiguration message may include a Random Access Channel (RACH) configuration of one or more NES SCells selected by the PCell gNB 301 for the UE 220.

[0054] At step 410, the UE 220 may receive a periodic SCell SSB broadcast message 410 from the NES SCell gNB 303.

[0055] At step 412, the UE 220 may transmit a RACH request to request for the OD-SSB from at least one of the one or more configured NES SCells (for example, the NES SCell gNB 303). The RACH request may correspond to a Wake Up Signal (WUS) for the NES SCell gNB 303 to transmit the OD-SSB. The UE 220 may transmit the RACH request to the NES SCell gNB 303 while connected to the PCell gNB 301. In another embodiment, the PCell gNB 301 may inform the NES SCell gNB 303 to initiate the OD-SSB transmission.

[0056] In response to the received RACH request for the OD-SSB, at step 414, the NES SCell gNB 303 may initiate transmission of the OD-SSB. At step 416, the gNB NES SCell may transmit the OD-SSB broadcast to the UE 220.

[0057] The UE 220 may perform one or more above-discussed measurements on the received OD- SSB of the NES Scell. Based on the performed measurements, at step 418, the UE 220 maytransmit the measurement report to the PCell gNB 301. In one non-limiting embodiment, the measurement report may include an indication to the gNB to activate the NES SCell gNB 303 for the UE 220.

[0058] In response to the received measurement report, the PCell gNB 301 may activate the one or more NES SCell (including the NES SCell gNB 303) for the UE 220.

[0059] Thus, the siganling diagrams 300 and 400 indicate that the UE 220 is now enabled to trigger configuration / activation for the one or more NES SCells to improve UE’s performance. The UE 220 may proactively request the gNB for Scell activation and not need to wait for the gNB 210 to activate the SCells .

[0060] FIGS. 5A-5B illustrate a flowchart depicting a method 500 for the NES SCell activation, in accordance with an embodiment of the present disclosure. In one embodiment, the steps of the method 500 as illustrated in FIG. 5 A may be performed by the apparatus 201 associated with the gNB 210, as discussed above with reference to FIGS. 2-4.

[0061] At step 502, a request to activate one or more NES SCells is received by the gNB 210 from the UE 220. For example, the gNB 210 may receive an UE assistance information message, including the unsatisfactory bitrate requesting SCell activation cause. The unsatisfactory bitrate requesting SCell activation cause is based on the one or more KPIs associated with the UE 220. In one embodiment, upon determining that the one or more KPIs associated with the data rate (bit rate) of the UE 220 are unsatisfactory, the UE 220 may update the UE assistance information with the unsatisfactory bitrate requesting SCell activation cause. This cause may indicate the gNB 210 to activate / configure one or more NES SCells for the UE 220. The one or more KPIs may include, but are not limited to, the GBR, the ARP, the MBR, and the AMBR.

[0062] At step 504, the gNB 210 identifies at least one NES SCell (for example, the NES SCell gNB 303) based on the received request from the UE 220. In one embodiment, the gNB 210 may utilize the received UE assistance information, the location of the UE 220, and a preferred list of NES Scells from the UE 220, to identify the at least one NES SCell (the NES SCell gNB 303).

[0063] At step 506, the gNB 210 may prepare a configuration of the identified at least one NES SCell (the NES SCell gNB 303) for the UE 220. To prepare the configuration of the identified at least one NES SCell (the NES SCell gNB 303), the gNB 210 may receive measurement reports from the UE for the one or more Scells. The gNB 210 may determine a valid list of SCells (include the NES SCell gNB 303) associated with the PCell (the PCell gNB 301) of the gNB 210 based on the UE assistance information and / or the received measurement reports. Thereafter, the gNB 210 may configure the identified at least one NES SCell (the NES SCell gNB 303) for the UE 220 based on the determined list of the valid SCells. In some non-limiting embodiments, the UE assistance information may include, but is not limited to, non-overlapping coverage information, neighbor cell information, other cells reported in the measurement report, and a location of the UE 220 in the PCell (the PCell gNB 301).

[0064] At step 508, the gNB 210 may transmit the RRC reconfiguration message indicating the configuration of the identified at least one NES SCell (the NES SCell gNB 303) for the UE 220.

[0065] At step 510, the gNB 210 may initiate the identified at least one NES SCell (the NES SCell gNB 303) to transmit the one or more on-demand SSBs to the UE 220.

[0066] At step 512, the gNB 210 may receive one or more measurement reports for the transmitted one or more OD-SSBs of the identified at least one NES SCell (the NES SCell gNB 303).

[0067] At step 514, the gNB 210 may activate the identified at least one NES SCell (the NES SCell gNB 303). In one embodiment, the gNB 210 may also transmit the activation confirmation of the at least one NES SCell (the NES SCell gNB 303) to the UE 220.

[0068] While the above-discussed steps in FIG. 5A are shown and described in a particular sequence, the steps may occur in variations to the sequence in accordance with various embodiments. Further, a detailed description related to the various steps of FIG. 5A is already covered in the description related to FIGS. 2-4 and is omitted herein for the sake of brevity.

[0069] In one embodiment, the steps of the method 500 as illustrated in FIG. 5B may be performed by the UE 220, as discussed above with reference to FIGS. 2-4.

[0070] At step 516, the UE 220 may monitor the one or more KPIs.

[0071] At step 518, the UE 220 may compare the one or more KPIs with corresponding one or more threshold values to determine whether the one or more KPIs are unsatisfactory.

[0072] At step 520, upon determining the one or more KPIs are unsatisfactory, the UE 220 may identify one or more NES SCells associated with the gNB 210 based on information in the SIB of the PCell (the PCell gNB 301) associated with the gNB 210. In one embodiment, to identify the one or more NES SCells, the UE 220 may be configured to receive a list of NES SCells in an Energy Saving (ES) mode on the SIB of the PCell, from the gNB 210. Further, the UE 220 may identify the one or more NES SCells based on the received list of NES SCells. In one non-limiting embodiment, the UE 220 may be configured to identify the one or more NES SCells based on historical CA configuration information in one of the current or the previous connected mode session.

[0073] At step 522, the UE 220 may transmit the request to activate at least one of the identified one or more NES Scells (the NES SCell gNB 303) to the gNB 210. In one embodiment, the UE 220 may transmit the request via one of an RRC or L1 / L2 signaling. The request may correspond to the activation of CA to improve the one or more KPIs of the UE 220. In one non-limiting embodiment, the UE 220 may update the UE assistance information message to include the unsatisfactory bitrate requesting SCell activation cause. The UE 220 may then transmit the UE assistance message to the gNB 210 as the request.

[0074] In response to the transmitted request, at step 524, the UE 220 may receive the one or more on-demand SSBs from the one of the identified one or more NES Scells (the NES SCell gNB 303).

[0075] Next, at step 526, in response to the received one or more on-demand SSBs, the UE 220 may transmit the measurement report corresponding to each of the one or more NES SCells.

[0076] At step 528, the UE 220 may receive the activation confirmation of one or more NES SCells (the NES SCell gNB 303) based on the transmitted measurement report, from the gNB 210.

[0077] While the above-discussed steps in FIG. 5B are shown and described in a particular sequence, the steps may occur in variations to the sequence in accordance with various embodiments. Further, a detailed description related to the various steps of FIG. 5B is already covered in the description related to FIGS. 2-4 and is omitted herein for the sake of brevity.

[0078] FIG. 6 is a diagram of example components of a wireless communication device 600, in accordance with an embodiment of the present disclosure. In one or more embodiments, the wireless communication device 600 may correspond to the gNB 210 or the UE 220. As shown in FIG. 6, the device 600 includes a processor 610, a memory 620, a storage component 630, an input component 640, an output component 650, a communication interface 660, and a bus 670.

[0079] The processor 610, as used herein, means any type of computational circuit that may comprise hardware elements and software elements. The processor 610 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 610 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.

[0080] The memory 620 includes a non-transitory computer-readable medium. The memory 620 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 the processor 610. The memory 620 comprises machine-readable instructions which are executable by the processor 610. These machine-readable instructions when executed by the processor 610 cause the processor 610 to perform one or more method steps of an embodiment described above.

[0081] The storage component 630 stores information and / or software related to the operation and use of the device 600. For example, the storage component 630 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.

[0082] The input component 640 is configured to receive information, such as user input. For example, the input component 640 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, oralternatively, the input component 640 may include a sensor for sensing information (e.g., a Global Positioning System (GPS), an accelerometer, a gyroscope, and / or an actuator).

[0083] The output component 650 is configured to provide output information from the device 600. For example, the output component 650 maybe, but is not limited to, a display, a speaker, an instruction device to an external device, and / or one or more Light-Emitting Diodes (LEDs).

[0084] The communication interface 660 is an interface that provides a communication connection to other devices, such as external devices and internal devices. The connection by the communication interface 660 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 device 600 and other devices. In other words, the standard of the communication interface 660 is not limited.

[0085] The bus 670 acts as an interconnect between the processor 610, the memory 620, the storage component 630, the input component 640, the output component 650, and the communication interface 660 of the device 600. The bus 670 may include a wired interconnection or a wireless interconnection.

[0086] The number and arrangement of components shown in FIG. 6 are provided as an example. In practice, the device 600 may include additional components, fewer components, different components, or differently arranged components than those shown in FIG. 6. Additionally, or alternatively, a set of components (e.g., one or more components) of the device 600 may perform one or more functions described as being performed by another set of components of the device 600. Further, one or more method steps described in any of the embodiments may be performed utilizing a plurality of devices 600 in communication with one another.[1] An apparatus implemented at a gNodeB (gNB), the apparatus configured to: receive a request from a User Equipment (UE) to activate one or more Network Energy Saving (NES) Secondary Cells (SCells); identify at least one NES SCell based on at least one of the received request, a location of the UE, and a preferred list of NES SCells; prepare a configuration of the identified at least one NES SCell for the UE; transmit a Radio Resource Control (RRC) reconfiguration message indicating the configuration of the identified at least one NES SCell to the UE; initiate the identified at least one NES SCell to transmit one or more on-demand Synchronization Signal Blocks (on-demand SSBs) to the UE; receive measurement reports for the transmitted one or more on-demand SSBs of the identified at least one NES SCell; and activate the identified at least one NES SCell for the UE.[2] The apparatus as described in [1], wherein to prepare the configuration of the identified at least one NES SCell for the UE, the apparatus is configured to: receive measurement reports from the UE for the one or more SCells; determine a valid list of SCells associated with a Primary Cell (PCell) of the gNB based at least one of UE assistance information or the received measurement reports; and prepare the configuration of the identified at least one NES SCell for the UE based on the determined valid list of SCells,wherein the UE assistance information comprises one or more of non-overlapping coverage information, neighbor cell information, other cells reported in the measurement report, and a location of the UE in the PCell.[3] The apparatus as described in any one of [l]-[2], is further configured to: transmit an activation confirmation of the at least one NES SCell based on the received measurement report, to the UE.[4] The apparatus as described in any one of

[0001] -

[0003] , wherein to receive the request to activate the one or more NES SCells, the apparatus is configured to: receive an UE assistance information message including an unsatisfactory bitrate requesting SCell activation cause, from the UE, wherein the unsatisfactory bitrate requesting SCell activation cause is based on one or more Key Performance Indicators (KPIs) associated with the UE, and wherein one or more KPIs comprises at least one of a Guaranteed Bit Rate (GBR), an Allocation and Retention Priority (ARP), a Maximum Bit Rate (MBR), and an Adaptive MBR (AMBR).[5] A method comprising: receiving, by a gNodeB (gNB), a request from a User Equipment (UE) to activate one or more Network Energy Saving (NES) Secondary Cells (SCells); identifying, by the gNB, at least one NES SCell based on at least one of the received request from a UE, a location of the UE, and a preferred list of NES SCells; preparing, by the gNB, a configuration of the identified at least one NES SCell for the UE; transmitting, by the gNB, a Radio Resource Control (RRC) reconfiguration message indicating the configuration of the identified at least one NES SCell to the UE;initiating, by the gNB, the identified at least one NES SCell to transmit one or more on-demand Synchronization Signal Blocks (on-demand SSBs) to the UE; receiving, by the gNB, measurement reports for the transmitted one or more on-demand SSBs of the identified at least one NES SCell; and activating, by the gNB, the identified at least one NES SCell for the UE.[6] The method as described in [5], wherein preparing the configuration of the identified at least one NES SCell for the UE comprises: receiving, by the gNB, measurement reports from the UE for the one or more SCells; determining, by the gNB, a valid list of SCells associated with a Primary Cell (PCell) of the gNB based at least on UE assistance information or the received measurement reports; and configuring, by the gNB, the identified at least one NES SCell for the UE based on the determined valid list of SCells, wherein the UE assistance information comprises one or more of non-overlapping coverage information, neighbor cell information, other cells reported in the measurement report, and a location of the UE in the PCell.[7] The method as described in any one of [5]-[6], further comprising: transmitting, by the gNB, an activation confirmation of the at least one NES SCell based on the received measurement report, to the UE.[8] The method as described in any one of [5]-[7] wherein receiving the request to activate the one or more NES SCells comprises: receiving, by the gNB, an UE assistance information message including an unsatisfactory bitrate requesting SCell activation cause, from the UE, wherein the unsatisfactory bitrate requesting SCellactivation cause is based on one or more Key Performance Indicators (KPIs) associated with the UE, and wherein one or more KPIs comprises at least one of a Guaranteed Bit Rate (GBR), an Allocation and Retention Priority (ARP), a Maximum Bit Rate (MBR), and an Adaptive MBR (AMBR).[9] The method as described in any one of [5]-[8], further comprising: monitoring, by the UE, one or more KPIs; comparing, by the UE, the one or more KPIs with corresponding one or more threshold values to determine whether the one or more KPIs are unsatisfactory; upon determining the one or more KPIs are unsatisfactory, identifying, by the UE, the one or more NES SCells associated with the gNB based on information in a System Information Block (SIB) of a Primary Cell (PCell) associated with the gNB; transmitting, by the UE to the gNB, a request to activate at least one of the identified one or more NES SCells; and in response to the transmitted request, receiving, by the UE, the one or more on-demand SSBs from the one of the identified one or more NES SCells.

[0010] The method as described in any one of [5]-[9], wherein identifying the one or more NES SCells associated with the gNB comprises: receiving, by the UE, a list of NES SCells in Energy Saving (ES) mode on the SIB of the PCell from the gNB; identifying, by the UE, the one or more NES SCells based on the received list of NES SCells.

[0011] The method as described in any one of [5]-

[0010] , wherein identifying the one or more NESSCells associated with the gNB comprises: identifying, by the UE, the one or more NES SCells based on the historical Carrier Aggregation (CA) configuration information in one of a current or a previous connected mode session.

[0012] The method as described in any one of [5]-[l 1], further comprising: in response to the received one or more on-demand SSBs, transmitting, by the UE, a measurement report corresponding to each of the one or more NES SCells; and receiving, by the UE, the activation confirmation of one or more NES SCells based on the transmitted measurement report from the gNB.

[0013] The method as described in any one of [5]-[l 2], wherein transmitting the request to activate at least one of the identified one or more NES SCells comprises: transmitting, by the UE, the request via one of a Radio Resource Control (RRC) signaling or L1 / L2 signaling, wherein the request corresponds to an activation of Carrier Aggregation (CA) to improve the one or more KPIs of the UE.

[0014] The method as described in any one of [5]-[l 3], wherein transmitting the request to activate the at least one of the identified one or more NES SCells comprises: updating, by the UE, a UE assistance information message to include an unsatisfactory bitrate requesting SCell activation cause; and transmitting, by the UE, the UE assistance information message to the gNB.

[0015] A system comprising: a gNodeB (gNB) in communication with a User Equipment (UE), wherein the gNB is configured to:receive a request from a User Equipment (UE) to activate one or more Network Energy Saving (NES) Secondary Cells (SCells); identify at least one NES SCell based on at least one of the received request, a location of the UE, and a preferred list of NES SCells; prepare a configuration of the identified at least one NES SCell for the UE; transmit a Radio Resource Control (RRC) reconfiguration message indicating the configuration of the identified at least one NES SCell to the UE; initiate the identified at least one NES SCell to transmit one or more on-demand Synchronization Signal Blocks (on-demand SSBs) to the UE; receive measurement reports for the transmitted one or more on-demand SSBs of the identified at least one NES SCell; and activate the identified at least one NES SCell for the UE.

[0016] The system as described in

[0015] , wherein to prepare the configuration of the identified at least one NES SCell for the UE, the gNB is configured to: receive measurement reports from the UE for the one or more Scells; determine a valid list of SCells associated with a Primary Cell (PCell) of the gNB based at least one of UE assistance information or the received measurement reports; and prepare the configuration of the identified at least one NES SCell for the UE based on the determined valid list of SCells, wherein the UE assistance information comprises one or more of non-overlapping coverage information, neighbor cell information, other cells reported in the measurement report, and a location of the UE in the PCell.

[0017] The system as described in any one of

[0015] -

[0016] , wherein the gNB is further configured to: transmit an activation confirmation of the at least one NES SCell based on the received measurement report, to the UE.

[0018] The system as described in any one of

[0015] -

[0017] , wherein to receive the request to activate the one or more NES SCells, the gNB is configured to: receive an UE assistance information message including an unsatisfactory bitrate requesting SCell activation cause, from the UE, wherein the unsatisfactory bitrate requesting SCell activation cause is based on one or more Key Performance Indicators (KPIs) associated with the UE, and wherein one or more KPIs comprises at least one of a Guaranteed Bit Rate (GBR), an Allocation and Retention Priority (ARP), a Maximum Bit Rate (MBR), and an Adaptive MBR (AMBR).

[0019] The system as described in any one of

[0015] -

[0018] , wherein the UE is configured to: monitor one or more Key Performance Indicators (KPIs) associated with data transmission with a gNodeB (gNB); compare the one or more KPIs with corresponding one or more threshold values to determine whether the one or more KPIs are unsatisfactory; upon determining the one or more KPIs are unsatisfactory, identify one or more Network Energy Saving (NES) Secondary Cells (SCells) associated with the gNB based on information in a System Information Block (SIB) of a Primary Cell (PCell) associated with the gNB; transmit, to the gNB, a request to activate at least one of the identified one or more NES SCells; and in response to the transmitted request, receive, by the UE, the one or more on-demand SSBs from the one of the identified one or more NES SCells.

[0020] The system as described in any one of

[0015] -

[0019] , wherein the UE is further configured to: in response to the received one or more on-demand SSBs, transmit a measurement report corresponding to each of the one or more NES SCells; and receive the activation confirmation of one or more NES SCells based on the transmitted measurement report from the gNB (210).

[0021] A non-transitory computer-readable medium storing instructions, the instructions comprising: one or more instructions that, when executed by a gNodeB (gNB), the gNB comprising one or more processors, cause the one or more processors to: receive a request from a User Equipment (UE) to activate one or more Network Energy Saving (NES) Secondary Cells (SCells); identify at least one NES SCell based on at least one of the received request, a location of the UE, and a preferred list of NES SCells; prepare a configuration of the identified at least one NES SCell for the UE; transmit a Radio Resource Control (RRC) reconfiguration message indicating the configuration of the identified at least one NES SCell to the UE; initialize the identified at least one NES SCell to transmit one or more on-demand Synchronization Signal Blocks (on-demand SSBs) to the UE; receive measurement reports for the transmitted one or more on-demand SSBs of the identified at least one NES SCell; and activate the identified at least one NES SCell for the UE.

[0087] The embodiments disclosed herein can be implemented through at least one software program running on at least one hardware device and performing network management functionsto control the elements. The elements can be at least one of a hardware device, or a combination of hardware devices and software modules.

[0088] It is understood that terms including “unit” or “module” at the end may refer to the unit for processing at least one function or operation and may be implemented in hardware, software, or a combination of hardware and software.

[0089] While specific language has been used to describe the disclosure, any limitations arising on account of the same are not intended. As would be apparent to a person in the art, various working modifications may be made to the method in order to implement the inventive concept as taught herein.

[0090] The drawings and the forgoing description give examples of embodiments. Those skilled in the art will appreciate that one or more of the described elements may well be combined into a single functional element. Alternatively, certain elements may be split into multiple functional elements. Elements from one embodiment may be added to another embodiment. For example, orders of processes described herein may be changed and are not limited to the manner described herein.

[0091] Moreover, the actions of any flow diagram need not be implemented in the order shown; nor do all of the acts necessarily need to be performed. Also, those acts that are not dependent on other acts may be performed in parallel with the other acts. The scope of embodiments is by no means limited by these specific examples. Numerous variations, whether explicitly given in the specification or not, such as differences in structure, dimension, and use of material, are possible. The scope of embodiments is at least as broad as given by the following claims.

[0092] Benefits, other advantages, and solutions to problems have been described above with regard to specific embodiments. However, the benefits, advantages, solutions to problems, and any component(s) that may cause any benefit, advantage, or solution to occur or become more pronounced are not to be construed as a critical, required, or essential feature or component of any or all the claims.

[0093] 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 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 at least one embodiment, those skilled in the art will recognize that the embodiments herein can be practiced with modification within the spirit and scope of the embodiments as described herein.

Claims

We Claim:

1. An apparatus implemented at a gNodeB (gNB), the apparatus configured to: receive a request from a User Equipment (UE) to activate one or more Network Energy Saving (NES) Secondary Cells (SCells); identify at least one NES SCell based on at least one of the received request, a location of the UE, and a preferred list of NES SCells; prepare a configuration of the identified at least one NES SCell for the UE; transmit a Radio Resource Control (RRC) reconfiguration message indicating the configuration of the identified at least one NES SCell to the UE; initiate the identified at least one NES SCell to transmit one or more on-demand Synchronization Signal Blocks (on-demand SSBs) to the UE; receive measurement reports for the transmitted one or more on-demand SSBs of the identified at least one NES SCell; and activate the identified at least one NES SCell for the UE.

2. The apparatus as claimed in claim 1, wherein to prepare the configuration of the identified at least one NES SCell for the UE, the apparatus is configured to: receive measurement reports from the UE for the one or more SCells; determine a valid list of SCells associated with a Primary Cell (PCell) of the gNB based on at least one of UE assistance information or the received measurement reports; andprepare the configuration of the identified at least one NES SCell for the UE based on the determined valid list of SCells, wherein the UE assistance information comprises one or more of non-overlapping coverage information, neighbor cell information, other cells reported in the measurement report, and a location of the UE in the PCell.

3. The apparatus as claimed in claim 1, is further configured to: transmit an activation confirmation of the at least one NES SCell based on the received measurement report, to the UE.

4. The apparatus as claimed in claim 1, wherein to receive the request to activate the one or more NES SCells, the apparatus is configured to: receive an UE assistance information message including an unsatisfactory bitrate requesting SCell activation cause, from the UE, wherein the unsatisfactory bitrate requesting SCell activation cause is based on one or more Key Performance Indicators (KPIs) associated with the UE, and wherein one or more KPIs comprises at least one of a Guaranteed Bit Rate (GBR), an Allocation and Retention Priority (ARP), a Maximum Bit Rate (MBR), and an Adaptive MBR (AMBR).

5. A method comprising: receiving, by a gNodeB (gNB), a request from a User Equipment (UE) to activate one or more Network Energy Saving (NES) Secondary Cells (SCells);identifying, by the gNB, at least one NES SCell based on at least one of the received request from the UE, a location of the UE, and a preferred list of NES SCells; preparing, by the gNB, a configuration of the identified at least one NES SCell for the UE; transmitting, by the gNB, a Radio Resource Control (RRC) reconfiguration message indicating the configuration of the identified at least one NES SCell to the UE; initiating, by the gNB, the identified at least one NES SCell to transmit one or more on- demand Synchronization Signal Blocks (on-demand SSBs) to the UE; receiving, by the gNB, measurement reports for the transmitted one or more on-demand SSBs of the identified at least one NES SCell; and activating, by the gNB, the identified at least one NES SCell for the UE.

6. The method as claimed in claim 5, wherein preparing the configuration of the identified at least one NES SCell for the UE comprises: receiving, by the gNB, measurement reports from the UE for the one or more SCells; determining, by the gNB, a valid list of SCells associated with a Primary Cell (PCell) of the gNB based at least on UE assistance information or the received measurement reports; and configuring, by the gNB, the identified at least one NES SCell for the UE based on the determined valid list of SCells, wherein the UE assistance information comprises one or more of non-overlapping coverage information, neighbor cell information, other cells reported in the measurement report, and a location of the UE in the PCell.

7. The method as claimed in claim 5, further comprising: transmitting, by the gNB, an activation confirmation of the at least one NES SCell based on the received measurement report, to the UE.

8. The method as claimed in claim 5, wherein receiving the request to activate the one or more NES SCells comprises: receiving, by the gNB, a UE assistance information message including an unsatisfactory bitrate requesting SCell activation cause, from the UE, wherein the unsatisfactory bitrate requesting SCell activation cause is based on one or more Key Performance Indicators (KPIs) associated with the UE, and wherein one or more KPIs comprises at least one of a Guaranteed Bit Rate (GBR), an Allocation and Retention Priority (ARP), a Maximum Bit Rate (MBR), and an Adaptive MBR (AMBR).

9. The method as claimed in claim 5, further comprising: monitoring, by the UE, one or more KPIs; comparing, by the UE, the one or more KPIs with corresponding one or more threshold values to determine whether the one or more KPIs are unsatisfactory; upon determining the one or more KPIs are unsatisfactory, identifying, by the UE, the one or more NES SCells associated with the gNB based on information in a System Information Block (SIB) of a Primary Cell (PCell) associated with the gNB; transmitting, by the UE to the gNB, a request to activate at least one of the identified one or more NES SCells; andin response to the transmitted request, receiving, by the UE, the one or more on- demand SSBs from the one of the identified one or more NES SCells.

10. The method as claimed in claim 9, wherein identifying the one or more NES SCells associated with the gNB comprises: receiving, by the UE, a list of NES SCells in Energy Saving (ES) mode on the SIB1 of the PCell from the gNB; identifying, by the UE, the one or more NES SCells based on the received list of NES SCells.

11. The method as claimed in claim 9, wherein identifying the one or more NES SCells associated with the gNB comprises: identifying, by the UE, the one or more NES SCells based on the historical Carrier Aggregation (CA) configuration information in one of a current or a previous connected mode session.

12. The method as claimed in claim 9, further comprising: in response to the received one or more on-demand SSBs, transmitting, by the UE, a measurement report corresponding to each of the one or more NES SCells; and receiving, by the UE, the activation confirmation of one or more NES SCells based on the transmitted measurement report from the gNB.

13. The method as claimed in claim 9, wherein transmitting the request to activate at least one of the identified one or more NES SCells comprises: transmitting, by the UE, the request via one of a Radio Resource Control (RRC) signaling or L1 / L2 signaling, wherein the request corresponds to an activation of Carrier Aggregation (CA) to improve the one or more KPIs of the UE.

14. The method as claimed in claim 9, wherein transmitting the request to activate the at least one of the identified one or more NES SCells comprises: updating, by the UE, a UE assistance information message to include an unsatisfactory bitrate requesting SCell activation cause; and transmitting, by the UE, the UE assistance information message to the gNB.

15. A system comprising: a gNodeB (gNB) in communication with a User Equipment (UE), wherein the gNB is configured to: receive a request from the UE to activate one or more Network Energy Saving (NES) Secondary Cells (SCells); identify at least one NES SCell based on at least one of the received request, a location of the UE, and a preferred list of NES SCells; prepare a configuration of the identified at least one NES SCell for the UE; transmit a Radio Resource Control (RRC) reconfiguration message indicating the configuration of the identified at least one NES SCell to the UE;initiate the identified at least one NES SCell to transmit one or more on- demand Synchronization Signal Blocks (on-demand SSBs) to the UE; receive measurement reports for the transmitted one or more on-demand SSBs of the identified at least one NES SCell; and activate the identified at least one NES SCell for the UE.

16. The system as claimed in claim 15, wherein to prepare the configuration of the identified at least one NES SCell for the UE, the gNB is configured to: receive measurement reports from the UE for the one or more Scells; determine a valid list of SCells associated with a Primary Cell (PCell) of the gNB based at least one of UE assistance information or the received measurement reports; and prepare the configuration of the identified at least one NES SCell for the UE based on the determined valid list of SCells, wherein the UE assistance information comprises one or more of non-overlapping coverage information, neighbor cell information, other cells reported in the measurement report, and a location of the UE in the PCell.

17. The system as claimed in claim 15, wherein the gNB is further configured to: transmit an activation confirmation of the at least one NES SCell based on the received measurement report, to the UE.

18. The system as claimed in claim 15, wherein to receive the request to activate the one or more NES SCells, the gNB is configured to: receive a UE assistance information message including an unsatisfactory bitrate requesting SCell activation cause, from the UE, wherein the unsatisfactory bitrate requesting SCell activation cause is based on one or more Key Performance Indicators (KPIs) associated with the UE, and wherein one or more KPIs comprises at least one of a Guaranteed Bit Rate (GBR), an Allocation and Retention Priority (ARP), a Maximum Bit Rate (MBR), and an Adaptive MBR (AMBR).

19. The system as claimed in claim 15, wherein the UE is configured to: monitor one or more Key Performance Indicators (KPIs) associated with data transmission with the gNB; compare the one or more KPIs with corresponding one or more threshold values to determine whether the one or more KPIs are unsatisfactory; upon determining the one or more KPIs are unsatisfactory, identify one or more Network Energy Saving (NES) Secondary Cells (SCells) associated with the gNB based on information in a System Information Block (SIB) of a Primary Cell (PCell) associated with the gNB; transmit, to the gNB, a request to activate at least one of the identified one or moreNES SCells; and in response to the transmitted request, receive the one or more on-demand SSBs from the one of the identified one or more NES SCells.

20. The system as claimed in claim 15, wherein the UE is further configured to: in response to the received one or more on-demand SSBs, transmit a measurement report corresponding to each of the one or more NES SCells; and receive the activation confirmation of one or more NES SCells based on the transmitted measurement report from the gNB.

Images