Component carrier activation and deactivation

Abstract

Aspects of the present disclosure generally relate to wireless communications. In some aspects, a user equipment (UE) may receive an indication of at least one of a time configuration for deactivation of a cell, a deactivation type for the deactivation of the cell, or a discontinuous reception (DRX) configuration for the deactivation of the cell. The UE may receive signaling indicating deactivation of the cell. The UE may deactivate the cell according to at least one of the time configuration, the deactivation type, or the DRX configuration. Numerous other aspects are described.

Description

Technical Field

[0001] This patent application claims priority to U.S. Patent Application No. 18 / 055,685, titled "COMPONENT CARRIER ACTIVATION AND DEACTIVATION", filed on November 15, 2022, and assigned to the assignee of this patent application. The disclosure of the prior application is considered to be a part of this patent application and is incorporated herein by reference. Technical Field

[0003] Aspects of the present disclosure generally relate to wireless communication and relate to techniques and apparatuses for component carrier activation and deactivation. Background Art

[0004] Wireless communication systems are widely deployed to provide various telecommunication services such as telephony, video, data, messaging, broadcasting, or other similar types of services. These wireless communication systems may employ multiple access techniques capable of supporting communication with those users by sharing available wireless communication system resources among multiple users.

[0005] Despite the significant technological advancements made in wireless communication systems over the years, challenges still remain. For example, complex and dynamic environments can still attenuate or block signals between a wireless transmitter and a wireless receiver. Accordingly, there is a continuing expectation to improve the technical performance of wireless communication systems, including, for example: improving the speed and data carrying capacity of communication, improving the efficiency of using the shared communication medium, reducing the power consumed by the transmitter and receiver when performing communication, improving the reliability of wireless communication, avoiding redundant transmission and / or reception and associated processing, improving the coverage area of wireless communication, increasing the number and types of devices that can access the wireless communication system, increasing the ability of different types of devices to communicate with each other, increasing the number and types of available wireless communication media, etc. Therefore, there is a need to further improve wireless communication systems to overcome the aforementioned technical challenges and other challenges. Summary of the Invention

[0006] One aspect provides a method for wireless communication by a user equipment (UE). The method includes: receiving an indication of at least one of: a time configuration for deactivation of a cell, a type of deactivation for the deactivation of the cell, or a discontinuous reception (DRX) configuration for the deactivation of the cell; receiving a signaling indicating deactivation of the cell; and deactivating the cell according to at least one of the time configuration, the type of deactivation, or the DRX configuration.

[0007] On the other hand, there is provided a method for wireless communication by a network entity. The method includes: outputting an indication of at least one of the following: a time configuration for deactivation of a cell for a UE, a type of deactivation for the deactivation of the cell, or a DRX configuration for the deactivation of the cell; and outputting a signaling indicating the deactivated cell.

[0008] In other aspects, there is provided: an apparatus operable to, configured to, or otherwise adapted to perform any one or more of the foregoing methods and / or those methods described herein with reference to the accompanying drawings and illustrated in the drawings and the specification; a non-transitory computer-readable medium comprising instructions that, when executed by a processor of the apparatus, cause the apparatus to perform the foregoing methods and those methods described herein with reference to the accompanying drawings and illustrated in the drawings and the specification; a computer program product embodied on a computer-readable storage medium, the computer-readable storage medium comprising code for performing the foregoing methods and those methods described herein with reference to the accompanying drawings and illustrated in the drawings and the specification; and / or an apparatus comprising components for performing the foregoing methods and those methods described herein with reference to the accompanying drawings and illustrated in the drawings and the specification. By way of example, an apparatus may include a processing system, a device having a processing system, or a processing system cooperating via one or more networks.

[0009] The features and technical advantages of examples in accordance with the present disclosure have been outlined rather broadly above so that the detailed description that follows may be better understood. Additional features and advantages will be described hereinafter. The disclosed concepts and specific examples may be readily utilized as a basis for modifying or designing other structures for carrying out the same purposes of the present disclosure. Such equivalent constructions do not depart from the scope of the appended claims. The characteristics of the concepts disclosed herein, both as to their organization and operation methods, as well as the associated advantages, will be better understood when considered in conjunction with the following description taken in connection with the accompanying drawings. Each of the accompanying drawings is provided for purposes of illustration and description and is not a definition of the limits of the claims.

[0010] While aspects are described herein by way of illustration of some examples, those skilled in the art will understand that such aspects can be implemented in many different arrangements and scenarios. The techniques described herein can be implemented using different platform types, devices, systems, shapes, sizes, and / or packaging arrangements. For example, some aspects can be implemented via an integrated chip implementation or other non-module component-based devices (e.g., end-user devices, vehicles, communication devices, computing devices, industrial equipment, retail / shopping devices, medical devices, and / or artificial intelligence devices). Aspects can be implemented in chip-level components, modular components, non-modular components, non-chip-level components, device-level components, and / or system-level components. Devices incorporating the described aspects and features can include additional components and features for implementing and practicing the claimed and described aspects. For example, the transmission and reception of wireless signals can include one or more components for analog and digital purposes (e.g., hardware components including antennas, radio frequency (RF) chains, power amplifiers, modulators, buffers, processors, interleavers, adders, and / or summers). The aspects described herein are intended to be practiced in a wide variety of devices, components, systems, distributed arrangements, and / or end-user devices of various sizes, shapes, and configurations. BRIEF DESCRIPTION OF THE DRAWINGS

[0011] To gain a more specific understanding of the above-described features of the present disclosure, a more detailed description can be obtained by reference to the aspects, some of which are illustrated in the drawings. However, it should be noted that the drawings only illustrate certain typical aspects of the present disclosure and are therefore not considered to limit its scope, as the specification may admit other equally valid aspects. The same reference numerals in different drawings can identify the same or similar elements.

[0012] Figure 1 Depicts an example of a wireless network in accordance with the present disclosure.

[0013] Figure 2 Depicts aspects of an example base station (BS) and user equipment (UE) in accordance with the present disclosure.

[0014] Figure 3 Depicts an example decomposed base station architecture.

[0015] Figure 4A 、 Figure 4B 、 Figure 4C and Figure 4D Depicts aspects of a data structure for a wireless communication network (such as Figure 1 the wireless network) in accordance with the present disclosure.

[0016] Figure 5 Is a diagram illustrating an example of carrier aggregation in accordance with the present disclosure.

[0017] Figure 6 is a diagram of an example associated with component carrier activation and deactivation in accordance with the present disclosure.

[0018] Figure 7 illustrates a method of wireless communication by a UE in accordance with the present disclosure.

[0019] Figure 8 illustrates a method of wireless communication by a network entity in accordance with the present disclosure.

[0020] Figure 9 depicts aspects of an example communication device in accordance with the present disclosure.

[0021] Figure 10 depicts aspects of an example communication device in accordance with the present disclosure. DETAILED DESCRIPTION

[0022] Aspects of the present disclosure provide apparatuses, methods, processing systems, and computer-readable media for component carrier activation and deactivation.

[0023] Telecommunication networks, such as cellular networks, consume energy. Reducing energy consumption is one way to make cellular networks more pervasive and accessible. With respect to user equipment (UE), an energy-saving opportunity occurs. Generally, a UE may be configured with multiple component carriers (also referred to as “cells”) for transmitting and receiving signals from other network components. Energy can be saved by deactivating and reactivating one or more of the component carriers, particularly those that are not needed for short periods of time. The deactivation and reactivation can be performed dynamically (e.g., using dynamic signaling such as radio resource control or downlink control information signaling indicating activation or deactivation of a particular cell) or semi-statically (e.g., where a schedule for activating and deactivating cells, or one or more power-saving states of the cells, is configured).

[0024] However, frequently deactivating and reactivating component carriers can cause problems. For example, when one or more component carriers are reactivated, certain configuration parameters, such as automatic gain control parameters, may need to be updated. Also, there may be situations where it is beneficial for the UE to deactivate the radio frequency (RF) chain associated with a deactivated carrier (e.g., power off, switch to a low-power mode), and other situations where it is not beneficial for the UE to deactivate the RF chain. This is particularly true for component carriers that are deactivated for long periods of time.

[0025] One way for a UE to operate more efficiently and implement energy-saving techniques is for the UE to receive information about the time and / or type of deactivation and act on that information. The information can include, for example, how long a component carrier will be deactivated, whether the deactivation is associated with a sleep mode, the type of capabilities affected by the deactivation, etc.

[0026] Providing the foregoing information to the UE may allow the UE to solve the foregoing problems regarding the frequent deactivation and reactivation of component carriers. For example, if the UE knows how long the component carrier will be deactivated and / or the nature of the deactivation (e.g., sleep mode, RF deactivation, baseband deactivation), the UE may decide whether to update the appropriate configuration parameters for component carrier reactivation.

[0027] Aspects of the present disclosure are described more fully hereinafter with reference to the accompanying drawings. However, the present disclosure may be embodied in many different forms and should not be construed as limited to any specific structure or function presented throughout this disclosure. Rather, these aspects are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the present disclosure to those skilled in the art. Those skilled in the art should understand that the scope of the present disclosure is intended to cover any aspect of the disclosure disclosed herein, whether implemented independently of or in combination with any other aspect of the disclosure. For example, any number of the aspects described herein may be used to implement an apparatus or practice a method. In addition, the scope of the present disclosure is intended to cover such an apparatus or method practiced using other structures, functionality, or a combination of structures and functionality in addition to or different from the aspects of the disclosure described herein. It should be understood that any aspect of the disclosure disclosed herein may be embodied by one or more elements of the present invention.

[0028] Several aspects of a telecommunications system will now be presented with reference to various apparatuses and techniques. These apparatuses and techniques will be described in the following detailed description and illustrated in the accompanying drawings by various blocks, modules, components, circuits, steps, processes, algorithms, etc. (collectively referred to as "elements"). These elements may be implemented using hardware, software, or a combination thereof. Whether such elements are implemented as hardware or software depends upon the particular application and design constraints imposed on the overall system.

[0029] Although terms generally associated with 5G or New Radio (NR) radio access technology (RAT) may be used herein to describe aspects, aspects of the present disclosure may be applied to other RATs, such as 3G RAT, 4G RAT, and / or post-5G (e.g., 6G) RATs.

[0030] Figure 1 An example of a wireless network 100 in accordance with the present disclosure is depicted.

[0031] Generally speaking, the wireless network 100 includes various network entities (alternatively, network elements or network nodes). Network entities are typically communication devices and / or communication functions performed by communication devices (e.g., user equipment (UE), base station (BS), components of the BS, servers, etc.). For example, the various functions of the network and the various devices associated with and interacting with the network can be regarded as network entities. In addition, the wireless network 100 includes a terrestrial aspect and a non-terrestrial aspect. The terrestrial aspect is such as terrestrial-based network entities (e.g., BS 110), and the non-terrestrial aspect is such as satellite 140 and aircraft 145. The non-terrestrial aspect may include airborne network entities (e.g., one or more BSs) capable of communicating with other network elements (e.g., terrestrial BSs) and UEs.

[0032] In the depicted example, the wireless network 100 includes BS 110, UE 120, and one or more core networks such as the evolved packet core (EPC) 160 and the 5G core (5GC) 190, which interoperate to provide communication services over various communication links (including wired and wireless links).

[0033] Figure 1 Depicted are various example UEs 120, which may include: cellular phones, smart phones, session initiation protocol (SIP) phones, laptop computers, personal digital assistants (PDAs), satellite radios, global positioning system units, multimedia devices, video devices, digital audio players, cameras, game consoles, tablet computers, smart devices, wearable devices, vehicles, electricity meters, air pumps, kitchen appliances, healthcare devices, implants, sensors / actuators, displays, Internet of Things (IoT) devices, always-on (AON) devices, edge processing devices, or another device. UE 120 may also more generally be referred to as a mobile device, wireless device, wireless communication device, station, mobile station, subscriber station, mobile subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, remote device, access terminal, mobile terminal, wireless terminal, remote terminal, or handset, etc.

[0034] BS 110 may communicate wirelessly with UE 120 via communication link 170 (e.g., send signals to or receive signals from the UE). The communication link 170 between BS 110 and UE 120 may carry an uplink (UL) (also referred to as a reverse link) transmission from UE 120 to BS 110 and / or a downlink (DL) (also referred to as a forward link) transmission from BS 110 to UE 120. In various aspects, the communication link 170 may use multiple-input multiple-output (MIMO) antenna technology, including spatial multiplexing, beamforming, and / or transmit diversity.

[0035] BS110 may generally include, for example, a NodeB, an enhanced NodeB (eNB), a next-generation enhanced NodeB (ng-eNB), a next-generation NodeB (gNB or gNodeB), an access point, a transceiver base station, a radio base station, a radio transceiver, a transceiver function, a transmit receive point, and / or others. BS110 may provide communication coverage for a corresponding geographic coverage area 112, which may sometimes be referred to as a cell and which may, in some cases, overlap (e.g., a small cell provided by BS110a may have a coverage area 112' that overlaps the coverage area 112 of a macro cell). For example, a BS may provide communication coverage for a macro cell (covering a relatively large geographic area), a pico cell (covering a relatively small geographic area, such as a stadium), a femto cell (covering a relatively small geographic area (e.g., a home)), and / or other types of cells.

[0036] Although BS110 is depicted as a single communication device in various aspects, BS110 may be implemented in various configurations. For example, one or more components of the base station may be decomposed, including a central unit (CU), one or more distributed units (DU), one or more radio units (RU), a near-real-time (near-RT) RAN intelligent controller (RIC), or a non-real-time (non-RT) RIC, to name a few examples. In another example, various aspects of the base station may be virtualized. More generally, a base station (e.g., BS110) may include components located at a single physical location or components located at various physical locations. In an example where the base station includes components located at various physical locations, the various components may each perform a function such that the various components together achieve functionality similar to that of a base station located at a single physical location. In some aspects, a base station including components located at various physical locations may be referred to as a decomposed radio access network architecture (such as an open RAN (O-RAN) or a virtualized RAN (VRAN) architecture). Figure 3 An example decomposed base station architecture is depicted and described.

[0037] The different BSs 110 within the wireless network 100 may also be configured to support different radio access technologies (such as 3G, 4G, and / or 5G and other examples). For example, a BS 110 configured for 4G LTE (collectively referred to as the evolved universal mobile telecommunications system (UMTS) terrestrial radio access network (E-UTRAN)) may interface with the EPC 160 via a first backhaul link 132 (e.g., the S1 interface). A BS 110 configured for 5G (e.g., 5G NR or next-generation RAN (NG-RAN)) may interface with the 5GC 190 via a second backhaul link 184. The BSs 110 may communicate directly or indirectly (e.g., via the EPC 160 or 5GC 190) with each other on a third backhaul link 134 (e.g., the X2 interface), which may be wired or wireless.

[0038] The wireless network 100 may subdivide the electromagnetic spectrum into various categories, frequency bands, channels, or other characteristics. In some aspects, the subdivision is provided based on wavelength and frequency, where the frequency may also be referred to as a carrier, sub-carrier, channel, tone, or sub-band. For example, 3GPP currently defines frequency range 1 (FR1) as including 410 megahertz (MHz) - 7125 MHz, which is commonly (interchangeably) referred to as "below 6 GHz". Similarly, 3GPP currently defines frequency range 2 (FR2) as including 24,250 MHz - 52,600 MHz, which is sometimes (interchangeably) referred to as "millimeter wave" ("mmW" or "mmWave"). A base station configured to communicate using a mmWave or near mmWave radio frequency band (e.g., a mmWave base station such as BS110b) may utilize beamforming with a UE (e.g., 120) (e.g., as shown by 182) to improve path loss and range.

[0039] The communication link 170 between a BS 110 and, for example, a UE 120 may use one or more carriers, which may have different bandwidths (e.g., 5 MHz, 10 MHz, 15 MHz, 20 MHz, 100 MHz, 400 MHz, and / or other bandwidths) and may be aggregated in various ways. The carriers may or may not be adjacent to each other in frequency. In some examples, the allocation of carriers may be asymmetric with respect to DL and UL (e.g., more or fewer carriers may be allocated for DL compared to UL).

[0040] Compared to communication at lower frequencies, communication using a higher frequency band may have higher path loss and shorter range. Accordingly, certain base stations (e.g., Figure 1The base station 110b) in can utilize beamforming with the UE 120 to improve path loss and range, as shown at 182. For example, BS110b and UE 120 can each include multiple antennas, such as antenna elements, antenna panels, and / or antenna arrays, to facilitate beamforming. In some cases, BS110b can send beamformed signals to UE 120 in one or more transmission directions 182'. UE 120 can receive beamformed signals from BS110b in one or more reception directions 182". UE 120 can also send beamformed signals to BS110b in one or more transmission directions 182". BS110b can also receive beamformed signals from UE 120 in one or more reception directions 182'. Then, BS110b and UE 120 can perform beam training to determine the optimal reception and transmission directions for each of BS110b and UE 120. It is noted that the transmission direction and reception direction of BS110b can be the same or can be different. Similarly, the transmission direction and reception direction of UE 120 can be the same or can be different.

[0041] The wireless network 100 can include a Wi-Fi AP 150 that communicates with a Wi-Fi station (STA) 152 (e.g., UE 120) via a communication link 154 in, for example, the 2.4 GHz and / or 5 GHz unlicensed spectrum.

[0042] Certain UEs 120 can communicate with each other using device-to-device (D2D) communication links 158. The D2D communication links 158 can use one or more sidelink channels, such as the physical sidelink broadcast channel (PSBCH), the physical sidelink discovery channel (PSDCH), the physical sidelink shared channel (PSSCH), the physical sidelink control channel (PSCCH), and / or the physical sidelink feedback channel (PSFCH).

[0043] The EPC 160 can include various functional components, including: a mobility management entity (MME) 161, other MMEs 162, a serving gateway 163, a multimedia broadcast multicast service (MBMS) gateway 164, a broadcast multicast service center (BM-SC) 165, and / or a packet data network (PDN) gateway 166, such as in the depicted example. The MME 161 can communicate with a home subscriber server (HSS) 167. The MME 161 is a control node that processes signaling between the UE 120 and the EPC 160. Generally speaking, the MME 161 provides bearer and connection management.

[0044] User Internet Protocol (IP) packets can be transmitted through the Serving Gateway 163, which is connected to the PDN Gateway 166. The PDN Gateway 166 provides UE IP address allocation and other functions. The PDN Gateway 166 and the BM-SC 165 are connected to the IP service 168, which may include, for example, the Internet, an intranet, an IP Multimedia Subsystem (IMS), a Packet-Switched (PS) streaming service, and / or other IP services.

[0045] The BM-SC 165 can provide functions for MBMS user service provisioning and delivery. The BM-SC 165 can serve as an entry point for content provider MBMS transmissions, can be used to authorize and initiate MBMS bearer services within a Public Land Mobile Network (PLMN), and / or can be used to schedule MBMS transmissions. The MBMS Gateway 164 can be used to distribute MBMS services to the BS110 belonging to a Multicast Broadcast Single Frequency Network (MBSFN) area for a particular service being broadcast, and / or can be responsible for session management (e.g., session start / stop) and for collecting eMBMS-related charging information.

[0046] The 5GC 190 can include various functional components, including: an Access and Mobility Management Function (AMF) 191, other AMF 192, a Session Management Function (SMF) 193, and a User Plane Function (UPF) 194. The AMF 191 can communicate with the Unified Data Management (UDM) 195.

[0047] The AMF 191 is a control node that processes the signaling between the UE 120 and the 5GC 190. The AMF 191 provides, for example, Quality of Service (QoS) flow and session management.

[0048] IP packets are transmitted through the UPF 194, which is connected to the IP service 196 and provides UE IP address allocation and other functions for the 5GC 190. The IP service 196 may include, for example, the Internet, an intranet, an IMS, a PS streaming service, and / or other IP services.

[0049] In various aspects, by way of example, a network entity or network node can be implemented as an aggregated base station, a disaggregated base station, a component of a base station, an Integrated Access and Backhaul (IAB) node, a relay node, a sidelink node, or a Transmission and Reception Point (TRP).

[0050] As indicated above, Figure 1 is provided as an example. Other examples may be different from the examples described with respect to Figure 1 which are provided.

[0051] Figure 2 depicts aspects of an example BS110 and UE 120 in accordance with the present disclosure.

[0052] BS110 includes various processors (e.g., 220, 230, 238, and 240), antennas 234a - 234t (collectively 234), transceivers 232a - 232t (collectively 232) including modulators and demodulators, and other aspects that implement wireless transmission of data (e.g., data source 212) and wireless reception of data (e.g., data sink 239). For example, BS110 can transmit and receive data between BS110 and UE 120. BS110 includes a controller / processor 240 that can be configured to implement various functions described herein related to wireless communication.

[0053] UE 120 includes various processors (e.g., 258, 264, 266, and 280), antennas 252a - 252r (collectively 252), transceivers 254a - 254r (collectively 254) including modulators and demodulators, and other aspects that implement wireless transmission of data (e.g., retrieved from data source 262) and wireless reception of data (e.g., provided to data sink 260). UE 120 includes a controller / processor 280 that can be configured to implement various functions described herein related to wireless communication.

[0054] Regarding an example downlink transmission, BS110 includes a transmit processor 220 that can receive data from data source 212 and control information from controller / processor 240. This control information can be for the physical broadcast channel (PBCH), physical control format indicator channel (PCFICH), physical hybrid automatic repeat request (HARQ) indicator channel (PHICH), physical downlink control channel (PDCCH), group common PDCCH (GC PDCCH), and / or others. In some examples, the data can be for the physical downlink shared channel (PDSCH).

[0055] The transmit processor 220 can process (e.g., encode and symbol map) the data and control information to obtain data symbols and control symbols respectively. The transmit processor 220 can also generate reference symbols (such as for the primary synchronization signal (PSS), secondary synchronization signal (SSS), PBCH demodulation reference signal (DMRS), and channel state information reference signal (CSI - RS)).

[0056] The transmit (TX) multiple-input multiple-output (MIMO) processor 230 may perform spatial processing (e.g., precoding) on data symbols, control symbols, and / or reference symbols when applicable, and may provide an output symbol stream to a modulator (MOD) in transceivers 232a - 232t. Each modulator in transceivers 232a - 232t may process the corresponding output symbol stream to obtain an output sample stream. Each modulator may further process (e.g., convert to analog, amplify, filter, and up-convert) the output sample stream to obtain a downlink signal. The downlink signals from the modulators in transceivers 232a - 232t may be transmitted via antennas 234a - 234t, respectively.

[0057] To receive a downlink transmission, the UE 120 includes antennas 252a - 252r, which may receive downlink signals from the BS 110 and may provide the received signals to a demodulator (DEMOD) in transceivers 254a - 254r, respectively. Each demodulator in transceivers 254a - 254r may condition (e.g., filter, amplify, down-convert, and digitize) the corresponding received signal to obtain input samples. Each demodulator may further process the input samples to obtain received symbols.

[0058] The MIMO detector 256 may obtain received symbols from all demodulators in transceivers 254a - 254r, perform MIMO detection on the received symbols when applicable, and provide the detected symbols. The receive processor 258 may process (e.g., demodulate, de-interleave, and decode) the detected symbols, provide the decoded data for the UE 120 to the data sink 260, and provide the decoded control information to the controller / processor 280.

[0059] For an example uplink transmission, the UE 120 further includes a transmit processor 264, which may receive and process data from a data source 262 (e.g., for a physical uplink shared channel (PUSCH)) and control information from the controller / processor 280 (e.g., for a physical uplink control channel (PUCCH)). The transmit processor 264 may also generate reference symbols for a reference signal (e.g., for a sounding reference signal (SRS)). The symbols from the transmit processor 264 may be precoded by the TX MIMO processor 266 when applicable, further processed by a modulator in transceivers 254a - 254r (e.g., for SC-FDM), and transmitted to the BS 110.

[0060] At BS110, the uplink signal from UE 120 can be received by antennas 234a - 234t, processed by a demodulator in transceivers 232a - 232t, detected by MIMO detector 236 when applicable, and further processed by receive processor 238 to obtain the decoded data and control information transmitted by UE 120. Receive processor 238 can provide the decoded data to data sink 239 and the decoded control information to controller / processor 240. Memories 242 and 282 can store data and program codes for BS110 and UE 120 respectively. Scheduler 244 can schedule UEs for data transmission on the downlink and / or uplink.

[0061] In various aspects, BS110 can be described as transmitting and receiving various types of data associated with the methods described herein. In these contexts, "transmitting" can refer to various mechanisms for outputting data, such as outputting data from data source 212, scheduler 244, memory 242, transmit processor 220, controller / processor 240, TX MIMO processor 230, transceivers 232a - 232t, antennas 234a - 234t, and / or other aspects described herein. Similarly, "receiving" can refer to various mechanisms for obtaining data, such as obtaining data from antennas 234a - 234t, transceivers 232a - 232t, RX MIMO detector 236, controller / processor 240, receive processor 238, scheduler 244, memory 242, and / or other aspects described herein.

[0062] In various aspects, UE 120 can similarly be described as transmitting and receiving various types of data associated with the methods described herein. In these contexts, "transmitting" can refer to various mechanisms for outputting data, such as outputting data from data source 262, memory 282, transmit processor 264, controller / processor 280, TX MIMO processor 266, transceivers 254a - 254t, antennas 252a - 252t, and / or other aspects described herein. Similarly, "receiving" can refer to various mechanisms for obtaining data, such as obtaining data from antennas 252a - 252t, transceivers 254a - 254t, RX MIMO detector 256, controller / processor 280, receive processor 258, memory 282, and / or other aspects described herein.

[0063] In some aspects, a processor can be configured to perform various operations (such as those associated with the methods described herein) and send (output) data to or receive (obtain) data from another interface configured to send or receive data respectively.

[0064] Although Figure 2The boxes in [description] are illustrated as separate components, but the functionality described above for these boxes can be implemented in a single hardware, software, or combined component, or in various combinations of components. For example, the functionality described for the transmit processor 264, receive processor 258, and / or TX MIMO processor 266 can be performed by, or under the control of, the controller / processor 280.

[0065] As indicated above, Figure 2 is provided as an example. Other examples may be different from the examples described with respect to Figure 2 which.

[0066] The deployment of a communication system (such as a 5G NR system) can be arranged with various components or constituent parts in a variety of ways. In a 5G NR system or network, network nodes, network entities, mobility elements of the network, RAN nodes, core network nodes, network elements, base stations, or network equipment can be implemented in an aggregated or disaggregated architecture. For example, a base station (such as Node B (NB), eNB, NR BS, 5G NB, AP, TRP, or cell, and other examples) or one or more units (or one or more components) performing base station functionality can be implemented as an aggregated base station (also referred to as a stand-alone base station or a monolithic base station) or a disaggregated base station. A "network entity" or "network node" can refer to a disaggregated base station or one or more units of a disaggregated base station (such as one or more CUs, one or more DUs, one or more RUs, or a combination thereof).

[0067] An aggregated base station (e.g., an aggregated network entity) can be configured to utilize a radio protocol stack that is physically or logically integrated within a single RAN node (e.g., within a single device or unit). A disaggregated base station (e.g., a disaggregated network entity) can be configured to utilize a protocol stack that is physically or logically distributed between two or more units (such as one or more CUs, one or more DUs, or one or more RUs). In some examples, a CU can be implemented within a network entity, and one or more DUs can be co-located with the CU, or alternatively, can be geographically or virtually spread across one or more other network nodes. A DU can be implemented to communicate with one or more RUs. Each of the CU, DU, and RU can also be implemented as a virtual unit, such as a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU), etc.

[0068] Base station type operations or network designs may consider the aggregation characteristics of base station functionality. For example, a disaggregated base station may be utilized in an IAB network, an open radio access network (O-RAN (such as a network configuration advocated by the O-RAN Alliance)), or a virtualized radio access network (vRAN, also known as a cloud radio access network (C-RAN)) to facilitate the scaling of a communication system by separating base station functionality into one or more units that can be deployed separately. A disaggregated base station may include functionality implemented across two or more units at various physical locations, as well as functionality virtualized for at least one unit, which can achieve flexibility in network design. Each unit of the disaggregated base station may be configured for wired or wireless communication with at least one other unit of the disaggregated base station.

[0069] Figure 3 An example disaggregated base station 300 architecture is depicted. The disaggregated base station 300 architecture may include one or more CUs 310, which may communicate directly with the core network 320 via a backhaul link, or indirectly with the core network 320 through one or more disaggregated base station units (such as a near real-time (near RT) RAN intelligent controller (RIC) 325 via an E2 link, or a non-real-time (non RT) RIC 315 associated with a service management and orchestration (SMO) framework 305, or both). The CU 310 may communicate with one or more DUs 330 via a respective midhaul link (such as an F1 interface). The DU 330 may communicate with one or more RUs 340 via a respective fronthaul link. The RU 340 may communicate with a respective UE 120 via one or more RF access links. In some specific implementations, the UE 120 may be served simultaneously by multiple RUs 340.

[0070] Each of the units (e.g., CU 310, DU 330, RU 340, and near RT RIC 325, non RT RIC 315, and SMO framework 305) may include one or more interfaces or be coupled to one or more interfaces that are configured to receive or transmit signals, data, or information (collectively referred to as signals) via a wired or wireless transmission medium. Each unit or an associated processor or controller that provides instructions to the communication interface of the unit may be configured to communicate with one or more of the other units via the transmission medium. For example, the units may include a wired interface that is configured to receive or transmit signals to one or more of the other units via a wired transmission medium. Additionally or alternatively, the unit may include a wireless interface that may include a receiver, a transmitter, or a transceiver (such as an RF transceiver) that is configured to receive or transmit signals or both to one or more of the other units over a wireless transmission medium.

[0071] In some aspects, the CU 310 may host one or more higher layer control functions. Such control functions may include Radio Resource Control (RRC), Packet Data Convergence Protocol (PDCP), Service Data Adaptation Protocol (SDAP), etc. Each control function may be implemented using an interface that is configured to communicate signals with other control functions hosted by the CU 310. The CU 310 may be configured to handle user plane functionality (e.g., Central Unit - User Plane (CU-UP)), control plane functionality (e.g., Central Unit - Control Plane (CU-CP)), or a combination thereof. In some embodiments, the CU 310 may be logically split into one or more CU-UP units and one or more CU-CP units. When implemented in an O-RAN configuration, the CU-UP units may communicate bidirectionally with the CU-CP units via an interface such as the E1 interface. As needed, the CU 310 may be implemented to communicate with the Distributed Unit (DU) 330 for network control and signaling.

[0072] The DU 330 may correspond to a logical unit that includes one or more base station functions for controlling the operation of one or more RUs 340. In some aspects, the DU 330 may host one or more of the Radio Link Control (RLC) layer, Media Access Control (MAC) layer, and one or more high Physical (PHY) layers (such as modules for forward error correction (FEC) encoding and decoding, scrambling, modulation and demodulation, etc.) at least in part depending on a function split (such as the function split defined by the 3rd Generation Partnership Project (3GPP)). In some aspects, the DU 330 may also host one or more low PHY layers. Each layer (or module) may be implemented using an interface that is configured to communicate signals with other layers (and modules) hosted by the DU 330 or with control functions hosted by the CU 310.

[0073] The lower layer functionality may be implemented by one or more RUs 340. In some deployments, the RUs 340 controlled by the DU 330 may correspond to logical nodes that host RF processing functions or low PHY layer functions (such as performing Fast Fourier Transform (FFT), Inverse FFT (iFFT), digital beamforming, Physical Random Access Channel (PRACH) extraction and filtering, etc.) or both at least in part based on a function split (such as a lower layer function split). In such an architecture, the RUs 340 may be implemented to handle over-the-air (OTA) communication with one or more UEs 120. In some embodiments, the real-time and non-real-time aspects of control plane and user plane communication with the RUs 340 may be controlled by the corresponding DU 330. In some scenarios, this configuration may enable the implementation of the DU 330 and CU 310 in a cloud-based RAN architecture such as a vRAN architecture.

[0074] The SMO framework 305 can be configured to support the RAN deployment and orchestration of non-virtualized network elements and virtualized network elements. For non-virtualized network elements, the SMO framework 305 can be configured to support the deployment of dedicated physical resources for RAN coverage requirements, which can be managed via an operation and maintenance interface (such as the O1 interface). For virtualized network elements, the SMO framework 305 can be configured to interact with a cloud computing platform (such as the Open Cloud (O-Cloud) 390) to perform network element lifecycle management (such as instantiating virtualized network elements) via a cloud computing platform interface (such as the O2 interface). Such virtualized network elements can include, but are not limited to, the CU 310, DU 330, RU 340, and near RT RIC 325. In some specific implementations, the SMO framework 305 can communicate with the hardware aspect of the 4G RAN (such as the Open eNB (O-eNB) 311) via the O1 interface. Additionally, in some specific implementations, the SMO framework 305 can communicate directly with one or more RUs 340 via the O1 interface. The SMO framework 305 can also include a non-RT RIC 315 configured to support the functionality of the SMO framework 305.

[0075] The non-RT RIC 315 can be configured to include logical functions that can enable non-real-time control and optimization of RAN elements and resources, artificial intelligence / machine learning (AI / ML) workflows including model training and updates, or policy-based guidance of applications / features in the near RT RIC 325. The non-RT RIC 315 can be coupled to or communicate with the near RT RIC 325 (such as via the A1 interface). The near RT RIC 325 can be configured to include logical functions that can enable near-real-time control and optimization of RAN elements and resources through an interface (such as via the E2 interface) via data collection and actions, which connects one or more CUs 310, one or more DUs 330, or both, and the O-eNB to the near RT RIC 325.

[0076] In some specific implementations, to generate the AI / ML models to be deployed in the near RT RIC 325, the non-RT RIC 315 may receive parameters or external enrichment information from an external server. Such information can be utilized by the near RT RIC 325 and can be received from non-network data sources or from network functions at the SMO framework 305 or at the non-RT RIC 315. In some examples, the non-RT RIC 315 or the near RT RIC 325 may be configured to tune the RAN behavior or performance. For example, the non-RT RIC 315 may monitor the long-term trends and patterns of performance and employ AI / ML models to perform corrective actions via the SMO framework 305 (such as reconfiguration via O1) or via creating RAN management policies (such as A1 policies).

[0077] As indicated above, Figure 3 is provided as an example. Other examples may be different from the examples described with respect to Figure 3 the example described.

[0078] Figure 4A , Figure 4B , Figure 4C and Figure 4D depict aspects of data structures for a wireless communication network (such as Figure 1 the wireless network 100) according to the present disclosure. Figure 4A is a diagram 400 that illustrates an example of a first subframe within a 5G (e.g., 5G NR) frame structure, Figure 4B is a diagram 430 that illustrates an example of a DL channel within a 5G subframe, Figure 4C is a diagram 450 that illustrates an example of a second subframe within a 5G frame structure, and Figure 4D is a diagram 480 that illustrates an example of a UL channel within a 5G subframe.

[0079] A wireless communication system may utilize orthogonal frequency division multiplexing (OFDM) with a cyclic prefix (CP) on the uplink and downlink. Such systems may also support half-duplex operation using time division duplexing (TDD). OFDM and single carrier frequency division multiplexing (SC-FDM) divide (e.g., as depicted in Figure 4B and Figure 4D ) the system bandwidth into multiple orthogonal subcarriers. Each subcarrier can be modulated with data. Modulation symbols can be transmitted in the frequency domain using OFDM and / or in the time domain using SC-FDM.

[0080] The wireless communication frame structure can be frequency division duplexing (FDD), where for a specific set of subcarriers, the subframes within that set of subcarriers are dedicated to either DL or UL. The wireless communication frame structure can also be time division duplexing (TDD), where for a specific set of subcarriers, the subframes within that set of subcarriers are dedicated to both DL and UL.

[0081] In Figure 4A and Figure 4C , the radio communication frame structure is TDD, where D is DL, U is UL, and F is flexibly used between DL / UL. The UE can be configured with a slot format by a received Slot Format Indicator (SFI) (configured dynamically via Downlink Control Information (DCI) or semi-statically / statically via RRC signaling). In the depicted example, a 10 ms frame is divided into 10 equal-sized 1 ms subframes. Each subframe may include one or more slots. In some examples, each slot may include 7 or 14 symbols, depending on the slot format. A subframe may also include mini-slots, which typically have fewer symbols than an entire slot. Other radio communication technologies may have different frame structures and / or different channels.

[0082] In some aspects, the number of slots within a subframe is based on the slot configuration and the numerology. For example, for slot configuration 0, different numerologies (μ) 0 to 5 allow 1, 2, 4, 8, 16, and 32 slots per subframe, respectively. For slot configuration 1, different numerologies 0 to 2 allow 2, 4, and 8 slots per subframe, respectively. Accordingly, for slot configuration 0 and numerology μ, there are 14 symbols per slot and 2 μ slots per subframe. The subcarrier spacing and symbol length / duration are functions of the numerology. The subcarrier spacing can be equal to 2 μ × 15 kHz, where μ is the numerology index, which can be selected from values 0 to 5. Thus, the subcarrier spacing for numerology μ = 0 is 15 kHz, and the subcarrier spacing for numerology μ = 5 is 480 kHz. Other numerologies and subcarrier spacings can be used. The symbol length / duration is negatively correlated with the subcarrier spacing. Figure 4A , Figure 4B , Figure 4C and Figure 4D provide an example of slot configuration 0 with 14 symbols per slot and numerology μ = 2 with 4 slots per subframe. The slot duration is 0.25 ms, the subcarrier spacing is 60 kHz, and the symbol duration is approximately 16.67 μs.

[0083] As Figure 4A , Figure 4B , Figure 4C and Figure 4D depicted, a resource grid can be used to represent the frame structure. Each slot includes a Resource Block (RB) (also referred to as a Physical RB (PRB)) that extends, for example, 12 consecutive subcarriers. The resource grid is divided into multiple Resource Elements (REs). The number of bits carried by each RE depends on the modulation scheme.

[0084] As Figure 4AAs illustrated, some of the REs in the RE carry reference (pilot) signals (RSs) for a UE (e.g., UE 120). The RSs may include demodulation RSs (DMRSs) and / or channel state information reference signals (CSI-RSs) for channel estimation at the UE. The RSs may also include beam measurement RSs (BRSs), beam refinement RSs (BRRSs), and / or phase tracking RSs (PT-RSs).

[0085] Figure 4B Examples of various DL channels within a subframe of a frame are illustrated. The physical downlink control channel (PDCCH) carries DCI within one or more control channel elements (CCEs), each CCE including, for example, nine resource element groups (REGs), each REG including, for example, four consecutive RES in an OFDM symbol.

[0086] The primary synchronization signal (PSS) may be in symbol 2 of a specific subframe of a frame. The PSS is used by a UE (e.g., UE 120) to determine subframe / symbol timing and the physical layer identity.

[0087] The secondary synchronization signal (SSS) may be in symbol 4 of a specific subframe of a frame. The SSS is used by the UE to determine the physical layer cell identity group number and radio frame timing.

[0088] Based on the physical layer identity and the physical layer cell identity group number, the UE may determine the physical cell identifier (PCI). Based on the PCI, the UE may determine the location of the aforementioned DMRS. The physical broadcast channel (PBCH) carrying the master information block (MIB) may be logically grouped with the PSS and SSS to form a synchronization signal (SS) / PBCH block (SSB). The MIB provides the number of resource blocks (RBs) in the system bandwidth and the system frame number (SFN). The physical downlink shared channel (PDSCH) carries user data, broadcast system information not transmitted via the PBCH (such as system information blocks (SIBs)), and / or paging messages.

[0089] As Figure 4CAs illustrated, some of the REs in the RE carry DMRS for channel estimation at the base station (indicated as R for one particular configuration, but other DMRS configurations are possible). The UE can send DMRS for PUCCH and DMRS for PUSCH. The PUSCH DMRS can be sent, for example, in the one or two symbols preceding the PUSCH. The PUCCH DMRS can be sent in different configurations depending on whether a short PUCCH or a long PUCCH is sent and depending on the particular PUCCH format used. The UE 120 can send a sounding reference signal (SRS). The SRS can be sent, for example, in the last symbol of the subframe. The SRS can have a comb structure, and the UE can send the SRS on one of these comb teeth. The SRS can be used by the base station for channel quality estimation to enable frequency-dependent scheduling of the UL.

[0090] Figure 4D Examples of various UL channels within a subframe of a frame are illustrated. The PUCCH can be located at the position indicated in one configuration. The PUCCH carries uplink control information (UCI), such as a scheduling request, a channel quality indicator (CQI), a precoding matrix indicator (PMI), a rank indicator (RI), and HARQ ACK / NACK feedback. The PUSCH carries data and can additionally be used to carry a buffer status report (BSR), a power headroom report (PHR), and / or UCI.

[0091] Figure 5 Is a diagram illustrating Example 500 of carrier aggregation according to the present disclosure.

[0092] Carrier aggregation is a technique that enables two or more component carriers (CCs, sometimes referred to as carriers or cells) to be combined (e.g., combined into a single channel) for a single UE 120 to enhance data capacity. As shown in the figure, carriers can be combined in the same or different frequency bands. Additionally or alternatively, continuous or discontinuous carriers can be combined. The network node 110 can configure carrier aggregation for the UE 120, such as in an RRC message, DCI, and / or another signaling message.

[0093] As indicated by reference numeral 505, in some aspects, carrier aggregation can be configured in an in-band continuous mode, where the aggregated carriers are contiguous with each other and in the same frequency band. As indicated by reference numeral 510, in some aspects, carrier aggregation can be configured in an in-band discontinuous mode, where the aggregated carriers are non-contiguous with each other and in the same frequency band. As indicated by reference numeral 515, in some aspects, carrier aggregation can be configured in an inter-band discontinuous mode, where the aggregated carriers are non-contiguous with each other and in different frequency bands.

[0094] In carrier aggregation, the UE 120 may be configured with a primary carrier or primary cell (PCell) and one or more secondary carriers or secondary cells (SCells). In some aspects, the primary carrier may carry control information (e.g., downlink control information and / or scheduling information) for scheduling data communications on one or more secondary carriers, which may be referred to as cross-carrier scheduling. In some aspects, a carrier (e.g., the primary carrier or a secondary carrier) may carry control information for scheduling data communications on that carrier, which may be referred to as self-carrier scheduling or carrier self-scheduling.

[0095] In some examples, a CC may be dynamically activated or deactivated, or switched to a network energy-saving state or out of the network energy-saving state, as detailed below. In some examples, "dynamic deactivation" may include disabling communications on the CC such that the UE 120 does not receive or transmit communications (including reference signaling) on the CC. In some examples, the network energy-saving state may indicate a deactivated state, a reduced number of antennas, a reduced transmit power, a reduced amount of reference signaling, etc. In some examples, a network entity may dynamically deactivate a CC such that the network entity may power down (or reduce the power consumption of) the RU providing the CC to the UE 120. For example, in some cases, dynamic deactivation may be characterized by the turning off of one or more radio resources (e.g., RUs, antenna panels) providing the CC, while "non-dynamic" deactivation (such as deactivation of a CC via DCI, not in the context of network energy saving) may be characterized by the one or more radio resources continuing to operate such that reference signaling may continue to be transmitted on the CC. It should be noted that the dynamic deactivation of a CC and / or the indication of the network energy-saving state may be implemented using DCI signaling, RRC signaling, a combination thereof, or another form of signaling (e.g., a configuration for semi-static scheduling for dynamic activation and / or deactivation and / or network energy-saving state). It should also be noted that the techniques described herein may apply to both dynamic activation / deactivation and non-dynamic activation / deactivation. As used herein, in the context of a CC, "activation" and "deactivation" may refer to dynamic activation / deactivation or non-dynamic activation / deactivation. The term "activation / deactivation" may refer to an operation that causes a CC to become activated, an operation that causes a CC to become deactivated, an operation that causes a CC to become reactivated, and / or a combination thereof.

[0096] As indicated above, Figure 5 is provided as an example. Other examples may be different from the examples described with respect to Figure 5 which are described.

[0097] A cell can be deactivated (e.g., dynamically deactivated) to reduce network energy consumption. However, dynamically deactivating a cell may introduce problems. For example, a UE may not know whether certain configuration parameters, such as automatic gain control (AGC) parameters, should be updated when the cell is reactivated. AGC parameters are used to adjust the received signal strength. Failure to update the AGC parameters can result in undesirable effects, such as amplifying noise, clipping the received signal, etc., which can inhibit the UE's ability to operate properly. Another example is that there may be some cases where it is beneficial for the UE to deactivate the RF chain associated with a deactivated carrier (e.g., power off, switch to a low-power mode), and other cases where it is not beneficial for the UE to deactivate the RF chain. For example, when the carrier is to be deactivated for a long period of time, it may be beneficial for the UE to deactivate the RF chain.

[0098] Some of the techniques described herein provide an indication of at least one of the following: a time configuration for deactivating a cell, a deactivation type for deactivating a cell, or a discontinuous reception (DRX) configuration for deactivating a cell; receiving signaling indicating deactivation of a cell; and deactivating a cell according to at least one of the time configuration, deactivation type, or DRX configuration. Using the time configuration, deactivation type, and / or DRX configuration, the UE can schedule the deactivation and reactivation of a cell. For example, the UE can determine whether to update certain configuration parameters based on the duration of deactivation, the type of deactivation, etc. Thus, the UE can avoid problems such as amplifying noise, clipping the received signal, etc.

[0099] Some of the techniques described herein include a network entity outputting an indication of at least one of the following: a time configuration for deactivating a cell of a UE, a deactivation type for deactivating a cell, or a DRX configuration for deactivating a cell; and outputting signaling indicating deactivation of a cell. By communicating the time configuration, deactivation type, and / or DRX configuration to the UE, the network entity can increase the likelihood that the UE can facilitate the frequent deactivation and reactivation of a cell, resulting in reduced energy consumption without adversely affecting the operation of the UE.

[0100] Figure 6 is a diagram of example 600 associated with component carrier activation and deactivation according to the present disclosure. As Figure 6 shown, a network entity (e.g., network node 110, CU, DU, and / or RU) can communicate with a user equipment (e.g., UE 120). In some aspects, the network entity and the UE can be part of a wireless network (e.g., wireless network 100). In some aspects, the UE and the network entity can have established a wireless connection (e.g., RRC connection) before the operations Figure 6 shown. Regarding Figure 6Activation and deactivation of the described cell can be implemented for dynamic activation / deactivation, non-dynamic activation / deactivation, or indication of activation or deactivation of the network energy saving state, as described elsewhere in this document.

[0101] As shown by reference numeral 605, the network entity may output deactivation information, and the UE may receive the deactivation information. The deactivation information may include time configuration, deactivation type, DRX configuration, combinations thereof, etc. In some aspects, the time configuration may indicate the time when the cell is to be deactivated. In some aspects, the time configuration may indicate the length of time for which the cell is to be deactivated. After this length of time, the UE may assume that the cell is activated. In some aspects, the time configuration may indicate the minimum amount of time for which the cell is to remain deactivated. In such cases, the UE may assume that the cell will not be reactivated until the minimum amount of time has elapsed.

[0102] In some aspects, the deactivation type may indicate deactivation modes such as RF deactivation (i.e., deactivating certain RF operations) and / or baseband deactivation (i.e., deactivating certain baseband operations). In some aspects, the deactivation type may indicate that the network entity will operate in a sleep mode (i.e., at least some components of the network entity such as DU, RU, antenna panel, antenna sub-panel, etc. are deactivated). If the network entity knows (or can estimate) the amount of time required to reactivate the cell, the network entity may indicate to the UE which capabilities can be deactivated and which capabilities should remain active. The network entity may make such a determination based on one or more UE capabilities and the expected time required to deactivate and / or reactivate the cell. The UE capabilities may be sent from the UE and provided to the network entity. In some aspects, the capabilities sent from the UE may indicate that the UE supports dynamic activation / deactivation of the cell. In some aspects, the capabilities may further indicate one or more parameters regarding the capabilities, such as the expected handover time (e.g., from the active state to the deactivated state or vice versa), supported network energy saving states, combinations thereof, etc.

[0103] In some aspects, the deactivation information may include a DRX configuration for deactivation of the cell. In some aspects, the UE may receive an explicit or implicit indication to start DRX operation for a given amount of time (such as the amount of time until the cell is closed). The UE may be configured with multiple DRX configurations and a mapping between the deactivation time and / or deactivation type and the corresponding DRX configuration. When the network signals the deactivation time or deactivation type, the UE may start DRX operation using the corresponding DRX configuration, as discussed in more detail below. The DRX configuration may include one or more parameters related to DRX, such as periodicity, on-duration, length of the DRX operation (e.g., a given amount of time), resources for the DRX operation, etc.

[0104] In some aspects, deactivation information may be provided in the configuration of a cell. For example, the deactivation information may be provided to the UE via RRC configuration. In such cases, each cell may be configured with a handover time and / or type. The "handover time and / or type" may refer to or indicate a deactivation time, a deactivation type, a reactivation time, a reactivation type, a combination thereof, etc. As discussed below, upon receiving a deactivation signal indicating activation or deactivation of a cell, the UE may determine the handover time and / or type for the cell from the RRC configuration. If the RRC configuration is lost, the UE may assume that the deactivation or reactivation is permanent.

[0105] As indicated by reference numeral 610, the UE may be configured for cell deactivation. In some aspects, the UE may be configured to perform cell deactivation based on the received deactivation information. In some aspects, the UE may configure (e.g., deactivate, activate, switch to a network energy-saving state) one or more cells according to the deactivation information.

[0106] As indicated by reference numeral 615, the network entity may output deactivation signaling, and the UE may receive the deactivation signaling. The deactivation signaling may command the UE to deactivate one or more cells according to the deactivation information. In some aspects, such as when the time configuration indicates the time at which the cell is to be deactivated, the UE may deactivate the cell without the explicit deactivation signaling at 615. In some aspects, the deactivation information at 605 or the reception of the deactivation information at 605 may be used as the deactivation signal at 615. For example, as an alternative form of the RRC signaling discussed above, the deactivation information may be provided via deactivation DCI. For example, the deactivation DCI may include one or more bits or an invalid non-scheduled DCI combination mapped to an index in an RRC configuration table (e.g., configured at 605) that provides the handover time and / or type.

[0107] As indicated by reference numeral 620, the UE may deactivate the cell. The UE may deactivate the cell according to the deactivation information. In some aspects, the UE may deactivate the cell at the time indicated by the time configuration. In some aspects, the UE may deactivate the cell for a duration indicated by the time configuration. In some aspects, the UE may deactivate the cell according to the deactivation type. For example, the UE may deactivate the cell according to a sleep mode (e.g., RF deactivation or baseband deactivation) or other deactivation modes indicated by the deactivation information. In some aspects, deactivating the cell according to a sleep mode or other deactivation modes may include deactivating the cell for a pre-determined amount of time, deactivating certain features (such as RF or baseband operations), etc.

[0108] As indicated by reference numeral 625, the UE may perform DRX operations when the cell is deactivated. The DRX operations may include the UE operating in an idle or inactive mode, which results in increased energy savings when the cell is deactivated. For example, the UE may monitor for wake-up signals or paging for the UE (e.g., on the deactivated cell or a different cell). In some aspects, the DRX operations may start after the cell is deactivated. In some aspects, the DRX operations may be completed before the cell is reactivated. In some aspects, the UE may perform DRX operations for a given amount of time (e.g., indicated by a DRX configuration, amount of time until the cell is reactivated, etc.).

[0109] As indicated by reference numeral 630, the UE may reactivate the cell based on deactivation information. In some aspects, the UE may reactivate the cell at least in part based on a time configuration. In some aspects, the time configuration may indicate a minimum amount of time for which the cell is to be deactivated. In such aspects, the UE may reactivate the cell after the minimum amount of time has elapsed. In some aspects, the UE may reactivate the cell according to reactivation signaling output by a network entity. The reactivation signaling may configure the UE to reactivate one or more deactivated cells.

[0110] In some aspects, reactivating the cell may include updating one or more configuration parameters. For example, the UE may update an AGC parameter. Whether to update one or more of the configuration parameters may be at least in part based on the minimum amount of time for which the cell is to be deactivated or the length of time for which the cell has been deactivated. The likelihood that one or more of the configuration parameters will need to be updated may be proportional to the length of the minimum amount of time or the length of time. That is, a longer length of time may result in a greater chance that the UE will need to update one or more of the configuration parameters. As another example, if the minimum amount of time or the length of time meets a threshold, the UE may update the configuration parameters, and if the minimum amount of time or the length of time fails to meet the threshold, the configuration parameters may not be updated.

[0111] In some aspects, the UE may reactivate the cell according to the type of deactivation. As discussed above, the type of deactivation may indicate a sleep mode and / or a deactivation mode. In such cases, reactivation of the cell may include the UE resuming certain operations on the cell, including RF operations and / or baseband operations.

[0112] As discussed above, using a time configuration, a deactivation type, and / or a DRX configuration, a UE can schedule deactivation and reactivation of a cell. That is, the UE can determine whether to update certain configuration parameters based on the duration of the deactivation, the type of deactivation, etc., and potentially avoid problems such as amplified noise, clipping of received signals, etc. Additionally, by communicating the time configuration, deactivation type, and / or DRX configuration to the UE, a network entity can increase the likelihood that the UE can facilitate frequent deactivation and reactivation of the cell, resulting in reduced energy consumption without adversely affecting the operation of the UE.

[0113] As indicated above, Figure 6 is provided as an example. Other examples may be different from the example described with respect to Figure 6 what is described.

[0114] Figure 7 FIG. 700 illustrates a method for wireless communication by a UE (such as UE 120).

[0115] Method 700 begins at 710, where an indication of at least one of the following is received: a time configuration for deactivation of a cell, a deactivation type for deactivation of a cell, or a DRX configuration for deactivation of a cell. For example, the UE (e.g., using Figure 9 the transceiver 908, code 931, and / or circuitry 921 depicted, or any combination thereof) may receive an indication of at least one of the following: a time configuration for deactivation of a cell, a deactivation type for deactivation of a cell, or a DRX configuration for deactivation of a cell, as described above.

[0116] Then, method 700 proceeds to step 720, where signaling indicating deactivation of the cell is received. For example, the UE (e.g., using Figure 9 the transceiver 908, circuitry 922, and / or code 932 depicted, or any combination thereof) may receive signaling indicating deactivation of the cell, as described above.

[0117] Then, method 700 proceeds to step 730, where the cell is deactivated according to at least one of the time configuration, deactivation type, or DRX configuration. For example, the UE (e.g., using Figure 9 the circuitry 923 and / or code 933 depicted, or any combination thereof) may deactivate the cell according to at least one of the time configuration, deactivation type, or DRX configuration, as described above.

[0118] In one aspect, method 700 further includes deactivating the cell according to at least one of the time configuration, deactivation type, or DRX configuration.

[0119] In a first aspect, the indication is time-configured, and the time configuration indicates the time at which the cell is to be deactivated.

[0120] In a second aspect, either alone or in combination with the first aspect, the indication is time-configured, and the time configuration defines at least a minimum amount of time for which the cell is to be deactivated.

[0121] In a third aspect, either alone or in combination with one or more of the first and second aspects, method 700 includes reactivating the cell after the minimum amount of time has elapsed.

[0122] In a fourth aspect, either alone or in combination with one or more of the first to third aspects, method 700 includes updating an automatic gain control value before reactivating the cell.

[0123] In a fifth aspect, either alone or in combination with one or more of the first to fourth aspects, method 700 includes updating an automatic gain control value if the minimum amount of time exceeds a predetermined threshold.

[0124] In a sixth aspect, either alone or in combination with one or more of the first to fifth aspects, the indication is of the deactivation type, and the deactivation type includes at least one of RF deactivation or baseband deactivation.

[0125] In a seventh aspect, either alone or in combination with one or more of the first to sixth aspects, the indication is of the deactivation type, where the deactivation type includes at least one of a sleep mode or a deactivation mode.

[0126] In an eighth aspect, either alone or in combination with one or more of the first to seventh aspects, the indication is of the DRX configuration, and method 700 includes starting DRX operation when the cell is deactivated.

[0127] In a ninth aspect, either alone or in combination with one or more of the first to eighth aspects, the DRX configuration defines a time interval for DRX operation, where the time interval is shorter than the amount of time for which the cell is to be deactivated.

[0128] In a tenth aspect, either alone or in combination with one or more of the first to ninth aspects, method 700 includes completing DRX operation when the cell is deactivated.

[0129] In an eleventh aspect, either alone or in combination with one or more of the first to tenth aspects, the indication is included in downlink control information.

[0130] In a twelfth aspect, either alone or in combination with one or more of the first to eleventh aspects, the indication is included in radio resource control signaling.

[0131] In one aspect, method 700 or any aspect related thereto may be performed by a device such as Figure 9 communication device 900, which includes various components operable to, configured to, or adapted to perform method 700. Communication device 900 is described in more detail below.

[0132] Note that Figure 7 this is merely an example of a method, and according to the present disclosure, other methods including fewer, additional, or alternative steps are possible.

[0133] Figure 8 Method 800 for wireless communication by a network entity such as network node 110 or a decomposed base station as discussed with respect to Figure 3 is shown.

[0134] Method 800 begins at 810, where an indication of at least one of the following is output: a deactivation time configuration for a cell for a UE, a deactivation type for cell deactivation, or a DRX configuration for cell deactivation. For example, a network entity (e.g., using Figure 10 transceiver 1008, code 1031, circuitry 1021, or a combination thereof as depicted) may output an indication of at least one of the following: a deactivation time configuration for a cell for a UE, a deactivation type for cell deactivation, or a DRX configuration for cell deactivation, as described above.

[0135] Method 800 then proceeds to step 820, where signaling indicating deactivation of the cell is output. For example, a network entity (e.g., using Figure 10 transceiver 1008, code 1031, circuitry 1021, or a combination thereof) may output signaling indicating deactivation of the cell, as described above.

[0136] In a first aspect, the indication is of a time configuration, where the time configuration indicates the time at which the cell is to be deactivated.

[0137] In a second aspect, either alone or in combination with the first aspect, the time configuration defines at least a minimum amount of time for which the cell is to be deactivated.

[0138] In a third aspect, either alone or in combination with one or more of the first and second aspects, method 800 includes outputting signaling indicating reactivation of the cell after the minimum amount of time has elapsed.

[0139] In a fourth aspect, either alone or in combination with one or more of the first through third aspects, the indication is of a deactivation type, where the deactivation type includes at least one of RF deactivation or baseband deactivation.

[0140] In a fifth aspect, either alone or in combination with one or more of the first to fourth aspects, method 800 includes selecting a deactivation type based on UE capabilities and an expected handover time.

[0141] In a sixth aspect, either alone or in combination with one or more of the first to fifth aspects, the indication is for the deactivation type, where the deactivation type includes at least one of a sleep mode or a deactivation mode.

[0142] In a seventh aspect, either alone or in combination with one or more of the first to sixth aspects, the indication is included in downlink control information.

[0143] In an eighth aspect, either alone or in combination with one or more of the first to seventh aspects, the indication is included in radio resource control signaling.

[0144] In one aspect, method 800 or any aspect related thereto may be performed by a device such as Figure 10 communication device 1000, which includes various components operable to, configured to, or adapted to perform method 800. Communication device 1000 is described in more detail below.

[0145] Note that Figure 8 is merely an example of a method, and according to the present disclosure, other methods including fewer, additional, or alternative steps are possible.

[0146] Figure 9 Aspects of an example communication device 900 are depicted. In some aspects, communication device 900 is a user equipment, such as UE 120.

[0147] Communication device 900 includes a processing system 902 coupled to a transceiver 908 (e.g., a transmitter and / or a receiver). Transceiver 908 is configured to transmit and receive signals for communication device 900 via an antenna 910, such as the various signals described herein. Processing system 902 may be configured to perform the processing functions of communication device 900, including processing signals received by and / or to be transmitted by communication device 900.

[0148] Processing system 902 includes one or more processors 920. In various aspects, one or more processors 920 may represent one or more of a receiving processor 258, a transmitting processor 264, a TX MIMO processor 266, and / or a controller / processor 280, as described with respect to Figure 2As described. One or more processors 920 are coupled to the computer-readable medium / memory 930 via a bus 906. In some aspects, the computer-readable medium / memory 930 is configured to store instructions (e.g., computer-executable code) that, when executed by one or more processors 920, cause the one or more processors 920 to perform with respect to Figure 7 the method 700 described or any aspect related thereto. Note that references to processors that perform the functions of the communication device 900 may include one or more processors that perform the functions of the communication device 900.

[0149] In the depicted example, the computer-readable medium / memory 930 stores code (e.g., executable instructions) 931 for receiving an indication of at least one of a time configuration for deactivation of a cell, a deactivation type for deactivation of a cell, or a DRX configuration for deactivation of a cell; code 932 for receiving signaling indicating deactivation of a cell; code 933 for deactivating a cell according to at least one of a time configuration, a deactivation type, or a DRX configuration; code 934 for reactivating a cell after a minimum amount of time has elapsed; code 935 for updating an AGC value before reactivating a cell; code 936 for updating an AGC value if the minimum amount of time exceeds a predetermined threshold; and code 937 for completing a DRX operation when a cell is deactivated. Processing of the code 931-937 may cause the communication device 900 to perform with respect to Figure 7 the method 700 described or any aspect related thereto.

[0150] One or more processors 920 include circuitry configured to implement (e.g., execute) code stored in the computer-readable medium / memory 930, the circuitry including circuitry 921 for receiving an indication of at least one of a time configuration for deactivation of a cell, a deactivation type for deactivation of a cell, or a DRX configuration for deactivation of a cell; circuitry 922 for receiving signaling indicating deactivation of a cell; circuitry 923 for deactivating a cell according to at least one of a time configuration, a deactivation type, or a DRX configuration; circuitry 924 for reactivating a cell after a minimum amount of time has elapsed; circuitry 925 for updating an AGC value before reactivating a cell; circuitry 926 for updating an AGC value if the minimum amount of time exceeds a predetermined threshold; and circuitry 927 for completing a DRX operation when a cell is deactivated. Processing using the circuitry 921-927 may cause the communication device 900 to perform with respect to Figure 7 the method 700 described or any aspect related thereto.

[0151] The various components of the communication device 900 may provide for performing with respect to Figure 7Components of the described method 700 or any aspect related thereto. For example, components for transmitting, conveying, or outputting for transmission may include transceiver 254 and / or antenna 252 of UE 120, and / or Figure 9 transceiver 908 and antenna 910 of communication device 900 in Figure 9 . Components for receiving or obtaining may include transceiver 254 and / or antenna 252 of UE 120, and / or

[0152] Figure 10 Depicts aspects of an example communication device. In some aspects, communication device 1000 is a network entity, such as BS 110 or a split base station as discussed with respect to Figure 3 .

[0153] Communication device 1000 includes a processing system 1002 coupled to a transceiver 1008 (e.g., a transmitter and / or a receiver) and / or a network interface 1012. Transceiver 1008 is configured to transmit and receive signals for communication device 1000 via antenna 1010, such as the various signals described herein. Network interface 1012 is configured to obtain and convey signals for communication device 1000 via a communication link (such as a backhaul link, a midhaul link, and / or a fronthaul link as described herein with respect to Figure 3 ). Processing system 1002 may be configured to perform processing functions of communication device 1000, including processing signals received by communication device 1000 and / or to be transmitted by the communication device.

[0154] Processing system 1002 includes one or more processors 1020. In various aspects, one or more processors 1020 may represent one or more of receive processor 238, transmit processor 220, TX MIMO processor 230, and / or controller / processor 240, as described with respect to Figure 2 . One or more processors 1020 are coupled to a computer-readable medium / memory 1030 via a bus 1006. In certain aspects, computer-readable medium / memory 1030 is configured to store instructions (e.g., computer-executable code) that, when executed by one or more processors 1020, cause one or more processors 1020 to perform method 800 described with respect to Figure 8 or any aspect related thereto. Note that references to processors of communication device 1000 that perform functions may include one or more processors of communication device 1000 that perform the function.

[0155] In the depicted example, computer-readable medium / memory 1030 stores code 1031 (e.g., executable instructions) for outputting an indication of at least one of a time configuration for deactivating a cell for a UE, a deactivation type for deactivating a cell, or a DRX configuration for deactivating a cell; code 1032 for outputting signaling indicating deactivation of a cell; code 1033 for outputting signaling indicating reactivation of a cell after a minimum amount of time has elapsed; and code 1034 for selecting a deactivation type based on UE capabilities and an expected handover time. Processing of code 1031-1034 may cause communication device 1000 to perform with respect to Figure 8 the method 800 described or any aspect related thereto.

[0156] One or more processors 1020 include circuitry configured to implement (e.g., execute) the code stored in computer-readable medium / memory 1030, the circuitry including circuitry 1021 for outputting an indication of at least one of a time configuration for deactivating a cell for a UE, a deactivation type for deactivating a cell, or a DRX configuration for deactivating a cell; circuitry 1022 for outputting signaling indicating deactivation of a cell; circuitry 1023 for outputting signaling indicating reactivation of a cell after a minimum amount of time has elapsed; and circuitry 1024 for selecting a deactivation type based on UE capabilities and an expected handover time. Processing using circuitry 1021-1024 may cause communication device 1000 to perform with respect to Figure 8 the method 800 described or any aspect related thereto.

[0157] Various components of communication device 1000 may provide components for performing as described with respect to Figure 8 the method 800 described or any aspect related thereto. Components for transmitting, conveying, or outputting for transmission may include transceiver 232 and / or antenna 234 of BS110, and / or Figure 10 transceiver 1008 and antenna 1010 of communication device 1000 in Figure 10 . Components for receiving or obtaining may include transceiver 232 and / or antenna 234 of BS110, and / or

[0158] An overview of some aspects of the present disclosure is provided below:

[0159] Aspect 1: A method for wireless communication performed by a UE, the method comprising: receiving an indication of at least one of the following: a time configuration for deactivation of a cell, a deactivation type for the deactivation of the cell, or a DRX configuration for the deactivation of the cell; receiving a signaling indicating deactivation of the cell; and deactivating the cell according to at least one of the time configuration, the deactivation type, or the DRX configuration.

[0160] Aspect 2: The method according to aspect 1, wherein the indication is for the time configuration, and wherein the time configuration indicates the time at which the cell is to be deactivated.

[0161] Aspect 3: The method according to any one of aspects 1 or 2, wherein the indication is for the time configuration, and wherein the time configuration at least defines a minimum amount of time for which the cell is to be deactivated.

[0162] Aspect 4: The method according to aspect 3, the method further comprising: reactivating the cell after the minimum amount of time has elapsed.

[0163] Aspect 5: The method according to any one of aspects 3 or 4, the method further comprising: updating an automatic gain control value before reactivating the cell.

[0164] Aspect 6: The method according to any one of aspects 3 or 4, the method further comprising: updating an automatic gain control value when the minimum amount of time exceeds a predetermined threshold.

[0165] Aspect 7: The method according to aspect 1, wherein the indication is for the deactivation type, and wherein the deactivation type includes at least one of radio frequency deactivation or baseband deactivation.

[0166] Aspect 8: The method according to any one of aspects 1, 6 or 7, wherein the indication is for the deactivation type, and wherein the deactivation type includes at least one of a sleep mode or a deactivation mode.

[0167] Aspect 9: The method according to aspect 1, wherein the indication is for the DRX configuration, and wherein the method further comprises: starting DRX operation when the cell is deactivated.

[0168] Aspect 10: The method according to aspect 9, wherein the DRX configuration defines a time interval for the DRX operation, and wherein the time interval is shorter than the amount of time for which the cell is to be deactivated.

[0169] Aspect 11: The method according to any one of aspects 9 or 10, the method further comprising: completing the DRX operation when the cell is deactivated.

[0170] Aspect 12: The method according to any one of Aspects 1 to 11, wherein the indication is included in downlink control information.

[0171] Aspect 13: The method according to any one of Aspects 1 to 11, wherein the indication is included in radio resource control signaling.

[0172] Aspect 14: A method of wireless communication performed by a network entity, the method comprising: outputting an indication of at least one of: a time configuration for deactivating a cell for a UE, a deactivation type for the deactivation of the cell, or a discontinuous reception (DRX) configuration for the deactivation of the cell; and outputting a signaling indicating deactivation of the cell.

[0173] Aspect 15: The method according to Aspect 14, wherein the indication is for the time configuration, and wherein the time configuration indicates the time at which the cell is to be deactivated.

[0174] Aspect 16: The method according to any one of Aspects 14 to 15, wherein the time configuration defines at least a minimum amount of time for which the cell is to be deactivated.

[0175] Aspect 17: The method according to Aspect 16, the method further comprising: outputting a signaling indicating reactivation of the cell after the minimum amount of time has elapsed.

[0176] Aspect 18: The method according to Aspect 14, wherein the indication is for the deactivation type, and wherein the deactivation type includes at least one of radio frequency deactivation or baseband deactivation.

[0177] Aspect 19: The method according to Aspect 18, the method further comprising: selecting the deactivation type based on UE capabilities and an expected handover time.

[0178] Aspect 20: The method according to any one of Aspects 14, 18 or 19, wherein the indication is for the deactivation type, and wherein the deactivation type includes at least one of a sleep mode or a deactivation mode.

[0179] Aspect 21: The method according to any one of Aspects 14 to 20, wherein the indication is included in downlink control information.

[0180] Aspect 22: The method according to any one of Aspects 14 to 20, wherein the indication is included in radio resource control signaling.

[0181] Aspect 23: An apparatus for wireless communication at a device, the apparatus comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform the method according to one or more of Aspects 1 to 13.

[0182] Aspect 24: A device for wireless communication, the device comprising: a memory; and one or more processors coupled to the memory, the one or more processors configured to perform the method according to one or more of Aspects 1 to 13.

[0183] Aspect 25: An apparatus for wireless communication, the apparatus comprising: at least one component for performing the method according to one or more of Aspects 1 to 13.

[0184] Aspect 26: A non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by a processor to perform the method according to one or more of Aspects 1 to 13.

[0185] Aspect 27: A non-transitory computer-readable medium storing an instruction set for wireless communication, the instruction set comprising one or more instructions that, when executed by one or more processors of a device, cause the device to perform the method according to one or more of Aspects 1 to 13.

[0186] Aspect 28: An apparatus for wireless communication at a device, the apparatus comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform the method according to one or more of Aspects 14 to 22.

[0187] Aspect 29: A device for wireless communication, the device comprising: a memory; and one or more processors coupled to the memory, the one or more processors configured to perform the method according to one or more of Aspects 14 to 22.

[0188] Aspect 30: An apparatus for wireless communication, the apparatus comprising: at least one component for performing the method according to one or more of Aspects 14 to 22.

[0189] Aspect 31: A non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by a processor to perform the method according to one or more of Aspects 14 to 22.

[0190] Aspect 32: A non-transitory computer-readable medium storing an instruction set for wireless communication, the instruction set including one or more instructions that, when executed by one or more processors of a device, cause the device to perform the method according to one or more of Aspects 14 to 22.

[0191] The foregoing disclosure provides illustration and description, but is not intended to be exhaustive or to limit the aspects to the precise forms disclosed. Modifications and variations may be made in light of the above disclosure, or may be obtained from practice of the aspects.

[0192] As used herein, the term "component" is intended to be broadly construed as a combination of hardware and / or hardware and software. Whether called software, firmware, middleware, microcode, hardware description language, or other name, "software" shall be broadly construed to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, procedures, and / or functions, etc. As used herein, a "processor" is implemented in a combination of hardware and / or hardware and software. It will be apparent that the systems and / or methods described herein may be implemented by different forms of hardware and / or hardware and software combinations. The actual specific control hardware or software code used to implement these systems and / or methods does not limit the aspects. Accordingly, the operation and behavior of the systems and / or methods are not described herein with reference to specific software code, as those skilled in the art will understand that the software and hardware can be designed at least in part based on the description herein to implement the systems and / or methods.

[0193] As used herein, depending on the context, "meeting a threshold" may refer to a value greater than a threshold, greater than or equal to a threshold, less than a threshold, less than or equal to a threshold, equal to a threshold, not equal to a threshold, etc.

[0194] Although specific combinations of features are recited in the claims and / or disclosed in the specification, these combinations are not intended to limit the disclosure of the various aspects. Many of these features may be combined in ways not specifically recited in the claims and / or not disclosed in the specification. The disclosure of each aspect includes each dependent claim in combination with every other claim in the set of claims. As used herein, the phrase referring to a list of items “at least one of” refers to any combination of those items (which includes a single member). By way of example, “at least one of a, b, or c” is intended to cover a, b, c, a + b, a + c, b + c, and a + b + c, as well as any combination with multiple of the same element (e.g., a + a, a + a + a, a + a + b, a + a + c, a + b + b, a + c + c, b + b, b + b + b, b + b + c, c + c, and c + c + c, or any other ordering of a, b, and c).

[0195] Any element, act, or instruction used herein should not be construed as critical or essential unless explicitly so described. Additionally, as used herein, the article “a” is intended to include one or more items and may be used interchangeably with “one or more.” Additionally, as used herein, the article “the” is intended to include one or more items referred to in conjunction with the article “the” and may be used interchangeably with “one or more.” Additionally, as used herein, the terms “set” and “group” are intended to include one or more items and may be used interchangeably with “one or more.” If only intending to refer to a single item, the phrase “only one” or similar will be used. Additionally, as used herein, the terms “has,” “having,” etc. are intended to be open-ended terms that do not limit the elements they modify (e.g., an element “having” A may also have B). Additionally, the phrase “based on” is intended to mean “at least partially based on” unless otherwise explicitly stated. Additionally, as used herein, the term “or” when used in a series is intended to be open-ended and may be used interchangeably with “and / or” unless otherwise explicitly stated (e.g., if used in conjunction with “either” or “only one”).

[0196] The foregoing description is provided to enable any person skilled in the art to practice the various aspects described herein. The examples discussed herein do not limit the scope, applicability, or aspects set forth in the claims. Various modifications to these aspects will be apparent to those skilled in the art, and the general principles defined herein may be applied to other aspects. For example, the functions and arrangements of the elements discussed may be changed without departing from the scope of the disclosure. Various examples may omit, substitute, or add various procedures or components as appropriate. For example, the methods described may be performed in an order different from that described, and various actions may be added, omitted, or combined. In addition, features described with respect to some examples may be combined in some other examples. For example, any number of the aspects set forth herein may be used to implement a device or practice a method. Additionally, the scope of the present disclosure is intended to cover such devices or methods that are practiced using other structures, functionality, or a combination of structures and functionality that supplement or replace the various aspects of the present disclosure set forth herein. It should be understood that any aspect of the disclosure herein may be embodied by one or more elements of the present invention.

[0197] The various illustrative logical blocks, modules, and circuits described in connection with the present disclosure may be implemented or performed with a general purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device (PLD), discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. While a general purpose processor may be a microprocessor, in the alternative, the processor may be any commercially available processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in conjunction with a DSP core, a system on a chip (SoC), or any other such configuration).

[0198] As used herein, the term "determine" encompasses a variety of actions. For example, "determine" may include calculating, computing, processing, deriving, investigating, looking up (e.g., looking up in a table, database, or other data structure), ascertaining, etc. Additionally, "determine" may include receiving (e.g., receiving information), accessing (e.g., accessing data in a memory), etc. Further, "determine" may include parsing, selecting, picking, establishing, etc.

[0199] The methods disclosed herein include one or more acts for implementing the methods. The method acts may be interchanged with one another without departing from the scope of the claims. In other words, unless a specific order of the acts is specified, the order and / or use of a particular act may be modified without departing from the scope of the claims. Further, the various operations of the methods described above may be performed by any suitable component capable of performing the corresponding functions. The component may include various hardware and / or software components and / or modules, including but not limited to circuitry, an application specific integrated circuit (ASIC), or a processor.

[0200] The following claims are not intended to be limited to the aspects shown herein but should be accorded the full scope consistent with the claim language. In the claims, unless specifically stated otherwise, the recitation of a singular element is not intended to mean "one and only one" but rather "one or more." The term "some," unless specifically stated otherwise, means one or more. No claim element is to be construed under the provisions of 35 U.S.C. § 112(f), unless the element is expressly recited using the phrase "means for." All structural and functional equivalents of the elements of the various aspects described throughout this disclosure that are known or later become known to those of ordinary skill in the art are expressly incorporated herein by reference and are intended to be covered by the claims. Moreover, nothing disclosed herein is intended to be dedicated to the public, whether or not the disclosure is explicitly recited in the claims.

Claims

1. A method of wireless communication performed by a user equipment (UE), the method comprising: Receive an indication of at least one of the following: Time configuration for deactivation of a cell, Deactivation type for the deactivation of the cell, or Discontinuous reception (DRX) configuration for the deactivation of the cell; Receive signaling indicating deactivation of the cell; And Deactivate the cell according to at least one of the time configuration, the deactivation type, or the DRX configuration.

2. The method according to claim 1, wherein the indication is configured for the time, and wherein the time configuration indicates the time when the cell is to be deactivated.

3. The method according to claim 1, wherein the indication is configured for the time, and wherein the time configuration defines at least a minimum amount of time when the cell is to be deactivated.

4. The method according to claim 3, the method further comprising: Reactivate the cell after the minimum amount of time has elapsed.

5. The method according to claim 3, the method further comprising: Update the automatic gain control value before reactivating the cell.

6. The method according to claim 3, the method further comprising: Update the automatic gain control value if the minimum amount of time exceeds a predetermined threshold.

7. The method according to claim 1, wherein the indication is for the deactivation type, and wherein the deactivation type includes at least one of radio frequency deactivation or baseband deactivation.

8. The method according to claim 1, wherein the indication is for the deactivation type, wherein the deactivation type includes at least one of a sleep mode or a deactivation mode.

9. The method according to claim 1, wherein the indication is for the DRX configuration, and wherein the method further comprises: Start DRX operation when the cell is deactivated.

10. The method according to claim 9, wherein the DRX configuration defines a time interval for the DRX operation, wherein the time interval is shorter than the amount of time when the cell is to be deactivated.

11. The method according to claim 9, the method further comprising: Complete the DRX operation when the cell is deactivated.

12. The method according to claim 1, wherein the indication is included in downlink control information.

13. The method according to claim 1, wherein the indication is included in radio resource control signaling.

14. A method of wireless communication performed by a network entity, the method comprising: Output an indication of at least one of the following: Time configuration for deactivation of a cell for a user equipment (UE), Deactivation type for the deactivation of the cell, or Discontinuous reception (DRX) configuration for the deactivation of the cell; and Output signaling indicating deactivation of the cell.

15. The method according to claim 14, wherein the indication is configured for the time, and the time configuration indicates the time when the cell is to be deactivated.

16. The method according to claim 14, wherein the time configuration at least defines a minimum amount of time when the cell is to be deactivated.

17. The method according to claim 16, the method further comprising: Output signaling indicating reactivation of the cell after the minimum amount of time has elapsed.

18. The method according to claim 14, wherein the indication is for the type of deactivation, and the type of deactivation includes at least one of radio frequency deactivation or baseband deactivation.

19. The method according to claim 18, the method further comprising: Select the deactivation type based on UE capabilities and expected handover time.

20. The method according to claim 14, wherein the indication is for the type of deactivation, and the type of deactivation includes at least one of sleep mode or deactivation mode.

21. The method according to claim 14, wherein the indication is included in downlink control information.

22. The method according to claim 14, wherein the indication is included in radio resource control signaling.

23. A user equipment (UE) configured for wireless communication, the user equipment (UE) comprising: A memory including processor-executable instructions; And A processor configured to execute the processor-executable instructions and cause the UE to: Receive an indication of at least one of the following: Time configuration for deactivation of a cell, Deactivation type for the deactivation of the cell, or Discontinuous reception (DRX) configuration for the deactivation of the cell; Receive signaling indicating deactivation of the cell; And Deactivate the cell according to at least one of the time configuration, the deactivation type, or the DRX configuration.

24. A network entity configured for wireless communication, the network entity comprising: A memory including processor-executable instructions; And A processor configured to execute the processor-executable instructions and cause the network entity to: Output an indication of at least one of the following: Time configuration for deactivation of a cell for a user equipment (UE), Deactivation type for the deactivation of the cell, or Discontinuous reception (DRX) configuration for the deactivation of the cell; And Output signaling indicating deactivation of the cell.

Images