Energy-saving Time Division Duplex (TDD) mode

By introducing an energy-saving TDD mode, defining the unused TTI/slot/symbol state and implementing energy consumption optimization strategies, the problem that conventional TDD mode cannot promote network energy saving is solved, and higher energy efficiency and communication performance are achieved.

CN123125828APending Publication Date: 2026-11-17QUALCOMM INC
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202580028343.5
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Priority Date
2024-05-01
Filing Date
2025-04-02
Publication Date
2026-11-17

AI Technical Summary

Technical Problem

Conventional Time Division Duplex (TDD) mode has failed to effectively promote network energy saving (NES) because the state of fully or partially unused TTIs/slots/symbols is not defined, making it impossible to implement energy optimization strategies during these states.

Method used

Introduce an energy-saving TDD mode, defining completely unused TTI/slots/symbols (OFF state) or partially unused TTI/slots/symbols (power back-off state), and implement NES strategies such as shutting down component power or applying power back-off in these states.

Benefits of technology

By using the energy-saving TDD mode, the energy efficiency of wireless communication networks is improved and the overall performance is enhanced, while maintaining or improving the performance of the communication system.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN123125828A_ABST
    Figure CN123125828A_ABST
Patent Text Reader

Abstract

Certain aspects of this disclosure provide techniques for improving network energy efficiency (NES) using energy-saving time-division duplex (TDD) modes. An example method is performed at a first network entity (e.g., a radio unit (RU)). This example method typically includes: receiving signaling from a second network entity (e.g., a distributed unit (DU)) indicating a time-division duplex (TDD) mode that defines uplink and downlink configurations for transmission time intervals (TTIs), wherein the TDD mode indicates that one or more of these TTIs are at least partially unused; and performing one or more actions based on the indication that one or more of these TTIs are at least partially unused.
Need to check novelty before this filing date? Find Prior Art

Description

[0001] Cross-reference to related applications

[0002] This application claims priority to U.S. Patent Application No. 18 / 652,658, filed May 1, 2024, which has been assigned to the assignee of this application and is expressly incorporated herein by reference in its entirety, as fully set forth below and for all applicable purposes. Technical Field

[0003] Various aspects of this disclosure relate to wireless communications, and more specifically, to techniques for improving network energy efficiency (NES) using energy-saving time-division duplex (TDD) modes.

[0004] Related technical descriptions

[0005] Wireless communication systems are widely deployed to provide a variety of telecommunications services, such as telephone, video, data, messaging, broadcasting, or other similar services. These wireless communication systems may employ multiple access technologies that enable communication with several users by sharing available wireless communication system resources.

[0006] Despite significant technological advancements in wireless communication systems over the years, challenges remain. For example, complex and dynamic environments can still attenuate or block signals between wireless transmitters and receivers. Therefore, there is a continuous expectation for improving the technical performance of wireless communication systems, including, for example: improving communication speed and data carrying capacity; improving the efficiency of shared communication media; reducing the power used by transmitters and receivers during communication; improving the reliability of wireless communication; avoiding redundant transmission and / or reception and related 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; and increasing the number and types of available wireless communication media. Therefore, there is a need for further improvements to wireless communication systems to overcome the aforementioned technical challenges and other obstacles. Summary of the Invention

[0007] One aspect provides a method for wireless communication at a first network entity. The method includes: receiving from a second network entity signaling an indication of a time-division duplex (TDD) mode, the TDD mode defining uplink and downlink configurations for transmission time intervals (TTIs), wherein the TDD mode indicates that one or more of these TTIs are at least partially unused; and performing one or more actions based on the indication that one or more of these TTIs are at least partially unused.

[0008] On the other hand, a method for wireless communication at a second network entity is provided. The method includes: obtaining a Time Division Duplex (TDD) mode that defines uplink and downlink configurations for transmission time intervals (TTIs) for communication between a first network entity and a user equipment (UE), wherein the TDD mode indicates that one or more of these TTIs are at least partially unused; and sending signaling to the first network entity indicating the TDD mode.

[0009] On the other hand, a method for wireless communication at a user equipment (UE) is provided. The method includes: receiving from a first network entity signaling an indication of a time-division duplex (TDD) mode, the TDD mode defining uplink and downlink configurations for transmission time intervals (TTIs), wherein the TDD mode indicates that one or more of these TTIs are at least partially unused; and performing one or more actions based on the indication that one or more of these TTIs are at least partially unused.

[0010] Other aspects provide: an apparatus capable of operating to, being configured to, or otherwise adapted to perform one or more of the foregoing methods and / or those methods described elsewhere herein; a non-transitory computer-readable medium comprising instructions that, when executed by one or more processors of the apparatus (e.g., directly, indirectly, after preprocessing, or without preprocessing), cause the apparatus to perform the foregoing methods and those methods described elsewhere herein; a computer program product embodied on a computer-readable storage medium comprising: code for performing the foregoing methods and those methods described elsewhere herein; and / or an apparatus comprising components for performing the foregoing methods and those methods described elsewhere herein. 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.

[0011] For illustrative purposes, the following description and figures illustrate certain features. Attached Figure Description

[0012] The accompanying drawings depict certain features of the various aspects described herein and should not be considered as limiting the scope of this disclosure.

[0013] Figure 1 An example wireless communication network is depicted.

[0014] Figure 2 An example decomposed base station architecture is described.

[0015] Figure 3 Various aspects of the example base station and example user equipment are described.

[0016] Figure 4A , Figure 4B , Figure 4C and Figure 4D Various example aspects of data structures used in wireless communication networks are described.

[0017] Figure 5 An example description of the lower-layer uplink link division between O-RAN Distributed Units (O-DUs) and O-RAN Radio Units (O-RUs) is provided.

[0018] Figure 6 A table depicting examples of a standard Time Division Duplex (TDD) mode is provided.

[0019] Figure 7 A table depicts examples of energy-saving TDD modes according to certain aspects of this disclosure.

[0020] Figure 8 A call flow diagram illustrating techniques for improving network energy efficiency (NES) using energy-saving TDD mode, according to certain aspects of this disclosure, is depicted.

[0021] Figure 9 A method for wireless communication is described.

[0022] Figure 10 A method for wireless communication is described.

[0023] Figure 11 A method for wireless communication is described.

[0024] Figure 12 Various aspects of the example communication device are described. Detailed Implementation

[0025] This disclosure provides apparatus, methods, processing systems, and computer-readable media for improving network energy efficiency (NES) using energy-saving time-division duplex (TDD) mode.

[0026] Communication systems, such as 5G New Radio (NR) systems, can be deployed with various components or parts in a variety of ways. In such systems, network entities (such as base stations (BS)) or one or more units (or components) that perform base station functionality can be implemented in a decomposed architecture. For example, a decomposed base station can be configured to utilize a protocol stack that is physically or logically distributed among two or more units, such as one or more central or centralized units (CU), one or more distributed units (DU), or one or more radio units (RU)).

[0027] In some cases, decomposed base stations can be utilized in Open Radio Access Networks (O-RAN, such as network configurations initiated by the O-RAN Alliance). Decomposition can include distributing functionality across two or more units in various physical locations, as well as virtually distributing the functionality of at least one unit, which allows for flexibility in network design. The various units of a decomposed base station or decomposed RAN architecture can be configured to communicate with at least one other unit via wired or wireless communication.

[0028] O-RAN specifies the control plane, user plane, and synchronization plane protocols used on the fronthaul interface, which employs an architecture based on lower-level function splitting (e.g., function splitting-7-2x) to link O-DUs (O-RAN Distributed Units) with O-RUs (O-RAN Radio Units). As used herein, the term "function splitting" generally refers to (e.g., gNB) how functionality is divided among network entities (O-DUs and O-RUs).

[0029] Time Division Duplex (TDD) is a communication technology commonly used in wireless systems to enable bidirectional communication over a shared frequency band. In TDD, the available spectrum is divided into time slots, and the same frequency channel is used alternately for transmission and reception, with time division occurring cyclically. Unlike Frequency Division Duplex (FDD), where different frequency bands are allocated for uplink and downlink communication, TDD dynamically allocates time slots for transmission and reception within the same frequency band. This allows for more efficient spectrum utilization, as the system can adapt to the ever-changing demands of communication services. TDD is particularly advantageous in scenarios with variable service patterns because it provides the ability to flexibly allocate resources based on the demand for uplink or downlink communication at any given time.

[0030] In TDD, the allocation / arrangement of time slots for downlink (D), uplink (U), and special (S) purposes constitutes the TDD mode. These modes define how available time in a communication cycle is divided (e.g., alternated between) transmissions from the base station to the user equipment (downlink), transmissions from the user equipment to the base station (uplink), and any special-purpose time slots denoted as (S), which can be used for various purposes, including guard time, synchronization, or other system-specific functions. Special time slots ensure proper coordination and synchronization within the TDD system. TDD systems typically use symmetric or asymmetric modes depending on application requirements. The specific choice of TDD mode depends on the characteristics of the wireless communication system, including the service mode, system requirements, and the need for flexible resource allocation between downlink and uplink transmissions.

[0031] Network energy efficiency (NES) in wireless communications refers to strategies and technologies aimed at reducing energy consumption within a wireless network. The primary objective is to improve the energy efficiency of network operations while maintaining or improving overall performance. NES initiatives typically involve optimizing the use of network resources, such as base stations and other wireless nodes (e.g., user equipment (UEs)), to minimize unnecessary energy consumption during periods of low or sporadic user activity. Key NES strategies may include dynamic power management, where network components are adjusted or powered off during periods of low demand.

[0032] However, the regular TDD mode does not promote / help NES because the regular TDD mode does not include defining the states of completely unused TTI / slots / symbols or partially unused TTI / slots / symbols, during which NES strategies can be employed.

[0033] However, aspects of this disclosure provide an energy-saving TDD mode that may include defining a state where a TTI / slot / symbol is completely unused (e.g., OFF state) or partially unused (e.g., power back-off state). By using the energy-saving TDD mode disclosed herein, NES strategies (e.g., shutting down the power supply to components such as power amplifiers (PAs) or applying power back-off) can be employed during the OFF state or power back-off state (e.g., fully / partially unused TTI / slot / symbols). Therefore, utilizing the techniques disclosed herein can improve energy efficiency and enhance overall performance.

[0034] An introduction to wireless communication networks

[0035] The techniques and methods described herein can be used in a variety of wireless communication networks. While aspects may be described herein using terms commonly associated with 3G, 4G, and / or 5G wireless technologies, aspects of this disclosure are equally applicable to other communication systems and standards not explicitly mentioned herein.

[0036] Figure 1 An example of a wireless communication network 100 in which the aspects described herein can be implemented is depicted.

[0037] Generally, wireless communication network 100 includes various network entities (optionally, 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, various functions of the network and various devices associated with and interacting with the network can be considered network entities. Furthermore, wireless communication network 100 includes terrestrial aspects, such as terrestrial network entities (e.g., BS 102), and non-terrestrial aspects, such as satellite 140 and aircraft 145, which may include onboard network entities (e.g., one or more BSs) capable of communicating with other network elements (e.g., terrestrial BSs) and user equipment.

[0038] In the depicted example, wireless communication network 100 includes BS 102, UE 104 and one or more core networks (such as Evolved Packet Core (EPC) 160 and 5G Core (5GC) network 190) that interoperate to provide communication services over various communication links, including wired and wireless links.

[0039] Figure 1 Various example UE 104s are described, which may more generally include: cellular phones, smartphones, Session Initiation Protocol (SIP) phones, laptops, personal digital assistants (PDAs), satellite radios, global positioning systems, multimedia devices, video devices, digital audio players, cameras, game consoles, tablet computers, smart devices, wearable devices, vehicles, electricity meters, air pumps, large or small kitchen appliances, healthcare devices, implants, sensors / actuators, displays, Internet of Things (IoT) devices, always-on (AON) devices, edge processing devices, or other similar devices. UE 104 may also be more generally referred to as mobile devices, wireless devices, wireless communication devices, stations, mobile stations, subscriber stations, mobile subscriber stations, mobile units, subscriber units, wireless units, remote units, remote devices, access terminals, mobile terminals, wireless terminals, remote terminals, mobile phones, and others.

[0040] BS 102 communicates wirelessly with UE 104 via communication link 120 (e.g., sending or receiving signals to or from UE 104). Communication link 120 between BS 102 and UE 104 may include uplink (UL) transmission (also referred to as reverse link) from UE 104 to BS 102 and / or downlink (DL) transmission (also referred to as forward link) transmission from BS 102 to UE 104. In various aspects, communication link 120 may utilize multiple-input multiple-output (MIMO) antenna technologies, including spatial multiplexing, beamforming, and / or transmit diversity.

[0041] BS 102 may typically include: NodeB, enhanced NodeB (eNB), next-generation enhanced NodeB (ng-eNB), next-generation NodeB (gNB or gNodeB), access point, transceiver base station, radio base station, radio transceiver, transceiver functionality, transmit / receive point, and / or others. Each BS in BS 102 may provide communication coverage for a corresponding geographic coverage area 110, which may sometimes be referred to as a cell, and in some cases may overlap (e.g., a small cell 102' may have a coverage area 110' that overlaps with the coverage area 110 of a macro cell). For example, BS may provide communication coverage for macro cells (covering a relatively large geographic area), pico cells (covering a relatively small geographic area, such as a stadium), femtocells (covering a relatively small geographic area (e.g., a home)), and / or other types of cells.

[0042] Although BS 102 is described as a single communication device in various aspects, it can be implemented in a variety of configurations. For example, to give a few examples, one or more components of the base station can 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. In another example, various aspects of the base station can be virtualized. More generally, a base station (e.g., BS 102) can include components located at a single physical location or components located at various physical locations. In examples where the base station includes components located at various physical locations, the various components can each perform functions, such that the various components collectively achieve functionality similar to a base station located at a single physical location. In some aspects, a base station including components located at various physical locations can be referred to as a decomposed radio access network architecture (such as an open RAN (O-RAN) or virtualized RAN (VRAN) architecture). Figure 2 An example decomposed base station architecture is depicted and described.

[0043] Different BSs 102 within the wireless communication network 100 can also be configured to support different radio access technologies (such as 3G, 4G, and / or 5G). For example, a BS 102 configured for 4G LTE (collectively referred to as Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRAN)) can interface with EPC 160 via a first backhaul link 132 (e.g., S1 interface). A BS 102 configured for 5G (e.g., 5G NR or Next Generation RAN (NG-RAN)) can interface with 5GC 190 via a second backhaul link 184. BSs 102 can communicate directly or indirectly (e.g., via EPC 160 or 5GC 190) on a third backhaul link 134 (e.g., X2 interface), which can be wired or wireless.

[0044] Wireless communication network 100 can subdivide the electromagnetic spectrum into various categories, bands, channels, or other characteristics. In some aspects, subdivision is provided based on wavelength and frequency, where frequency may also be referred to as carrier, subcarrier, channel, tone, or subband. For example, 3GPP currently defines frequency range 1 (FR1) as including 410MHz to 7125MHz, which is often (interchangeably) referred to as “sub-6GHz”. Similarly, 3GPP currently defines frequency range 2 (FR2) as including 24,250MHz to 71,000MHz, which is sometimes (interchangeably) referred to as “millimeter wave” (“mmW” or “mmWave”). In some cases, FR2 can be further defined according to subranges (such as a first subrange FR2-1 including 24,250MHz to 52,600MHz and a second subrange FR2-2 including 52,600MHz to 71,000MHz). Base stations configured to communicate using mmWave / near mmWave radio bands (e.g., mmWave base stations such as BS 180) can utilize beamforming (e.g., 182) with UEs (e.g., 104) to improve path loss and range.

[0045] The communication link 120 between BS 102 and, for example, UE 104 can be via one or more carriers, which may have different bandwidths (e.g., 5MHz, 10MHz, 15MHz, 20MHz, 100MHz, 400MHz and / or other MHz) and may be aggregated in various ways. The carriers may be adjacent to each other or may not be adjacent to each other. The allocation of carriers may be asymmetric for DL ​​and UL (e.g., more or fewer carriers may be allocated to DL compared to UL).

[0046] Compared to lower-frequency communication, communication using higher frequency bands may have higher path loss and shorter range. Therefore, some base stations (e.g., Figure 1 The beamforming 182 of the BS 180 (180) with the UE 104 can be used to improve path loss and range. For example, the BS 180 and UE 104 may each include multiple antennas, such as antenna elements, antenna panels, and / or antenna arrays, to facilitate beamforming. In some cases, the BS 180 may transmit beamformed signals to the UE 104 in one or more transmit directions 182''. The UE 104 may receive beamformed signals from the BS 180 in one or more receive directions 182''. The UE 104 may also transmit beamformed signals to the BS 180 in one or more transmit directions 182''. The BS 180 may also receive beamformed signals from the UE 104 in one or more receive directions 182''. The BS 180 and UE 104 may then perform beamforming training to determine the optimal receive and transmit directions for each of the BS 180 and UE 104. It is worth noting that the transmit and receive directions of the BS 180 may be the same or different. Similarly, the sending and receiving directions of UE 104 can be the same or different.

[0047] The wireless communication network 100 also includes a Wi-Fi AP 150 that communicates with a Wi-Fi station (STA) 152 via a communication link 154 in, for example, unlicensed spectrum in 2.4 GHz and / or 5 GHz.

[0048] Some UEs 104 may use device-to-device (D2D) communication link 158 to communicate with each other. The D2D communication link 158 may use one or more sidelink channels, such as physical sidelink broadcast channel (PSBCH), physical sidelink discovery channel (PSDCH), physical sidelink shared channel (PSSCH), physical sidelink control channel (PSCCH), and / or physical sidelink feedback channel (PSFCH).

[0049] EPC 160 may include various functional components, including: Mobility Management Entity (MME) 162, other MMEs 164, Serving Gateway 166, Multimedia Broadcast Multicast Service (MBMS) Gateway 168, Broadcast Multicast Service Center (BM-SC) 170, and / or Packet Data Network (PDN) Gateway 172, as in the illustrated example. MME 162 may communicate with Home Subscriber Server (HSS) 174. MME 162 is the control node that handles signaling between UE 104 and EPC 160. Generally, MME 162 provides bearer and connectivity management.

[0050] Generally, user Internet Protocol (IP) packets are transmitted through Serving Gateway 166, which is itself connected to PDN Gateway 172. PDN Gateway 172 provides UE IP address allocation and other functions. PDN Gateway 172 and BM-SC 170 are connected to IP services 176, which may include, for example, the Internet, intranets, IP Multimedia Subsystem (IMS), packet-switched (PS) streaming services, and / or other IP services.

[0051] The BM-SC 170 provides functionality for MBMS user service dispatch and delivery. The BM-SC 170 can serve as an entry point for content provider MBMS transmissions, authorize and initiate MBMS bearer services within a Public Land Mobile Network (PLMN), and / or schedule MBMS transmissions. The MBMS Gateway 168 can distribute MBMS services to BS 102 within a Broadcast-Specific Service Single Frequency Network (MBSFN) area, and / or be responsible for session management (start / stop) and collecting eMBMS-related billing information.

[0052] 5GC 190 may include various functional components, including: Access and Mobility Management Function (AMF) 192, other AMFs 193, Session Management Function (SMF) 194, and User Plane Function (UPF) 195. AMF 192 may communicate with Unified Data Management (UDM) 196.

[0053] AMF 192 is the control node that handles signaling between UE 104 and 5GC 190. AMF 192 provides services such as Quality of Service (QoS) flow and session management.

[0054] Internet Protocol (IP) packets are transmitted via UPF 195, which connects to IP service 197 and provides UE IP address allocation and other functions for 5GC 190. IP service 197 may include, for example, the Internet, intranet, IMS, PS streaming service, and / or other IP services.

[0055] In various aspects, to give a few examples, network entities or network nodes can be implemented as aggregated base stations, decomposed base stations, components of base stations, integrated access and backhaul (IAB) nodes, relay nodes, and sidelink nodes.

[0056] Figure 2An example decomposed base station 200 architecture is depicted. The decomposed base station 200 architecture may include one or more central units (CUs) 210, which may communicate directly with the core network 220 via a backhaul link, or indirectly with the core network 220 through one or more decomposed base station units, such as a near real-time (near-RT) RAN Intelligent Controller (RIC) 225 via an E2 link, or a non-real-time (non-RT) RIC 215 associated with a Service Management and Orchestration (SMO) framework 205, or both. CUs 210 may communicate with one or more distributed units (DUs) 230 via corresponding midhaul links (such as F1 interfaces). DUs 230 may communicate with one or more radio units (RUs) 240 via corresponding fronthaul links. RUs 240 may communicate with a corresponding UE 104 via one or more radio frequency (RF) access links. In some specific implementations, UE 104 may be served simultaneously by multiple RUs 240.

[0057] Each unit in a cell (e.g., CU 210, DU 230, RU 240, and near-RT RIC 225, non-RT RIC 215, and SMO frame 205) may include or be coupled to one or more interfaces configured to receive or transmit signals, data, or information (collectively, signals) via a wired or wireless transmission medium. Each of the cells, or an associated processor or controller that provides instructions to the cell's communication interface, may be configured to communicate with one or more other cells via a transmission medium. For example, these cells may include a wired interface configured to receive signals or transmit signals to one or more other cells via a wired transmission medium. Additionally or alternatively, a cell may include a wireless interface that may include a receiver, transmitter, or transceiver (such as a radio frequency (RF) transceiver) configured to receive signals on a wireless transmission medium or transmit signals to one or more other cells, or both.

[0058] In some aspects, CU 210 can host one or more higher-level control functions. Such control functions may include Radio Resource Control (RRC), Packet Data Convergence Protocol (PDCP), Serving Data Adaptation Protocol (SDAP), etc. Each control function can be implemented using an interface configured to signal to other control functions hosted by CU 210. CU 210 can be configured to handle user plane functions (e.g., Central Unit-User Plane (CU-UP)), control plane functions (e.g., Central Unit-Control Plane (CU-CP)), or combinations thereof. In some implementations, CU 210 can be logically split into one or more CU-UP units and one or more CU-CP units. When implemented in an O-RAN configuration, CU-UP units can communicate bidirectionally with CU-CP units via an interface (such as an E1 interface). CU 210 can be implemented to communicate with DU 230 for network control and signaling transmission as needed.

[0059] DU 230 may correspond to a logical unit comprising one or more base station functions for controlling the operation of one or more RU 240s. In some aspects, DU 230 may at least partially host one or more of the Radio Link Control (RLC) layer, Medium 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.) according to functional splits (such as those defined by the 3rd Generation Partnership Project (3GPP). In some aspects, DU 230 may further host one or more low PHY layers. Each layer (or module) may be implemented using an interface configured to communicate signals with other layers (and modules) hosted by DU 230 or with control functions hosted by CU 210.

[0060] Lower-layer functionality can be implemented by one or more RU 240s. In some deployments, the RU240 controlled by the DU 230 may correspond to a logical node that hosts 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, or both, based at least in part on functional decomposition (such as lower-layer functional decomposition). In such architectures, the RU 240 may be implemented to handle over-the-air (OTA) communications with one or more UE 104s. In some specific implementations, the real-time and non-real-time aspects of control plane and user plane communications with the RU 240 may be controlled by the corresponding DU 230. In some scenarios, this configuration allows the DU 230 and CU 210 to be implemented in a cloud-based RAN architecture (such as a vRAN architecture).

[0061] SMO framework 205 can be configured to support RAN deployment and provisioning of both non-virtualized and virtualized network elements. For non-virtualized network elements, SMO framework 205 can be configured to support the deployment of dedicated physical resources for RAN coverage requirements, which can be managed via operation and maintenance interfaces such as the O1 interface. For virtualized network elements, SMO framework 205 can be configured to interact with a cloud computing platform such as Open Cloud (O-Cloud) 290 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 may include, but are not limited to, CU 210, DU 230, RU 240, and near-RT RIC 225. In some implementations, SMO framework 205 can communicate with the hardware aspects of the 4G RAN (such as Open eNB (O-eNB) 211) via the O1 interface. Additionally, in some implementations, SMO framework 205 can communicate directly with one or more RU 240s via the O1 interface. SMO framework 205 may also include a non-RT RIC 215 configured to support the functionality of SMO framework 205.

[0062] The non-RT RIC 215 can be configured to include logical functions that enable non-real-time control and optimization of RAN elements and resources, including artificial intelligence / machine learning (AI / ML) workflows for model training and updates, or policy-based guidance for applications / features in the near-RT RIC 225. The non-RT RIC 215 can be coupled to or communicate with the near-RT RIC 225, such as via an A1 interface. The near-RT RIC 225 can be configured to include logical functions that enable near real-time control and optimization of RAN elements and resources via an interface, such as via an E2 interface, through data collection and actions, connecting one or more CU 210s, one or more DU 230s, or both, and O-eNBs to the near-RT RIC 225.

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

[0064] Figure 3 Various aspects of examples BS 102 and UE 104 are described.

[0065] Generally, BS 102 includes various processors (e.g., 320, 330, 338, and 340), antennas 334a to 234t (collectively referred to as 334), transceivers 332a to 232t (collectively referred to as 332) including modulators and demodulators, and other aspects that enable the wireless transmission of data (e.g., data source 312) and the wireless reception of data (e.g., data sink 339). For example, BS 102 can transmit and receive data between BS 102 and UE 104. BS 102 includes a controller / processor 340 that can be configured to implement the various wireless communication-related functions described herein.

[0066] Generally, UE 104 includes various processors (e.g., 358, 364, 366, and 380), antennas 352a to 252r (collectively referred to as 352), transceivers 354a to 254r (collectively referred to as 354) including modulators and demodulators, and other aspects that enable the wireless transmission of data (e.g., retrieval from data source 362) and the wireless reception of data (e.g., provision to data sink 360). UE 104 includes a controller / processor 380 that can be configured to implement the various wireless communication-related functions described herein.

[0067] Regarding example downlink transmission, BS 102 includes a transmission processor 320 that can receive data from data source 312 and control information from controller / processor 340. The control information may be for a Physical Broadcast Channel (PBCH), Physical Control Format Indicator Channel (PCFICH), Physical HARQ Indicator Channel (PHICH), Physical Downlink Control Channel (PDCCH), Group Shared PDCCH (GC PDCCH), and / or others. In some examples, this data may be for a Physical Downlink Shared Channel (PDSCH).

[0068] The transmitter processor 320 can process data and control information (e.g., encoding and symbol mapping) to obtain data symbols and control symbols, respectively. The transmitter processor 320 can also generate reference symbols (such as those for the primary synchronization signal (PSS), secondary synchronization signal (SSS), PBCH demodulation reference signal (DMRS), and channel state information reference signal (CSI-RS)).

[0069] The transmit (TX) multiple-input multiple-output (MIMO) processor 330 can perform spatial processing (e.g., pre-decoding) on ​​data symbols, control symbols, and / or reference symbols where applicable, and can provide the output symbol stream to the modulators (MODs) in transceivers 332a to 332t. Each modulator in transceivers 332a to 332t can process the corresponding output symbol stream to obtain an output sample stream. Each modulator can further process (e.g., convert to analog, amplify, filter, and up-convert) the output sample stream to obtain a downlink signal. The downlink signal from the modulators in transceivers 332a to 332t can be transmitted via antennas 334a to 334t, respectively.

[0070] To receive downlink transmissions, UE 104 includes antennas 352a to 352r that receive downlink signals from BS 102 and provide the received signals to demodulators (DEMODs) in transceivers 354a to 354r, respectively. Each demodulator in transceivers 354a to 354r can adjust (e.g., filter, amplify, down-convert, and digitize) the corresponding received signal to obtain an input sample. Each demodulator can further process the input sample to obtain the received symbols.

[0071] The MIMO detector 356 acquires received symbols from all demodulators in transceivers 354a-354r, performs MIMO detection on the received symbols where applicable, and provides the detected symbols. The receive processor 358 processes the detected symbols (e.g., demodulation, deinterleaving, and decoding), provides the decoded data of UE 104 to data sink 360, and provides the decoded control information to controller / processor 380.

[0072] Regarding example uplink transmission, UE 104 also includes a transmit processor 364 that receives and processes data from data source 362 (e.g., for PUSCH) and control information from controller / processor 380 (e.g., for Physical Uplink Control Channel (PUCCH)). Transmit processor 364 may also generate reference symbols for reference signals (e.g., for Sounding Reference Signal (SRS)). Symbols from transmit processor 364 may be pre-decoded by TX MIMO processor 366 where applicable, further processed by modulators in transceivers 354a to 354r (e.g., for SC-FDM), and transmitted to BS 102.

[0073] At BS 102, uplink signals from UE 104 can be received by antennas 334a to 334t, processed by demodulators in transceivers 332a to 332t, detected by MIMO detector 336 where applicable, and further processed by receiver processor 338 to obtain decoded data and control information transmitted by UE 104. Receiver processor 338 can provide decoded data to data sink 339 and decoded control information to controller / processor 340.

[0074] Memory 342 and memory 382 can store data and program code for BS 102 and UE 104, respectively.

[0075] Scheduler 344 can schedule UE to send data on the downlink and / or uplink.

[0076] In various respects, BS 102 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 that output data, such as from data source 312, scheduler 344, memory 342, transmit processor 320, controller / processor 340, TX MIMO processor 330, transceivers 332a to 332t, antennas 334a to 334t, and / or other aspects described herein. Similarly, “receiving” can refer to various mechanisms that acquire data, such as from antennas 334a to 334t, transceivers 332a to 332t, RX MIMO detector 336, controller / processor 340, receive processor 338, scheduler 344, memory 342, and / or other aspects described herein.

[0077] In various respects, UE 104 can also 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 that output data, such as from data source 362, memory 382, ​​transmit processor 364, controller / processor 380, TX MIMO processor 366, transceivers 354a to 354t, antennas 352a to 352t, and / or other aspects described herein. Similarly, “receiving” can refer to various mechanisms that acquire data, such as from antennas 352a to 352t, transceivers 354a to 354t, RX MIMO detector 356, controller / processor 380, receive processor 358, memory 382, ​​and / or other aspects described herein.

[0078] In some respects, one or more processors may be configured to perform various operations (such as those associated with the methods described herein) and respectively send (output) data to another interface configured to send data or receive (obtain) data from another interface configured to receive data.

[0079] Figure 4A , Figure 4B , Figure 4C and Figure 4D Describes the use of wireless communication networks (such as Figure 1 All aspects of the data structure of the wireless communication network 100.

[0080] Specifically, Figure 4A Figure 400 is an example of the first subframe within a 5G (e.g., 5G NR) frame structure. Figure 4B Figure 430 illustrates an example of a DL channel within a 5G subframe. Figure 4C Figure 450 illustrates an example of the second subframe within a 5G frame structure, and Figure 4D Figure 480 illustrates an example of a UL channel within a 5G subframe.

[0081] Wireless communication systems can utilize Orthogonal Frequency Division Multiplexing (OFDM) with a cyclic prefix (CP) on both the uplink and downlink. Such systems can also support half-duplex operation using Time Division Duplex (TDD). OFDM and Single-Carrier Frequency Division Multiplexing (SC-FDM) will (e.g., as...) Figure 4B and Figure 4D The system bandwidth (as depicted in the text) is divided 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.

[0082] Wireless communication frame structures can be frequency division duplex (FDD), where for a specific set of subcarriers, subframes within that set are dedicated to either deep (DL) or ultra-low (UL). Wireless communication frame structures can also be time division duplex (TDD), where for a specific set of subcarriers, subframes within that set are dedicated to both DL and UL.

[0083] exist Figure 4A and Figure 4C In this example, the wireless communication frame structure is TDD, where D stands for DL, U for UL, and X is flexibly used between DL and UL. The UE can be configured using a slot format via a received Slot Format Indicator (SFI) (dynamically via DL Control Information (DCI) or semi-statically / statically via Radio Resource Control (RRC) signaling). In the depicted example, a 10ms frame is divided into 10 equal-sized 1ms 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. Subframes may also include micro-slots, which typically have fewer symbols than the entire slot. Other wireless communication technologies may have different frame structures and / or different channels.

[0084] In some respects, the number of time slots within a subframe is based on the time slot configuration and parameter set. For example, for time slot configuration 0, different parameter sets (μ) 0 to 6 allow 1, 2, 4, 8, 16, 32, and 64 time slots per subframe, respectively. For time slot configuration 1, different parameter sets 0 to 2 allow 2, 4, and 8 time slots per subframe, respectively. Therefore, for time slot configuration 0 and parameter set μ, there are 14 symbols per time slot and 2µ time slots per subframe. The subcarrier spacing and symbol length / duration are functions of the parameter set. The subcarrier spacing can be equal to... kHz, where μ is the parameter set from 0 to 6. Therefore, the parameter set... It has a subcarrier spacing of 15 kHz and a parameter set It has a subcarrier spacing of 960 kHz. The symbol length / duration is negatively correlated with the subcarrier spacing. Figure 4A , Figure 4B , Figure 4C and Figure 4D It provides slot configuration 0 with 14 symbols per slot and parameter set with 4 slots per subframe. Example: The time slot duration is 0.25 ms, the subcarrier spacing is 60 kHz, and the symbol duration is approximately 16.67 μs.

[0085] like Figure 4A , Figure 4B , Figure 4C and Figure 4DAs depicted, the resource grid can be used to represent the frame structure. Each time slot includes a resource block (RB) (also known as a physical RB (PRB)) extending for, 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.

[0086] like Figure 4A As illustrated in the example, some REs in the RE carry information for the UE (e.g., Figure 1 and Figure 3 The reference (pilot) signal (RS) for the UE (104) may include a demodulation RS (DMRS) and / or a channel state information reference signal (CSI-RS) for channel estimation at the UE. The RS may also include a beam measurement RS (BRS), a beam refinement RS (BRRS), and / or a phase tracking RS (PT-RS).

[0087] Figure 4B Examples of various DL channels within a subframe of a frame are illustrated. The Physical Downlink Control Channel (PDCCH) carries the DCI within one or more Control Channel Elements (CCEs), each CCE comprising, for example, nine RE groups (REGs), each REG comprising, for example, four consecutive REs in an OFDM symbol.

[0088] The Primary Synchronization Signal (PSS) can be located within symbol 2 of a specific subframe of the frame. The PSS is generated by the UE (e.g., Figure 1 and Figure 3 104) is used to determine subframe / symbol timing and physical layer identifier.

[0089] The Supplemental Synchronization Signal (SSS) can be located in symbol 4 of a specific subframe of the frame. The SSS is used by the UE to determine the physical layer cell identifier group number and radio frame timing.

[0090] Based on the Physical Layer Identifier and Physical Layer Cell Identifier Group Number, the UE can determine the Physical Cell Identifier (PCI). Based on the PCI, the UE can determine the location of the aforementioned DMRS. The Physical Broadcast Channel (PBCH), carrying the Master Information Block (MIB), can be logically grouped with the PSS and SSS to form a Synchronization Signal (SS) / PBCH block. The MIB provides the System Frame Number (SFN) and the number of Restricted Frames (RBs) in the system bandwidth. The Physical Downlink Shared Channel (PDSCH) carries user data, broadcast system information (such as System Information Blocks (SIBs)) not transmitted via the PBCH, and / or paging messages.

[0091] like Figure 4CAs illustrated, some REs in the REs carry DMRS for channel estimation at the base station (indicated as R for a particular configuration, but other DMRS configurations are possible). The UE can transmit DMRS for PUCCH and DMRS for PUSCH. PUSCH DMRS can be transmitted, for example, in the first or second symbol before the PUSCH. PUCCH DMRS can be transmitted in different configurations depending on whether a short or long PUCCH is being transmitted and depending on the specific PUCCH format used. UE104 can transmit a Sounding Reference Signal (SRS). SRS can be transmitted, for example, in the last symbol of a subframe. SRS can have a comb structure, and the UE can transmit SRS on one of the comb teeth. SRS can be used by the base station for channel quality estimation to enable frequency-dependent scheduling of the UL.

[0092] Figure 4D Examples of various UL channels within a subframe of a frame are illustrated. The PUCCH can be located as indicated in one configuration. The PUCCH carries uplink control information (UCI), such as scheduling requests, channel quality indicators (CQI), pre-decoding matrix indicators (PMI), rank indicators (RI), and HARQ ACK / NACK feedback. The PUSCH carries data and may additionally be used to carry buffer status reports (BSR), power clearance reports (PHR), and / or UCI.

[0093] O-RAN Overview

[0094] Communication systems, such as 5G New Radio (NR) systems, can be deployed with various components or parts in a variety of ways. In such systems, network entities (such as base stations (BS)) or one or more units (or components) that perform base station functionality can be implemented in a decomposed architecture. For example, a decomposed base station can be configured to utilize a protocol stack that is physically or logically distributed among two or more units, such as one or more central or centralized units (CU), one or more distributed units (DU), or one or more radio units (RU)).

[0095] In some cases, decomposed base stations can be utilized in Open Radio Access Networks (O-RAN, such as network configurations initiated by the O-RAN Alliance). Decomposition can include distributing functionality across two or more units in various physical locations, as well as virtually distributing the functionality of at least one unit, which allows for flexibility in network design. The various units of a decomposed base station or decomposed RAN architecture can be configured to communicate with at least one other unit via wired or wireless communication.

[0096] As noted above, O-RAN specifies the control plane, user plane, and synchronization plane protocols used on the fronthaul interface, which employs an architecture based on lower-level function splitting to link O-DUs (O-RAN Distributed Units) with O-RUs (O-RAN Radio Units). Figure 5 An example of an O-RAN architecture 500 is illustrated, such as a split for uplink transmission, which is transmitted from the O-RU to the O-DU via the fronthaul (FH) interface.

[0097] Network Energy Saving (NES) Overview

[0098] Power consumption of wireless nodes in large-scale wireless networks (e.g., 4G, 5G, and higher generations) is a primary concern. To help reduce this power consumption, some wireless nodes may be able to employ Network Energy Saving (NES) modes / techniques / strategies. Network Energy Saving (NES) in wireless communications refers to strategies and techniques designed to reduce energy consumption within a wireless network. The main objective is to improve the energy efficiency of network operations while maintaining or improving overall performance. NES initiatives typically involve optimizing the use of network resources (such as base stations and other wireless nodes) to minimize unnecessary energy consumption during periods of low or sporadic user activity. Key NES strategies may include dynamic power management, where network components are adjusted or powered off during periods of low demand.

[0099] Enabling NES is crucial in wireless communication systems because it allows wireless nodes to dynamically adjust parameters, components, and / or functions to reduce power consumption.

[0100] Time Division Duplex (TDD) Mode Overview

[0101] Time Division Duplex (TDD) is a communication technology commonly used in wireless systems to enable bidirectional communication over a shared frequency band. In TDD, the available spectrum is divided into time slots, and the same frequency channel is used alternately for transmission and reception, with time division occurring cyclically. Unlike Frequency Division Duplex (FDD), where different frequency bands are allocated for uplink and downlink communication, TDD dynamically allocates time slots for transmission and reception within the same frequency band. This allows for more efficient spectrum utilization, as the system can adapt to the ever-changing demands of communication services. TDD is particularly advantageous in scenarios with variable service patterns because it provides the ability to flexibly allocate resources based on the demand for uplink or downlink communication at any given time.

[0102] In TDD, the allocation / arrangement of time slots for downlink (D), uplink (U), and special (S) purposes constitutes the TDD mode. These modes define how available time in a communication cycle is divided (e.g., alternated between) transmissions from the base station to the user equipment (downlink), transmissions from the user equipment to the base station (uplink), and any special-purpose time slots denoted as (S), which can be used for various purposes, including guard time, synchronization, or other system-specific functions. Special time slots ensure proper coordination and synchronization within the TDD system. TDD systems typically use symmetric or asymmetric modes depending on application requirements. The specific choice of TDD mode depends on the characteristics of the wireless communication system, including the service mode, system requirements, and the need for flexible resource allocation between downlink and uplink transmissions.

[0103] Figure 6 Table 600 illustrates an example of a conventional Time Division Duplex (TDD) mode. As illustrated, the conventional TDD mode allocates time slots for downlink (D), uplink (U), and special (S) purposes.

[0104] However, as noted above, the conventional TDD mode does not promote / help NES because the conventional TDD mode does not include defining states of completely unused TTI / slots / symbols or partially unused TTI / slots / symbols, during which NES strategies can be employed.

[0105] Aspects related to energy-saving time-division duplex (TDD) mode

[0106] Various aspects of this disclosure provide an energy-saving TDD mode that may include defining a state where a TTI / slot / symbol is completely unused (e.g., OFF state) or partially unused (e.g., power back-off state). By using the energy-saving TDD mode disclosed herein, NES strategies (e.g., turning off the power amplifier (PA) or applying power back-off) can be employed during the OFF state or power back-off state (e.g., completely / partially unused TTI / slot / symbol).

[0107] Figure 7 Table 700 illustrates examples of energy-saving TDD modes according to certain aspects of this disclosure. As noted above, the energy-saving TDD modes disclosed herein may include one or more additional (new) states to indicate (fully) unused or partially (un)used TTI / slot / symbol states. New states may include one or more powerBackoffdB states and / or OFF states (in addition to downlink (D), uplink (U), and special (S) states). In some aspects, the TDD mode may be announced by the management plane (M-Plane).

[0108] As illustrated at 702, for example, multiple powerBackoff dB states can be defined, each indicating a different level of power backoff. For example, D-3 can indicate a 3dB power backoff during a time slot (e.g., downlink), while D-4 can indicate a 4dB power backoff, D-6 can indicate a 6dB power backoff, and D-2 can indicate a 2dB power backoff.

[0109] As illustrated at 704, an OFF state (e.g., D-off) can be defined, which indicates (e.g., downlink) no occupancy / transmission / reception. For example, during a D-off time slot, one or more components (e.g., power amplifier (PA) and / or one or more antennas / receivers) at a network entity (e.g., RU) or UE can be powered off and / or disabled.

[0110] In some cases, the powerBackoffdB state and / or OFF state can be a subtype of a special (S) state. In some cases, the powerBackoffdB value can be optional. In other words, the powerBackoffdB state can indicate power back-off without specifying a decibel level.

[0111] Section extension (SE) signaling (e.g., Section 4) can be used to specify / switch to a new TDD mode and / or a selected frame boundary. In other words, Section 4 signaling specifies a switch to a particular TDD mode for a specified duration. After the specified duration has elapsed (if such a duration was specified), the switch back to the previous mode is possible.

[0112] For example, for a power back-off command, Section 4 signaling may specify a new TDD mode / structure (e.g., mode / TDD structure 2X), a start frame (e.g., frame 123), an end time (or no end time), and / or an end frame (or no end frame). Additionally, Section 4 signaling may include one or more extensions.

[0113] The first extension (e.g., Ext1; Ext = 1) allows updating the power level or power backoff level. For example, Ext1PowerBackOff can specify a backoff value (e.g., in dB) for all (e.g., downlink) slots in (e.g., the current) TDD mode.

[0114] The second extension (e.g., Ext2; Ext = 2) allows for selective power backoff for each slot. For example, Ext2 can specify a backoff value (e.g., in dB) for each slot (e.g., for a full frame—20 slots per frame), which could be expressed as: powerBackoff[slot@numerology] 1,1,1,2,2,3……..2 1; dB. In some cases, selective power backoff per slot can be applied only to downlink slots, and the parameter set can be adjusted accordingly.

[0115] A third extension (e.g., Ext3; Ext = 3) can be used to apply TTI / slot / symbol masks (e.g., to apply TDD modes only to certain specified TTI / slot / symbols). For example, Ext3 can specify a symbol mask, which can be represented as: Sym_mask = 11111110000000b, indicating that TDD modes should be applied to symbols in the symbol mask corresponding to the value "1". In some aspects, in addition to different extensions (e.g., Ext1 / Ext2), TTI / slot / symbol masks can also be used to selectively apply TDD modes and / or power back-off.

[0116] A fourth extension (e.g., Ext4; Ext = 4) can be used to apply an antenna reduction mask, which can be specified in a similar manner to Ext3. The antenna reduction mask specifies the TTI / timeslot / symbol to be reduced in the number of operating antennas (e.g., for RU to transmit or UE to receive). In some aspects, in addition to different extensions (e.g., Ext1 / Ext2), antenna masks can be used to selectively apply TDD modes and / or power back-off and selectively reduce the number of antennas, thereby increasing potential power savings. In some aspects, the antenna reduction mask can be 64 bits. For off antennas… calibration is still performed.

[0117] In some aspects, the management plane (M-Plane) may advertise one or more of the following: the maximum supported power backoff (e.g., in decibels or configured backoff levels), the number of power backoff levels, a list of backoff values, and / or backoff value steps. In some aspects, within TDD mode (e.g., advertised by M-Plane), an option field may be added for each time slot, indicating the power backoff value (e.g., in dB).

[0118] Figure 8 A call flow diagram 800 illustrates a technique for improving network energy efficiency (NES) using a power-saving TDD mode, according to certain aspects of this disclosure. In some aspects, Figure 8 The UE shown can be about Figure 1 and Figure 3An example of UE 104 depicted and described. In some respects, the first network entity and / or the second network entity (e.g., RU and / or DU) shown in the figure may be relative to... Figure 1 and Figure 3 Examples of BS 102 (e.g., gNB) depicted and described, or relative to Figure 2 An example of a decomposed base station that is depicted and described.

[0119] In some respects, as illustrated at 802, the DU may receive from the RU information about the RU's ability to apply power back-off during at least a portion or all of the TTI when it is not in use.

[0120] As illustrated at 804, the DU may send signaling to the RU indicating a TDD mode (e.g., an energy-saving TDD mode) that indicates one or more TTIs that are at least partially (e.g., partially or completely) unused. As illustrated, the RU may send (e.g., forward) signaling to the UE indicating an energy-saving TDD mode.

[0121] As illustrated at 806, the RU may perform one or more actions (e.g., apply power back-off, adjust parameters, disable transmission, or turn off the power to a component) based on instructions from one or more TTIs that are at least partially unused.

[0122] As illustrated at 808, the UE may perform one or more actions (e.g., monitor DL ​​transmission, adjust parameters, disable reception, or power off components) based on indications of one or more TTIs that are at least partially unused.

[0123] As noted above, the techniques disclosed herein can improve energy efficiency and enhance overall performance.

[0124] Example Operation

[0125] Figure 9 It is shown in the first network entity (such as Figure 1 and Figure 3 (BS 102) or as relative to Figure 2 An example of the method 900 for wireless communication at the decomposed base station discussed.

[0126] Method 900 begins at step 905, which involves receiving signaling from a second network entity indicating a Time Division Duplex (TDD) mode. This TDD mode defines uplink and downlink configurations for transmission time intervals (TTIs), wherein the TDD mode indicates that one or more of these TTIs are at least partially unused. In some cases, this step refers to the operation as described in reference... Figure 12The circuitry and / or code described for receiving, or that can be executed by the circuitry and / or the code.

[0127] Method 900 then proceeds to step 910, which involves performing one or more actions based on indications that one or more of these TTIs are at least partially unused. In some cases, the operation of this step refers to, as referenced... Figure 12 The circuitry described for execution and / or the code for execution, or the circuitry and / or the code that can be executed.

[0128] In some respects, at least one of these actions includes applying power backoff to downlink transmissions during at least one TTI in which at least some TTIs are not used.

[0129] In some respects, applying power backoff involves adjusting one or more parameters of the power amplifier (PA) of the first network entity.

[0130] In some aspects, applying power backoff involves adjusting the number of transmit antennas.

[0131] In some respects, the signaling indicates that at least one of the TTIs in which power back-off is to be applied is at least partially unused.

[0132] In some aspects, method 900 also includes providing a second network entity with information about the first network entity's ability to apply power backoff during at least one TTI in a TTI that is at least partially unused. In some cases, the operation of this step involves, as referenced... Figure 12 The circuitry described is used to provide the circuitry and / or the code used to provide the circuitry, or the circuitry and / or the code that can be executed.

[0133] In some respects, this information includes at least one of the following: the maximum power backoff supported; one or more levels used when applying power backoff; or one or more step sizes used when applying power backoff.

[0134] In some respects, the signaling indicates the power backoff level for each of at least one of the TTIs that is at least partially unused.

[0135] In some aspects, method 900 also includes providing information about the TDD mode to the user equipment (UE). In some cases, the operation of this step involves, as described in reference... Figure 12 The circuitry described is used to provide the circuitry and / or the code used to provide the circuitry, or the circuitry and / or the code that can be executed.

[0136] In some respects, the TDD mode indicates that at least one of these TTIs is completely unused.

[0137] In some respects, the one or more actions include at least one of the following: disabling transmission during at least one completely unused TTI; or turning off the power amplifier (PA) during at least one completely unused TTI.

[0138] In some respects, TTI includes time slots or symbols.

[0139] In some respects, the first network entity includes a radio unit (RU); the second network entity includes a distributed unit (DU); and the signaling includes section extension (SE).

[0140] In one aspect, method 900 or any aspect thereof may be made by means of a device (such as...) Figure 12 The communication device 1200 performs the execution, and the device includes various components capable of operating, being configured, or adapted to perform the method 900. The communication device 1200 is described in further detail below.

[0141] It should be noted that Figure 9 This is merely one example of a method, and other methods that include fewer, additional, or alternative steps may also be consistent with this disclosure.

[0142] Figure 10 It is shown in the second network entity (such as Figure 1 and Figure 3 (BS 102) or as per BS 102) Figure 2 An example of the method 1000 for wireless communication at the decomposed base station discussed.

[0143] Method 1000 begins at step 1005, which obtains a Time Division Duplex (TDD) mode that defines the uplink and downlink configurations for Transmission Time Intervals (TTIs) used for communication between a first network entity and a User Equipment (UE), wherein the TDD mode indicates that one or more of these TTIs are at least partially unused. In some cases, the operation of this step involves, as referenced... Figure 12 The circuit and / or code described for obtaining, or that can be executed by the circuit and / or the code.

[0144] Method 1000 then proceeds to step 1010, which involves sending signaling indicating the TDD mode to the first network entity. In some cases, this step refers to the operation as described in reference [reference needed]. Figure 12 The circuitry and / or code described for transmitting, or that can be executed by the circuitry and / or the code.

[0145] In some respects, the signaling instructs the first network entity to apply power backoff for at least one of the at least partially unused TTIs.

[0146] In some aspects, method 1000 further includes receiving information from a first network entity regarding the first network entity's ability to apply power backoff during at least one TTI in a TTI that is at least partially unused. In some cases, this step refers to operations as described in reference... Figure 12 The circuitry and / or code described for receiving, or that can be executed by the circuitry and / or the code.

[0147] In some respects, this information includes at least one of the following: the maximum power backoff supported; one or more levels used when applying power backoff; or one or more step sizes used when applying power backoff.

[0148] In some respects, the signaling indicates the power backoff level for each of at least one of the TTIs that is at least partially unused.

[0149] In some respects, the TDD mode indicates that at least one of these TTIs is completely unused.

[0150] In some respects, TTI includes time slots or symbols.

[0151] In some respects, the first network entity includes a radio unit (RU); the second network entity includes a distributed unit (DU); and the signaling includes section extension (SE).

[0152] In one aspect, method 1000 or any aspect thereof may be made by means of a device (such as...) Figure 12 The communication device 1200 is used to perform the method 1000. The device includes various components that are operable to, configured to, or adapted to perform the method 1000. The communication device 1200 is described in further detail below.

[0153] It should be noted that Figure 10 This is merely one example of a method, and other methods that include fewer, additional, or alternative steps may also be consistent with this disclosure.

[0154] Figure 11 This illustrates in user equipment (UE), such as Figure 1 and Figure 3 An example of a method 1100 for wireless communication at UE 104.

[0155] Method 1100 begins at step 1105, which involves receiving signaling from a first network entity indicating a Time Division Duplex (TDD) mode. This TDD mode defines uplink and downlink configurations for transmission time intervals (TTIs), wherein the TDD mode indicates that one or more of these TTIs are at least partially unused. In some cases, this step refers to the operation as described in reference... Figure 12 The circuitry and / or code described for receiving, or that can be executed by the circuitry and / or the code.

[0156] Method 1100 then proceeds to step 1110, which involves performing one or more actions based on indications that one or more of these TTIs are at least partially unused. In some cases, the operation of this step refers to, as referenced... Figure 12 The circuitry described for execution and / or the code for execution, or the circuitry and / or the code that can be executed.

[0157] In some respects, at least one of these actions includes monitoring downlink transmissions during at least one TTI in which at least some TTIs are not in use.

[0158] In some respects, at least one of these actions includes adjusting one or more parameters used to receive signals from the first network entity.

[0159] In some respects, the one or more parameters include the number of receiving antennas; and the one or more actions include, based on an indication that one or more of these TTIs are at least partially unused, performing at least one of the following: increasing or decreasing the number of receiving antennas.

[0160] In some respects, the signaling indicates at least one TTI in which the one or more actions are to be performed, which is at least partially unused.

[0161] In some respects, the signaling instructs at least one action for each of at least one of the at least partially unused TTIs.

[0162] In some respects, the TDD mode indicates that at least one of these TTIs is completely unused.

[0163] In some respects, the one or more actions include at least one of the following: disabling reception during at least one completely unused TTI; or turning off the power to the receiver during at least one completely unused TTI.

[0164] In some respects, TTI includes time slots or symbols.

[0165] In some respects, the first network entity includes a radio unit (RU); and the signaling includes section extension (SE).

[0166] In one aspect, method 1100 or any aspect thereof may be made by means of a device (such as...) Figure 12The communication device 1200 is used to perform the method 1100. The device includes various components that are operable to, configured to, or adapted to perform the method 1100. The communication device 1200 is described in further detail below.

[0167] It should be noted that Figure 11 This is merely one example of a method, and other methods that include fewer, additional, or alternative steps may also be consistent with this disclosure.

[0168] Example communication device

[0169] Figure 12 Various aspects of the example communication device 1200 are described. In some aspects, the communication device 1200 is user equipment, such as those described above. Figure 1 and Figure 3 The UE 104 is described. In some respects, the communication device 1200 is a network entity, such as... Figure 1 and Figure 3 BS 102 or as about Figure 2 The decomposed base station under discussion.

[0170] Communication device 1200 includes a processing system 1205 coupled to transceiver 1275 (e.g., transmitter and / or receiver). In some aspects (e.g., when communication device 1200 is a network entity), processing system 1205 may be coupled to network interface 1285, which is configured to communicate via a communication link (such as, as described herein, regarding...). Figure 2 The described backhaul link, midhaul link, and / or fronthaul link acquire and transmit signals for communication device 1200. Transceiver 1275 is configured to transmit and receive signals for communication device 1200 via antenna 1280, such as the various signals described herein. Processing system 1205 may be configured to perform processing functions for communication device 1200, including processing signals received by communication device 1200 and / or to be transmitted by the communication device.

[0171] Processing system 1205 includes one or more processors 1210. In various aspects, the one or more processors 1210 may represent one or more of a receive processor 358, a transmit processor 364, a TX MIMO processor 366, and / or a controller / processor 380, as relative to... Figure 3 As described. In various respects, one or more processors 1210 may represent one or more of the following: receive processor 338, transmit processor 320, TX MIMO processor 330, and / or controller / processor 340, as relative to Figure 3As described. One or more processors 1210 are coupled to a computer-readable medium / memory 1240 via a bus 1270. In some aspects, the computer-readable medium / memory 1240 is configured to store instructions (e.g., computer-executable code) that, when executed by one or more processors 1210, cause one or more processors 1210 to perform actions related to... Figure 9 The described method 900 or any aspect related to that method; relative to Figure 10 The described method 1000 or any aspect thereof; and relative to Figure 11 The method 1100 described herein or any aspect thereof. It should be noted that references to processors performing the functions of communication device 1200 may include one or more processors 1210 performing such functions of communication device 1200.

[0172] In the depicted example, computer-readable medium / memory 1240 stores code (e.g., executable instructions), such as code 1245 for receiving, code 1250 for executing, code 1255 for providing, code 1260 for obtaining, and code 1265 for sending. Processing the code 1245 for receiving, the code 1250 for executing, the code 1255 for providing, the code 1260 for obtaining, and the code 1265 for sending causes the communication device 1200 to perform actions relative to... Figure 9 The described method 900 or any aspect thereof; relative to Figure 10 The described method 1000 or any aspect thereof; and relative to Figure 11 The method 1100 described or any aspect thereof.

[0173] One or more processors 1210 include circuitry configured to implement (e.g., execute) code stored in computer-readable medium / memory 1240, including circuitry 1215 for receiving, circuitry 1220 for executing, circuitry 1225 for providing, circuitry 1230 for obtaining, and circuitry 1235 for transmitting. Processing using the circuitry 1215 for receiving, the circuitry 1220 for executing, the circuitry 1225 for providing, the circuitry 1230 for obtaining, and the circuitry 1235 for transmitting enables the communication device 1200 to perform operations relative to... Figure 9 The described method 900 or any aspect thereof; relative to Figure 10 The described method 1000 or any aspect thereof; and relative to Figure 11 The method 1100 described or any aspect thereof.

[0174] The various components of the communication device 1200 provide parts for performing: about Figure 9The described method 900 or any aspect related to that method; relative to Figure 10 The described method 1000 or any aspect thereof; and relative to Figure 11 The described method 1100 or any aspect thereof. For example, components for sending, transmitting, or outputting for transmission may include... Figure 3 The transceiver 354 and / or antenna 352 of UE 104 illustrated herein Figure 3 The transceiver 332 and / or antenna 334 of BS 102 illustrated herein Figure 12 The communication device 1200 includes a transceiver 1275 and an antenna 1280. Components for receiving or acquiring data may include... Figure 3 The transceiver 354 and / or antenna 352 of UE 104 illustrated herein Figure 3 The transceiver 332 and / or antenna 334 of BS 102 illustrated herein Figure 12 The transceiver 1275 and antenna 1280 of the communication equipment 1200.

[0175] Example Terms

[0176] Specific implementation examples are described in the following numbered clauses: Clause 1: A method for wireless communication at a first network entity, the method comprising: receiving from a second network entity a signaling indicating a time division duplex (TDD) mode, the TDD mode defining an uplink configuration and a downlink configuration for a transmission time interval (TTI), wherein the TDD mode indicates that one or more TTIs are at least partially unused; and performing one or more actions based on the indication that one or more TTIs are at least partially unused.

[0177] Clause 2: The method according to Clause 1, wherein at least one of the actions includes applying power backoff to the downlink transmission during at least one TTI in which at least some TTIs are not used.

[0178] Clause 3: The method described in Clause 2, wherein applying the power backoff includes adjusting one or more parameters of the power amplifier (PA) of the first network entity.

[0179] Clause 4: The method described in Clause 2, wherein applying the power backoff includes adjusting the number of transmit antennas.

[0180] Clause 5: The method according to Clause 2, wherein the signaling indicates the at least one TTI in which the power back-off is to be applied in the at least partially unused TTI.

[0181] Clause 6: The method according to Clause 2 further includes: providing the second network entity with information about the first network entity's ability to apply power backoff during at least one TTI in the at least partially unused TTI.

[0182] Clause 7: The method described in Clause 6, wherein the information includes at least one of the following: the maximum power backoff supported; one or more levels used when applying the power backoff; or one or more step sizes used when applying the power backoff.

[0183] Clause 8: The method according to Clause 2, wherein the signaling indicates the power back-off level of each of the at least one TTI among the at least partially unused TTIs.

[0184] Clause 9: The method according to any one of Clauses 1 to 8, wherein the TDD mode indicates that at least one of the TTIs is completely unused.

[0185] Clause 10: The method described in Clause 9, wherein the one or more actions include at least one of the following: disabling transmission during at least one completely unused TTI; or turning off the power amplifier (PA) during the at least one completely unused TTI.

[0186] Clause 11: The method according to any one of Clauses 1 to 10, wherein the TTI includes a time slot or a symbol.

[0187] Clause 12: The method according to any one of Clauses 1 to 11, wherein: the first network entity includes a radio unit (RU); the second network entity includes a distributed unit (DU); and the signaling includes section extension (SE).

[0188] Clause 13: The method described in Clause 2 further includes: providing information about the TDD mode to the user equipment (UE).

[0189] Clause 14: A method for wireless communication at a second network entity, the method comprising: obtaining a time division duplex (TDD) mode, the TDD mode defining an uplink configuration and a downlink configuration for a transmission time interval (TTI) for communication between a first network entity and a user equipment (UE), wherein the TDD mode indicates that one or more of the TTIs are at least partially unused; and sending signaling to the first network entity indicating the TDD mode.

[0190] Clause 15: The method according to Clause 14, wherein the signaling indicates at least one of the at least partially unused TTIs, and the first network entity applies power backoff for the at least one TTI.

[0191] Clause 16: The method according to any one of Clauses 14 to 15, the method further comprising: receiving from the first network entity information about the first network entity's ability to apply power backoff during at least one TTI in the at least partially unused TTI.

[0192] Clause 17: The method according to Clause 16, wherein the information includes at least one of the following: the maximum power backoff supported; one or more levels used when applying the power backoff; or one or more step sizes used when applying the power backoff.

[0193] Clause 18: The method according to any one of Clauses 14 to 17, wherein the signaling indicates the power back-off level of each of the at least one TTI among the at least partially unused TTIs.

[0194] Clause 19: The method according to any one of Clauses 14 to 18, wherein the TDD mode indicates that at least one of the TTIs is completely unused.

[0195] Clause 20: The method according to any one of Clauses 14 to 19, wherein the TTI includes a time slot or a symbol.

[0196] Clause 21: The method according to any one of Clauses 14 to 20, wherein: the first network entity includes a radio unit (RU); the second network entity includes a distributed unit (DU); and the signaling includes section extension (SE).

[0197] Clause 22: A method for wireless communication at a user equipment (UE), the method comprising: receiving from a first network entity a signaling indicating a time division duplex (TDD) mode, the TDD mode defining an uplink configuration and a downlink configuration for a transmission time interval (TTI), wherein the TDD mode indicates that one or more TTIs are at least partially unused; and performing one or more actions based on the indication that one or more TTIs are at least partially unused.

[0198] Clause 23: The method according to Clause 22, wherein at least one of the actions includes: monitoring downlink transmissions during at least one TTI in which at least some of the TTIs are not used.

[0199] Clause 24: The method according to any one of Clauses 22 to 23, wherein at least one of the actions includes adjusting one or more parameters for receiving signals from the first network entity.

[0200] Clause 25: The method according to Clause 24, wherein: the one or more parameters include the number of receiving antennas; and the one or more actions include, based on the indication that one or more of the TTIs are at least partially unused, performing at least one of the following: increasing or decreasing the number of receiving antennas.

[0201] Clause 26: The method according to any one of Clauses 22 to 25, wherein the signaling indicates at least one TTI of the at least partially unused TTI to perform the one or more actions.

[0202] Clause 27: The method according to any one of Clauses 22 to 26, wherein the signaling indicates at least one action of the action for each of the at least one TTI in the at least partially unused TTI.

[0203] Clause 28: The method according to any one of Clauses 22 to 27, wherein the TDD mode indicates that at least one of the TTIs is completely unused.

[0204] Clause 29: The method described in Clause 28, wherein the one or more actions include at least one of the following: disabling reception during at least one completely unused TTI; or turning off the power to the receiver during the at least one completely unused TTI.

[0205] Clause 30: The method according to any one of Clauses 22 to 29, wherein the TTI includes a time slot or a symbol.

[0206] Clause 31: The method according to any one of Clauses 22 to 30, wherein: the first network entity includes a radio unit (RU); and the signaling includes section extension (SE).

[0207] Clause 32: An apparatus comprising: at least one memory including executable instructions; and at least one processor configured to execute the executable instructions and cause the apparatus to perform a method according to any one of Clauses 1 to 31.

[0208] Clause 33: An apparatus comprising components for performing the method according to any one of Clauses 1 to 31.

[0209] Clause 34: A non-transitory computer-readable medium comprising executable instructions that, when executed by at least one processor of a device, cause the device to perform the method according to any one of Clauses 1 to 31.

[0210] Clause 35: A computer program product embodied on a computer-readable storage medium, the computer-readable storage medium including code for performing the method according to any one of Clauses 1 to 31.

[0211] Additional Notes

[0212] 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 function and arrangement of the elements discussed may be changed without departing from the scope of this disclosure. Various processes or components may be omitted, substituted, or added as appropriate in various examples. For example, the described methods may be performed in a different order than described, and various actions may be added, omitted, or combined. Furthermore, features described in some examples may be combined in some other examples. For example, any number of aspects set forth herein may be used to implement an apparatus or practice. Moreover, the scope of this disclosure is intended to cover such apparatuses or methods practiced using other structures, functionalities, or structures and functionalities that complement or replace the various aspects of this 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 claims.

[0213] The various exemplary logic blocks, modules, and circuits described in this disclosure can be implemented or executed using a general-purpose processor, graphics processing unit (GPU), neural processing unit (NPU), digital signal processor (DSP), ASIC, field-programmable gate array (FPGA) or other programmable logic device (PLD), discrete gate or transistor logic unit, discrete hardware component, or any combination thereof designed to perform the functions described herein. While the general-purpose processor may be a microprocessor, in alternative embodiments, 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, such as a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors working in conjunction with a DSP core, a system-on-a-chip (SoC), or any other such configuration.

[0214] As used herein, "processor," "at least one processor," or "one or more processors" generally refers to a single processor configured to perform one or more operations, or multiple processors configured to collectively perform one or more operations. In the case of multiple processors, the execution of one or more operations may be divided among different processors, but one processor may perform multiple operations, and multiple processors may collectively perform a single operation. Similarly, "memory," "at least one memory," or "one or more memory" generally refers to a single memory configured to store data and / or instructions, or multiple memories configured to collectively store data and / or instructions.

[0215] The components for receiving, executing, providing, obtaining, and sending may include one or more processors, such as those mentioned above. Figure 12 One or more processors as described.

[0216] As used in this article, the phrase “at least one of” in a list of items refers to any combination of these items, including a single member. For example, “at least one of a, b, or c” is intended to cover a, b, c, ab, ac, bc, and abc, as well as any combination with multiple identical elements (e.g., aa, aaa, aab, aac, abb, acc, bb, bbb, bbc, cc, and ccc, or any other ordering of a, b, and c).

[0217] As used herein, the term "determine" encompasses a wide variety of actions. For example, "determine" can include calculation, operation, processing, deduction, investigation, searching (e.g., searching in a table, database, or other data structure), and probing. Additionally, "determine" can include receiving (e.g., receiving information), accessing (e.g., accessing data in memory), and so on. Furthermore, "determine" can include parsing, selecting, picking, and building.

[0218] The methods disclosed herein include one or more actions for implementing the methods. These actions may be interchanged without departing from the scope of the claims. In other words, unless a specified order of actions is specified, the order and / or use of a particular action may be modified without departing from the scope of the claims. Furthermore, the various operations of the methods described above may be performed by any suitable component capable of performing the corresponding function. This component may include various hardware and / or software components and / or modules, including but not limited to circuits, application-specific integrated circuits (ASICs), or processors. Software should be broadly interpreted as instructions, instruction sets, code, code segments, program code, programs, subroutines, software modules, applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, or functions, whether referred to as software, firmware, middleware, microcode, hardware description languages, or other terms.

[0219] The following claims are not intended to be limited to the aspects shown herein, but should be given the full scope consistent with the language of the claims. Within the claims, unless specifically stated otherwise, reference to the singular form of an element is not intended to mean “one and only one,” but rather “one or more.” Unless specifically stated otherwise, the term “some” means one or more. No element of any claim shall be interpreted in accordance with 35 USC §112(f) unless that element is explicitly stated using the phrase “for a component of.” All structural and functional equivalents of the elements throughout the various aspects described herein that are known to a person of ordinary skill in the art, or will later be known, are expressly incorporated herein by reference and are intended to be covered by the claims. Furthermore, nothing disclosed herein is intended to be offered to the public, whether or not such disclosure is explicitly recited in the claims.

Claims

1. A method for wireless communication at a first network entity, the method comprising: Receive signaling from a second network entity indicating a Time Division Duplex (TDD) mode, wherein the TDD mode defines an uplink configuration and a downlink configuration for a Transmission Time Interval (TTI), wherein the TDD mode indicates that one or more TTIs are at least partially unused; as well as One or more actions are performed based on the indication that is at least partially unused in one or more of the TTIs.

2. The method of claim 1, wherein at least one of the actions includes applying power backoff to the downlink transmission during at least one TTI in which at least some TTIs are not used.

3. The method of claim 2, wherein applying the power backoff includes adjusting one or more parameters of the power amplifier (PA) of the first network entity.

4. The method of claim 2, wherein applying the power backoff includes adjusting the number of transmit antennas.

5. The method of claim 2, wherein the signaling indicates the at least one TTI in which the power back-off is to be applied, which is at least partially unused.

6. The method according to claim 2, further comprising: The second network entity is provided with information about the first network entity's ability to apply power backoff during at least one of the at least partially unused TTIs.

7. The method of claim 6, wherein the information comprises at least one of the following: Maximum supported power backoff; One or more levels used when applying the power backoff; or One or more step sizes used when applying the power back-off.

8. The method of claim 2, wherein the signaling indicates the power back-off level of each of the at least one TTI among the at least partially unused TTIs.

9. The method of claim 1, wherein the TDD mode indicates that at least one of the TTIs is completely unused.

10. The method of claim 9, wherein the one or more actions comprise at least one of the following: Disable sending during at least one completely unused TTI; or Power to the power amplifier (PA) is turned off during at least one completely unused TTI.

11. The method of claim 1, wherein the TTI comprises a time slot or a symbol.

12. The method according to claim 1, wherein: The first network entity includes a radio unit (RU); The second network entity includes a distributed unit (DU); and The signaling includes section extension (SE).

13. The method according to claim 2, further comprising: Provide information about the TDD mode to the user equipment (UE).

14. A method for wireless communication at a second network entity, the method comprising: Obtain a Time Division Duplex (TDD) mode, wherein the Time Division Duplex (TDD) mode defines the uplink and downlink configurations of the Transmission Time Interval (TTI) for communication between a first network entity and a User Equipment (UE), wherein the TDD mode indicates that one or more of the TTIs are at least partially unused; as well as Send a signaling instruction indicating the TDD mode to the first network entity.

15. The method of claim 14, wherein the signaling indicates at least one of the at least partially unused TTIs, and the first network entity applies power backoff for the at least one TTI.

16. The method of claim 14, further comprising: Receive information from the first network entity regarding the first network entity's ability to apply power backoff during at least one TTI in a TTI that is at least partially unused.

17. The method of claim 16, wherein the information comprises at least one of the following: Maximum supported power backoff; One or more levels used when applying the power backoff; or One or more step sizes used when applying the power back-off.

18. The method of claim 14, wherein the signaling indicates the power back-off level of each TTI in at least one of the at least partially unused TTIs.

19. The method of claim 14, wherein the TDD mode indicates that at least one of the TTIs is completely unused.

20. The method of claim 14, wherein the TTI comprises a time slot or a symbol.

21. The method of claim 14, wherein: The first network entity includes a radio unit (RU); The second network entity includes a distributed unit (DU); and The signaling includes section extension (SE).

22. A method for conducting wireless communication at a user equipment (UE), the method comprising: Receive signaling from a first network entity indicating a Time Division Duplex (TDD) mode, the TDD mode defining uplink and downlink configurations for transmission time intervals (TTIs), wherein the TDD mode indicates that one or more TTIs are at least partially unused; as well as One or more actions are performed based on the indication that is at least partially unused in one or more of the TTIs.

23. The method of claim 22, wherein at least one of the actions comprises: Monitor downlink transmissions during at least one of the at least partially unused TTIs.

24. The method of claim 22, wherein at least one of the actions includes adjusting one or more parameters for receiving signals from the first network entity.

25. The method of claim 24, wherein: The one or more parameters include the number of receiving antennas; and The one or more actions include, based on the indication that one or more of the TTIs are at least partially unused, performing at least one of the following: increasing or decreasing the number of receiving antennas.

26. The method of claim 22, wherein the signaling indicates at least one TTI in which the one or more actions are to be performed, which is at least partially unused.

27. The method of claim 22, wherein the signaling indicates at least one action in each of at least one of at least partially unused TTIs.

28. The method of claim 22, wherein the TDD mode indicates that at least one of the TTIs is completely unused.

29. The method of claim 28, wherein the one or more actions comprise at least one of the following: Disable reception during at least one completely unused TTI; or Power off the receiver during at least one completely unused TTI.

30. The method of claim 22, wherein the TTI comprises a time slot or a symbol.

31. The method according to claim 22, wherein: The first network entity includes a radio unit (RU); and The signaling includes section extension (SE).