Signaling of expected time division duplex downlink-uplink configuration

Abstract

Various aspects of the disclosure generally relate to wireless communication. In some aspects, a network node can generate an intended time division duplex (TDD) downlink-uplink (DL-UL) configuration, where the network node is associated with a first central unit (CU) and a second CU, and where the intended TDD DL-UL configuration is for a cell served by the network node and associated with the second CU. The network node can transmit the intended TDD DL-UL configuration for the cell to the first CU. Numerous other aspects are described.

Description

[0001] Cross Reference to Related Applications

[0002] This Patent Application claims priority to U.S. Provisional Patent Application No. 62 / 706,848, filed September 14, 2020, entitled “INTERFERENCE MANAGEMENT AND POWER CORRDIATION IN RADIO ACCESS NETWORK SHARING SCENARIOS,” and U.S. Non-Provisional Patent Application No. 17 / 447,517, filed September 13, 2021, entitled “SIGNALING OF INTENDED TIMEDIVISION DUPLEXING DOWNLINK-UPLINK CONFIGURATION,” which are expressly incorporated by reference herein in their entirety. TECHNICAL FIELD

[0003] Aspects of the present disclosure generally relate to wireless communication, and to techniques and apparatuses for interference management and power coordination in radio access network (RAN) sharing scenarios. BACKGROUND

[0004] Wireless communication systems are widely deployed to provide various telecommunication services such as telephony, video, data, messaging, and broadcasts. Typical wireless communication systems can employ multiple-access technologies capable of supporting communication with multiple users by sharing available system resources (e.g., bandwidth, transmit power, etc.). Examples of such multiple-access technologies include code division multiple access (CDMA) systems, time division multiple access (TDMA) systems, frequency division multiple access (FDMA) systems, orthogonal frequency division multiple access (OFDMA) systems, single-carrier frequency division multiple access (SC-FDMA) systems, time division synchronous code division multiple access (TD-SCDMA) systems, and Long Term Evolution (LTE). LTE / LTE-Advanced is a set of enhancements to the Universal Mobile Telecommunications System (UMTS) mobile standard promulgated by the Third Generation Partnership Project (3 GPP).

[0005] A wireless network can include a number of base stations (BSs) that can support communication for a number of user equipment (UEs). A UE can communicate with a BS via the downlink and uplink. The downlink (or forward link) refers to the communication from the BS to the UE, and the uplink (or reverse link) refers to the communication from the UE to the BS. As will be described in more detail herein, a BS can be referred to as a Node B, a gNB, an access point (AP), a radio head, a transmit receive point (TRP), a new radio (NR) BS, a 5G Node B, and / or the like.

[0006] These multiple access technologies have been adopted in various telecommunication standards to provide common protocols to enable different wireless devices to communicate on a municipal, national, regional, and even global level. NR, which can also be referred to as 5G, is a set of enhancements to the LTE mobile standard promulgated by 3GPP. NR is designed to better support mobile broadband Internet access by improving spectral efficiency, lowering costs, improving services, making use of new spectrum, and better integrating with other open standards using orthogonal frequency division multiplexing (OFDM) with a cyclic prefix (CP) (CP-OFDM) on the downlink (DL), using CP- OFDM and / or SC-FDM (e.g., also known as discrete Fourier transform spread orthogonal frequency division multiplexing (DFT-s-OFDM)) for the uplink (UL), as well as supporting beamforming, multiple-input multiple-output (MIMO) antenna technology, and carrier aggregation. As the demand for mobile broadband access continues to increase, further improvements in LTE, NR, and other radio access technologies remain useful. SUMMARY

[0007] In some aspects, a method of wireless communication, performed by a network node, includes generating an intended time division duplex (TDD) downlink-uplink (DL-UL) configuration, wherein the network node is associated with a first central unit (CU) and a second CU, and wherein the intended TDD DL-UL configuration is for a cell served by the network node and associated with the second CU; and transmitting the intended TDD DL-UL configuration for the cell to the first CU.

[0008] In some aspects, a method of wireless communication, performed by a network node, includes generating an intended time division duplex (TDD) downlink-uplink (DL-UL) configuration, wherein the network node is associated with a first central unit (CU) and a second CU, and wherein the intended TDD DL-UL configuration is for a cell served by the network node and associated with the second CU; and transmitting the intended TDD DL-UL configuration for the cell to the first CU.

[0009] In some aspects, a network node for wireless communication includes a memory and one or more processors coupled to the memory, the one or more processors configured to: generate an intended TDD DL-UL configuration, wherein the network node is associated with a first CU and a second CU, and wherein the intended TDD DL-UL configuration is for a cell served by the network node and associated with the second CU; and transmit the intended TDD DL-UL configuration for the cell to the first CU.

[0010] In some aspects, a first CU for wireless communication includes a memory and one or more processors coupled to the memory, the one or more processors configured to: receive, from a network node, an intended TDD DL-UL configuration, wherein the network node is associated with the first CU and a second CU, and wherein the intended TDD DL-UL configuration is for a cell served by the network node and associated with the second CU; and communicate based at least in part on the intended TDD DL-UL configuration for the cell.

[0011] In some aspects, a non-transitory computer-readable medium storing a set of instructions for wireless communication includes one or more instructions that, when executed by one or more processors of a network node, cause the network node to: generate an intended TDD DL-UL configuration, wherein the network node is associated with a first CU and a second CU, and wherein the intended TDD DL-UL configuration is for a cell served by the network node and associated with the second CU; and transmit, to the first CU, the intended TDD DL-UL configuration for the cell.

[0012] In some aspects, a non-transitory computer-readable medium storing a set of instructions for wireless communication includes one or more instructions that, when executed by one or more processors of a first CU, cause the first CU to: receive, from a network node, an intended TDD DL-UL configuration, wherein the network node is associated with the first CU and a second CU, and wherein the intended TDD DL-UL configuration is for a cell served by the network node and associated with the second CU; and communicate based at least in part on the intended TDD DL-UL configuration for the cell.

[0013] In some aspects, an apparatus for wireless communication includes means for generating an intended TDD DL-UL configuration, wherein the apparatus is associated with a first CU and a second CU, and wherein the intended TDD DL-UL configuration is for a cell served by the apparatus and associated with the second CU; and means for transmitting, to the first CU, the intended TDD DL-UL configuration for the cell.

[0014] In some aspects, an apparatus for wireless communication includes means for receiving, from a network node, an intended TDD DL-UL configuration, wherein the network node is associated with the apparatus and a second CU, and wherein the intended TDD DL-UL configuration is for a cell served by the network node and associated with the second CU; and means for communicating based at least in part on the intended TDD DL-UL configuration for the cell.

[0015] As generally described herein with reference to the figures and descriptions, aspects generally include methods, apparatus, systems, computer program products, non-transitory computer-readable media, user equipment, base stations, wireless communication devices, and / or processing systems.

[0016] The foregoing has outlined rather broadly the features and technical advantages of examples according to the disclosure in order that the detailed description that follows can be better understood. Additional features and advantages will be described hereinafter. The disclosed concepts and specific examples can be readily utilized as bases for modifying or designing other for carrying the same purposes thereof. Such equivalent constructions are not to be regarded as a departure from the scope of the appended claims. The illustrative examples disclosed herein are to be considered merely illustrative, rather than restrictive, and all changes that come within the meaning and equivalency range of the appended claims are intended to be embraced therein. The claims are to be afforded their broadest interpretation so as to encompass all equivalent structures and functions.

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

[0018] In order that the above-recited features of the present disclosure can be understood in detail, a more particular description will be rendered by reference to various aspects, some of which are illustrated in the appended drawings. It is appreciated that the drawings are not limiting of the scope of the present disclosure, as some aspects are described with reference to multiple drawings. Like references can indicate like elements or features in different drawings.

[0019] Figure 1is a diagram illustrating an example of a wireless network, in accordance with the present disclosure.

[0020] Figure 2 is a diagram illustrating an example of a base station in communication with a user equipment (UE) in a wireless network, in accordance with the present disclosure.

[0021] Figure 3 is a diagram illustrating an example of radio access network (RAN) sharing, in accordance with the present disclosure.

[0022] Figure 4 is a diagram illustrating an example of relaying an intended time division duplex (TDD) downlink-uplink (DL-UL) configuration associated with a cell served by a second central unit (CU) to a first CU, in accordance with the present disclosure.

[0023] Figures 5-6 is a diagram illustrating an example process associated with intended TDD DL-UL configuration signaling in a RAN sharing deployment, in accordance with the present disclosure.

[0024] Figures 7-8 is a block diagram of an example apparatus for wireless communication, in accordance with the present disclosure. DETAILED DESCRIPTION

[0025] Various aspects of the disclosure are described in further detail below. The disclosure may, however, be embodied in many different forms and should not be construed as limited to any specific structure or function presented throughout this disclosure. Rather, these aspects are provided as illustrative examples so that this disclosure will be thorough and complete, and will fully convey the scope of the disclosure to those skilled in the art. Based on the teachings herein one skilled in the art should appreciate that the scope of the disclosure is intended to cover any aspect of the disclosure disclosed herein, whether implemented independently of or combined with any additional aspect of the disclosure. For example, an apparatus can be implemented or a method can be practiced using any number of the aspects set forth herein. In addition, the scope of the disclosure is intended to cover such an apparatus or method which is practiced using, as alternative to, in combination with, or in addition to, the aspects set forth herein. It should be understood that any aspect of the disclosure disclosed herein can be embodied by one or more elements of a claim.

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

[0027] It should be noted that while aspects can be described herein using terminology commonly associated with a 5G or NR wireless access technology (RAT), aspects of the present disclosure can be applied to other RATs, such as a 3G RAT, a 4G RAT, and / or a RAT subsequent to 5G (e.g., 6G).

[0028] Figure 1 is a diagram illustrating an example of a wireless network 100, in accordance with the present disclosure. Wireless network 100 can be or include elements of a 5G (NR) network and / or an LTE network, among other examples. Wireless network 100 can include a number of base stations 110 (shown as BS 110a, BS 110b, BS 110c, and BS 1 lOd) and other network entities. A base station (BS) is an entity that communicates with user equipment (UEs) and can also be referred to as an NR BS, a Node B, a gNB, a 5G node B (NB), an access point, a transmit receive point (TRP), and / or the like. Each BS can provide communication coverage for a particular geographic area. In 3GPP, the term “cell” can refer to a coverage area of a BS and / or a BS subsystem serving the coverage area, depending on the context in which the term is used.

[0029] BSs can be referred to as macro BS, micro BS, pico BS, and / or the like. A BS can be utilized in conjunction with a cell. A cell can refer to a coverage area of a BS and / or a BS subsystem serving the coverage area, depending on the context in which the term is used. For example, the term can refer to a coverage area of a BS and / or a BS subsystem serving the coverage area, depending on the context in which the term is used. A BS can support one or multiple (e.g., three) cells. The terms “eNB,” “base station,” “NR BS,” “gNB,” “TRP,” “AP,” “node B,” “5G NB,” and “cell” can be used interchangeably herein. Figure 1 In the example shown in FIG. 1, BS 110a can be a macro BS for a macro cell 102a, BS 110b can be a pico BS for a pico cell 102b, and BS 110c can be a femto BS for a femto cell 102c. A BS can support one or multiple (e.g., three) cells. The terms “eNB,” “base station,” “NR BS,” “gNB,” “TRP,” “AP,” “node B,” “5G NB,” and “cell” can be used interchangeably herein.

[0030] In some aspects, a cell can not necessarily be stationary, and the geographic area of the cell can move based on the location of a mobile BS. In some aspects, BSs can be interconnected to one another and / or to one or more other BSs or network nodes (not shown) in wireless network 100 through various types of backhaul interfaces such as a direct physical connection or a virtual network using any suitable transport network.

[0031] Wireless network 100 can also include relay stations. A relay station is an entity that can receive a transmission of data from an upstream station (e.g., a BS or a UE) and send a transmission of the data to a downstream station (e.g., a UE or a BS). A relay station can also be a UE that can relay transmissions for other UEs. Figure 1 In the example shown in Figure 1, a relay BS 1 lOd can communicate with macro BS 110a and a UE 120d in order to facilitate communications between BS 110a and UE 120d. A relay BS can also be referred to as a relay station, a relay base station, a relay, or the like.

[0032] Wireless network 100 can be a heterogeneous network that includes BSs of different types, such as macro BSs, pico BSs, femto BSs, relay BSs, or the like. These different types of BSs can have different transmit power levels, different coverage areas, and different impacts on interference. For example, macro BSs can have a high transmit power level (e.g., 5 to 40 watts) whereas pico BSs, femto BSs, and relay BSs can have relatively lower transmit power levels (e.g., 0.1 to 2 watts).

[0033] A network controller 130 can couple to a set of BSs and can provide coordination and control for these BSs. Network controller 130 can be

[0034] The UEs 120 (e.g., 120a, 120b, 120c) can be dispersed throughout the wireless network 100, and each UE can be stationary or mobile. A UE can also be referred to as an access terminal, a terminal, a mobile station, a subscriber unit, a station, etc. A UE can be a cellular phone (e.g., a smart phone), a personal digital assistant (PDA), a wireless modem, a wireless communication device, a handheld device, a laptop computer, a cordless phone, a wireless local loop (WLL) station, a tablet, a camera, a gaming device, a netbook, a smartbook, an ultrabook, a medical device or equipment, a biometric sensor / device, a wearable device such as a smart watch, smart clothing, smart glasses, a smart wrist band, a smart jewelry (e.g., a smart ring, a smart bracelet), an entertainment device (e.g., a music or video device, or a satellite radio), a vehicular component or sensor, a smart meter / sensor, industrial manufacturing equipment, a global positioning system device, or any other suitable device that is configured to communicate via a wireless or wired medium.

[0035] Some UEs can be considered machine-type communication (MTC) or evolved or enhanced machine-type communication (eMTC) UEs. MTC and eMTC UEs include, for example, robots, drones, remote devices, sensors, meters, monitors, and / or location tags, that can communicate with a base station, another device (e.g., remote device), or some other entity. A wireless node can provide, for example, connectivity for or to a network (e.g., a wide area network such as the Internet or a cellular network) via a wired or wireless communication link. Some UEs can be considered Intemet-of-Things (IoT) devices, and / or can be implemented as NB-IoT (narrowband

[0036] In general, any number of wireless networks can be deployed in a given geographic area. Each wireless network can support a particular RAT and can operate on one or more frequencies. A RAT can also be referred to as a radio technology, an air interface, etc. A frequency can also be referred to as a carrier, a frequency channel, etc. Each frequency can support a single RAT in a given geographic area in order to avoid interference between wireless networks of different RATs. In some cases, NR or 5G RAT networks can be deployed.

[0037] In some aspects, two or more UEs 120 (e.g., shown as UE 120a and UE 120e) can communicate directly using one or more sidelink channels (e.g., without using a base station 110 as an intermediary to communicate with each other). For example, UE s 120 can communicate using peer-to-peer (P2P) communications, device-to-device (D2D) communications, vehicle-to-everything (V2X) protocols (which can include vehicle-to-vehicle (V2V) protocols or vehicle-to-infrastructure (V2I) protocols), and / or netw ork communications. In this case, the UE 120s can perform scheduling operations, resource selection operations, and / or other operations described elsewhere herein as being performed by the base station 110.

[0038] Devices of the wireless network 100 can use electromagnetic spectrum for communications, which can be subdivided, based on frequency or wavelength, into various classes, bands, channels, and / or the like. For example, devices of the wireless network 100 can communicate using an operating band having a first frequency range (FR1), which can span from 410 MHz to 7.125 GHz, and / or can communicate using an operating band having a second frequency range (FR2), which can span from 24.25 GHz to 52.6 GHz. The frequencies between FR1 and FR2 are sometimes referred to as mid-band frequencies. Although a portion of FR1 is greater than 6 GHz, FR1 is often referred to as a “sub-6 GHz” band. Similarly, FR2 is often referred to as a “millimeter wave” band despite being different from the extremely high frequency (EHF) band (30 GHz - 300 GHz) which is identified by the International Telecommunications Union (ITU) as a “millimeter wave” band. Thus, unless specifically stated otherwise, the term “sub-6 GHz” or the like means frequencies less than 6 GHz, frequencies within FR1, and / or mid-band frequencies (e.g., greater than 7.125 GHz), as appropriate, if used herein. Similarly, unless specifically stated otherwise, the term “millimeter wave” or the like means frequencies within the EHF band, frequencies within FR2, and / or mid-band frequencies (e.g., less than 24.25 GHz), as appropriate, if used herein. It is contemplated that frequencies included in FR1 and FR2 can be modified, and techniques described herein are applicable to those modified frequency ranges.

[0039] As described above, Figure 1 are provided by way of example only. Other examples can differ from what is described Figure 1 without departing from the spirit of the disclosure.

[0040] Figure 2is a diagram illustrating an example 200 of a base station 110 in communication with a UE 120 in a wireless network 100, in accordance with the present disclosure. Base station 110 can be equipped with T antennas 234a through 234t, and UE 120 can be equipped with R antennas 252a through 252r, where in general T > 1 and R > 1.

[0041] At base station 110, a transmit processor 220 can receive data from a data source 212 for one or more UEs, select one or more modulation and coding schemes (MCSs) for each UE based at least in part on channel quality indicators (CQIs) received from that UE, process (e.g., encode and modulate) the data for each UE based at least in part on the MCS(s) selected for the UE, and provide data symbols for all UEs. Transmit processor 220 can also process system information (e.g., semi-static resource partitioning information (SRPI)) and control information (e.g., CQI requests, grants, and / or upper layer signaling) and provide overhead symbols and control symbols. Transmit processor 220 can also generate reference symbols for reference signals (e.g., a cell-specific reference signal (CRS) or a demodulation reference signal (DMRS)) and synchronization signals (e.g., a primary synchronization signal (PSS) or a secondary synchronization signal (SSS)). A transmit (TX) multiple-input multiple-output (MIMO) processor 230 can perform spatial processing (e.g., precoding) on the data symbols, the control symbols, the overhead symbols, and / or the reference symbols, if applicable, and can provide T output symbol streams to T modulators (MODs) 232a through 232t. Each modulator 232 can process a respective output symbol stream (e.g., for OFDM) to obtain an output sample stream. Each modulator 232 can further process (e.g., convert to analog, amplify, filter, and upconvert) the output sample stream to obtain a downlink signal. T downlink signals from modulators 232a through 232t can be transmitted via T antennas 234a through 234t, respectively.

[0042] At the UE 120, the antennas 252a through 252r can receive the downlink signals from the base station 110 and / or other base stations and can provide received signals to the demodulators (DEMODs) 254a through 254r, respectively. Each demodulator 254 can condition (e.g., filter, amplify, downconvert, and digitize) a received signal to obtain input samples. Each demodulator 254 can further process the input samples (e.g., for OFDM) to obtain received symbols. A MIMO detector 256 can obtain received symbols from all R demodulators 254a through 254r, perform MIMO detection on the received symbols if applicable, and provide detected symbols. A receive processor 258 can process (e.g., demodulate and decode) the detected symbols, provide decoded data for the UE 120 to a data sink 260, and provide decoded control information and system information to a controller / processor 280. The term “controller / processor” can refer to one or more controllers, one or more processors, or combinations thereof. A channel processor can determine reference signal received power (RSRP) parameters, received signal strength indicator (RSSI) parameters, reference signal received quality (RSRQ) parameters, and / or CQI parameters, among other examples. In some aspects, one or more components of UE 120 can be included in a housing 284.

[0043] The network controller 130 can include a communication unit 294, a controller / processor 290, and a memory 292. The network controller 130 can include, for example, one or more devices in a core network. The network controller 130 can communicate with the base station 110 via the communication unit 294.

[0044] Antennas (e.g., antennas 234a through 234t and / or antennas 252a through 252r) can include or be included within one or more antenna panels, antenna groups, sets of antenna elements, and / or antenna arrays, among other examples. An antenna panel, antenna group, set of antenna elements, and / or antenna array can include one or more antenna elements. An antenna panel, antenna group, set of antenna elements, and / or antenna array can include a set of co-planar antenna elements and / or a set of non-co-planar antenna elements. An antenna panel, antenna group, set of antenna elements, and / or antenna array can include antenna elements within a single housing and / or antenna elements within multiple housings. An antenna panel, antenna group, set of antenna elements, and / or antenna array can include one or more antenna elements coupled to one or more transmit and / or receive components (such as one or more components of a transceiver 230 and / or a transceiver 270). Figure 2 An antenna panel, antenna group, set of antenna elements, and / or antenna array can include one or more antenna elements coupled to one or more transmit and / or receive components (such as one or more components of a transceiver 230 and / or a transceiver 270).

[0045] On the uplink, at UE 120, a transmit processor 264 can receive and process data from a data source 262 and control information (e.g., for reports comprising RSRP, RSSI, RSRQ, and / or CQI) from controller / processor 280. Transmit processor 264 can also generate reference symbols for one or more reference signals. The symbols from transmit processor 264 can be precoded by a TX MIMO processor 266 if applicable, further processed by modulators 254a through 254r (e.g., for DFT-s-OFDM or CP-OFDM), and transmitted to base station 110. In some aspects, a modulator and a demodulator (e.g., MOD / DEMOD 254) of the UE 120 can be included in a modem of the UE 120. In some aspects, the UE 120 includes a transceiver. The transceiver can include any combination of antenna(s) 252, modulators and / or demodulators 254, MIMO detector 256, receive processor 258, transmit processor 264, and / or TX MIMO processor 266. The transceiver can be used by a processor (e.g., controller / processor 280) and memory 282 to perform aspects of any of the methods described herein (for example, as described with reference to Figures 3-8 the description).

[0046] At base station 110, the uplink signals from UE 120 and other UEs can be received by antennas 234, processed by demodulators 232, detected by a MIMO detector 236 if applicable, and further processed by a receive processor 238 to obtain decoded data and control information sent by UE 120. Receive processor 238 can provide the decoded data to a data sink 239 and to controller / processor 240 for control information. Base station 110 can include communication unit 244 and communicate to network controller 130 via communication unit 244. Base station 110 can include a scheduler 246 to schedule UEs 120 for downlink and / or uplink communications. In some aspects, a modulator and a demodulator (e.g., MOD / DEMOD 232) of the base station 110 can be included in a modem of the base station 110. In some aspects, the base station 110 includes a transceiver. The transceiver can include any combination of antenna(s) 234, modulators and / or demodulators 232, MIMO detector 236, receive processor 238, transmit processor 220, and / or TX MIMO processor 230. The transceiver can be used by a processor (e.g., controller / processor 240) and memory 242 to perform aspects of any of the methods described herein (for example, as described with reference to Figures 3-8 the description).

[0047] Controller / processor 240 of base station 110, controller / processor 280 of UE 120, and / or Figure 2Any other component may perform one or more techniques associated with the anticipated Time Division Duplex (TDD) downlink-uplink (DL-UL) configuration signaling for RAN shared deployment, as described in more detail elsewhere herein. For example, the controller / processor 240 of base station 110, the controller / processor 280 of UE 120, and / or Figure 2 Any other component can execute or direct, for example Figure 5 Processing 500 Figure 6 The operation of processing 600 and / or other processing described herein. Memory 242 and 282 may store data and program code for base station 110 and UE 120, respectively. In some aspects, memory 242 and / or memory 282 may include a non-transitory computer-readable medium storing one or more instructions (e.g., code and / or program code) for wireless communication. For example, one or more instructions, when executed by one or more processors of base station 110 and / or UE 120 (e.g., directly, or after compilation, translation, and / or interpretation), may cause one or more processors, UE 120, and / or base station 110 to perform or direct, for example... Figure 5 Process 500 Figure 6 The operation of process 600 and / or other processes as described herein. In some aspects, among other examples, execution instructions may include run instructions, transform instructions, compile instructions, and / or interpret instructions.

[0048] In some aspects, the network node includes components for generating a desired TDD DL-UL configuration, wherein the network node is associated with a first central unit (CU) and a second CU, and wherein the desired TDD DL-UL configuration is for a cell served by the network node and associated with the second CU; and / or components for transmitting the desired TDD DL-UL configuration of the cell to the first CU. For example, components of the network node performing the operations described herein may include a transmit processor 220, a TXMIMO processor 230, a modulator 232, an antenna 234, a demodulator 232, a MIMO detector 236, a receive processor 238, a controller / processor 240, a memory 242, and / or a scheduler 246.

[0049] In some aspects, the network node includes components for sending information to a first CU indicating a second anticipated TDD DL-UL configuration for a second cell. In some aspects, the network node includes components for receiving a request from the first CU for the anticipated TDD DL-UL configuration, wherein the transmission of the anticipated TDD DL-UL configuration is at least in part based on the request.

[0050] In some aspects, the first CU includes means for receiving, from a network node, an intended TDD DL-UL configuration, wherein the network node is associated with the first CU and a second CU, and wherein the intended TDD DL-UL configuration is for a cell served by the network node and associated with the second CU; and means for communicating based at least in part on the intended TDD DL-UL configuration for the cell. The means for the first CU to perform operations described herein can include, for example, transmit processor 220, TX MIMO processor 230, modulator 232, antenna 234, demodulator 232, MIMO detector 236, receive processor 238, controller / processor 240, memory 242, and / or scheduler 246. In some aspects, the first CU includes means for receiving, from a network node, information indicating a second intended TDD DL-UL configuration for a second cell. In some aspects, the first CU includes means for transmitting, to the network node, a request for an intended TDD DL-UL configuration, wherein receiving the intended TDD DL-UL configuration is based at least in part on the request. In some aspects, the first CU includes means for performing cross-link interference mitigation based at least in part on the intended TDD DL-UL configuration. In some aspects, the first CU includes means for performing power coordination for dual connectivity based at least in part on the intended TDD DL-UL configuration. In some aspects, the first CU includes means for forwarding the intended TDD DL-UL configuration to a second distributed unit (DU) associated with the first CU. In some aspects, the first CU includes means for receiving a second intended TDD DL-UL configuration. In some aspects, the first CU includes means for merging the first intended TDD DL-UL configuration and the second intended TDD DL-UL configuration. In some aspects, the first CU includes means for forwarding the merged intended TDD DL-UL configuration to a DU associated with the first CU. In some aspects, the first CU includes means for transmitting the intended TDD DL-UL configuration to a third CU or gNB.

[0051] Although Figure 2 The blocks in FIG. 14 are illustrated as distinct components only for the sake of clarity, and the functionality described regarding the blocks can be implemented in a single hardware, software, or combined component or in various combinations of components. For example, the functionality described for transmit processor 264, receive processor 258, and / or TX MIMO processor 266 can be performed by controller / processor 280 or under its control.

[0052] As described above, Figure 2 are provided by way of example only. Other examples can differ from what is described. Figure 2 in connection with what is described.

[0053] Figure 3 is a diagram illustrating an example 300 of RAN sharing according to the present disclosure. As shown, the example 300 includes a gNB central unit 1 (CU1) and a gNB central unit 2 (CU2). Further, the example 300 includes a plurality of gNB DUs. A gNB can include a CU and one or more DUs. The CU can communicate with the DUs via an Fl interface, such as an Fl control (Fl-C) interface or an Fl application protocol (Fl-AP) interface. The DUs can be associated with a gNB or can be associated with a network node, such as an integrated access and backhaul (IAB) node.

[0054] Generally, a gNB CU can handle packet data convergence protocol (PDCP) layer functions, while a gNB DU can handle radio link control (RLC), medium access control (MAC), and physical (PHY) layer functions. For example, the CU can handle network configuration and management tasks, while the DU can handle layer 1 or layer 2 communication tasks, such as relaying, scheduling, etc. Thus, the CU / DU architecture can help virtualize network functions in the CU while facilitating lower layer functions (e.g., RLC / MAC / PHY) that can be difficult to virtualize.

[0055] In some cases, multiple CUs can be associated with an interface between one another. For example, a first CU and a second CU can have an Xn interface that is based at least in part on the first CU and the second CU being associated with a same public land mobile network (PLMN) or a same non-public network (NPN). Thus, information can be exchanged between the first CU and the second CU. In some aspects, two CUs can be associated with different networks (e.g., different PLMNs or different NPNs). If two CUs are associated with different networks, the two CUs can not be associated with a direct interface between one another.

[0056] A DU can handle scheduling for one or more child nodes, such as UEs, network nodes, etc. The child nodes are represented by the circles. The child nodes can be connected to units served by the DUs. For example, gNB DU1 is associated with a single child node that can be connected to a cell served by gNB DU1. Figure 3

[0057] ​In some cases, a network node can provide multiple DUs. For example, the network node shown by reference number 310 can provide a first DU associated with a gNB CU1 and a second DU associated with a gNB CU2 (e.g., a gNB DU2). In this case, the first DU can be associated with the CU1 based at least in part on the units provided by the first DU being associated with the CU1, while the second DU can be associated with the CU gNB CU2 based at least in part on the units provided by the second DU being associated with the CU2. The first DU and the second DU can be capable of exchanging information with each other. Thus, the first DU and the second DU can effectively have an Fl-C or radio resource control (RRC) interface with both the gNB CU1 and the gNB CU2, even though the gNB CU1 and the gNB CU2 do not have an interface between each other.

[0058] A cell can have a cell global identifier (CGI), such as an NR CGI (NCGI). The NCGI uniquely identifies a cell. The NCGI includes a PLMN identifier and an NR cell identifier. The PLMN identifier (which can include 24 bits) can include an MCC (e.g., 12 bits) and an MNC (e.g., 12 bits). The NCI (e.g., 36 bits in 5G) can include a gNB identifier (e.g., the leftmost 22 to 32 bits) and a local cell identifier (e.g., the remaining bits of the NCI). The gNB can be unique within a gNB and can be common to all cells (e.g., all IAB donor DUs and all IAB node DUs) that a gNB serves with one IAB donor CU. Equivalently, the PLMN and gNB ID can globally identify a gNB.

[0059] A cell can be a TDD cell. For a TDD cell, time resources (e.g., slots or symbols) can be designated for either uplink only communication, downlink only communication, or either uplink or downlink communication (referred to as flexible resources). Designating a time resource as UL only, DL only, or flexible can be designated by a TDD DL-UL slot configuration. The configuration can indicate a periodicity and a list of slot indices based at least in part on the periodicity. The configuration can also indicate which symbols of the slots identified by the list of slot indices are uplink only, downlink only, or flexible.

[0060] A cell can be associated with an intended TDD DL-UL configuration. The intended TDD DL-UL configuration can indicate a subcarrier spacing, a cyclic prefix, and a TDD DL-UL slot configuration of the cell. A DU or a CU can determine the intended TDD DL-UL configuration and can provide the intended TDD DL-UL configuration to another node (e.g., another next generation wireless access network (NG-RAN) node, such as another CU or DU). The receiving NG-RAN node (e.g., a neighboring NG-RAN node) can consider the intended TDD DL-UL configuration when operating the cell of the receiving NG-RAN node for cross-link interference mitigation and / or new radio dual connectivity (NR-DC) power coordination.

[0061] If the intended TDD DL-UL configuration information element is included in an Xn application protocol (Xn-AP) message, the receiving NG-RAN node can consider the information element for cross-link interference management and / or NR-DC power coordination with the sending NG-RAN node. If the intended TDD DL-UL configuration information element is present in an Fl-AP message to a gNB-CU, the receiving gNB-CU can use the intended TDD DL-UL configuration for cross-link interference management and / or NR-DC power coordination. In some cases, a gNB CU can consolidate intended TDD DL-UL configuration information received from two or more DUs. If the neighboring cell information list information element is present in an Fl-AP message to a gNB-DU, the receiving gNB-DU can use the received information for cross-link interference management and / or NR-DC power coordination. Thus, the intended TDD DL-UL configuration can be used for cross-link interference mitigation and / or NR-DC power coordination, particularly in systems with multiple CUs and / or multiple DUs.

[0062] If there is an Xn interface between gNB CU1 and gNB CU2, gNB CU2 can send information to gNB CU1 indicating the intended TDD DL-UL configuration for a cell served by gNB CU2. gNB CU1 can then forward the intended TDD DL-UL configuration to gNB DU1 for cross-link interference management or NR-DC power coordination. However, in some cases, there can not be an Xn interface between gNB CU1 and gNB CU2. For example, if gNB CU1 is associated with a first network and gNB CU2 is associated with a second network, there can not be a direct interface between gNB CU1 and gNB CU2, meaning that the intended TDD DL-UL configuration cannot be communicated between gNB CU1 and gNB CU2. If the intended TDD DL-UL configuration cannot be communicated between gNB CU1 and gNB CU2 (and thus between the DUs associated with gNB CU1 or gNB CU2), the DUs can not be able to consider the intended TDD DL-UL configuration when performing cross-link interference mitigation or NR-DC power coordination, which increases cross-link interference and decreases power coordination of network nodes and / or UEs.

[0063] Some techniques and apparatuses described herein enable a DU (e.g., gNB DU2) with a signaling connection to a first CU and a second CU (or a network node implementing the DU, such as the network node shown by reference number 310) to provide the intended TDD DL-UL configuration for a cell associated with the second CU to the first CU. For example, the network node shown by reference number 310 can provide the intended TDD DL-UL configuration for a cell 320 associated with gNB CU2 from gNB CU2 to gNB CU1 via respective Fl-C or RRC connections with gNB CU1 and gNB CU2. In some aspects, the cell can be served by the DU and can be associated with an NCI associated with the second CU. As another example, the cell can be associated with an NCI associated with the first CU, where the cell is deactivated by the first CU or access is prohibited for child nodes that select the network associated with the first CU. The first CU can consider the intended TDD DL-UL configuration for cross-link interference mitigation, NR-DC power coordination, or other operations. Additionally or alternatively, the first CU can forward the intended TDD DL-UL configuration to one or more DUs associated with the first CU, and the one or more DUs can perform cross-link interference mitigation, NR-DC power coordination, or other operations. Thus, interference is reduced, NR-DC power coordination is improved, and coexistence of different networks (e.g., different PLMNs or different NPNs) is improved.

[0064] As described above,Figure 3 are provided by way of example only. Other examples can differ from those specifically described. Figure 3 what is described.

[0065] Figure 4 is a diagram illustrating an example 400 of relaying an intended TDD DL-UL configuration associated with a cell served by a second CU to a first CU, according to the present disclosure. As shown, example 400 includes a first CU (e.g., a gNB CU, such as gNB CU1 depicted in Figure 3 ), a second CU (e.g., a gNB CU, such as gNB CU2 depicted in Figure 3 ), and DUs (e.g., gNB DUs, such as gNB DU1 and gNB DU2 depicted in Figure 3 ). In some aspects, one or more operations described as being performed by a DU can be performed by the network node implementing the DU, or by another DU implemented by the network node implementing the DU. Additionally or alternatively, communication operations of a DU, such as transmitting and receiving, can be performed by a mobile terminal (MT) associated with the DU.

[0066] A network node associated with the first CU (e.g., a DU, a MT, a UE, etc.) is indicated by the dashed outline in Figure 4 . For example, a DU associated with the first CU can provide a cell associated with an NCI identifying the first CU. Network nodes associated with the second CU are indicated by the solid outline. Here, a first DU is associated with the second CU, and a second DU and a third DU are associated with the first CU. Further, the first DU and the second DU are implemented at a single network node. For example, the first DU and the second DU can be logical DUs implemented by the network node. The first DU can be associated with a signaling connection with the second CU (e.g., via an Fl interface, an RRC interface, or a similar interface). The second DU and the third DU can be associated with signaling connections with the first CU (e.g., via an Fl interface, an RRC interface, or a similar interface). Thus, the network device implementing the first DU and the second DU can communicate with the first CU and the second CU.

[0067] As shown by reference number 405, the first CU can send, via the second DU, a request to the first DU for one or more intended TDD DL-UL configurations associated with the second CU. For example, the first CU can send the request shown by reference number 405 via a signaling connection between the first CU and the second DU. The second DU can provide the request shown by reference number 405 to the first DU over a signaling interface between the second DU and the first DU. In some aspects, the first CU can request one or more intended TDD DL-UL configurations for cells 415 served by the first DU and associated with the second CU. For example, the first CU can request a consolidated intended TDD DL-UL configuration, or can request separate intended TDD DL-UL configurations for cells 415 served by the first DU and associated with the second CU. A consolidated intended TDD DL-UL configuration refers to an information element that indicates intended TDD DL-UL configurations for multiple different cells. In some aspects, the first DU can receive an activation of a cell from the second CU. For example, the first DU can receive an activation of cell 415 from the second CU.

[0068] As shown by reference number 410, the first DU can generate one or more intended TDD DL-UL configurations for cells 415 served by the second CU. For example, the first DU can generate the one or more intended TDD DL-UL configurations based at least in part on respective TDD DL-UL slot configurations of the one or more cells 415. In some aspects, the first DU can receive information from the second CU indicating the one or more intended TDD DL-UL configurations. In some aspects, the first DU can determine the one or more intended TDD DL-UL configurations. For example, the first DU can determine the one or more intended TDD DL-UL configurations based at least in part on serving the one or more cells 415.

[0069] As shown by reference number 420, the first DU can provide, via the second DU, information to the first CU indicating one or more intended TDD DL-UL configurations associated with the one or more cells 415. For example, the first DU can provide the information indicating the one or more intended TDD DL-UL configurations via a signaling connection between the first CU and the second DU. In some aspects, the first DU can provide information indicating an intended TDD DL-UL configuration for a cell based at least in part on the first CU requesting the intended TDD DL-UL configuration for the cell. In some aspects, the first DU can provide information indicating one or more intended TDD DL-UL configurations for each cell served by the first DU and associated with the second CU.

[0070] In some aspects, the cell for which the intended TDD DL-UL configuration is provided can have an NCI carrying an identifier of the second CU (e.g., a second gNB associated with the second CU). In some aspects, the cell for which the intended TDD DL-UL configuration is provided can have an NCI carrying an identifier of the first CU (e.g., a first gNB associated with the first CU), where the cell is deactivated by the first CU or access is prohibited for a child node of the PLMN selected to associate with the first CU.

[0071] The intended TDD DL-UL configuration can include, for example, information indicating a transmission periodicity associated with the respective cell, information indicating a set of slots (e.g., information indicating respective indices of a set of slots), a slot format for the set of slots (e.g., a slot format indicating uplink symbols, downlink symbols, or flexible symbols), and / or the like. In some aspects, the intended TDD DL-UL configuration can include at least a portion of the information included in the intended TDD DL-UL configuration as described above in connection with Figure 3

[0072] In some aspects, as shown in example 300, the first DU can serve multiple cells. In this case, the first DU can provide an intended TDD DL-UL configuration for multiple cells. For example, the first DU can transmit a separate intended TDD DL-UL configuration for each cell served by the first DU. As another example, the first DU can transmit a consolidated intended TDD DL-UL configuration for a first cell and a second cell, as described elsewhere. In some aspects, the different cells for which the first DU provides an intended TDD DL-UL configuration can be associated with the first CU, the second CU, or the third CU. For example, the first DU can provide an intended TDD DL-UL configuration for a first cell associated with the second CU and for a second cell associated with one of the first CU, the second CU, or the third CU. Thus, the first DU can provide intended TDD DL-UL configurations for cells associated with the same CU or different CUs.

[0073] As shown by reference number 425, the first CU can perform one or more actions based at least in part on the one or more intended TDD DL-UL configurations received from the first DU. As one example, the first CU can perform or configure cross-link interference (CLI) mitigation based at least in part on the one or more intended TDD DL-UL configurations. As another example, the first CU can perform NR-DC power coordination based at least in part on the one or more intended TDD DL-UL configurations.

[0074] ​In some aspects, as shown by reference number 430, the first CU can provide at least a portion of the one or more intended TDD DL-UL configurations to a third DU. For example, the first CU can forward at least a portion of the one or more intended TDD DL-UL configurations to one or more DUs associated with the first CU. As shown by reference number 435, the third DU (e.g., a DU associated with the first CU) can perform an action based at least in part on the one or more intended TDD DL-UL configurations. For example, the third DU can perform cross-link interference mitigation, NR-DC power coordination, and / or the like.

[0075] In some aspects, the first CU can receive a plurality of intended TDD DL-UL configurations. For example, the first CU can receive the plurality of intended TDD DL-UL configurations from the same DU, from different DUs, or from another CU (e.g., a second CU or a different CU). In some aspects, the first CU can merge the plurality of intended TDD DL-UL configurations to form a merged intended TDD DL-UL configuration. In some aspects, the first CU can forward the merged intended TDD DL-UL configuration to a DU that has a signaling connection with the first CU. For example, the first CU can forward the merged intended TDD DL-UL configuration to a DU associated with the first CU. In some aspects, the first CU can transmit the intended TDD DL-UL configuration received from the first DU to another CU gNB (e.g., a CU associated with the other CU gNB). Additionally or alternatively, the first CU can transmit the merged intended TDD DL-UL configuration to another CU (e.g., a CU associated with the other CU gNB) that incorporates the received intended TDD DL-UL configuration gNB.

[0076] By transmitting the one or more intended TDD DL-UL configurations to the first CU, the first DU facilitates cross-link interference mitigation and NR-DC power coordination for the first CU and / or DUs served by the first CU. Thus, the first DU reduces cross-link interference, improves UE power utilization, and improves coexistence of CUs such as CUs associated with different networks.

[0077] As described above, Figure 4 are provided by way of example only. Other examples can differ from what is described Figure 4 without departing from the spirit of the disclosure.

[0078] Figure 5 is a diagram illustrating an example process 500 performed, for example, by a network node, in accordance with the present disclosure. Example process 500 is a process performed by a gNB DU2, for example, Figure 3 in accordance with the present disclosure.Figure 4 Examples of the first DU, the network node implementing the DU, the BS 110, etc., performing operations associated with interference management and power coordination in a RAN sharing scenario.

[0079] As shown in Figure 5 some aspects, process 500 can include receiving an activation of a cell served by a network node, where the network node is associated with a first CU and a second CU, and the cell is associated with the second CU (block 520). For example, the network node (e.g., using reception component 702 depicted in FIG. 7) can receive an activation of a cell served by a network node, where the network node is associated with a first CU and a second CU, and the cell is associated with the second CU, as described above. Figure 7

[0080] As shown in Figure 5 some aspects, process 500 can include generating an intended TDD DL-UL configuration, where the intended TDD DL-UL configuration is for a cell served by the network node and associated with the second CU (block 520). For example, the network node (e.g., using generation component 708 depicted in FIG. 7) can generate an intended TDD DL-UL configuration, where the network node is associated with a first CU and a second CU, and where the intended TDD DL-UL configuration is for a cell served by the network node and associated with the second CU, as described above. Figure 7

[0081] As shown in Figure 5 some aspects, process 500 can include transmitting the intended TDD DL-UL configuration for the cell to the first CU (block 530). For example, the network node (e.g., using transmission component 704 depicted in FIG. 7) can transmit the intended TDD DL-UL configuration for the cell to the first CU, as described above. Figure 7

[0082] Process 500 can include other aspects, such as any single aspect or any combination of aspects described below and / or in connection with one or more other processes described elsewhere herein.

[0083] In a first aspect, the intended TDD DL-UL configuration is transmitted to the first CU on a signaling connection associated with an Fl control protocol.

[0084] In a second aspect, alone or in combination with the first aspect, the network node and the second CU are associated with a signaling connection associated with an Fl control protocol.

[0085] ​​​In a third aspect, alone or in combination with one or more of the first and second aspects, the network node includes a first DU associated with the first CU and a second DU associated with the second CU.

[0086] In a fourth aspect, alone or in combination with one or more of the first through third aspects, the first and second CUs are associated with a same network.

[0087] In a fifth aspect, alone or in combination with one or more of the first through fourth aspects, the first and second CUs are associated with different networks.

[0088] In a sixth aspect, alone or in combination with one or more of the first through fifth aspects, the cell is associated with a cell identifier (e.g., NCI) that identifies the second CU.

[0089] In a seventh aspect, alone or in combination with one or more of the first through sixth aspects, the cell is associated with a cell identifier (e.g., NCI) that identifies the first CU, and the cell is deactivated by the first CU or is barred from access by a child node that selects a network associated with the first CU.

[0090] In an eighth aspect, alone or in combination with one or more of the first through seventh aspects, the intended TDD DL-UL configuration indicates a transmission period for the cell.

[0091] In a ninth aspect, alone or in combination with one or more of the first through eighth aspects, the intended TDD DL-UL configuration indicates a set of slots, the set of slots having a corresponding index and slot format for the set of slots.

[0092] In a tenth aspect, alone or in combination with one or more of the first through ninth aspects, the cell is a first cell, and the network node serves a second cell.

[0093] In an eleventh aspect, alone or in combination with one or more of the first through tenth aspects, the intended TDD DL-UL configuration is a first intended TDD DL-UL configuration, and process 500 further includes transmitting, to the first CU, information indicating a second intended TDD DL-UL configuration for the second cell.

[0094] In a twelfth aspect, alone or in combination with one or more of the first through eleventh aspects, the intended TDD DL-UL configuration is for a first cell and a second cell.

[0095] In the thirteenth aspect, the second cell is associated with the first CU, either alone or in combination with one or more of the first to twelfth aspects.

[0096] In the fourteenth aspect, the second cell is associated with the second CU, either alone or in combination with one or more of the first to thirteenth aspects.

[0097] In the fifteenth aspect, the second cell is associated with the third CU, either alone or in combination with one or more of the first to fourteenth aspects.

[0098] In the sixteenth aspect, either alone or in combination with one or more of the first to fifteenth aspects, process 500 includes receiving a request from the first CU for a desired TDD DL-UL configuration, wherein the desired TDD DL-UL configuration is sent at least in part based on the request.

[0099] In the seventeenth aspect, alone or in combination with one or more of the first to sixteenth aspects, the request is directed to the anticipated TDDDL-UL configuration for merging of cells served by the network node and associated with the second CU.

[0100] although Figure 5 The illustration shows an example block of process 500, but in some respects, process 500 may include... Figure 5 The blocks depicted in the diagram are compared to additional blocks, fewer blocks, different blocks, or blocks arranged differently. Alternatively, two or more blocks of process 500 can be executed in parallel.

[0101] Figure 6 This is a diagram illustrating an exemplary process 600 performed, for example, by a first CU according to the present disclosure. Exemplary process 600 is a first CU (e.g., BS 110, such as...). Figure 3 gNB CU2 of gNB-CU, Figure 4 The first CU) is an example of performing operations related to interference management and power coordination in a RAN-shared scenario.

[0102] like Figure 6 As shown, in some aspects, process 600 may include receiving a anticipated TDD DL-UL configuration from a network node associated with a first CU and a second CU, and wherein the anticipated TDD DL-UL configuration is for a cell served by the network node and associated with the second CU (box 610). For example, the CU (e.g., using...) Figure 8The reception component 802, depicted in middle, can receive an intended TDD DL-UL configuration from a network node, where the network node is associated with a first CU and a second CU, and where the intended TDD DL-UL configuration is for a cell served by the network node and associated with the second CU, as described above.

[0103] As Figure 6 As further depicted in middle, in some aspects, process 600 can include communicating based at least in part on the intended TDD DL-UL configuration for the cell (block 620). For example, the CU (e.g., using reception component 802 or transmission component 804) can communicate based at least in part on the intended TDD DL-UL configuration for the cell, as described above. Figure 8 The reception component 802 or transmission component 804, depicted in middle, can communicate based at least in part on the intended TDD DL-UL configuration for the cell, as described above.

[0104] Process 600 can include other aspects, such as any single aspect or any combination of aspects described below and / or in connection with one or more other processes described elsewhere herein.

[0105] In a first aspect, the intended TDD DL-UL configuration is received on a signaling connection associated with an Fl control protocol.

[0106] In a second aspect, alone or in combination with the first aspect, the network node includes a first DU associated with the first CU and a second DU associated with the second CU.

[0107] In a third aspect, alone or in combination with one or more of the first and second aspects, the first CU and the second CU are associated with a same network.

[0108] In a fourth aspect, alone or in combination with one or more of the first through third aspects, the first CU and the second CU are associated with different networks.

[0109] In a fifth aspect, alone or in combination with one or more of the first through fourth aspects, the cell is associated with a cell identifier (e.g., NCI) that identifies the second CU.

[0110] In a sixth aspect, alone or in combination with one or more of the first through fifth aspects, the cell is associated with a cell identifier (e.g., NCI) that identifies the first CU, and where the cell is deactivated by the first CU or is prohibited from being accessed by a child node of a network selected to be associated with the first CU.

[0111] In a seventh aspect, alone or in combination with one or more of the first through sixth aspects, the anticipated TDD DL-UL configuration indicates a transmission periodicity for the cell.

[0112] In an eighth aspect, alone or in combination with one or more of the first through seventh aspects, the anticipated TDD DL-UL configuration indicates a set of slots having corresponding indices and slot formats for the set of slots.

[0113] In a ninth aspect, alone or in combination with one or more of the first through eighth aspects, the cell is a first cell, and wherein the network node serves a second cell.

[0114] In a tenth aspect, alone or in combination with one or more of the first through ninth aspects, the anticipated TDD DL-UL configuration is a first anticipated TDD DL-UL configuration, and the process 600 further includes receiving, from the network node, information indicating a second anticipated TDD DL-UL configuration for a second cell.

[0115] In an eleventh aspect, alone or in combination with one or more of the first through tenth aspects, the anticipated TDD DL-UL configuration is for the first cell and the second cell.

[0116] In a twelfth aspect, alone or in combination with one or more of the first through eleventh aspects, the second unit is associated with the first CU.

[0117] In a thirteenth aspect, alone or in combination with one or more of the first through twelfth aspects, the second unit is associated with the second CU.

[0118] In a fourteenth aspect, alone or in combination with one or more of the first through thirteenth aspects, the second cell is associated with a third CU.

[0119] In a fifteenth aspect, alone or in combination with one or more of the first through fourteenth aspects, the process 600 includes transmitting, to the network node, a request for an anticipated TDD DL-UL configuration, wherein receiving the anticipated TDD DL-UL configuration is based at least in part on the request.

[0120] In a sixteenth aspect, alone or in combination with one or more of the first through fifteenth aspects, the request is for a consolidated anticipated TDD DL-UL configuration for cells served by the network node and associated with the second CU.

[0121] In a seventeenth aspect, alone or in combination with one or more of the first through sixteenth aspects, communicating based at least in part on the expected TDD DL-UL configuration further comprises performing cross-link interference mitigation based at least in part on the expected TDD DL-UL configuration.

[0122] In an eighteenth aspect, alone or in combination with one or more of the first through seventeenth aspects, communicating based at least in part on the expected TDD DL-UL configuration further comprises performing power coordination for dual connectivity based at least in part on the expected TDD DL-UL configuration.

[0123] In a nineteenth aspect, alone or in combination with one or more of the first through eighteenth aspects, the network node is a first DU, and communicating based at least in part on the expected TDD DL-UL configuration further comprises forwarding the expected TDD DL-UL configuration to a second DU associated with the first CU.

[0124] In a twentieth aspect, alone or in combination with one or more of the first through nineteenth aspects, the expected TDD DL-UL configuration is a first expected TDD DL-UL configuration, and the process 600 further comprises receiving a second expected TDD DL-UL configuration.

[0125] In a twenty-first aspect, alone or in combination with one or more of the first through twentieth aspects, the process 600 comprises merging the first expected TDD DL-UL configuration with the second expected TDD DL-UL configuration.

[0126] In a twenty-second aspect, alone or in combination with one or more of the first through twenty-first aspects, the process 600 comprises forwarding the merged expected TDD DL-UL configuration to a DU associated with the first CU.

[0127] In a twenty-third aspect, alone or in combination with one or more of the first through twenty-second aspects, the process 600 comprises transmitting the expected TDD DL-UL configuration to a third CU or gNB.

[0128] Although Figure 6 FIGURE 18 illustrates example blocks of a process 1800, in accordance with Figure 6 In addition or as an alternative, two or more of the blocks of the process 1800 can be performed in parallel.

[0129] Figure 7This is a block diagram of an exemplary device 700 for wireless communication. Device 700 may be a network node, or a network node may include device 700. In some aspects, device 700 includes a receiving component 702 and a transmitting component 704, which can communicate with each other (e.g., via one or more buses and / or one or more other components). As shown, device 700 can use the receiving component 702 and the transmitting component 704 to communicate with another device 706 (such as a UE, a base station, or another wireless communication device). As further shown, among other examples, device 700 may include a generating component 708.

[0130] In some respects, device 700 can be configured to perform the functions described herein. Figures 3-4 One or more operations described herein. Alternatively or concurrently, the apparatus 700 may be configured to perform one or more processes described herein, such as Figure 5 The process is 500. In some respects, Figure 7 The illustrated device 700 and / or one or more components may include the above combination. Figure 2 The described network node consists of one or more components. Alternatively, Figure 7 One or more components shown can be combined above. Figure 2 Implemented within one or more of the described components. Alternatively, one or more of the components in this group may be implemented at least partially as software stored in memory. For example, a component (or a portion of a component) may be implemented as instructions or code stored in a non-transitory computer-readable medium and executable by a controller or processor to perform the function or operation of said component.

[0131] Receiver 702 may receive communications from device 706, such as reference signals, control information, data communications, or combinations thereof. Receiver 702 may provide the received communications to one or more other components of device 700. In some aspects, receiver 702 may perform signal processing on the received communications (among other examples, such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding), and may provide the processed signal to one or more other components of device 706. In some aspects, receiver 702 may include combinations of the above. Figure 2 The network node described includes one or more antennas, demodulators, MIMO detectors, receiver processors, controllers / processors, memory, or combinations thereof.

[0132] The transmission component 704 can transmit communications, such as reference signals, control information, data communications, or a combination thereof, to the apparatus 706. In some aspects, one or more other components of the apparatus 706 can generate communications and can provide the generated communications to the transmission component 704 for transmission to the apparatus 706. In some aspects, the transmission component 704 can perform signal processing on the generated communications (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, among other examples), and can transmit the processed signals to the apparatus 706. In some aspects, the transmission component 704 can include one or more antennas, a modulator, a transmit MIMO processor, a transmit processor, a controller / processor, a memory, or a combination thereof, of the network node described above in connection with Fig. 2. In some aspects, the transmission component 704 can be co-located with the reception component 702 in a transceiver. Figure 2 The reception component 702 can receive communications, such as reference signals, control information, data communications, or a combination thereof, from the apparatus 706. In some aspects, one or more other components of the apparatus 706 can generate communications and can provide the generated communications to the reception component 702 for transmission to the apparatus 706. In some aspects, the reception component 702 can perform signal processing on the communications received from the apparatus 706 (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, de-mapping, decoding, or the like, among other examples). In some aspects, the reception component 702 can include one or more antennas, a demodulator, a MIMO detector, a receive processor, a modulator, a transmit MIMO processor, a transmit processor, a controller / processor, a memory, or a combination thereof, of the network node described above in connection with Fig. 2. In some aspects, the reception component 702 can be co-located with the transmission component 704 in a transceiver.

[0133] The generation component 708 can generate an intended TDD DL-UL configuration, where the network node is associated with a first CU and a second CU, and where the intended TDD DL-UL configuration is for a cell served by the network node and associated with the second CU, as described above. In some aspects, the generation component 708 can include one or more antennas, a demodulator, a MIMO detector, a receive processor, a modulator, a transmit MIMO processor, a transmit processor, a controller / processor, a memory, or a combination thereof, of the network node described above in connection with Fig. 2. Figure 2 The transmission component 704 can transmit communications, such as reference signals, control information, data communications, or a combination thereof, to the apparatus 706. In some aspects, one or more other components of the apparatus 706 can generate communications and can provide the generated communications to the transmission component 704 for transmission to the apparatus 706. In some aspects, the transmission component 704 can perform signal processing on the generated communications (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, among other examples), and can transmit the processed signals to the apparatus 706. In some aspects, the transmission component 704 can include one or more antennas, a modulator, a transmit MIMO processor, a transmit processor, a controller / processor, a memory, or a combination thereof, of the network node described above in connection with Fig. 2. In some aspects, the transmission component 704 can be co-located with the reception component 702 in a transceiver.

[0134] Figure 7 The number and arrangement of components shown in Fig. 8 are provided as an example. In practice, there can be additional components, fewer components, different components, or differently arranged components than those shown in Fig. 8. Additionally or alternatively, two or more components shown in Fig. 8 can be implemented within a single component, or a single component shown in Fig. 8 can be implemented as multiple, distributed components. Furthermore, a component shown in Fig. 8 can perform one or more functions in addition to those functions shown in Fig. 8. Figure 7 Fig. 8, components instead of those components shown in Fig. 8. Additionally or alternatively, a component shown in Fig. 8 can perform one or more functions in addition to those functions shown in Fig. 8. Figure 7 Two or more components shown in Fig. 8 can be implemented within a single component, or a single component shown in Fig. 8 can be implemented as multiple, distributed components. Additionally or alternatively, a component recited in Fig. 8 can perform one or more functions in addition to those functions described herein. Figure 7 A set of one or more components in Fig. 8 can be implemented together in a single component, or separately as distinct components. Figure 7 A set of one or more components in Fig. 8 can be implemented together in a single component, or separately as distinct components. Figure 7 A set of one or more components in Fig. 8 can be implemented together in a single component, or separately as distinct components.

[0135] Figure 8This is a block diagram of an exemplary device 800 for wireless communication. Device 800 may be a CU, or a CU may include device 800. In some aspects, device 800 includes a receiving component 802 and a transmitting component 804 that can communicate with each other (e.g., via one or more buses and / or one or more other components). As shown, device 800 can use the receiving component 802 and the transmitting component 804 to communicate with another device 806 (such as a UE, a base station, or another wireless communication device). As further shown, among other examples, device 800 may include one or more of a merging component 808, a power coordination component 810, or an interference mitigation component 812.

[0136] In some respects, device 800 can be configured to perform the functions described herein. Figures 3-4 One or more operations described herein. Alternatively or concurrently, the apparatus 800 may be configured to perform one or more processes described herein, such as Figure 6 The process is 600. In some respects, Figure 8 The device 800 and / or one or more components shown may include the above combination. Figure 2 One or more components of the described CU. Alternatively or alternatively, Figure 8 One or more components shown can be combined above. Figure 2 Implemented within one or more of the described components. Alternatively, one or more of the components in this group may be implemented at least partially as software stored in memory. For example, a component (or a portion of a component) may be implemented as instructions or code stored in a non-transitory computer-readable medium and executable by a controller or processor to perform the function or operation of said component.

[0137] Receiver 802 may receive communications from device 806, such as reference signals, control information, data communications, or combinations thereof. Receiver 802 may provide the received communications to one or more other components of device 800. In some aspects, receiver 802 may perform signal processing on the received communications (among other examples, such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding), and may provide the processed signal to one or more other components of device 806. In some aspects, receiver 802 may include combinations of the above. Figure 2 The BS110 may include one or more antennas, demodulators, MIMO detectors, receiver processors, controllers / processors, memory, or combinations thereof.

[0138] The transmission component 804 can transmit communications, such as reference signals, control information, data communications, or a combination thereof, to the apparatus 806. In some aspects, one or more other components of the apparatus 806 can generate communications and can provide the generated communications to the transmission component 804 for transmission to the apparatus 806. In some aspects, the transmission component 804 can perform signal processing on the generated communications (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, among other examples), and can transmit the processed signals to the apparatus 806. In some aspects, the transmission component 804 can include one or more antennas, a modulator, a transmit MIMO processor, a transmit processor, a controller / processor, a memory, or a combination thereof, of the BS 110 described above in connection with Fig. 2. In some aspects, the transmission component 804 can be co-located with the reception component 802 in a transceiver. Figure 2 The reception component 802 can receive an intended TDD DL-UL configuration from a network node, where the network node is associated with the first CU and the second CU, and where the intended TDD DL-UL configuration is for a cell served by the network node and associated with the second CU. The reception component 802 or the transmission component 804 can communicate based at least in part on the intended TDD DL-UL configuration for the cell.

[0139] The transmission component 804 can transmit a request for an intended TDD DL-UL configuration to the network node, where receiving the intended TDD DL-UL configuration is based at least in part on the request.

[0140] The transmission component 804 can transmit a request for an intended TDD DL-UL configuration to the network node, where receiving the intended TDD DL-UL configuration is based at least in part on the request.

[0141] The merging component 808 can merge the first intended TDD DL-UL configuration and the second intended TDD DL-UL configuration. In some aspects, the merging component 808 can include one or more antennas, a demodulator, a MIMO detector, a receive processor, a modulator, a transmit MIMO processor, a transmit processor, a controller / processor, a memory, or a combination thereof, of the BS 110 described above in connection with Fig. 2. Figure 2 The reception component 802 can receive an intended TDD DL-UL configuration from a network node, where the network node is associated with the first CU and the second CU, and where the intended TDD DL-UL configuration is for a cell served by the network node and associated with the second CU. The reception component 802 or the transmission component 804 can communicate based at least in part on the intended TDD DL-UL configuration for the cell.

[0142] The transmission component 804 can forward the merged intended TDD DL-UL configuration to a DU associated with the first CU. The transmission component 804 can transmit the intended TDD DL-UL configuration to a third CU or a gNB.

[0143] The power coordination component 810 can perform power coordination for dual connectivity based at least in part on the intended TDD DL-UL configuration. In some aspects, the power coordination component 810 can include one or more antennas, a demodulator, a MIMO detector, a receive processor, a modulator, a transmit MIMO processor, a transmit processor, a controller / processor, a memory, or a combination thereof, of the BS 110 described above in connection with Fig. 2. Figure 2one or more antennas, a demodulator, a MIMO detector, a receive processor, a modulator, a transmit MIMO processor, a transmit processor, a controller / processor, a memory, or combinations thereof.

[0144] The interference mitigation component 812 can perform cross-link interference mitigation based at least in part on the intended TDD DL-UL configuration. In some aspects, the interference mitigation component 812 can include one or more components of the BS 110 described above in connection with the interference mitigation component 812, which can perform cross-link interference mitigation based at least in part on the intended TDD DL-UL configuration. Figure 2 one or more antennas, a demodulator, a MIMO detector, a receive processor, a modulator, a transmit MIMO processor, a transmit processor, a controller / processor, a memory, or combinations thereof.

[0145] Figure 8 The number and arrangement of components shown in FIG. 12 are provided as an example. In practice, there can be additional components, fewer components, different components, or differently arranged components than those shown in FIG. 12. Additionally or alternatively, two or more components shown in FIG. 12 can be implemented within a single component, or a single component shown in FIG. 12 can be implemented as multiple, distributed components. Additionally or alternatively, a component recited as being configured to perform a particular function Figure 8 may include more, fewer, different, or differently arranged components than those shown in FIG. 12. Additionally or alternatively, two or more components shown in FIG. 12 can be implemented within a single component, or a single component shown in FIG. 12 can be implemented as multiple, distributed components. Additionally or alternatively, a component recited as being configured to perform a particular function can actually include one or more other components that facilitate the performance of the recited Figure 8 two or more components shown can be implemented within a single component, or a single component shown can be implemented as multiple, distributed components. Additionally or alternatively, Figure 8 a set of one or more components shown in FIG. 12 can perform one or more functions described as being performed by another set of one or more components shown in FIG. 12. Figure 8 a set of one or more components shown in FIG. 12 can perform one or more functions described as being performed by another set of one or more components shown in FIG. 12. Figure 8

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

[0147] Aspect 1 : A method of wireless communication performed by a network node, the method comprising: generating an intended time division duplex (TDD) downlink- uplink (DL-UL) configuration, wherein the network node is associated with a first central unit (CU) and a second CU, and wherein the intended TDD DL-UL configuration is for a cell served by the network node and associated with the second CU; and transmitting the intended TDD DL-UL configuration for the cell to the first CU.

[0148] Aspect 2: The method of any of the preceding aspects, wherein the intended TDD DL-UL configuration is transmitted to the first CU on a signaling connection associated with an Fl control protocol.

[0149] Aspect 3: The method of any of the preceding aspects, wherein the network node and the second CU are associated with a signaling connection associated with an Fl control protocol.

[0150] ​Aspect 4: The method of any of the preceding aspects, wherein the network node comprises a first distributed unit (DU) associated with the first CU and a second DU associated with the second CU.

[0151] Aspect 5: The method of any of the preceding aspects, wherein the first CU and the second CU are associated with a same network.

[0152] Aspect 6: The method of any of the preceding aspects, wherein the first CU and the second CU are associated with different networks.

[0153] Aspect 7: The method of any of the preceding aspects, wherein the cell is associated with a cell identifier that identifies the second CU.

[0154] Aspect 8: The method of any of the preceding aspects, wherein the cell is associated with a cell identifier that identifies the first CU, and wherein the cell is deactivated by the first CU or is barred from access by a child node of the network selected to be associated with the first CU.

[0155] Aspect 9: The method of any of the preceding aspects, wherein the intended TDD DL-UL configuration indicates a transmission period for a cell.

[0156] Aspect 10: The method of any of the preceding aspects, wherein the intended TDD DL-UL configuration indicates a set of slots having corresponding indices and slot formats for the set of slots.

[0157] Aspect 11 : The method of any of the preceding aspects, wherein the cell is a first cell, and wherein the network node serves a second cell.

[0158] Aspect 12: The method of aspect 11, wherein the intended TDD DL-UL configuration is a first intended TDD DL-UL configuration, and wherein the method further comprises: transmitting, to the first CU, information indicating a second intended TDD DL-UL configuration for the second cell.

[0159] Aspect 13: The method of aspect 11, wherein the intended TDD DL-UL configuration is for the first cell and the second cell.

[0160] Aspect 14: The method of aspect 11, wherein the second unit is associated with the first CU.

[0161] Aspect 15: The method of aspect 11, wherein the second unit is associated with the second CU.

[0162] Aspect 16: The method of aspect 11, wherein the second unit is associated with a third CU.

[0163] Aspect 17: The method of any of the preceding aspects, further comprising: receiving a request from the first CU for the intended TDD DL-UL configuration, wherein transmitting the intended TDD DL-UL configuration is based at least in part on the request.

[0164] Aspect 18: The method of aspect 17, wherein the request is for an intended TDD DL-UL configuration for consolidation of cells served by the network node and associated with the second CU.

[0165] Aspect 19: A method of wireless communication performed by a first central unit (CU), the method comprising: receiving, from a network node, an intended time division duplex (TDD) downlink-uplink (DL-UL) configuration, wherein the network node is associated with the first CU and a second CU, and wherein the intended TDD DL-UL configuration is for a cell served by the network node and associated with the second CU; and communicating based at least in part on the intended TDD DL-UL configuration for the cell.

[0166] Aspect 20: The method of aspect 19, wherein the intended TDD DL-UL configuration is received on a signaling connection associated with an Fl control protocol.

[0167] Aspect 21: The method of any of aspects 19-20, wherein the network node comprises a first distributed unit (DU) associated with the first CU and a second DU associated with the second CU.

[0168] Aspect 22: The method of any of aspects 19-21, wherein the first CU and the second CU are associated with a same network.

[0169] Aspect 23: The method of any of aspects 19-22, wherein the first CU and the second CU are associated with different networks.

[0170] Aspect 24: The method of any of aspects 19-23, wherein the cell is associated with a cell identifier that identifies the second CU.

[0171] Aspect 25: The method of any of aspects 19-24, wherein the cell is associated with a cell identifier that identifies the first CU, and wherein the cell is deactivated by the first CU or is prohibited from being accessed by a child node of a network selected to be associated with the first CU.

[0172] Aspect 26: The method of any of aspects 19-25, wherein the intended TDD DL-UL configuration indicates a transmission period for the cell.

[0173] Aspect 27: The method of any of aspects 19-26, wherein the intended TDD DL-UL configuration indicates a set of slots, the set of slots having a corresponding index and slot format for the set of slots.

[0174] Aspect 28: The method of any of aspects 19-27, wherein the cell is a first cell, and wherein the network node serves a second cell.

[0175] Aspect 29: The method of aspect 28, wherein the intended TDD DL-UL configuration is a first intended TDD DL-UL configuration, and wherein the method further comprises: receiving, from the network node, information indicating a second intended TDD DL-UL configuration for the second cell.

[0176] Aspect 30: The method of aspect 28, wherein the intended TDD DL-UL configuration is for the first cell and the second cell.

[0177] Aspect 31: The method of aspect 28, wherein the second unit is associated with the first CU.

[0178] Aspect 32: The method of aspect 28, wherein the second unit is associated with the second CU.

[0179] Aspect 33: The method of aspect 28, wherein the second unit is associated with a third CU.

[0180] Aspect 34: The method of any of aspects 19-33, the method further comprising: transmitting, to the network node, a request for the intended TDD DL-UL configuration, wherein receiving the intended TDD DL-UL configuration is based at least in part on the request.

[0181] Aspect 35: The method of aspect 34, wherein the request is for a consolidated intended TDD DL-UL configuration for cells served by the network node and associated with the second CU.

[0182] Aspect 36: The method of any of aspects 19-35, wherein communicating based at least in part on the intended TDD DL-UL configuration further comprises: performing cross-link interference mitigation based at least in part on the intended TDD DL-UL configuration.

[0183] Aspect 37: The method of any of aspects 19-36, wherein communicating based at least in part on the intended TDD DL-UL configuration further comprises: performing power coordination for dual connectivity based at least in part on the intended TDD DL-UL configuration.

[0184] Aspect 38: The method of any of aspects 19-37, wherein the network node is a first distributed unit (DU), and wherein communicating based at least in part on the expected TDD DL-UL configuration further comprises forwarding the expected TDD DL-UL configuration to a second DU associated with the first CU.

[0185] Aspect 39: The method of any of aspects 19-38, wherein the expected TDD DL-UL configuration is a first expected TDD DL-UL configuration, and wherein the method further comprises receiving a second expected TDD DL-UL configuration.

[0186] Aspect 40: The method of aspect 39, further comprising merging the first expected TDD DL-UL configuration and the second expected TDD DL-UL configuration.

[0187] Aspect 41: The method of aspect 40, further comprising forwarding the merged expected TDD DL-UL configuration to a distributed unit (DU) associated with the first CU.

[0188] Aspect 42: The method of any of aspects 19-41, further comprising transmitting the expected TDD DL-UL configuration to a third CU or gNB.

[0189] Aspect 43: A method of wireless communication performed by a network node, the method comprising: receiving an activation of a cell served by the network node, wherein the network node is associated with a first central unit (CU) and a second CU, and the cell is associated with the second CU; and transmitting, to the first CU, an expected time division duplex (TDD) downlink-uplink (DL-UL) configuration for the cell.

[0190] Aspect 44: The method of aspect 43, wherein the expected TDD DL-UL configuration is transmitted to the first CU on a signaling connection associated with an Fl control protocol.

[0191] Aspect 45: The method of any of aspects 43-44, wherein the network node and the second CU are associated with a signaling connection associated with an Fl control protocol.

[0192] Aspect 46: The method of any of aspects 43-45, wherein the network node comprises a first distributed unit (DU) associated with the first CU and a second DU associated with the second CU.

[0193] Aspect 47: The method of any of aspects 43-46, wherein the first CU and the second CU are associated with a same network.

[0194] Aspect 48: The method of any of aspects 43-47, wherein the first CU and the second CU are associated with different networks.

[0195] Aspect 49: The method of any of aspects 43-48, wherein the cell is associated with a cell identifier that identifies the second CU.

[0196] Aspect 50: The method of any of aspects 43-49, wherein the cell is associated with a cell identifier that identifies the first CU, and wherein the cell is deactivated by the first CU or is prohibited from being accessed by child nodes of the network that are selected to be associated with the first CU.

[0197] Aspect 51 : The method of any of aspects 43-50, wherein the intended TDD DL-UL configuration indicates a transmission period for a cell.

[0198] Aspect 52: The method of any of aspects 43-51, wherein the intended TDD DL-UL configuration indicates a set of slots having corresponding indices and slot formats for the set of slots.

[0199] Aspect 53: The method of any of aspects 43-52, wherein the cell is a first cell, and wherein the network node serves a second cell, and wherein the intended TDD DL-UL configuration is for the first cell and the second cell.

[0200] Aspect 54: The method of aspect 53, wherein the second cell is associated with one of: the first CU, the second CU, or a third CU.

[0201] Aspect 55: The method of any of aspects 43-54, further comprising: receiving a request for the intended TDD DL-UL configuration from the first CU, wherein transmitting the intended TDD DL-UL configuration is based at least in part on the request.

[0202] Aspect 56: The method of aspect 55, wherein the request is for a consolidated intended TDD DL-UL configuration for cells served by the network node and associated with the second CU.

[0203] Aspect 57: A method of wireless communication performed by a first central unit (CU), the method comprising: receiving, from a network node, an intended time division duplex (TDD) downlink-uplink (DL-UL) configuration, wherein the network node is associated with the first CU and a second CU, and wherein the intended TDD DL-UL configuration is for a cell served by the network node and associated with the second CU; and communicating based at least in part on the intended TDD DL-UL configuration for the cell.

[0204] Aspect 58: The method of aspect 57, wherein the first CU and the second CU are associated with a same network.

[0205] Aspect 59: The method of any of aspects 57-58, wherein the first CU and the second CU are associated with different networks.

[0206] Aspect 60: The method of any of aspects 57-59, wherein the cell is associated with a cell identifier that identifies the second CU.

[0207] Aspect 61 : The method of any of aspects 57-60, wherein the cell is associated with a cell identifier that identifies the first CU, and wherein the cell is deactivated by the first CU or is barred from access by child nodes of the network selected to be associated with the first CU.

[0208] Aspect 62: The method of any of aspects 57-61, wherein the cell is a first cell, and wherein the network node serves a second cell, and wherein the intended TDD DL-UL configuration is for the first cell and the second cell.

[0209] Aspect 63: The method of aspect 62, wherein the second cell is associated with one of: the first CU, the second CU, or a third CU.

[0210] Aspect 64: The method of any of aspects 57-63, further comprising: transmitting, to the network node, a request for the intended TDD DL-UL configuration, wherein receiving the intended TDD DL-UL configuration is based at least in part on the request.

[0211] Aspect 65: The method of aspect 64, wherein the request is for a consolidated intended TDD DL-UL configuration for cells served by the network node and associated with the second CU.

[0212] Aspect 66: The method of any of aspects 57-65, wherein communicating based at least in part on the intended TDD DL-UL configuration further comprises: performing cross-link interference mitigation based at least in part on the intended TDD DL-UL configuration.

[0213] Aspect 67: The method of any of aspects 57-66, wherein communicating based at least in part on the intended TDD DL-UL configuration further comprises: performing power coordination for dual connectivity based at least in part on the intended TDD DL-UL configuration.

[0214] Aspect 68: The method of any of aspects 57-67, wherein the network node is a first distributed unit (DU), and wherein communicating based at least in part on the expected TDD DL-UL configuration further comprises forwarding the expected TDD DL-UL configuration to a second DU associated with the first CU.

[0215] Aspect 69: The method of any of aspects 57-68, wherein the expected TDD DL-UL configuration is a first expected TDD DL-UL configuration, and wherein the method further comprises: receiving a second expected TDD DL-UL configuration; merging the first expected TDD DL-UL configuration and the second expected TDD DL-UL configuration; and forwarding the merged expected TDD DL-UL configuration to a distributed unit (DU) associated with the first CU.

[0216] Aspect 70: The method of any of aspects 57-69, further comprising: transmitting the expected TDD DL-UL configuration to a third CU or gNB.

[0217] Aspect 71: An apparatus for wireless communication at a device, the apparatus comprising a processor; memory coupled with the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform the method of one or more aspects of aspects 1-70.

[0218] Aspect 72: A device for wireless communication, the device comprising a memory and one or more processors coupled to the memory, the one or more processors configured to perform the method of one or more aspects of aspects 1-70.

[0219] Aspect 73: An apparatus for wireless communication, the apparatus comprising at least one means for performing the method of one or more aspects of aspects 1-70.

[0220] Aspect 74: A non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by a processor to perform the method of one or more aspects of aspects 1-70.

[0221] Aspect 75: A non-transitory computer-readable medium storing a set of instructions for wireless communication, the set of instructions comprising one or more instructions that, when executed by one or more processors of a device, cause the device to perform the method of one or more aspects of aspects 1-70.

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

[0223] As used herein, the term “component” is intended to be broadly interpreted to encompass hardware and / or a combination of hardware and software. Software shall be broadly interpreted to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, and / or functions, among other examples, whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise. As used herein, a processor is implemented in hardware and / or a combination of hardware and software. It will be clearly understood that the systems and / or methods described herein can be implemented in various forms of hardware and / or combinations of hardware and software. Specific details of components or processes are not to be understood as limiting, and the

[0224] As used herein, meeting a threshold can refer to being greater than the threshold, being greater than or equal to the threshold, being less than or equal to the threshold, not being equal to the threshold, etc., depending on the context.

[0225] Although specific combinations of features are recited in the claims and / or disclosed in the specification, these combinations are not intended to limit the disclosure of different aspects. In fact, many of these features can be combined in ways not specifically recited in the claims and / or disclosed in the specification. Although each dependent claim listed below can directly depend on only one claim, the disclosure of different aspects includes each dependent claim in combination with every other claim in the set in which it is found. As used herein, a phrase referring to “at least one of’ a list of items refers to any combination of those items, including single members. As an example, “at least one of a, b, or c” is intended to cover a, b, c, a-b, a-c, b-c, and a-b-c, as well as any combination of items from among a, b, and c (e.g., a-a, a-a-a, a-a-b, a-a-c, a-b-b, a-c-c, b-b, b-b-b, b-b-c, c-c, and c-c-c, or any other ordering of a, b, and c).

[0226] No element, act, or instruction used herein should be construed as critical or essential unless explicitly described as such. Also, as used herein, the articles “a” and “an” are intended to include one or more items, and can be used interchangeably with “one or more.” Furthermore, as used herein, the article “the” is intended to include one or more items referenced, and can be used interchangeably with “the one or more.” Also, as used herein, the terms “set” and “group” are intended to include one or more items (for example, related items, unrelated items, a combination of related and unrelated items), and can be used interchangeably with “one or more.” Where only one item is intended, the phrase “only one” or similar language is used. Also, as used herein, the terms “has,” “have,” “having,” or the like are intended to be open-ended terms. Further, the phrase “based on” is intended to mean “based, at least in part, on” unless explicitly stated otherwise. Also, as used herein, the term “or” is intended to be inclusive when used in a series and can be used interchangeably with “and / or,” unless explicitly stated otherwise (e.g., if used in combination with “either… or,” “only one of the… or”).

Claims

1. A network node for wireless communication, comprising: One or more memory units; and One or more processors coupled to the one or more memories, at least one of the one or more processors being operable to cause the network node to: Receive activation for a cell served by the network node, wherein the network node includes signaling connections to a first central unit (CU) and a second CU, and the cell is served by the second CU; as well as Send the expected time-division duplex (TDD) downlink-uplink (DL-UL) configuration for the cell served by the second CU to the first CU.

2. The network node of claim 1, wherein the intended TDD DL-UL configuration is sent to the first CU over a signaling connection associated with the F1 control protocol.

3. The network node of claim 1, wherein the network node and the second CU are associated with a signaling connection associated with the F1 control protocol.

4. The network node of claim 1, wherein the network node comprises a first distributed unit (DU) associated with the first CU and a second DU associated with the second CU.

5. The network node of claim 1, wherein the first CU and the second CU are associated with the same network.

6. The network node of claim 1, wherein the first CU and the second CU are associated with different networks.

7. The network node of claim 1, wherein the cell is associated with a cell identifier that identifies the second CU.

8. The network node of claim 1, wherein the cell is associated with a cell identifier that identifies the first CU, and wherein the cell is deactivated by the first CU or is prohibited from access by a child node of the network associated with the first CU.

9. The network node of claim 1, wherein the intended TDD DL-UL configuration indicates the transmission period for the cell.

10. The network node of claim 1, wherein the intended TDD DL-UL configuration indicates a set of time slots having a corresponding index and time slot format for the set of time slots.

11. The network node of claim 1, wherein the cell is a first cell, and wherein the network node serves a second cell, and wherein the intended TDD DL-UL configuration is used for both the first cell and the second cell.

12. The network node of claim 11, wherein the second cell is associated with one of the following: The first CU, The second CU, or Third CU.

13. The network node of claim 1, wherein at least one of the one or more processors is further operable to cause the network node to: A request for the intended TDD DL-UL configuration is received from the first CU, wherein the intended TDD DL-UL configuration is sent at least in part based on the request.

14. The network node of claim 13, wherein the request is for a proposed TDD DL-UL configuration for merging of cells served by the network node and associated with the second CU.

15. A first central unit (CU) for wireless communication, comprising: One or more memory units; and One or more processors coupled to the one or more memories, at least one of the one or more processors being operable to cause the first CU to: Receive a planned Time Division Duplex (TDD) downlink-uplink (DL-UL) configuration from a network node, wherein the network node includes signaling connections to the first CU and the second CU, and wherein the planned TDD DL-UL configuration is for use by the network node with the cell served by the second CU; and Communication is based at least in part on the intended TDD DL-UL configuration for the cell.

16. The first CU of claim 15, wherein the first CU and the second CU are associated with the same network.

17. The first CU of claim 15, wherein the first CU and the second CU are associated with different networks.

18. The first CU of claim 15, wherein the cell is associated with a cell identifier that identifies the second CU.

19. The first CU of claim 15, wherein the cell is associated with a cell identifier that identifies the first CU, and wherein the cell is deactivated by the first CU or is prohibited from access by a child node of a network selected to be associated with the first CU.

20. The first CU of claim 15, wherein the cell is a first cell, and wherein the network node serves a second cell, and wherein the intended TDD DL-UL configuration is used for the first cell and the second cell.

21. The first CU of claim 20, wherein the second cell is associated with one of the following: The first CU, The second CU, or Third CU.

22. The first CU of claim 15, wherein at least one of the one or more processors is further operable to cause the first CU to: Send a request to the network node for the expected TDD DL-UL configuration, wherein receiving the expected TDD DL-UL configuration is at least in part based on the request.

23. The first CU of claim 22, wherein the request is for a proposed TDD DL-UL configuration for merging of cells served by the network node and associated with the second CU.

24. The first CU of claim 15, wherein, in order to communicate at least in part based on the intended TDD DL-UL configuration, at least one of the one or more processors is also operable to cause the first CU to: Cross-link interference mitigation is performed at least in part based on the anticipated TDD DL-UL configuration.

25. The first CU of claim 15, wherein, in order to communicate at least in part based on the intended TDD DL-UL configuration, at least one of the one or more processors is operable to cause the first CU to: Power coordination for dual connectivity is performed, at least in part, based on the anticipated TDD DL-UL configuration.

26. The first CU of claim 15, wherein the network node is a first distributed unit (DU), and wherein, in order to communicate at least in part based on the intended TDD DL-UL configuration, at least one of the one or more processors is operable to cause the first CU to: The intended TDD DL-UL configuration is forwarded to the second DU associated with the first CU.

27. The first CU of claim 15, wherein the intended TDD DL-UL configuration is a first intended TDD DL-UL configuration, and wherein at least one of the one or more processors is operable to cause the first CU to: Receive the second expected TDD DL-UL configuration; Merge the first anticipated TDD DL-UL configuration and the second anticipated TDD DL-UL configuration; and The merged expected TDD DL-UL configuration is forwarded to the distributed unit DU associated with the first CU.

28. The first CU of claim 15, wherein at least one of the one or more processors is operable to cause the first CU to: Send the expected TDD DL-UL configuration to the third CU or gNB.

29. A method for wireless communication performed by a network node, comprising: Receive activation for a cell served by the network node, wherein the network node includes signaling connections to a first central unit (CU) and a second CU, and wherein the cell is served by the second CU; and Send the expected time-division duplex (TDD) downlink-uplink (DL-UL) configuration for the cell served by the second CU to the first CU.

30. A method for wireless communication performed by a first central unit (CU), comprising: Receive a planned Time Division Duplex (TDD) downlink-uplink (DL-UL) configuration from a network node, wherein the network node includes signaling connections to the first CU and the second CU, and wherein the planned TDD DL-UL configuration is for use by the network node with the cell served by the second CU; and Communication is based at least in part on the intended TDD DL-UL configuration for the cell.

31. A computer program product comprising computer-readable instructions that, when executed by a processor, cause the processor to perform the method of claim 29.

32. A computer program product comprising computer-readable instructions that, when executed by a processor, cause the processor to perform the method of claim 30.

Images